From 2be405592fcb720a4137a3e153ef3485ed8553b0 Mon Sep 17 00:00:00 2001 From: Travis Smith Date: Thu, 8 Apr 2021 16:46:48 -0600 Subject: [PATCH] otguide2.5 to master --- sites/oteguide/404.html | 2 +- sites/oteguide/404/index.html | 2 +- .../OT&E_Guide/1-1-introduction/index.html | 4 +- .../1-3-fielding-combat-capes/index.html | 4 +- .../1-5-acquisition-pathways/index.html | 4 +- .../OT&E_Guide/1-6-art-principles/index.html | 4 +- .../2-test-lifecycle-overview/index.html | 4 +- .../3-1-involvement-decision/index.html | 4 +- .../3-2-standing-activities/index.html | 4 +- .../OT&E_Guide/3-3-test-strategy/index.html | 4 +- .../OT&E_Guide/4-1-levels-of-test/index.html | 4 +- .../4-2-OT-test-activity-cycles/index.html | 4 +- .../OT&E_Guide/4-3-OT-construct/index.html | 4 +- .../4-4-building-the-ot-construct/index.html | 4 +- .../5-test-lifecycle-exit/index.html | 4 +- .../6-0-ot-business-practices/index.html | 4 +- .../OT&E_Guide/6-1-1-tasking/index.html | 4 +- .../OT&E_Guide/6-1-2-team-standup/index.html | 4 +- .../OT&E_Guide/6-1-3-team-training/index.html | 4 +- .../OT&E_Guide/6-2-risk-management/index.html | 4 +- .../OT&E_Guide/6-3-resources/index.html | 4 +- .../6-4-coordination-across-afotec/index.html | 4 +- .../index.html | 4 +- sites/oteguide/OT&E_Guide/6-6-acap/index.html | 4 +- .../OT&E_Guide/6-7-case-study/index.html | 4 +- sites/oteguide/OT&E_Guide/index.html | 2 +- .../1-2-INTRODUCTION/index.html | 36 + .../index.html | 48 + .../index.html | 35 + .../index.html | 59 + .../index.html | 40 + .../index.html | 20 + .../1-8-Battlespace-Development/index.html | 365 ++++ .../1-9-Evaluation-Summary-Chart/index.html | 34 + .../2-1-Test-Design/index.html | 89 + .../2-2-Measures-Development/index.html | 58 + .../2-3-Test-Execution-Planning/index.html | 377 ++++ .../index.html | 49 + .../index.html | 10 + .../1-2-INTRODUCTION/index.html | 26 + .../index.html | 24 + .../index.html | 27 + .../index.html | 28 + .../index.html | 16 + .../1-7-Accreditation-Concepts/index.html | 21 + .../1-8-Risk-Matrix:-Example/index.html | 43 + .../1-9-Previous-Accreditation/index.html | 37 + .../2-1-Accreditation-Process/index.html | 64 + .../index.html | 38 + .../index.html | 20 + .../index.html | 12 + .../index.html | 24 + .../index.html | 28 + .../2-7-Best-Practices/index.html | 18 + .../2-8-Summary/index.html | 28 + .../2-9-References-and-Resources/index.html | 67 + .../3-1-Governance/index.html | 24 + .../3-2-Points-of-Contact/index.html | 12 + sites/oteguide/accreditation_guide/index.html | 10 + sites/oteguide/acronyms/index.html | 6 +- .../1-2-OVERVIEW/index.html | 50 + .../index.html | 37 + .../index.html | 82 + .../1-5-GOALS-AND-TYPES-OF-TEST/index.html | 20 + .../1-6-Characterize/index.html | 24 + .../1-7-Compare/index.html | 13 + .../1-8-Problem-Identification/index.html | 22 + .../1-9-TYPES-OF-TEST-DESIGNS/index.html | 22 + .../2-1-Factorials/index.html | 310 ++++ .../index.html | 152 ++ .../2-3-Augmented-Designs/index.html | 57 + .../index.html | 74 + .../index.html | 19 + .../index.html | 20 + .../index.html | 123 ++ .../2-8-Demonstrations/index.html | 30 + .../2-9-Cases/index.html | 18 + .../3-1-Observational-Studies/index.html | 121 ++ .../index.html | 18 + .../3-3-Power/index.html | 38 + .../3-4-Optimality-Efficiency/index.html | 25 + .../index.html | 57 + .../3-6-Prediction-Variance/index.html | 47 + .../index.html | 42 + .../index.html | 15 + .../3-9-Randomization/index.html | 29 + .../4-1-Replication/index.html | 25 + .../4-2-Blocking/index.html | 60 + .../4-3-TYPICAL-SITUATIONS/index.html | 197 ++ .../index.html | 34 + .../4-5-Appendices/index.html | 10 + .../4-6-Test-Design-Guidance/index.html | 21 + .../index.html | 42 + .../4-8-Footnotes/index.html | 97 + .../analyst_test_design_guide/index.html | 10 + ...c7b4bf2.js => app-03e333c274b6bc210459.js} | 6 +- ...> app-03e333c274b6bc210459.js.LICENSE.txt} | 0 .../oteguide/app-03e333c274b6bc210459.js.map | 1 + .../oteguide/app-eec04d2f552ddc7b4bf2.js.map | 1 - sites/oteguide/chunk-map.json | 2 +- .../1-2-PURPOSE/index.html | 25 + .../index.html | 30 + .../1-4-Consistency-is-Key/index.html | 13 + .../1-5-One-Voice/index.html | 14 + .../1-6-Templates/index.html | 24 + .../1-7-Microsoft-Word-Options/index.html | 17 + .../1-8-Focus-Areas/index.html | 12 + .../1-9-Styles/index.html | 40 + .../2-1-Acronyms/index.html | 45 + .../2-2-Commas/index.html | 15 + .../2-3-Next-Page-and-Page-Breaks/index.html | 22 + .../2-4-Headers-and-Footers/index.html | 23 + .../2-5-Page-Numbering/index.html | 15 + .../2-6-Blank-Pages/index.html | 18 + .../2-7-Capitalization/index.html | 26 + .../index.html | 16 + .../2-9-Vertical-Lists/index.html | 18 + .../index.html | 15 + .../3-2-Tables/index.html | 32 + .../3-3-Figures/index.html | 26 + .../3-4-Passive-Voice/index.html | 14 + .../3-5-Copyrights-and-Trademarks/index.html | 25 + .../3-6-Wordiness/index.html | 12 + .../index.html | 33 + .../3-8-Apostrophes/index.html | 17 + .../3-9-Choppy-Sentences/index.html | 14 + .../4-1-Numbers/index.html | 13 + .../4-2-Dates/index.html | 19 + .../4-3-Abbreviations/index.html | 13 + .../4-4-Terms/index.html | 20 + .../index.html | 12 + .../4-6-Verb-Tenses/index.html | 13 + .../4-7-Embedded-Files/index.html | 17 + .../4-8-Converting-Pictures/index.html | 24 + .../index.html | 24 + .../5-1-Patches/index.html | 16 + .../5-2-Classification-Markings}/index.html | 48 +- .../5-3-Distribution-List/index.html | 18 + .../index.html | 41 + .../5-5-Spell-Check/index.html | 12 + .../5-6-Configuration-Control/index.html | 27 + .../5-7-Table-of-Contents/index.html | 14 + .../5-8-Standardization-Checklist/index.html | 12 + .../oteguide/editing_reports_guide/index.html | 13 + .../2-INTRODUCTION/index.html | 18 + .../3-TEST-ACTIVITY-SEQUENCE/index.html | 19 + .../index.html | 45 + .../5-STRUCTURE-OF-AN-EVALUATION/index.html | 79 + .../evaluation_and_reporting_guide/index.html | 10 + .../index.html | 1100 ----------- .../analyst_test_design_guide/index.html | 1621 ----------------- .../editing_reports_guide/index.html | 470 ----- .../evaluation_and_reporting_guide/index.html | 1054 ----------- sites/oteguide/fn_guides/index.html | 4 +- sites/oteguide/glossary/index.html | 4 +- sites/oteguide/index.html | 2 +- .../1-2-INTRODUCTION-AND-INTENT}/index.html | 109 +- .../index.html | 29 + .../1-4-Policy-Guidance/index.html | 11 + .../1-5-PROCESS/index.html | 33 + .../oteguide/lessons_learned_guide/index.html | 10 + .../measures_guide/2-INTRODUCTION/index.html | 19 + .../index.html | 85 + .../index.html | 132 ++ .../index.html | 99 + .../index.html | 619 +------ .../index.html | 10 + .../index.html | 677 ++++--- sites/oteguide/measures_guide/index.html | 10 + .../1-1-introduction/page-data.json | 2 +- .../1-3-fielding-combat-capes/page-data.json | 2 +- .../1-5-acquisition-pathways/page-data.json | 2 +- .../1-6-art-principles/page-data.json | 2 +- .../2-test-lifecycle-overview/page-data.json | 2 +- .../3-1-involvement-decision/page-data.json | 2 +- .../3-2-standing-activities/page-data.json | 2 +- .../3-3-test-strategy/page-data.json | 2 +- .../4-1-levels-of-test/page-data.json | 2 +- .../page-data.json | 2 +- .../4-3-OT-construct/page-data.json | 2 +- .../page-data.json | 2 +- .../5-test-lifecycle-exit/page-data.json | 2 +- .../6-0-ot-business-practices/page-data.json | 2 +- .../OT&E_Guide/6-1-1-tasking/page-data.json | 2 +- .../6-1-2-team-standup/page-data.json | 2 +- .../6-1-3-team-training/page-data.json | 2 +- .../6-2-risk-management/page-data.json | 2 +- .../OT&E_Guide/6-3-resources/page-data.json | 2 +- .../page-data.json | 2 +- .../page-data.json | 2 +- .../OT&E_Guide/6-6-acap/page-data.json | 2 +- .../OT&E_Guide/6-7-case-study/page-data.json | 2 +- .../page-data/OT&E_Guide/page-data.json | 2 +- .../1-2-INTRODUCTION/page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../2-1-Test-Design/page-data.json | 1 + .../2-2-Measures-Development/page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../1-2-INTRODUCTION/page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../1-7-Accreditation-Concepts/page-data.json | 1 + .../1-8-Risk-Matrix:-Example/page-data.json | 1 + .../1-9-Previous-Accreditation/page-data.json | 1 + .../2-1-Accreditation-Process/page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../2-7-Best-Practices/page-data.json | 1 + .../2-8-Summary/page-data.json | 1 + .../page-data.json | 1 + .../3-1-Governance/page-data.json | 1 + .../3-2-Points-of-Contact/page-data.json | 1 + .../accreditation_guide/page-data.json | 1 + .../page-data/acronyms/page-data.json | 2 +- .../1-2-OVERVIEW/page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../1-6-Characterize/page-data.json | 1 + .../1-7-Compare/page-data.json | 1 + .../1-8-Problem-Identification/page-data.json | 1 + .../1-9-TYPES-OF-TEST-DESIGNS/page-data.json | 1 + .../2-1-Factorials/page-data.json | 1 + .../page-data.json | 1 + .../2-3-Augmented-Designs/page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../2-8-Demonstrations/page-data.json | 1 + .../2-9-Cases/page-data.json | 1 + .../3-1-Observational-Studies/page-data.json | 1 + .../page-data.json | 1 + .../3-3-Power/page-data.json | 1 + .../3-4-Optimality-Efficiency/page-data.json | 1 + .../page-data.json | 1 + .../3-6-Prediction-Variance/page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../3-9-Randomization/page-data.json | 1 + .../4-1-Replication/page-data.json | 1 + .../4-2-Blocking/page-data.json | 1 + .../4-3-TYPICAL-SITUATIONS/page-data.json | 1 + .../page-data.json | 1 + .../4-5-Appendices/page-data.json | 1 + .../4-6-Test-Design-Guidance/page-data.json | 1 + .../page-data.json | 1 + .../4-8-Footnotes/page-data.json | 1 + .../analyst_test_design_guide/page-data.json | 1 + sites/oteguide/page-data/app-data.json | 2 +- .../1-2-PURPOSE/page-data.json | 1 + .../page-data.json | 1 + .../1-4-Consistency-is-Key/page-data.json | 1 + .../1-5-One-Voice/page-data.json | 1 + .../1-6-Templates/page-data.json | 1 + .../1-7-Microsoft-Word-Options/page-data.json | 1 + .../1-8-Focus-Areas/page-data.json | 1 + .../1-9-Styles/page-data.json | 1 + .../2-1-Acronyms/page-data.json | 1 + .../2-2-Commas/page-data.json | 1 + .../page-data.json | 1 + .../2-4-Headers-and-Footers/page-data.json | 1 + .../2-5-Page-Numbering/page-data.json | 1 + .../2-6-Blank-Pages/page-data.json | 1 + .../2-7-Capitalization/page-data.json | 1 + .../page-data.json | 1 + .../2-9-Vertical-Lists/page-data.json | 1 + .../page-data.json | 1 + .../3-2-Tables/page-data.json | 1 + .../3-3-Figures/page-data.json | 1 + .../3-4-Passive-Voice/page-data.json | 1 + .../page-data.json | 1 + .../3-6-Wordiness/page-data.json | 1 + .../page-data.json | 1 + .../3-8-Apostrophes/page-data.json | 1 + .../3-9-Choppy-Sentences/page-data.json | 1 + .../4-1-Numbers/page-data.json | 1 + .../4-2-Dates/page-data.json | 1 + .../4-3-Abbreviations/page-data.json | 1 + .../4-4-Terms/page-data.json | 1 + .../page-data.json | 1 + .../4-6-Verb-Tenses/page-data.json | 1 + .../4-7-Embedded-Files/page-data.json | 1 + .../4-8-Converting-Pictures/page-data.json | 1 + .../page-data.json | 1 + .../5-1-Patches/page-data.json | 1 + .../page-data.json | 1 + .../5-3-Distribution-List/page-data.json | 1 + .../page-data.json | 1 + .../5-5-Spell-Check/page-data.json | 1 + .../5-6-Configuration-Control/page-data.json | 1 + .../5-7-Table-of-Contents/page-data.json | 1 + .../page-data.json | 1 + .../editing_reports_guide/page-data.json | 1 + .../2-INTRODUCTION/page-data.json | 1 + .../3-TEST-ACTIVITY-SEQUENCE/page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 - .../accreditation_guide/page-data.json | 1 - .../analyst_test_design_guide/page-data.json | 1 - .../editing_reports_guide/page-data.json | 1 - .../page-data.json | 1 - .../lessons_learned_guide/page-data.json | 1 - .../fn_guides/measures_guide/page-data.json | 1 - .../page-data/fn_guides/page-data.json | 2 +- .../safety_risk_mgmt_guide/page-data.json | 1 - .../page-data.json | 1 - .../test_capability_guide/page-data.json | 1 - .../page-data/glossary/page-data.json | 2 +- sites/oteguide/page-data/index/page-data.json | 2 +- .../page-data.json | 1 + .../page-data.json | 1 + .../1-4-Policy-Guidance/page-data.json | 1 + .../1-5-PROCESS/page-data.json | 1 + .../lessons_learned_guide/page-data.json | 1 + .../2-INTRODUCTION/page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data.json | 1 + .../page-data/measures_guide/page-data.json | 1 + .../safety_risk_mgmt_guide/page-data.json | 1 + sites/oteguide/page-data/sq/d/1685914912.json | 2 +- sites/oteguide/page-data/sq/d/1928916242.json | 2 +- sites/oteguide/page-data/sq/d/2619113677.json | 2 +- .../page-data.json | 1 + .../test_capability_guide/page-data.json | 1 + .../safety_risk_mgmt_guide/index.html | 4 +- sites/oteguide/sitemap.xml | 199 +- .../6b9fd/image11.png | Bin 16652 -> 0 bytes .../a2ead/image11.png | Bin 7359 -> 0 bytes .../efc66/image11.png | Bin 18808 -> 0 bytes .../69476/image5.png | Bin 26301 -> 0 bytes .../6b9fd/image5.png | Bin 24154 -> 0 bytes .../a2ead/image5.png | Bin 8275 -> 0 bytes .../6b9fd/image12.png | Bin 9280 -> 0 bytes .../a2ead/image12.png | Bin 4630 -> 0 bytes .../c56af/image12.png | Bin 15564 -> 0 bytes .../e3189/image12.png | Bin 20381 -> 0 bytes .../62da8/image13.png | Bin 23812 -> 0 bytes .../6b9fd/image13.png | Bin 13809 -> 0 bytes .../a2ead/image13.png | Bin 6055 -> 0 bytes .../e3189/image13.png | Bin 30950 -> 0 bytes .../66caf/image9.png | Bin 18293 -> 0 bytes .../6b9fd/image9.png | Bin 12561 -> 0 bytes .../a2ead/image9.png | Bin 5159 -> 0 bytes .../6b9fd/image4.png | Bin 8685 -> 0 bytes .../98314/image4.png | Bin 13252 -> 0 bytes .../a2ead/image4.png | Bin 4038 -> 0 bytes .../6b9fd/image8.png | Bin 18715 -> 0 bytes .../a2ead/image8.png | Bin 8539 -> 0 bytes .../c61d0/image8.png | Bin 26535 -> 0 bytes .../e3189/image8.png | Bin 43428 -> 0 bytes .../6b9fd/image6.png | Bin 6596 -> 0 bytes .../6da96/image6.png | Bin 9761 -> 0 bytes .../a2ead/image6.png | Bin 1627 -> 0 bytes .../2f6f6/image15.png | Bin 35331 -> 0 bytes .../6b9fd/image15.png | Bin 20734 -> 0 bytes .../a2ead/image15.png | Bin 8321 -> 0 bytes .../e3189/image15.png | Bin 49450 -> 0 bytes .../29c1d/image14.png | Bin 54293 -> 0 bytes .../6b9fd/image14.png | Bin 31632 -> 0 bytes .../a2ead/image14.png | Bin 10942 -> 0 bytes .../e3189/image14.png | Bin 79673 -> 0 bytes .../669eb/image10.png | Bin 19310 -> 0 bytes .../6b9fd/image10.png | Bin 11231 -> 0 bytes .../a2ead/image10.png | Bin 5128 -> 0 bytes .../e3189/image10.png | Bin 26462 -> 0 bytes .../6b9fd/image6.png | Bin 16115 -> 0 bytes .../78a22/image6.png | Bin 10613 -> 0 bytes .../a2ead/image6.png | Bin 7051 -> 0 bytes .../5ecaa/image7.png | Bin 608 -> 0 bytes .../5c98f/image16.png | Bin 17571 -> 0 bytes .../6b9fd/image16.png | Bin 9959 -> 0 bytes .../a2ead/image16.png | Bin 4795 -> 0 bytes .../e3189/image16.png | Bin 23021 -> 0 bytes .../index.html | 4 +- .../oteguide/test_capability_guide/index.html | 35 + sites/oteguide/webpack.stats.json | 2 +- 396 files changed, 5995 insertions(+), 5504 deletions(-) create mode 100644 sites/oteguide/OTE_construct_development_guide/1-2-INTRODUCTION/index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct/index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy/index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles/index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach./index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/1-7-Construct-Development-Meetings/index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/1-8-Battlespace-Development/index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart/index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/2-1-Test-Design/index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/2-2-Measures-Development/index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/2-3-Test-Execution-Planning/index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct/index.html create mode 100644 sites/oteguide/OTE_construct_development_guide/index.html create mode 100644 sites/oteguide/accreditation_guide/1-2-INTRODUCTION/index.html create mode 100644 sites/oteguide/accreditation_guide/1-3-Test-Capability-Accreditation/index.html create mode 100644 sites/oteguide/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation/index.html create mode 100644 sites/oteguide/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions/index.html create mode 100644 sites/oteguide/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation/index.html create mode 100644 sites/oteguide/accreditation_guide/1-7-Accreditation-Concepts/index.html create mode 100644 sites/oteguide/accreditation_guide/1-8-Risk-Matrix:-Example/index.html create mode 100644 sites/oteguide/accreditation_guide/1-9-Previous-Accreditation/index.html create mode 100644 sites/oteguide/accreditation_guide/2-1-Accreditation-Process/index.html create mode 100644 sites/oteguide/accreditation_guide/2-2-Test-Capability-Accreditation-Concept/index.html create mode 100644 sites/oteguide/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format/index.html create mode 100644 sites/oteguide/accreditation_guide/2-4-Accreditation-References-and-Resources/index.html create mode 100644 sites/oteguide/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation/index.html create mode 100644 sites/oteguide/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office/index.html create mode 100644 sites/oteguide/accreditation_guide/2-7-Best-Practices/index.html create mode 100644 sites/oteguide/accreditation_guide/2-8-Summary/index.html create mode 100644 sites/oteguide/accreditation_guide/2-9-References-and-Resources/index.html create mode 100644 sites/oteguide/accreditation_guide/3-1-Governance/index.html create mode 100644 sites/oteguide/accreditation_guide/3-2-Points-of-Contact/index.html create mode 100644 sites/oteguide/accreditation_guide/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/1-2-OVERVIEW/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/1-6-Characterize/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/1-7-Compare/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/1-8-Problem-Identification/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/2-1-Factorials/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/2-3-Augmented-Designs/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/2-8-Demonstrations/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/2-9-Cases/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/3-1-Observational-Studies/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/3-3-Power/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/3-4-Optimality-Efficiency/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/3-5-Correlation-Multicollinearity/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/3-6-Prediction-Variance/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/3-9-Randomization/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/4-1-Replication/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/4-2-Blocking/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/4-5-Appendices/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/4-6-Test-Design-Guidance/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/4-7-Technical-References-and-Citations/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/4-8-Footnotes/index.html create mode 100644 sites/oteguide/analyst_test_design_guide/index.html rename sites/oteguide/{app-eec04d2f552ddc7b4bf2.js => app-03e333c274b6bc210459.js} (83%) rename sites/oteguide/{app-eec04d2f552ddc7b4bf2.js.LICENSE.txt => app-03e333c274b6bc210459.js.LICENSE.txt} (100%) create mode 100644 sites/oteguide/app-03e333c274b6bc210459.js.map delete mode 100644 sites/oteguide/app-eec04d2f552ddc7b4bf2.js.map create mode 100644 sites/oteguide/editing_reports_guide/1-2-PURPOSE/index.html create mode 100644 sites/oteguide/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices/index.html create mode 100644 sites/oteguide/editing_reports_guide/1-4-Consistency-is-Key/index.html create mode 100644 sites/oteguide/editing_reports_guide/1-5-One-Voice/index.html create mode 100644 sites/oteguide/editing_reports_guide/1-6-Templates/index.html create mode 100644 sites/oteguide/editing_reports_guide/1-7-Microsoft-Word-Options/index.html create mode 100644 sites/oteguide/editing_reports_guide/1-8-Focus-Areas/index.html create mode 100644 sites/oteguide/editing_reports_guide/1-9-Styles/index.html create mode 100644 sites/oteguide/editing_reports_guide/2-1-Acronyms/index.html create mode 100644 sites/oteguide/editing_reports_guide/2-2-Commas/index.html create mode 100644 sites/oteguide/editing_reports_guide/2-3-Next-Page-and-Page-Breaks/index.html create mode 100644 sites/oteguide/editing_reports_guide/2-4-Headers-and-Footers/index.html create mode 100644 sites/oteguide/editing_reports_guide/2-5-Page-Numbering/index.html create mode 100644 sites/oteguide/editing_reports_guide/2-6-Blank-Pages/index.html create mode 100644 sites/oteguide/editing_reports_guide/2-7-Capitalization/index.html create mode 100644 sites/oteguide/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases/index.html create mode 100644 sites/oteguide/editing_reports_guide/2-9-Vertical-Lists/index.html create mode 100644 sites/oteguide/editing_reports_guide/3-1-Numbering-Tables-and-Figures/index.html create mode 100644 sites/oteguide/editing_reports_guide/3-2-Tables/index.html create mode 100644 sites/oteguide/editing_reports_guide/3-3-Figures/index.html create mode 100644 sites/oteguide/editing_reports_guide/3-4-Passive-Voice/index.html create mode 100644 sites/oteguide/editing_reports_guide/3-5-Copyrights-and-Trademarks/index.html create mode 100644 sites/oteguide/editing_reports_guide/3-6-Wordiness/index.html create mode 100644 sites/oteguide/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes/index.html create mode 100644 sites/oteguide/editing_reports_guide/3-8-Apostrophes/index.html create mode 100644 sites/oteguide/editing_reports_guide/3-9-Choppy-Sentences/index.html create mode 100644 sites/oteguide/editing_reports_guide/4-1-Numbers/index.html create mode 100644 sites/oteguide/editing_reports_guide/4-2-Dates/index.html create mode 100644 sites/oteguide/editing_reports_guide/4-3-Abbreviations/index.html create mode 100644 sites/oteguide/editing_reports_guide/4-4-Terms/index.html create mode 100644 sites/oteguide/editing_reports_guide/4-5-Symbols-and-Units-of-Measure/index.html create mode 100644 sites/oteguide/editing_reports_guide/4-6-Verb-Tenses/index.html create mode 100644 sites/oteguide/editing_reports_guide/4-7-Embedded-Files/index.html create mode 100644 sites/oteguide/editing_reports_guide/4-8-Converting-Pictures/index.html create mode 100644 sites/oteguide/editing_reports_guide/4-9-References-and-Documentation/index.html create mode 100644 sites/oteguide/editing_reports_guide/5-1-Patches/index.html rename sites/oteguide/{fn_guides/test_capability_guide => editing_reports_guide/5-2-Classification-Markings}/index.html (84%) create mode 100644 sites/oteguide/editing_reports_guide/5-3-Distribution-List/index.html create mode 100644 sites/oteguide/editing_reports_guide/5-4-SF298-Report-Documentation-Page/index.html create mode 100644 sites/oteguide/editing_reports_guide/5-5-Spell-Check/index.html create mode 100644 sites/oteguide/editing_reports_guide/5-6-Configuration-Control/index.html create mode 100644 sites/oteguide/editing_reports_guide/5-7-Table-of-Contents/index.html create mode 100644 sites/oteguide/editing_reports_guide/5-8-Standardization-Checklist/index.html create mode 100644 sites/oteguide/editing_reports_guide/index.html create mode 100644 sites/oteguide/evaluation_and_reporting_guide/2-INTRODUCTION/index.html create mode 100644 sites/oteguide/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE/index.html create mode 100644 sites/oteguide/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING/index.html create mode 100644 sites/oteguide/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION/index.html create mode 100644 sites/oteguide/evaluation_and_reporting_guide/index.html delete mode 100644 sites/oteguide/fn_guides/OTE_construct_development_guide/index.html delete mode 100644 sites/oteguide/fn_guides/analyst_test_design_guide/index.html delete mode 100644 sites/oteguide/fn_guides/editing_reports_guide/index.html delete mode 100644 sites/oteguide/fn_guides/evaluation_and_reporting_guide/index.html rename sites/oteguide/{fn_guides/lessons_learned_guide => lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT}/index.html (79%) create mode 100644 sites/oteguide/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned/index.html create mode 100644 sites/oteguide/lessons_learned_guide/1-4-Policy-Guidance/index.html create mode 100644 sites/oteguide/lessons_learned_guide/1-5-PROCESS/index.html create mode 100644 sites/oteguide/lessons_learned_guide/index.html create mode 100644 sites/oteguide/measures_guide/2-INTRODUCTION/index.html create mode 100644 sites/oteguide/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT/index.html create mode 100644 sites/oteguide/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT/index.html create mode 100644 sites/oteguide/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION/index.html rename sites/oteguide/{fn_guides/measures_guide => measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES}/index.html (58%) create mode 100644 sites/oteguide/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE/index.html rename sites/oteguide/{fn_guides/accreditation_guide => measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES}/index.html (57%) create mode 100644 sites/oteguide/measures_guide/index.html create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/1-2-INTRODUCTION/page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct/page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy/page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles/page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach./page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/1-7-Construct-Development-Meetings/page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/1-8-Battlespace-Development/page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart/page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/2-1-Test-Design/page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/2-2-Measures-Development/page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/2-3-Test-Execution-Planning/page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct/page-data.json create mode 100644 sites/oteguide/page-data/OTE_construct_development_guide/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/1-2-INTRODUCTION/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/1-3-Test-Capability-Accreditation/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/1-7-Accreditation-Concepts/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/1-8-Risk-Matrix:-Example/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/1-9-Previous-Accreditation/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/2-1-Accreditation-Process/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/2-2-Test-Capability-Accreditation-Concept/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/2-4-Accreditation-References-and-Resources/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/2-7-Best-Practices/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/2-8-Summary/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/2-9-References-and-Resources/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/3-1-Governance/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/3-2-Points-of-Contact/page-data.json create mode 100644 sites/oteguide/page-data/accreditation_guide/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/1-2-OVERVIEW/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/1-6-Characterize/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/1-7-Compare/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/1-8-Problem-Identification/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/2-1-Factorials/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/2-3-Augmented-Designs/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/2-8-Demonstrations/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/2-9-Cases/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/3-1-Observational-Studies/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/3-3-Power/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/3-4-Optimality-Efficiency/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/3-5-Correlation-Multicollinearity/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/3-6-Prediction-Variance/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/3-9-Randomization/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/4-1-Replication/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/4-2-Blocking/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/4-5-Appendices/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/4-6-Test-Design-Guidance/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/4-7-Technical-References-and-Citations/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/4-8-Footnotes/page-data.json create mode 100644 sites/oteguide/page-data/analyst_test_design_guide/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/1-2-PURPOSE/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/1-4-Consistency-is-Key/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/1-5-One-Voice/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/1-6-Templates/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/1-7-Microsoft-Word-Options/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/1-8-Focus-Areas/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/1-9-Styles/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/2-1-Acronyms/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/2-2-Commas/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/2-3-Next-Page-and-Page-Breaks/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/2-4-Headers-and-Footers/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/2-5-Page-Numbering/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/2-6-Blank-Pages/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/2-7-Capitalization/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/2-9-Vertical-Lists/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/3-1-Numbering-Tables-and-Figures/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/3-2-Tables/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/3-3-Figures/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/3-4-Passive-Voice/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/3-5-Copyrights-and-Trademarks/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/3-6-Wordiness/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/3-8-Apostrophes/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/3-9-Choppy-Sentences/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/4-1-Numbers/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/4-2-Dates/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/4-3-Abbreviations/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/4-4-Terms/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/4-5-Symbols-and-Units-of-Measure/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/4-6-Verb-Tenses/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/4-7-Embedded-Files/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/4-8-Converting-Pictures/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/4-9-References-and-Documentation/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/5-1-Patches/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/5-2-Classification-Markings/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/5-3-Distribution-List/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/5-4-SF298-Report-Documentation-Page/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/5-5-Spell-Check/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/5-6-Configuration-Control/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/5-7-Table-of-Contents/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/5-8-Standardization-Checklist/page-data.json create mode 100644 sites/oteguide/page-data/editing_reports_guide/page-data.json create mode 100644 sites/oteguide/page-data/evaluation_and_reporting_guide/2-INTRODUCTION/page-data.json create mode 100644 sites/oteguide/page-data/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE/page-data.json create mode 100644 sites/oteguide/page-data/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING/page-data.json create mode 100644 sites/oteguide/page-data/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION/page-data.json create mode 100644 sites/oteguide/page-data/evaluation_and_reporting_guide/page-data.json delete mode 100644 sites/oteguide/page-data/fn_guides/OTE_construct_development_guide/page-data.json delete mode 100644 sites/oteguide/page-data/fn_guides/accreditation_guide/page-data.json delete mode 100644 sites/oteguide/page-data/fn_guides/analyst_test_design_guide/page-data.json delete mode 100644 sites/oteguide/page-data/fn_guides/editing_reports_guide/page-data.json delete mode 100644 sites/oteguide/page-data/fn_guides/evaluation_and_reporting_guide/page-data.json delete mode 100644 sites/oteguide/page-data/fn_guides/lessons_learned_guide/page-data.json delete mode 100644 sites/oteguide/page-data/fn_guides/measures_guide/page-data.json delete mode 100644 sites/oteguide/page-data/fn_guides/safety_risk_mgmt_guide/page-data.json delete mode 100644 sites/oteguide/page-data/fn_guides/strat_planning_programming_guide/page-data.json delete mode 100644 sites/oteguide/page-data/fn_guides/test_capability_guide/page-data.json create mode 100644 sites/oteguide/page-data/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT/page-data.json create mode 100644 sites/oteguide/page-data/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned/page-data.json create mode 100644 sites/oteguide/page-data/lessons_learned_guide/1-4-Policy-Guidance/page-data.json create mode 100644 sites/oteguide/page-data/lessons_learned_guide/1-5-PROCESS/page-data.json create mode 100644 sites/oteguide/page-data/lessons_learned_guide/page-data.json create mode 100644 sites/oteguide/page-data/measures_guide/2-INTRODUCTION/page-data.json create mode 100644 sites/oteguide/page-data/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT/page-data.json create mode 100644 sites/oteguide/page-data/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT/page-data.json create mode 100644 sites/oteguide/page-data/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION/page-data.json create mode 100644 sites/oteguide/page-data/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES/page-data.json create mode 100644 sites/oteguide/page-data/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE/page-data.json create mode 100644 sites/oteguide/page-data/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES/page-data.json create mode 100644 sites/oteguide/page-data/measures_guide/page-data.json create mode 100644 sites/oteguide/page-data/safety_risk_mgmt_guide/page-data.json create mode 100644 sites/oteguide/page-data/strat_planning_programming_guide/page-data.json create mode 100644 sites/oteguide/page-data/test_capability_guide/page-data.json rename sites/oteguide/{fn_guides => }/safety_risk_mgmt_guide/index.html (84%) delete mode 100644 sites/oteguide/static/146a07273349dbc36954330a63b5388e/6b9fd/image11.png delete mode 100644 sites/oteguide/static/146a07273349dbc36954330a63b5388e/a2ead/image11.png delete mode 100644 sites/oteguide/static/146a07273349dbc36954330a63b5388e/efc66/image11.png delete mode 100644 sites/oteguide/static/1882a4460923a55391e4af55449a1048/69476/image5.png delete mode 100644 sites/oteguide/static/1882a4460923a55391e4af55449a1048/6b9fd/image5.png delete mode 100644 sites/oteguide/static/1882a4460923a55391e4af55449a1048/a2ead/image5.png delete mode 100644 sites/oteguide/static/1eed82d67c46689b62a7e6728fc45a05/6b9fd/image12.png delete mode 100644 sites/oteguide/static/1eed82d67c46689b62a7e6728fc45a05/a2ead/image12.png delete mode 100644 sites/oteguide/static/1eed82d67c46689b62a7e6728fc45a05/c56af/image12.png delete mode 100644 sites/oteguide/static/1eed82d67c46689b62a7e6728fc45a05/e3189/image12.png delete mode 100644 sites/oteguide/static/494a1319872ca8029c3f59b6fb1b72d2/62da8/image13.png delete mode 100644 sites/oteguide/static/494a1319872ca8029c3f59b6fb1b72d2/6b9fd/image13.png delete mode 100644 sites/oteguide/static/494a1319872ca8029c3f59b6fb1b72d2/a2ead/image13.png delete mode 100644 sites/oteguide/static/494a1319872ca8029c3f59b6fb1b72d2/e3189/image13.png delete mode 100644 sites/oteguide/static/67a8e7809655d9884d926e93f455b88a/66caf/image9.png delete mode 100644 sites/oteguide/static/67a8e7809655d9884d926e93f455b88a/6b9fd/image9.png delete mode 100644 sites/oteguide/static/67a8e7809655d9884d926e93f455b88a/a2ead/image9.png delete mode 100644 sites/oteguide/static/688af7e1bde67ae8e5b5f8c57a84b5f2/6b9fd/image4.png delete mode 100644 sites/oteguide/static/688af7e1bde67ae8e5b5f8c57a84b5f2/98314/image4.png delete mode 100644 sites/oteguide/static/688af7e1bde67ae8e5b5f8c57a84b5f2/a2ead/image4.png delete mode 100644 sites/oteguide/static/6b9833f68a1524a0b0cf7cfa443edbc8/6b9fd/image8.png delete mode 100644 sites/oteguide/static/6b9833f68a1524a0b0cf7cfa443edbc8/a2ead/image8.png delete mode 100644 sites/oteguide/static/6b9833f68a1524a0b0cf7cfa443edbc8/c61d0/image8.png delete mode 100644 sites/oteguide/static/6b9833f68a1524a0b0cf7cfa443edbc8/e3189/image8.png delete mode 100644 sites/oteguide/static/854f02679aa6ba16edc99c0cc9bd8035/6b9fd/image6.png delete mode 100644 sites/oteguide/static/854f02679aa6ba16edc99c0cc9bd8035/6da96/image6.png delete mode 100644 sites/oteguide/static/854f02679aa6ba16edc99c0cc9bd8035/a2ead/image6.png delete mode 100644 sites/oteguide/static/85d2923d3fca34d2087f79a66d925e25/2f6f6/image15.png delete mode 100644 sites/oteguide/static/85d2923d3fca34d2087f79a66d925e25/6b9fd/image15.png delete mode 100644 sites/oteguide/static/85d2923d3fca34d2087f79a66d925e25/a2ead/image15.png delete mode 100644 sites/oteguide/static/85d2923d3fca34d2087f79a66d925e25/e3189/image15.png delete mode 100644 sites/oteguide/static/8888bba70268037c536a218fe81ca688/29c1d/image14.png delete mode 100644 sites/oteguide/static/8888bba70268037c536a218fe81ca688/6b9fd/image14.png delete mode 100644 sites/oteguide/static/8888bba70268037c536a218fe81ca688/a2ead/image14.png delete mode 100644 sites/oteguide/static/8888bba70268037c536a218fe81ca688/e3189/image14.png delete mode 100644 sites/oteguide/static/bae1e4e348a78fabaf5658337ed25708/669eb/image10.png delete mode 100644 sites/oteguide/static/bae1e4e348a78fabaf5658337ed25708/6b9fd/image10.png delete mode 100644 sites/oteguide/static/bae1e4e348a78fabaf5658337ed25708/a2ead/image10.png delete mode 100644 sites/oteguide/static/bae1e4e348a78fabaf5658337ed25708/e3189/image10.png delete mode 100644 sites/oteguide/static/c63b7dbae6812abcf7b6b5d97ebbb864/6b9fd/image6.png delete mode 100644 sites/oteguide/static/c63b7dbae6812abcf7b6b5d97ebbb864/78a22/image6.png delete mode 100644 sites/oteguide/static/c63b7dbae6812abcf7b6b5d97ebbb864/a2ead/image6.png delete mode 100644 sites/oteguide/static/e246abddf2a51a9e75b101fe3824e795/5ecaa/image7.png delete mode 100644 sites/oteguide/static/f58c73453be1fe2eb373edf77fa2e353/5c98f/image16.png delete mode 100644 sites/oteguide/static/f58c73453be1fe2eb373edf77fa2e353/6b9fd/image16.png delete mode 100644 sites/oteguide/static/f58c73453be1fe2eb373edf77fa2e353/a2ead/image16.png delete mode 100644 sites/oteguide/static/f58c73453be1fe2eb373edf77fa2e353/e3189/image16.png rename sites/oteguide/{fn_guides => }/strat_planning_programming_guide/index.html (83%) create mode 100644 sites/oteguide/test_capability_guide/index.html diff --git a/sites/oteguide/404.html b/sites/oteguide/404.html index b6331566..a5a6c0cb 100644 --- a/sites/oteguide/404.html +++ b/sites/oteguide/404.html @@ -1,4 +1,4 @@ -
\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct/index.html b/sites/oteguide/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct/index.html new file mode 100644 index 00000000..3c87b818 --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct/index.html @@ -0,0 +1,48 @@ +The Operational Test and Evaluation Construct

The Operational Test and Evaluation Construct

The OT&E Construct is the framework for conducting operational test. It +identifies the following elements of an operational test and their +relationship to one another:

  • Operational Effectiveness:  Measure of the *overall capability

    to accomplish a mission when used by representative personnel in +the environment planned or expected for operational employment of +the system considering organization, doctrine, supportability, +survivability, vulnerability and threat. (AFI 99‑103, +Capability‑Based Test and Evaluation*, 6 Apr 17)

  • Operational Suitability:  The *degree to which a system can be

    placed satisfactorily in field use with consideration given to +availability, compatibility, transportability, interoperability, +reliability, wartime usage rates, maintainability, safety, human +factors, manpower supportability, logistics supportability, +natural environmental effects and impacts, documentation and +training requirements. (AFI 99-103, Capabilities-Based Test and +Evaluation*, 6 Apr 17)

  • Mission Statement: Mission statements are written at a high,

    overarching level consistent with the mission the system is +intended to support or enable.

  • Critical Operational Issues (COI): A COI addresses a *critical

    mission element or operational objective* examined during OT&E to +determine the system’s overall capability to support mission +accomplishment (often referred to as operations-based COIs).

  • Operations: A COI is composed of one or more operations.

    Operations describe the actions, activities, or phases of a +mission needed to accomplish the COI. With two or more +operations, the overarching operational objective is the same; +however, the steps and/or conditions to achieve the COI are +different between operations.

  • Mission Effects: Mission effects are outcomes or results of

    conducting an operation.

  • Operational Capabilities: OCs provide operational context for

    system capabilities or attributes of high interest or importance +within an operation. It may be useful to distinguish between +system capabilities (i.e., the potential to perform some action) +and system attributes (i.e., the functions, properties, structure) +of a system. Operational capabilities provide the means to conduct +an operation and achieve effects.

  • Operational (User) Requirements: A *system capability,

    attribute, or characteristic required to accomplish approved +capability needs*. Operational requirements (including +suitability) are typically performance attributes, but they may +also be derived from cost and schedule (AFI 10-601). Typically +referred to as “requirements.”

  • Operational Conditions: Operational conditions are identified

    for each COI or operation and depict the operational battlespace. +An operational condition is defined by a set of factors, each set +at a given level. A factor is a variable of the environment that +may affect task performance. A level is a set value within the +range of values a factor can hold.

  • Measures: Measures are designed to convey information about a

    system’s effect, capabilities, functions, properties, or structure +being addressed.

  • Data/Data Element: Data is *any measurement or information used

    to determine the value of a measure*. Data may be quantitative, +qualitative, subjective, or objective.

  • Test Design: The test design is a set of test events for each

    operation and battlespace condition, including the rationale for +selecting the test events.

  • Test Event: A test event is a *single execution of an operation

    or sequence/set of operations* under specified conditions for the +operations.

This guide provides methods to develop these elements of the OT&E +Construct for the overarching goal of determining effectiveness and +suitability.

\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy/index.html b/sites/oteguide/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy/index.html new file mode 100644 index 00000000..f7b7a526 --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy/index.html @@ -0,0 +1,35 @@ +Operational Sufficiency and Technical Adequacy

Operational Sufficiency and Technical Adequacy

Operational sufficiency and technical adequacy are two basic AFOTEC +tenets leading to an adequate and credible test.

Operational Sufficiency addresses the breadth of the operations and +conditions addressed while employing new or modified capabilities within +the context of representative employment and support concepts. An +operational test and evaluation (OT&E) is considered operationally +sufficient if it provides the decision maker and the warfighter with +results from test events executed across sufficient operations and +conditions to identify the capabilities and limitations associated with +employment and support, and enables an effectiveness and suitability +determination.

Ensuring operational sufficiency requires a thorough understanding and +identification of the operational employment and support environment and +conditions, to include operational threats. AFOTEC core teams address +operational sufficiency while designing test events to ensure +capabilities and concepts are adequately addressed within the +operational evaluation. Core teams are one tool to address operational +sufficiency by using operational perspective, experience, and judgment +to ensure test events are evaluated within the context of envisioned +operations and support. This allows AFOTEC to characterize systems’ +capabilities and mission effects.

Technical Adequacy addresses the relevance of the technical information +produced by the test in relation to the purpose of the test (i.e., test +events address operationally relevant questions). This includes test +design, test measures, relevant threat environments, data collection +methods, scoring, analysis, modeling and simulation, and test capability +accreditation. A test is technically adequate if the test data +evaluation provides the acquisition decision maker information to inform +the relevant decision.

\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles/index.html b/sites/oteguide/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles/index.html new file mode 100644 index 00000000..490b6386 --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles/index.html @@ -0,0 +1,59 @@ +Operational Test and Evaluation Test Activity Cycles

Operational Test and Evaluation Test Activity Cycles

A general test activity is the sequence of determining what to test, how +to test, executing the test and collecting data, analyzing the results, +and reporting the conclusions (see figure 1). The success of this +activity depends largely on an initial understanding of the battlespace, +the capabilities under test, and how the capabilities fit within the +battlespace. All subsequent activities build on a test team’s basic +understanding of the expected capabilities under test, in what +operational conditions the capabilities will be employed and supported, +and what needs to be measured. This is called “Defining the What.” Using +more operational terminology, this effort is commonly referred to as +battlespace development and should be the first step for the OT&E +Construct test activity.

Figure 1. Steps in the OT&E Construct Test Activity

+ + + image3 + + Developing +a battlespace is the first of five major steps in the AFOTEC OT&E +Construct and is accomplished in conjunction with Test Design (discussed +in this guide with more detail in the Analyst Test Design Guide). This +step frames the OT&E by answering four fundamental questions. *What* are +the capabilities under test; *what* is the intended use of the +capabilities; in *what* operational conditions will the capabilities be +employed/supported (operations and conditions); and *what* do you need +to measure to determine combat capability?

Test teams have latitude in how they develop the battlespace. However, +this guide presents a long-standing and proven approach test teams +should consider before proceeding with test design. It is systematic and +can quickly take test teams from limited operational understanding to +credible OT&E Constructs. This AFOTEC default approach to battlespace +development will provide a sound foundation for the second step, Test +Design. Figure 2 generalizes this approach. Although depicted as a +sequence of steps, the process is iterative and adaptive.

Figure 2. Battlespace Development Within the OT&E Construct

+ + + image4 + +

Battlespace development provides the foundation for operationally +sufficient and technically adequate OT&E by ensuring operations-based +test designs. It supports the later application of scientific methods of +testing needed to design and analyze tests across the operational +battlespace to ensure credibility. A key element of the scientific +method of operational test is mission thread analysis, which includes +identifying the operational conditions and considering test constraints, +thereby leading to a set of high-return test events. These events will +lead to a defensible basis for resource estimations (test articles, +personnel, etc.) early in an acquisition and OT&E lifecycle. It also +aids the development of test execution methodologies (field test, +modeling and simulation, hybrid), identifying test capability +requirements and shortfalls, and refining OT activities and schedule +(Integrated Test & Evaluation).

\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach./index.html b/sites/oteguide/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach./index.html new file mode 100644 index 00000000..5ccbefb7 --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach./index.html @@ -0,0 +1,40 @@ +Using a Core Team Approach.

Using a Core Team Approach.

The core team is an AFOTEC-led working group established to support +program test activities. Examples include battlespace development, test +design, measures workshops, and technical reviews. The core team is +composed of all AFOTEC stakeholders (Test Team, Detachment and +Headquarters staff). The core team is led by the responsible test +director (TD). It includes any AFOTEC Detachment subject matter +expertise (SME) the TD believes is needed (e.g., logistics and cyber +SMEs). AFOTEC/A3 typically facilitates the process. An AFOTEC +directorate’s core team member’s general responsibilities include +ensuring their directorate’s intent and expertise is considered as early +as possible. It also aids the staff awareness and support during later +activities and staffing actions. External stakeholders are also invited +to support OT&E Construct development. Key external representatives come +from operational users, program offices, development test, and other +OTAs (for Multi-service OT). DOT&E action officers (or support +contractors, typically the Institute for Defense Analyses (IDA)) should +also be invited if the program is on the DOT&E oversight list. External +involvement during the OT&E Construct development is significant in +terms of early buy-in on AFOTEC’s foundational planning effort, and it +builds relationships at the earliest possible opportunity. The OT&E +Construct can be developed without externals, and with some rapid test +activities it may be required to keep a program moving quickly. However, +OT&E Constructs are typically better if external stakeholder +interests/inputs are considered. Figure 3 reflects a typical CT +composition and potential external stakeholders.

Figure 3. Core Team Composition

+ + + C:\Users\James.Thomas\Desktop\ITD Brief\CT Picture.png + +

The typical roles and responsibilities for core team members and +external stakeholders are addressed in table 1.

Table 1. Core team and External participant Roles and Responsibilities

Core TeamExternal Participants.

Detachment TD:

- Serves as the overall lead for all core/test team activities from program involvement through OT closeout

- Produces well-written documents and well-prepared briefings

- Serves as primary briefer for the program

Note: Det/CC has operational control of the testing process from TO through OT closeout

Battlespace development facilitator:

- Facilitates the battlespace development and assists TD with developing the test design

- Documents the OT&E Construct

- Co-facilitates test events, methodologies, and scenarios

A-2/9 Staff:

- Co-facilitates test events, methodologies, and scenarios

- Assesses program’s intelligence sensitivity

- Provides assistance with development of realistic threat scenarios

- Provides specialized support to team in the effectiveness analysis, suitability analysis, modeling and simulation expertise, test design expertise, weather, intelligence, and human factors

A-5/8 Staff: Provides policy guidance, test capability, and range identification

SE Staff: Provides environmental, safety, and health guidance

- Warfighters bring operational currency, background information and clarity when addressing operational requirements and concepts of operations

- Program office participants bring program information (schedules, technical risk areas, funding, etc.) Gain insight into OT expectations; know potential impact to contract awards with OT flavor

- Lead Developmental test organization (LDTO)/CTA participants bring developmental test (DT) information, gain insight into OT expectations, identify operationally representative OT events that DT can fulfill, know potential impact on capability requirements clarification start provide insight into integrated test challenges

- Other agencies provide insight into test capabilities, expectations, plans, limitations

-- Director, Operational Test and Evaluation (DOT&E) fulfills an oversight function

-- Other OTAs address their Service equities for MOT&Es

--- Army Test and Evaluation Center (ATEC)

--- Operational Test and Evaluation Force (OPTEVFOR)

--- Marine Corps Operational Test and Evaluation Agency (MCOTEA)

\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/1-7-Construct-Development-Meetings/index.html b/sites/oteguide/OTE_construct_development_guide/1-7-Construct-Development-Meetings/index.html new file mode 100644 index 00000000..0e81b74d --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/1-7-Construct-Development-Meetings/index.html @@ -0,0 +1,20 @@ +Construct Development Meetings

Construct Development Meetings

Battlespace development typically occurs in a formal meeting(s) +environment. It is closely tied to the test design and is often +accomplished during the same meeting(s). In most cases, an A3 test +design manager (TDM) will accomplish pre-work with the TD prior to the +formal battlespace development meeting. The pre-work, coupled with A3 +facilitation, allows the meeting to be executed quickly and efficiently. +Successful battlespace development typically takes a couple of days +allowing a transition into the test design activity during the same +formal meeting. Optimally, one battlespace development/test design +meeting is required with follow-on activities for measures development +(measures workshop) and execution planning activities.

\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/1-8-Battlespace-Development/index.html b/sites/oteguide/OTE_construct_development_guide/1-8-Battlespace-Development/index.html new file mode 100644 index 00000000..520a9d9b --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/1-8-Battlespace-Development/index.html @@ -0,0 +1,365 @@ +Battlespace Development

Battlespace Development

The Battlespace development steps are captured in the subsequent +paragraphs.

Researching the Capability or System Being Acquired

Core team members and external stakeholders should strive for maximum +understanding of the capability being acquired, the mission(s) it +supports, and how it will be employed and supported before the formal +meeting. To prepare for the battlespace development/test design meeting, +research capability-based requirements (e.g., draft ICD, CDD) and any +available system information from various sources (e.g., SRD, TRD). +Other documents critical to operational understanding are CONOPS, TTPs +and threat documentation. This research results in knowledge of where +and how the system fits into the envisioned battlespace and the intended +operational capabilities. Gaining this knowledge can be inherently +difficult early in a program’s acquisition cycle with only a draft ICD +and a limited, or no written CONOPS. The operational significance of the +required capabilities and their impact on the battlespace need to be +understood sufficiently in order to properly scope the overall +operational evaluation.

The CT should strive to understand:

  • The mission the system is designed to support

  • Operational objectives required to accomplish the mission

  • The critical elements of the mission the system supports

  • Information/data cyber dependencies which enable the mission

  • Bounds of the “system” acquisition and the T&E processes (i.e., “to

    what extent are other systems impacted, beyond the system being +acquired, within the T&E processes?”)

  • Threat environment (kinetic and non-kinetic) in which the system is

    expected to operate

  • Limitations and issues that are resolved to support the acquisition

    and T&E processes (technical as well as operational)

  • Program documentation:

  • System CONOPS

  • Capability requirements documents

  • Program acquisition strategy (DoDI 5000.02 model being employed -

    hardware- or software-centric; additional documents may be used, +as required)

  • AFOTEC battlespace development process

  • AFOTEC test design process

+ + + image6 + + To +facilitate common understanding a series of briefings are typically +provided at the start of a battlespace development /test design meeting. +The briefings cover the Acquisition, CONOPS, capability requirements and +threats. Generally, the program office, warfighting user, and +intelligence representatives provide the briefings. Once the team +understands the battlespace and how the SUT will support the operation +in that battlespace, the team can examine how the required capabilities +map to the operational activities. The AFOTEC approach to ensure the +core team understands the capability and system being acquired is to +build battlespace depiction in the form of an Evaluation View (EV).

Battlespace Depiction

+ + + image7 + +

When +developing the battlespace depiction, the core team should consider the +type of capability being acquired, what actions the capability enables, +what objective(s) the capability supports, and the objective’s +dependencies on other systems. For example, if accomplishment of an +operational objective depends on numerous other systems and operational +factors, it may be difficult to provide a credible answer about the +system’s contribution to the objective; in this case the scope or level +of test could be too high (e.g., operational level of conflict, table 4) +versus a more credible tactical level of conflict. These considerations +will help guide the level of detail for the nodes in the evaluation view +and define the scope of the test.

The Evaluation View

The evaluation view (EV) (Figure 5) is one method used to aid +operational understanding; it is a facilitation tool to get the core +team and external participants to a point of common battlespace +understanding before jumping into operational test design. The EV +illustrates three important OT fundamentals: where in the operation the +system will likely influence operational outcome; where and when +OT-relevant data will likely be generated; and where the operational +environment could affect the system’s capability.

The EV is not intended to be a literal depiction. The core team should +understand that the battlespace depiction is not perfect, but that it +meets the needs of process facilitation. The core team will need to have +a degree of understanding and latitude as they progress through the +process because they will have to reach a consensus on the level of +detail they deem sufficient to proceed to the next step.

There are other methods to gain operational understanding, but using the +EV has proven successful over several hundred test efforts and is +typically the tool of choice to facilitate the majority of battlespace +development efforts. It has advantages over various other tools such as +the DoD Architecture Framework (DODAF) views. Although DODAF views are +useful for different levels of planning, they are oftentimes not +available for the early AFOTEC planning efforts. The DODAF system views +(SV) and technical views (TV) are very specific in purpose and do not +provide an overall picture of the battlespace. A DODAF operational view +1 (OV-1) is often useful; however, it normally only addresses the +pointy-edge of the operation and does not typically address logistics to +an acceptable level of detail. When an EV is complete, and done +properly, it should reflect a tailored battlespace depiction that shows:

  • Major battlespace phases

  • Elements of the operation (primary nodes)

  • Mission statement

  • Critical operational issues (COI) and subordinate operations

  • Capability requirements mapping

  • Information sources/references

  • Inherently addresses both effectiveness and suitability elements

  • Provides equal consideration to logistics-centric operations

The Evaluation View 1

+ + + image8 + +

Building +an EV can look challenging on the surface, but it is initially framed by +an A-3 Test Design Manager (TDM) skilled in their development. The TDM +works hand-in-hand with the TD in all pre-work activities and the +initial framing occurs prior to any formal meetings. The EV-1 forms a +system-of-systems depiction of the Joint and/or Air Force doctrinal +mission area that the new/modified capability is intended to support. It +is developed using the broad knowledge gained from early involvement, +studying Joint and Air Force doctrine and researching all available +program documentation (e.g., AoA, system CONOPS, ICD, CDD/IS CDD, T&E +strategy, Air Force & Joint CONOPS & Doctrine, associated DODAF +architectures). The EV consists of typical operational nodes linked +together using a “necessary conditions” methodology. Primary nodes are +significant elements of the operation. Major phases are logical +groupings of primary nodes and are used to add clarity and understanding +to differing phases of the operation. Major phases of the operation +usually become apparent after the primary nodes are linked and are +further differentiated using different colors to associate the primary +nodes with their respective major phase.

The Evaluation View 2

EV-2s are a near-seamless evolution of EV-1s and differ in three primary +areas. The EV-2 has capability requirements, critical operational issues +(COI) and subordinate operations mapped into the battlespace.

Capability Requirements Mapping

The EV 2 (Figure 6) builds on the operational environment depicted on +EV-1. The EV-2 is developed by mapping operational capability +requirements into the depiction where the operational performance data +would likely be generated during a typical operations. Operational +capability requirements are found in a variety of documents (e.g., draft +ICD, CDD and CONOPS). Operational capability requirements usually +contain key characteristics (attributes) with appropriate parameters and +metrics. However, they may be described with only the characteristic +(e.g., “the system must possess high reliability”). Other times there +may not be any documented capability requirements and in these cases +there will be greater reliance on current operational expertise to +define the material solution (system under test). This is the most +extreme case for defining the battlespace and system under test and +would require documenting capability documentation shortfalls. While +mapping requirements, keep in mind that teams often identify +requirements shortfalls that should be mapped as derived capabilities.

Derived capabilities are usually the result of some inferences in the +ICD or CDD, or could result from an interpretation of the CONOPS and +capabilities relationship and understanding that certain performance +characteristics must exist for a system to meet its overall mission +need. Derived capabilities do not have associated criteria or +references, but generally influence the overall effectiveness and/or +suitability determinations (The TD must validate capabilities derived +during the core team process with the user).

To help teams readily identify cybersecurity interest areas. The nodes +with cyber dependencies will be identified by a blue border and will +have applicable requirements and verbiage detailing the cyber dependency +mapped into it. The purpose of this step is to generate discussion and +identify area for further investigation into possible test implications +concerning Cybersecurity.

During DT/OT, the test team should monitor/assist with cybersecurity +test events, pursuing test events using standard scenarios based on real +procedures, real operators, and production-representative equipment. If +viable, the team should plan accordingly and reflect the plan in the +TEMP and other test-planning documentation. The team must incorporate +the CDD/CPD and system CONOPS as testing evolves.

Mission Statement

Mission statements are written at a high, overarching level consistent +with the mission the system is intended to support. For example, “Combat +Search and Rescue Locator (CSARL) supports the combat search and rescue +mission.” The team should ask, “What mission is the system intended to +execute or support?” or “Why are the capabilities being acquired?” +Mission statements should be consistent with wording from published +documents like the ICD/IS ICD, CDD/IS CDD, CONOPS, doctrine, etc. The +mission statement should also trace to the capability gaps identified in +the ICD. The Detachment TD and A-3 TDM develop a recommended mission +statement in the pre-work and present it to the team during the meeting.

Critical Operational Issues

A critical operational issues (COI) is an operational question. AFOTEC +defines a COI as a critical mission element or operational objective +that is examined during OT&E to determine the system’s overall +capability to support mission accomplishment as determined by +effectiveness and suitability. Put simply, COIs are operations, and +should clearly speak to the warfighter. When answered, the operational +impact is clear. For COIs, the team should ask, “What are the critical +elements of the mission?” or “What warfighter goals, major operations, +or activities are intended to be accomplished?”

A COI may be composed of more than one type of operation and may +describe the operation in a set of activities or phases of a mission +needed to accomplish the COI. An example is the KC-46 COI, “Can KC-46 +provide refueling?” There are at least two distinct activities or +operations within this COI: air-to-air refueling and forward area +refueling point (FARP), which is forward ground refueling. Although the +overarching goal is the same (to provide refueling), the activities and +the conditions to do this are different. Identifying operations allows +for designing test around the unique operations and associated +operational conditions. The major phases identified on the EV should +provide a logical COI structure. The COIs and any breakout of +subordinate operations are documented on the EV near logically group +operational nodes.

COIs are operations, not functions, system characteristics, or enable +characteristics. Figure 7 illustrates some basic COI tenants.

Figure 7. COI Tenets

+ + + image9 + +

As with all things, there are exceptions. Given the emphasis on +cybersecurity, teams have the option to address cybersecurity as a +separate COI. This is typically done because teams believe there are +test reporting advantages. For some systems, a cyber COI may be helpful +for reporting cyber effects to warfighters and acquisition community +separate from system performance in an uncontested cyber environment. +Reporting this way highlights cyber during OT&E by more narrowly +focusing on what needs to be corrected, why, and the impact if not +corrected from a cyber perspective. In these cases, a separate COI to +capture cybersecurity concerns, may be warranted. Considerations that +could justify a separate cyber COI are characteristics of the SUT (e.g., +common architecture across all COIs, a software/network focus, and +potential catastrophic node), characteristics of the operating +environment (e.g., significant documented cyber threats or reliance on +out of boundary systems or connections), or when cyber effects are not +fully captured in traditional ops-based COIs. Test teams can choose from +three OT&E constructs (integrated, stand-alone, and hybrid) to capture +and report cyber impacts in a manner that ensures stakeholders +understands performance and mission impacts in a cyber-contested +environment. Cyber considerations do not mandate a cyber-centric COI; +however, core teams have flexibility should they desire a different +cyber reporting approach.

The integrated approach (commonly referred to as traditional or +Ops-based) would only have a cyber-centric COI if there was a defined +cyber operation introduced by the SUT. Cyber elements (operational +conditions, threats, test measures, etc.) are addressed within the +context of the missions or operations-based COIs (wherever cyber can +affect operational outcome). Using the integrated approach, any notable +issues identified that extend beyond the SUT (e.g., do not affect the +degree of mission accomplishment of the SUT or the ability to place in +field use) may be addressed in a separate annex to the OT&E report, if +warranted.

The stand-alone approach addresses all of the operations-based COIs in +an uncontested cyber environment; the stand-alone, cyber-centric COI +addresses the operations in a cyber-contested environment. This approach +allows the baselining of uncontested performance, as compared to +contested performance of the SUT. The Stand-alone Cyber COI essentially +embeds and executes the operations documented in the traditional COIs in +a cyber COI that has a contested environment. All cyber contested +elements (e.g., operational conditions, threats, test measures, and test +events) are addressed within the cyber COI. Additional cyber-specific +measures address the system’s cyber operational capabilities.

The hybrid approach applies elements of both the integrated and +stand-alone approaches, addressing cyber both within the +operations-based COIs and a separate cyber-centric COI. Cyber elements +(e.g., operational conditions, threats, test measures, and test events) +are addressed within the context of the missions or operations-based +COIs, the cyber COI is functionally focused (e.g., cybersecurity +operational capabilities) and also addresses effects not seen within the +missions or operations-based COIs (i.e., indirect effects, 2nd/3rd order +effects). This may also be used to expand cyber reporting beyond the +SUT, if warranted.

Operations

Based on different activities or different operational conditions within +a COI, multiple subordinate operations may be identified under a COI. An +example COI for the KC-46 was, “Can KC-46 provide refueling?” There are +at least two distinct activities or operations within this COI: +air-to-air refueling and forward area refueling point (FARP). Although +the overarching goal is the same (to provide refueling), the activities +and the conditions to achieve this are different. Another example could +be sustainment operations that has a subordinate maintenance operation, +deployed operation, and training operation. Again the need for breaking +down various operations become obvious when identifying the various +conditions associated with the different operations.

Operational Employment and Support Conditions

Measures of Effectiveness

MOEs (very similar to the previous Mission-Oriented Response Variables +or MORV) are developed for each COI or for each operation. An MOE is a +measure of a system’s (or operation’s) degree of mission success and +will be commensurate with the level of test. It is a dependent variable +which gauges the achievement of a desired effect (aka measure of +effect). MOEs also guide the development of factors and levels by +assessing factors’ expected impact on the MOEs.

Ideally, an MOE should be continuous, but could also be binary—was the +effect achieved or not. While a categorical or binary MOE may be a +strong indicator of mission success, it might also drive considerably +more testing and resource requirements than a continuous MOE would +require to achieve the same statistical significance.

Examples of MOEs for a notional Combat Search and Rescue system’s +operation of Recover Personnel might be:

  • Binary: “Percentage of Rescue Attempts that are Successful”

  • Continuous: “Proportion of Survivors Rescued”

    Note the measure of effectiveness reflects the outcome or effect of +an operation.

Operational Conditions (Factors and Levels)

Operational conditions define the system’s operations and support +environment. After MOEs have been developed, operational conditions that +potentially have a significant influence on outcome of the operations +are identified. Operational conditions are identified for each COI or +operation within a COI and depict the operational battlespace identified +to support development of test events and scenarios. An operational +condition is defined by a set of factors, each set at a given level. A +factor is a variable of the environment that affects task performance. A +level is a set value within the range of values that a factor can hold. +It is important to understand the factors influencing task performance +in order to initially capture representative operational conditions in +the OT&E Construct. The terminology (conditions, factors, and levels) is +derived from CJCSM 3500.04D.

The set of factors and levels forms the relevant set of operational +conditions. These conditions are contained in the test design +worksheets. As an example, the Mode of Travel, Battery Type, Terrain, +Time of Day, and Threat are all factors (Table 3) potentially +influencing the outcome of the operation as defined by the MOE: +Percentage of Rescue Attempts that are Successful. No Vehicle, +Rechargeable, Flat, Night, and High are one level for each factor, +respectively. A single condition for the survivor/evader navigation COI +can be described by a specific combination of factors and levels. For +example, one possible combination or single condition can be described +as mode is no vehicle, battery is non-rechargeable, terrain is +mountainous, time of day is night and the threat is high. Another +operational condition can be described as the terrain is flat, time of +day is daytime, and the threat is low. Cyber threats have the potential +to impact most systems. The cyber factors in table 2 are generally +sufficient for test designs; however, other cyber focused factors may be +appropriate depending on the COIs and/or subordinate operations.

Table 2. COI 2, Survivor/Evader Navigation

Operational Conditions
FactorsLevels
Mode of TravelVehicleNo vehicle
Battery TypeRechargeableNon-rechargeable
TerrainFlatMountainousLittoral
Time of DayNightDayTransition
ThreatHighLow
Disruptive Cyber threatYesNo
Non Disruptive Cyber threatYesNo

Identify Factors and Levels.

Factors and levels are identified through a number of methods. If +studies (such as an AoA) have been conducted, they could provide insight +on potential factors. If requirements have been mapped on the EV, they +could provide specific factors of interest (e.g., for “the system shall +operate day and night” the factor would be time of day). The CT, +composed of the users, developers, operators, analysts, etc., brings a +great deal of knowledge and expertise to the task of brainstorming ideas +on factors.

To identify factors, the team reviews each COI and asks the question, +“What factors potentially influence the outcome of the COI or operation +captured by the MOEs?” Some of these factors may be an explicit part of +the environment in which the system will be employed (e.g., altitude, +weather, network load.) Other factors may not seem as directly related +to the employment environment, such as manning level, technical orders, +skill level. Yet, others may appear as inherent system factors that will +likely be “as-is” when the system is employed. Examples of this include +memory size, number of display screens, and seat positions, we identify +these as a “Given” level within the design. While this list is not +exhaustive set of factors, it is important to document all of the +factors identified for future reference. For OT purposes, attempt to +focus on the sets that will have a potential effect on the outcome of +the operation and are likely to vary the operational environment or the +user/operator.

After the core team documents the factors, appropriate levels will be +added to each factor. When identifying the levels, it is desirable to +capture the range of possible levels. The decision on exactly which +levels to test will be made later during test design. At this point, it +may be recognized that several of the factors, particularly the inherent +system factors, may be given for operational test. In the example, the +factors are software version and training. It is not necessary to +identify levels for those factors (although, the developer may wish to +do so). Table 3 expands on the navigation COI example discussed in table +3.

The last two factors highlight the point of documenting all identified +factors. In the illustrated example, these particular factors were +previously recognized as going to be “given” or “as-is” when the system +is delivered. Therefore, they are not prioritized since there is no +possibility for them to change. The software version factor is important +to document since it is part of the operation and is measured and +reported. The last two factors (software version/training) is at a set +value for the OT&E.

Table 3. COI 2, Survivor/Evader Navigation

Operational Conditions
FactorsLevels
Mode of TravelVehicleNo vehicle
Battery TypeRechargeableNon-rechargeable
TerrainFlatMountainousLittoral
Time of DayNightDayTransition
ThreatHighLow
Disruptive Cyber threatYesNo
Non-Disruptive Cyber threatYesNo
Software VersionGiven
TrainingGiven

Prioritizing Factors

The table of factors may include factors in the operational environment +which may not influence the SUT, but are used to describe an operational +environment. As a result, a prioritization process is used to rank +factors based on their impact against each COI’s operations by +considering their effect on the MOEs. This is a subjective determination +made by the Core Team and is intended to identify those operational +conditions that have the most impact to mission success and are +therefore more important from a test design perspective. This is a +two-step process for each factor and is accomplished during the +Battlespace Development meeting, using operator/SME input. The +prioritization process begins with determining the likelihood or +frequency of encountering each level of each factor in the operational +environments and continues by determining the estimated magnitude of +impact varying the levels of a factor has on the MOE.

The first step determines the likelihood of encountering the particular +levels for each factor. This is based on the potential to encounter a +particular factor/level in the operational environment (e.g., the +probability of recovery from mountains is high, but the probability of +recovery from Flat is low). This may be done with specific probabilities +or percentages or with qualitative statements (e.g., likely, frequently, +seldom). The combinations of the factors, levels, and the likelihood of +encountering each level describes the possible battlespace conditions +the system under test could operate within when conducting the +activities depicted by the COI or Operation.

The second step estimates the magnitude of impact and assigns a “high,” +“medium,” “low,” or “none” rating for each MOE for each factor. The +impact is assigned after considering the potential size of the change in +the MOE when the factor is varied between its levels, leading to a +significant change in the outcome of the operation with consideration of +the MOE. Table 4 shows the prioritized factors highlighted in grey.

Table 4. Factor Prioritization

COI 1: Can CSARL enable survivor/evader navigation to a rendezvous location?
Operation 1: Rescue Survivor

MOE 1: Timeliness of Rescue;

MOE 2 Accuracy of Pick-up Point

FactorLevelsPrioritizationFactor MgmtWhy factor is operationally important; Why level is selectedNotes
Likelihood of EncounteringMagnitude of Impact
MOE 1MOE 2
Mode of Travel

Vehicle

No Vehicle

Frequent

Seldom

HHAffects the survivor’s ability to move from the area.
Battery Type

Rechargeable

Non Rechargeable

Frequent

Seldom

HHAbility of the survivor/evader to have communications.
Terrain

Flat

Mountainous

Littoral

BalancedHHDifference in the terrain could affect the survivors’ ability to move or platform recovery.
Time of Day

Day

Night

Transition

BalancedMMNight time could affect the ability to see the survivor/evader.The CT should document notes for each F&L set.
Threat

High

Low

BalancedHHThis would affect the platforms ability to reach location.
Disruptive Cyber Threat

Yes

No

CommonHHWill have to look at mission planer vulnerabilities.
Non Disruptive Cyber Threat

Yes

No

CommonMMLook at possible mission effects.
Software VersionGivenGivens not prioritizedComplete instructions on how to plan and operate system, also affects maintenance.Latest version.
TrainingGivenGivens not prioritizedPlatform dependent, survival or equipment related capabilities.Both survivor and recovery team have training.

The last two factors highlight the point of documenting all identified +factors. In this example, these particular factors are seen as “given” +upon system delivery. Therefore, they are not prioritized because there +is no possibility they will change. The technical data factor is +important to document because it is part of the operation and will be +measured and reported. The last factor will be at a set value for the +OT&E. The team has determined this factor is unlikely to have an impact; +nonetheless, it is documented as part of the set of factors. The last +two factors and the factor “threat” are not removed from the list—they +are still needed to ensure the test environment is operationally +representative. Consideration should be given to them for resource +planning and test execution.

Operational Capabilities

An OC is a system attribute or grouping of attributes users or SMEs +identified as having value or that are crucial to the system to satisfy +the capability gap within the context of the operations defined by the +COIs. They provide operational context for attributes of high interest +or importance within the operation. OCs are identified by reviewing the +system’s requirements documents and by SMEs identifying system +capability attributes that can significantly influence achieving the +COIs.

Cybersecurity and cyber resiliency are high-interest attributes and +are assessed/evaluated as applicable across all operations.

The OCs are not part of the rating structure or evaluation at the end of +test, but serve instead to highlight possible trends/patterns of +operational impact along a particular capability. For instance, if in +the final evaluation, multiple measures fail across the OC +“Interoperability”, then this potential capability impact is highlighted +to leadership and decision makers. OCs are captured as a short phrase or +topic. Although the identification of OCs is a facilitated effort by the +A3 TDM, table 5 shows which areas to examine when developing OCs.

Table 5. Operational Capability Areas

OCArea to Examine
Operational PerformanceWhat are the measures of desired effects (e.g., timeliness)?
What operational performance attributes are listed (e.g., precision, responsiveness)?
What operational performance attributes are associated with the key performance parameters (KPP) and key system attributes (KSA) (e.g., accuracy)?
What attributes are high risk (e.g., lethality; cybersecurity, dependent on new technology)?
System SupportWhat support attributes are listed (e.g., reliability, maintainability, availability, compatibility)?
What are the support‑related attributes associated with the KPPs and KSAs (e.g., cybersecurity)?
What attributes are high risk (e.g., reliability; dependent on new manufacturing techniques)?

On the ESC, OCs allow some logical grouping of the operational +capabilities or capability requirements (e.g., from an ICD or CDD). The +relationship between operations (defined by the COIs), operational +capabilities and capability requirements are clearly depicted.

\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart/index.html b/sites/oteguide/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart/index.html new file mode 100644 index 00000000..c929b14b --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart/index.html @@ -0,0 +1,34 @@ +Evaluation Summary Chart

Evaluation Summary Chart

The team presents the program’s OT&E Construct in an Evaluation Summary +Chart (ESC). The chart will vary slightly depending on the COI approach +(see tables 6-8). The ESC identifies the various elements of an +operational test and the relationship of the individual elements to each +other. The initial elements of the OT&E Construct are the Mission +Statement (optional), COIs, Mission Effects (as MOEs), OCs, and +Operational Requirements; these form the first version of the ESC +labeled an ESC-1. The ESC-1 is intended to be a concise presentation +tool for summarizing the focus and scope of the test and relationship of +COIs and operational capabilities. The TD presents the ESC as part of an +Initial Test Design (ITD) Briefing.

Table 6. Evaluation Summary Chart-1 (Integrated COI Approach)

Mission Statement: The CSARL supports the combat search and rescue mission.

Critical Operational Issues

COI 1: Can CSARL enable rescue team navigation to a survivor/evader’s location?COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?COI 3: Does CSARL support worldwide search and rescue operations?

Mission Effects →

Operational

Capabilities ↓

MOE 1.1, 1.2MOE 2.1, 2.2, 2.3MOE 3.1, 3.2, 3.3
Accuracy4.3, 7.4
Situational Awareness4.1, 4.24.1, 4.2, 4.9
Timeliness4.4, 4.54.4, 4.5, 4.6
Mission Planning4.9–4.124.10–4.13
Cyber Resiliency/ Survivability*4.21*4.21*4.21
Interoperability4.294.30–4.324.33–4.35
Reliability4.254.254.26–4.28
Compatibility4.22, 4.244.22, 4.23
Availability4.39
Maintainability4.40–4.43
Ground Equipment4.44
*KPP or supports KPPEffectiveness CentricSuitability Centric

Table 7. Evaluation Summary Chart-1 (Hybrid COI Approach)

Mission Statement: The CSARL supports the combat search and rescue mission.
Critical Operational Issues →COI 1: Can CSARL enable rescue team navigation to a survivor/evader’s location?COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?COI 3: Does CSARL support worldwide search and rescue operations?COI 4: Does CSARL Cyber Ops enable support Mission Assurance?

Mission Effects →

Operational

Capabilities ↓

MOE 1.1, 1.2MOE 2.1, 2.2, 2.3MOE 3.1, 3.2, 3.3MOE 4.1, 4.2, 4.3
Accuracy4.3, 7.4
...
Cyber Resiliency/ Survivability*4.21*4.21*4.21*4.21
....
*KPP or supports KPPEffectiveness CentricSuitability Centric

Table 8. Evaluation Summary Chart-1 (Stand-Alone COI Approach)

Mission Statement: The CSARL supports the combat search and rescue mission.
Critical Operational Issues →COI 1: Can CSARL enable rescue team navigation to a survivor/evader’s location?COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?COI 3: Does CSARL support worldwide search and rescue operations?COI 4: Can CSARL operate in a cyber contested environment?

Mission Effects →

Operational

Capabilities ↓

MOE 1.1, 1.2MOE 2.1, 2.2, 2.3MOE 3.1, 3.2, 3.3MOE 4.1, 4.2, 4.3
Accuracy4.3, 7.4

4.1-4.13, 7.4.

Note: Will require later development of COI 1, COI 2, and COI 3 composite MOP/MOS

Situational Awareness4.1, 4.24.1, 4.2, 4.9
Timeliness4.4, 4.54.4, 4.5, 4.6
Mission Planning4.9–4.124.10–4.13
Cyber Resiliency/ Survivability*4.21*4.21*4.21*4.21
Interoperability4.294.30–4.324.33–4.35

4.29-4.44

Note: Will address in later COI 1, COI 2, and COI 3 composite MOP/MOS

Reliability4.254.254.26–4.28
............
*KPP or supports KPPEffectiveness CentricSuitability Centric

Mission Statement in an Evaluation Summary Chart

The mission statement (optional) is copied and pasted into the +Evaluation Summary Chart.

Critical Operational Issues in an Evaluation Summary Chart

COIs are copied and pasted into the Evaluation Summary Chart.

Mission Effects in an Evaluation Summary Chart

Mission effects, captured as MOEs for the COIs, are listed on the +Evaluation Summary Chart

Operational Capability Requirements in an Evaluation Summary Chart

Operational capability requirements paragraph references from the ICD/IS +ICD/CDD/IS CDD are copied into the first version of the Evaluation +Summary Chart (ESC-1) based on their relationship to the COIs on the +EV-2. This provides a clear understanding of how the COIs and +operational capability requirements relate to the operational and +support‑related performance attributes of the system and provide the +capability required by the warfighter. They are intended as high‑level +placeholders for operational test measures (MOEs/MOPs/MOSs) to be +developed later during the measures workshop and refined during test +concept development.

Note: Operations and conditions (factors and levels) are not depicted +on an Evaluation Summary Chart. However, they are part of the overall +OT&E Construct and are typically provided in the test design and test +concept briefings.

\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/2-1-Test-Design/index.html b/sites/oteguide/OTE_construct_development_guide/2-1-Test-Design/index.html new file mode 100644 index 00000000..d7d91a69 --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/2-1-Test-Design/index.html @@ -0,0 +1,89 @@ +Test Design

Test Design

Test design is the second step in a test activity (see figure 8). For +the OT&E Construct test activity, the focus is on the test design for +evaluating achievement of the mission effects. The test design addresses +the following areas.

Test Design Goals

The SUT, the level of test and the kind of answer required, determine +the test design goals for each COI/operation and each may have multiple +goals and therefore designs. In general, AFOTEC uses three types of test +design goals: characterize, compare, and problem identification.

Types of Test Design

Choosing the most appropriate test design(s) requires expertise on the +system and the operational application it supports. An AFOTEC test +program will likely have combinations of the designs presented here. +Each COI or operation has its own test design and may have more than one +design. The result of a test design is a set of design points and the +rationale for choosing them. The following are typical types of design.

  • Demonstrations.  Demonstration test designs are used to

    demonstrate whether something is possible or not.

  • Space‑Filling Designs.  Space‑filling designs use a variety of

    techniques and criteria to select design points to provide +coverage across the possible set of conditions.

  • Combinatorial Designs. A combinatorial design employs the

    science of systematically selecting combinations of factors and +levels to provide the best chance of identifying problems. This is +most often used in testing software intensive systems.

  • Case Designs.  Case designs are used to demonstrate the

    capabilities of a system and operation under a specified set of +conditions. Several cases may be created using multiple methods.

  • Worst Case/Best Case Design.  One method may be “worst case,”

    where the conditions chosen are those perceived to be the most +stressing.

  • Special Cases Design.  Some special cases may be of particular

    interest to someone (e.g., the user, OSD, Congress). The +underlying reason for the special case should be documented, +because experience has shown the underlying goal is to prove it +either works or it does not work under some specific condition of +interest.

  • Operational Profiles Case Design.  Select cases based on the

    expected frequency of encountering the particular conditions +during planned operations (e.g., from the CONOPS). The rationale +(besides operationally realistic) is that this would be the +fastest way to reveal the most operationally‑relevant problems.

**
+**

Figure 8. Test Design Within the OT&E Construct

+ + + image10 + +

Factor Management

Within the test design, for each operation, operational factors are +managed at specified levels. How they are managed will depend on the +test design goal, the likelihood of encountering levels, and the +magnitude of operational impacts when a levels are changed. Table 9 +illustrates the factor management logic.

  • Vary factor. If a factor management is “Vary,” that factor’s

    levels will be changed in accordance with the test design by the +test team.

  • Fixed factor. “Fixed” factors will be set and will not change

    throughout the test.

  • Log (Record) Factor. Those factors labeled “Log” are not

    actively managed, but the setting of that factor will be recorded +during the execution of test events for possible use during +post-test data analysis.

Table 9. Factor Management Logic

+ + + image11 + +

Table 10 reflects the typical factor management resulting from the +factor prioritization discussed earlier in the guide.

**
+**

Table 10. Factor Management

COI 1: Can CSARL enable survivor/evader navigation to a rendezvous location?
Operation 1: Rescue Survivor
MOE 1: Timeliness of Rescue; MOE 2 Accuracy of Pick-up Point
FactorLevelsPrioritizationFactor MgmtWhy factor is operationally important; Why level is selectedNotes
Likelihood of EncounteringMagnitude of Impact
MOE 1MOE 2
Mode of Travel

Vehicle

No Vehicle

Frequent

Seldom

HHVary VaryAffects the survivor’s ability to move from the area.
Battery Type

Rechargeable

Non Rechargeable

Frequent

Seldom

HHVary VaryAbility of the survivor/evader to have communications.
Terrain

Flat

Mountainous

Littoral

BalancedHH

Vary Vary

Demo

Difference in the terrain could affect the survivors’ ability to move or platform recovery.
Time of Day

Day

Night

Transition

BalancedMMVary Vary DemoNight time could affect the ability to see the survivor/evader.The CT should document notes for each F&L set.
Threat

High

Low

BalancedHHVary VaryThis would affect the platforms ability to reach location.
Disruptive Cyber Threat

Yes

No

CommonHH

Fix

Demo

Will have to look at mission planer vulnerabilities.Fix at Yes.
Non Disruptive Cyber Threat

Yes

No

CommonMM

Fix

Demo

Look at possible mission effects.Fix at Yes.
Software VersionGivenGivens not prioritizedLogComplete instructions on how to plan and operate system, also affects maintenance.Latest version.
TrainingGivenGivens not prioritizedLogPlatform dependent, survival or equipment related capabilities.Both survivor and recovery team have training.

Unconstrained and Constrained events

In prioritizing the factors and determining factor management, the +entire set of possible test conditions has been filtered into a smaller, +more manageable and executable set of test conditions. The process +continues by introducing constraints and picking an appropriate test +design or set of test designs. Test design requires a discussion on +factor constraints. The core team will examine all of the possible +combinations of factor levels and specify which are infeasible due to +operational or physical constraints.

Statistical Measures of Merit

All test designs have associated measures of merit, or quality +indicators, and most are grounded in scientific statistical +methodologies. The measures of merit should be considered when deciding +on a test design. Regardless of chosen design type, there is a related +measure of merit which should be a consideration addressed in the test +plan documentation. The AFOTEC Test Design Guide has more information on +statistical measures of merit and their applicability to different +design types.

Test Events

Any single design results in a set of test events. A single test event +is defined as a single execution of a test to collect data with the +operational factors set at a single, given level (i.e., a single +condition or design point). Table 11 continues the survivor/evader +navigation example introduced earlier. In this example, the team has +decided the type of answer they wanted to provide was to characterize +the system’s behavior. Consequently, a characterize design matches well +with the desired type of answer. Other factors are fixed.

Table 11. Example COI Test Events to Recover Isolated Personnel

Test EventMode of TravelBattery TypeTerrainTime of DayThreat
Characterize
1No VehicleRechargeableMountainTransitionLow
2VehicleNon-rechargeableFlatNightLow
3No VehicleNon-rechargeableLittoralNightHigh
4No VehicleNon-rechargeableMountainDayHigh
5VehicleRechargeableLittoralDayHigh
6No VehicleNon-rechargeableFlatTransitionHigh
7VehicleRechargeableMountainNightHigh
8VehicleNon-rechargeableLittoralTransitionLow
9No VehicleRechargeableMountainTransitionLow
10VehicleNon-rechargeableFlatNightLow
11No VehicleNon-rechargeableLittoralNightHigh
12No VehicleNon-rechargeableMountainDayHigh
Problem ID
13VehicleRechargeableLittoralDayHigh
14No VehicleNon-rechargeableFlatTransitionHigh
15VehicleRechargeableNightHigh

If multiple test designs are created, such as a characterize design +supplemented with a case design, the total number of test events +increases. Similarly, the total number of test events increases in +accordance with test events that are replicated.

Test Design Validations

Testing evolves continuously and it is expected that test designs will +change. Most of the design evolution is managed by the test teams during +the normal testing ops. However, a test design validation is a more +formal effort that generally occurs at the request of a Detachment TD +and is usually employed when the test design is significantly outdated, +when there have been major changes in the scope of an acquisition, or +when earlier test design documentation is not sufficient/available. The +scope of a design validation depends on the test team needs. It could +require all of the step leading to a test design or only specific pieces +of the test design to be readdressed. When making a design validation +scope determination, keep in mind that most of the steps build on one +another. Formal test design validations should be requested by the +Detachment through the A‑3 PM.

\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/2-2-Measures-Development/index.html b/sites/oteguide/OTE_construct_development_guide/2-2-Measures-Development/index.html new file mode 100644 index 00000000..d32c3aaf --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/2-2-Measures-Development/index.html @@ -0,0 +1,58 @@ +Measures Development

Measures Development

This section discusses the process for refining MOEs, developing +measures of performance (MOP), and measures of suitability (MOS), and +identifying the associated data elements. MOEs are identified during the +earlier battlespace development effort and refined during a measures +workshop (MW). See the AFOTEC Measures Guide for additional details. In +AFOTEC, measures are developed using a top-down and bottom-up approach. +The top down approach is most useful for MOE development and the +bottom-up approach is effective when developing MOPs and MOSs. Figure 9 +illustrates where measures fit in the OT&E construct.

Figure 9. Measure development in the OT&E Construct

+ + + image12 + +

Measures of performance and suitability (MOP/MOS) are initially +developed in a MW facilitated by A‑2/9 with A‑3 and Detachment +participation. The optimal time for a MW after the initial OT&E +Construct is approved and a draft CDD/IS CDD, or an equivalent document, +(e.g., AF Form 1067, A‑spec) is available as the source document for +capability requirements. Measures development can also be triggered by +immediate need.

Measures are expected for RFP and MS B/C TEMPs, test concept +briefings, and all AFOTEC assessment and test plans. For RFP TEMPs +that are too early for a Measures Workshop, an initial measure set +will be developed by A-2/9 (working with the detachment and the Test +Team as input to the RFP TEMP.

Measures of effectiveness (MOE) are the measures related to the +capability to accomplish an operation. MOEs directly determine the +degree of the desired effect achieved for a COI.

Measures may also be associated with the operational capabilities that +contribute to a COI being satisfied. Measures of Performance (MOP) are +the measures related to the system’s capabilities, features, functions, +and properties enabling the effects to be achieved. Measures of +suitability (MOS) are the measures related to the degree to which a +system can be placed satisfactorily into field use. Additional +information on MOPs and MOSs can be found in AFI 63‑101/20‑101_AFGM +2016-01, Life Cycle Management, 9 May 17; AFI 99‑103, Capabilities +Based Test and Evaluation, 6 Apr 17; and AFOTECPAM 99‑104, AFOTEC +Operational Suitability Test and Evaluation Guide, 24 Sep 13, etc.). +Test teams should consult the AFOTEC Measures Guide, their Detachment +TA, and A‑2/9 for current best practices on the development of measures. +Proposed exceptions to these best practices should be discussed with +A‑2/9 before developing measures. Generally, the desired outcome of a MW +is a complete set of measures for the test activity with defined scopes +for each measure.

The MW are meetings facilitated by A-2/9 and A-3. Major stakeholders in +the acquisition program are invited: the user community, the program +office (PO), DOT&E, system developers, and developmental testers. All +participants apply their subject matter expertise toward the goal of +developing a measure set and test designs. Generally, the Detachment, +A‑2/9 and A‑3 do “homework” prior to the workshop. A‑2/9, with inputs +from the Detachment TD or technical advisor, develops draft measures in +preparation for the MW meeting. The purpose of MW preparation before +holding the MW meeting is to save time and level of effort.

\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/2-3-Test-Execution-Planning/index.html b/sites/oteguide/OTE_construct_development_guide/2-3-Test-Execution-Planning/index.html new file mode 100644 index 00000000..853f3278 --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/2-3-Test-Execution-Planning/index.html @@ -0,0 +1,377 @@ +Test Execution Planning

Test Execution Planning

The AFOTEC core team members will usually meet informally to continue +building upon the information compiled during the Battlespace +Development, initial test design, and measures development. This is +referred to as execution planning (see figure 10). The purpose of these +follow-on meetings is to finalize the test construct such as refining +test design worksheets, identifying test methodologies, creating test +scenarios, and identifying resources.

Figure 10. Test execution Planning in the OT&E Construct

+ + + image13 + +

Test Methodology

Test events may be executed through a variety of methods. Replicating a +realistic mission or mission segment should be used whenever feasible. +Replicating a realistic mission does not have to focus on the engagement +or battle outcome level (full engagement level of testing can be cost +prohibitive), but should provide the means to evaluate the operational +effectiveness and suitability of the system or subsystem in +operationally realistic conditions. Additionally, it should provide a +means to determine overall mission capability. Testers create controlled +test scenarios to reflect the conditions that best evaluate the system. +Field testing is a good, initial choice for operational testing as it +provides the most operationally realistic environment. However, field +testing is not always feasible to capture all test events. M&S provides +another venue for executing test events (USC, Title 10 imposes +constraints on the use of M&S during operational testing) and may +include distributed test applications using live, virtual and +constructive (LVC) simulation assets. M&S requirements should be +determined early in order to become part of the system development +contract. Other test methods include studies and analysis, exercises and +training opportunities. The test methodologies may be a combination of +these methods during DT, IT&E and OT. For example, early in a program, +you might use M&S to help identify important operational factors to +include in an Early Operational Assessment (EOA) or Operational +Assessment (OA). Execution of test events during the EOA/OA is followed +by some analysis highlighting that some factors may not be important +(and possibly identify new factors). The revised set of operational +factors is then used in the OT&E.

If test capability requirements (to include modeling and simulation) are +identified during OT&E Construct development, accreditation activities +are required. Identification of test capability requirements will result +in the development of an accreditation memo. The memo identifies the +test capability requirements, accreditation documentation requirements +and format, timelines, the accreditation authority and other pertinent +information. The memo is increasingly important because it initiates +development of the accreditation plans and begins tracking VV&A resource +expenditures including manpower and dollars.

Test Scenarios

Test scenarios capture the end‑to‑end flow and reintroduce the factors +identified during the battlespace development and test design. During +those earlier steps the operational factors were used to identify +condition based test events. These events must be translated into +representative operational test scenarios (figure 11). Test events +should be executed in in the most representative scenarios possible. +This allows the best evaluation of a system by replicating a realistic +mission or mission segment. Test scenarios should allow all key factors +identified in the condition-based test event to be exercised.

Figure 11. Test Events and Scenario Linkage

+ + + image14 + +

Test scenarios may include test events supporting multiple measures or +COIs. Thus, one scenario may satisfy the completion of multiple test +events simultaneously (Figure X). Evaluating a system by replicating a +realistic mission or mission segment should be used whenever feasible. +Mission replication should provide the means to evaluate the operational +effectiveness and suitability of the system or subsystem in +operationally realistic conditions. Realistic threats, including cyber +threats, should be drawn from the latest intelligence sources for the +employing commands. Core teams create controlled test scenarios that +reflect the operationally realistic conditions to best evaluate the +system. Defense business systems testing will include theft/fraud test +scenarios.

The intent is to identify test scenarios that allow for an end‑to‑end +flow from one COI to the next, as well as for concurrent COIs. Within +the test scenarios, factors are set to the appropriate levels called for +by each test design. It is important to realize that the levels may be +different or vary from scenario to scenario. For example, an F‑16 +conducting a CSAR scenario is unlikely to fly at high altitudes; thus, +the level for altitude is set to low and another scenario (such as a +strike scenario) is used to capture altitude at its high level. Another +approach would be to select a set of test scenarios that allow all the +test events (described by the factors and levels) to be executed within +the scenarios. Selecting test scenarios appropriately allows for +efficient use of test resources, as well as presenting an operationally +realistic test environment. Proper scenario selection also helps avoid +testing in independent segments (e.g., COIs) when there are actually +interactions between these segments. However, not all test events are +likely to be executable as part of one overall scenario or set of +scenarios. Expect some test events to require separate, specific +portions of a scenario to establish the necessary operational +conditions. A consequence of identifying end‑to‑end flow and interaction +between COIs is that test events are overlapping and occurring +simultaneously. For example, the same F‑16 sortie that captures two +targeting test events (one in mountainous terrain, the other in flat +terrain) also captures a mission‑planning test event and a weapons +load‑time test event. These events all take place within the context of +a CSAR scenario where the particular operational factors are set to +levels consistent with a CSAR scenario. Figure 12 reflects this concept +of end-to-end threads across COIs

Figure 12. End-to-end threads across COIs

+ + + image15 + +

Test scenarios also allow the re‑introduction of the operational factors +that were set aside earlier. These are the operational factors likely to +exist in the operational environment, but at a given level or minimally +related to the system. These are included in the test scenarios to +ensure operationally realistic conditions.

Test Capability Needs and Shortfalls

Execution of operationally relevant OT&E will normally require test +capabilities. This section only discusses test capabilities and +accreditation to the extent needed for an initial test design. For more +details see the AFOTEC Test Capabilities Guide and the AFOTEC +Accreditation Guide. AFOTEC does not own or operate test ranges, +facilities, or assets and must identify test capability resource +requirements as early as possible to ensure they are available, and +technically and operationally sufficient, for OT&E purposes. The +battlespace development and test design processes defined the test scope +and methodologies and is the foundation for identifying test capability +requirements. Table 10 shows typical test capability requirements.

Table 10. Typical Test Capabilities

  • Test articles

  • Test sites

  • Test instrumentation

  • Test support equipment

  • Threat representation

  • Test targets and expendables

  • Operational force test support

  • Models, simulations, and test beds

  • Joint operational test environment

  • Special requirements

Requirements that cannot be met by existing test infrastructure and +capabilities must be identified to A-5R. Gaps/shortfalls associated with +NTTR should be addressed through A-8Z. Test capability requirements are +addressed in the AFOTEC Test Resource Plan (TRP) and the AFOTEC uses a +Time-Phased Investment Planning Document process to advocate for test +capability development. For test capabilities that may require foreign +threat capability, contact AFOTEC A-2N to request and advocate for +foreign assets through the AF foreign materiel program (FMP) process. +This process acquires and exploits foreign systems for testing, training +and intelligence purposes and may satisfy a threat test capability need.

Time-Phased Investment Document

The AFOTEC T-PhID (formerly Test Capability Roadmap) serves as the +cornerstone of AFOTEC’s test capability investment strategy. AFOTEC must +communicate OT requirements to AF and DoD investment forums. Test +capability development must be funded in appropriate investment +portfolios to ensure the needed capabilities will be in place, verified, +and validated in time to support the test. A-5R continuously gathers OT +requirements (test capability gaps/shortfalls) through:

  • Individual program test capability readiness assessments (TCRAs)

  • SharePoint interface used for spontaneous/asynchronous +identification of requirements by test teams

  • An annual requirements call closely aligned with the AFOTEC RRB

Test capability requirements priorities are approved by AFOTEC CC +annually, in time to support AF and DoD investment planning processes. +Some of the test capability investment forums are listed below.

  • Test Investment Planning and Programming (TIPP)

  • Central Test and Evaluation Investment Program (CTEIP)

  • Resource Enhancement Program (REP)

  • Threat Systems Working Group (TSWG)

  • Joint Aircraft Survivability Program (JASP)

A-5R coordinates communication of AFOTEC test capability requirements to +these investment forums, coordinates review of development proposals to +identify those that may satisfy AFOTEC needs, and monitors program +development ensuring fulfillment of AFOTEC needs including completion of +capability verification and validation. There are numerous range +capability requirements that must be addressed as early as possible.

Determining Range Requirements

In building a mission scenario and determining range requirements, the +tester needs to know, for example, the type of target, the number of +aircraft attacking a target and weapons employed. The tester also needs +to consider the range’s ability to accommodate the operational test +without environmental impact. The system CONOPS should contain +information such as specific tactics and techniques to be employed +against certain targets and threat systems. Ensure that range personnel +have a full understanding of the specific OT objectives. The core team +should consult with A‑8Z (OL‑NN post-tasking order) for testing +considerations at NTTR and A‑5R for any other test range or facilities.

Range Requirement Identification

Carefully thought‑out mission scenarios provide the test team with +preliminary test range resource requirements (e.g., threat simulators +and instrumentation packages). Early identification of these +requirements is extremely important for advanced range scheduling, test +resource plan (TRP) development, and incorporation of new range +requirements into the various range improvement programs and other +investment forums (need at least 1 year lead time). In support of the +core team, A‑5R (A‑8Z for NTTR) provides information on current and +legacy DoD T&E databases that archive data on existing T&E test assets +and is the Air Force’s focal point for integrating new T&E range +requirements into the range improvements program. All potential test +sites should be considered before the final selection is made.

Range Selection Considerations

The Test Team may have to give special consideration to test range +selection and use. Usually, flight test programs require scheduling of +and coordinating with test ranges for some or all test sorties. Test +teams need to ensure range availability at the time of their scheduled +test. All major ranges and centers are subject to the DoD uniform +funding policy and require formal documentation of the test and the +support needed. The range, in turn, provides a statement of their +capability to support the test. The range process can take 6 months or +more. Although documentation requirements vary among the ranges and +centers, most require the development of a Program Introduction Document +(PID). When selecting a range, ensure the availability of applicable +range data is considered. To determine specific range initiation +requirements, consult the Universal Documentation System Handbook +501‑08, available from Secretariat, Range Commanders Council, +TEDT‑WS‑RCC, White Sands Missile Range, New Mexico 88002‑5110.

National Cyber Range Considerations

The National Cyber Range (NCR) provides test teams with a capability to +accomplish system training and perform disruptive and non-disruptive +cyber-attacks on a complete or sub-component of a system under test at +multiple classification levels. The NCR’s system reset capabilities make +it possible for cyber attackers to completely disable or even +catastrophically damage a system without the risk of negatively +impacting operational users or causing unrecoverable damage to the test +environment. This environment also provides a means for cyber offensive +and defensive training as well as basic user training before or during +test execution (to include cybersecurity assessments). As the NCR is a +contained range, connections with outside systems may need to be +emulated. Having said that, events can occur exclusively at NCR, or in +conjunction with other Joint Mission Environment Test Capability or +Joint Information Operations Range nodes. However, programs using unique +systems (i.e., components that won’t be used by any other programs in +the future) may incur a cost of purchasing the necessary hardware and/or +software. Test Directors interested in learning more about the NCR or +seeing if the NCR can support their program can contact the NCR directly +at osd.pentagon.ousd-atl.mbx.trmc-ncr@mail.mil.

Test Targets

Test targets, when applicable, should be realistic; they should be +operationally representative and challenging. The TD should coordinate +with the applicable MAJCOM to develop the target list. Through A‑2N, +coordinate with the appropriate intelligence agency on the design of +selected targets, existing and newly developed. A‑5R maintains current +lists of available aerial test targets in the inventory and is the POC +for obtaining target allocations. A‑5R also maintains contacts for other +target types such as surface targets. Funding for target‑related +expenditures must be included in the TRP.

Range Safety Considerations

Ranges and test centers are sensitive to safety considerations and may +require special test procedures, hardware, or software to reduce the +risk of a mishap during the test. Ranges and test centers frequently +require safety review boards before start of testing. The TD should +allow sufficient time to support these safety reviews. SE can assist in +resolving range safety issues or support in safety reviews. When +identifying required test resources and range requirements, test teams +should ensure weather warnings and advisories are considered in support +requirements (contact A‑2/9 for assistance).

Range Instrumentation Considerations

Instrumentation varies widely among ranges. Therefore, the test team +should carefully select a range to ensure instrumentation is available +to provide the required information and to allow the most realistic +representation of the operational environment.

Range Data Processing Considerations

Data processing capabilities and times are considered when the test +schedule is prepared. The range equipment user’s guide, facilities +handbook, or the test support contact may be consulted for typical +processing times. TDs must also consider the method by which test data +is transmitted for analysis (SIPRNET, courier, etc.).

Test Article Instrumentation

Identify the test article instrumentation requirements early to ensure +that instrumentation is sufficient to support test events. There is a +fine balance between not compromising the production‑representative test +article and obtaining telemetry from an instrumentation package. Test +article instrumentation should be compatible with the range or test +facility telemetry and data collection systems, with sufficient accuracy +and sample rates to enable verification of system performance. If the +test article needs to transmit instrumentation data, the instrumentation +package needs to be compatible with the MIL‑STD‑1553 multiplex data bus.

Program Introduction Document Release Authority

PIDs are executing direction approved in TRPs for obtaining test range +support. Det/CCs are authorized to release PIDs to range agencies. +Copies of all PIDs are sent to the AFOTEC/CC, A‑3 and A‑5/8 when +released to range support agencies by the Det/CC. Issues identified +during subsequent PID coordination with the supporting range are +highlighted during the Detachment Commander Monthly Program Update.

The Use of Modeling and Simulation

M&S includes, but is not limited to, digital M&S, hardware‑in‑the‑loop +(HITL) virtual simulations and test drivers such as data injectors and +stimulators. M&S also includes physical models of targets, threat +representations and combinations of simulations. Testers (DT&E, LFT&E, +OT&E) should collaborate early with the program manager’s (PM) M&S +proponent on planned uses of M&S for the purpose of identifying OT M&S +requirements, necessary verification and validation (V&V) activities, +and for securing program office M&S funding (as applicable) IAW +DODI 5000.02 and AFI 63‑101/20‑101, 9 May 17.

AFOTEC uses digital M&S for two primary purposes: prediction of SUT +performance and extension of field test results. AFOTEC uses HITL +virtual simulations (and facilities) and test drivers to test system +performance under conditions that cannot be reproduced on an open‑air +range or on actual operational equipment. The OT&E Construct, test +concept and test plan should identify and explicitly describe the use of +M&S to include the use of distributed capabilities for executing +operational test events.

M&S can play a helpful role in optimizing limited open‑air range (OAR) +or ground test facility test time. In addition, testers can examine +various configurations of the OAR and SUT. Resulting information +provides insight to maximize return from limited range time and to +investigate areas of principle interest to the warfighter.

With an adequate representation of the SUT, the test team can use M&S +assets to predict SUT performance and optimize field test events by +estimating SUT performance boundaries. The optimization enables +tailoring of field testing to address those areas that merit further +evaluation or are of special interest to the user.

M&S can fill in gaps associated with field testing in cases where it +would be too expensive or impossible due to lack of capability to +conduct an OAR‑only evaluation. The test team would first use M&S to +rehearse and construct valid OAR events and ensure a common baseline. +Then once the M&S is appropriately accredited, the test team can use it +to run events beyond the scope of OAR events.

As an example, consider testing an air‑to‑air missile system, where +the primary target of interest is a foreign fighter. Since it would be +impractical or impossible to fire the SUT missile at an actual foreign +aircraft, OAR events may consist of firing the SUT missile at a USAF +fighter configured as a surrogate foreign aircraft. M&S would then +repeat the OAR drone aircraft firings and “extend” the results to the +foreign aircraft of interest by executing the M&S with a +representation of the foreign aircraft signature and other parameters +of interest, provided by an external organization (NASIC, MSIC, etc.). +AFOTEC could then provide the user information regarding SUT +performance versus real threats.

Other reasons for using M&S are safety concerns, environmental concerns +(hazmat), treaty limitations, OPSEC concerns, or support concept +limitations.

Whenever the test team intends to use M&S results to capture information +in an OT&E Final Report, they need to ensure proper M&S accreditation. +Test teams are encouraged to contact A‑2/9 early in the life of a +program, primarily after the OT&E Construct is completed, for assistance +in determining M&S applicability and VV&A requirements. A‑2/9 and A-5/8 +maintains information on various DoD and AF M&S and VV&A applications, +including OT&E‑specific M&S/VV&A guidance.

Test Capability Accreditation

AFOTEC often uses test capabilities to create a pseudo-employment or +combat environment in which to conduct the operational testing. These +test capabilities may include M&S of the employment environment as well +as M&S of the SUT. The AFOTEC Accreditation Guide provides actionable +information for Test Directors, analysts, engineers, and program +managers on how best to plan, execute, and report accreditation of M&S +systems. The accreditation process involves:

  • Developing an executable plan, assessment, and report with focus on

    documenting the results of the accreditation assessment

  • Documenting the recommendations in support of the accreditation

    decision, and

  • Documenting lessons learned during accreditation

Accreditation is applicable when a test capability is used directly or +indirectly to provide information that appears in an OT&E Final Report. +If a TD intends to draw weapon system capability conclusions (i.e., rate +measures) based upon the use of a test capability, accreditation is +required. AFOTEC accreditation policy exists to ensure standardization +across test teams and a consistent level of rigor in determining +adequacy of test capabilities. Accreditation activities should not +excessively burden test teams or lead to inordinate expense. The AFOTEC +staff lead for Accreditation is A-2/9. Refer questions about +Verification, Validation, and Accreditation to +UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil.

Test capabilities used solely for test‑planning purposes and assessments +(such as observations, EOAs) do not require a formal accreditation, +although the analyst should exercise a similar process to ensure that +the test capability is adequate and to identify risks involved and how +they may affect the overall test. Any informal accreditation +investigation procedures (peer review, analyst investigations, etc.) +should be documented to ensure continuity when program personnel change.

AFOTEC’s mission is to Deliver Combat Capability through Operational +Test. AFOTEC often uses test capabilities to create a pseudo-employment +or combat environment in which to conduct the operational testing. These +test capabilities may include M&S of the employment environment as well +as M&S of the SUT. The test capabilities used in a given test do not +always represent the employment environment with 100% accuracy. There +are usually some differences in fidelity between the actual combat +systems and test representations. Given these differences, AFOTEC is +careful in drawing conclusions about SUT capabilities and ensures that +the representation of the employment environment is adequate to draw +credible conclusions. Inherently, AFOTEC assumes some degree of risk +when using test capabilities to represent an employment environment or +SUT to determine SUT capabilities. The purpose of accreditation is to +characterize that risk and ensure the risk is acceptable.

See the AFOTEC Accreditation Guide accreditation details.

Test Constraints and Limitations

Limitations may be identified at any point in a program, however the +earlier a potential limitation is identified, the more likely it can be +resolved without impacting OT&E credibility. The TD and core team +including A-5R and/or A‑8Z are encouraged to identify limitations as +early as possible. The documentation provides justification for +continued improvement and modernization of test capabilities that +ultimately lead to more useful and relevant T&E reports and better +systems delivered to the warfighter. A limitation is something that +would influence being able to accomplish a credible operational +evaluation.

  • Limitation: A limitation affects the ability to evaluate certain

    aspects of a weapon system or to re‑create certain aspects of the +operational environment. Limitations can be due to differences in +the scenario (operational versus test), test capabilities such as +threat simulation, range restrictions (safety, physical airspace), +specific test measurement constraints, numbers of test articles, +or the threat lay down (types and numbers). Limitations, once +identified, are carried throughout all phases of the test program +unless the underlying factors are no longer applicable. A system +that is not production representative for an OT&E may be +identified as a limitation.

  • Mitigation: Each limitation requires the team to plan a

    mitigation to reduce the risk to the evaluation of the system. +Mitigation is intended to reduce the impact of the limitation to +the point where the evaluation is still credible. There are +typically few, if any, limitations in conducting credible EOAs and +OAs. However, when there are limitations, mitigation may be +different for an EOA, OA, or IOT&E. M&S is one method used to +mitigate a limitation. Teams should actively pursue mitigation of +a limitation in order to have an adequate test.

  • Impact (of a limitation after mitigation): The impact should

    describe the extent to which the limitation will (for a plan) or +did (for a report) affect the quality, completeness and/or +confidence of our evaluation of the system under test’s +effectiveness, suitability and mission capability. The intent is +to acknowledge limitations and inform the decision‑maker and +warfighter of the extent to which the limitations will or did +affect our ability to report weapon system performance. The impact +should clearly state what characteristics or attributes of the +evaluation are affected.

Table 12 provides some example limitations, mitigations, and impacts.

Table 12. Examples of Limitations

LimitationMitigationImpact
Limited UAS System Availability

Coordination with operational unit to share assets between the field training unit and IOT&E test

Leverage combat missions

Inability to fully evaluate all measures

Cybersecurity not evaluated

Limited Flight Hours for Reliability, Maintainability and Availability EvaluationUse reliability availability logistics operations modelReported values may not reflect actual values in operational use
Limited capability of Red Team to test weapon system via data link while in flightCoordinated with AFTC to emulate mission parameters in anechoic chamber to allow Red Team cyber attacks

Cyber-exploitation effects not fully evaluated

Inability to fully evaluate all measures

Lack of Threat Systems at Test FacilitiesNoneInability to report system effectiveness versus some threats
No integration of Lynx Radar Capability in Mobile Ground Control StationNoneUnable to evaluate Lynx synthetic aperture radar

Basis of Estimate for Test Resources

Together, the set of test events, test methodologies and test scenarios +form the basis of estimate. They describe why you are testing, what you +are going to do and how you are going to do it. Underlying the basis of +estimate is a set of assumptions that are validated to the extent +possible and documented. For the OT&E Construct, particular focus is +placed on the high cost (which includes high level of effort) and +long‑lead items. Typical examples of such items are threats, +instrumentation and M&S efforts. Some of these items have been +identified throughout the preceding steps. In forming the basis of +estimate, these previously identified items are consolidated and test +designs are reviewed to identify new items. Collectively, there may be +overlap between the resources required for each COI. These should be +identified and a consolidated list of resources should be provided (with +traceability and rationale).

Table 13 contains the basis of estimate contents.

Table 13. Contents of Basis of Estimate

Content AreaContent Expectations
COIsThe COIs define the operations that need to be exercised during OT&E and provide 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.
Test EventsFor the particular test design(s) underlying the test events, a review of the factors and levels provide 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.
Test MethodologyHow 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.
Test ScenariosTest 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.
AssumptionsAlthough assumptions may not directly drive resources, they provide indicators of potential risks and disconnects with other organizations.

Initial Resource Estimates

The core team uses the OT&E Construct basis of estimate to refine +initial resource estimates documented in the initial TRP. The Detachment +TRM updates the TRP to support the ITD Brief. The TD and Det TRM review +each resource category of the TRP to determine which line items need +costing and which ones need to be paid for by AFOTEC. Table 14 contains +the OT&E support costs breakdown.

Table14. Operational T&E Support Costs

AFOTEC PaysAFOTEC Does Not Pay
  • Range costs

  • Equipment Rental

  • Printing and reproduction

  • Communications

  • Real property maintenance and construction

  • Contractor support for OT&E

  • Data reduction

  • Special supplies and equipment

  • Leases

  • Civilian pay for (temporary over hires)

  • Per diem and travel

  • Transportation of equipment required for test

  • Supplies and equipment

  • Dry run planning

  • Test preparation

  • COTS M&S supporting test planning and reporting (including accreditation)

  • Cybersecurity testing (cooperative vulnerability & penetration assessment/ adversarial assessment)

  • Acquisition/modification of the system

  • Aircraft flying hours (other than range support aircraft)

  • Acquisition costs for major test vehicles

  • 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.

  • Missiles, munitions and targets

  • Telemetry kits

  • Range infrastructure

  • Type 1 (contractor) training

  • Digital M&S that produces data for OT&E

  • M&S V&V

Identifying Resources. To move from the basis of estimate to a +completed test resource plan (TRP) takes a significant amount of effort. +This is an iterative process, and teams will generally refine the +initially planned events/activities based on resource availability, +realism, cost, etc., which are focused on arriving at the best +cost-benefit solution.

The actual costing of resources, developing agreements, and many other +detailed steps required to source and cost are not captured here. These +specifics depend on acquisition and test approaches (joint, OT lead, +resource types, participants, funding strategies, time-to-test start, +infrastructure developmental needs, etc.), and teams rely on the +Headquarters and Detachment resource managers to support each OT&E +Construct effort.

\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct/index.html b/sites/oteguide/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct/index.html new file mode 100644 index 00000000..3a753f42 --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct/index.html @@ -0,0 +1,49 @@ +Documenting the Operational Test and Evaluation Construct

Documenting the Operational Test and Evaluation Construct

Documentation cannot be overstated. Too many programs efforts have been +lost and needed to be re-accomplished because they were not properly +documented or in some cases, not documented at all. Each of the process +steps above have a recommended documentation approach. Why documentation +important?

  • The only constant with acquisition programs and the people who work +them, is change. Personnel come and go, and programs evolve. When +new people start a program, questions about how and why the OT&E +looks the way it does.

  • Leadership often ask why OT&E is doing various activities

  • DOT&E often has questions about the OT&E approach

  • Integrating testing is best served by robust OT&E documentation

  • Provides the foundational products and narrative for TEMP and OT&E +plan inputs

Following the test design development, the TDM provides the test design +products to the TD. Using these products, the TD then begins developing +the ITD Briefing with support from his core team for presentation to the +AFOTEC/CC on the date specified in the tasking order. This briefing will +be developed and coordinated electronically for 2‑letter approval. The +briefing is an internal‑only AFOTEC product (i.e. it is not presented to +DOT&E). The purpose of the ITD Briefing is to convey to the AFOTEC/CC, +with a high degree of confidence, the complete beginning‑to‑end scope of +OT activities, resources, and costs with rationale. The ITD Briefing +indicates the specific acquisition events that the planned OT activities +support. The Detachment TD presents the acquisition information in a +briefing to the AFOTEC/CC for approval. Tailor the level of detail in +each area within the briefing to fit the specific program circumstances. +If a particular subject area in the ITD Briefing template does not apply +to a program, do not include that subject area in the briefing. +Significant issues should be resolved with appropriate HQ directorates +before the formal ITD Briefing. The ITD Briefing must include all +supporting information by using embedded documents, as described in the +briefing template. Following completion of the briefing, the OT&E +Construct is updated as required by the Detachment TD to reflect the +decisions made. The detailed ITD Briefing template is found on the +AFOTEC SharePoint.

The OT&E Construct supports early integration and promotes the +combining, where appropriate, of DT and OT events to satisfy both DT and +OT objectives. Remember that throughout IT&E planning and execution, the +individual DT and OT objectives should not be compromised. Early +integration of DT and OT planning provides the foundation for the MS A +(and beyond) Test and Evaluation Master Plan development and supports +identification T&E requirements needed for RFPs. The TEMP is an +opportunity to document integration with the DT community and reduce +dedicated OT events when they have been accomplished satisfactorily in +IT&E. These events are only removed from dedicated OT when OT +requirements have been met.

\ No newline at end of file diff --git a/sites/oteguide/OTE_construct_development_guide/index.html b/sites/oteguide/OTE_construct_development_guide/index.html new file mode 100644 index 00000000..300a006e --- /dev/null +++ b/sites/oteguide/OTE_construct_development_guide/index.html @@ -0,0 +1,10 @@ +OT&E Test Construct Development Guide

OT&E Test Construct Development Guide

11 February 2021

Last Updated: 26 February 2021

Originating Office: OPR is AFOTEC A-3 and OCR is AFOTEC A-2/9

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/1-2-INTRODUCTION/index.html b/sites/oteguide/accreditation_guide/1-2-INTRODUCTION/index.html new file mode 100644 index 00000000..d4ade649 --- /dev/null +++ b/sites/oteguide/accreditation_guide/1-2-INTRODUCTION/index.html @@ -0,0 +1,26 @@ +INTRODUCTION

INTRODUCTION

The AFOTEC Accreditation Guide provides actionable information for test +directors (TD), analysts, engineers, and program managers on how best to +plan, execute, and report accreditation of modeling and simulation (M&S) +systems. The accreditation process involves:

  • Developing an executable plan, assessment, and report with focus on +documenting the results of the accreditation assessment

  • Documenting the recommendations in support of the accreditation +decision, and

  • Documenting lessons learned during accreditation

Accreditation is applicable when a test capability is used directly or +indirectly to provide information that appears in an operational test +(OT) final report. If a TD intends +to draw weapon system capability conclusions (i.e., rate measures) based +upon the use of a test capability, accreditation is required. AFOTEC +accreditation policy exists to ensure standardization across test teams +and a consistent level of rigor in determining adequacy of test +capabilities. Accreditation activities should not excessively burden +test teams or lead to inordinate expense. The AFOTEC staff lead for +Accreditation is A-2/9. Email questions about verification, validation, +and accreditation to A-2/9 workflow at: +UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil .

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/1-3-Test-Capability-Accreditation/index.html b/sites/oteguide/accreditation_guide/1-3-Test-Capability-Accreditation/index.html new file mode 100644 index 00000000..9c7b4fc0 --- /dev/null +++ b/sites/oteguide/accreditation_guide/1-3-Test-Capability-Accreditation/index.html @@ -0,0 +1,24 @@ +Test Capability Accreditation

Test Capability Accreditation

AFOTEC's mission is to deliver combat capability through operational +test. AFOTEC often uses test capabilities to create a pseudo-employment +or combat environment in which to conduct the operational testing. These +test capabilities may include M&S of the employment environment as well +as M&S of the system under test (SUT). The test capabilities used in a +given test do not always represent the employment environment with 100% +accuracy. There are usually some differences in fidelity between the +actual combat systems and test representations. Given these differences, +AFOTEC is careful in drawing conclusions about SUT capabilities and +ensures that the representation of the employment environment is +adequate to draw credible conclusions. Inherently, AFOTEC assumes some +degree of risk when using test capabilities to represent an employment +environment or SUT to determine SUT capabilities. The purpose of +accreditation is to characterize that risk and ensure the risk is +acceptable.

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation/index.html b/sites/oteguide/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation/index.html new file mode 100644 index 00000000..e794bf93 --- /dev/null +++ b/sites/oteguide/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation/index.html @@ -0,0 +1,27 @@ +The Use of Modeling and Simulation

The Use of Modeling and Simulation

The "AFOTEC OT&E Guide," 11th ed. states that whenever M&S is used to +capture information in an OT&E Final Report, proper M&S accreditation is +required. M&S includes, but is not limited to, digital M&S, +hardware-in-the-loop (HITL) virtual simulations and test drivers such as +data injectors and stimulators. M&S also includes physical models of +targets, threat representations and combinations of simulations. Test +planners (DT&E, LFT&E, OT&E) should collaborate early with the program +manager's (PM) M&S proponent on planned uses of M&S for the purpose of +identifying OT M&S requirements, necessary verification and validation +(V&V) activities, and for securing program office M&S funding (as +applicable) IAW DoDI 5000.02 and AFI 63-101/20-101, 9 May 17.

AFOTEC uses digital M&S for three primary purposes: test planning, +prediction of SUT performance, and extension of field test results. +AFOTEC uses HITL virtual simulations (and facilities) and test drivers +to test system performance under conditions that cannot be reproduced on +an open‑air range or on actual operational equipment. The ITD, test +concept and test plan should identify and explicitly describe the use of +M&S to include the use of distributed capabilities for executing +operational test events.

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions/index.html b/sites/oteguide/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions/index.html new file mode 100644 index 00000000..5cead403 --- /dev/null +++ b/sites/oteguide/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions/index.html @@ -0,0 +1,28 @@ +Verification, Validation and Accreditation Definitions

Verification, Validation and Accreditation Definitions

Definitions are based on DoDI 5000.61, DoD M&S Verification, Validation +& Accreditation (VV&A)

  • Verification. The process of determining that a test capability +accurately represents the developer's conceptual description and +specifications. Verification addresses whether the M&S works as +planned. Verification is typically accomplished by the model +developer (SPO, system contractor or facility/M&S owner).

  • Validation. The process of determining the degree to which a test +capability provides an accurate representation of the real world +from the perspective of the intended uses of the test capability. +Validation addresses whether the M&S represents reality. Validation +is typically accomplished by the model developer (Program Office +(PO), system contractor or facility/M&S owner).

  • Accreditation. The official certification that a test capability is +acceptable for use with a specific application. Accreditation +addresses whether the M&S is acceptable for a specific use. +Accreditation is accomplished by AFOTEC.

The accreditation requirement applies to I/Q/F/MOT&Es and Operational +Utility Evaluations (UOUEs). Typical test capabilities requiring +accreditation may include open air range (OAR) assets, ground test +facilities, M&S, foreign materiel acquisition, test drivers, threat +simulators, targets, blue weapons used as threat surrogates and kill +removal systems.

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation/index.html b/sites/oteguide/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation/index.html new file mode 100644 index 00000000..f78c00a5 --- /dev/null +++ b/sites/oteguide/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation/index.html @@ -0,0 +1,16 @@ +Acquisition Implications of Verification, Validation and Accreditation

Acquisition Implications of Verification, Validation and Accreditation

With the inception of agile acquisition, sprints, and rapid testing, it +is likely that there will be a unique acquisition approach for each +system under test. The AFOTEC OT&E Guide states: "There is no single +acquisition approach for a given type of system. The approach is +influenced by the urgency of need, the technology development +requirements, the amount of money allocated to the program, or any of a +variety of other influences."

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/1-7-Accreditation-Concepts/index.html b/sites/oteguide/accreditation_guide/1-7-Accreditation-Concepts/index.html new file mode 100644 index 00000000..7dad7b96 --- /dev/null +++ b/sites/oteguide/accreditation_guide/1-7-Accreditation-Concepts/index.html @@ -0,0 +1,21 @@ +Accreditation Concepts

Accreditation Concepts

Test teams should plan to accomplish the accreditation and publish the +accreditation report prior to test readiness review (TRR). AFOTEC will +be able to begin the test execution phase with confidence that the M&S +is credible. It may not always be possible to complete the accreditation +report prior to TRR but that should be the goal.

Accreditation is about characterizing risk. Specifically, it is about +ensuring that the risk of using a model and/or simulation to determine +and report SUT effectiveness/suitability in an OT&E final report is +acceptable. Keeping this fundamental principle in mind will help keep +accreditation efforts on track. Test teams are encouraged to focus the +accreditation effort and documentation describing the risks. The +accreditation authority will ultimately decide whether or not to accept +the risks.

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/1-8-Risk-Matrix:-Example/index.html b/sites/oteguide/accreditation_guide/1-8-Risk-Matrix:-Example/index.html new file mode 100644 index 00000000..71385e9e --- /dev/null +++ b/sites/oteguide/accreditation_guide/1-8-Risk-Matrix:-Example/index.html @@ -0,0 +1,43 @@ +Risk Matrix: Example

Risk Matrix: Example

The following excerpt is from the Accreditation Report for the Radar +Simulation Suite (RSS) used in the Cobra Judy Replacement Multi-Service +Operational Test and Evaluation (MOT&E), 12 Mar 14.

The test team assessed the impacts to OT and the probability of +occurrence using the Air Force operational risk management general +assessment practices and definitions presented in Table 5-9, in +accordance with the 'Risk Management Guide for DOD Acquisition,' 6th +edition, Aug 06.

For each identified risk, the test team has provided a narrative +discussion and identified major issues. The test team provided an +overall risk assessment for the use of RSS in OT." Table 5-9 defines the +severity of each risk ratings (low, low/medium, medium, medium/high, and +high). Table 5-10 identifies the assigned risk assessment by the test +team: Figure 5-5 shows the risk management rating scale (RMRS) with +green (low), yellow (medium) and red (high) ratings. "After rating each +primary risk, the test team populated the RMRS with the associated risk +number". "Risk 1 was identified as L/M impact and M/H probability of +occurrence.

Table 5-9. Risk Severity Definitions

Impact to OTDefinitionProbability of OccurrenceDefinition
LNoneLUnlikely
L/MNegligibleL/MSeldom
MModerateMOccasional
M/HCriticalM/HLikely
HCatastrophicHFrequent

Figure 5-5. Risk Management Rating Scale

+ + + image2 + +

AFOTEC should strive to publish the accreditation plan early in the test +program lifecycle (shortly after measures are defined). The +accreditation plan establishes acceptance criteria, to which the +validation plans and reports should respond. Publishing the +accreditation plan early ensures AFOTECs opportunity to influence the +scope and nature of subsequent V&V activities and products, and to enter +discussions early with the developer of the M&S capability. DOT&E +expects the TEMP to include details on the VV&A approach, or a reference +to such details IAW DOT&E memo, 14 Mar 16.

Known baseline. To the extent possible, the accreditation acceptance +criteria should be based upon comparing model output to a known +baseline. For example, for a threat, the known baseline may be the +Intelligence community assessment of threat behavior. For a target drone +aircraft the known baseline may be measured signature data of a foreign +aircraft. Strive to establish quantitative criteria whenever possible.

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/1-9-Previous-Accreditation/index.html b/sites/oteguide/accreditation_guide/1-9-Previous-Accreditation/index.html new file mode 100644 index 00000000..6a1a5fb8 --- /dev/null +++ b/sites/oteguide/accreditation_guide/1-9-Previous-Accreditation/index.html @@ -0,0 +1,37 @@ +Previous Accreditation

Previous Accreditation

There may be an opportunity to use M&S that has been accredited in the +past, either by AFOTEC or by another organization. For example, if +AFOTEC or another organization has used the intended M&S for similar +purposes, it may be possible to focus the accreditation effort on "delta +accreditation." In this case, the accreditation team will need to +articulate how the M&S has changed, if at all, since last accredited. In +addition, the team must illustrate how use of the previously accredited +model compares to the proposed use.

AFOTEC does not make blanket or class accreditations. However, if "delta +accreditation" is feasible or the upcoming test, a new accreditation +report is not required. Depending on the intended use of the M&S, the +accreditation effort may consist of a comprehensive new report or a +one-page memo for record. When beginning any accreditation effort, it is +best to examine what has been done in order to avoid potential +duplication of effort or unnecessary documentation and staffing. Consult +with HQ A-2/9 to help decide the best route to take. Table 2 describes +the AFOTEC offices that have a role in the Accreditation process as well +as the correlation (if any) to VV&A roles as outlined in AFI 16-1001, +and associated responsibilities.

Table 2. VV&A Roles and Documentation Responsibilities

OfficeAFI Role CorrelationResponsibilities
AFOTEC (typically the TD)Requiring AgencyEstablish the need for M&S for use in a particular program
AFOTEC Technical Advisor (CA)*Accreditation AuthorityApproves AFOTEC accreditation plans and reports
Det Technical Advisor (TA)Accreditation AgentReview and sign accreditation plans and reports prior to submission to CA
Det Commander*Accreditation AuthorityApproves and signs accreditation plans/reports originating from his/her Detachment
Det TDAccreditation Agent
  • Reviews/signs accreditation plans/reports documenting adequacy of test capabilities to support OT&E

  • Briefs M&S developer on Accreditation Plan and ensures V&V plans/reports meet Accreditation requirements identified in Accreditation Plan

  • Briefs the accreditation approach to A‑2/9 during the TR

  • Ensures that all test capabilities are accredited

  • Sends signed copies of accreditation plans and reports to A‑3 and HO for records management and archiving

Det AnalystAccreditation AgentAuthors, signs and executes accreditation plans and authors accreditation reports for all test capabilities
Operations Directorate (A‑3)None
  • Reviews accreditation plans/reports documenting adequacy of test capabilities to support OT&E

  • Validates test capability requirements

Intelligence, Analyses and Assessments Directorate (A‑2/9)None
  • Assists the TD with the accreditation process as directed in the program tasking order

  • Advises on VV&A policy and process

  • Post final accreditation plans/reports to AFOTEC‑SharePoint site.

  • Records the decision on whether accreditation is required or not in a memo for the Det/TD post ITD

  • Reviews accreditation plans/reports for technical adequacy and advises CA accordingly

  • Staffs plans/reports through HQ via SSS; tracks comments and revisions, obtains CA signature

  • Monitors AF and DoD VV&A policy and communicates policy changes within AFOTEC

Special Projects Division for NTTR (A‑8Z)None
  • Assists the TD as directed in the program tasking order

  • Maintains cognizance of accreditation activities associated with NTTR assets

  • Advises test team on the likelihood of successful accreditation for specific test capabilities

  • Maintains library of accreditation plans/reports associated with NTTR

A-5RNoneMonitors test capability through participation in AF and DoD investment processes ensuring V&V plans support accreditation, are fully funded, and are included in the project management plans
HONone
  • Receives copies of accreditation plans/reports from the TD

  • Maintains library of all AFOTEC accreditation plans/reports

  • Maintains a library of verification and validation reports for facilities AFOTEC commonly uses

V&V ManagerNoneN/A
V&V AgentNoneN/A
PM/DeveloperNoneN/A
*For the F-35 program and BMDS, the AFOTEC Commander (as a member of the F-35 Executive Committee) serves as the accreditation authority

Verification and validation are the responsibility of the M&S +developer/owner. Figure 1 illustrates an overview of the VV&A process, +including the roles/responsibilities associated with VV&A. The bold +vertical line indicates the distinction between the capability owner +(V&V manager & V&V agent) V&V) and the capability user (Accreditation +Agent & Accreditation Authority).

Figure 1. VV&A Overview

+ + + image3 + +

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/2-1-Accreditation-Process/index.html b/sites/oteguide/accreditation_guide/2-1-Accreditation-Process/index.html new file mode 100644 index 00000000..6f03163c --- /dev/null +++ b/sites/oteguide/accreditation_guide/2-1-Accreditation-Process/index.html @@ -0,0 +1,64 @@ +Accreditation Process

Accreditation Process

The Det will email unclassified accreditation plans/reports to the A-2/9 +workflow address: UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil . If the +plan/report is classified, contact the A-2/9 POC or workflow for +instructions. The A-2/9 POC will place accreditation plans/reports into +2-ltr coordination for 5 days and adjudicate all comments. Upon +completion, the A-2/9 POC will place accreditation plans/reports into CS +coordination for review and signature by the CA. The "AFOTEC OT&E Guide" +shows AFOTEC's accreditation process (Figure 2 below). Accreditation +activities begin during the OT&E Construct development with +identification of test capability requirements, followed by development +of an accreditation memo.

Figure 2. AFOTEC Accreditation Process

+ + + image4 + +

The memo from the Director, A‑2/9 to the detachment commander identifies +the test capability requirements, accreditation documentation +requirements, initial timelines, and relevant VV&A documents available. +Upon receipt of this memo, the TD (and designated test team members/with +HQ assistance) begins tracking VV&A resource expenditures including +manpower and dollars.

During each Test Concept Technical Review, the TD will discuss the test +capabilities to be used and how the accreditation will be accomplished +based on the guidelines for use of the capability. A‑2/9 advises whether +accreditation is required or not. Throughout test planning, the TD +should inform A‑2/9 on the accreditation approach during scheduled +technical reviews, including proposed level of effort, completion dates +and accreditation resource requirements. The information enables A‑2/9 +to ensure technical adequacy on the overall accreditation approach and +prevent unnecessary expenditure of resources. As the program progresses, +the test team should identify planned use of test capabilities and the +associated accreditation approach in ITD and test concept briefings.

The next step is an accreditation concept discussion, typically +conducted via VTC. This discussion is between the test team and A-2/9. +The purpose is to initiate dialogue and agree on assumptions and the +overall accreditation approach before initiating development of the +accreditation plan. The topics shown in Figure 5-8 help frame this +dialogue. After internal AFOTEC discussion it is a good idea to discuss +the accreditation concept with the DOT&E action officer, if DOT&E is +involved, to ensure there are no disconnects between AFOTEC and DOT&E +with respect to VV&A.

Following completion of the accreditation concept discussion the test +team initiates development of the accreditation plan(s). Many test +capabilities have existing validation and/or accreditation reports that +may be useful for current and future VV&A efforts. A‑8Z, A‑2/9 and the +History Office (HO) may have copies of previous VV&A documents. The +accreditation plan establishes the benchmark for all remaining V&V +activities. Per AFI 16-1001, "Acceptability criteria are the most +important content of the accreditation plan and should be presented as +minimum criteria for accreditation." The team should place priority on +developing meaningful accreditation acceptance criteria. The TD submits +the plan to A-2/9, who reviews and coordinates the plan and submits the +plan to CA for approval.

Once the plan is approved, the TD distributes the plan to M&S capability +owners so they can prepare V&V plans/reports that will produce data to +allow AFOTEC to determine whether or not the acceptance criteria have +been met. Following receipt of the V&V reports, the test team executes +the accreditation plan. This step primarily involves comparing the +results of the V&V to the acceptance criteria.

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/2-2-Test-Capability-Accreditation-Concept/index.html b/sites/oteguide/accreditation_guide/2-2-Test-Capability-Accreditation-Concept/index.html new file mode 100644 index 00000000..26435ac7 --- /dev/null +++ b/sites/oteguide/accreditation_guide/2-2-Test-Capability-Accreditation-Concept/index.html @@ -0,0 +1,38 @@ +Test Capability Accreditation Concept

Test Capability Accreditation Concept

Discussion Topics

  • Describe system under test and its CONOPS

  • Include threats, targets and/or situations likely to require M&S

    • Describe what must be simulated and why (much simulate moving +vehicle targets; insufficient quantity at test ranges, etc.
  • Explain why you selected a particular test capability

  • Identify measures that require test capability to rate

  • Describe the risks of using a specific test capability in terms of +the effect on rating specific measures of effectiveness (MOEs), +measures of performance (MOPs), and measures of suitability (MOSs).

  • What is the likelihood of drawing an incorrect conclusion on +effectiveness/suitability?

  • Explain how you will convince yourself the capability is acceptable +for use in a specific test

  • Identify accreditation criteria

  • Typically involves comparison of test capability performance to some +known or expected values

  • Explain your accreditation timing

  • What V&V information is available or missing?

  • What are the risks of accrediting before the start of OT&E versus +after?

Based upon review of the V&V reports, the test team produces an +accreditation report. The accreditation report summarizes the V&V report +findings and concludes with a recommendation to either: accredit, +accredit with limitations, or do not accredit the M&S. The typical +outcome will be accredit--accredit with limitations will be by +exception. The accreditation report should include a summary statement +that the M&S is accredited for a specific OT&E to address specific +MOEs/MOPs/MOSs. The test team submits the accreditation report to A-2/9 +for review and coordination and then A-2/9 submits the report to CA for +approval.

From a timing standpoint the team should strive to publish the +accreditation report prior to test readiness review (TRR). This ensures +AFOTEC leadership is aware of all risks associated with using M&S prior +to the use of the M&S. Sometimes it is not possible to publish the +accreditation report prior to TRR. In this case the TD should include +information in the TRR briefing characterizing the risk associated with +using M&S and any mitigating factors, and include information regarding +when the accreditation report will be published.

Next, the test team will use M&S as planned (e.g. execute the test), +consider lessons learned associated with the VV&A process, and document +those lessons learned in the OT&E final report.

Finally, A-2/9 reviews the lessons learned and considers adjustments to +the VV&A process as needed. A-2/9 ensures the accreditation +plans/reports are archived and submits any necessary metadata to the +appropriate agency.

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format/index.html b/sites/oteguide/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format/index.html new file mode 100644 index 00000000..176889ba --- /dev/null +++ b/sites/oteguide/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format/index.html @@ -0,0 +1,20 @@ +Accreditation Plan and Report Format

Accreditation Plan and Report Format

A sample format for accreditation plans and reports is located on the +AFOTEC SharePoint.

The format is based upon MIL‑STD‑3022, DoD Standard Practice +Documentation of VV&A for Models and Simulations. Accreditation +documentation need not be voluminous, but should provide sufficient +information to enable the accreditation authority to make the +accreditation decision. The selected format (determined collaboratively +by the test team and A-2/9) will depend on past use of the test +capability, the number of measures impacted, resources needed for +accreditation, the test schedule and other factors. If the plan or +report is distributed outside of AFOTEC, it needs to be properly marked +along with the appropriate distribution statement.

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/2-4-Accreditation-References-and-Resources/index.html b/sites/oteguide/accreditation_guide/2-4-Accreditation-References-and-Resources/index.html new file mode 100644 index 00000000..e7b8bd1b --- /dev/null +++ b/sites/oteguide/accreditation_guide/2-4-Accreditation-References-and-Resources/index.html @@ -0,0 +1,12 @@ +Accreditation References and Resources

Accreditation References and Resources

The following are organizations that the accreditation team can +reference for assistance in gathering pertinent accreditation +information.

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation/index.html b/sites/oteguide/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation/index.html new file mode 100644 index 00000000..c2535811 --- /dev/null +++ b/sites/oteguide/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation/index.html @@ -0,0 +1,24 @@ +Air Force Agency for Modeling and Simulation

Air Force Agency for Modeling and Simulation

The Air Force Agency for Modeling and Simulation (AFAMS) ( +http://www.afams.af.mil ) is a field operating agency of the Deputy +Chief of Staff for Operations, Plans and Requirements, Headquarters U.S. +Air Force. The Agency is located in Orlando\'s Central Florida Research +Park, with DoD, Joint, service, contractor, and educational +organizations focused on modeling and simulation (M&S). AFAMS\' mission +is to provide seamless integration of cross-functional Live Virtual +Constructive-Operational Training environments that allow warfighters to +maximize performance and decision making. AFAMS works closely with +Combatant Commands, Major Commands, the Air Force Reserve Command, the +Air National Guard, the Air Force Headquarters, Direct Reporting Units, +and Field Operating Agencies to provide the necessary development and +implementation standards for common access and interoperability within +the Live, Virtual and Constructive (LVC) Training domains for efficient +and secure global operations.

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office/index.html b/sites/oteguide/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office/index.html new file mode 100644 index 00000000..997047f2 --- /dev/null +++ b/sites/oteguide/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office/index.html @@ -0,0 +1,28 @@ +Modeling and Simulation Coordination Office

Modeling and Simulation Coordination Office

The Department of Defense (DoD) Modeling and Simulation Coordination +Office (M&SCO) ( http://www.msco.mil) is the focal point for +coordinating all matters regarding modeling and simulation across the +DoD for the Undersecretary of Defense (Acquisition, Technology and +Logistics) (USD(AT&L)) . M&SCO recommends +policies, plans, and programs to the USD(AT&L) that supports the M&S +Strategic Vision and DoD priorities. Among other documents, MSCO +maintains the DoD VV&A Recommended Practices Guide.

AFOTEC provides the M&SCO a descriptive summary and metadata for all +accredited models or simulations that can potentially be reused by other +programs.

On 18 March 2020, M&SCO released a new M&S Guidebook. The guidebook is a +compendium of short articles that capture key concepts in the M&S realm. +According to their website, the intent of the guidebook is to "provide +DoD M&S practitioners an information resource to leverage existing +knowledge, past experience, and available tools."

Organizations supported by M&S need visibility into the tools, data and +services that meet their requirements. The DOD M&S steering committee +has established a web based search capability to provide a card catalog +level of detail about M&S tools, data and services. The catalog is +operated by the DMSC. Register to view this catalog here: +MSCatalogHelpDesk@mscatalog.msco.mil

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/2-7-Best-Practices/index.html b/sites/oteguide/accreditation_guide/2-7-Best-Practices/index.html new file mode 100644 index 00000000..5a6222f0 --- /dev/null +++ b/sites/oteguide/accreditation_guide/2-7-Best-Practices/index.html @@ -0,0 +1,18 @@ +Best Practices

Best Practices

  • It is OK to conclude that the test capability is inadequate or to +recommend that the test capability not be accredited for use; +include justification and documentation. Establish acceptance +criteria in terms of comparison to known baseline. Can recommend +Accredit, accredit w/ limitations, don't accredit

  • Computer-based constructive models must be approved for use on Air +Force networks; start early

  • Ensure that a clear link exists between test capability use and test +limitations

  • Convince the Accreditation Authority the level of risk is +acceptable. Answer the question: "To what extent is this +representation adequate for purposes of a given test?"

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/2-8-Summary/index.html b/sites/oteguide/accreditation_guide/2-8-Summary/index.html new file mode 100644 index 00000000..3756421e --- /dev/null +++ b/sites/oteguide/accreditation_guide/2-8-Summary/index.html @@ -0,0 +1,28 @@ +Summary

Summary

Models and simulations will not be 100% accurate and there is risk +associated with drawing inferences about the models and their +applicability to actual systems. There is potential to draw incorrect +conclusions about SUT performance based on use of a particular test +capability. Remember AFOTECs credibility is at stake with every report. +Ensuring due diligence will result in a robust and valid accreditation +process. Inherently, AFOTEC assumes some degree of risk when using test +capabilities to represent an employment environment to determine SUT +capabilities. The purpose of accreditation is to assess and document +that risk.

Remember that acceptability criteria are the most important concepts of +Accreditation. Make sure to consider the following: How confident are +you that the proposed test capability is acceptable for use during the +OT? List the pros and cons. What acceptability criteria did you +establish? What research/analysis did you perform? How did you reach +your conclusions? The accreditation plan and report configuration is at +the discretion of the test team. It is acceptable to have one plan and +multiple reports, or multiple plans and multiple reports. The AFOTEC +SharePoint site contains current accreditation information and +templates, including the DoD VV&A Recommended Practices Guide.

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/2-9-References-and-Resources/index.html b/sites/oteguide/accreditation_guide/2-9-References-and-Resources/index.html new file mode 100644 index 00000000..272979be --- /dev/null +++ b/sites/oteguide/accreditation_guide/2-9-References-and-Resources/index.html @@ -0,0 +1,67 @@ +References and Resources

References and Resources

AFOTEC Accreditation Statement. "AFOTEC accredits [model] for use +in [SUT] OT&E to address the following +MOEs:_______________"

Example "Delta Accreditation" Memo

Documents from Recommended Practices Guide

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/3-1-Governance/index.html b/sites/oteguide/accreditation_guide/3-1-Governance/index.html new file mode 100644 index 00000000..7eec2437 --- /dev/null +++ b/sites/oteguide/accreditation_guide/3-1-Governance/index.html @@ -0,0 +1,24 @@ +Governance

Governance

DoDI 5000.02, 7 Jan 15: "Every distinct use of a model or simulation in +support of an operational evaluation will be accredited by an OTA, and, +for programs under DOT&E Oversight, its use for the operational +evaluation will be approved by DOT&E."

DoDI 5000.61, DoD Modeling and Simulation (M&S) Verification, +Validation, and Accreditation (VV&A) , 9 Dec 09, para 4.a-b: "Models, +simulations, and associated data used to support DoD processes, +products, and decisions shall undergo verification and validation (V&V) +throughout their lifecycles. Models, simulations, and associated data +used to support DoD processes, products, and decisions shall be +accredited for an intended use."

AFI 16-1001, Verification, Validation and Accreditation (VV&A) , 29 +Apr 2020, para 2.3: \"Air Force M&S applications will be accredited for +their intended purpose when supporting major DoD decision-making +organizations or processes, joint training, and joint exercises. All +executed V&V activities will support the model acceptance and +accreditation requirements defined by the accreditation authority.\"

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/3-2-Points-of-Contact/index.html b/sites/oteguide/accreditation_guide/3-2-Points-of-Contact/index.html new file mode 100644 index 00000000..8d654c18 --- /dev/null +++ b/sites/oteguide/accreditation_guide/3-2-Points-of-Contact/index.html @@ -0,0 +1,12 @@ +Points of Contact

Points of Contact

\ No newline at end of file diff --git a/sites/oteguide/accreditation_guide/index.html b/sites/oteguide/accreditation_guide/index.html new file mode 100644 index 00000000..198f5671 --- /dev/null +++ b/sites/oteguide/accreditation_guide/index.html @@ -0,0 +1,10 @@ +Accreditation Guide

Accreditation Guide

08 December 2020

Originating Office: AFOTEC A-2/9

\ No newline at end of file diff --git a/sites/oteguide/acronyms/index.html b/sites/oteguide/acronyms/index.html index 07d10f4f..d18001d5 100644 --- a/sites/oteguide/acronyms/index.html +++ b/sites/oteguide/acronyms/index.html @@ -1,4 +1,4 @@ -Acronyms

Acronyms

If you're just searching for the meaning of an ancroym, here's the place.

2Ltr: 2-Letter

Blk: Block

Det: Detachment

Stan/Eval: Standardization and Evaluation

3DELRR: Three Dimensional Expeditionary Long Range Radar

3PS: Third Party Source

AAS: Advisory and Assistance Services

A3M: Air Force and Army Anti-Jam Modem

AA: Adversarial Assessment

AAIP: Aircraft Availability Improvement Program

AAR: After-Action Review / Report

AARGM: Advanced Anti-Radiation Guided Missile

AARI: Air-to-air Range Infrastructure

ABSD: Airborne Strategic Deterrence

AC: Alternating Current

ACAT: Acquisition Category

ACC: Air Combat Command

ACCM: Alternative Compensatory Control Measure

ACE: Acquisition Center of Excellence

ACES: Automated Civil Engineer System

ACPAT: Air Force C4I Program Assessment Tool

ACPINS: Automated Computer Program Identification Number System

ACPO: Acquisition Chief Process Office

ACTD: Advanced Concept Technology Demonstration

ACWP: Actual Cost Work Performed

ADM: Acquisition Decision Memorandum

ADS: Advanced Distributed Simulation

AEC: United States Army Evaluation Center

AECO: Advance Engineering Change Order

AECS: Advanced Entry Control System OR AFOTEC Electronic Coordination System

AEF: Air and Space Expeditionary Force

AEHF: Advanced Extremely High Frequency

AEP: Accrued Expenditures Paid

AESO: Advance Engineering Supplemental Order

AETC: Air Education and Training Command

AETF: Army Evaluation Task Force

AEU: Accrued Expenditures Unpaid

AF GCIC: Air Force Global Cyberspace Integration Center

AFMOASP: Air Force Management and Oversight of Acquisition Services Process

AF: (US) Air Force

AF/A10: Assistant Chief of Staff for Strategic Deterrence and Nuclear Integration

AF/A2: Deputy Chief of Staff +Acronyms

Acronyms

If you're just searching for the meaning of an ancroym, here's the place.

2Ltr: 2-Letter

Blk: Block

Det: Detachment

Stan/Eval: Standardization and Evaluation

3DELRR: Three Dimensional Expeditionary Long Range Radar

3PS: Third Party Source

AAS: Advisory and Assistance Services

A3M: Air Force and Army Anti-Jam Modem

AA: Adversarial Assessment

AAIP: Aircraft Availability Improvement Program

AAR: After-Action Review / Report

AARGM: Advanced Anti-Radiation Guided Missile

AARI: Air-to-air Range Infrastructure

ABSD: Airborne Strategic Deterrence

AC: Alternating Current

ACAT: Acquisition Category

ACC: Air Combat Command

ACCM: Alternative Compensatory Control Measure

ACE: Acquisition Center of Excellence

ACES: Automated Civil Engineer System

ACPAT: Air Force C4I Program Assessment Tool

ACPINS: Automated Computer Program Identification Number System

ACPO: Acquisition Chief Process Office

ACTD: Advanced Concept Technology Demonstration

ACWP: Actual Cost Work Performed

ADM: Acquisition Decision Memorandum

ADS: Advanced Distributed Simulation

AEC: United States Army Evaluation Center

AECO: Advance Engineering Change Order

AECS: Advanced Entry Control System OR AFOTEC Electronic Coordination System

AEF: Air and Space Expeditionary Force

AEHF: Advanced Extremely High Frequency

AEP: Accrued Expenditures Paid

AESO: Advance Engineering Supplemental Order

AETC: Air Education and Training Command

AETF: Army Evaluation Task Force

AEU: Accrued Expenditures Unpaid

AF GCIC: Air Force Global Cyberspace Integration Center

AFMOASP: Air Force Management and Oversight of Acquisition Services Process

AF: (US) Air Force

AF/A10: Assistant Chief of Staff for Strategic Deterrence and Nuclear Integration

AF/A2: Deputy Chief of Staff Intelligence Surveillance and Reconnaissance

AF/A3/5: Deputy Chief of Staff Operations @@ -100,7 +100,7 @@ Special Access Program Coordinator

M&S: Modeling and Simulation

M&S CO: Modeling and Simulation Coordination Office

MAAP: Master Air Attack Plan

MAAPTK: Master Air Attack Planning Toolkit

MAC: Mission Assurance Category

MACH: Modular Air Crew Helmet

MADL: Multifunction Advanced Data Link

MAF-DRC: Mobility Air Forces-Dynamic Retasking Capability

MAFPS: Mobility Air Force Automated Flight Planning Service

MAIS: Major Automated Information System

MAJCOM: Major Command

MALD-J: Miniature Air Launched Decoy-Jammer

MANPAD: Man Portable Air Defense System

MANPRINT: Manpower and Personnel Integration

MAnTSS: Modular Analysis and Test Support System

MAR: Monthly Acquisition Report

MAV: Maverick

MBITR: Multiband Inter/Intra Team Radio

MBTD: Mission Based Test Design

MC: Mission Capable

MCF: Mission Critical Functions

MCOTEA: Marine Corps Operational Test and Evaluation Activity

MCR: Message Completion Rate

MD: Mission Directive

MDA: Milestone Decision Authority OR Missile Defense Agency

MDAP: Major Defense Acquisition Program

MDD: Maintenance Data Documentation OR Material Development Decision

MDF: Mission Data File

MDS: Mission Design Series

MDT: Mean Down Time

ME/SE: Maintenance Engineering/Sustaining Engineering

MECSIP: Mechanical Subsystems Integrity Plan

MEDALS: Military Engineering Data Asset Locator System

MEFL: Mission Essential Functions List

MEO: Medium Earth Orbit

MER: Manpower Estimate Report

MESL: Minimum Essential Subsystems List

MEV: Military Equipment Valuation

MFOQA: Military Flight Operations Quality Assurance

MFP: Major Force Program OR Materiel Fielding Plan

MFR: Memorandum for Record

MFT: Multi-Functional Team

MGRS: Military Grid Referencing System

MGUE Inc 2 HH: Military GPS User Equipment Hand Held

MGUE: Military GPS User Equipment

MHS: Modular Handgun System

MHz: Megahertz

MIL-DTL:Military Detail (Specification)

MIL-HDBK:Military Handbook

MIL-PRF:Military Performance (Specification)

MIL-STD:Military Standard

MIP: Materiel Improvement Program OR Military Intelligence Program

MIPR: Military Interdepartmental Purchase Request

MIPRB: Material Improvement Program Review Board

MLS: Multiple Levels of Security

MMT: Munitions Missiles -and Target

MNS: Mission Needs Statement

MOA: Memorandum of Agreement

MOASP: Management and Oversight of Acquisition Services Process

MOE: Measure of Effectiveness

MOEs: Measures of Effectiveness

MOP: Measure of Performance

MOPP: Mission Oriented Protective Posture

MORV: Mission-Oriented Response Variables

MOS: Measure of Suitability OR Military Occupational Specialty

MOSA: Modular Open Systems Approach

MOT&E: Multiservice Operational Test and Evaluation

MOU: Memorandum of Understanding

MP: Mission Profile

MPA: Manpower Authorization

MPE: Mission Planning Element

MPGPA: Multipart GPS Pulse-per-Second Adapter

MPS: Master Program Schedule OR Mission Planning System

MPTO: Methods and Procedures Technical Order

MRA: Manufacturing Readiness Assessment

MRB: Mission Requirements Board

MRDS: Man-Portable Radiological Detection System

MRL: Manufacturing Readiness Level

MROi: Air Force Depot Maintenance +and Target

MNS: Mission Needs Statement

MOA: Memorandum of Agreement

MOASP: Management and Oversight of Acquisition Services Process

MOE: Measure of Effectiveness

MOEs: Measures of Effectiveness

MOP: Measure of Performance

MOPP: Mission Oriented Protective Posture

MORV: Mission-Oriented Response Variables

MOS: Measure of Suitability

MOSA: Modular Open Systems Approach

MOT&E: Multiservice Operational Test and Evaluation

MOU: Memorandum of Understanding

MP: Mission Profile

MPA: Manpower Authorization

MPE: Mission Planning Element

MPGPA: Multipart GPS Pulse-per-Second Adapter

MPS: Master Program Schedule OR Mission Planning System

MPTO: Methods and Procedures Technical Order

MRA: Manufacturing Readiness Assessment

MRB: Mission Requirements Board

MRDS: Man-Portable Radiological Detection System

MRL: Manufacturing Readiness Level

MROi: Air Force Depot Maintenance Repair and Overhaul Initiative

MRP: Munitions Requirements Process

MRR: Materiel Release Review

MRRB: Maintenance Requirement Review Board

MRSP: Mobility Readiness Spares Package

MRTFB: Major Range and Test Facility Base

MS: Milestone

MSA: Materiel Solution Analysis

MSIAC: Modeling and Simulation Information Analysis Center

MSL: Mean Sea Level

MSSP: Modeling and Simulation Support Plan

MTBEFF: Mean Time Between Essential Function Failures

MTTR: Mean Time To Repair

MUA: Military Utility Assessment

MUOS: Mobile User Objective System

MW: Measures Workshop

NAOC: National Airborne Operations Center

NASIC: National Air and Space Intelligence Center

NATO: North Atlantic Treaty Organization

NAVPLAN TPC: Navigation Plan Tactical Pilotage Charts

NBC: Nuclear Biological and Chemical

NC2-ESI: Nuclear Command and Control-Extremely Sensitive Information

NC3: Nuclear Command @@ -149,7 +149,7 @@ Designation and Hand-Off System

TLE: Target Location Error

TM: Technical Manual OR Telemetry OR Test Manager

TMCR: Technical Manual Contract Requirement

TMDE: Test Measurement Diagnostic Equipment

TMIPJ: Theater Medical Information Program-Joint

TMLA: Triple Missile Launcher Adapter

TMRR: Technology Maturation & Risk Reduction (phase)

TMSS: Technical Manual Specifications and Standards

TMT: Task Management Tool

TNMCM: Total Not Mission Capable-Maintenance

TNMCS: Total Not Mission Capable-Supply

TO: Tasking Order OR Technical Order

TOA: Total Obligation Authority

TOAC: Technical Order Advisory Council

TOC: Tactical Operation Center OR Total Ownership Cost OR Table of Contents

TODO: Technical Order Distribution Office

TOMA: Technical Order Management Agency

TPCF: Test Program Case File

TPM: Technical Performance Measure OR Test Program Management

TPP: Technology Protection Plan

TPS: Test Program Set

TPT: Training Planning Team

TPWG: Test Plan Working Group

TR: Technical Review

TRA: Technology Readiness Assessment

TRADOC: Training and Doctrine Command (US Army)

TRB: Technical Review Board

TRD: Technical Requirements Document

TRL: Technology Readiness Level

TRM: Technology Reference Model OR Test Resource Manager

TRMC: Test Resource Management Center

TRP: Test Resource Plan

TRR: Test Readiness Review

TS: Test Squadron OR Top Secret

TSN: Trusted Systems & Networks

TSP: Test Support Plan OR Transfer Support Plan OR Transition Support Plan

TS-PGM: Training System Product Group Manager

TSPI: Time / Space / Position Information

TSRA: Training System Requirements Analysis

TSWG: Threat Systems Working Group

TTCP: The Technology Cooperation Program

TTP: Tactics Techniques and Procedures OR Technology Transition Plan

TV: Technical View

TW: Test Wing

UAI: Universal Armament

UAS: Unmanned Aerial Systems

UAV: Unmanned Aerial Vehicle

UC: Unified Capabilities

UCA: Undefinitized Contract Action

UCC: Unified Combatant Commander

UHF: Ultra-High Frequency

UID: Unique Identification number

UIF: Unfavorable Information File

UII: Unique Item Identifier

UIPE: Uniform Integrated Protection Ensemble

UJTL: Universal Joint Task List

ULB: Underwater Locator Beacon

ULO: Unliquidated Obligation

UON: Urgent Operational Need

UOTT: US Operational Test Team

UP: Unified Platform

URA: User Representative Agency

URL: Uniform Resource Locator

URN: Unit Reference Number

USAF: United States Air Force

USAFWC: United States Air Force Warfare Center

USB: Universal Serial Bus

USC: United States Code

USD: Undersecretary of Defense

USecAF: Under Secretary of the Air Force

USMC: United States Marine Corps

USSF: United States Space Force

USSOCOM: U.S. Special Operations Command

UTC: Coordinated Universal Time

UTTR: Utah Test and Training Range

V&V: Verification and Validation

VCJCS: Vice Chairman of the Joint Chiefs of Staff

VCSAF: Vice Chief of Staff of the United States Air Force

VCSO: Vice Chief of Space Operations

VE: Value Engineering

VECP: Value Engineering Change Proposal

VEP: Value Engineering Proposal

VHF: Very High Frequency

VIDOC: Visual Information Documentation

VIM: Visual Information Manager

VMC: Visual Meteorological Conditions

VML: Vulnerable to Move List

VMP: Vulnerability Management Process

VOLT: Validated Online Lifecycle Threat

VPV: Virtual Prime Vendor

VSP: Verification Status Page

VSTAR: Virtual System Threat Assessment Report

VTC: Video Teleconference

VV&A: Verification -Validation and Accreditation

WAS: Wide Area Surveillance

WAWF: Wide Area Workflow

WBS: Work Breakdown Schedule

WCF: Working Capital Fund

WIPT: WorkingLevel Integrated Product Team

WIT: Watch Item Tracking

WMA: Warfighting Mission Area

WMD: weapons of mass destruction

WRAP: Warfighter Rapid Acquisition Process

WS3 SLEP: Weapons Storage and Security System Service Life Extension Program

WSEP: Weapon System Evaluation Program

WSER: Weapon System Enterprise Reviews

WSF-EO/IR: Weather Satellite Follow-on Electro-Optical /Infra-Red

WSF-M: Weather Satellite Follow-on Microwave

WSI: Weapon System Integration OR Weapon System Integrity

WSIG: Weapon System Integrity Guide

WSIP: Weapon System Integrity Program

WSMR: White Sands Missile Range

WSSP: Weapons System Support Program

WX: Weather

XDR: Extended Data Rate

YTD: Year to Date

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS/index.html b/sites/oteguide/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS/index.html new file mode 100644 index 00000000..237fa010 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS/index.html @@ -0,0 +1,37 @@ +ELEMENTS OF THE TEST PLANNING PROCESS

ELEMENTS OF THE TEST PLANNING PROCESS

Critical Operational Issues and Operations

The AFOTEC process begins with a thorough understanding of the missions +that the SUT is expected to enable or support; the AFOTEC OT&E Guide +provides an overview of this process. Once the mission is defined, the +core team identifies the COI and subordinate operations. Operations are the distinct activities or +processes that occur within a COI and are the focus of test design. Each +COI will have at least one operation.

Response Variables

Each operation under a COI shall have at least one Mission Oriented +Response Variable (MORV). A MORV is an indicator that a system under +test can successfully accomplish its mission in the operational +environment. MORVs are the dependent variables that guide the initial +test design (ITD) process. Ideally, a MORV should be quantitative +1 . If a MORV is qualitative +2 an analyst should develop one or more +continuous response variables (measures) to complement it. While a +qualitative MORV may be a satisfactory indicator of mission success, it +might also require considerably more testing and resources than a +quantitative MORV. In statistical terms, for a given test size, the +population parameter 3 +estimates 4 for a continuous +response have less variability than estimates for the population +parameter for a binary response. Therefore tests using binary MORVs must +have a significantly larger sample 5 size than tests using continuous MORVs; i.e., more runs +are required to achieve equivalent statistical quality and precision of +the parameter estimates. Thus qualitative MORVs should be used with +caution.

Ideally, a MORV should be written as a measure (see the Measures Guide +for further guidance on writing measures). However, it is not necessary +that a measure threshold be identified for a MORV. If a MORV becomes a +measure during the measures workshop, the appropriate detail is then +added.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization/index.html b/sites/oteguide/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization/index.html new file mode 100644 index 00000000..b62ecede --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization/index.html @@ -0,0 +1,82 @@ +Factors, Levels, and Prioritization

Factors, Levels, and Prioritization

A key event in the AFOTEC process is the initial test design (ITD) +meeting. The following organizations send representatives to this +week-long event: AFOTEC headquarters; the detachment conducting the +operational test; Director, Operational Test and Evaluation (DOT&E); the +Institute for Defense Analysis (IDA); the program office (PO); the +developmental test organization; and subject matter experts from the +user community.

An ITD has several phases. In the first phase the COIs, operations, and +MORVs are refined and vetted. In the second phase the ITD participants +develop a list of factors 6 and +levels 7 (F&L) that apply to each +MORV under an operation. Factors are the independent variables that +define the battlespace---with a range of values called levels---that may +affect a MORV when the factor's level is changed.

The AFOTEC Operational Test & Evaluation (OT&E) Guide has several +examples of desirable factor characteristics that should be considered +during the test design process. There are attributes of the factors +(quantitative data type, qualitative data type, number of levels, etc.) +which will significantly affect the size and quality of the test design. +These attributes should be considered by the analyst as they facilitate +the F&L discussion during the ITD process.

In addition to the characteristics and examples in the AFOTEC OT&E +Guide, the facilitator should consider the following:

  • It is a best practice to use quantitative factors with numeric +values for levels (e.g., Altitude: 10,000 ft and 30,000 ft) instead +of categorical factor levels (e.g., Altitude: Low and High).

  • Factor levels must be mutually exclusive, meaning that two levels of +the same factor describe conditions that cannot simultaneously +occur.

In phase three, the ITD participants determine two things: the magnitude +of a factor's impact on each MORV, and the likelihood of each factor +level occurring in the operational environment. Based on the combination +of a factor's impact and the likelihood of occurrence for each of its +levels, the test team chooses one of four methods for incorporating that +factor in the test design.

  1. Vary -- The factor is deliberately manipulated during the test

  2. Fix -- The factor level is held constant during the test

  3. Log -- During a test run, the level of this factor is recorded +as an observation

  4. Demo -- The level will be incorporated into a test run that is +executed and analyzed separately from the design incorporating the +varied factors

Choosing one of the four methods for each factor is referred to as +factor management. Figure 1 gives general guidance on which of the four +management methods to select for a factor level given a combination of +the factor's magnitude of impact and the likelihood of encountering the +factor level.

Figure 1. Factor Management Guidance

+ + + image3 + +

The test team should keep in mind that the factor level likelihood +should be determined in the context of the system conducting its +mission, not the likelihood the level occurs in general. For example, a +factor level related to a nuclear weapon system may be very unlikely in +peacetime, but may be very likely in the context of a nuclear weapon +employment. The latter is the likelihood that should be documented.

It is important to remember that even if a factor's levels occur in +unequal proportions in the operational environment, the frequency that +the levels occur in the test design may not coincide with those +proportions. Factor levels that occur disproportionally frequently (or +infrequently) in the test design could create an unrepresentative sample +of the system's overall performance across a typical set of operational +conditions. Consequently, the test design could cause an overly +pessimistic or optimistic assessment of the SUT.

Test Design Workbook

The major product from an ITD that summarizes the test planning elements +and F&Ls is the Test Design Workbook (TDW). Figure 2 shows the F&L tab +for COI 1 from the TDW for the X-100 Block Upgrade 1.1 (X-100 is a +fictitious program). COI 1, Does X-100 1.1 support Airland operations +, is shown at the top. This COI had three operations: Takeoff & +Departure, Enroute, and Arrival . Operation 1, Takeoff & Departure +, is shown underneath COI 1. The MORV for Operation 1 is Delta Time +between Planned and Actual Take-Off Time .

The test team developed a list of 23 factors for Operation 1 at the ITD. +However, only two will be strategically controlled (varied) during the +operational test. The other factors will either have their levels +demonstrated (demo), fixed during the test runs +8, or logged. Typically factors will +be logged because the levels cannot be controlled. However, for some +factors that are controllable but judged to be inconsequential, the +analyst may choose to log the levels in case the factors are actually +significant.

Four of 23 factors are shown: two factors to be varied and two factors +that cannot be controlled (which will be logged.) In the columns under +prioritization, the test team noted the magnitude of impact of the +factor, and the likelihood of encountering each factor level.

Figure 2. F&L Tab of TDW

Accurately selecting and prioritizing factors, levels, and their impact +on the system's MORVs is extremely important to ensure the test design +selected will achieve the test goal.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST/index.html b/sites/oteguide/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST/index.html new file mode 100644 index 00000000..bf4c33e1 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST/index.html @@ -0,0 +1,20 @@ +GOALS AND TYPES OF TEST

GOALS AND TYPES OF TEST

Before selecting the test design, the goal of the test must be +established. The goal not only determines how the test is designed and +executed but how it is reported as well. Within AFOTEC, there are +generally three goals of a test:

  • characterize system performance

  • compare system performance to a requirement or to another system

  • identify problems with the system

A test program may include up to all three test design goals. Generally, +each goal will have its own collection of test events based on one of +the design types outlined later in this guide. The above list states the +common goals in AFOTEC testing, but it is not all-inclusive. If a test +team has a different goal for their operational test, they should +provide an explanation including the unique nature of the desired test +goal and how it affects the design, execution, and reporting of the +test.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/1-6-Characterize/index.html b/sites/oteguide/analyst_test_design_guide/1-6-Characterize/index.html new file mode 100644 index 00000000..4391de3c --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/1-6-Characterize/index.html @@ -0,0 +1,24 @@ +Characterize

Characterize

When characterizing a system, the test goal is to analyze the system's +measures across the operational conditions (battlespace) defined by the +factors and levels. In addition, the test team quantifies the +effect 9 that changing factor +levels (and combinations of factor levels) have on the measures. To +accomplish this test teams use test designs that allow the estimation of +the factors' main effects 10 +and the factor interactions 11 +.

Designs used to characterize the system vary the levels of multiple +factors simultaneously with the intent of testing and reporting the +performance of a system under different operational conditions. They +also enable an analyst to determine which factors are most influential +on system performance. The data produced by these designs can be used in +future testing and for the development of operational Tactics, +Techniques and Procedures.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/1-7-Compare/index.html b/sites/oteguide/analyst_test_design_guide/1-7-Compare/index.html new file mode 100644 index 00000000..686aad46 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/1-7-Compare/index.html @@ -0,0 +1,13 @@ +Compare

Compare

When the goal of a test is to compare, the test team gathers data on a +system and compares it to data from another system, to a requirement +threshold, or to some other criterion. System comparisons do not provide +information about the system's performance across the battlespace.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/1-8-Problem-Identification/index.html b/sites/oteguide/analyst_test_design_guide/1-8-Problem-Identification/index.html new file mode 100644 index 00000000..b6538708 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/1-8-Problem-Identification/index.html @@ -0,0 +1,22 @@ +Problem Identification

Problem Identification

When one of the test goals is problem-identification, the test team +attempts to determine whether a "success" or "failure" occurs at one or +more factor level combinations that define the battlespace. One approach +is to use combinatorial designs; these designs efficiently combine +factor levels so that problems caused by specific factor level +combinations can be identified with less resources than designs used for +system characterization. However, combinatorial designs do not generally +provide data that can be analyzed with statistical modeling (system +characterization.)

Another approach is to demonstrate (demo) strategically chosen (and +usually infrequently occurring) factor level combinations. The data from +these demo runs are analyzed separately from the data associated with +test runs used to characterize the system performance. The analysis +essentially determines if a failure occurred during the demo.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS/index.html b/sites/oteguide/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS/index.html new file mode 100644 index 00000000..88aae2d4 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS/index.html @@ -0,0 +1,22 @@ +TYPES OF TEST DESIGNS

TYPES OF TEST DESIGNS

Choosing the most appropriate test design is a combination of science +and art. The choice requires expertise on the SUT, the operational +mission it supports, and DOE principles . Each +of the designs in this section has strengths and weaknesses depending on +the test goal and the nature of the SUT.

An AFOTEC test program may use a combination of the designs presented in +this section. It is typical to use a separate test design for each +operation under a COI, as factors and levels are often different between +operations. Some MORVs may even require a separate test design.

Test designs have associated quality indicators; within AFOTEC these +indicators are referred to as measures of merit. Measures of merit +provide a basis for comparison when choosing between multiple designs. +Also, measures of merit are used as evidence that a test design meets +the AFOTEC standards for technical adequacy. The Test Design Measures of Merit section of this guide presents a +more detailed explanation of the measures most often used at AFOTEC.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/2-1-Factorials/index.html b/sites/oteguide/analyst_test_design_guide/2-1-Factorials/index.html new file mode 100644 index 00000000..bc8f1dfe --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/2-1-Factorials/index.html @@ -0,0 +1,310 @@ +Factorials

Factorials

A factorial design 12 is a list +of test runs in which multiple factors are varied simultaneously from +run to run. This list of runs is called a test event matrix (TEM). The +special structure of the factor level combinations in the TEM enables +the tester to estimate the main factor effects and interactions between +factors. The following sections discuss two types of factorial designs: +full factorials and fractional factorials.

Full Factorial

A full factorial is a test design that includes every possible +combination of the levels across all factors. Full factorial designs +have the following desirable properties:

  • Every factor level occurs equally often in the test matrix. For +example, if a factor has 4 levels and there are 16 test runs, each +factor level will occur in 4 runs. This property is related to +balance 13 , and it +ensures that factor levels do not have a disproportionate influence +on the analytical results.

  • The design includes every possible factor level combination in the +TEM. This ensures that system performance can be analyzed over the +entire battlespace and we can identify factor level combinations +that lead to exceptionally negative or positive performance.

  • The effects (main effects and all interactions) are completely +uncorrelated in the TEM. This means the estimation of each effect is +not biased (influenced) by other main effects and interactions.

Full factorials are orthogonal 14 , balanced, and easy to construct with or without +software. Since every possible factor level combination must be present +in a full factorial, these designs are not applicable to test scenarios +with disallowed combinations 15 +of factors.

Use the following process to construct a full factorial design in JMP +13. The example shown in figure 3 a/b is for the X-100 Block Upgrade 1.1 +program.

Creating Full Factorial Designs in JMP 13:

  1. From the DOE menu, select Classical , then select Full +Factorial Design (figure 3a)

  2. Specify the Factors and levels. In the Factors section, add the +continuous and categorical factors using the drop down menu. Specify +the number of levels for each factor. The factors and levels can be +given appropriate names. Figure 3b shows the input for the X-100 BU +1 example.

  3. Click Continue when all of the factors and levels have been +entered.

    Figure 3a. Creating a Full Factorial in JMP Figure 3b. Enter the Factors and Levels

    + + + image5 + + + + + image6 + +

  4. Specify your Run Order ; JMP can output your design runs in +random order, or sorted from left to right (or right to left) by +factor level. The number of runs is the product of the number of +levels for each factor---in this example the number of runs is +3x4x4x3=144.

  5. Choose the number of center points 16 (only applicable when using continuous factors).

  6. Choose the number of replicates . The number of replicates is +the number of times you want the original full factorial design +repeated. Thus 1 replicate implies 2 copies of the full factorial. +Note that when reporting the number of replicates in a test design +worksheet (TDW), the AFOTEC convention is to state the number of +replicates as the number of copies; thus, on a TDW, 2 replicates +implies 2 copies.

  7. Click Make Table (figure 4a)

  8. JMP outputs a new design table (figure 4b)

    Figure 4a. Output Options Figure 4b. The Design Table + + + + image7 + + + + + image8 + +

The main weakness of a full factorial design is that the run size grows +rapidly with the addition of factors. The number of runs in a full +factorial design is equal to the product of the number of levels of each +factor in the design. In the X-100 BU 1.1 example, if we added just one +additional 2‑level factor, the number of runs in the design would double +from 3x4x4x3=144 runs to 288 runs! Because the number of runs increases +so rapidly, a full factorial design is infeasible for many test programs +unless there are only a small number of varied factors.

Rather than reducing the number of varied factors in order to enable the +use of a full factorial design, we recommend using one of the other +design types that are discussed in the subsequent sections. This +recommendation is rooted in the concept that AFOTEC tests should also be +operationally sufficient as well as technically adequate. A test is +operationally sufficient if it provides both the decision maker and the +warfighter with results drawn from test events executed across a +sufficiently broad set of operational conditions.

Fractional Factorial

A fractional factorial design is a strategically selected fraction +(typically ½ or ¼) of the runs in a full factorial design. These designs +have many of the same advantageous characteristics of a full factorial. +Depending on the degree of fractionation, fractional factorials can +yield the same information about main effects and two-factor +interactions (2FI) with fewer test runs. They are easy to construct, +orthogonal, balanced, and are an economical alternative to full +factorials.

As an example, suppose the X-100 BU 1.1 program chose to vary four +two-level factors, as shown in figure 5.

Figure 5. Sample of F&Ls for X-100 BU 1.1

+ + + image9 + +

The full factorial test design matrix would look like the design in +figure 6a. However, if test resources were not available to execute 16 +test runs, a fractional factorial design could be used to execute the +test in 8 runs---a ½ fraction of the original full factorial. The test +design matrix would look like the design in figure 6b. It is important +to note that this example is only intended to illustrate the concept of +a fractional factorial; practically speaking the design in figure 6b +should not be used at AFOTEC since main effects are confounded with 2FI. +How to choose appropriate fractional factorials is covered in the next +section.

Figure 6a. Full Factorial Figure 6b. Fractional Factorial


+ + + image10 + + + + + image11 + +

Observe that columns are balanced in both the full factorial and +fractional factorial figures; i.e., each factor level occurs the same +number of times. Also, for the runs involving a specific level of one +factor, the other factors' levels are also balanced. For example, in the +first four runs of figure 6b where the departure type factor is set to +the instrument level, there are 2 occurrences of each of the other +factor levels: 2xDay, 2xNight, 2xLocal, 2xNon-local, 2xOff, and 2xOn. +Recall that this means the fractional factorial is an orthogonal design.

Fractional factorials have the projection 17 property; if a factor in the design is determined to be +insignificant and its associated design column removed, the degree of +fractionation is reduced. In figure 6b, if Autopilot was not an +active effect 18 (significant +factor), the resulting design is no longer a ½ fraction, but a full +factorial in the three remaining factors. If the fractional factorial +was a ¼ fraction, removing one insignificant factor creates a ½ +fraction.

The strategy of using only a fraction of the runs in a full factorial is +based on the Sparsity‑of‑Effects 19 principle. The principle implies that the effect of the +higher order (3-factor or greater) interactions are likely negligible. +Although there is strong evidence that this principle applies in OT, it +is not always true and therefore should be assumed with caution. It is +wise to verify this assumption by discussing the issue with system +experts.

Although fractional factorial designs save resources and have many of +the same properties as full factorials (balance, orthogonality), these +designs have less information than full factorials and may not allow the +independent estimation of the main effects and 2FI if the fractionated +design is too small. The next section discusses how fractional +factorials are classified based on the degree to which independent +factor estimation is impeded.

Resolution, Aliasing, and Confounding

A central issue in experimental design is minimizing the degree to which +factors are correlated 20 with +each other while adhering to the test resource constraints. To +illustrate the problem with correlated factors, figure 7a shows three +possible designs for two varied factors in the X-100 BU 1.1 test. +Suppose the average response for runs 1-4 was higher than the average +for runs 5‑8.

Figure 7a. Perfect Aliasing Figure 7b. Partial Aliasing Figure 7c. Orthogonality + + + + image12 + + + + + image13 + + + + + image14 + +

The problem with the first design in figure 7a is that every time the +Departure Type factor is set at the Instrument level, the Takeoff +Procedure factor is set at the Normal level. Also, every time the +Departure Type factor is set at the Tactical level, the Takeoff +Procedure factor is set at the Adjusted Max Effort level. Since both +factors' levels were changed at the same time, it cannot be determined +if the higher response in runs 5-8 was due to changing the Departure +Type factor, or due to changing the Takeoff Procedure factor---or +perhaps the increase was due to changing both factors.

This ambiguity is because Departure Type and Takeoff Procedure are +perfectly correlated; i.e., a level of Departure Type is always +matched with the same level of Takeoff Procedure . In the terminology +of DOE, these factors are perfectly aliased 21. It is also equivalent to say that Departure Type and +Takeoff Procedure are confounded 22.

The second design in figure 7b is also not ideal. Although the factors +are no longer perfectly aliased (perfectly correlated), they are still +correlated, i.e. when Departure Type is set to the Instrument level, +it is more common that Takeoff Procedure is set to the Normal level. +In this scenario, Departure Type and Takeoff Procedure are partially +aliased; which means the estimate of the effect of Departure Type on +the response will be influenced by the effect of Takeoff Procedure .

The ideal case is the third design shown in figure 7c. When Departure +Type is set to the Instrument level, the two levels of Takeoff +Procedure appear equally often (2x each)---likewise for the Tactical +level. Thus the two factors are uncorrelated and therefore this design +is orthogonal. The effect of changing the level of the Departure Type +factor from Instrument to Tactical can be independently determined +because the effect of changing from the Normal level of Takeoff +Procedure to the Adjusted Max Effort level will average out over each +level of Departure Type .

Aliasing and confounding are sometimes used interchangeably, but +confounding conventionally refers to perfect aliasing. Any time a test +design is not a full factorial, there are some effects--- main effects +or interactions of some degree---that are aliased/confounded. Fractional +factorials do not have any partially aliased effects; the effects are +either orthogonal or completely confounded.

Note that the use of full and fractional factorials assumes that the +levels of factors can be chosen independently; i.e., If level 1 for +factor A is chosen, that does not constrain what level is chosen for +factor B. Occasionally the levels of two factor cannot be independently +chosen, perhaps due to some physical constraint---in other words these +factors are naturally correlated. For example, if one factor is user +weight and a second factor is user height (each with two levels, low and +high), it may be difficult to find military users who are relatively +short and relatively heavy; likewise it may be hard to find military +users who are relatively tall and relatively light. In this situation it +may not be possible to have separate factors for weight and height since +all of the possible level combinations cannot be effectively covered in +the test.

The resolution 23 of fractional +factorial designs gives information about the type of effects that are +confounded; the convention is to use roman numerals to signify the +resolution. Table 2 shows which types of effects are confounded at the +three common design resolutions. The size of a design increases as the +resolution increases. Thus test teams may not have enough resources to +use the ideal resolution V design.

Table 2. Design Resolution

ResolutionAliasing of Effects
III

Some/all main effects are aliased with 2FI

Some/all 2FI are aliased with other 2FI

IV

All main effects are orthogonal to 2FI

Some/all 2FI are aliased with other 2FI

V

All main effects are orthogonal to 2FI

All 2FI are orthogonal to other 2FI

Since main effects are confounded with 2-factor interactions in +Resolution III designs, these designs are not recommended for use at +AFOTEC. Resolution III fractional factorials are typically used as +screening designs 24 . They are +intended for experiments where the intent is to determine the active +main effects before subsequent testing is conducted to de-alias and +estimate the active 2FI. Since AFOTEC does not typically conduct +follow-on testing, resolution III designs do not provide enough +information during a test event and are not suitable for operational +test. If it is not feasible to use a larger resolution IV design, then +an optimal design (discussed later in this section) is a better design +choice.

Resolution IV designs are an appropriate choice when resource +constraints are a significant concern and a larger resolution V design +cannot be executed. Main effects can be accurately estimated because +they are uncorrelated with any 2FI. However 2FI are correlated with +other 2FI. Since it is often the case that multiple 2FI are active, +these designs do may not facilitate an adequate characterization of the +system in the battlespace.

Resolution V designs are the most popular choice. If the +Sparsity-of-Effects principle is valid, three-factor interactions or +higher are likely negligible, so main effects and 2FI are most likely +the only important effects required to characterize a system. Since both +main effects and 2FI are orthogonal to other main effects and 2FI in +resolution V designs, these are more efficient designs (require fewer +resources) for characterizing a SUT than full factorials.

Any test design higher than resolution V is likely a waste of test +resources and any design less than resolution V represents an increased +risk of not discovering or accurately estimating all of the active +effects. The goal within AFOTEC is to minimize or eliminate the +aliasing/confounding for the main effects and all 2FI. When this is not +possible, a balance must be struck between what can be estimated and the +test resources available.

Creating Fractional Factorial Designs in JMP 13:

  1. From the main JMP menu, choose DOE then Classical , then +Screening Design

Figure 8. Creating Fractional Factorials in JMP 13

+ + + image15 + +

  1. In the Factors section, add the continuous and categorical +factors using the drop down menu. Specify the number of levels for +each factor. The factors and levels can be given appropriate names. +Figures 9a/b shows the input for the X-100 BU 1 example.

  2. Click Continue .

  3. Select " Choose from a list of fractional factorial designs " +(figure 9b).

    Figure 9a. Enter Factors and Levels Figure 9b. Request a List of Fractional Factorials + + + + image16 + + + + + image17 + +

  4. Figure 10a shows the fractional factorial design list provided in +JMP 13. Notice that JMP states the resolution of each design +(although they do not use roman numerals.) You can choose a standard +fractional factorial or you can choose a fractional factorial with +blocks (Blocks are discussed in the section of this guide titled, " +The Three Principles of DOE " Note that +the full factorial is also available as an option, since there are +no resolution V designs smaller than the full factorial.

  5. Select a design and click Continue .

  6. JMP presents menu options to evaluate and modify your design (figure +10b). The Aliasing of Effects output shows which effects are +aliased (confounded) with which other effects. Figure 11a shows that +in the X-100 BU 1.1 example, the ½ fractional factorial +(resolution IV) has 3 pairs of 2FI that are aliased.

    Figure 10a. Fractional Factorial Options Figure 10b. Additional Diagnostics and Options + + + + image18 + + + + + image19 + +

  7. Specify your Run Order ; JMP provides options to sort (or +randomize) the run order and add replicates to your design.

  8. Click Make Table to create the fractional factorial design +(figure 11b)

    Figure 11a. Aliasing of Effects Figure 11b. Fractional Factorial Design + + + + image20 + + + + + image21 + +

JMP can only create fractional factorials if every factor is restricted +to two levels. There are methodologies for fractionating designs +involving factors with more than two levels, but that topic is beyond +the scope of this design guide. When it is not applicable to use +fractional factorials with 2-level factors, AFOTEC analysts typically +use JMP to create an optimal design; these designs are discussed in a +subsequent part of this section. The National Institute of Standards and +Technology has a comprehensive list of 2-level fractional factorial +designs here: +http://www.itl.nist.gov/div898/handbook/pri/section3/pri3347.htm

For more information on fractional factorials and design resolution see +Chapter 8 of Montgomery, D. C. (2013). Design and Analysis of +Experiments, 8th Edition. Hoboken, NJ: John Wiley & Sons, Inc.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)/index.html b/sites/oteguide/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)/index.html new file mode 100644 index 00000000..b1533c5d --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)/index.html @@ -0,0 +1,152 @@ +Optimal Designs (Computer Generated Designs)

Optimal Designs (Computer Generated Designs)

An Optimal design 25, +sometimes referred to as computer generated design (CGD), is a test +design whose levels are combined in a way that optimizes a specified +statistical criterion that is a function of the design matrix. Unlike +factorial designs, which are constructed using a standard method that +guarantees balance and orthogonality, optimal designs are constructed by +a computer implementing an algorithm. Design construction algorithms +combine factor levels into test runs with the goal of optimizing some +design quality criterion. The optimization incorporates constraints such +as run size or disallowed combinations of factors.

Optimal design construction algorithms may not always find the "best" +design. One reason is that the algorithm may not be allowed to run long +enough to find the optimal combination of factor levels. Another reason +is that there may be multiple designs which have the same optimal value +of the chosen criterion. The generated design may be optimal for the +specified criterion, but another design (with the same optimal value) +may be superior in terms of a different un-evaluated criterion. As a +consequence, optimal designs must be evaluated for quality by a +knowledgeable test analyst. The test team should also modify the default +settings of the construction algorithm---as an example, the algorithm +run time---if a generated design has flaws.

An optimal design is constructed based on a model specified by the +analyst. The analyst may include in the model any number of main +effects, two-factor interactions, or higher-order terms if necessary; +three-factor interactions and higher are not generally included at +AFOTEC based on the Sparsity‑of‑Effects principle.

The optimality criterion chosen to create the design depends on the test +goal. The following are optimal designs that can be created with JMP +software.

  1. D-optimal designs - Used when an analyst places a priority on +accurate effect estimates. This is because D-optimal designs +minimize the joint variance of the parameters in the statistical +model. For example, when using continuous factors, these designs +minimize the joint variance of the linear regression +26 coefficients \widehat{\mathbf{\beta}} . When model +parameter estimates have low variance, we can expect the estimates +to be close to the true value (assuming we are using unbiased +estimates.) D-optimal designs are used most often in OT as they are +ideal for characterizing a system.

  2. I-optimal designs - Used when an analyst prioritizes accurate +predictions from a statistical model. These designs minimize the +average prediction variance of statistical models. Unlike D-optimal +designs which have test points located at the extremes of the design +space, some test points in I-optimal designs may be spread +throughout the design space (when continuous factors are used.) +These points improve a model's predictive capability across the +whole design space.

  3. Alias-optimal designs - Used when an analyst prioritizes +minimizing bias in the parameter estimates from un-modeled factors. +These designs minimize the aliasing (correlation) between the +specified model effects and other terms not included in the model. +This optimality criterion is typically used when a design is +constructed to estimate main effects only, but the analyst wants to +insure against 2FI which may be active (but are not included in the +model).

Creating a D-Optimal design in JMP 13:

  1. From the main JMP menu, choose DOE then Custom Design +(figure 12a)

  2. Add the response variables

    a. One response variable is included by default. Change the +response name by clicking on "Y"

    b. For additional responses, use the Add Response drop down +menu in the Responses box. You can choose whether the +response should be maximized, match a target value, minimized, +or none of these

  3. Add the factors

    a. In the Factors box, use the Add Factor drop down menu to +add the appropriate type of factor. AFOTEC typically uses +categorical factors, although continuous factors are ideal; the +number of levels must be specified for Categorical and +Discrete Numeric factors

    b. For adding multiple factors of the same type and number of +levels, input the appropriate number in the Add N Factors +box

    c. If you have created a JMP table of your factors and levels, you +can populate them in the Factors box by clicking on the red +triangle to the left of Custom Design and choosing Load +Factors

  4. In the Specify Factors box, click Continue

  5. Linear constraints on continuous factors, or disallowed combinations +of categorical factors can be added in the Define Factor +Constraints box

  6. Only the main effects are loaded by default in the Model box +(figure 12b). To add more model terms click on the Interactions +drop down menu and choose 2nd (this will load all 2-factor +interactions -- if you want higher order interactions, choose those +as well)

    Figure 12a. Creating a D-optimal Design Figure 12b. Adding 2-way Interactions to Model + + + + image22 + + + + + image23 + +

  7. Input the number of runs. Select either the Minimum (determined +by the model terms you entered in the Model box), Default, +or enter the number of runs you want in User Specified (figure +13a)

  8. Click on the red triangle to the left of Custom Design

    a. Choose Optimality Criterion , then Make D-Optimal Design +(figure 13b)

    b. Choose Number of Starts ; enter an appropriate number and +choose OK

    c. Choose Design Search Time; enter an appropriate number and +choose OK

  9. Click on Make Design

    Figure 13a. Specify the Number of Runs Figure 13b. Specify the Optimality Criterion + + + + image24 + + + + + image25 + +

  10. At the bottom of the new window, set Run Order to Sort Left to +Right

  11. Click on Make Table . Notice that unlike when using a Full +Factorial or Screening design, there is no Pattern column

  12. To assess the designs balance, JMP has graphically see the results +(balance) of the design:

    a. From the JMP main menu, click on Analyze then +Distribution

    b. Under Select Columns , select all the factors except Y +(the response variable) and click on Y, Columns to add all +the factors to that box

    c. Click on OK

    d. The bar charts can be used to determine if each factor has +balanced levels, and whether the other factors' levels are +balanced over a factor level.

Creating optimal designs requires a sound understanding of design +principles. Analysts can create an optimal design to meet the +requirements of almost any test situation, but should review the test +design to ensure the following:

  1. There is no excessive aliasing/confounding between main effects and +two-factor interactions; A good rule of thumb is to have +correlations below 0.5 as much as possible and not exceed 0.7.

  2. There are enough degrees of freedom (dof) for error estimation; a +good rule of thumb is to have at least 5 dof to estimate error.

The aliasing structure in an optimal design can be very complex, which +results in biased effect estimates. The D-optimality criterion is most +frequently used at AFOTEC, as it minimizes the bias in the effect +estimates that results from correlation between the specified model +effects. When JMP is used to construct an optimal design, the design +diagnostics which can be used to evaluate the correlation structure are +provided under the Design Evaluation header.

An analyst should create several optimal designs and compare them using +the Test Design Measures of Merit. The +algorithm that generates the optimal design may not always produce the +"best" design. Optimal designs are usually created based on a single +optimization criterion. In contrast, full and fractional factorials are +optimal over several optimality criteria; when fitting a model with main +effects and two-factor interactions, factorials are D-optimal, +I-optimal, and Alias-optimal. If the number of runs in a test is a power +of two and all factors have two levels, then the optimal design is a +full or fractional factorial.

Unfortunately, it is possible an optimal design algorithm may not +produce a factorial when appropriate. As mentioned earlier in this +section, this may be due to insufficient run time for the algorithm or +another design has an equivalent value of the specified optimality +criterion. Consequently, it is wise to verify that the software used to +generate an optimal design actually produces a factorial design when +applicable.

The number of runs in the test design can have a significant impact on +the quality of a design produced by a construction algorithm. Suppose +you have a design with two three-level factors and one four-level +factor. If you require a design with fewer runs than the full factorial +with 36 runs, you should choose a design size that is evenly divisible +by the number of levels in as many factors as possible. By doing this, +you make it more likely the factor levels are balanced. For example, if +the chosen design size is 26 it is impossible to balance both the +three-level and four-level factors. However, if the design size is 24, +then the design could be balanced; each level of the three-level factors +could be in eight runs, and each level of the four-level factor could be +in six runs.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/2-3-Augmented-Designs/index.html b/sites/oteguide/analyst_test_design_guide/2-3-Augmented-Designs/index.html new file mode 100644 index 00000000..39ce9978 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/2-3-Augmented-Designs/index.html @@ -0,0 +1,57 @@ +Augmented Designs

Augmented Designs

When a test plan changes during execution, the uncompleted portion of +the design should be updated ( augmented 27 ) with new runs; optimal designs in particular may not be +robust to lost or altered test runs. Designs can be created and +augmented quickly with software, but logistical constraints may make it +difficult to adjust test events in real time. The following describes +how to augment designs in JMP 13. Note that JMP assumes that data is +entered in the response column.

  1. Augmenting a design in JMP 13:

  2. Open the existing design table in JMP

  3. From the main JMP menu, choose DOE then Augment Design

  4. Drag the response to the Y, Response box

  5. Drag the factors to the X, Factor box

  6. In the Action box, click OK

    Figure 14a. Augmenting a Design in JMP Figure 14b. Enter the Response and Factors + + + + image26 + + + + + image27 + +

  7. If the existing design has already been executed, it is a best +practice to check the box next to "Group new runs into separate +block" (See the blocking discussion.)

  8. Linear constraints on continuous factors, or disallowed combinations +of categorical factors can be added in the Define Factor +Constraints box

  9. To replicate the existing design, choose Replicate in the +Augmentation Choices box

  10. To add center points to the existing design, choose Add +Centerpoints in the Augmentation Choices box

  11. Otherwise choose Augment in the Augmentation Choices box

    a. Only the main effects are loaded by default in the Model +box. To add more model terms click on the Interactions drop +down menu and choose 2nd (this will load all 2-factor +interactions); If you want higher order interactions, choose +those as well)

    b. Under the Design Generation header, enter the total number +of runs in the design AFTER augmentation; e.g., given a +design with 20 completed runs, if you want to augment it with 10 +additional runs then enter 30 runs.

  12. Click the red triangle next to Augment Design , select +Optimality Criterion and select Make D-Optimal Design

  13. Click Make Design

    Figure 15a. Select an Augmentation Choice Figure 15b. Define the Model and Enter # of Runs + + + + image28 + + + + + image29 + +

  14. Click on Make Table

  15. To graphically see the results (balance) of the design:

    a. From the JMP main menu, click on Analyze then +Distribution

    b. Under Select Columns , select all the factors except Y +(the response variable) and click on Y, Columns to add all +the factors to that box

    c. Click on OK

    d. The bar charts can be used to determine if each factor has +balanced levels, and whether the other factors' levels are +balanced over a factor level.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments/index.html b/sites/oteguide/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments/index.html new file mode 100644 index 00000000..7d435163 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments/index.html @@ -0,0 +1,74 @@ +Designs for Computer Experiments

Designs for Computer Experiments

Data for some test programs are obtained from simulation models, many of +which are deterministic 28. +This means that the simulation output does not change if the inputs are +held constant. In other words, a single observation obtained from a +given combination of factor levels (test point) provides all of the +information available about that test point.

When obtaining data from deterministic simulations (or software systems +which have deterministic outputs) using a factorial design may not be +the best experimental design strategy. An efficient design strategy for +deterministic systems uses the following two principles:

  1. Designs should not replicate test design runs; one run provides +complete information about the response variable at that test point +because there is no variance in the response.

  2. Designs should allow for the fitting of complex models by providing +information about the response variable at all areas of the design +region.

The next section discusses some alternative designs that follow the +above principles.

Space-Filling Designs

Space-filling designs are constructed so that they spread design points +evenly throughout a design region. These designs are used when the test +factors are continuous. The following are general construction methods:

  1. Disperse the design points as uniformly as possible in the design +region using distance measures.

  2. Obtain design points using sampling methods in the design region

  3. Utilize a hybrid distance measure/sampling approach

Common construction algorithms for these designs include Uniform +sampling, Sphere Packing, and Latin Hypercube sampling.

  1. Uniform space-filling designs -- Design points are randomly selected +from a uniform distribution 29 +defined over the range of a factor. They are simple to construct and +augment (just add more randomly selected points to the space.) +However these designs tend to leave gaps in the design coverage when +the points are unevenly distributed---particularly when the number +of test points is small relative to the size of the design space.

  2. Sphere packing space-filling designs -- Algorithms pack circles, +spheres or hyper spheres of equal radii into the design space and +use the center of each as the design point. Sphere packing designs +give even coverage across the design space but are difficult to +augment because the spheres have already been optimally "packed" +into the design space and any new points would upset the +distribution of existing points.

  3. Latin Hypercube Designs -- Each continuous factor is divided into n +evenly spaced intervals, creating a grid of hypercubes (in the +two-dimensional case this is a square grid with n2 squares.) The +design points are chosen so that each of the n subintervals are +chosen exactly once in each dimension. The worst case scenario, if +this process is done completely at random, is that all of the design +points fall along the diagonal of the hypercube (figure 16a). To +avoid this, the algorithm is usually modified to create designs more +like figure 16b.

    Figure 16a. Worst Case Space Filling Design Figure 16b. Desirable Space Filling Design + + + + image30 + + + + + image31 + +

You can create Space Filling Designs in JMP 13 by going to the DOE +menu and selecting the Special Purpose option, then Space Filling +Design (figure 17a). JMP 13 provides 7 design construction methods +(figure 17b).

Figure 17a. Opening the Space Filling Design Platform Figure 17b. Space Filling Design Methods in JMP 13 + + + + image32 + + + + + image33 + +

For specific questions that are not addressed here or in the JMP help +files, feel free to contact the Intelligence, Analysis and Assessments +Directorate (A-2/9).

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems/index.html b/sites/oteguide/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems/index.html new file mode 100644 index 00000000..7c05efc4 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems/index.html @@ -0,0 +1,19 @@ +Test Designs for Comparing Systems

Test Designs for Comparing Systems

Comparison tests are conducted to test the hypothesis that a system +meets a specified threshold, to compare system performance under two or +more different conditions, or to compare the performance of two or more +systems. When designing a comparison test, there are two important +issues to address:

  1. When data is grouped by the systems being compared, or the different +operational conditions for which performance is compared, it is a +best practice to have an equal number of test points in each group. +This will facilitate a more effective comparison of the group means.

  2. The number of test points in each group gives appropriate power to +detect the delta (difference between the group means) of interest.

For more information please contact the Test Design and Analyses +Division of A-2/9.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification/index.html b/sites/oteguide/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification/index.html new file mode 100644 index 00000000..bc165bf4 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification/index.html @@ -0,0 +1,20 @@ +Test Designs for Problem Identification

Test Designs for Problem Identification

Test designs for problem identification are constructed using different +design principles than those used for system characterization. The +designs, called combinatorial designs or covering arrays, are used when +the SUT is assumed to have a deterministic response variable; i.e., +replicating the design points is not necessary. They are typically not +suitable for characterization of system performance in the battlespace, +but they generally require fewer runs than designs used for performance +characterization. These designs are a useful tool for designing test +runs for "demo'd" factor levels; i.e., for test runs representing rare +operational conditions. Consequently, an AFOTEC test may involve designs +for both characterization and problem identification.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays/index.html b/sites/oteguide/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays/index.html new file mode 100644 index 00000000..a1179cd1 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays/index.html @@ -0,0 +1,123 @@ +Combinatorial Designs (Covering Arrays)

Combinatorial Designs (Covering Arrays)

Combinatorial Designs or Covering Arrays (CA), terms sometimes used +interchangeably, employ the science of systematically selecting +combinations of factors and levels to provide the best chance of +identifying problems. They are constructed to efficiently evaluate a +system at all possible level combinations for subsets of t factors, +where t is usually small relative to the total number of factors. Note +that a combination of levels for t factors is called a t -tuple +30. Combinatorial designs are often +used in testing software intensive systems with a deterministic binomial +response variable (a pass/fail response which will not change no matter +how many times the design point is replicated.) However, these designs +can also be applied to testing other types of systems where problem +identification is the primary goal.

Combinatorial designs have advantages and disadvantages. The drawback of +combinatorial designs is that they do not allow for the effect of a +factor to be estimated nor do they allow for statistical modeling; they +are rarely balanced or orthogonal. The advantage of these designs is +that they can be used with a large number of factors---even if they have +many levels---as the size of the design can be controlled.

Design size is determined by adjusting construction parameters called +strength 31 and coverage +32. Combinatorial designs have +strength t if every possible t -tuple of factor levels appears at +least once in the design. The notion of combinatorial design coverage is +used to quantify what percentage of the possible factor level t +-tuples occur in the design. Intuitively, 100% coverage at strength t +means that all possible t ‑tuples appear in the design at least once. +A test team may choose a design with less than 100% coverage at strength +t , rather than 100% coverage at strength t-1 . The benefit is that +even though the design only partially covers the possible t -tuple +combinations, the probability of finding a fault caused by a t-way +interaction of factors is higher than when using the smaller design of +strength t‑1 (with 100% coverage); therefore the overall effectiveness +of the design at finding faults is higher.

A combinatorial design can be constructed for any combination of +categorical factors and levels (continuous factors must be converted to +categorical). Disallowed combinations of levels can be removed from the +designs, but this may increase the size of the design for a given +strength and coverage. Industry has embraced combinatorial designs for +software testing as an efficient method of finding software problems +when the possible input (factor) space is large (Kacker, Kuhn, & +Lawrence, 2013). During an operational test for a software intensive +system, a combinatorial design may be an option to evaluate +deterministic measures. However, data for any stochastic +33 measures (those having random +variation) should be collected using other types of designs.

The National Institute of Standards and Technology has a free tool for +creating Covering Arrays and Combinatorial Designs: Automated +Combinatorial Testing System (ACTS). The tool takes the factor and level +inputs from a test design, and provides the minimal factor covering +array at the desired strength and coverage. The tool is located at:

http://csrc.nist.gov/groups/SNS/acts/documents/comparison-report.html +.

JMP does not have a platform for constructing combinatorial designs.

Creating a Combinatorial Design in ACTS:

Note: when entering factor or level names, do not use commas, spaces, or +special characters.

  1. Select System , then select New (figure 18a)

  2. Enter the name of the system in the System Name box

  3. Enter a factor (ACTS refers to factors as parameters)

    a. Type the factor name in the Parameter Name box

    b. Enter the nature of the levels and the level names

    i. If the factor is a Boolean type (true/false, yes/no,
    > pass/fail)
    +
    1. Select **Boolean** in the **Parameter Type** drop down
    > menu
    +
    2. The factor levels are automatically named **true** and
    > **false**
    +
    ii. If the factor is categorical
    +
    1. Select **Enum** in the **Parameter Type** drop down menu
    +
    2. Type the level name in the **Simple Value** box
    +
    3. Click **Add**
    +
    4. Repeat steps 2-3 for all factor levels
    +
    iii. If the factor is continuous
    +
    1. Select **Number** in the **Parameter Type** drop down
    > menu
    +
    2. Type the level value as an integer in the **Simple
    > Value** box
    +
    3. Click **Add**
    +
    4. Repeat steps 2-3 for all factor levels
    +
    iv. If the factor is categorical or continuous and the levels
    > are labeled by consecutive integers
    +
    1. Select **Range** in the **Parameter Type** drop down
    > menu
    +
    2. Type the first integer value in the left **Range Value**
    > box
    +
    3. Type the last integer value in the right **Range Value**
    > box
    +
    4. Click **Add**

    c. Click Add to Table

  4. Repeat Step 3 for all factors

    Figure 18a. Creating a Combinatorial Design Figure 18b. Enter the Factors and Levels + + + + image34 + + + + + image35 + +

  5. Click Add System when all factors are entered (figure 18b)

  6. Create the combinatorial design by opening the Operations menu +and clicking Build (figure 19a)

    a. Specify the algorithm in the Algorithm box (the recommended

    > one is **IPOG** )

    b. In the Strength box, indicate the strength of the

    > combinatorial array (1-6)

    c. In the Mode box

    i. Select **Scratch** to create a new combinatorial array
    +
    ii. Select **Extend** to extend an existing array

    d. In the Constraint Handling box, select how the algorithm

    > incorporates disallowed combinations of levels; the default
    > method is recommended

    e. Check the Show Progress box if you want to see the

    > algorithm's progress

    f. Check the Ignore Constraints box if you have entered

    > constraints but want to compare the design with constraints to
    > a design without constraints

    g. Uncheck the Randomize DontCare Values box unless you have

    > constraints

    h. Click Build (figure 19b)

    Figure 19a. Build the Combinatorial Design Figure 19b. Select the Design Options + + + + image36 + + + + + image37 + +

  7. Check the design statistics (figure 20)

    a. Click on the Statistics tab

    b. Click Graph to see a graph of the coverage ratio vs. the +number of test runs.

Figure 20. Checking the Combinatorial Design Statistics

+ + + image38 + +

Example of a Combinatorial Design

Suppose AFOTEC is testing an enterprise software system. There is a +pass/fail deterministic response variable that indicates whether the +operator was able to successfully use the system under a specified +condition defined by a combination of factor levels. There are six +three-level categorical factors, so a full factorial requires [ 3 ^6^ += 729 ]{.math .inline} runs. The test team cannot afford that many runs, +so they use ACTS to investigate how a combinatorial design can reduce +the size of the test. Table 3 shows the number of runs required for a +design of strength t , for t = 1 to 6 .

Table 3. Number of Runs Required for Strength t

StrengthNumber of Runs
13
215
348
4140
5318
6729

Suppose the test team has resources for a test with 100 runs. Then if +the test team wants 100% coverage of the t -tuples, they should use +the combinatorial design of strength 3 with 48 runs. However, since they +have the budget to conduct a test twice that size, the test team +considers using a subset of the strength 4 design and accepting partial +coverage of the 1215 possible 4‑tuples. Checking the graph of the +coverage ratio vs. the number of test runs (figure 20), the test team +learns that using 100 runs from the strength four design will give +approximately 90% coverage of the 4-tuples; this is a very good design +option. For more information on combinatorial designs contact the Test +Design and Analyses Division of A-2/9.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/2-8-Demonstrations/index.html b/sites/oteguide/analyst_test_design_guide/2-8-Demonstrations/index.html new file mode 100644 index 00000000..751be8d8 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/2-8-Demonstrations/index.html @@ -0,0 +1,30 @@ +Demonstrations

Demonstrations

Demonstrations are the simplest of the problem identification test +designs. They are usually single events demonstrating that a system can +successfully operate under a particular condition of interest (a single +factor level or specific combination of levels). Demonstrations should +only be used to supplement more statistically rigorous test designs, not +used as the primary test design. The test team should methodically +select the factor levels for the demonstration test points using prior +knowledge from SMEs.

It is unlikely that any meaningful inferential conclusions can be drawn +from demonstrations alone, as the principles of DOE are rarely applied +to these runs. There is usually little to no replication of the factor +level being evaluated, so it is difficult to characterize the average +performance of the response at the demo'd factor level. Also, for the +factors that are not of interest in a demo run, there is a tendency for +their levels to be randomly selected during execution. Also, if there +are several factors with levels marked for demonstration, these levels +may be combined into a single demo run. These practices add significant +ambiguity concerning the attribution of system performance to the demo'd +factor's level. If there are several demo runs in a test, it is a best +practice to fix the levels of the factors that are not of interest. This +allows the impact of the demo levels to be more easily determined in the +analysis.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/2-9-Cases/index.html b/sites/oteguide/analyst_test_design_guide/2-9-Cases/index.html new file mode 100644 index 00000000..6a1375c9 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/2-9-Cases/index.html @@ -0,0 +1,18 @@ +Cases

Cases

Cases are like demonstrations but have several specific combinations of +factors and levels that are intended to be examined together. Types of +case designs include examining the worst or best case configuration of +the factors and levels. The belief is that if a problem exists, it will +exhibit itself when the system is operated under the worst possible or +best possible scenario. Sometimes a case design is executed for a +special-interest item or even political reasons. As with single +demonstrations, it is unlikely the data recorded from these events can +be statistically analyzed.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/3-1-Observational-Studies/index.html b/sites/oteguide/analyst_test_design_guide/3-1-Observational-Studies/index.html new file mode 100644 index 00000000..4712e84b --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/3-1-Observational-Studies/index.html @@ -0,0 +1,121 @@ +Observational Studies

Observational Studies

A pure observational study is a rigorous investigation of treatments and +the effects they cause, but differs from a designed experiment (or test) +in that the investigator cannot control the assignment of factor levels +(treatments) to the items under test. Consequently, the analysis of the +treatment effects must consider any possible bias due to confounded +factors. When using statistics to draw inferences about a population, it +is commonly said, "Correlation does not equal causation." This is +especially important to remember when using an observational study to +draw conclusions about the performance of a system. Since the test team +does not change factor level settings and then directly observe a +response, it is more difficult to attribute the change in a measure +(response variable) to the change of a particular factor's level. This +difficulty is caused by the increased likelihood that nuisance factors +are strongly correlated with test factors in an observational study, +which prevents clear attribution of cause and effect between factors and +the measures.

During some AFOTEC tests, it is impossible to control the test +conditions. However, there are combinations of factors and levels that +the test team wants to see at some point during the test event. It is a +best practice to create a test event matrix (TEM) for observational +studies which includes all of the factor/level combinations that the +test team desires to see. Then the goal of test planning is to maximize +the probability that each level combination is observed a sufficient +number of times.

For example, figure 21 shows a portion of the TEM for the notional New +Air Force Electronic Pay System (NAFEPS). NAFEPS will replace the Air +Force's legacy human resource (HR) software system. Factors in the test +include the HR business process, the user role executing the process +(e.g., HR specialist), the affected member's total force component +(e.g., Air Force Reserve), the affected member's classification (e.g., +officer), and the organization level at which the business process is +executed (e.g., base level).

Figure 21. TEM for the New Air Force Electronic Pay System (NAFEPS)

+ + + image39 + +

During OT, the system will be live and capable of altering real-world +databases. Without the "sandbox" environment of DT, the test team is +unable to direct users to process fictitious paperwork, such as +recording disciplinary actions or retirements. Consequently, the test +team can only observe users executing various HR business processes +during the course of their normal duty.

The TEM aids the test team in determining where and when to observe the +SUT in order to maximize the probability of observing the factor level +combinations of interest. For example, the test team could choose to +send a team to the Air Reserve Personnel Center (ARPC) at Buckley Air +Force Base, CO to observe ARPC HR specialists processing retirement +paperwork. For business practices that peak in frequency at various +times of the year, the test teams will time the site visits accordingly.

Another important question the test team must answer is how long to +observe the SUT in order to see all of the factor level combinations of +interest. Some factor level combinations may be relatively rare, such as +design point 1. "Record Disciplinary Actions" against Regular Air Force +cadets. Fortunately there are some simple formulas that can be used for +planning the duration of observational studies.

If the factor level combinations of interest occur at a predictable rate +during some period of time, but completely at random during the time +period, then the test event can be modeled as a Poisson Process. Poisson +processes are used to model situations like the arrivals of customers to +a store, or the number of car accidents in a certain area. The important +assumptions are:

  1. The events occur at a certain rate but completely at random within +an interval (e.g., on average, 5 customers arrive at a store per +hour; but when they arrive within the hour is completely random)

  2. The number of events in some interval of length t is independent of +and identically distributed as the number of events in another +(disjoint) interval of length t (e.g., the average number of +customers arriving to the store between 0900 and 1000 is the same +average number arriving between 1100 and 1200)

In the context of observational studies, the arrivals of interest are +the rare factor level combinations. It suffices to focus on the +probabilities of the rare factor level combinations, as the +probabilities of observing the more common events will be greater and +therefore are not limiting factors.

Example 1: Calculating the Time to Observe One Rare Event with +Specified Probability. Suppose we want to know the test time t that +gives a probability of 80% (p = 0.8) that the test team will observe a +rare factor level combination.

The first step is to estimate the rate [ λ ]{.math .inline} of the +average number of events per time period. Suppose a rare factor level +combination occurs randomly 1 time every 3 working days (on average) +while a system is operating. Assuming an 8 hour work day, this is 1 +event every 24 working hours, implying [ λ ]{.math .inline} = 0.042 +events per hour.

\frac{\mathbf{1}\ \mathbf{\text{event}}}{\mathbf{24}\ \mathbf{\text{hours}}}\overset{\Rightarrow}{\ }\mathbf{\lambda} = \mathbf{0}.\mathbf{042}\ \mathbf{\text{events}}/\mathbf{\text{hour}}

Step 2 is to convert 80% into the decimal p = 0.8 and use the following +formula to calculate the test time t.

\mathbf{t} = \frac{- \mathbf{\ln}\left( \mathbf{1} - \mathbf{p} \right)}{\mathbf{\lambda}}

\mathbf{t} = \frac{- \mathbf{\ln}\left( \mathbf{1} - \mathbf{0}.\mathbf{8} \right)}{\mathbf{0}.\mathbf{042}} = \mathbf{38}.\mathbf{3}\ \mathbf{\text{hours}}

The analysis shows that 38.3 test hours are required to have an 80% +chance of observing a factor level combination that occurs randomly 1 +time every 24 hours (on average.)

Example 2: Calculating the Time to Observe k Rare Events with +Specified Probability. Suppose we want to know the test time t that +gives us an 80% probability (p = 0.8) chance of observing k = 3 +occurrences of a rare factor level combination that occurs randomly 1 +time every 3 working days (on average). We already calculated that [ +λ ]{.math .inline} = 0.042 events per hour. In this example a more +complicated formula is required:

\mathbf{1} - \mathbf{p} = \sum\_{\mathbf{n} = \mathbf{0}}^{\mathbf{k} - \mathbf{1}}{\frac{\mathbf{1}}{\mathbf{n}!}\mathbf{e}^{- \mathbf{\lambda}\mathbf{t}}\left( \mathbf{\lambda}\mathbf{t} \right)^{\mathbf{n}}}

Plugging in the values we know (p = 0.8, k = 3, [ λ ]{.math .inline} += 0.042) we have

\mathbf{0}.\mathbf{20} = \mathbf{e}^{- \mathbf{0}.\mathbf{042}\mathbf{t}} + \mathbf{e}^{- \mathbf{0}.\mathbf{042}\mathbf{t}}\left( \mathbf{0}.\mathbf{042}\mathbf{t} \right) + \frac{\mathbf{1}}{\mathbf{2}}\mathbf{e}^{- \mathbf{0}.\mathbf{042}\mathbf{t}}\left( \mathbf{0}.\mathbf{042}\mathbf{t} \right)^{\mathbf{2}}

A simple way to solve this equation for t is to use Excel's solver +function to find the value for t that minimizes the difference between +the equation's right hand side and the left hand side (0.2 in this +example.) The solver reports that t = 71.3 hours. This means we must +observe the system 71.3 hours in order to have an 80% chance of seeing 3 +occurrences of a rare factor level combination that occurs 1 time every +3 working days (on average.)

Example 3: Calculating the Probability of Observing a Rare Event with +Specified Time. Suppose the resource constraints have imposed a limit +of 4 working days (32 hours) for the observational study. Given a fixed +test time t = 32 hours, we want to determine the probability of +observing a rare factor level combination that occurs randomly 1 time +every 3 working days. In other words, if [ T ~1~ ]{.math .inline} is +the time of the first occurrence of the rare event, then we want the +probability that [ T ~1~ ]{.math .inline} is less than t : P [ ( T +~1~ \< t ) ]{.math .inline} . Recall that [ λ ]{.math .inline} += 0.042 events per hour. The formula to use is:

**P** ( **T** **1** **<** **t** ) **=** **1** **** **e** **** (λt)
+
**P** ( **T** **1** **<** **32** ) **=** **1** **** **e** **** **(** **0.042** **)** **(** **32** **)** **=** **0.74**

Therefore we have a 74% chance of seeing the rare event during the 32 +hour test.

In summary, the three formulas in Examples 1-3 provide probability +assessments that can be used to plan the duration of observational +studies, as well as characterize the risk of not observing important +factor level combinations.

An observational study should only be used when it is impossible to +control the factor levels. They must have sufficient documentation to +prove the test team will gather the appropriate data to answer all of +the desired questions. While an observational study is not the ideal +test scenario, with proper planning these tests can provide data to +characterize the performance of the system. For more information on the +use of an observational study for an AFOTEC test program, and the theory +behind the use of Poisson Process modeling, please contact the Test +Design and Analyses Division of A-2/9.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT/index.html b/sites/oteguide/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT/index.html new file mode 100644 index 00000000..4299f8dd --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT/index.html @@ -0,0 +1,18 @@ +TEST DESIGN MEASURES OF MERIT

TEST DESIGN MEASURES OF MERIT

All test designs have associated measures of merit, or quality +indicators, which should be considered when deciding on a test design. +Test design measures of merit include power, optimality efficiency, +correlation, prediction variance, resolution, strength, and coverage. +The most commonly encountered and generally applicable test design +measures of merit are presented in this section. Note that some measures +of merit which pertain to specific design types (like strength and +coverage for combinatorial designs) are discussed in the sections of +this guide corresponding to the relevant designs.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/3-3-Power/index.html b/sites/oteguide/analyst_test_design_guide/3-3-Power/index.html new file mode 100644 index 00000000..add675f4 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/3-3-Power/index.html @@ -0,0 +1,38 @@ +Power

Power

In a hypothesis test, power is a measure of the probability the null +hypothesis will be correctly rejected when it is false. In the context +of statistical modeling, the null hypothesis is that a factor is not +active (has no effect on the response); therefore in that context power +refers to the probability the test data will correctly identify a factor +as active. Power is a function of the test design, significance level, +signal (e.g., difference in the response between factor levels), and +noise (natural variation in the measure for a given test run.)

AFOTEC calculates power over a range of signal to noise ratios (SNR) at +a significance level of [ α = 0.2 ]{.math .inline} . SNR refers to the +ratio of the minimum desired detectable difference, delta (δ), and the +standard deviation of the response values at a given design point, sigma +(σ). AFOTEC typically evaluates power for 0 \< δ/σ \<  3.5; the range of +interest for AFOTEC and DOT&E is usually between 1 \< δ/σ \< 2. Rather +than using a SNR, power can also be calculated by using SMEs, +requirements documents, and previous system data (from a legacy system +or DT) to identify appropriate values for δ and σ.

A rule of thumb is to employ designs with a minimum power of 80% for +effects of interest. Power analysis for a designed experiment requires +the following information:

  1. The test design matrix metadata (which includes the number of +factors, levels for each factor, and sample size)

  2. The proposed statistical model

  3. The significant level (α)

  4. The desired detectable change in the response (δ)

  5. The standard deviation of the response value at a given design point +(σ); the assumption for power analysis is that σ is the same at all +design points.

List items 4 and 5 can be combined into a SNR value.

Power calculations for binary response variables are different than +those for continuous response variables. More information on calculating +power for binomial response variables can be found here:

http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdf +. (Ortiz, 2014)

For guidance on creating power curves or power calculations in AFOTEC +refer to the November 2014 guide, Power Analysis Tutorial for +Experimental Design Software, which can be found on the AFOTEC +SharePoint in the Analyst and Engineer Community. Contact the Test +Design and Analyses Division of A-2/9 for assistance creating or +interpreting power curves.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/3-4-Optimality-Efficiency/index.html b/sites/oteguide/analyst_test_design_guide/3-4-Optimality-Efficiency/index.html new file mode 100644 index 00000000..c9876cbe --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/3-4-Optimality-Efficiency/index.html @@ -0,0 +1,25 @@ +Optimality (Efficiency)

Optimality (Efficiency)

An important measure of merit for optimal designs is the optimality +efficiency. The optimality relates to the criteria used to determine the +"best" design during execution of the design construction algorithm. JMP +calculates efficiencies for the D 34, G 35 and A 36 optimality criteria, which were discussed in the Optimal Designs section of this guide. The efficiencies are +the ratio of the optimality criterion value of the evaluated design to +the optimal value of an ideal (perhaps unobtainable) design of the same +dimensions. When JMP constructs a computer generated design, it reports +the D, G, and A efficiencies under the Design Diagnostics header under +" Design Evaluation " (figure 22).

Figure 22. Optimality Efficiencies under Design Diagnostics

+ + + image40 + +

The efficiency values will range from 0-100% with 100% being the best. +For more information, please consult the JMP documentation or contact +the Test Design and Analyses Division of A-2/9.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/3-5-Correlation-Multicollinearity/index.html b/sites/oteguide/analyst_test_design_guide/3-5-Correlation-Multicollinearity/index.html new file mode 100644 index 00000000..1edd95fb --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/3-5-Correlation-Multicollinearity/index.html @@ -0,0 +1,57 @@ +Correlation (Multicollinearity)

Correlation (Multicollinearity)

Correlation between two factors is a statistical measure that indicates +the extent to which the levels of those factors vary together. A +positive correlation indicates that factors increase or decrease in +parallel; a negative correlation indicates that one factor increases as +the other decreases.

It is undesirable to have correlated factors in a test design. First, +when two active factors are perfectly correlated, it is not possible to +quantify the independent effect of each factor on the response. Second, +correlated factors increase the variance of the estimates of the +statistical model parameters and the estimates of the mean response +value.

Bias due to multicollinearity can be unintentionally introduced when +influential and controllable factors that are not of interest +operationally are allowed to vary randomly during the test event. This +situation may occur when the test team decides to exclude medium impact +factors from the list of varied factors in order to prevent the design +from becoming too large, or to prevent the test from having low power. +It is poor practice to label these excluded factors as "logged" factors, +as the chances of biased data becomes far more likely. Instead, include +these factors in an "off-line" test design (that will be used for test +execution) if you think post-test analysis might possibly involve them. +These factors can be omitted from the reported design for the purposes +of calculating measures of merit like power.

A correlation matrix shows the linear relationship between any pair of +factors. If any of the values in the correlation matrix is above 0.5, +the design should be adjusted if possible to reduce the correlation. JMP +will produce a "Color Map on Correlations" in the "Design Diagnostics" +tab. Figure 23 shows two "Color Map on Correlations" plots from JMP.

Figure 23. Examples of Color Maps

+ + + image41 + + + + + image42 + +

The horizontal labels across the top are the main effects and the +2-factor interactions. The labels on the vertical axis are not shown but +are the same as the horizontal axis. The scale on the right indicates +the amount of pair-wise correlation. Royal blue indicates no correlation +and red indicates perfect correlation. The plot on the left is the +optimal, and depicts no correlation between any of the factors or their +2-factor interactions (the red diagonal is the correlation of each +factor with itself and therefore shows red for perfect correlation.)

The color map on the right shows a plot with some partial correlation +between the main effects and one or more 2-factor interactions, as +indicated by the grey color. The upper left 4x4 portion of the map (in +the black square) shows us that no main effect is correlated with any +other main effect. If a completely blue map (apart from the diagonal) +cannot be achieved, attempt to make the correlation between main effects +as small as possible.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/3-6-Prediction-Variance/index.html b/sites/oteguide/analyst_test_design_guide/3-6-Prediction-Variance/index.html new file mode 100644 index 00000000..72e820a3 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/3-6-Prediction-Variance/index.html @@ -0,0 +1,47 @@ +Prediction Variance

Prediction Variance

Prediction variance is a test design measure of merit which provides +information regarding the variability in the estimate of the response +variable at a particular point in the design space. It essentially +quantifies how precise the model is in estimating the true average +response. If the prediction variance is large, the true average response +value may be quite different from the model's estimate.

Prediction variance is a function of both natural system variation ( [ +σ ^2^ ) ]{.math .inline} and the structure of the experimental design. +Relative prediction variance considers only the experimental design's +influence on the prediction variance (independent of natural system +variation). Although we do not usually create predictive statistical +models at AFOTEC, this metric can still be useful because the predictive +variance is indicative of the design quality.

JMP provides graphical tools that are useful for assessing the +prediction variance of a test design. They are the " Prediction +Variance Profiler " (2D and 3D) and the " Fraction of the Design +Space " (FDS) plot.

Figure 24. Example of JMP\'s 2D Prediction Variance Profiler

+ + + image43 + +

The prediction variance profiler (figure 24) in JMP plots the relative +variance of prediction as a function of each factor level. These plots +can be used to identify combination of factor levels with high +prediction variance. It is ideal for the prediction variance to be small +throughout the design region. Generally, the prediction variance drops +as the sample size increases.

A fraction of the design space (FDS) plot (figure 25) may be created in +JMP to show what proportion of the design space has prediction variance +at or below a given level.

Figure 25. Fraction of Design Space Plot

+ + + image44 + +

The figure shows that 50% of the design region has a relative prediction +variance below 0.039. The "flatness" of the plot is an indication of the +prediction variance stability; i.e., the prediction variance does not +significantly increase in some portion of the design region. Comparing +the FDS plot for two designs side-by-side is one way to compare two +designs; the preferred design is the one with lower prediction variance +on average throughout the design space.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit/index.html b/sites/oteguide/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit/index.html new file mode 100644 index 00000000..0ef791b6 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit/index.html @@ -0,0 +1,42 @@ +Comparing Measures of Merit

Comparing Measures of Merit

JMP has created the Compare Designs platform to provide a convenient +way to compare two or three designs.

Comparing Designs in JMP

  1. From the menu above one of the design tables, launch the platform by +selecting DOE , then Design Diagnostics , then Compare +Designs (figure 26a).

  2. In the Compare Reference Design With box, select the +other designs to be compared (figure 26b).

    Figure 26a. Comparing Designs in JMP Figure 26b. Choosing Designs to Compare + + + + image45 + + + + + image46 + +

  3. In the Matching Specification Box, you can specify which columns +are equivalent (matched) in the two designs. Click the gray triangle +to reveal the Match button. Highlight a factor in each design and +click Match .

  4. Click OK in the Action box (figure 27a).

  5. Measures of Merit for all of the designs such as power (figure 27b), +prediction variance, FDS plots, and optimality efficiencies are +provided in the output.

    Figure 27a. Matching Columns of Multiple Designs Figure 27b. Comparing Power of Two Designs + + + + image47 + + + + + image48 + +

For more information on the design comparison platform, see JMP's help +documentation or contact the Test Design and Analyses Division of A-2/9.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS/index.html b/sites/oteguide/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS/index.html new file mode 100644 index 00000000..ac21f48a --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS/index.html @@ -0,0 +1,15 @@ +THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS

THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS

For many AFOTEC tests the response data has variability; i.e., if two +test runs are conducted while holding the factor levels constant, we +will likely measure two different response values. There are three basic +principles of DOE that help us compensate for, quantify, and control +variability in our response data: randomization, replication, and +blocking.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/3-9-Randomization/index.html b/sites/oteguide/analyst_test_design_guide/3-9-Randomization/index.html new file mode 100644 index 00000000..f5f9ad42 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/3-9-Randomization/index.html @@ -0,0 +1,29 @@ +Randomization

Randomization

Randomization is a principle of DOE used to average out the effects of +unknown and uncontrollable nuisance factors. Randomization refers to +both the random allocation of test material to a test run, and to the +order in which the test runs are executed. If possible, the order of +test runs should be randomized to avoid biasing the factor effect +estimates with the effects of the unknown nuisance variables.

For example, suppose we have one two-level factor of interest. Our test +is conducted over a morning and afternoon with 4 test runs in the +morning and 4 test runs in the afternoon. Suppose the temperature in the +morning is 15 degrees cooler than in the afternoon, and the response +value increases as the temperature increases. The test is not randomized +and factor level 1 is run in the morning and factor level 2 is run in +the afternoon. The test data show that the response is higher for factor +level 2 than for factor level 1. Unfortunately the test team cannot be +certain whether the increase in the response was due to changing from +factor level 1 to factor level 2, or due to the increase in the ambient +temperature from the morning to the afternoon.

If the test was randomized, the runs in the morning would involve both +factor level 1 and level 2 (and likewise for the afternoon.) Ideally the +effect of the ambient temperature will average out over each level of +the factor, and we remove its influence on the estimate of the factor +effect.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/4-1-Replication/index.html b/sites/oteguide/analyst_test_design_guide/4-1-Replication/index.html new file mode 100644 index 00000000..a6853209 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/4-1-Replication/index.html @@ -0,0 +1,25 @@ +Replication

Replication

Replication is an independent, repeated run of a factor level +combination (as opposed to measuring the result of a single test run +twice---this is a repeated measure.) Replicating factor level +combinations is the best method for obtaining an estimate of run-to-run +variability, which is often called experimental noise. An important +benefit of factorial experimentation is that there is hidden replication +in the test design. This means that even if a factorial design for k +factors is unreplicated, if one factor is determined to be +insignificant, the resulting design is a replicated design for k-1 +factors.

Since statistical analysis of test data using ANOVA +37 or linear regression involves +evaluating a ratio of an estimated factor effect to the experimental +noise, replication is important to enabling accurate analysis. While +there are methods to estimate experimental noise without replication, +these methods produce estimates that are generally inferior to those +produced by repeating factor level combinations.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/4-2-Blocking/index.html b/sites/oteguide/analyst_test_design_guide/4-2-Blocking/index.html new file mode 100644 index 00000000..c94dfea3 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/4-2-Blocking/index.html @@ -0,0 +1,60 @@ +Blocking

Blocking

Blocking is one of the fundamental principles of Design of Experiments +(DOE) that allows us to account for the variability in our response data +caused by controllable nuisance factors---factors that are not of +interest but can be controlled. In the absence of blocking, variability +caused by nuisance variables is attributed to experimental noise and may +also bias factor effect estimates; this inflates the experimental noise +estimate and makes it more difficult to determine if factors of interest +have an effect on the response variable.

During operational test, there is almost always a nuisance factor that +is a source of variability that could and should be controlled. Some +typical operational test nuisance factors are the day of the test, +shifts of operators, pilots, tail numbers, terminal/position numbers, +and ranges. These factors can impact the response variable +significantly, sometimes even more than the factors of interest.

Blocking is simply incorporating a nuisance factor into the test design +as a blocking factor. Just as with the factors of interest, the goal is +to make the blocking factor orthogonal to the other factors. If the +levels of a blocking factor are time based, such as the day of the test +or a shift of operators, then the blocking factor creates a restriction +on randomization. This is because the blocking factor level is held +constant for some period of time.

One way to add a blocking factor in JMP is through the Custom Design +Menu. Suppose we have a test with three 2-level categorical factors and +one 3-level categorical factor. If an 18 run test was planned over three +days, it may improve the analysis to block on the day of the test. Doing +so would account for the variability from nuisance factors that vary +day-to-day, such as precipitation, humidity, sunlight, and temperature. +Figure 28 shows the JMP Custom Design Menu. To add blocking factor for +Test Day, under the Factors box, select Add Factors , then +Blocking , then Other. By selecting 6 runs per block, we can +divide the 18 test runs among the three days such that all of the levels +of the factors of interest occur equally often on each day. Thus any +differences between each test day will average out across the levels of +the factors of interest. Now the estimates of the factors of interest +will be independent of any effect on the response caused by the test day +conditions. Also, the error estimate will be reduced, as the variability +associated with each test day would have been included in the error +estimate if the test was unblocked.

Figure 28. Adding Blocking Factors in JMP

+ + + image49 + +

Blocking can also be employed as a strategy to hedge against the +negative impact on analysis resulting from lost test data. The levels of +the factors of interest should be balanced across the levels of the +blocking factors; the consequence of this is that all blocks typically +contain data for every factor level. In the above example with a three +day test, if one test day was lost due to weather or an equipment +malfunction, the test runs from the other test days will still be +balanced. Also, the factors of interest will likely be less correlated +than they would be in a scenario where a random set of 6 test runs were +lost.

JMP's help files have useful information on building blocking factors +into a test design. The rule of thumb is: "Block what you know, +randomize the rest!"

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS/index.html b/sites/oteguide/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS/index.html new file mode 100644 index 00000000..68805ca7 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS/index.html @@ -0,0 +1,197 @@ +TYPICAL SITUATIONS

TYPICAL SITUATIONS

The next section covers some typical situations that may be encountered +in AFOTEC and some suggested remedies.

How do I Select a Design?

Table of commonly encountered design scenarios and possible design matches.Full Factorial2kFractional FactorialOrthogonal ArraysCovering Array/Combinatorial DesignComputer Generated Design (Optimal)Split/Strip Plot DesignsSpace Filling DesignsDemonstrationCases
Factor Considerations
All continuous factorsXXXXXX31XX
All 2-level factors (mixed continuous and/or categorical)XXXXXXXX
Mixed level factors (mixed continuous and/or categorical)XX [38](#fn38)XXXXXX
Disallowed combinationsXXXX
Modeling Considerations
Quadratic termsXX [39](#fn39)
Two-factor interaction termsXXX [40](#fn40)XXX
Three-factor or higher interaction termsXX [41](#fn41)XXXX
Response Variable Considerations
Random VariationXXXXX
DeterministicXX31XX

If all of the factors in your test have only 2-levels or are all +continuous, you can choose almost any design type. It is most desirable +to select a design with a run size that is a power of 2 (8, 16, 32, +etc.) If resource constraints prevent this, choose a D-Optimal design.

When a test involves categorical factors with more than 2 levels, it is +most common to create a full factorial or D-Optimal design. Create +several design options and compare them using the test design measures +of merit presented in this guide.

When a test involves a deterministic response, use a combinatorial +design to find factor level combinations that cause problems in the +system. If you plan to characterize the system, choose a space filling +design.

I Have Factors that Are Hard to Change

It is the rare operational test scenario where the runs in the test +event matrix can be executed in an entirely randomized order. It is +common that a group of runs involving a particular factor level must be +executed consecutively because of constraints imposed by the range, test +asset availability, or feasible tactics. It is these cases when the +design should be set up, run and analyzed using a split plot +configuration.

Split Plot designs can be created from an existing design type +(typically a computer generated design) by identifying the +hard‑to‑change factors and easy‑to‑change factors. The hard‑to‑change +factors are those that cannot be arbitrarily changed from run to run. +These factors are arranged into groups of runs called Whole Plots. Whole +Plots contain equally sized (usually) sets of runs and the levels of the +easy‑to‑change factors are randomized. Figure 29 shows a Split Plot +configuration with one hard‑to‑change and two easy‑to‑change factors.

Figure 29. Split Plot with One Hard to Change Factor

+ + + image50 + +

If there are two hard‑to‑change factors (one will be specified as +very‑hard‑to‑change and the other hard‑to‑change) the +very‑hard‑to‑change factor will determine the whole plots and the +hard‑to‑change factor will be used to create sub plots within the whole +plots. The easy‑to‑change factors will be randomized within the subplots +as shown in figure 30.

Figure 30. Split Plot with a Very Hard and Hard to Change Factor

+ + + image51 + +

The consequence of designing the test in this manner is that we can no +longer use a common estimate of error to evaluate both the +hard‑to‑change and easy‑to‑change factors. There is more variability in +the average response between the levels of the hard‑to‑change factors +than between the easy‑to‑change factor levels. Hence the power for the +hard‑to‑change factors will be lower than for the easy‑to‑change +factors. To improve the power of the hard‑to‑change factors, the test +should include multiple whole plots for each hard‑to‑change factor +level. The resulting test will be larger than if a completely randomized +design was used.

To construct a split plot design in JMP's custom designer, open the +Custom Designer tab, and enter the desired factors as usual. Under +the Changes column for the factors, change Easy to Hard . +Very Hard is used if there are two hard-to-change factors and there +will be subplots within the whole plots; the subplot factor will be +labeled Hard . Specify the desired model.

Specify the number of runs in each whole plot. Under Design +Generation , enter the Number of Whole Plots , which will +determine the number of times the levels of the Hard factor (if +there is only one hard-to-change factor) or Very Hard factor is +replicated. In figure 31 the very hard-to-change factor will have each +factor level replicated 2 times; 4 whole plots divided by 2 levels +equals 2 whole plots for each level.

Specify the Number of Subplots (if necessary because there are 2 +hard-to-change factors). Each whole plot will have 2 subplots; 8 +subplots divided by 4 whole plots equals 2 subplots per whole plot. +Ensure that analysis is done in the table created by JMP, as several +important factor properties have been changed to enable a proper +analysis.

Figure 31. Creating a Split Plot Design in JMP

+ + + image52 + +

For more specific information on the construction and analysis of Split +Plot designs, check the JMP help files or contact the Test Design and +Analyses Division of A-2/9.

Can I Combine Developmental Test and Operational Test Data?

Developmental and Operational Test data can be combined if the +developmental test is determined to be operationally representative. +During test planning, if the analyst thinks that combining developmental +test (DT) data with operational test (OT) data may be a possibility, +there are some important considerations to discuss with the DT team.

To combine any data to be used for characterization, the DT events +should have factors that correspond to the factors for the OT event. The +DT test articles must also be the "same" as the OT test articles. Any +variability caused by small changes to the SUT may be addressed with an +additional blocking variable. Another very important requirement is that +the DT events must be "operational" in nature. Lab tests, chamber tests +or table top tests are not usually operational and so cannot be +considered for combined DT/OT data.

During test planning and test design, discussion of the possibility of +combining the DT/OT data is essential to ensure that the future +combination will be feasible. Ultimately, it may not be possible to +combine the data because of the evolution of the SUT, but proper +planning will maintain the possibility. The same considerations can be +applied when planning the combination of data from Initial and Follow-on +Test & Evaluations.

There are several advantages to combining DT and OT data. First, +combining data makes the "Test-Analyze-Test" strategy viable. DT test +data can be used to determine the significant main effects so that later +in OT the test event matrix can be more focused on the relevant factors +and their interactions. Second, OT test events are usually planned and +executed for the "minimum" data needed, so DT data is an attractive way +to increase the sample size of the data for OT analysis. To obtain more +information on combining DT and OT data, contact the Test Design and +Analyses Division of A-2/9.

I Have Disallowed Combinations

One of the reasons optimal designs have skyrocketed in popularity at +AFOTEC is the ability to deal with disallowed combinations. A disallowed +combination occurs when one level of a factor cannot occur +simultaneously with a level of another factor. The JMP Custom Design +platform allows you to specify disallowed combinations using a script or +filter.

Keep in mind that if the operation/MORV in question has a large number +of disallowed combinations, you may need to make some modifications to +the test design. One solution could be to add another operation to the +COI in order to separate the factor list into two groups for separate +test events. Perhaps the factor prioritization and management may need +to be reevaluated to determine if a factor can be removed from the test. +The factors in question may not be independent enough to be separate +factors, and combining the factors into a super factor could be the best +approach. For more information on these or other techniques to avoid or +overcome disallowed combinations contact the Test Design and Analyses +Division of A-2/9.

My Power Is Too Low

You have created the test event matrix, created the power curves, and +determined that the power for either your main effects or two-factor +interactions is not sufficient. A straight-forward solution is to +increase the test size, but this is often not feasible due to resource +constraints. Another common solution is to eliminate factors. This +solution results in a less-thorough exploration of the battlespace and +could result in undetected system problems. Fortunately, there are some +other options to consider:

  • Keep the same test plan and explain why this added risk is +acceptable for the test program.

  • Split a factor into two factors: As an example, splitting a 4 level +factor into two 2 level factors will increase the estimation power +of a design without any additional runs. This can be an option for +many factors that are amalgamations of multiple factors.

  • Reexamine the likelihood and magnitude of impact for the two-factor +interactions; if some are not as important or less likely to exist, +include the important ones and remove the other interactions from +the power analysis.

  • Report the power on the main effects only and explain why the added +risk of not detecting two-factor interactions is acceptable for the +test program.

  • Make sure the categorical factors really are categorical; if factors +can be changed to continuous, the levels can be reduced to two (but +add some center points). Fewer levels will increase the power for +those factors.

  • Ask someone outside the program for their thoughts. Creating test +designs only within the test team can lead to "group think," and +external advice may provide another point of view and a solution.

Whatever the option chosen, it is important to document the rationale in +the Test and Evaluation Master Plan to keep interested parties informed. +In the end, if the power is too low and there are not any realistic +options to increase the power, it is better to report the low power and +the associated risk, than to eliminate factors which may be crucial to +the warfighter's situational awareness. For guidance on creating power +curves or power calculations in AFOTEC, see the November 2014 guide, +Power Analysis Tutorial for Experimental Design Software.

I Have Factor Levels that Depend on Other Factor Levels

The traditional nested design occurs when the levels of one factor are +similar but not identical for the levels of another factor. These types +of designs are also called hierarchical designs (Montgomery, 2013). In +operational test they might resemble figure 32.

Figure 32. Example of a Traditional Nested Design in Operational Test

+ + + image53 + +

Each aircraft has four power ports which may be used during test, but +the power port "A" on the AC-130 is different than the power ports "A" +on the A-10 and the F-15. The response variable can still be analyzed +under both factors but the analysis model must be set up differently +than a traditional ANOVA model; e.g., do not include an interaction term +between the parent and nested factor. In the design construction in JMP +change the attribute of the nested factor to "nested". Include in the +test design documentation that "Power Port" is nested within "Aircraft".

Within AFOTEC, there is a type of test design called a sub-design. As an +example, a test with a sub-design might occur when examining terrain. +Maritime terrain has sea states, while desert and mountain terrain does +not. See figure 33.

Figure 33. Example of an AFOTEC Sub-Design

+ + + image54 + +

There are two primary ways to deal with a scenario such as this one; one +approach would require a computer generated design while the second +would allow the choice of any other appropriate design type.

The design could be constructed as an optimal design with specified +disallowed combinations for the Sea State and Terrain factors. The +optimal design would then only contain runs where the Mountain/Desert +levels were paired with the Sea State = 0 level. Figure 34 shows how the +" Define Factor Constraints " box in the JMP Custom Design tool +can be used to specify disallowed combinations using a script. In the +resulting design, only the Maritime factor will have a sea state other +than 0.

Figure 34. Computer Generated Design with Disallowed Combinations

+ + + image55 + +

Another way to address the scenario would be to create a "super" factor +of Terrain and Sea State. The factor would have a level for each of the +allowed combinations of Terrain and Sea State (7 total levels.) The +super factor has seven levels, so the test size will need to increase to +obtain the same effect power that the former five level Terrain factor +had. Figure 35 shows the super factor, "Terrain" as described in this +example.

Figure 35. Super Factor to Address a Nested Factor Scenario

+ + + image56 + +

For more information on nested factors, refer to the JMP help files or +contact the Test Design and Analyses Division of A-2/9.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design/index.html b/sites/oteguide/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design/index.html new file mode 100644 index 00000000..1115e7aa --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design/index.html @@ -0,0 +1,34 @@ +Best Practices and Pitfalls in Test Design

Best Practices and Pitfalls in Test Design

Best Practices

  • When possible, make factors continuous.

  • If you use a continuous factor and you suspect a nonlinear +relationship between the factor and the response, use three levels +for the factor. Most textbooks advocate using two levels and +including center points in the design, but this assumes a sequential +test-analyze-test approach.

  • Use continuous MORVs when possible. Continuous MORVs offer several +advantages to binary MORVs. First, for the same size test, power +will be higher using a continuous MORV. Second, more information is +contained in continuous data; a continuous MORV can be turned into a +binary MORV, but the reverse is not true. If a binary/discrete MORV +is used, consider developing other continuous MORVs for power +calculations.

  • Your first design option should be a full factorial. Consider other +options only if the full factorial is infeasible or inefficient +(i.e., many more runs than required to estimate a main effect and +two-factor interaction model).

  • Create two or three test designs that meet your needs and use the +measures of merit to compare them.

  • Control the nuisance variability you know about with blocking; +average out the unknown nuisance variability with randomization.

  • Ask for help, advice or sanity checks. Even the most experienced +analyst may not have thought of the best way to do something.

Pitfalls:

  • Be cautious with disallowed combinations. If you have a lot, you may +require additional operations under a COI.

  • Don't limit your design because you believe you won't be able to +test it. Things change all the time and the capability may exist by +the time you go to test or may be developed just for your test.

  • Just because you generate a design in JMP's Custom Designer, doesn't +mean it is the optimal design! Run the design generation algorithm +several times and check multiple measures of merit.

  • Don't just turn the crank on JMP or the Test Design Suite. It is +your job to understand the output and what methods are used to +generate the results.

  • Never change a design point without re-evaluating the design's +capability to estimate the main effects and two-factor interactions.

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/4-5-Appendices/index.html b/sites/oteguide/analyst_test_design_guide/4-5-Appendices/index.html new file mode 100644 index 00000000..6c4c13ae --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/4-5-Appendices/index.html @@ -0,0 +1,10 @@ +Appendices

Appendices

Glossary
Active EffectA term used to describe a main effect (factor) or interaction that causes a statistically significant difference in the response variable when the factor levels are changed.
AliasingA condition where the effect estimate of one factor includes the influence of one or more other effects (main effect or higher-order interactions).
ANalysis Of VAriance (ANOVA)A mathematical process for evaluating the variation in data between groups and within groups in order to determine whether there is a differences between the group means. This procedure can be used to compare multiple systems, or determine if there are differences in the mean response between levels of a factor.
AugmentationThe process of strategically adding new runs to an existing test design after some data has been collected.
BalanceA column in a test design matrix is balanced if every factor level occurs an equal number of times. A test design is balanced if every possible factor level combination occurs an equal number of times.
BlockingBlocking is one of the fundamental principles of Design of Experiments (DOE) that allows us to account for the variability in our response data caused by nuisance factors—factors that are not of interest but can be controlled. Blocking factors become part of a test event matrix.
Center PointsA test run where every continuous factor is set to the value halfway between its minimum and maximum factor levels.
ConfoundingSynonymous with aliasing: a condition where the effect estimate of one factor includes the influence of one or more other effects (main effect or higher-order interactions).
CorrelationA statistical measure on a scale from -1 to 1 that indicates how close two variables are to having a linear relationship with each other. Two factors are perfectly correlated when the value of one factor’s level can be precisely determined by knowing the value of the other factor’s level.
CoverageDescribes the percentage of possible factor level combinations (after removing the disallowed combinations from the complete combination space) that a combinatorial design includes at a given strength.
DeterministicA deterministic system or model will always produce the same output from a given starting condition (level settings of the independent variables.)
Disallowed CombinationA combination of the levels of two or more factors that cannot be feasibly executed together in a test run.
DistributionA listing or function showing all the possible values of a data set and how often they occur.
EffectThe average change in a response variable produced by changing the level of a factor.
EstimationAn attempt to gain insight about an unknown population parameter based on information obtained from sample data. At AFOTEC we typically estimate means and variances of measures, factor effects, and proportions of failures.
FactorAn independent variable which may affect the performance of a system when its levels are changed
FactorialA test plan consisting of two or more factors, each with discrete possible values (or levels). A full factorial is a design whose experimental units (runs) take on all possible combinations of these levels. A design which includes a strategically selected subset of the possible combinations is called a fractional factorial.
InteractionA situation where the effect of one factor on a response depends on the level of another factor.
LevelA specific setting of a factor during a test or experiment.
Main EffectThe effect of a factor (independent variable) on a measure (dependent variable) averaging across the levels of the other factors.
Optimal DesignsA test design whose levels are combined in a way that optimizes some statistical design quality criterion that is a function of the design matrix.
OrthogonalityA test design is orthogonal if each factor can be evaluated independently of all the other factors. This is possible if, for the test runs involving any level of any factor, the levels of the other factors are present in equal amounts. When an orthogonal test design has two-level factors coded -1 and +1, the inner (dot) product of any two columns is 0.
Population ParameterA quantity or statistical measure that for a given population is fixed, such as a mean or a variance. The parameter is used in some general distribution or frequency function (e.g., a Normal Distribution) to make it descriptive of that population.
Prior DistributionThe probability distribution that expresses beliefs about an unknown quantity before testing takes place. Within AFOTEC this distribution could be based on the performance of a similar system, the performance of a previous version of a system, or SME knowledge.
Posterior DistributionThe conditional probability distribution that describes an unknown quantity after test or experimental data is taken into account.
ProjectionA property of factorial designs where the degree of replication doubles when a design column is removed (such as when a factor is determined to be insignificant). With fractional factorial designs the degree of fractionation is reduced.
QualitativeA term used to describe data that is descriptive or subjective; the values are ordinal or nominal in nature; e.g., red, blue and green.
QuantitativeA term used to describe data that is measured on a numeric or quantitative scale; interval and ratio scales are quantitative. The data may be discrete or continuous.
RandomizationA principle of DOE used to average out the effects of unknown and uncontrollable nuisance factors.
RegressionA statistical process to model the change in the mean value of a continuous dependent variable (e.g., measure) as the values of one or more continuous independent variables change.
ReplicationReplication is an independent, repeated run of a factor level combination (as opposed to measuring the result of a single test run twice—this is a repeated measure.) In JMP, requesting one replicate will create a design with two of each design point.
ResolutionAn indication of the ability to independently estimate main effects and interactions in a fractional factorial design.
RunOne combination of factor levels used for collecting data on one or more measures; a test design point.
SampleA set of data collected from a population. In operational test, it is usually impossible to test the entire population of a new system, so a sample is tested.
Screening DesignsDesigns that focus on the identification of active main effects. The goal is to reduce an initially large list of potential factors to only those that are influential on the response variable. Using screening designs decreases the size of subsequent tests conducted to estimate two-factor interactions or higher-order effects.
Sparsity-of-Effects PrincipleThe principle that a system is usually dominated by main effects and low-order interactions. Thus it is very likely that main effects (single factor) and two-factor interactions are the only significant effects when analyzing data from a test; higher-order interactions such as three-factor interactions are very rare.
StochasticRandomly determined; Any process or system that has a random probability distribution or pattern which may be analyzed statistically, but not predicted perfectly.
StrengthAn integer between 2 and the total number of factors in the test design. For combinatorial designs, strength t means that for every possible subset of t factors, every possible t-tuple of level combinations is present in the design at least one time.
t-tuple

A combination of the levels of t factors selected from a design. Suppose there is a design with four two-level factors with levels coded as +1 and -1.

There are four possible 2-tuples, e.g. (+1,-1).

There are eight possible 3-tuples, e.g. (+1,-1,+1).

There are sixteen possible 4-tuples, e.g. (+1,-1,+1,+1).

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/4-6-Test-Design-Guidance/index.html b/sites/oteguide/analyst_test_design_guide/4-6-Test-Design-Guidance/index.html new file mode 100644 index 00000000..dd7c6e10 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/4-6-Test-Design-Guidance/index.html @@ -0,0 +1,21 @@ +Test Design Guidance

Test Design Guidance

The following documents have more information and guidance from the +Department of Defense and the Air Force on the use of Design of +Experiments in OT&E. They are all accessible on the AFOTEC SharePoint or +in the AFOTEC Analyst and Engineer Community.

  • MOA between the service Operational Test Agencies (ATEC, OPTEVFOR, +AFOTEC, JTIC and DOT&E), 20 Feb 09, Using Design of Experiments for +Operational Test and Evaluation

  • OSD DOT&E Memo, 19 Oct 10, Guidance on the use of Design of +Experiments (DOE) in Operational Test and Evaluation

  • OSD DOT&E Memo, 23 Jul 13, Best Practices for Assessing the +Statistical Adequacy of Experimental Designs Used in Operational +Test and Evaluation

  • "AFOTEC OT&E Guide," Apr 20

  • Institute for Defense Analyses paper, Nov 14, Power Analysis +Tutorial for Experimental Design Software

  • AFOTEC Operational Test Information File, 17 Feb 15, Statistical +Power for Test Designs

  • DODI 5000.02, Operation of the Defense Acquisition System , 7 Jan +15

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/4-7-Technical-References-and-Citations/index.html b/sites/oteguide/analyst_test_design_guide/4-7-Technical-References-and-Citations/index.html new file mode 100644 index 00000000..05400867 --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/4-7-Technical-References-and-Citations/index.html @@ -0,0 +1,42 @@ +Technical References and Citations

Technical References and Citations

Best Practices for Assessing the Statistical +Adequacy of Experimental Designs Used in Operational Test and +Evaluation. Washington, D.C.: OSD.Freeman, L. J., Johnson, T. H., & +Simpson, J. R. (2014).

Power Analysis Tutorial for Experimental Design +Software. Alexandria, Virginia: INSTITUTE FOR DEFENSE ANALYSES.Hartman, +M. (2014, August 19).

Test Design Comparison and Slection Method Best +Practice. Retrieved March 3, 2015, from AFIT STAT COE: +http://www.afit.edu/docs/Test%20Design%20Comparison%20and%20Selection-Best%20Practice.pdfKacker,

R. N., Kuhn, R. D., & Lawrence, J. F. (2013). Combinatorial testing for +software: An adaptation of design of experiments.

Measurement, 46 (9), +3745-3752.Kruschke, J. K. (2012, May 31).

Bayesian Estimation +supercedes the t test. Retrieved March 17, 2015, from Indiana +University, Bloomington: +http://www.indiana.edu/\~kruschke/BEST/BEST.pdfKuhn, K. L. (2010).

Practical Combinatorial Testing. NIST, U.S. Department of +Commerce.Montgomery, D. C. (2009).

Design and Analysis of Experiments, +7th Edition. New York: Wiley and Sons.Myers, M. A.-C. (2009).

Response +Surface Methodology. Hoboken, NJ: John Wiley & Sons, Inc.NIST1. (n.d.).

Engineering Statistics Handbook . Retrieved from +http://math.nist.gov/coveringarrays/coveringarray.htmlNIST2. (n.d.).

Engineering Statistics Handbook . Retrieved from What are John\'s 3/4 +fractional factorial designs?: +http://www.itl.nist.gov/div898/handbook/pri/section5/pri57.htmNIST3. +(n.d.).

Plackett-Burman Designs . Retrieved from Engineering +Statistics Handbook: +http://www.itl.nist.gov/div898/handbook/pri/section3/pri335.htmNIST4. +(n.d.).

Central Composite Designs (CCD) . Retrieved from Engineering +Statistics Handbook: +http://www.itl.nist.gov/div898/handbook/pri/section3/pri3361.htmOrtiz, +F. (2014).

Dealing with Categorical Data Types in a Designed Experiment +Part II: Sizing a Designed Experiment when Using a Binary Response. +Retrieved March 3, 2015, from AFIT STAT COE: +http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdfRosenbaum, +P. R. (2002).

Observational Studies Second Edition. New York: +Springer-Verlag Inc. .Winkler, R. L. (2003).

An Introduction to +Bayesian Inference and Decision, 2nd Edition. Gainsville, FL: +Probabalistic Publishing (www.decisions-books.com).

\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/4-8-Footnotes/index.html b/sites/oteguide/analyst_test_design_guide/4-8-Footnotes/index.html new file mode 100644 index 00000000..840732da --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/4-8-Footnotes/index.html @@ -0,0 +1,97 @@ +Footnotes

Footnotes

fn1

  1. Quantitative -- A term used to describe data that is measured on a +numeric or quantitative scale; interval and ratio scales are +quantitative. The data may be discrete or continuous.

fn2

  1. Qualitative -- A term used to describe data that is descriptive or +subjective; the values are ordinal or nominal in nature; e.g., red, +blue and green.

fn3

  1. Population parameter -- A quantity or statistical measure that for a +given population is fixed, such as a mean or a variance. The +parameter is used in some general distribution or frequency function +(e.g., a Normal Distribution) to make it descriptive of that +population.

fn4

  1. Estimation -- An attempt to gain insight about an unknown population +parameter based on information obtained from sample data. At AFOTEC +we typically estimate means and variances of measures, factor +effects, and proportions of failures.

fn5

  1. Sample -- A set of data collected from a population.

fn6

  1. Factor -- An independent variable which may affect the performance +of a system when its levels are changed.

fn7

  1. Level -- A specific setting of a factor during a test or experiment.

fn8

  1. Run -- One combination of factor levels used for collecting data on +one or more measures; a test design point.

fn9

  1. Effect - The average change in a response variable produced by +changing the level of a factor.

fn10

  1. Main Effect - The effect of a factor (independent variable) on a +measure (dependent variable) averaging across the levels of the +other factors.

fn11

  1. Interaction -- A situation where the effect of one factor on a +response depends on the level of another factor.

fn12

  1. Factorial Design -- A test plan consisting of two or more factors, +each with discrete possible values (or levels). A full factorial is +a design whose experimental units (runs) take on all possible +combinations of these levels. A design which includes a +strategically selected subset of the possible combinations is called +a fractional factorial.

fn13

  1. Balance -- A column in a test design matrix is balanced if every +factor level occurs an equal number of times. A test design is +balanced if every possible factor level combination occurs an equal +number of times.

fn14

  1. Orthogonal - A test design is orthogonal if each factor can be +evaluated independently of all the other factors. This is possible +if, for the test runs involving any level of any factor, the levels +of the other factors are present in equal amounts. When an +orthogonal test design has two-level factors coded -1 and +1, the +inner (dot) product of any two columns is 0.

fn15

  1. Disallowed Combinations - A combination of the levels of two or more +factors that cannot be feasibly executed together in a test run.

fn16

  1. Center Point -- A test run where every continuous factor is set to +the value halfway between its minimum and maximum factor levels.

fn17

  1. Projection -- A property of factorial designs where the degree of +replication doubles when a design column is removed (such as when a +factor is determined to be insignificant). With fractional factorial +designs the degree of fractionation is reduced.

fn18

  1. Active Effect -- A term used to describe a main effect (factor) or +interaction that causes a statistically significant difference in +the response variable when the factor levels are changed.

fn19

  1. Sparsity-of-Effects Principle -- The principle that a system is +usually dominated by main effects and low-order interactions. Thus +it is very likely that main effects (single factor) and two-factor +interactions are the only significant effects when analyzing data +from a test; higher-order interactions such as three-factor +interactions are very rare.

fn20

  1. Correlation -- A statistical measure on a scale from -1 to 1 that +indicates how close two variables are to having a linear +relationship with each other. Two factors are perfectly correlated +when the value of one factor's level can be precisely determined by +knowing the value of the other factor's level.

fn21

  1. Aliasing - A condition where the effect estimate of one factor +includes the influence of one or more other effects (main effect or +higher-order interactions).

fn22

  1. Confounding -- Synonymous with aliasing: a condition where the +effect estimate of one factor includes the influence of one or more +other effects (main effect or higher-order interactions).

fn23

  1. Resolution -- An indication of the ability to independently estimate +main effects and interactions in a fractional factorial design.

fn24

  1. Screening design -- Designs that focus on the identification of +active main effects. The goal is to reduce an initially large list +of potential factors to only those that are influential on the +response variable. Using screening designs decreases the size of +subsequent test designs used to estimate two factor interactions or +higher-order effects.

fn25

  1. Optimal Designs -- A test design whose levels are combined in a way +that optimizes some statistical design quality criterion that is a +function of the design matrix.

fn26

  1. Linear Regression -- A statistical process to model the change in +the mean value of a continuous dependent variable (e.g., measure) as +the values of one or more continuous independent variables change.

fn27

  1. Augmentation -- The process of strategically adding new runs to an +existing test design after some data has been collected.

fn28

  1. Deterministic -- A deterministic system or model will always produce +the same output from a given starting condition (level settings of +the independent variables.)

fn29

  1. Distribution -- A table or function showing all the possible values +of a data set and how often they occur.

fn30

  1. t -tuples - A combination of the levels of t factors selected from +a design. Suppose there is a design with four two-level factors with +levels coded as +1 and -1. There are four possible 2-tuples, e.g. +(+1,-1). There are eight possible 3-tuples, e.g. (+1,-1,+1). There +are sixteen possible 4-tuples, e.g. (+1,-1,+1,+1).

fn31

  1. Strength - An integer between 2 and the total number of factors in +the test design. For combinatorial designs, strength t means that +for every possible subset of t factors, every possible t -tuple of +level combinations is present in the design at least one time.

fn32

  1. Coverage - Describes the percentage of possible factor level +combinations (after removing the disallowed combinations from the +complete combination space) that a combinatorial design includes at +a given strength.

fn33

  1. Stochastic - Randomly determined; any process or system that has a +random probability distribution or pattern which may be analyzed +statistically, but not predicted perfectly.

fn34

  1. D-Efficiency is calculated as follows: = 100 \times \left( \frac{\left| X^{'}X \right|^{\frac{1}{p}}}{N} \right) where p is the number of columns in X matrix and N +is the number of runs.

fn35

  1. G-Efficiency is calculated as follows: = 100 \times \left( \frac{\sqrt{\frac{p}{N}}}{\sigma\_{M}} \right) where p is the number of columns in X matrix, N is the +number of runs and [ σ ~M~ ]{.math .inline} is the maximum +standard error for prediction across the space. The X matrix is the +de-correlated X matrix.

fn36

  1. A-Efficiency is calculated as follows: = 100 \times \left( \frac{p}{\text{trace}\left( N \times \left( X^{'}X \right)^{- 1} \right)} \right) where p is the +number of columns in X matrix and N is the number of runs. The X +matrix is the de-correlated X matrix.

fn37

  1. ANOVA -- A mathematical process for evaluating the variation in data +between groups and within groups in order to determine whether there +is a differences between the group means. This procedure can be used +to compare multiple systems, or determine if there are differences +in the mean response between levels of a factor.

fn38

  1. An orthogonal array may not exist for the required number of factors +and levels ↩︎

fn39

  1. All factors must be continuous

fn40

  1. Strength 4 and higher

fn41

  1. Resolution VI or higher is required to analyze 3 factor interactions
\ No newline at end of file diff --git a/sites/oteguide/analyst_test_design_guide/index.html b/sites/oteguide/analyst_test_design_guide/index.html new file mode 100644 index 00000000..0d4d248f --- /dev/null +++ b/sites/oteguide/analyst_test_design_guide/index.html @@ -0,0 +1,10 @@ +Analyst Test Design Guide

Analyst Test Design Guide

Last Updated/Reviewed: 08 December 2020

Originating Office: AFOTEC A-2/9

\ No newline at end of file diff --git a/sites/oteguide/app-eec04d2f552ddc7b4bf2.js b/sites/oteguide/app-03e333c274b6bc210459.js similarity index 83% rename from sites/oteguide/app-eec04d2f552ddc7b4bf2.js rename to sites/oteguide/app-03e333c274b6bc210459.js index 8c16dcad..17b63271 100644 --- a/sites/oteguide/app-eec04d2f552ddc7b4bf2.js +++ b/sites/oteguide/app-03e333c274b6bc210459.js @@ -1,3 +1,3 @@ -/*! For license information please see app-eec04d2f552ddc7b4bf2.js.LICENSE.txt */ -(window.webpackJsonp=window.webpackJsonp||[]).push([[3],{"+ZDr":function(e,t,n){"use strict";var r=n("TqRt");t.__esModule=!0,t.withPrefix=m,t.withAssetPrefix=function(e){return m(e,g())},t.navigateTo=t.replace=t.push=t.navigate=t.default=void 0;var a=r(n("8OQS")),i=r(n("PJYZ")),o=r(n("VbXa")),s=r(n("pVnL")),c=r(n("17x9")),l=r(n("q1tI")),u=n("YwZP"),d=n("LYrO"),p=n("cu4x");t.parsePath=p.parsePath;var f=function(e){return null==e?void 0:e.startsWith("/")};function m(e,t){var n,r;if(void 0===t&&(t=h()),!y(e))return e;if(e.startsWith("./")||e.startsWith("../"))return e;var a=null!==(n=null!==(r=t)&&void 0!==r?r:g())&&void 0!==n?n:"/";return""+((null==a?void 0:a.endsWith("/"))?a.slice(0,-1):a)+(e.startsWith("/")?e:"/"+e)}var g=function(){return""},h=function(){return""},y=function(e){return e&&!e.startsWith("http://")&&!e.startsWith("https://")&&!e.startsWith("//")};var b=function(e,t){return"number"==typeof e?e:y(e)?f(e)?m(e):function(e,t){return f(e)?e:(0,d.resolve)(e,t)}(e,t):e},S={activeClassName:c.default.string,activeStyle:c.default.object,partiallyActive:c.default.bool};function A(e){return l.default.createElement(u.Location,null,(function(t){var n=t.location;return l.default.createElement(v,(0,s.default)({},e,{_location:n}))}))}var v=function(e){function t(t){var n;(n=e.call(this,t)||this).defaultGetProps=function(e){var t=e.isPartiallyCurrent,r=e.isCurrent;return(n.props.partiallyActive?t:r)?{className:[n.props.className,n.props.activeClassName].filter(Boolean).join(" "),style:(0,s.default)({},n.props.style,n.props.activeStyle)}:null};var r=!1;return"undefined"!=typeof window&&window.IntersectionObserver&&(r=!0),n.state={IOSupported:r},n.handleRef=n.handleRef.bind((0,i.default)(n)),n}(0,o.default)(t,e);var n=t.prototype;return n._prefetch=function(){var e=window.location.pathname;this.props._location&&this.props._location.pathname&&(e=this.props._location.pathname);var t=b(this.props.to,e),n=(0,p.parsePath)(t).pathname;e!==n&&___loader.enqueue(n)},n.componentDidUpdate=function(e,t){this.props.to===e.to||this.state.IOSupported||this._prefetch()},n.componentDidMount=function(){this.state.IOSupported||this._prefetch()},n.componentWillUnmount=function(){if(this.io){var e=this.io,t=e.instance,n=e.el;t.unobserve(n),t.disconnect()}},n.handleRef=function(e){var t,n,r,a=this;this.props.innerRef&&this.props.innerRef.hasOwnProperty("current")?this.props.innerRef.current=e:this.props.innerRef&&this.props.innerRef(e),this.state.IOSupported&&e&&(this.io=(t=e,n=function(){a._prefetch()},(r=new window.IntersectionObserver((function(e){e.forEach((function(e){t===e.target&&(e.isIntersecting||e.intersectionRatio>0)&&(r.unobserve(t),r.disconnect(),n())}))}))).observe(t),{instance:r,el:t}))},n.render=function(){var e=this,t=this.props,n=t.to,r=t.getProps,i=void 0===r?this.defaultGetProps:r,o=t.onClick,c=t.onMouseEnter,d=(t.activeClassName,t.activeStyle,t.innerRef,t.partiallyActive,t.state),f=t.replace,m=t._location,g=(0,a.default)(t,["to","getProps","onClick","onMouseEnter","activeClassName","activeStyle","innerRef","partiallyActive","state","replace","_location"]);var h=b(n,m.pathname);return y(h)?l.default.createElement(u.Link,(0,s.default)({to:h,state:d,getProps:i,innerRef:this.handleRef,onMouseEnter:function(e){c&&c(e),___loader.hovering((0,p.parsePath)(h).pathname)},onClick:function(t){if(o&&o(t),!(0!==t.button||e.props.target||t.defaultPrevented||t.metaKey||t.altKey||t.ctrlKey||t.shiftKey)){t.preventDefault();var n=f,r=encodeURI(h)===m.pathname;"boolean"!=typeof f&&r&&(n=!0),window.___navigate(h,{state:d,replace:n})}return!0}},g)):l.default.createElement("a",(0,s.default)({href:h},g))},t}(l.default.Component);v.propTypes=(0,s.default)({},S,{onClick:c.default.func,to:c.default.string.isRequired,replace:c.default.bool,state:c.default.object});var C=function(e,t,n){return console.warn('The "'+e+'" method is now deprecated and will be removed in Gatsby v'+n+'. Please use "'+t+'" instead.')},O=l.default.forwardRef((function(e,t){return l.default.createElement(A,(0,s.default)({innerRef:t},e))}));t.default=O;t.navigate=function(e,t){window.___navigate(b(e,window.location.pathname),t)};var T=function(e){C("push","navigate",3),window.___push(b(e,window.location.pathname))};t.push=T;t.replace=function(e){C("replace","navigate",3),window.___replace(b(e,window.location.pathname))};t.navigateTo=function(e){return C("navigateTo","navigate",3),T(e)}},"/hTd":function(e,t,n){"use strict";t.__esModule=!0,t.SessionStorage=void 0;var r=function(){function e(){}var t=e.prototype;return t.read=function(e,t){var n=this.getStateKey(e,t);try{var r=window.sessionStorage.getItem(n);return r?JSON.parse(r):0}catch(a){return window&&window.___GATSBY_REACT_ROUTER_SCROLL&&window.___GATSBY_REACT_ROUTER_SCROLL[n]?window.___GATSBY_REACT_ROUTER_SCROLL[n]:0}},t.save=function(e,t,n){var r=this.getStateKey(e,t),a=JSON.stringify(n);try{window.sessionStorage.setItem(r,a)}catch(i){window&&window.___GATSBY_REACT_ROUTER_SCROLL||(window.___GATSBY_REACT_ROUTER_SCROLL={}),window.___GATSBY_REACT_ROUTER_SCROLL[r]=JSON.parse(a)}},t.getStateKey=function(e,t){var n="@@scroll|"+e.pathname;return null==t?n:n+"|"+t},e}();t.SessionStorage=r},"284h":function(e,t,n){var r=n("cDf5").default;function a(){if("function"!=typeof WeakMap)return null;var e=new WeakMap;return a=function(){return e},e}e.exports=function(e){if(e&&e.__esModule)return e;if(null===e||"object"!==r(e)&&"function"!=typeof e)return{default:e};var t=a();if(t&&t.has(e))return t.get(e);var n={},i=Object.defineProperty&&Object.getOwnPropertyDescriptor;for(var o in e)if(Object.prototype.hasOwnProperty.call(e,o)){var s=i?Object.getOwnPropertyDescriptor(e,o):null;s&&(s.get||s.set)?Object.defineProperty(n,o,s):n[o]=e[o]}return n.default=e,t&&t.set(e,n),n},e.exports.default=e.exports,e.exports.__esModule=!0},"2mql":function(e,t,n){"use strict";var r=n("TOwV"),a={childContextTypes:!0,contextType:!0,contextTypes:!0,defaultProps:!0,displayName:!0,getDefaultProps:!0,getDerivedStateFromError:!0,getDerivedStateFromProps:!0,mixins:!0,propTypes:!0,type:!0},i={name:!0,length:!0,prototype:!0,caller:!0,callee:!0,arguments:!0,arity:!0},o={$$typeof:!0,compare:!0,defaultProps:!0,displayName:!0,propTypes:!0,type:!0},s={};function c(e){return r.isMemo(e)?o:s[e.$$typeof]||a}s[r.ForwardRef]={$$typeof:!0,render:!0,defaultProps:!0,displayName:!0,propTypes:!0},s[r.Memo]=o;var l=Object.defineProperty,u=Object.getOwnPropertyNames,d=Object.getOwnPropertySymbols,p=Object.getOwnPropertyDescriptor,f=Object.getPrototypeOf,m=Object.prototype;e.exports=function e(t,n,r){if("string"!=typeof n){if(m){var a=f(n);a&&a!==m&&e(t,a,r)}var o=u(n);d&&(o=o.concat(d(n)));for(var s=c(t),g=c(n),h=0;h0&&e[n-1]===t?e:e.concat(t)},p=function(e,t){var n=e.plain,r=Object.create(null),a=e.styles.reduce((function(e,n){var r=n.languages,a=n.style;return r&&!r.includes(t)||n.types.forEach((function(t){var n=c({},e[t],a);e[t]=n})),e}),r);return a.root=n,a.plain=c({},n,{backgroundColor:null}),a};function f(e,t){var n={};for(var r in e)Object.prototype.hasOwnProperty.call(e,r)&&-1===t.indexOf(r)&&(n[r]=e[r]);return n}var m=function(e){function t(){for(var t=this,n=[],r=arguments.length;r--;)n[r]=arguments[r];e.apply(this,n),s(this,"getThemeDict",(function(e){if(void 0!==t.themeDict&&e.theme===t.prevTheme&&e.language===t.prevLanguage)return t.themeDict;t.prevTheme=e.theme,t.prevLanguage=e.language;var n=e.theme?p(e.theme,e.language):void 0;return t.themeDict=n})),s(this,"getLineProps",(function(e){var n=e.key,r=e.className,a=e.style,i=c({},f(e,["key","className","style","line"]),{className:"token-line",style:void 0,key:void 0}),o=t.getThemeDict(t.props);return void 0!==o&&(i.style=o.plain),void 0!==a&&(i.style=void 0!==i.style?c({},i.style,a):a),void 0!==n&&(i.key=n),r&&(i.className+=" "+r),i})),s(this,"getStyleForToken",(function(e){var n=e.types,r=e.empty,a=n.length,i=t.getThemeDict(t.props);if(void 0!==i){if(1===a&&"plain"===n[0])return r?{display:"inline-block"}:void 0;if(1===a&&!r)return i[n[0]];var o=r?{display:"inline-block"}:{},s=n.map((function(e){return i[e]}));return Object.assign.apply(Object,[o].concat(s))}})),s(this,"getTokenProps",(function(e){var n=e.key,r=e.className,a=e.style,i=e.token,o=c({},f(e,["key","className","style","token"]),{className:"token "+i.types.join(" "),children:i.content,style:t.getStyleForToken(i),key:void 0});return void 0!==a&&(o.style=void 0!==o.style?c({},o.style,a):a),void 0!==n&&(o.key=n),r&&(o.className+=" "+r),o})),s(this,"tokenize",(function(e,t,n,r){var a={code:t,grammar:n,language:r,tokens:[]};e.hooks.run("before-tokenize",a);var i=a.tokens=e.tokenize(a.code,a.grammar,a.language);return e.hooks.run("after-tokenize",a),i}))}return e&&(t.__proto__=e),t.prototype=Object.create(e&&e.prototype),t.prototype.constructor=t,t.prototype.render=function(){var e=this.props,t=e.Prism,n=e.language,r=e.code,a=e.children,i=this.getThemeDict(this.props),o=t.languages[n];return a({tokens:function(e){for(var t=[[]],n=[e],r=[0],a=[e.length],i=0,o=0,s=[],c=[s];o>-1;){for(;(i=r[o]++)0?f:["plain"],p=m):(f=d(f,m.type),m.alias&&(f=d(f,m.alias)),p=m.content),"string"==typeof p){var g=p.split(l),h=g.length;s.push({types:f,content:g[0]});for(var y=1;y>>0,1)},emit:function(t,n){(e[t]||[]).slice().map((function(e){e(n)})),(e["*"]||[]).slice().map((function(e){e(t,n)}))}}}();t.a=r},"7hJ6":function(e,t,n){"use strict";t.__esModule=!0,t.useScrollRestoration=t.ScrollContainer=t.ScrollContext=void 0;var r=n("Enzk");t.ScrollContext=r.ScrollHandler;var a=n("hd9s");t.ScrollContainer=a.ScrollContainer;var i=n("3uz+");t.useScrollRestoration=i.useScrollRestoration},"7ljp":function(e,t,n){"use strict";n.r(t),n.d(t,"MDXContext",(function(){return u})),n.d(t,"MDXProvider",(function(){return f})),n.d(t,"mdx",(function(){return h})),n.d(t,"useMDXComponents",(function(){return p})),n.d(t,"withMDXComponents",(function(){return d}));var r=n("q1tI"),a=n.n(r);function i(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function o(){return(o=Object.assign||function(e){for(var t=1;t=0||(a[n]=e[n]);return a}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(a[n]=e[n])}return a}var u=a.a.createContext({}),d=function(e){return function(t){var n=p(t.components);return a.a.createElement(e,o({},t,{components:n}))}},p=function(e){var t=a.a.useContext(u),n=t;return e&&(n="function"==typeof e?e(t):c(c({},t),e)),n},f=function(e){var t=p(e.components);return a.a.createElement(u.Provider,{value:t},e.children)},m={inlineCode:"code",wrapper:function(e){var t=e.children;return a.a.createElement(a.a.Fragment,{},t)}},g=a.a.forwardRef((function(e,t){var n=e.components,r=e.mdxType,i=e.originalType,o=e.parentName,s=l(e,["components","mdxType","originalType","parentName"]),u=p(n),d=r,f=u["".concat(o,".").concat(d)]||u[d]||m[d]||i;return n?a.a.createElement(f,c(c({ref:t},s),{},{components:n})):a.a.createElement(f,c({ref:t},s))}));function h(e,t){var n=arguments,r=t&&t.mdxType;if("string"==typeof e||r){var i=n.length,o=new Array(i);o[0]=g;var s={};for(var c in t)hasOwnProperty.call(t,c)&&(s[c]=t[c]);s.originalType=e,s.mdxType="string"==typeof e?e:r,o[1]=s;for(var l=2;l=0||(a[n]=e[n]);return a},e.exports.default=e.exports,e.exports.__esModule=!0},"94VI":function(e,t){t.polyfill=function(e){return e}},"9Xx/":function(e,t,n){"use strict";n.d(t,"c",(function(){return c})),n.d(t,"d",(function(){return l})),n.d(t,"a",(function(){return i})),n.d(t,"b",(function(){return o}));var r=Object.assign||function(e){for(var t=1;t1&&void 0!==arguments[1]?arguments[1]:{},l=c.state,u=c.replace,d=void 0!==u&&u;if("number"==typeof t)e.history.go(t);else{l=r({},l,{key:Date.now()+""});try{o||d?e.history.replaceState(l,null,t):e.history.pushState(l,null,t)}catch(f){e.location[d?"replace":"assign"](t)}}i=a(e),o=!0;var p=new Promise((function(e){return s=e}));return n.forEach((function(e){return e({location:i,action:"PUSH"})})),p}}},o=function(){var e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:"/",t=e.indexOf("?"),n={pathname:t>-1?e.substr(0,t):e,search:t>-1?e.substr(t):""},r=0,a=[n],i=[null];return{get location(){return a[r]},addEventListener:function(e,t){},removeEventListener:function(e,t){},history:{get entries(){return a},get index(){return r},get state(){return i[r]},pushState:function(e,t,n){var o=n.split("?"),s=o[0],c=o[1],l=void 0===c?"":c;r++,a.push({pathname:s,search:l.length?"?"+l:l}),i.push(e)},replaceState:function(e,t,n){var o=n.split("?"),s=o[0],c=o[1],l=void 0===c?"":c;a[r]={pathname:s,search:l},i[r]=e},go:function(e){var t=r+e;t<0||t>i.length-1||(r=t)}}}},s=!("undefined"==typeof window||!window.document||!window.document.createElement),c=i(s?window:o()),l=c.navigate},"9uj6":function(e,t,n){"use strict";var r=n("4qRI"),a=/^((children|dangerouslySetInnerHTML|key|ref|autoFocus|defaultValue|defaultChecked|innerHTML|suppressContentEditableWarning|suppressHydrationWarning|valueLink|accept|acceptCharset|accessKey|action|allow|allowUserMedia|allowPaymentRequest|allowFullScreen|allowTransparency|alt|async|autoComplete|autoPlay|capture|cellPadding|cellSpacing|challenge|charSet|checked|cite|classID|className|cols|colSpan|content|contentEditable|contextMenu|controls|controlsList|coords|crossOrigin|data|dateTime|decoding|default|defer|dir|disabled|disablePictureInPicture|download|draggable|encType|form|formAction|formEncType|formMethod|formNoValidate|formTarget|frameBorder|headers|height|hidden|high|href|hrefLang|htmlFor|httpEquiv|id|inputMode|integrity|is|keyParams|keyType|kind|label|lang|list|loading|loop|low|marginHeight|marginWidth|max|maxLength|media|mediaGroup|method|min|minLength|multiple|muted|name|nonce|noValidate|open|optimum|pattern|placeholder|playsInline|poster|preload|profile|radioGroup|readOnly|referrerPolicy|rel|required|reversed|role|rows|rowSpan|sandbox|scope|scoped|scrolling|seamless|selected|shape|size|sizes|slot|span|spellCheck|src|srcDoc|srcLang|srcSet|start|step|style|summary|tabIndex|target|title|type|useMap|value|width|wmode|wrap|about|datatype|inlist|prefix|property|resource|typeof|vocab|autoCapitalize|autoCorrect|autoSave|color|inert|itemProp|itemScope|itemType|itemID|itemRef|on|results|security|unselectable|accentHeight|accumulate|additive|alignmentBaseline|allowReorder|alphabetic|amplitude|arabicForm|ascent|attributeName|attributeType|autoReverse|azimuth|baseFrequency|baselineShift|baseProfile|bbox|begin|bias|by|calcMode|capHeight|clip|clipPathUnits|clipPath|clipRule|colorInterpolation|colorInterpolationFilters|colorProfile|colorRendering|contentScriptType|contentStyleType|cursor|cx|cy|d|decelerate|descent|diffuseConstant|direction|display|divisor|dominantBaseline|dur|dx|dy|edgeMode|elevation|enableBackground|end|exponent|externalResourcesRequired|fill|fillOpacity|fillRule|filter|filterRes|filterUnits|floodColor|floodOpacity|focusable|fontFamily|fontSize|fontSizeAdjust|fontStretch|fontStyle|fontVariant|fontWeight|format|from|fr|fx|fy|g1|g2|glyphName|glyphOrientationHorizontal|glyphOrientationVertical|glyphRef|gradientTransform|gradientUnits|hanging|horizAdvX|horizOriginX|ideographic|imageRendering|in|in2|intercept|k|k1|k2|k3|k4|kernelMatrix|kernelUnitLength|kerning|keyPoints|keySplines|keyTimes|lengthAdjust|letterSpacing|lightingColor|limitingConeAngle|local|markerEnd|markerMid|markerStart|markerHeight|markerUnits|markerWidth|mask|maskContentUnits|maskUnits|mathematical|mode|numOctaves|offset|opacity|operator|order|orient|orientation|origin|overflow|overlinePosition|overlineThickness|panose1|paintOrder|pathLength|patternContentUnits|patternTransform|patternUnits|pointerEvents|points|pointsAtX|pointsAtY|pointsAtZ|preserveAlpha|preserveAspectRatio|primitiveUnits|r|radius|refX|refY|renderingIntent|repeatCount|repeatDur|requiredExtensions|requiredFeatures|restart|result|rotate|rx|ry|scale|seed|shapeRendering|slope|spacing|specularConstant|specularExponent|speed|spreadMethod|startOffset|stdDeviation|stemh|stemv|stitchTiles|stopColor|stopOpacity|strikethroughPosition|strikethroughThickness|string|stroke|strokeDasharray|strokeDashoffset|strokeLinecap|strokeLinejoin|strokeMiterlimit|strokeOpacity|strokeWidth|surfaceScale|systemLanguage|tableValues|targetX|targetY|textAnchor|textDecoration|textRendering|textLength|to|transform|u1|u2|underlinePosition|underlineThickness|unicode|unicodeBidi|unicodeRange|unitsPerEm|vAlphabetic|vHanging|vIdeographic|vMathematical|values|vectorEffect|version|vertAdvY|vertOriginX|vertOriginY|viewBox|viewTarget|visibility|widths|wordSpacing|writingMode|x|xHeight|x1|x2|xChannelSelector|xlinkActuate|xlinkArcrole|xlinkHref|xlinkRole|xlinkShow|xlinkTitle|xlinkType|xmlBase|xmlns|xmlnsXlink|xmlLang|xmlSpace|y|y1|y2|yChannelSelector|z|zoomAndPan|for|class|autofocus)|(([Dd][Aa][Tt][Aa]|[Aa][Rr][Ii][Aa]|x)-.*))$/,i=Object(r.a)((function(e){return a.test(e)||111===e.charCodeAt(0)&&110===e.charCodeAt(1)&&e.charCodeAt(2)<91}));t.a=i},BFUG:function(e,t){e.exports="data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IEFkb2JlIElsbHVzdHJhdG9yIDIzLjAuMywgU1ZHIEV4cG9ydCBQbHVnLUluIC4gU1ZHIFZlcnNpb246IDYuMDAgQnVpbGQgMCkgIC0tPgo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkxheWVyXzEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHg9IjBweCIgeT0iMHB4IgoJIHZpZXdCb3g9IjAgMCAzNSAyNyIgc3R5bGU9ImVuYWJsZS1iYWNrZ3JvdW5kOm5ldyAwIDAgMzUgMjc7IiB4bWw6c3BhY2U9InByZXNlcnZlIj4KPHN0eWxlIHR5cGU9InRleHQvY3NzIj4KCS5zdDB7ZmlsbC1ydWxlOmV2ZW5vZGQ7Y2xpcC1ydWxlOmV2ZW5vZGQ7ZmlsbDojRkZGRkZGO30KPC9zdHlsZT4KPHBhdGggY2xhc3M9InN0MCIgZD0iTTE3LDcuMmwwLjEsMS4ybC0xLjMtMC4xYy00LjYtMC41LTguNi0yLjQtMTItNS41TDIuMSwxLjFMMS43LDIuM0MwLjgsNC44LDEuMyw3LjUsMy4yLDkuM2MxLDEsMC44LDEuMS0xLDAuNQoJQzEuNyw5LjcsMS4xLDkuNSwxLjEsOS42QzAuOSw5LjgsMS41LDExLjksMiwxMi44YzAuNywxLjIsMiwyLjQsMy41LDMuMWwxLjIsMC41bC0xLjUsMGMtMS40LDAtMS41LDAtMS4zLDAuNQoJYzAuNSwxLjUsMi41LDMuMiw0LjcsMy45bDEuNiwwLjVsLTEuNCwwLjhjLTIsMS4xLTQuNCwxLjctNi44LDEuOEMwLjksMjMuOSwwLDI0LDAsMjQuMWMwLDAuMiwzLjEsMS42LDQuOSwyLjEKCWM1LjQsMS41LDExLjgsMC45LDE2LjYtMS44YzMuNC0xLjksNi44LTUuNiw4LjQtOS4yYzAuOS0xLjksMS43LTUuNSwxLjctNy4xYzAtMS4xLDAuMS0xLjIsMS41LTIuNmMwLjgtMC44LDEuNi0xLjYsMS44LTEuOAoJYzAuMy0wLjUsMC4yLTAuNS0xLjEsMGMtMi4xLDAuNy0yLjUsMC42LTEuNC0wLjVjMC44LTAuOCwxLjctMi4xLDEuNy0yLjVjMC0wLjEtMC40LDAtMC44LDAuM2MtMC41LDAuMi0xLjUsMC42LTIuMiwwLjhsLTEuNCwwLjQKCWwtMS4yLTAuOGMtMC43LTAuNC0xLjYtMC45LTIuMS0xYy0xLjMtMC4zLTMuMy0wLjMtNC40LDAuMUMxOC44LDEuNCwxNi44LDQuMiwxNyw3LjJ6Ii8+Cjwvc3ZnPgo="},BOnt:function(e,t,n){"use strict";var r=n("TqRt"),a=n("Wbzz"),i=r(n("hqbx"));t.onClientEntry=function(e,t){void 0===t&&(t={}),(0,i.default)(window,t,(function(e){(0,a.navigate)(e)}))}},BfwJ:function(e,t,n){"use strict";n.r(t),n.d(t,"useMDXScope",(function(){return o})),n.d(t,"MDXScopeProvider",(function(){return s}));var r=n("q1tI"),a=n.n(r),i=Object(r.createContext)({}),o=function(e){var t=Object(r.useContext)(i);return e||t},s=function(e){var t=e.__mdxScope,n=e.children;return a.a.createElement(i.Provider,{value:t},n)}},Bnag:function(e,t){e.exports=function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")},e.exports.default=e.exports,e.exports.__esModule=!0},BsWD:function(e,t,n){"use strict";n.d(t,"a",(function(){return a}));var r=n("a3WO");function a(e,t){if(e){if("string"==typeof e)return Object(r.a)(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);return"Object"===n&&e.constructor&&(n=e.constructor.name),"Map"===n||"Set"===n?Array.from(e):"Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n)?Object(r.a)(e,t):void 0}}},CnBM:function(e,t,n){"use strict";var r="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Symbol&&e.constructor===Symbol&&e!==Symbol.prototype?"symbol":typeof e};function a(e,t){if(!(e instanceof t))throw new TypeError("Cannot call a class as a function")}function i(e,t){if(!e)throw new ReferenceError("this hasn't been initialised - super() hasn't been called");return!t||"object"!=typeof t&&"function"!=typeof t?e:t}function o(e,t){if("function"!=typeof t&&null!==t)throw new TypeError("Super expression must either be null or a function, not "+typeof t);e.prototype=Object.create(t&&t.prototype,{constructor:{value:e,enumerable:!1,writable:!0,configurable:!0}}),t&&(Object.setPrototypeOf?Object.setPrototypeOf(e,t):e.__proto__=t)}var s=n("q1tI"),c=n("17x9"),l=[],u=[];function d(e){var t=e(),n={loading:!0,loaded:null,error:null};return n.promise=t.then((function(e){return n.loading=!1,n.loaded=e,e})).catch((function(e){throw n.loading=!1,n.error=e,e})),n}function p(e){var t={loading:!1,loaded:{},error:null},n=[];try{Object.keys(e).forEach((function(r){var a=d(e[r]);a.loading?t.loading=!0:(t.loaded[r]=a.loaded,t.error=a.error),n.push(a.promise),a.promise.then((function(e){t.loaded[r]=e})).catch((function(e){t.error=e}))}))}catch(r){t.error=r}return t.promise=Promise.all(n).then((function(e){return t.loading=!1,e})).catch((function(e){throw t.loading=!1,e})),t}function f(e,t){return s.createElement((n=e)&&n.__esModule?n.default:n,t);var n}function m(e,t){var d,p;if(!t.loading)throw new Error("react-loadable requires a `loading` component");var m=Object.assign({loader:null,loading:null,delay:200,timeout:null,render:f,webpack:null,modules:null},t),g=null;function h(){return g||(g=e(m.loader)),g.promise}return l.push(h),"function"==typeof m.webpack&&u.push((function(){if(e=m.webpack,"object"===r(n.m)&&e().every((function(e){return void 0!==e&&void 0!==n.m[e]})))return h();var e})),p=d=function(t){function n(r){a(this,n);var o=i(this,t.call(this,r));return o.retry=function(){o.setState({error:null,loading:!0,timedOut:!1}),g=e(m.loader),o._loadModule()},h(),o.state={error:g.error,pastDelay:!1,timedOut:!1,loading:g.loading,loaded:g.loaded},o}return o(n,t),n.preload=function(){return h()},n.prototype.componentWillMount=function(){this._mounted=!0,this._loadModule()},n.prototype._loadModule=function(){var e=this;if(this.context.loadable&&Array.isArray(m.modules)&&m.modules.forEach((function(t){e.context.loadable.report(t)})),g.loading){"number"==typeof m.delay&&(0===m.delay?this.setState({pastDelay:!0}):this._delay=setTimeout((function(){e.setState({pastDelay:!0})}),m.delay)),"number"==typeof m.timeout&&(this._timeout=setTimeout((function(){e.setState({timedOut:!0})}),m.timeout));var t=function(){e._mounted&&(e.setState({error:g.error,loaded:g.loaded,loading:g.loading}),e._clearTimeouts())};g.promise.then((function(){t()})).catch((function(e){t()}))}},n.prototype.componentWillUnmount=function(){this._mounted=!1,this._clearTimeouts()},n.prototype._clearTimeouts=function(){clearTimeout(this._delay),clearTimeout(this._timeout)},n.prototype.render=function(){return this.state.loading||this.state.error?s.createElement(m.loading,{isLoading:this.state.loading,pastDelay:this.state.pastDelay,timedOut:this.state.timedOut,error:this.state.error,retry:this.retry}):this.state.loaded?m.render(this.state.loaded,this.props):null},n}(s.Component),d.contextTypes={loadable:c.shape({report:c.func.isRequired})},p}function g(e){return m(d,e)}g.Map=function(e){if("function"!=typeof e.render)throw new Error("LoadableMap requires a `render(loaded, props)` function");return m(p,e)};var h=function(e){function t(){return a(this,t),i(this,e.apply(this,arguments))}return o(t,e),t.prototype.getChildContext=function(){return{loadable:{report:this.props.report}}},t.prototype.render=function(){return s.Children.only(this.props.children)},t}(s.Component);function y(e){for(var t=[];e.length;){var n=e.pop();t.push(n())}return Promise.all(t).then((function(){if(e.length)return y(e)}))}h.propTypes={report:c.func.isRequired},h.childContextTypes={loadable:c.shape({report:c.func.isRequired}).isRequired},g.Capture=h,g.preloadAll=function(){return new Promise((function(e,t){y(l).then(e,t)}))},g.preloadReady=function(){return new Promise((function(e,t){y(u).then(e,e)}))},e.exports=g},EbDI:function(e,t){e.exports=function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)},e.exports.default=e.exports,e.exports.__esModule=!0},Enzk:function(e,t,n){"use strict";var r=n("284h"),a=n("TqRt");t.__esModule=!0,t.ScrollHandler=t.ScrollContext=void 0;var i=a(n("PJYZ")),o=a(n("VbXa")),s=r(n("q1tI")),c=a(n("17x9")),l=n("/hTd"),u=s.createContext(new l.SessionStorage);t.ScrollContext=u,u.displayName="GatsbyScrollContext";var d=function(e){function t(){for(var t,n=arguments.length,r=new Array(n),a=0;at.score?-1:e.index-t.index}))},h=function(e){return e.replace(/(^\/+|\/+$)/g,"").split("/")},y=function(e){for(var t=arguments.length,n=Array(t>1?t-1:0),r=1;r0})))&&n.length>0?"?"+n.join("&"):"")},b=["uri","path"],S=function(e,t){var n=Object.keys(e);return n.length===Object.keys(t).length&&n.every((function(n){return t.hasOwnProperty(n)&&e[n]===t[n]}))}},LeKB:function(e,t,n){e.exports=[{plugin:n("gSxY"),options:{plugins:[],component:"/home/t42/Documents/programming/Projects/OT_Guide/IL-2 Guide/src/templates/docs.js"}},{plugin:n("BOnt"),options:{plugins:[]}},{plugin:n("flL/"),options:{plugins:[],gatsbyRemarkPlugins:[{resolve:"gatsby-remark-images",options:{maxWidth:1035,sizeByPixelDensity:!0}},{resolve:"gatsby-remark-katex",options:{strict:"ignore"}},{resolve:"gatsby-remark-copy-linked-files"},{resolve:"gatsby-remark-acronyms",options:{acronyms:{"2Ltr":"2-Letter",Blk:"Block",Det:"Detachment","Stan/Eval":"Standardization and Evaluation","3DELRR":"Three Dimensional Expeditionary Long Range Radar","3PS":"Third Party Source",AAS:"Advisory and Assistance Services",A3M:"Air Force and Army Anti-Jam Modem",AA:"Adversarial Assessment",AAIP:"Aircraft Availability Improvement Program",AAR:"After-Action Review / Report",AARGM:"Advanced Anti-Radiation Guided Missile",AARI:"Air-to-air Range Infrastructure",ABSD:"Airborne Strategic Deterrence",AC:"Alternating Current",ACAT:"Acquisition Category",ACC:"Air Combat Command",ACCM:"Alternative Compensatory Control Measure",ACE:"Acquisition Center of Excellence",ACES:"Automated Civil Engineer System",ACPAT:"Air Force C4I Program Assessment Tool",ACPINS:"Automated Computer Program Identification Number System",ACPO:"Acquisition Chief Process Office",ACTD:"Advanced Concept Technology Demonstration",ACWP:"Actual Cost Work Performed",ADM:"Acquisition Decision Memorandum",ADS:"Advanced Distributed Simulation",AEC:"United States Army Evaluation Center",AECO:"Advance Engineering Change Order",AECS:"Advanced Entry Control System OR AFOTEC Electronic Coordination System",AEF:"Air and Space Expeditionary Force",AEHF:"Advanced Extremely High Frequency",AEP:"Accrued Expenditures Paid",AESO:"Advance Engineering Supplemental Order",AETC:"Air Education and Training Command",AETF:"Army Evaluation Task Force",AEU:"Accrued Expenditures Unpaid","AF GCIC":"Air Force Global Cyberspace Integration Center",AFMOASP:"Air Force Management and Oversight of Acquisition Services Process",AF:"(US) Air Force","AF/A10":"Assistant Chief of Staff for Strategic Deterrence and Nuclear Integration","AF/A2":"Deputy Chief of Staff, Intelligence, Surveillance and Reconnaissance","AF/A3/5":"Deputy Chief of Staff, Operations, Plans, and Requirements","AF/A4/7":"Deputy Chief of Staff, Logistics, Installations, and Mission Support","AF/A5/8":"HQ AF, Strategic Plans and Programs","AF/A5R":"Air Force Requirements Office","AF/A6":"Chief of Warfighting Integration and Chief Information Officer (CIO)","AF/A8":"Headquarters, Air Force Strategic Plans and Programs","AF/CC":"Chief of Staff, United States Air Force","AF/CV":"Vice Chief of Staff, United States Air Force","AF/SE":"Air Force Chief of Safety","AF/TE":"Headquarters Air Force Test and Evaluation Directorate",AFAE:"Air Force Acquisition Executive",AFAMS:"Air Force Agency for Modeling and Simulation",AFB:"Air Force Base",AFC2IC:"Air Force Command & Control Integration Center",AFC2ISRC:"Air Force Command and Control and Intelligence, Surveillance, and Reconnaissance Center (disestablished)",AFCA:"Air Force Communications Agency",AFCAA:"Air Force Cost Analysis Agency",AFCAP:"Air Force Certification and Accreditation Program",AFCD:"Air Force Capabilities Document",AFCEC:"Air Force Civil Engineer Center",AFCESA:"Air Force Civil Engineer Support Agency",AFDD:"Air Force Doctrine Document",AFDPO:"Air Force Departmental Publishing Office","AF-EA":"Air Force Enterprise Architecture",AFEE:"Air Force Element of Expense",AFEWES:"Air Force Electronic Warfare Simulator",AFFARS:"Air Force Federal Acquisition Regulation Supplement",AFFMA:"Air Force Frequency Management Agency",AFGK:"Air Force Gatekeeper",AFGLSC:"Air Force Global Logistics Support Center",AFGSC:"Air Force Global Strike Command",AFI:"Air Force Instruction",AFICE:"Air Force Integrated Collaborative Environment",AFIOC:"Air Force Information Operations Center",AFIPPS:"Air Force Integrated Personnel and Pay System",AFIT:"Air Force Institute of Technology",AFIWC:"Air Force Information Warfare Center (disestablished)",AFJO:"Air Force Joint Test Program Office",AFKN:"Air Force Knowledge Now",AFL2P:"Air Force Lessons Learned Program",AFLCMC:"Air Force Life Cycle Management Center",AFLIRP:"Air Force Lesson Issue Resolution Program",AFMAN:"Air Force Manual",AFMC:"Air Force Material Command",AFMD:"Air Force Mission Directive",AFMETCAL:"Air Force Metrology and Calibration",AFMSRR:"Air Force Modeling and Simulation Resource Repository",AFNET:"Air Force Network",AFNIC:"Air Force Network Integration Center","AF-NNSA":"Air Force-National Nuclear Security Administration",AFNWC:"Air Force Nuclear Weapons Center",AFOSH:"Air Force Occupational and Environmental Safety, Fire Protection, and Health OR Air Force Office of Safety and Health",AFOSI:"Air Force Office of Special Investigations",AFOTEC:"Air Force Operational Test and Evaluation Center","AFOTEC/A-1":"Manpower and Personnel Directorate","AFOTEC/A-1T":"Training Division","AFOTEC/A-1W":"Manpower and Personnel (Operations) Division","AFOTEC/A-2/9":"Intelligence, Analyses, and Assessments Directorate","AFOTEC/A-2N":"Intelligence Division","AFOTEC/A-3":"Operations Directorate","AFOTEC/A-3C":"Cyber Strategic Evaluation Division","AFOTEC/A-3E":"Operations Mission Support Division","AFOTEC/A-3F":"Test Operations Division","AFOTEC/A-3I":"Cyberspace Test Division","AFOTEC/A-3O":"Test Design Operations Division","AFOTEC/A-3Z":"Special Access Programs Division","AFOTEC/A-4/7":"Installations and Mission Support Directorate","AFOTEC/A-4F":"Logistics and Facilities Management Division","AFOTEC/A-5/8":"Plans and Programs Directorate","AFOTEC/A-5R":"Test Infrastructure Division","AFOTEC/A-6":"Communications and Information Directorate","AFOTEC/A-6O":"Cyber Operations Division","AFOTEC/A-6X":"Plans and Resources Division","AFOTEC/A-6Z":"Special Access Programs Information Technology Division","AFOTEC/A-7K":"Contracting Division","AFOTEC/A-7R":"Financial Resources Division","AFOTEC/A-8P":"Programming Division","AFOTEC/A-8R":"Long Range Investments Division","AFOTEC/A-8X":"Strategic Plans and Policy Division","AFOTEC/A-9A":"Analysis and Assessments Division","AFOTEC/A-9I":"Analysis Foundation and Integration Division","AFOTEC/A-9X":"Methods and Tools Division","AFOTEC/CA":"Technical Advisor","AFOTEC/CC":"AFOTEC Commander","AFOTEC/CCE":"Executive Officer","AFOTEC/CCJ":"Graphics","AFOTEC/CCP":"Protocol","AFOTEC/CCS":"Secretary","AFOTEC/CCX":"Commander’s Action Group","AFOTEC/CEM":"Chief Enlisted Manager","AFOTEC/CS":"Command Staff","AFOTEC/CV":"Vice Commander","AFOTEC/DS":"Director of Staff","AFOTEC/ED":"Executive Director","AFOTEC/HO":"History Office","AFOTEC/IGI":"Inspector General (Inspections)","AFOTEC/IP":"Information Protection","AFOTEC/LC":"Legal Council","AFOTEC/PA":"Public Affairs","AFOTEC/SE":"Safety",AFOTECI:"AFOTEC Instruction",AFOTECPAM:"AFOTEC Pamphlet",AFOTTP:"Air Force Operational Tactics, Techniques, and Procedures",AFPAM:"Air Force Pamphlet",AFPD:"Air Force Policy Directive","AFPEO/CM":"Air Force Program Executive Officer/Combat and Mission Support",AFRB:"Air Force Review Board",AFRC:"Air Force Reserve Command","AFRIMS RDS":"Air Force Information Management System Records Disposition Schedule",AFRIMS:"Air Force Records Information Management System",AFRL:"Air Force Research Laboratory",AFROC:"Air Force Requirements Oversight Council",AFROCC:"Air Force Requirements for Operational Capabilities Council",AFROCM:"Air Force Requirements Oversight Council Memorandum",AFRRG:"Air Force Requirements Review Group",AFSC:"Air Force Specialty Code",AFSEO:"Air Force SEEK EAGLE Office",AFSFC:"Air Force Security Forces Center",AFSIT:"Air Force System Interoperability Testing",AFSOC:"Air Force Special Operations Command",AFSPC:"Air Force Space Command",AFSSI:"Air Force Systems Security Instruction",AFTC:"Air Force Test Center",AGL:"Above Ground Level",AGM:"Air Ground Missile",AGR:"Active Guard and Reserve",AIM:"Air Intercept Missile","AIM-120 Adv EPIP":"AIM-120C Advanced Electronic Protection Improvement Program","AIM 120D SIP-3":"AIM-120D System Improvement Program",AIP:"Aircraft Information Program",AIR:"Acquisition Information Repository",AIS:"Automated Information Systems",AISR:"Airborne Intelligence, Surveillance, and Reconnaissance",AIT:"Automatic Identification Technology",ALC:"Air Logistics Center",ALCM:"Air Launched Cruise Missile","ALCS-R":"Airborne Launch Control System Replacement",ALDT:"Administrative and Logistics Delay",ALIS:"Autonomic Logistics Information System (F-35)",AMARG:"Aerospace Maintenance and Regeneration Group",AMAS:"AFOTEC Mission Applications Suite",AMC:"Air Mobility Command",AME:"Alternate Mission Equipment",AML:"Acquisition Master List",AMP:"C-130 Avionics Modernization Program",AMSAA:"Army Materiel Systems Analysis Activity","AN/PRC":"Army Navy/Portable Radio Communication",ANG:"Air National Guard",AO:"Area of Operations or Authorizing Official or Action Officer",Ao:"Operational Availability",AoA:"Analysis of Alternatives","AOC WS":"Air Operations Center Weapon System",AOTR:"Assessment of Operational Test Readiness",APA:"Additional Performance Attribute",APAT:"Acquisition Process Architecture Team",APB:"Acquisition Program Baseline",APDP:"Acquisition Professional Development Program",APKWS:"Advanced Precision Kill Weapon System",APM:"Acquisition Process Model",APML:"Acquisition Program Master List",APPG:"Annual Planning and Programming Guidance",APSR:"Accountable Property Systems of Record",APT:"Advanced Pilot Training",APUC:"Average Unit Procurement Cost",AR:"Analysis and Reporting Toolset OR Army Regulation",ARM:"Anti-Radiation Missile",ARRW:"Air-Launched Rapid Response Weapon",ART:"Adaptive-Relevant Test",ARTS:"Advanced Radar Threat System","AS Tool Kit":"Acquisition and Sustainment Tool Kit",AS:"Acquisition Strategy",ASACMS:"Advanced Situational Awareness Countermeasures System",ASACoE:"Application Software Assurance Center of Excellence",ASAF:"Assistant Secretary of the Air Force",ASD:"Acquisition Strategy Development OR Agile Software Development OR Assist Sec of Defense",ASDNII:"Assistant Secretary of Defense (Network and Information Integration",ASIP:"Airborne Signals Intelligence Payload OR Aircraft Structural Integrity Program",ASP:"Acquisition Strategy Panel",ASR:"Acquisition and Sustainment Reviews OR Alternative Systems Review",ASTK:"Acquisition Sustainment Tool Kit",ASuW:"Anti-Surface Warfare",AT:"Anti-Tamper","AT&L":"Acquisition, Technology, and Logistics",ATAPPS:"Automated Time Attendance and Production System",ATCALS:"Air Traffic Control and Landing Systems",ATD:"Advanced Technology Demonstration (or Development)",ATE:"Automatic Test Equipment",ATEC:"Army Test and Evaluation Command",ATO:"Air Tasking Order OR Authority to Operate",ATOS:"Automated Technical Orders System",ATPA:"AFOTEC Test Program Application","ATP-SE":"Advanced Targeting Pod-Sensor Enhancement",ATS:"Automatic Test System",ATTIC:"Analyst Training and Technical Information Center",AUTL:"Army Universal Task List",AV:"All Viewpoint",AVIP:"Aviation Integrity Program",AVPOL:"Aviation Petroleum, Oil, and Lubricants",AWACS:"Airborne Warning and Control System",AWBS:"Air Warfare Battle Shaping",AWIP:"Advanced Weapons Integration Program","B-2 DMS":"Defensive Management System","B-2 EHF SATCOM":"Extremely High Frequency Satellite Communications","B-52 CERP":"B-52 Commercial Engine Replacement Program","B-52 RMP":"B-52 Radar Modernization Program","B61 LEP":"B61 Life Extension Program",BAA:"Buy American Act",BBP:"Bullet Background Paper",BC:"Business Case",BCA:"Business Case Analysis",BCL:"Business Capability Lifecycle",BCS:"Baseline Comparison System","BCS-F":"Battle Control System-Fixed",BDA:"Big Data Analytics; Bomb Damage Assessment",BDRSK:"Battle Damage Repair Spares Kit",BEA:"Business Enterprise Architecture",BES:"Budget Estimate Submission",BFT:"Blue Force Tracking",BISS:"Base and Installation Security System","BLOS C2":"Beyond-Line-of-Sight Command and Control",BLOS:"Beyond Line of Sight",BLU:"Bomb, Live Unit",BMC2:"Battle Management Command and Control Communications",BMD:"Ballistic Missile Defense",BMDS:"Ballistic Missile Defense System",BOS:"Base Operating Support",BPAC:"Budget Program Activity Code",BRU:"Bomb Release Units",BU:"Block Update","C&A":"Certification and Accreditation","C&L":"Capabilities and Limitations","C&LR":"Capabilities and Limitations Report",C2:"Command and Control",C2AOS:"Command and Control Air Operations Suite",C2BMC:"Command, Control, Battle Management, and Communications",C2D2:"Continuous Capability Development and Delivery",C2IS:"Command and Control Information Services",C4:"Command, Control, Communications, and Computers",C4I:"Command, Control, Communications, Computers, and Intelligence",C4ISP:"Command, Control, Communication, Computers, and Intelligence Support Plan",C4ISR:"Cmd, Control, Comm, Computers, Intel, Surveillance, and Reconnaissance",CA:"Command Technical Advisor OR Contract Award OR Criticality Analysis",CAC:"Common Access Card ",CAD:"Computer-Aided Design (or Drafting)",CAE:"Component Acquisition Executive",CAFTOP:"Comprehensive Air Force Technical Order Plan",CAG:"Commander’s Action Group",CAGE:"Commercial and Government Entity",CAIG:"Cost Analysis Improvement Group",CALS:"Common Analytical Laboratory System",CAM:"Centralized Asset Management",CAOC:"Coalition Air Operations Center",CAP:"Contractor Acquired Property OR Critical Acquisition Position",CAPCO:"Controlled Access Program Coordinating Office",CAPE:"Cost Assessment and Program Evaluation",CAPES:"F-16 Combat Avionics Programmed Extension Suite",CARD:"Cost Analysis Requirements Description",CASS:"Close Air Support System",CAT:"Category",CBA:"Capabilities-Based Assessment",CBDP:"Chemical and Biological Defense Program",CBM:"Condition-Based Maintenance Plus",CBP:"Capability-Based Planning",CBR:"Chemical, Biological, and Radiological",CBRD:"Capabilities-Based Requirements Document",CBRN:"Chemical, Biological, Radiological and Nuclear",CC:"Commander OR Critical Component",CCA:"Clinger-Cohen Act OR Component Cost Analysis",CCaR:"Comprehensive Cost and Requirement System",CCCA:"Common Core Compliance Area",CCD:"Combat Capability Document",CCDR:"Combatant Commander",CCJO:"Capstone Concept for Joint Operations",CCMD:"Combatant Command",CCP:"Command Control Points",CCPE:"Corrosion Control Program Executive",CCR:"Call Completion Rate","C-CS":"Counter-Concealment Sensing",CCT:"Capability Collaboration Teams",CCTD:"Concept Characterization and Technical Description",CCX:"Commander’s Action Group Office Symbol",CD:"Capability Director (or Directorate) OR Deputy Commander",CDA:"Current Design Activity",CDD:"Capability Development Document",CDP:"Capability Definition Package",CDR:"Critical Design Review",CDRL:"Contract Data Requirements List",CDS:"Cross Domain Solution",CDT:"Chief Developmental Tester",CE:"Civil Engineer OR Conducted Emissions",CEP:"Circular Error Probability",CERT:"Certification",CFL:"Core Function Lead",CFLI:"Core Function Lead Integrator",CFMP:"Core Function Master Plan",CFO:"Chief Financial Officer",CFP:"Capabilities Focused Planning",CFR:"Code of Federal Regulations",CFSR:"Contract Funds Status Report",CGA:"Capability Gap Assessment",CGM:"Common GPS Module",CI:"Configuration Item OR Counterintelligence",CICA:"Competition in Contracting Act",CIDAS:"Contamination Indicator Decontamination Assurance System",CIED:"Counter-Improvised Explosive Device",CIMB:"Commander’s Inspection Management Board",CIO:"Chief Information Officer",CIP:"Critical Intelligence Parameter",CIPS:"Cyberspace Infrastructure Planning System",CIR:"Capital Investment Report",CISP:"Counterintelligence Support Plan",CITE:"Center of Industrial and Technical Excellence",CJCS:"Chairman, Joint Chiefs of Staff",CJCSI:"Chairman, Joint Chief of Staff Instruction",CJCSM:"Chairman, Joint Chiefs of Staff Manual",CJR:"COBRA JUDY Replacement",CJTF:"Coalition Joint Task Force",CL:"China Lake OR Civilian Leader OR Continuous Learning",CLIN:"Contract Line Item Number",CLS:"Contractor Logistics Support",CM:"Configuration Management OR Consequence Management OR Constellation Management OR Corrective Maintenance",CMBRE:"Common Munitions BIT Reprogramming Equipment",CMC:"C-5 Core Mission Computer and Weather Radar Program",CML:"Capability-Mission Lattice",CMMI:"Capability Maturity Model Integration",CMP:"Configuration Management Plan",CMRS:"Collaboration and Measurements Requirements Summary",CNA:"Computer Network Attack",CNEO:"Change Notice Engineering Order",CNSSI:"Committee on National Security Systems (CNSS) Instruction",CNWDI:"Critical Nuclear Weapons Design Information",CO:"Contracting Officer",COA:"Course of Action",CoC:"Certificate of Compliance",COCOM:"Combatant Command",COD:"Capability Development Document",COI:"Critical Operational Issue",COLISEUM:"Community On-Line Intelligence System for End Users and Managers",COMAFFOR:"Commander Air Force Forces",COMOPTEVFOR:"Naval Command Operational Test and Evaluation Force",COMSEC:"Communications Security",CoN:"Certificate of Networthiness",CONECT:"B-52 Combat Network Communications Technology",CONEMP:"Concept of Employment",CONOPS:"Concept of Operations",COOP:"Continuity of Operations Plan",COP:"Common Operating Picture",CoP:"Community of Practice",COR:"Contracting Officer’s Representative",CORE:"Critical Operational Issues and Criteria",COTF:"Commander, Operational Test Force (OPTEVFOR)",COTS:"Commercial Off-the-Shelf",COTT:"Combined Operational Test Team",CPA:"Chairman’s Program Assessment",CPAF:"Cost-Plus Award Fee",CPARS:"Contractor Performance Assessment Reporting System",CPCP:"Corrosion Prevention and Control Plan",CPD:"Capability Production Document",CPI:"Crash Position Indicator OR Critical Program Information",CPIF:"Cost Plus Incentive Fee",CPM:"Capability Portfolio Manager",CPR:"Chairman’s Program Recommendation",CR:"Change Request",CR6:"Hexavalent Chromium",CRA:"Continuing Resolution Authority OR Cost Risk Assessment OR Chairman’s Risk Assessment",CRD:"Capabilities Requirements Document ",CRDA:"Cooperative Research and Development Agreement",CRH:"Combat Rescue Helicopter",CRIIS:"Common Range Integrated Instrumentation System",CRISP:"Cross Industry Standard Process for Data Mining",CRM:"Component Resolution Matrix OR Crew Resource Management",CRRA:"Capabilities Review and Risk Assessment",CRS:"Chairman’s Readiness System",CS:"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy",CSA:"Combat Support Agency",CSAF:"Chief of Staff of the Air Force",CSAG:"Consolidated Sustainment Activity Group",CSAR:"Combat Search and Rescue",CSARL:"Combat Search and Rescue Locator",CSB:"Configuration Steering Board",CSCI:"Computer Software Configuration Items",CSE:"Center for Systems Engineering OR Common Support Equipment",CSH:"Common Support Helicopter",CSI:"Critical Safety Item",CSO:"Commodity Strategy Official",CSR:"Critical System Resources",CSS:"Contract Sustainment Support","C-sUAS":"Counter-small Unmanned Aerial Systems",CSWS:"Contractor Supported Weapon System",CT:"Contractor Testing OR Critical Technology",CTA:"Capability Threat Assessments OR Center Test Authority",CTE:"Critical Technology Element",CTEIP:"Central Test & Evaluation Investment Program",CTF:"Combined Task Force",CTIC:"Contractor Technical Information Code",CTM:"Capability Transition Memorandum",CtO:"Certificate to Operate",CTOM:"Centralized Technical Order Management",CTP:"Critical Technical Parameter",CTR:"Capability Transition Review",CUI:"Controlled Unclassified Information",CUMI:"Controlled Unclassified Military Information",CV:"Vice Commander OR Capability Viewpoint",CVI:"AFOTEC Information Protection/SAP Security (office symbol)",CVLSP:"Common Vertical Lift Support Platform",CVPA:"Cooperative Vulnerability and Penetration Assessment",CVW:"Carrier Air Wing",CWI:"Continuous Wave Illuminator",CY:"Calendar Year","D&F":"Determination and Findings","D,ARA":"Director, Acquisition Resources, and Analysis","D/CAPE":"Director, Cost Assessment, and Program Evaluation","D/QT&E":"Development/Qualification Test and Evaluation",DA:"Department of the Army",DAA:"Designated Approval Authority",DAB:"Defense Acquisition Board",DAC:"Designated Acquisition Commander",DACM:"Director, Acquisition Career Management",DAE:"Defense Acquisition Executive",DAES:"Defense Acquisition Executive Summary",DAF:"Department of the Air Force",DAG:"Defense Acquisition Guidebook",DAMIR:"Defense Acquisition Management Information Retrieval",DAO:"Designated Acquisition Officials",DARC:"Deep Space Advanced Radar Concept",DARPA:"Defense Advanced Research Projects Agency",DART:"Data, Acquisition, Recording, and Telemetry OR Deficiency Analysis Ranking Technique",DAS:"Defense Acquisition System",DASD:"Deputy Assistant Secretary of Defense",DATO:"Denial of Authorization to Operate",DAU:"Defense Acquisition University",DAWIA:"Defense Acquisition Workforce Improvement Act",DBC:"Defense Business Council",DBS:"Defense Business Systems",DBSMC:"Defense Business Systems Management Committee",DC:"Derivative Classifier OR Direct Current",DCAA:"Defense Contract Audit Agency",DCAPE:"Director of Cost Assessment and Program Evaluation",DCAPES:"Deliberate and Crisis Action Planning and Execution Segments",DCGS:"Distributed Common Ground System",DCID:"Director of Central Intelligence Directive",DCMA:"Defense Contract Management Agency",DCPDS:"Defense Civilian Personnel Data System",DCR:"DOTMLPF-P Change Recommendation",DCS:"Deputy Chief of Staff","DDNI/M":"Deputy Director of National Intelligence for Management",DDR:"Deputy Director for Requirements OR Dismount Detection Radar","DDT&E":"Director, Developmental Test and Evaluation",DEAD:"Destruction of Enemy Air Defenses",DEAMS:"Defense Enterprise Accounting and Management System",DEF:"Developmental Evaluation Framework",DepSecDef:"Deputy Secretary of Defense","Det/CC":"Detachment Commander",DEW:"Directed Energy Weapons",DEWCB:"Directed Energy Weapons Certification Board",DFARS:"Defense Federal Acquisition Regulation Supplement",DFCN:"Dual Frequency Civil Navigation",DFoS:"Decontamination Family of Systems",DHMSM:"Defense Healthcare Management Systems Modernization",DIA:"Defense Intelligence Agency",DIACAP:"DoD Information Assurance Certification and Accreditation Process",DID:"Data Item Description",DIP:"DIACAP Implementation Plan",DISA:"Defense Information Systems Agency",DISR:"Department of Defense Information Technology Standards Registry",DITSCAP:"Department of Defense Information Technology Security Certification and Accreditation Program",DIV:"Data and Information Viewpoint",DLA:"Defense Logistics Agency",DLR:"Depot-Level Repairable",DM:"Data Mining",DMAP:"Data Management and Analysis Plan",DMAWG:"Depot Maintenance Activation Working Group",DMEA:"Defense Microelectronics Activity",DMI:"Depot Maintenance Interservice","DMIX JLV":"Defense Medical Information Exchange Joint Legacy Viewer",DMS:"Defensive Management System OR Diminishing Manufacturing Sources",DMSMS:"Diminishing Manufacturing Sources Material Shortages",DNAD:"Domestic Non-Availability Determination",DNI:"Director of National Intelligence",DoD:"Department of Defense",DODAAC:"Department of Defense Activity Code",DODD:"Department of Defense Directive",DODI:"Department of Defense Instruction",DODIN:"Department of Defense Information Network",DODIPP:"Department of Defense Intelligence Production Program",DODISS:"Department of Defense Index of Specifications and Standards",DODM:"Department of Defense Manual",DOE:"Department of Energy OR Design of Experiments",DoN:"Department of the Navy","DOT&E":"Director of Operational Test and Evaluation","DOTMLPF-P":"Doctrine, Organization, Training, materiel, Leadership Policy and Education, Personnel, Facilities, and Policy",DP:"Development Planning",DPAP:"Director of Procurement and Acquisition Policy",DPAS:"Defense Priorities and Allocation System",DPEM:"Depot Purchased Equipment Maintenance",DPG:"Defense Planning Guidance",DPGS:"Data Processing Ground Station",DPPG:"Defense Planning and Programming Guidance","DR SKO":"Dismounted Reconnaissance Sets, Kits, and Outfits",DR:"Deficiency Report",DRAGON:"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation",DRB:"Deficiency Review Board",DREN:"Defense Research Engineering Network",DRI:"Data Referential Integrity","DRI&R":"Deficiency Reporting, Investigation and Resolution",DRM:"DRAGON Requirements Memorandum",DRMO:"Defense Reutilization Marketing Office",DRR:"Design Readiness Review",DRU:"Direct Reporting Unit","DS&TI":"Designated Science and Technology Information",DSA:"Direct Sales Agreement",DSC:"Decision Support Question",DSCA:"Defense Security Cooperation Agency",DSM:"Development System Manager OR Digital System Model",DSOR:"Depot Source of Repair","DSOR-EM":"Depot Source of Repair-Electronic Manager",DT:"Developmental Test","DT&E":"Developmental Test and Evaluation",DTD:"Data Type Definition",DTIC:"Defense Technical Information Center",DTM:"Directive-Type Memorandum",DTP:"Detailed Test Plan",DUSD:"Deputy Under Secretary of Defense","E&S":"Effectiveness and Suitability","E-3 DRAGON":"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation",E3:"Electromagnetic Environmental Effects",EA:"Economic Analysis OR Electronic Attack OR Evolutionary Acquisition OR Executing Authority",EAC:"Estimate at Completion",ECD:"Estimated Completion Date",ECM:"Electronic Countermeasures",ECN:"Enclave Control Node",ECSS:"Expeditionary Combat Support System",ED:"Executive Director",EDGC:"Engineering Data Guidance Conference",EDM:"Engineering Data Manager (or Management) OR Engineering Development Model",EDSC:"Engineering Data Service Center",EEC:"Enterprise Engineering Center",EEIC:"Element of Expense Investment Code",EFF:"Essential Function Failure",EHF:"Extremely High Frequency",EIAP:"Environment Impact Analysis Process",EIEMA:"Enterprise Information Environment Mission Area",EIS:"Early Influence Strategy",EIT:"Early Influence Team",EITDR:"Enterprise Information Technology Data Repository",EKMS:"Electronic Key Management System",ELA:"Elevated Level of Assurance",ELT:"Emergency Locator Transmitter",EMA:"Expectation Management Agreement",EMC:"Electromagnetic Compatibility","EMC/EMI":"Electromagnetic Compatibility/Electromagnetic Interference",EMD:"Engineering and Manufacturing Development",EMI:"Electromagnetic Interference",EMP:"Electromagnetic Pulse",EMSEC:"Emission Security",EMV:"Electromagnetic Vulnerability",ENSIP:"Engine Structural Integrity Program",EO:"Electro-Optical OR Executive Order OR Engineering Order",EOA:"Early Operational Assessment",EOD:"Explosive Ordnance Disposal",EP:"Electronic Protection",EPAWSS:"F-15 Eagle Passive and Active Warning and Survivability System",EPG:"Electronic Proving Ground",EPIP:"AIM-120C Advanced Electronic Protection Improvement Program",EPS:"Enhanced Polar System",EPVD:"Electromagnetically Enhanced Physical Vapor Deposition (gun tube coating",ERF:"Electronic Remote Fill",ERM:"Environmental Resources Manager",ESC:"Electromagnetic Spectrum Certification OR Evaluation Summary Chart",ESOH:"Environment, Safety, and Occupational Health",ESOHC:"Environment, Safety, and Occupational Health Council",ESOHCB:"Environment, Safety, and Occupational Health Certification Board","ESOH-MS":"Environment, Safety, and Occupational Health Management System",ESP:"Emergency and Special Program",ESS:"Effectiveness, Suitability, and Survivability OR Evolved Strategic Satellite Communications",ESW:"Electronic Systems Wing OR Evaluation Summary Worksheet",ETIMS:"Enhanced Technical Information Management System",ETM:"Electronic Technical Manual",ETO:"Executing Test Organization",EU:"Engineering Units",EUC:"End Use Certificate",EV:"Evaluation View",EVM:"Earned Value Management","EVM-CR":"Earned Value Management-Central Repository",EVMS:"Earned Value Management System",EW:"Electronic Warfare",EWIIP:"Electronic Warfare Infrastructure Improvement Program",EWIR:"Electronic Warfare Integrated Reprogramming",EWSR:"Executive Weapons System Review","F-15 EPAWSS":"F-15 Eagle Passive and Active Warning and Survivability System","F-15 IRST":"F-15 Infrared Search and Track System",F3I:"Form, Fit, Function, or Interface",FAA:"Federal Aviation Administration OR Functional Area Analysis","FAB-T":"Family of Advanced Beyond Line Of Sight Terminals","FAC-A":"Forward Air Controller-Airborne",FAR:"Federal Acquisition Regulation",FARM:"Functional Area Records Manager",FAT:"First Article Test",FCA:"Functional Configuration Audit",FCB:"Functional Capabilities Board",FCC:"Flagship Capability Concepts",FCT:"Foreign Comparative Test",FD:"Fielding Decision","FD/SC":"Failure Definition/Scoring Criteria",FDB:"Final Evaluation and Decision Brief",FDD:"Full Deployment Decision",FDDR:"Full Deployment Decision Review",FDE:"Force Development Evaluation",FDO:"Fee Determining Official",FDR:"Final (or Formal) Design Review",FET:"Force Element Terminal",FFP:"Firm Fixed Price",FFRDC:"Federally Funded Research and Development Centers",FFT:"Friendly Force Tracking",FH:"Flying Hours",FIAR:"Financial Improvement and Audit Readiness",FIP:"Federal Information Processing",FISCAM:"Federal Information System Controls Audit Manual",FISMA:"Federal Information Security Management Act of 2002",FM:"Financial Management OR Frequency Modulation OR Functional Manager",FMC:"Fully Mission Capable",FMECA:"Failure Mode, Effects, and Criticality Analysis",FMM:"Flight Manual Manager",FMP:"Flight Manuals Program OR Foreign Materiel Program",FMR:"Financial Management Regulation",FMRS:"Financial Management Regulation System",FMS:"Foreign Military Sales","FMU-139 D/B":"Fuze Module Unit-139",FNA:"Functional Needs Analysis",FOA:"Field Operating Agency",FOB:"Forward Operating Base",FOC:"Full Operational Capability",FOIA:"Freedom of Information Act",FoM:"Follow-on Modernization",FORGE:"Future Operationally Resilient Ground Evolution",FoS:"Family of Systems","FOT&E":"Follow-on Operational Test and Evaluation",FOU:"Full Operational Utility",FOUO:"For Official Use Only",FOV:"Field of View",FPAF:"Fixed-Price with Award Fee",FPD:"Follow-on Production Decision","FPDS-NG":"Federal Procurement data System-Next Generation",FPIF:"Fixed-Price Incentive",FPR:"Final Pricing Report OR Final Proposal Revision",FPRA:"Forward Price Rate Agreements",FQR:"Formal Qualification Review",FRD:"Formerly Restricted Data",FRP:"Full-Rate Production","FRP/FD":"Full-Rate Production or Full Deployment",FRPDR:"Full Rate Production Decision Review",FRRB:"Functional Requirements Review Board",FSA:"Functional Solution Analysis",FSC:"Federal Supply Classification",FSR:"Field Service Representative",FTE:"Full Time Equivalent",FTX:"Field Training Exercise",FY:"Fiscal Year",FYDP:"Future Years Defense Program","G&A":"General and Administrative (Expense)",GAO:"Government Accountability Office",GAT:"Government Analysis Tool",GBS:"Global Broadcast Service",GBSD:"Ground Based Strategic Deterrent",GBU:"Guided Bomb Unit",GCIC:"Global Cyberspace Integration Center",GCS:"Ground Control Stations","GCSS-AF":"Global Combat Support System – Air Force",GDT:"Government Development Test",GEF:"Guidance for the Employment of the Force",GEO:"Geosynchronous Earth Orbit",GFE:"Government Furnished Equipment",GFI:"Government Furnished Information",GFM:"Global Force Management",GFP:"Government Furnished Property","GH GSMP":"Global Hawk Ground Segment Modernization Program",GIDEP:"Government Industry Data Exchange Program",GIG:"Global Information Grid",GLSC:"Global Logistics Support Center",GMT:"Ground Movement Terrain Radar",GMTI:"Ground Moving Target Indicator",GO:"General Officer","GO/SES":"General Officer/Senior Executive Service",GOCO:"Government Owned Contractor Operated",GOSG:"General Officer Steering Group",GOTS:"Government Off-the-Shelf",GPA:"GPS Pulse-per-Second Adapter",GPC:"Government Purchase Card",GPD:"General Purpose Decontaminant Program",GPLR:"Government Purpose License Rights",GPR:"Government Purpose Rights","GPS III COps":"Global Positioning System III Contingency Operations","GPS MCEU":"Global Positioning System M-Code Early Use","GPS MGUE":"Military GPS User Equipment","GPS OCX":"GPS Next Generation Operational Control System",GPS:"Global Positioning System",GS:"General Schedule",GSA:"Government Services Administration",GSMP:"Ground Segment Modernization Program","GTG-F":"Global Information Grid Technical Guidance Federation","G-TSCMIS":"Global Theater Security Cooperative Management Information System",GTV:"Guided Test Vehicle",HAF:"Headquarters Air Force",HAFMD:"Headquarters Air Force Mission Directive",HAMS:"Hardness Assurance, Maintenance, and Surveillance",HARPOON:"(AGM-84-Fixed Wing; RGM-Surface Ships; UGM-Submarine Launched)",HCA:"Head of Contracting Activity (or Agency)",HCI:"Human-Computer Interactions",HCSP:"Human Capital Strategic Plan",HCSW:"Hypersonic Conventional Strike Weapon",HDF:"Hierarchical Data Format",HEMP:"High-Altitude Electromagnetic Pulse",HERF:"Hazards of Electromagnetic Radiation to Volatile Material",HERO:"Hazards of Electromagnetic Radiation to Ordinance",HERP:"Hazards of Electromagnetic Radiation to Personnel",HFE:"Human Factors Engineering",HITL:"Hardware in the Loop","HM/HS":"Hardness Maintenance / Hardness Surveillance",HMS:"Handheld, Manpack, and Small Form Fit",HO:"HQ AFOTEC History Office",HOI:"Headquarters Operating Instruction",HPT:"High Performance Team",HQ:"Headquarters",HSI:"Human Systems Integration",HSN:"High Speed Network",HSP:"Health and Safety Plan",HTM:"Hard Target Munitions",HTVSF:"Hard Target Void Sensing Fuze",HwA:"Hardware Assurance",IA:"Information Assurance (replaced by “cybersecurity”)",IAC:"International Armaments Cooperation",IAD:"Integrated Air Defense",IADS:"Integrated Air Defense System",IAE:"Integrated Aircrew Ensemble",IAMD:"Integrated Air and Missile Defense",IATO:"Interim Authorization to Operate",IATT:"Interim Authority to Test or Authorization to Test",IAVA:"Information Assurance Vulnerability Alert",IAW:"In Accordance With",IB:"Involvement Briefing",IBA:"Individual Body Armor",IBBP:"Involvement Bullet Background Paper",IBCT:"Infantry Brigade Combat Team",IBDC2:"Integrated Base Defense Command and Control",IBDSS:"Integrated Base Defense Security System",IBR:"Integrated Baseline Review",IBS:"Integrated Broadcast Service",IC:"Intelligence Community",ICADS:"Individual Combat Aircrew Display System",ICBM:"Intercontinental Ballistic Missile",ICCR:"Intelligence Community Capability Requirements",ICD:"Initial Capabilities Document OR Interface Control Document",iCDD:"initial Capability Development Document",ICE:"Independent Cost Estimate",ICEP:"Information Certification Evaluation Plan",ICM:"Interim Contractor Support",ICP:"Inventory Control Point",ICS:"Interim Contract Support",ICT:"Integrated Concept Team",ID:"Identification","ID/IQ":"Indefinite Delivery/Indefinite Quantity",IDE:"Integrated Data Environment",IDL:"Indentured Data List",IDRL:"Integrated Data Requirements List",IEB:"Initial Evaluation Briefing",IED:"Improvised Explosive Device",iEHR:"Integrated Electronic Health Records",IER:"Information Exchange Requirements",IETM:"Interactive Electronic Technical Manual",IFC:"Integrated Functional Capability",IFDL:"Intraflight Datalink",IFM:"Intelligence in Force Modernization",IFTU:"In-Flight Targeting Update",IGF:"Inherently Governmental Function",IITD:"Initial Integrated Test Design",IL:"Involvement Letter",ILCM:"Integrated Life Cycle Management",ILS:"Instrument Landing System OR Integrated Logistics Support",ILSP:"Integrated Logistics Support Plan",IM:"Insensitive Munitions",IMC:"Instrument Meteorological Conditions",IMD:"Intelligence Mission Data",IMDS:"Integrated Maintenance Data System",IMET:"International Military Education and Training",IMP:"Integrated Master Plan",IMS:"Integrated Master Schedule",IMT:"Information Management Tool",IMTP:"Integrated Master Test Plan",INC:"Increment",INS:"Inertial Navigation System",IO:"Information Operations",IOC:"Initial Operational Capability",IOT:"Initial Operational Test","IOT&E":"Initial Operational Test and Evaluation",IP:"Information Protection OR Initial Point OR Intellectual Property OR Internet Protocol",IPA:"Independent Program Assessment",IPAT:"Independent Program Assessment Team",IPL:"Integrated Priority List",IPMR:"Independent Program Management Report",IPR:"In-Process Review",IPS:"Integrated Program Summary OR Intellectual Property Strategy",IPSS:"Initial Provisioning Performance Specifications",IPT:"Integrated Product Team",IR:"Infrared",IRAD:"Independent Research and Development",IRB:"Intelligence Resources Board OR Investment Review Board",IRCM:"Infrared Countermeasures",IRSS:"Information and Resource Support System",IRST:"Infrared Search and Track System","IS CDD":"Information System Capability Development Document","IS ICD":"Information System Initial Capabilities Document",IS:"Information System",ISA:"International Standardization Agreement",ISACA:"Information Systems Audit and Control Association",ISO:"International Standards Organization",ISOO:"Information Security Oversight Office",ISP:"Information Support Plan",ISPAN:"Integrated Strategic Planning and Analysis Network",ISR:"Intelligence, Surveillance, and Reconnaissance OR Interim Summary Report",ISSM:"Information System Security Manager",ISWG:"Intelligence Support Working Group","IT Lean":"Information Technology Lean",IT:"Information Technology OR Integrated Testing","IT&E":"Integrated Test and Evaluation","IT/NSS":"Information Technology/National Security System",ITA:"Interface Test Adapter",ITAB:"Information Technology Acquisition Board",ITC:"Integrated Test Concept",ITD:"Initial Test Design",ITEA:"Initial Threat Environment Assessment",ITO:"Initial Tasking Order",ITP:"Integrated Test Plan",ITT:"Integrated Test Team",IUID:"Item Unique Identification",IUS:"Internal Use Software",IW:"Information Warfare",IWBU:"Internal Weapons Bay Upgrade",IWSM:"Integrated Weapons System Management","J&A":"Justification and Approval","J-8/DDR":"Joint Staff J-8, Deputy Director for Requirements","J-8/SAPCOORD":"Joint Staff J-8, Special Access Program Coordinator",JAFAN:"Joint Air Force Army Navy",JAGM:"Joint Air-to-Ground Missile",JALN:"Joint Aerial Layered Network",JASP:"Joint Aircraft Survivability Program",JASSM:"Joint Air-to-Surface Standoff Missile",JAWS:"Joint Avionics Workstation",JBADS:"Joint Biological Agent Decontamination System",JBTDS:"Joint Biological Tactical Detection System",JCA:"Joint Capability Area",JCAAMP:"Joint Improvised Explosive Device Defeat Capability Approval and Acquisition Management Process",JCALS:"Joint Computer-Aided Acquisition and Logistic Support",JCB:"Joint Capabilities Board",JCC2:"Joint Cyber Command and Control",JCCA:"Joint Combat Capability Assessment",JCD:"Joint Capabilities Document",JCIDS:"Joint Capabilities Integration and Development System",JCPATE:"Joint C4I Program Assessment Tool-Empowered",JCREW:"Joint Counter Radio-Controlled Improvised Explosive Device Electronic Warfare",JCS:"Joint Chiefs of Staff",JCTD:"Joint Capability Technology Demonstration",JDAM:"Joint Direct Attack Munition",JDMAG:"Joint Depot Maintenance Activities Group",JDRS:"Joint Deficiency Reporting System",JEDMICS:"Joint Engineering Data Management Information and Combat System",JEM:"Joint Effects Model",JENM:"Joint Enterprise Network Manager",JEON:"Joint Emergent Operational Need",JFC:"Joint Functional Concept",JFCC:"Joint Functional Component Commander",JIC:"Joint Integrating Concept",JICO:"Joint Interface Control Officer",JIE:"Joint Intelligence Estimate",JIEDDF:"Joint Improvised Explosive Device Defeat Fund",JIEDDO:"Joint Improvised Explosive Device Defeat Organization",JITC:"Joint Interoperability Test Command",JLE:"Joint Logistics Estimate",JLLP:"Joint Lessons Learned Program",JLTV:"Joint Light Tactical Vehicle",JMC:"Joint Mission Computer",JMETC:"Joint Mission Environment Test Capability",JMM:"Joint Miniature Munitions",JMS:"Joint Space Operations Center (JSpOC) Mission System",JMT:"Joint Mission Thread",JOC:"Joint Operating Concept",JOMIS:"Joint Operational Medicine Information Systems",JOpsC:"Joint Operations Concept",JOTT:"JSF Operational Test Team",JP:"Joint Publication",JPALS:"Joint Precision Approach and Landing System",JPD:"Joint Potential Designator",JPE:"Joint Personnel Estimate",JPG:"Joint Planning Guidance",JPO:"Joint Strike fighter Program Office",JRAC:"Joint Rapid Acquisition Cell",JRMET:"Joint Reliability and Maintainability Evaluation Team",JRO:"Joint Requirements Office",JROC:"Joint Requirements Oversight Council",JROCM:"Joint Requirements Oversight Council Memorandum",JS:"Joint Staff",JSA:"Joint Strategic Assessment","JSAM-FW":"Joint Service Aircrew Mask-Fixed Wing","JSAM-SA":"Joint Service Aircrew Mask-Strategic Aircraft","JSAM-TA":"Joint Service Aircrew Mask-Tactical Aircraft",JSD:"Joint Staffing Designator",JSE:"Joint Simulation Environment",JSEW:"Joint Sensitive Equipment Wipes (Decontamination Family of Systems)",JSF:"Joint Strike Fighter",JSIG:"Joint Special Access Program (SAP) Implementation Guide",JSOW:"Joint Stand-Off Weapon",JSpOC:"Joint Space Operations Center",JSPS:"Joint Strategic Planning System",JSR:"Joint Strategy Review",JSS:"Joint Interface Control Officer (JICO) Support System",JSTAR:"Joint System Threat Assessment Report","JSTARS RECAP":"Joint Surveillance Target Attack Radar System Recapitalization","JT&E":"Joint Test and Evaluation",JTAC:"Joint Terminal Attack Controller",JTR:"Joint Tactical Radio",JTRS:"Joint Tactical Radio System","JTRS-AMF":"Joint Tactical Radio System-Airborne Maritime Fixed",JUON:"Joint Urgent Operational Need",JUPITR:"Joint United States Forces Korea Portal and Integrated Threat Recognition",JWARN:"Joint Warning & Reporting Network",JWICS:"Joint Worldwide Intelligence Communications System",KDP:"Key Decision Point",KIP:"Key Interface Profile",KLP:"Key Leadership Position","KM/DS":"Knowledge Management/Decision Support",KN:"Knowledge Now",KPP:"Key Performance Parameter",KSA:"Key System Attribute",L2:"Lessons Learned",LA:"Logistics Assessment",LAT:"Lot Acceptance Test","L-band":"Long Band",LC:"HQ AFOTEC Legal Counsel",LCB:"Lower Confidence Bound",LCC:"Life Cycle Cost",LCCE:"Life Cycle Cost Estimate",LCMC:"Life Cycle Management Center",LCMP:"Life Cycle Management Plan",LCRM:"Life Cycle Risk Management",LCS:"Launch and Checkout System",LCSP:"Life Cycle Sustainment Plan",LD:"Limited Deployment OR Logistics Demonstration",LDC:"LAN Data Collector",LDTO:"Lead Developmental Test Organization",LED:"Light Emitting Diode",LEO:"Low Earth Orbit",LEP:"Life Extension Program",LFD:"Limited Fielding Decision","LFT&E":"Live Fire Test and Evaluation",LHA:"Logistics Health Assessments",LJDAM:"Laser Joint Direct Attack Munition (GBU-56)",LM:"Lockheed Martin",LMD:"Logistics MANPRINT Demonstration",LMDP:"Life Cycle Mission Data Plan",LNE:"Late Network Entry",LNO:"Liaison Officers",LOA:"Letter of Offer and Acceptance",LORA:"Level of Repair Analysis",LOS:"Line of Sight",LR:"Limited Rights",LRDR:"Long Range Discrimination Radar",LRIP:"Low Rate Initial Production",LRSO:"Long Range Standoff",LRT:"Logistics Response Time",LRU:"Line-Replaceable Unit",LSC:"Logistics Support Concept",LSE:"Lead Systems Engineer",LSI:"Large Scale Integration OR Lead Systems Integrator",LTE:"Last Test Event",LTWG:"Logistics Test Working Group",LUT:"Limited User Test",LVC:"Live, Virtual, and Constructive","M&S":"Modeling and Simulation","M&S CO":"Modeling and Simulation Coordination Office",MAAP:"Master Air Attack Plan",MAAPTK:"Master Air Attack Planning Toolkit",MAC:"Mission Assurance Category",MACH:"Modular Air Crew Helmet",MADL:"Multifunction Advanced Data Link","MAF-DRC":"Mobility Air Forces-Dynamic Retasking Capability",MAFPS:"Mobility Air Force Automated Flight Planning Service",MAIS:"Major Automated Information System",MAJCOM:"Major Command","MALD-J":"Miniature Air Launched Decoy-Jammer",MANPAD:"Man Portable Air Defense System",MANPRINT:"Manpower and Personnel Integration",MAnTSS:"Modular Analysis and Test Support System",MAR:"Monthly Acquisition Report",MAV:"Maverick",MBITR:"Multiband Inter/Intra Team Radio",MBTD:"Mission Based Test Design",MC:"Mission Capable",MCF:"Mission Critical Functions",MCOTEA:"Marine Corps Operational Test and Evaluation Activity",MCR:"Message Completion Rate",MD:"Mission Directive",MDA:"Milestone Decision Authority OR Missile Defense Agency",MDAP:"Major Defense Acquisition Program",MDD:"Maintenance Data Documentation OR Material Development Decision",MDF:"Mission Data File",MDS:"Mission Design Series",MDT:"Mean Down Time","ME/SE":"Maintenance Engineering/Sustaining Engineering",MECSIP:"Mechanical Subsystems Integrity Plan",MEDALS:"Military Engineering Data Asset Locator System",MEFL:"Mission Essential Functions List",MEO:"Medium Earth Orbit",MER:"Manpower Estimate Report",MESL:"Minimum Essential Subsystems List",MEV:"Military Equipment Valuation",MFOQA:"Military Flight Operations Quality Assurance",MFP:"Major Force Program OR Materiel Fielding Plan",MFR:"Memorandum for Record",MFT:"Multi-Functional Team",MGRS:"Military Grid Referencing System","MGUE Inc 2 HH":"Military GPS User Equipment Hand Held",MGUE:"Military GPS User Equipment",MHS:"Modular Handgun System",MHz:"Megahertz","MIL-DTL":"Military Detail (Specification)","MIL-HDBK":"Military Handbook","MIL-PRF":"Military Performance (Specification)","MIL-STD":"Military Standard",MIP:"Materiel Improvement Program OR Military Intelligence Program",MIPR:"Military Interdepartmental Purchase Request",MIPRB:"Material Improvement Program Review Board",MLS:"Multiple Levels of Security",MMT:"Munitions, Missiles, and Target",MNS:"Mission Needs Statement",MOA:"Memorandum of Agreement",MOASP:"Management and Oversight of Acquisition Services Process",MOE:"Measure of Effectiveness",MOEs:"Measures of Effectiveness",MOP:"Measure of Performance",MOPP:"Mission Oriented Protective Posture",MORV:"Mission-Oriented Response Variables",MOS:"Measure of Suitability OR Military Occupational Specialty",MOSA:"Modular Open Systems Approach","MOT&E":"Multiservice Operational Test and Evaluation",MOU:"Memorandum of Understanding",MP:"Mission Profile",MPA:"Manpower Authorization",MPE:"Mission Planning Element",MPGPA:"Multipart GPS Pulse-per-Second Adapter",MPS:"Master Program Schedule OR Mission Planning System",MPTO:"Methods and Procedures Technical Order",MRA:"Manufacturing Readiness Assessment",MRB:"Mission Requirements Board",MRDS:"Man-Portable Radiological Detection System",MRL:"Manufacturing Readiness Level",MROi:"Air Force Depot Maintenance, Repair, and Overhaul Initiative",MRP:"Munitions Requirements Process",MRR:"Materiel Release Review",MRRB:"Maintenance Requirement Review Board",MRSP:"Mobility Readiness Spares Package",MRTFB:"Major Range and Test Facility Base",MS:"Milestone",MSA:"Materiel Solution Analysis",MSIAC:"Modeling and Simulation Information Analysis Center",MSL:"Mean Sea Level",MSSP:"Modeling and Simulation Support Plan",MTBEFF:"Mean Time Between Essential Function Failures",MTTR:"Mean Time To Repair",MUA:"Military Utility Assessment",MUOS:"Mobile User Objective System",MW:"Measures Workshop",NAOC:"National Airborne Operations Center",NASIC:"National Air and Space Intelligence Center",NATO:"North Atlantic Treaty Organization","NAVPLAN TPC":"Navigation Plan Tactical Pilotage Charts",NBC:"Nuclear, Biological and Chemical","NC2-ESI":"Nuclear Command and Control-Extremely Sensitive Information",NC3:"Nuclear Command, Control, Communications",NCOW:"Network-Centric Operations and Warfare","NCOW RM":"Net-Centric Operations and Warfare Reference Model",NDAA:"National Defense Authorization Act",NDF:"Network Design Facility",NDI:"Non-Developmental Item",NDS:"National Defense Strategy",NEPA:"National Environmental Policy Act",NET:"New Equipment Training",NetRA:"Network Risk Assessment",NEW:"Network Enabled Weapon",NGG:"Next Generation Geosynchronous Earth Orbit (GEO)",NGP:"Next Generation Polar",NGA:"National Geospatial-Intelligence Agency",NGB:"National Guard Bureau",NGCD:"Next Generation Chemical Detector",NGDS:"Next Generation Diagnostic System",NGREA:"National Guard and Reserve Equipment Account",NGS:"Non-Government Standard (commercial)",NID:"National Interest Determination",NIP:"National Intelligence Program",NIPRNet:"Non-Secure Internet Protocol Router Network",NISPOM:"National Industrial Security Program Operating Manual",NIST:"National Institute of Standards and Technology",NKCE:"Non-Kinetic Counter Electronics",NLT:"No or Not Later Than",NM:"Network Management",NMC:"Not Mission Capable",NMS:"National Military Strategy",NNMSB:"Nonnuclear Munitions Safety Board",NNSA:"National Nuclear Security Administration",NOU:"No Operational Utility",NPES:"Nuclear Planning and Execution System Modernization","NR KPP":"Net-Ready Key Performance Parameter",NRE:"Non-Recurring Engineering",NRO:"National Reconnaissance Office",NSA:"National Security Agency",NSL:"Near Strike Lightning",NSN:"National Stock Number",NSPS:"National Security Personnel System",NSS:"National Security Space OR National Security Strategy OR National Security System",NTTR:"Nevada Test and Training Range",NWC:"Nuclear Weapons Council",NWRM:"Nuclear Weapons Related Materiel","O&M":"Operation and Maintenance","O&S":"Operation and Support",OA:"Operational Assessment OR Operational Availability",OAG:"Operational Advisory Group (USN/USMC)",OAR:"Open-Air Range",OARL:"Operating at Risk List",OAS:"Office of Aerospace Studies","OASD/NII":"Office Assistant Secretary of Defense/Network and Information Integration",OASuW:"Offensive Anti-Surface Weapon",OC:"Operational Capability",OCA:"Original Classification Authority",OCC:"Occupational Specialty Code",OCDD:"Operational Capability Development Document",OCE:"Operational Concept of Employment",OCR:"Office of Collateral Responsibility OR Operational Capability Requirement",OCX:"GPS Next Generation Operational Control System",OE:"Operational Effectiveness OR Operational Environment",OEM:"Original Equipment Manufacturer",OER:"Operational Test Agency Evaluation Report",OFP:"Operational Flight Program",OFS:"Operational Flight Software",OIPT:"Overarching Integrated Product Team",OL:"Operating Location",OMB:"Office of Management and Budget",OML:"Outer Mold Line",OMS:"Operational Mission Summary OR Operational Mode Summary",OND:"Operational Need Date",OPIR:"Overhead Persistent Infrared",OPLAN:"Operations Plan",OPORD:"Operations Order",OPR:"Office of Primary Responsibility",OPSEC:"Operations Security",OPTEMPO:"Operational Tempo",OPTEVFOR:"Operational Test and Evaluation Force",ORD:"Operational Requirements Document",ORM:"Operational Risk Management",OS:"Operational Suitability",OSD:"Office of the Secretary of Defense",OSHA:"Occupational Safety and Health Administration","OSS&E":"Operational Safety, Suitability, and Effectiveness",OT:"Operational Test","OT&E":"Operational Test and Evaluation",OTA:"Operational Test Agency OR Other Transactions Authority",OTAR:"Over-the-Air Re-key",OTB:"Over Target Baseline",OTC:"United States Army Operational Test Command",OTD:"Open Technology Development",OTI:"Operational Training Infrastructure",OTIF:"Operational Test Information Files",OTO:"Operational Test Organization",OTRR:"Operational Test Readiness Review",OTS:"Over Target Schedule",OU:"Operational Utility",OUA:"Operational Utility Assessment",OUE:"Operational Utility Evaluation",OUSD:"Office of the Under Secretary of Defense",OV:"Operational View (or Viewpoint)",OWLP:"Overseas Workload Program","P&D":"Production and Deployment (phase)",P3I:"Pre-Planned Product Improvement",PA:"Partnering Arrangement OR Preparing Activity OR Preparing Authority OR Program Authorization ORPublic Affairs",PAA:"Phased Adaptive Approach",PAD:"Program Action Directive",PAM:"Pamphlet OR Performance Attributes Matrix",PAR:"Presidential Aircraft Recapitalization OR Proposal Analysis Report",PAS:"Personnel Accounting Symbol","PAT&E":"Production Acceptance Test and Evaluation",PAUC:"Program Acquisition Unit Cost",PB:"President’s Budget",PBA:"Performance Based Acquisition OR Performance Based Agreement",PBCM:"Portable Biological Containment Module",PBL:"Performance Based Logistics",PBR:"Program/Budget Review",PC:"Product Center",PCC:"Program Control Chief",PCO:"Procuring Contracting Officer",PD:"Program Director",PDAQ:"Product Data Acquisition",PDM:"Program Decision Memorandum OR Programmed Depot Maintenance",PDR:"Preliminary Design Review",PE:"Program Element",PEM:"Program Element Monitor",PEO:"Program Executive Office / Officer",PESD:"Personnel Electrostatic Discharge",PESHE:"Programmatic Environment, Safety, and Occupational Health Evaluation",PG:"Product Group",PGI:"Procedures, Guidance, and Information",PGL:"Program Guidance Letter",PGM:"Precision Guided Munitions OR Product Group Manager","PHS&T":"Packaging, Handling, Storage, and Transportation",PIA:"Privacy Impact Assessment",PID:"Program Introduction Document",PII:"Personally Identifiable Information",PIR:"Post-Implementation Review",PISR:"Persistent Intelligence, Surveillance, and Reconnaissance",PIT:"Platform Information Technology",PL:"Public Law",PLI:"Position Location Information",PLMS:"Product Lifecycle Management System",PLR:"Position Location Recorder",PM:"Program Manager","PM/MFT":"Program Management or Multi-Functional Team",PMA:"Program Management Agreement",PMB:"Performance Measurement Baseline",PMC:"Partially Mission Capable",PMCS:"Preventive Maintenance Checks and Services",PMD:"Program Management Directive",PML:"Program Management Listing",PMO:"Program Management Office",PMRT:"Program Management Resource Tools",PMT:"Program Manager‘s Tool",PNVC:"Presidential and National Voice Conferencing",PO:"Program Office OR Project Officer","POA&M":"Plan of Action & Milestones",POC:"Point of Contact",POE:"Program Office Estimates",POM:"Program Objective Memorandum",POMx:"Point of Maintenance",PoPS:"Probability of Program Success",PoR:"Program of Record",POS:"Pre-Operational Support",POU:"Partial Operational Utility",PPBE:"Planning, Programming, Budgeting, and Execution","P-PLAN":"Programming Plan",PPLANS:"Programming Plans",PPP:"Program Protection Plan OR Public-Private Partnership",PPQT:"Pre-Production Qualification Test",PPR:"Post-Publication Review",PQT:"Production Qualification Test",PRA:"Performance Risk Assessment",PRO:"Portable Rugged Objected",PRR:"Production Readiness Review","PS-BCA":"Product Support Business Case Analysis",PSEAG:"Physical Security Equipment Action Group",PSI:"Product Support Integrator",PSIP:"Propulsion Systems Integrity Program",PSM:"Product Support Manager",PSMP:"Product Support Management Plan",PSN:"Publication Stock Number",PSP:"Product Support Provider",PSpec:"Preliminary Specification",PSR:"Program Support Review",PTES:"Protected Tactical Enterprise Services",PTO:"Participating Test Organization OR Preliminary Technical Order",PTS:"Protected Tactical SATCOM",PTSS:"Precision Tracking Space System",PV:"Project Viewpoint",PVI:"Pilot Vehicle Interface",PWS:"Performance Work Statement",QDR:"Quadrennial Defense Review",QoS:"Quality of Service","QOT&E":"Qualification Operational Test and Evaluation",QRC:"Quick Reaction Capability",QRF:"Quick Reaction Fund",QRG:"Quick Reference Guide",QRIP:"Quick Reaction Instrumentation Package","QT&E":"Qualification Test and Evaluation","R&D":"Research and Development","R&M":"Reliability and Maintainability","R/T":"Request for Test",RAA:"Rapid Acquisition Authority OR Required Assets Available",RADAR:"Radio Detection and Ranging",RAI:"Recorded Aircraft Information",RALOT:"Risk Assessment Level of Test",RAM:"Reliability, Availability, and Maintainability","RAM&C":"Reliability, Availability, Maintainability, and Cost",RAMPOD:"Reliability, Availability, Maintainability for Pods and Integrated Systems",RAMS:"Reliability, Availability, Maintainability, and Supportability",RAPIDS:"Rapid Analysis Processing Instrumentation Deployment System",RC:"Recommended Changes",RCA:"Regulatory Contracting Approval",RCM:"Reliability Centered Maintenance",RCN:"Report Control Number",RCT:"Requirements Correlation Table",RD:"Restricted Data",RDGT:"Reliability Development/Growth Test",RDS:"Radiological Detection System OR Records Disposition Schedule","RDT&E":"Research, Development, Test and Evaluation",REMIS:"Reliability and Maintainability Information System",REP:"Resource Enhancement Program",RF:"Radio Frequency",RFID:"Radio Frequency Identification",RFP:"Request for Proposal",RGC:"Reliability Growth Curve",RI3:"Risk Identification: Integration & -Ilities",RICS2:"Remote Reconfigurable Intelligent Instrumentation to Control, Collect, Simulate and Stimulate",RIID:"Radioisotope Identification Detector",RLA:"Rotary Launcher Assembly",RM:"Reference Manual OR Risk Management","RM&A":"Reliability, Maintainability and Availability",RMCT:"Requirements Management Certification Training",RMD:"Requirements Management Division",RMF:"Risk Management Framework",RMP:"Radar Modernization Program OR Risk Management Plan",ROM:"Rough Order of Magnitude",RPA:"Remotely Piloted Aircraft",RPIE:"Real Property Installed Equipment","RQ-4B Bk 30 MSI":"RQ-4B Block 30 Multi-Spectral Intelligence",RR:"Rifleman Radio",RRB:"Requirements Review Board",RRF:"Rapid Reaction Fund",RRP:"Rapid Response Process",RS:"Radiated Susceptibility",RSE:"Radar Signal Emulator",RSR:"Requirements Strategy Review",RTKN:"Real Time Kill Notification",RTO:"Radio Telephone Operator OR Ready for Transition to Operations ORResponsible Test Organization (now obsolete) OR Range Training Officer","R-TOC":"Reduction of Total Ownership Cost",RTT:"Readiness to Test","S&T":"Science and Technology",S2E2:"Space Based Infrared Sys (SBIRS) Survivable and Endurable Evolution",SA:"Security Assistance OR Situational Awareness OR System Administrator",SAASM:"Selective Availability Anti-Spoofing Module",SAE:"Service Acquisition Executive",SAF:"Secretary of the Air Force","SAF/AQ":"Assistant Secretary of the Air Force (Acquisition)","SAF/AQX":"Deputy Assistant Secretary for Acquisition Integration","SAF/CIO A6":"Chief of Warfighting Integration and Chief Information Officer (CIO)","SAF/FM":"Assistant Secretary of the Air Force (Financial Management)","SAF/FMC":"Deputy Assistant Secretary (DAS) of the Air Force for Cost and Economics","SAF/GC":"General Counsel of the Air Force","SAF/GCQ":"Deputy General Counsel (Acquisition)","SAF/IE":"Assistant Secretary of the Air Force (Installations, Environment, and Logistics","SAF/IG":"Inspector General of the Air Force","SAF/LL":"Assistant Secretary of the Air Force (Legislative Affairs)","SAF/US":"Under Secretary of the Air Force","SAF/XC":"Secretary of the Air Force Directorate (Warfighting Integration and Chief Information Officer)",SAM:"Support Agreement Manager",SAMP:"Single Acquisition Management Plan",SAO:"Security Assistance Organizations",SAP:"Security Assessment Plan OR Security Assistance Program OR Special Access Program",SAPCO:"Special Access Program Control Office",SAR:"Security Assessment Report OR Special Access Required OR Synthetic Aperture Radar OR System Assessment Report",SATAF:"Site Activation Task Force",SATCOM:"Satellite Communications",SATOP:"Security Assistance Technical Order Program",SB:"Small Business",SBIR:"Small Business Innovation Research",SBIRS:"Space Based Infrared System","SBIRS F/O":"Space Based Infrared System Follow-on",SBRA:"Smart Bomb Rack Assembly","SBSS F/O":"Space Based Space Surveillance Follow-On",SCD:"System Capabilities Document",SCG:"Security Classification Guide",SCI:"Sensitive Compartmented Information",SCM:"Supply Chain Manager",SCO:"Senior Contracting Official",SCP:"Service Cost Position",SCRM:"Supply Chain Risk Management",SCWDL:"Strike Common Weapon Data Link",SD:"Standardization Document",SDB:"Small Diameter Bomb",SDD:"System Development and Demonstration",SDO:"Services Designated Official",SDR:"System Design Review",SE:"Safety OR Support Equipment OR Systems Engineering","SE/ATS":"Support Equipment/Automatic Test System",SEAD:"Suppression of Enemy Air Defenses",SEAM:"Systems Engineering Assessment Model",SECAF:"Secretary of the Air Force",SECDEF:"Secretary of Defense",SEI:"Software Engineering Institute",SENSR:"Spectrum Efficient National Surveillance Radar System",SEP:"System Evaluation Plan OR Systems Engineering Plan",SERD:"Support Equipment Recommendation Data",SES:"Senior Executive Service",SESAME:"Selected Essential Item Stockage for Availability Methodology",SF:"Security Forces OR Standard Form",SFF:"Small Form Fit",SFR:"System Functional Review",SIAO:"Senior Information Assurance Official",SIGINT:"Signals Intelligence",SII:"Special Interest Item",SIM:"Serialized Item Management",SIMAF:"Simulation and Analysis Facility",SIMCERT:"Simulator Certification",SIMVAL:"Simulator Validation",SIO:"Senior Intelligence Officer","SIOP-ESI":"Single Integrated Operational Plan-Extremely Sensitive Information",SIP:"System Identification Profile OR System Information Profile",SIPC:"Service Intelligence Production Centers",SIPRNET:"Secret Internet Protocol Router Network",SISSU:"Security, Interoperability, Supportability, Sustainability, and Usability",SITREP:"Situational Report",SLA:"Service Level Agreements","SLAM-ER":"Standoff Land Attack Missile Expanded Response",SLEP:"Service Life Extension Program",SLIN:"Sub-Line Item Number",SM:"Security Manager OR Service Manager OR Single Manager",SMART:"Science, Mathematics, And Research For Transformation OR System Metrics and Reporting Tool",SMC:"Space and Missile Systems Center",SMCA:"Single Manager for Conventional Ammunition",SME:"Subject Matter Expert",SMI:"Soldier-Machine Interface",SMM:"System Maturity Matrix","SOC RPA":"Standardized Operations Center Remotely Piloted Aircraft",SOC:"Statement of Capabilities",SOCOM:"Special Operations Command",SOF:"Special Operations Forces",SOI:"Statement of Intent",SOO:"Statement of Objectives","SO-P":"Special Operations-Peculiar",SOR:"Source of Repair",SORA:"Source of Repair Assignment",SORAP:"Source of Repair Assignment Process",SORN:"System of Record Notice",SoS:"Speed of Service OR System of Systems",SOTR:"Sufficiency of Operational Test Review OR Sufficiency of Test Report",SOW:"Special Operations Wing OR Statement of Work",SP:"Security Plan OR Special Publication",SPA:"Single Point Adjustment",SPD:"System Program Director",SPE:"Senior Procurement Executive",SPG:"Strategic Planning Guidance",SPM:"System Program Manager",SPML:"Sustainment Program Master List",SPO:"System Program Office",SpOC:"Space Operations Command",SPT:"Systems Planning Team",SQL:"Structured Query Language",SRA:"Schedule Risk Assessment",SRB:"Safety Review Board",SRD:"Software or Systems Requirements Document",SRR:"System Requirements Review OR Systems Readiness Review",SRW:"Soldier Radio Waveform",SSA:"Source Selection Authority",SSAA:"Systems Security Authorization Agreement",SSAEM:"Space Situational Awareness-Environmental Monitoring",SSD:"Source Selection Decision",SSDD:"Source Selection Decision Document",SSE:"Systems Security Engineering",SSET:"Source Selection Evaluation Team",SSM:"System Sustainment Manager",SSN:"Social Security Number",SSOM:"Standard Surveillance Operating Manual",SSOR:"Strategic Source of Repair",SSP:"Source Selection Plan OR System Support Package",SSS:"Staff Summary Sheet",SSWG:"Systems Security Working Group",STA:"System Threat Analysis OR System Threat Assessment",STAR:"System Threat Assessment Report",STARCOM:"Space Training and Readiness Command",STAT:"Scientific Test and Analysis Techniques",StdV:"Standards Viewpoint",STEP:"Standard for Exchange of Product",STIG:"Security Technical Implementation Guide",STINFO:"Scientific and Technical Information",STP:"Space Test Program OR System Training Plan",STR:"Sea Test Range",STT:"Strategy-To-Task",STTR:"Small Business Technology Transfer",SUT:"System Under Test",SV:"System View",SVAD:"Survivability, Vulnerability, and Assessment Directorate",SvcV:"Services Viewpoint",SVR:"System Verification Review",SwA:"Software Assurance",SYSCOM:"Systems Command","T&E ITT":"Test and Evaluation Integrated Test Team","T&E":"Test and Evaluation",TA:"Technical Advisor OR Test Area",TAA:"Technical Airworthiness Authority",TACO:"Test and Checkout",TACP:"Tactical Air Control Party","TACP-M":"Tactical Air Control Party-Modernization",TASS:"Tactical Automated Security System",TBD:"To Be Determined","TCM-TR":"TRADOC Capabilities Manager-Tactical Radios",TCRA:"test capability readiness assessment",TCRAs:"test capability readiness assessments",TCT:"Total Contract Training",TCTO:"Time Compliance Technical Order",TD:"Test Director OR Technical Director OR Technology Development OR Technology Director","TD&E":"Tactics Development and Evaluation",TDM:"Test Design Manager",TDP:"Technical Data Package",TDR:"Test Design Requirement",TDS:"Technology Development Strategy",TDSB:"Test Data Scoring Board",TDY:"Temporary Duty",TE:"Technical Editor OR Test Evaluation",TEI:"Text Element Identifiers",TEMP:"Test and Evaluation Master Plan",TEMPEST:"Transient Electromagnetic Pulse Surveillance Technology",TEO:"Technology Executive Officers",TES:"Test and Evaluation Strategy",TFI:"Total Force Integration",TIPP:"Test Investment Planning and Programming",TIPT:"Test Integrated Product Team",TIR:"Test Incident Report",TIS:"Test Information Sheet",TISP:"Tailored Information Support Plan",TKA:"Tail Kit Assembly",TLDHS:"Target Location, Designation, and Hand-Off System",TLE:"Target Location Error",TM:"Technical Manual OR Telemetry OR Test Manager",TMCR:"Technical Manual Contract Requirement",TMDE:"Test Measurement Diagnostic Equipment",TMIPJ:"Theater Medical Information Program-Joint",TMLA:"Triple Missile Launcher Adapter",TMRR:"Technology Maturation & Risk Reduction (phase)",TMSS:"Technical Manual Specifications and Standards",TMT:"Task Management Tool",TNMCM:"Total Not Mission Capable-Maintenance",TNMCS:"Total Not Mission Capable-Supply",TO:"Tasking Order OR Technical Order",TOA:"Total Obligation Authority",TOAC:"Technical Order Advisory Council",TOC:"Tactical Operation Center OR Total Ownership Cost OR Table of Contents",TODO:"Technical Order Distribution Office",TOMA:"Technical Order Management Agency",TPCF:"Test Program Case File",TPM:"Technical Performance Measure OR Test Program Management",TPP:"Technology Protection Plan",TPS:"Test Program Set",TPT:"Training Planning Team",TPWG:"Test Plan Working Group",TR:"Technical Review",TRA:"Technology Readiness Assessment",TRADOC:"Training and Doctrine Command (US Army)",TRB:"Technical Review Board",TRD:"Technical Requirements Document",TRL:"Technology Readiness Level",TRM:"Technology Reference Model OR Test Resource Manager",TRMC:"Test Resource Management Center",TRP:"Test Resource Plan",TRR:"Test Readiness Review",TS:"Test Squadron OR Top Secret",TSN:"Trusted Systems & Networks",TSP:"Test Support Plan OR Transfer Support Plan OR Transition Support Plan","TS-PGM":"Training System Product Group Manager",TSPI:"Time / Space / Position Information",TSRA:"Training System Requirements Analysis",TSWG:"Threat Systems Working Group",TTCP:"The Technology Cooperation Program",TTP:"Tactics, Techniques, and Procedures OR Technology Transition Plan",TV:"Technical View",TW:"Test Wing",UAI:"Universal Armament",UAS:"Unmanned Aerial Systems",UAV:"Unmanned Aerial Vehicle",UC:"Unified Capabilities",UCA:"Undefinitized Contract Action",UCC:"Unified Combatant Commander",UHF:"Ultra-High Frequency",UID:"Unique Identification number",UIF:"Unfavorable Information File",UII:"Unique Item Identifier",UIPE:"Uniform Integrated Protection Ensemble",UJTL:"Universal Joint Task List",ULB:"Underwater Locator Beacon",ULO:"Unliquidated Obligation",UON:"Urgent Operational Need",UOTT:"US Operational Test Team",UP:"Unified Platform",URA:"User Representative Agency",URL:"Uniform Resource Locator",URN:"Unit Reference Number",USAF:"United States Air Force",USAFWC:"United States Air Force Warfare Center",USB:"Universal Serial Bus",USC:"United States Code",USD:"Undersecretary of Defense",USecAF:"Under Secretary of the Air Force",USMC:"United States Marine Corps",USSF:"United States Space Force",USSOCOM:"U.S. Special Operations Command",UTC:"Coordinated Universal Time",UTTR:"Utah Test and Training Range","V&V":"Verification and Validation",VCJCS:"Vice Chairman of the Joint Chiefs of Staff",VCSAF:"Vice Chief of Staff of the United States Air Force",VCSO:"Vice Chief of Space Operations",VE:"Value Engineering",VECP:"Value Engineering Change Proposal",VEP:"Value Engineering Proposal",VHF:"Very High Frequency",VIDOC:"Visual Information Documentation",VIM:"Visual Information Manager",VMC:"Visual Meteorological Conditions",VML:"Vulnerable to Move List",VMP:"Vulnerability Management Process",VOLT:"Validated Online Lifecycle Threat",VPV:"Virtual Prime Vendor",VSP:"Verification Status Page",VSTAR:"Virtual System Threat Assessment Report",VTC:"Video Teleconference","VV&A":"Verification, Validation and Accreditation",WAS:"Wide Area Surveillance",WAWF:"Wide Area Workflow",WBS:"Work Breakdown Schedule",WCF:"Working Capital Fund",WIPT:"WorkingLevel Integrated Product Team",WIT:"Watch Item Tracking",WMA:"Warfighting Mission Area",WMD:"weapons of mass destruction",WRAP:"Warfighter Rapid Acquisition Process","WS3 SLEP":"Weapons Storage and Security System Service Life Extension Program",WSEP:"Weapon System Evaluation Program",WSER:"Weapon System Enterprise Reviews","WSF-EO/IR":"Weather Satellite Follow-on Electro-Optical /Infra-Red","WSF-M":"Weather Satellite Follow-on Microwave",WSI:"Weapon System Integration OR Weapon System Integrity",WSIG:"Weapon System Integrity Guide",WSIP:"Weapon System Integrity Program",WSMR:"White Sands Missile Range",WSSP:"Weapons System Support Program",WX:"Weather",XDR:"Extended Data Rate",YTD:"Year to Date"}}}],extensions:[".mdx",".md"],defaultLayouts:{},lessBabel:!1,remarkPlugins:[],rehypePlugins:[],mediaTypes:["text/markdown","text/x-markdown"],root:"/home/t42/Documents/programming/Projects/OT_Guide/IL-2 Guide"}},{plugin:n("b9Nj"),options:{plugins:[],trackingId:null,head:!0,anonymize:!1}},{plugin:n("GddB"),options:{plugins:[]}}]},M53A:function(e,t,n){e.exports=n.p+"static/logo-8619e329fe17a156b627acc1b8227098.svg"},ME5O:function(e,t,n){"use strict";t.a={animationIterationCount:1,borderImageOutset:1,borderImageSlice:1,borderImageWidth:1,boxFlex:1,boxFlexGroup:1,boxOrdinalGroup:1,columnCount:1,columns:1,flex:1,flexGrow:1,flexPositive:1,flexShrink:1,flexNegative:1,flexOrder:1,gridRow:1,gridRowEnd:1,gridRowSpan:1,gridRowStart:1,gridColumn:1,gridColumnEnd:1,gridColumnSpan:1,gridColumnStart:1,msGridRow:1,msGridRowSpan:1,msGridColumn:1,msGridColumnSpan:1,fontWeight:1,lineHeight:1,opacity:1,order:1,orphans:1,tabSize:1,widows:1,zIndex:1,zoom:1,WebkitLineClamp:1,fillOpacity:1,floodOpacity:1,stopOpacity:1,strokeDasharray:1,strokeDashoffset:1,strokeMiterlimit:1,strokeOpacity:1,strokeWidth:1}},MMVs:function(e,t,n){e.exports=function(){var e=!1;-1!==navigator.appVersion.indexOf("MSIE 10")&&(e=!0);var t,n=[],r="object"==typeof document&&document,a=e?r.documentElement.doScroll("left"):r.documentElement.doScroll,i=r&&(a?/^loaded|^c/:/^loaded|^i|^c/).test(r.readyState);return!i&&r&&r.addEventListener("DOMContentLoaded",t=function(){for(r.removeEventListener("DOMContentLoaded",t),i=1;t=n.shift();)t()}),function(e){i?setTimeout(e,0):n.push(e)}}()},MiSq:function(e,t,n){"use strict";n.d(t,"a",(function(){return g}));var r=function(e){for(var t,n=0,r=0,a=e.length;a>=4;++r,a-=4)t=1540483477*(65535&(t=255&e.charCodeAt(r)|(255&e.charCodeAt(++r))<<8|(255&e.charCodeAt(++r))<<16|(255&e.charCodeAt(++r))<<24))+(59797*(t>>>16)<<16),n=1540483477*(65535&(t^=t>>>24))+(59797*(t>>>16)<<16)^1540483477*(65535&n)+(59797*(n>>>16)<<16);switch(a){case 3:n^=(255&e.charCodeAt(r+2))<<16;case 2:n^=(255&e.charCodeAt(r+1))<<8;case 1:n=1540483477*(65535&(n^=255&e.charCodeAt(r)))+(59797*(n>>>16)<<16)}return(((n=1540483477*(65535&(n^=n>>>13))+(59797*(n>>>16)<<16))^n>>>15)>>>0).toString(36)},a=n("ME5O"),i=n("4qRI"),o=/[A-Z]|^ms/g,s=/_EMO_([^_]+?)_([^]*?)_EMO_/g,c=function(e){return 45===e.charCodeAt(1)},l=function(e){return null!=e&&"boolean"!=typeof e},u=Object(i.a)((function(e){return c(e)?e:e.replace(o,"-$&").toLowerCase()})),d=function(e,t){switch(e){case"animation":case"animationName":if("string"==typeof t)return t.replace(s,(function(e,t,n){return f={name:t,styles:n,next:f},t}))}return 1===a.a[e]||c(e)||"number"!=typeof t||0===t?t:t+"px"};function p(e,t,n,r){if(null==n)return"";if(void 0!==n.__emotion_styles)return n;switch(typeof n){case"boolean":return"";case"object":if(1===n.anim)return f={name:n.name,styles:n.styles,next:f},n.name;if(void 0!==n.styles){var a=n.next;if(void 0!==a)for(;void 0!==a;)f={name:a.name,styles:a.styles,next:f},a=a.next;return n.styles+";"}return function(e,t,n){var r="";if(Array.isArray(n))for(var a=0;a1){c={types:["template-string","string"],content:e.content.slice(1)};var n={types:["operator"],content:e.content.charAt(0)};return Object(A.d)(o.Fragment,{key:e+t},Object(A.d)("span",Object(f.a)({},i({token:n,key:t}),{style:l})),Object(A.d)("span",i({token:c,key:t})))}return Object(A.d)("span",Object(f.a)({},i({token:e,key:t}),{style:l}))}return Object(A.d)("span",i({token:e,key:t}))})))})))}))},T=function(e){var t=e.children,n=Object(g.a)(e,["children"]);return t?Object(A.d)("a",{href:n.href,target:"_blank",rel:"noopener noreferrer"},t):null},E=Object(m.a)("pre",{target:"e2z1ahw0"})("padding:16px;background:",(function(e){return e.theme.colors.preFormattedText}),";"),P={h1:function(e){return Object(A.d)("h1",Object(f.a)({className:"heading1",id:e.children.replace(/\s+/g,"").toLowerCase()},e))},p:function(e){return Object(A.d)("p",Object(f.a)({className:"paragraph"},e))},pre:function(e){return Object(A.d)(E,null,Object(A.d)("pre",e))},code:O,a:T},R=n("lSNA"),I=n.n(R),M=n("gRFL");n("pVnL"),n("2mql");function w(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}var D=function(e,t){return"function"==typeof t?t(e):function(e){for(var t=1;t=e.length?{done:!0}:{done:!1,value:e[r++]}}}throw new TypeError("Invalid attempt to iterate non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}return(n=e[Symbol.iterator]()).next.bind(n)}function ne(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);nt.label?1:0}))}));var s=z.a.gatsby&&z.a.gatsby.trailingSlash?r.length-2:r.length-1,c=a.findIndex((function(e){return e.label===r[s]}));return a.length&&e.items.unshift(a.splice(c,1)[0]),e}),t)}(t)}))[0],a={};n.items.forEach((function(e){z.a.sidebar.collapsedNav&&z.a.sidebar.collapsedNav.includes(e.url)?a[e.url]=!0:a[e.url]=!1}));var i=Object(o.useState)(a),s=i[0],c=i[1];return Object(A.d)(Z,Object(f.a)({className:(z.a.sidebar.frontLine?"showFrontLine":"hideFrontLine")+" firstLevel",setCollapsed:function(e){var t;c(ee(ee({},s),{},((t={})[e]=!s[e],t)))},collapsed:s},n))};function ae(){return(ae=Object.assign||function(e){for(var t=1;t=0||(a[n]=e[n]);return a}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(a[n]=e[n])}return a}var oe=Object(o.forwardRef)((function(e,t){var n=e.color,r=void 0===n?"currentColor":n,a=e.size,i=void 0===a?24:a,o=ie(e,["color","size"]);return s.a.createElement("svg",ae({ref:t,xmlns:"http://www.w3.org/2000/svg",width:i,height:i,viewBox:"0 0 24 24",fill:"none",stroke:r,strokeWidth:"2",strokeLinecap:"round",strokeLinejoin:"round"},o),s.a.createElement("path",{d:"M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"}),s.a.createElement("polyline",{points:"15 3 21 3 21 9"}),s.a.createElement("line",{x1:"10",y1:"14",x2:"21",y2:"3"}))}));oe.displayName="ExternalLink";var se=oe;var ce=Object(m.a)((function(e){var t=e.className,n=(e.active,e.level,Object(g.a)(e,["className","active","level"]));return Object(A.d)("li",{className:t},Object(A.d)("a",Object(f.a)({href:n.to},n,{target:"_blank",rel:"noopener noreferrer"}),n.children))}),{target:"e1cpd07x0"})("list-style:none;a{color:#5c6975;text-decoration:none;font-weight:",(function(e){return 0===e.level?700:400}),";padding:0.45rem 0 0.45rem ",(function(e){return 2+1*(e.level||0)}),"rem;display:block;position:relative;&:hover{color:#2dc4f3 !important;}",(function(e){return e.active&&"\n // color: #663399;\n border-color: rgb(230,236,241) !important;\n border-style: solid none solid solid;\n border-width: 1px 0px 1px 1px;\n background-color: #fff;\n "})," svg{float:right;margin-right:1rem;}}"),le=Object(m.a)("aside",{target:"e1cpd07x1"})({name:"8uxxw2",styles:"width:100%;height:100vh;overflow:auto;position:fixed;padding-left:0px;position:-webkit-sticky;position:-moz-sticky;position:sticky;top:0;padding-right:0;-webkit-box-shadow:-1px 0px 4px 1px rgba(175,158,232,0.4);@media only screen and (max-width:1023px){width:100%;height:100vh;}@media (min-width:767px) and (max-width:1023px){padding-left:0;}@media only screen and (max-width:767px){padding-left:0px;height:auto;}"}),ue=Object(m.a)((function(e){return Object(A.d)("li",e,Object(A.d)("hr",null))}),{target:"e1cpd07x2"})({name:"1q387v1",styles:"list-style:none;padding:0.5rem 0;hr{margin:0;padding:0;border:0;border-bottom:1px solid #ede7f3;}"}),de=function(e){e.location;return Object(A.d)(u.StaticQuery,{query:"2619113677",render:function(e){var t=e.allMdx;return Object(A.d)(le,null,z.a.sidebar.title?Object(A.d)("div",{className:"sidebarTitle hiddenMobile",dangerouslySetInnerHTML:{__html:z.a.sidebar.title}}):null,Object(A.d)("ul",{className:"sideBarUL"},Object(A.d)(re,{edges:t.edges}),z.a.sidebar.links&&z.a.sidebar.links.length>0&&Object(A.d)(ue,null),z.a.sidebar.links.map((function(e,t){if(""!==e.link&&""!==e.text)return Object(A.d)(ce,{key:t,to:e.link},e.text,Object(A.d)(se,{size:14}))}))))}})},pe=n("ZIiI"),fe=!(!z.a.header.search||!z.a.header.search.enabled),me=[];fe&&z.a.header.search.indexName&&me.push({name:""+z.a.header.search.indexName,title:"Results",hitComp:"PageHit"});var ge=S()({loader:function(){return Promise.all([n.e(0),n.e(8)]).then(n.bind(null,"GMNA"))},loading:v});function he(){var e=document.getElementById("navbar");"topnav"===e.className?e.className+=" responsive":e.className="topnav"}var ye=Object(m.a)("div",{target:"e1uaxj470"})("height:60px;box-shadow:0 3px 6px 0 rgba(0,0,0,0.16);background-color:#f8f8f8;position:relative;display:none;background:",(function(e){return e.isDarkThemeActive?"#001932":void 0}),";@media (max-width:767px){display:block;}"),be=function(e){var t=e.location,r=e.isDarkThemeActive,a=e.toggleActiveTheme;return Object(A.d)(u.StaticQuery,{query:"1685914912",render:function(e){var i=n("M53A"),o=n("BFUG"),s=(n("ai/O"),n("3hAw"),e.site.siteMetadata),c=s.headerTitle,l=s.helpUrl,u=s.tweetText,d=s.logo,p=s.headerLinks,f=""!==d.link?d.link:"https://www.afotec.af.mil/";return Object(A.d)("div",{className:"navBarWrapper"},Object(A.d)("nav",{className:"navBarDefault"},Object(A.d)("div",{className:"navBarHeader"},Object(A.d)(U,{to:f,className:"navBarBrand"},Object(A.d)("img",{className:"img-responsive displayInline",src:""!==d.image?d.image:i,alt:"logo"})),Object(A.d)("div",{className:"headerTitle displayInline",dangerouslySetInnerHTML:{__html:c}})),z.a.header.social?Object(A.d)("ul",{className:"socialWrapper visibleMobileView",dangerouslySetInnerHTML:{__html:z.a.header.social}}):null,Object(A.d)("div",{id:"navbar",className:"topnav"},Object(A.d)("div",{className:"visibleMobile"},Object(A.d)(de,{location:t}),Object(A.d)("hr",null)),Object(A.d)("ul",{className:"navBarUL navBarNav navBarULRight"},p.map((function(e,t){if(""!==e.link&&""!==e.text)return Object(A.d)("li",{key:t},Object(A.d)("a",{className:"sidebarLink",href:e.link,target:"_blank",rel:"noopener noreferrer",dangerouslySetInnerHTML:{__html:e.text}}))})),""!==l?Object(A.d)("li",null,Object(A.d)("a",{href:l},Object(A.d)("img",{src:pe,alt:"Help icon"}))):null,""!==u?Object(A.d)("li",null,Object(A.d)("a",{href:"https://twitter.com/intent/tweet?&text="+u,target:"_blank",rel:"noopener noreferrer"},Object(A.d)("img",{className:"shareIcon",src:o,alt:"Twitter"}))):null,""!==u?Object(A.d)("li",{className:"divider hiddenMobile"}):null,z.a.header.social?Object(A.d)("li",{className:"hiddenMobile"},Object(A.d)("ul",{className:"socialWrapper",dangerouslySetInnerHTML:{__html:z.a.header.social}})):null,Object(A.d)("li",null,Object(A.d)("div",{className:"headerTitleReleasable displayInline",dangerouslySetInnerHTML:{__html:"There are no releasability restrictions on this publication"}})),Object(A.d)("li",null,Object(A.d)($,{isDarkThemeActive:r,toggleActiveTheme:a})),fe?Object(A.d)("div",{className:"searchWrapper hiddenMobile navBarUL"},Object(A.d)(ge,{collapse:!0,indices:me})):null))),Object(A.d)(ye,{isDarkThemeActive:r},Object(A.d)("div",{className:"navBarDefault removePadd"},Object(A.d)("span",{onClick:he,className:"navBarToggle",onKeyDown:he,role:"button",tabIndex:0},Object(A.d)("span",{className:"iconBar"}),Object(A.d)("span",{className:"iconBar"}),Object(A.d)("span",{className:"iconBar"}))),fe?Object(A.d)("div",{className:"searchWrapper"},Object(A.d)(ge,{collapse:!0,indices:me})):null))}})},Se=n("TqVZ"),Ae=n("MiSq"),ve=n("SIPS");function Ce(e,t){if(void 0===e.inserted[t.name])return e.insert("",t,e.sheet,!0)}function Oe(e,t,n){var r=[],a=Object(ve.a)(e,r,n);return r.length<2?n:a+t(r)}var Te=function e(t){for(var n="",r=0;r a{background-color:#2dc4f3;color:#fff !important;}.firstLevel ul li .collapser svg path{fill:#fff !important;}.active .collapser > svg > path{fill:#001933 !important;}.firstLevel ul .item ul .item{border-left:1px solid #e6ecf1;}.sideBarUL .item{list-style:none;padding:0;}.sideBarUL .item > a{color:#2dc4f3;text-decoration:none;display:flex;align-items:center;position:relative;width:100%;padding-right:35px;padding-left:15px;}.showFrontLine .item > a:hover{background-color:#001933;}.showFrontLine .active > a{background-color:#001933;}.sideBarUL .item .item{margin-left:16px;}.firstLevel > ul > .item{margin-left:0 !important;}.showFrontLine .item .item{border-left:1px solid #e6ecf1;border-left-color:rgb(230,236,241);padding:0;width:calc(100% - 16px) !important;}.showFrontLine .item .active > a{border-color:rgb(230,236,241) !important;border-style:solid none solid solid;border-width:1px 0px 1px 1px;background-color:#2dc4f3 !important;color:#fff;}.titleWrapper{display:flex;align-items:center;padding-bottom:40px;border-bottom:1px solid rgb(230,236,241);margin-bottom:32px;}.gitBtn{height:30px;min-height:30px;display:flex;align-items:center;}.gitBtn img{width:15px;display:inline-block;margin-right:5px;}.addPaddTopBottom{padding:50px 0;}.preRightWrapper{display:block;margin:0px;flex:1 1 0%;padding:16px;text-align:right;}.smallContent{display:block;margin:0px;padding:0px;color:#6e6e6e;}.smallContent span{font-size:12px;line-height:1.625;font-weight:400;}.nextRightWrapper{display:block;margin:0px;padding:16px;flex:1 1 0%;}table{padding:0;}table tr{border-top:1px solid #cccccc;margin:0;padding:0;}table tr:nth-child(2n){background-color:#f8f8f8;}table tr th{font-weight:bold;border:1px solid #cccccc;text-align:left;margin:0;padding:6px 13px;}table tr td{border:1px solid #cccccc;text-align:left;margin:0;padding:6px 13px;}table tr th:first-child,table tr td:first-child{margin-top:0;}table tr th:last-child,table tr td:last-child{margin-bottom:0;}img{max-width:100%;}.communitySection{font-size:24px;font-weight:700;}.authorSection{padding:20px 0;}.authorSection,.authorName{display:flex;align-items:center;}.authorImg img{width:75px;height:75px;border-radius:50%;min-width:75px;max-width:75px;min-height:75px;max-height:75px;}.authorDetails{padding-left:10px;}.authorDesc{padding-top:5px;font-size:14px;}.authorName img{margin-left:10px;display:inline-block;width:20px;}.authorName img:hover{opacity:0.7;}.heading1{font-size:26px;font-weight:800;line-height:1.5;margin-bottom:16px;margin-top:32px;}.heading2{font-size:24px;font-weight:700;line-height:1.5;margin-bottom:16px;margin-top:32px;}.heading3{font-size:20px;font-weight:600;line-height:1.5;margin-bottom:16px;margin-top:32px;}.heading4{font-size:18px;font-weight:500;line-height:1.5;margin-bottom:16px;margin-top:32px;}.heading5{font-size:16px;font-weight:400;line-height:1.5;margin-bottom:16px;margin-top:32px;}.heading6{font-size:14px;font-weight:300;line-height:1.5;margin-bottom:16px;margin-top:32px;}.paragraph{margin:16px 0px 32px;line-height:1.625;}.pre{font-size:14px;margin:0px;padding:16px;overflow:auto;}.topnav{-webkit-transition:top 0.5s,bottom 0.5s;}@media (max-width:767px){.formElement svg path{fill:#001934;}.visibleMobileView{display:block !important;}.searchInput{color:#001934;}.socialWrapper{position:absolute;right:10px;top:29px;}.responsive{margin-top:15px;position:relative;padding-bottom:20px;border-top:1px solid #fff;}.headerTitle{padding-right:50px;font-size:16px;}.navBarBrand{min-height:40px;}.navBarBrand img{margin-right:8px;}.topnav.responsive .visibleMobile{display:block;}.topnav .navBarUL{display:none;}.topnav.responsive .navBarUL{display:block;text-align:left;}.hiddenMobile{display:none !important;}hr{margin-top:0;margin-bottom:0;}.navBarParent{display:block;}.separator{margin-top:20px;margin-bottom:20px;}.navBarULRight{position:static;}.navBarUL{display:flex;align-items:center;margin:7.5px 0px;}.navBarUL li{height:37px;}.navBarUL li a{font-size:14px;padding:10px 15px;}.navBarDefault{display:block;height:auto;}.navBarToggle{margin-right:0;display:block;position:absolute;left:11px;top:15px;background:#fff;}.navBarHeader{display:flex;min-width:auto;padding-right:0;align-items:center;}.navBarBrand{font-size:20px;padding:0 0;padding-left:0;flex:initial;padding-right:15px;}.titleWrapper{padding:0 15px;display:block;}.gitBtn{display:inline-block;}.mobileView{text-align:left !important;padding-left:0 !important;}.searchWrapper{padding:0px 0;padding-top:0px;position:absolute;bottom:0px;width:calc(100% - 70px);position:absolute;left:40px;top:8px;}.hitWrapper{width:100%;right:0;top:35px;max-height:fit-content;position:static;}}@media (min-width:768px) and (max-width:991px){.navBarDefault{padding:10px;}.navBarBrand{font-size:22px;}.navBarHeader{min-width:240px;flex:initial;}.divider{margin:0 5px;height:20px;}.hitWrapper{max-width:500px;}.navBarUL li a{padding:10px 5px;}.searchWrapper{padding-left:0px;}}"}),Ie=function(e){function t(){for(var t,n=arguments.length,r=new Array(n),a=0;a0)r.edges.map((function(e,r){var a;void 0!==e&&(e.node.fields.slug!==t.pathname&&z.a.gatsby.pathPrefix+e.node.fields.slug!==t.pathname||e.node.tableOfContents.items&&(a=e.node.tableOfContents.items.map((function(e,t){var n=e.title?e.title.replace(/\s+/g,"").toLowerCase():"#";return Object(A.d)(De,{key:t,to:"#"+n,level:1},e.title)})))),a&&(n=a)}));return n&&n.length?Object(A.d)(we,null,Object(A.d)("ul",{className:"rightSideBarUL"},Object(A.d)("li",{className:"rightSideTitle"},"CONTENTS"),n)):Object(A.d)(we,null,Object(A.d)("ul",null))}})};n("vg9a");var ke=Object(m.a)("div",{target:"edsd0s90"})("display:flex;justify-content:space-between;background:",(function(e){return e.theme.colors.background}),";.sideBarUL li a{color:",(function(e){return e.theme.colors.text}),";}.sideBarUL .item > a:hover{background-color:#2dc4f3;color:#fff !important;}@media only screen and (max-width:767px){display:block;}"),Le=Object(m.a)("main",{target:"edsd0s91"})("display:flex;flex-grow:1;margin:0px 88px;padding-top:3rem;background:",(function(e){return e.theme.colors.background}),";table tr{background:",(function(e){return e.theme.colors.background}),";}@media only screen and (max-width:1023px){padding-left:0;margin:0 10px;padding-top:3rem;}"),Fe=Object(m.a)("div",{target:"edsd0s92"})({name:"14zj307",styles:"@media only screen and (max-width:50rem){width:100%;position:relative;}"}),je=Object(m.a)("div",{target:"edsd0s93"})({name:"192n44p",styles:"width:298px;"}),Ne=Object(m.a)("div",{target:"edsd0s94"})({name:"gqp3x7",styles:"width:224px;"}),_e=function(e){var t=e.children,n=e.location;return Object(A.d)(Ie,{location:n},Object(A.d)(Me.MDXProvider,{components:P},Object(A.d)(ke,null,Object(A.d)(je,{className:"hiddenMobile"},Object(A.d)(de,{location:n})),z.a.sidebar.title?Object(A.d)("div",{className:"sidebarTitle sideBarShow",dangerouslySetInnerHTML:{__html:z.a.sidebar.title}}):null,Object(A.d)(Le,null,Object(A.d)(Fe,null,t)),Object(A.d)(Ne,{className:"hiddenMobile"},Object(A.d)(xe,{location:n})))))},Be=Object(m.a)("div",{target:"e1svfi2a0"})("margin:0px;padding:0px;width:auto;display:grid;grid-template-rows:auto;column-gap:24px;grid-template-columns:calc(50% - 8px) calc(50% - 8px);.previousBtn{cursor:pointer;-moz-box-align:center;-moz-box-direction:normal;-moz-box-orient:horizontal;margin:0px;padding:0px;position:relative;display:flex;flex-direction:row;align-items:center;place-self:stretch;border-radius:3px;border:1px solid rgb(230,236,241);transition:border 200ms ease 0s;box-shadow:rgba(116,129,141,0.1) 0px 3px 8px 0px;text-decoration:none;background-color:",(function(e){return e.theme.colors.background}),";color:",(function(e){return e.theme.colors.text}),";}.nextBtn{cursor:pointer;-moz-box-align:center;-moz-box-direction:normal;-moz-box-orient:horizontal;margin:0px;padding:0px;position:relative;display:flex;flex-direction:row;align-items:center;place-self:stretch;border-radius:3px;border:1px solid rgb(230,236,241);transition:border 200ms ease 0s;box-shadow:rgba(116,129,141,0.1) 0px 3px 8px 0px;text-decoration:none;background-color:",(function(e){return e.theme.colors.background}),";color:",(function(e){return e.theme.colors.text}),";}.nextBtn:hover,.previousBtn:hover{text-decoration:none;border:1px solid #2dc4f3;}.nextBtn:hover .rightArrow,.previousBtn:hover .leftArrow{color:#2dc4f3;}.leftArrow{display:block;margin:0px;color:rgb(157,170,182);flex:0 0 auto;font-size:24px;transition:color 200ms ease 0s;padding:16px;padding-right:16px;}.rightArrow{flex:0 0 auto;font-size:24px;transition:color 200ms ease 0s;padding:16px;padding-left:16px;display:block;margin:0px;color:rgb(157,170,182);}.nextPreviousTitle{display:block;margin:0px;padding:0px;transition:color 200ms ease 0s;}.nextPreviousTitle span{font-size:16px;line-height:1.5;font-weight:500;}@media (max-width:767px){display:block;padding:0 15px;.previousBtn{margin-bottom:20px;}}"),Ge=function(e){var t,n=e.mdx,r=e.nav,a=(r.map((function(e,r){e&&e.url===n.fields.slug&&(t=r)})),{}),i={};return void 0===t?(r[0]&&(a.url=r[0].url,a.title=r[0].title),i.url=null,i.title=null,t=-1):0===t?(a.url=r[t+1]?r[t+1].url:null,a.title=r[t+1]?r[t+1].title:null,i.url=null,i.title=null):t===r.length-1?(a.url=null,a.title=null,i.url=r[t-1]?r[t-1].url:null,i.title=r[t-1]?r[t-1].title:null):t&&(a.url=r[t+1].url,a.title=r[t+1].title,r[t-1]&&(i.url=r[t-1].url,i.title=r[t-1].title)),Object(A.d)(Be,null,i.url&&t>=0?Object(A.d)(U,{to:r[t-1].url,className:"previousBtn"},Object(A.d)("div",{className:"leftArrow"},Object(A.d)("svg",{preserveAspectRatio:"xMidYMid meet",height:"1em",width:"1em",fill:"none",xmlns:"http://www.w3.org/2000/svg",viewBox:"0 0 24 24",strokeWidth:"2",strokeLinecap:"round",strokeLinejoin:"round",stroke:"currentColor",className:"_13gjrqj"},Object(A.d)("g",null,Object(A.d)("line",{x1:"19",y1:"12",x2:"5",y2:"12"}),Object(A.d)("polyline",{points:"12 19 5 12 12 5"})))),Object(A.d)("div",{className:"preRightWrapper"},Object(A.d)("div",{className:"smallContent"},Object(A.d)("span",null,"Previous")),Object(A.d)("div",{className:"nextPreviousTitle"},Object(A.d)("span",null,r[t-1].title)))):null,a.url&&t>=0?Object(A.d)(U,{to:r[t+1].url,className:"nextBtn"},Object(A.d)("div",{className:"nextRightWrapper"},Object(A.d)("div",{className:"smallContent"},Object(A.d)("span",null,"Next")),Object(A.d)("div",{className:"nextPreviousTitle"},Object(A.d)("span",null,r[t+1]&&r[t+1].title))),Object(A.d)("div",{className:"rightArrow"},Object(A.d)("svg",{preserveAspectRatio:"xMidYMid meet",height:"1em",width:"1em",fill:"none",xmlns:"http://www.w3.org/2000/svg",viewBox:"0 0 24 24",strokeWidth:"2",strokeLinecap:"round",strokeLinejoin:"round",stroke:"currentColor",className:"_13gjrqj"},Object(A.d)("g",null,Object(A.d)("line",{x1:"5",y1:"12",x2:"19",y2:"12"}),Object(A.d)("polyline",{points:"12 5 19 12 12 19"}))))):null)};var Ue=Object(m.a)("h1",{target:"e17yakb10"})("font-size:32px;line-height:1.5;font-weight:500;border-left:2px solid #2dc4f3;padding:0 16px;flex:1;margin-top:0;padding-top:0;color:",(function(e){return e.theme.colors.heading}),";"),We=Object(m.a)("div",{target:"e17yakb11"})({name:"qu2iew",styles:"padding:1rem 1.5rem;text-align:right;a{font-size:14px;font-weight:500;line-height:1em;text-decoration:none;color:#555;border:1px solid rgb(211,220,228);cursor:pointer;border-radius:3px;transition:all 0.2s ease-out 0s;text-decoration:none;color:rgb(36,42,49);background-color:rgb(255,255,255);box-shadow:rgba(116,129,141,0.1) 0px 1px 1px 0px;height:30px;padding:5px 16px;&:hover{background-color:rgb(245,247,249);}}"}),ze=Object(m.a)("div",{target:"e17yakb12"})("max-width:750px;color:",(function(e){return e.theme.colors.text}),";ul,ol{-webkit-padding-start:40px;-moz-padding-start:40px;-o-padding-start:40px;margin:24px 0px;padding:0px 0px 0px 2em;li{font-size:16px;line-height:1.8;font-weight:400;}}a{transition:color 0.15s;color:",(function(e){return e.theme.colors.link}),";}code{border:1px solid #ede7f3;border-radius:4px;padding:2px 6px;font-size:0.9375em;background:",(function(e){return e.theme.colors.background}),";}@media (max-width:767px){padding:0 15px;}"),He=function(){var e=Object(o.useState)(!0),t=e[0],n=e[1],r=Object(o.useState)(0),a=r[0],i=r[1],s=function(){window.scrollY>a?n(!0):n(!1),i(window.scrollY)};Object(o.useEffect)((function(){return window.addEventListener("scroll",s),window.onscroll=function(){0===window.scrollY&&(n(!0),i(0))},function(){window.removeEventListener("scroll",s)}}));return Object(A.d)("button",{className:"mobileScrollUpButton "+(t?"":"fade"),onClick:function(){window.scroll(0,0)}},"Scroll to top")};function qe(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function Je(e){for(var t=1;te.length)return;if(!(v instanceof c)){if(g&&S!=t.length-1){if(p.lastIndex=A,!(R=p.exec(e)))break;for(var C=R.index+(m?R[1].length:0),O=R.index+R[0].length,T=S,E=A,P=t.length;T=(E+=t[T].length)&&(++S,A=E);if(t[S]instanceof c)continue;I=T-S,v=e.slice(A,E),R.index-=A}else{p.lastIndex=0;var R=p.exec(v),I=1}if(R){m&&(h=R[1]?R[1].length:0),O=(C=R.index+h)+(R=R[0].slice(h)).length;var M=v.slice(0,C),w=v.slice(O),D=[S,I];M&&(++S,A+=M.length,D.push(M));var x=new c(l,f?a.tokenize(R,f):R,y,R,g);if(D.push(x),w&&D.push(w),Array.prototype.splice.apply(t,D),1!=I&&a.matchGrammar(e,t,n,S,A,!0,l),o)break}else if(o)break}}}}},hooks:{add:function(){},run:function(e,t){}},tokenize:function(e,t,n){var r=[e],i=t.rest;if(i){for(var o in i)t[o]=i[o];delete t.rest}return a.matchGrammar(e,r,t,0,0,!1),r}},(i=a.Token=function(e,t,n,r,a){this.type=e,this.content=t,this.alias=n,this.length=0|(r||"").length,this.greedy=!!a}).stringify=function(e,t,n){if("string"==typeof e)return e;if("Array"===a.util.type(e))return e.map((function(n){return i.stringify(n,t,e)})).join("");var r={type:e.type,content:i.stringify(e.content,t,n),tag:"span",classes:["token",e.type],attributes:{},language:t,parent:n};if(e.alias){var o="Array"===a.util.type(e.alias)?e.alias:[e.alias];Array.prototype.push.apply(r.classes,o)}var s=Object.keys(r.attributes).map((function(e){return e+'="'+(r.attributes[e]||"").replace(/"/g,""")+'"'})).join(" ");return"<"+r.tag+' class="'+r.classes.join(" ")+'"'+(s?" "+s:"")+">"+r.content+""},a);o.languages.markup={comment://,prolog:/<\?[\s\S]+?\?>/,doctype:{pattern:/"'[\]]|"[^"]*"|'[^']*')+(?:\[(?:[^<"'\]]|"[^"]*"|'[^']*'|<(?!!--)|)*\]\s*)?>/i,greedy:!0,inside:{"internal-subset":{pattern:/(\[)[\s\S]+(?=\]>$)/,lookbehind:!0,greedy:!0,inside:null},string:{pattern:/"[^"]*"|'[^']*'/,greedy:!0},punctuation:/^$|[[\]]/,"doctype-tag":/^DOCTYPE/,name:/[^\s<>'"]+/}},cdata://i,tag:{pattern:/<\/?(?!\d)[^\s>\/=$<%]+(?:\s(?:\s*[^\s>\/=]+(?:\s*=\s*(?:"[^"]*"|'[^']*'|[^\s'">=]+(?=[\s>]))|(?=[\s/>])))+)?\s*\/?>/,greedy:!0,inside:{tag:{pattern:/^<\/?[^\s>\/]+/,inside:{punctuation:/^<\/?/,namespace:/^[^\s>\/:]+:/}},"attr-value":{pattern:/=\s*(?:"[^"]*"|'[^']*'|[^\s'">=]+)/,inside:{punctuation:[{pattern:/^=/,alias:"attr-equals"},/"|'/]}},punctuation:/\/?>/,"attr-name":{pattern:/[^\s>\/]+/,inside:{namespace:/^[^\s>\/:]+:/}}}},entity:[{pattern:/&[\da-z]{1,8};/i,alias:"named-entity"},/&#x?[\da-f]{1,8};/i]},o.languages.markup.tag.inside["attr-value"].inside.entity=o.languages.markup.entity,o.languages.markup.doctype.inside["internal-subset"].inside=o.languages.markup,o.hooks.add("wrap",(function(e){"entity"===e.type&&(e.attributes.title=e.content.replace(/&/,"&"))})),Object.defineProperty(o.languages.markup.tag,"addInlined",{value:function(e,t){var n={};n["language-"+t]={pattern:/(^$)/i,lookbehind:!0,inside:o.languages[t]},n.cdata=/^$/i;var r={"included-cdata":{pattern://i,inside:n}};r["language-"+t]={pattern:/[\s\S]+/,inside:o.languages[t]};var a={};a[e]={pattern:RegExp(/(<__[^>]*>)(?:))*\]\]>|(?!)/.source.replace(/__/g,(function(){return e})),"i"),lookbehind:!0,greedy:!0,inside:r},o.languages.insertBefore("markup","cdata",a)}}),o.languages.html=o.languages.markup,o.languages.mathml=o.languages.markup,o.languages.svg=o.languages.markup,o.languages.xml=o.languages.extend("markup",{}),o.languages.ssml=o.languages.xml,o.languages.atom=o.languages.xml,o.languages.rss=o.languages.xml,function(e){var t="\\b(?:BASH|BASHOPTS|BASH_ALIASES|BASH_ARGC|BASH_ARGV|BASH_CMDS|BASH_COMPLETION_COMPAT_DIR|BASH_LINENO|BASH_REMATCH|BASH_SOURCE|BASH_VERSINFO|BASH_VERSION|COLORTERM|COLUMNS|COMP_WORDBREAKS|DBUS_SESSION_BUS_ADDRESS|DEFAULTS_PATH|DESKTOP_SESSION|DIRSTACK|DISPLAY|EUID|GDMSESSION|GDM_LANG|GNOME_KEYRING_CONTROL|GNOME_KEYRING_PID|GPG_AGENT_INFO|GROUPS|HISTCONTROL|HISTFILE|HISTFILESIZE|HISTSIZE|HOME|HOSTNAME|HOSTTYPE|IFS|INSTANCE|JOB|LANG|LANGUAGE|LC_ADDRESS|LC_ALL|LC_IDENTIFICATION|LC_MEASUREMENT|LC_MONETARY|LC_NAME|LC_NUMERIC|LC_PAPER|LC_TELEPHONE|LC_TIME|LESSCLOSE|LESSOPEN|LINES|LOGNAME|LS_COLORS|MACHTYPE|MAILCHECK|MANDATORY_PATH|NO_AT_BRIDGE|OLDPWD|OPTERR|OPTIND|ORBIT_SOCKETDIR|OSTYPE|PAPERSIZE|PATH|PIPESTATUS|PPID|PS1|PS2|PS3|PS4|PWD|RANDOM|REPLY|SECONDS|SELINUX_INIT|SESSION|SESSIONTYPE|SESSION_MANAGER|SHELL|SHELLOPTS|SHLVL|SSH_AUTH_SOCK|TERM|UID|UPSTART_EVENTS|UPSTART_INSTANCE|UPSTART_JOB|UPSTART_SESSION|USER|WINDOWID|XAUTHORITY|XDG_CONFIG_DIRS|XDG_CURRENT_DESKTOP|XDG_DATA_DIRS|XDG_GREETER_DATA_DIR|XDG_MENU_PREFIX|XDG_RUNTIME_DIR|XDG_SEAT|XDG_SEAT_PATH|XDG_SESSION_DESKTOP|XDG_SESSION_ID|XDG_SESSION_PATH|XDG_SESSION_TYPE|XDG_VTNR|XMODIFIERS)\\b",n={pattern:/(^(["']?)\w+\2)[ \t]+\S.*/,lookbehind:!0,alias:"punctuation",inside:null},r={bash:n,environment:{pattern:RegExp("\\$"+t),alias:"constant"},variable:[{pattern:/\$?\(\([\s\S]+?\)\)/,greedy:!0,inside:{variable:[{pattern:/(^\$\(\([\s\S]+)\)\)/,lookbehind:!0},/^\$\(\(/],number:/\b0x[\dA-Fa-f]+\b|(?:\b\d+(?:\.\d*)?|\B\.\d+)(?:[Ee]-?\d+)?/,operator:/--?|-=|\+\+?|\+=|!=?|~|\*\*?|\*=|\/=?|%=?|<<=?|>>=?|<=?|>=?|==?|&&?|&=|\^=?|\|\|?|\|=|\?|:/,punctuation:/\(\(?|\)\)?|,|;/}},{pattern:/\$\((?:\([^)]+\)|[^()])+\)|`[^`]+`/,greedy:!0,inside:{variable:/^\$\(|^`|\)$|`$/}},{pattern:/\$\{[^}]+\}/,greedy:!0,inside:{operator:/:[-=?+]?|[!\/]|##?|%%?|\^\^?|,,?/,punctuation:/[\[\]]/,environment:{pattern:RegExp("(\\{)"+t),lookbehind:!0,alias:"constant"}}},/\$(?:\w+|[#?*!@$])/],entity:/\\(?:[abceEfnrtv\\"]|O?[0-7]{1,3}|x[0-9a-fA-F]{1,2}|u[0-9a-fA-F]{4}|U[0-9a-fA-F]{8})/};e.languages.bash={shebang:{pattern:/^#!\s*\/.*/,alias:"important"},comment:{pattern:/(^|[^"{\\$])#.*/,lookbehind:!0},"function-name":[{pattern:/(\bfunction\s+)\w+(?=(?:\s*\(?:\s*\))?\s*\{)/,lookbehind:!0,alias:"function"},{pattern:/\b\w+(?=\s*\(\s*\)\s*\{)/,alias:"function"}],"for-or-select":{pattern:/(\b(?:for|select)\s+)\w+(?=\s+in\s)/,alias:"variable",lookbehind:!0},"assign-left":{pattern:/(^|[\s;|&]|[<>]\()\w+(?=\+?=)/,inside:{environment:{pattern:RegExp("(^|[\\s;|&]|[<>]\\()"+t),lookbehind:!0,alias:"constant"}},alias:"variable",lookbehind:!0},string:[{pattern:/((?:^|[^<])<<-?\s*)(\w+?)\s[\s\S]*?(?:\r?\n|\r)\2/,lookbehind:!0,greedy:!0,inside:r},{pattern:/((?:^|[^<])<<-?\s*)(["'])(\w+)\2\s[\s\S]*?(?:\r?\n|\r)\3/,lookbehind:!0,greedy:!0,inside:{bash:n}},{pattern:/(^|[^\\](?:\\\\)*)(["'])(?:\\[\s\S]|\$\([^)]+\)|\$(?!\()|`[^`]+`|(?!\2)[^\\`$])*\2/,lookbehind:!0,greedy:!0,inside:r}],environment:{pattern:RegExp("\\$?"+t),alias:"constant"},variable:r.variable,function:{pattern:/(^|[\s;|&]|[<>]\()(?:add|apropos|apt|aptitude|apt-cache|apt-get|aspell|automysqlbackup|awk|basename|bash|bc|bconsole|bg|bzip2|cal|cat|cfdisk|chgrp|chkconfig|chmod|chown|chroot|cksum|clear|cmp|column|comm|composer|cp|cron|crontab|csplit|curl|cut|date|dc|dd|ddrescue|debootstrap|df|diff|diff3|dig|dir|dircolors|dirname|dirs|dmesg|du|egrep|eject|env|ethtool|expand|expect|expr|fdformat|fdisk|fg|fgrep|file|find|fmt|fold|format|free|fsck|ftp|fuser|gawk|git|gparted|grep|groupadd|groupdel|groupmod|groups|grub-mkconfig|gzip|halt|head|hg|history|host|hostname|htop|iconv|id|ifconfig|ifdown|ifup|import|install|ip|jobs|join|kill|killall|less|link|ln|locate|logname|logrotate|look|lpc|lpr|lprint|lprintd|lprintq|lprm|ls|lsof|lynx|make|man|mc|mdadm|mkconfig|mkdir|mke2fs|mkfifo|mkfs|mkisofs|mknod|mkswap|mmv|more|most|mount|mtools|mtr|mutt|mv|nano|nc|netstat|nice|nl|nohup|notify-send|npm|nslookup|op|open|parted|passwd|paste|pathchk|ping|pkill|pnpm|popd|pr|printcap|printenv|ps|pushd|pv|quota|quotacheck|quotactl|ram|rar|rcp|reboot|remsync|rename|renice|rev|rm|rmdir|rpm|rsync|scp|screen|sdiff|sed|sendmail|seq|service|sftp|sh|shellcheck|shuf|shutdown|sleep|slocate|sort|split|ssh|stat|strace|su|sudo|sum|suspend|swapon|sync|tac|tail|tar|tee|time|timeout|top|touch|tr|traceroute|tsort|tty|umount|uname|unexpand|uniq|units|unrar|unshar|unzip|update-grub|uptime|useradd|userdel|usermod|users|uudecode|uuencode|v|vdir|vi|vim|virsh|vmstat|wait|watch|wc|wget|whereis|which|who|whoami|write|xargs|xdg-open|yarn|yes|zenity|zip|zsh|zypper)(?=$|[)\s;|&])/,lookbehind:!0},keyword:{pattern:/(^|[\s;|&]|[<>]\()(?:if|then|else|elif|fi|for|while|in|case|esac|function|select|do|done|until)(?=$|[)\s;|&])/,lookbehind:!0},builtin:{pattern:/(^|[\s;|&]|[<>]\()(?:\.|:|break|cd|continue|eval|exec|exit|export|getopts|hash|pwd|readonly|return|shift|test|times|trap|umask|unset|alias|bind|builtin|caller|command|declare|echo|enable|help|let|local|logout|mapfile|printf|read|readarray|source|type|typeset|ulimit|unalias|set|shopt)(?=$|[)\s;|&])/,lookbehind:!0,alias:"class-name"},boolean:{pattern:/(^|[\s;|&]|[<>]\()(?:true|false)(?=$|[)\s;|&])/,lookbehind:!0},"file-descriptor":{pattern:/\B&\d\b/,alias:"important"},operator:{pattern:/\d?<>|>\||\+=|==?|!=?|=~|<<[<-]?|[&\d]?>>|\d?[<>]&?|&[>&]?|\|[&|]?|<=?|>=?/,inside:{"file-descriptor":{pattern:/^\d/,alias:"important"}}},punctuation:/\$?\(\(?|\)\)?|\.\.|[{}[\];\\]/,number:{pattern:/(^|\s)(?:[1-9]\d*|0)(?:[.,]\d+)?\b/,lookbehind:!0}},n.inside=e.languages.bash;for(var a=["comment","function-name","for-or-select","assign-left","string","environment","function","keyword","builtin","boolean","file-descriptor","operator","punctuation","number"],i=r.variable[1].inside,o=0;o]=?|[!=]=?=?|--?|\+\+?|&&?|\|\|?|[?*/~^%]/,punctuation:/[{}[\];(),.:]/},o.languages.c=o.languages.extend("clike",{comment:{pattern:/\/\/(?:[^\r\n\\]|\\(?:\r\n?|\n|(?![\r\n])))*|\/\*[\s\S]*?(?:\*\/|$)/,greedy:!0},"class-name":{pattern:/(\b(?:enum|struct)\s+(?:__attribute__\s*\(\([\s\S]*?\)\)\s*)?)\w+|\b[a-z]\w*_t\b/,lookbehind:!0},keyword:/\b(?:__attribute__|_Alignas|_Alignof|_Atomic|_Bool|_Complex|_Generic|_Imaginary|_Noreturn|_Static_assert|_Thread_local|asm|typeof|inline|auto|break|case|char|const|continue|default|do|double|else|enum|extern|float|for|goto|if|int|long|register|return|short|signed|sizeof|static|struct|switch|typedef|union|unsigned|void|volatile|while)\b/,function:/[a-z_]\w*(?=\s*\()/i,number:/(?:\b0x(?:[\da-f]+(?:\.[\da-f]*)?|\.[\da-f]+)(?:p[+-]?\d+)?|(?:\b\d+(?:\.\d*)?|\B\.\d+)(?:e[+-]?\d+)?)[ful]{0,4}/i,operator:/>>=?|<<=?|->|([-+&|:])\1|[?:~]|[-+*/%&|^!=<>]=?/}),o.languages.insertBefore("c","string",{macro:{pattern:/(^\s*)#\s*[a-z](?:[^\r\n\\/]|\/(?!\*)|\/\*(?:[^*]|\*(?!\/))*\*\/|\\(?:\r\n|[\s\S]))*/im,lookbehind:!0,greedy:!0,alias:"property",inside:{string:[{pattern:/^(#\s*include\s*)<[^>]+>/,lookbehind:!0},o.languages.c.string],comment:o.languages.c.comment,"macro-name":[{pattern:/(^#\s*define\s+)\w+\b(?!\()/i,lookbehind:!0},{pattern:/(^#\s*define\s+)\w+\b(?=\()/i,lookbehind:!0,alias:"function"}],directive:{pattern:/^(#\s*)[a-z]+/,lookbehind:!0,alias:"keyword"},"directive-hash":/^#/,punctuation:/##|\\(?=[\r\n])/,expression:{pattern:/\S[\s\S]*/,inside:o.languages.c}}},constant:/\b(?:__FILE__|__LINE__|__DATE__|__TIME__|__TIMESTAMP__|__func__|EOF|NULL|SEEK_CUR|SEEK_END|SEEK_SET|stdin|stdout|stderr)\b/}),delete o.languages.c.boolean,function(e){var t=/\b(?:alignas|alignof|asm|auto|bool|break|case|catch|char|char8_t|char16_t|char32_t|class|compl|concept|const|consteval|constexpr|constinit|const_cast|continue|co_await|co_return|co_yield|decltype|default|delete|do|double|dynamic_cast|else|enum|explicit|export|extern|float|for|friend|goto|if|inline|int|int8_t|int16_t|int32_t|int64_t|uint8_t|uint16_t|uint32_t|uint64_t|long|mutable|namespace|new|noexcept|nullptr|operator|private|protected|public|register|reinterpret_cast|requires|return|short|signed|sizeof|static|static_assert|static_cast|struct|switch|template|this|thread_local|throw|try|typedef|typeid|typename|union|unsigned|using|virtual|void|volatile|wchar_t|while)\b/;e.languages.cpp=e.languages.extend("c",{"class-name":[{pattern:RegExp(/(\b(?:class|concept|enum|struct|typename)\s+)(?!)\w+/.source.replace(//g,(function(){return t.source}))),lookbehind:!0},/\b[A-Z]\w*(?=\s*::\s*\w+\s*\()/,/\b[A-Z_]\w*(?=\s*::\s*~\w+\s*\()/i,/\w+(?=\s*<(?:[^<>]|<(?:[^<>]|<[^<>]*>)*>)*>\s*::\s*\w+\s*\()/],keyword:t,number:{pattern:/(?:\b0b[01']+|\b0x(?:[\da-f']+(?:\.[\da-f']*)?|\.[\da-f']+)(?:p[+-]?[\d']+)?|(?:\b[\d']+(?:\.[\d']*)?|\B\.[\d']+)(?:e[+-]?[\d']+)?)[ful]{0,4}/i,greedy:!0},operator:/>>=?|<<=?|->|([-+&|:])\1|[?:~]|<=>|[-+*/%&|^!=<>]=?|\b(?:and|and_eq|bitand|bitor|not|not_eq|or|or_eq|xor|xor_eq)\b/,boolean:/\b(?:true|false)\b/}),e.languages.insertBefore("cpp","string",{"raw-string":{pattern:/R"([^()\\ ]{0,16})\([\s\S]*?\)\1"/,alias:"string",greedy:!0}}),e.languages.insertBefore("cpp","class-name",{"base-clause":{pattern:/(\b(?:class|struct)\s+\w+\s*:\s*)[^;{}"'\s]+(?:\s+[^;{}"'\s]+)*(?=\s*[;{])/,lookbehind:!0,greedy:!0,inside:e.languages.extend("cpp",{})}}),e.languages.insertBefore("inside","operator",{"class-name":/\b[a-z_]\w*\b(?!\s*::)/i},e.languages.cpp["base-clause"])}(o),function(e){var t=/("|')(?:\\(?:\r\n|[\s\S])|(?!\1)[^\\\r\n])*\1/;e.languages.css={comment:/\/\*[\s\S]*?\*\//,atrule:{pattern:/@[\w-](?:[^;{\s]|\s+(?![\s{]))*(?:;|(?=\s*\{))/,inside:{rule:/^@[\w-]+/,"selector-function-argument":{pattern:/(\bselector\s*\(\s*(?![\s)]))(?:[^()\s]|\s+(?![\s)])|\((?:[^()]|\([^()]*\))*\))+(?=\s*\))/,lookbehind:!0,alias:"selector"},keyword:{pattern:/(^|[^\w-])(?:and|not|only|or)(?![\w-])/,lookbehind:!0}}},url:{pattern:RegExp("\\burl\\((?:"+t.source+"|"+/(?:[^\\\r\n()"']|\\[\s\S])*/.source+")\\)","i"),greedy:!0,inside:{function:/^url/i,punctuation:/^\(|\)$/,string:{pattern:RegExp("^"+t.source+"$"),alias:"url"}}},selector:RegExp("[^{}\\s](?:[^{};\"'\\s]|\\s+(?![\\s{])|"+t.source+")*(?=\\s*\\{)"),string:{pattern:t,greedy:!0},property:/(?!\s)[-_a-z\xA0-\uFFFF](?:(?!\s)[-\w\xA0-\uFFFF])*(?=\s*:)/i,important:/!important\b/i,function:/[-a-z0-9]+(?=\()/i,punctuation:/[(){};:,]/},e.languages.css.atrule.inside.rest=e.languages.css;var n=e.languages.markup;n&&(n.tag.addInlined("style","css"),e.languages.insertBefore("inside","attr-value",{"style-attr":{pattern:/(^|["'\s])style\s*=\s*(?:"[^"]*"|'[^']*')/i,lookbehind:!0,inside:{"attr-value":{pattern:/=\s*(?:"[^"]*"|'[^']*'|[^\s'">=]+)/,inside:{style:{pattern:/(["'])[\s\S]+(?=["']$)/,lookbehind:!0,alias:"language-css",inside:e.languages.css},punctuation:[{pattern:/^=/,alias:"attr-equals"},/"|'/]}},"attr-name":/^style/i}}},n.tag))}(o),function(e){var t,n=/("|')(?:\\(?:\r\n|[\s\S])|(?!\1)[^\\\r\n])*\1/;e.languages.css.selector={pattern:e.languages.css.selector,inside:t={"pseudo-element":/:(?:after|before|first-letter|first-line|selection)|::[-\w]+/,"pseudo-class":/:[-\w]+/,class:/\.[-\w]+/,id:/#[-\w]+/,attribute:{pattern:RegExp("\\[(?:[^[\\]\"']|"+n.source+")*\\]"),greedy:!0,inside:{punctuation:/^\[|\]$/,"case-sensitivity":{pattern:/(\s)[si]$/i,lookbehind:!0,alias:"keyword"},namespace:{pattern:/^(\s*)(?:(?!\s)[-*\w\xA0-\uFFFF])*\|(?!=)/,lookbehind:!0,inside:{punctuation:/\|$/}},"attr-name":{pattern:/^(\s*)(?:(?!\s)[-\w\xA0-\uFFFF])+/,lookbehind:!0},"attr-value":[n,{pattern:/(=\s*)(?:(?!\s)[-\w\xA0-\uFFFF])+(?=\s*$)/,lookbehind:!0}],operator:/[|~*^$]?=/}},"n-th":[{pattern:/(\(\s*)[+-]?\d*[\dn](?:\s*[+-]\s*\d+)?(?=\s*\))/,lookbehind:!0,inside:{number:/[\dn]+/,operator:/[+-]/}},{pattern:/(\(\s*)(?:even|odd)(?=\s*\))/i,lookbehind:!0}],combinator:/>|\+|~|\|\|/,punctuation:/[(),]/}},e.languages.css.atrule.inside["selector-function-argument"].inside=t,e.languages.insertBefore("css","property",{variable:{pattern:/(^|[^-\w\xA0-\uFFFF])--(?!\s)[-_a-z\xA0-\uFFFF](?:(?!\s)[-\w\xA0-\uFFFF])*/i,lookbehind:!0}});var r={pattern:/(\b\d+)(?:%|[a-z]+\b)/,lookbehind:!0},a={pattern:/(^|[^\w.-])-?(?:\d+(?:\.\d+)?|\.\d+)/,lookbehind:!0};e.languages.insertBefore("css","function",{operator:{pattern:/(\s)[+\-*\/](?=\s)/,lookbehind:!0},hexcode:{pattern:/\B#(?:[\da-f]{1,2}){3,4}\b/i,alias:"color"},color:[/\b(?:AliceBlue|AntiqueWhite|Aqua|Aquamarine|Azure|Beige|Bisque|Black|BlanchedAlmond|Blue|BlueViolet|Brown|BurlyWood|CadetBlue|Chartreuse|Chocolate|Coral|CornflowerBlue|Cornsilk|Crimson|Cyan|DarkBlue|DarkCyan|DarkGoldenRod|DarkGr[ae]y|DarkGreen|DarkKhaki|DarkMagenta|DarkOliveGreen|DarkOrange|DarkOrchid|DarkRed|DarkSalmon|DarkSeaGreen|DarkSlateBlue|DarkSlateGr[ae]y|DarkTurquoise|DarkViolet|DeepPink|DeepSkyBlue|DimGr[ae]y|DodgerBlue|FireBrick|FloralWhite|ForestGreen|Fuchsia|Gainsboro|GhostWhite|Gold|GoldenRod|Gr[ae]y|Green|GreenYellow|HoneyDew|HotPink|IndianRed|Indigo|Ivory|Khaki|Lavender|LavenderBlush|LawnGreen|LemonChiffon|LightBlue|LightCoral|LightCyan|LightGoldenRodYellow|LightGr[ae]y|LightGreen|LightPink|LightSalmon|LightSeaGreen|LightSkyBlue|LightSlateGr[ae]y|LightSteelBlue|LightYellow|Lime|LimeGreen|Linen|Magenta|Maroon|MediumAquaMarine|MediumBlue|MediumOrchid|MediumPurple|MediumSeaGreen|MediumSlateBlue|MediumSpringGreen|MediumTurquoise|MediumVioletRed|MidnightBlue|MintCream|MistyRose|Moccasin|NavajoWhite|Navy|OldLace|Olive|OliveDrab|Orange|OrangeRed|Orchid|PaleGoldenRod|PaleGreen|PaleTurquoise|PaleVioletRed|PapayaWhip|PeachPuff|Peru|Pink|Plum|PowderBlue|Purple|Red|RosyBrown|RoyalBlue|SaddleBrown|Salmon|SandyBrown|SeaGreen|SeaShell|Sienna|Silver|SkyBlue|SlateBlue|SlateGr[ae]y|Snow|SpringGreen|SteelBlue|Tan|Teal|Thistle|Tomato|Transparent|Turquoise|Violet|Wheat|White|WhiteSmoke|Yellow|YellowGreen)\b/i,{pattern:/\b(?:rgb|hsl)\(\s*\d{1,3}\s*,\s*\d{1,3}%?\s*,\s*\d{1,3}%?\s*\)\B|\b(?:rgb|hsl)a\(\s*\d{1,3}\s*,\s*\d{1,3}%?\s*,\s*\d{1,3}%?\s*,\s*(?:0|0?\.\d+|1)\s*\)\B/i,inside:{unit:r,number:a,function:/[\w-]+(?=\()/,punctuation:/[(),]/}}],entity:/\\[\da-f]{1,8}/i,unit:r,number:a})}(o),o.languages.javascript=o.languages.extend("clike",{"class-name":[o.languages.clike["class-name"],{pattern:/(^|[^$\w\xA0-\uFFFF])(?!\s)[_$A-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*(?=\.(?:prototype|constructor))/,lookbehind:!0}],keyword:[{pattern:/((?:^|})\s*)(?:catch|finally)\b/,lookbehind:!0},{pattern:/(^|[^.]|\.\.\.\s*)\b(?:as|async(?=\s*(?:function\b|\(|[$\w\xA0-\uFFFF]|$))|await|break|case|class|const|continue|debugger|default|delete|do|else|enum|export|extends|for|from|function|(?:get|set)(?=\s*[\[$\w\xA0-\uFFFF])|if|implements|import|in|instanceof|interface|let|new|null|of|package|private|protected|public|return|static|super|switch|this|throw|try|typeof|undefined|var|void|while|with|yield)\b/,lookbehind:!0}],function:/#?(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*(?=\s*(?:\.\s*(?:apply|bind|call)\s*)?\()/,number:/\b(?:(?:0[xX](?:[\dA-Fa-f](?:_[\dA-Fa-f])?)+|0[bB](?:[01](?:_[01])?)+|0[oO](?:[0-7](?:_[0-7])?)+)n?|(?:\d(?:_\d)?)+n|NaN|Infinity)\b|(?:\b(?:\d(?:_\d)?)+\.?(?:\d(?:_\d)?)*|\B\.(?:\d(?:_\d)?)+)(?:[Ee][+-]?(?:\d(?:_\d)?)+)?/,operator:/--|\+\+|\*\*=?|=>|&&=?|\|\|=?|[!=]==|<<=?|>>>?=?|[-+*/%&|^!=<>]=?|\.{3}|\?\?=?|\?\.?|[~:]/}),o.languages.javascript["class-name"][0].pattern=/(\b(?:class|interface|extends|implements|instanceof|new)\s+)[\w.\\]+/,o.languages.insertBefore("javascript","keyword",{regex:{pattern:/((?:^|[^$\w\xA0-\uFFFF."'\])\s]|\b(?:return|yield))\s*)\/(?:\[(?:[^\]\\\r\n]|\\.)*]|\\.|[^/\\\[\r\n])+\/[gimyus]{0,6}(?=(?:\s|\/\*(?:[^*]|\*(?!\/))*\*\/)*(?:$|[\r\n,.;:})\]]|\/\/))/,lookbehind:!0,greedy:!0,inside:{"regex-source":{pattern:/^(\/)[\s\S]+(?=\/[a-z]*$)/,lookbehind:!0,alias:"language-regex",inside:o.languages.regex},"regex-flags":/[a-z]+$/,"regex-delimiter":/^\/|\/$/}},"function-variable":{pattern:/#?(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*(?=\s*[=:]\s*(?:async\s*)?(?:\bfunction\b|(?:\((?:[^()]|\([^()]*\))*\)|(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*)\s*=>))/,alias:"function"},parameter:[{pattern:/(function(?:\s+(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*)?\s*\(\s*)(?!\s)(?:[^()\s]|\s+(?![\s)])|\([^()]*\))+(?=\s*\))/,lookbehind:!0,inside:o.languages.javascript},{pattern:/(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*(?=\s*=>)/i,inside:o.languages.javascript},{pattern:/(\(\s*)(?!\s)(?:[^()\s]|\s+(?![\s)])|\([^()]*\))+(?=\s*\)\s*=>)/,lookbehind:!0,inside:o.languages.javascript},{pattern:/((?:\b|\s|^)(?!(?:as|async|await|break|case|catch|class|const|continue|debugger|default|delete|do|else|enum|export|extends|finally|for|from|function|get|if|implements|import|in|instanceof|interface|let|new|null|of|package|private|protected|public|return|set|static|super|switch|this|throw|try|typeof|undefined|var|void|while|with|yield)(?![$\w\xA0-\uFFFF]))(?:(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*\s*)\(\s*|\]\s*\(\s*)(?!\s)(?:[^()\s]|\s+(?![\s)])|\([^()]*\))+(?=\s*\)\s*\{)/,lookbehind:!0,inside:o.languages.javascript}],constant:/\b[A-Z](?:[A-Z_]|\dx?)*\b/}),o.languages.insertBefore("javascript","string",{"template-string":{pattern:/`(?:\\[\s\S]|\${(?:[^{}]|{(?:[^{}]|{[^}]*})*})+}|(?!\${)[^\\`])*`/,greedy:!0,inside:{"template-punctuation":{pattern:/^`|`$/,alias:"string"},interpolation:{pattern:/((?:^|[^\\])(?:\\{2})*)\${(?:[^{}]|{(?:[^{}]|{[^}]*})*})+}/,lookbehind:!0,inside:{"interpolation-punctuation":{pattern:/^\${|}$/,alias:"punctuation"},rest:o.languages.javascript}},string:/[\s\S]+/}}}),o.languages.markup&&o.languages.markup.tag.addInlined("script","javascript"),o.languages.js=o.languages.javascript,function(e){var t=e.util.clone(e.languages.javascript);e.languages.jsx=e.languages.extend("markup",t),e.languages.jsx.tag.pattern=/<\/?(?:[\w.:-]+(?:\s+(?:[\w.:$-]+(?:=(?:"(?:\\[^]|[^\\"])*"|'(?:\\[^]|[^\\'])*'|[^\s{'">=]+|\{(?:\{(?:\{[^{}]*\}|[^{}])*\}|[^{}])+\}))?|\{\s*\.{3}\s*[a-z_$][\w$]*(?:\.[a-z_$][\w$]*)*\s*\}))*\s*\/?)?>/i,e.languages.jsx.tag.inside.tag.pattern=/^<\/?[^\s>\/]*/i,e.languages.jsx.tag.inside["attr-value"].pattern=/=(?!\{)(?:"(?:\\[^]|[^\\"])*"|'(?:\\[^]|[^\\'])*'|[^\s'">]+)/i,e.languages.jsx.tag.inside.tag.inside["class-name"]=/^[A-Z]\w*(?:\.[A-Z]\w*)*$/,e.languages.insertBefore("inside","attr-name",{spread:{pattern:/\{\s*\.{3}\s*[a-z_$][\w$]*(?:\.[a-z_$][\w$]*)*\s*\}/,inside:{punctuation:/\.{3}|[{}.]/,"attr-value":/\w+/}}},e.languages.jsx.tag),e.languages.insertBefore("inside","attr-value",{script:{pattern:/=(?:\{(?:\{(?:\{[^{}]*\}|[^{}])*\}|[^{}])+\})/i,inside:{"script-punctuation":{pattern:/^=(?={)/,alias:"punctuation"},rest:e.languages.jsx},alias:"language-javascript"}},e.languages.jsx.tag);var n=function e(t){return t?"string"==typeof t?t:"string"==typeof t.content?t.content:t.content.map(e).join(""):""};e.hooks.add("after-tokenize",(function(t){"jsx"!==t.language&&"tsx"!==t.language||function t(r){for(var a=[],i=0;i0&&a[a.length-1].tagName===n(o.content[0].content[1])&&a.pop():"/>"===o.content[o.content.length-1].content||a.push({tagName:n(o.content[0].content[1]),openedBraces:0}):a.length>0&&"punctuation"===o.type&&"{"===o.content?a[a.length-1].openedBraces++:a.length>0&&a[a.length-1].openedBraces>0&&"punctuation"===o.type&&"}"===o.content?a[a.length-1].openedBraces--:s=!0),(s||"string"==typeof o)&&a.length>0&&0===a[a.length-1].openedBraces){var c=n(o);i0&&("string"==typeof r[i-1]||"plain-text"===r[i-1].type)&&(c=n(r[i-1])+c,r.splice(i-1,1),i--),r[i]=new e.Token("plain-text",c,null,c)}o.content&&"string"!=typeof o.content&&t(o.content)}}(t.tokens)}))}(o),function(e){function t(e,t){return RegExp(e.replace(//g,(function(){return/(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*/.source})),t)}e.languages.insertBefore("javascript","function-variable",{"method-variable":{pattern:RegExp("(\\.\\s*)"+e.languages.javascript["function-variable"].pattern.source),lookbehind:!0,alias:["function-variable","method","function","property-access"]}}),e.languages.insertBefore("javascript","function",{method:{pattern:RegExp("(\\.\\s*)"+e.languages.javascript.function.source),lookbehind:!0,alias:["function","property-access"]}}),e.languages.insertBefore("javascript","constant",{"known-class-name":[{pattern:/\b(?:(?:(?:Uint|Int)(?:8|16|32)|Uint8Clamped|Float(?:32|64))?Array|ArrayBuffer|BigInt|Boolean|DataView|Date|Error|Function|Intl|JSON|Math|Number|Object|Promise|Proxy|Reflect|RegExp|String|Symbol|(?:Weak)?(?:Set|Map)|WebAssembly)\b/,alias:"class-name"},{pattern:/\b(?:[A-Z]\w*)Error\b/,alias:"class-name"}]}),e.languages.insertBefore("javascript","keyword",{imports:{pattern:t(/(\bimport\b\s*)(?:(?:\s*,\s*(?:\*\s*as\s+|\{[^{}]*\}))?|\*\s*as\s+|\{[^{}]*\})(?=\s*\bfrom\b)/.source),lookbehind:!0,inside:e.languages.javascript},exports:{pattern:t(/(\bexport\b\s*)(?:\*(?:\s*as\s+)?(?=\s*\bfrom\b)|\{[^{}]*\})/.source),lookbehind:!0,inside:e.languages.javascript}}),e.languages.javascript.keyword.unshift({pattern:/\b(?:as|default|export|from|import)\b/,alias:"module"},{pattern:/\b(?:await|break|catch|continue|do|else|for|finally|if|return|switch|throw|try|while|yield)\b/,alias:"control-flow"},{pattern:/\bnull\b/,alias:["null","nil"]},{pattern:/\bundefined\b/,alias:"nil"}),e.languages.insertBefore("javascript","operator",{spread:{pattern:/\.{3}/,alias:"operator"},arrow:{pattern:/=>/,alias:"operator"}}),e.languages.insertBefore("javascript","punctuation",{"property-access":{pattern:t(/(\.\s*)#?/.source),lookbehind:!0},"maybe-class-name":{pattern:/(^|[^$\w\xA0-\uFFFF])[A-Z][$\w\xA0-\uFFFF]+/,lookbehind:!0},dom:{pattern:/\b(?:document|location|navigator|performance|(?:local|session)Storage|window)\b/,alias:"variable"},console:{pattern:/\bconsole(?=\s*\.)/,alias:"class-name"}});for(var n=["function","function-variable","method","method-variable","property-access"],r=0;r",unchanged:" ",diff:"!"};Object.keys(t).forEach((function(n){var r=t[n],a=[];/^\w+$/.test(n)||a.push(/\w+/.exec(n)[0]),"diff"===n&&a.push("bold"),e.languages.diff[n]={pattern:RegExp("^(?:["+r+"].*(?:\r\n?|\n|(?![\\s\\S])))+","m"),alias:a,inside:{line:{pattern:/(.)(?=[\s\S]).*(?:\r\n?|\n)?/,lookbehind:!0},prefix:{pattern:/[\s\S]/,alias:/\w+/.exec(n)[0]}}}})),Object.defineProperty(e.languages.diff,"PREFIXES",{value:t})}(o),o.languages.git={comment:/^#.*/m,deleted:/^[-–].*/m,inserted:/^\+.*/m,string:/("|')(?:\\.|(?!\1)[^\\\r\n])*\1/m,command:{pattern:/^.*\$ git .*$/m,inside:{parameter:/\s--?\w+/m}},coord:/^@@.*@@$/m,"commit-sha1":/^commit \w{40}$/m},o.languages.go=o.languages.extend("clike",{string:{pattern:/(["'`])(?:\\[\s\S]|(?!\1)[^\\])*\1/,greedy:!0},keyword:/\b(?:break|case|chan|const|continue|default|defer|else|fallthrough|for|func|go(?:to)?|if|import|interface|map|package|range|return|select|struct|switch|type|var)\b/,boolean:/\b(?:_|iota|nil|true|false)\b/,number:/(?:\b0x[a-f\d]+|(?:\b\d+(?:\.\d*)?|\B\.\d+)(?:e[-+]?\d+)?)i?/i,operator:/[*\/%^!=]=?|\+[=+]?|-[=-]?|\|[=|]?|&(?:=|&|\^=?)?|>(?:>=?|=)?|<(?:<=?|=|-)?|:=|\.\.\./,builtin:/\b(?:bool|byte|complex(?:64|128)|error|float(?:32|64)|rune|string|u?int(?:8|16|32|64)?|uintptr|append|cap|close|complex|copy|delete|imag|len|make|new|panic|print(?:ln)?|real|recover)\b/}),delete o.languages.go["class-name"],o.languages.graphql={comment:/#.*/,description:{pattern:/(?:"""(?:[^"]|(?!""")")*"""|"(?:\\.|[^\\"\r\n])*")(?=\s*[a-z_])/i,greedy:!0,alias:"string",inside:{"language-markdown":{pattern:/(^"(?:"")?)(?!\1)[\s\S]+(?=\1$)/,lookbehind:!0,inside:o.languages.markdown}}},string:{pattern:/"""(?:[^"]|(?!""")")*"""|"(?:\\.|[^\\"\r\n])*"/,greedy:!0},number:/(?:\B-|\b)\d+(?:\.\d+)?(?:e[+-]?\d+)?\b/i,boolean:/\b(?:true|false)\b/,variable:/\$[a-z_]\w*/i,directive:{pattern:/@[a-z_]\w*/i,alias:"function"},"attr-name":{pattern:/[a-z_]\w*(?=\s*(?:\((?:[^()"]|"(?:\\.|[^\\"\r\n])*")*\))?:)/i,greedy:!0},"class-name":{pattern:/(\b(?:enum|implements|interface|on|scalar|type|union)\s+|&\s*)[a-zA-Z_]\w*/,lookbehind:!0},fragment:{pattern:/(\bfragment\s+|\.{3}\s*(?!on\b))[a-zA-Z_]\w*/,lookbehind:!0,alias:"function"},keyword:/\b(?:directive|enum|extend|fragment|implements|input|interface|mutation|on|query|repeatable|scalar|schema|subscription|type|union)\b/,operator:/[!=|&]|\.{3}/,punctuation:/[!(){}\[\]:=,]/,constant:/\b(?!ID\b)[A-Z][A-Z_\d]*\b/},function(e){function t(e,t){return"___"+e.toUpperCase()+t+"___"}Object.defineProperties(e.languages["markup-templating"]={},{buildPlaceholders:{value:function(n,r,a,i){if(n.language===r){var o=n.tokenStack=[];n.code=n.code.replace(a,(function(e){if("function"==typeof i&&!i(e))return e;for(var a,s=o.length;-1!==n.code.indexOf(a=t(r,s));)++s;return o[s]=e,a})),n.grammar=e.languages.markup}}},tokenizePlaceholders:{value:function(n,r){if(n.language===r&&n.tokenStack){n.grammar=e.languages[r];var a=0,i=Object.keys(n.tokenStack);!function o(s){for(var c=0;c=i.length);c++){var l=s[c];if("string"==typeof l||l.content&&"string"==typeof l.content){var u=i[a],d=n.tokenStack[u],p="string"==typeof l?l:l.content,f=t(r,u),m=p.indexOf(f);if(m>-1){++a;var g=p.substring(0,m),h=new e.Token(r,e.tokenize(d,n.grammar),"language-"+r,d),y=p.substring(m+f.length),b=[];g&&b.push.apply(b,o([g])),b.push(h),y&&b.push.apply(b,o([y])),"string"==typeof l?s.splice.apply(s,[c,1].concat(b)):l.content=b}}else l.content&&o(l.content)}return s}(n.tokens)}}}})}(o),function(e){e.languages.handlebars={comment:/\{\{![\s\S]*?\}\}/,delimiter:{pattern:/^\{\{\{?|\}\}\}?$/i,alias:"punctuation"},string:/(["'])(?:\\.|(?!\1)[^\\\r\n])*\1/,number:/\b0x[\dA-Fa-f]+\b|(?:\b\d+(?:\.\d*)?|\B\.\d+)(?:[Ee][+-]?\d+)?/,boolean:/\b(?:true|false)\b/,block:{pattern:/^(\s*(?:~\s*)?)[#\/]\S+?(?=\s*(?:~\s*)?$|\s)/i,lookbehind:!0,alias:"keyword"},brackets:{pattern:/\[[^\]]+\]/,inside:{punctuation:/\[|\]/,variable:/[\s\S]+/}},punctuation:/[!"#%&':()*+,.\/;<=>@\[\\\]^`{|}~]/,variable:/[^!"#%&'()*+,\/;<=>@\[\\\]^`{|}~\s]+/},e.hooks.add("before-tokenize",(function(t){e.languages["markup-templating"].buildPlaceholders(t,"handlebars",/\{\{\{[\s\S]+?\}\}\}|\{\{[\s\S]+?\}\}/g)})),e.hooks.add("after-tokenize",(function(t){e.languages["markup-templating"].tokenizePlaceholders(t,"handlebars")}))}(o),o.languages.json={property:{pattern:/"(?:\\.|[^\\"\r\n])*"(?=\s*:)/,greedy:!0},string:{pattern:/"(?:\\.|[^\\"\r\n])*"(?!\s*:)/,greedy:!0},comment:{pattern:/\/\/.*|\/\*[\s\S]*?(?:\*\/|$)/,greedy:!0},number:/-?\b\d+(?:\.\d+)?(?:e[+-]?\d+)?\b/i,punctuation:/[{}[\],]/,operator:/:/,boolean:/\b(?:true|false)\b/,null:{pattern:/\bnull\b/,alias:"keyword"}},o.languages.webmanifest=o.languages.json,o.languages.less=o.languages.extend("css",{comment:[/\/\*[\s\S]*?\*\//,{pattern:/(^|[^\\])\/\/.*/,lookbehind:!0}],atrule:{pattern:/@[\w-](?:\((?:[^(){}]|\([^(){}]*\))*\)|[^(){};\s]|\s+(?!\s))*?(?=\s*\{)/,inside:{punctuation:/[:()]/}},selector:{pattern:/(?:@\{[\w-]+\}|[^{};\s@])(?:@\{[\w-]+\}|\((?:[^(){}]|\([^(){}]*\))*\)|[^(){};@\s]|\s+(?!\s))*?(?=\s*\{)/,inside:{variable:/@+[\w-]+/}},property:/(?:@\{[\w-]+\}|[\w-])+(?:\+_?)?(?=\s*:)/i,operator:/[+\-*\/]/}),o.languages.insertBefore("less","property",{variable:[{pattern:/@[\w-]+\s*:/,inside:{punctuation:/:/}},/@@?[\w-]+/],"mixin-usage":{pattern:/([{;]\s*)[.#](?!\d)[\w-].*?(?=[(;])/,lookbehind:!0,alias:"function"}}),o.languages.makefile={comment:{pattern:/(^|[^\\])#(?:\\(?:\r\n|[\s\S])|[^\\\r\n])*/,lookbehind:!0},string:{pattern:/(["'])(?:\\(?:\r\n|[\s\S])|(?!\1)[^\\\r\n])*\1/,greedy:!0},builtin:/\.[A-Z][^:#=\s]+(?=\s*:(?!=))/,symbol:{pattern:/^(?:[^:=\s]|[ \t]+(?![\s:]))+(?=\s*:(?!=))/m,inside:{variable:/\$+(?:(?!\$)[^(){}:#=\s]+|(?=[({]))/}},variable:/\$+(?:(?!\$)[^(){}:#=\s]+|\([@*%<^+?][DF]\)|(?=[({]))/,keyword:[/-include\b|\b(?:define|else|endef|endif|export|ifn?def|ifn?eq|include|override|private|sinclude|undefine|unexport|vpath)\b/,{pattern:/(\()(?:addsuffix|abspath|and|basename|call|dir|error|eval|file|filter(?:-out)?|findstring|firstword|flavor|foreach|guile|if|info|join|lastword|load|notdir|or|origin|patsubst|realpath|shell|sort|strip|subst|suffix|value|warning|wildcard|word(?:s|list)?)(?=[ \t])/,lookbehind:!0}],operator:/(?:::|[?:+!])?=|[|@]/,punctuation:/[:;(){}]/},function(e){var t=/(?:\\.|[^\\\n\r]|(?:\n|\r\n?)(?!\n|\r\n?))/.source;function n(e){return e=e.replace(//g,(function(){return t})),RegExp(/((?:^|[^\\])(?:\\{2})*)/.source+"(?:"+e+")")}var r=/(?:\\.|``(?:[^`\r\n]|`(?!`))+``|`[^`\r\n]+`|[^\\|\r\n`])+/.source,a=/\|?__(?:\|__)+\|?(?:(?:\n|\r\n?)|(?![\s\S]))/.source.replace(/__/g,(function(){return r})),i=/\|?[ \t]*:?-{3,}:?[ \t]*(?:\|[ \t]*:?-{3,}:?[ \t]*)+\|?(?:\n|\r\n?)/.source;e.languages.markdown=e.languages.extend("markup",{}),e.languages.insertBefore("markdown","prolog",{"front-matter-block":{pattern:/(^(?:\s*[\r\n])?)---(?!.)[\s\S]*?[\r\n]---(?!.)/,lookbehind:!0,greedy:!0,inside:{punctuation:/^---|---$/,"font-matter":{pattern:/\S+(?:\s+\S+)*/,alias:["yaml","language-yaml"],inside:e.languages.yaml}}},blockquote:{pattern:/^>(?:[\t ]*>)*/m,alias:"punctuation"},table:{pattern:RegExp("^"+a+i+"(?:"+a+")*","m"),inside:{"table-data-rows":{pattern:RegExp("^("+a+i+")(?:"+a+")*$"),lookbehind:!0,inside:{"table-data":{pattern:RegExp(r),inside:e.languages.markdown},punctuation:/\|/}},"table-line":{pattern:RegExp("^("+a+")"+i+"$"),lookbehind:!0,inside:{punctuation:/\||:?-{3,}:?/}},"table-header-row":{pattern:RegExp("^"+a+"$"),inside:{"table-header":{pattern:RegExp(r),alias:"important",inside:e.languages.markdown},punctuation:/\|/}}}},code:[{pattern:/((?:^|\n)[ \t]*\n|(?:^|\r\n?)[ \t]*\r\n?)(?: {4}|\t).+(?:(?:\n|\r\n?)(?: {4}|\t).+)*/,lookbehind:!0,alias:"keyword"},{pattern:/``.+?``|`[^`\r\n]+`/,alias:"keyword"},{pattern:/^```[\s\S]*?^```$/m,greedy:!0,inside:{"code-block":{pattern:/^(```.*(?:\n|\r\n?))[\s\S]+?(?=(?:\n|\r\n?)^```$)/m,lookbehind:!0},"code-language":{pattern:/^(```).+/,lookbehind:!0},punctuation:/```/}}],title:[{pattern:/\S.*(?:\n|\r\n?)(?:==+|--+)(?=[ \t]*$)/m,alias:"important",inside:{punctuation:/==+$|--+$/}},{pattern:/(^\s*)#.+/m,lookbehind:!0,alias:"important",inside:{punctuation:/^#+|#+$/}}],hr:{pattern:/(^\s*)([*-])(?:[\t ]*\2){2,}(?=\s*$)/m,lookbehind:!0,alias:"punctuation"},list:{pattern:/(^\s*)(?:[*+-]|\d+\.)(?=[\t ].)/m,lookbehind:!0,alias:"punctuation"},"url-reference":{pattern:/!?\[[^\]]+\]:[\t ]+(?:\S+|<(?:\\.|[^>\\])+>)(?:[\t ]+(?:"(?:\\.|[^"\\])*"|'(?:\\.|[^'\\])*'|\((?:\\.|[^)\\])*\)))?/,inside:{variable:{pattern:/^(!?\[)[^\]]+/,lookbehind:!0},string:/(?:"(?:\\.|[^"\\])*"|'(?:\\.|[^'\\])*'|\((?:\\.|[^)\\])*\))$/,punctuation:/^[\[\]!:]|[<>]/},alias:"url"},bold:{pattern:n(/\b__(?:(?!_)|_(?:(?!_))+_)+__\b|\*\*(?:(?!\*)|\*(?:(?!\*))+\*)+\*\*/.source),lookbehind:!0,greedy:!0,inside:{content:{pattern:/(^..)[\s\S]+(?=..$)/,lookbehind:!0,inside:{}},punctuation:/\*\*|__/}},italic:{pattern:n(/\b_(?:(?!_)|__(?:(?!_))+__)+_\b|\*(?:(?!\*)|\*\*(?:(?!\*))+\*\*)+\*/.source),lookbehind:!0,greedy:!0,inside:{content:{pattern:/(^.)[\s\S]+(?=.$)/,lookbehind:!0,inside:{}},punctuation:/[*_]/}},strike:{pattern:n(/(~~?)(?:(?!~))+?\2/.source),lookbehind:!0,greedy:!0,inside:{content:{pattern:/(^~~?)[\s\S]+(?=\1$)/,lookbehind:!0,inside:{}},punctuation:/~~?/}},url:{pattern:n(/!?\[(?:(?!\]))+\](?:\([^\s)]+(?:[\t ]+"(?:\\.|[^"\\])*")?\)|[ \t]?\[(?:(?!\]))+\])/.source),lookbehind:!0,greedy:!0,inside:{operator:/^!/,content:{pattern:/(^\[)[^\]]+(?=\])/,lookbehind:!0,inside:{}},variable:{pattern:/(^\][ \t]?\[)[^\]]+(?=\]$)/,lookbehind:!0},url:{pattern:/(^\]\()[^\s)]+/,lookbehind:!0},string:{pattern:/(^[ \t]+)"(?:\\.|[^"\\])*"(?=\)$)/,lookbehind:!0}}}}),["url","bold","italic","strike"].forEach((function(t){["url","bold","italic","strike"].forEach((function(n){t!==n&&(e.languages.markdown[t].inside.content.inside[n]=e.languages.markdown[n])}))})),e.hooks.add("after-tokenize",(function(e){"markdown"!==e.language&&"md"!==e.language||function e(t){if(t&&"string"!=typeof t)for(var n=0,r=t.length;n]?|\+\+?|!=?|<>?=?|==?|&&?|\|\|?|[~^%?*\/@]/}),delete o.languages.objectivec["class-name"],o.languages.objc=o.languages.objectivec,o.languages.ocaml={comment:/\(\*[\s\S]*?\*\)/,string:[{pattern:/"(?:\\.|[^\\\r\n"])*"/,greedy:!0},{pattern:/(['`])(?:\\(?:\d+|x[\da-f]+|.)|(?!\1)[^\\\r\n])\1/i,greedy:!0}],number:/\b(?:0x[\da-f][\da-f_]+|(?:0[bo])?\d[\d_]*(?:\.[\d_]*)?(?:e[+-]?[\d_]+)?)/i,directive:{pattern:/\B#\w+/,alias:"important"},label:{pattern:/\B~\w+/,alias:"function"},"type-variable":{pattern:/\B'\w+/,alias:"function"},variant:{pattern:/`\w+/,alias:"variable"},module:{pattern:/\b[A-Z]\w+/,alias:"variable"},keyword:/\b(?:as|assert|begin|class|constraint|do|done|downto|else|end|exception|external|for|fun|function|functor|if|in|include|inherit|initializer|lazy|let|match|method|module|mutable|new|nonrec|object|of|open|private|rec|sig|struct|then|to|try|type|val|value|virtual|when|where|while|with)\b/,boolean:/\b(?:false|true)\b/,operator:/:=|[=<>@^|&+\-*\/$%!?~][!$%&*+\-.\/:<=>?@^|~]*|\b(?:and|asr|land|lor|lsl|lsr|lxor|mod|or)\b/,punctuation:/[(){}\[\]|.,:;]|\b_\b/},o.languages.python={comment:{pattern:/(^|[^\\])#.*/,lookbehind:!0},"string-interpolation":{pattern:/(?:f|rf|fr)(?:("""|''')[\s\S]*?\1|("|')(?:\\.|(?!\2)[^\\\r\n])*\2)/i,greedy:!0,inside:{interpolation:{pattern:/((?:^|[^{])(?:{{)*){(?!{)(?:[^{}]|{(?!{)(?:[^{}]|{(?!{)(?:[^{}])+})+})+}/,lookbehind:!0,inside:{"format-spec":{pattern:/(:)[^:(){}]+(?=}$)/,lookbehind:!0},"conversion-option":{pattern:/![sra](?=[:}]$)/,alias:"punctuation"},rest:null}},string:/[\s\S]+/}},"triple-quoted-string":{pattern:/(?:[rub]|rb|br)?("""|''')[\s\S]*?\1/i,greedy:!0,alias:"string"},string:{pattern:/(?:[rub]|rb|br)?("|')(?:\\.|(?!\1)[^\\\r\n])*\1/i,greedy:!0},function:{pattern:/((?:^|\s)def[ \t]+)[a-zA-Z_]\w*(?=\s*\()/g,lookbehind:!0},"class-name":{pattern:/(\bclass\s+)\w+/i,lookbehind:!0},decorator:{pattern:/(^\s*)@\w+(?:\.\w+)*/im,lookbehind:!0,alias:["annotation","punctuation"],inside:{punctuation:/\./}},keyword:/\b(?:and|as|assert|async|await|break|class|continue|def|del|elif|else|except|exec|finally|for|from|global|if|import|in|is|lambda|nonlocal|not|or|pass|print|raise|return|try|while|with|yield)\b/,builtin:/\b(?:__import__|abs|all|any|apply|ascii|basestring|bin|bool|buffer|bytearray|bytes|callable|chr|classmethod|cmp|coerce|compile|complex|delattr|dict|dir|divmod|enumerate|eval|execfile|file|filter|float|format|frozenset|getattr|globals|hasattr|hash|help|hex|id|input|int|intern|isinstance|issubclass|iter|len|list|locals|long|map|max|memoryview|min|next|object|oct|open|ord|pow|property|range|raw_input|reduce|reload|repr|reversed|round|set|setattr|slice|sorted|staticmethod|str|sum|super|tuple|type|unichr|unicode|vars|xrange|zip)\b/,boolean:/\b(?:True|False|None)\b/,number:/(?:\b(?=\d)|\B(?=\.))(?:0[bo])?(?:(?:\d|0x[\da-f])[\da-f]*(?:\.\d*)?|\.\d+)(?:e[+-]?\d+)?j?\b/i,operator:/[-+%=]=?|!=|\*\*?=?|\/\/?=?|<[<=>]?|>[=>]?|[&|^~]/,punctuation:/[{}[\];(),.:]/},o.languages.python["string-interpolation"].inside.interpolation.inside.rest=o.languages.python,o.languages.py=o.languages.python,o.languages.reason=o.languages.extend("clike",{string:{pattern:/"(?:\\(?:\r\n|[\s\S])|[^\\\r\n"])*"/,greedy:!0},"class-name":/\b[A-Z]\w*/,keyword:/\b(?:and|as|assert|begin|class|constraint|do|done|downto|else|end|exception|external|for|fun|function|functor|if|in|include|inherit|initializer|lazy|let|method|module|mutable|new|nonrec|object|of|open|or|private|rec|sig|struct|switch|then|to|try|type|val|virtual|when|while|with)\b/,operator:/\.{3}|:[:=]|\|>|->|=(?:==?|>)?|<=?|>=?|[|^?'#!~`]|[+\-*\/]\.?|\b(?:mod|land|lor|lxor|lsl|lsr|asr)\b/}),o.languages.insertBefore("reason","class-name",{character:{pattern:/'(?:\\x[\da-f]{2}|\\o[0-3][0-7][0-7]|\\\d{3}|\\.|[^'\\\r\n])'/,alias:"string"},constructor:{pattern:/\b[A-Z]\w*\b(?!\s*\.)/,alias:"variable"},label:{pattern:/\b[a-z]\w*(?=::)/,alias:"symbol"}}),delete o.languages.reason.function,function(e){e.languages.sass=e.languages.extend("css",{comment:{pattern:/^([ \t]*)\/[\/*].*(?:(?:\r?\n|\r)\1[ \t].+)*/m,lookbehind:!0}}),e.languages.insertBefore("sass","atrule",{"atrule-line":{pattern:/^(?:[ \t]*)[@+=].+/m,inside:{atrule:/(?:@[\w-]+|[+=])/m}}}),delete e.languages.sass.atrule;var t=/\$[-\w]+|#\{\$[-\w]+\}/,n=[/[+*\/%]|[=!]=|<=?|>=?|\b(?:and|or|not)\b/,{pattern:/(\s+)-(?=\s)/,lookbehind:!0}];e.languages.insertBefore("sass","property",{"variable-line":{pattern:/^[ \t]*\$.+/m,inside:{punctuation:/:/,variable:t,operator:n}},"property-line":{pattern:/^[ \t]*(?:[^:\s]+ *:.*|:[^:\s].*)/m,inside:{property:[/[^:\s]+(?=\s*:)/,{pattern:/(:)[^:\s]+/,lookbehind:!0}],punctuation:/:/,variable:t,operator:n,important:e.languages.sass.important}}}),delete e.languages.sass.property,delete e.languages.sass.important,e.languages.insertBefore("sass","punctuation",{selector:{pattern:/([ \t]*)\S(?:,[^,\r\n]+|[^,\r\n]*)(?:,[^,\r\n]+)*(?:,(?:\r?\n|\r)\1[ \t]+\S(?:,[^,\r\n]+|[^,\r\n]*)(?:,[^,\r\n]+)*)*/,lookbehind:!0}})}(o),o.languages.scss=o.languages.extend("css",{comment:{pattern:/(^|[^\\])(?:\/\*[\s\S]*?\*\/|\/\/.*)/,lookbehind:!0},atrule:{pattern:/@[\w-](?:\([^()]+\)|[^()\s]|\s+(?!\s))*?(?=\s+[{;])/,inside:{rule:/@[\w-]+/}},url:/(?:[-a-z]+-)?url(?=\()/i,selector:{pattern:/(?=\S)[^@;{}()]?(?:[^@;{}()\s]|\s+(?!\s)|#\{\$[-\w]+\})+(?=\s*\{(?:\}|\s|[^}][^:{}]*[:{][^}]+))/m,inside:{parent:{pattern:/&/,alias:"important"},placeholder:/%[-\w]+/,variable:/\$[-\w]+|#\{\$[-\w]+\}/}},property:{pattern:/(?:[-\w]|\$[-\w]|#\{\$[-\w]+\})+(?=\s*:)/,inside:{variable:/\$[-\w]+|#\{\$[-\w]+\}/}}}),o.languages.insertBefore("scss","atrule",{keyword:[/@(?:if|else(?: if)?|forward|for|each|while|import|use|extend|debug|warn|mixin|include|function|return|content)\b/i,{pattern:/( +)(?:from|through)(?= )/,lookbehind:!0}]}),o.languages.insertBefore("scss","important",{variable:/\$[-\w]+|#\{\$[-\w]+\}/}),o.languages.insertBefore("scss","function",{"module-modifier":{pattern:/\b(?:as|with|show|hide)\b/i,alias:"keyword"},placeholder:{pattern:/%[-\w]+/,alias:"selector"},statement:{pattern:/\B!(?:default|optional)\b/i,alias:"keyword"},boolean:/\b(?:true|false)\b/,null:{pattern:/\bnull\b/,alias:"keyword"},operator:{pattern:/(\s)(?:[-+*\/%]|[=!]=|<=?|>=?|and|or|not)(?=\s)/,lookbehind:!0}}),o.languages.scss.atrule.inside.rest=o.languages.scss,o.languages.sql={comment:{pattern:/(^|[^\\])(?:\/\*[\s\S]*?\*\/|(?:--|\/\/|#).*)/,lookbehind:!0},variable:[{pattern:/@(["'`])(?:\\[\s\S]|(?!\1)[^\\])+\1/,greedy:!0},/@[\w.$]+/],string:{pattern:/(^|[^@\\])("|')(?:\\[\s\S]|(?!\2)[^\\]|\2\2)*\2/,greedy:!0,lookbehind:!0},function:/\b(?:AVG|COUNT|FIRST|FORMAT|LAST|LCASE|LEN|MAX|MID|MIN|MOD|NOW|ROUND|SUM|UCASE)(?=\s*\()/i,keyword:/\b(?:ACTION|ADD|AFTER|ALGORITHM|ALL|ALTER|ANALYZE|ANY|APPLY|AS|ASC|AUTHORIZATION|AUTO_INCREMENT|BACKUP|BDB|BEGIN|BERKELEYDB|BIGINT|BINARY|BIT|BLOB|BOOL|BOOLEAN|BREAK|BROWSE|BTREE|BULK|BY|CALL|CASCADED?|CASE|CHAIN|CHAR(?:ACTER|SET)?|CHECK(?:POINT)?|CLOSE|CLUSTERED|COALESCE|COLLATE|COLUMNS?|COMMENT|COMMIT(?:TED)?|COMPUTE|CONNECT|CONSISTENT|CONSTRAINT|CONTAINS(?:TABLE)?|CONTINUE|CONVERT|CREATE|CROSS|CURRENT(?:_DATE|_TIME|_TIMESTAMP|_USER)?|CURSOR|CYCLE|DATA(?:BASES?)?|DATE(?:TIME)?|DAY|DBCC|DEALLOCATE|DEC|DECIMAL|DECLARE|DEFAULT|DEFINER|DELAYED|DELETE|DELIMITERS?|DENY|DESC|DESCRIBE|DETERMINISTIC|DISABLE|DISCARD|DISK|DISTINCT|DISTINCTROW|DISTRIBUTED|DO|DOUBLE|DROP|DUMMY|DUMP(?:FILE)?|DUPLICATE|ELSE(?:IF)?|ENABLE|ENCLOSED|END|ENGINE|ENUM|ERRLVL|ERRORS|ESCAPED?|EXCEPT|EXEC(?:UTE)?|EXISTS|EXIT|EXPLAIN|EXTENDED|FETCH|FIELDS|FILE|FILLFACTOR|FIRST|FIXED|FLOAT|FOLLOWING|FOR(?: EACH ROW)?|FORCE|FOREIGN|FREETEXT(?:TABLE)?|FROM|FULL|FUNCTION|GEOMETRY(?:COLLECTION)?|GLOBAL|GOTO|GRANT|GROUP|HANDLER|HASH|HAVING|HOLDLOCK|HOUR|IDENTITY(?:_INSERT|COL)?|IF|IGNORE|IMPORT|INDEX|INFILE|INNER|INNODB|INOUT|INSERT|INT|INTEGER|INTERSECT|INTERVAL|INTO|INVOKER|ISOLATION|ITERATE|JOIN|KEYS?|KILL|LANGUAGE|LAST|LEAVE|LEFT|LEVEL|LIMIT|LINENO|LINES|LINESTRING|LOAD|LOCAL|LOCK|LONG(?:BLOB|TEXT)|LOOP|MATCH(?:ED)?|MEDIUM(?:BLOB|INT|TEXT)|MERGE|MIDDLEINT|MINUTE|MODE|MODIFIES|MODIFY|MONTH|MULTI(?:LINESTRING|POINT|POLYGON)|NATIONAL|NATURAL|NCHAR|NEXT|NO|NONCLUSTERED|NULLIF|NUMERIC|OFF?|OFFSETS?|ON|OPEN(?:DATASOURCE|QUERY|ROWSET)?|OPTIMIZE|OPTION(?:ALLY)?|ORDER|OUT(?:ER|FILE)?|OVER|PARTIAL|PARTITION|PERCENT|PIVOT|PLAN|POINT|POLYGON|PRECEDING|PRECISION|PREPARE|PREV|PRIMARY|PRINT|PRIVILEGES|PROC(?:EDURE)?|PUBLIC|PURGE|QUICK|RAISERROR|READS?|REAL|RECONFIGURE|REFERENCES|RELEASE|RENAME|REPEAT(?:ABLE)?|REPLACE|REPLICATION|REQUIRE|RESIGNAL|RESTORE|RESTRICT|RETURN(?:S|ING)?|REVOKE|RIGHT|ROLLBACK|ROUTINE|ROW(?:COUNT|GUIDCOL|S)?|RTREE|RULE|SAVE(?:POINT)?|SCHEMA|SECOND|SELECT|SERIAL(?:IZABLE)?|SESSION(?:_USER)?|SET(?:USER)?|SHARE|SHOW|SHUTDOWN|SIMPLE|SMALLINT|SNAPSHOT|SOME|SONAME|SQL|START(?:ING)?|STATISTICS|STATUS|STRIPED|SYSTEM_USER|TABLES?|TABLESPACE|TEMP(?:ORARY|TABLE)?|TERMINATED|TEXT(?:SIZE)?|THEN|TIME(?:STAMP)?|TINY(?:BLOB|INT|TEXT)|TOP?|TRAN(?:SACTIONS?)?|TRIGGER|TRUNCATE|TSEQUAL|TYPES?|UNBOUNDED|UNCOMMITTED|UNDEFINED|UNION|UNIQUE|UNLOCK|UNPIVOT|UNSIGNED|UPDATE(?:TEXT)?|USAGE|USE|USER|USING|VALUES?|VAR(?:BINARY|CHAR|CHARACTER|YING)|VIEW|WAITFOR|WARNINGS|WHEN|WHERE|WHILE|WITH(?: ROLLUP|IN)?|WORK|WRITE(?:TEXT)?|YEAR)\b/i,boolean:/\b(?:TRUE|FALSE|NULL)\b/i,number:/\b0x[\da-f]+\b|\b\d+(?:\.\d*)?|\B\.\d+\b/i,operator:/[-+*\/=%^~]|&&?|\|\|?|!=?|<(?:=>?|<|>)?|>[>=]?|\b(?:AND|BETWEEN|IN|LIKE|NOT|OR|IS|DIV|REGEXP|RLIKE|SOUNDS LIKE|XOR)\b/i,punctuation:/[;[\]()`,.]/},function(e){var t={pattern:/(\b\d+)(?:%|[a-z]+)/,lookbehind:!0},n={pattern:/(^|[^\w.-])-?(?:\d+(?:\.\d+)?|\.\d+)/,lookbehind:!0},r={comment:{pattern:/(^|[^\\])(?:\/\*[\s\S]*?\*\/|\/\/.*)/,lookbehind:!0},url:{pattern:/url\((["']?).*?\1\)/i,greedy:!0},string:{pattern:/("|')(?:(?!\1)[^\\\r\n]|\\(?:\r\n|[\s\S]))*\1/,greedy:!0},interpolation:null,func:null,important:/\B!(?:important|optional)\b/i,keyword:{pattern:/(^|\s+)(?:(?:if|else|for|return|unless)(?=\s+|$)|@[\w-]+)/,lookbehind:!0},hexcode:/#[\da-f]{3,6}/i,color:[/\b(?:AliceBlue|AntiqueWhite|Aqua|Aquamarine|Azure|Beige|Bisque|Black|BlanchedAlmond|Blue|BlueViolet|Brown|BurlyWood|CadetBlue|Chartreuse|Chocolate|Coral|CornflowerBlue|Cornsilk|Crimson|Cyan|DarkBlue|DarkCyan|DarkGoldenRod|DarkGr[ae]y|DarkGreen|DarkKhaki|DarkMagenta|DarkOliveGreen|DarkOrange|DarkOrchid|DarkRed|DarkSalmon|DarkSeaGreen|DarkSlateBlue|DarkSlateGr[ae]y|DarkTurquoise|DarkViolet|DeepPink|DeepSkyBlue|DimGr[ae]y|DodgerBlue|FireBrick|FloralWhite|ForestGreen|Fuchsia|Gainsboro|GhostWhite|Gold|GoldenRod|Gr[ae]y|Green|GreenYellow|HoneyDew|HotPink|IndianRed|Indigo|Ivory|Khaki|Lavender|LavenderBlush|LawnGreen|LemonChiffon|LightBlue|LightCoral|LightCyan|LightGoldenRodYellow|LightGr[ae]y|LightGreen|LightPink|LightSalmon|LightSeaGreen|LightSkyBlue|LightSlateGr[ae]y|LightSteelBlue|LightYellow|Lime|LimeGreen|Linen|Magenta|Maroon|MediumAquaMarine|MediumBlue|MediumOrchid|MediumPurple|MediumSeaGreen|MediumSlateBlue|MediumSpringGreen|MediumTurquoise|MediumVioletRed|MidnightBlue|MintCream|MistyRose|Moccasin|NavajoWhite|Navy|OldLace|Olive|OliveDrab|Orange|OrangeRed|Orchid|PaleGoldenRod|PaleGreen|PaleTurquoise|PaleVioletRed|PapayaWhip|PeachPuff|Peru|Pink|Plum|PowderBlue|Purple|Red|RosyBrown|RoyalBlue|SaddleBrown|Salmon|SandyBrown|SeaGreen|SeaShell|Sienna|Silver|SkyBlue|SlateBlue|SlateGr[ae]y|Snow|SpringGreen|SteelBlue|Tan|Teal|Thistle|Tomato|Transparent|Turquoise|Violet|Wheat|White|WhiteSmoke|Yellow|YellowGreen)\b/i,{pattern:/\b(?:rgb|hsl)\(\s*\d{1,3}\s*,\s*\d{1,3}%?\s*,\s*\d{1,3}%?\s*\)\B|\b(?:rgb|hsl)a\(\s*\d{1,3}\s*,\s*\d{1,3}%?\s*,\s*\d{1,3}%?\s*,\s*(?:0|0?\.\d+|1)\s*\)\B/i,inside:{unit:t,number:n,function:/[\w-]+(?=\()/,punctuation:/[(),]/}}],entity:/\\[\da-f]{1,8}/i,unit:t,boolean:/\b(?:true|false)\b/,operator:[/~|[+!\/%<>?=]=?|[-:]=|\*[*=]?|\.{2,3}|&&|\|\||\B-\B|\b(?:and|in|is(?: a| defined| not|nt)?|not|or)\b/],number:n,punctuation:/[{}()\[\];:,]/};r.interpolation={pattern:/\{[^\r\n}:]+\}/,alias:"variable",inside:{delimiter:{pattern:/^{|}$/,alias:"punctuation"},rest:r}},r.func={pattern:/[\w-]+\([^)]*\).*/,inside:{function:/^[^(]+/,rest:r}},e.languages.stylus={"atrule-declaration":{pattern:/(^\s*)@.+/m,lookbehind:!0,inside:{atrule:/^@[\w-]+/,rest:r}},"variable-declaration":{pattern:/(^[ \t]*)[\w$-]+\s*.?=[ \t]*(?:\{[^{}]*\}|\S.*|$)/m,lookbehind:!0,inside:{variable:/^\S+/,rest:r}},statement:{pattern:/(^[ \t]*)(?:if|else|for|return|unless)[ \t].+/m,lookbehind:!0,inside:{keyword:/^\S+/,rest:r}},"property-declaration":{pattern:/((?:^|\{)([ \t]*))(?:[\w-]|\{[^}\r\n]+\})+(?:\s*:\s*|[ \t]+)(?!\s)[^{\r\n]*(?:;|[^{\r\n,](?=$)(?!(?:\r?\n|\r)(?:\{|\2[ \t]+)))/m,lookbehind:!0,inside:{property:{pattern:/^[^\s:]+/,inside:{interpolation:r.interpolation}},rest:r}},selector:{pattern:/(^[ \t]*)(?:(?=\S)(?:[^{}\r\n:()]|::?[\w-]+(?:\([^)\r\n]*\)|(?![\w-]))|\{[^}\r\n]+\})+)(?:(?:\r?\n|\r)(?:\1(?:(?=\S)(?:[^{}\r\n:()]|::?[\w-]+(?:\([^)\r\n]*\)|(?![\w-]))|\{[^}\r\n]+\})+)))*(?:,$|\{|(?=(?:\r?\n|\r)(?:\{|\1[ \t]+)))/m,lookbehind:!0,inside:{interpolation:r.interpolation,comment:r.comment,punctuation:/[{},]/}},func:r.func,string:r.string,comment:{pattern:/(^|[^\\])(?:\/\*[\s\S]*?\*\/|\/\/.*)/,lookbehind:!0,greedy:!0},interpolation:r.interpolation,punctuation:/[{}()\[\];:.]/}}(o),function(e){e.languages.typescript=e.languages.extend("javascript",{"class-name":{pattern:/(\b(?:class|extends|implements|instanceof|interface|new|type)\s+)(?!keyof\b)(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*(?:\s*<(?:[^<>]|<(?:[^<>]|<[^<>]*>)*>)*>)?/,lookbehind:!0,greedy:!0,inside:null},keyword:/\b(?:abstract|as|asserts|async|await|break|case|catch|class|const|constructor|continue|debugger|declare|default|delete|do|else|enum|export|extends|finally|for|from|function|get|if|implements|import|in|instanceof|interface|is|keyof|let|module|namespace|new|null|of|package|private|protected|public|readonly|return|require|set|static|super|switch|this|throw|try|type|typeof|undefined|var|void|while|with|yield)\b/,builtin:/\b(?:string|Function|any|number|boolean|Array|symbol|console|Promise|unknown|never)\b/}),delete e.languages.typescript.parameter;var t=e.languages.extend("typescript",{});delete t["class-name"],e.languages.typescript["class-name"].inside=t,e.languages.insertBefore("typescript","function",{"generic-function":{pattern:/#?(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*\s*<(?:[^<>]|<(?:[^<>]|<[^<>]*>)*>)*>(?=\s*\()/,greedy:!0,inside:{function:/^#?(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*/,generic:{pattern:/<[\s\S]+/,alias:"class-name",inside:t}}}}),e.languages.ts=e.languages.typescript}(o),function(e){var t=e.util.clone(e.languages.typescript);e.languages.tsx=e.languages.extend("jsx",t);var n=e.languages.tsx.tag;n.pattern=RegExp(/(^|[^\w$]|(?=<\/))/.source+"(?:"+n.pattern.source+")",n.pattern.flags),n.lookbehind=!0}(o),o.languages.wasm={comment:[/\(;[\s\S]*?;\)/,{pattern:/;;.*/,greedy:!0}],string:{pattern:/"(?:\\[\s\S]|[^"\\])*"/,greedy:!0},keyword:[{pattern:/\b(?:align|offset)=/,inside:{operator:/=/}},{pattern:/\b(?:(?:f32|f64|i32|i64)(?:\.(?:abs|add|and|ceil|clz|const|convert_[su]\/i(?:32|64)|copysign|ctz|demote\/f64|div(?:_[su])?|eqz?|extend_[su]\/i32|floor|ge(?:_[su])?|gt(?:_[su])?|le(?:_[su])?|load(?:(?:8|16|32)_[su])?|lt(?:_[su])?|max|min|mul|nearest|neg?|or|popcnt|promote\/f32|reinterpret\/[fi](?:32|64)|rem_[su]|rot[lr]|shl|shr_[su]|store(?:8|16|32)?|sqrt|sub|trunc(?:_[su]\/f(?:32|64))?|wrap\/i64|xor))?|memory\.(?:grow|size))\b/,inside:{punctuation:/\./}},/\b(?:anyfunc|block|br(?:_if|_table)?|call(?:_indirect)?|data|drop|elem|else|end|export|func|get_(?:global|local)|global|if|import|local|loop|memory|module|mut|nop|offset|param|result|return|select|set_(?:global|local)|start|table|tee_local|then|type|unreachable)\b/],variable:/\$[\w!#$%&'*+\-./:<=>?@\\^_`|~]+/i,number:/[+-]?\b(?:\d(?:_?\d)*(?:\.\d(?:_?\d)*)?(?:[eE][+-]?\d(?:_?\d)*)?|0x[\da-fA-F](?:_?[\da-fA-F])*(?:\.[\da-fA-F](?:_?[\da-fA-D])*)?(?:[pP][+-]?\d(?:_?\d)*)?)\b|\binf\b|\bnan(?::0x[\da-fA-F](?:_?[\da-fA-D])*)?\b/,punctuation:/[()]/},function(e){var t=/[*&][^\s[\]{},]+/,n=/!(?:<[\w\-%#;/?:@&=+$,.!~*'()[\]]+>|(?:[a-zA-Z\d-]*!)?[\w\-%#;/?:@&=+$.~*'()]+)?/,r="(?:"+n.source+"(?:[ \t]+"+t.source+")?|"+t.source+"(?:[ \t]+"+n.source+")?)",a=/(?:[^\s\x00-\x08\x0e-\x1f!"#%&'*,\-:>?@[\]`{|}\x7f-\x84\x86-\x9f\ud800-\udfff\ufffe\uffff]|[?:-])(?:[ \t]*(?:(?![#:])|:))*/.source.replace(//g,(function(){return/[^\s\x00-\x08\x0e-\x1f,[\]{}\x7f-\x84\x86-\x9f\ud800-\udfff\ufffe\uffff]/.source})),i=/"(?:[^"\\\r\n]|\\.)*"|'(?:[^'\\\r\n]|\\.)*'/.source;function o(e,t){t=(t||"").replace(/m/g,"")+"m";var n=/([:\-,[{]\s*(?:\s<>[ \t]+)?)(?:<>)(?=[ \t]*(?:$|,|]|}|(?:[\r\n]\s*)?#))/.source.replace(/<>/g,(function(){return r})).replace(/<>/g,(function(){return e}));return RegExp(n,t)}e.languages.yaml={scalar:{pattern:RegExp(/([\-:]\s*(?:\s<>[ \t]+)?[|>])[ \t]*(?:((?:\r?\n|\r)[ \t]+)\S[^\r\n]*(?:\2[^\r\n]+)*)/.source.replace(/<>/g,(function(){return r}))),lookbehind:!0,alias:"string"},comment:/#.*/,key:{pattern:RegExp(/((?:^|[:\-,[{\r\n?])[ \t]*(?:<>[ \t]+)?)<>(?=\s*:\s)/.source.replace(/<>/g,(function(){return r})).replace(/<>/g,(function(){return"(?:"+a+"|"+i+")"}))),lookbehind:!0,greedy:!0,alias:"atrule"},directive:{pattern:/(^[ \t]*)%.+/m,lookbehind:!0,alias:"important"},datetime:{pattern:o(/\d{4}-\d\d?-\d\d?(?:[tT]|[ \t]+)\d\d?:\d{2}:\d{2}(?:\.\d*)?(?:[ \t]*(?:Z|[-+]\d\d?(?::\d{2})?))?|\d{4}-\d{2}-\d{2}|\d\d?:\d{2}(?::\d{2}(?:\.\d*)?)?/.source),lookbehind:!0,alias:"number"},boolean:{pattern:o(/true|false/.source,"i"),lookbehind:!0,alias:"important"},null:{pattern:o(/null|~/.source,"i"),lookbehind:!0,alias:"important"},string:{pattern:o(i),lookbehind:!0,greedy:!0},number:{pattern:o(/[+-]?(?:0x[\da-f]+|0o[0-7]+|(?:\d+(?:\.\d*)?|\.?\d+)(?:e[+-]?\d+)?|\.inf|\.nan)/.source,"i"),lookbehind:!0},tag:n,important:t,punctuation:/---|[:[\]{}\-,|>?]|\.\.\./},e.languages.yml=e.languages.yaml}(o),t.a=o},SksO:function(e,t){function n(t,r){return e.exports=n=Object.setPrototypeOf||function(e,t){return e.__proto__=t,e},e.exports.default=e.exports,e.exports.__esModule=!0,n(t,r)}e.exports=n,e.exports.default=e.exports,e.exports.__esModule=!0},TJpk:function(e,t,n){t.__esModule=!0,t.Helmet=void 0;var r=Object.assign||function(e){for(var t=1;t=0||Object.prototype.hasOwnProperty.call(e,r)&&(n[r]=e[r]);return n}function f(e,t){if(!(e instanceof t))throw new TypeError("Cannot call a class as a function")}function m(e,t){if(!e)throw new ReferenceError("this hasn't been initialised - super() hasn't been called");return!t||"object"!=typeof t&&"function"!=typeof t?e:t}var g,h,y,b=(0,s.default)(l.reducePropsToState,l.handleClientStateChange,l.mapStateOnServer)((function(){return null})),S=(g=b,y=h=function(e){function t(){return f(this,t),m(this,e.apply(this,arguments))}return function(e,t){if("function"!=typeof t&&null!==t)throw new TypeError("Super expression must either be null or a function, not "+typeof t);e.prototype=Object.create(t&&t.prototype,{constructor:{value:e,enumerable:!1,writable:!0,configurable:!0}}),t&&(Object.setPrototypeOf?Object.setPrototypeOf(e,t):e.__proto__=t)}(t,e),t.prototype.shouldComponentUpdate=function(e){return!(0,c.default)(this.props,e)},t.prototype.mapNestedChildrenToProps=function(e,t){if(!t)return null;switch(e.type){case u.TAG_NAMES.SCRIPT:case u.TAG_NAMES.NOSCRIPT:return{innerHTML:t};case u.TAG_NAMES.STYLE:return{cssText:t}}throw new Error("<"+e.type+" /> elements are self-closing and can not contain children. Refer to our API for more information.")},t.prototype.flattenArrayTypeChildren=function(e){var t,n=e.child,a=e.arrayTypeChildren,i=e.newChildProps,o=e.nestedChildren;return r({},a,((t={})[n.type]=[].concat(a[n.type]||[],[r({},i,this.mapNestedChildrenToProps(n,o))]),t))},t.prototype.mapObjectTypeChildren=function(e){var t,n,a=e.child,i=e.newProps,o=e.newChildProps,s=e.nestedChildren;switch(a.type){case u.TAG_NAMES.TITLE:return r({},i,((t={})[a.type]=s,t.titleAttributes=r({},o),t));case u.TAG_NAMES.BODY:return r({},i,{bodyAttributes:r({},o)});case u.TAG_NAMES.HTML:return r({},i,{htmlAttributes:r({},o)})}return r({},i,((n={})[a.type]=r({},o),n))},t.prototype.mapArrayTypeChildrenToProps=function(e,t){var n=r({},t);return Object.keys(e).forEach((function(t){var a;n=r({},n,((a={})[t]=e[t],a))})),n},t.prototype.warnOnInvalidChildren=function(e,t){return!0},t.prototype.mapChildrenToProps=function(e,t){var n=this,r={};return i.default.Children.forEach(e,(function(e){if(e&&e.props){var a=e.props,i=a.children,o=p(a,["children"]),s=(0,l.convertReactPropstoHtmlAttributes)(o);switch(n.warnOnInvalidChildren(e,i),e.type){case u.TAG_NAMES.LINK:case u.TAG_NAMES.META:case u.TAG_NAMES.NOSCRIPT:case u.TAG_NAMES.SCRIPT:case u.TAG_NAMES.STYLE:r=n.flattenArrayTypeChildren({child:e,arrayTypeChildren:r,newChildProps:s,nestedChildren:i});break;default:t=n.mapObjectTypeChildren({child:e,newProps:t,newChildProps:s,nestedChildren:i})}}})),t=this.mapArrayTypeChildrenToProps(r,t)},t.prototype.render=function(){var e=this.props,t=e.children,n=p(e,["children"]),a=r({},n);return t&&(a=this.mapChildrenToProps(t,a)),i.default.createElement(g,a)},a(t,null,[{key:"canUseDOM",set:function(e){g.canUseDOM=e}}]),t}(i.default.Component),h.propTypes={base:o.default.object,bodyAttributes:o.default.object,children:o.default.oneOfType([o.default.arrayOf(o.default.node),o.default.node]),defaultTitle:o.default.string,defer:o.default.bool,encodeSpecialCharacters:o.default.bool,htmlAttributes:o.default.object,link:o.default.arrayOf(o.default.object),meta:o.default.arrayOf(o.default.object),noscript:o.default.arrayOf(o.default.object),onChangeClientState:o.default.func,script:o.default.arrayOf(o.default.object),style:o.default.arrayOf(o.default.object),title:o.default.string,titleAttributes:o.default.object,titleTemplate:o.default.string},h.defaultProps={defer:!0,encodeSpecialCharacters:!0},h.peek=g.peek,h.rewind=function(){var e=g.rewind();return e||(e=(0,l.mapStateOnServer)({baseTag:[],bodyAttributes:{},encodeSpecialCharacters:!0,htmlAttributes:{},linkTags:[],metaTags:[],noscriptTags:[],scriptTags:[],styleTags:[],title:"",titleAttributes:{}})),e},y);S.renderStatic=S.rewind,t.Helmet=S,t.default=S},TOwV:function(e,t,n){"use strict";e.exports=n("qT12")},TqRt:function(e,t){e.exports=function(e){return e&&e.__esModule?e:{default:e}},e.exports.default=e.exports,e.exports.__esModule=!0},TqVZ:function(e,t,n){"use strict";var r=n("z9I/");var a=function(e){function t(e,t,r){var a=t.trim().split(m);t=a;var i=a.length,o=e.length;switch(o){case 0:case 1:var s=0;for(e=0===o?"":e[0]+" ";sr&&(r=(t=t.trim()).charCodeAt(0)),r){case 38:return t.replace(g,"$1"+e.trim());case 58:return e.trim()+t.replace(g,"$1"+e.trim());default:if(0<1*n&&0c.charCodeAt(8))break;case 115:o=o.replace(c,"-webkit-"+c)+";"+o;break;case 207:case 102:o=o.replace(c,"-webkit-"+(102s.charCodeAt(0)&&(s=s.trim()),s=[s],0f)&&(B=(W=W.replace(" ",":")).length),00)return s[s.length-1];if(e&&e.location.pathname===a)return o?decodeURI(o.slice(1)):[0,0];return!0}var M=function(e){function t(t){var n;return(n=e.call(this,t)||this).announcementRef=s.a.createRef(),n}Object(a.a)(t,e);var n=t.prototype;return n.componentDidUpdate=function(e,t){var n=this;requestAnimationFrame((function(){var e="new page at "+n.props.location.pathname;document.title&&(e=document.title);var t=document.querySelectorAll("#gatsby-focus-wrapper h1");t&&t.length&&(e=t[0].textContent);var r="Navigated to "+e;n.announcementRef.current&&(n.announcementRef.current.innerText!==r&&(n.announcementRef.current.innerText=r))}))},n.render=function(){return Object(v.d)("div",Object(r.a)({},b,{ref:this.announcementRef}))},t}(s.a.Component),w=function(e,t){var n,r;return e.href!==t.href||(null==e||null===(n=e.state)||void 0===n?void 0:n.key)!==(null==t||null===(r=t.state)||void 0===r?void 0:r.key)},D=function(e){function t(t){var n;return n=e.call(this,t)||this,E(t.location,null),n}Object(a.a)(t,e);var n=t.prototype;return n.componentDidMount=function(){P(this.props.location,null)},n.shouldComponentUpdate=function(e){return!!w(e.location,this.props.location)&&(E(this.props.location,e.location),!0)},n.componentDidUpdate=function(e){w(e.location,this.props.location)&&P(this.props.location,e.location)},n.render=function(){return Object(v.d)(s.a.Fragment,null,this.props.children,Object(v.d)(M,{location:location}))},t}(s.a.Component),x=n("IOVJ"),k=n("NsGk"),L=n.n(k),F=n("rePB");function j(e,t){for(var n in e)if(!(n in t))return!0;for(var r in t)if(e[r]!==t[r])return!0;return!1}function N(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function _(e){for(var t=1;t0&&n("NSX3");var e=function(e){return Object(v.d)(u.BaseContext.Provider,{value:{baseuri:"/",basepath:"/"}},Object(v.d)(x.a,e))},t=s.a.createContext({}),o=function(e){function n(){return e.apply(this,arguments)||this}return Object(a.a)(n,e),n.prototype.render=function(){var e=this.props.children;return Object(v.d)(u.Location,null,(function(n){var r=n.location;return Object(v.d)(B,{location:r},(function(n){var r=n.pageResources,a=n.location,i=Object(g.getStaticQueryResults)();return Object(v.d)(m.StaticQueryContext.Provider,{value:i},Object(v.d)(t.Provider,{value:{pageResources:r,location:a}},e))}))}))},n}(s.a.Component),c=function(n){function i(){return n.apply(this,arguments)||this}return Object(a.a)(i,n),i.prototype.render=function(){var n=this;return Object(v.d)(t.Consumer,null,(function(t){var a=t.pageResources,i=t.location;return Object(v.d)(D,{location:i},Object(v.d)(d.ScrollContext,{location:i,shouldUpdateScroll:I},Object(v.d)(u.Router,{basepath:"",location:i,id:"gatsby-focus-wrapper"},Object(v.d)(e,Object(r.a)({path:"/404.html"===a.page.path?Object(G.a)(i.pathname,""):encodeURI(a.page.matchPath||a.page.path)},n.props,{location:i,pageResources:a},a.json)))))}))},i}(s.a.Component),p=window,h=p.pagePath,y=p.location;h&&""+h!==y.pathname&&!(W.findMatchPath(Object(G.a)(y.pathname,""))||"/404.html"===h||h.match(/^\/404\/?$/)||h.match(/^\/offline-plugin-app-shell-fallback\/?$/))&&Object(u.navigate)(""+h+y.search+y.hash,{replace:!0}),g.publicLoader.loadPage(y.pathname).then((function(e){if(!e||e.status===g.PageResourceStatus.Error)throw new Error("page resources for "+y.pathname+" not found. Not rendering React");window.___webpackCompilationHash=e.page.webpackCompilationHash;var t=Object(i.apiRunner)("wrapRootElement",{element:Object(v.d)(c,null)},Object(v.d)(c,null),(function(e){return{element:e.result}})).pop(),n=function(){return Object(v.d)(o,null,t)},r=Object(i.apiRunner)("replaceHydrateFunction",void 0,l.a.hydrate)[0];f()((function(){r(Object(v.d)(n,null),"undefined"!=typeof window?document.getElementById("___gatsby"):void 0,(function(){Object(i.apiRunner)("onInitialClientRender")}))}))}))}))},VX4j:function(e,t){e.exports="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAYAAADgdz34AAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAAApgAAAKYB3X3/OAAAABl0RVh0U29mdHdhcmUAd3d3Lmlua3NjYXBlLm9yZ5vuPBoAAANGSURBVEiJndVPbNRVEAfwz9vd/q8tBQtoxSYYDKYmejMGD3DxYloMiRoT22IEDQcPno3xoFclMf6JHrDFyIVEI3g2eiDoRWOMfygqNrSkoeAWCtIu230e3m+77e6KCZO8vH3zZuY7M+/7mxVjVFu7C+vPt7mmh4fi+eEDMUYFVZkdeZU7dhgIzxOj25ULe3fJx6PYamZkDYD4rRDmmgafDIdE3aIJbcrKxkQF4/GtBtuY/43KGVBxOsT/S3YijAomEVBCBe0geNlYfLfBZ3bfJmFlp7u/ONUcYCIMCw6jL1vhFikUURS9Zn88Vn9ZaOJA8DTuA3n0Zjm3ZlDL2VrASpZE8CwaABormAgPC75Cny7cmYE0kwou4Rq4IWeP0fhdc4DjIe+GD0QvIKcbmzOrtl56t9O2gRBYvsKVcyz9ne7nsQgiPhUdtD8uNVYwGRbQK497qu3ZzsYHUuB1EimepTiVKplBGZQM6rI7liFX5/Ur0rPmpYw3ZcEL7fRso3eQQgcCfffT0Z+i9K3GOFMNvh7gWOjDYGpJpuvbkQK1dND/IF1b6Oynf4jW7jU2a3zY6uPQ3whw0/u4S5DYIqsAOjdrkKqutSfbVcncL+ejOoAQsC39VGN9yOiTa8LmXIGOx8h11RxqzzTgeHLOAGKUM4pFFdzMzJYX0n79YiPAP/O0PUSlHTE9cCXdCJ7zVFxZA4DReA4/gKVMd/WvtJcWKf6e6FlapPgHS0UW3uPyN9b58IuxOFU91Ne+E+kL7cb1Oa5O0zPI0kJaa+XaLIszif21q4x2if+1ClLP/iRrUfYNufQTF79P2ceY2lFaZP5HLqaCFaUxmOSsT3RWD42j4mh4RnQEnTZYP+pCLh1Se2uZF0FZdNC0o16Plf8GgMnwOZ5Eot9GiefVmbQiDbtitif52njcUx+q+TSNTgoZQAlzddblJj7ByWah0htc2LvL7L5Nq9r98YhBLSo2481Vfbkh+DtytljWaiy+3QwgxOnhIfl4AmdoGTXw2eUGq8lwWNCDD1WUBC+hYNyLTf9iZ554RAiPG/jyjYKcR7E1wa3sxKkGh/H4Sp3mULNsVyVvTgxTqYIYmRk5oOK0e0/8fEvH25B/AZyRWA6LDlu9AAAAAElFTkSuQmCC"},VbXa:function(e,t,n){var r=n("SksO");e.exports=function(e,t){e.prototype=Object.create(t.prototype),e.prototype.constructor=e,r(e,t)},e.exports.default=e.exports,e.exports.__esModule=!0},Wbzz:function(e,t,n){"use strict";n.r(t),n.d(t,"graphql",(function(){return y})),n.d(t,"StaticQueryContext",(function(){return f})),n.d(t,"StaticQuery",(function(){return g})),n.d(t,"useStaticQuery",(function(){return h})),n.d(t,"prefetchPathname",(function(){return p}));var r=n("q1tI"),a=n.n(r),i=n("+ZDr"),o=n.n(i);n.d(t,"Link",(function(){return o.a})),n.d(t,"withAssetPrefix",(function(){return i.withAssetPrefix})),n.d(t,"withPrefix",(function(){return i.withPrefix})),n.d(t,"parsePath",(function(){return i.parsePath})),n.d(t,"navigate",(function(){return i.navigate})),n.d(t,"push",(function(){return i.push})),n.d(t,"replace",(function(){return i.replace})),n.d(t,"navigateTo",(function(){return i.navigateTo}));var s=n("7hJ6");n.d(t,"useScrollRestoration",(function(){return s.useScrollRestoration}));var c=n("lw3w"),l=n.n(c);n.d(t,"PageRenderer",(function(){return l.a}));var u=n("emEt"),d=n("qKvR"),p=u.default.enqueue,f=a.a.createContext({});function m(e){var t=e.staticQueryData,n=e.data,r=e.query,i=e.render,o=n?n.data:t[r]&&t[r].data;return Object(d.d)(a.a.Fragment,null,o&&i(o),!o&&Object(d.d)("div",null,"Loading (StaticQuery)"))}var g=function(e){var t=e.data,n=e.query,r=e.render,a=e.children;return Object(d.d)(f.Consumer,null,(function(e){return Object(d.d)(m,{data:t,query:n,render:r||a,staticQueryData:e})}))},h=function(e){var t;a.a.useContext;var n=a.a.useContext(f);if(isNaN(Number(e)))throw new Error("useStaticQuery was called with a string but expects to be called using `graphql`. Try this:\n\nimport { useStaticQuery, graphql } from 'gatsby';\n\nuseStaticQuery(graphql`"+e+"`);\n");if(null!==(t=n[e])&&void 0!==t&&t.data)return n[e].data;throw new Error("The result of this StaticQuery could not be fetched.\n\nThis is likely a bug in Gatsby and if refreshing the page does not fix it, please open an issue in https://github.com/gatsbyjs/gatsby/issues")};function y(){throw new Error("It appears like Gatsby is misconfigured. Gatsby related `graphql` calls are supposed to only be evaluated at compile time, and then compiled away. Unfortunately, something went wrong and the query was left in the compiled code.\n\nUnless your site has a complex or custom babel/Gatsby configuration this is likely a bug in Gatsby.")}},WkPL:function(e,t){e.exports=function(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n=0||Object.prototype.hasOwnProperty.call(e,r)&&(n[r]=e[r]);return n}function m(e,t){if(!(e instanceof t))throw new TypeError("Cannot call a class as a function")}function g(e,t){if(!e)throw new ReferenceError("this hasn't been initialised - super() hasn't been called");return!t||"object"!=typeof t&&"function"!=typeof t?e:t}function h(e,t){if("function"!=typeof t&&null!==t)throw new TypeError("Super expression must either be null or a function, not "+typeof t);e.prototype=Object.create(t&&t.prototype,{constructor:{value:e,enumerable:!1,writable:!0,configurable:!0}}),t&&(Object.setPrototypeOf?Object.setPrototypeOf(e,t):e.__proto__=t)}var y=function(e,t){var n=c()(t);return n.displayName=e,n},b=y("Location"),S=function(e){var t=e.children;return a.a.createElement(b.Consumer,null,(function(e){return e?t(e):a.a.createElement(A,null,t)}))},A=function(e){function t(){var n,r;m(this,t);for(var a=arguments.length,i=Array(a),o=0;o-1?(i=t.substring(0,r),o=t.substring(r)):i=t,a.a.createElement(b.Provider,{value:{location:{pathname:i,search:o,hash:""},navigate:function(){throw new Error("You can't call navigate on the server.")}}},n)},C=y("Base",{baseuri:"/",basepath:"/"}),O=function(e){return a.a.createElement(C.Consumer,null,(function(t){return a.a.createElement(S,null,(function(n){return a.a.createElement(T,p({},t,n,e))}))}))},T=function(e){function t(){return m(this,t),g(this,e.apply(this,arguments))}return h(t,e),t.prototype.render=function(){var e=this.props,t=e.location,n=e.navigate,r=e.basepath,i=e.primary,o=e.children,s=(e.baseuri,e.component),c=void 0===s?"div":s,l=f(e,["location","navigate","basepath","primary","children","baseuri","component"]),d=a.a.Children.toArray(o).reduce((function(e,t){var n=H(r)(t);return e.concat(n)}),[]),m=t.pathname,g=Object(u.pick)(d,m);if(g){var h=g.params,y=g.uri,b=g.route,S=g.route.value;r=b.default?r:b.path.replace(/\*$/,"");var A=p({},h,{uri:y,location:t,navigate:function(e,t){return n(Object(u.resolve)(e,y),t)}}),v=a.a.cloneElement(S,A,S.props.children?a.a.createElement(O,{location:t,primary:i},S.props.children):void 0),T=i?P:c,E=i?p({uri:y,location:t,component:c},l):l;return a.a.createElement(C.Provider,{value:{baseuri:y,basepath:r}},a.a.createElement(T,E,v))}return null},t}(a.a.PureComponent);T.defaultProps={primary:!0};var E=y("Focus"),P=function(e){var t=e.uri,n=e.location,r=e.component,i=f(e,["uri","location","component"]);return a.a.createElement(E.Consumer,null,(function(e){return a.a.createElement(M,p({},i,{component:r,requestFocus:e,uri:t,location:n}))}))},R=!0,I=0,M=function(e){function t(){var n,r;m(this,t);for(var a=arguments.length,i=Array(a),o=0;oe.length)&&(t=e.length);for(var n=0,r=new Array(t);nAFOTEC OT&E Guide",githubUrl:"",helpUrl:"",tweetText:"",links:[{text:"",link:""}],search:{enabled:!0,indexName:"il2_guide",algoliaAppId:"8WYYTT6SZL",algoliaSearchKey:"cbce654033659a526bb5fcd00086ebcc",algoliaAdminKey:{}.ALGOLIA_ADMIN_KEY}},sidebar:{forcedNavOrder:["/OT&E_Guide","/fn_guides","/acronyms","/glossary"],collapsedNav:["/OT&E_Guide"],links:[{text:"AFOTEC",link:"https://www.afotec.af.mil"},{text:"OT&E Templates/Job Aids",link:"https://usaf.dps.mil/sites/AFOTEC-PRIVATE/mainlibrary/"},{text:"OT&E Tools Catalog",link:"https://usaf.dps.mil/sites/AFOTEC-PRIVATE/mainlibrary/oteguide/SitePages/Tools-Page.aspx"}],frontline:!1,ignoreIndex:!0,title:""},siteMetadata:{title:"AFOTEC OT&E Guide",description:"Air Force Operational Test and Evaluation Guide",ogImage:null,docsLocation:"",favicon:"https://raw.githubusercontent.com/Travis42/misc/main/favicon.ico"},pwa:{enabled:!1,manifest:{name:"AFOTEC OT&E Guide",short_name:"OT&E Guide",start_url:"/",background_color:"#6b37bf",theme_color:"#6b37bf",display:"standalone",crossOrigin:"use-credentials",icons:[{src:"src/pwa-512.png",sizes:"512x512",type:"image/png"}]}}};e.exports=n},oxjq:function(e,t,n){"use strict";var r=/[|\\{}()[\]^$+*?.]/g;e.exports=function(e){if("string"!=typeof e)throw new TypeError("Expected a string");return e.replace(r,"\\$&")}},pVnL:function(e,t){function n(){return e.exports=n=Object.assign||function(e){for(var t=1;t1&&void 0!==arguments[1])||arguments[1];return!1===t?String(e):String(e).replace(/&/g,"&").replace(//g,">").replace(/"/g,""").replace(/'/g,"'")},d=function(e){var t=h(e,s.TAG_NAMES.TITLE),n=h(e,s.HELMET_PROPS.TITLE_TEMPLATE);if(n&&t)return n.replace(/%s/g,(function(){return t}));var r=h(e,s.HELMET_PROPS.DEFAULT_TITLE);return t||r||void 0},p=function(e){return h(e,s.HELMET_PROPS.ON_CHANGE_CLIENT_STATE)||function(){}},f=function(e,t){return t.filter((function(t){return void 0!==t[e]})).map((function(t){return t[e]})).reduce((function(e,t){return a({},e,t)}),{})},m=function(e,t){return t.filter((function(e){return void 0!==e[s.TAG_NAMES.BASE]})).map((function(e){return e[s.TAG_NAMES.BASE]})).reverse().reduce((function(t,n){if(!t.length)for(var r=Object.keys(n),a=0;a=0;n--){var r=e[n];if(r.hasOwnProperty(t))return r[t]}return null},y=(l=Date.now(),function(e){var t=Date.now();t-l>16?(l=t,e(t)):setTimeout((function(){y(e)}),0)}),b=function(e){return clearTimeout(e)},S="undefined"!=typeof window?window.requestAnimationFrame||window.webkitRequestAnimationFrame||window.mozRequestAnimationFrame||y:e.requestAnimationFrame||y,A="undefined"!=typeof window?window.cancelAnimationFrame||window.webkitCancelAnimationFrame||window.mozCancelAnimationFrame||b:e.cancelAnimationFrame||b,v=function(e){return console&&"function"==typeof console.warn&&console.warn(e)},C=null,O=function(e,t){var n=e.baseTag,r=e.bodyAttributes,a=e.htmlAttributes,i=e.linkTags,o=e.metaTags,c=e.noscriptTags,l=e.onChangeClientState,u=e.scriptTags,d=e.styleTags,p=e.title,f=e.titleAttributes;P(s.TAG_NAMES.BODY,r),P(s.TAG_NAMES.HTML,a),E(p,f);var m={baseTag:R(s.TAG_NAMES.BASE,n),linkTags:R(s.TAG_NAMES.LINK,i),metaTags:R(s.TAG_NAMES.META,o),noscriptTags:R(s.TAG_NAMES.NOSCRIPT,c),scriptTags:R(s.TAG_NAMES.SCRIPT,u),styleTags:R(s.TAG_NAMES.STYLE,d)},g={},h={};Object.keys(m).forEach((function(e){var t=m[e],n=t.newTags,r=t.oldTags;n.length&&(g[e]=n),r.length&&(h[e]=m[e].oldTags)})),t&&t(),l(e,g,h)},T=function(e){return Array.isArray(e)?e.join(""):e},E=function(e,t){void 0!==e&&document.title!==e&&(document.title=T(e)),P(s.TAG_NAMES.TITLE,t)},P=function(e,t){var n=document.getElementsByTagName(e)[0];if(n){for(var r=n.getAttribute(s.HELMET_ATTRIBUTE),a=r?r.split(","):[],i=[].concat(a),o=Object.keys(t),c=0;c=0;p--)n.removeAttribute(i[p]);a.length===i.length?n.removeAttribute(s.HELMET_ATTRIBUTE):n.getAttribute(s.HELMET_ATTRIBUTE)!==o.join(",")&&n.setAttribute(s.HELMET_ATTRIBUTE,o.join(","))}},R=function(e,t){var n=document.head||document.querySelector(s.TAG_NAMES.HEAD),r=n.querySelectorAll(e+"["+s.HELMET_ATTRIBUTE+"]"),a=Array.prototype.slice.call(r),i=[],o=void 0;return t&&t.length&&t.forEach((function(t){var n=document.createElement(e);for(var r in t)if(t.hasOwnProperty(r))if(r===s.TAG_PROPERTIES.INNER_HTML)n.innerHTML=t.innerHTML;else if(r===s.TAG_PROPERTIES.CSS_TEXT)n.styleSheet?n.styleSheet.cssText=t.cssText:n.appendChild(document.createTextNode(t.cssText));else{var c=void 0===t[r]?"":t[r];n.setAttribute(r,c)}n.setAttribute(s.HELMET_ATTRIBUTE,"true"),a.some((function(e,t){return o=t,n.isEqualNode(e)}))?a.splice(o,1):i.push(n)})),a.forEach((function(e){return e.parentNode.removeChild(e)})),i.forEach((function(e){return n.appendChild(e)})),{oldTags:a,newTags:i}},I=function(e){return Object.keys(e).reduce((function(t,n){var r=void 0!==e[n]?n+'="'+e[n]+'"':""+n;return t?t+" "+r:r}),"")},M=function(e){var t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:{};return Object.keys(e).reduce((function(t,n){return t[s.REACT_TAG_MAP[n]||n]=e[n],t}),t)},w=function(e,t,n){switch(e){case s.TAG_NAMES.TITLE:return{toComponent:function(){return e=t.title,n=t.titleAttributes,(r={key:e})[s.HELMET_ATTRIBUTE]=!0,a=M(n,r),[i.default.createElement(s.TAG_NAMES.TITLE,a,e)];var e,n,r,a},toString:function(){return function(e,t,n,r){var a=I(n),i=T(t);return a?"<"+e+" "+s.HELMET_ATTRIBUTE+'="true" '+a+">"+u(i,r)+"":"<"+e+" "+s.HELMET_ATTRIBUTE+'="true">'+u(i,r)+""}(e,t.title,t.titleAttributes,n)}};case s.ATTRIBUTE_NAMES.BODY:case s.ATTRIBUTE_NAMES.HTML:return{toComponent:function(){return M(t)},toString:function(){return I(t)}};default:return{toComponent:function(){return function(e,t){return t.map((function(t,n){var r,a=((r={key:n})[s.HELMET_ATTRIBUTE]=!0,r);return Object.keys(t).forEach((function(e){var n=s.REACT_TAG_MAP[e]||e;if(n===s.TAG_PROPERTIES.INNER_HTML||n===s.TAG_PROPERTIES.CSS_TEXT){var r=t.innerHTML||t.cssText;a.dangerouslySetInnerHTML={__html:r}}else a[n]=t[e]})),i.default.createElement(e,a)}))}(e,t)},toString:function(){return function(e,t,n){return t.reduce((function(t,r){var a=Object.keys(r).filter((function(e){return!(e===s.TAG_PROPERTIES.INNER_HTML||e===s.TAG_PROPERTIES.CSS_TEXT)})).reduce((function(e,t){var a=void 0===r[t]?t:t+'="'+u(r[t],n)+'"';return e?e+" "+a:a}),""),i=r.innerHTML||r.cssText||"",o=-1===s.SELF_CLOSING_TAGS.indexOf(e);return t+"<"+e+" "+s.HELMET_ATTRIBUTE+'="true" '+a+(o?"/>":">"+i+"")}),"")}(e,t,n)}}}};t.convertReactPropstoHtmlAttributes=function(e){var t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:{};return Object.keys(e).reduce((function(t,n){return t[s.HTML_TAG_MAP[n]||n]=e[n],t}),t)},t.handleClientStateChange=function(e){C&&A(C),e.defer?C=S((function(){O(e,(function(){C=null}))})):(O(e),C=null)},t.mapStateOnServer=function(e){var t=e.baseTag,n=e.bodyAttributes,r=e.encode,a=e.htmlAttributes,i=e.linkTags,o=e.metaTags,c=e.noscriptTags,l=e.scriptTags,u=e.styleTags,d=e.title,p=void 0===d?"":d,f=e.titleAttributes;return{base:w(s.TAG_NAMES.BASE,t,r),bodyAttributes:w(s.ATTRIBUTE_NAMES.BODY,n,r),htmlAttributes:w(s.ATTRIBUTE_NAMES.HTML,a,r),link:w(s.TAG_NAMES.LINK,i,r),meta:w(s.TAG_NAMES.META,o,r),noscript:w(s.TAG_NAMES.NOSCRIPT,c,r),script:w(s.TAG_NAMES.SCRIPT,l,r),style:w(s.TAG_NAMES.STYLE,u,r),title:w(s.TAG_NAMES.TITLE,{title:p,titleAttributes:f},r)}},t.reducePropsToState=function(e){return{baseTag:m([s.TAG_PROPERTIES.HREF],e),bodyAttributes:f(s.ATTRIBUTE_NAMES.BODY,e),defer:h(e,s.HELMET_PROPS.DEFER),encode:h(e,s.HELMET_PROPS.ENCODE_SPECIAL_CHARACTERS),htmlAttributes:f(s.ATTRIBUTE_NAMES.HTML,e),linkTags:g(s.TAG_NAMES.LINK,[s.TAG_PROPERTIES.REL,s.TAG_PROPERTIES.HREF],e),metaTags:g(s.TAG_NAMES.META,[s.TAG_PROPERTIES.NAME,s.TAG_PROPERTIES.CHARSET,s.TAG_PROPERTIES.HTTPEQUIV,s.TAG_PROPERTIES.PROPERTY,s.TAG_PROPERTIES.ITEM_PROP],e),noscriptTags:g(s.TAG_NAMES.NOSCRIPT,[s.TAG_PROPERTIES.INNER_HTML],e),onChangeClientState:p(e),scriptTags:g(s.TAG_NAMES.SCRIPT,[s.TAG_PROPERTIES.SRC,s.TAG_PROPERTIES.INNER_HTML],e),styleTags:g(s.TAG_NAMES.STYLE,[s.TAG_PROPERTIES.CSS_TEXT],e),title:d(e),titleAttributes:f(s.ATTRIBUTE_NAMES.TITLE,e)}},t.requestAnimationFrame=S,t.warn=v}).call(this,n("yLpj"))},vg9a:function(e,t,n){},wTIg:function(e,t,n){"use strict";var r=n("lSNA"),a=n.n(r),i=n("q1tI"),o=n("9uj6"),s=n("qKvR"),c=n("SIPS"),l=n("MiSq"),u=o.a,d=function(e){return"theme"!==e&&"innerRef"!==e},p=function(e){return"string"==typeof e&&e.charCodeAt(0)>96?u:d};function f(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function m(e){for(var t=1;t0?u:n?[n]:[]},t.apiRunnerAsync=function(e,t,n){return r.reduce((function(n,r){return r.plugin[e]?n.then((function(){return r.plugin[e](t,r.options)})):n}),Promise.resolve())}},yHiX:function(e,t,n){"use strict";var r,a,i=n("q1tI");try{a=n("RJKl"),r=a&&a.default||a}catch(o){throw-1!==o.toString().indexOf("Error: Cannot find module")?new Error("Couldn't find layout component at \"/home/t42/Documents/programming/Projects/OT_Guide/IL-2 Guide/src/templates/docs.js.\n\nPlease create layout component in that location or specify path to layout component in gatsby-config.js"):(console.error(o),o)}e.exports=function(e){var t=e.element,n=e.props;return i.createElement(r,n,t)}},yJwK:function(e,t,n){"use strict";e.exports=function(e,t,n,r,a,i,o,s){if(!e){var c;if(void 0===t)c=new Error("Minified exception occurred; use the non-minified dev environment for the full error message and additional helpful warnings.");else{var l=[n,r,a,i,o,s],u=0;(c=new Error(t.replace(/%s/g,(function(){return l[u++]})))).name="Invariant Violation"}throw c.framesToPop=1,c}}},"z9I/":function(e,t,n){"use strict";n.d(t,"a",(function(){return r}));var r=function(){function e(e){this.isSpeedy=void 0===e.speedy||e.speedy,this.tags=[],this.ctr=0,this.nonce=e.nonce,this.key=e.key,this.container=e.container,this.before=null}var t=e.prototype;return t.insert=function(e){if(this.ctr%(this.isSpeedy?65e3:1)==0){var t,n=function(e){var t=document.createElement("style");return t.setAttribute("data-emotion",e.key),void 0!==e.nonce&&t.setAttribute("nonce",e.nonce),t.appendChild(document.createTextNode("")),t}(this);t=0===this.tags.length?this.before:this.tags[this.tags.length-1].nextSibling,this.container.insertBefore(n,t),this.tags.push(n)}var r=this.tags[this.tags.length-1];if(this.isSpeedy){var a=function(e){if(e.sheet)return e.sheet;for(var t=0;t=0||(a[n]=e[n]);return a}n.d(t,"a",(function(){return r}))}},[["UxWs",1,5,7,0]]]); -//# sourceMappingURL=app-eec04d2f552ddc7b4bf2.js.map \ No newline at end of file +/*! For license information please see app-03e333c274b6bc210459.js.LICENSE.txt */ +(window.webpackJsonp=window.webpackJsonp||[]).push([[3],{"+ZDr":function(e,t,n){"use strict";var r=n("TqRt");t.__esModule=!0,t.withPrefix=g,t.withAssetPrefix=function(e){return g(e,m())},t.navigateTo=t.replace=t.push=t.navigate=t.default=void 0;var a=r(n("8OQS")),i=r(n("PJYZ")),o=r(n("VbXa")),s=r(n("pVnL")),c=r(n("17x9")),l=r(n("q1tI")),u=n("YwZP"),d=n("LYrO"),p=n("cu4x");t.parsePath=p.parsePath;var f=function(e){return null==e?void 0:e.startsWith("/")};function g(e,t){var n,r;if(void 0===t&&(t=h()),!y(e))return e;if(e.startsWith("./")||e.startsWith("../"))return e;var a=null!==(n=null!==(r=t)&&void 0!==r?r:m())&&void 0!==n?n:"/";return""+((null==a?void 0:a.endsWith("/"))?a.slice(0,-1):a)+(e.startsWith("/")?e:"/"+e)}var m=function(){return""},h=function(){return""},y=function(e){return e&&!e.startsWith("http://")&&!e.startsWith("https://")&&!e.startsWith("//")};var b=function(e,t){return"number"==typeof e?e:y(e)?f(e)?g(e):function(e,t){return f(e)?e:(0,d.resolve)(e,t)}(e,t):e},A={activeClassName:c.default.string,activeStyle:c.default.object,partiallyActive:c.default.bool};function S(e){return l.default.createElement(u.Location,null,(function(t){var n=t.location;return l.default.createElement(v,(0,s.default)({},e,{_location:n}))}))}var v=function(e){function t(t){var n;(n=e.call(this,t)||this).defaultGetProps=function(e){var t=e.isPartiallyCurrent,r=e.isCurrent;return(n.props.partiallyActive?t:r)?{className:[n.props.className,n.props.activeClassName].filter(Boolean).join(" "),style:(0,s.default)({},n.props.style,n.props.activeStyle)}:null};var r=!1;return"undefined"!=typeof window&&window.IntersectionObserver&&(r=!0),n.state={IOSupported:r},n.handleRef=n.handleRef.bind((0,i.default)(n)),n}(0,o.default)(t,e);var n=t.prototype;return n._prefetch=function(){var e=window.location.pathname;this.props._location&&this.props._location.pathname&&(e=this.props._location.pathname);var t=b(this.props.to,e),n=(0,p.parsePath)(t).pathname;e!==n&&___loader.enqueue(n)},n.componentDidUpdate=function(e,t){this.props.to===e.to||this.state.IOSupported||this._prefetch()},n.componentDidMount=function(){this.state.IOSupported||this._prefetch()},n.componentWillUnmount=function(){if(this.io){var e=this.io,t=e.instance,n=e.el;t.unobserve(n),t.disconnect()}},n.handleRef=function(e){var t,n,r,a=this;this.props.innerRef&&this.props.innerRef.hasOwnProperty("current")?this.props.innerRef.current=e:this.props.innerRef&&this.props.innerRef(e),this.state.IOSupported&&e&&(this.io=(t=e,n=function(){a._prefetch()},(r=new window.IntersectionObserver((function(e){e.forEach((function(e){t===e.target&&(e.isIntersecting||e.intersectionRatio>0)&&(r.unobserve(t),r.disconnect(),n())}))}))).observe(t),{instance:r,el:t}))},n.render=function(){var e=this,t=this.props,n=t.to,r=t.getProps,i=void 0===r?this.defaultGetProps:r,o=t.onClick,c=t.onMouseEnter,d=(t.activeClassName,t.activeStyle,t.innerRef,t.partiallyActive,t.state),f=t.replace,g=t._location,m=(0,a.default)(t,["to","getProps","onClick","onMouseEnter","activeClassName","activeStyle","innerRef","partiallyActive","state","replace","_location"]);var h=b(n,g.pathname);return y(h)?l.default.createElement(u.Link,(0,s.default)({to:h,state:d,getProps:i,innerRef:this.handleRef,onMouseEnter:function(e){c&&c(e),___loader.hovering((0,p.parsePath)(h).pathname)},onClick:function(t){if(o&&o(t),!(0!==t.button||e.props.target||t.defaultPrevented||t.metaKey||t.altKey||t.ctrlKey||t.shiftKey)){t.preventDefault();var n=f,r=encodeURI(h)===g.pathname;"boolean"!=typeof f&&r&&(n=!0),window.___navigate(h,{state:d,replace:n})}return!0}},m)):l.default.createElement("a",(0,s.default)({href:h},m))},t}(l.default.Component);v.propTypes=(0,s.default)({},A,{onClick:c.default.func,to:c.default.string.isRequired,replace:c.default.bool,state:c.default.object});var O=function(e,t,n){return console.warn('The "'+e+'" method is now deprecated and will be removed in Gatsby v'+n+'. Please use "'+t+'" instead.')},C=l.default.forwardRef((function(e,t){return l.default.createElement(S,(0,s.default)({innerRef:t},e))}));t.default=C;t.navigate=function(e,t){window.___navigate(b(e,window.location.pathname),t)};var T=function(e){O("push","navigate",3),window.___push(b(e,window.location.pathname))};t.push=T;t.replace=function(e){O("replace","navigate",3),window.___replace(b(e,window.location.pathname))};t.navigateTo=function(e){return O("navigateTo","navigate",3),T(e)}},"/hTd":function(e,t,n){"use strict";t.__esModule=!0,t.SessionStorage=void 0;var r=function(){function e(){}var t=e.prototype;return t.read=function(e,t){var n=this.getStateKey(e,t);try{var r=window.sessionStorage.getItem(n);return r?JSON.parse(r):0}catch(a){return window&&window.___GATSBY_REACT_ROUTER_SCROLL&&window.___GATSBY_REACT_ROUTER_SCROLL[n]?window.___GATSBY_REACT_ROUTER_SCROLL[n]:0}},t.save=function(e,t,n){var r=this.getStateKey(e,t),a=JSON.stringify(n);try{window.sessionStorage.setItem(r,a)}catch(i){window&&window.___GATSBY_REACT_ROUTER_SCROLL||(window.___GATSBY_REACT_ROUTER_SCROLL={}),window.___GATSBY_REACT_ROUTER_SCROLL[r]=JSON.parse(a)}},t.getStateKey=function(e,t){var n="@@scroll|"+e.pathname;return null==t?n:n+"|"+t},e}();t.SessionStorage=r},"284h":function(e,t,n){var r=n("cDf5").default;function a(){if("function"!=typeof WeakMap)return null;var e=new WeakMap;return a=function(){return e},e}e.exports=function(e){if(e&&e.__esModule)return e;if(null===e||"object"!==r(e)&&"function"!=typeof e)return{default:e};var t=a();if(t&&t.has(e))return t.get(e);var n={},i=Object.defineProperty&&Object.getOwnPropertyDescriptor;for(var o in e)if(Object.prototype.hasOwnProperty.call(e,o)){var s=i?Object.getOwnPropertyDescriptor(e,o):null;s&&(s.get||s.set)?Object.defineProperty(n,o,s):n[o]=e[o]}return n.default=e,t&&t.set(e,n),n},e.exports.default=e.exports,e.exports.__esModule=!0},"2mql":function(e,t,n){"use strict";var r=n("TOwV"),a={childContextTypes:!0,contextType:!0,contextTypes:!0,defaultProps:!0,displayName:!0,getDefaultProps:!0,getDerivedStateFromError:!0,getDerivedStateFromProps:!0,mixins:!0,propTypes:!0,type:!0},i={name:!0,length:!0,prototype:!0,caller:!0,callee:!0,arguments:!0,arity:!0},o={$$typeof:!0,compare:!0,defaultProps:!0,displayName:!0,propTypes:!0,type:!0},s={};function c(e){return r.isMemo(e)?o:s[e.$$typeof]||a}s[r.ForwardRef]={$$typeof:!0,render:!0,defaultProps:!0,displayName:!0,propTypes:!0},s[r.Memo]=o;var l=Object.defineProperty,u=Object.getOwnPropertyNames,d=Object.getOwnPropertySymbols,p=Object.getOwnPropertyDescriptor,f=Object.getPrototypeOf,g=Object.prototype;e.exports=function e(t,n,r){if("string"!=typeof n){if(g){var a=f(n);a&&a!==g&&e(t,a,r)}var o=u(n);d&&(o=o.concat(d(n)));for(var s=c(t),m=c(n),h=0;h0&&e[n-1]===t?e:e.concat(t)},p=function(e,t){var n=e.plain,r=Object.create(null),a=e.styles.reduce((function(e,n){var r=n.languages,a=n.style;return r&&!r.includes(t)||n.types.forEach((function(t){var n=c({},e[t],a);e[t]=n})),e}),r);return a.root=n,a.plain=c({},n,{backgroundColor:null}),a};function f(e,t){var n={};for(var r in e)Object.prototype.hasOwnProperty.call(e,r)&&-1===t.indexOf(r)&&(n[r]=e[r]);return n}var g=function(e){function t(){for(var t=this,n=[],r=arguments.length;r--;)n[r]=arguments[r];e.apply(this,n),s(this,"getThemeDict",(function(e){if(void 0!==t.themeDict&&e.theme===t.prevTheme&&e.language===t.prevLanguage)return t.themeDict;t.prevTheme=e.theme,t.prevLanguage=e.language;var n=e.theme?p(e.theme,e.language):void 0;return t.themeDict=n})),s(this,"getLineProps",(function(e){var n=e.key,r=e.className,a=e.style,i=c({},f(e,["key","className","style","line"]),{className:"token-line",style:void 0,key:void 0}),o=t.getThemeDict(t.props);return void 0!==o&&(i.style=o.plain),void 0!==a&&(i.style=void 0!==i.style?c({},i.style,a):a),void 0!==n&&(i.key=n),r&&(i.className+=" "+r),i})),s(this,"getStyleForToken",(function(e){var n=e.types,r=e.empty,a=n.length,i=t.getThemeDict(t.props);if(void 0!==i){if(1===a&&"plain"===n[0])return r?{display:"inline-block"}:void 0;if(1===a&&!r)return i[n[0]];var o=r?{display:"inline-block"}:{},s=n.map((function(e){return i[e]}));return Object.assign.apply(Object,[o].concat(s))}})),s(this,"getTokenProps",(function(e){var n=e.key,r=e.className,a=e.style,i=e.token,o=c({},f(e,["key","className","style","token"]),{className:"token "+i.types.join(" "),children:i.content,style:t.getStyleForToken(i),key:void 0});return void 0!==a&&(o.style=void 0!==o.style?c({},o.style,a):a),void 0!==n&&(o.key=n),r&&(o.className+=" "+r),o})),s(this,"tokenize",(function(e,t,n,r){var a={code:t,grammar:n,language:r,tokens:[]};e.hooks.run("before-tokenize",a);var i=a.tokens=e.tokenize(a.code,a.grammar,a.language);return e.hooks.run("after-tokenize",a),i}))}return e&&(t.__proto__=e),t.prototype=Object.create(e&&e.prototype),t.prototype.constructor=t,t.prototype.render=function(){var e=this.props,t=e.Prism,n=e.language,r=e.code,a=e.children,i=this.getThemeDict(this.props),o=t.languages[n];return a({tokens:function(e){for(var t=[[]],n=[e],r=[0],a=[e.length],i=0,o=0,s=[],c=[s];o>-1;){for(;(i=r[o]++)0?f:["plain"],p=g):(f=d(f,g.type),g.alias&&(f=d(f,g.alias)),p=g.content),"string"==typeof p){var m=p.split(l),h=m.length;s.push({types:f,content:m[0]});for(var y=1;y>>0,1)},emit:function(t,n){(e[t]||[]).slice().map((function(e){e(n)})),(e["*"]||[]).slice().map((function(e){e(t,n)}))}}}();t.a=r},"7hJ6":function(e,t,n){"use strict";t.__esModule=!0,t.useScrollRestoration=t.ScrollContainer=t.ScrollContext=void 0;var r=n("Enzk");t.ScrollContext=r.ScrollHandler;var a=n("hd9s");t.ScrollContainer=a.ScrollContainer;var i=n("3uz+");t.useScrollRestoration=i.useScrollRestoration},"7ljp":function(e,t,n){"use strict";n.r(t),n.d(t,"MDXContext",(function(){return u})),n.d(t,"MDXProvider",(function(){return f})),n.d(t,"mdx",(function(){return h})),n.d(t,"useMDXComponents",(function(){return p})),n.d(t,"withMDXComponents",(function(){return d}));var r=n("q1tI"),a=n.n(r);function i(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function o(){return(o=Object.assign||function(e){for(var t=1;t=0||(a[n]=e[n]);return a}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(a[n]=e[n])}return a}var u=a.a.createContext({}),d=function(e){return function(t){var n=p(t.components);return a.a.createElement(e,o({},t,{components:n}))}},p=function(e){var t=a.a.useContext(u),n=t;return e&&(n="function"==typeof e?e(t):c(c({},t),e)),n},f=function(e){var t=p(e.components);return a.a.createElement(u.Provider,{value:t},e.children)},g={inlineCode:"code",wrapper:function(e){var t=e.children;return a.a.createElement(a.a.Fragment,{},t)}},m=a.a.forwardRef((function(e,t){var n=e.components,r=e.mdxType,i=e.originalType,o=e.parentName,s=l(e,["components","mdxType","originalType","parentName"]),u=p(n),d=r,f=u["".concat(o,".").concat(d)]||u[d]||g[d]||i;return n?a.a.createElement(f,c(c({ref:t},s),{},{components:n})):a.a.createElement(f,c({ref:t},s))}));function h(e,t){var n=arguments,r=t&&t.mdxType;if("string"==typeof e||r){var i=n.length,o=new Array(i);o[0]=m;var s={};for(var c in t)hasOwnProperty.call(t,c)&&(s[c]=t[c]);s.originalType=e,s.mdxType="string"==typeof e?e:r,o[1]=s;for(var l=2;l=0||(a[n]=e[n]);return a},e.exports.default=e.exports,e.exports.__esModule=!0},"94VI":function(e,t){t.polyfill=function(e){return e}},"9Xx/":function(e,t,n){"use strict";n.d(t,"c",(function(){return c})),n.d(t,"d",(function(){return l})),n.d(t,"a",(function(){return i})),n.d(t,"b",(function(){return o}));var r=Object.assign||function(e){for(var t=1;t1&&void 0!==arguments[1]?arguments[1]:{},l=c.state,u=c.replace,d=void 0!==u&&u;if("number"==typeof t)e.history.go(t);else{l=r({},l,{key:Date.now()+""});try{o||d?e.history.replaceState(l,null,t):e.history.pushState(l,null,t)}catch(f){e.location[d?"replace":"assign"](t)}}i=a(e),o=!0;var p=new Promise((function(e){return s=e}));return n.forEach((function(e){return e({location:i,action:"PUSH"})})),p}}},o=function(){var e=arguments.length>0&&void 0!==arguments[0]?arguments[0]:"/",t=e.indexOf("?"),n={pathname:t>-1?e.substr(0,t):e,search:t>-1?e.substr(t):""},r=0,a=[n],i=[null];return{get location(){return a[r]},addEventListener:function(e,t){},removeEventListener:function(e,t){},history:{get entries(){return a},get index(){return r},get state(){return i[r]},pushState:function(e,t,n){var o=n.split("?"),s=o[0],c=o[1],l=void 0===c?"":c;r++,a.push({pathname:s,search:l.length?"?"+l:l}),i.push(e)},replaceState:function(e,t,n){var o=n.split("?"),s=o[0],c=o[1],l=void 0===c?"":c;a[r]={pathname:s,search:l},i[r]=e},go:function(e){var t=r+e;t<0||t>i.length-1||(r=t)}}}},s=!("undefined"==typeof window||!window.document||!window.document.createElement),c=i(s?window:o()),l=c.navigate},"9uj6":function(e,t,n){"use strict";var r=n("4qRI"),a=/^((children|dangerouslySetInnerHTML|key|ref|autoFocus|defaultValue|defaultChecked|innerHTML|suppressContentEditableWarning|suppressHydrationWarning|valueLink|accept|acceptCharset|accessKey|action|allow|allowUserMedia|allowPaymentRequest|allowFullScreen|allowTransparency|alt|async|autoComplete|autoPlay|capture|cellPadding|cellSpacing|challenge|charSet|checked|cite|classID|className|cols|colSpan|content|contentEditable|contextMenu|controls|controlsList|coords|crossOrigin|data|dateTime|decoding|default|defer|dir|disabled|disablePictureInPicture|download|draggable|encType|form|formAction|formEncType|formMethod|formNoValidate|formTarget|frameBorder|headers|height|hidden|high|href|hrefLang|htmlFor|httpEquiv|id|inputMode|integrity|is|keyParams|keyType|kind|label|lang|list|loading|loop|low|marginHeight|marginWidth|max|maxLength|media|mediaGroup|method|min|minLength|multiple|muted|name|nonce|noValidate|open|optimum|pattern|placeholder|playsInline|poster|preload|profile|radioGroup|readOnly|referrerPolicy|rel|required|reversed|role|rows|rowSpan|sandbox|scope|scoped|scrolling|seamless|selected|shape|size|sizes|slot|span|spellCheck|src|srcDoc|srcLang|srcSet|start|step|style|summary|tabIndex|target|title|type|useMap|value|width|wmode|wrap|about|datatype|inlist|prefix|property|resource|typeof|vocab|autoCapitalize|autoCorrect|autoSave|color|inert|itemProp|itemScope|itemType|itemID|itemRef|on|results|security|unselectable|accentHeight|accumulate|additive|alignmentBaseline|allowReorder|alphabetic|amplitude|arabicForm|ascent|attributeName|attributeType|autoReverse|azimuth|baseFrequency|baselineShift|baseProfile|bbox|begin|bias|by|calcMode|capHeight|clip|clipPathUnits|clipPath|clipRule|colorInterpolation|colorInterpolationFilters|colorProfile|colorRendering|contentScriptType|contentStyleType|cursor|cx|cy|d|decelerate|descent|diffuseConstant|direction|display|divisor|dominantBaseline|dur|dx|dy|edgeMode|elevation|enableBackground|end|exponent|externalResourcesRequired|fill|fillOpacity|fillRule|filter|filterRes|filterUnits|floodColor|floodOpacity|focusable|fontFamily|fontSize|fontSizeAdjust|fontStretch|fontStyle|fontVariant|fontWeight|format|from|fr|fx|fy|g1|g2|glyphName|glyphOrientationHorizontal|glyphOrientationVertical|glyphRef|gradientTransform|gradientUnits|hanging|horizAdvX|horizOriginX|ideographic|imageRendering|in|in2|intercept|k|k1|k2|k3|k4|kernelMatrix|kernelUnitLength|kerning|keyPoints|keySplines|keyTimes|lengthAdjust|letterSpacing|lightingColor|limitingConeAngle|local|markerEnd|markerMid|markerStart|markerHeight|markerUnits|markerWidth|mask|maskContentUnits|maskUnits|mathematical|mode|numOctaves|offset|opacity|operator|order|orient|orientation|origin|overflow|overlinePosition|overlineThickness|panose1|paintOrder|pathLength|patternContentUnits|patternTransform|patternUnits|pointerEvents|points|pointsAtX|pointsAtY|pointsAtZ|preserveAlpha|preserveAspectRatio|primitiveUnits|r|radius|refX|refY|renderingIntent|repeatCount|repeatDur|requiredExtensions|requiredFeatures|restart|result|rotate|rx|ry|scale|seed|shapeRendering|slope|spacing|specularConstant|specularExponent|speed|spreadMethod|startOffset|stdDeviation|stemh|stemv|stitchTiles|stopColor|stopOpacity|strikethroughPosition|strikethroughThickness|string|stroke|strokeDasharray|strokeDashoffset|strokeLinecap|strokeLinejoin|strokeMiterlimit|strokeOpacity|strokeWidth|surfaceScale|systemLanguage|tableValues|targetX|targetY|textAnchor|textDecoration|textRendering|textLength|to|transform|u1|u2|underlinePosition|underlineThickness|unicode|unicodeBidi|unicodeRange|unitsPerEm|vAlphabetic|vHanging|vIdeographic|vMathematical|values|vectorEffect|version|vertAdvY|vertOriginX|vertOriginY|viewBox|viewTarget|visibility|widths|wordSpacing|writingMode|x|xHeight|x1|x2|xChannelSelector|xlinkActuate|xlinkArcrole|xlinkHref|xlinkRole|xlinkShow|xlinkTitle|xlinkType|xmlBase|xmlns|xmlnsXlink|xmlLang|xmlSpace|y|y1|y2|yChannelSelector|z|zoomAndPan|for|class|autofocus)|(([Dd][Aa][Tt][Aa]|[Aa][Rr][Ii][Aa]|x)-.*))$/,i=Object(r.a)((function(e){return a.test(e)||111===e.charCodeAt(0)&&110===e.charCodeAt(1)&&e.charCodeAt(2)<91}));t.a=i},BFUG:function(e,t){e.exports="data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IEFkb2JlIElsbHVzdHJhdG9yIDIzLjAuMywgU1ZHIEV4cG9ydCBQbHVnLUluIC4gU1ZHIFZlcnNpb246IDYuMDAgQnVpbGQgMCkgIC0tPgo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkxheWVyXzEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHg9IjBweCIgeT0iMHB4IgoJIHZpZXdCb3g9IjAgMCAzNSAyNyIgc3R5bGU9ImVuYWJsZS1iYWNrZ3JvdW5kOm5ldyAwIDAgMzUgMjc7IiB4bWw6c3BhY2U9InByZXNlcnZlIj4KPHN0eWxlIHR5cGU9InRleHQvY3NzIj4KCS5zdDB7ZmlsbC1ydWxlOmV2ZW5vZGQ7Y2xpcC1ydWxlOmV2ZW5vZGQ7ZmlsbDojRkZGRkZGO30KPC9zdHlsZT4KPHBhdGggY2xhc3M9InN0MCIgZD0iTTE3LDcuMmwwLjEsMS4ybC0xLjMtMC4xYy00LjYtMC41LTguNi0yLjQtMTItNS41TDIuMSwxLjFMMS43LDIuM0MwLjgsNC44LDEuMyw3LjUsMy4yLDkuM2MxLDEsMC44LDEuMS0xLDAuNQoJQzEuNyw5LjcsMS4xLDkuNSwxLjEsOS42QzAuOSw5LjgsMS41LDExLjksMiwxMi44YzAuNywxLjIsMiwyLjQsMy41LDMuMWwxLjIsMC41bC0xLjUsMGMtMS40LDAtMS41LDAtMS4zLDAuNQoJYzAuNSwxLjUsMi41LDMuMiw0LjcsMy45bDEuNiwwLjVsLTEuNCwwLjhjLTIsMS4xLTQuNCwxLjctNi44LDEuOEMwLjksMjMuOSwwLDI0LDAsMjQuMWMwLDAuMiwzLjEsMS42LDQuOSwyLjEKCWM1LjQsMS41LDExLjgsMC45LDE2LjYtMS44YzMuNC0xLjksNi44LTUuNiw4LjQtOS4yYzAuOS0xLjksMS43LTUuNSwxLjctNy4xYzAtMS4xLDAuMS0xLjIsMS41LTIuNmMwLjgtMC44LDEuNi0xLjYsMS44LTEuOAoJYzAuMy0wLjUsMC4yLTAuNS0xLjEsMGMtMi4xLDAuNy0yLjUsMC42LTEuNC0wLjVjMC44LTAuOCwxLjctMi4xLDEuNy0yLjVjMC0wLjEtMC40LDAtMC44LDAuM2MtMC41LDAuMi0xLjUsMC42LTIuMiwwLjhsLTEuNCwwLjQKCWwtMS4yLTAuOGMtMC43LTAuNC0xLjYtMC45LTIuMS0xYy0xLjMtMC4zLTMuMy0wLjMtNC40LDAuMUMxOC44LDEuNCwxNi44LDQuMiwxNyw3LjJ6Ii8+Cjwvc3ZnPgo="},BOnt:function(e,t,n){"use strict";var r=n("TqRt"),a=n("Wbzz"),i=r(n("hqbx"));t.onClientEntry=function(e,t){void 0===t&&(t={}),(0,i.default)(window,t,(function(e){(0,a.navigate)(e)}))}},BfwJ:function(e,t,n){"use strict";n.r(t),n.d(t,"useMDXScope",(function(){return o})),n.d(t,"MDXScopeProvider",(function(){return s}));var r=n("q1tI"),a=n.n(r),i=Object(r.createContext)({}),o=function(e){var t=Object(r.useContext)(i);return e||t},s=function(e){var t=e.__mdxScope,n=e.children;return a.a.createElement(i.Provider,{value:t},n)}},Bnag:function(e,t){e.exports=function(){throw new TypeError("Invalid attempt to spread non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")},e.exports.default=e.exports,e.exports.__esModule=!0},BsWD:function(e,t,n){"use strict";n.d(t,"a",(function(){return a}));var r=n("a3WO");function a(e,t){if(e){if("string"==typeof e)return Object(r.a)(e,t);var n=Object.prototype.toString.call(e).slice(8,-1);return"Object"===n&&e.constructor&&(n=e.constructor.name),"Map"===n||"Set"===n?Array.from(e):"Arguments"===n||/^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n)?Object(r.a)(e,t):void 0}}},CnBM:function(e,t,n){"use strict";var r="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Symbol&&e.constructor===Symbol&&e!==Symbol.prototype?"symbol":typeof e};function a(e,t){if(!(e instanceof t))throw new TypeError("Cannot call a class as a function")}function i(e,t){if(!e)throw new ReferenceError("this hasn't been initialised - super() hasn't been called");return!t||"object"!=typeof t&&"function"!=typeof t?e:t}function o(e,t){if("function"!=typeof t&&null!==t)throw new TypeError("Super expression must either be null or a function, not "+typeof t);e.prototype=Object.create(t&&t.prototype,{constructor:{value:e,enumerable:!1,writable:!0,configurable:!0}}),t&&(Object.setPrototypeOf?Object.setPrototypeOf(e,t):e.__proto__=t)}var s=n("q1tI"),c=n("17x9"),l=[],u=[];function d(e){var t=e(),n={loading:!0,loaded:null,error:null};return n.promise=t.then((function(e){return n.loading=!1,n.loaded=e,e})).catch((function(e){throw n.loading=!1,n.error=e,e})),n}function p(e){var t={loading:!1,loaded:{},error:null},n=[];try{Object.keys(e).forEach((function(r){var a=d(e[r]);a.loading?t.loading=!0:(t.loaded[r]=a.loaded,t.error=a.error),n.push(a.promise),a.promise.then((function(e){t.loaded[r]=e})).catch((function(e){t.error=e}))}))}catch(r){t.error=r}return t.promise=Promise.all(n).then((function(e){return t.loading=!1,e})).catch((function(e){throw t.loading=!1,e})),t}function f(e,t){return s.createElement((n=e)&&n.__esModule?n.default:n,t);var n}function g(e,t){var d,p;if(!t.loading)throw new Error("react-loadable requires a `loading` component");var g=Object.assign({loader:null,loading:null,delay:200,timeout:null,render:f,webpack:null,modules:null},t),m=null;function h(){return m||(m=e(g.loader)),m.promise}return l.push(h),"function"==typeof g.webpack&&u.push((function(){if(e=g.webpack,"object"===r(n.m)&&e().every((function(e){return void 0!==e&&void 0!==n.m[e]})))return h();var e})),p=d=function(t){function n(r){a(this,n);var o=i(this,t.call(this,r));return o.retry=function(){o.setState({error:null,loading:!0,timedOut:!1}),m=e(g.loader),o._loadModule()},h(),o.state={error:m.error,pastDelay:!1,timedOut:!1,loading:m.loading,loaded:m.loaded},o}return o(n,t),n.preload=function(){return h()},n.prototype.componentWillMount=function(){this._mounted=!0,this._loadModule()},n.prototype._loadModule=function(){var e=this;if(this.context.loadable&&Array.isArray(g.modules)&&g.modules.forEach((function(t){e.context.loadable.report(t)})),m.loading){"number"==typeof g.delay&&(0===g.delay?this.setState({pastDelay:!0}):this._delay=setTimeout((function(){e.setState({pastDelay:!0})}),g.delay)),"number"==typeof g.timeout&&(this._timeout=setTimeout((function(){e.setState({timedOut:!0})}),g.timeout));var t=function(){e._mounted&&(e.setState({error:m.error,loaded:m.loaded,loading:m.loading}),e._clearTimeouts())};m.promise.then((function(){t()})).catch((function(e){t()}))}},n.prototype.componentWillUnmount=function(){this._mounted=!1,this._clearTimeouts()},n.prototype._clearTimeouts=function(){clearTimeout(this._delay),clearTimeout(this._timeout)},n.prototype.render=function(){return this.state.loading||this.state.error?s.createElement(g.loading,{isLoading:this.state.loading,pastDelay:this.state.pastDelay,timedOut:this.state.timedOut,error:this.state.error,retry:this.retry}):this.state.loaded?g.render(this.state.loaded,this.props):null},n}(s.Component),d.contextTypes={loadable:c.shape({report:c.func.isRequired})},p}function m(e){return g(d,e)}m.Map=function(e){if("function"!=typeof e.render)throw new Error("LoadableMap requires a `render(loaded, props)` function");return g(p,e)};var h=function(e){function t(){return a(this,t),i(this,e.apply(this,arguments))}return o(t,e),t.prototype.getChildContext=function(){return{loadable:{report:this.props.report}}},t.prototype.render=function(){return s.Children.only(this.props.children)},t}(s.Component);function y(e){for(var t=[];e.length;){var n=e.pop();t.push(n())}return Promise.all(t).then((function(){if(e.length)return y(e)}))}h.propTypes={report:c.func.isRequired},h.childContextTypes={loadable:c.shape({report:c.func.isRequired}).isRequired},m.Capture=h,m.preloadAll=function(){return new Promise((function(e,t){y(l).then(e,t)}))},m.preloadReady=function(){return new Promise((function(e,t){y(u).then(e,e)}))},e.exports=m},EbDI:function(e,t){e.exports=function(e){if("undefined"!=typeof Symbol&&Symbol.iterator in Object(e))return Array.from(e)},e.exports.default=e.exports,e.exports.__esModule=!0},Enzk:function(e,t,n){"use strict";var r=n("284h"),a=n("TqRt");t.__esModule=!0,t.ScrollHandler=t.ScrollContext=void 0;var i=a(n("PJYZ")),o=a(n("VbXa")),s=r(n("q1tI")),c=a(n("17x9")),l=n("/hTd"),u=s.createContext(new l.SessionStorage);t.ScrollContext=u,u.displayName="GatsbyScrollContext";var d=function(e){function t(){for(var t,n=arguments.length,r=new Array(n),a=0;at.score?-1:e.index-t.index}))},h=function(e){return e.replace(/(^\/+|\/+$)/g,"").split("/")},y=function(e){for(var t=arguments.length,n=Array(t>1?t-1:0),r=1;r0})))&&n.length>0?"?"+n.join("&"):"")},b=["uri","path"],A=function(e,t){var n=Object.keys(e);return n.length===Object.keys(t).length&&n.every((function(n){return t.hasOwnProperty(n)&&e[n]===t[n]}))}},LeKB:function(e,t,n){e.exports=[{plugin:n("gSxY"),options:{plugins:[],component:"/home/t42/Documents/programming/Projects/OT_Guide/IL-2 Guide/src/templates/docs.js"}},{plugin:n("BOnt"),options:{plugins:[]}},{plugin:n("flL/"),options:{plugins:[],gatsbyRemarkPlugins:[{resolve:"gatsby-remark-images",options:{maxWidth:1035,sizeByPixelDensity:!0}},{resolve:"gatsby-remark-katex",options:{strict:"ignore"}},{resolve:"gatsby-remark-copy-linked-files"},{resolve:"gatsby-remark-acronyms",options:{acronyms:{"2Ltr":"2-Letter",Blk:"Block",Det:"Detachment","Stan/Eval":"Standardization and Evaluation","3DELRR":"Three Dimensional Expeditionary Long Range Radar","3PS":"Third Party Source",AAS:"Advisory and Assistance Services",A3M:"Air Force and Army Anti-Jam Modem",AA:"Adversarial Assessment",AAIP:"Aircraft Availability Improvement Program",AAR:"After-Action Review / Report",AARGM:"Advanced Anti-Radiation Guided Missile",AARI:"Air-to-air Range Infrastructure",ABSD:"Airborne Strategic Deterrence",AC:"Alternating Current",ACAT:"Acquisition Category",ACC:"Air Combat Command",ACCM:"Alternative Compensatory Control Measure",ACE:"Acquisition Center of Excellence",ACES:"Automated Civil Engineer System",ACPAT:"Air Force C4I Program Assessment Tool",ACPINS:"Automated Computer Program Identification Number System",ACPO:"Acquisition Chief Process Office",ACTD:"Advanced Concept Technology Demonstration",ACWP:"Actual Cost Work Performed",ADM:"Acquisition Decision Memorandum",ADS:"Advanced Distributed Simulation",AEC:"United States Army Evaluation Center",AECO:"Advance Engineering Change Order",AECS:"Advanced Entry Control System OR AFOTEC Electronic Coordination System",AEF:"Air and Space Expeditionary Force",AEHF:"Advanced Extremely High Frequency",AEP:"Accrued Expenditures Paid",AESO:"Advance Engineering Supplemental Order",AETC:"Air Education and Training Command",AETF:"Army Evaluation Task Force",AEU:"Accrued Expenditures Unpaid","AF GCIC":"Air Force Global Cyberspace Integration Center",AFMOASP:"Air Force Management and Oversight of Acquisition Services Process",AF:"(US) Air Force","AF/A10":"Assistant Chief of Staff for Strategic Deterrence and Nuclear Integration","AF/A2":"Deputy Chief of Staff, Intelligence, Surveillance and Reconnaissance","AF/A3/5":"Deputy Chief of Staff, Operations, Plans, and Requirements","AF/A4/7":"Deputy Chief of Staff, Logistics, Installations, and Mission Support","AF/A5/8":"HQ AF, Strategic Plans and Programs","AF/A5R":"Air Force Requirements Office","AF/A6":"Chief of Warfighting Integration and Chief Information Officer (CIO)","AF/A8":"Headquarters, Air Force Strategic Plans and Programs","AF/CC":"Chief of Staff, United States Air Force","AF/CV":"Vice Chief of Staff, United States Air Force","AF/SE":"Air Force Chief of Safety","AF/TE":"Headquarters Air Force Test and Evaluation Directorate",AFAE:"Air Force Acquisition Executive",AFAMS:"Air Force Agency for Modeling and Simulation",AFB:"Air Force Base",AFC2IC:"Air Force Command & Control Integration Center",AFC2ISRC:"Air Force Command and Control and Intelligence, Surveillance, and Reconnaissance Center (disestablished)",AFCA:"Air Force Communications Agency",AFCAA:"Air Force Cost Analysis Agency",AFCAP:"Air Force Certification and Accreditation Program",AFCD:"Air Force Capabilities Document",AFCEC:"Air Force Civil Engineer Center",AFCESA:"Air Force Civil Engineer Support Agency",AFDD:"Air Force Doctrine Document",AFDPO:"Air Force Departmental Publishing Office","AF-EA":"Air Force Enterprise Architecture",AFEE:"Air Force Element of Expense",AFEWES:"Air Force Electronic Warfare Simulator",AFFARS:"Air Force Federal Acquisition Regulation Supplement",AFFMA:"Air Force Frequency Management Agency",AFGK:"Air Force Gatekeeper",AFGLSC:"Air Force Global Logistics Support Center",AFGSC:"Air Force Global Strike Command",AFI:"Air Force Instruction",AFICE:"Air Force Integrated Collaborative Environment",AFIOC:"Air Force Information Operations Center",AFIPPS:"Air Force Integrated Personnel and Pay System",AFIT:"Air Force Institute of Technology",AFIWC:"Air Force Information Warfare Center (disestablished)",AFJO:"Air Force Joint Test Program Office",AFKN:"Air Force Knowledge Now",AFL2P:"Air Force Lessons Learned Program",AFLCMC:"Air Force Life Cycle Management Center",AFLIRP:"Air Force Lesson Issue Resolution Program",AFMAN:"Air Force Manual",AFMC:"Air Force Material Command",AFMD:"Air Force Mission Directive",AFMETCAL:"Air Force Metrology and Calibration",AFMSRR:"Air Force Modeling and Simulation Resource Repository",AFNET:"Air Force Network",AFNIC:"Air Force Network Integration Center","AF-NNSA":"Air Force-National Nuclear Security Administration",AFNWC:"Air Force Nuclear Weapons Center",AFOSH:"Air Force Occupational and Environmental Safety, Fire Protection, and Health OR Air Force Office of Safety and Health",AFOSI:"Air Force Office of Special Investigations",AFOTEC:"Air Force Operational Test and Evaluation Center","AFOTEC/A-1":"Manpower and Personnel Directorate","AFOTEC/A-1T":"Training Division","AFOTEC/A-1W":"Manpower and Personnel (Operations) Division","AFOTEC/A-2/9":"Intelligence, Analyses, and Assessments Directorate","AFOTEC/A-2N":"Intelligence Division","AFOTEC/A-3":"Operations Directorate","AFOTEC/A-3C":"Cyber Strategic Evaluation Division","AFOTEC/A-3E":"Operations Mission Support Division","AFOTEC/A-3F":"Test Operations Division","AFOTEC/A-3I":"Cyberspace Test Division","AFOTEC/A-3O":"Test Design Operations Division","AFOTEC/A-3Z":"Special Access Programs Division","AFOTEC/A-4/7":"Installations and Mission Support Directorate","AFOTEC/A-4F":"Logistics and Facilities Management Division","AFOTEC/A-5/8":"Plans and Programs Directorate","AFOTEC/A-5R":"Test Infrastructure Division","AFOTEC/A-6":"Communications and Information Directorate","AFOTEC/A-6O":"Cyber Operations Division","AFOTEC/A-6X":"Plans and Resources Division","AFOTEC/A-6Z":"Special Access Programs Information Technology Division","AFOTEC/A-7K":"Contracting Division","AFOTEC/A-7R":"Financial Resources Division","AFOTEC/A-8P":"Programming Division","AFOTEC/A-8R":"Long Range Investments Division","AFOTEC/A-8X":"Strategic Plans and Policy Division","AFOTEC/A-9A":"Analysis and Assessments Division","AFOTEC/A-9I":"Analysis Foundation and Integration Division","AFOTEC/A-9X":"Methods and Tools Division","AFOTEC/CA":"Technical Advisor","AFOTEC/CC":"AFOTEC Commander","AFOTEC/CCE":"Executive Officer","AFOTEC/CCJ":"Graphics","AFOTEC/CCP":"Protocol","AFOTEC/CCS":"Secretary","AFOTEC/CCX":"Commander’s Action Group","AFOTEC/CEM":"Chief Enlisted Manager","AFOTEC/CS":"Command Staff","AFOTEC/CV":"Vice Commander","AFOTEC/DS":"Director of Staff","AFOTEC/ED":"Executive Director","AFOTEC/HO":"History Office","AFOTEC/IGI":"Inspector General (Inspections)","AFOTEC/IP":"Information Protection","AFOTEC/LC":"Legal Council","AFOTEC/PA":"Public Affairs","AFOTEC/SE":"Safety",AFOTECI:"AFOTEC Instruction",AFOTECPAM:"AFOTEC Pamphlet",AFOTTP:"Air Force Operational Tactics, Techniques, and Procedures",AFPAM:"Air Force Pamphlet",AFPD:"Air Force Policy Directive","AFPEO/CM":"Air Force Program Executive Officer/Combat and Mission Support",AFRB:"Air Force Review Board",AFRC:"Air Force Reserve Command","AFRIMS RDS":"Air Force Information Management System Records Disposition Schedule",AFRIMS:"Air Force Records Information Management System",AFRL:"Air Force Research Laboratory",AFROC:"Air Force Requirements Oversight Council",AFROCC:"Air Force Requirements for Operational Capabilities Council",AFROCM:"Air Force Requirements Oversight Council Memorandum",AFRRG:"Air Force Requirements Review Group",AFSC:"Air Force Specialty Code",AFSEO:"Air Force SEEK EAGLE Office",AFSFC:"Air Force Security Forces Center",AFSIT:"Air Force System Interoperability Testing",AFSOC:"Air Force Special Operations Command",AFSPC:"Air Force Space Command",AFSSI:"Air Force Systems Security Instruction",AFTC:"Air Force Test Center",AGL:"Above Ground Level",AGM:"Air Ground Missile",AGR:"Active Guard and Reserve",AIM:"Air Intercept Missile","AIM-120 Adv EPIP":"AIM-120C Advanced Electronic Protection Improvement Program","AIM 120D SIP-3":"AIM-120D System Improvement Program",AIP:"Aircraft Information Program",AIR:"Acquisition Information Repository",AIS:"Automated Information Systems",AISR:"Airborne Intelligence, Surveillance, and Reconnaissance",AIT:"Automatic Identification Technology",ALC:"Air Logistics Center",ALCM:"Air Launched Cruise Missile","ALCS-R":"Airborne Launch Control System Replacement",ALDT:"Administrative and Logistics Delay",ALIS:"Autonomic Logistics Information System (F-35)",AMARG:"Aerospace Maintenance and Regeneration Group",AMAS:"AFOTEC Mission Applications Suite",AMC:"Air Mobility Command",AME:"Alternate Mission Equipment",AML:"Acquisition Master List",AMP:"C-130 Avionics Modernization Program",AMSAA:"Army Materiel Systems Analysis Activity","AN/PRC":"Army Navy/Portable Radio Communication",ANG:"Air National Guard",AO:"Area of Operations or Authorizing Official or Action Officer",Ao:"Operational Availability",AoA:"Analysis of Alternatives","AOC WS":"Air Operations Center Weapon System",AOTR:"Assessment of Operational Test Readiness",APA:"Additional Performance Attribute",APAT:"Acquisition Process Architecture Team",APB:"Acquisition Program Baseline",APDP:"Acquisition Professional Development Program",APKWS:"Advanced Precision Kill Weapon System",APM:"Acquisition Process Model",APML:"Acquisition Program Master List",APPG:"Annual Planning and Programming Guidance",APSR:"Accountable Property Systems of Record",APT:"Advanced Pilot Training",APUC:"Average Unit Procurement Cost",AR:"Analysis and Reporting Toolset OR Army Regulation",ARM:"Anti-Radiation Missile",ARRW:"Air-Launched Rapid Response Weapon",ART:"Adaptive-Relevant Test",ARTS:"Advanced Radar Threat System","AS Tool Kit":"Acquisition and Sustainment Tool Kit",AS:"Acquisition Strategy",ASACMS:"Advanced Situational Awareness Countermeasures System",ASACoE:"Application Software Assurance Center of Excellence",ASAF:"Assistant Secretary of the Air Force",ASD:"Acquisition Strategy Development OR Agile Software Development OR Assist Sec of Defense",ASDNII:"Assistant Secretary of Defense (Network and Information Integration",ASIP:"Airborne Signals Intelligence Payload OR Aircraft Structural Integrity Program",ASP:"Acquisition Strategy Panel",ASR:"Acquisition and Sustainment Reviews OR Alternative Systems Review",ASTK:"Acquisition Sustainment Tool Kit",ASuW:"Anti-Surface Warfare",AT:"Anti-Tamper","AT&L":"Acquisition, Technology, and Logistics",ATAPPS:"Automated Time Attendance and Production System",ATCALS:"Air Traffic Control and Landing Systems",ATD:"Advanced Technology Demonstration (or Development)",ATE:"Automatic Test Equipment",ATEC:"Army Test and Evaluation Command",ATO:"Air Tasking Order OR Authority to Operate",ATOS:"Automated Technical Orders System",ATPA:"AFOTEC Test Program Application","ATP-SE":"Advanced Targeting Pod-Sensor Enhancement",ATS:"Automatic Test System",ATTIC:"Analyst Training and Technical Information Center",AUTL:"Army Universal Task List",AV:"All Viewpoint",AVIP:"Aviation Integrity Program",AVPOL:"Aviation Petroleum, Oil, and Lubricants",AWACS:"Airborne Warning and Control System",AWBS:"Air Warfare Battle Shaping",AWIP:"Advanced Weapons Integration Program","B-2 DMS":"Defensive Management System","B-2 EHF SATCOM":"Extremely High Frequency Satellite Communications","B-52 CERP":"B-52 Commercial Engine Replacement Program","B-52 RMP":"B-52 Radar Modernization Program","B61 LEP":"B61 Life Extension Program",BAA:"Buy American Act",BBP:"Bullet Background Paper",BC:"Business Case",BCA:"Business Case Analysis",BCL:"Business Capability Lifecycle",BCS:"Baseline Comparison System","BCS-F":"Battle Control System-Fixed",BDA:"Big Data Analytics; Bomb Damage Assessment",BDRSK:"Battle Damage Repair Spares Kit",BEA:"Business Enterprise Architecture",BES:"Budget Estimate Submission",BFT:"Blue Force Tracking",BISS:"Base and Installation Security System","BLOS C2":"Beyond-Line-of-Sight Command and Control",BLOS:"Beyond Line of Sight",BLU:"Bomb, Live Unit",BMC2:"Battle Management Command and Control Communications",BMD:"Ballistic Missile Defense",BMDS:"Ballistic Missile Defense System",BOS:"Base Operating Support",BPAC:"Budget Program Activity Code",BRU:"Bomb Release Units",BU:"Block Update","C&A":"Certification and Accreditation","C&L":"Capabilities and Limitations","C&LR":"Capabilities and Limitations Report",C2:"Command and Control",C2AOS:"Command and Control Air Operations Suite",C2BMC:"Command, Control, Battle Management, and Communications",C2D2:"Continuous Capability Development and Delivery",C2IS:"Command and Control Information Services",C4:"Command, Control, Communications, and Computers",C4I:"Command, Control, Communications, Computers, and Intelligence",C4ISP:"Command, Control, Communication, Computers, and Intelligence Support Plan",C4ISR:"Cmd, Control, Comm, Computers, Intel, Surveillance, and Reconnaissance",CA:"Command Technical Advisor OR Contract Award OR Criticality Analysis",CAC:"Common Access Card ",CAD:"Computer-Aided Design (or Drafting)",CAE:"Component Acquisition Executive",CAFTOP:"Comprehensive Air Force Technical Order Plan",CAG:"Commander’s Action Group",CAGE:"Commercial and Government Entity",CAIG:"Cost Analysis Improvement Group",CALS:"Common Analytical Laboratory System",CAM:"Centralized Asset Management",CAOC:"Coalition Air Operations Center",CAP:"Contractor Acquired Property OR Critical Acquisition Position",CAPCO:"Controlled Access Program Coordinating Office",CAPE:"Cost Assessment and Program Evaluation",CAPES:"F-16 Combat Avionics Programmed Extension Suite",CARD:"Cost Analysis Requirements Description",CASS:"Close Air Support System",CAT:"Category",CBA:"Capabilities-Based Assessment",CBDP:"Chemical and Biological Defense Program",CBM:"Condition-Based Maintenance Plus",CBP:"Capability-Based Planning",CBR:"Chemical, Biological, and Radiological",CBRD:"Capabilities-Based Requirements Document",CBRN:"Chemical, Biological, Radiological and Nuclear",CC:"Commander OR Critical Component",CCA:"Clinger-Cohen Act OR Component Cost Analysis",CCaR:"Comprehensive Cost and Requirement System",CCCA:"Common Core Compliance Area",CCD:"Combat Capability Document",CCDR:"Combatant Commander",CCJO:"Capstone Concept for Joint Operations",CCMD:"Combatant Command",CCP:"Command Control Points",CCPE:"Corrosion Control Program Executive",CCR:"Call Completion Rate","C-CS":"Counter-Concealment Sensing",CCT:"Capability Collaboration Teams",CCTD:"Concept Characterization and Technical Description",CCX:"Commander’s Action Group Office Symbol",CD:"Capability Director (or Directorate) OR Deputy Commander",CDA:"Current Design Activity",CDD:"Capability Development Document",CDP:"Capability Definition Package",CDR:"Critical Design Review",CDRL:"Contract Data Requirements List",CDS:"Cross Domain Solution",CDT:"Chief Developmental Tester",CE:"Civil Engineer OR Conducted Emissions",CEP:"Circular Error Probability",CERT:"Certification",CFL:"Core Function Lead",CFLI:"Core Function Lead Integrator",CFMP:"Core Function Master Plan",CFO:"Chief Financial Officer",CFP:"Capabilities Focused Planning",CFR:"Code of Federal Regulations",CFSR:"Contract Funds Status Report",CGA:"Capability Gap Assessment",CGM:"Common GPS Module",CI:"Configuration Item OR Counterintelligence",CICA:"Competition in Contracting Act",CIDAS:"Contamination Indicator Decontamination Assurance System",CIED:"Counter-Improvised Explosive Device",CIMB:"Commander’s Inspection Management Board",CIO:"Chief Information Officer",CIP:"Critical Intelligence Parameter",CIPS:"Cyberspace Infrastructure Planning System",CIR:"Capital Investment Report",CISP:"Counterintelligence Support Plan",CITE:"Center of Industrial and Technical Excellence",CJCS:"Chairman, Joint Chiefs of Staff",CJCSI:"Chairman, Joint Chief of Staff Instruction",CJCSM:"Chairman, Joint Chiefs of Staff Manual",CJR:"COBRA JUDY Replacement",CJTF:"Coalition Joint Task Force",CL:"China Lake OR Civilian Leader OR Continuous Learning",CLIN:"Contract Line Item Number",CLS:"Contractor Logistics Support",CM:"Configuration Management OR Consequence Management OR Constellation Management OR Corrective Maintenance",CMBRE:"Common Munitions BIT Reprogramming Equipment",CMC:"C-5 Core Mission Computer and Weather Radar Program",CML:"Capability-Mission Lattice",CMMI:"Capability Maturity Model Integration",CMP:"Configuration Management Plan",CMRS:"Collaboration and Measurements Requirements Summary",CNA:"Computer Network Attack",CNEO:"Change Notice Engineering Order",CNSSI:"Committee on National Security Systems (CNSS) Instruction",CNWDI:"Critical Nuclear Weapons Design Information",CO:"Contracting Officer",COA:"Course of Action",CoC:"Certificate of Compliance",COCOM:"Combatant Command",COD:"Capability Development Document",COI:"Critical Operational Issue",COLISEUM:"Community On-Line Intelligence System for End Users and Managers",COMAFFOR:"Commander Air Force Forces",COMOPTEVFOR:"Naval Command Operational Test and Evaluation Force",COMSEC:"Communications Security",CoN:"Certificate of Networthiness",CONECT:"B-52 Combat Network Communications Technology",CONEMP:"Concept of Employment",CONOPS:"Concept of Operations",COOP:"Continuity of Operations Plan",COP:"Common Operating Picture",CoP:"Community of Practice",COR:"Contracting Officer’s Representative",CORE:"Critical Operational Issues and Criteria",COTF:"Commander, Operational Test Force (OPTEVFOR)",COTS:"Commercial Off-the-Shelf",COTT:"Combined Operational Test Team",CPA:"Chairman’s Program Assessment",CPAF:"Cost-Plus Award Fee",CPARS:"Contractor Performance Assessment Reporting System",CPCP:"Corrosion Prevention and Control Plan",CPD:"Capability Production Document",CPI:"Crash Position Indicator OR Critical Program Information",CPIF:"Cost Plus Incentive Fee",CPM:"Capability Portfolio Manager",CPR:"Chairman’s Program Recommendation",CR:"Change Request",CR6:"Hexavalent Chromium",CRA:"Continuing Resolution Authority OR Cost Risk Assessment OR Chairman’s Risk Assessment",CRD:"Capabilities Requirements Document ",CRDA:"Cooperative Research and Development Agreement",CRH:"Combat Rescue Helicopter",CRIIS:"Common Range Integrated Instrumentation System",CRISP:"Cross Industry Standard Process for Data Mining",CRM:"Component Resolution Matrix OR Crew Resource Management",CRRA:"Capabilities Review and Risk Assessment",CRS:"Chairman’s Readiness System",CS:"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy",CSA:"Combat Support Agency",CSAF:"Chief of Staff of the Air Force",CSAG:"Consolidated Sustainment Activity Group",CSAR:"Combat Search and Rescue",CSARL:"Combat Search and Rescue Locator",CSB:"Configuration Steering Board",CSCI:"Computer Software Configuration Items",CSE:"Center for Systems Engineering OR Common Support Equipment",CSH:"Common Support Helicopter",CSI:"Critical Safety Item",CSO:"Commodity Strategy Official",CSR:"Critical System Resources",CSS:"Contract Sustainment Support","C-sUAS":"Counter-small Unmanned Aerial Systems",CSWS:"Contractor Supported Weapon System",CT:"Contractor Testing OR Critical Technology",CTA:"Capability Threat Assessments OR Center Test Authority",CTE:"Critical Technology Element",CTEIP:"Central Test & Evaluation Investment Program",CTF:"Combined Task Force",CTIC:"Contractor Technical Information Code",CTM:"Capability Transition Memorandum",CtO:"Certificate to Operate",CTOM:"Centralized Technical Order Management",CTP:"Critical Technical Parameter",CTR:"Capability Transition Review",CUI:"Controlled Unclassified Information",CUMI:"Controlled Unclassified Military Information",CV:"Vice Commander OR Capability Viewpoint",CVI:"AFOTEC Information Protection/SAP Security (office symbol)",CVLSP:"Common Vertical Lift Support Platform",CVPA:"Cooperative Vulnerability and Penetration Assessment",CVW:"Carrier Air Wing",CWI:"Continuous Wave Illuminator",CY:"Calendar Year","D&F":"Determination and Findings","D,ARA":"Director, Acquisition Resources, and Analysis","D/CAPE":"Director, Cost Assessment, and Program Evaluation","D/QT&E":"Development/Qualification Test and Evaluation",DA:"Department of the Army",DAA:"Designated Approval Authority",DAB:"Defense Acquisition Board",DAC:"Designated Acquisition Commander",DACM:"Director, Acquisition Career Management",DAE:"Defense Acquisition Executive",DAES:"Defense Acquisition Executive Summary",DAF:"Department of the Air Force",DAG:"Defense Acquisition Guidebook",DAMIR:"Defense Acquisition Management Information Retrieval",DAO:"Designated Acquisition Officials",DARC:"Deep Space Advanced Radar Concept",DARPA:"Defense Advanced Research Projects Agency",DART:"Data, Acquisition, Recording, and Telemetry OR Deficiency Analysis Ranking Technique",DAS:"Defense Acquisition System",DASD:"Deputy Assistant Secretary of Defense",DATO:"Denial of Authorization to Operate",DAU:"Defense Acquisition University",DAWIA:"Defense Acquisition Workforce Improvement Act",DBC:"Defense Business Council",DBS:"Defense Business Systems",DBSMC:"Defense Business Systems Management Committee",DC:"Derivative Classifier OR Direct Current",DCAA:"Defense Contract Audit Agency",DCAPE:"Director of Cost Assessment and Program Evaluation",DCAPES:"Deliberate and Crisis Action Planning and Execution Segments",DCGS:"Distributed Common Ground System",DCID:"Director of Central Intelligence Directive",DCMA:"Defense Contract Management Agency",DCPDS:"Defense Civilian Personnel Data System",DCR:"DOTMLPF-P Change Recommendation",DCS:"Deputy Chief of Staff","DDNI/M":"Deputy Director of National Intelligence for Management",DDR:"Deputy Director for Requirements OR Dismount Detection Radar","DDT&E":"Director, Developmental Test and Evaluation",DEAD:"Destruction of Enemy Air Defenses",DEAMS:"Defense Enterprise Accounting and Management System",DEF:"Developmental Evaluation Framework",DepSecDef:"Deputy Secretary of Defense","Det/CC":"Detachment Commander",DEW:"Directed Energy Weapons",DEWCB:"Directed Energy Weapons Certification Board",DFARS:"Defense Federal Acquisition Regulation Supplement",DFCN:"Dual Frequency Civil Navigation",DFoS:"Decontamination Family of Systems",DHMSM:"Defense Healthcare Management Systems Modernization",DIA:"Defense Intelligence Agency",DIACAP:"DoD Information Assurance Certification and Accreditation Process",DID:"Data Item Description",DIP:"DIACAP Implementation Plan",DISA:"Defense Information Systems Agency",DISR:"Department of Defense Information Technology Standards Registry",DITSCAP:"Department of Defense Information Technology Security Certification and Accreditation Program",DIV:"Data and Information Viewpoint",DLA:"Defense Logistics Agency",DLR:"Depot-Level Repairable",DM:"Data Mining",DMAP:"Data Management and Analysis Plan",DMAWG:"Depot Maintenance Activation Working Group",DMEA:"Defense Microelectronics Activity",DMI:"Depot Maintenance Interservice","DMIX JLV":"Defense Medical Information Exchange Joint Legacy Viewer",DMS:"Defensive Management System OR Diminishing Manufacturing Sources",DMSMS:"Diminishing Manufacturing Sources Material Shortages",DNAD:"Domestic Non-Availability Determination",DNI:"Director of National Intelligence",DoD:"Department of Defense",DODAAC:"Department of Defense Activity Code",DODD:"Department of Defense Directive",DODI:"Department of Defense Instruction",DODIN:"Department of Defense Information Network",DODIPP:"Department of Defense Intelligence Production Program",DODISS:"Department of Defense Index of Specifications and Standards",DODM:"Department of Defense Manual",DOE:"Department of Energy OR Design of Experiments",DoN:"Department of the Navy","DOT&E":"Director of Operational Test and Evaluation","DOTMLPF-P":"Doctrine, Organization, Training, materiel, Leadership Policy and Education, Personnel, Facilities, and Policy",DP:"Development Planning",DPAP:"Director of Procurement and Acquisition Policy",DPAS:"Defense Priorities and Allocation System",DPEM:"Depot Purchased Equipment Maintenance",DPG:"Defense Planning Guidance",DPGS:"Data Processing Ground Station",DPPG:"Defense Planning and Programming Guidance","DR SKO":"Dismounted Reconnaissance Sets, Kits, and Outfits",DR:"Deficiency Report",DRAGON:"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation",DRB:"Deficiency Review Board",DREN:"Defense Research Engineering Network",DRI:"Data Referential Integrity","DRI&R":"Deficiency Reporting, Investigation and Resolution",DRM:"DRAGON Requirements Memorandum",DRMO:"Defense Reutilization Marketing Office",DRR:"Design Readiness Review",DRU:"Direct Reporting Unit","DS&TI":"Designated Science and Technology Information",DSA:"Direct Sales Agreement",DSC:"Decision Support Question",DSCA:"Defense Security Cooperation Agency",DSM:"Development System Manager OR Digital System Model",DSOR:"Depot Source of Repair","DSOR-EM":"Depot Source of Repair-Electronic Manager",DT:"Developmental Test","DT&E":"Developmental Test and Evaluation",DTD:"Data Type Definition",DTIC:"Defense Technical Information Center",DTM:"Directive-Type Memorandum",DTP:"Detailed Test Plan",DUSD:"Deputy Under Secretary of Defense","E&S":"Effectiveness and Suitability","E-3 DRAGON":"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation",E3:"Electromagnetic Environmental Effects",EA:"Economic Analysis OR Electronic Attack OR Evolutionary Acquisition OR Executing Authority",EAC:"Estimate at Completion",ECD:"Estimated Completion Date",ECM:"Electronic Countermeasures",ECN:"Enclave Control Node",ECSS:"Expeditionary Combat Support System",ED:"Executive Director",EDGC:"Engineering Data Guidance Conference",EDM:"Engineering Data Manager (or Management) OR Engineering Development Model",EDSC:"Engineering Data Service Center",EEC:"Enterprise Engineering Center",EEIC:"Element of Expense Investment Code",EFF:"Essential Function Failure",EHF:"Extremely High Frequency",EIAP:"Environment Impact Analysis Process",EIEMA:"Enterprise Information Environment Mission Area",EIS:"Early Influence Strategy",EIT:"Early Influence Team",EITDR:"Enterprise Information Technology Data Repository",EKMS:"Electronic Key Management System",ELA:"Elevated Level of Assurance",ELT:"Emergency Locator Transmitter",EMA:"Expectation Management Agreement",EMC:"Electromagnetic Compatibility","EMC/EMI":"Electromagnetic Compatibility/Electromagnetic Interference",EMD:"Engineering and Manufacturing Development",EMI:"Electromagnetic Interference",EMP:"Electromagnetic Pulse",EMSEC:"Emission Security",EMV:"Electromagnetic Vulnerability",ENSIP:"Engine Structural Integrity Program",EO:"Electro-Optical OR Executive Order OR Engineering Order",EOA:"Early Operational Assessment",EOD:"Explosive Ordnance Disposal",EP:"Electronic Protection",EPAWSS:"F-15 Eagle Passive and Active Warning and Survivability System",EPG:"Electronic Proving Ground",EPIP:"AIM-120C Advanced Electronic Protection Improvement Program",EPS:"Enhanced Polar System",EPVD:"Electromagnetically Enhanced Physical Vapor Deposition (gun tube coating",ERF:"Electronic Remote Fill",ERM:"Environmental Resources Manager",ESC:"Electromagnetic Spectrum Certification OR Evaluation Summary Chart",ESOH:"Environment, Safety, and Occupational Health",ESOHC:"Environment, Safety, and Occupational Health Council",ESOHCB:"Environment, Safety, and Occupational Health Certification Board","ESOH-MS":"Environment, Safety, and Occupational Health Management System",ESP:"Emergency and Special Program",ESS:"Effectiveness, Suitability, and Survivability OR Evolved Strategic Satellite Communications",ESW:"Electronic Systems Wing OR Evaluation Summary Worksheet",ETIMS:"Enhanced Technical Information Management System",ETM:"Electronic Technical Manual",ETO:"Executing Test Organization",EU:"Engineering Units",EUC:"End Use Certificate",EV:"Evaluation View",EVM:"Earned Value Management","EVM-CR":"Earned Value Management-Central Repository",EVMS:"Earned Value Management System",EW:"Electronic Warfare",EWIIP:"Electronic Warfare Infrastructure Improvement Program",EWIR:"Electronic Warfare Integrated Reprogramming",EWSR:"Executive Weapons System Review","F-15 EPAWSS":"F-15 Eagle Passive and Active Warning and Survivability System","F-15 IRST":"F-15 Infrared Search and Track System",F3I:"Form, Fit, Function, or Interface",FAA:"Federal Aviation Administration OR Functional Area Analysis","FAB-T":"Family of Advanced Beyond Line Of Sight Terminals","FAC-A":"Forward Air Controller-Airborne",FAR:"Federal Acquisition Regulation",FARM:"Functional Area Records Manager",FAT:"First Article Test",FCA:"Functional Configuration Audit",FCB:"Functional Capabilities Board",FCC:"Flagship Capability Concepts",FCT:"Foreign Comparative Test",FD:"Fielding Decision","FD/SC":"Failure Definition/Scoring Criteria",FDB:"Final Evaluation and Decision Brief",FDD:"Full Deployment Decision",FDDR:"Full Deployment Decision Review",FDE:"Force Development Evaluation",FDO:"Fee Determining Official",FDR:"Final (or Formal) Design Review",FET:"Force Element Terminal",FFP:"Firm Fixed Price",FFRDC:"Federally Funded Research and Development Centers",FFT:"Friendly Force Tracking",FH:"Flying Hours",FIAR:"Financial Improvement and Audit Readiness",FIP:"Federal Information Processing",FISCAM:"Federal Information System Controls Audit Manual",FISMA:"Federal Information Security Management Act of 2002",FM:"Financial Management OR Frequency Modulation OR Functional Manager",FMC:"Fully Mission Capable",FMECA:"Failure Mode, Effects, and Criticality Analysis",FMM:"Flight Manual Manager",FMP:"Flight Manuals Program OR Foreign Materiel Program",FMR:"Financial Management Regulation",FMRS:"Financial Management Regulation System",FMS:"Foreign Military Sales","FMU-139 D/B":"Fuze Module Unit-139",FNA:"Functional Needs Analysis",FOA:"Field Operating Agency",FOB:"Forward Operating Base",FOC:"Full Operational Capability",FOIA:"Freedom of Information Act",FoM:"Follow-on Modernization",FORGE:"Future Operationally Resilient Ground Evolution",FoS:"Family of Systems","FOT&E":"Follow-on Operational Test and Evaluation",FOU:"Full Operational Utility",FOUO:"For Official Use Only",FOV:"Field of View",FPAF:"Fixed-Price with Award Fee",FPD:"Follow-on Production Decision","FPDS-NG":"Federal Procurement data System-Next Generation",FPIF:"Fixed-Price Incentive",FPR:"Final Pricing Report OR Final Proposal Revision",FPRA:"Forward Price Rate Agreements",FQR:"Formal Qualification Review",FRD:"Formerly Restricted Data",FRP:"Full-Rate Production","FRP/FD":"Full-Rate Production or Full Deployment",FRPDR:"Full Rate Production Decision Review",FRRB:"Functional Requirements Review Board",FSA:"Functional Solution Analysis",FSC:"Federal Supply Classification",FSR:"Field Service Representative",FTE:"Full Time Equivalent",FTX:"Field Training Exercise",FY:"Fiscal Year",FYDP:"Future Years Defense Program","G&A":"General and Administrative (Expense)",GAO:"Government Accountability Office",GAT:"Government Analysis Tool",GBS:"Global Broadcast Service",GBSD:"Ground Based Strategic Deterrent",GBU:"Guided Bomb Unit",GCIC:"Global Cyberspace Integration Center",GCS:"Ground Control Stations","GCSS-AF":"Global Combat Support System – Air Force",GDT:"Government Development Test",GEF:"Guidance for the Employment of the Force",GEO:"Geosynchronous Earth Orbit",GFE:"Government Furnished Equipment",GFI:"Government Furnished Information",GFM:"Global Force Management",GFP:"Government Furnished Property","GH GSMP":"Global Hawk Ground Segment Modernization Program",GIDEP:"Government Industry Data Exchange Program",GIG:"Global Information Grid",GLSC:"Global Logistics Support Center",GMT:"Ground Movement Terrain Radar",GMTI:"Ground Moving Target Indicator",GO:"General Officer","GO/SES":"General Officer/Senior Executive Service",GOCO:"Government Owned Contractor Operated",GOSG:"General Officer Steering Group",GOTS:"Government Off-the-Shelf",GPA:"GPS Pulse-per-Second Adapter",GPC:"Government Purchase Card",GPD:"General Purpose Decontaminant Program",GPLR:"Government Purpose License Rights",GPR:"Government Purpose Rights","GPS III COps":"Global Positioning System III Contingency Operations","GPS MCEU":"Global Positioning System M-Code Early Use","GPS MGUE":"Military GPS User Equipment","GPS OCX":"GPS Next Generation Operational Control System",GPS:"Global Positioning System",GS:"General Schedule",GSA:"Government Services Administration",GSMP:"Ground Segment Modernization Program","GTG-F":"Global Information Grid Technical Guidance Federation","G-TSCMIS":"Global Theater Security Cooperative Management Information System",GTV:"Guided Test Vehicle",HAF:"Headquarters Air Force",HAFMD:"Headquarters Air Force Mission Directive",HAMS:"Hardness Assurance, Maintenance, and Surveillance",HARPOON:"(AGM-84-Fixed Wing; RGM-Surface Ships; UGM-Submarine Launched)",HCA:"Head of Contracting Activity (or Agency)",HCI:"Human-Computer Interactions",HCSP:"Human Capital Strategic Plan",HCSW:"Hypersonic Conventional Strike Weapon",HDF:"Hierarchical Data Format",HEMP:"High-Altitude Electromagnetic Pulse",HERF:"Hazards of Electromagnetic Radiation to Volatile Material",HERO:"Hazards of Electromagnetic Radiation to Ordinance",HERP:"Hazards of Electromagnetic Radiation to Personnel",HFE:"Human Factors Engineering",HITL:"Hardware in the Loop","HM/HS":"Hardness Maintenance / Hardness Surveillance",HMS:"Handheld, Manpack, and Small Form Fit",HO:"HQ AFOTEC History Office",HOI:"Headquarters Operating Instruction",HPT:"High Performance Team",HQ:"Headquarters",HSI:"Human Systems Integration",HSN:"High Speed Network",HSP:"Health and Safety Plan",HTM:"Hard Target Munitions",HTVSF:"Hard Target Void Sensing Fuze",HwA:"Hardware Assurance",IA:"Information Assurance (replaced by “cybersecurity”)",IAC:"International Armaments Cooperation",IAD:"Integrated Air Defense",IADS:"Integrated Air Defense System",IAE:"Integrated Aircrew Ensemble",IAMD:"Integrated Air and Missile Defense",IATO:"Interim Authorization to Operate",IATT:"Interim Authority to Test or Authorization to Test",IAVA:"Information Assurance Vulnerability Alert",IAW:"In Accordance With",IB:"Involvement Briefing",IBA:"Individual Body Armor",IBBP:"Involvement Bullet Background Paper",IBCT:"Infantry Brigade Combat Team",IBDC2:"Integrated Base Defense Command and Control",IBDSS:"Integrated Base Defense Security System",IBR:"Integrated Baseline Review",IBS:"Integrated Broadcast Service",IC:"Intelligence Community",ICADS:"Individual Combat Aircrew Display System",ICBM:"Intercontinental Ballistic Missile",ICCR:"Intelligence Community Capability Requirements",ICD:"Initial Capabilities Document OR Interface Control Document",iCDD:"initial Capability Development Document",ICE:"Independent Cost Estimate",ICEP:"Information Certification Evaluation Plan",ICM:"Interim Contractor Support",ICP:"Inventory Control Point",ICS:"Interim Contract Support",ICT:"Integrated Concept Team",ID:"Identification","ID/IQ":"Indefinite Delivery/Indefinite Quantity",IDE:"Integrated Data Environment",IDL:"Indentured Data List",IDRL:"Integrated Data Requirements List",IEB:"Initial Evaluation Briefing",IED:"Improvised Explosive Device",iEHR:"Integrated Electronic Health Records",IER:"Information Exchange Requirements",IETM:"Interactive Electronic Technical Manual",IFC:"Integrated Functional Capability",IFDL:"Intraflight Datalink",IFM:"Intelligence in Force Modernization",IFTU:"In-Flight Targeting Update",IGF:"Inherently Governmental Function",IITD:"Initial Integrated Test Design",IL:"Involvement Letter",ILCM:"Integrated Life Cycle Management",ILS:"Instrument Landing System OR Integrated Logistics Support",ILSP:"Integrated Logistics Support Plan",IM:"Insensitive Munitions",IMC:"Instrument Meteorological Conditions",IMD:"Intelligence Mission Data",IMDS:"Integrated Maintenance Data System",IMET:"International Military Education and Training",IMP:"Integrated Master Plan",IMS:"Integrated Master Schedule",IMT:"Information Management Tool",IMTP:"Integrated Master Test Plan",INC:"Increment",INS:"Inertial Navigation System",IO:"Information Operations",IOC:"Initial Operational Capability",IOT:"Initial Operational Test","IOT&E":"Initial Operational Test and Evaluation",IP:"Information Protection OR Initial Point OR Intellectual Property OR Internet Protocol",IPA:"Independent Program Assessment",IPAT:"Independent Program Assessment Team",IPL:"Integrated Priority List",IPMR:"Independent Program Management Report",IPR:"In-Process Review",IPS:"Integrated Program Summary OR Intellectual Property Strategy",IPSS:"Initial Provisioning Performance Specifications",IPT:"Integrated Product Team",IR:"Infrared",IRAD:"Independent Research and Development",IRB:"Intelligence Resources Board OR Investment Review Board",IRCM:"Infrared Countermeasures",IRSS:"Information and Resource Support System",IRST:"Infrared Search and Track System","IS CDD":"Information System Capability Development Document","IS ICD":"Information System Initial Capabilities Document",IS:"Information System",ISA:"International Standardization Agreement",ISACA:"Information Systems Audit and Control Association",ISO:"International Standards Organization",ISOO:"Information Security Oversight Office",ISP:"Information Support Plan",ISPAN:"Integrated Strategic Planning and Analysis Network",ISR:"Intelligence, Surveillance, and Reconnaissance OR Interim Summary Report",ISSM:"Information System Security Manager",ISWG:"Intelligence Support Working Group","IT Lean":"Information Technology Lean",IT:"Information Technology OR Integrated Testing","IT&E":"Integrated Test and Evaluation","IT/NSS":"Information Technology/National Security System",ITA:"Interface Test Adapter",ITAB:"Information Technology Acquisition Board",ITC:"Integrated Test Concept",ITD:"Initial Test Design",ITEA:"Initial Threat Environment Assessment",ITO:"Initial Tasking Order",ITP:"Integrated Test Plan",ITT:"Integrated Test Team",IUID:"Item Unique Identification",IUS:"Internal Use Software",IW:"Information Warfare",IWBU:"Internal Weapons Bay Upgrade",IWSM:"Integrated Weapons System Management","J&A":"Justification and Approval","J-8/DDR":"Joint Staff J-8, Deputy Director for Requirements","J-8/SAPCOORD":"Joint Staff J-8, Special Access Program Coordinator",JAFAN:"Joint Air Force Army Navy",JAGM:"Joint Air-to-Ground Missile",JALN:"Joint Aerial Layered Network",JASP:"Joint Aircraft Survivability Program",JASSM:"Joint Air-to-Surface Standoff Missile",JAWS:"Joint Avionics Workstation",JBADS:"Joint Biological Agent Decontamination System",JBTDS:"Joint Biological Tactical Detection System",JCA:"Joint Capability Area",JCAAMP:"Joint Improvised Explosive Device Defeat Capability Approval and Acquisition Management Process",JCALS:"Joint Computer-Aided Acquisition and Logistic Support",JCB:"Joint Capabilities Board",JCC2:"Joint Cyber Command and Control",JCCA:"Joint Combat Capability Assessment",JCD:"Joint Capabilities Document",JCIDS:"Joint Capabilities Integration and Development System",JCPATE:"Joint C4I Program Assessment Tool-Empowered",JCREW:"Joint Counter Radio-Controlled Improvised Explosive Device Electronic Warfare",JCS:"Joint Chiefs of Staff",JCTD:"Joint Capability Technology Demonstration",JDAM:"Joint Direct Attack Munition",JDMAG:"Joint Depot Maintenance Activities Group",JDRS:"Joint Deficiency Reporting System",JEDMICS:"Joint Engineering Data Management Information and Combat System",JEM:"Joint Effects Model",JENM:"Joint Enterprise Network Manager",JEON:"Joint Emergent Operational Need",JFC:"Joint Functional Concept",JFCC:"Joint Functional Component Commander",JIC:"Joint Integrating Concept",JICO:"Joint Interface Control Officer",JIE:"Joint Intelligence Estimate",JIEDDF:"Joint Improvised Explosive Device Defeat Fund",JIEDDO:"Joint Improvised Explosive Device Defeat Organization",JITC:"Joint Interoperability Test Command",JLE:"Joint Logistics Estimate",JLLP:"Joint Lessons Learned Program",JLTV:"Joint Light Tactical Vehicle",JMC:"Joint Mission Computer",JMETC:"Joint Mission Environment Test Capability",JMM:"Joint Miniature Munitions",JMS:"Joint Space Operations Center (JSpOC) Mission System",JMT:"Joint Mission Thread",JOC:"Joint Operating Concept",JOMIS:"Joint Operational Medicine Information Systems",JOpsC:"Joint Operations Concept",JOTT:"JSF Operational Test Team",JP:"Joint Publication",JPALS:"Joint Precision Approach and Landing System",JPD:"Joint Potential Designator",JPE:"Joint Personnel Estimate",JPG:"Joint Planning Guidance",JPO:"Joint Strike fighter Program Office",JRAC:"Joint Rapid Acquisition Cell",JRMET:"Joint Reliability and Maintainability Evaluation Team",JRO:"Joint Requirements Office",JROC:"Joint Requirements Oversight Council",JROCM:"Joint Requirements Oversight Council Memorandum",JS:"Joint Staff",JSA:"Joint Strategic Assessment","JSAM-FW":"Joint Service Aircrew Mask-Fixed Wing","JSAM-SA":"Joint Service Aircrew Mask-Strategic Aircraft","JSAM-TA":"Joint Service Aircrew Mask-Tactical Aircraft",JSD:"Joint Staffing Designator",JSE:"Joint Simulation Environment",JSEW:"Joint Sensitive Equipment Wipes (Decontamination Family of Systems)",JSF:"Joint Strike Fighter",JSIG:"Joint Special Access Program (SAP) Implementation Guide",JSOW:"Joint Stand-Off Weapon",JSpOC:"Joint Space Operations Center",JSPS:"Joint Strategic Planning System",JSR:"Joint Strategy Review",JSS:"Joint Interface Control Officer (JICO) Support System",JSTAR:"Joint System Threat Assessment Report","JSTARS RECAP":"Joint Surveillance Target Attack Radar System Recapitalization","JT&E":"Joint Test and Evaluation",JTAC:"Joint Terminal Attack Controller",JTR:"Joint Tactical Radio",JTRS:"Joint Tactical Radio System","JTRS-AMF":"Joint Tactical Radio System-Airborne Maritime Fixed",JUON:"Joint Urgent Operational Need",JUPITR:"Joint United States Forces Korea Portal and Integrated Threat Recognition",JWARN:"Joint Warning & Reporting Network",JWICS:"Joint Worldwide Intelligence Communications System",KDP:"Key Decision Point",KIP:"Key Interface Profile",KLP:"Key Leadership Position","KM/DS":"Knowledge Management/Decision Support",KN:"Knowledge Now",KPP:"Key Performance Parameter",KSA:"Key System Attribute",L2:"Lessons Learned",LA:"Logistics Assessment",LAT:"Lot Acceptance Test","L-band":"Long Band",LC:"HQ AFOTEC Legal Counsel",LCB:"Lower Confidence Bound",LCC:"Life Cycle Cost",LCCE:"Life Cycle Cost Estimate",LCMC:"Life Cycle Management Center",LCMP:"Life Cycle Management Plan",LCRM:"Life Cycle Risk Management",LCS:"Launch and Checkout System",LCSP:"Life Cycle Sustainment Plan",LD:"Limited Deployment OR Logistics Demonstration",LDC:"LAN Data Collector",LDTO:"Lead Developmental Test Organization",LED:"Light Emitting Diode",LEO:"Low Earth Orbit",LEP:"Life Extension Program",LFD:"Limited Fielding Decision","LFT&E":"Live Fire Test and Evaluation",LHA:"Logistics Health Assessments",LJDAM:"Laser Joint Direct Attack Munition (GBU-56)",LM:"Lockheed Martin",LMD:"Logistics MANPRINT Demonstration",LMDP:"Life Cycle Mission Data Plan",LNE:"Late Network Entry",LNO:"Liaison Officers",LOA:"Letter of Offer and Acceptance",LORA:"Level of Repair Analysis",LOS:"Line of Sight",LR:"Limited Rights",LRDR:"Long Range Discrimination Radar",LRIP:"Low Rate Initial Production",LRSO:"Long Range Standoff",LRT:"Logistics Response Time",LRU:"Line-Replaceable Unit",LSC:"Logistics Support Concept",LSE:"Lead Systems Engineer",LSI:"Large Scale Integration OR Lead Systems Integrator",LTE:"Last Test Event",LTWG:"Logistics Test Working Group",LUT:"Limited User Test",LVC:"Live, Virtual, and Constructive","M&S":"Modeling and Simulation","M&S CO":"Modeling and Simulation Coordination Office",MAAP:"Master Air Attack Plan",MAAPTK:"Master Air Attack Planning Toolkit",MAC:"Mission Assurance Category",MACH:"Modular Air Crew Helmet",MADL:"Multifunction Advanced Data Link","MAF-DRC":"Mobility Air Forces-Dynamic Retasking Capability",MAFPS:"Mobility Air Force Automated Flight Planning Service",MAIS:"Major Automated Information System",MAJCOM:"Major Command","MALD-J":"Miniature Air Launched Decoy-Jammer",MANPAD:"Man Portable Air Defense System",MANPRINT:"Manpower and Personnel Integration",MAnTSS:"Modular Analysis and Test Support System",MAR:"Monthly Acquisition Report",MAV:"Maverick",MBITR:"Multiband Inter/Intra Team Radio",MBTD:"Mission Based Test Design",MC:"Mission Capable",MCF:"Mission Critical Functions",MCOTEA:"Marine Corps Operational Test and Evaluation Activity",MCR:"Message Completion Rate",MD:"Mission Directive",MDA:"Milestone Decision Authority OR Missile Defense Agency",MDAP:"Major Defense Acquisition Program",MDD:"Maintenance Data Documentation OR Material Development Decision",MDF:"Mission Data File",MDS:"Mission Design Series",MDT:"Mean Down Time","ME/SE":"Maintenance Engineering/Sustaining Engineering",MECSIP:"Mechanical Subsystems Integrity Plan",MEDALS:"Military Engineering Data Asset Locator System",MEFL:"Mission Essential Functions List",MEO:"Medium Earth Orbit",MER:"Manpower Estimate Report",MESL:"Minimum Essential Subsystems List",MEV:"Military Equipment Valuation",MFOQA:"Military Flight Operations Quality Assurance",MFP:"Major Force Program OR Materiel Fielding Plan",MFR:"Memorandum for Record",MFT:"Multi-Functional Team",MGRS:"Military Grid Referencing System","MGUE Inc 2 HH":"Military GPS User Equipment Hand Held",MGUE:"Military GPS User Equipment",MHS:"Modular Handgun System",MHz:"Megahertz","MIL-DTL":"Military Detail (Specification)","MIL-HDBK":"Military Handbook","MIL-PRF":"Military Performance (Specification)","MIL-STD":"Military Standard",MIP:"Materiel Improvement Program OR Military Intelligence Program",MIPR:"Military Interdepartmental Purchase Request",MIPRB:"Material Improvement Program Review Board",MLS:"Multiple Levels of Security",MMT:"Munitions, Missiles, and Target",MNS:"Mission Needs Statement",MOA:"Memorandum of Agreement",MOASP:"Management and Oversight of Acquisition Services Process",MOE:"Measure of Effectiveness",MOEs:"Measures of Effectiveness",MOP:"Measure of Performance",MOPP:"Mission Oriented Protective Posture",MORV:"Mission-Oriented Response Variables",MOS:"Measure of Suitability OR Military Occupational Specialty",MOSA:"Modular Open Systems Approach","MOT&E":"Multiservice Operational Test and Evaluation",MOU:"Memorandum of Understanding",MP:"Mission Profile",MPA:"Manpower Authorization",MPE:"Mission Planning Element",MPGPA:"Multipart GPS Pulse-per-Second Adapter",MPS:"Master Program Schedule OR Mission Planning System",MPTO:"Methods and Procedures Technical Order",MRA:"Manufacturing Readiness Assessment",MRB:"Mission Requirements Board",MRDS:"Man-Portable Radiological Detection System",MRL:"Manufacturing Readiness Level",MROi:"Air Force Depot Maintenance, Repair, and Overhaul Initiative",MRP:"Munitions Requirements Process",MRR:"Materiel Release Review",MRRB:"Maintenance Requirement Review Board",MRSP:"Mobility Readiness Spares Package",MRTFB:"Major Range and Test Facility Base",MS:"Milestone",MSA:"Materiel Solution Analysis",MSIAC:"Modeling and Simulation Information Analysis Center",MSL:"Mean Sea Level",MSSP:"Modeling and Simulation Support Plan",MTBEFF:"Mean Time Between Essential Function Failures",MTTR:"Mean Time To Repair",MUA:"Military Utility Assessment",MUOS:"Mobile User Objective System",MW:"Measures Workshop",NAOC:"National Airborne Operations Center",NASIC:"National Air and Space Intelligence Center",NATO:"North Atlantic Treaty Organization","NAVPLAN TPC":"Navigation Plan Tactical Pilotage Charts",NBC:"Nuclear, Biological and Chemical","NC2-ESI":"Nuclear Command and Control-Extremely Sensitive Information",NC3:"Nuclear Command, Control, Communications",NCOW:"Network-Centric Operations and Warfare","NCOW RM":"Net-Centric Operations and Warfare Reference Model",NDAA:"National Defense Authorization Act",NDF:"Network Design Facility",NDI:"Non-Developmental Item",NDS:"National Defense Strategy",NEPA:"National Environmental Policy Act",NET:"New Equipment Training",NetRA:"Network Risk Assessment",NEW:"Network Enabled Weapon",NGG:"Next Generation Geosynchronous Earth Orbit (GEO)",NGP:"Next Generation Polar",NGA:"National Geospatial-Intelligence Agency",NGB:"National Guard Bureau",NGCD:"Next Generation Chemical Detector",NGDS:"Next Generation Diagnostic System",NGREA:"National Guard and Reserve Equipment Account",NGS:"Non-Government Standard (commercial)",NID:"National Interest Determination",NIP:"National Intelligence Program",NIPRNet:"Non-Secure Internet Protocol Router Network",NISPOM:"National Industrial Security Program Operating Manual",NIST:"National Institute of Standards and Technology",NKCE:"Non-Kinetic Counter Electronics",NLT:"No or Not Later Than",NM:"Network Management",NMC:"Not Mission Capable",NMS:"National Military Strategy",NNMSB:"Nonnuclear Munitions Safety Board",NNSA:"National Nuclear Security Administration",NOU:"No Operational Utility",NPES:"Nuclear Planning and Execution System Modernization","NR KPP":"Net-Ready Key Performance Parameter",NRE:"Non-Recurring Engineering",NRO:"National Reconnaissance Office",NSA:"National Security Agency",NSL:"Near Strike Lightning",NSN:"National Stock Number",NSPS:"National Security Personnel System",NSS:"National Security Space OR National Security Strategy OR National Security System",NTTR:"Nevada Test and Training Range",NWC:"Nuclear Weapons Council",NWRM:"Nuclear Weapons Related Materiel","O&M":"Operation and Maintenance","O&S":"Operation and Support",OA:"Operational Assessment OR Operational Availability",OAG:"Operational Advisory Group (USN/USMC)",OAR:"Open-Air Range",OARL:"Operating at Risk List",OAS:"Office of Aerospace Studies","OASD/NII":"Office Assistant Secretary of Defense/Network and Information Integration",OASuW:"Offensive Anti-Surface Weapon",OC:"Operational Capability",OCA:"Original Classification Authority",OCC:"Occupational Specialty Code",OCDD:"Operational Capability Development Document",OCE:"Operational Concept of Employment",OCR:"Office of Collateral Responsibility OR Operational Capability Requirement",OCX:"GPS Next Generation Operational Control System",OE:"Operational Effectiveness OR Operational Environment",OEM:"Original Equipment Manufacturer",OER:"Operational Test Agency Evaluation Report",OFP:"Operational Flight Program",OFS:"Operational Flight Software",OIPT:"Overarching Integrated Product Team",OL:"Operating Location",OMB:"Office of Management and Budget",OML:"Outer Mold Line",OMS:"Operational Mission Summary OR Operational Mode Summary",OND:"Operational Need Date",OPIR:"Overhead Persistent Infrared",OPLAN:"Operations Plan",OPORD:"Operations Order",OPR:"Office of Primary Responsibility",OPSEC:"Operations Security",OPTEMPO:"Operational Tempo",OPTEVFOR:"Operational Test and Evaluation Force",ORD:"Operational Requirements Document",ORM:"Operational Risk Management",OS:"Operational Suitability",OSD:"Office of the Secretary of Defense",OSHA:"Occupational Safety and Health Administration","OSS&E":"Operational Safety, Suitability, and Effectiveness",OT:"Operational Test","OT&E":"Operational Test and Evaluation",OTA:"Operational Test Agency OR Other Transactions Authority",OTAR:"Over-the-Air Re-key",OTB:"Over Target Baseline",OTC:"United States Army Operational Test Command",OTD:"Open Technology Development",OTI:"Operational Training Infrastructure",OTIF:"Operational Test Information Files",OTO:"Operational Test Organization",OTRR:"Operational Test Readiness Review",OTS:"Over Target Schedule",OU:"Operational Utility",OUA:"Operational Utility Assessment",OUE:"Operational Utility Evaluation",OUSD:"Office of the Under Secretary of Defense",OV:"Operational View (or Viewpoint)",OWLP:"Overseas Workload Program","P&D":"Production and Deployment (phase)",P3I:"Pre-Planned Product Improvement",PA:"Partnering Arrangement OR Preparing Activity OR Preparing Authority OR Program Authorization ORPublic Affairs",PAA:"Phased Adaptive Approach",PAD:"Program Action Directive",PAM:"Pamphlet OR Performance Attributes Matrix",PAR:"Presidential Aircraft Recapitalization OR Proposal Analysis Report",PAS:"Personnel Accounting Symbol","PAT&E":"Production Acceptance Test and Evaluation",PAUC:"Program Acquisition Unit Cost",PB:"President’s Budget",PBA:"Performance Based Acquisition OR Performance Based Agreement",PBCM:"Portable Biological Containment Module",PBL:"Performance Based Logistics",PBR:"Program/Budget Review",PC:"Product Center",PCC:"Program Control Chief",PCO:"Procuring Contracting Officer",PD:"Program Director",PDAQ:"Product Data Acquisition",PDM:"Program Decision Memorandum OR Programmed Depot Maintenance",PDR:"Preliminary Design Review",PE:"Program Element",PEM:"Program Element Monitor",PEO:"Program Executive Office / Officer",PESD:"Personnel Electrostatic Discharge",PESHE:"Programmatic Environment, Safety, and Occupational Health Evaluation",PG:"Product Group",PGI:"Procedures, Guidance, and Information",PGL:"Program Guidance Letter",PGM:"Precision Guided Munitions OR Product Group Manager","PHS&T":"Packaging, Handling, Storage, and Transportation",PIA:"Privacy Impact Assessment",PID:"Program Introduction Document",PII:"Personally Identifiable Information",PIR:"Post-Implementation Review",PISR:"Persistent Intelligence, Surveillance, and Reconnaissance",PIT:"Platform Information Technology",PL:"Public Law",PLI:"Position Location Information",PLMS:"Product Lifecycle Management System",PLR:"Position Location Recorder",PM:"Program Manager","PM/MFT":"Program Management or Multi-Functional Team",PMA:"Program Management Agreement",PMB:"Performance Measurement Baseline",PMC:"Partially Mission Capable",PMCS:"Preventive Maintenance Checks and Services",PMD:"Program Management Directive",PML:"Program Management Listing",PMO:"Program Management Office",PMRT:"Program Management Resource Tools",PMT:"Program Manager‘s Tool",PNVC:"Presidential and National Voice Conferencing",PO:"Program Office OR Project Officer","POA&M":"Plan of Action & Milestones",POC:"Point of Contact",POE:"Program Office Estimates",POM:"Program Objective Memorandum",POMx:"Point of Maintenance",PoPS:"Probability of Program Success",PoR:"Program of Record",POS:"Pre-Operational Support",POU:"Partial Operational Utility",PPBE:"Planning, Programming, Budgeting, and Execution","P-PLAN":"Programming Plan",PPLANS:"Programming Plans",PPP:"Program Protection Plan OR Public-Private Partnership",PPQT:"Pre-Production Qualification Test",PPR:"Post-Publication Review",PQT:"Production Qualification Test",PRA:"Performance Risk Assessment",PRO:"Portable Rugged Objected",PRR:"Production Readiness Review","PS-BCA":"Product Support Business Case Analysis",PSEAG:"Physical Security Equipment Action Group",PSI:"Product Support Integrator",PSIP:"Propulsion Systems Integrity Program",PSM:"Product Support Manager",PSMP:"Product Support Management Plan",PSN:"Publication Stock Number",PSP:"Product Support Provider",PSpec:"Preliminary Specification",PSR:"Program Support Review",PTES:"Protected Tactical Enterprise Services",PTO:"Participating Test Organization OR Preliminary Technical Order",PTS:"Protected Tactical SATCOM",PTSS:"Precision Tracking Space System",PV:"Project Viewpoint",PVI:"Pilot Vehicle Interface",PWS:"Performance Work Statement",QDR:"Quadrennial Defense Review",QoS:"Quality of Service","QOT&E":"Qualification Operational Test and Evaluation",QRC:"Quick Reaction Capability",QRF:"Quick Reaction Fund",QRG:"Quick Reference Guide",QRIP:"Quick Reaction Instrumentation Package","QT&E":"Qualification Test and Evaluation","R&D":"Research and Development","R&M":"Reliability and Maintainability","R/T":"Request for Test",RAA:"Rapid Acquisition Authority OR Required Assets Available",RADAR:"Radio Detection and Ranging",RAI:"Recorded Aircraft Information",RALOT:"Risk Assessment Level of Test",RAM:"Reliability, Availability, and Maintainability","RAM&C":"Reliability, Availability, Maintainability, and Cost",RAMPOD:"Reliability, Availability, Maintainability for Pods and Integrated Systems",RAMS:"Reliability, Availability, Maintainability, and Supportability",RAPIDS:"Rapid Analysis Processing Instrumentation Deployment System",RC:"Recommended Changes",RCA:"Regulatory Contracting Approval",RCM:"Reliability Centered Maintenance",RCN:"Report Control Number",RCT:"Requirements Correlation Table",RD:"Restricted Data",RDGT:"Reliability Development/Growth Test",RDS:"Radiological Detection System OR Records Disposition Schedule","RDT&E":"Research, Development, Test and Evaluation",REMIS:"Reliability and Maintainability Information System",REP:"Resource Enhancement Program",RF:"Radio Frequency",RFID:"Radio Frequency Identification",RFP:"Request for Proposal",RGC:"Reliability Growth Curve",RI3:"Risk Identification: Integration & -Ilities",RICS2:"Remote Reconfigurable Intelligent Instrumentation to Control, Collect, Simulate and Stimulate",RIID:"Radioisotope Identification Detector",RLA:"Rotary Launcher Assembly",RM:"Reference Manual OR Risk Management","RM&A":"Reliability, Maintainability and Availability",RMCT:"Requirements Management Certification Training",RMD:"Requirements Management Division",RMF:"Risk Management Framework",RMP:"Radar Modernization Program OR Risk Management Plan",ROM:"Rough Order of Magnitude",RPA:"Remotely Piloted Aircraft",RPIE:"Real Property Installed Equipment","RQ-4B Bk 30 MSI":"RQ-4B Block 30 Multi-Spectral Intelligence",RR:"Rifleman Radio",RRB:"Requirements Review Board",RRF:"Rapid Reaction Fund",RRP:"Rapid Response Process",RS:"Radiated Susceptibility",RSE:"Radar Signal Emulator",RSR:"Requirements Strategy Review",RTKN:"Real Time Kill Notification",RTO:"Radio Telephone Operator OR Ready for Transition to Operations ORResponsible Test Organization (now obsolete) OR Range Training Officer","R-TOC":"Reduction of Total Ownership Cost",RTT:"Readiness to Test","S&T":"Science and Technology",S2E2:"Space Based Infrared Sys (SBIRS) Survivable and Endurable Evolution",SA:"Security Assistance OR Situational Awareness OR System Administrator",SAASM:"Selective Availability Anti-Spoofing Module",SAE:"Service Acquisition Executive",SAF:"Secretary of the Air Force","SAF/AQ":"Assistant Secretary of the Air Force (Acquisition)","SAF/AQX":"Deputy Assistant Secretary for Acquisition Integration","SAF/CIO A6":"Chief of Warfighting Integration and Chief Information Officer (CIO)","SAF/FM":"Assistant Secretary of the Air Force (Financial Management)","SAF/FMC":"Deputy Assistant Secretary (DAS) of the Air Force for Cost and Economics","SAF/GC":"General Counsel of the Air Force","SAF/GCQ":"Deputy General Counsel (Acquisition)","SAF/IE":"Assistant Secretary of the Air Force (Installations, Environment, and Logistics","SAF/IG":"Inspector General of the Air Force","SAF/LL":"Assistant Secretary of the Air Force (Legislative Affairs)","SAF/US":"Under Secretary of the Air Force","SAF/XC":"Secretary of the Air Force Directorate (Warfighting Integration and Chief Information Officer)",SAM:"Support Agreement Manager",SAMP:"Single Acquisition Management Plan",SAO:"Security Assistance Organizations",SAP:"Security Assessment Plan OR Security Assistance Program OR Special Access Program",SAPCO:"Special Access Program Control Office",SAR:"Security Assessment Report OR Special Access Required OR Synthetic Aperture Radar OR System Assessment Report",SATAF:"Site Activation Task Force",SATCOM:"Satellite Communications",SATOP:"Security Assistance Technical Order Program",SB:"Small Business",SBIR:"Small Business Innovation Research",SBIRS:"Space Based Infrared System","SBIRS F/O":"Space Based Infrared System Follow-on",SBRA:"Smart Bomb Rack Assembly","SBSS F/O":"Space Based Space Surveillance Follow-On",SCD:"System Capabilities Document",SCG:"Security Classification Guide",SCI:"Sensitive Compartmented Information",SCM:"Supply Chain Manager",SCO:"Senior Contracting Official",SCP:"Service Cost Position",SCRM:"Supply Chain Risk Management",SCWDL:"Strike Common Weapon Data Link",SD:"Standardization Document",SDB:"Small Diameter Bomb",SDD:"System Development and Demonstration",SDO:"Services Designated Official",SDR:"System Design Review",SE:"Safety OR Support Equipment OR Systems Engineering","SE/ATS":"Support Equipment/Automatic Test System",SEAD:"Suppression of Enemy Air Defenses",SEAM:"Systems Engineering Assessment Model",SECAF:"Secretary of the Air Force",SECDEF:"Secretary of Defense",SEI:"Software Engineering Institute",SENSR:"Spectrum Efficient National Surveillance Radar System",SEP:"System Evaluation Plan OR Systems Engineering Plan",SERD:"Support Equipment Recommendation Data",SES:"Senior Executive Service",SESAME:"Selected Essential Item Stockage for Availability Methodology",SF:"Security Forces OR Standard Form",SFF:"Small Form Fit",SFR:"System Functional Review",SIAO:"Senior Information Assurance Official",SIGINT:"Signals Intelligence",SII:"Special Interest Item",SIM:"Serialized Item Management",SIMAF:"Simulation and Analysis Facility",SIMCERT:"Simulator Certification",SIMVAL:"Simulator Validation",SIO:"Senior Intelligence Officer","SIOP-ESI":"Single Integrated Operational Plan-Extremely Sensitive Information",SIP:"System Identification Profile OR System Information Profile",SIPC:"Service Intelligence Production Centers",SIPRNET:"Secret Internet Protocol Router Network",SISSU:"Security, Interoperability, Supportability, Sustainability, and Usability",SITREP:"Situational Report",SLA:"Service Level Agreements","SLAM-ER":"Standoff Land Attack Missile Expanded Response",SLEP:"Service Life Extension Program",SLIN:"Sub-Line Item Number",SM:"Security Manager OR Service Manager OR Single Manager",SMART:"Science, Mathematics, And Research For Transformation OR System Metrics and Reporting Tool",SMC:"Space and Missile Systems Center",SMCA:"Single Manager for Conventional Ammunition",SME:"Subject Matter Expert",SMI:"Soldier-Machine Interface",SMM:"System Maturity Matrix","SOC RPA":"Standardized Operations Center Remotely Piloted Aircraft",SOC:"Statement of Capabilities",SOCOM:"Special Operations Command",SOF:"Special Operations Forces",SOI:"Statement of Intent",SOO:"Statement of Objectives","SO-P":"Special Operations-Peculiar",SOR:"Source of Repair",SORA:"Source of Repair Assignment",SORAP:"Source of Repair Assignment Process",SORN:"System of Record Notice",SoS:"Speed of Service OR System of Systems",SOTR:"Sufficiency of Operational Test Review OR Sufficiency of Test Report",SOW:"Special Operations Wing OR Statement of Work",SP:"Security Plan OR Special Publication",SPA:"Single Point Adjustment",SPD:"System Program Director",SPE:"Senior Procurement Executive",SPG:"Strategic Planning Guidance",SPM:"System Program Manager",SPML:"Sustainment Program Master List",SPO:"System Program Office",SpOC:"Space Operations Command",SPT:"Systems Planning Team",SQL:"Structured Query Language",SRA:"Schedule Risk Assessment",SRB:"Safety Review Board",SRD:"Software or Systems Requirements Document",SRR:"System Requirements Review OR Systems Readiness Review",SRW:"Soldier Radio Waveform",SSA:"Source Selection Authority",SSAA:"Systems Security Authorization Agreement",SSAEM:"Space Situational Awareness-Environmental Monitoring",SSD:"Source Selection Decision",SSDD:"Source Selection Decision Document",SSE:"Systems Security Engineering",SSET:"Source Selection Evaluation Team",SSM:"System Sustainment Manager",SSN:"Social Security Number",SSOM:"Standard Surveillance Operating Manual",SSOR:"Strategic Source of Repair",SSP:"Source Selection Plan OR System Support Package",SSS:"Staff Summary Sheet",SSWG:"Systems Security Working Group",STA:"System Threat Analysis OR System Threat Assessment",STAR:"System Threat Assessment Report",STARCOM:"Space Training and Readiness Command",STAT:"Scientific Test and Analysis Techniques",StdV:"Standards Viewpoint",STEP:"Standard for Exchange of Product",STIG:"Security Technical Implementation Guide",STINFO:"Scientific and Technical Information",STP:"Space Test Program OR System Training Plan",STR:"Sea Test Range",STT:"Strategy-To-Task",STTR:"Small Business Technology Transfer",SUT:"System Under Test",SV:"System View",SVAD:"Survivability, Vulnerability, and Assessment Directorate",SvcV:"Services Viewpoint",SVR:"System Verification Review",SwA:"Software Assurance",SYSCOM:"Systems Command","T&E ITT":"Test and Evaluation Integrated Test Team","T&E":"Test and Evaluation",TA:"Technical Advisor OR Test Area",TAA:"Technical Airworthiness Authority",TACO:"Test and Checkout",TACP:"Tactical Air Control Party","TACP-M":"Tactical Air Control Party-Modernization",TASS:"Tactical Automated Security System",TBD:"To Be Determined","TCM-TR":"TRADOC Capabilities Manager-Tactical Radios",TCRA:"test capability readiness assessment",TCRAs:"test capability readiness assessments",TCT:"Total Contract Training",TCTO:"Time Compliance Technical Order",TD:"Test Director OR Technical Director OR Technology Development OR Technology Director","TD&E":"Tactics Development and Evaluation",TDM:"Test Design Manager",TDP:"Technical Data Package",TDR:"Test Design Requirement",TDS:"Technology Development Strategy",TDSB:"Test Data Scoring Board",TDY:"Temporary Duty",TE:"Technical Editor OR Test Evaluation",TEI:"Text Element Identifiers",TEMP:"Test and Evaluation Master Plan",TEMPEST:"Transient Electromagnetic Pulse Surveillance Technology",TEO:"Technology Executive Officers",TES:"Test and Evaluation Strategy",TFI:"Total Force Integration",TIPP:"Test Investment Planning and Programming",TIPT:"Test Integrated Product Team",TIR:"Test Incident Report",TIS:"Test Information Sheet",TISP:"Tailored Information Support Plan",TKA:"Tail Kit Assembly",TLDHS:"Target Location, Designation, and Hand-Off System",TLE:"Target Location Error",TM:"Technical Manual OR Telemetry OR Test Manager",TMCR:"Technical Manual Contract Requirement",TMDE:"Test Measurement Diagnostic Equipment",TMIPJ:"Theater Medical Information Program-Joint",TMLA:"Triple Missile Launcher Adapter",TMRR:"Technology Maturation & Risk Reduction (phase)",TMSS:"Technical Manual Specifications and Standards",TMT:"Task Management Tool",TNMCM:"Total Not Mission Capable-Maintenance",TNMCS:"Total Not Mission Capable-Supply",TO:"Tasking Order OR Technical Order",TOA:"Total Obligation Authority",TOAC:"Technical Order Advisory Council",TOC:"Tactical Operation Center OR Total Ownership Cost OR Table of Contents",TODO:"Technical Order Distribution Office",TOMA:"Technical Order Management Agency",TPCF:"Test Program Case File",TPM:"Technical Performance Measure OR Test Program Management",TPP:"Technology Protection Plan",TPS:"Test Program Set",TPT:"Training Planning Team",TPWG:"Test Plan Working Group",TR:"Technical Review",TRA:"Technology Readiness Assessment",TRADOC:"Training and Doctrine Command (US Army)",TRB:"Technical Review Board",TRD:"Technical Requirements Document",TRL:"Technology Readiness Level",TRM:"Technology Reference Model OR Test Resource Manager",TRMC:"Test Resource Management Center",TRP:"Test Resource Plan",TRR:"Test Readiness Review",TS:"Test Squadron OR Top Secret",TSN:"Trusted Systems & Networks",TSP:"Test Support Plan OR Transfer Support Plan OR Transition Support Plan","TS-PGM":"Training System Product Group Manager",TSPI:"Time / Space / Position Information",TSRA:"Training System Requirements Analysis",TSWG:"Threat Systems Working Group",TTCP:"The Technology Cooperation Program",TTP:"Tactics, Techniques, and Procedures OR Technology Transition Plan",TV:"Technical View",TW:"Test Wing",UAI:"Universal Armament",UAS:"Unmanned Aerial Systems",UAV:"Unmanned Aerial Vehicle",UC:"Unified Capabilities",UCA:"Undefinitized Contract Action",UCC:"Unified Combatant Commander",UHF:"Ultra-High Frequency",UID:"Unique Identification number",UIF:"Unfavorable Information File",UII:"Unique Item Identifier",UIPE:"Uniform Integrated Protection Ensemble",UJTL:"Universal Joint Task List",ULB:"Underwater Locator Beacon",ULO:"Unliquidated Obligation",UON:"Urgent Operational Need",UOTT:"US Operational Test Team",UP:"Unified Platform",URA:"User Representative Agency",URL:"Uniform Resource Locator",URN:"Unit Reference Number",USAF:"United States Air Force",USAFWC:"United States Air Force Warfare Center",USB:"Universal Serial Bus",USC:"United States Code",USD:"Undersecretary of Defense",USecAF:"Under Secretary of the Air Force",USMC:"United States Marine Corps",USSF:"United States Space Force",USSOCOM:"U.S. Special Operations Command",UTC:"Coordinated Universal Time",UTTR:"Utah Test and Training Range","V&V":"Verification and Validation",VCJCS:"Vice Chairman of the Joint Chiefs of Staff",VCSAF:"Vice Chief of Staff of the United States Air Force",VCSO:"Vice Chief of Space Operations",VE:"Value Engineering",VECP:"Value Engineering Change Proposal",VEP:"Value Engineering Proposal",VHF:"Very High Frequency",VIDOC:"Visual Information Documentation",VIM:"Visual Information Manager",VMC:"Visual Meteorological Conditions",VML:"Vulnerable to Move List",VMP:"Vulnerability Management Process",VOLT:"Validated Online Lifecycle Threat",VPV:"Virtual Prime Vendor",VSP:"Verification Status Page",VSTAR:"Virtual System Threat Assessment Report",VTC:"Video Teleconference","VV&A":"Verification, Validation and Accreditation",WAS:"Wide Area Surveillance",WAWF:"Wide Area Workflow",WBS:"Work Breakdown Schedule",WCF:"Working Capital Fund",WIPT:"WorkingLevel Integrated Product Team",WIT:"Watch Item Tracking",WMA:"Warfighting Mission Area",WMD:"weapons of mass destruction",WRAP:"Warfighter Rapid Acquisition Process","WS3 SLEP":"Weapons Storage and Security System Service Life Extension Program",WSEP:"Weapon System Evaluation Program",WSER:"Weapon System Enterprise Reviews","WSF-EO/IR":"Weather Satellite Follow-on Electro-Optical /Infra-Red","WSF-M":"Weather Satellite Follow-on Microwave",WSI:"Weapon System Integration OR Weapon System Integrity",WSIG:"Weapon System Integrity Guide",WSIP:"Weapon System Integrity Program",WSMR:"White Sands Missile Range",WSSP:"Weapons System Support Program",WX:"Weather",XDR:"Extended Data Rate",YTD:"Year to Date"}}}],extensions:[".mdx",".md"],defaultLayouts:{},lessBabel:!1,remarkPlugins:[],rehypePlugins:[],mediaTypes:["text/markdown","text/x-markdown"],root:"/home/t42/Documents/programming/Projects/OT_Guide/IL-2 Guide"}},{plugin:n("b9Nj"),options:{plugins:[],trackingId:null,head:!0,anonymize:!1}},{plugin:n("GddB"),options:{plugins:[]}}]},M53A:function(e,t,n){e.exports=n.p+"static/logo-8619e329fe17a156b627acc1b8227098.svg"},ME5O:function(e,t,n){"use strict";t.a={animationIterationCount:1,borderImageOutset:1,borderImageSlice:1,borderImageWidth:1,boxFlex:1,boxFlexGroup:1,boxOrdinalGroup:1,columnCount:1,columns:1,flex:1,flexGrow:1,flexPositive:1,flexShrink:1,flexNegative:1,flexOrder:1,gridRow:1,gridRowEnd:1,gridRowSpan:1,gridRowStart:1,gridColumn:1,gridColumnEnd:1,gridColumnSpan:1,gridColumnStart:1,msGridRow:1,msGridRowSpan:1,msGridColumn:1,msGridColumnSpan:1,fontWeight:1,lineHeight:1,opacity:1,order:1,orphans:1,tabSize:1,widows:1,zIndex:1,zoom:1,WebkitLineClamp:1,fillOpacity:1,floodOpacity:1,stopOpacity:1,strokeDasharray:1,strokeDashoffset:1,strokeMiterlimit:1,strokeOpacity:1,strokeWidth:1}},MMVs:function(e,t,n){e.exports=function(){var e=!1;-1!==navigator.appVersion.indexOf("MSIE 10")&&(e=!0);var t,n=[],r="object"==typeof document&&document,a=e?r.documentElement.doScroll("left"):r.documentElement.doScroll,i=r&&(a?/^loaded|^c/:/^loaded|^i|^c/).test(r.readyState);return!i&&r&&r.addEventListener("DOMContentLoaded",t=function(){for(r.removeEventListener("DOMContentLoaded",t),i=1;t=n.shift();)t()}),function(e){i?setTimeout(e,0):n.push(e)}}()},MiSq:function(e,t,n){"use strict";n.d(t,"a",(function(){return m}));var r=function(e){for(var t,n=0,r=0,a=e.length;a>=4;++r,a-=4)t=1540483477*(65535&(t=255&e.charCodeAt(r)|(255&e.charCodeAt(++r))<<8|(255&e.charCodeAt(++r))<<16|(255&e.charCodeAt(++r))<<24))+(59797*(t>>>16)<<16),n=1540483477*(65535&(t^=t>>>24))+(59797*(t>>>16)<<16)^1540483477*(65535&n)+(59797*(n>>>16)<<16);switch(a){case 3:n^=(255&e.charCodeAt(r+2))<<16;case 2:n^=(255&e.charCodeAt(r+1))<<8;case 1:n=1540483477*(65535&(n^=255&e.charCodeAt(r)))+(59797*(n>>>16)<<16)}return(((n=1540483477*(65535&(n^=n>>>13))+(59797*(n>>>16)<<16))^n>>>15)>>>0).toString(36)},a=n("ME5O"),i=n("4qRI"),o=/[A-Z]|^ms/g,s=/_EMO_([^_]+?)_([^]*?)_EMO_/g,c=function(e){return 45===e.charCodeAt(1)},l=function(e){return null!=e&&"boolean"!=typeof e},u=Object(i.a)((function(e){return c(e)?e:e.replace(o,"-$&").toLowerCase()})),d=function(e,t){switch(e){case"animation":case"animationName":if("string"==typeof t)return t.replace(s,(function(e,t,n){return f={name:t,styles:n,next:f},t}))}return 1===a.a[e]||c(e)||"number"!=typeof t||0===t?t:t+"px"};function p(e,t,n,r){if(null==n)return"";if(void 0!==n.__emotion_styles)return n;switch(typeof n){case"boolean":return"";case"object":if(1===n.anim)return f={name:n.name,styles:n.styles,next:f},n.name;if(void 0!==n.styles){var a=n.next;if(void 0!==a)for(;void 0!==a;)f={name:a.name,styles:a.styles,next:f},a=a.next;return n.styles+";"}return function(e,t,n){var r="";if(Array.isArray(n))for(var a=0;a1){c={types:["template-string","string"],content:e.content.slice(1)};var n={types:["operator"],content:e.content.charAt(0)};return Object(S.d)(o.Fragment,{key:e+t},Object(S.d)("span",Object(f.a)({},i({token:n,key:t}),{style:l})),Object(S.d)("span",i({token:c,key:t})))}return Object(S.d)("span",Object(f.a)({},i({token:e,key:t}),{style:l}))}return Object(S.d)("span",i({token:e,key:t}))})))})))}))},T=function(e){var t=e.children,n=Object(m.a)(e,["children"]);return t?Object(S.d)("a",{href:n.href,target:"_blank",rel:"noopener noreferrer"},t):null},E=Object(g.a)("pre",{target:"e2z1ahw0"})("padding:16px;background:",(function(e){return e.theme.colors.preFormattedText}),";"),P={h1:function(e){return Object(S.d)("h1",Object(f.a)({className:"heading1",id:e.children.replace(/\s+/g,"").toLowerCase()},e))},p:function(e){return Object(S.d)("p",Object(f.a)({className:"paragraph"},e))},pre:function(e){return Object(S.d)(E,null,Object(S.d)("pre",e))},code:C,a:T},R=n("lSNA"),I=n.n(R),M=n("gRFL");n("pVnL"),n("2mql");function w(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}var D=function(e,t){return"function"==typeof t?t(e):function(e){for(var t=1;t=e.length?{done:!0}:{done:!1,value:e[r++]}}}throw new TypeError("Invalid attempt to iterate non-iterable instance.\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.")}return(n=e[Symbol.iterator]()).next.bind(n)}function ne(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);nt.label?1:0}))}));var s=z.a.gatsby&&z.a.gatsby.trailingSlash?r.length-2:r.length-1,c=a.findIndex((function(e){return e.label===r[s]}));return a.length&&e.items.unshift(a.splice(c,1)[0]),e}),t)}(t)}))[0],a={};n.items.forEach((function(e){z.a.sidebar.collapsedNav&&z.a.sidebar.collapsedNav.includes(e.url)?a[e.url]=!0:a[e.url]=!1}));var i=Object(o.useState)(a),s=i[0],c=i[1];return Object(S.d)(Z,Object(f.a)({className:(z.a.sidebar.frontLine?"showFrontLine":"hideFrontLine")+" firstLevel",setCollapsed:function(e){var t;c(ee(ee({},s),{},((t={})[e]=!s[e],t)))},collapsed:s},n))};function ae(){return(ae=Object.assign||function(e){for(var t=1;t=0||(a[n]=e[n]);return a}(e,t);if(Object.getOwnPropertySymbols){var i=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(a[n]=e[n])}return a}var oe=Object(o.forwardRef)((function(e,t){var n=e.color,r=void 0===n?"currentColor":n,a=e.size,i=void 0===a?24:a,o=ie(e,["color","size"]);return s.a.createElement("svg",ae({ref:t,xmlns:"http://www.w3.org/2000/svg",width:i,height:i,viewBox:"0 0 24 24",fill:"none",stroke:r,strokeWidth:"2",strokeLinecap:"round",strokeLinejoin:"round"},o),s.a.createElement("path",{d:"M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6"}),s.a.createElement("polyline",{points:"15 3 21 3 21 9"}),s.a.createElement("line",{x1:"10",y1:"14",x2:"21",y2:"3"}))}));oe.displayName="ExternalLink";var se=oe;var ce=Object(g.a)((function(e){var t=e.className,n=(e.active,e.level,Object(m.a)(e,["className","active","level"]));return Object(S.d)("li",{className:t},Object(S.d)("a",Object(f.a)({href:n.to},n,{target:"_blank",rel:"noopener noreferrer"}),n.children))}),{target:"e1cpd07x0"})("list-style:none;a{color:#5c6975;text-decoration:none;font-weight:",(function(e){return 0===e.level?700:400}),";padding:0.45rem 0 0.45rem ",(function(e){return 2+1*(e.level||0)}),"rem;display:block;position:relative;&:hover{color:#2dc4f3 !important;}",(function(e){return e.active&&"\n // color: #663399;\n border-color: rgb(230,236,241) !important;\n border-style: solid none solid solid;\n border-width: 1px 0px 1px 1px;\n background-color: #fff;\n "})," svg{float:right;margin-right:1rem;}}"),le=Object(g.a)("aside",{target:"e1cpd07x1"})({name:"8uxxw2",styles:"width:100%;height:100vh;overflow:auto;position:fixed;padding-left:0px;position:-webkit-sticky;position:-moz-sticky;position:sticky;top:0;padding-right:0;-webkit-box-shadow:-1px 0px 4px 1px rgba(175,158,232,0.4);@media only screen and (max-width:1023px){width:100%;height:100vh;}@media (min-width:767px) and (max-width:1023px){padding-left:0;}@media only screen and (max-width:767px){padding-left:0px;height:auto;}"}),ue=Object(g.a)((function(e){return Object(S.d)("li",e,Object(S.d)("hr",null))}),{target:"e1cpd07x2"})({name:"1q387v1",styles:"list-style:none;padding:0.5rem 0;hr{margin:0;padding:0;border:0;border-bottom:1px solid #ede7f3;}"}),de=function(e){e.location;return Object(S.d)(u.StaticQuery,{query:"2619113677",render:function(e){var t=e.allMdx;return Object(S.d)(le,null,z.a.sidebar.title?Object(S.d)("div",{className:"sidebarTitle hiddenMobile",dangerouslySetInnerHTML:{__html:z.a.sidebar.title}}):null,Object(S.d)("ul",{className:"sideBarUL"},Object(S.d)(re,{edges:t.edges}),z.a.sidebar.links&&z.a.sidebar.links.length>0&&Object(S.d)(ue,null),z.a.sidebar.links.map((function(e,t){if(""!==e.link&&""!==e.text)return Object(S.d)(ce,{key:t,to:e.link},e.text,Object(S.d)(se,{size:14}))}))))}})},pe=n("ZIiI"),fe=!(!z.a.header.search||!z.a.header.search.enabled),ge=[];fe&&z.a.header.search.indexName&&ge.push({name:""+z.a.header.search.indexName,title:"Results",hitComp:"PageHit"});var me=A()({loader:function(){return Promise.all([n.e(0),n.e(8)]).then(n.bind(null,"GMNA"))},loading:v});function he(){var e=document.getElementById("navbar");"topnav"===e.className?e.className+=" responsive":e.className="topnav"}var ye=Object(g.a)("div",{target:"e1uaxj470"})("height:60px;box-shadow:0 3px 6px 0 rgba(0,0,0,0.16);background-color:#f8f8f8;position:relative;display:none;background:",(function(e){return e.isDarkThemeActive?"#001932":void 0}),";@media (max-width:767px){display:block;}"),be=function(e){var t=e.location,r=e.isDarkThemeActive,a=e.toggleActiveTheme;return Object(S.d)(u.StaticQuery,{query:"1685914912",render:function(e){var i=n("M53A"),o=n("BFUG"),s=(n("ai/O"),n("3hAw"),e.site.siteMetadata),c=s.headerTitle,l=s.helpUrl,u=s.tweetText,d=s.logo,p=s.headerLinks,f=""!==d.link?d.link:"https://www.afotec.af.mil/";return Object(S.d)("div",{className:"navBarWrapper"},Object(S.d)("nav",{className:"navBarDefault"},Object(S.d)("div",{className:"navBarHeader"},Object(S.d)(U,{to:f,className:"navBarBrand"},Object(S.d)("img",{className:"img-responsive displayInline",src:""!==d.image?d.image:i,alt:"logo"})),Object(S.d)("div",{className:"headerTitle displayInline",dangerouslySetInnerHTML:{__html:c}})),z.a.header.social?Object(S.d)("ul",{className:"socialWrapper visibleMobileView",dangerouslySetInnerHTML:{__html:z.a.header.social}}):null,Object(S.d)("div",{id:"navbar",className:"topnav"},Object(S.d)("div",{className:"visibleMobile"},Object(S.d)(de,{location:t}),Object(S.d)("hr",null)),Object(S.d)("ul",{className:"navBarUL navBarNav navBarULRight"},p.map((function(e,t){if(""!==e.link&&""!==e.text)return Object(S.d)("li",{key:t},Object(S.d)("a",{className:"sidebarLink",href:e.link,target:"_blank",rel:"noopener noreferrer",dangerouslySetInnerHTML:{__html:e.text}}))})),""!==l?Object(S.d)("li",null,Object(S.d)("a",{href:l},Object(S.d)("img",{src:pe,alt:"Help icon"}))):null,""!==u?Object(S.d)("li",null,Object(S.d)("a",{href:"https://twitter.com/intent/tweet?&text="+u,target:"_blank",rel:"noopener noreferrer"},Object(S.d)("img",{className:"shareIcon",src:o,alt:"Twitter"}))):null,""!==u?Object(S.d)("li",{className:"divider hiddenMobile"}):null,z.a.header.social?Object(S.d)("li",{className:"hiddenMobile"},Object(S.d)("ul",{className:"socialWrapper",dangerouslySetInnerHTML:{__html:z.a.header.social}})):null,Object(S.d)("li",null,Object(S.d)("div",{className:"headerTitleReleasable displayInline",dangerouslySetInnerHTML:{__html:"There are no releasability restrictions on this publication"}})),Object(S.d)("li",null,Object(S.d)($,{isDarkThemeActive:r,toggleActiveTheme:a})),fe?Object(S.d)("div",{className:"searchWrapper hiddenMobile navBarUL"},Object(S.d)(me,{collapse:!0,indices:ge})):null))),Object(S.d)(ye,{isDarkThemeActive:r},Object(S.d)("div",{className:"navBarDefault removePadd"},Object(S.d)("span",{onClick:he,className:"navBarToggle",onKeyDown:he,role:"button",tabIndex:0},Object(S.d)("span",{className:"iconBar"}),Object(S.d)("span",{className:"iconBar"}),Object(S.d)("span",{className:"iconBar"}))),fe?Object(S.d)("div",{className:"searchWrapper"},Object(S.d)(me,{collapse:!0,indices:ge})):null))}})},Ae=n("TqVZ"),Se=n("MiSq"),ve=n("SIPS");function Oe(e,t){if(void 0===e.inserted[t.name])return e.insert("",t,e.sheet,!0)}function Ce(e,t,n){var r=[],a=Object(ve.a)(e,r,n);return r.length<2?n:a+t(r)}var Te=function e(t){for(var n="",r=0;r a{background-color:#2dc4f3;color:#fff !important;}.firstLevel ul li .collapser svg path{fill:#fff !important;}.active .collapser > svg > path{fill:#001933 !important;}.firstLevel ul .item ul .item{border-left:1px solid #e6ecf1;}.sideBarUL .item{list-style:none;padding:0;}.sideBarUL .item > a{color:#2dc4f3;text-decoration:none;display:flex;align-items:center;position:relative;width:100%;padding-right:35px;padding-left:15px;}.showFrontLine .item > a:hover{background-color:#001933;}.showFrontLine .active > a{background-color:#001933;}.sideBarUL .item .item{margin-left:16px;}.firstLevel > ul > .item{margin-left:0 !important;}.showFrontLine .item .item{border-left:1px solid #e6ecf1;border-left-color:rgb(230,236,241);padding:0;width:calc(100% - 16px) !important;}.showFrontLine .item .active > a{border-color:rgb(230,236,241) !important;border-style:solid none solid solid;border-width:1px 0px 1px 1px;background-color:#2dc4f3 !important;color:#fff;}.titleWrapper{display:flex;align-items:center;padding-bottom:40px;border-bottom:1px solid rgb(230,236,241);margin-bottom:32px;}.gitBtn{height:30px;min-height:30px;display:flex;align-items:center;}.gitBtn img{width:15px;display:inline-block;margin-right:5px;}.addPaddTopBottom{padding:50px 0;}.preRightWrapper{display:block;margin:0px;flex:1 1 0%;padding:16px;text-align:right;}.smallContent{display:block;margin:0px;padding:0px;color:#6e6e6e;}.smallContent span{font-size:12px;line-height:1.625;font-weight:400;}.nextRightWrapper{display:block;margin:0px;padding:16px;flex:1 1 0%;}table{padding:0;}table tr{border-top:1px solid #cccccc;margin:0;padding:0;}table tr:nth-child(2n){background-color:#f8f8f8;}table tr th{font-weight:bold;border:1px solid #cccccc;text-align:left;margin:0;padding:6px 13px;}table tr td{border:1px solid #cccccc;text-align:left;margin:0;padding:6px 13px;}table tr th:first-child,table tr td:first-child{margin-top:0;}table tr th:last-child,table tr td:last-child{margin-bottom:0;}img{max-width:100%;}.communitySection{font-size:24px;font-weight:700;}.authorSection{padding:20px 0;}.authorSection,.authorName{display:flex;align-items:center;}.authorImg img{width:75px;height:75px;border-radius:50%;min-width:75px;max-width:75px;min-height:75px;max-height:75px;}.authorDetails{padding-left:10px;}.authorDesc{padding-top:5px;font-size:14px;}.authorName img{margin-left:10px;display:inline-block;width:20px;}.authorName img:hover{opacity:0.7;}.heading1{font-size:26px;font-weight:800;line-height:1.5;margin-bottom:16px;margin-top:32px;}.heading2{font-size:24px;font-weight:700;line-height:1.5;margin-bottom:16px;margin-top:32px;}.heading3{font-size:20px;font-weight:600;line-height:1.5;margin-bottom:16px;margin-top:32px;}.heading4{font-size:18px;font-weight:500;line-height:1.5;margin-bottom:16px;margin-top:32px;}.heading5{font-size:16px;font-weight:400;line-height:1.5;margin-bottom:16px;margin-top:32px;}.heading6{font-size:14px;font-weight:300;line-height:1.5;margin-bottom:16px;margin-top:32px;}.paragraph{margin:16px 0px 32px;line-height:1.625;}.pre{font-size:14px;margin:0px;padding:16px;overflow:auto;}.topnav{-webkit-transition:top 0.5s,bottom 0.5s;}@media (max-width:767px){.formElement svg path{fill:#001934;}.visibleMobileView{display:block !important;}.searchInput{color:#001934;}.socialWrapper{position:absolute;right:10px;top:29px;}.responsive{margin-top:15px;position:relative;padding-bottom:20px;border-top:1px solid #fff;}.headerTitle{padding-right:50px;font-size:16px;}.navBarBrand{min-height:40px;}.navBarBrand img{margin-right:8px;}.topnav.responsive .visibleMobile{display:block;}.topnav .navBarUL{display:none;}.topnav.responsive .navBarUL{display:block;text-align:left;}.hiddenMobile{display:none !important;}hr{margin-top:0;margin-bottom:0;}.navBarParent{display:block;}.separator{margin-top:20px;margin-bottom:20px;}.navBarULRight{position:static;}.navBarUL{display:flex;align-items:center;margin:7.5px 0px;}.navBarUL li{height:37px;}.navBarUL li a{font-size:14px;padding:10px 15px;}.navBarDefault{display:block;height:auto;}.navBarToggle{margin-right:0;display:block;position:absolute;left:11px;top:15px;background:#fff;}.navBarHeader{display:flex;min-width:auto;padding-right:0;align-items:center;}.navBarBrand{font-size:20px;padding:0 0;padding-left:0;flex:initial;padding-right:15px;}.titleWrapper{padding:0 15px;display:block;}.gitBtn{display:inline-block;}.mobileView{text-align:left !important;padding-left:0 !important;}.searchWrapper{padding:0px 0;padding-top:0px;position:absolute;bottom:0px;width:calc(100% - 70px);position:absolute;left:40px;top:8px;}.hitWrapper{width:100%;right:0;top:35px;max-height:fit-content;position:static;}}@media (min-width:768px) and (max-width:991px){.navBarDefault{padding:10px;}.navBarBrand{font-size:22px;}.navBarHeader{min-width:240px;flex:initial;}.divider{margin:0 5px;height:20px;}.hitWrapper{max-width:500px;}.navBarUL li a{padding:10px 5px;}.searchWrapper{padding-left:0px;}}"}),Ie=function(e){function t(){for(var t,n=arguments.length,r=new Array(n),a=0;a0)r.edges.map((function(e,r){var a;void 0!==e&&(e.node.fields.slug!==t.pathname&&z.a.gatsby.pathPrefix+e.node.fields.slug!==t.pathname||e.node.tableOfContents.items&&(a=e.node.tableOfContents.items.map((function(e,t){var n=e.title?e.title.replace(/\s+/g,"").toLowerCase():"#";return Object(S.d)(De,{key:t,to:"#"+n,level:1},e.title)})))),a&&(n=a)}));return n&&n.length?Object(S.d)(we,null,Object(S.d)("ul",{className:"rightSideBarUL"},Object(S.d)("li",{className:"rightSideTitle"},"CONTENTS"),n)):Object(S.d)(we,null,Object(S.d)("ul",null))}})};n("vg9a");var ke=Object(g.a)("div",{target:"edsd0s90"})("display:flex;justify-content:space-between;background:",(function(e){return e.theme.colors.background}),";.sideBarUL li a{color:",(function(e){return e.theme.colors.text}),";}.sideBarUL .item > a:hover{background-color:#2dc4f3;color:#fff !important;}@media only screen and (max-width:767px){display:block;}"),Le=Object(g.a)("main",{target:"edsd0s91"})("display:flex;flex-grow:1;margin:0px 88px;padding-top:3rem;background:",(function(e){return e.theme.colors.background}),";table tr{background:",(function(e){return e.theme.colors.background}),";}@media only screen and (max-width:1023px){padding-left:0;margin:0 10px;padding-top:3rem;}"),Fe=Object(g.a)("div",{target:"edsd0s92"})({name:"14zj307",styles:"@media only screen and (max-width:50rem){width:100%;position:relative;}"}),je=Object(g.a)("div",{target:"edsd0s93"})({name:"192n44p",styles:"width:298px;"}),Ne=Object(g.a)("div",{target:"edsd0s94"})({name:"gqp3x7",styles:"width:224px;"}),_e=function(e){var t=e.children,n=e.location;return Object(S.d)(Ie,{location:n},Object(S.d)(Me.MDXProvider,{components:P},Object(S.d)(ke,null,Object(S.d)(je,{className:"hiddenMobile"},Object(S.d)(de,{location:n})),z.a.sidebar.title?Object(S.d)("div",{className:"sidebarTitle sideBarShow",dangerouslySetInnerHTML:{__html:z.a.sidebar.title}}):null,Object(S.d)(Le,null,Object(S.d)(Fe,null,t)),Object(S.d)(Ne,{className:"hiddenMobile"},Object(S.d)(xe,{location:n})))))},Be=Object(g.a)("div",{target:"e1svfi2a0"})("margin:0px;padding:0px;width:auto;display:grid;grid-template-rows:auto;column-gap:24px;grid-template-columns:calc(50% - 8px) calc(50% - 8px);.previousBtn{cursor:pointer;-moz-box-align:center;-moz-box-direction:normal;-moz-box-orient:horizontal;margin:0px;padding:0px;position:relative;display:flex;flex-direction:row;align-items:center;place-self:stretch;border-radius:3px;border:1px solid rgb(230,236,241);transition:border 200ms ease 0s;box-shadow:rgba(116,129,141,0.1) 0px 3px 8px 0px;text-decoration:none;background-color:",(function(e){return e.theme.colors.background}),";color:",(function(e){return e.theme.colors.text}),";}.nextBtn{cursor:pointer;-moz-box-align:center;-moz-box-direction:normal;-moz-box-orient:horizontal;margin:0px;padding:0px;position:relative;display:flex;flex-direction:row;align-items:center;place-self:stretch;border-radius:3px;border:1px solid rgb(230,236,241);transition:border 200ms ease 0s;box-shadow:rgba(116,129,141,0.1) 0px 3px 8px 0px;text-decoration:none;background-color:",(function(e){return e.theme.colors.background}),";color:",(function(e){return e.theme.colors.text}),";}.nextBtn:hover,.previousBtn:hover{text-decoration:none;border:1px solid #2dc4f3;}.nextBtn:hover .rightArrow,.previousBtn:hover .leftArrow{color:#2dc4f3;}.leftArrow{display:block;margin:0px;color:rgb(157,170,182);flex:0 0 auto;font-size:24px;transition:color 200ms ease 0s;padding:16px;padding-right:16px;}.rightArrow{flex:0 0 auto;font-size:24px;transition:color 200ms ease 0s;padding:16px;padding-left:16px;display:block;margin:0px;color:rgb(157,170,182);}.nextPreviousTitle{display:block;margin:0px;padding:0px;transition:color 200ms ease 0s;}.nextPreviousTitle span{font-size:16px;line-height:1.5;font-weight:500;}@media (max-width:767px){display:block;padding:0 15px;.previousBtn{margin-bottom:20px;}}"),Ge=function(e){var t,n=e.mdx,r=e.nav,a=(r.map((function(e,r){e&&e.url===n.fields.slug&&(t=r)})),{}),i={};return void 0===t?(r[0]&&(a.url=r[0].url,a.title=r[0].title),i.url=null,i.title=null,t=-1):0===t?(a.url=r[t+1]?r[t+1].url:null,a.title=r[t+1]?r[t+1].title:null,i.url=null,i.title=null):t===r.length-1?(a.url=null,a.title=null,i.url=r[t-1]?r[t-1].url:null,i.title=r[t-1]?r[t-1].title:null):t&&(a.url=r[t+1].url,a.title=r[t+1].title,r[t-1]&&(i.url=r[t-1].url,i.title=r[t-1].title)),Object(S.d)(Be,null,i.url&&t>=0?Object(S.d)(U,{to:r[t-1].url,className:"previousBtn"},Object(S.d)("div",{className:"leftArrow"},Object(S.d)("svg",{preserveAspectRatio:"xMidYMid meet",height:"1em",width:"1em",fill:"none",xmlns:"http://www.w3.org/2000/svg",viewBox:"0 0 24 24",strokeWidth:"2",strokeLinecap:"round",strokeLinejoin:"round",stroke:"currentColor",className:"_13gjrqj"},Object(S.d)("g",null,Object(S.d)("line",{x1:"19",y1:"12",x2:"5",y2:"12"}),Object(S.d)("polyline",{points:"12 19 5 12 12 5"})))),Object(S.d)("div",{className:"preRightWrapper"},Object(S.d)("div",{className:"smallContent"},Object(S.d)("span",null,"Previous")),Object(S.d)("div",{className:"nextPreviousTitle"},Object(S.d)("span",null,r[t-1].title)))):null,a.url&&t>=0?Object(S.d)(U,{to:r[t+1].url,className:"nextBtn"},Object(S.d)("div",{className:"nextRightWrapper"},Object(S.d)("div",{className:"smallContent"},Object(S.d)("span",null,"Next")),Object(S.d)("div",{className:"nextPreviousTitle"},Object(S.d)("span",null,r[t+1]&&r[t+1].title))),Object(S.d)("div",{className:"rightArrow"},Object(S.d)("svg",{preserveAspectRatio:"xMidYMid meet",height:"1em",width:"1em",fill:"none",xmlns:"http://www.w3.org/2000/svg",viewBox:"0 0 24 24",strokeWidth:"2",strokeLinecap:"round",strokeLinejoin:"round",stroke:"currentColor",className:"_13gjrqj"},Object(S.d)("g",null,Object(S.d)("line",{x1:"5",y1:"12",x2:"19",y2:"12"}),Object(S.d)("polyline",{points:"12 5 19 12 12 19"}))))):null)};var Ue=Object(g.a)("h1",{target:"e17yakb10"})("font-size:32px;line-height:1.5;font-weight:500;border-left:2px solid #2dc4f3;padding:0 16px;flex:1;margin-top:0;padding-top:0;color:",(function(e){return e.theme.colors.heading}),";"),We=Object(g.a)("div",{target:"e17yakb11"})({name:"qu2iew",styles:"padding:1rem 1.5rem;text-align:right;a{font-size:14px;font-weight:500;line-height:1em;text-decoration:none;color:#555;border:1px solid rgb(211,220,228);cursor:pointer;border-radius:3px;transition:all 0.2s ease-out 0s;text-decoration:none;color:rgb(36,42,49);background-color:rgb(255,255,255);box-shadow:rgba(116,129,141,0.1) 0px 1px 1px 0px;height:30px;padding:5px 16px;&:hover{background-color:rgb(245,247,249);}}"}),ze=Object(g.a)("div",{target:"e17yakb12"})("max-width:750px;color:",(function(e){return e.theme.colors.text}),";ul,ol{-webkit-padding-start:40px;-moz-padding-start:40px;-o-padding-start:40px;margin:24px 0px;padding:0px 0px 0px 2em;li{font-size:16px;line-height:1.8;font-weight:400;}}a{transition:color 0.15s;color:",(function(e){return e.theme.colors.link}),";}code{border:1px solid #ede7f3;border-radius:4px;padding:2px 6px;font-size:0.9375em;background:",(function(e){return e.theme.colors.background}),";}@media (max-width:767px){padding:0 15px;}"),He=function(){var e=Object(o.useState)(!0),t=e[0],n=e[1],r=Object(o.useState)(0),a=r[0],i=r[1],s=function(){window.scrollY>a?n(!0):n(!1),i(window.scrollY)};Object(o.useEffect)((function(){return window.addEventListener("scroll",s),window.onscroll=function(){0===window.scrollY&&(n(!0),i(0))},function(){window.removeEventListener("scroll",s)}}));return Object(S.d)("button",{className:"mobileScrollUpButton "+(t?"":"fade"),onClick:function(){window.scroll(0,0)}},"Scroll to top")};function qe(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function Je(e){for(var t=1;te.length)return;if(!(v instanceof c)){if(m&&A!=t.length-1){if(p.lastIndex=S,!(R=p.exec(e)))break;for(var O=R.index+(g?R[1].length:0),C=R.index+R[0].length,T=A,E=S,P=t.length;T=(E+=t[T].length)&&(++A,S=E);if(t[A]instanceof c)continue;I=T-A,v=e.slice(S,E),R.index-=S}else{p.lastIndex=0;var R=p.exec(v),I=1}if(R){g&&(h=R[1]?R[1].length:0),C=(O=R.index+h)+(R=R[0].slice(h)).length;var M=v.slice(0,O),w=v.slice(C),D=[A,I];M&&(++A,S+=M.length,D.push(M));var x=new c(l,f?a.tokenize(R,f):R,y,R,m);if(D.push(x),w&&D.push(w),Array.prototype.splice.apply(t,D),1!=I&&a.matchGrammar(e,t,n,A,S,!0,l),o)break}else if(o)break}}}}},hooks:{add:function(){},run:function(e,t){}},tokenize:function(e,t,n){var r=[e],i=t.rest;if(i){for(var o in i)t[o]=i[o];delete t.rest}return a.matchGrammar(e,r,t,0,0,!1),r}},(i=a.Token=function(e,t,n,r,a){this.type=e,this.content=t,this.alias=n,this.length=0|(r||"").length,this.greedy=!!a}).stringify=function(e,t,n){if("string"==typeof e)return e;if("Array"===a.util.type(e))return e.map((function(n){return i.stringify(n,t,e)})).join("");var r={type:e.type,content:i.stringify(e.content,t,n),tag:"span",classes:["token",e.type],attributes:{},language:t,parent:n};if(e.alias){var o="Array"===a.util.type(e.alias)?e.alias:[e.alias];Array.prototype.push.apply(r.classes,o)}var s=Object.keys(r.attributes).map((function(e){return e+'="'+(r.attributes[e]||"").replace(/"/g,""")+'"'})).join(" ");return"<"+r.tag+' class="'+r.classes.join(" ")+'"'+(s?" "+s:"")+">"+r.content+""},a);o.languages.markup={comment://,prolog:/<\?[\s\S]+?\?>/,doctype:{pattern:/"'[\]]|"[^"]*"|'[^']*')+(?:\[(?:[^<"'\]]|"[^"]*"|'[^']*'|<(?!!--)|)*\]\s*)?>/i,greedy:!0,inside:{"internal-subset":{pattern:/(\[)[\s\S]+(?=\]>$)/,lookbehind:!0,greedy:!0,inside:null},string:{pattern:/"[^"]*"|'[^']*'/,greedy:!0},punctuation:/^$|[[\]]/,"doctype-tag":/^DOCTYPE/,name:/[^\s<>'"]+/}},cdata://i,tag:{pattern:/<\/?(?!\d)[^\s>\/=$<%]+(?:\s(?:\s*[^\s>\/=]+(?:\s*=\s*(?:"[^"]*"|'[^']*'|[^\s'">=]+(?=[\s>]))|(?=[\s/>])))+)?\s*\/?>/,greedy:!0,inside:{tag:{pattern:/^<\/?[^\s>\/]+/,inside:{punctuation:/^<\/?/,namespace:/^[^\s>\/:]+:/}},"attr-value":{pattern:/=\s*(?:"[^"]*"|'[^']*'|[^\s'">=]+)/,inside:{punctuation:[{pattern:/^=/,alias:"attr-equals"},/"|'/]}},punctuation:/\/?>/,"attr-name":{pattern:/[^\s>\/]+/,inside:{namespace:/^[^\s>\/:]+:/}}}},entity:[{pattern:/&[\da-z]{1,8};/i,alias:"named-entity"},/&#x?[\da-f]{1,8};/i]},o.languages.markup.tag.inside["attr-value"].inside.entity=o.languages.markup.entity,o.languages.markup.doctype.inside["internal-subset"].inside=o.languages.markup,o.hooks.add("wrap",(function(e){"entity"===e.type&&(e.attributes.title=e.content.replace(/&/,"&"))})),Object.defineProperty(o.languages.markup.tag,"addInlined",{value:function(e,t){var n={};n["language-"+t]={pattern:/(^$)/i,lookbehind:!0,inside:o.languages[t]},n.cdata=/^$/i;var r={"included-cdata":{pattern://i,inside:n}};r["language-"+t]={pattern:/[\s\S]+/,inside:o.languages[t]};var a={};a[e]={pattern:RegExp(/(<__[^>]*>)(?:))*\]\]>|(?!)/.source.replace(/__/g,(function(){return e})),"i"),lookbehind:!0,greedy:!0,inside:r},o.languages.insertBefore("markup","cdata",a)}}),o.languages.html=o.languages.markup,o.languages.mathml=o.languages.markup,o.languages.svg=o.languages.markup,o.languages.xml=o.languages.extend("markup",{}),o.languages.ssml=o.languages.xml,o.languages.atom=o.languages.xml,o.languages.rss=o.languages.xml,function(e){var t="\\b(?:BASH|BASHOPTS|BASH_ALIASES|BASH_ARGC|BASH_ARGV|BASH_CMDS|BASH_COMPLETION_COMPAT_DIR|BASH_LINENO|BASH_REMATCH|BASH_SOURCE|BASH_VERSINFO|BASH_VERSION|COLORTERM|COLUMNS|COMP_WORDBREAKS|DBUS_SESSION_BUS_ADDRESS|DEFAULTS_PATH|DESKTOP_SESSION|DIRSTACK|DISPLAY|EUID|GDMSESSION|GDM_LANG|GNOME_KEYRING_CONTROL|GNOME_KEYRING_PID|GPG_AGENT_INFO|GROUPS|HISTCONTROL|HISTFILE|HISTFILESIZE|HISTSIZE|HOME|HOSTNAME|HOSTTYPE|IFS|INSTANCE|JOB|LANG|LANGUAGE|LC_ADDRESS|LC_ALL|LC_IDENTIFICATION|LC_MEASUREMENT|LC_MONETARY|LC_NAME|LC_NUMERIC|LC_PAPER|LC_TELEPHONE|LC_TIME|LESSCLOSE|LESSOPEN|LINES|LOGNAME|LS_COLORS|MACHTYPE|MAILCHECK|MANDATORY_PATH|NO_AT_BRIDGE|OLDPWD|OPTERR|OPTIND|ORBIT_SOCKETDIR|OSTYPE|PAPERSIZE|PATH|PIPESTATUS|PPID|PS1|PS2|PS3|PS4|PWD|RANDOM|REPLY|SECONDS|SELINUX_INIT|SESSION|SESSIONTYPE|SESSION_MANAGER|SHELL|SHELLOPTS|SHLVL|SSH_AUTH_SOCK|TERM|UID|UPSTART_EVENTS|UPSTART_INSTANCE|UPSTART_JOB|UPSTART_SESSION|USER|WINDOWID|XAUTHORITY|XDG_CONFIG_DIRS|XDG_CURRENT_DESKTOP|XDG_DATA_DIRS|XDG_GREETER_DATA_DIR|XDG_MENU_PREFIX|XDG_RUNTIME_DIR|XDG_SEAT|XDG_SEAT_PATH|XDG_SESSION_DESKTOP|XDG_SESSION_ID|XDG_SESSION_PATH|XDG_SESSION_TYPE|XDG_VTNR|XMODIFIERS)\\b",n={pattern:/(^(["']?)\w+\2)[ \t]+\S.*/,lookbehind:!0,alias:"punctuation",inside:null},r={bash:n,environment:{pattern:RegExp("\\$"+t),alias:"constant"},variable:[{pattern:/\$?\(\([\s\S]+?\)\)/,greedy:!0,inside:{variable:[{pattern:/(^\$\(\([\s\S]+)\)\)/,lookbehind:!0},/^\$\(\(/],number:/\b0x[\dA-Fa-f]+\b|(?:\b\d+(?:\.\d*)?|\B\.\d+)(?:[Ee]-?\d+)?/,operator:/--?|-=|\+\+?|\+=|!=?|~|\*\*?|\*=|\/=?|%=?|<<=?|>>=?|<=?|>=?|==?|&&?|&=|\^=?|\|\|?|\|=|\?|:/,punctuation:/\(\(?|\)\)?|,|;/}},{pattern:/\$\((?:\([^)]+\)|[^()])+\)|`[^`]+`/,greedy:!0,inside:{variable:/^\$\(|^`|\)$|`$/}},{pattern:/\$\{[^}]+\}/,greedy:!0,inside:{operator:/:[-=?+]?|[!\/]|##?|%%?|\^\^?|,,?/,punctuation:/[\[\]]/,environment:{pattern:RegExp("(\\{)"+t),lookbehind:!0,alias:"constant"}}},/\$(?:\w+|[#?*!@$])/],entity:/\\(?:[abceEfnrtv\\"]|O?[0-7]{1,3}|x[0-9a-fA-F]{1,2}|u[0-9a-fA-F]{4}|U[0-9a-fA-F]{8})/};e.languages.bash={shebang:{pattern:/^#!\s*\/.*/,alias:"important"},comment:{pattern:/(^|[^"{\\$])#.*/,lookbehind:!0},"function-name":[{pattern:/(\bfunction\s+)\w+(?=(?:\s*\(?:\s*\))?\s*\{)/,lookbehind:!0,alias:"function"},{pattern:/\b\w+(?=\s*\(\s*\)\s*\{)/,alias:"function"}],"for-or-select":{pattern:/(\b(?:for|select)\s+)\w+(?=\s+in\s)/,alias:"variable",lookbehind:!0},"assign-left":{pattern:/(^|[\s;|&]|[<>]\()\w+(?=\+?=)/,inside:{environment:{pattern:RegExp("(^|[\\s;|&]|[<>]\\()"+t),lookbehind:!0,alias:"constant"}},alias:"variable",lookbehind:!0},string:[{pattern:/((?:^|[^<])<<-?\s*)(\w+?)\s[\s\S]*?(?:\r?\n|\r)\2/,lookbehind:!0,greedy:!0,inside:r},{pattern:/((?:^|[^<])<<-?\s*)(["'])(\w+)\2\s[\s\S]*?(?:\r?\n|\r)\3/,lookbehind:!0,greedy:!0,inside:{bash:n}},{pattern:/(^|[^\\](?:\\\\)*)(["'])(?:\\[\s\S]|\$\([^)]+\)|\$(?!\()|`[^`]+`|(?!\2)[^\\`$])*\2/,lookbehind:!0,greedy:!0,inside:r}],environment:{pattern:RegExp("\\$?"+t),alias:"constant"},variable:r.variable,function:{pattern:/(^|[\s;|&]|[<>]\()(?:add|apropos|apt|aptitude|apt-cache|apt-get|aspell|automysqlbackup|awk|basename|bash|bc|bconsole|bg|bzip2|cal|cat|cfdisk|chgrp|chkconfig|chmod|chown|chroot|cksum|clear|cmp|column|comm|composer|cp|cron|crontab|csplit|curl|cut|date|dc|dd|ddrescue|debootstrap|df|diff|diff3|dig|dir|dircolors|dirname|dirs|dmesg|du|egrep|eject|env|ethtool|expand|expect|expr|fdformat|fdisk|fg|fgrep|file|find|fmt|fold|format|free|fsck|ftp|fuser|gawk|git|gparted|grep|groupadd|groupdel|groupmod|groups|grub-mkconfig|gzip|halt|head|hg|history|host|hostname|htop|iconv|id|ifconfig|ifdown|ifup|import|install|ip|jobs|join|kill|killall|less|link|ln|locate|logname|logrotate|look|lpc|lpr|lprint|lprintd|lprintq|lprm|ls|lsof|lynx|make|man|mc|mdadm|mkconfig|mkdir|mke2fs|mkfifo|mkfs|mkisofs|mknod|mkswap|mmv|more|most|mount|mtools|mtr|mutt|mv|nano|nc|netstat|nice|nl|nohup|notify-send|npm|nslookup|op|open|parted|passwd|paste|pathchk|ping|pkill|pnpm|popd|pr|printcap|printenv|ps|pushd|pv|quota|quotacheck|quotactl|ram|rar|rcp|reboot|remsync|rename|renice|rev|rm|rmdir|rpm|rsync|scp|screen|sdiff|sed|sendmail|seq|service|sftp|sh|shellcheck|shuf|shutdown|sleep|slocate|sort|split|ssh|stat|strace|su|sudo|sum|suspend|swapon|sync|tac|tail|tar|tee|time|timeout|top|touch|tr|traceroute|tsort|tty|umount|uname|unexpand|uniq|units|unrar|unshar|unzip|update-grub|uptime|useradd|userdel|usermod|users|uudecode|uuencode|v|vdir|vi|vim|virsh|vmstat|wait|watch|wc|wget|whereis|which|who|whoami|write|xargs|xdg-open|yarn|yes|zenity|zip|zsh|zypper)(?=$|[)\s;|&])/,lookbehind:!0},keyword:{pattern:/(^|[\s;|&]|[<>]\()(?:if|then|else|elif|fi|for|while|in|case|esac|function|select|do|done|until)(?=$|[)\s;|&])/,lookbehind:!0},builtin:{pattern:/(^|[\s;|&]|[<>]\()(?:\.|:|break|cd|continue|eval|exec|exit|export|getopts|hash|pwd|readonly|return|shift|test|times|trap|umask|unset|alias|bind|builtin|caller|command|declare|echo|enable|help|let|local|logout|mapfile|printf|read|readarray|source|type|typeset|ulimit|unalias|set|shopt)(?=$|[)\s;|&])/,lookbehind:!0,alias:"class-name"},boolean:{pattern:/(^|[\s;|&]|[<>]\()(?:true|false)(?=$|[)\s;|&])/,lookbehind:!0},"file-descriptor":{pattern:/\B&\d\b/,alias:"important"},operator:{pattern:/\d?<>|>\||\+=|==?|!=?|=~|<<[<-]?|[&\d]?>>|\d?[<>]&?|&[>&]?|\|[&|]?|<=?|>=?/,inside:{"file-descriptor":{pattern:/^\d/,alias:"important"}}},punctuation:/\$?\(\(?|\)\)?|\.\.|[{}[\];\\]/,number:{pattern:/(^|\s)(?:[1-9]\d*|0)(?:[.,]\d+)?\b/,lookbehind:!0}},n.inside=e.languages.bash;for(var a=["comment","function-name","for-or-select","assign-left","string","environment","function","keyword","builtin","boolean","file-descriptor","operator","punctuation","number"],i=r.variable[1].inside,o=0;o]=?|[!=]=?=?|--?|\+\+?|&&?|\|\|?|[?*/~^%]/,punctuation:/[{}[\];(),.:]/},o.languages.c=o.languages.extend("clike",{comment:{pattern:/\/\/(?:[^\r\n\\]|\\(?:\r\n?|\n|(?![\r\n])))*|\/\*[\s\S]*?(?:\*\/|$)/,greedy:!0},"class-name":{pattern:/(\b(?:enum|struct)\s+(?:__attribute__\s*\(\([\s\S]*?\)\)\s*)?)\w+|\b[a-z]\w*_t\b/,lookbehind:!0},keyword:/\b(?:__attribute__|_Alignas|_Alignof|_Atomic|_Bool|_Complex|_Generic|_Imaginary|_Noreturn|_Static_assert|_Thread_local|asm|typeof|inline|auto|break|case|char|const|continue|default|do|double|else|enum|extern|float|for|goto|if|int|long|register|return|short|signed|sizeof|static|struct|switch|typedef|union|unsigned|void|volatile|while)\b/,function:/[a-z_]\w*(?=\s*\()/i,number:/(?:\b0x(?:[\da-f]+(?:\.[\da-f]*)?|\.[\da-f]+)(?:p[+-]?\d+)?|(?:\b\d+(?:\.\d*)?|\B\.\d+)(?:e[+-]?\d+)?)[ful]{0,4}/i,operator:/>>=?|<<=?|->|([-+&|:])\1|[?:~]|[-+*/%&|^!=<>]=?/}),o.languages.insertBefore("c","string",{macro:{pattern:/(^\s*)#\s*[a-z](?:[^\r\n\\/]|\/(?!\*)|\/\*(?:[^*]|\*(?!\/))*\*\/|\\(?:\r\n|[\s\S]))*/im,lookbehind:!0,greedy:!0,alias:"property",inside:{string:[{pattern:/^(#\s*include\s*)<[^>]+>/,lookbehind:!0},o.languages.c.string],comment:o.languages.c.comment,"macro-name":[{pattern:/(^#\s*define\s+)\w+\b(?!\()/i,lookbehind:!0},{pattern:/(^#\s*define\s+)\w+\b(?=\()/i,lookbehind:!0,alias:"function"}],directive:{pattern:/^(#\s*)[a-z]+/,lookbehind:!0,alias:"keyword"},"directive-hash":/^#/,punctuation:/##|\\(?=[\r\n])/,expression:{pattern:/\S[\s\S]*/,inside:o.languages.c}}},constant:/\b(?:__FILE__|__LINE__|__DATE__|__TIME__|__TIMESTAMP__|__func__|EOF|NULL|SEEK_CUR|SEEK_END|SEEK_SET|stdin|stdout|stderr)\b/}),delete o.languages.c.boolean,function(e){var t=/\b(?:alignas|alignof|asm|auto|bool|break|case|catch|char|char8_t|char16_t|char32_t|class|compl|concept|const|consteval|constexpr|constinit|const_cast|continue|co_await|co_return|co_yield|decltype|default|delete|do|double|dynamic_cast|else|enum|explicit|export|extern|float|for|friend|goto|if|inline|int|int8_t|int16_t|int32_t|int64_t|uint8_t|uint16_t|uint32_t|uint64_t|long|mutable|namespace|new|noexcept|nullptr|operator|private|protected|public|register|reinterpret_cast|requires|return|short|signed|sizeof|static|static_assert|static_cast|struct|switch|template|this|thread_local|throw|try|typedef|typeid|typename|union|unsigned|using|virtual|void|volatile|wchar_t|while)\b/;e.languages.cpp=e.languages.extend("c",{"class-name":[{pattern:RegExp(/(\b(?:class|concept|enum|struct|typename)\s+)(?!)\w+/.source.replace(//g,(function(){return t.source}))),lookbehind:!0},/\b[A-Z]\w*(?=\s*::\s*\w+\s*\()/,/\b[A-Z_]\w*(?=\s*::\s*~\w+\s*\()/i,/\w+(?=\s*<(?:[^<>]|<(?:[^<>]|<[^<>]*>)*>)*>\s*::\s*\w+\s*\()/],keyword:t,number:{pattern:/(?:\b0b[01']+|\b0x(?:[\da-f']+(?:\.[\da-f']*)?|\.[\da-f']+)(?:p[+-]?[\d']+)?|(?:\b[\d']+(?:\.[\d']*)?|\B\.[\d']+)(?:e[+-]?[\d']+)?)[ful]{0,4}/i,greedy:!0},operator:/>>=?|<<=?|->|([-+&|:])\1|[?:~]|<=>|[-+*/%&|^!=<>]=?|\b(?:and|and_eq|bitand|bitor|not|not_eq|or|or_eq|xor|xor_eq)\b/,boolean:/\b(?:true|false)\b/}),e.languages.insertBefore("cpp","string",{"raw-string":{pattern:/R"([^()\\ ]{0,16})\([\s\S]*?\)\1"/,alias:"string",greedy:!0}}),e.languages.insertBefore("cpp","class-name",{"base-clause":{pattern:/(\b(?:class|struct)\s+\w+\s*:\s*)[^;{}"'\s]+(?:\s+[^;{}"'\s]+)*(?=\s*[;{])/,lookbehind:!0,greedy:!0,inside:e.languages.extend("cpp",{})}}),e.languages.insertBefore("inside","operator",{"class-name":/\b[a-z_]\w*\b(?!\s*::)/i},e.languages.cpp["base-clause"])}(o),function(e){var t=/("|')(?:\\(?:\r\n|[\s\S])|(?!\1)[^\\\r\n])*\1/;e.languages.css={comment:/\/\*[\s\S]*?\*\//,atrule:{pattern:/@[\w-](?:[^;{\s]|\s+(?![\s{]))*(?:;|(?=\s*\{))/,inside:{rule:/^@[\w-]+/,"selector-function-argument":{pattern:/(\bselector\s*\(\s*(?![\s)]))(?:[^()\s]|\s+(?![\s)])|\((?:[^()]|\([^()]*\))*\))+(?=\s*\))/,lookbehind:!0,alias:"selector"},keyword:{pattern:/(^|[^\w-])(?:and|not|only|or)(?![\w-])/,lookbehind:!0}}},url:{pattern:RegExp("\\burl\\((?:"+t.source+"|"+/(?:[^\\\r\n()"']|\\[\s\S])*/.source+")\\)","i"),greedy:!0,inside:{function:/^url/i,punctuation:/^\(|\)$/,string:{pattern:RegExp("^"+t.source+"$"),alias:"url"}}},selector:RegExp("[^{}\\s](?:[^{};\"'\\s]|\\s+(?![\\s{])|"+t.source+")*(?=\\s*\\{)"),string:{pattern:t,greedy:!0},property:/(?!\s)[-_a-z\xA0-\uFFFF](?:(?!\s)[-\w\xA0-\uFFFF])*(?=\s*:)/i,important:/!important\b/i,function:/[-a-z0-9]+(?=\()/i,punctuation:/[(){};:,]/},e.languages.css.atrule.inside.rest=e.languages.css;var n=e.languages.markup;n&&(n.tag.addInlined("style","css"),e.languages.insertBefore("inside","attr-value",{"style-attr":{pattern:/(^|["'\s])style\s*=\s*(?:"[^"]*"|'[^']*')/i,lookbehind:!0,inside:{"attr-value":{pattern:/=\s*(?:"[^"]*"|'[^']*'|[^\s'">=]+)/,inside:{style:{pattern:/(["'])[\s\S]+(?=["']$)/,lookbehind:!0,alias:"language-css",inside:e.languages.css},punctuation:[{pattern:/^=/,alias:"attr-equals"},/"|'/]}},"attr-name":/^style/i}}},n.tag))}(o),function(e){var t,n=/("|')(?:\\(?:\r\n|[\s\S])|(?!\1)[^\\\r\n])*\1/;e.languages.css.selector={pattern:e.languages.css.selector,inside:t={"pseudo-element":/:(?:after|before|first-letter|first-line|selection)|::[-\w]+/,"pseudo-class":/:[-\w]+/,class:/\.[-\w]+/,id:/#[-\w]+/,attribute:{pattern:RegExp("\\[(?:[^[\\]\"']|"+n.source+")*\\]"),greedy:!0,inside:{punctuation:/^\[|\]$/,"case-sensitivity":{pattern:/(\s)[si]$/i,lookbehind:!0,alias:"keyword"},namespace:{pattern:/^(\s*)(?:(?!\s)[-*\w\xA0-\uFFFF])*\|(?!=)/,lookbehind:!0,inside:{punctuation:/\|$/}},"attr-name":{pattern:/^(\s*)(?:(?!\s)[-\w\xA0-\uFFFF])+/,lookbehind:!0},"attr-value":[n,{pattern:/(=\s*)(?:(?!\s)[-\w\xA0-\uFFFF])+(?=\s*$)/,lookbehind:!0}],operator:/[|~*^$]?=/}},"n-th":[{pattern:/(\(\s*)[+-]?\d*[\dn](?:\s*[+-]\s*\d+)?(?=\s*\))/,lookbehind:!0,inside:{number:/[\dn]+/,operator:/[+-]/}},{pattern:/(\(\s*)(?:even|odd)(?=\s*\))/i,lookbehind:!0}],combinator:/>|\+|~|\|\|/,punctuation:/[(),]/}},e.languages.css.atrule.inside["selector-function-argument"].inside=t,e.languages.insertBefore("css","property",{variable:{pattern:/(^|[^-\w\xA0-\uFFFF])--(?!\s)[-_a-z\xA0-\uFFFF](?:(?!\s)[-\w\xA0-\uFFFF])*/i,lookbehind:!0}});var r={pattern:/(\b\d+)(?:%|[a-z]+\b)/,lookbehind:!0},a={pattern:/(^|[^\w.-])-?(?:\d+(?:\.\d+)?|\.\d+)/,lookbehind:!0};e.languages.insertBefore("css","function",{operator:{pattern:/(\s)[+\-*\/](?=\s)/,lookbehind:!0},hexcode:{pattern:/\B#(?:[\da-f]{1,2}){3,4}\b/i,alias:"color"},color:[/\b(?:AliceBlue|AntiqueWhite|Aqua|Aquamarine|Azure|Beige|Bisque|Black|BlanchedAlmond|Blue|BlueViolet|Brown|BurlyWood|CadetBlue|Chartreuse|Chocolate|Coral|CornflowerBlue|Cornsilk|Crimson|Cyan|DarkBlue|DarkCyan|DarkGoldenRod|DarkGr[ae]y|DarkGreen|DarkKhaki|DarkMagenta|DarkOliveGreen|DarkOrange|DarkOrchid|DarkRed|DarkSalmon|DarkSeaGreen|DarkSlateBlue|DarkSlateGr[ae]y|DarkTurquoise|DarkViolet|DeepPink|DeepSkyBlue|DimGr[ae]y|DodgerBlue|FireBrick|FloralWhite|ForestGreen|Fuchsia|Gainsboro|GhostWhite|Gold|GoldenRod|Gr[ae]y|Green|GreenYellow|HoneyDew|HotPink|IndianRed|Indigo|Ivory|Khaki|Lavender|LavenderBlush|LawnGreen|LemonChiffon|LightBlue|LightCoral|LightCyan|LightGoldenRodYellow|LightGr[ae]y|LightGreen|LightPink|LightSalmon|LightSeaGreen|LightSkyBlue|LightSlateGr[ae]y|LightSteelBlue|LightYellow|Lime|LimeGreen|Linen|Magenta|Maroon|MediumAquaMarine|MediumBlue|MediumOrchid|MediumPurple|MediumSeaGreen|MediumSlateBlue|MediumSpringGreen|MediumTurquoise|MediumVioletRed|MidnightBlue|MintCream|MistyRose|Moccasin|NavajoWhite|Navy|OldLace|Olive|OliveDrab|Orange|OrangeRed|Orchid|PaleGoldenRod|PaleGreen|PaleTurquoise|PaleVioletRed|PapayaWhip|PeachPuff|Peru|Pink|Plum|PowderBlue|Purple|Red|RosyBrown|RoyalBlue|SaddleBrown|Salmon|SandyBrown|SeaGreen|SeaShell|Sienna|Silver|SkyBlue|SlateBlue|SlateGr[ae]y|Snow|SpringGreen|SteelBlue|Tan|Teal|Thistle|Tomato|Transparent|Turquoise|Violet|Wheat|White|WhiteSmoke|Yellow|YellowGreen)\b/i,{pattern:/\b(?:rgb|hsl)\(\s*\d{1,3}\s*,\s*\d{1,3}%?\s*,\s*\d{1,3}%?\s*\)\B|\b(?:rgb|hsl)a\(\s*\d{1,3}\s*,\s*\d{1,3}%?\s*,\s*\d{1,3}%?\s*,\s*(?:0|0?\.\d+|1)\s*\)\B/i,inside:{unit:r,number:a,function:/[\w-]+(?=\()/,punctuation:/[(),]/}}],entity:/\\[\da-f]{1,8}/i,unit:r,number:a})}(o),o.languages.javascript=o.languages.extend("clike",{"class-name":[o.languages.clike["class-name"],{pattern:/(^|[^$\w\xA0-\uFFFF])(?!\s)[_$A-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*(?=\.(?:prototype|constructor))/,lookbehind:!0}],keyword:[{pattern:/((?:^|})\s*)(?:catch|finally)\b/,lookbehind:!0},{pattern:/(^|[^.]|\.\.\.\s*)\b(?:as|async(?=\s*(?:function\b|\(|[$\w\xA0-\uFFFF]|$))|await|break|case|class|const|continue|debugger|default|delete|do|else|enum|export|extends|for|from|function|(?:get|set)(?=\s*[\[$\w\xA0-\uFFFF])|if|implements|import|in|instanceof|interface|let|new|null|of|package|private|protected|public|return|static|super|switch|this|throw|try|typeof|undefined|var|void|while|with|yield)\b/,lookbehind:!0}],function:/#?(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*(?=\s*(?:\.\s*(?:apply|bind|call)\s*)?\()/,number:/\b(?:(?:0[xX](?:[\dA-Fa-f](?:_[\dA-Fa-f])?)+|0[bB](?:[01](?:_[01])?)+|0[oO](?:[0-7](?:_[0-7])?)+)n?|(?:\d(?:_\d)?)+n|NaN|Infinity)\b|(?:\b(?:\d(?:_\d)?)+\.?(?:\d(?:_\d)?)*|\B\.(?:\d(?:_\d)?)+)(?:[Ee][+-]?(?:\d(?:_\d)?)+)?/,operator:/--|\+\+|\*\*=?|=>|&&=?|\|\|=?|[!=]==|<<=?|>>>?=?|[-+*/%&|^!=<>]=?|\.{3}|\?\?=?|\?\.?|[~:]/}),o.languages.javascript["class-name"][0].pattern=/(\b(?:class|interface|extends|implements|instanceof|new)\s+)[\w.\\]+/,o.languages.insertBefore("javascript","keyword",{regex:{pattern:/((?:^|[^$\w\xA0-\uFFFF."'\])\s]|\b(?:return|yield))\s*)\/(?:\[(?:[^\]\\\r\n]|\\.)*]|\\.|[^/\\\[\r\n])+\/[gimyus]{0,6}(?=(?:\s|\/\*(?:[^*]|\*(?!\/))*\*\/)*(?:$|[\r\n,.;:})\]]|\/\/))/,lookbehind:!0,greedy:!0,inside:{"regex-source":{pattern:/^(\/)[\s\S]+(?=\/[a-z]*$)/,lookbehind:!0,alias:"language-regex",inside:o.languages.regex},"regex-flags":/[a-z]+$/,"regex-delimiter":/^\/|\/$/}},"function-variable":{pattern:/#?(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*(?=\s*[=:]\s*(?:async\s*)?(?:\bfunction\b|(?:\((?:[^()]|\([^()]*\))*\)|(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*)\s*=>))/,alias:"function"},parameter:[{pattern:/(function(?:\s+(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*)?\s*\(\s*)(?!\s)(?:[^()\s]|\s+(?![\s)])|\([^()]*\))+(?=\s*\))/,lookbehind:!0,inside:o.languages.javascript},{pattern:/(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*(?=\s*=>)/i,inside:o.languages.javascript},{pattern:/(\(\s*)(?!\s)(?:[^()\s]|\s+(?![\s)])|\([^()]*\))+(?=\s*\)\s*=>)/,lookbehind:!0,inside:o.languages.javascript},{pattern:/((?:\b|\s|^)(?!(?:as|async|await|break|case|catch|class|const|continue|debugger|default|delete|do|else|enum|export|extends|finally|for|from|function|get|if|implements|import|in|instanceof|interface|let|new|null|of|package|private|protected|public|return|set|static|super|switch|this|throw|try|typeof|undefined|var|void|while|with|yield)(?![$\w\xA0-\uFFFF]))(?:(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*\s*)\(\s*|\]\s*\(\s*)(?!\s)(?:[^()\s]|\s+(?![\s)])|\([^()]*\))+(?=\s*\)\s*\{)/,lookbehind:!0,inside:o.languages.javascript}],constant:/\b[A-Z](?:[A-Z_]|\dx?)*\b/}),o.languages.insertBefore("javascript","string",{"template-string":{pattern:/`(?:\\[\s\S]|\${(?:[^{}]|{(?:[^{}]|{[^}]*})*})+}|(?!\${)[^\\`])*`/,greedy:!0,inside:{"template-punctuation":{pattern:/^`|`$/,alias:"string"},interpolation:{pattern:/((?:^|[^\\])(?:\\{2})*)\${(?:[^{}]|{(?:[^{}]|{[^}]*})*})+}/,lookbehind:!0,inside:{"interpolation-punctuation":{pattern:/^\${|}$/,alias:"punctuation"},rest:o.languages.javascript}},string:/[\s\S]+/}}}),o.languages.markup&&o.languages.markup.tag.addInlined("script","javascript"),o.languages.js=o.languages.javascript,function(e){var t=e.util.clone(e.languages.javascript);e.languages.jsx=e.languages.extend("markup",t),e.languages.jsx.tag.pattern=/<\/?(?:[\w.:-]+(?:\s+(?:[\w.:$-]+(?:=(?:"(?:\\[^]|[^\\"])*"|'(?:\\[^]|[^\\'])*'|[^\s{'">=]+|\{(?:\{(?:\{[^{}]*\}|[^{}])*\}|[^{}])+\}))?|\{\s*\.{3}\s*[a-z_$][\w$]*(?:\.[a-z_$][\w$]*)*\s*\}))*\s*\/?)?>/i,e.languages.jsx.tag.inside.tag.pattern=/^<\/?[^\s>\/]*/i,e.languages.jsx.tag.inside["attr-value"].pattern=/=(?!\{)(?:"(?:\\[^]|[^\\"])*"|'(?:\\[^]|[^\\'])*'|[^\s'">]+)/i,e.languages.jsx.tag.inside.tag.inside["class-name"]=/^[A-Z]\w*(?:\.[A-Z]\w*)*$/,e.languages.insertBefore("inside","attr-name",{spread:{pattern:/\{\s*\.{3}\s*[a-z_$][\w$]*(?:\.[a-z_$][\w$]*)*\s*\}/,inside:{punctuation:/\.{3}|[{}.]/,"attr-value":/\w+/}}},e.languages.jsx.tag),e.languages.insertBefore("inside","attr-value",{script:{pattern:/=(?:\{(?:\{(?:\{[^{}]*\}|[^{}])*\}|[^{}])+\})/i,inside:{"script-punctuation":{pattern:/^=(?={)/,alias:"punctuation"},rest:e.languages.jsx},alias:"language-javascript"}},e.languages.jsx.tag);var n=function e(t){return t?"string"==typeof t?t:"string"==typeof t.content?t.content:t.content.map(e).join(""):""};e.hooks.add("after-tokenize",(function(t){"jsx"!==t.language&&"tsx"!==t.language||function t(r){for(var a=[],i=0;i0&&a[a.length-1].tagName===n(o.content[0].content[1])&&a.pop():"/>"===o.content[o.content.length-1].content||a.push({tagName:n(o.content[0].content[1]),openedBraces:0}):a.length>0&&"punctuation"===o.type&&"{"===o.content?a[a.length-1].openedBraces++:a.length>0&&a[a.length-1].openedBraces>0&&"punctuation"===o.type&&"}"===o.content?a[a.length-1].openedBraces--:s=!0),(s||"string"==typeof o)&&a.length>0&&0===a[a.length-1].openedBraces){var c=n(o);i0&&("string"==typeof r[i-1]||"plain-text"===r[i-1].type)&&(c=n(r[i-1])+c,r.splice(i-1,1),i--),r[i]=new e.Token("plain-text",c,null,c)}o.content&&"string"!=typeof o.content&&t(o.content)}}(t.tokens)}))}(o),function(e){function t(e,t){return RegExp(e.replace(//g,(function(){return/(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*/.source})),t)}e.languages.insertBefore("javascript","function-variable",{"method-variable":{pattern:RegExp("(\\.\\s*)"+e.languages.javascript["function-variable"].pattern.source),lookbehind:!0,alias:["function-variable","method","function","property-access"]}}),e.languages.insertBefore("javascript","function",{method:{pattern:RegExp("(\\.\\s*)"+e.languages.javascript.function.source),lookbehind:!0,alias:["function","property-access"]}}),e.languages.insertBefore("javascript","constant",{"known-class-name":[{pattern:/\b(?:(?:(?:Uint|Int)(?:8|16|32)|Uint8Clamped|Float(?:32|64))?Array|ArrayBuffer|BigInt|Boolean|DataView|Date|Error|Function|Intl|JSON|Math|Number|Object|Promise|Proxy|Reflect|RegExp|String|Symbol|(?:Weak)?(?:Set|Map)|WebAssembly)\b/,alias:"class-name"},{pattern:/\b(?:[A-Z]\w*)Error\b/,alias:"class-name"}]}),e.languages.insertBefore("javascript","keyword",{imports:{pattern:t(/(\bimport\b\s*)(?:(?:\s*,\s*(?:\*\s*as\s+|\{[^{}]*\}))?|\*\s*as\s+|\{[^{}]*\})(?=\s*\bfrom\b)/.source),lookbehind:!0,inside:e.languages.javascript},exports:{pattern:t(/(\bexport\b\s*)(?:\*(?:\s*as\s+)?(?=\s*\bfrom\b)|\{[^{}]*\})/.source),lookbehind:!0,inside:e.languages.javascript}}),e.languages.javascript.keyword.unshift({pattern:/\b(?:as|default|export|from|import)\b/,alias:"module"},{pattern:/\b(?:await|break|catch|continue|do|else|for|finally|if|return|switch|throw|try|while|yield)\b/,alias:"control-flow"},{pattern:/\bnull\b/,alias:["null","nil"]},{pattern:/\bundefined\b/,alias:"nil"}),e.languages.insertBefore("javascript","operator",{spread:{pattern:/\.{3}/,alias:"operator"},arrow:{pattern:/=>/,alias:"operator"}}),e.languages.insertBefore("javascript","punctuation",{"property-access":{pattern:t(/(\.\s*)#?/.source),lookbehind:!0},"maybe-class-name":{pattern:/(^|[^$\w\xA0-\uFFFF])[A-Z][$\w\xA0-\uFFFF]+/,lookbehind:!0},dom:{pattern:/\b(?:document|location|navigator|performance|(?:local|session)Storage|window)\b/,alias:"variable"},console:{pattern:/\bconsole(?=\s*\.)/,alias:"class-name"}});for(var n=["function","function-variable","method","method-variable","property-access"],r=0;r",unchanged:" ",diff:"!"};Object.keys(t).forEach((function(n){var r=t[n],a=[];/^\w+$/.test(n)||a.push(/\w+/.exec(n)[0]),"diff"===n&&a.push("bold"),e.languages.diff[n]={pattern:RegExp("^(?:["+r+"].*(?:\r\n?|\n|(?![\\s\\S])))+","m"),alias:a,inside:{line:{pattern:/(.)(?=[\s\S]).*(?:\r\n?|\n)?/,lookbehind:!0},prefix:{pattern:/[\s\S]/,alias:/\w+/.exec(n)[0]}}}})),Object.defineProperty(e.languages.diff,"PREFIXES",{value:t})}(o),o.languages.git={comment:/^#.*/m,deleted:/^[-–].*/m,inserted:/^\+.*/m,string:/("|')(?:\\.|(?!\1)[^\\\r\n])*\1/m,command:{pattern:/^.*\$ git .*$/m,inside:{parameter:/\s--?\w+/m}},coord:/^@@.*@@$/m,"commit-sha1":/^commit \w{40}$/m},o.languages.go=o.languages.extend("clike",{string:{pattern:/(["'`])(?:\\[\s\S]|(?!\1)[^\\])*\1/,greedy:!0},keyword:/\b(?:break|case|chan|const|continue|default|defer|else|fallthrough|for|func|go(?:to)?|if|import|interface|map|package|range|return|select|struct|switch|type|var)\b/,boolean:/\b(?:_|iota|nil|true|false)\b/,number:/(?:\b0x[a-f\d]+|(?:\b\d+(?:\.\d*)?|\B\.\d+)(?:e[-+]?\d+)?)i?/i,operator:/[*\/%^!=]=?|\+[=+]?|-[=-]?|\|[=|]?|&(?:=|&|\^=?)?|>(?:>=?|=)?|<(?:<=?|=|-)?|:=|\.\.\./,builtin:/\b(?:bool|byte|complex(?:64|128)|error|float(?:32|64)|rune|string|u?int(?:8|16|32|64)?|uintptr|append|cap|close|complex|copy|delete|imag|len|make|new|panic|print(?:ln)?|real|recover)\b/}),delete o.languages.go["class-name"],o.languages.graphql={comment:/#.*/,description:{pattern:/(?:"""(?:[^"]|(?!""")")*"""|"(?:\\.|[^\\"\r\n])*")(?=\s*[a-z_])/i,greedy:!0,alias:"string",inside:{"language-markdown":{pattern:/(^"(?:"")?)(?!\1)[\s\S]+(?=\1$)/,lookbehind:!0,inside:o.languages.markdown}}},string:{pattern:/"""(?:[^"]|(?!""")")*"""|"(?:\\.|[^\\"\r\n])*"/,greedy:!0},number:/(?:\B-|\b)\d+(?:\.\d+)?(?:e[+-]?\d+)?\b/i,boolean:/\b(?:true|false)\b/,variable:/\$[a-z_]\w*/i,directive:{pattern:/@[a-z_]\w*/i,alias:"function"},"attr-name":{pattern:/[a-z_]\w*(?=\s*(?:\((?:[^()"]|"(?:\\.|[^\\"\r\n])*")*\))?:)/i,greedy:!0},"class-name":{pattern:/(\b(?:enum|implements|interface|on|scalar|type|union)\s+|&\s*)[a-zA-Z_]\w*/,lookbehind:!0},fragment:{pattern:/(\bfragment\s+|\.{3}\s*(?!on\b))[a-zA-Z_]\w*/,lookbehind:!0,alias:"function"},keyword:/\b(?:directive|enum|extend|fragment|implements|input|interface|mutation|on|query|repeatable|scalar|schema|subscription|type|union)\b/,operator:/[!=|&]|\.{3}/,punctuation:/[!(){}\[\]:=,]/,constant:/\b(?!ID\b)[A-Z][A-Z_\d]*\b/},function(e){function t(e,t){return"___"+e.toUpperCase()+t+"___"}Object.defineProperties(e.languages["markup-templating"]={},{buildPlaceholders:{value:function(n,r,a,i){if(n.language===r){var o=n.tokenStack=[];n.code=n.code.replace(a,(function(e){if("function"==typeof i&&!i(e))return e;for(var a,s=o.length;-1!==n.code.indexOf(a=t(r,s));)++s;return o[s]=e,a})),n.grammar=e.languages.markup}}},tokenizePlaceholders:{value:function(n,r){if(n.language===r&&n.tokenStack){n.grammar=e.languages[r];var a=0,i=Object.keys(n.tokenStack);!function o(s){for(var c=0;c=i.length);c++){var l=s[c];if("string"==typeof l||l.content&&"string"==typeof l.content){var u=i[a],d=n.tokenStack[u],p="string"==typeof l?l:l.content,f=t(r,u),g=p.indexOf(f);if(g>-1){++a;var m=p.substring(0,g),h=new e.Token(r,e.tokenize(d,n.grammar),"language-"+r,d),y=p.substring(g+f.length),b=[];m&&b.push.apply(b,o([m])),b.push(h),y&&b.push.apply(b,o([y])),"string"==typeof l?s.splice.apply(s,[c,1].concat(b)):l.content=b}}else l.content&&o(l.content)}return s}(n.tokens)}}}})}(o),function(e){e.languages.handlebars={comment:/\{\{![\s\S]*?\}\}/,delimiter:{pattern:/^\{\{\{?|\}\}\}?$/i,alias:"punctuation"},string:/(["'])(?:\\.|(?!\1)[^\\\r\n])*\1/,number:/\b0x[\dA-Fa-f]+\b|(?:\b\d+(?:\.\d*)?|\B\.\d+)(?:[Ee][+-]?\d+)?/,boolean:/\b(?:true|false)\b/,block:{pattern:/^(\s*(?:~\s*)?)[#\/]\S+?(?=\s*(?:~\s*)?$|\s)/i,lookbehind:!0,alias:"keyword"},brackets:{pattern:/\[[^\]]+\]/,inside:{punctuation:/\[|\]/,variable:/[\s\S]+/}},punctuation:/[!"#%&':()*+,.\/;<=>@\[\\\]^`{|}~]/,variable:/[^!"#%&'()*+,\/;<=>@\[\\\]^`{|}~\s]+/},e.hooks.add("before-tokenize",(function(t){e.languages["markup-templating"].buildPlaceholders(t,"handlebars",/\{\{\{[\s\S]+?\}\}\}|\{\{[\s\S]+?\}\}/g)})),e.hooks.add("after-tokenize",(function(t){e.languages["markup-templating"].tokenizePlaceholders(t,"handlebars")}))}(o),o.languages.json={property:{pattern:/"(?:\\.|[^\\"\r\n])*"(?=\s*:)/,greedy:!0},string:{pattern:/"(?:\\.|[^\\"\r\n])*"(?!\s*:)/,greedy:!0},comment:{pattern:/\/\/.*|\/\*[\s\S]*?(?:\*\/|$)/,greedy:!0},number:/-?\b\d+(?:\.\d+)?(?:e[+-]?\d+)?\b/i,punctuation:/[{}[\],]/,operator:/:/,boolean:/\b(?:true|false)\b/,null:{pattern:/\bnull\b/,alias:"keyword"}},o.languages.webmanifest=o.languages.json,o.languages.less=o.languages.extend("css",{comment:[/\/\*[\s\S]*?\*\//,{pattern:/(^|[^\\])\/\/.*/,lookbehind:!0}],atrule:{pattern:/@[\w-](?:\((?:[^(){}]|\([^(){}]*\))*\)|[^(){};\s]|\s+(?!\s))*?(?=\s*\{)/,inside:{punctuation:/[:()]/}},selector:{pattern:/(?:@\{[\w-]+\}|[^{};\s@])(?:@\{[\w-]+\}|\((?:[^(){}]|\([^(){}]*\))*\)|[^(){};@\s]|\s+(?!\s))*?(?=\s*\{)/,inside:{variable:/@+[\w-]+/}},property:/(?:@\{[\w-]+\}|[\w-])+(?:\+_?)?(?=\s*:)/i,operator:/[+\-*\/]/}),o.languages.insertBefore("less","property",{variable:[{pattern:/@[\w-]+\s*:/,inside:{punctuation:/:/}},/@@?[\w-]+/],"mixin-usage":{pattern:/([{;]\s*)[.#](?!\d)[\w-].*?(?=[(;])/,lookbehind:!0,alias:"function"}}),o.languages.makefile={comment:{pattern:/(^|[^\\])#(?:\\(?:\r\n|[\s\S])|[^\\\r\n])*/,lookbehind:!0},string:{pattern:/(["'])(?:\\(?:\r\n|[\s\S])|(?!\1)[^\\\r\n])*\1/,greedy:!0},builtin:/\.[A-Z][^:#=\s]+(?=\s*:(?!=))/,symbol:{pattern:/^(?:[^:=\s]|[ \t]+(?![\s:]))+(?=\s*:(?!=))/m,inside:{variable:/\$+(?:(?!\$)[^(){}:#=\s]+|(?=[({]))/}},variable:/\$+(?:(?!\$)[^(){}:#=\s]+|\([@*%<^+?][DF]\)|(?=[({]))/,keyword:[/-include\b|\b(?:define|else|endef|endif|export|ifn?def|ifn?eq|include|override|private|sinclude|undefine|unexport|vpath)\b/,{pattern:/(\()(?:addsuffix|abspath|and|basename|call|dir|error|eval|file|filter(?:-out)?|findstring|firstword|flavor|foreach|guile|if|info|join|lastword|load|notdir|or|origin|patsubst|realpath|shell|sort|strip|subst|suffix|value|warning|wildcard|word(?:s|list)?)(?=[ \t])/,lookbehind:!0}],operator:/(?:::|[?:+!])?=|[|@]/,punctuation:/[:;(){}]/},function(e){var t=/(?:\\.|[^\\\n\r]|(?:\n|\r\n?)(?!\n|\r\n?))/.source;function n(e){return e=e.replace(//g,(function(){return t})),RegExp(/((?:^|[^\\])(?:\\{2})*)/.source+"(?:"+e+")")}var r=/(?:\\.|``(?:[^`\r\n]|`(?!`))+``|`[^`\r\n]+`|[^\\|\r\n`])+/.source,a=/\|?__(?:\|__)+\|?(?:(?:\n|\r\n?)|(?![\s\S]))/.source.replace(/__/g,(function(){return r})),i=/\|?[ \t]*:?-{3,}:?[ \t]*(?:\|[ \t]*:?-{3,}:?[ \t]*)+\|?(?:\n|\r\n?)/.source;e.languages.markdown=e.languages.extend("markup",{}),e.languages.insertBefore("markdown","prolog",{"front-matter-block":{pattern:/(^(?:\s*[\r\n])?)---(?!.)[\s\S]*?[\r\n]---(?!.)/,lookbehind:!0,greedy:!0,inside:{punctuation:/^---|---$/,"font-matter":{pattern:/\S+(?:\s+\S+)*/,alias:["yaml","language-yaml"],inside:e.languages.yaml}}},blockquote:{pattern:/^>(?:[\t ]*>)*/m,alias:"punctuation"},table:{pattern:RegExp("^"+a+i+"(?:"+a+")*","m"),inside:{"table-data-rows":{pattern:RegExp("^("+a+i+")(?:"+a+")*$"),lookbehind:!0,inside:{"table-data":{pattern:RegExp(r),inside:e.languages.markdown},punctuation:/\|/}},"table-line":{pattern:RegExp("^("+a+")"+i+"$"),lookbehind:!0,inside:{punctuation:/\||:?-{3,}:?/}},"table-header-row":{pattern:RegExp("^"+a+"$"),inside:{"table-header":{pattern:RegExp(r),alias:"important",inside:e.languages.markdown},punctuation:/\|/}}}},code:[{pattern:/((?:^|\n)[ \t]*\n|(?:^|\r\n?)[ \t]*\r\n?)(?: {4}|\t).+(?:(?:\n|\r\n?)(?: {4}|\t).+)*/,lookbehind:!0,alias:"keyword"},{pattern:/``.+?``|`[^`\r\n]+`/,alias:"keyword"},{pattern:/^```[\s\S]*?^```$/m,greedy:!0,inside:{"code-block":{pattern:/^(```.*(?:\n|\r\n?))[\s\S]+?(?=(?:\n|\r\n?)^```$)/m,lookbehind:!0},"code-language":{pattern:/^(```).+/,lookbehind:!0},punctuation:/```/}}],title:[{pattern:/\S.*(?:\n|\r\n?)(?:==+|--+)(?=[ \t]*$)/m,alias:"important",inside:{punctuation:/==+$|--+$/}},{pattern:/(^\s*)#.+/m,lookbehind:!0,alias:"important",inside:{punctuation:/^#+|#+$/}}],hr:{pattern:/(^\s*)([*-])(?:[\t ]*\2){2,}(?=\s*$)/m,lookbehind:!0,alias:"punctuation"},list:{pattern:/(^\s*)(?:[*+-]|\d+\.)(?=[\t ].)/m,lookbehind:!0,alias:"punctuation"},"url-reference":{pattern:/!?\[[^\]]+\]:[\t ]+(?:\S+|<(?:\\.|[^>\\])+>)(?:[\t ]+(?:"(?:\\.|[^"\\])*"|'(?:\\.|[^'\\])*'|\((?:\\.|[^)\\])*\)))?/,inside:{variable:{pattern:/^(!?\[)[^\]]+/,lookbehind:!0},string:/(?:"(?:\\.|[^"\\])*"|'(?:\\.|[^'\\])*'|\((?:\\.|[^)\\])*\))$/,punctuation:/^[\[\]!:]|[<>]/},alias:"url"},bold:{pattern:n(/\b__(?:(?!_)|_(?:(?!_))+_)+__\b|\*\*(?:(?!\*)|\*(?:(?!\*))+\*)+\*\*/.source),lookbehind:!0,greedy:!0,inside:{content:{pattern:/(^..)[\s\S]+(?=..$)/,lookbehind:!0,inside:{}},punctuation:/\*\*|__/}},italic:{pattern:n(/\b_(?:(?!_)|__(?:(?!_))+__)+_\b|\*(?:(?!\*)|\*\*(?:(?!\*))+\*\*)+\*/.source),lookbehind:!0,greedy:!0,inside:{content:{pattern:/(^.)[\s\S]+(?=.$)/,lookbehind:!0,inside:{}},punctuation:/[*_]/}},strike:{pattern:n(/(~~?)(?:(?!~))+?\2/.source),lookbehind:!0,greedy:!0,inside:{content:{pattern:/(^~~?)[\s\S]+(?=\1$)/,lookbehind:!0,inside:{}},punctuation:/~~?/}},url:{pattern:n(/!?\[(?:(?!\]))+\](?:\([^\s)]+(?:[\t ]+"(?:\\.|[^"\\])*")?\)|[ \t]?\[(?:(?!\]))+\])/.source),lookbehind:!0,greedy:!0,inside:{operator:/^!/,content:{pattern:/(^\[)[^\]]+(?=\])/,lookbehind:!0,inside:{}},variable:{pattern:/(^\][ \t]?\[)[^\]]+(?=\]$)/,lookbehind:!0},url:{pattern:/(^\]\()[^\s)]+/,lookbehind:!0},string:{pattern:/(^[ \t]+)"(?:\\.|[^"\\])*"(?=\)$)/,lookbehind:!0}}}}),["url","bold","italic","strike"].forEach((function(t){["url","bold","italic","strike"].forEach((function(n){t!==n&&(e.languages.markdown[t].inside.content.inside[n]=e.languages.markdown[n])}))})),e.hooks.add("after-tokenize",(function(e){"markdown"!==e.language&&"md"!==e.language||function e(t){if(t&&"string"!=typeof t)for(var n=0,r=t.length;n]?|\+\+?|!=?|<>?=?|==?|&&?|\|\|?|[~^%?*\/@]/}),delete o.languages.objectivec["class-name"],o.languages.objc=o.languages.objectivec,o.languages.ocaml={comment:/\(\*[\s\S]*?\*\)/,string:[{pattern:/"(?:\\.|[^\\\r\n"])*"/,greedy:!0},{pattern:/(['`])(?:\\(?:\d+|x[\da-f]+|.)|(?!\1)[^\\\r\n])\1/i,greedy:!0}],number:/\b(?:0x[\da-f][\da-f_]+|(?:0[bo])?\d[\d_]*(?:\.[\d_]*)?(?:e[+-]?[\d_]+)?)/i,directive:{pattern:/\B#\w+/,alias:"important"},label:{pattern:/\B~\w+/,alias:"function"},"type-variable":{pattern:/\B'\w+/,alias:"function"},variant:{pattern:/`\w+/,alias:"variable"},module:{pattern:/\b[A-Z]\w+/,alias:"variable"},keyword:/\b(?:as|assert|begin|class|constraint|do|done|downto|else|end|exception|external|for|fun|function|functor|if|in|include|inherit|initializer|lazy|let|match|method|module|mutable|new|nonrec|object|of|open|private|rec|sig|struct|then|to|try|type|val|value|virtual|when|where|while|with)\b/,boolean:/\b(?:false|true)\b/,operator:/:=|[=<>@^|&+\-*\/$%!?~][!$%&*+\-.\/:<=>?@^|~]*|\b(?:and|asr|land|lor|lsl|lsr|lxor|mod|or)\b/,punctuation:/[(){}\[\]|.,:;]|\b_\b/},o.languages.python={comment:{pattern:/(^|[^\\])#.*/,lookbehind:!0},"string-interpolation":{pattern:/(?:f|rf|fr)(?:("""|''')[\s\S]*?\1|("|')(?:\\.|(?!\2)[^\\\r\n])*\2)/i,greedy:!0,inside:{interpolation:{pattern:/((?:^|[^{])(?:{{)*){(?!{)(?:[^{}]|{(?!{)(?:[^{}]|{(?!{)(?:[^{}])+})+})+}/,lookbehind:!0,inside:{"format-spec":{pattern:/(:)[^:(){}]+(?=}$)/,lookbehind:!0},"conversion-option":{pattern:/![sra](?=[:}]$)/,alias:"punctuation"},rest:null}},string:/[\s\S]+/}},"triple-quoted-string":{pattern:/(?:[rub]|rb|br)?("""|''')[\s\S]*?\1/i,greedy:!0,alias:"string"},string:{pattern:/(?:[rub]|rb|br)?("|')(?:\\.|(?!\1)[^\\\r\n])*\1/i,greedy:!0},function:{pattern:/((?:^|\s)def[ \t]+)[a-zA-Z_]\w*(?=\s*\()/g,lookbehind:!0},"class-name":{pattern:/(\bclass\s+)\w+/i,lookbehind:!0},decorator:{pattern:/(^\s*)@\w+(?:\.\w+)*/im,lookbehind:!0,alias:["annotation","punctuation"],inside:{punctuation:/\./}},keyword:/\b(?:and|as|assert|async|await|break|class|continue|def|del|elif|else|except|exec|finally|for|from|global|if|import|in|is|lambda|nonlocal|not|or|pass|print|raise|return|try|while|with|yield)\b/,builtin:/\b(?:__import__|abs|all|any|apply|ascii|basestring|bin|bool|buffer|bytearray|bytes|callable|chr|classmethod|cmp|coerce|compile|complex|delattr|dict|dir|divmod|enumerate|eval|execfile|file|filter|float|format|frozenset|getattr|globals|hasattr|hash|help|hex|id|input|int|intern|isinstance|issubclass|iter|len|list|locals|long|map|max|memoryview|min|next|object|oct|open|ord|pow|property|range|raw_input|reduce|reload|repr|reversed|round|set|setattr|slice|sorted|staticmethod|str|sum|super|tuple|type|unichr|unicode|vars|xrange|zip)\b/,boolean:/\b(?:True|False|None)\b/,number:/(?:\b(?=\d)|\B(?=\.))(?:0[bo])?(?:(?:\d|0x[\da-f])[\da-f]*(?:\.\d*)?|\.\d+)(?:e[+-]?\d+)?j?\b/i,operator:/[-+%=]=?|!=|\*\*?=?|\/\/?=?|<[<=>]?|>[=>]?|[&|^~]/,punctuation:/[{}[\];(),.:]/},o.languages.python["string-interpolation"].inside.interpolation.inside.rest=o.languages.python,o.languages.py=o.languages.python,o.languages.reason=o.languages.extend("clike",{string:{pattern:/"(?:\\(?:\r\n|[\s\S])|[^\\\r\n"])*"/,greedy:!0},"class-name":/\b[A-Z]\w*/,keyword:/\b(?:and|as|assert|begin|class|constraint|do|done|downto|else|end|exception|external|for|fun|function|functor|if|in|include|inherit|initializer|lazy|let|method|module|mutable|new|nonrec|object|of|open|or|private|rec|sig|struct|switch|then|to|try|type|val|virtual|when|while|with)\b/,operator:/\.{3}|:[:=]|\|>|->|=(?:==?|>)?|<=?|>=?|[|^?'#!~`]|[+\-*\/]\.?|\b(?:mod|land|lor|lxor|lsl|lsr|asr)\b/}),o.languages.insertBefore("reason","class-name",{character:{pattern:/'(?:\\x[\da-f]{2}|\\o[0-3][0-7][0-7]|\\\d{3}|\\.|[^'\\\r\n])'/,alias:"string"},constructor:{pattern:/\b[A-Z]\w*\b(?!\s*\.)/,alias:"variable"},label:{pattern:/\b[a-z]\w*(?=::)/,alias:"symbol"}}),delete o.languages.reason.function,function(e){e.languages.sass=e.languages.extend("css",{comment:{pattern:/^([ \t]*)\/[\/*].*(?:(?:\r?\n|\r)\1[ \t].+)*/m,lookbehind:!0}}),e.languages.insertBefore("sass","atrule",{"atrule-line":{pattern:/^(?:[ \t]*)[@+=].+/m,inside:{atrule:/(?:@[\w-]+|[+=])/m}}}),delete e.languages.sass.atrule;var t=/\$[-\w]+|#\{\$[-\w]+\}/,n=[/[+*\/%]|[=!]=|<=?|>=?|\b(?:and|or|not)\b/,{pattern:/(\s+)-(?=\s)/,lookbehind:!0}];e.languages.insertBefore("sass","property",{"variable-line":{pattern:/^[ \t]*\$.+/m,inside:{punctuation:/:/,variable:t,operator:n}},"property-line":{pattern:/^[ \t]*(?:[^:\s]+ *:.*|:[^:\s].*)/m,inside:{property:[/[^:\s]+(?=\s*:)/,{pattern:/(:)[^:\s]+/,lookbehind:!0}],punctuation:/:/,variable:t,operator:n,important:e.languages.sass.important}}}),delete e.languages.sass.property,delete e.languages.sass.important,e.languages.insertBefore("sass","punctuation",{selector:{pattern:/([ \t]*)\S(?:,[^,\r\n]+|[^,\r\n]*)(?:,[^,\r\n]+)*(?:,(?:\r?\n|\r)\1[ \t]+\S(?:,[^,\r\n]+|[^,\r\n]*)(?:,[^,\r\n]+)*)*/,lookbehind:!0}})}(o),o.languages.scss=o.languages.extend("css",{comment:{pattern:/(^|[^\\])(?:\/\*[\s\S]*?\*\/|\/\/.*)/,lookbehind:!0},atrule:{pattern:/@[\w-](?:\([^()]+\)|[^()\s]|\s+(?!\s))*?(?=\s+[{;])/,inside:{rule:/@[\w-]+/}},url:/(?:[-a-z]+-)?url(?=\()/i,selector:{pattern:/(?=\S)[^@;{}()]?(?:[^@;{}()\s]|\s+(?!\s)|#\{\$[-\w]+\})+(?=\s*\{(?:\}|\s|[^}][^:{}]*[:{][^}]+))/m,inside:{parent:{pattern:/&/,alias:"important"},placeholder:/%[-\w]+/,variable:/\$[-\w]+|#\{\$[-\w]+\}/}},property:{pattern:/(?:[-\w]|\$[-\w]|#\{\$[-\w]+\})+(?=\s*:)/,inside:{variable:/\$[-\w]+|#\{\$[-\w]+\}/}}}),o.languages.insertBefore("scss","atrule",{keyword:[/@(?:if|else(?: if)?|forward|for|each|while|import|use|extend|debug|warn|mixin|include|function|return|content)\b/i,{pattern:/( +)(?:from|through)(?= )/,lookbehind:!0}]}),o.languages.insertBefore("scss","important",{variable:/\$[-\w]+|#\{\$[-\w]+\}/}),o.languages.insertBefore("scss","function",{"module-modifier":{pattern:/\b(?:as|with|show|hide)\b/i,alias:"keyword"},placeholder:{pattern:/%[-\w]+/,alias:"selector"},statement:{pattern:/\B!(?:default|optional)\b/i,alias:"keyword"},boolean:/\b(?:true|false)\b/,null:{pattern:/\bnull\b/,alias:"keyword"},operator:{pattern:/(\s)(?:[-+*\/%]|[=!]=|<=?|>=?|and|or|not)(?=\s)/,lookbehind:!0}}),o.languages.scss.atrule.inside.rest=o.languages.scss,o.languages.sql={comment:{pattern:/(^|[^\\])(?:\/\*[\s\S]*?\*\/|(?:--|\/\/|#).*)/,lookbehind:!0},variable:[{pattern:/@(["'`])(?:\\[\s\S]|(?!\1)[^\\])+\1/,greedy:!0},/@[\w.$]+/],string:{pattern:/(^|[^@\\])("|')(?:\\[\s\S]|(?!\2)[^\\]|\2\2)*\2/,greedy:!0,lookbehind:!0},function:/\b(?:AVG|COUNT|FIRST|FORMAT|LAST|LCASE|LEN|MAX|MID|MIN|MOD|NOW|ROUND|SUM|UCASE)(?=\s*\()/i,keyword:/\b(?:ACTION|ADD|AFTER|ALGORITHM|ALL|ALTER|ANALYZE|ANY|APPLY|AS|ASC|AUTHORIZATION|AUTO_INCREMENT|BACKUP|BDB|BEGIN|BERKELEYDB|BIGINT|BINARY|BIT|BLOB|BOOL|BOOLEAN|BREAK|BROWSE|BTREE|BULK|BY|CALL|CASCADED?|CASE|CHAIN|CHAR(?:ACTER|SET)?|CHECK(?:POINT)?|CLOSE|CLUSTERED|COALESCE|COLLATE|COLUMNS?|COMMENT|COMMIT(?:TED)?|COMPUTE|CONNECT|CONSISTENT|CONSTRAINT|CONTAINS(?:TABLE)?|CONTINUE|CONVERT|CREATE|CROSS|CURRENT(?:_DATE|_TIME|_TIMESTAMP|_USER)?|CURSOR|CYCLE|DATA(?:BASES?)?|DATE(?:TIME)?|DAY|DBCC|DEALLOCATE|DEC|DECIMAL|DECLARE|DEFAULT|DEFINER|DELAYED|DELETE|DELIMITERS?|DENY|DESC|DESCRIBE|DETERMINISTIC|DISABLE|DISCARD|DISK|DISTINCT|DISTINCTROW|DISTRIBUTED|DO|DOUBLE|DROP|DUMMY|DUMP(?:FILE)?|DUPLICATE|ELSE(?:IF)?|ENABLE|ENCLOSED|END|ENGINE|ENUM|ERRLVL|ERRORS|ESCAPED?|EXCEPT|EXEC(?:UTE)?|EXISTS|EXIT|EXPLAIN|EXTENDED|FETCH|FIELDS|FILE|FILLFACTOR|FIRST|FIXED|FLOAT|FOLLOWING|FOR(?: EACH ROW)?|FORCE|FOREIGN|FREETEXT(?:TABLE)?|FROM|FULL|FUNCTION|GEOMETRY(?:COLLECTION)?|GLOBAL|GOTO|GRANT|GROUP|HANDLER|HASH|HAVING|HOLDLOCK|HOUR|IDENTITY(?:_INSERT|COL)?|IF|IGNORE|IMPORT|INDEX|INFILE|INNER|INNODB|INOUT|INSERT|INT|INTEGER|INTERSECT|INTERVAL|INTO|INVOKER|ISOLATION|ITERATE|JOIN|KEYS?|KILL|LANGUAGE|LAST|LEAVE|LEFT|LEVEL|LIMIT|LINENO|LINES|LINESTRING|LOAD|LOCAL|LOCK|LONG(?:BLOB|TEXT)|LOOP|MATCH(?:ED)?|MEDIUM(?:BLOB|INT|TEXT)|MERGE|MIDDLEINT|MINUTE|MODE|MODIFIES|MODIFY|MONTH|MULTI(?:LINESTRING|POINT|POLYGON)|NATIONAL|NATURAL|NCHAR|NEXT|NO|NONCLUSTERED|NULLIF|NUMERIC|OFF?|OFFSETS?|ON|OPEN(?:DATASOURCE|QUERY|ROWSET)?|OPTIMIZE|OPTION(?:ALLY)?|ORDER|OUT(?:ER|FILE)?|OVER|PARTIAL|PARTITION|PERCENT|PIVOT|PLAN|POINT|POLYGON|PRECEDING|PRECISION|PREPARE|PREV|PRIMARY|PRINT|PRIVILEGES|PROC(?:EDURE)?|PUBLIC|PURGE|QUICK|RAISERROR|READS?|REAL|RECONFIGURE|REFERENCES|RELEASE|RENAME|REPEAT(?:ABLE)?|REPLACE|REPLICATION|REQUIRE|RESIGNAL|RESTORE|RESTRICT|RETURN(?:S|ING)?|REVOKE|RIGHT|ROLLBACK|ROUTINE|ROW(?:COUNT|GUIDCOL|S)?|RTREE|RULE|SAVE(?:POINT)?|SCHEMA|SECOND|SELECT|SERIAL(?:IZABLE)?|SESSION(?:_USER)?|SET(?:USER)?|SHARE|SHOW|SHUTDOWN|SIMPLE|SMALLINT|SNAPSHOT|SOME|SONAME|SQL|START(?:ING)?|STATISTICS|STATUS|STRIPED|SYSTEM_USER|TABLES?|TABLESPACE|TEMP(?:ORARY|TABLE)?|TERMINATED|TEXT(?:SIZE)?|THEN|TIME(?:STAMP)?|TINY(?:BLOB|INT|TEXT)|TOP?|TRAN(?:SACTIONS?)?|TRIGGER|TRUNCATE|TSEQUAL|TYPES?|UNBOUNDED|UNCOMMITTED|UNDEFINED|UNION|UNIQUE|UNLOCK|UNPIVOT|UNSIGNED|UPDATE(?:TEXT)?|USAGE|USE|USER|USING|VALUES?|VAR(?:BINARY|CHAR|CHARACTER|YING)|VIEW|WAITFOR|WARNINGS|WHEN|WHERE|WHILE|WITH(?: ROLLUP|IN)?|WORK|WRITE(?:TEXT)?|YEAR)\b/i,boolean:/\b(?:TRUE|FALSE|NULL)\b/i,number:/\b0x[\da-f]+\b|\b\d+(?:\.\d*)?|\B\.\d+\b/i,operator:/[-+*\/=%^~]|&&?|\|\|?|!=?|<(?:=>?|<|>)?|>[>=]?|\b(?:AND|BETWEEN|IN|LIKE|NOT|OR|IS|DIV|REGEXP|RLIKE|SOUNDS LIKE|XOR)\b/i,punctuation:/[;[\]()`,.]/},function(e){var t={pattern:/(\b\d+)(?:%|[a-z]+)/,lookbehind:!0},n={pattern:/(^|[^\w.-])-?(?:\d+(?:\.\d+)?|\.\d+)/,lookbehind:!0},r={comment:{pattern:/(^|[^\\])(?:\/\*[\s\S]*?\*\/|\/\/.*)/,lookbehind:!0},url:{pattern:/url\((["']?).*?\1\)/i,greedy:!0},string:{pattern:/("|')(?:(?!\1)[^\\\r\n]|\\(?:\r\n|[\s\S]))*\1/,greedy:!0},interpolation:null,func:null,important:/\B!(?:important|optional)\b/i,keyword:{pattern:/(^|\s+)(?:(?:if|else|for|return|unless)(?=\s+|$)|@[\w-]+)/,lookbehind:!0},hexcode:/#[\da-f]{3,6}/i,color:[/\b(?:AliceBlue|AntiqueWhite|Aqua|Aquamarine|Azure|Beige|Bisque|Black|BlanchedAlmond|Blue|BlueViolet|Brown|BurlyWood|CadetBlue|Chartreuse|Chocolate|Coral|CornflowerBlue|Cornsilk|Crimson|Cyan|DarkBlue|DarkCyan|DarkGoldenRod|DarkGr[ae]y|DarkGreen|DarkKhaki|DarkMagenta|DarkOliveGreen|DarkOrange|DarkOrchid|DarkRed|DarkSalmon|DarkSeaGreen|DarkSlateBlue|DarkSlateGr[ae]y|DarkTurquoise|DarkViolet|DeepPink|DeepSkyBlue|DimGr[ae]y|DodgerBlue|FireBrick|FloralWhite|ForestGreen|Fuchsia|Gainsboro|GhostWhite|Gold|GoldenRod|Gr[ae]y|Green|GreenYellow|HoneyDew|HotPink|IndianRed|Indigo|Ivory|Khaki|Lavender|LavenderBlush|LawnGreen|LemonChiffon|LightBlue|LightCoral|LightCyan|LightGoldenRodYellow|LightGr[ae]y|LightGreen|LightPink|LightSalmon|LightSeaGreen|LightSkyBlue|LightSlateGr[ae]y|LightSteelBlue|LightYellow|Lime|LimeGreen|Linen|Magenta|Maroon|MediumAquaMarine|MediumBlue|MediumOrchid|MediumPurple|MediumSeaGreen|MediumSlateBlue|MediumSpringGreen|MediumTurquoise|MediumVioletRed|MidnightBlue|MintCream|MistyRose|Moccasin|NavajoWhite|Navy|OldLace|Olive|OliveDrab|Orange|OrangeRed|Orchid|PaleGoldenRod|PaleGreen|PaleTurquoise|PaleVioletRed|PapayaWhip|PeachPuff|Peru|Pink|Plum|PowderBlue|Purple|Red|RosyBrown|RoyalBlue|SaddleBrown|Salmon|SandyBrown|SeaGreen|SeaShell|Sienna|Silver|SkyBlue|SlateBlue|SlateGr[ae]y|Snow|SpringGreen|SteelBlue|Tan|Teal|Thistle|Tomato|Transparent|Turquoise|Violet|Wheat|White|WhiteSmoke|Yellow|YellowGreen)\b/i,{pattern:/\b(?:rgb|hsl)\(\s*\d{1,3}\s*,\s*\d{1,3}%?\s*,\s*\d{1,3}%?\s*\)\B|\b(?:rgb|hsl)a\(\s*\d{1,3}\s*,\s*\d{1,3}%?\s*,\s*\d{1,3}%?\s*,\s*(?:0|0?\.\d+|1)\s*\)\B/i,inside:{unit:t,number:n,function:/[\w-]+(?=\()/,punctuation:/[(),]/}}],entity:/\\[\da-f]{1,8}/i,unit:t,boolean:/\b(?:true|false)\b/,operator:[/~|[+!\/%<>?=]=?|[-:]=|\*[*=]?|\.{2,3}|&&|\|\||\B-\B|\b(?:and|in|is(?: a| defined| not|nt)?|not|or)\b/],number:n,punctuation:/[{}()\[\];:,]/};r.interpolation={pattern:/\{[^\r\n}:]+\}/,alias:"variable",inside:{delimiter:{pattern:/^{|}$/,alias:"punctuation"},rest:r}},r.func={pattern:/[\w-]+\([^)]*\).*/,inside:{function:/^[^(]+/,rest:r}},e.languages.stylus={"atrule-declaration":{pattern:/(^\s*)@.+/m,lookbehind:!0,inside:{atrule:/^@[\w-]+/,rest:r}},"variable-declaration":{pattern:/(^[ \t]*)[\w$-]+\s*.?=[ \t]*(?:\{[^{}]*\}|\S.*|$)/m,lookbehind:!0,inside:{variable:/^\S+/,rest:r}},statement:{pattern:/(^[ \t]*)(?:if|else|for|return|unless)[ \t].+/m,lookbehind:!0,inside:{keyword:/^\S+/,rest:r}},"property-declaration":{pattern:/((?:^|\{)([ \t]*))(?:[\w-]|\{[^}\r\n]+\})+(?:\s*:\s*|[ \t]+)(?!\s)[^{\r\n]*(?:;|[^{\r\n,](?=$)(?!(?:\r?\n|\r)(?:\{|\2[ \t]+)))/m,lookbehind:!0,inside:{property:{pattern:/^[^\s:]+/,inside:{interpolation:r.interpolation}},rest:r}},selector:{pattern:/(^[ \t]*)(?:(?=\S)(?:[^{}\r\n:()]|::?[\w-]+(?:\([^)\r\n]*\)|(?![\w-]))|\{[^}\r\n]+\})+)(?:(?:\r?\n|\r)(?:\1(?:(?=\S)(?:[^{}\r\n:()]|::?[\w-]+(?:\([^)\r\n]*\)|(?![\w-]))|\{[^}\r\n]+\})+)))*(?:,$|\{|(?=(?:\r?\n|\r)(?:\{|\1[ \t]+)))/m,lookbehind:!0,inside:{interpolation:r.interpolation,comment:r.comment,punctuation:/[{},]/}},func:r.func,string:r.string,comment:{pattern:/(^|[^\\])(?:\/\*[\s\S]*?\*\/|\/\/.*)/,lookbehind:!0,greedy:!0},interpolation:r.interpolation,punctuation:/[{}()\[\];:.]/}}(o),function(e){e.languages.typescript=e.languages.extend("javascript",{"class-name":{pattern:/(\b(?:class|extends|implements|instanceof|interface|new|type)\s+)(?!keyof\b)(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*(?:\s*<(?:[^<>]|<(?:[^<>]|<[^<>]*>)*>)*>)?/,lookbehind:!0,greedy:!0,inside:null},keyword:/\b(?:abstract|as|asserts|async|await|break|case|catch|class|const|constructor|continue|debugger|declare|default|delete|do|else|enum|export|extends|finally|for|from|function|get|if|implements|import|in|instanceof|interface|is|keyof|let|module|namespace|new|null|of|package|private|protected|public|readonly|return|require|set|static|super|switch|this|throw|try|type|typeof|undefined|var|void|while|with|yield)\b/,builtin:/\b(?:string|Function|any|number|boolean|Array|symbol|console|Promise|unknown|never)\b/}),delete e.languages.typescript.parameter;var t=e.languages.extend("typescript",{});delete t["class-name"],e.languages.typescript["class-name"].inside=t,e.languages.insertBefore("typescript","function",{"generic-function":{pattern:/#?(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*\s*<(?:[^<>]|<(?:[^<>]|<[^<>]*>)*>)*>(?=\s*\()/,greedy:!0,inside:{function:/^#?(?!\s)[_$a-zA-Z\xA0-\uFFFF](?:(?!\s)[$\w\xA0-\uFFFF])*/,generic:{pattern:/<[\s\S]+/,alias:"class-name",inside:t}}}}),e.languages.ts=e.languages.typescript}(o),function(e){var t=e.util.clone(e.languages.typescript);e.languages.tsx=e.languages.extend("jsx",t);var n=e.languages.tsx.tag;n.pattern=RegExp(/(^|[^\w$]|(?=<\/))/.source+"(?:"+n.pattern.source+")",n.pattern.flags),n.lookbehind=!0}(o),o.languages.wasm={comment:[/\(;[\s\S]*?;\)/,{pattern:/;;.*/,greedy:!0}],string:{pattern:/"(?:\\[\s\S]|[^"\\])*"/,greedy:!0},keyword:[{pattern:/\b(?:align|offset)=/,inside:{operator:/=/}},{pattern:/\b(?:(?:f32|f64|i32|i64)(?:\.(?:abs|add|and|ceil|clz|const|convert_[su]\/i(?:32|64)|copysign|ctz|demote\/f64|div(?:_[su])?|eqz?|extend_[su]\/i32|floor|ge(?:_[su])?|gt(?:_[su])?|le(?:_[su])?|load(?:(?:8|16|32)_[su])?|lt(?:_[su])?|max|min|mul|nearest|neg?|or|popcnt|promote\/f32|reinterpret\/[fi](?:32|64)|rem_[su]|rot[lr]|shl|shr_[su]|store(?:8|16|32)?|sqrt|sub|trunc(?:_[su]\/f(?:32|64))?|wrap\/i64|xor))?|memory\.(?:grow|size))\b/,inside:{punctuation:/\./}},/\b(?:anyfunc|block|br(?:_if|_table)?|call(?:_indirect)?|data|drop|elem|else|end|export|func|get_(?:global|local)|global|if|import|local|loop|memory|module|mut|nop|offset|param|result|return|select|set_(?:global|local)|start|table|tee_local|then|type|unreachable)\b/],variable:/\$[\w!#$%&'*+\-./:<=>?@\\^_`|~]+/i,number:/[+-]?\b(?:\d(?:_?\d)*(?:\.\d(?:_?\d)*)?(?:[eE][+-]?\d(?:_?\d)*)?|0x[\da-fA-F](?:_?[\da-fA-F])*(?:\.[\da-fA-F](?:_?[\da-fA-D])*)?(?:[pP][+-]?\d(?:_?\d)*)?)\b|\binf\b|\bnan(?::0x[\da-fA-F](?:_?[\da-fA-D])*)?\b/,punctuation:/[()]/},function(e){var t=/[*&][^\s[\]{},]+/,n=/!(?:<[\w\-%#;/?:@&=+$,.!~*'()[\]]+>|(?:[a-zA-Z\d-]*!)?[\w\-%#;/?:@&=+$.~*'()]+)?/,r="(?:"+n.source+"(?:[ \t]+"+t.source+")?|"+t.source+"(?:[ \t]+"+n.source+")?)",a=/(?:[^\s\x00-\x08\x0e-\x1f!"#%&'*,\-:>?@[\]`{|}\x7f-\x84\x86-\x9f\ud800-\udfff\ufffe\uffff]|[?:-])(?:[ \t]*(?:(?![#:])|:))*/.source.replace(//g,(function(){return/[^\s\x00-\x08\x0e-\x1f,[\]{}\x7f-\x84\x86-\x9f\ud800-\udfff\ufffe\uffff]/.source})),i=/"(?:[^"\\\r\n]|\\.)*"|'(?:[^'\\\r\n]|\\.)*'/.source;function o(e,t){t=(t||"").replace(/m/g,"")+"m";var n=/([:\-,[{]\s*(?:\s<>[ \t]+)?)(?:<>)(?=[ \t]*(?:$|,|]|}|(?:[\r\n]\s*)?#))/.source.replace(/<>/g,(function(){return r})).replace(/<>/g,(function(){return e}));return RegExp(n,t)}e.languages.yaml={scalar:{pattern:RegExp(/([\-:]\s*(?:\s<>[ \t]+)?[|>])[ \t]*(?:((?:\r?\n|\r)[ \t]+)\S[^\r\n]*(?:\2[^\r\n]+)*)/.source.replace(/<>/g,(function(){return r}))),lookbehind:!0,alias:"string"},comment:/#.*/,key:{pattern:RegExp(/((?:^|[:\-,[{\r\n?])[ \t]*(?:<>[ \t]+)?)<>(?=\s*:\s)/.source.replace(/<>/g,(function(){return r})).replace(/<>/g,(function(){return"(?:"+a+"|"+i+")"}))),lookbehind:!0,greedy:!0,alias:"atrule"},directive:{pattern:/(^[ \t]*)%.+/m,lookbehind:!0,alias:"important"},datetime:{pattern:o(/\d{4}-\d\d?-\d\d?(?:[tT]|[ \t]+)\d\d?:\d{2}:\d{2}(?:\.\d*)?(?:[ \t]*(?:Z|[-+]\d\d?(?::\d{2})?))?|\d{4}-\d{2}-\d{2}|\d\d?:\d{2}(?::\d{2}(?:\.\d*)?)?/.source),lookbehind:!0,alias:"number"},boolean:{pattern:o(/true|false/.source,"i"),lookbehind:!0,alias:"important"},null:{pattern:o(/null|~/.source,"i"),lookbehind:!0,alias:"important"},string:{pattern:o(i),lookbehind:!0,greedy:!0},number:{pattern:o(/[+-]?(?:0x[\da-f]+|0o[0-7]+|(?:\d+(?:\.\d*)?|\.?\d+)(?:e[+-]?\d+)?|\.inf|\.nan)/.source,"i"),lookbehind:!0},tag:n,important:t,punctuation:/---|[:[\]{}\-,|>?]|\.\.\./},e.languages.yml=e.languages.yaml}(o),t.a=o},SksO:function(e,t){function n(t,r){return e.exports=n=Object.setPrototypeOf||function(e,t){return e.__proto__=t,e},e.exports.default=e.exports,e.exports.__esModule=!0,n(t,r)}e.exports=n,e.exports.default=e.exports,e.exports.__esModule=!0},TJpk:function(e,t,n){t.__esModule=!0,t.Helmet=void 0;var r=Object.assign||function(e){for(var t=1;t=0||Object.prototype.hasOwnProperty.call(e,r)&&(n[r]=e[r]);return n}function f(e,t){if(!(e instanceof t))throw new TypeError("Cannot call a class as a function")}function g(e,t){if(!e)throw new ReferenceError("this hasn't been initialised - super() hasn't been called");return!t||"object"!=typeof t&&"function"!=typeof t?e:t}var m,h,y,b=(0,s.default)(l.reducePropsToState,l.handleClientStateChange,l.mapStateOnServer)((function(){return null})),A=(m=b,y=h=function(e){function t(){return f(this,t),g(this,e.apply(this,arguments))}return function(e,t){if("function"!=typeof t&&null!==t)throw new TypeError("Super expression must either be null or a function, not "+typeof t);e.prototype=Object.create(t&&t.prototype,{constructor:{value:e,enumerable:!1,writable:!0,configurable:!0}}),t&&(Object.setPrototypeOf?Object.setPrototypeOf(e,t):e.__proto__=t)}(t,e),t.prototype.shouldComponentUpdate=function(e){return!(0,c.default)(this.props,e)},t.prototype.mapNestedChildrenToProps=function(e,t){if(!t)return null;switch(e.type){case u.TAG_NAMES.SCRIPT:case u.TAG_NAMES.NOSCRIPT:return{innerHTML:t};case u.TAG_NAMES.STYLE:return{cssText:t}}throw new Error("<"+e.type+" /> elements are self-closing and can not contain children. Refer to our API for more information.")},t.prototype.flattenArrayTypeChildren=function(e){var t,n=e.child,a=e.arrayTypeChildren,i=e.newChildProps,o=e.nestedChildren;return r({},a,((t={})[n.type]=[].concat(a[n.type]||[],[r({},i,this.mapNestedChildrenToProps(n,o))]),t))},t.prototype.mapObjectTypeChildren=function(e){var t,n,a=e.child,i=e.newProps,o=e.newChildProps,s=e.nestedChildren;switch(a.type){case u.TAG_NAMES.TITLE:return r({},i,((t={})[a.type]=s,t.titleAttributes=r({},o),t));case u.TAG_NAMES.BODY:return r({},i,{bodyAttributes:r({},o)});case u.TAG_NAMES.HTML:return r({},i,{htmlAttributes:r({},o)})}return r({},i,((n={})[a.type]=r({},o),n))},t.prototype.mapArrayTypeChildrenToProps=function(e,t){var n=r({},t);return Object.keys(e).forEach((function(t){var a;n=r({},n,((a={})[t]=e[t],a))})),n},t.prototype.warnOnInvalidChildren=function(e,t){return!0},t.prototype.mapChildrenToProps=function(e,t){var n=this,r={};return i.default.Children.forEach(e,(function(e){if(e&&e.props){var a=e.props,i=a.children,o=p(a,["children"]),s=(0,l.convertReactPropstoHtmlAttributes)(o);switch(n.warnOnInvalidChildren(e,i),e.type){case u.TAG_NAMES.LINK:case u.TAG_NAMES.META:case u.TAG_NAMES.NOSCRIPT:case u.TAG_NAMES.SCRIPT:case u.TAG_NAMES.STYLE:r=n.flattenArrayTypeChildren({child:e,arrayTypeChildren:r,newChildProps:s,nestedChildren:i});break;default:t=n.mapObjectTypeChildren({child:e,newProps:t,newChildProps:s,nestedChildren:i})}}})),t=this.mapArrayTypeChildrenToProps(r,t)},t.prototype.render=function(){var e=this.props,t=e.children,n=p(e,["children"]),a=r({},n);return t&&(a=this.mapChildrenToProps(t,a)),i.default.createElement(m,a)},a(t,null,[{key:"canUseDOM",set:function(e){m.canUseDOM=e}}]),t}(i.default.Component),h.propTypes={base:o.default.object,bodyAttributes:o.default.object,children:o.default.oneOfType([o.default.arrayOf(o.default.node),o.default.node]),defaultTitle:o.default.string,defer:o.default.bool,encodeSpecialCharacters:o.default.bool,htmlAttributes:o.default.object,link:o.default.arrayOf(o.default.object),meta:o.default.arrayOf(o.default.object),noscript:o.default.arrayOf(o.default.object),onChangeClientState:o.default.func,script:o.default.arrayOf(o.default.object),style:o.default.arrayOf(o.default.object),title:o.default.string,titleAttributes:o.default.object,titleTemplate:o.default.string},h.defaultProps={defer:!0,encodeSpecialCharacters:!0},h.peek=m.peek,h.rewind=function(){var e=m.rewind();return e||(e=(0,l.mapStateOnServer)({baseTag:[],bodyAttributes:{},encodeSpecialCharacters:!0,htmlAttributes:{},linkTags:[],metaTags:[],noscriptTags:[],scriptTags:[],styleTags:[],title:"",titleAttributes:{}})),e},y);A.renderStatic=A.rewind,t.Helmet=A,t.default=A},TOwV:function(e,t,n){"use strict";e.exports=n("qT12")},TqRt:function(e,t){e.exports=function(e){return e&&e.__esModule?e:{default:e}},e.exports.default=e.exports,e.exports.__esModule=!0},TqVZ:function(e,t,n){"use strict";var r=n("z9I/");var a=function(e){function t(e,t,r){var a=t.trim().split(g);t=a;var i=a.length,o=e.length;switch(o){case 0:case 1:var s=0;for(e=0===o?"":e[0]+" ";sr&&(r=(t=t.trim()).charCodeAt(0)),r){case 38:return t.replace(m,"$1"+e.trim());case 58:return e.trim()+t.replace(m,"$1"+e.trim());default:if(0<1*n&&0c.charCodeAt(8))break;case 115:o=o.replace(c,"-webkit-"+c)+";"+o;break;case 207:case 102:o=o.replace(c,"-webkit-"+(102s.charCodeAt(0)&&(s=s.trim()),s=[s],0f)&&(B=(W=W.replace(" ",":")).length),00)return s[s.length-1];if(e&&e.location.pathname===a)return o?decodeURI(o.slice(1)):[0,0];return!0}var M=function(e){function t(t){var n;return(n=e.call(this,t)||this).announcementRef=s.a.createRef(),n}Object(a.a)(t,e);var n=t.prototype;return n.componentDidUpdate=function(e,t){var n=this;requestAnimationFrame((function(){var e="new page at "+n.props.location.pathname;document.title&&(e=document.title);var t=document.querySelectorAll("#gatsby-focus-wrapper h1");t&&t.length&&(e=t[0].textContent);var r="Navigated to "+e;n.announcementRef.current&&(n.announcementRef.current.innerText!==r&&(n.announcementRef.current.innerText=r))}))},n.render=function(){return Object(v.d)("div",Object(r.a)({},b,{ref:this.announcementRef}))},t}(s.a.Component),w=function(e,t){var n,r;return e.href!==t.href||(null==e||null===(n=e.state)||void 0===n?void 0:n.key)!==(null==t||null===(r=t.state)||void 0===r?void 0:r.key)},D=function(e){function t(t){var n;return n=e.call(this,t)||this,E(t.location,null),n}Object(a.a)(t,e);var n=t.prototype;return n.componentDidMount=function(){P(this.props.location,null)},n.shouldComponentUpdate=function(e){return!!w(e.location,this.props.location)&&(E(this.props.location,e.location),!0)},n.componentDidUpdate=function(e){w(e.location,this.props.location)&&P(this.props.location,e.location)},n.render=function(){return Object(v.d)(s.a.Fragment,null,this.props.children,Object(v.d)(M,{location:location}))},t}(s.a.Component),x=n("IOVJ"),k=n("NsGk"),L=n.n(k),F=n("rePB");function j(e,t){for(var n in e)if(!(n in t))return!0;for(var r in t)if(e[r]!==t[r])return!0;return!1}function N(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function _(e){for(var t=1;t0&&n("NSX3");var e=function(e){return Object(v.d)(u.BaseContext.Provider,{value:{baseuri:"/",basepath:"/"}},Object(v.d)(x.a,e))},t=s.a.createContext({}),o=function(e){function n(){return e.apply(this,arguments)||this}return Object(a.a)(n,e),n.prototype.render=function(){var e=this.props.children;return Object(v.d)(u.Location,null,(function(n){var r=n.location;return Object(v.d)(B,{location:r},(function(n){var r=n.pageResources,a=n.location,i=Object(m.getStaticQueryResults)();return Object(v.d)(g.StaticQueryContext.Provider,{value:i},Object(v.d)(t.Provider,{value:{pageResources:r,location:a}},e))}))}))},n}(s.a.Component),c=function(n){function i(){return n.apply(this,arguments)||this}return Object(a.a)(i,n),i.prototype.render=function(){var n=this;return Object(v.d)(t.Consumer,null,(function(t){var a=t.pageResources,i=t.location;return Object(v.d)(D,{location:i},Object(v.d)(d.ScrollContext,{location:i,shouldUpdateScroll:I},Object(v.d)(u.Router,{basepath:"",location:i,id:"gatsby-focus-wrapper"},Object(v.d)(e,Object(r.a)({path:"/404.html"===a.page.path?Object(G.a)(i.pathname,""):encodeURI(a.page.matchPath||a.page.path)},n.props,{location:i,pageResources:a},a.json)))))}))},i}(s.a.Component),p=window,h=p.pagePath,y=p.location;h&&""+h!==y.pathname&&!(W.findMatchPath(Object(G.a)(y.pathname,""))||"/404.html"===h||h.match(/^\/404\/?$/)||h.match(/^\/offline-plugin-app-shell-fallback\/?$/))&&Object(u.navigate)(""+h+y.search+y.hash,{replace:!0}),m.publicLoader.loadPage(y.pathname).then((function(e){if(!e||e.status===m.PageResourceStatus.Error)throw new Error("page resources for "+y.pathname+" not found. Not rendering React");window.___webpackCompilationHash=e.page.webpackCompilationHash;var t=Object(i.apiRunner)("wrapRootElement",{element:Object(v.d)(c,null)},Object(v.d)(c,null),(function(e){return{element:e.result}})).pop(),n=function(){return Object(v.d)(o,null,t)},r=Object(i.apiRunner)("replaceHydrateFunction",void 0,l.a.hydrate)[0];f()((function(){r(Object(v.d)(n,null),"undefined"!=typeof window?document.getElementById("___gatsby"):void 0,(function(){Object(i.apiRunner)("onInitialClientRender")}))}))}))}))},VX4j:function(e,t){e.exports="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAYAAADgdz34AAAABHNCSVQICAgIfAhkiAAAAAlwSFlzAAAApgAAAKYB3X3/OAAAABl0RVh0U29mdHdhcmUAd3d3Lmlua3NjYXBlLm9yZ5vuPBoAAANGSURBVEiJndVPbNRVEAfwz9vd/q8tBQtoxSYYDKYmejMGD3DxYloMiRoT22IEDQcPno3xoFclMf6JHrDFyIVEI3g2eiDoRWOMfygqNrSkoeAWCtIu230e3m+77e6KCZO8vH3zZuY7M+/7mxVjVFu7C+vPt7mmh4fi+eEDMUYFVZkdeZU7dhgIzxOj25ULe3fJx6PYamZkDYD4rRDmmgafDIdE3aIJbcrKxkQF4/GtBtuY/43KGVBxOsT/S3YijAomEVBCBe0geNlYfLfBZ3bfJmFlp7u/ONUcYCIMCw6jL1vhFikUURS9Zn88Vn9ZaOJA8DTuA3n0Zjm3ZlDL2VrASpZE8CwaABormAgPC75Cny7cmYE0kwou4Rq4IWeP0fhdc4DjIe+GD0QvIKcbmzOrtl56t9O2gRBYvsKVcyz9ne7nsQgiPhUdtD8uNVYwGRbQK497qu3ZzsYHUuB1EimepTiVKplBGZQM6rI7liFX5/Ur0rPmpYw3ZcEL7fRso3eQQgcCfffT0Z+i9K3GOFMNvh7gWOjDYGpJpuvbkQK1dND/IF1b6Oynf4jW7jU2a3zY6uPQ3whw0/u4S5DYIqsAOjdrkKqutSfbVcncL+ejOoAQsC39VGN9yOiTa8LmXIGOx8h11RxqzzTgeHLOAGKUM4pFFdzMzJYX0n79YiPAP/O0PUSlHTE9cCXdCJ7zVFxZA4DReA4/gKVMd/WvtJcWKf6e6FlapPgHS0UW3uPyN9b58IuxOFU91Ne+E+kL7cb1Oa5O0zPI0kJaa+XaLIszif21q4x2if+1ClLP/iRrUfYNufQTF79P2ceY2lFaZP5HLqaCFaUxmOSsT3RWD42j4mh4RnQEnTZYP+pCLh1Se2uZF0FZdNC0o16Plf8GgMnwOZ5Eot9GiefVmbQiDbtitif52njcUx+q+TSNTgoZQAlzddblJj7ByWah0htc2LvL7L5Nq9r98YhBLSo2481Vfbkh+DtytljWaiy+3QwgxOnhIfl4AmdoGTXw2eUGq8lwWNCDD1WUBC+hYNyLTf9iZ554RAiPG/jyjYKcR7E1wa3sxKkGh/H4Sp3mULNsVyVvTgxTqYIYmRk5oOK0e0/8fEvH25B/AZyRWA6LDlu9AAAAAElFTkSuQmCC"},VbXa:function(e,t,n){var r=n("SksO");e.exports=function(e,t){e.prototype=Object.create(t.prototype),e.prototype.constructor=e,r(e,t)},e.exports.default=e.exports,e.exports.__esModule=!0},Wbzz:function(e,t,n){"use strict";n.r(t),n.d(t,"graphql",(function(){return y})),n.d(t,"StaticQueryContext",(function(){return f})),n.d(t,"StaticQuery",(function(){return m})),n.d(t,"useStaticQuery",(function(){return h})),n.d(t,"prefetchPathname",(function(){return p}));var r=n("q1tI"),a=n.n(r),i=n("+ZDr"),o=n.n(i);n.d(t,"Link",(function(){return o.a})),n.d(t,"withAssetPrefix",(function(){return i.withAssetPrefix})),n.d(t,"withPrefix",(function(){return i.withPrefix})),n.d(t,"parsePath",(function(){return i.parsePath})),n.d(t,"navigate",(function(){return i.navigate})),n.d(t,"push",(function(){return i.push})),n.d(t,"replace",(function(){return i.replace})),n.d(t,"navigateTo",(function(){return i.navigateTo}));var s=n("7hJ6");n.d(t,"useScrollRestoration",(function(){return s.useScrollRestoration}));var c=n("lw3w"),l=n.n(c);n.d(t,"PageRenderer",(function(){return l.a}));var u=n("emEt"),d=n("qKvR"),p=u.default.enqueue,f=a.a.createContext({});function g(e){var t=e.staticQueryData,n=e.data,r=e.query,i=e.render,o=n?n.data:t[r]&&t[r].data;return Object(d.d)(a.a.Fragment,null,o&&i(o),!o&&Object(d.d)("div",null,"Loading (StaticQuery)"))}var m=function(e){var t=e.data,n=e.query,r=e.render,a=e.children;return Object(d.d)(f.Consumer,null,(function(e){return Object(d.d)(g,{data:t,query:n,render:r||a,staticQueryData:e})}))},h=function(e){var t;a.a.useContext;var n=a.a.useContext(f);if(isNaN(Number(e)))throw new Error("useStaticQuery was called with a string but expects to be called using `graphql`. Try this:\n\nimport { useStaticQuery, graphql } from 'gatsby';\n\nuseStaticQuery(graphql`"+e+"`);\n");if(null!==(t=n[e])&&void 0!==t&&t.data)return n[e].data;throw new Error("The result of this StaticQuery could not be fetched.\n\nThis is likely a bug in Gatsby and if refreshing the page does not fix it, please open an issue in https://github.com/gatsbyjs/gatsby/issues")};function y(){throw new Error("It appears like Gatsby is misconfigured. Gatsby related `graphql` calls are supposed to only be evaluated at compile time, and then compiled away. Unfortunately, something went wrong and the query was left in the compiled code.\n\nUnless your site has a complex or custom babel/Gatsby configuration this is likely a bug in Gatsby.")}},WkPL:function(e,t){e.exports=function(e,t){(null==t||t>e.length)&&(t=e.length);for(var n=0,r=new Array(t);n=0||Object.prototype.hasOwnProperty.call(e,r)&&(n[r]=e[r]);return n}function g(e,t){if(!(e instanceof t))throw new TypeError("Cannot call a class as a function")}function m(e,t){if(!e)throw new ReferenceError("this hasn't been initialised - super() hasn't been called");return!t||"object"!=typeof t&&"function"!=typeof t?e:t}function h(e,t){if("function"!=typeof t&&null!==t)throw new TypeError("Super expression must either be null or a function, not "+typeof t);e.prototype=Object.create(t&&t.prototype,{constructor:{value:e,enumerable:!1,writable:!0,configurable:!0}}),t&&(Object.setPrototypeOf?Object.setPrototypeOf(e,t):e.__proto__=t)}var y=function(e,t){var n=c()(t);return n.displayName=e,n},b=y("Location"),A=function(e){var t=e.children;return a.a.createElement(b.Consumer,null,(function(e){return e?t(e):a.a.createElement(S,null,t)}))},S=function(e){function t(){var n,r;g(this,t);for(var a=arguments.length,i=Array(a),o=0;o-1?(i=t.substring(0,r),o=t.substring(r)):i=t,a.a.createElement(b.Provider,{value:{location:{pathname:i,search:o,hash:""},navigate:function(){throw new Error("You can't call navigate on the server.")}}},n)},O=y("Base",{baseuri:"/",basepath:"/"}),C=function(e){return a.a.createElement(O.Consumer,null,(function(t){return a.a.createElement(A,null,(function(n){return a.a.createElement(T,p({},t,n,e))}))}))},T=function(e){function t(){return g(this,t),m(this,e.apply(this,arguments))}return h(t,e),t.prototype.render=function(){var e=this.props,t=e.location,n=e.navigate,r=e.basepath,i=e.primary,o=e.children,s=(e.baseuri,e.component),c=void 0===s?"div":s,l=f(e,["location","navigate","basepath","primary","children","baseuri","component"]),d=a.a.Children.toArray(o).reduce((function(e,t){var n=H(r)(t);return e.concat(n)}),[]),g=t.pathname,m=Object(u.pick)(d,g);if(m){var h=m.params,y=m.uri,b=m.route,A=m.route.value;r=b.default?r:b.path.replace(/\*$/,"");var S=p({},h,{uri:y,location:t,navigate:function(e,t){return n(Object(u.resolve)(e,y),t)}}),v=a.a.cloneElement(A,S,A.props.children?a.a.createElement(C,{location:t,primary:i},A.props.children):void 0),T=i?P:c,E=i?p({uri:y,location:t,component:c},l):l;return a.a.createElement(O.Provider,{value:{baseuri:y,basepath:r}},a.a.createElement(T,E,v))}return null},t}(a.a.PureComponent);T.defaultProps={primary:!0};var E=y("Focus"),P=function(e){var t=e.uri,n=e.location,r=e.component,i=f(e,["uri","location","component"]);return a.a.createElement(E.Consumer,null,(function(e){return a.a.createElement(M,p({},i,{component:r,requestFocus:e,uri:t,location:n}))}))},R=!0,I=0,M=function(e){function t(){var n,r;g(this,t);for(var a=arguments.length,i=Array(a),o=0;oe.length)&&(t=e.length);for(var n=0,r=new Array(t);nAFOTEC OT&E Guide",githubUrl:"",helpUrl:"",tweetText:"",links:[{text:"",link:""}],search:{enabled:!0,indexName:"il2_guide",algoliaAppId:"8WYYTT6SZL",algoliaSearchKey:"cbce654033659a526bb5fcd00086ebcc",algoliaAdminKey:{}.ALGOLIA_ADMIN_KEY}},sidebar:{forcedNavOrder:["/OT&E_Guide","/fn_guides","/OTE_construct_development_guide","/accreditation_guide","/analyst_test_design_guide","/editing_reports_guide","/evaluation_and_reporting_guide","/lessons_learned_guide","/measures_guide","/safety_risk_mgmt_guide","/strat_planning_programming_guide","/test_capability_guide","/acronyms","/glossary"],collapsedNav:["/OT&E_Guide","/OTE_construct_development_guide","/OTE_construct_development_guide","/accreditation_guide","/analyst_test_design_guide","/editing_reports_guide","/evaluation_and_reporting_guide","/lessons_learned_guide","/measures_guide","/safety_risk_mgmt_guide","/strat_planning_programming_guide","/test_capability_guide"],links:[{text:"AFOTEC",link:"https://www.afotec.af.mil"},{text:"Cyber Support Package Guide",link:"https://usaf.dps.mil/:w:/r/sites/AFOTEC-PRIVATE/mainlibrary/oteguide/Shared%20Documents/Functional%20Guides/AFOTEC%20Cyber%20Support%20Package%20Guide.docx?d=wa256f83b0e4c475485e72f4a383f81a3&csf=1&web=1&e=C2RUBJ"},{text:"Risk Assessment and Level of Test (RALOT) Guide",link:"https://cs2.eis.af.mil/sites/10008/library/jobaidsguides/AFOTEC%20RALOT%20Guide%20Template.dotx?Web=1"},{text:"OT&E Templates/Job Aids",link:"https://usaf.dps.mil/sites/AFOTEC-PRIVATE/mainlibrary/"},{text:"OT&E Tools Catalog",link:"https://usaf.dps.mil/sites/AFOTEC-PRIVATE/mainlibrary/oteguide/SitePages/Tools-Page.aspx"}],frontline:!0,ignoreIndex:!0,title:""},siteMetadata:{title:"AFOTEC OT&E Guide",description:"Air Force Operational Test and Evaluation Guide",ogImage:null,docsLocation:"",favicon:"https://raw.githubusercontent.com/Travis42/misc/main/favicon.ico"},pwa:{enabled:!1,manifest:{name:"AFOTEC OT&E Guide",short_name:"OT&E Guide",start_url:"/",background_color:"#6b37bf",theme_color:"#6b37bf",display:"standalone",crossOrigin:"use-credentials",icons:[{src:"src/pwa-512.png",sizes:"512x512",type:"image/png"}]}}};e.exports=n},oxjq:function(e,t,n){"use strict";var r=/[|\\{}()[\]^$+*?.]/g;e.exports=function(e){if("string"!=typeof e)throw new TypeError("Expected a string");return e.replace(r,"\\$&")}},pVnL:function(e,t){function n(){return e.exports=n=Object.assign||function(e){for(var t=1;t1&&void 0!==arguments[1])||arguments[1];return!1===t?String(e):String(e).replace(/&/g,"&").replace(//g,">").replace(/"/g,""").replace(/'/g,"'")},d=function(e){var t=h(e,s.TAG_NAMES.TITLE),n=h(e,s.HELMET_PROPS.TITLE_TEMPLATE);if(n&&t)return n.replace(/%s/g,(function(){return t}));var r=h(e,s.HELMET_PROPS.DEFAULT_TITLE);return t||r||void 0},p=function(e){return h(e,s.HELMET_PROPS.ON_CHANGE_CLIENT_STATE)||function(){}},f=function(e,t){return t.filter((function(t){return void 0!==t[e]})).map((function(t){return t[e]})).reduce((function(e,t){return a({},e,t)}),{})},g=function(e,t){return t.filter((function(e){return void 0!==e[s.TAG_NAMES.BASE]})).map((function(e){return e[s.TAG_NAMES.BASE]})).reverse().reduce((function(t,n){if(!t.length)for(var r=Object.keys(n),a=0;a=0;n--){var r=e[n];if(r.hasOwnProperty(t))return r[t]}return null},y=(l=Date.now(),function(e){var t=Date.now();t-l>16?(l=t,e(t)):setTimeout((function(){y(e)}),0)}),b=function(e){return clearTimeout(e)},A="undefined"!=typeof window?window.requestAnimationFrame||window.webkitRequestAnimationFrame||window.mozRequestAnimationFrame||y:e.requestAnimationFrame||y,S="undefined"!=typeof window?window.cancelAnimationFrame||window.webkitCancelAnimationFrame||window.mozCancelAnimationFrame||b:e.cancelAnimationFrame||b,v=function(e){return console&&"function"==typeof console.warn&&console.warn(e)},O=null,C=function(e,t){var n=e.baseTag,r=e.bodyAttributes,a=e.htmlAttributes,i=e.linkTags,o=e.metaTags,c=e.noscriptTags,l=e.onChangeClientState,u=e.scriptTags,d=e.styleTags,p=e.title,f=e.titleAttributes;P(s.TAG_NAMES.BODY,r),P(s.TAG_NAMES.HTML,a),E(p,f);var g={baseTag:R(s.TAG_NAMES.BASE,n),linkTags:R(s.TAG_NAMES.LINK,i),metaTags:R(s.TAG_NAMES.META,o),noscriptTags:R(s.TAG_NAMES.NOSCRIPT,c),scriptTags:R(s.TAG_NAMES.SCRIPT,u),styleTags:R(s.TAG_NAMES.STYLE,d)},m={},h={};Object.keys(g).forEach((function(e){var t=g[e],n=t.newTags,r=t.oldTags;n.length&&(m[e]=n),r.length&&(h[e]=g[e].oldTags)})),t&&t(),l(e,m,h)},T=function(e){return Array.isArray(e)?e.join(""):e},E=function(e,t){void 0!==e&&document.title!==e&&(document.title=T(e)),P(s.TAG_NAMES.TITLE,t)},P=function(e,t){var n=document.getElementsByTagName(e)[0];if(n){for(var r=n.getAttribute(s.HELMET_ATTRIBUTE),a=r?r.split(","):[],i=[].concat(a),o=Object.keys(t),c=0;c=0;p--)n.removeAttribute(i[p]);a.length===i.length?n.removeAttribute(s.HELMET_ATTRIBUTE):n.getAttribute(s.HELMET_ATTRIBUTE)!==o.join(",")&&n.setAttribute(s.HELMET_ATTRIBUTE,o.join(","))}},R=function(e,t){var n=document.head||document.querySelector(s.TAG_NAMES.HEAD),r=n.querySelectorAll(e+"["+s.HELMET_ATTRIBUTE+"]"),a=Array.prototype.slice.call(r),i=[],o=void 0;return t&&t.length&&t.forEach((function(t){var n=document.createElement(e);for(var r in t)if(t.hasOwnProperty(r))if(r===s.TAG_PROPERTIES.INNER_HTML)n.innerHTML=t.innerHTML;else if(r===s.TAG_PROPERTIES.CSS_TEXT)n.styleSheet?n.styleSheet.cssText=t.cssText:n.appendChild(document.createTextNode(t.cssText));else{var c=void 0===t[r]?"":t[r];n.setAttribute(r,c)}n.setAttribute(s.HELMET_ATTRIBUTE,"true"),a.some((function(e,t){return o=t,n.isEqualNode(e)}))?a.splice(o,1):i.push(n)})),a.forEach((function(e){return e.parentNode.removeChild(e)})),i.forEach((function(e){return n.appendChild(e)})),{oldTags:a,newTags:i}},I=function(e){return Object.keys(e).reduce((function(t,n){var r=void 0!==e[n]?n+'="'+e[n]+'"':""+n;return t?t+" "+r:r}),"")},M=function(e){var t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:{};return Object.keys(e).reduce((function(t,n){return t[s.REACT_TAG_MAP[n]||n]=e[n],t}),t)},w=function(e,t,n){switch(e){case s.TAG_NAMES.TITLE:return{toComponent:function(){return e=t.title,n=t.titleAttributes,(r={key:e})[s.HELMET_ATTRIBUTE]=!0,a=M(n,r),[i.default.createElement(s.TAG_NAMES.TITLE,a,e)];var e,n,r,a},toString:function(){return function(e,t,n,r){var a=I(n),i=T(t);return a?"<"+e+" "+s.HELMET_ATTRIBUTE+'="true" '+a+">"+u(i,r)+"":"<"+e+" "+s.HELMET_ATTRIBUTE+'="true">'+u(i,r)+""}(e,t.title,t.titleAttributes,n)}};case s.ATTRIBUTE_NAMES.BODY:case s.ATTRIBUTE_NAMES.HTML:return{toComponent:function(){return M(t)},toString:function(){return I(t)}};default:return{toComponent:function(){return function(e,t){return t.map((function(t,n){var r,a=((r={key:n})[s.HELMET_ATTRIBUTE]=!0,r);return Object.keys(t).forEach((function(e){var n=s.REACT_TAG_MAP[e]||e;if(n===s.TAG_PROPERTIES.INNER_HTML||n===s.TAG_PROPERTIES.CSS_TEXT){var r=t.innerHTML||t.cssText;a.dangerouslySetInnerHTML={__html:r}}else a[n]=t[e]})),i.default.createElement(e,a)}))}(e,t)},toString:function(){return function(e,t,n){return t.reduce((function(t,r){var a=Object.keys(r).filter((function(e){return!(e===s.TAG_PROPERTIES.INNER_HTML||e===s.TAG_PROPERTIES.CSS_TEXT)})).reduce((function(e,t){var a=void 0===r[t]?t:t+'="'+u(r[t],n)+'"';return e?e+" "+a:a}),""),i=r.innerHTML||r.cssText||"",o=-1===s.SELF_CLOSING_TAGS.indexOf(e);return t+"<"+e+" "+s.HELMET_ATTRIBUTE+'="true" '+a+(o?"/>":">"+i+"")}),"")}(e,t,n)}}}};t.convertReactPropstoHtmlAttributes=function(e){var t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:{};return Object.keys(e).reduce((function(t,n){return t[s.HTML_TAG_MAP[n]||n]=e[n],t}),t)},t.handleClientStateChange=function(e){O&&S(O),e.defer?O=A((function(){C(e,(function(){O=null}))})):(C(e),O=null)},t.mapStateOnServer=function(e){var t=e.baseTag,n=e.bodyAttributes,r=e.encode,a=e.htmlAttributes,i=e.linkTags,o=e.metaTags,c=e.noscriptTags,l=e.scriptTags,u=e.styleTags,d=e.title,p=void 0===d?"":d,f=e.titleAttributes;return{base:w(s.TAG_NAMES.BASE,t,r),bodyAttributes:w(s.ATTRIBUTE_NAMES.BODY,n,r),htmlAttributes:w(s.ATTRIBUTE_NAMES.HTML,a,r),link:w(s.TAG_NAMES.LINK,i,r),meta:w(s.TAG_NAMES.META,o,r),noscript:w(s.TAG_NAMES.NOSCRIPT,c,r),script:w(s.TAG_NAMES.SCRIPT,l,r),style:w(s.TAG_NAMES.STYLE,u,r),title:w(s.TAG_NAMES.TITLE,{title:p,titleAttributes:f},r)}},t.reducePropsToState=function(e){return{baseTag:g([s.TAG_PROPERTIES.HREF],e),bodyAttributes:f(s.ATTRIBUTE_NAMES.BODY,e),defer:h(e,s.HELMET_PROPS.DEFER),encode:h(e,s.HELMET_PROPS.ENCODE_SPECIAL_CHARACTERS),htmlAttributes:f(s.ATTRIBUTE_NAMES.HTML,e),linkTags:m(s.TAG_NAMES.LINK,[s.TAG_PROPERTIES.REL,s.TAG_PROPERTIES.HREF],e),metaTags:m(s.TAG_NAMES.META,[s.TAG_PROPERTIES.NAME,s.TAG_PROPERTIES.CHARSET,s.TAG_PROPERTIES.HTTPEQUIV,s.TAG_PROPERTIES.PROPERTY,s.TAG_PROPERTIES.ITEM_PROP],e),noscriptTags:m(s.TAG_NAMES.NOSCRIPT,[s.TAG_PROPERTIES.INNER_HTML],e),onChangeClientState:p(e),scriptTags:m(s.TAG_NAMES.SCRIPT,[s.TAG_PROPERTIES.SRC,s.TAG_PROPERTIES.INNER_HTML],e),styleTags:m(s.TAG_NAMES.STYLE,[s.TAG_PROPERTIES.CSS_TEXT],e),title:d(e),titleAttributes:f(s.ATTRIBUTE_NAMES.TITLE,e)}},t.requestAnimationFrame=A,t.warn=v}).call(this,n("yLpj"))},vg9a:function(e,t,n){},wTIg:function(e,t,n){"use strict";var r=n("lSNA"),a=n.n(r),i=n("q1tI"),o=n("9uj6"),s=n("qKvR"),c=n("SIPS"),l=n("MiSq"),u=o.a,d=function(e){return"theme"!==e&&"innerRef"!==e},p=function(e){return"string"==typeof e&&e.charCodeAt(0)>96?u:d};function f(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function g(e){for(var t=1;t0?u:n?[n]:[]},t.apiRunnerAsync=function(e,t,n){return r.reduce((function(n,r){return r.plugin[e]?n.then((function(){return r.plugin[e](t,r.options)})):n}),Promise.resolve())}},yHiX:function(e,t,n){"use strict";var r,a,i=n("q1tI");try{a=n("RJKl"),r=a&&a.default||a}catch(o){throw-1!==o.toString().indexOf("Error: Cannot find module")?new Error("Couldn't find layout component at \"/home/t42/Documents/programming/Projects/OT_Guide/IL-2 Guide/src/templates/docs.js.\n\nPlease create layout component in that location or specify path to layout component in gatsby-config.js"):(console.error(o),o)}e.exports=function(e){var t=e.element,n=e.props;return i.createElement(r,n,t)}},yJwK:function(e,t,n){"use strict";e.exports=function(e,t,n,r,a,i,o,s){if(!e){var c;if(void 0===t)c=new Error("Minified exception occurred; use the non-minified dev environment for the full error message and additional helpful warnings.");else{var l=[n,r,a,i,o,s],u=0;(c=new Error(t.replace(/%s/g,(function(){return l[u++]})))).name="Invariant Violation"}throw c.framesToPop=1,c}}},"z9I/":function(e,t,n){"use strict";n.d(t,"a",(function(){return r}));var r=function(){function e(e){this.isSpeedy=void 0===e.speedy||e.speedy,this.tags=[],this.ctr=0,this.nonce=e.nonce,this.key=e.key,this.container=e.container,this.before=null}var t=e.prototype;return t.insert=function(e){if(this.ctr%(this.isSpeedy?65e3:1)==0){var t,n=function(e){var t=document.createElement("style");return t.setAttribute("data-emotion",e.key),void 0!==e.nonce&&t.setAttribute("nonce",e.nonce),t.appendChild(document.createTextNode("")),t}(this);t=0===this.tags.length?this.before:this.tags[this.tags.length-1].nextSibling,this.container.insertBefore(n,t),this.tags.push(n)}var r=this.tags[this.tags.length-1];if(this.isSpeedy){var a=function(e){if(e.sheet)return e.sheet;for(var t=0;t=0||(a[n]=e[n]);return a}n.d(t,"a",(function(){return r}))}},[["UxWs",1,5,7,0]]]); +//# sourceMappingURL=app-03e333c274b6bc210459.js.map \ No newline at end of file diff --git a/sites/oteguide/app-eec04d2f552ddc7b4bf2.js.LICENSE.txt b/sites/oteguide/app-03e333c274b6bc210459.js.LICENSE.txt similarity index 100% rename from sites/oteguide/app-eec04d2f552ddc7b4bf2.js.LICENSE.txt rename to sites/oteguide/app-03e333c274b6bc210459.js.LICENSE.txt diff --git a/sites/oteguide/app-03e333c274b6bc210459.js.map b/sites/oteguide/app-03e333c274b6bc210459.js.map new file mode 100644 index 00000000..9b333a01 --- /dev/null +++ b/sites/oteguide/app-03e333c274b6bc210459.js.map @@ -0,0 +1 @@ +{"version":3,"sources":["webpack:///./node_modules/gatsby-link/index.js","webpack:///./node_modules/gatsby-react-router-scroll/session-storage.js","webpack:///./node_modules/@babel/runtime/helpers/interopRequireWildcard.js","webpack:///./node_modules/hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js","webpack:///./.cache/normalize-page-path.js","webpack:///./.cache/find-path.js","webpack:///./node_modules/prism-react-renderer/themes/duotoneDark/index.js","webpack:///./node_modules/prism-react-renderer/dist/index.js","webpack:///./src/components/images/twitter-brands-block.svg","webpack:///./node_modules/gatsby-react-router-scroll/use-scroll-restoration.js","webpack:///./node_modules/@emotion/memoize/dist/memoize.browser.esm.js","webpack:///./node_modules/mitt/dist/mitt.es.js","webpack:///./.cache/emitter.js","webpack:///./node_modules/gatsby-react-router-scroll/index.js","webpack:///./node_modules/@mdx-js/react/dist/esm.js","webpack:///./node_modules/react-side-effect/lib/index.js","webpack:///./node_modules/@babel/runtime/helpers/objectWithoutPropertiesLoose.js","webpack:///./.cache/react-lifecycles-compat.js","webpack:///./node_modules/@reach/router/es/lib/history.js","webpack:///./node_modules/@emotion/is-prop-valid/dist/is-prop-valid.browser.esm.js","webpack:///./src/components/images/twitter.svg","webpack:///./node_modules/gatsby-plugin-catch-links/gatsby-browser.js","webpack:///./node_modules/gatsby-plugin-mdx/context.js","webpack:///./node_modules/@babel/runtime/helpers/nonIterableSpread.js","webpack:///./node_modules/@babel/runtime/helpers/esm/unsupportedIterableToArray.js","webpack:///./node_modules/react-loadable/lib/index.js","webpack:///./node_modules/@babel/runtime/helpers/iterableToArray.js","webpack:///./node_modules/gatsby-react-router-scroll/scroll-handler.js","webpack:///./gatsby-browser.js","webpack:///./node_modules/shallowequal/index.js","webpack:///./.cache/page-renderer.js","webpack:///./node_modules/@babel/runtime/helpers/arrayWithoutHoles.js","webpack:///./.cache/caches/gatsby-plugin-mdx/mdx-scopes-dir/e92f8988d65cf25c087d226e6c0ef06f.js","webpack:///./node_modules/@babel/runtime/helpers/esm/toConsumableArray.js","webpack:///./node_modules/@babel/runtime/helpers/esm/arrayWithoutHoles.js","webpack:///./node_modules/@babel/runtime/helpers/esm/iterableToArray.js","webpack:///./node_modules/@babel/runtime/helpers/esm/nonIterableSpread.js","webpack:///./node_modules/@reach/router/es/lib/utils.js","webpack:///./.cache/api-runner-browser-plugins.js","webpack:///./src/components/images/logo.svg","webpack:///./node_modules/@emotion/unitless/dist/unitless.browser.esm.js","webpack:///./node_modules/@mikaelkristiansson/domready/ready.js","webpack:///./node_modules/@emotion/hash/dist/hash.browser.esm.js","webpack:///./node_modules/@emotion/serialize/dist/serialize.browser.esm.js","webpack:///./.cache/register-service-worker.js","webpack:///./.cache/_this_is_virtual_fs_path_/$virtual/async-requires.js","webpack:///./node_modules/@babel/runtime/helpers/assertThisInitialized.js","webpack:///./node_modules/is-absolute-url/index.js","webpack:///./node_modules/@babel/runtime/helpers/toConsumableArray.js","webpack:///./node_modules/prism-react-renderer/themes/vsDark/index.js","webpack:///./src/components/mdxComponents/loading.js","webpack:///./src/components/mdxComponents/codeBlock.js","webpack:///./src/components/mdxComponents/anchor.js","webpack:///./src/components/mdxComponents/index.js","webpack:///./node_modules/emotion-theming/dist/emotion-theming.browser.esm.js","webpack:///./src/components/theme/index.js","webpack:///./src/components/link.js","webpack:///./src/components/DarkModeSwitch.js","webpack:///./src/components/images/opened.js","webpack:///./src/components/images/closed.js","webpack:///./src/components/sidebar/treeNode.js","webpack:///./src/components/sidebar/tree.js","webpack:///./node_modules/react-feather/dist/icons/external-link.js","webpack:///./src/components/sidebar/index.js","webpack:///./src/components/Header.js","webpack:///./node_modules/create-emotion/dist/create-emotion.browser.esm.js","webpack:///./node_modules/emotion/dist/emotion.esm.js","webpack:///./src/components/styles/GlobalStyles.js","webpack:///./src/components/theme/themeProvider.js","webpack:///./src/components/styles/Sidebar.js","webpack:///./src/components/rightSidebar.js","webpack:///./src/components/layout.js","webpack:///./src/components/styles/PageNavigationButtons.js","webpack:///./src/components/NextPrevious.js","webpack:///./src/components/styles/Docs.js","webpack:///./src/templates/MobileScrollUpButton.js","webpack:///./src/templates/docs.js","webpack:///./node_modules/@emotion/utils/dist/utils.browser.esm.js","webpack:///./node_modules/prism-react-renderer/prism/index.js","webpack:///./node_modules/@babel/runtime/helpers/setPrototypeOf.js","webpack:///./node_modules/react-helmet/lib/Helmet.js","webpack:///./node_modules/react-is/index.js","webpack:///./node_modules/@babel/runtime/helpers/interopRequireDefault.js","webpack:///./node_modules/@emotion/stylis/dist/stylis.browser.esm.js","webpack:///./node_modules/@emotion/cache/dist/cache.browser.esm.js","webpack:///./.cache/route-announcer-props.js","webpack:///./.cache/navigation.js","webpack:///./node_modules/shallow-compare/es/index.js","webpack:///./.cache/ensure-resources.js","webpack:///./.cache/production-app.js","webpack:///./src/components/images/day.png","webpack:///./node_modules/@babel/runtime/helpers/inheritsLoose.js","webpack:///./.cache/gatsby-browser-entry.js","webpack:///./node_modules/@babel/runtime/helpers/arrayLikeToArray.js","webpack:///./node_modules/gatsby-plugin-mdx/mdx-renderer.js","webpack:///./src/components/images/night.png","webpack:///./node_modules/gatsby/dist/internal-plugins/bundle-optimisations/polyfills/object-assign.js","webpack:///./node_modules/@reach/router/es/index.js","webpack:///./src/components/images/help.svg","webpack:///./node_modules/@babel/runtime/helpers/unsupportedIterableToArray.js","webpack:///./node_modules/@babel/runtime/helpers/esm/arrayLikeToArray.js","webpack:///./src/components/images/discord-brands-block.svg","webpack:///./node_modules/@babel/runtime/helpers/isNativeReflectConstruct.js","webpack:///./node_modules/gatsby-plugin-gtag/gatsby-browser.js","webpack:///./node_modules/react-fast-compare/index.js","webpack:///./node_modules/@babel/runtime/helpers/typeof.js","webpack:///./.cache/strip-prefix.js","webpack:///./node_modules/gatsby-link/parse-path.js","webpack:///./node_modules/@babel/runtime/helpers/esm/inheritsLoose.js","webpack:///./.cache/prefetch.js","webpack:///./.cache/loader.js","webpack:///./node_modules/gatsby-plugin-mdx/loaders/mdx-scopes.js","webpack:///./node_modules/gatsby-plugin-mdx/wrap-root-element.js","webpack:///./node_modules/gatsby-plugin-mdx/gatsby-browser.js","webpack:///./node_modules/@emotion/weak-memoize/dist/weak-memoize.browser.esm.js","webpack:///./node_modules/gatsby-plugin-layout/gatsby-browser.js","webpack:///./node_modules/gatsby-plugin-mdx/loaders/mdx-components.js","webpack:///./node_modules/react-helmet/lib/HelmetConstants.js","webpack:///./node_modules/gatsby-react-router-scroll/scroll-container.js","webpack:///./node_modules/gatsby-plugin-catch-links/catch-links.js","webpack:///./node_modules/@babel/runtime/helpers/defineProperty.js","webpack:///./.cache/public-page-renderer.js","webpack:///./.cache/create-react-context.js","webpack:///./config.js","webpack:///./node_modules/escape-string-regexp/index.js","webpack:///./node_modules/@babel/runtime/helpers/extends.js","webpack:///./node_modules/@emotion/core/dist/emotion-element-57a3a7a3.browser.esm.js","webpack:///./node_modules/@emotion/css/dist/css.browser.esm.js","webpack:///./node_modules/@emotion/core/dist/core.browser.esm.js","webpack:///./node_modules/react-is/cjs/react-is.production.min.js","webpack:///./node_modules/@babel/runtime/helpers/esm/defineProperty.js","webpack:///./.cache/public-page-renderer-prod.js","webpack:///./node_modules/@babel/runtime/helpers/esm/setPrototypeOf.js","webpack:///./node_modules/@babel/runtime/helpers/construct.js","webpack:///./node_modules/react-helmet/lib/HelmetUtils.js","webpack:///./node_modules/@emotion/styled-base/dist/styled-base.browser.esm.js","webpack:///./node_modules/@babel/runtime/helpers/esm/extends.js","webpack:///./.cache/api-runner-browser.js","webpack:///./node_modules/gatsby-plugin-layout/wrap-page.js","webpack:///./node_modules/@reach/router/node_modules/invariant/browser.js","webpack:///./node_modules/@emotion/sheet/dist/sheet.browser.esm.js","webpack:///./node_modules/@babel/runtime/helpers/esm/objectWithoutPropertiesLoose.js"],"names":["_interopRequireDefault","require","exports","__esModule","withPrefix","withAssetPrefix","path","getGlobalPathPrefix","navigateTo","replace","push","navigate","default","_objectWithoutPropertiesLoose2","_assertThisInitialized2","_inheritsLoose2","_extends2","_propTypes","_react","_router","_utils","_parsePath","parsePath","isAbsolutePath","startsWith","prefix","_ref","_prefix","getGlobalBasePrefix","isLocalLink","base","endsWith","slice","__PATH_PREFIX__","__BASE_PATH__","rewriteLinkPath","relativeTo","current","resolve","absolutify","NavLinkPropTypes","activeClassName","string","activeStyle","object","partiallyActive","bool","GatsbyLinkLocationWrapper","props","createElement","Location","_ref2","location","GatsbyLink","_location","_React$Component","_this","call","this","defaultGetProps","_ref3","isPartiallyCurrent","isCurrent","className","filter","Boolean","join","style","IOSupported","window","IntersectionObserver","state","handleRef","bind","_proto","prototype","_prefetch","currentPath","pathname","rewrittenPath","to","newPathName","___loader","enqueue","componentDidUpdate","prevProps","prevState","componentDidMount","componentWillUnmount","io","_this$io","instance","el","unobserve","disconnect","ref","cb","_this2","innerRef","hasOwnProperty","entries","forEach","entry","target","isIntersecting","intersectionRatio","observe","render","_this3","_this$props","_this$props$getProps","getProps","_onClick","onClick","_onMouseEnter","onMouseEnter","rest","prefixedTo","Link","e","hovering","button","defaultPrevented","metaKey","altKey","ctrlKey","shiftKey","preventDefault","shouldReplace","encodeURI","___navigate","href","Component","propTypes","func","isRequired","showDeprecationWarning","functionName","altFunctionName","version","console","warn","_default","forwardRef","options","___push","___replace","SessionStorage","read","key","stateKey","getStateKey","value","sessionStorage","getItem","JSON","parse","save","storedValue","stringify","setItem","stateKeyBase","_typeof","_getRequireWildcardCache","WeakMap","cache","module","obj","has","get","newObj","hasPropertyDescriptor","Object","defineProperty","getOwnPropertyDescriptor","desc","set","reactIs","REACT_STATICS","childContextTypes","contextType","contextTypes","defaultProps","displayName","getDefaultProps","getDerivedStateFromError","getDerivedStateFromProps","mixins","type","KNOWN_STATICS","name","length","caller","callee","arguments","arity","MEMO_STATICS","compare","TYPE_STATICS","getStatics","component","isMemo","ForwardRef","Memo","getOwnPropertyNames","getOwnPropertySymbols","getPrototypeOf","objectPrototype","hoistNonReactStatics","targetComponent","sourceComponent","blacklist","inheritedComponent","keys","concat","targetStatics","sourceStatics","i","descriptor","undefined","charAt","pathCache","Map","matchPaths","trimPathname","rawPathname","decodeURIComponent","stripPrefix","split","URL","setMatchPaths","findMatchPath","trimmedPathname","cleanPath","pickPaths","map","matchPath","originalPath","pick","normalizePagePath","route","grabMatchParams","params","findPath","foundPath","plain","backgroundColor","color","styles","types","opacity","textDecorationLine","fontStyle","fontWeight","Prism","theme","_defineProperty","enumerable","configurable","writable","_extends","assign","source","apply","newlineRe","normalizeEmptyLines","line","content","empty","appendTypes","add","typesSize","themeToDict","language","create","themeDict","reduce","acc","themeEntry","languages","includes","accStyle","root","objectWithoutProperties","exclude","k","indexOf","Highlight","this$1","args","len","prevTheme","prevLanguage","output","getThemeDict","display","baseStyle","typeStyles","token","children","getStyleForToken","code","grammar","env","tokens","hooks","run","tokenize","__proto__","constructor","typeArrStack","tokenArrStack","tokenArrIndexStack","tokenArrSizeStack","stackIndex","currentLine","alias","splitByNewlines","newlineCount","i$1","pop","normalizeTokens","getLineProps","getTokenProps","useScrollRestoration","identifier","useLocation","useContext","_scrollHandler","ScrollContext","useRef","useLayoutEffect","position","scrollTo","onScroll","scrollTop","fn","arg","emitter","all","on","handler","off","splice","emit","evt","mitt","ScrollContainer","ScrollHandler","_scrollContainer","_useScrollRestoration","ownKeys","enumerableOnly","symbols","sym","_objectSpread2","getOwnPropertyDescriptors","defineProperties","_objectWithoutProperties","excluded","sourceKeys","_objectWithoutPropertiesLoose","sourceSymbolKeys","propertyIsEnumerable","MDXContext","createContext","withMDXComponents","allComponents","useMDXComponents","components","contextComponents","MDXProvider","Provider","DEFAULTS","inlineCode","wrapper","Fragment","MDXCreateElement","propComponents","mdxType","originalType","parentName","etc","argsLength","createElementArgArray","Array","newProps","_interopDefault","ex","React","React__default","shallowEqual","canUseDOM","document","reducePropsToState","handleStateChangeOnClient","mapStateOnServer","Error","WrappedComponent","mountedInstances","emitChange","SideEffect","_Component","subClass","superClass","peek","rewind","recordedState","shouldComponentUpdate","nextProps","componentWillMount","index","getDisplayName","polyfill","getLocation","_source$location","search","hash","origin","protocol","host","hostname","port","decodeURI","history","createHistory","listeners","transitioning","resolveTransition","_onTransitionComplete","listen","listener","popstateListener","action","addEventListener","removeEventListener","_ref$replace","go","Date","now","replaceState","pushState","transition","Promise","res","createMemorySource","initialPath","searchIndex","initialLocation","substr","stack","states","_","uri","_uri$split","_uri$split$","_uri$split2","_uri$split2$","newIndex","globalHistory","reactPropsRegex","prop","test","charCodeAt","_gatsby","_catchLinks","onClientEntry","pluginOptions","GatsbyMDXScopeContext","useMDXScope","scope","contextScope","MDXScopeProvider","__mdxScope","TypeError","_unsupportedIterableToArray","o","minLen","n","toString","from","Symbol","iterator","_classCallCheck","Constructor","_possibleConstructorReturn","self","ReferenceError","_inherits","setPrototypeOf","PropTypes","ALL_INITIALIZERS","READY_INITIALIZERS","load","loader","promise","loading","loaded","error","then","catch","err","loadMap","promises","result","createLoadableComponent","loadFn","_class","_temp","opts","delay","timeout","webpack","modules","init","getModuleIds","every","moduleId","LoadableComponent","retry","setState","timedOut","_loadModule","pastDelay","preload","_mounted","context","loadable","isArray","moduleName","report","_delay","setTimeout","_timeout","update","_clearTimeouts","clearTimeout","isLoading","shape","Loadable","Capture","_React$Component2","getChildContext","Children","only","flushInitializers","initializers","preloadAll","reject","preloadReady","iter","_interopRequireWildcard","_sessionStorage","_len","_key","_stateStorage","scrollListener","scrollY","windowScroll","shouldUpdateScroll","scrollToHash","node","getElementById","substring","scrollIntoView","prevRouterProps","routerProps","scrollPosition","_this$props$location","_this$props$location2","element","onServiceWorkerUpdateReady","confirm","reload","objA","objB","compareContext","ret","keysA","keysB","bHasOwnProperty","idx","valueA","valueB","PageRenderer","pageResources","json","pageContext","__params","pathContext","pageElement","apiRunner","publicLoader","page","arrayLikeToArray","arr","_toConsumableArray","unsupportedIterableToArray","routes","match","default_","uriPathname","uriSegments","segmentize","isRootUri","ranked","rankRoutes","l","missed","routeSegments","max","Math","routeSegment","uriSegment","isSplat","dynamicMatch","paramRe","exec","reservedNames","_to$split","toPathname","toQuery","basePathname","toSegments","baseSegments","addQuery","allSegments","segments","segment","insertParams","_path$split","pathBase","_path$split$","query","constructedPath","_params$location","_params$location$sear","searchSplit","validateRedirect","isDynamic","sort","rankRoute","score","isRootSegment","SEGMENT_POINTS","a","b","q","shallowCompare","obj1","obj2","obj1Keys","plugin","animationIterationCount","borderImageOutset","borderImageSlice","borderImageWidth","boxFlex","boxFlexGroup","boxOrdinalGroup","columnCount","columns","flex","flexGrow","flexPositive","flexShrink","flexNegative","flexOrder","gridRow","gridRowEnd","gridRowSpan","gridRowStart","gridColumn","gridColumnEnd","gridColumnSpan","gridColumnStart","msGridRow","msGridRowSpan","msGridColumn","msGridColumnSpan","lineHeight","order","orphans","tabSize","widows","zIndex","zoom","WebkitLineClamp","fillOpacity","floodOpacity","stopOpacity","strokeDasharray","strokeDashoffset","strokeMiterlimit","strokeOpacity","strokeWidth","ie10","navigator","appVersion","fns","doc","hack","documentElement","doScroll","readyState","shift","definition","str","h","hyphenateRegex","animationRegex","isCustomProperty","property","isProcessableValue","processStyleName","styleName","toLowerCase","p1","p2","cursor","next","handleInterpolation","mergedProps","registered","interpolation","couldBeSelectorInterpolation","__emotion_styles","anim","interpolated","_i","createStringFromObject","previousCursor","cached","labelPattern","stringMode","strings","raw","lastIndex","identifierName","serviceWorker","register","reg","installingWorker","installing","log","controller","___swUpdated","___failedResources","url","arrayWithoutHoles","iterableToArray","nonIterableSpread","LoadingProvider","CodeBlock","exampleCode","prismTheme","p","tokensLength","lastToken","cleanTokens","lineClass","isDiff","lineProps","splitToken","diffStyle","userSelect","MozUserSelect","WebkitUserSelect","firstChar","AnchorTag","link","rel","StyledPre","colors","preFormattedText","h1","id","pre","getTheme","outerTheme","_objectSpread","createCacheWithTheme","Consumer","baseTheme","fonts","mono","lightTheme","background","heading","text","darkTheme","isAbsoluteUrl","StyledSwitch","NightImage","DayImage","DarkModeSwitch","isDarkThemeActive","toggleActiveTheme","onChange","checked","OpenedSvg","xmlns","width","height","viewBox","d","ClosedSvg","TreeNode","setCollapsed","collapsed","title","items","isCollapsed","hasChildren","calculatedClassName","config","gatsby","pathPrefix","sidebar","frontLine","aria-label","item","Tree","edges","treeData","useState","tree","ignoreIndex","fields","slug","accu","parts","prevItems","part","tmp","find","label","trailingSlash","slicedLength","existingItem","forcedNavOrder","reverse","findIndex","unshift","calculateTreeData","defaultCollapsed","collapsedNav","ExternalLink","_ref$color","_ref$size","size","fill","stroke","strokeLinecap","strokeLinejoin","points","x1","y1","x2","y2","ListItem","active","level","Sidebar","Divider","SidebarLayout","allMdx","dangerouslySetInnerHTML","__html","links","help","isSearchEnabled","header","enabled","searchIndices","indexName","hitComp","myFunction","x","StyledBgDiv","Header","data","logoImg","twitter","site","siteMetadata","headerTitle","helpUrl","tweetText","logo","headerLinks","finalLogoLink","src","image","alt","social","collapse","indices","onKeyDown","role","tabIndex","insertWithoutScoping","serialized","inserted","insert","sheet","merge","css","registeredStyles","rawClassName","classnames","cls","toAdd","_createEmotion","speedy","isSpeedy","compat","cx","_len4","_key4","injectGlobal","_len3","_key3","keyframes","_len2","_key2","animation","hydrate","ids","flush","getRegisteredStyles","baseStyles","ThemeProvider","retrieveActiveTheme","localStorage","currentActiveTheme","finalNavItems","innerItems","tableOfContents","innerItem","itemId","Wrapper","Content","MaxWidth","LeftSideBarWidth","RightSideBarWidth","Layout","mdxComponents","StyledNextPrevious","NextPrevious","currentIndex","mdx","nav","nextInfo","previousInfo","preserveAspectRatio","StyledHeading","Edit","StyledMainWrapper","MobileScrollUpButton","hideButton","setHideButton","prevScrollHeight","setPrevScrollHeight","showOrHide","useEffect","onscroll","scroll","MDXRuntimeTest","navItems","docsLocation","cur","metaTitle","frontmatter","metaDescription","canonicalUrl","siteUrl","body","classNames","insertStyles","isStringTag","uniqueId","Token","util","encode","objId","clone","visited","v","extend","redef","lang","insertBefore","inside","before","newToken","DFS","callback","plugins","highlight","matchGrammar","strarr","startPos","oneshot","patterns","j","pattern","lookbehind","greedy","lookbehindLength","global","flags","RegExp","pos","delNum","after","wrapped","matchedStr","parent","tag","classes","attributes","aliases","markup","tagName","includedCdataInside","def","html","mathml","svg","xml","ssml","atom","rss","envVars","commandAfterHeredoc","insideString","bash","variable","toBeCopied","shell","clike","c","keyword","cpp","addInlined","selectorInside","selector","unit","number","javascript","regex","js","jsx","stringifyToken","walkTokens","openedTags","notTagNorBrace","openedBraces","plainText","withId","maybeClassNameTokens","comment","coffeescript","coffee","diff","PREFIXES","git","graphql","markdown","getPlaceholder","toUpperCase","buildPlaceholders","placeholderPattern","replaceFilter","tokenStack","placeholder","tokenizePlaceholders","t","s","middle","replacement","handlebars","punctuation","webmanifest","less","makefile","inner","createInline","tableCell","tableRow","tableLine","yaml","codeLang","codeBlock","autoloader","valueOf","floor","random","loadLanguages","ele","innerHTML","textContent","md","objectivec","objc","ocaml","python","py","reason","function","sass","atrule","operator","important","scss","sql","stylus","typescript","typeInside","ts","tsx","wasm","anchorOrAlias","properties","plainKey","createValuePattern","yml","_setPrototypeOf","Helmet","_createClass","protoProps","staticProps","_react2","_propTypes2","_reactSideEffect2","_reactFastCompare2","_HelmetUtils","_HelmetConstants","HelmetSideEffects","handleClientStateChange","HelmetExport","HelmetWrapper","mapNestedChildrenToProps","child","nestedChildren","TAG_NAMES","SCRIPT","NOSCRIPT","STYLE","cssText","flattenArrayTypeChildren","arrayTypeChildren","newChildProps","mapObjectTypeChildren","_extends3","_extends4","TITLE","titleAttributes","BODY","bodyAttributes","HTML","htmlAttributes","mapArrayTypeChildrenToProps","newFlattenedProps","arrayChildName","_extends5","warnOnInvalidChildren","mapChildrenToProps","_child$props","childProps","convertReactPropstoHtmlAttributes","LINK","META","_props","oneOfType","arrayOf","defaultTitle","defer","encodeSpecialCharacters","meta","noscript","onChangeClientState","script","titleTemplate","mappedState","baseTag","linkTags","metaTags","noscriptTags","scriptTags","styleTags","renderStatic","W","X","trim","ia","m","Z","F","P","w","L","ja","ka","aa","G","ba","la","ma","R","na","ea","oa","H","g","A","S","B","U","D","z","M","y","C","K","u","r","I","J","f","N","ca","O","da","fa","Y","E","ha","Q","use","T","toSheet","block","Sheet","ruleSheet","selectors","parents","column","ns","depth","at","delimiter","stylisOptions","stylis","container","head","_insert","nodes","querySelectorAll","getAttribute","parentNode","appendChild","stylisPlugins","shouldCache","nonce","RouteAnnouncerProps","top","padding","overflow","clip","whiteSpace","border","redirectMap","redirectIgnoreCaseMap","maybeRedirect","redirect","toPath","redirects","ignoreCase","fromPath","onPreRouteUpdate","prevLocation","onRouteUpdate","timeoutId","loadPage","status","PageResourceStatus","webpackCompilationHash","___webpackCompilationHash","postMessage","gatsbyApi","reachNavigate","results","getSavedScrollPosition","RouteAnnouncer","announcementRef","createRef","requestAnimationFrame","pageName","pageHeadings","newAnnouncement","innerText","compareLocationProps","nextLocation","RouteUpdates","shallowDiffers","EnsureResources","loadPageSync","loadResources","rawPath","nextState","ProdLoader","asyncRequires","setLoader","setApiRunner","___emitter","apiRunnerAsync","RouteHandler","baseuri","basepath","DataContext","GatsbyRoot","staticQueryResults","getStaticQueryResults","LocationHandler","pagePath","browserLoc","SiteRoot","App","renderer","ReactDOM","domReady","prefetchPathname","StaticQueryContext","StaticQueryDataRenderer","staticQueryData","finalData","StaticQuery","useStaticQuery","isNaN","Number","arr2","mdxScope","End","fullScope","values","createNamedContext","defaultValue","Ctx","LocationContext","LocationProvider","getContext","refs","unlisten","_props$history","componentDidCatch","info","isRedirect","_navigate","unmounted","ServerLocation","BaseContext","Router","baseContext","locationContext","RouterImpl","_React$PureComponent","_navigate2","primary","_props$component","domProps","toArray","array","createRoute","cloneElement","FocusWrapper","FocusHandler","wrapperProps","PureComponent","FocusContext","requestFocus","FocusHandlerImpl","initialRender","focusHandlerCount","_temp2","_this4","shouldFocus","focus","myURIChanged","navigatedUpToMe","contains","activeElement","_this5","_props2","_props2$component","Comp","outline","_ref4","_ref5","_ref6","_props$getProps","anchorProps","encodedHref","event","shouldNavigate","_location$state","restState","RedirectRequest","redirectTo","RedirectImpl","_React$Component3","_props3","_props3$replace","noThrow","resolvedTo","_props4","Redirect","_ref7","Match","_ref8","_ref9","_ref10","resolvedPath","useNavigate","useParams","useMatch","stripSlashes","elementPath","_arrayLikeToArray","Reflect","construct","sham","Proxy","trackingId","GATSBY_GTAG_PLUGIN_GA_TRACKING_ID","anonymize","GATSBY_GTAG_PLUGIN_ANONYMIZE","gtag","locationStr","anonymizeObj","anonymize_ip","page_path","keyList","hasProp","hasElementType","Element","equal","arrA","arrB","dateA","dateB","getTime","regexpA","regexpB","$$typeof","message","hashIndex","_inheritsLoose","supportedPrefetchStrategy","feature","fakeLink","relList","supports","support","setAttribute","onload","onerror","getElementsByTagName","getElementsByName","req","XMLHttpRequest","open","send","preFetched","prefetch","Success","preferDefault","createPageDataUrl","doFetch","method","onreadystatechange","toPageResources","pageData","componentChunkName","staticQueryHashes","BaseLoader","loadComponent","inFlightNetworkRequests","pageDb","inFlightDb","staticQueryDb","pageDataDb","prefetchTriggered","Set","prefetchCompleted","memoizedGet","inFlightPromise","response","delete","prefetchDisabled","some","fetchPageDataJson","loadObj","retries","responseText","jsonPayload","payload","notFound","loadPageDataJson","loadAppData","allData","finalResult","componentChunkPromise","createdAt","staticQueryBatchPromise","staticQueryHash","staticQueryResultsMap","shouldPrefetch","connection","effectiveType","saveData","doesConnectionSupportPrefetch","realPath","doPrefetch","pageDataUrl","prefetchHelper","crossOrigin","as","getResourceURLsForPathname","createComponentUrls","isPageNotFound","appData","___chunkMapping","chunk","chunkName","componentUrls","_loader","getResourcesForPathname","getResourcesForPathnameSync","scope_0","componentsAndGuards","mdxPlugins","guards","componentName","guard","componentFromGuards","MDXConsumer","componentsFromContext","scopeContexts","wrapRootElement","wrapPageElement","ATTRIBUTE_NAMES","BASE","HEAD","REACT_TAG_MAP","VALID_TAG_NAMES","TAG_PROPERTIES","CHARSET","CSS_TEXT","HREF","HTTPEQUIV","INNER_HTML","ITEM_PROP","NAME","PROPERTY","REL","SRC","accesskey","charset","class","contenteditable","contextmenu","itemprop","tabindex","HELMET_PROPS","DEFAULT_TITLE","DEFER","ENCODE_SPECIAL_CHARACTERS","ON_CHANGE_CLIENT_STATE","TITLE_TEMPLATE","HTML_TAG_MAP","SELF_CLOSING_TAGS","HELMET_ATTRIBUTE","_reactDom","scrollKey","ScrollContainerImplementation","findDOMNode","clickHandler","routeThroughBrowserOrApp","hashShouldBeFollowed","pathIsNotHandledByApp","urlsAreOnSameOrigin","authorIsForcingNavigation","anchorsTargetIsEquivalentToSelf","findClosestAnchor","navigationWasHandledElsewhere","slashedPathname","userIsForcingNavigation","_escapeStringRegexp","nodeName","anchor","hasAttribute","ownerDocument","defaultView","destination","pathStartRegEx","hrefHandler","clickedAnchor","SVGAnimatedString","animVal","excludePattern","destinationPathname","gaTrackingId","logoLink","githubUrl","algoliaAppId","process","algoliaSearchKey","algoliaAdminKey","ALGOLIA_ADMIN_KEY","frontline","description","ogImage","favicon","pwa","manifest","short_name","start_url","background_color","theme_color","icons","sizes","matchOperatorsRe","EmotionCacheContext","HTMLElement","ThemeContext","typePropName","createEmotionProps","cssProp","Emotion","Global","InnerGlobal","updater","querySelector","tags","nextElementSibling","for","AsyncMode","ConcurrentMode","ContextConsumer","ContextProvider","Lazy","Portal","Profiler","StrictMode","Suspense","isAsyncMode","isConcurrentMode","isContextConsumer","isContextProvider","isElement","isForwardRef","isFragment","isLazy","isPortal","isProfiler","isStrictMode","isSuspense","isValidElementType","typeOf","ProdPageRenderer","InternalPageRenderer","isNativeReflectConstruct","_construct","Parent","Class","Function","_objectAssign2","clock","String","getTitleFromPropsList","propsList","innermostTitle","getInnermostProperty","innermostTemplate","innermostDefaultTitle","getOnChangeClientState","getAttributesFromPropsList","tagType","tagAttrs","getBaseTagFromPropsList","primaryAttributes","innermostBaseTag","lowerCaseAttributeKey","getTagsFromPropsList","approvedSeenTags","approvedTags","instanceTags","instanceSeenTags","primaryAttributeKey","attributeKey","tagUnion","rafPolyfill","currentTime","cafPolyfill","webkitRequestAnimationFrame","mozRequestAnimationFrame","cancelAnimationFrame","webkitCancelAnimationFrame","mozCancelAnimationFrame","msg","_helmetCallback","commitTagChanges","newState","updateAttributes","updateTitle","tagUpdates","updateTags","addedTags","removedTags","_tagUpdates$tagType","newTags","oldTags","flattenArray","possibleArray","elementTag","helmetAttributeString","helmetAttributes","attributesToRemove","attributeKeys","attribute","indexToSave","removeAttribute","headElement","tagNodes","indexToDelete","newElement","styleSheet","createTextNode","existingTag","isEqualNode","removeChild","generateElementAttributesAsString","attr","convertElementAttributestoReactProps","initProps","getMethodsForTag","toComponent","_initProps","attributeString","flattenedTitle","generateTitleAsString","_mappedTag","mappedTag","mappedAttribute","generateTagsAsReactComponent","attributeHtml","tagContent","isSelfClosing","generateTagsAsString","initAttributes","_ref$title","testOmitPropsOnStringTag","testOmitPropsOnComponent","getDefaultShouldForwardProp","createStyled","shouldForwardProp","targetClassName","__emotion_forwardProp","propName","isReal","__emotion_real","__emotion_base","defaultShouldForwardProp","shouldUseAs","Styled","finalTag","classInterpolations","finalShouldForwardProp","withComponent","nextTag","nextOptions","api","defaultReturn","argTransform","previous","GATSBY_LAYOUT_COMPONENT_PATH","condition","format","argIndex","framesToPop","StyleSheet","ctr","rule","_tag","createStyleElement","nextSibling","styleSheets","ownerNode","sheetForTag","isImportRule","insertRule","cssRules"],"mappings":";6FAEA,IAAIA,EAAyBC,EAAQ,QAErCC,EAAQC,YAAa,EACrBD,EAAQE,WAAaA,EACrBF,EAAQG,gBA4DR,SAAyBC,GACvB,OAAOF,EAAWE,EAAMC,MA5D1BL,EAAQM,WAAaN,EAAQO,QAAUP,EAAQQ,KAAOR,EAAQS,SAAWT,EAAQU,aAAU,EAE3F,IAAIC,EAAiCb,EAAuBC,EAAQ,SAEhEa,EAA0Bd,EAAuBC,EAAQ,SAEzDc,EAAkBf,EAAuBC,EAAQ,SAEjDe,EAAYhB,EAAuBC,EAAQ,SAE3CgB,EAAajB,EAAuBC,EAAQ,SAE5CiB,EAASlB,EAAuBC,EAAQ,SAExCkB,EAAUlB,EAAQ,QAElBmB,EAASnB,EAAQ,QAEjBoB,EAAapB,EAAQ,QAEzBC,EAAQoB,UAAYD,EAAWC,UAE/B,IAAIC,EAAiB,SAAwBjB,GAC3C,OAAOA,aAAmC,EAASA,EAAKkB,WAAW,MAGrE,SAASpB,EAAWE,EAAMmB,GACxB,IAAIC,EAAMC,EAMV,QAJe,IAAXF,IACFA,EAASG,MAGNC,EAAYvB,GACf,OAAOA,EAGT,GAAIA,EAAKkB,WAAW,OAASlB,EAAKkB,WAAW,OAC3C,OAAOlB,EAGT,IAAIwB,EAAwG,QAAhGJ,EAA8B,QAAtBC,EAAUF,SAAgC,IAAZE,EAAqBA,EAAUpB,WAA4C,IAATmB,EAAkBA,EAAO,IAC7I,MAAO,KAAOI,aAAmC,EAASA,EAAKC,SAAS,MAAQD,EAAKE,MAAM,GAAI,GAAKF,IAASxB,EAAKkB,WAAW,KAAOlB,EAAO,IAAMA,GAKnJ,IAAIC,EAAsB,WACxB,MAAsH0B,IAGpHL,EAAsB,WACxB,MAAkHM,IAGhHL,EAAc,SAAqBvB,GACrC,OAAOA,IAASA,EAAKkB,WAAW,aAAelB,EAAKkB,WAAW,cAAgBlB,EAAKkB,WAAW,OAgBjG,IAAIW,EAAkB,SAAyB7B,EAAM8B,GACnD,MAAoB,iBAAT9B,EACFA,EAGJuB,EAAYvB,GAIViB,EAAejB,GAAQF,EAAWE,GAlB3C,SAAoBA,EAAM+B,GAExB,OAAId,EAAejB,GACVA,GAGF,EAAIc,EAAOkB,SAAShC,EAAM+B,GAYgBE,CAAWjC,EAAM8B,GAHzD9B,GAMPkC,EAAmB,CACrBC,gBAAiBxB,EAAWL,QAAQ8B,OACpCC,YAAa1B,EAAWL,QAAQgC,OAChCC,gBAAiB5B,EAAWL,QAAQkC,MAyBtC,SAASC,EAA0BC,GACjC,OAAoB9B,EAAON,QAAQqC,cAAc9B,EAAQ+B,SAAU,MAAM,SAAUC,GACjF,IAAIC,EAAWD,EAAMC,SACrB,OAAoBlC,EAAON,QAAQqC,cAAcI,GAAY,EAAIrC,EAAUJ,SAAS,GAAIoC,EAAO,CAC7FM,UAAWF,QAKjB,IAAIC,EAA0B,SAAUE,GAGtC,SAASF,EAAWL,GAClB,IAAIQ,GAEJA,EAAQD,EAAiBE,KAAKC,KAAMV,IAAUU,MAExCC,gBAAkB,SAAUC,GAChC,IAAIC,EAAqBD,EAAMC,mBAC3BC,EAAYF,EAAME,UAEtB,OAAIN,EAAMR,MAAMH,gBAAkBgB,EAAqBC,GAC9C,CACLC,UAAW,CAACP,EAAMR,MAAMe,UAAWP,EAAMR,MAAMP,iBAAiBuB,OAAOC,SAASC,KAAK,KACrFC,OAAO,EAAInD,EAAUJ,SAAS,GAAI4C,EAAMR,MAAMmB,MAAOX,EAAMR,MAAML,cAI9D,MAGT,IAAIyB,GAAc,EAUlB,MARsB,oBAAXC,QAA0BA,OAAOC,uBAC1CF,GAAc,GAGhBZ,EAAMe,MAAQ,CACZH,YAAaA,GAEfZ,EAAMgB,UAAYhB,EAAMgB,UAAUC,MAAK,EAAI3D,EAAwBF,SAAS4C,IACrEA,GA/BT,EAAIzC,EAAgBH,SAASyC,EAAYE,GAkCzC,IAAImB,EAASrB,EAAWsB,UAuIxB,OArIAD,EAAOE,UAAY,WACjB,IAAIC,EAAcR,OAAOjB,SAAS0B,SAE9BpB,KAAKV,MAAMM,WAAaI,KAAKV,MAAMM,UAAUwB,WAC/CD,EAAcnB,KAAKV,MAAMM,UAAUwB,UAGrC,IAAIC,EAAgB5C,EAAgBuB,KAAKV,MAAMgC,GAAIH,GAC/CI,GAAc,EAAI5D,EAAWC,WAAWyD,GAAeD,SAGvDD,IAAgBI,GAClBC,UAAUC,QAAQF,IAItBP,EAAOU,mBAAqB,SAA4BC,EAAWC,GAE7D5B,KAAKV,MAAMgC,KAAOK,EAAUL,IAAOtB,KAAKa,MAAMH,aAChDV,KAAKkB,aAITF,EAAOa,kBAAoB,WAEpB7B,KAAKa,MAAMH,aACdV,KAAKkB,aAITF,EAAOc,qBAAuB,WAC5B,GAAK9B,KAAK+B,GAAV,CAIA,IAAIC,EAAWhC,KAAK+B,GAChBE,EAAWD,EAASC,SACpBC,EAAKF,EAASE,GAClBD,EAASE,UAAUD,GACnBD,EAASG,eAGXpB,EAAOF,UAAY,SAAmBuB,GACpC,IA/GiEH,EAAII,EACnEP,EA8GEQ,EAASvC,KAETA,KAAKV,MAAMkD,UAAYxC,KAAKV,MAAMkD,SAASC,eAAe,WAC5DzC,KAAKV,MAAMkD,SAAS7D,QAAU0D,EACrBrC,KAAKV,MAAMkD,UACpBxC,KAAKV,MAAMkD,SAASH,GAGlBrC,KAAKa,MAAMH,aAAe2B,IAE5BrC,KAAK+B,IAzH0DG,EAyH1BG,EAzH8BC,EAyHzB,WACxCC,EAAOrB,cAzHTa,EAAK,IAAIpB,OAAOC,sBAAqB,SAAU8B,GACjDA,EAAQC,SAAQ,SAAUC,GACpBV,IAAOU,EAAMC,SAGXD,EAAME,gBAAkBF,EAAMG,kBAAoB,KACpDhB,EAAGI,UAAUD,GACbH,EAAGK,aACHE,YAMLU,QAAQd,GACJ,CACLD,SAAUF,EACVG,GAAIA,MA6GNlB,EAAOiC,OAAS,WACd,IAAIC,EAASlD,KAETmD,EAAcnD,KAAKV,MACnBgC,EAAK6B,EAAY7B,GACjB8B,EAAuBD,EAAYE,SACnCA,OAAoC,IAAzBD,EAAkCpD,KAAKC,gBAAkBmD,EACpEE,EAAWH,EAAYI,QACvBC,EAAgBL,EAAYM,aAK5B5C,GAJmBsC,EAAYpE,gBAChBoE,EAAYlE,YACfkE,EAAYX,SACNW,EAAYhE,gBACtBgE,EAAYtC,OACpB9D,EAAUoG,EAAYpG,QACtB6C,EAAYuD,EAAYvD,UACxB8D,GAAO,EAAIvG,EAA+BD,SAASiG,EAAa,CAAC,KAAM,WAAY,UAAW,eAAgB,kBAAmB,cAAe,WAAY,kBAAmB,QAAS,UAAW,cAMvM,IAAIQ,EAAalF,EAAgB6C,EAAI1B,EAAUwB,UAE/C,OAAKjD,EAAYwF,GAMGnG,EAAON,QAAQqC,cAAc9B,EAAQmG,MAAM,EAAItG,EAAUJ,SAAS,CACpFoE,GAAIqC,EACJ9C,MAAOA,EACPwC,SAAUA,EACVb,SAAUxC,KAAKc,UACf2C,aAAc,SAAsBI,GAC9BL,GACFA,EAAcK,GAGhBrC,UAAUsC,UAAS,EAAInG,EAAWC,WAAW+F,GAAYvC,WAE3DmC,QAAS,SAAiBM,GAKxB,GAJIP,GACFA,EAASO,KAGM,IAAbA,EAAEE,QACLb,EAAO5D,MAAMuD,QACbgB,EAAEG,kBACFH,EAAEI,SACFJ,EAAEK,QAAWL,EAAEM,SAAYN,EAAEO,UAAU,CACtCP,EAAEQ,iBACF,IAAIC,EAAgBvH,EAEhBqD,EAAYmE,UAAUZ,KAAgB/D,EAAUwB,SAE7B,kBAAZrE,GAAyBqD,IAClCkE,GAAgB,GAKlB3D,OAAO6D,YAAYb,EAAY,CAC7B9C,MAAOA,EACP9D,QAASuH,IAIb,OAAO,IAERZ,IA9CmBlG,EAAON,QAAQqC,cAAc,KAAK,EAAIjC,EAAUJ,SAAS,CAC3EuH,KAAMd,GACLD,KA+CA/D,EA1KqB,CA2K5BnC,EAAON,QAAQwH,WAEjB/E,EAAWgF,WAAY,EAAIrH,EAAUJ,SAAS,GAAI4B,EAAkB,CAClEyE,QAAShG,EAAWL,QAAQ0H,KAC5BtD,GAAI/D,EAAWL,QAAQ8B,OAAO6F,WAC9B9H,QAASQ,EAAWL,QAAQkC,KAC5ByB,MAAOtD,EAAWL,QAAQgC,SAG5B,IAAI4F,EAAyB,SAAgCC,EAAcC,EAAiBC,GAC1F,OAAOC,QAAQC,KAAK,QAAWJ,EAAe,6DAAgEE,EAAU,iBAAoBD,EAAkB,eAG5JI,EAAwB5H,EAAON,QAAQmI,YAAW,SAAU/F,EAAO+C,GACrE,OAAoB7E,EAAON,QAAQqC,cAAcF,GAA2B,EAAI/B,EAAUJ,SAAS,CACjGsF,SAAUH,GACT/C,OAGL9C,EAAQU,QAAUkI,EAMlB5I,EAAQS,SAJO,SAAkBqE,EAAIgE,GACnC3E,OAAO6D,YAAY/F,EAAgB6C,EAAIX,OAAOjB,SAAS0B,UAAWkE,IAKpE,IAAItI,EAAO,SAAcsE,GACvBwD,EAAuB,OAAQ,WAAY,GAE3CnE,OAAO4E,QAAQ9G,EAAgB6C,EAAIX,OAAOjB,SAAS0B,YAGrD5E,EAAQQ,KAAOA,EASfR,EAAQO,QAPM,SAAiBuE,GAC7BwD,EAAuB,UAAW,WAAY,GAE9CnE,OAAO6E,WAAW/G,EAAgB6C,EAAIX,OAAOjB,SAAS0B,YAWxD5E,EAAQM,WALS,SAAoBwE,GAEnC,OADAwD,EAAuB,aAAc,WAAY,GAC1C9H,EAAKsE,K,oCCvVd9E,EAAQC,YAAa,EACrBD,EAAQiJ,oBAAiB,EACzB,IAGIA,EAA8B,WAChC,SAASA,KAET,IAAIzE,EAASyE,EAAexE,UA8C5B,OA5CAD,EAAO0E,KAAO,SAAchG,EAAUiG,GACpC,IAAIC,EAAW5F,KAAK6F,YAAYnG,EAAUiG,GAE1C,IACE,IAAIG,EAAQnF,OAAOoF,eAAeC,QAAQJ,GAC1C,OAAOE,EAAQG,KAAKC,MAAMJ,GAAS,EACnC,MAAOjC,GAKP,OAAIlD,QAAUA,OAAiC,+BAAKA,OAAiC,8BAAEiF,GAC9EjF,OAAiC,8BAAEiF,GAGrC,IAIX5E,EAAOmF,KAAO,SAAczG,EAAUiG,EAAKG,GACzC,IAAIF,EAAW5F,KAAK6F,YAAYnG,EAAUiG,GACtCS,EAAcH,KAAKI,UAAUP,GAEjC,IACEnF,OAAOoF,eAAeO,QAAQV,EAAUQ,GACxC,MAAOvC,GACHlD,QAAUA,OAAiC,gCAG7CA,OAAiC,8BAAI,IAFrCA,OAAiC,8BAAEiF,GAAYK,KAAKC,MAAME,KAYhEpF,EAAO6E,YAAc,SAAqBnG,EAAUiG,GAClD,IAAIY,EAhDe,YAgDwB7G,EAAS0B,SACpD,OAAOuE,QAA6CY,EAAeA,EAAe,IAAMZ,GAGnFF,EAjDyB,GAoDlCjJ,EAAQiJ,eAAiBA,G,uBC3DzB,IAAIe,EAAU,EAAQ,QAA0C,QAEhE,SAASC,IACP,GAAuB,mBAAZC,QAAwB,OAAO,KAC1C,IAAIC,EAAQ,IAAID,QAMhB,OAJAD,EAA2B,WACzB,OAAOE,GAGFA,EA4CTC,EAAOpK,QAzCP,SAAiCqK,GAC/B,GAAIA,GAAOA,EAAIpK,WACb,OAAOoK,EAGT,GAAY,OAARA,GAAiC,WAAjBL,EAAQK,IAAoC,mBAARA,EACtD,MAAO,CACL,QAAWA,GAIf,IAAIF,EAAQF,IAEZ,GAAIE,GAASA,EAAMG,IAAID,GACrB,OAAOF,EAAMI,IAAIF,GAGnB,IAAIG,EAAS,GACTC,EAAwBC,OAAOC,gBAAkBD,OAAOE,yBAE5D,IAAK,IAAIzB,KAAOkB,EACd,GAAIK,OAAOjG,UAAUwB,eAAe1C,KAAK8G,EAAKlB,GAAM,CAClD,IAAI0B,EAAOJ,EAAwBC,OAAOE,yBAAyBP,EAAKlB,GAAO,KAE3E0B,IAASA,EAAKN,KAAOM,EAAKC,KAC5BJ,OAAOC,eAAeH,EAAQrB,EAAK0B,GAEnCL,EAAOrB,GAAOkB,EAAIlB,GAWxB,OANAqB,EAAgB,QAAIH,EAEhBF,GACFA,EAAMW,IAAIT,EAAKG,GAGVA,GAITJ,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,oCCrDxE,IAAI8K,EAAU,EAAQ,QAOlBC,EAAgB,CAClBC,mBAAmB,EACnBC,aAAa,EACbC,cAAc,EACdC,cAAc,EACdC,aAAa,EACbC,iBAAiB,EACjBC,0BAA0B,EAC1BC,0BAA0B,EAC1BC,QAAQ,EACRtD,WAAW,EACXuD,MAAM,GAEJC,EAAgB,CAClBC,MAAM,EACNC,QAAQ,EACRpH,WAAW,EACXqH,QAAQ,EACRC,QAAQ,EACRC,WAAW,EACXC,OAAO,GASLC,EAAe,CACjB,UAAY,EACZC,SAAS,EACTf,cAAc,EACdC,aAAa,EACblD,WAAW,EACXuD,MAAM,GAEJU,EAAe,GAInB,SAASC,EAAWC,GAElB,OAAIvB,EAAQwB,OAAOD,GACVJ,EAIFE,EAAaE,EAAoB,WAAMtB,EAVhDoB,EAAarB,EAAQyB,YAhBK,CACxB,UAAY,EACZ/F,QAAQ,EACR2E,cAAc,EACdC,aAAa,EACblD,WAAW,GAYbiE,EAAarB,EAAQ0B,MAAQP,EAY7B,IAAIvB,EAAiBD,OAAOC,eACxB+B,EAAsBhC,OAAOgC,oBAC7BC,EAAwBjC,OAAOiC,sBAC/B/B,EAA2BF,OAAOE,yBAClCgC,EAAiBlC,OAAOkC,eACxBC,EAAkBnC,OAAOjG,UAuC7B2F,EAAOpK,QArCP,SAAS8M,EAAqBC,EAAiBC,EAAiBC,GAC9D,GAA+B,iBAApBD,EAA8B,CAEvC,GAAIH,EAAiB,CACnB,IAAIK,EAAqBN,EAAeI,GAEpCE,GAAsBA,IAAuBL,GAC/CC,EAAqBC,EAAiBG,EAAoBD,GAI9D,IAAIE,EAAOT,EAAoBM,GAE3BL,IACFQ,EAAOA,EAAKC,OAAOT,EAAsBK,KAM3C,IAHA,IAAIK,EAAgBhB,EAAWU,GAC3BO,EAAgBjB,EAAWW,GAEtBO,EAAI,EAAGA,EAAIJ,EAAKtB,SAAU0B,EAAG,CACpC,IAAIpE,EAAMgE,EAAKI,GAEf,KAAK5B,EAAcxC,IAAU8D,GAAaA,EAAU9D,IAAWmE,GAAiBA,EAAcnE,IAAWkE,GAAiBA,EAAclE,IAAO,CAC7I,IAAIqE,EAAa5C,EAAyBoC,EAAiB7D,GAE3D,IAEEwB,EAAeoC,EAAiB5D,EAAKqE,GACrC,MAAOnG,OAKf,OAAO0F,I,wMCrGM,WAAA3M,GACb,YAAaqN,IAATrN,EACKA,EAED,MAAJA,EACI,IAEJ,MAAAA,EAAKsN,OAAOtN,EAAKyL,OAAS,GACrBzL,EAAK0B,MAAM,GAAI,GAEjB1B,GCNHuN,EAAY,IAAIC,IAClBC,EAAa,GAEXC,EAAe,SAAAC,GACnB,IAAMnJ,EAAWoJ,mBAAmBD,GAQpC,OANwBE,YAAYrJ,EAAU5C,IAE3CkM,MAFqB,KAEV,GAEXA,MAJqB,KAIV,IAKhB,SAAS7L,EAAWjC,GAElB,OACEA,EAAKkB,WAAL,MACAlB,EAAKkB,WAAL,aACAlB,EAAKkB,WAAL,WAEOlB,EAIF,IAAI+N,IACT/N,EACA+D,OAAOjB,SAAS+E,MAAQ9D,OAAOjB,SAAS+E,KAAKpG,SAArB,cACxB+C,SAQG,IAAMwJ,EAAgB,SAAA9E,GAC3BuE,EAAavE,GAWF+E,EAAgB,SAAAN,GAC3B,IAAMO,EAAkBC,EAAUR,GAE5BS,EAAYX,EAAWY,KAAI,YAA0B,IAAvBrO,EAAsB,EAAtBA,KAClC,MAAO,CACLA,KAFsD,EAAhBsO,UAGtCC,aAAcvO,MAIZA,EAAOwO,eAAKJ,EAAWF,GAE7B,OAAIlO,EACKyO,EAAkBzO,EAAK0O,MAAMH,cAG/B,MAYII,EAAkB,SAAAhB,GAC7B,IAAMO,EAAkBC,EAAUR,GAE5BS,EAAYX,EAAWY,KAAI,YAA0B,IAAvBrO,EAAsB,EAAtBA,KAClC,MAAO,CACLA,KAFsD,EAAhBsO,UAGtCC,aAAcvO,MAIZA,EAAOwO,eAAKJ,EAAWF,GAE7B,OAAIlO,EACKA,EAAK4O,OAGP,IAWIC,EAAW,SAAAlB,GACtB,IAAMO,EAAkBR,EAAazL,EAAW0L,IAChD,GAAIJ,EAAUrD,IAAIgE,GAChB,OAAOX,EAAUpD,IAAI+D,GAGvB,IAAIY,EAAYb,EAAcC,GAQ9B,OANKY,IACHA,EAAYX,EAAUR,IAGxBJ,EAAU7C,IAAIwD,EAAiBY,GAExBA,GAUIX,EAAY,SAAAR,GACvB,IAEImB,EAFoBpB,EAAazL,EAAW0L,IAShD,MANa,gBAATmB,IACFA,EAAS,KAGXA,EAAYL,EAAkBK,K,sFCrEjB,EAnEH,CACVC,MAAO,CACLC,gBAAiB,UACjBC,MAAO,WAETC,OAAQ,CAAC,CACPC,MAAO,CAAC,UAAW,SAAU,UAAW,QAAS,eACjDtL,MAAO,CACLoL,MAAO,YAER,CACDE,MAAO,CAAC,aACRtL,MAAO,CACLuL,QAAS,KAEV,CACDD,MAAO,CAAC,MAAO,WAAY,UAC3BtL,MAAO,CACLoL,MAAO,YAER,CACDE,MAAO,CAAC,WAAY,YACpBtL,MAAO,CACLoL,MAAO,YAER,CACDE,MAAO,CAAC,SAAU,WAAY,aAC9BtL,MAAO,CACLoL,MAAO,YAER,CACDE,MAAO,CAAC,aACRtL,MAAO,CACLoL,MAAO,YAER,CACDE,MAAO,CAAC,UAAW,SAAU,SAAU,MAAO,aAAc,UAAW,UAAW,YAAa,OAAQ,YAAa,QAAS,UAAW,cAAe,YACvJtL,MAAO,CACLoL,MAAO,YAER,CACDE,MAAO,CAAC,WACRtL,MAAO,CACLwL,mBAAoB,iBAErB,CACDF,MAAO,CAAC,YACRtL,MAAO,CACLwL,mBAAoB,cAErB,CACDF,MAAO,CAAC,UACRtL,MAAO,CACLyL,UAAW,WAEZ,CACDH,MAAO,CAAC,YAAa,QACrBtL,MAAO,CACL0L,WAAY,SAEb,CACDJ,MAAO,CAAC,aACRtL,MAAO,CACLoL,MAAO,c,YC/DTjE,EAAe,CAEjBwE,MAAO,IACPC,MAAO,GAGT,SAASC,EAAgBzF,EAAKlB,EAAKG,GAYjC,OAXIH,KAAOkB,EACTK,OAAOC,eAAeN,EAAKlB,EAAK,CAC9BG,MAAOA,EACPyG,YAAY,EACZC,cAAc,EACdC,UAAU,IAGZ5F,EAAIlB,GAAOG,EAGNe,EAGT,SAAS6F,IAeP,OAdAA,EAAWxF,OAAOyF,QAAU,SAAU9J,GACpC,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CACzC,IAAI6C,EAASpE,UAAUuB,GAEvB,IAAK,IAAIpE,KAAOiH,EACV1F,OAAOjG,UAAUwB,eAAe1C,KAAK6M,EAAQjH,KAC/C9C,EAAO8C,GAAOiH,EAAOjH,IAK3B,OAAO9C,IAGOgK,MAAM7M,KAAMwI,WAG9B,IAAIsE,EAAY,aAEZC,EAAsB,SAA6BC,GACjC,IAAhBA,EAAK3E,OACP2E,EAAKhQ,KAAK,CACR+O,MAAO,CAAC,SACRkB,QAAS,KACTC,OAAO,IAEgB,IAAhBF,EAAK3E,QAAoC,KAApB2E,EAAK,GAAGC,UACtCD,EAAK,GAAGC,QAAU,KAClBD,EAAK,GAAGE,OAAQ,IAIhBC,EAAc,SAAqBpB,EAAOqB,GAC5C,IAAIC,EAAYtB,EAAM1D,OAEtB,OAAIgF,EAAY,GAAKtB,EAAMsB,EAAY,KAAOD,EACrCrB,EAGFA,EAAMnC,OAAOwD,IA+ElBE,EAAc,SAAqBjB,EAAOkB,GAC5C,IAAI5B,EAAQU,EAAMV,MAEdvN,EAAO8I,OAAOsG,OAAO,MACrBC,EAAYpB,EAAMP,OAAO4B,QAAO,SAAUC,EAAKC,GACjD,IAAIC,EAAYD,EAAWC,UACvBpN,EAAQmN,EAAWnN,MAEvB,OAAIoN,IAAcA,EAAUC,SAASP,IAIrCK,EAAW7B,MAAMpJ,SAAQ,SAAUuF,GAEjC,IAAI6F,EAAWrB,EAAS,GAAIiB,EAAIzF,GAAOzH,GAEvCkN,EAAIzF,GAAQ6F,KAPLJ,IAURvP,GAOH,OALAqP,EAAUO,KAAOrC,EAEjB8B,EAAU9B,MAAQe,EAAS,GAAIf,EAAO,CACpCC,gBAAiB,OAEZ6B,GAGT,SAASQ,EAAwBpH,EAAKqH,GACpC,IAAIrL,EAAS,GAEb,IAAK,IAAIsL,KAAKtH,EACRK,OAAOjG,UAAUwB,eAAe1C,KAAK8G,EAAKsH,KAA8B,IAAxBD,EAAQE,QAAQD,KAAWtL,EAAOsL,GAAKtH,EAAIsH,IAGjG,OAAOtL,EAGT,IAAIwL,EAAyB,SAAU3J,GACrC,SAAS2J,IAKP,IAJA,IAAIC,EAAStO,KACTuO,EAAO,GACPC,EAAMhG,UAAUH,OAEbmG,KACLD,EAAKC,GAAOhG,UAAUgG,GAGxB9J,EAAUmI,MAAM7M,KAAMuO,GAEtBjC,EAAgBtM,KAAM,gBAAgB,SAAUV,GAC9C,QAAyB2K,IAArBqE,EAAOb,WAA2BnO,EAAM+M,QAAUiC,EAAOG,WAAanP,EAAMiO,WAAae,EAAOI,aAClG,OAAOJ,EAAOb,UAGhBa,EAAOG,UAAYnP,EAAM+M,MACzBiC,EAAOI,aAAepP,EAAMiO,SAC5B,IAAIE,EAAYnO,EAAM+M,MAAQiB,EAAYhO,EAAM+M,MAAO/M,EAAMiO,eAAYtD,EACzE,OAAOqE,EAAOb,UAAYA,KAG5BnB,EAAgBtM,KAAM,gBAAgB,SAAUqC,GAC9C,IAAIsD,EAAMtD,EAAIsD,IACVtF,EAAYgC,EAAIhC,UAChBI,EAAQ4B,EAAI5B,MAIZkO,EAASjC,EAAS,GAHTuB,EAAwB5L,EAAK,CAAC,MAAO,YAAa,QAAS,SAGxC,CAC9BhC,UAAW,aACXI,WAAOwJ,EACPtE,SAAKsE,IAGHwD,EAAYa,EAAOM,aAAaN,EAAOhP,OAkB3C,YAhBkB2K,IAAdwD,IACFkB,EAAOlO,MAAQgN,EAAU9B,YAGb1B,IAAVxJ,IACFkO,EAAOlO,WAAyBwJ,IAAjB0E,EAAOlO,MAAsBiM,EAAS,GAAIiC,EAAOlO,MAAOA,GAASA,QAGtEwJ,IAARtE,IACFgJ,EAAOhJ,IAAMA,GAGXtF,IACFsO,EAAOtO,WAAa,IAAMA,GAGrBsO,KAGTrC,EAAgBtM,KAAM,oBAAoB,SAAUqC,GAClD,IAAI0J,EAAQ1J,EAAI0J,MACZmB,EAAQ7K,EAAI6K,MACZG,EAAYtB,EAAM1D,OAClBoF,EAAYa,EAAOM,aAAaN,EAAOhP,OAE3C,QAAkB2K,IAAdwD,EAAJ,CAEO,GAAkB,IAAdJ,GAAgC,UAAbtB,EAAM,GAClC,OAAOmB,EAAQ,CACb2B,QAAS,qBACP5E,EACC,GAAkB,IAAdoD,IAAoBH,EAC7B,OAAOO,EAAU1B,EAAM,IAGzB,IAAI+C,EAAY5B,EAAQ,CACtB2B,QAAS,gBACP,GAEAE,EAAahD,EAAMd,KAAI,SAAU/C,GACnC,OAAOuF,EAAUvF,MAEnB,OAAOhB,OAAOyF,OAAOE,MAAM3F,OAAQ,CAAC4H,GAAWlF,OAAOmF,QAGxDzC,EAAgBtM,KAAM,iBAAiB,SAAUqC,GAC/C,IAAIsD,EAAMtD,EAAIsD,IACVtF,EAAYgC,EAAIhC,UAChBI,EAAQ4B,EAAI5B,MACZuO,EAAQ3M,EAAI2M,MAIZL,EAASjC,EAAS,GAHTuB,EAAwB5L,EAAK,CAAC,MAAO,YAAa,QAAS,UAGxC,CAC9BhC,UAAW,SAAW2O,EAAMjD,MAAMvL,KAAK,KACvCyO,SAAUD,EAAM/B,QAChBxM,MAAO6N,EAAOY,iBAAiBF,GAC/BrJ,SAAKsE,IAeP,YAZcA,IAAVxJ,IACFkO,EAAOlO,WAAyBwJ,IAAjB0E,EAAOlO,MAAsBiM,EAAS,GAAIiC,EAAOlO,MAAOA,GAASA,QAGtEwJ,IAARtE,IACFgJ,EAAOhJ,IAAMA,GAGXtF,IACFsO,EAAOtO,WAAa,IAAMA,GAGrBsO,KAGTrC,EAAgBtM,KAAM,YAAY,SAAUoM,EAAO+C,EAAMC,EAAS7B,GAChE,IAAI8B,EAAM,CACRF,KAAMA,EACNC,QAASA,EACT7B,SAAUA,EACV+B,OAAQ,IAEVlD,EAAMmD,MAAMC,IAAI,kBAAmBH,GACnC,IAAIC,EAASD,EAAIC,OAASlD,EAAMqD,SAASJ,EAAIF,KAAME,EAAID,QAASC,EAAI9B,UAEpE,OADAnB,EAAMmD,MAAMC,IAAI,iBAAkBH,GAC3BC,KA2BX,OAvBI5K,IAAW2J,EAAUqB,UAAYhL,GACrC2J,EAAUpN,UAAYiG,OAAOsG,OAAO9I,GAAaA,EAAUzD,WAC3DoN,EAAUpN,UAAU0O,YAActB,EAElCA,EAAUpN,UAAUgC,OAAS,WAC3B,IAAIZ,EAAMrC,KAAKV,MACX8M,EAAQ/J,EAAI+J,MACZmB,EAAWlL,EAAIkL,SACf4B,EAAO9M,EAAI8M,KACXF,EAAW5M,EAAI4M,SACfxB,EAAYzN,KAAK4O,aAAa5O,KAAKV,OACnC8P,EAAUhD,EAAMyB,UAAUN,GAG9B,OAAO0B,EAAS,CACdK,OA3PgB,SAAyBA,GAU7C,IATA,IAAIM,EAAe,CAAC,IAChBC,EAAgB,CAACP,GACjBQ,EAAqB,CAAC,GACtBC,EAAoB,CAACT,EAAOjH,QAC5B0B,EAAI,EACJiG,EAAa,EACbC,EAAc,GACdtC,EAAM,CAACsC,GAEJD,GAAc,GAAG,CACtB,MAAQjG,EAAI+F,EAAmBE,MAAiBD,EAAkBC,IAAa,CAC7E,IAAI/C,OAAU,EACVlB,EAAQ6D,EAAaI,GAErBhB,EADWa,EAAcG,GACRjG,GAgBrB,GAdqB,iBAAViF,GACTjD,EAAQiE,EAAa,EAAIjE,EAAQ,CAAC,SAClCkB,EAAU+B,IAEVjD,EAAQoB,EAAYpB,EAAOiD,EAAM9G,MAE7B8G,EAAMkB,QACRnE,EAAQoB,EAAYpB,EAAOiD,EAAMkB,QAGnCjD,EAAU+B,EAAM/B,SAIK,iBAAZA,EAAX,CAUA,IAAIkD,EAAkBlD,EAAQvC,MAAMoC,GAChCsD,EAAeD,EAAgB9H,OACnC4H,EAAYjT,KAAK,CACf+O,MAAOA,EACPkB,QAASkD,EAAgB,KAG3B,IAAK,IAAIE,EAAM,EAAGA,EAAMD,EAAcC,IACpCtD,EAAoBkD,GACpBtC,EAAI3Q,KAAKiT,EAAc,IACvBA,EAAYjT,KAAK,CACf+O,MAAOA,EACPkB,QAASkD,EAAgBE,UArB3BL,IACAJ,EAAa5S,KAAK+O,GAClB8D,EAAc7S,KAAKiQ,GACnB6C,EAAmB9S,KAAK,GACxB+S,EAAkB/S,KAAKiQ,EAAQ5E,QAuBnC2H,IACAJ,EAAaU,MACbT,EAAcS,MACdR,EAAmBQ,MACnBP,EAAkBO,MAIpB,OADAvD,EAAoBkD,GACbtC,EAsLQ4C,MADiBtG,IAAZmF,EAAwBpP,KAAKyP,SAASrD,EAAO+C,EAAMC,EAAS7B,GAAY,CAAC4B,IAIzF9O,UAAW,uBAAyBkN,EACpC9M,WAAqBwJ,IAAdwD,EAA0BA,EAAUO,KAAO,GAClDwC,aAAcxQ,KAAKwQ,aACnBC,cAAezQ,KAAKyQ,iBAIjBpC,EAtJoB,CAuJ3B,aAEa,O,qBChVfzH,EAAOpK,QAAU,kkC,oCCEjBA,EAAQC,YAAa,EACrBD,EAAQkU,qBAQR,SAA8BC,GAC5B,IAAIjR,GAAW,EAAIjC,EAAQmT,eACvB/P,GAAQ,EAAIrD,EAAOqT,YAAYC,EAAeC,eAC9C1O,GAAM,EAAI7E,EAAOwT,UAOrB,OANA,EAAIxT,EAAOyT,kBAAiB,WAC1B,GAAI5O,EAAI1D,QAAS,CACf,IAAIuS,EAAWrQ,EAAM6E,KAAKhG,EAAUiR,GACpCtO,EAAI1D,QAAQwS,SAAS,EAAGD,GAAY,MAErC,IACI,CACL7O,IAAKA,EACL+O,SAAU,WACJ/O,EAAI1D,SACNkC,EAAMsF,KAAKzG,EAAUiR,EAAYtO,EAAI1D,QAAQ0S,cApBrD,IAAIP,EAAiB,EAAQ,QAEzBtT,EAAS,EAAQ,QAEjBC,EAAU,EAAQ,S,oCCDP,IARf,SAAiB6T,GACf,IAAI3K,EAAQ,GACZ,OAAO,SAAU4K,GAEf,YADmBtH,IAAftD,EAAM4K,KAAoB5K,EAAM4K,GAAOD,EAAGC,IACvC5K,EAAM4K,M,oCC0DF,IC5DTC,EDiBN,SAAcC,GAGb,OAFAA,EAAMA,GAAOvK,OAAOsG,OAAO,MAEpB,CAQNkE,GAAI,SAAYxJ,EAAcyJ,IAC5BF,EAAIvJ,KAAUuJ,EAAIvJ,GAAQ,KAAKlL,KAAK2U,IAUtCC,IAAK,SAAa1J,EAAcyJ,GAC3BF,EAAIvJ,IACPuJ,EAAIvJ,GAAM2J,OAAOJ,EAAIvJ,GAAMkG,QAAQuD,KAAa,EAAG,IAYrDG,KAAM,SAAc5J,EAAc6J,IAChCN,EAAIvJ,IAAS,IAAI5J,QAAQ2M,KAAI,SAAU0G,GAAWA,EAAQI,OAC1DN,EAAI,MAAQ,IAAInT,QAAQ2M,KAAI,SAAU0G,GAAWA,EAAQzJ,EAAM6J,QCvDnDC,GACDR,O,oCCDfhV,EAAQC,YAAa,EACrBD,EAAQkU,qBAAuBlU,EAAQyV,gBAAkBzV,EAAQuU,mBAAgB,EAEjF,IAAID,EAAiB,EAAQ,QAE7BtU,EAAQuU,cAAgBD,EAAeoB,cAEvC,IAAIC,EAAmB,EAAQ,QAE/B3V,EAAQyV,gBAAkBE,EAAiBF,gBAE3C,IAAIG,EAAwB,EAAQ,QAEpC5V,EAAQkU,qBAAuB0B,EAAsB1B,sB,oCCfrD,8PAEA,SAASpE,EAAgBzF,EAAKlB,EAAKG,GAYjC,OAXIH,KAAOkB,EACTK,OAAOC,eAAeN,EAAKlB,EAAK,CAC9BG,MAAOA,EACPyG,YAAY,EACZC,cAAc,EACdC,UAAU,IAGZ5F,EAAIlB,GAAOG,EAGNe,EAGT,SAAS6F,IAeP,OAdAA,EAAWxF,OAAOyF,QAAU,SAAU9J,GACpC,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CACzC,IAAI6C,EAASpE,UAAUuB,GAEvB,IAAK,IAAIpE,KAAOiH,EACV1F,OAAOjG,UAAUwB,eAAe1C,KAAK6M,EAAQjH,KAC/C9C,EAAO8C,GAAOiH,EAAOjH,IAK3B,OAAO9C,IAGOgK,MAAM7M,KAAMwI,WAG9B,SAAS6J,EAAQnT,EAAQoT,GACvB,IAAI3I,EAAOzC,OAAOyC,KAAKzK,GAEvB,GAAIgI,OAAOiC,sBAAuB,CAChC,IAAIoJ,EAAUrL,OAAOiC,sBAAsBjK,GACvCoT,IAAgBC,EAAUA,EAAQjS,QAAO,SAAUkS,GACrD,OAAOtL,OAAOE,yBAAyBlI,EAAQsT,GAAKjG,eAEtD5C,EAAK3M,KAAK6P,MAAMlD,EAAM4I,GAGxB,OAAO5I,EAGT,SAAS8I,EAAe5P,GACtB,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CACzC,IAAI6C,EAAyB,MAAhBpE,UAAUuB,GAAavB,UAAUuB,GAAK,GAE/CA,EAAI,EACNsI,EAAQnL,OAAO0F,IAAS,GAAMjK,SAAQ,SAAUgD,GAC9C2G,EAAgBzJ,EAAQ8C,EAAKiH,EAAOjH,OAE7BuB,OAAOwL,0BAChBxL,OAAOyL,iBAAiB9P,EAAQqE,OAAOwL,0BAA0B9F,IAEjEyF,EAAQnL,OAAO0F,IAASjK,SAAQ,SAAUgD,GACxCuB,OAAOC,eAAetE,EAAQ8C,EAAKuB,OAAOE,yBAAyBwF,EAAQjH,OAKjF,OAAO9C,EAkBT,SAAS+P,EAAyBhG,EAAQiG,GACxC,GAAc,MAAVjG,EAAgB,MAAO,GAE3B,IAEIjH,EAAKoE,EAFLlH,EAlBN,SAAuC+J,EAAQiG,GAC7C,GAAc,MAAVjG,EAAgB,MAAO,GAC3B,IAEIjH,EAAKoE,EAFLlH,EAAS,GACTiQ,EAAa5L,OAAOyC,KAAKiD,GAG7B,IAAK7C,EAAI,EAAGA,EAAI+I,EAAWzK,OAAQ0B,IACjCpE,EAAMmN,EAAW/I,GACb8I,EAASzE,QAAQzI,IAAQ,IAC7B9C,EAAO8C,GAAOiH,EAAOjH,IAGvB,OAAO9C,EAMMkQ,CAA8BnG,EAAQiG,GAInD,GAAI3L,OAAOiC,sBAAuB,CAChC,IAAI6J,EAAmB9L,OAAOiC,sBAAsByD,GAEpD,IAAK7C,EAAI,EAAGA,EAAIiJ,EAAiB3K,OAAQ0B,IACvCpE,EAAMqN,EAAiBjJ,GACnB8I,EAASzE,QAAQzI,IAAQ,GACxBuB,OAAOjG,UAAUgS,qBAAqBlT,KAAK6M,EAAQjH,KACxD9C,EAAO8C,GAAOiH,EAAOjH,IAIzB,OAAO9C,EAGT,IAIIqQ,EAA0B,IAAMC,cAAc,IAE9CC,EAAoB,SAA2B1O,GACjD,OAAO,SAAUpF,GACf,IAAI+T,EAAgBC,EAAiBhU,EAAMiU,YAC3C,OAAoB,IAAMhU,cAAcmF,EAAWgI,EAAS,GAAIpN,EAAO,CACrEiU,WAAYF,OAKdC,EAAmB,SAA0BC,GAC/C,IAAIC,EAAoB,IAAM3C,WAAWqC,GACrCG,EAAgBG,EAMpB,OAJID,IACFF,EAnBoB,mBAmBOE,EAAcA,EAAWC,GAAqBf,EAAeA,EAAe,GAAIe,GAAoBD,IAG1HF,GAGLI,EAAc,SAAqBnU,GACrC,IAAI+T,EAAgBC,EAAiBhU,EAAMiU,YAC3C,OAAoB,IAAMhU,cAAc2T,EAAWQ,SAAU,CAC3D5N,MAAOuN,GACN/T,EAAM2P,WAIP0E,EAAW,CACbC,WAAY,OACZC,QAAS,SAAiB7V,GACxB,IAAIiR,EAAWjR,EAAKiR,SACpB,OAAoB,IAAM1P,cAAc,IAAMuU,SAAU,GAAI7E,KAG5D8E,EAAgC,IAAM1O,YAAW,SAAU/F,EAAO+C,GACpE,IAAI2R,EAAiB1U,EAAMiU,WACvBU,EAAU3U,EAAM2U,QAChBC,EAAe5U,EAAM4U,aACrBC,EAAa7U,EAAM6U,WACnBC,EAAMxB,EAAyBtT,EAAO,CAAC,aAAc,UAAW,eAAgB,eAEhFiU,EAAaD,EAAiBU,GAC9B9L,EAAO+L,EACPvP,EAAY6O,EAAW,GAAG3J,OAAOuK,EAAY,KAAKvK,OAAO1B,KAAUqL,EAAWrL,IAASyL,EAASzL,IAASgM,EAE7G,OAAIF,EACkB,IAAMzU,cAAcmF,EAAW+N,EAAeA,EAAe,CAC/EpQ,IAAKA,GACJ+R,GAAM,GAAI,CACXb,WAAYS,KAII,IAAMzU,cAAcmF,EAAW+N,EAAe,CAChEpQ,IAAKA,GACJ+R,OAIL,SAAS7U,EAAc2I,EAAM5I,GAC3B,IAAIiP,EAAO/F,UACPyL,EAAU3U,GAASA,EAAM2U,QAE7B,GAAoB,iBAAT/L,GAAqB+L,EAAS,CACvC,IAAII,EAAa9F,EAAKlG,OAClBiM,EAAwB,IAAIC,MAAMF,GACtCC,EAAsB,GAAKP,EAC3B,IAAIS,EAAW,GAEf,IAAK,IAAI7O,KAAOrG,EACVmD,eAAe1C,KAAKT,EAAOqG,KAC7B6O,EAAS7O,GAAOrG,EAAMqG,IAI1B6O,EAASN,aAAehM,EACxBsM,EAAuB,QAAoB,iBAATtM,EAAoBA,EAAO+L,EAC7DK,EAAsB,GAAKE,EAE3B,IAAK,IAAIzK,EAAI,EAAGA,EAAIsK,EAAYtK,IAC9BuK,EAAsBvK,GAAKwE,EAAKxE,GAGlC,OAAO,IAAMxK,cAAcsN,MAAM,KAAMyH,GAGzC,OAAO,IAAM/U,cAAcsN,MAAM,KAAM0B,GA7BzCwF,EAAiBlM,YAAc,oB,oCCvK/B,SAAS4M,EAAgBC,GACvB,OAAOA,GAAoB,iBAAPA,GAAmB,YAAaA,EAAKA,EAAY,QAAIA,EAG3E,IAAIC,EAAQ,EAAQ,QAEhBC,EAAiBH,EAAgBE,GAEjCE,EAAeJ,EAAgB,EAAQ,SAE3C,SAASnI,EAAgBzF,EAAKlB,EAAKG,GAYjC,OAXIH,KAAOkB,EACTK,OAAOC,eAAeN,EAAKlB,EAAK,CAC9BG,MAAOA,EACPyG,YAAY,EACZC,cAAc,EACdC,UAAU,IAGZ5F,EAAIlB,GAAOG,EAGNe,EAST,IAAIiO,IAAiC,oBAAXnU,SAA0BA,OAAOoU,WAAYpU,OAAOoU,SAASxV,eAmGvFqH,EAAOpK,QAjGP,SAAwBwY,EAAoBC,EAA2BC,GACrE,GAAkC,mBAAvBF,EACT,MAAM,IAAIG,MAAM,iDAGlB,GAAyC,mBAA9BF,EACT,MAAM,IAAIE,MAAM,wDAGlB,QAAgC,IAArBD,GAAgE,mBAArBA,EACpD,MAAM,IAAIC,MAAM,mEAOlB,OAAO,SAAcC,GACnB,GAAgC,mBAArBA,EACT,MAAM,IAAID,MAAM,sDAGlB,IACItU,EADAwU,EAAmB,GAGvB,SAASC,IACPzU,EAAQmU,EAAmBK,EAAiBpK,KAAI,SAAUhJ,GACxD,OAAOA,EAAS3C,UAGdiW,EAAWT,UACbG,EAA0BpU,GACjBqU,IACTrU,EAAQqU,EAAiBrU,IAI7B,IAAI0U,EAA0B,SAAUC,GA7C5C,IAAwBC,EAAUC,EAgD5B,SAASH,IACP,OAAOC,EAAW3I,MAAM7M,KAAMwI,YAAcxI,KAjDlB0V,EA8CDF,GA9CTC,EA8CHF,GA7CVtU,UAAYiG,OAAOsG,OAAOkI,EAAWzU,WAC9CwU,EAASxU,UAAU0O,YAAc8F,EACjCA,EAAS/F,UAAYgG,EAmDjBH,EAAWI,KAAO,WAChB,OAAO9U,GAGT0U,EAAWK,OAAS,WAClB,GAAIL,EAAWT,UACb,MAAM,IAAIK,MAAM,oFAGlB,IAAIU,EAAgBhV,EAGpB,OAFAA,OAAQoJ,EACRoL,EAAmB,GACZQ,GAGT,IAAI7U,EAASuU,EAAWtU,UAyBxB,OAvBAD,EAAO8U,sBAAwB,SAA+BC,GAC5D,OAAQlB,EAAakB,EAAW/V,KAAKV,QAGvC0B,EAAOgV,mBAAqB,WAC1BX,EAAiBrY,KAAKgD,MACtBsV,KAGFtU,EAAOU,mBAAqB,WAC1B4T,KAGFtU,EAAOc,qBAAuB,WAC5B,IAAImU,EAAQZ,EAAiBjH,QAAQpO,MACrCqV,EAAiBxD,OAAOoE,EAAO,GAC/BX,KAGFtU,EAAOiC,OAAS,WACd,OAAO2R,EAAerV,cAAc6V,EAAkBpV,KAAKV,QAGtDiW,EAjDqB,CAkD5BZ,EAAMjQ,WAMR,OAJA4H,EAAgBiJ,EAAY,cAAe,cA5E7C,SAAwBH,GACtB,OAAOA,EAAiBvN,aAAeuN,EAAiBhN,MAAQ,YA2EL8N,CAAed,GAAoB,KAE9F9I,EAAgBiJ,EAAY,YAAaT,GAElCS,K,qBCjHX3O,EAAOpK,QAfP,SAAuCoQ,EAAQiG,GAC7C,GAAc,MAAVjG,EAAgB,MAAO,GAC3B,IAEIjH,EAAKoE,EAFLlH,EAAS,GACTiQ,EAAa5L,OAAOyC,KAAKiD,GAG7B,IAAK7C,EAAI,EAAGA,EAAI+I,EAAWzK,OAAQ0B,IACjCpE,EAAMmN,EAAW/I,GACb8I,EAASzE,QAAQzI,IAAQ,IAC7B9C,EAAO8C,GAAOiH,EAAOjH,IAGvB,OAAO9C,GAIT+D,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,qBChBxED,EAAQ2Z,SAAW,SAAAzR,GAAS,OAAIA,I,oCCAhC,4IAAIgI,EAAWxF,OAAOyF,QAAU,SAAU9J,GAAU,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CAAE,IAAI6C,EAASpE,UAAUuB,GAAI,IAAK,IAAIpE,KAAOiH,EAAc1F,OAAOjG,UAAUwB,eAAe1C,KAAK6M,EAAQjH,KAAQ9C,EAAO8C,GAAOiH,EAAOjH,IAAY,OAAO9C,GAEnPuT,EAAc,SAAqBxJ,GACrC,IAAIyJ,EAAmBzJ,EAAOlN,SAC1B4W,EAASD,EAAiBC,OAC1BC,EAAOF,EAAiBE,KACxB9R,EAAO4R,EAAiB5R,KACxB+R,EAASH,EAAiBG,OAC1BC,EAAWJ,EAAiBI,SAC5BC,EAAOL,EAAiBK,KACxBC,EAAWN,EAAiBM,SAC5BC,EAAOP,EAAiBO,KACxBxV,EAAWwL,EAAOlN,SAAS0B,UAG1BA,GAAYqD,GAAQqQ,IAEvB1T,EADU,IAAIuJ,IAAIlG,GACHrD,UAGjB,MAAO,CACLA,SAAUmD,UAAUsS,UAAUzV,IAC9BkV,OAAQA,EACRC,KAAMA,EACN9R,KAAMA,EACN+R,OAAQA,EACRC,SAAUA,EACVC,KAAMA,EACNC,SAAUA,EACVC,KAAMA,EACN/V,MAAO+L,EAAOkK,QAAQjW,MACtB8E,IAAKiH,EAAOkK,QAAQjW,OAAS+L,EAAOkK,QAAQjW,MAAM8E,KAAO,YAIzDoR,EAAgB,SAAuBnK,EAAQtH,GACjD,IAAI0R,EAAY,GACZtX,EAAW0W,EAAYxJ,GACvBqK,GAAgB,EAChBC,EAAoB,aAExB,MAAO,CACL,eACE,OAAOxX,GAGT,oBACE,OAAOuX,GAGTE,sBAAuB,WACrBF,GAAgB,EAChBC,KAEFE,OAAQ,SAAgBC,GACtBL,EAAUha,KAAKqa,GAEf,IAAIC,EAAmB,WACrB5X,EAAW0W,EAAYxJ,GACvByK,EAAS,CAAE3X,SAAUA,EAAU6X,OAAQ,SAKzC,OAFA3K,EAAO4K,iBAAiB,WAAYF,GAE7B,WACL1K,EAAO6K,oBAAoB,WAAYH,GACvCN,EAAYA,EAAU1W,QAAO,SAAUgR,GACrC,OAAOA,IAAO+F,OAIpBpa,SAAU,SAAkBqE,GAC1B,IAAItD,EAAOwK,UAAUH,OAAS,QAAsB4B,IAAjBzB,UAAU,GAAmBA,UAAU,GAAK,GAC3E3H,EAAQ7C,EAAK6C,MACb6W,EAAe1Z,EAAKjB,QACpBA,OAA2BkN,IAAjByN,GAAqCA,EAEnD,GAAkB,iBAAPpW,EACTsL,EAAOkK,QAAQa,GAAGrW,OACb,CACLT,EAAQ6L,EAAS,GAAI7L,EAAO,CAAE8E,IAAKiS,KAAKC,MAAQ,KAEhD,IACMZ,GAAiBla,EACnB6P,EAAOkK,QAAQgB,aAAajX,EAAO,KAAMS,GAEzCsL,EAAOkK,QAAQiB,UAAUlX,EAAO,KAAMS,GAExC,MAAOuC,GACP+I,EAAOlN,SAAS3C,EAAU,UAAY,UAAUuE,IAIpD5B,EAAW0W,EAAYxJ,GACvBqK,GAAgB,EAChB,IAAIe,EAAa,IAAIC,SAAQ,SAAUC,GACrC,OAAOhB,EAAoBgB,KAK7B,OAHAlB,EAAUrU,SAAQ,SAAU0U,GAC1B,OAAOA,EAAS,CAAE3X,SAAUA,EAAU6X,OAAQ,YAEzCS,KAOTG,EAAqB,WACvB,IAAIC,EAAc5P,UAAUH,OAAS,QAAsB4B,IAAjBzB,UAAU,GAAmBA,UAAU,GAAK,IAElF6P,EAAcD,EAAYhK,QAAQ,KAClCkK,EAAkB,CACpBlX,SAAUiX,GAAe,EAAID,EAAYG,OAAO,EAAGF,GAAeD,EAClE9B,OAAQ+B,GAAe,EAAID,EAAYG,OAAOF,GAAe,IAE3DpC,EAAQ,EACRuC,EAAQ,CAACF,GACTG,EAAS,CAAC,MAEd,MAAO,CACL,eACE,OAAOD,EAAMvC,IAEfuB,iBAAkB,SAA0BpP,EAAMkJ,KAClDmG,oBAAqB,SAA6BrP,EAAMkJ,KAExDwF,QAAS,CACP,cACE,OAAO0B,GAET,YACE,OAAOvC,GAET,YACE,OAAOwC,EAAOxC,IAEhB8B,UAAW,SAAmBlX,EAAO6X,EAAGC,GACtC,IAAIC,EAAaD,EAAIjO,MAAM,KACvBtJ,EAAWwX,EAAW,GACtBC,EAAcD,EAAW,GACzBtC,OAAyBrM,IAAhB4O,EAA4B,GAAKA,EAE9C5C,IACAuC,EAAMxb,KAAK,CAAEoE,SAAUA,EAAUkV,OAAQA,EAAOjO,OAAS,IAAMiO,EAASA,IACxEmC,EAAOzb,KAAK6D,IAEdiX,aAAc,SAAsBjX,EAAO6X,EAAGC,GAC5C,IAAIG,EAAcH,EAAIjO,MAAM,KACxBtJ,EAAW0X,EAAY,GACvBC,EAAeD,EAAY,GAC3BxC,OAA0BrM,IAAjB8O,EAA6B,GAAKA,EAE/CP,EAAMvC,GAAS,CAAE7U,SAAUA,EAAUkV,OAAQA,GAC7CmC,EAAOxC,GAASpV,GAElB8W,GAAI,SAAYrW,GACd,IAAI0X,EAAW/C,EAAQ3U,EAEnB0X,EAAW,GAAKA,EAAWP,EAAOpQ,OAAS,IAI/C4N,EAAQ+C,OASZlE,IAAiC,oBAAXnU,SAA0BA,OAAOoU,WAAYpU,OAAOoU,SAASxV,eAKnF0Z,EAAgBlC,EAHXjC,EAAYnU,OAASwX,KAI1Blb,EAAWgc,EAAchc,U,oCClL7B,gBACIic,EAAkB,45HAElBjD,EAAQ,aAAQ,SAAUkD,GAC5B,OAAOD,EAAgBE,KAAKD,IAAgC,MAAvBA,EAAKE,WAAW,IAE3B,MAAvBF,EAAKE,WAAW,IAEhBF,EAAKE,WAAW,GAAK,MAIX,O,mBCZfzS,EAAOpK,QAAU,0/C,kCCEjB,IAAIF,EAAyBC,EAAQ,QAEjC+c,EAAU/c,EAAQ,QAElBgd,EAAcjd,EAAuBC,EAAQ,SAEjDC,EAAQgd,cAAgB,SAAUd,EAAGe,QACb,IAAlBA,IACFA,EAAgB,KAGlB,EAAIF,EAAYrc,SAASyD,OAAQ8Y,GAAe,SAAUhV,IACxD,EAAI6U,EAAQrc,UAAUwH,Q,kCCd1B,6HAEMiV,EAAwBvG,wBAA9B,IAEawG,EAAc,SAAAC,GACzB,IAAMC,EAAehJ,qBAArB,GACA,OAAO+I,GAAP,GAGWE,EAAmB,SAAC,GAAD,IAAGC,EAAH,aAAe9K,EAAf,kBAC9B,kBACEyK,EADF,SAEE,CAAE5T,MAAOiU,GAHmB,K,mBCLhCnT,EAAOpK,QAJP,WACE,MAAM,IAAIwd,UAAU,yIAItBpT,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,kCCLxE,kDACe,SAASwd,EAA4BC,EAAGC,GACrD,GAAKD,EAAL,CACA,GAAiB,iBAANA,EAAgB,OAAO,YAAiBA,EAAGC,GACtD,IAAIC,EAAIlT,OAAOjG,UAAUoZ,SAASta,KAAKma,GAAG5b,MAAM,GAAI,GAEpD,MADU,WAAN8b,GAAkBF,EAAEvK,cAAayK,EAAIF,EAAEvK,YAAYvH,MAC7C,QAANgS,GAAqB,QAANA,EAAoB7F,MAAM+F,KAAKJ,GACxC,cAANE,GAAqB,2CAA2ChB,KAAKgB,GAAW,YAAiBF,EAAGC,QAAxG,K,kCCLF,IAAI3T,EAA4B,mBAAX+T,QAAoD,iBAApBA,OAAOC,SAAwB,SAAU3T,GAC5F,cAAcA,GACZ,SAAUA,GACZ,OAAOA,GAAyB,mBAAX0T,QAAyB1T,EAAI8I,cAAgB4K,QAAU1T,IAAQ0T,OAAOtZ,UAAY,gBAAkB4F,GAG3H,SAAS4T,EAAgBxY,EAAUyY,GACjC,KAAMzY,aAAoByY,GACxB,MAAM,IAAIV,UAAU,qCAIxB,SAASW,EAA2BC,EAAM7a,GACxC,IAAK6a,EACH,MAAM,IAAIC,eAAe,6DAG3B,OAAO9a,GAAyB,iBAATA,GAAqC,mBAATA,EAA8B6a,EAAP7a,EAG5E,SAAS+a,EAAUrF,EAAUC,GAC3B,GAA0B,mBAAfA,GAA4C,OAAfA,EACtC,MAAM,IAAIsE,UAAU,kEAAoEtE,GAG1FD,EAASxU,UAAYiG,OAAOsG,OAAOkI,GAAcA,EAAWzU,UAAW,CACrE0O,YAAa,CACX7J,MAAO2P,EACPlJ,YAAY,EACZE,UAAU,EACVD,cAAc,KAGdkJ,IAAYxO,OAAO6T,eAAiB7T,OAAO6T,eAAetF,EAAUC,GAAcD,EAAS/F,UAAYgG,GAG7G,IAAIf,EAAQ,EAAQ,QAEhBqG,EAAY,EAAQ,QAEpBC,EAAmB,GACnBC,EAAqB,GAYzB,SAASC,EAAKC,GACZ,IAAIC,EAAUD,IACVva,EAAQ,CACVya,SAAS,EACTC,OAAQ,KACRC,MAAO,MAWT,OATA3a,EAAMwa,QAAUA,EAAQI,MAAK,SAAUF,GAGrC,OAFA1a,EAAMya,SAAU,EAChBza,EAAM0a,OAASA,EACRA,KACNG,OAAM,SAAUC,GAGjB,MAFA9a,EAAMya,SAAU,EAChBza,EAAM2a,MAAQG,EACRA,KAED9a,EAGT,SAAS+a,EAAQ/U,GACf,IAAIhG,EAAQ,CACVya,SAAS,EACTC,OAAQ,GACRC,MAAO,MAELK,EAAW,GAEf,IACE3U,OAAOyC,KAAK9C,GAAKlE,SAAQ,SAAUgD,GACjC,IAAImW,EAASX,EAAKtU,EAAIlB,IAEjBmW,EAAOR,QAIVza,EAAMya,SAAU,GAHhBza,EAAM0a,OAAO5V,GAAOmW,EAAOP,OAC3B1a,EAAM2a,MAAQM,EAAON,OAKvBK,EAAS7e,KAAK8e,EAAOT,SACrBS,EAAOT,QAAQI,MAAK,SAAUvD,GAC5BrX,EAAM0a,OAAO5V,GAAOuS,KACnBwD,OAAM,SAAUC,GACjB9a,EAAM2a,MAAQG,QAGlB,MAAOA,GACP9a,EAAM2a,MAAQG,EAUhB,OAPA9a,EAAMwa,QAAUpD,QAAQxG,IAAIoK,GAAUJ,MAAK,SAAUvD,GAEnD,OADArX,EAAMya,SAAU,EACTpD,KACNwD,OAAM,SAAUC,GAEjB,MADA9a,EAAMya,SAAU,EACVK,KAED9a,EAOT,SAASoC,EAAOsY,EAAQjc,GACtB,OAAOqV,EAAMpV,eALEsH,EAKoB0U,IAJrB1U,EAAIpK,WAAaoK,EAAI3J,QAAU2J,EAIDvH,GAL9C,IAAiBuH,EAQjB,SAASkV,EAAwBC,EAAQ1W,GACvC,IAAI2W,EAAQC,EAEZ,IAAK5W,EAAQgW,QACX,MAAM,IAAInG,MAAM,iDAGlB,IAAIgH,EAAOjV,OAAOyF,OAAO,CACvByO,OAAQ,KACRE,QAAS,KACTc,MAAO,IACPC,QAAS,KACTpZ,OAAQA,EACRqZ,QAAS,KACTC,QAAS,MACRjX,GACC4S,EAAM,KAEV,SAASsE,IAKP,OAJKtE,IACHA,EAAM8D,EAAOG,EAAKf,SAGblD,EAAImD,QAab,OAVAJ,EAAiBje,KAAKwf,GAEM,mBAAjBL,EAAKG,SACdpB,EAAmBle,MAAK,WACtB,GA3GkByf,EA2GCN,EAAKG,QA1GsE,WAAlC9V,EAAQ,MAIjEiW,IAAeC,OAAM,SAAUC,GACpC,YAA2B,IAAbA,QAAqE,IAAlC,IAAoBA,MAsGjE,OAAOH,IA5Gf,IAAwBC,KAiHfP,EAAQD,EAAS,SAAUpc,GAGhC,SAAS+c,EAAkBtd,GACzBmb,EAAgBza,KAAM4c,GAEtB,IAAI9c,EAAQ6a,EAA2B3a,KAAMH,EAAiBE,KAAKC,KAAMV,IAsBzE,OApBAQ,EAAM+c,MAAQ,WACZ/c,EAAMgd,SAAS,CACbtB,MAAO,KACPF,SAAS,EACTyB,UAAU,IAGZ7E,EAAM8D,EAAOG,EAAKf,QAElBtb,EAAMkd,eAGRR,IACA1c,EAAMe,MAAQ,CACZ2a,MAAOtD,EAAIsD,MACXyB,WAAW,EACXF,UAAU,EACVzB,QAASpD,EAAIoD,QACbC,OAAQrD,EAAIqD,QAEPzb,EAgGT,OA3HAgb,EAAU8B,EAAmB/c,GA8B7B+c,EAAkBM,QAAU,WAC1B,OAAOV,KAGTI,EAAkB3b,UAAU+U,mBAAqB,WAC/ChW,KAAKmd,UAAW,EAEhBnd,KAAKgd,eAGPJ,EAAkB3b,UAAU+b,YAAc,WACxC,IAAIza,EAASvC,KAQb,GANIA,KAAKod,QAAQC,UAAY9I,MAAM+I,QAAQnB,EAAKI,UAC9CJ,EAAKI,QAAQ5Z,SAAQ,SAAU4a,GAC7Bhb,EAAO6a,QAAQC,SAASG,OAAOD,MAI9BrF,EAAIoD,QAAT,CAI0B,iBAAfa,EAAKC,QACK,IAAfD,EAAKC,MACPpc,KAAK8c,SAAS,CACZG,WAAW,IAGbjd,KAAKyd,OAASC,YAAW,WACvBnb,EAAOua,SAAS,CACdG,WAAW,MAEZd,EAAKC,QAIgB,iBAAjBD,EAAKE,UACdrc,KAAK2d,SAAWD,YAAW,WACzBnb,EAAOua,SAAS,CACdC,UAAU,MAEXZ,EAAKE,UAGV,IAAIuB,EAAS,WACNrb,EAAO4a,WAIZ5a,EAAOua,SAAS,CACdtB,MAAOtD,EAAIsD,MACXD,OAAQrD,EAAIqD,OACZD,QAASpD,EAAIoD,UAGf/Y,EAAOsb,mBAGT3F,EAAImD,QAAQI,MAAK,WACfmC,OACClC,OAAM,SAAUC,GACjBiC,SAIJhB,EAAkB3b,UAAUa,qBAAuB,WACjD9B,KAAKmd,UAAW,EAEhBnd,KAAK6d,kBAGPjB,EAAkB3b,UAAU4c,eAAiB,WAC3CC,aAAa9d,KAAKyd,QAClBK,aAAa9d,KAAK2d,WAGpBf,EAAkB3b,UAAUgC,OAAS,WACnC,OAAIjD,KAAKa,MAAMya,SAAWtb,KAAKa,MAAM2a,MAC5B7G,EAAMpV,cAAc4c,EAAKb,QAAS,CACvCyC,UAAW/d,KAAKa,MAAMya,QACtB2B,UAAWjd,KAAKa,MAAMoc,UACtBF,SAAU/c,KAAKa,MAAMkc,SACrBvB,MAAOxb,KAAKa,MAAM2a,MAClBqB,MAAO7c,KAAK6c,QAEL7c,KAAKa,MAAM0a,OACbY,EAAKlZ,OAAOjD,KAAKa,MAAM0a,OAAQvb,KAAKV,OAEpC,MAIJsd,EA5He,CA6HtBjI,EAAMjQ,WAAYuX,EAAOtU,aAAe,CACxC0V,SAAUrC,EAAUgD,MAAM,CACxBR,OAAQxC,EAAUpW,KAAKC,cAExBqX,EAGL,SAAS+B,EAAS9B,GAChB,OAAOJ,EAAwBZ,EAAMgB,GAWvC8B,EAAS7T,IART,SAAqB+R,GACnB,GAA2B,mBAAhBA,EAAKlZ,OACd,MAAM,IAAIkS,MAAM,2DAGlB,OAAO4G,EAAwBH,EAASO,IAK1C,IAAI+B,EAAU,SAAUC,GAGtB,SAASD,IAGP,OAFAzD,EAAgBza,KAAMke,GAEfvD,EAA2B3a,KAAMme,EAAkBtR,MAAM7M,KAAMwI,YAexE,OApBAsS,EAAUoD,EAASC,GAQnBD,EAAQjd,UAAUmd,gBAAkB,WAClC,MAAO,CACLf,SAAU,CACRG,OAAQxd,KAAKV,MAAMke,UAKzBU,EAAQjd,UAAUgC,OAAS,WACzB,OAAO0R,EAAM0J,SAASC,KAAKte,KAAKV,MAAM2P,WAGjCiP,EArBK,CAsBZvJ,EAAMjQ,WAYR,SAAS6Z,EAAkBC,GAGzB,IAFA,IAAI3C,EAAW,GAER2C,EAAanW,QAAQ,CAC1B,IAAImU,EAAOgC,EAAalO,MACxBuL,EAAS7e,KAAKwf,KAGhB,OAAOvE,QAAQxG,IAAIoK,GAAUJ,MAAK,WAChC,GAAI+C,EAAanW,OACf,OAAOkW,EAAkBC,MApB/BN,EAAQvZ,UAAY,CAClB6Y,OAAQxC,EAAUpW,KAAKC,YAEzBqZ,EAAQzW,kBAAoB,CAC1B4V,SAAUrC,EAAUgD,MAAM,CACxBR,OAAQxC,EAAUpW,KAAKC,aACtBA,YAELoZ,EAASC,QAAUA,EAiBnBD,EAASQ,WAAa,WACpB,OAAO,IAAIxG,SAAQ,SAAUrZ,EAAS8f,GACpCH,EAAkBtD,GAAkBQ,KAAK7c,EAAS8f,OAItDT,EAASU,aAAe,WACtB,OAAO,IAAI1G,SAAQ,SAAUrZ,EAAS8f,GAEpCH,EAAkBrD,GAAoBO,KAAK7c,EAASA,OAIxDgI,EAAOpK,QAAUyhB,G,mBC1WjBrX,EAAOpK,QAJP,SAA0BoiB,GACxB,GAAsB,oBAAXrE,QAA0BA,OAAOC,YAAYtT,OAAO0X,GAAO,OAAOrK,MAAM+F,KAAKsE,IAI1FhY,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,kCCHxE,IAAIoiB,EAA0B,EAAQ,QAElCviB,EAAyB,EAAQ,QAErCE,EAAQC,YAAa,EACrBD,EAAQ0V,cAAgB1V,EAAQuU,mBAAgB,EAEhD,IAAI3T,EAA0Bd,EAAuB,EAAQ,SAEzDe,EAAkBf,EAAuB,EAAQ,SAEjDqY,EAAQkK,EAAwB,EAAQ,SAExCthB,EAAajB,EAAuB,EAAQ,SAE5CwiB,EAAkB,EAAQ,QAE1B/N,EAA6B4D,EAAMxB,cAAc,IAAI2L,EAAgBrZ,gBACzEjJ,EAAQuU,cAAgBA,EACxBA,EAAclJ,YAAc,sBAE5B,IAAIqK,EAA6B,SAAUrS,GAGzC,SAASqS,IAGP,IAFA,IAAIpS,EAEKif,EAAOvW,UAAUH,OAAQkG,EAAO,IAAIgG,MAAMwK,GAAOC,EAAO,EAAGA,EAAOD,EAAMC,IAC/EzQ,EAAKyQ,GAAQxW,UAAUwW,GAuCzB,OApCAlf,EAAQD,EAAiBE,KAAK8M,MAAMhN,EAAkB,CAACG,MAAM4J,OAAO2E,KAAUvO,MACxEif,cAAgB,IAAIH,EAAgBrZ,eAE1C3F,EAAMof,eAAiB,WACrB,IAAIvZ,EAAM7F,EAAMR,MAAMI,SAASiG,IAE3BA,GACF7F,EAAMmf,cAAc9Y,KAAKrG,EAAMR,MAAMI,SAAUiG,EAAKhF,OAAOwe,UAI/Drf,EAAMsf,aAAe,SAAUlO,EAAUvP,GACnC7B,EAAMuf,mBAAmB1d,EAAW7B,EAAMR,QAC5CqB,OAAOwQ,SAAS,EAAGD,IAIvBpR,EAAMwf,aAAe,SAAU/I,EAAM5U,GACnC,IAAI4d,EAAOxK,SAASyK,eAAejJ,EAAKkJ,UAAU,IAE9CF,GAAQzf,EAAMuf,mBAAmB1d,EAAW7B,EAAMR,QACpDigB,EAAKG,kBAIT5f,EAAMuf,mBAAqB,SAAUM,EAAiBC,GACpD,IAAIP,EAAqBvf,EAAMR,MAAM+f,mBAErC,OAAKA,GAKEA,EAAmBtf,MAAK,EAAI3C,EAAwBF,SAAS4C,GAAQ6f,EAAiBC,IAGxF9f,GA7CT,EAAIzC,EAAgBH,SAASgV,EAAerS,GAgD5C,IAAImB,EAASkR,EAAcjR,UAwD3B,OAtDAD,EAAOa,kBAAoB,WAEzB,IAAIge,EADJlf,OAAO6W,iBAAiB,SAAUxX,KAAKkf,gBAEvC,IAAIY,EAAuB9f,KAAKV,MAAMI,SAClCiG,EAAMma,EAAqBna,IAC3B4Q,EAAOuJ,EAAqBvJ,KAE5B5Q,IACFka,EAAiB7f,KAAKif,cAAcvZ,KAAK1F,KAAKV,MAAMI,SAAUiG,IAG5Dka,EACF7f,KAAKof,aAAaS,OAAgB5V,GACzBsM,GACTvW,KAAKsf,aAAazI,UAAUN,QAAOtM,IAIvCjJ,EAAOc,qBAAuB,WAC5BnB,OAAO8W,oBAAoB,SAAUzX,KAAKkf,iBAG5Cle,EAAOU,mBAAqB,SAA4BC,GACtD,IAGIke,EAHAE,EAAwB/f,KAAKV,MAAMI,SACnC6W,EAAOwJ,EAAsBxJ,KAC7B5Q,EAAMoa,EAAsBpa,IAG5BA,IACFka,EAAiB7f,KAAKif,cAAcvZ,KAAK1F,KAAKV,MAAMI,SAAUiG,IAY5D4Q,EACFvW,KAAKsf,aAAazI,UAAUN,GAAO5U,GAEnC3B,KAAKof,aAAaS,EAAgBle,IAItCX,EAAOiC,OAAS,WACd,OAAoB0R,EAAMpV,cAAcwR,EAAc2C,SAAU,CAC9D5N,MAAO9F,KAAKif,eACXjf,KAAKV,MAAM2P,WAGTiD,EAzGwB,CA0G/ByC,EAAMjQ,WAERlI,EAAQ0V,cAAgBA,EACxBA,EAAcvN,UAAY,CACxB0a,mBAAoB9hB,EAAWL,QAAQ0H,KACvCqK,SAAU1R,EAAWL,QAAQ8iB,QAAQnb,WACrCnF,SAAUnC,EAAWL,QAAQgC,OAAO2F,a,kCCvItC,kEAAO,IAAMob,EAA6B,YAKzB,IAJAtf,OAAOuf,QACpB,0EAIAvf,OAAOjB,SAASygB,W,mBCLpBvZ,EAAOpK,QAAU,SAAsB4jB,EAAMC,EAAM1X,EAAS2X,GAC1D,IAAIC,EAAM5X,EAAUA,EAAQ5I,KAAKugB,EAAgBF,EAAMC,QAAQ,EAE/D,QAAY,IAARE,EACF,QAASA,EAGX,GAAIH,IAASC,EACX,OAAO,EAGT,GAAoB,iBAATD,IAAsBA,GAAwB,iBAATC,IAAsBA,EACpE,OAAO,EAGT,IAAIG,EAAQtZ,OAAOyC,KAAKyW,GACpBK,EAAQvZ,OAAOyC,KAAK0W,GAExB,GAAIG,EAAMnY,SAAWoY,EAAMpY,OACzB,OAAO,EAKT,IAFA,IAAIqY,EAAkBxZ,OAAOjG,UAAUwB,eAAe1B,KAAKsf,GAElDM,EAAM,EAAGA,EAAMH,EAAMnY,OAAQsY,IAAO,CAC3C,IAAIhb,EAAM6a,EAAMG,GAEhB,IAAKD,EAAgB/a,GACnB,OAAO,EAGT,IAAIib,EAASR,EAAKza,GACdkb,EAASR,EAAK1a,GAGlB,IAAY,KAFZ4a,EAAM5X,EAAUA,EAAQ5I,KAAKugB,EAAgBM,EAAQC,EAAQlb,QAAO,SAEvC,IAAR4a,GAAkBK,IAAWC,EAChD,OAAO,EAIX,OAAO,I,osBClCHC,E,kGACJ7d,OAAA,WACE,IAAM3D,EAAK,OACNU,KAAKV,OADC,IAETkM,OAAO,EAAD,KACDD,YAAgBvL,KAAKV,MAAMI,SAAS0B,WACpCpB,KAAKV,MAAMyhB,cAAcC,KAAKC,YAAYC,UAE/CC,YAAanhB,KAAKV,MAAM2hB,cAQpBG,EALuBC,oBAAU,2BAA4B,CACjE/hB,MAAOU,KAAKV,MACZ8b,OAAQkG,iBAZH,IAiBL/hB,wBAAcS,KAAKV,MAAMyhB,cAAcjY,UAA1B,OACRxJ,GADQ,IAEXqG,IAAK3F,KAAKV,MAAM1C,MAAQoD,KAAKV,MAAMyhB,cAAcQ,KAAK3kB,QAY1D,OAToBykB,oBAAU,kBAE5B,CAAErB,QAASoB,EAAa9hB,SACxB8hB,GACA,YACE,MAAO,CAAEpB,QADK,EAAblE,OACyBxc,YAE5BgR,O,GA9BqBqE,IAAMjQ,WA2ClBoc,O,qBClDf,IAAIU,EAAmB,EAAQ,QAM/B5a,EAAOpK,QAJP,SAA4BilB,GAC1B,GAAIlN,MAAM+I,QAAQmE,GAAM,OAAOD,EAAiBC,IAIlD7a,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,kCCPxE,uBACe,WACbkY,U,iJCEa,SAAS+M,EAAmBD,GACzC,OCJa,SAA4BA,GACzC,GAAIlN,MAAM+I,QAAQmE,GAAM,OAAO,OAAAD,EAAA,GAAiBC,GDGzC,CAAkBA,IELZ,SAA0B7C,GACvC,GAAsB,oBAAXrE,QAA0BA,OAAOC,YAAYtT,OAAO0X,GAAO,OAAOrK,MAAM+F,KAAKsE,GFIvD,CAAgB6C,IAAQ,OAAAE,EAAA,GAA2BF,IGLvE,WACb,MAAM,IAAIzH,UAAU,wIHIwE,K,kCIL9F,2UAIIlc,EAAa,SAAoBkB,EAAQsX,GAC3C,OAAOtX,EAAOuZ,OAAO,EAAGjC,EAAOjO,UAAYiO,GAwBzClL,EAAO,SAAcwW,EAAQjJ,GAW/B,IAVA,IAAIkJ,OAAQ,EACRC,OAAW,EAGXC,EADapJ,EAAIjO,MAAM,KACE,GAEzBsX,EAAcC,EAAWF,GACzBG,EAA+B,KAAnBF,EAAY,GACxBG,EAASC,EAAWR,GAEf7X,EAAI,EAAGsY,EAAIF,EAAO9Z,OAAQ0B,EAAIsY,EAAGtY,IAAK,CAC7C,IAAIuY,GAAS,EACThX,EAAQ6W,EAAOpY,GAAGuB,MAEtB,GAAIA,EAAMpO,QACR4kB,EAAW,CACTxW,MAAOA,EACPE,OAAQ,GACRmN,IAAKA,OAJT,CAcA,IALA,IAAI4J,EAAgBN,EAAW3W,EAAM1O,MACjC4O,EAAS,GACTgX,EAAMC,KAAKD,IAAIR,EAAY3Z,OAAQka,EAAcla,QACjD4N,EAAQ,EAELA,EAAQuM,EAAKvM,IAAS,CAC3B,IAAIyM,EAAeH,EAActM,GAC7B0M,EAAaX,EAAY/L,GAE7B,GAAI2M,EAAQF,GAAe,CAKzBlX,EADYkX,EAAapkB,MAAM,IAAM,KACrB0jB,EAAY1jB,MAAM2X,GAAOhL,IAAIT,oBAAoBhK,KAAK,KACtE,MAGF,QAAmByJ,IAAf0Y,EAA0B,CAI5BL,GAAS,EACT,MAGF,IAAIO,EAAeC,EAAQC,KAAKL,GAEhC,GAAIG,IAAiBX,EAAW,EACuC,IAA5Cc,EAAc5U,QAAQyU,EAAa,KAC6J,KAAU,GACnO,IAAI/c,EAAQ0E,mBAAmBmY,GAC/BnX,EAAOqX,EAAa,IAAM/c,OACrB,GAAI4c,IAAiBC,EAAY,CAItCL,GAAS,EACT,OAIJ,IAAKA,EAAQ,CACXT,EAAQ,CACNvW,MAAOA,EACPE,OAAQA,EACRmN,IAAK,IAAMqJ,EAAY1jB,MAAM,EAAG2X,GAAOzV,KAAK,MAE9C,QAIJ,OAAOqhB,GAASC,GAAY,MAK1BD,EAAQ,SAAejlB,EAAM+b,GAC/B,OAAOvN,EAAK,CAAC,CAAExO,KAAMA,IAAS+b,IA6B5B/Z,EAAU,SAAiB0C,EAAIlD,GAEjC,GAAIN,EAAWwD,EAAI,KACjB,OAAOA,EAGT,IAAI2hB,EAAY3hB,EAAGoJ,MAAM,KACrBwY,EAAaD,EAAU,GACvBE,EAAUF,EAAU,GAGpBG,EADchlB,EAAKsM,MAAM,KACE,GAE3B2Y,EAAapB,EAAWiB,GACxBI,EAAerB,EAAWmB,GAG9B,GAAsB,KAAlBC,EAAW,GACb,OAAOE,EAASH,EAAcD,GAIhC,IAAKrlB,EAAWulB,EAAW,GAAI,KAAM,CACnC,IAAIjiB,EAAWkiB,EAAa1Z,OAAOyZ,GAAY7iB,KAAK,KACpD,OAAO+iB,GAA2B,MAAjBH,EAAuB,GAAK,KAAOhiB,EAAU+hB,GAUhE,IAFA,IAAIK,EAAcF,EAAa1Z,OAAOyZ,GAClCI,EAAW,GACN1Z,EAAI,EAAGsY,EAAImB,EAAYnb,OAAQ0B,EAAIsY,EAAGtY,IAAK,CAClD,IAAI2Z,EAAUF,EAAYzZ,GACV,OAAZ2Z,EAAkBD,EAASnT,MAA2B,MAAZoT,GAAiBD,EAASzmB,KAAK0mB,GAG/E,OAAOH,EAAS,IAAME,EAASjjB,KAAK,KAAM2iB,IAMxCQ,EAAe,SAAsB/mB,EAAM4O,GAC7C,IAAIoY,EAAchnB,EAAK8N,MAAM,KACzBmZ,EAAWD,EAAY,GACvBE,EAAeF,EAAY,GAC3BG,OAAyB9Z,IAAjB6Z,EAA6B,GAAKA,EAG1CE,EAAkB,IADP/B,EAAW4B,GACW5Y,KAAI,SAAUyY,GACjD,IAAI7B,EAAQiB,EAAQC,KAAKW,GACzB,OAAO7B,EAAQrW,EAAOqW,EAAM,IAAM6B,KACjCljB,KAAK,KACJyjB,EAAmBzY,EAAO9L,SAE1BwkB,GADJD,OAAwCha,IAArBga,EAAiC,GAAKA,GACZ3N,OAGzC6N,QAFmCla,IAA1Bia,EAAsC,GAAKA,GAE/BxZ,MAAM,KAAK,IAAM,GAE1C,OADAsZ,EAAkBT,EAASS,EAAiBD,EAAOI,IAIjDC,EAAmB,SAA0B9J,EAAMhZ,GACrD,IAAIhB,EAAS,SAAgBojB,GAC3B,OAAOW,EAAUX,IAInB,OAFiBzB,EAAW3H,GAAMha,OAAOA,GAAQgkB,OAAO9jB,KAAK,OAC9CyhB,EAAW3gB,GAAIhB,OAAOA,GAAQgkB,OAAO9jB,KAAK,MAMvDsiB,EAAU,SAWVuB,EAAY,SAAmBX,GACjC,OAAOZ,EAAQ1J,KAAKsK,IAElBd,EAAU,SAAiBc,GAC7B,OAAOA,GAA0B,MAAfA,EAAQ,IAGxBa,EAAY,SAAmBjZ,EAAO2K,GAMxC,MAAO,CAAE3K,MAAOA,EAAOkZ,MALXlZ,EAAMpO,QAAU,EAAI+kB,EAAW3W,EAAM1O,MAAM8Q,QAAO,SAAU8W,EAAOd,GAG7E,OAFAc,GAlBiB,GAMD,SAAuBd,GACzC,MAAmB,KAAZA,EAYDe,CAAcf,GAAwCW,EAAUX,GAAUc,GAjB7D,EAiB8F5B,EAAQc,GAAUc,GAASE,EAAoCF,GAlB9J,EAkBYA,GAfd,EAgBPA,IACN,GACkCvO,MAAOA,IAG1CmM,EAAa,SAAoBR,GACnC,OAAOA,EAAO3W,IAAIsZ,GAAWD,MAAK,SAAUK,EAAGC,GAC7C,OAAOD,EAAEH,MAAQI,EAAEJ,MAAQ,EAAIG,EAAEH,MAAQI,EAAEJ,OAAS,EAAIG,EAAE1O,MAAQ2O,EAAE3O,UAIpEgM,EAAa,SAAoBtJ,GACnC,OAAOA,EAEN5b,QAAQ,eAAgB,IAAI2N,MAAM,MAGjC6Y,EAAW,SAAkBniB,GAC/B,IAAK,IAAI2d,EAAOvW,UAAUH,OAAQ0b,EAAQxP,MAAMwK,EAAO,EAAIA,EAAO,EAAI,GAAIC,EAAO,EAAGA,EAAOD,EAAMC,IAC/F+E,EAAM/E,EAAO,GAAKxW,UAAUwW,GAM9B,OAAO5d,IAHP2iB,EAAQA,EAAMzjB,QAAO,SAAUukB,GAC7B,OAAOA,GAAKA,EAAExc,OAAS,OAEG0b,EAAM1b,OAAS,EAAI,IAAM0b,EAAMvjB,KAAK,KAAO,KAGrEwiB,EAAgB,CAAC,MAAO,QAOxB8B,EAAiB,SAAwBC,EAAMC,GACjD,IAAIC,EAAW/d,OAAOyC,KAAKob,GAC3B,OAAOE,EAAS5c,SAAWnB,OAAOyC,KAAKqb,GAAM3c,QAAU4c,EAASvI,OAAM,SAAU/W,GAC9E,OAAOqf,EAAKviB,eAAekD,IAAQof,EAAKpf,KAASqf,EAAKrf,Q,qBCrR1DiB,EAAOpK,QAAU,CAAC,CACZ0oB,OAAQ3oB,EAAQ,QAChB+I,QAAS,CAAC,QAAU,GAAG,UAAY,uFACnC,CACA4f,OAAQ3oB,EAAQ,QAChB+I,QAAS,CAAC,QAAU,KACpB,CACA4f,OAAQ3oB,EAAQ,QAChB+I,QAAS,CAAC,QAAU,GAAG,oBAAsB,CAAC,CAAC,QAAU,uBAAuB,QAAU,CAAC,SAAW,KAAK,oBAAqB,IAAO,CAAC,QAAU,sBAAsB,QAAU,CAAC,OAAS,WAAW,CAAC,QAAU,mCAAmC,CAAC,QAAU,yBAAyB,QAAU,CAAC,SAAW,CAAC,OAAO,WAAW,IAAM,QAAQ,IAAM,aAAa,YAAY,iCAAiC,SAAS,mDAAmD,MAAM,qBAAqB,IAAM,mCAAmC,IAAM,oCAAoC,GAAK,yBAAyB,KAAO,4CAA4C,IAAM,+BAA+B,MAAQ,yCAAyC,KAAO,kCAAkC,KAAO,gCAAgC,GAAK,sBAAsB,KAAO,uBAAuB,IAAM,qBAAqB,KAAO,2CAA2C,IAAM,mCAAmC,KAAO,kCAAkC,MAAQ,wCAAwC,OAAS,0DAA0D,KAAO,mCAAmC,KAAO,4CAA4C,KAAO,6BAA6B,IAAM,kCAAkC,IAAM,kCAAkC,IAAM,uCAAuC,KAAO,mCAAmC,KAAO,yEAAyE,IAAM,oCAAoC,KAAO,oCAAoC,IAAM,4BAA4B,KAAO,yCAAyC,KAAO,qCAAqC,KAAO,6BAA6B,IAAM,8BAA8B,UAAU,iDAAiD,QAAU,qEAAqE,GAAK,iBAAiB,SAAS,4EAA4E,QAAQ,uEAAuE,UAAU,6DAA6D,UAAU,uEAAuE,UAAU,sCAAsC,SAAS,gCAAgC,QAAQ,uEAAuE,QAAQ,uDAAuD,QAAQ,0CAA0C,QAAQ,+CAA+C,QAAQ,4BAA4B,QAAQ,yDAAyD,KAAO,kCAAkC,MAAQ,+CAA+C,IAAM,iBAAiB,OAAS,iDAAiD,SAAW,2GAA2G,KAAO,kCAAkC,MAAQ,iCAAiC,MAAQ,oDAAoD,KAAO,kCAAkC,MAAQ,kCAAkC,OAAS,0CAA0C,KAAO,8BAA8B,MAAQ,2CAA2C,QAAQ,oCAAoC,KAAO,+BAA+B,OAAS,yCAAyC,OAAS,sDAAsD,MAAQ,wCAAwC,KAAO,uBAAuB,OAAS,4CAA4C,MAAQ,kCAAkC,IAAM,wBAAwB,MAAQ,iDAAiD,MAAQ,0CAA0C,OAAS,gDAAgD,KAAO,oCAAoC,MAAQ,wDAAwD,KAAO,sCAAsC,KAAO,0BAA0B,MAAQ,oCAAoC,OAAS,yCAAyC,OAAS,4CAA4C,MAAQ,mBAAmB,KAAO,6BAA6B,KAAO,8BAA8B,SAAW,sCAAsC,OAAS,wDAAwD,MAAQ,oBAAoB,MAAQ,uCAAuC,UAAU,qDAAqD,MAAQ,mCAAmC,MAAQ,wHAAwH,MAAQ,6CAA6C,OAAS,mDAAmD,aAAa,qCAAqC,cAAc,oBAAoB,cAAc,+CAA+C,eAAe,sDAAsD,cAAc,wBAAwB,aAAa,yBAAyB,cAAc,sCAAsC,cAAc,sCAAsC,cAAc,2BAA2B,cAAc,2BAA2B,cAAc,kCAAkC,cAAc,mCAAmC,eAAe,gDAAgD,cAAc,+CAA+C,eAAe,iCAAiC,cAAc,+BAA+B,aAAa,6CAA6C,cAAc,4BAA4B,cAAc,+BAA+B,cAAc,0DAA0D,cAAc,uBAAuB,cAAc,+BAA+B,cAAc,uBAAuB,cAAc,kCAAkC,cAAc,sCAAsC,cAAc,oCAAoC,cAAc,+CAA+C,cAAc,6BAA6B,YAAY,oBAAoB,YAAY,mBAAmB,aAAa,oBAAoB,aAAa,WAAW,aAAa,WAAW,aAAa,YAAY,aAAa,2BAA2B,aAAa,yBAAyB,YAAY,gBAAgB,YAAY,iBAAiB,YAAY,oBAAoB,YAAY,qBAAqB,YAAY,iBAAiB,aAAa,kCAAkC,YAAY,yBAAyB,YAAY,gBAAgB,YAAY,iBAAiB,YAAY,SAAS,QAAU,qBAAqB,UAAY,kBAAkB,OAAS,4DAA4D,MAAQ,qBAAqB,KAAO,6BAA6B,WAAW,iEAAiE,KAAO,yBAAyB,KAAO,4BAA4B,aAAa,uEAAuE,OAAS,kDAAkD,KAAO,gCAAgC,MAAQ,2CAA2C,OAAS,8DAA8D,OAAS,sDAAsD,MAAQ,sCAAsC,KAAO,2BAA2B,MAAQ,8BAA8B,MAAQ,mCAAmC,MAAQ,4CAA4C,MAAQ,uCAAuC,MAAQ,0BAA0B,MAAQ,yCAAyC,KAAO,wBAAwB,IAAM,qBAAqB,IAAM,qBAAqB,IAAM,2BAA2B,IAAM,wBAAwB,mBAAmB,8DAA8D,iBAAiB,sCAAsC,IAAM,+BAA+B,IAAM,qCAAqC,IAAM,gCAAgC,KAAO,0DAA0D,IAAM,sCAAsC,IAAM,uBAAuB,KAAO,8BAA8B,SAAS,6CAA6C,KAAO,qCAAqC,KAAO,gDAAgD,MAAQ,+CAA+C,KAAO,oCAAoC,IAAM,uBAAuB,IAAM,8BAA8B,IAAM,0BAA0B,IAAM,uCAAuC,MAAQ,0CAA0C,SAAS,yCAAyC,IAAM,qBAAqB,GAAK,+DAA+D,GAAK,2BAA2B,IAAM,2BAA2B,SAAS,sCAAsC,KAAO,2CAA2C,IAAM,mCAAmC,KAAO,wCAAwC,IAAM,+BAA+B,KAAO,+CAA+C,MAAQ,wCAAwC,IAAM,4BAA4B,KAAO,kCAAkC,KAAO,2CAA2C,KAAO,yCAAyC,IAAM,0BAA0B,KAAO,gCAAgC,GAAK,oDAAoD,IAAM,yBAAyB,KAAO,qCAAqC,IAAM,yBAAyB,KAAO,+BAA+B,cAAc,uCAAuC,GAAK,uBAAuB,OAAS,wDAAwD,OAAS,sDAAsD,KAAO,uCAAuC,IAAM,0FAA0F,OAAS,sEAAsE,KAAO,iFAAiF,IAAM,6BAA6B,IAAM,oEAAoE,KAAO,mCAAmC,KAAO,uBAAuB,GAAK,cAAc,OAAO,yCAAyC,OAAS,kDAAkD,OAAS,0CAA0C,IAAM,qDAAqD,IAAM,2BAA2B,KAAO,mCAAmC,IAAM,4CAA4C,KAAO,oCAAoC,KAAO,kCAAkC,SAAS,4CAA4C,IAAM,wBAAwB,MAAQ,oDAAoD,KAAO,2BAA2B,GAAK,gBAAgB,KAAO,6BAA6B,MAAQ,0CAA0C,MAAQ,sCAAsC,KAAO,6BAA6B,KAAO,uCAAuC,UAAU,8BAA8B,iBAAiB,oDAAoD,YAAY,6CAA6C,WAAW,mCAAmC,UAAU,6BAA6B,IAAM,mBAAmB,IAAM,0BAA0B,GAAK,gBAAgB,IAAM,yBAAyB,IAAM,gCAAgC,IAAM,6BAA6B,QAAQ,8BAA8B,IAAM,6CAA6C,MAAQ,kCAAkC,IAAM,mCAAmC,IAAM,6BAA6B,IAAM,sBAAsB,KAAO,wCAAwC,UAAU,2CAA2C,KAAO,uBAAuB,IAAM,kBAAkB,KAAO,uDAAuD,IAAM,4BAA4B,KAAO,mCAAmC,IAAM,yBAAyB,KAAO,+BAA+B,IAAM,qBAAqB,GAAK,eAAe,MAAM,kCAAkC,MAAM,+BAA+B,OAAO,sCAAsC,GAAK,sBAAsB,MAAQ,2CAA2C,MAAQ,0DAA0D,KAAO,iDAAiD,KAAO,2CAA2C,GAAK,kDAAkD,IAAM,gEAAgE,MAAQ,4EAA4E,MAAQ,yEAAyE,GAAK,sEAAsE,IAAM,sBAAsB,IAAM,sCAAsC,IAAM,kCAAkC,OAAS,+CAA+C,IAAM,2BAA2B,KAAO,mCAAmC,KAAO,kCAAkC,KAAO,sCAAsC,IAAM,+BAA+B,KAAO,kCAAkC,IAAM,gEAAgE,MAAQ,gDAAgD,KAAO,yCAAyC,MAAQ,kDAAkD,KAAO,yCAAyC,KAAO,2BAA2B,IAAM,WAAW,IAAM,gCAAgC,KAAO,0CAA0C,IAAM,mCAAmC,IAAM,4BAA4B,IAAM,yCAAyC,KAAO,2CAA2C,KAAO,iDAAiD,GAAK,kCAAkC,IAAM,+CAA+C,KAAO,4CAA4C,KAAO,8BAA8B,IAAM,6BAA6B,KAAO,sBAAsB,KAAO,wCAAwC,KAAO,oBAAoB,IAAM,yBAAyB,KAAO,sCAAsC,IAAM,uBAAuB,OAAO,8BAA8B,IAAM,iCAAiC,KAAO,qDAAqD,IAAM,yCAAyC,GAAK,2DAA2D,IAAM,0BAA0B,IAAM,kCAAkC,IAAM,gCAAgC,IAAM,yBAAyB,KAAO,kCAAkC,IAAM,wBAAwB,IAAM,6BAA6B,GAAK,wCAAwC,IAAM,6BAA6B,KAAO,gBAAgB,IAAM,qBAAqB,KAAO,gCAAgC,KAAO,4BAA4B,IAAM,0BAA0B,IAAM,gCAAgC,IAAM,8BAA8B,KAAO,+BAA+B,IAAM,4BAA4B,IAAM,oBAAoB,GAAK,4CAA4C,KAAO,iCAAiC,MAAQ,2DAA2D,KAAO,sCAAsC,KAAO,0CAA0C,IAAM,4BAA4B,IAAM,kCAAkC,KAAO,4CAA4C,IAAM,4BAA4B,KAAO,mCAAmC,KAAO,gDAAgD,KAAO,kCAAkC,MAAQ,6CAA6C,MAAQ,yCAAyC,IAAM,yBAAyB,KAAO,6BAA6B,GAAK,uDAAuD,KAAO,4BAA4B,IAAM,+BAA+B,GAAK,2GAA2G,MAAQ,+CAA+C,IAAM,sDAAsD,IAAM,6BAA6B,KAAO,wCAAwC,IAAM,gCAAgC,KAAO,sDAAsD,IAAM,0BAA0B,KAAO,kCAAkC,MAAQ,4DAA4D,MAAQ,8CAA8C,GAAK,sBAAsB,IAAM,mBAAmB,IAAM,4BAA4B,MAAQ,oBAAoB,IAAM,kCAAkC,IAAM,6BAA6B,SAAW,mEAAmE,SAAW,6BAA6B,YAAc,sDAAsD,OAAS,0BAA0B,IAAM,+BAA+B,OAAS,gDAAgD,OAAS,wBAAwB,OAAS,wBAAwB,KAAO,gCAAgC,IAAM,2BAA2B,IAAM,wBAAwB,IAAM,uCAAuC,KAAO,2CAA2C,KAAO,+CAA+C,KAAO,2BAA2B,KAAO,iCAAiC,IAAM,gCAAgC,KAAO,sBAAsB,MAAQ,qDAAqD,KAAO,wCAAwC,IAAM,iCAAiC,IAAM,2DAA2D,KAAO,0BAA0B,IAAM,+BAA+B,IAAM,oCAAoC,GAAK,iBAAiB,IAAM,sBAAsB,IAAM,wFAAwF,IAAM,sCAAsC,KAAO,iDAAiD,IAAM,2BAA2B,MAAQ,iDAAiD,MAAQ,kDAAkD,IAAM,0DAA0D,KAAO,0CAA0C,IAAM,8BAA8B,GAAK,gHAAgH,IAAM,wBAAwB,KAAO,kCAAkC,KAAO,0CAA0C,KAAO,2BAA2B,MAAQ,mCAAmC,IAAM,+BAA+B,KAAO,wCAAwC,IAAM,6DAA6D,IAAM,4BAA4B,IAAM,uBAAuB,IAAM,8BAA8B,IAAM,4BAA4B,IAAM,+BAA+B,SAAS,wCAAwC,KAAO,qCAAqC,GAAK,4CAA4C,IAAM,yDAAyD,IAAM,8BAA8B,MAAQ,+CAA+C,IAAM,sBAAsB,KAAO,wCAAwC,IAAM,mCAAmC,IAAM,yBAAyB,KAAO,yCAAyC,IAAM,+BAA+B,IAAM,+BAA+B,IAAM,sCAAsC,KAAO,+CAA+C,GAAK,yCAAyC,IAAM,6DAA6D,MAAQ,wCAAwC,KAAO,uDAAuD,IAAM,mBAAmB,IAAM,8BAA8B,GAAK,gBAAgB,MAAM,6BAA6B,QAAQ,gDAAgD,SAAS,oDAAoD,SAAS,gDAAgD,GAAK,yBAAyB,IAAM,gCAAgC,IAAM,4BAA4B,IAAM,mCAAmC,KAAO,0CAA0C,IAAM,gCAAgC,KAAO,wCAAwC,IAAM,8BAA8B,IAAM,gCAAgC,MAAQ,uDAAuD,IAAM,mCAAmC,KAAO,oCAAoC,MAAQ,4CAA4C,KAAO,uFAAuF,IAAM,6BAA6B,KAAO,wCAAwC,KAAO,qCAAqC,IAAM,iCAAiC,MAAQ,gDAAgD,IAAM,2BAA2B,IAAM,2BAA2B,MAAQ,gDAAgD,GAAK,0CAA0C,KAAO,gCAAgC,MAAQ,qDAAqD,OAAS,+DAA+D,KAAO,mCAAmC,KAAO,6CAA6C,KAAO,qCAAqC,MAAQ,yCAAyC,IAAM,kCAAkC,IAAM,wBAAwB,SAAS,0DAA0D,IAAM,+DAA+D,QAAQ,8CAA8C,KAAO,oCAAoC,MAAQ,sDAAsD,IAAM,qCAAqC,UAAY,8BAA8B,SAAS,uBAAuB,IAAM,0BAA0B,MAAQ,8CAA8C,MAAQ,oDAAoD,KAAO,kCAAkC,KAAO,oCAAoC,MAAQ,sDAAsD,IAAM,8BAA8B,OAAS,oEAAoE,IAAM,wBAAwB,IAAM,6BAA6B,KAAO,qCAAqC,KAAO,kEAAkE,QAAU,gGAAgG,IAAM,iCAAiC,IAAM,2BAA2B,IAAM,yBAAyB,GAAK,cAAc,KAAO,oCAAoC,MAAQ,6CAA6C,KAAO,oCAAoC,IAAM,iCAAiC,WAAW,2DAA2D,IAAM,mEAAmE,MAAQ,uDAAuD,KAAO,0CAA0C,IAAM,oCAAoC,IAAM,wBAAwB,OAAS,sCAAsC,KAAO,kCAAkC,KAAO,oCAAoC,MAAQ,4CAA4C,OAAS,wDAAwD,OAAS,8DAA8D,KAAO,+BAA+B,IAAM,gDAAgD,IAAM,yBAAyB,QAAQ,8CAA8C,YAAY,iHAAiH,GAAK,uBAAuB,KAAO,iDAAiD,KAAO,2CAA2C,KAAO,wCAAwC,IAAM,4BAA4B,KAAO,iCAAiC,KAAO,4CAA4C,SAAS,oDAAoD,GAAK,oBAAoB,OAAS,qGAAqG,IAAM,0BAA0B,KAAO,uCAAuC,IAAM,6BAA6B,QAAQ,qDAAqD,IAAM,iCAAiC,KAAO,yCAAyC,IAAM,0BAA0B,IAAM,wBAAwB,QAAQ,gDAAgD,IAAM,yBAAyB,IAAM,4BAA4B,KAAO,sCAAsC,IAAM,qDAAqD,KAAO,yBAAyB,UAAU,4CAA4C,GAAK,qBAAqB,OAAO,oCAAoC,IAAM,uBAAuB,KAAO,uCAAuC,IAAM,4BAA4B,IAAM,qBAAqB,KAAO,oCAAoC,MAAM,gCAAgC,aAAa,qGAAqG,GAAK,wCAAwC,GAAK,4FAA4F,IAAM,yBAAyB,IAAM,4BAA4B,IAAM,6BAA6B,IAAM,uBAAuB,KAAO,sCAAsC,GAAK,qBAAqB,KAAO,uCAAuC,IAAM,4EAA4E,KAAO,kCAAkC,IAAM,gCAAgC,KAAO,qCAAqC,IAAM,6BAA6B,IAAM,2BAA2B,KAAO,sCAAsC,MAAQ,kDAAkD,IAAM,2BAA2B,IAAM,uBAAuB,MAAQ,oDAAoD,KAAO,mCAAmC,IAAM,8BAA8B,IAAM,gCAAgC,IAAM,mCAAmC,IAAM,gCAAgC,UAAU,6DAA6D,IAAM,4CAA4C,IAAM,+BAA+B,IAAM,wBAAwB,MAAQ,oBAAoB,IAAM,gCAAgC,MAAQ,sCAAsC,GAAK,0DAA0D,IAAM,+BAA+B,IAAM,8BAA8B,GAAK,wBAAwB,OAAS,iEAAiE,IAAM,4BAA4B,KAAO,8DAA8D,IAAM,wBAAwB,KAAO,2EAA2E,IAAM,yBAAyB,IAAM,kCAAkC,IAAM,qEAAqE,KAAO,+CAA+C,MAAQ,uDAAuD,OAAS,mEAAmE,UAAU,iEAAiE,IAAM,gCAAgC,IAAM,8FAA8F,IAAM,0DAA0D,MAAQ,mDAAmD,IAAM,8BAA8B,IAAM,8BAA8B,GAAK,oBAAoB,IAAM,sBAAsB,GAAK,kBAAkB,IAAM,0BAA0B,SAAS,6CAA6C,KAAO,iCAAiC,GAAK,qBAAqB,MAAQ,wDAAwD,KAAO,8CAA8C,KAAO,kCAAkC,cAAc,iEAAiE,YAAY,wCAAwC,IAAM,oCAAoC,IAAM,8DAA8D,QAAQ,oDAAoD,QAAQ,kCAAkC,IAAM,iCAAiC,KAAO,kCAAkC,IAAM,qBAAqB,IAAM,iCAAiC,IAAM,gCAAgC,IAAM,+BAA+B,IAAM,2BAA2B,GAAK,oBAAoB,QAAQ,sCAAsC,IAAM,sCAAsC,IAAM,2BAA2B,KAAO,kCAAkC,IAAM,+BAA+B,IAAM,2BAA2B,IAAM,kCAAkC,IAAM,yBAAyB,IAAM,mBAAmB,MAAQ,oDAAoD,IAAM,0BAA0B,GAAK,eAAe,KAAO,4CAA4C,IAAM,iCAAiC,OAAS,mDAAmD,MAAQ,sDAAsD,GAAK,qEAAqE,IAAM,wBAAwB,MAAQ,kDAAkD,IAAM,wBAAwB,IAAM,qDAAqD,IAAM,kCAAkC,KAAO,yCAAyC,IAAM,yBAAyB,cAAc,uBAAuB,IAAM,4BAA4B,IAAM,yBAAyB,IAAM,yBAAyB,IAAM,8BAA8B,KAAO,6BAA6B,IAAM,0BAA0B,MAAQ,kDAAkD,IAAM,oBAAoB,QAAQ,4CAA4C,IAAM,2BAA2B,KAAO,wBAAwB,IAAM,gBAAgB,KAAO,6BAA6B,IAAM,gCAAgC,UAAU,kDAAkD,KAAO,wBAAwB,IAAM,kDAAkD,KAAO,gCAAgC,IAAM,8BAA8B,IAAM,2BAA2B,IAAM,uBAAuB,SAAS,0CAA0C,MAAQ,uCAAuC,KAAO,uCAAuC,IAAM,+BAA+B,IAAM,gCAAgC,IAAM,+BAA+B,IAAM,uBAAuB,IAAM,0BAA0B,GAAK,cAAc,KAAO,+BAA+B,MAAM,uCAAuC,IAAM,mCAAmC,IAAM,2BAA2B,IAAM,2BAA2B,KAAO,mCAAmC,IAAM,mBAAmB,KAAO,uCAAuC,IAAM,0BAA0B,UAAU,2CAA2C,IAAM,8BAA8B,IAAM,2CAA2C,IAAM,6BAA6B,IAAM,iCAAiC,IAAM,mCAAmC,IAAM,0BAA0B,IAAM,gCAAgC,UAAU,mDAAmD,MAAQ,4CAA4C,IAAM,0BAA0B,KAAO,kCAAkC,IAAM,gCAAgC,KAAO,iCAAiC,GAAK,kBAAkB,SAAS,2CAA2C,KAAO,uCAAuC,KAAO,iCAAiC,KAAO,2BAA2B,IAAM,+BAA+B,IAAM,2BAA2B,IAAM,wCAAwC,KAAO,oCAAoC,IAAM,4BAA4B,eAAe,uDAAuD,WAAW,6CAA6C,WAAW,8BAA8B,UAAU,iDAAiD,IAAM,4BAA4B,GAAK,mBAAmB,IAAM,qCAAqC,KAAO,uCAAuC,QAAQ,wDAAwD,WAAW,oEAAoE,IAAM,sBAAsB,IAAM,yBAAyB,MAAQ,2CAA2C,KAAO,oDAAoD,QAAU,iEAAiE,IAAM,2CAA2C,IAAM,8BAA8B,KAAO,+BAA+B,KAAO,wCAAwC,IAAM,2BAA2B,KAAO,sCAAsC,KAAO,4DAA4D,KAAO,oDAAoD,KAAO,oDAAoD,IAAM,4BAA4B,KAAO,uBAAuB,QAAQ,+CAA+C,IAAM,wCAAwC,GAAK,2BAA2B,IAAM,qCAAqC,IAAM,wBAAwB,GAAK,eAAe,IAAM,4BAA4B,IAAM,qBAAqB,IAAM,yBAAyB,IAAM,wBAAwB,MAAQ,gCAAgC,IAAM,qBAAqB,GAAK,sDAAsD,IAAM,sCAAsC,IAAM,yBAAyB,KAAO,gCAAgC,IAAM,8BAA8B,KAAO,qCAAqC,KAAO,mCAAmC,KAAO,qDAAqD,KAAO,4CAA4C,IAAM,qBAAqB,GAAK,uBAAuB,IAAM,wBAAwB,KAAO,sCAAsC,KAAO,+BAA+B,MAAQ,8CAA8C,MAAQ,0CAA0C,IAAM,6BAA6B,IAAM,+BAA+B,GAAK,yBAAyB,MAAQ,2CAA2C,KAAO,qCAAqC,KAAO,iDAAiD,IAAM,8DAA8D,KAAO,0CAA0C,IAAM,4BAA4B,KAAO,4CAA4C,IAAM,6BAA6B,IAAM,0BAA0B,IAAM,2BAA2B,IAAM,0BAA0B,GAAK,iBAAiB,QAAQ,0CAA0C,IAAM,8BAA8B,IAAM,uBAAuB,KAAO,oCAAoC,IAAM,8BAA8B,IAAM,8BAA8B,KAAO,uCAAuC,IAAM,oCAAoC,KAAO,0CAA0C,IAAM,mCAAmC,KAAO,uBAAuB,IAAM,sCAAsC,KAAO,6BAA6B,IAAM,mCAAmC,KAAO,iCAAiC,GAAK,qBAAqB,KAAO,mCAAmC,IAAM,4DAA4D,KAAO,oCAAoC,GAAK,wBAAwB,IAAM,uCAAuC,IAAM,4BAA4B,KAAO,qCAAqC,KAAO,gDAAgD,IAAM,yBAAyB,IAAM,6BAA6B,IAAM,8BAA8B,KAAO,8BAA8B,IAAM,YAAY,IAAM,6BAA6B,GAAK,yBAAyB,IAAM,iCAAiC,IAAM,2BAA2B,QAAQ,0CAA0C,GAAK,wFAAwF,IAAM,iCAAiC,KAAO,sCAAsC,IAAM,2BAA2B,KAAO,wCAAwC,IAAM,oBAAoB,IAAM,+DAA+D,KAAO,kDAAkD,IAAM,0BAA0B,GAAK,WAAW,KAAO,uCAAuC,IAAM,0DAA0D,KAAO,2BAA2B,KAAO,0CAA0C,KAAO,mCAAmC,SAAS,qDAAqD,SAAS,mDAAmD,GAAK,qBAAqB,IAAM,0CAA0C,MAAQ,oDAAoD,IAAM,uCAAuC,KAAO,wCAAwC,IAAM,2BAA2B,MAAQ,qDAAqD,IAAM,2EAA2E,KAAO,sCAAsC,KAAO,qCAAqC,UAAU,8BAA8B,GAAK,+CAA+C,OAAO,iCAAiC,SAAS,kDAAkD,IAAM,yBAAyB,KAAO,2CAA2C,IAAM,0BAA0B,IAAM,sBAAsB,KAAO,wCAAwC,IAAM,wBAAwB,IAAM,uBAAuB,IAAM,uBAAuB,KAAO,6BAA6B,IAAM,wBAAwB,GAAK,sBAAsB,KAAO,+BAA+B,KAAO,uCAAuC,MAAM,6BAA6B,UAAU,oDAAoD,eAAe,sDAAsD,MAAQ,4BAA4B,KAAO,8BAA8B,KAAO,+BAA+B,KAAO,uCAAuC,MAAQ,wCAAwC,KAAO,6BAA6B,MAAQ,gDAAgD,MAAQ,6CAA6C,IAAM,wBAAwB,OAAS,kGAAkG,MAAQ,wDAAwD,IAAM,2BAA2B,KAAO,kCAAkC,KAAO,qCAAqC,IAAM,8BAA8B,MAAQ,wDAAwD,OAAS,8CAA8C,MAAQ,gFAAgF,IAAM,wBAAwB,KAAO,4CAA4C,KAAO,+BAA+B,MAAQ,2CAA2C,KAAO,oCAAoC,QAAU,kEAAkE,IAAM,sBAAsB,KAAO,mCAAmC,KAAO,kCAAkC,IAAM,2BAA2B,KAAO,uCAAuC,IAAM,4BAA4B,KAAO,kCAAkC,IAAM,8BAA8B,OAAS,gDAAgD,OAAS,wDAAwD,KAAO,sCAAsC,IAAM,2BAA2B,KAAO,gCAAgC,KAAO,+BAA+B,IAAM,yBAAyB,MAAQ,4CAA4C,IAAM,4BAA4B,IAAM,uDAAuD,IAAM,uBAAuB,IAAM,0BAA0B,MAAQ,iDAAiD,MAAQ,2BAA2B,KAAO,4BAA4B,GAAK,oBAAoB,MAAQ,8CAA8C,IAAM,6BAA6B,IAAM,2BAA2B,IAAM,0BAA0B,IAAM,sCAAsC,KAAO,+BAA+B,MAAQ,wDAAwD,IAAM,4BAA4B,KAAO,uCAAuC,MAAQ,kDAAkD,GAAK,cAAc,IAAM,6BAA6B,UAAU,wCAAwC,UAAU,gDAAgD,UAAU,+CAA+C,IAAM,4BAA4B,IAAM,+BAA+B,KAAO,sEAAsE,IAAM,uBAAuB,KAAO,0DAA0D,KAAO,yBAAyB,MAAQ,gCAAgC,KAAO,kCAAkC,IAAM,wBAAwB,IAAM,wDAAwD,MAAQ,wCAAwC,eAAe,iEAAiE,OAAO,4BAA4B,KAAO,mCAAmC,IAAM,uBAAuB,KAAO,8BAA8B,WAAW,sDAAsD,KAAO,gCAAgC,OAAS,4EAA4E,MAAQ,oCAAoC,MAAQ,qDAAqD,IAAM,qBAAqB,IAAM,wBAAwB,IAAM,0BAA0B,QAAQ,wCAAwC,GAAK,gBAAgB,IAAM,4BAA4B,IAAM,uBAAuB,GAAK,kBAAkB,GAAK,uBAAuB,IAAM,sBAAsB,SAAS,YAAY,GAAK,0BAA0B,IAAM,yBAAyB,IAAM,kBAAkB,KAAO,2BAA2B,KAAO,+BAA+B,KAAO,6BAA6B,KAAO,6BAA6B,IAAM,6BAA6B,KAAO,8BAA8B,GAAK,gDAAgD,IAAM,qBAAqB,KAAO,uCAAuC,IAAM,uBAAuB,IAAM,kBAAkB,IAAM,yBAAyB,IAAM,4BAA4B,QAAQ,gCAAgC,IAAM,+BAA+B,MAAQ,8CAA8C,GAAK,kBAAkB,IAAM,mCAAmC,KAAO,+BAA+B,IAAM,qBAAqB,IAAM,mBAAmB,IAAM,iCAAiC,KAAO,2BAA2B,IAAM,gBAAgB,GAAK,iBAAiB,KAAO,kCAAkC,KAAO,8BAA8B,KAAO,sBAAsB,IAAM,0BAA0B,IAAM,wBAAwB,IAAM,4BAA4B,IAAM,wBAAwB,IAAM,qDAAqD,IAAM,kBAAkB,KAAO,+BAA+B,IAAM,oBAAoB,IAAM,kCAAkC,MAAM,0BAA0B,SAAS,8CAA8C,KAAO,yBAAyB,OAAS,qCAAqC,IAAM,6BAA6B,KAAO,0BAA0B,KAAO,mCAAmC,UAAU,mDAAmD,MAAQ,uDAAuD,KAAO,qCAAqC,OAAS,gBAAgB,SAAS,sCAAsC,OAAS,kCAAkC,SAAW,qCAAqC,OAAS,2CAA2C,IAAM,6BAA6B,IAAM,WAAW,MAAQ,mCAAmC,KAAO,4BAA4B,GAAK,kBAAkB,IAAM,6BAA6B,OAAS,wDAAwD,IAAM,0BAA0B,GAAK,oBAAoB,IAAM,yDAAyD,KAAO,oCAAoC,IAAM,kEAAkE,IAAM,oBAAoB,IAAM,wBAAwB,IAAM,iBAAiB,QAAQ,iDAAiD,OAAS,uCAAuC,OAAS,iDAAiD,KAAO,mCAAmC,IAAM,qBAAqB,IAAM,2BAA2B,KAAO,oCAAoC,IAAM,+BAA+B,MAAQ,+CAA+C,IAAM,gDAAgD,IAAM,wBAAwB,IAAM,wBAAwB,KAAO,mCAAmC,gBAAgB,wCAAwC,KAAO,8BAA8B,IAAM,yBAAyB,IAAM,YAAY,UAAU,kCAAkC,WAAW,oBAAoB,UAAU,uCAAuC,UAAU,oBAAoB,IAAM,gEAAgE,KAAO,8CAA8C,MAAQ,4CAA4C,IAAM,8BAA8B,IAAM,kCAAkC,IAAM,0BAA0B,IAAM,0BAA0B,MAAQ,2DAA2D,IAAM,2BAA2B,KAAO,4BAA4B,IAAM,yBAAyB,KAAO,sCAAsC,KAAO,sCAAsC,IAAM,4DAA4D,KAAO,gCAAgC,QAAQ,+CAA+C,IAAM,8BAA8B,GAAK,kBAAkB,IAAM,yBAAyB,IAAM,2BAA2B,MAAQ,yCAAyC,IAAM,qDAAqD,KAAO,yCAAyC,IAAM,qCAAqC,IAAM,6BAA6B,KAAO,6CAA6C,IAAM,gCAAgC,KAAO,+DAA+D,IAAM,iCAAiC,IAAM,0BAA0B,KAAO,uCAAuC,KAAO,oCAAoC,MAAQ,qCAAqC,GAAK,YAAY,IAAM,6BAA6B,MAAQ,sDAAsD,IAAM,iBAAiB,KAAO,uCAAuC,OAAS,gDAAgD,KAAO,sBAAsB,IAAM,8BAA8B,KAAO,+BAA+B,GAAK,oBAAoB,KAAO,sCAAsC,MAAQ,6CAA6C,KAAO,qCAAqC,cAAc,2CAA2C,IAAM,mCAAmC,UAAU,8DAA8D,IAAM,2CAA2C,KAAO,yCAAyC,UAAU,qDAAqD,KAAO,qCAAqC,IAAM,0BAA0B,IAAM,yBAAyB,IAAM,4BAA4B,KAAO,oCAAoC,IAAM,yBAAyB,MAAQ,0BAA0B,IAAM,yBAAyB,IAAM,mDAAmD,IAAM,wBAAwB,IAAM,0CAA0C,IAAM,wBAAwB,KAAO,oCAAoC,KAAO,oCAAoC,MAAQ,+CAA+C,IAAM,uCAAuC,IAAM,kCAAkC,IAAM,gCAAgC,QAAU,8CAA8C,OAAS,wDAAwD,KAAO,iDAAiD,KAAO,kCAAkC,IAAM,uBAAuB,GAAK,qBAAqB,IAAM,sBAAsB,IAAM,6BAA6B,MAAQ,oCAAoC,KAAO,2CAA2C,IAAM,yBAAyB,KAAO,sDAAsD,SAAS,sCAAsC,IAAM,4BAA4B,IAAM,iCAAiC,IAAM,2BAA2B,IAAM,wBAAwB,IAAM,wBAAwB,KAAO,qCAAqC,IAAM,oFAAoF,KAAO,iCAAiC,IAAM,0BAA0B,KAAO,mCAAmC,MAAM,4BAA4B,MAAM,wBAAwB,GAAK,qDAAqD,IAAM,wCAAwC,IAAM,iBAAiB,KAAO,yBAAyB,IAAM,8BAA8B,WAAW,4EAA4E,MAAQ,gCAAgC,GAAK,yBAAyB,IAAM,oCAAoC,IAAM,8BAA8B,KAAO,8CAA8C,IAAM,oCAAoC,IAAM,4EAA4E,IAAM,iDAAiD,GAAK,uDAAuD,IAAM,kCAAkC,IAAM,4CAA4C,IAAM,6BAA6B,IAAM,8BAA8B,KAAO,sCAAsC,GAAK,qBAAqB,IAAM,kCAAkC,IAAM,kBAAkB,IAAM,0DAA0D,IAAM,wBAAwB,KAAO,+BAA+B,MAAQ,kBAAkB,MAAQ,mBAAmB,IAAM,mCAAmC,MAAQ,sBAAsB,QAAU,oBAAoB,SAAW,wCAAwC,IAAM,oCAAoC,IAAM,8BAA8B,GAAK,0BAA0B,IAAM,qCAAqC,KAAO,gDAAgD,QAAQ,qDAAqD,GAAK,mBAAmB,OAAO,kCAAkC,IAAM,0DAA0D,KAAO,sBAAsB,IAAM,uBAAuB,IAAM,8CAA8C,IAAM,8BAA8B,IAAM,sCAAsC,KAAO,qCAAqC,IAAM,gCAAgC,KAAO,oCAAoC,IAAM,uBAAuB,GAAK,sBAAsB,IAAM,iCAAiC,IAAM,iCAAiC,KAAO,2CAA2C,GAAK,kCAAkC,KAAO,4BAA4B,MAAM,oCAAoC,IAAM,kCAAkC,GAAK,gHAAgH,IAAM,2BAA2B,IAAM,2BAA2B,IAAM,4CAA4C,IAAM,qEAAqE,IAAM,8BAA8B,QAAQ,4CAA4C,KAAO,gCAAgC,GAAK,qBAAqB,IAAM,+DAA+D,KAAO,yCAAyC,IAAM,8BAA8B,IAAM,wBAAwB,GAAK,iBAAiB,IAAM,wBAAwB,IAAM,gCAAgC,GAAK,mBAAmB,KAAO,2BAA2B,IAAM,8DAA8D,IAAM,4BAA4B,GAAK,kBAAkB,IAAM,0BAA0B,IAAM,qCAAqC,KAAO,oCAAoC,MAAQ,uEAAuE,GAAK,gBAAgB,IAAM,wCAAwC,IAAM,0BAA0B,IAAM,sDAAsD,QAAQ,mDAAmD,IAAM,4BAA4B,IAAM,gCAAgC,IAAM,sCAAsC,IAAM,6BAA6B,KAAO,4DAA4D,IAAM,kCAAkC,GAAK,aAAa,IAAM,gCAAgC,KAAO,sCAAsC,IAAM,6BAA6B,GAAK,kBAAkB,SAAS,8CAA8C,IAAM,+BAA+B,IAAM,mCAAmC,IAAM,4BAA4B,KAAO,6CAA6C,IAAM,+BAA+B,IAAM,6BAA6B,IAAM,4BAA4B,KAAO,oCAAoC,IAAM,yBAAyB,KAAO,+CAA+C,GAAK,oCAAoC,QAAQ,8BAA8B,IAAM,mBAAmB,IAAM,2BAA2B,IAAM,+BAA+B,KAAO,uBAAuB,KAAO,iCAAiC,IAAM,oBAAoB,IAAM,0BAA0B,IAAM,8BAA8B,KAAO,kDAAkD,SAAS,mBAAmB,OAAS,oBAAoB,IAAM,wDAAwD,KAAO,oCAAoC,IAAM,0BAA0B,IAAM,gCAAgC,IAAM,8BAA8B,IAAM,2BAA2B,IAAM,8BAA8B,SAAS,yCAAyC,MAAQ,2CAA2C,IAAM,6BAA6B,KAAO,uCAAuC,IAAM,0BAA0B,KAAO,kCAAkC,IAAM,2BAA2B,IAAM,2BAA2B,MAAQ,4BAA4B,IAAM,yBAAyB,KAAO,yCAAyC,IAAM,iEAAiE,IAAM,4BAA4B,KAAO,kCAAkC,GAAK,oBAAoB,IAAM,0BAA0B,IAAM,6BAA6B,IAAM,6BAA6B,IAAM,qBAAqB,QAAQ,gDAAgD,IAAM,4BAA4B,IAAM,sBAAsB,IAAM,wBAAwB,KAAO,yCAAyC,OAAO,oCAAoC,MAAM,2BAA2B,MAAM,kCAAkC,MAAM,mBAAmB,IAAM,2DAA2D,MAAQ,8BAA8B,IAAM,gCAAgC,MAAQ,gCAAgC,IAAM,iDAAiD,QAAQ,uDAAuD,OAAS,6EAA6E,KAAO,iEAAiE,OAAS,8DAA8D,GAAK,sBAAsB,IAAM,kCAAkC,IAAM,mCAAmC,IAAM,wBAAwB,IAAM,iCAAiC,GAAK,kBAAkB,KAAO,sCAAsC,IAAM,gEAAgE,QAAQ,6CAA6C,MAAQ,qDAAqD,IAAM,+BAA+B,GAAK,kBAAkB,KAAO,iCAAiC,IAAM,uBAAuB,IAAM,2BAA2B,IAAM,8CAA8C,MAAQ,gGAAgG,KAAO,uCAAuC,IAAM,2BAA2B,GAAK,sCAAsC,OAAO,gDAAgD,KAAO,iDAAiD,IAAM,mCAAmC,IAAM,4BAA4B,IAAM,sDAAsD,IAAM,2BAA2B,IAAM,4BAA4B,KAAO,oCAAoC,kBAAkB,6CAA6C,GAAK,iBAAiB,IAAM,4BAA4B,IAAM,sBAAsB,IAAM,yBAAyB,GAAK,0BAA0B,IAAM,wBAAwB,IAAM,+BAA+B,KAAO,8BAA8B,IAAM,0IAA0I,QAAQ,oCAAoC,IAAM,oBAAoB,MAAM,yBAAyB,KAAO,sEAAsE,GAAK,uEAAuE,MAAQ,8CAA8C,IAAM,gCAAgC,IAAM,6BAA6B,SAAS,qDAAqD,UAAU,yDAAyD,aAAa,uEAAuE,SAAS,8DAA8D,UAAU,2EAA2E,SAAS,mCAAmC,UAAU,uCAAuC,SAAS,kFAAkF,SAAS,qCAAqC,SAAS,6DAA6D,SAAS,mCAAmC,SAAS,iGAAiG,IAAM,4BAA4B,KAAO,qCAAqC,IAAM,oCAAoC,IAAM,oFAAoF,MAAQ,wCAAwC,IAAM,gHAAgH,MAAQ,6BAA6B,OAAS,2BAA2B,MAAQ,8CAA8C,GAAK,iBAAiB,KAAO,qCAAqC,MAAQ,8BAA8B,YAAY,wCAAwC,KAAO,2BAA2B,WAAW,2CAA2C,IAAM,+BAA+B,IAAM,gCAAgC,IAAM,sCAAsC,IAAM,uBAAuB,IAAM,8BAA8B,IAAM,wBAAwB,KAAO,+BAA+B,MAAQ,iCAAiC,GAAK,2BAA2B,IAAM,sBAAsB,IAAM,uCAAuC,IAAM,+BAA+B,IAAM,uBAAuB,GAAK,qDAAqD,SAAS,0CAA0C,KAAO,oCAAoC,KAAO,uCAAuC,MAAQ,6BAA6B,OAAS,uBAAuB,IAAM,iCAAiC,MAAQ,wDAAwD,IAAM,qDAAqD,KAAO,wCAAwC,IAAM,2BAA2B,OAAS,gEAAgE,GAAK,mCAAmC,IAAM,iBAAiB,IAAM,2BAA2B,KAAO,wCAAwC,OAAS,uBAAuB,IAAM,wBAAwB,IAAM,6BAA6B,MAAQ,mCAAmC,QAAU,0BAA0B,OAAS,uBAAuB,IAAM,8BAA8B,WAAW,qEAAqE,IAAM,8DAA8D,KAAO,0CAA0C,QAAU,0CAA0C,MAAQ,4EAA4E,OAAS,qBAAqB,IAAM,2BAA2B,UAAU,iDAAiD,KAAO,iCAAiC,KAAO,uBAAuB,GAAK,wDAAwD,MAAQ,6FAA6F,IAAM,mCAAmC,KAAO,6CAA6C,IAAM,wBAAwB,IAAM,4BAA4B,IAAM,yBAAyB,UAAU,2DAA2D,IAAM,4BAA4B,MAAQ,6BAA6B,IAAM,4BAA4B,IAAM,sBAAsB,IAAM,0BAA0B,OAAO,8BAA8B,IAAM,mBAAmB,KAAO,8BAA8B,MAAQ,sCAAsC,KAAO,0BAA0B,IAAM,wCAAwC,KAAO,uEAAuE,IAAM,+CAA+C,GAAK,uCAAuC,IAAM,0BAA0B,IAAM,0BAA0B,IAAM,+BAA+B,IAAM,8BAA8B,IAAM,yBAAyB,KAAO,kCAAkC,IAAM,wBAAwB,KAAO,2BAA2B,IAAM,wBAAwB,IAAM,4BAA4B,IAAM,2BAA2B,IAAM,sBAAsB,IAAM,4CAA4C,IAAM,yDAAyD,IAAM,yBAAyB,IAAM,6BAA6B,KAAO,2CAA2C,MAAQ,uDAAuD,IAAM,4BAA4B,KAAO,qCAAqC,IAAM,+BAA+B,KAAO,mCAAmC,IAAM,6BAA6B,IAAM,yBAAyB,KAAO,yCAAyC,KAAO,6BAA6B,IAAM,kDAAkD,IAAM,sBAAsB,KAAO,iCAAiC,IAAM,qDAAqD,KAAO,kCAAkC,QAAU,uCAAuC,KAAO,0CAA0C,KAAO,sBAAsB,KAAO,mCAAmC,KAAO,0CAA0C,OAAS,uCAAuC,IAAM,6CAA6C,IAAM,iBAAiB,IAAM,mBAAmB,KAAO,qCAAqC,IAAM,oBAAoB,GAAK,cAAc,KAAO,2DAA2D,KAAO,qBAAqB,IAAM,6BAA6B,IAAM,qBAAqB,OAAS,kBAAkB,UAAU,2CAA2C,MAAM,sBAAsB,GAAK,iCAAiC,IAAM,oCAAoC,KAAO,oBAAoB,KAAO,6BAA6B,SAAS,2CAA2C,KAAO,qCAAqC,IAAM,mBAAmB,SAAS,8CAA8C,KAAO,uCAAuC,MAAQ,wCAAwC,IAAM,0BAA0B,KAAO,kCAAkC,GAAK,uFAAuF,OAAO,qCAAqC,IAAM,sBAAsB,IAAM,yBAAyB,IAAM,0BAA0B,IAAM,kCAAkC,KAAO,0BAA0B,IAAM,iBAAiB,GAAK,sCAAsC,IAAM,2BAA2B,KAAO,kCAAkC,QAAU,0DAA0D,IAAM,gCAAgC,IAAM,+BAA+B,IAAM,0BAA0B,KAAO,2CAA2C,KAAO,+BAA+B,IAAM,uBAAuB,IAAM,yBAAyB,KAAO,oCAAoC,IAAM,oBAAoB,MAAQ,oDAAoD,IAAM,wBAAwB,GAAK,gDAAgD,KAAO,wCAAwC,KAAO,wCAAwC,MAAQ,4CAA4C,KAAO,kCAAkC,KAAO,iDAAiD,KAAO,gDAAgD,IAAM,uBAAuB,MAAQ,wCAAwC,MAAQ,mCAAmC,GAAK,mCAAmC,IAAM,6BAA6B,KAAO,mCAAmC,IAAM,yEAAyE,KAAO,sCAAsC,KAAO,oCAAoC,KAAO,yBAAyB,IAAM,2DAA2D,IAAM,6BAA6B,IAAM,mBAAmB,IAAM,yBAAyB,KAAO,0BAA0B,GAAK,mBAAmB,IAAM,kCAAkC,OAAS,0CAA0C,IAAM,yBAAyB,IAAM,kCAAkC,IAAM,6BAA6B,IAAM,sDAAsD,KAAO,kCAAkC,IAAM,qBAAqB,IAAM,wBAAwB,GAAK,8BAA8B,IAAM,6BAA6B,IAAM,wEAAwE,SAAS,wCAAwC,KAAO,sCAAsC,KAAO,wCAAwC,KAAO,+BAA+B,KAAO,qCAAqC,IAAM,oEAAoE,GAAK,iBAAiB,GAAK,YAAY,IAAM,qBAAqB,IAAM,0BAA0B,IAAM,0BAA0B,GAAK,uBAAuB,IAAM,gCAAgC,IAAM,8BAA8B,IAAM,uBAAuB,IAAM,+BAA+B,IAAM,+BAA+B,IAAM,yBAAyB,KAAO,yCAAyC,KAAO,4BAA4B,IAAM,4BAA4B,IAAM,0BAA0B,IAAM,0BAA0B,KAAO,2BAA2B,GAAK,mBAAmB,IAAM,6BAA6B,IAAM,2BAA2B,IAAM,wBAAwB,KAAO,0BAA0B,OAAS,yCAAyC,IAAM,uBAAuB,IAAM,qBAAqB,IAAM,4BAA4B,OAAS,mCAAmC,KAAO,6BAA6B,KAAO,4BAA4B,QAAU,kCAAkC,IAAM,6BAA6B,KAAO,+BAA+B,MAAM,8BAA8B,MAAQ,6CAA6C,MAAQ,qDAAqD,KAAO,iCAAiC,GAAK,oBAAoB,KAAO,oCAAoC,IAAM,6BAA6B,IAAM,sBAAsB,MAAQ,mCAAmC,IAAM,6BAA6B,IAAM,mCAAmC,IAAM,0BAA0B,IAAM,mCAAmC,KAAO,oCAAoC,IAAM,uBAAuB,IAAM,2BAA2B,MAAQ,0CAA0C,IAAM,uBAAuB,OAAO,6CAA6C,IAAM,yBAAyB,KAAO,qBAAqB,IAAM,0BAA0B,IAAM,uBAAuB,KAAO,wCAA6C,IAAM,sBAAsB,IAAM,2BAA2B,IAAM,8BAA8B,KAAO,uCAAuC,WAAW,qEAAqE,KAAO,mCAAmC,KAAO,mCAAmC,YAAY,yDAAyD,QAAQ,wCAAwC,IAAM,uDAAuD,KAAO,gCAAgC,KAAO,kCAAkC,KAAO,4BAA4B,KAAO,iCAAiC,GAAK,UAAU,IAAM,qBAAqB,IAAM,mBAAmB,WAAa,CAAC,OAAO,OAAO,eAAiB,GAAG,WAAY,EAAM,cAAgB,GAAG,cAAgB,GAAG,WAAa,CAAC,gBAAgB,mBAAmB,KAAO,iEACnkuE,CACA4f,OAAQ3oB,EAAQ,QAChB+I,QAAS,CAAC,QAAU,GAAG,WAAa,KAAK,MAAO,EAAK,WAAY,IACjE,CACA4f,OAAQ3oB,EAAQ,QAChB+I,QAAS,CAAC,QAAU,O,qBCd1BsB,EAAOpK,QAAU,IAA0B,oD,kCCgD5B,IAhDI,CACjB2oB,wBAAyB,EACzBC,kBAAmB,EACnBC,iBAAkB,EAClBC,iBAAkB,EAClBC,QAAS,EACTC,aAAc,EACdC,gBAAiB,EACjBC,YAAa,EACbC,QAAS,EACTC,KAAM,EACNC,SAAU,EACVC,aAAc,EACdC,WAAY,EACZC,aAAc,EACdC,UAAW,EACXC,QAAS,EACTC,WAAY,EACZC,YAAa,EACbC,aAAc,EACdC,WAAY,EACZC,cAAe,EACfC,eAAgB,EAChBC,gBAAiB,EACjBC,UAAW,EACXC,cAAe,EACfC,aAAc,EACdC,iBAAkB,EAClB1a,WAAY,EACZ2a,WAAY,EACZ9a,QAAS,EACT+a,MAAO,EACPC,QAAS,EACTC,QAAS,EACTC,OAAQ,EACRC,OAAQ,EACRC,KAAM,EACNC,gBAAiB,EAEjBC,YAAa,EACbC,aAAc,EACdC,YAAa,EACbC,gBAAiB,EACjBC,iBAAkB,EAClBC,iBAAkB,EAClBC,cAAe,EACfC,YAAa,I,qBCzCqBjhB,EAAOpK,QAI5B,WACb,IAAIsrB,GAAO,GACsC,IAA7CC,UAAUC,WAAW5Z,QAAQ,aAC/B0Z,GAAO,GAGT,IACEzQ,EADE4Q,EAAM,GAERC,EAA0B,iBAAbnT,UAAyBA,SACtCoT,EAAOL,EACHI,EAAIE,gBAAgBC,SAAS,QAC7BH,EAAIE,gBAAgBC,SAExB9M,EACE2M,IAAQC,EAAO,aAAe,iBAAiB/O,KAAK8O,EAAII,YAY5D,OAVK/M,GAAU2M,GACbA,EAAI1Q,iBALe,mBAOhBH,EAAW,WAGV,IAFA6Q,EAAIzQ,oBARW,mBAQ2BJ,GAC1CkE,EAAS,EACDlE,EAAW4Q,EAAIM,SAAUlR,MAIhC,SAAS/F,GACdiK,EAASmC,WAAWpM,EAAI,GAAK2W,EAAIjrB,KAAKsU,IA/BWkX,I,oECiDtC,MAnDf,SAAiBC,GAYf,IANA,IAEIta,EAFAua,EAAI,EAGJ3e,EAAI,EACJyE,EAAMia,EAAIpgB,OAEPmG,GAAO,IAAKzE,EAAGyE,GAAO,EAE3BL,EAEe,YAAV,OAHLA,EAAwB,IAApBsa,EAAIpP,WAAWtP,IAAmC,IAAtB0e,EAAIpP,aAAatP,KAAc,GAA2B,IAAtB0e,EAAIpP,aAAatP,KAAc,IAA4B,IAAtB0e,EAAIpP,aAAatP,KAAc,MAG9F,OAAZoE,IAAM,KAAgB,IAIpDua,EAEe,YAAV,OALLva,GAEAA,IAAM,MAGoC,OAAZA,IAAM,KAAgB,IAErC,YAAV,MAAJua,IAAyC,OAAZA,IAAM,KAAgB,IAItD,OAAQla,GACN,KAAK,EACHka,IAA8B,IAAxBD,EAAIpP,WAAWtP,EAAI,KAAc,GAEzC,KAAK,EACH2e,IAA8B,IAAxBD,EAAIpP,WAAWtP,EAAI,KAAc,EAEzC,KAAK,EAEH2e,EAEe,YAAV,OAHLA,GAAyB,IAApBD,EAAIpP,WAAWtP,MAGsB,OAAZ2e,IAAM,KAAgB,IASxD,SAHAA,EAEe,YAAV,OAHLA,GAAKA,IAAM,MAG+B,OAAZA,IAAM,KAAgB,KACvCA,IAAM,MAAQ,GAAGrO,SAAS,K,wBC9CrCsO,EAAiB,aACjBC,EAAiB,8BAEjBC,EAAmB,SAA0BC,GAC/C,OAAkC,KAA3BA,EAASzP,WAAW,IAGzB0P,EAAqB,SAA4BjjB,GACnD,OAAgB,MAATA,GAAkC,kBAAVA,GAG7BkjB,EAAmB,aAAQ,SAAUC,GACvC,OAAOJ,EAAiBI,GAAaA,EAAYA,EAAUlsB,QAAQ4rB,EAAgB,OAAOO,iBAGxF,EAAoB,SAA2BvjB,EAAKG,GACtD,OAAQH,GACN,IAAK,YACL,IAAK,gBAED,GAAqB,iBAAVG,EACT,OAAOA,EAAM/I,QAAQ6rB,GAAgB,SAAU/G,EAAOsH,EAAIC,GAMxD,OALAC,EAAS,CACPjhB,KAAM+gB,EACNrd,OAAQsd,EACRE,KAAMD,GAEDF,KAMjB,OAAsB,IAAlB,IAASxjB,IAAekjB,EAAiBljB,IAAyB,iBAAVG,GAAgC,IAAVA,EAI3EA,EAHEA,EAAQ,MAoCnB,SAASyjB,EAAoBC,EAAaC,EAAYC,EAAeC,GACnE,GAAqB,MAAjBD,EACF,MAAO,GAGT,QAAuCzf,IAAnCyf,EAAcE,iBAKhB,OAAOF,EAGT,cAAeA,GACb,IAAK,UAED,MAAO,GAGX,IAAK,SAED,GAA2B,IAAvBA,EAAcG,KAMhB,OALAR,EAAS,CACPjhB,KAAMshB,EAActhB,KACpB0D,OAAQ4d,EAAc5d,OACtBwd,KAAMD,GAEDK,EAActhB,KAGvB,QAA6B6B,IAAzByf,EAAc5d,OAAsB,CACtC,IAAIwd,EAAOI,EAAcJ,KAEzB,QAAarf,IAATqf,EAGF,UAAgBrf,IAATqf,GACLD,EAAS,CACPjhB,KAAMkhB,EAAKlhB,KACX0D,OAAQwd,EAAKxd,OACbwd,KAAMD,GAERC,EAAOA,EAAKA,KAUhB,OANaI,EAAc5d,OAAS,IAStC,OAiDR,SAAgC0d,EAAaC,EAAY5iB,GACvD,IAAI7H,EAAS,GAEb,GAAIuV,MAAM+I,QAAQzW,GAChB,IAAK,IAAIkD,EAAI,EAAGA,EAAIlD,EAAIwB,OAAQ0B,IAC9B/K,GAAUuqB,EAAoBC,EAAaC,EAAY5iB,EAAIkD,IAAI,QAGjE,IAAK,IAAIiV,KAAQnY,EAAK,CACpB,IAAIf,EAAQe,EAAImY,GAEhB,GAAqB,iBAAVlZ,EACS,MAAd2jB,QAA4Cxf,IAAtBwf,EAAW3jB,GACnC9G,GAAUggB,EAAO,IAAMyK,EAAW3jB,GAAS,IAClCijB,EAAmBjjB,KAC5B9G,GAAUgqB,EAAiBhK,GAAQ,IAAM,EAAkBA,EAAMlZ,GAAS,UAO5E,IAAIyO,MAAM+I,QAAQxX,IAA8B,iBAAbA,EAAM,IAAkC,MAAd2jB,QAA+Cxf,IAAzBwf,EAAW3jB,EAAM,IAM7F,CACL,IAAIgkB,EAAeP,EAAoBC,EAAaC,EAAY3jB,GAAO,GAEvE,OAAQkZ,GACN,IAAK,YACL,IAAK,gBAEDhgB,GAAUgqB,EAAiBhK,GAAQ,IAAM8K,EAAe,IACxD,MAGJ,QAMI9qB,GAAUggB,EAAO,IAAM8K,EAAe,UAtB5C,IAAK,IAAIC,EAAK,EAAGA,EAAKjkB,EAAMuC,OAAQ0hB,IAC9BhB,EAAmBjjB,EAAMikB,MAC3B/qB,GAAUgqB,EAAiBhK,GAAQ,IAAM,EAAkBA,EAAMlZ,EAAMikB,IAAO,KA4B1F,OAAO/qB,EAtGMgrB,CAAuBR,EAAaC,EAAYC,GAG3D,IAAK,WAED,QAAoBzf,IAAhBuf,EAA2B,CAC7B,IAAIS,EAAiBZ,EACjBvN,EAAS4N,EAAcF,GAE3B,OADAH,EAASY,EACFV,EAAoBC,EAAaC,EAAY3N,EAAQ6N,GAK9D,MAGJ,IAAK,UAkBP,GAAkB,MAAdF,EACF,OAAOC,EAGT,IAAIQ,EAAST,EAAWC,GAOxB,YAAkBzf,IAAXigB,GAAyBP,EAAwCD,EAATQ,EA2DjE,IASIb,EATAc,EAAe,6BAWnB,IAAI,EAAkB,SAAyB5b,EAAMkb,EAAYD,GAC/D,GAAoB,IAAhBjb,EAAKlG,QAAmC,iBAAZkG,EAAK,IAA+B,OAAZA,EAAK,SAAkCtE,IAAnBsE,EAAK,GAAGzC,OAClF,OAAOyC,EAAK,GAGd,IAAI6b,GAAa,EACbte,EAAS,GACbud,OAASpf,EACT,IAAIogB,EAAU9b,EAAK,GAEJ,MAAX8b,QAAmCpgB,IAAhBogB,EAAQC,KAC7BF,GAAa,EACbte,GAAUyd,EAAoBC,EAAaC,EAAYY,GAAS,IAMhEve,GAAUue,EAAQ,GAIpB,IAAK,IAAItgB,EAAI,EAAGA,EAAIwE,EAAKlG,OAAQ0B,IAC/B+B,GAAUyd,EAAoBC,EAAaC,EAAYlb,EAAKxE,GAA6C,KAAzC+B,EAAOuN,WAAWvN,EAAOzD,OAAS,IAE9F+hB,IAKFte,GAAUue,EAAQtgB,IActBogB,EAAaI,UAAY,EAIzB,IAHA,IACI1I,EADA2I,EAAiB,GAG0B,QAAvC3I,EAAQsI,EAAapH,KAAKjX,KAChC0e,GAAkB,IAClB3I,EAAM,GAkBR,MAAO,CACLzZ,KAhBS,EAAW0D,GAAU0e,EAiB9B1e,OAAQA,EACRwd,KAAMD,K,kCC7TV,uBAGE,WAAA1oB,OAAOjB,SAAS+W,UAChB,cAAA9V,OAAOjB,SAASiX,SAEhBzR,QAAQsW,MAAR,gFAGS,kBAAmBuM,WAC5BA,UAAU0C,cACPC,SADH,UAEGjP,MAAK,SAAUkP,GACdA,EAAInT,iBAAJ,eAAoC,WAClC6J,oBAAU,6BAA8B,CAAEoJ,cAAeE,IAGzD,IAAMC,EAAmBD,EAAIE,WAC7B3lB,QAAQ4lB,IAAR,mBAAgCF,GAChCA,EAAiBpT,iBAAjB,eAAiD,WAC/C,OAAQoT,EAAiB/pB,OACvB,IAAI,YACEknB,UAAU0C,cAAcM,YAK1BpqB,OAAOqqB,cAAe,EAEtB3J,oBAAU,6BAA8B,CAAEoJ,cAAeE,IAGrDhqB,OAAOsqB,qBACT/lB,QAAQ4lB,IAAR,4CACAnqB,OAAOjB,SAASygB,YAKlBjb,QAAQ4lB,IAAR,qCAKAzJ,oBAAU,2BAA4B,CAAEoJ,cAAeE,KAEzD,MAEF,IAAI,YACFzlB,QAAQsW,MAAR,mDACA6F,oBAAU,2BAA4B,CAAEoJ,cAAeE,IACvD,MAEF,IAAI,YACFtJ,oBAAU,wBAAyB,CAAEoJ,cAAeE,cAM7DjP,OAAM,SAAU7X,GACfqB,QAAQsW,MAAR,4CAA2D3X,O,qBC1DjErH,EAAQ+W,WAAa,CACnB,+BAAgC,kBAAM,kCACtC,oCAAqC,kBAAM,+C,mBCG7C3M,EAAOpK,QARP,SAAgCoe,GAC9B,QAAa,IAATA,EACF,MAAM,IAAIC,eAAe,6DAG3B,OAAOD,GAIThU,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,kCCPxEmK,EAAOpK,QAAU,SAAU0uB,GACzB,GAAmB,iBAARA,EACT,MAAM,IAAIlR,UAAU,6BAA6BpQ,cAAcshB,EAAK,MAItE,OAAI,eAAe9R,KAAK8R,IAMjB,4BAA4B9R,KAAK8R,K,qBCd1C,IAAIC,EAAoB,EAAQ,QAE5BC,EAAkB,EAAQ,QAE1BzJ,EAA6B,EAAQ,QAErC0J,EAAoB,EAAQ,QAMhCzkB,EAAOpK,QAJP,SAA4BilB,GAC1B,OAAO0J,EAAkB1J,IAAQ2J,EAAgB3J,IAAQE,EAA2BF,IAAQ4J,KAI9FzkB,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,qPC2EzD,EAvFH,CACVkP,MAAO,CACLE,MAAO,UACPD,gBAAiB,WAEnBE,OAAQ,CAAC,CACPC,MAAO,CAAC,UACRtL,MAAO,CACLoL,MAAO,mBAER,CACDE,MAAO,CAAC,WACRtL,MAAO,CACLoL,MAAO,sBAER,CACDE,MAAO,CAAC,UAAW,UAAW,WAC9BtL,MAAO,CACLoL,MAAO,sBAER,CACDE,MAAO,CAAC,SAAU,YAClBtL,MAAO,CACLoL,MAAO,uBAER,CACDE,MAAO,CAAC,YACRtL,MAAO,CACLoL,MAAO,uBAER,CACDE,MAAO,CAAC,YAAa,YACrBtL,MAAO,CACLoL,MAAO,uBAER,CACDE,MAAO,CAAC,UAAW,SAAU,cAC7BtL,MAAO,CACLoL,MAAO,uBAER,CACDE,MAAO,CAAC,YACRtL,MAAO,CACLoL,MAAO,uBAER,CAEDE,MAAO,CAAC,OACRtL,MAAO,CACLoL,MAAO,sBAER,CAEDE,MAAO,CAAC,OACR8B,UAAW,CAAC,UACZpN,MAAO,CACLoL,MAAO,sBAER,CACDE,MAAO,CAAC,cAAe,YACvBtL,MAAO,CACLoL,MAAO,uBAER,CAEDE,MAAO,CAAC,eACR8B,UAAW,CAAC,UACZpN,MAAO,CACLoL,MAAO,YAER,CACDE,MAAO,CAAC,YACRtL,MAAO,CACLoL,MAAO,uBAER,CACDE,MAAO,CAAC,cACRtL,MAAO,CACLoL,MAAO,sBAER,CACDE,MAAO,CAAC,QACRtL,MAAO,CACLoL,MAAO,yB,iCC9EEyf,EAJS,SAAC,GAAiB,oBACxC,OAAO,yBCkBT,IAAM1O,EAAoBqB,IAAS,CACjC7C,OAAQ,kBAAM,+DACdE,QAASgQ,IAqFIC,EAjFG,SAAC,GAAyC,IAA7BC,EAA4B,EAAtCvc,SACnB,OADyD,4BAC/C,cACD,YAAC2N,EAAD,CAAmBzN,KAAMqc,IAG9B,YAAC,IAAD,eAAe5jB,IAAf,CAA6BuH,KAAMqc,EAAaje,SAAS,aAAalB,MAAOof,KAC1E,gBAAGprB,EAAH,EAAGA,UAAWI,EAAd,EAAcA,MAAO6O,EAArB,EAAqBA,OAAQkB,EAA7B,EAA6BA,aAAcC,EAA3C,EAA2CA,cAA3C,OACC,mBAAKpQ,UAAWA,EAAY,OAAQI,MAAOA,EAAOirB,EAAG,GA3B/D,SAAqBpc,GACnB,IAAMqc,EAAerc,EAAOjH,OAE5B,GAAqB,IAAjBsjB,EACF,OAAOrc,EAET,IAAMsc,EAAYtc,EAAOqc,EAAe,GAExC,OAAyB,IAArBC,EAAUvjB,QAAgBujB,EAAU,GAAG1e,MAClCoC,EAAOhR,MAAM,EAAGqtB,EAAe,GAEjCrc,EAiBIuc,CAAYvc,GAAQrE,KAAI,SAAC+B,EAAMjD,GAC9B,IAAI+hB,EAAY,GAEZC,GAAS,EAET/e,EAAK,IAAMA,EAAK,GAAGC,QAAQ5E,QAAiC,MAAvB2E,EAAK,GAAGC,QAAQ,IACvD6e,EAAY,CAAElgB,gBAAiB,0BAC/BmgB,GAAS,GACA/e,EAAK,IAAMA,EAAK,GAAGC,QAAQ5E,QAAiC,MAAvB2E,EAAK,GAAGC,QAAQ,IAC9D6e,EAAY,CAAElgB,gBAAiB,0BAC/BmgB,GAAS,GACA/e,EAAK,IAA0B,KAApBA,EAAK,GAAGC,SAAkBD,EAAK,IAA0B,MAApBA,EAAK,GAAGC,SACjE6e,EAAY,CAAElgB,gBAAiB,0BAC/BmgB,GAAS,GACA/e,EAAK,IAA0B,KAApBA,EAAK,GAAGC,SAAkBD,EAAK,IAA0B,MAApBA,EAAK,GAAGC,UACjE6e,EAAY,CAAElgB,gBAAiB,0BAC/BmgB,GAAS,GAEX,IAAMC,EAAYxb,EAAa,CAAExD,OAAMrH,IAAKoE,IAE5CiiB,EAAUvrB,MAAQqrB,EAClB,IAMIG,EANEC,EAAY,CAChBC,WAAY,OACZC,cAAe,YACfC,iBAAkB,QAKpB,OACE,iCAASL,EAAT,CAAoBrmB,IAAKqH,EAAOjD,IAC7BiD,EAAK/B,KAAI,SAAC+D,EAAOrJ,GAChB,GAAIomB,IAES,IAARpmB,GAAqB,IAARA,IACe,MAA5BqJ,EAAM/B,QAAQ/C,OAAO,IAA0C,MAA5B8E,EAAM/B,QAAQ/C,OAAO,IACzD,CACA,GAAI8E,EAAM/B,QAAQ5E,OAAS,EAAG,CAC5B4jB,EAAa,CACXlgB,MAAO,CAAC,kBAAmB,UAC3BkB,QAAS+B,EAAM/B,QAAQ3O,MAAM,IAE/B,IAAMguB,EAAY,CAChBvgB,MAAO,CAAC,YACRkB,QAAS+B,EAAM/B,QAAQ/C,OAAO,IAGhC,OACE,YAAC,WAAD,CAAgBvE,IAAKqJ,EAAQrJ,GAC3B,kCACM8K,EAAc,CAAEzB,MAAOsd,EAAW3mB,QADxC,CAEElF,MAAOyrB,KAET,mBAAUzb,EAAc,CAAEzB,MAAOid,EAAYtmB,UAIjD,OAAO,kCAAU8K,EAAc,CAAEzB,QAAOrJ,QAAjC,CAAyClF,MAAOyrB,KAI7D,OAAO,mBAAUzb,EAAc,CAAEzB,QAAOrJ,qBClF7C4mB,EAZG,SAAC,GAAkC,IAAtBC,EAAqB,EAA/Bvd,SAAmB3P,EAAY,4BAClD,OAAIktB,EAEA,iBAAG/nB,KAAMnF,EAAMmF,KAAM5B,OAAO,SAAS4pB,IAAI,uBACtCD,GAIE,MCJLE,EAAY,YAAO,MAAP,qBAAH,4BAEC,SAAAptB,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOC,mBAF7B,KAKA,GACbC,GAAI,SAAAvtB,GAAK,OACP,8BAAIe,UAAU,WAAWysB,GAAIxtB,EAAM2P,SAASlS,QAAQ,OAAQ,IAAImsB,eAAmB5pB,KAErFosB,EAAG,SAAApsB,GAAK,OAAI,6BAAGe,UAAU,aAAgBf,KACzCytB,IAAK,SAAAztB,GAAK,OACR,YAACotB,EAAD,KACE,kBAASptB,KAGb6P,KAAMoc,EACN5G,EAAG4H,G,qDCfL,SAASla,EAAQnT,EAAQoT,GACvB,IAAI3I,EAAOzC,OAAOyC,KAAKzK,GAEvB,GAAIgI,OAAOiC,sBAAuB,CAChC,IAAIoJ,EAAUrL,OAAOiC,sBAAsBjK,GACvCoT,IAAgBC,EAAUA,EAAQjS,QAAO,SAAUkS,GACrD,OAAOtL,OAAOE,yBAAyBlI,EAAQsT,GAAKjG,eAEtD5C,EAAK3M,KAAK6P,MAAMlD,EAAM4I,GAGxB,OAAO5I,EAuBT,IAAIqjB,EAAW,SAAkBC,EAAY5gB,GAC3C,MAAqB,mBAAVA,EACSA,EAAM4gB,GAtB5B,SAAuBpqB,GACrB,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CACzC,IAAI6C,EAAyB,MAAhBpE,UAAUuB,GAAavB,UAAUuB,GAAK,GAE/CA,EAAI,EACNsI,EAAQzF,GAAQ,GAAMjK,SAAQ,SAAUgD,GACtC,IAAgB9C,EAAQ8C,EAAKiH,EAAOjH,OAE7BuB,OAAOwL,0BAChBxL,OAAOyL,iBAAiB9P,EAAQqE,OAAOwL,0BAA0B9F,IAEjEyF,EAAQzF,GAAQjK,SAAQ,SAAUgD,GAChCuB,OAAOC,eAAetE,EAAQ8C,EAAKuB,OAAOE,yBAAyBwF,EAAQjH,OAKjF,OAAO9C,EAkBAqqB,CAAc,GAAID,EAAY,GAAI5gB,IAGvC8gB,EAAuB,aAAY,SAAUF,GAC/C,OAAO,aAAY,SAAU5gB,GAC3B,OAAO2gB,EAASC,EAAY5gB,SAI5B,EAAgB,SAAuB/M,GACzC,OAAO,wBAAc,IAAa8tB,SAAU,MAAM,SAAU/gB,GAK1D,OAJI/M,EAAM+M,QAAUA,IAClBA,EAAQ8gB,EAAqB9gB,EAArB8gB,CAA4B7tB,EAAM+M,QAGrC,wBAAc,IAAaqH,SAAU,CAC1C5N,MAAOuG,GACN/M,EAAM2P,c,ykBCzEb,IAAMoe,EAAY,CAChBC,MAAO,CACLC,KAAM,+CAIJC,EAAU,OACXH,GADW,IAEdV,OAAQ,CACNc,WAAY,OACZC,QAAS,OACTC,KAAM,UACNf,iBAAkB,qBAClBJ,KAAM,aAIJoB,EAAS,OACVP,GADU,IAEbV,OAAQ,CACNc,WAAY,UACZC,QAAS,OACTC,KAAM,OACNf,iBAAkB,OAClBJ,KAAM,a,qBCXK5oB,EATF,SAAC,GAAD,IAAGtC,EAAH,EAAGA,GAAOhC,EAAV,6BACXuuB,IAAcvsB,GACZ,6BAAGmD,KAAMnD,GAAQhC,GACdA,EAAM2P,UAGT,YAAC,OAAD,aAAY3N,GAAIA,GAAQhC,K,+DCJtBwuB,EAAe,YAAO,MAAP,qBAAH,khBA+CUC,IA/CV,4RA4DUC,IA5DV,wIA2ELC,EAAiB,SAAC,GAAD,IAAGC,EAAH,EAAGA,kBAAmBC,EAAtB,EAAsBA,kBAAtB,OAC5B,YAACL,EAAD,KACE,qBAAOhB,GAAG,SAASzsB,UAAU,UAC3B,qBACE6H,KAAK,WACL4kB,GAAG,SACHsB,SAAUD,EACVE,SAASH,IAEX,oBAAM7tB,UAAU,oBClFPiuB,EANG,kBAChB,mBAAKC,MAAM,6BAA6BC,MAAM,KAAKC,OAAO,KAAKC,QAAQ,aACrE,oBAAMC,EAAE,0ECIGC,EANG,kBAChB,mBAAKL,MAAM,6BAA6BC,MAAM,KAAKC,OAAO,KAAKC,QAAQ,aACrE,oBAAMC,EAAE,4ECkDGE,EAhDE,SAAXA,EAAY,GAA6E,IASzFnvB,EATwF,IAA1EW,iBAA0E,MAA9D,GAA8D,EAA1DyuB,EAA0D,EAA1DA,aAAcC,EAA4C,EAA5CA,UAAW7D,EAAiC,EAAjCA,IAAK8D,EAA4B,EAA5BA,MAAOC,EAAqB,EAArBA,MACjEC,GADsF,8EACxEH,EAAU7D,IAMxBiE,EAA+B,IAAjBF,EAAM5mB,OAIH,oBAAZ0M,WACTrV,EAAWqV,SAASrV,UAEtB,IAGM0vB,EAAyB/uB,EAAN,UAFvBX,IAAaA,EAAS0B,WAAa8pB,GAAOxrB,EAAS0B,WAAaiuB,IAAOC,OAAOC,WAAarE,GAEnC,SAAW,IAErE,OACE,kBAAI7qB,UAAW+uB,GACZJ,GACC,YAAC,EAAD,CAAM1tB,GAAI4pB,GACP8D,GACCK,IAAOG,QAAQC,WAAaT,GAASG,EACrC,sBAAQ5rB,QAtBD,WACfurB,EAAa5D,IAqBsBwE,aAAW,WAAWrvB,UAAU,aACvD6uB,EAA8B,YAAC,EAAD,MAAhB,YAAC,EAAD,OAEhB,OAINA,GAAeC,EACf,sBACGF,EAAMhkB,KAAI,SAAC0kB,EAAM1Z,GAAP,OACT,YAAC4Y,EAAD,aACElpB,IAAKgqB,EAAKzE,IAAMjV,EAAMoE,WACtByU,aAAcA,EACdC,UAAWA,GACPY,QAIR,O,g5CC7CV,IAkJeC,GAjCF,SAAC,GAAe,IAAbC,EAAY,EAAZA,MACTC,EAAYC,oBAAS,WACxB,OAnHsB,SAAAF,GACxB,IAUMG,GAVeX,IAAOG,QAAQS,YAChCJ,EAAMvvB,QACJ,kBAIe,MAJf,EACEif,KACE2Q,OAAUC,QAIhBN,GAEsBniB,QACxB,SACE0iB,EADF,GAeE,IARI,IAQJ,EARG,IAJD7Q,KACE2Q,OAAUC,EAGX,EAHWA,KAAMnB,EAGjB,EAHiBA,MAIdqB,EAAQF,EAAKzlB,MAAM,KAEZ4lB,EAAcF,EAArBnB,MAHH,iBAQQsB,EARR,QASGC,EAAMF,GAAaA,EAAUG,MAAK,qBAAGC,OAAqBH,KAE1DC,EACGA,EAAIvB,QACPuB,EAAIvB,MAAQ,KAGduB,EAAM,CAAEE,MAAOH,EAAMtB,MAAO,IAC5BqB,EAAUtzB,KAAKwzB,IAEjBF,EAAYE,EAAIvB,OAXlB,KAFEI,IAAOC,QAAUD,IAAOC,OAAOqB,cAAgBN,EAAM/xB,MAAM,GAAI,GAAK+xB,EAAM/xB,MAAM,GAAI,MAEtF,aAAiC,IAajC,IAAMsyB,EACJvB,IAAOC,QAAUD,IAAOC,OAAOqB,cAAgBN,EAAMhoB,OAAS,EAAIgoB,EAAMhoB,OAAS,EAE7EwoB,EAAeP,EAAUG,MAAK,qBAAGC,QAAsBL,EAAMO,MAanE,OAXIC,GACFA,EAAa3F,IAAMiF,EACnBU,EAAa7B,MAAQA,GAErBsB,EAAUtzB,KAAK,CACb0zB,MAAOL,EAAMO,GACb1F,IAAKiF,EACLlB,MAAO,GACPD,UAGGoB,IAET,CAAEnB,MAAO,KA1DsB,EA+D7BI,IADFG,QAAWsB,sBA9DoB,MA8DH,GA9DG,EAiE3BN,EAAG,YAAOM,GAKhB,OAHIzB,IAAOC,QAAUD,IAAOC,OAAOqB,cAEnCH,EAAIO,UACGP,EAAI9iB,QAAO,SAAC0iB,EAAMD,GAQvB,IAPA,IAOA,EAPME,EAAQF,EAAKzlB,MAAM,KAEZ4lB,EAAcF,EAArBnB,MAH0B,iBAQrBsB,EARqB,QAS1BC,EAAMF,EAAUG,MAAK,SAAAd,GAAI,OAAIA,GAAQA,EAAKe,OAASH,KAEnDC,EACGA,EAAIvB,QACPuB,EAAIvB,MAAQ,KAGduB,EAAM,CAAEE,MAAOH,EAAMtB,MAAO,IAC5BqB,EAAUtzB,KAAKwzB,IAEbA,GAAOA,EAAIvB,QACbqB,EAAYE,EAAIvB,QAZpB,KAFEI,IAAOC,QAAUD,IAAOC,OAAOqB,cAAgBN,EAAM/xB,MAAM,GAAI,GAAK+xB,EAAM/xB,MAAM,GAAI,MAEtF,aAAiC,IAgBjCgyB,EAAUrlB,KAAI,SAAA0kB,GACZA,EAAKV,MAAQU,EAAKV,MAAM3K,MAAK,SAASK,EAAGC,GACvC,OAAID,EAAE+L,MAAQ9L,EAAE8L,OAAe,EAC3B/L,EAAE+L,MAAQ9L,EAAE8L,MAAc,EACvB,QAGX,IAAME,EACJvB,IAAOC,QAAUD,IAAOC,OAAOqB,cAAgBN,EAAMhoB,OAAS,EAAIgoB,EAAMhoB,OAAS,EAE7E4N,EAAQqa,EAAUU,WAAU,qBAAGN,QAAsBL,EAAMO,MAKjE,OAHIN,EAAUjoB,QACZ+nB,EAAKnB,MAAMgC,QAAQX,EAAUze,OAAOoE,EAAO,GAAG,IAEzCma,IACNJ,GAKMkB,CAAkBrB,MAFD,GAKpBsB,EAAmB,GAEzBrB,EAASb,MAAMtsB,SAAQ,SAAAgtB,GACjBN,IAAOG,QAAQ4B,cAAgB/B,IAAOG,QAAQ4B,aAAatjB,SAAS6hB,EAAKzE,KAC3EiG,EAAiBxB,EAAKzE,MAAO,EAE7BiG,EAAiBxB,EAAKzE,MAAO,KAXP,MAcQ6E,mBAASoB,GAApCpC,EAdmB,KAcRD,EAdQ,KAuB1B,OACE,YAAC,EAAD,aACEzuB,WAAcgvB,IAAOG,QAAQC,UAAY,gBAAkB,iBAAlD,cACTX,aAVW,SAAA5D,GAAQ,IAAD,EACpB4D,EAAa,SACRC,GADO,WAET7D,IAAO6D,EAAU7D,GAFR,MAUV6D,UAAWA,GACPe,KCjJV,SAASpjB,KAeP,OAdAA,GAAWxF,OAAOyF,QAAU,SAAU9J,GACpC,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CACzC,IAAI6C,EAASpE,UAAUuB,GAEvB,IAAK,IAAIpE,KAAOiH,EACV1F,OAAOjG,UAAUwB,eAAe1C,KAAK6M,EAAQjH,KAC/C9C,EAAO8C,GAAOiH,EAAOjH,IAK3B,OAAO9C,IAGOgK,MAAM7M,KAAMwI,WAG9B,SAASoK,GAAyBhG,EAAQiG,GACxC,GAAc,MAAVjG,EAAgB,MAAO,GAE3B,IAEIjH,EAAKoE,EAFLlH,EAkBN,SAAuC+J,EAAQiG,GAC7C,GAAc,MAAVjG,EAAgB,MAAO,GAC3B,IAEIjH,EAAKoE,EAFLlH,EAAS,GACTiQ,EAAa5L,OAAOyC,KAAKiD,GAG7B,IAAK7C,EAAI,EAAGA,EAAI+I,EAAWzK,OAAQ0B,IACjCpE,EAAMmN,EAAW/I,GACb8I,EAASzE,QAAQzI,IAAQ,IAC7B9C,EAAO8C,GAAOiH,EAAOjH,IAGvB,OAAO9C,EA9BMkQ,CAA8BnG,EAAQiG,GAInD,GAAI3L,OAAOiC,sBAAuB,CAChC,IAAI6J,EAAmB9L,OAAOiC,sBAAsByD,GAEpD,IAAK7C,EAAI,EAAGA,EAAIiJ,EAAiB3K,OAAQ0B,IACvCpE,EAAMqN,EAAiBjJ,GACnB8I,EAASzE,QAAQzI,IAAQ,GACxBuB,OAAOjG,UAAUgS,qBAAqBlT,KAAK6M,EAAQjH,KACxD9C,EAAO8C,GAAOiH,EAAOjH,IAIzB,OAAO9C,EAmBT,IAAIwuB,GAAe,sBAAW,SAAUrzB,EAAMqE,GAC5C,IAAIivB,EAAatzB,EAAK6N,MAClBA,OAAuB,IAAfylB,EAAwB,eAAiBA,EACjDC,EAAYvzB,EAAKwzB,KACjBA,OAAqB,IAAdD,EAAuB,GAAKA,EACnC7tB,EAAOkP,GAAyB5U,EAAM,CAAC,QAAS,SAEpD,OAAoB,IAAMuB,cAAc,MAAOmN,GAAS,CACtDrK,IAAKA,EACLksB,MAAO,6BACPC,MAAOgD,EACP/C,OAAQ+C,EACR9C,QAAS,YACT+C,KAAM,OACNC,OAAQ7lB,EACRgc,YAAa,IACb8J,cAAe,QACfC,eAAgB,SACfluB,GAAoB,IAAMnE,cAAc,OAAQ,CACjDovB,EAAG,6DACY,IAAMpvB,cAAc,WAAY,CAC/CsyB,OAAQ,mBACO,IAAMtyB,cAAc,OAAQ,CAC3CuyB,GAAI,KACJC,GAAI,KACJC,GAAI,KACJC,GAAI,UAGRZ,GAAaxpB,YAAc,eACZ,UC7Ef,IAAMqqB,GAAW,aAAO,YAA6C,IAA1C7xB,EAAyC,EAAzCA,UAA6Bf,GAAY,EAA9B6yB,OAA8B,EAAtBC,MAAsB,+CAClE,OACE,kBAAI/xB,UAAWA,GACb,6BAAGoE,KAAMnF,EAAMgC,IAAQhC,EAAvB,CAA8BuD,OAAO,SAAS4pB,IAAI,wBAC/CntB,EAAM2P,aAJE,sBAAH,qEAcK,mBAA0B,IAA1B,EAAGmjB,MAA2B,IAAM,MAdzC,+BAemB,SAAA9yB,GAAK,OAAI,EAAyB,GAApBA,EAAM8yB,OAAS,KAfhD,0EAuBR,SAAA9yB,GAAK,OACLA,EAAM6yB,QAAN,yMAxBQ,0CAuCRE,GAAU,YAAO,QAAP,sBAAH,wbA6BPC,GAAU,aAAO,SAAAhzB,GAAK,OAC1B,iBAAQA,EACN,0BAFY,sBAAH,6HA6DEizB,GA7CO,SAAC,GAAD,EAAG7yB,SAAH,OACpB,YAAC,cAAD,CACEqkB,MAAK,aAcL9gB,OAAQ,YAAiB,IAAduvB,EAAa,EAAbA,OACT,OACE,YAACH,GAAD,KACGhD,IAAOG,QAAQR,MACd,mBACE3uB,UAAW,4BACXoyB,wBAAyB,CAAEC,OAAQrD,IAAOG,QAAQR,SAElD,KACJ,kBAAI3uB,UAAW,aACb,YAAC,GAAD,CAAMwvB,MAAO2C,EAAO3C,QACnBR,IAAOG,QAAQmD,OAAStD,IAAOG,QAAQmD,MAAMtqB,OAAS,GAAK,YAACiqB,GAAD,MAC3DjD,IAAOG,QAAQmD,MAAM1nB,KAAI,SAACuhB,EAAM7mB,GAC/B,GAAkB,KAAd6mB,EAAKA,MAA6B,KAAdA,EAAKmB,KAC3B,OACE,YAACuE,GAAD,CAAUvsB,IAAKA,EAAKrE,GAAIkrB,EAAKA,MAC1BA,EAAKmB,KACN,YAAC,GAAD,CAAc6D,KAAM,eCnHlCoB,GAAOr2B,EAAQ,QAEfs2B,MAAkBxD,IAAOyD,OAAOxc,SAAU+Y,IAAOyD,OAAOxc,OAAOyc,SAEjEC,GAAgB,GAEhBH,IAAmBxD,IAAOyD,OAAOxc,OAAO2c,WAC1CD,GAAch2B,KAAK,CACjBoL,KAAK,GAAIinB,IAAOyD,OAAOxc,OAAO2c,UAC9BjE,MAAM,UACNkE,QAAQ,YAMZ,IAAMtW,GAAoBqB,IAAS,CACjC7C,OAAQ,kBAAM,wDACdE,QAASgQ,IAGX,SAAS6H,KACP,IAAIC,EAAIre,SAASyK,eAAe,UAEZ,WAAhB4T,EAAE/yB,UACJ+yB,EAAE/yB,WAAa,cAEf+yB,EAAE/yB,UAAY,SAIlB,IAAMgzB,GAAc,YAAO,MAAP,sBAAH,2HAMD,SAAA/zB,GAAK,OAAKA,EAAM4uB,kBAAoB,eAAYjkB,IAN/C,6CA0KFqpB,GA7JA,SAAC,GAAD,IAAG5zB,EAAH,EAAGA,SAAUwuB,EAAb,EAAaA,kBAAmBC,EAAhC,EAAgCA,kBAAhC,OACb,YAAC,cAAD,CACEpK,MAAK,aAmBL9gB,OAAQ,SAAAswB,GACN,IAAMC,EAAUj3B,EAAQ,QAElBk3B,EAAUl3B,EAAQ,QAHV,GAKaA,EAAQ,QAERA,EAAQ,QAM/Bg3B,EAHFG,KACEC,cAAgBC,EAXN,EAWMA,YAAaC,EAXnB,EAWmBA,QAASC,EAX5B,EAW4BA,UAAWC,EAXvC,EAWuCA,KAAMC,EAX7C,EAW6CA,YAIrDC,EAA8B,KAAdF,EAAKvH,KAAcuH,EAAKvH,KAAO,6BAErD,OACE,mBAAKnsB,UAAW,iBACd,mBAAKA,UAAW,iBACd,mBAAKA,UAAW,gBAChB,YAAC,EAAD,CAAMiB,GAAI2yB,EAAe5zB,UAAW,eAChC,mBACEA,UAAW,+BACX6zB,IAAoB,KAAfH,EAAKI,MAAeJ,EAAKI,MAAQX,EACtCY,IAAK,UAGT,mBACE/zB,UAAW,4BACXoyB,wBAAyB,CAAEC,OAAQkB,MAGtCvE,IAAOyD,OAAOuB,OACb,kBACEh0B,UAAU,kCACVoyB,wBAAyB,CAAEC,OAAQrD,IAAOyD,OAAOuB,UAEjD,KACJ,mBAAKvH,GAAG,SAASzsB,UAAW,UAC1B,mBAAKA,UAAW,iBACd,YAAC,GAAD,CAASX,SAAUA,IACnB,wBAEF,kBAAIW,UAAW,oCACZ2zB,EAAY/oB,KAAI,SAACuhB,EAAM7mB,GACtB,GAAkB,KAAd6mB,EAAKA,MAA6B,KAAdA,EAAKmB,KAC3B,OACE,kBAAIhoB,IAAKA,GACP,iBACEtF,UAAU,cACVoE,KAAM+nB,EAAKA,KACX3pB,OAAO,SACP4pB,IAAI,sBACJgG,wBAAyB,CAAEC,OAAQlG,EAAKmB,YAMrC,KAAZkG,EACC,sBACE,iBAAGpvB,KAAMovB,GACP,mBAAKK,IAAKtB,GAAMwB,IAAK,gBAGvB,KAEW,KAAdN,EACC,sBACE,iBACErvB,KAAM,0CAA4CqvB,EAClDjxB,OAAO,SACP4pB,IAAI,uBAEJ,mBAAKpsB,UAAW,YAAa6zB,IAAKT,EAASW,IAAK,cAGlD,KACW,KAAdN,EACC,kBAAIzzB,UAAU,yBACZ,KACHgvB,IAAOyD,OAAOuB,OACb,kBAAIh0B,UAAW,gBACb,kBACEA,UAAU,gBACVoyB,wBAAyB,CAAEC,OAAQrD,IAAOyD,OAAOuB,WAGnD,KACJ,sBACA,mBACAh0B,UAAW,sCACXoyB,wBAAyB,CAAEC,OAAQ,kEAGnC,sBACE,YAAC,EAAD,CACExE,kBAAmBA,EACnBC,kBAAmBA,KAGtB0E,GACH,mBAAKxyB,UAAW,uCACd,YAAC,GAAD,CAAmBi0B,UAAU,EAAMC,QAASvB,MAE5C,QAIN,YAACK,GAAD,CAAanF,kBAAmBA,GAC9B,mBAAK7tB,UAAW,4BACd,oBACEkD,QAAS4vB,GACT9yB,UAAW,eACXm0B,UAAWrB,GACXsB,KAAK,SACLC,SAAU,GAEV,oBAAMr0B,UAAW,YACjB,oBAAMA,UAAW,YACjB,oBAAMA,UAAW,cAGpBwyB,GACC,mBAAKxyB,UAAW,iBACd,YAAC,GAAD,CAAmBi0B,UAAU,EAAMC,QAASvB,MAE5C,W,uCCvMhB,SAAS2B,GAAqBhuB,EAAOiuB,GACnC,QAAwC3qB,IAApCtD,EAAMkuB,SAASD,EAAWxsB,MAC5B,OAAOzB,EAAMmuB,OAAO,GAAIF,EAAYjuB,EAAMouB,OAAO,GAIrD,SAASC,GAAMvL,EAAYwL,EAAK50B,GAC9B,IAAI60B,EAAmB,GACnBC,EAAe,aAAoB1L,EAAYyL,EAAkB70B,GAErE,OAAI60B,EAAiB7sB,OAAS,EACrBhI,EAGF80B,EAAeF,EAAIC,GAG5B,IA6EIE,GAAa,SAASA,EAAW7mB,GAGnC,IAFA,IAAI8mB,EAAM,GAEDtrB,EAAI,EAAGA,EAAIwE,EAAKlG,OAAQ0B,IAAK,CACpC,IAAIwH,EAAMhD,EAAKxE,GACf,GAAW,MAAPwH,EAAJ,CACA,IAAI+jB,OAAQ,EAEZ,cAAe/jB,GACb,IAAK,UACH,MAEF,IAAK,SAED,GAAIgD,MAAM+I,QAAQ/L,GAChB+jB,EAAQF,EAAW7jB,QAInB,IAAK,IAAIpD,KAFTmnB,EAAQ,GAEM/jB,EACRA,EAAIpD,IAAMA,IACZmnB,IAAUA,GAAS,KACnBA,GAASnnB,GAKf,MAGJ,QAEImnB,EAAQ/jB,EAIV+jB,IACFD,IAAQA,GAAO,KACfA,GAAOC,IAIX,OAAOD,GC1ILE,GDmBgB,SAAuBjwB,GACzC,IAAIqB,EAAQ,aAAYrB,GAExBqB,EAAMouB,MAAMS,OAAS,SAAU1vB,GAK7B9F,KAAKy1B,SAAW3vB,GAGlBa,EAAM+uB,QAAS,EAEf,IAAIT,EAAM,WACR,IAAK,IAAIlW,EAAOvW,UAAUH,OAAQkG,EAAO,IAAIgG,MAAMwK,GAAOC,EAAO,EAAGA,EAAOD,EAAMC,IAC/EzQ,EAAKyQ,GAAQxW,UAAUwW,GAGzB,IAAI4V,EAAa,aAAgBrmB,EAAM5H,EAAM8iB,gBAAYxf,GAEzD,OADA,aAAatD,EAAOiuB,GAAY,GACzBjuB,EAAMhB,IAAM,IAAMivB,EAAWxsB,MAkCtC,MAAO,CACL6sB,IAAKA,EACLU,GAVO,WACP,IAAK,IAAIC,EAAQptB,UAAUH,OAAQkG,EAAO,IAAIgG,MAAMqhB,GAAQC,EAAQ,EAAGA,EAAQD,EAAOC,IACpFtnB,EAAKsnB,GAASrtB,UAAUqtB,GAG1B,OAAOb,GAAMruB,EAAM8iB,WAAYwL,EAAKG,GAAW7mB,KAM/CunB,aApBiB,WACjB,IAAK,IAAIC,EAAQvtB,UAAUH,OAAQkG,EAAO,IAAIgG,MAAMwhB,GAAQC,EAAQ,EAAGA,EAAQD,EAAOC,IACpFznB,EAAKynB,GAASxtB,UAAUwtB,GAG1B,IAAIpB,EAAa,aAAgBrmB,EAAM5H,EAAM8iB,YAC7CkL,GAAqBhuB,EAAOiuB,IAe5BqB,UAnCc,WACd,IAAK,IAAIC,EAAQ1tB,UAAUH,OAAQkG,EAAO,IAAIgG,MAAM2hB,GAAQC,EAAQ,EAAGA,EAAQD,EAAOC,IACpF5nB,EAAK4nB,GAAS3tB,UAAU2tB,GAG1B,IAAIvB,EAAa,aAAgBrmB,EAAM5H,EAAM8iB,YACzC2M,EAAY,aAAexB,EAAWxsB,KAK1C,OAJAusB,GAAqBhuB,EAAO,CAC1ByB,KAAMwsB,EAAWxsB,KACjB0D,OAAQ,cAAgBsqB,EAAY,IAAMxB,EAAW9oB,OAAS,MAEzDsqB,GAyBPC,QAAS,SAAiBC,GACxBA,EAAI3zB,SAAQ,SAAUgD,GACpBgB,EAAMkuB,SAASlvB,IAAO,MAG1B4wB,MAAO,WACL5vB,EAAM8iB,WAAa,GACnB9iB,EAAMkuB,SAAW,GACjBluB,EAAMouB,MAAMwB,SAGdxB,MAAOpuB,EAAMouB,MACbpuB,MAAOA,EACP6vB,oBAAqB,KAAoBz1B,KAAK,KAAM4F,EAAM8iB,YAC1DuL,MAAOA,GAAMj0B,KAAK,KAAM4F,EAAM8iB,WAAYwL,IC5FzB,GAMjB,IALQM,GAAegB,MACbhB,GAAec,QACpBd,GAAeI,GACZJ,GAAeP,MACDO,GAAeiB,oBACtBjB,GAAeO,cAClBP,GAAeU,UACrBV,GAAeN,IACbM,GAAeR,MACfQ,GAAe5uB,MCVpB,IAAM8vB,GAAU,u9WCgDRC,G,oJAzCb71B,MAAQ,CACNqtB,mBAAmB,G,EAOrByI,oBAAsB,WACpB,IAAMzI,EAAoBjoB,KAAKC,MAAMvF,OAAOi2B,aAAa5wB,QAAQ,sBAEjE,EAAK8W,SAAS,CAAEoR,uB,EAGlBC,kBAAoB,WAClB,EAAKrR,UAAS,SAAAlb,GAAS,MAAK,CAAEssB,mBAAoBtsB,EAAUssB,sBAE5DvtB,OAAOi2B,aAAatwB,QAAQ,oBAAqBL,KAAKI,WAAW,EAAKxF,MAAMqtB,qB,8CAb9ErsB,kBAAA,WACE7B,KAAK22B,uB,EAeP1zB,OAAA,WAAU,IAAD,EACwBjD,KAAKV,MAA5B2P,EADD,EACCA,SAAUvP,EADX,EACWA,SAEVwuB,EAAsBluB,KAAKa,MAA3BqtB,kBAEF2I,EAAqB3I,EAAoBN,EAAYJ,EAE3D,OACE,uBACE,YAAC,IAAD,CAAQ1hB,OAAQ2qB,KAChB,YAAC,GAAD,CACE/2B,SAAUA,EACVwuB,kBAAmBA,EACnBC,kBAAmBnuB,KAAKmuB,oBAE1B,YAAC,EAAD,CAAsB9hB,MAAOwqB,GAAqB5nB,K,GApC9B0F,a,aCNf0d,GAAU,YAAO,QAAP,sBAAH,wLAYJ,SAAA/yB,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOc,aAZxB,iNAwBP,SAAAnuB,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOgB,OAxBrB,qPA2CP,SAAAruB,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOgB,OA3CrB,6EAoDPuE,GAAW,aAAO,YAA6C,IAA1C7xB,EAAyC,EAAzCA,UAA6Bf,GAAY,EAA9B6yB,OAA8B,EAAtBC,MAAsB,+CACzE,OACE,kBAAI/xB,UAAWA,GACb,6BAAGoE,KAAMnF,EAAMgC,IAAQhC,GACpBA,EAAM2P,aAJS,sBAAH,qEAcF,mBAA0B,IAA1B,EAAGmjB,MAA2B,IAAM,MAdlC,+BAeY,SAAA9yB,GAAK,OAAI,EAAyB,GAApBA,EAAM8yB,OAAS,KAfzC,0EAuBf,SAAA9yB,GAAK,OACLA,EAAM6yB,QAAN,sMAxBe,0CCgCNI,GA/EO,SAAC,GAAD,IAAG7yB,EAAH,EAAGA,SAAH,OACpB,YAAC,cAAD,CACEqkB,MAAK,aAsBL9gB,OAAQ,YAAiB,IAGnB6zB,EAHKtE,EAAa,EAAbA,OAKT,QAAqBvoB,IAAjBuoB,EAAO3C,OAAuB2C,EAAO3C,MAAMxnB,OAAS,EACrCmqB,EAAO3C,MAAM5kB,KAAI,SAAC0kB,EAAM1Z,GACvC,IAAI8gB,OAES9sB,IAAT0lB,IAEAA,EAAKpQ,KAAK2Q,OAAOC,OAASzwB,EAAS0B,UACnCiuB,IAAOC,OAAOC,WAAaI,EAAKpQ,KAAK2Q,OAAOC,OAASzwB,EAAS0B,UAE1DuuB,EAAKpQ,KAAKyX,gBAAgB/H,QAC5B8H,EAAapH,EAAKpQ,KAAKyX,gBAAgB/H,MAAMhkB,KAAI,SAACgsB,EAAWhhB,GAC3D,IAAMihB,EAASD,EAAUjI,MACrBiI,EAAUjI,MAAMjyB,QAAQ,OAAQ,IAAImsB,cACpC,IAEJ,OACE,YAAC,GAAD,CAAUvjB,IAAKsQ,EAAO3U,GAAE,IAAM41B,EAAU9E,MAAO,GAC5C6E,EAAUjI,YAOnB+H,IACFD,EAAgBC,MAKtB,OAAID,GAAiBA,EAAczuB,OAE/B,YAAC,GAAD,KACE,kBAAIhI,UAAW,kBACb,kBAAIA,UAAW,kBAAf,YACCy2B,IAML,YAAC,GAAD,KACE,4B,UClEZ,IAAMK,GAAU,YAAO,MAAP,qBAAH,0DAGG,qBAAG9qB,MAAkBsgB,OAAOc,aAH/B,2BAMA,qBAAGphB,MAAkBsgB,OAAOgB,OAN5B,yIAqBPyJ,GAAU,YAAO,OAAP,qBAAH,yEAKG,qBAAG/qB,MAAkBsgB,OAAOc,aAL/B,yBAQK,qBAAGphB,MAAkBsgB,OAAOc,aARjC,+FAkBP4J,GAAW,YAAO,MAAP,qBAAH,mGAORC,GAAmB,YAAO,MAAP,qBAAH,wCAIhBC,GAAoB,YAAO,MAAP,qBAAH,uCA4BRC,GAxBA,SAAC,GAAD,IAAGvoB,EAAH,EAAGA,SAAUvP,EAAb,EAAaA,SAAb,OACb,YAAC,GAAD,CAAeA,SAAUA,GACvB,YAAC,eAAD,CAAa6T,WAAYkkB,GACvB,YAACN,GAAD,KACE,YAACG,GAAD,CAAkBj3B,UAAW,gBAC3B,YAAC,GAAD,CAASX,SAAUA,KAEpB2vB,IAAOG,QAAQR,MACd,mBACE3uB,UAAW,2BACXoyB,wBAAyB,CAAEC,OAAQrD,IAAOG,QAAQR,SAElD,KACJ,YAACoI,GAAD,KACE,YAACC,GAAD,KAAWpoB,IAEb,YAACsoB,GAAD,CAAmBl3B,UAAW,gBAC5B,YAAC,GAAD,CAAcX,SAAUA,SCjFrBg4B,GAAqB,YAAO,MAAP,sBAAH,khBA2BP,SAAAp4B,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOc,aA3BrB,WA4BlB,SAAAnuB,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOgB,OA5BV,mYAiDP,SAAAruB,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOc,aAjDrB,WAkDlB,SAAAnuB,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOgB,OAlDV,usBCqHhBgK,GAlHM,SAAC,GAAkB,IAClCC,EADkBC,EAAe,EAAfA,IAAKC,EAAU,EAAVA,IASrBC,GANwBD,EAAI7sB,KAAI,SAAC/I,EAAI+T,GACrC/T,GAAMA,EAAGgpB,MAAQ2M,EAAI3H,OAAOC,OAC9ByH,EAAe3hB,MAIF,IAEX+hB,EAAe,GAiCrB,YA/BqB/tB,IAAjB2tB,GAEEE,EAAI,KACNC,EAAS7M,IAAM4M,EAAI,GAAG5M,IACtB6M,EAAS/I,MAAQ8I,EAAI,GAAG9I,OAE1BgJ,EAAa9M,IAAM,KACnB8M,EAAahJ,MAAQ,KACrB4I,GAAgB,GACU,IAAjBA,GAETG,EAAS7M,IAAM4M,EAAIF,EAAe,GAAKE,EAAIF,EAAe,GAAG1M,IAAM,KACnE6M,EAAS/I,MAAQ8I,EAAIF,EAAe,GAAKE,EAAIF,EAAe,GAAG5I,MAAQ,KACvEgJ,EAAa9M,IAAM,KACnB8M,EAAahJ,MAAQ,MACZ4I,IAAiBE,EAAIzvB,OAAS,GAEvC0vB,EAAS7M,IAAM,KACf6M,EAAS/I,MAAQ,KACjBgJ,EAAa9M,IAAM4M,EAAIF,EAAe,GAAKE,EAAIF,EAAe,GAAG1M,IAAM,KACvE8M,EAAahJ,MAAQ8I,EAAIF,EAAe,GAAKE,EAAIF,EAAe,GAAG5I,MAAQ,MAClE4I,IAETG,EAAS7M,IAAM4M,EAAIF,EAAe,GAAG1M,IACrC6M,EAAS/I,MAAQ8I,EAAIF,EAAe,GAAG5I,MACnC8I,EAAIF,EAAe,KACrBI,EAAa9M,IAAM4M,EAAIF,EAAe,GAAG1M,IACzC8M,EAAahJ,MAAQ8I,EAAIF,EAAe,GAAG5I,QAK7C,YAAC0I,GAAD,KACGM,EAAa9M,KAAO0M,GAAgB,EACnC,YAAC,EAAD,CAAMt2B,GAAIw2B,EAAIF,EAAe,GAAG1M,IAAK7qB,UAAW,eAC9C,mBAAKA,UAAW,aACd,mBACE43B,oBAAoB,gBACpBxJ,OAAO,MACPD,MAAM,MACNiD,KAAK,OACLlD,MAAM,6BACNG,QAAQ,YACR7G,YAAY,IACZ8J,cAAc,QACdC,eAAe,QACfF,OAAO,eACPrxB,UAAU,YAEV,qBACE,oBAAMyxB,GAAG,KAAKC,GAAG,KAAKC,GAAG,IAAIC,GAAG,OAChC,wBAAUJ,OAAO,uBAIvB,mBAAKxxB,UAAW,mBACd,mBAAKA,UAAW,gBACd,qCAEF,mBAAKA,UAAW,qBACd,wBAAOy3B,EAAIF,EAAe,GAAG5I,UAIjC,KACH+I,EAAS7M,KAAO0M,GAAgB,EAC/B,YAAC,EAAD,CAAMt2B,GAAIw2B,EAAIF,EAAe,GAAG1M,IAAK7qB,UAAW,WAC9C,mBAAKA,UAAW,oBACd,mBAAKA,UAAW,gBACd,iCAEF,mBAAKA,UAAW,qBACd,wBAAOy3B,EAAIF,EAAe,IAAME,EAAIF,EAAe,GAAG5I,SAG1D,mBAAK3uB,UAAW,cACd,mBACE43B,oBAAoB,gBACpBxJ,OAAO,MACPD,MAAM,MACNiD,KAAK,OACLlD,MAAM,6BACNG,QAAQ,YACR7G,YAAY,IACZ8J,cAAc,QACdC,eAAe,QACfF,OAAO,eACPrxB,UAAU,YAEV,qBACE,oBAAMyxB,GAAG,IAAIC,GAAG,KAAKC,GAAG,KAAKC,GAAG,OAChC,wBAAUJ,OAAO,yBAKvB,OChHH,IAAMqG,GAAgB,YAAO,KAAP,sBAAH,wIASf,SAAA54B,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOe,UATb,KAYbyK,GAAO,YAAO,MAAP,sBAAH,ybA0BJC,GAAiB,kEAEnB,SAAA94B,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOgB,OAFT,+MAqBjB,SAAAruB,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOH,OArBX,oGA8BZ,SAAAltB,GAAK,OAAIA,EAAM+M,MAAMsgB,OAAOc,aA9BhB,+CCHf4K,GAnCc,WAAO,IAAD,EACGtI,oBAAS,GAAtCuI,EAD0B,KACdC,EADc,OAGexI,mBAAS,GAAlDyI,EAH0B,KAGRC,EAHQ,KAK3BC,EAAa,WACjB/3B,OAAOwe,QAAUqZ,EAAmBD,GAAc,GAAQA,GAAc,GACxEE,EAAoB93B,OAAOwe,UAG7BwZ,qBAAU,WASR,OARAh4B,OAAO6W,iBAAiB,SAAUkhB,GAElC/3B,OAAOi4B,SAAW,WACO,IAAnBj4B,OAAOwe,UACToZ,GAAc,GACdE,EAAoB,KAGjB,WACL93B,OAAO8W,oBAAoB,SAAUihB,OAQzC,OACE,sBAAQr4B,UAAS,yBAA0Bi4B,EAAa,GAAK,QAAU/0B,QALrD,WAClB5C,OAAOk4B,OAAO,EAAG,KAIjB,kB,6kBClBJ,IAAM/H,GAAiBzB,IAAOG,QAAQsB,eAEjBgI,G,kGACnB71B,OAAA,WAAU,IACAswB,EAASvzB,KAAKV,MAAdi0B,KAER,IAAKA,EACH,OAAO,KAET,IAAKA,EAAKG,KAER,OACE,YAAC,GAAW1zB,KAAKV,MACf,wCACA,iBAAGe,UAAW,cACZ,YAAC,OAAD,CAAMiB,GAAI,KAAV,aAZD,IAkBLkxB,EAKEe,EALFf,OACAqF,EAIEtE,EAJFsE,IAnBK,EAuBHtE,EAHFG,KACEC,aAIEoF,GAzBC,EAqBaC,aArBb,EAqB2BhK,MAIjBwD,EAAO3C,MACrB5kB,KAAI,qBAAGsU,KAAgB2Q,OAAOC,QAC9B7vB,QAAO,SAAA6vB,GAAI,MAAa,MAATA,KACf7L,OACA5W,QACC,SAACC,EAAKsrB,GAC0C,IAAD,EAA7C,GAAInI,GAAeL,MAAK,SAAAvF,GAAG,OAAIA,IAAQ+N,KACrC,OAAO,SAAKtrB,GAAZ,WAAkBsrB,GAAM,CAACA,GAAzB,IAGF,IAMgE,EAN5Dl7B,EAASk7B,EAAIvuB,MAAM,KAAK,GAM5B,OAJI2kB,IAAOC,QAAUD,IAAOC,OAAOqB,gBACjC5yB,GAAkB,KAGhBA,GAAU+yB,GAAeL,MAAK,SAAAvF,GAAG,OAAIA,IAAG,IAASntB,KAC5C,SAAK4P,GAAZ,eAAsB5P,GAAtB,sBAAqC4P,EAAI,IAAI5P,IAA7C,CAAwDk7B,IAAxD,IAEO,SAAKtrB,GAAZ,IAAiBshB,MAAM,GAAD,mBAAMthB,EAAIshB,OAAV,CAAiBgK,QAG3C,CAAEhK,MAAO,MAGP6I,EAAMhH,GACTpjB,QAAO,SAACC,EAAKsrB,GACZ,OAAOtrB,EAAI/D,OAAOmvB,EAASE,MAC1B,IACFrvB,OAAOmvB,EAAS9J,OAChBhkB,KAAI,SAAAklB,GACH,GAAIA,EAAM,CAAC,IACD5Q,EAASiT,EAAO3C,MAAMY,MAAK,qBAAGlR,KAAgB2Q,OAAOC,OAASA,KAA9D5Q,KAER,MAAO,CAAEyP,MAAOzP,EAAK2Q,OAAOlB,MAAO9D,IAAK3L,EAAK2Q,OAAOC,UAKpD+I,EAAYrB,EAAIsB,YAAYD,UAE5BE,EAAkBvB,EAAIsB,YAAYC,gBAEpCC,EAAehK,IAAOC,OAAOgK,QAMjC,OAJAD,EAC+B,MAA7BhK,IAAOC,OAAOC,WAAqB8J,EAAehK,IAAOC,OAAOC,WAAa8J,EAC/EA,GAA8BxB,EAAI3H,OAAOC,KAGvC,YAAC,GAAWnwB,KAAKV,MACf,YAAC,IAAD,KACG45B,EAAY,yBAAQA,GAAqB,KACzCA,EAAY,oBAAM9wB,KAAK,QAAQ6E,QAASisB,IAAgB,KACxDE,EAAkB,oBAAMhxB,KAAK,cAAc6E,QAASmsB,IAAsB,KAC1EF,EAAY,oBAAMpQ,SAAS,WAAW7b,QAASisB,IAAgB,KAC/DE,EAAkB,oBAAMtQ,SAAS,iBAAiB7b,QAASmsB,IAAsB,KACjFF,EAAY,oBAAMpQ,SAAS,gBAAgB7b,QAASisB,IAAgB,KACpEE,EACC,oBAAMtQ,SAAS,sBAAsB7b,QAASmsB,IAC5C,KACJ,oBAAM3M,IAAI,YAAYhoB,KAAM40B,KAE9B,mBAAKh5B,UAAW,gBACd,YAAC63B,GAAD,KAAgBL,EAAI3H,OAAOlB,OAC3B,YAACmJ,GAAD,CAAM93B,UAAW,gBAEnB,YAAC+3B,GAAD,KACE,YAAC,IAAD,KAAcP,EAAI0B,OAEpB,mBAAKl5B,UAAW,oBACd,YAAC,GAAD,CAAcw3B,IAAKA,EAAKC,IAAKA,KAE/B,YAAC,GAAD,Q,GAnGoCpzB,c,kCCf5C,oEAEA,SAAS8xB,EAAoB/M,EAAYyL,EAAkBsE,GACzD,IAAIrE,EAAe,GAQnB,OAPAqE,EAAW9uB,MAAM,KAAK/H,SAAQ,SAAUtC,QACR4J,IAA1Bwf,EAAWppB,GACb60B,EAAiBl4B,KAAKysB,EAAWppB,IAEjC80B,GAAgB90B,EAAY,OAGzB80B,EAGT,IAAIsE,EAAe,SAAsB9yB,EAAOiuB,EAAY8E,GAC1D,IAAIr5B,EAAYsG,EAAMhB,IAAM,IAAMivB,EAAWxsB,KAe7C,IARiB,IAAhBsxB,QAIqFzvB,IAAhCtD,EAAM8iB,WAAWppB,KACrEsG,EAAM8iB,WAAWppB,GAAau0B,EAAW9oB,aAGH7B,IAApCtD,EAAMkuB,SAASD,EAAWxsB,MAAqB,CACjD,IAAIzJ,EAAUi2B,EAEd,EAAG,CACiBjuB,EAAMmuB,OAAO,IAAMz0B,EAAW1B,EAASgI,EAAMouB,OAAO,GACtEp2B,EAAUA,EAAQ2qB,gBACCrf,IAAZtL,M,kCCpBb,IACMg7B,EACAjhB,EAmTAkhB,EArTFxtB,GACEutB,EAAW,EACXjhB,EAAI,CACNmhB,KAAM,CACJC,OAAQ,SAAgBxqB,GACtB,OAAIA,aAAkBsqB,EACb,IAAIA,EAAMtqB,EAAOpH,KAAMwQ,EAAEmhB,KAAKC,OAAOxqB,EAAOrC,SAAUqC,EAAOY,OACnC,UAAxBwI,EAAEmhB,KAAK3xB,KAAKoH,GACdA,EAAOrE,IAAIyN,EAAEmhB,KAAKC,QAElBxqB,EAAOvS,QAAQ,KAAM,SAASA,QAAQ,KAAM,QAAQA,QAAQ,UAAW,MAGlFmL,KAAM,SAAcgS,GAClB,OAAOhT,OAAOjG,UAAUoZ,SAASta,KAAKma,GAAG2H,MAAM,oBAAoB,IAErEkY,MAAO,SAAelzB,GAOpB,OANKA,EAAU,MACbK,OAAOC,eAAeN,EAAK,OAAQ,CACjCf,QAAS6zB,IAIN9yB,EAAU,MAGnBmzB,MAAO,SAAe9f,EAAG+f,GACvB,IAAI/xB,EAAOwQ,EAAEmhB,KAAK3xB,KAAKgS,GAIvB,OAFA+f,EAAUA,GAAW,GAEb/xB,GACN,IAAK,SACH,GAAI+xB,EAAQvhB,EAAEmhB,KAAKE,MAAM7f,IACvB,OAAO+f,EAAQvhB,EAAEmhB,KAAKE,MAAM7f,IAM9B,IAAK,IAAIvU,KAHLq0B,EAAQ,GACZC,EAAQvhB,EAAEmhB,KAAKE,MAAM7f,IAAM8f,EAEX9f,EACVA,EAAEzX,eAAekD,KACnBq0B,EAAMr0B,GAAO+S,EAAEmhB,KAAKG,MAAM9f,EAAEvU,GAAMs0B,IAItC,OAAOD,EAET,IAAK,QACH,GAAIC,EAAQvhB,EAAEmhB,KAAKE,MAAM7f,IACvB,OAAO+f,EAAQvhB,EAAEmhB,KAAKE,MAAM7f,IAG9B,IAAI8f,EAAQ,GAKZ,OAJAC,EAAQvhB,EAAEmhB,KAAKE,MAAM7f,IAAM8f,EAC3B9f,EAAEvX,SAAQ,SAAUu3B,EAAGnwB,GACrBiwB,EAAMjwB,GAAK2O,EAAEmhB,KAAKG,MAAME,EAAGD,MAEtBD,EAGX,OAAO9f,IAGXrM,UAAW,CACTssB,OAAQ,SAAgBrN,EAAIsN,GAC1B,IAAIC,EAAO3hB,EAAEmhB,KAAKG,MAAMthB,EAAE7K,UAAUif,IAEpC,IAAK,IAAInnB,KAAOy0B,EACdC,EAAK10B,GAAOy0B,EAAMz0B,GAGpB,OAAO00B,GAYTC,aAAc,SAAsBC,EAAQC,EAAQ1F,EAAQ9mB,GAE1D,IAAIoB,GADJpB,EAAOA,GAAQ0K,EAAE7K,WACE0sB,GAEnB,GAAwB,GAApB/xB,UAAUH,OAAa,CAGzB,IAAK,IAAIoyB,KAFT3F,EAAStsB,UAAU,GAGbssB,EAAOryB,eAAeg4B,KACxBrrB,EAAQqrB,GAAY3F,EAAO2F,IAI/B,OAAOrrB,EAGT,IAAImR,EAAM,GAEV,IAAK,IAAIvR,KAASI,EAChB,GAAIA,EAAQ3M,eAAeuM,GAAQ,CACjC,GAAIA,GAASwrB,EACX,IAAK,IAAIC,KAAY3F,EACfA,EAAOryB,eAAeg4B,KACxBla,EAAIka,GAAY3F,EAAO2F,IAK7Bla,EAAIvR,GAASI,EAAQJ,GAWzB,OANA0J,EAAE7K,UAAU6sB,IAAIhiB,EAAE7K,WAAW,SAAUlI,EAAKG,GACtCA,IAAUkI,EAAKusB,IAAW50B,GAAO40B,IACnCv6B,KAAK2F,GAAO4a,MAITvS,EAAKusB,GAAUha,GAGxBma,IAAK,SAAaxgB,EAAGygB,EAAUzyB,EAAM+xB,GAGnC,IAAK,IAAIlwB,KAFTkwB,EAAUA,GAAW,GAEP/f,EACRA,EAAEzX,eAAesH,KACnB4wB,EAAS56B,KAAKma,EAAGnQ,EAAGmQ,EAAEnQ,GAAI7B,GAAQ6B,GAER,WAAtB2O,EAAEmhB,KAAK3xB,KAAKgS,EAAEnQ,KAAqBkwB,EAAQvhB,EAAEmhB,KAAKE,MAAM7f,EAAEnQ,KAI7B,UAAtB2O,EAAEmhB,KAAK3xB,KAAKgS,EAAEnQ,KAAoBkwB,EAAQvhB,EAAEmhB,KAAKE,MAAM7f,EAAEnQ,OAClEkwB,EAAQvhB,EAAEmhB,KAAKE,MAAM7f,EAAEnQ,MAAO,EAE9B2O,EAAE7K,UAAU6sB,IAAIxgB,EAAEnQ,GAAI4wB,EAAU5wB,EAAGkwB,KANnCA,EAAQvhB,EAAEmhB,KAAKE,MAAM7f,EAAEnQ,MAAO,EAE9B2O,EAAE7K,UAAU6sB,IAAIxgB,EAAEnQ,GAAI4wB,EAAU,KAAMV,OAUhDW,QAAS,GACTC,UAAW,SAAmBlN,EAAMve,EAAS7B,GAC3C,IAAI8B,EAAM,CACRF,KAAMwe,EACNve,QAASA,EACT7B,SAAUA,GASZ,OANAmL,EAAEnJ,MAAMC,IAAI,kBAAmBH,GAE/BA,EAAIC,OAASoJ,EAAEjJ,SAASJ,EAAIF,KAAME,EAAID,SAEtCsJ,EAAEnJ,MAAMC,IAAI,iBAAkBH,GAEvBuqB,EAAMvzB,UAAUqS,EAAEmhB,KAAKC,OAAOzqB,EAAIC,QAASD,EAAI9B,WAExDutB,aAAc,SAAsBnN,EAAMoN,EAAQ3rB,EAAS6G,EAAO+kB,EAAUC,EAASp4B,GACnF,IAAI+2B,EAAQlhB,EAAEkhB,MAEd,IAAK,IAAI5qB,KAASI,EAChB,GAAKA,EAAQ3M,eAAeuM,IAAWI,EAAQJ,GAA/C,CAIA,GAAIA,GAASnM,EACX,OAGF,IAAIq4B,EAAW9rB,EAAQJ,GACvBksB,EAAqC,UAA1BxiB,EAAEmhB,KAAK3xB,KAAKgzB,GAAwBA,EAAW,CAACA,GAE3D,IAAK,IAAIC,EAAI,EAAGA,EAAID,EAAS7yB,SAAU8yB,EAAG,CACxC,IAAIC,EAAUF,EAASC,GACnBZ,EAASa,EAAQb,OACjBc,IAAeD,EAAQC,WACvBC,IAAWF,EAAQE,OACnBC,EAAmB,EACnBrrB,EAAQkrB,EAAQlrB,MAEpB,GAAIorB,IAAWF,EAAQA,QAAQI,OAAQ,CAErC,IAAIC,EAAQL,EAAQA,QAAQ/gB,WAAWwH,MAAM,YAAY,GACzDuZ,EAAQA,QAAUM,OAAON,EAAQA,QAAQxuB,OAAQ6uB,EAAQ,KAG3DL,EAAUA,EAAQA,SAAWA,EAE7B,IAAK,IAAIrxB,EAAIkM,EAAO0lB,EAAMX,EAAUjxB,EAAIgxB,EAAO1yB,OAAQszB,GAAOZ,EAAOhxB,GAAG1B,SAAU0B,EAAG,CACnF,IAAI0e,EAAMsS,EAAOhxB,GAEjB,GAAIgxB,EAAO1yB,OAASslB,EAAKtlB,OAEvB,OAGF,KAAIogB,aAAemR,GAAnB,CAIA,GAAI0B,GAAUvxB,GAAKgxB,EAAO1yB,OAAS,EAAG,CAIpC,GAHA+yB,EAAQ7Q,UAAYoR,IAChB9Z,EAAQuZ,EAAQrY,KAAK4K,IAGvB,MAQF,IALA,IAAIrT,EAAOuH,EAAM5L,OAASolB,EAAaxZ,EAAM,GAAGxZ,OAAS,GACrD/G,EAAKugB,EAAM5L,MAAQ4L,EAAM,GAAGxZ,OAC5B8F,EAAIpE,EACJ2hB,EAAIiQ,EAECntB,EAAMusB,EAAO1yB,OAAQ8F,EAAIK,IAAQkd,EAAIpqB,IAAOy5B,EAAO5sB,GAAGjG,OAAS6yB,EAAO5sB,EAAI,GAAGmtB,UAAWntB,EAG3FmM,IAFJoR,GAAKqP,EAAO5sB,GAAG9F,YAGX0B,EACF4xB,EAAMjQ,GAKV,GAAIqP,EAAOhxB,aAAc6vB,EACvB,SAIFgC,EAASztB,EAAIpE,EACb0e,EAAMkF,EAAKrvB,MAAMq9B,EAAKjQ,GACtB7J,EAAM5L,OAAS0lB,MACV,CACLP,EAAQ7Q,UAAY,EACpB,IAAI1I,EAAQuZ,EAAQrY,KAAK0F,GACrBmT,EAAS,EAGf,GAAK/Z,EAAL,CAQIwZ,IACFE,EAAmB1Z,EAAM,GAAKA,EAAM,GAAGxZ,OAAS,GAK9C/G,GAFAgZ,EAAOuH,EAAM5L,MAAQslB,IACrB1Z,EAAQA,EAAM,GAAGvjB,MAAMi9B,IACLlzB,OAFtB,IAGImyB,EAAS/R,EAAInqB,MAAM,EAAGgc,GACtBuhB,EAAQpT,EAAInqB,MAAMgD,GAClBiN,EAAO,CAACxE,EAAG6xB,GAEXpB,MACAzwB,EACF4xB,GAAOnB,EAAOnyB,OACdkG,EAAKvR,KAAKw9B,IAGZ,IAAIsB,EAAU,IAAIlC,EAAM5qB,EAAOurB,EAAS7hB,EAAEjJ,SAASoS,EAAO0Y,GAAU1Y,EAAO3R,EAAO2R,EAAOyZ,GAazF,GAZA/sB,EAAKvR,KAAK8+B,GAEND,GACFttB,EAAKvR,KAAK6+B,GAGZtnB,MAAMtT,UAAU4Q,OAAOhF,MAAMkuB,EAAQxsB,GAEvB,GAAVqtB,GACFljB,EAAEoiB,aAAanN,EAAMoN,EAAQ3rB,EAASrF,EAAG4xB,GAAK,EAAM3sB,GAGlDisB,EACF,WAtCA,GAAIA,EACF,WA2CZ1rB,MAAO,CACLnC,IAAK,aACLoC,IAAK,SAAapH,EAAMiH,MAE1BI,SAAU,SAAkBke,EAAMve,EAAS7B,GACzC,IAAIwtB,EAAS,CAACpN,GACVjqB,EAAO0L,EAAQ1L,KAEnB,GAAIA,EAAM,CACR,IAAK,IAAIsL,KAAStL,EAChB0L,EAAQJ,GAAStL,EAAKsL,UAGjBI,EAAQ1L,KAKjB,OAFAgV,EAAEoiB,aAAanN,EAAMoN,EAAQ3rB,EAAS,EAAG,GAAG,GAErC2rB,KAIPnB,EAAQlhB,EAAEkhB,MAAQ,SAAU1xB,EAAM+E,EAASiD,EAAO6rB,EAAYT,GAChEt7B,KAAKkI,KAAOA,EACZlI,KAAKiN,QAAUA,EACfjN,KAAKkQ,MAAQA,EAEblQ,KAAKqI,OAAqC,GAA3B0zB,GAAc,IAAI1zB,OACjCrI,KAAKs7B,SAAWA,IAGZj1B,UAAY,SAAU6T,EAAG3M,EAAUyuB,GACvC,GAAgB,iBAAL9hB,EACT,OAAOA,EAGT,GAAuB,UAAnBxB,EAAEmhB,KAAK3xB,KAAKgS,GACd,OAAOA,EAAEjP,KAAI,SAAU+U,GACrB,OAAO4Z,EAAMvzB,UAAU2Z,EAASzS,EAAU2M,MACzC1Z,KAAK,IAGV,IAAI6O,EAAM,CACRnH,KAAMgS,EAAEhS,KACR+E,QAAS2sB,EAAMvzB,UAAU6T,EAAEjN,QAASM,EAAUyuB,GAC9CC,IAAK,OACLC,QAAS,CAAC,QAAShiB,EAAEhS,MACrBi0B,WAAY,GACZ5uB,SAAUA,EACVyuB,OAAQA,GAGV,GAAI9hB,EAAEhK,MAAO,CACX,IAAIksB,EAAmC,UAAzB1jB,EAAEmhB,KAAK3xB,KAAKgS,EAAEhK,OAAqBgK,EAAEhK,MAAQ,CAACgK,EAAEhK,OAC9DqE,MAAMtT,UAAUjE,KAAK6P,MAAMwC,EAAI6sB,QAASE,GAG1C,IAAID,EAAaj1B,OAAOyC,KAAK0F,EAAI8sB,YAAYlxB,KAAI,SAAU7C,GACzD,OAAOA,EAAO,MAAQiH,EAAI8sB,WAAW/zB,IAAS,IAAIrL,QAAQ,KAAM,UAAY,OAC3EyD,KAAK,KACR,MAAO,IAAM6O,EAAI4sB,IAAM,WAAa5sB,EAAI6sB,QAAQ17B,KAAK,KAAO,KAAO27B,EAAa,IAAMA,EAAa,IAAM,IAAM9sB,EAAIpC,QAAU,KAAOoC,EAAI4sB,IAAM,KAGzIvjB,GAOTtM,EAAMyB,UAAUwuB,OAAS,CACvB,QAAW,kBACX,OAAU,iBACV,QAAW,CAETjB,QAAS,uHACTE,QAAQ,EACRf,OAAQ,CACN,kBAAmB,CACjBa,QAAS,sBACTC,YAAY,EACZC,QAAQ,EACRf,OAAQ,MAGV,OAAU,CACRa,QAAS,kBACTE,QAAQ,GAEV,YAAe,eACf,cAAe,WACf,KAAQ,eAGZ,MAAS,0BACT,IAAO,CACLF,QAAS,uHACTE,QAAQ,EACRf,OAAQ,CACN,IAAO,CACLa,QAAS,iBACTb,OAAQ,CACN,YAAe,QACf,UAAa,iBAGjB,aAAc,CACZa,QAAS,qCACTb,OAAQ,CACN,YAAe,CAAC,CACda,QAAS,KACTlrB,MAAO,eACN,SAGP,YAAe,OACf,YAAa,CACXkrB,QAAS,YACTb,OAAQ,CACN,UAAa,mBAKrB,OAAU,CAAC,CACTa,QAAS,kBACTlrB,MAAO,gBACN,uBAEL9D,EAAMyB,UAAUwuB,OAAY,IAAE9B,OAAO,cAAcA,OAAe,OAAInuB,EAAMyB,UAAUwuB,OAAe,OACrGjwB,EAAMyB,UAAUwuB,OAAgB,QAAE9B,OAAO,mBAAmBA,OAASnuB,EAAMyB,UAAUwuB,OAErFjwB,EAAMmD,MAAMnC,IAAI,QAAQ,SAAUiC,GACf,WAAbA,EAAInH,OACNmH,EAAI8sB,WAAkB,MAAI9sB,EAAIpC,QAAQlQ,QAAQ,QAAS,SAG3DmK,OAAOC,eAAeiF,EAAMyB,UAAUwuB,OAAOJ,IAAK,aAAc,CAY9Dn2B,MAAO,SAAoBw2B,EAASjC,GAClC,IAAIkC,EAAsB,GAC1BA,EAAoB,YAAclC,GAAQ,CACxCe,QAAS,oCACTC,YAAY,EACZd,OAAQnuB,EAAMyB,UAAUwsB,IAE1BkC,EAA2B,MAAI,uBAC/B,IAAIhC,EAAS,CACX,iBAAkB,CAChBa,QAAS,4BACTb,OAAQgC,IAGZhC,EAAO,YAAcF,GAAQ,CAC3Be,QAAS,UACTb,OAAQnuB,EAAMyB,UAAUwsB,IAE1B,IAAImC,EAAM,GACVA,EAAIF,GAAW,CACblB,QAASM,OAAO,wFAAwF9uB,OAAO7P,QAAQ,OAAO,WAC5H,OAAOu/B,KACL,KACJjB,YAAY,EACZC,QAAQ,EACRf,OAAQA,GAEVnuB,EAAMyB,UAAUysB,aAAa,SAAU,QAASkC,MAGpDpwB,EAAMyB,UAAU4uB,KAAOrwB,EAAMyB,UAAUwuB,OACvCjwB,EAAMyB,UAAU6uB,OAAStwB,EAAMyB,UAAUwuB,OACzCjwB,EAAMyB,UAAU8uB,IAAMvwB,EAAMyB,UAAUwuB,OACtCjwB,EAAMyB,UAAU+uB,IAAMxwB,EAAMyB,UAAUssB,OAAO,SAAU,IACvD/tB,EAAMyB,UAAUgvB,KAAOzwB,EAAMyB,UAAU+uB,IACvCxwB,EAAMyB,UAAUivB,KAAO1wB,EAAMyB,UAAU+uB,IACvCxwB,EAAMyB,UAAUkvB,IAAM3wB,EAAMyB,UAAU+uB,IAGtC,SAAWxwB,GAKT,IAAI4wB,EAAU,0oCACVC,EAAsB,CACxB7B,QAAS,4BACTC,YAAY,EACZnrB,MAAO,cAEPqqB,OAAQ,MAGN2C,EAAe,CACjB,KAAQD,EACR,YAAe,CACb7B,QAASM,OAAO,MAAQsB,GACxB9sB,MAAO,YAET,SAAY,CACZ,CACEkrB,QAAS,sBACTE,QAAQ,EACRf,OAAQ,CAEN,SAAY,CAAC,CACXa,QAAS,uBACTC,YAAY,GACX,WACH,OAAU,8DAEV,SAAY,6FAEZ,YAAe,oBAGnB,CACED,QAAS,qCACTE,QAAQ,EACRf,OAAQ,CACN,SAAY,oBAGhB,CACEa,QAAS,cACTE,QAAQ,EACRf,OAAQ,CACN,SAAY,mCACZ,YAAe,SACf,YAAe,CACba,QAASM,OAAO,QAAUsB,GAC1B3B,YAAY,EACZnrB,MAAO,cAGV,sBAEH,OAAU,wFAEZ9D,EAAMyB,UAAUsvB,KAAO,CACrB,QAAW,CACT/B,QAAS,aACTlrB,MAAO,aAET,QAAW,CACTkrB,QAAS,kBACTC,YAAY,GAEd,gBAAiB,CAIjB,CAEED,QAAS,+CACTC,YAAY,EACZnrB,MAAO,YACN,CAEDkrB,QAAS,2BACTlrB,MAAO,aAGT,gBAAiB,CACfkrB,QAAS,sCACTlrB,MAAO,WACPmrB,YAAY,GAId,cAAe,CACbD,QAAS,gCACTb,OAAQ,CACN,YAAe,CACba,QAASM,OAAO,uBAAyBsB,GACzC3B,YAAY,EACZnrB,MAAO,aAGXA,MAAO,WACPmrB,YAAY,GAEd,OAAU,CACV,CACED,QAAS,oDACTC,YAAY,EACZC,QAAQ,EACRf,OAAQ2C,GAGV,CACE9B,QAAS,2DACTC,YAAY,EACZC,QAAQ,EACRf,OAAQ,CACN,KAAQ0C,IAGZ,CACE7B,QAAS,qFACTC,YAAY,EACZC,QAAQ,EACRf,OAAQ2C,IAEV,YAAe,CACb9B,QAASM,OAAO,OAASsB,GACzB9sB,MAAO,YAET,SAAYgtB,EAAaE,SACzB,SAAY,CACVhC,QAAS,ogDACTC,YAAY,GAEd,QAAW,CACTD,QAAS,gHACTC,YAAY,GAGd,QAAW,CACTD,QAAS,6SACTC,YAAY,EAEZnrB,MAAO,cAET,QAAW,CACTkrB,QAAS,iDACTC,YAAY,GAEd,kBAAmB,CACjBD,QAAS,UACTlrB,MAAO,aAET,SAAY,CAEVkrB,QAAS,6EACTb,OAAQ,CACN,kBAAmB,CACjBa,QAAS,MACTlrB,MAAO,eAIb,YAAe,iCACf,OAAU,CACRkrB,QAAS,qCACTC,YAAY,IAGhB4B,EAAoB1C,OAASnuB,EAAMyB,UAAUsvB,KAM7C,IAHA,IAAIE,EAAa,CAAC,UAAW,gBAAiB,gBAAiB,cAAe,SAAU,cAAe,WAAY,UAAW,UAAW,UAAW,kBAAmB,WAAY,cAAe,UAC9L9C,EAAS2C,EAAaE,SAAS,GAAG7C,OAE7BxwB,EAAI,EAAGA,EAAIszB,EAAWh1B,OAAQ0B,IACrCwwB,EAAO8C,EAAWtzB,IAAMqC,EAAMyB,UAAUsvB,KAAKE,EAAWtzB,IAG1DqC,EAAMyB,UAAUyvB,MAAQlxB,EAAMyB,UAAUsvB,KAnL1C,CAoLG/wB,GAIHA,EAAMyB,UAAU0vB,MAAQ,CACtB,QAAW,CAAC,CACVnC,QAAS,kCACTC,YAAY,EACZC,QAAQ,GACP,CACDF,QAAS,mBACTC,YAAY,EACZC,QAAQ,IAEV,OAAU,CACRF,QAAS,iDACTE,QAAQ,GAEV,aAAc,CACZF,QAAS,2FACTC,YAAY,EACZd,OAAQ,CACN,YAAe,UAGnB,QAAW,6GACX,QAAW,qBACX,SAAY,YACZ,OAAU,4DACV,SAAY,+CACZ,YAAe,iBAIjBnuB,EAAMyB,UAAU2vB,EAAIpxB,EAAMyB,UAAUssB,OAAO,QAAS,CAClD,QAAW,CACTiB,QAAS,sEACTE,QAAQ,GAEV,aAAc,CACZF,QAAS,mFACTC,YAAY,GAEd,QAAW,oVACX,SAAY,sBACZ,OAAU,oHACV,SAAY,oDAEdjvB,EAAMyB,UAAUysB,aAAa,IAAK,SAAU,CAC1C,MAAS,CAGPc,QAAS,yFACTC,YAAY,EACZC,QAAQ,EACRprB,MAAO,WACPqqB,OAAQ,CACN,OAAU,CAAC,CAETa,QAAS,2BACTC,YAAY,GACXjvB,EAAMyB,UAAU2vB,EAAU,QAC7B,QAAWpxB,EAAMyB,UAAU2vB,EAAW,QACtC,aAAc,CAAC,CACbpC,QAAS,+BACTC,YAAY,GACX,CACDD,QAAS,+BACTC,YAAY,EACZnrB,MAAO,aAGT,UAAa,CACXkrB,QAAS,gBACTC,YAAY,EACZnrB,MAAO,WAET,iBAAkB,KAClB,YAAe,kBACf,WAAc,CACZkrB,QAAS,YACTb,OAAQnuB,EAAMyB,UAAU2vB,KAK9B,SAAY,sIAEPpxB,EAAMyB,UAAU2vB,EAAW,QAGlC,SAAWpxB,GACT,IAAIqxB,EAAU,uqBACdrxB,EAAMyB,UAAU6vB,IAAMtxB,EAAMyB,UAAUssB,OAAO,IAAK,CAChD,aAAc,CAAC,CACbiB,QAASM,OAAO,gEAAgE9uB,OAAO7P,QAAQ,cAAc,WAC3G,OAAO0gC,EAAQ7wB,WAEjByuB,YAAY,GAKd,iCAEA,oCAEA,gEACA,QAAWoC,EACX,OAAU,CACRrC,QAAS,iJACTE,QAAQ,GAEV,SAAY,qHACZ,QAAW,uBAEblvB,EAAMyB,UAAUysB,aAAa,MAAO,SAAU,CAC5C,aAAc,CACZc,QAAS,oCACTlrB,MAAO,SACPorB,QAAQ,KAGZlvB,EAAMyB,UAAUysB,aAAa,MAAO,aAAc,CAGhD,cAAe,CACbc,QAAS,6EACTC,YAAY,EACZC,QAAQ,EACRf,OAAQnuB,EAAMyB,UAAUssB,OAAO,MAAO,OAG1C/tB,EAAMyB,UAAUysB,aAAa,SAAU,WAAY,CAEjD,aAAc,2BACbluB,EAAMyB,UAAU6vB,IAAI,gBA7CzB,CA8CGtxB,GAIH,SAAWA,GACT,IAAIpN,EAAS,gDACboN,EAAMyB,UAAUonB,IAAM,CACpB,QAAW,mBACX,OAAU,CACRmG,QAAS,iDACTb,OAAQ,CACN,KAAQ,WACR,6BAA8B,CAC5Ba,QAAS,4FACTC,YAAY,EACZnrB,MAAO,YAET,QAAW,CACTkrB,QAAS,yCACTC,YAAY,KAKlB,IAAO,CAELD,QAASM,OAAO,eAAiB18B,EAAO4N,OAAS,IAAM,8BAA8BA,OAAS,OAAQ,KACtG0uB,QAAQ,EACRf,OAAQ,CACN,SAAY,QACZ,YAAe,UACf,OAAU,CACRa,QAASM,OAAO,IAAM18B,EAAO4N,OAAS,KACtCsD,MAAO,SAIb,SAAYwrB,OAAO,0CAA4C18B,EAAO4N,OAAS,iBAC/E,OAAU,CACRwuB,QAASp8B,EACTs8B,QAAQ,GAEV,SAAY,+DACZ,UAAa,gBACb,SAAY,oBACZ,YAAe,aAEjBlvB,EAAMyB,UAAUonB,IAAY,OAAEsF,OAAO72B,KAAO0I,EAAMyB,UAAUonB,IAC5D,IAAIoH,EAASjwB,EAAMyB,UAAUwuB,OAEzBA,IACFA,EAAOJ,IAAI0B,WAAW,QAAS,OAC/BvxB,EAAMyB,UAAUysB,aAAa,SAAU,aAAc,CACnD,aAAc,CACZc,QAAS,6CACTC,YAAY,EACZd,OAAQ,CACN,aAAc,CACZa,QAAS,qCACTb,OAAQ,CACN,MAAS,CACPa,QAAS,yBACTC,YAAY,EACZnrB,MAAO,eACPqqB,OAAQnuB,EAAMyB,UAAUonB,KAE1B,YAAe,CAAC,CACdmG,QAAS,KACTlrB,MAAO,eACN,SAGP,YAAa,aAGhBmsB,EAAOJ,MAvEd,CAyEG7vB,GAIH,SAAWA,GACT,IACIwxB,EADA5+B,EAAS,gDAEboN,EAAMyB,UAAUonB,IAAI4I,SAAW,CAC7BzC,QAAShvB,EAAMyB,UAAUonB,IAAI4I,SAC7BtD,OAAQqD,EAAiB,CACvB,iBAAkB,+DAClB,eAAgB,UAChB,MAAS,WACT,GAAM,UACN,UAAa,CACXxC,QAASM,OAAO,oBAAsB18B,EAAO4N,OAAS,SACtD0uB,QAAQ,EACRf,OAAQ,CACN,YAAe,UACf,mBAAoB,CAClBa,QAAS,aACTC,YAAY,EACZnrB,MAAO,WAET,UAAa,CACXkrB,QAAS,4CACTC,YAAY,EACZd,OAAQ,CACN,YAAe,QAGnB,YAAa,CACXa,QAAS,oCACTC,YAAY,GAEd,aAAc,CAACr8B,EAAQ,CACrBo8B,QAAS,4CACTC,YAAY,IAEd,SAAY,cAGhB,OAAQ,CAAC,CACPD,QAAS,kDACTC,YAAY,EACZd,OAAQ,CACN,OAAU,SACV,SAAY,SAEb,CACDa,QAAS,gCACTC,YAAY,IAEd,WAAc,cAId,YAAe,UAGnBjvB,EAAMyB,UAAUonB,IAAY,OAAEsF,OAAO,8BAA8BA,OAASqD,EAC5ExxB,EAAMyB,UAAUysB,aAAa,MAAO,WAAY,CAC9C,SAAY,CACVc,QAAS,8EACTC,YAAY,KAGhB,IAAIyC,EAAO,CACT1C,QAAS,wBACTC,YAAY,GAGV0C,EAAS,CACX3C,QAAS,uCACTC,YAAY,GAEdjvB,EAAMyB,UAAUysB,aAAa,MAAO,WAAY,CAC9C,SAAY,CACVc,QAAS,qBACTC,YAAY,GAId,QAAW,CACTD,QAAS,8BACTlrB,MAAO,SAET,MAAS,CAAC,q5CAAs5C,CAC95CkrB,QAAS,4JACTb,OAAQ,CACN,KAAQuD,EACR,OAAUC,EACV,SAAY,eACZ,YAAe,WAInB,OAAU,kBACV,KAAQD,EACR,OAAUC,IA/Fd,CAiGG3xB,GAIHA,EAAMyB,UAAUmwB,WAAa5xB,EAAMyB,UAAUssB,OAAO,QAAS,CAC3D,aAAc,CAAC/tB,EAAMyB,UAAU0vB,MAAM,cAAe,CAClDnC,QAAS,0GACTC,YAAY,IAEd,QAAW,CAAC,CACVD,QAAS,kCACTC,YAAY,GACX,CACDD,QAAS,oZACTC,YAAY,IAGd,SAAY,oGACZ,OAAU,gOACV,SAAY,8FAEdjvB,EAAMyB,UAAUmwB,WAAW,cAAc,GAAG5C,QAAU,uEACtDhvB,EAAMyB,UAAUysB,aAAa,aAAc,UAAW,CACpD,MAAS,CACPc,QAAS,uLACTC,YAAY,EACZC,QAAQ,EACRf,OAAQ,CACN,eAAgB,CACda,QAAS,4BACTC,YAAY,EACZnrB,MAAO,iBACPqqB,OAAQnuB,EAAMyB,UAAUowB,OAE1B,cAAe,UACf,kBAAmB,YAIvB,oBAAqB,CACnB7C,QAAS,gMACTlrB,MAAO,YAET,UAAa,CAAC,CACZkrB,QAAS,sIACTC,YAAY,EACZd,OAAQnuB,EAAMyB,UAAUmwB,YACvB,CACD5C,QAAS,mEACTb,OAAQnuB,EAAMyB,UAAUmwB,YACvB,CACD5C,QAAS,kEACTC,YAAY,EACZd,OAAQnuB,EAAMyB,UAAUmwB,YACvB,CACD5C,QAAS,8eACTC,YAAY,EACZd,OAAQnuB,EAAMyB,UAAUmwB,aAE1B,SAAY,8BAEd5xB,EAAMyB,UAAUysB,aAAa,aAAc,SAAU,CACnD,kBAAmB,CACjBc,QAAS,oEACTE,QAAQ,EACRf,OAAQ,CACN,uBAAwB,CACtBa,QAAS,QACTlrB,MAAO,UAET,cAAiB,CACfkrB,QAAS,6DACTC,YAAY,EACZd,OAAQ,CACN,4BAA6B,CAC3Ba,QAAS,UACTlrB,MAAO,eAETxM,KAAM0I,EAAMyB,UAAUmwB,aAG1B,OAAU,cAKZ5xB,EAAMyB,UAAUwuB,QAClBjwB,EAAMyB,UAAUwuB,OAAOJ,IAAI0B,WAAW,SAAU,cAGlDvxB,EAAMyB,UAAUqwB,GAAK9xB,EAAMyB,UAAUmwB,WAGrC,SAAW5xB,GACT,IAAI4xB,EAAa5xB,EAAMytB,KAAKG,MAAM5tB,EAAMyB,UAAUmwB,YAClD5xB,EAAMyB,UAAUswB,IAAM/xB,EAAMyB,UAAUssB,OAAO,SAAU6D,GACvD5xB,EAAMyB,UAAUswB,IAAIlC,IAAIb,QAAU,2MAClChvB,EAAMyB,UAAUswB,IAAIlC,IAAI1B,OAAY,IAAEa,QAAU,kBAChDhvB,EAAMyB,UAAUswB,IAAIlC,IAAI1B,OAAO,cAAca,QAAU,gEACvDhvB,EAAMyB,UAAUswB,IAAIlC,IAAI1B,OAAY,IAAEA,OAAO,cAAgB,4BAC7DnuB,EAAMyB,UAAUysB,aAAa,SAAU,YAAa,CAClD,OAAU,CACRc,QAAS,sDACTb,OAAQ,CACN,YAAe,cACf,aAAc,SAGjBnuB,EAAMyB,UAAUswB,IAAIlC,KACvB7vB,EAAMyB,UAAUysB,aAAa,SAAU,aAAc,CACnD,OAAU,CAERc,QAAS,iDACTb,OAAQ,CACN,qBAAsB,CACpBa,QAAS,UACTlrB,MAAO,eAETxM,KAAM0I,EAAMyB,UAAUswB,KAExB,MAAS,wBAEV/xB,EAAMyB,UAAUswB,IAAIlC,KAEvB,IAAImC,EAAiB,SAASA,EAAepvB,GAC3C,OAAKA,EAIgB,iBAAVA,EACFA,EAGoB,iBAAlBA,EAAM/B,QACR+B,EAAM/B,QAGR+B,EAAM/B,QAAQhC,IAAImzB,GAAgB59B,KAAK,IAXrC,IA6EX4L,EAAMmD,MAAMnC,IAAI,kBAAkB,SAAUiC,GACrB,QAAjBA,EAAI9B,UAAuC,QAAjB8B,EAAI9B,UAhEnB,SAAS8wB,EAAW/uB,GAGnC,IAFA,IAAIgvB,EAAa,GAERv0B,EAAI,EAAGA,EAAIuF,EAAOjH,OAAQ0B,IAAK,CACtC,IAAIiF,EAAQM,EAAOvF,GACfw0B,GAAiB,EA+BrB,GA7BqB,iBAAVvvB,IACU,QAAfA,EAAM9G,MAAkB8G,EAAM/B,QAAQ,IAAgC,QAA1B+B,EAAM/B,QAAQ,GAAG/E,KAEnB,OAAxC8G,EAAM/B,QAAQ,GAAGA,QAAQ,GAAGA,QAE1BqxB,EAAWj2B,OAAS,GAAKi2B,EAAWA,EAAWj2B,OAAS,GAAGi0B,UAAY8B,EAAepvB,EAAM/B,QAAQ,GAAGA,QAAQ,KAEjHqxB,EAAWhuB,MAG2C,OAApDtB,EAAM/B,QAAQ+B,EAAM/B,QAAQ5E,OAAS,GAAG4E,SAE1CqxB,EAAWthC,KAAK,CACds/B,QAAS8B,EAAepvB,EAAM/B,QAAQ,GAAGA,QAAQ,IACjDuxB,aAAc,IAIXF,EAAWj2B,OAAS,GAAoB,gBAAf2G,EAAM9G,MAA4C,MAAlB8G,EAAM/B,QAExEqxB,EAAWA,EAAWj2B,OAAS,GAAGm2B,eACzBF,EAAWj2B,OAAS,GAAKi2B,EAAWA,EAAWj2B,OAAS,GAAGm2B,aAAe,GAAoB,gBAAfxvB,EAAM9G,MAA4C,MAAlB8G,EAAM/B,QAE9HqxB,EAAWA,EAAWj2B,OAAS,GAAGm2B,eAElCD,GAAiB,IAIjBA,GAAmC,iBAAVvvB,IACvBsvB,EAAWj2B,OAAS,GAAwD,IAAnDi2B,EAAWA,EAAWj2B,OAAS,GAAGm2B,aAAoB,CAGjF,IAAIC,EAAYL,EAAepvB,GAE3BjF,EAAIuF,EAAOjH,OAAS,IAA+B,iBAAlBiH,EAAOvF,EAAI,IAA0C,eAAvBuF,EAAOvF,EAAI,GAAG7B,QAC/Eu2B,GAAaL,EAAe9uB,EAAOvF,EAAI,IACvCuF,EAAOuC,OAAO9H,EAAI,EAAG,IAGnBA,EAAI,IAA+B,iBAAlBuF,EAAOvF,EAAI,IAA0C,eAAvBuF,EAAOvF,EAAI,GAAG7B,QAC/Du2B,EAAYL,EAAe9uB,EAAOvF,EAAI,IAAM00B,EAC5CnvB,EAAOuC,OAAO9H,EAAI,EAAG,GACrBA,KAGFuF,EAAOvF,GAAK,IAAIqC,EAAMwtB,MAAM,aAAc6E,EAAW,KAAMA,GAI3DzvB,EAAM/B,SAAoC,iBAAlB+B,EAAM/B,SAChCoxB,EAAWrvB,EAAM/B,UAUrBoxB,CAAWhvB,EAAIC,WAnHnB,CAqHGlD,GAIH,SAAWA,GAmCT,SAASsyB,EAAO9xB,EAAQ6uB,GACtB,OAAOC,OAAO9uB,EAAO7P,QAAQ,SAAS,WACpC,MAAO,yDAAyD6P,UAC9D6uB,GArCNrvB,EAAMyB,UAAUysB,aAAa,aAAc,oBAAqB,CAC9D,kBAAmB,CACjBc,QAASM,OAAO,YAActvB,EAAMyB,UAAUmwB,WAAW,qBAAqB5C,QAAQxuB,QACtFyuB,YAAY,EACZnrB,MAAO,CAAC,oBAAqB,SAAU,WAAY,sBAGvD9D,EAAMyB,UAAUysB,aAAa,aAAc,WAAY,CACrD,OAAU,CACRc,QAASM,OAAO,YAActvB,EAAMyB,UAAUmwB,WAAqB,SAAEpxB,QACrEyuB,YAAY,EACZnrB,MAAO,CAAC,WAAY,sBAGxB9D,EAAMyB,UAAUysB,aAAa,aAAc,WAAY,CACrD,mBAAoB,CAAC,CAGnBc,QAAS,yOACTlrB,MAAO,cACN,CAEDkrB,QAAS,wBACTlrB,MAAO,iBAiBX9D,EAAMyB,UAAUysB,aAAa,aAAc,UAAW,CACpD,QAAW,CAETc,QAASsD,EAAO,4GAA4G9xB,QAC5HyuB,YAAY,EACZd,OAAQnuB,EAAMyB,UAAUmwB,YAE1B,QAAW,CAET5C,QAASsD,EAAO,mEAAmE9xB,QACnFyuB,YAAY,EACZd,OAAQnuB,EAAMyB,UAAUmwB,cAG5B5xB,EAAMyB,UAAUmwB,WAAoB,QAAE/M,QAAQ,CAC5CmK,QAAS,wCACTlrB,MAAO,UACN,CACDkrB,QAAS,gGACTlrB,MAAO,gBACN,CACDkrB,QAAS,WACTlrB,MAAO,CAAC,OAAQ,QACf,CACDkrB,QAAS,gBACTlrB,MAAO,QAET9D,EAAMyB,UAAUysB,aAAa,aAAc,WAAY,CACrD,OAAU,CACRc,QAAS,QACTlrB,MAAO,YAET,MAAS,CACPkrB,QAAS,KACTlrB,MAAO,cAGX9D,EAAMyB,UAAUysB,aAAa,aAAc,cAAe,CACxD,kBAAmB,CACjBc,QAASsD,EAAO,gBAAgB9xB,QAChCyuB,YAAY,GAEd,mBAAoB,CAClBD,QAAS,8CACTC,YAAY,GAEd,IAAO,CAELD,QAAS,kFACTlrB,MAAO,YAET,QAAW,CACTkrB,QAAS,qBACTlrB,MAAO,gBAMX,IAFA,IAAIyuB,EAAuB,CAAC,WAAY,oBAAqB,SAAU,kBAAmB,mBAEjF50B,EAAI,EAAGA,EAAI40B,EAAqBt2B,OAAQ0B,IAAK,CACpD,IAAIiF,EAAQ2vB,EAAqB50B,GAC7BjE,EAAQsG,EAAMyB,UAAUmwB,WAAWhvB,GAER,WAA3B5C,EAAMytB,KAAK3xB,KAAKpC,KAClBA,EAAQsG,EAAMyB,UAAUmwB,WAAWhvB,GAAS,CAC1CosB,QAASt1B,IAKb,IAAIy0B,EAASz0B,EAAMy0B,QAAU,GAC7Bz0B,EAAMy0B,OAASA,EACfA,EAAO,oBAAsB,iBAjHjC,CAmHGnuB,GAIH,SAAWA,GAET,IAAIwyB,EAAU,YACVlV,EAAgB,CAClB0R,QAAS,aACTlrB,MAAO,YAET9D,EAAMyB,UAAUgxB,aAAezyB,EAAMyB,UAAUssB,OAAO,aAAc,CAClE,QAAWyE,EACX,OAAU,CACV,CACExD,QAAS,yBACTE,QAAQ,GACP,CAEDF,QAAS,yBACTE,QAAQ,EACRf,OAAQ,CACN,cAAiB7Q,KAGrB,QAAW,mSACX,eAAgB,CACd0R,QAAS,aACTlrB,MAAO,cAGX9D,EAAMyB,UAAUysB,aAAa,eAAgB,UAAW,CACtD,oBAAqB,CACnBc,QAAS,iBACTlrB,MAAO,WAGT,cAAe,CACbkrB,QAAS,qBACTlrB,MAAO,QACPqqB,OAAQ,CACN,QAAWqE,EACX,cAAiBlV,MAIvBtd,EAAMyB,UAAUysB,aAAa,eAAgB,SAAU,CACrD,oBAAqB,CACnBc,QAAS,yBACTb,OAAQ,CACN,UAAa,CACXa,QAAS,QACTlrB,MAAO,eAET,OAAU,CACRkrB,QAAS,UACTlrB,MAAO,sBACPqqB,OAAQnuB,EAAMyB,UAAUmwB,cAK9B,mBAAoB,CAAC,CACnB5C,QAAS,iBACTE,QAAQ,EACRprB,MAAO,UACN,CACDkrB,QAAS,iBACTE,QAAQ,EACRprB,MAAO,SACPqqB,OAAQ,CACN7Q,cAAeA,OAIrBtd,EAAMyB,UAAUysB,aAAa,eAAgB,UAAW,CAEtD,SAAY,kCAEPluB,EAAMyB,UAAUgxB,aAAa,mBACpCzyB,EAAMyB,UAAUixB,OAAS1yB,EAAMyB,UAAUgxB,aA5E3C,CA6EGzyB,GAIH,SAAWA,GACTA,EAAMyB,UAAUkxB,KAAO,CACrB,MAAS,CACT,4BACA,YACA,YASF,IAAIC,EAAW,CACb,eAAgB,IAChB,gBAAiB,IACjB,gBAAiB,IACjB,iBAAkB,IAClB,UAAa,IACb,KAAQ,KAGV93B,OAAOyC,KAAKq1B,GAAUr8B,SAAQ,SAAUyF,GACtC,IAAIrK,EAASihC,EAAS52B,GAClB8H,EAAQ,GAEP,QAAQkJ,KAAKhR,IAEhB8H,EAAMlT,KAAK,MAAM+lB,KAAK3a,GAAM,IAGjB,SAATA,GACF8H,EAAMlT,KAAK,QAGboP,EAAMyB,UAAUkxB,KAAK32B,GAAQ,CAC3BgzB,QAASM,OAAO,QAAU39B,EAAS,iCAAkC,KACrEmS,MAAOA,EACPqqB,OAAQ,CACN,KAAQ,CACNa,QAAS,+BACTC,YAAY,GAEd,OAAU,CACRD,QAAS,SACTlrB,MAAO,MAAM6S,KAAK3a,GAAM,SAMhClB,OAAOC,eAAeiF,EAAMyB,UAAUkxB,KAAM,WAAY,CACtDj5B,MAAOk5B,IArDX,CAuDG5yB,GAIHA,EAAMyB,UAAUoxB,IAAM,CAUpB,QAAW,QAKX,QAAW,WACX,SAAY,SAKZ,OAAU,mCAOV,QAAW,CACT7D,QAAS,iBACTb,OAAQ,CAON,UAAa,cAiBjB,MAAS,YAYT,cAAe,oBAIjBnuB,EAAMyB,UAAU8J,GAAKvL,EAAMyB,UAAUssB,OAAO,QAAS,CACnD,OAAU,CACRiB,QAAS,qCACTE,QAAQ,GAEV,QAAW,sKACX,QAAW,gCACX,OAAU,gEACV,SAAY,wFACZ,QAAW,oMAENlvB,EAAMyB,UAAU8J,GAAG,cAG1BvL,EAAMyB,UAAUqxB,QAAU,CACxB,QAAW,MACX,YAAe,CACb9D,QAAS,mEACTE,QAAQ,EACRprB,MAAO,SACPqqB,OAAQ,CACN,oBAAqB,CACnBa,QAAS,kCACTC,YAAY,EACZd,OAAQnuB,EAAMyB,UAAUsxB,YAI9B,OAAU,CACR/D,QAAS,iDACTE,QAAQ,GAEV,OAAU,2CACV,QAAW,qBACX,SAAY,eACZ,UAAa,CACXF,QAAS,cACTlrB,MAAO,YAET,YAAa,CACXkrB,QAAS,+DACTE,QAAQ,GAEV,aAAc,CACZF,QAAS,6EACTC,YAAY,GAEd,SAAY,CACVD,QAAS,+CACTC,YAAY,EACZnrB,MAAO,YAET,QAAW,uIACX,SAAY,eACZ,YAAe,iBACf,SAAY,8BAId,SAAW9D,GAQT,SAASgzB,EAAe7xB,EAAU0I,GAChC,MAAO,MAAQ1I,EAAS8xB,cAAgBppB,EAAQ,MAGlD/O,OAAOyL,iBAAiBvG,EAAMyB,UAAU,qBAAuB,GAAI,CACjEyxB,kBAAmB,CAYjBx5B,MAAO,SAAeuJ,EAAK9B,EAAUgyB,EAAoBC,GACvD,GAAInwB,EAAI9B,WAAaA,EAArB,CAIA,IAAIkyB,EAAapwB,EAAIowB,WAAa,GAClCpwB,EAAIF,KAAOE,EAAIF,KAAKpS,QAAQwiC,GAAoB,SAAU1d,GACxD,GAA6B,mBAAlB2d,IAAiCA,EAAc3d,GACxD,OAAOA,EAMT,IAHA,IACI6d,EADA31B,EAAI01B,EAAWp3B,QAGqD,IAAjEgH,EAAIF,KAAKf,QAAQsxB,EAAcN,EAAe7xB,EAAUxD,OAC3DA,EAKJ,OADA01B,EAAW11B,GAAK8X,EACT6d,KAGTrwB,EAAID,QAAUhD,EAAMyB,UAAUwuB,UAGlCsD,qBAAsB,CAOpB75B,MAAO,SAAeuJ,EAAK9B,GACzB,GAAI8B,EAAI9B,WAAaA,GAAa8B,EAAIowB,WAAtC,CAKApwB,EAAID,QAAUhD,EAAMyB,UAAUN,GAC9B,IAAI4tB,EAAI,EACJxxB,EAAOzC,OAAOyC,KAAK0F,EAAIowB,aAE3B,SAASpB,EAAW/uB,GAClB,IAAK,IAAIvF,EAAI,EAAGA,EAAIuF,EAAOjH,UAErB8yB,GAAKxxB,EAAKtB,QAFmB0B,IAAK,CAMtC,IAAIiF,EAAQM,EAAOvF,GAEnB,GAAqB,iBAAViF,GAAsBA,EAAM/B,SAAoC,iBAAlB+B,EAAM/B,QAAsB,CACnF,IAAIkB,EAAIxE,EAAKwxB,GACTyE,EAAIvwB,EAAIowB,WAAWtxB,GACnB0xB,EAAqB,iBAAV7wB,EAAqBA,EAAQA,EAAM/B,QAC9CyyB,EAAcN,EAAe7xB,EAAUY,GACvC8H,EAAQ4pB,EAAEzxB,QAAQsxB,GAEtB,GAAIzpB,GAAS,EAAG,GACZklB,EACF,IAAIX,EAASqF,EAAEpgB,UAAU,EAAGxJ,GACxB6pB,EAAS,IAAI1zB,EAAMwtB,MAAMrsB,EAAUnB,EAAMqD,SAASmwB,EAAGvwB,EAAID,SAAU,YAAc7B,EAAUqyB,GAC3F/D,EAAQgE,EAAEpgB,UAAUxJ,EAAQypB,EAAYr3B,QACxC03B,EAAc,GAEdvF,GACFuF,EAAY/iC,KAAK6P,MAAMkzB,EAAa1B,EAAW,CAAC7D,KAGlDuF,EAAY/iC,KAAK8iC,GAEbjE,GACFkE,EAAY/iC,KAAK6P,MAAMkzB,EAAa1B,EAAW,CAACxC,KAG7B,iBAAV7sB,EACTM,EAAOuC,OAAOhF,MAAMyC,EAAQ,CAACvF,EAAG,GAAGH,OAAOm2B,IAE1C/wB,EAAM/B,QAAU8yB,QAGX/wB,EAAM/B,SAGboxB,EAAWrvB,EAAM/B,SAIvB,OAAOqC,EAGT+uB,CAAWhvB,EAAIC,aArHvB,CAyHGlD,GAIH,SAAWA,GACTA,EAAMyB,UAAUmyB,WAAa,CAC3B,QAAW,oBACX,UAAa,CACX5E,QAAS,qBACTlrB,MAAO,eAET,OAAU,mCACV,OAAU,iEACV,QAAW,qBACX,MAAS,CACPkrB,QAAS,gDACTC,YAAY,EACZnrB,MAAO,WAET,SAAY,CACVkrB,QAAS,aACTb,OAAQ,CACN0F,YAAa,QACb7C,SAAU,YAGd,YAAe,qCACf,SAAY,wCAEdhxB,EAAMmD,MAAMnC,IAAI,mBAAmB,SAAUiC,GAE3CjD,EAAMyB,UAAU,qBAAqByxB,kBAAkBjwB,EAAK,aADpC,6CAG1BjD,EAAMmD,MAAMnC,IAAI,kBAAkB,SAAUiC,GAC1CjD,EAAMyB,UAAU,qBAAqB8xB,qBAAqBtwB,EAAK,iBA9BnE,CAgCGjD,GAKHA,EAAMyB,UAAUmT,KAAO,CACrB,SAAY,CACVoa,QAAS,gCACTE,QAAQ,GAEV,OAAU,CACRF,QAAS,gCACTE,QAAQ,GAEV,QAAW,CACTF,QAAS,gCACTE,QAAQ,GAEV,OAAU,qCACV,YAAe,WACf,SAAY,IACZ,QAAW,qBACX,KAAQ,CACNF,QAAS,WACTlrB,MAAO,YAGX9D,EAAMyB,UAAUqyB,YAAc9zB,EAAMyB,UAAUmT,KAW9C5U,EAAMyB,UAAUsyB,KAAO/zB,EAAMyB,UAAUssB,OAAO,MAAO,CACnD,QAAW,CAAC,mBAAoB,CAC9BiB,QAAS,kBACTC,YAAY,IAEd,OAAU,CACRD,QAAS,0EACTb,OAAQ,CACN,YAAe,UAInB,SAAY,CACVa,QAAS,0GACTb,OAAQ,CAEN,SAAY,aAGhB,SAAY,2CACZ,SAAY,aAEdnuB,EAAMyB,UAAUysB,aAAa,OAAQ,WAAY,CAC/C,SAAY,CACZ,CACEc,QAAS,cACTb,OAAQ,CACN,YAAe,MAGnB,aACA,cAAe,CACba,QAAS,sCACTC,YAAY,EACZnrB,MAAO,cAKX9D,EAAMyB,UAAUuyB,SAAW,CACzB,QAAW,CACThF,QAAS,6CACTC,YAAY,GAEd,OAAU,CACRD,QAAS,iDACTE,QAAQ,GAGV,QAAW,gCAEX,OAAU,CACRF,QAAS,8CACTb,OAAQ,CACN,SAAY,wCAGhB,SAAY,wDACZ,QAAW,CACX,6HACA,CACEa,QAAS,wQACTC,YAAY,IAEd,SAAY,uBACZ,YAAe,YAIjB,SAAWjvB,GAET,IAAIi0B,EAAQ,6CAA6CzzB,OAYzD,SAAS0zB,EAAalF,GAIpB,OAHAA,EAAUA,EAAQr+B,QAAQ,YAAY,WACpC,OAAOsjC,KAEF3E,OAAO,0BAA0B9uB,OAAS,MAAQwuB,EAAU,KAGrE,IAAImF,EAAY,4DAA4D3zB,OACxE4zB,EAAW,+CAA+C5zB,OAAO7P,QAAQ,OAAO,WAClF,OAAOwjC,KAELE,EAAY,sEAAsE7zB,OACtFR,EAAMyB,UAAUsxB,SAAW/yB,EAAMyB,UAAUssB,OAAO,SAAU,IAC5D/tB,EAAMyB,UAAUysB,aAAa,WAAY,SAAU,CACjD,qBAAsB,CACpBc,QAAS,kDACTC,YAAY,EACZC,QAAQ,EACRf,OAAQ,CACN,YAAe,YACf,cAAe,CACba,QAAS,iBACTlrB,MAAO,CAAC,OAAQ,iBAChBqqB,OAAQnuB,EAAMyB,UAAU6yB,QAI9B,WAAc,CAEZtF,QAAS,kBACTlrB,MAAO,eAET,MAAS,CACPkrB,QAASM,OAAO,IAAM8E,EAAWC,EAAY,MAAQD,EAAW,KAAM,KACtEjG,OAAQ,CACN,kBAAmB,CACjBa,QAASM,OAAO,KAAO8E,EAAWC,EAAY,OAASD,EAAW,OAClEnF,YAAY,EACZd,OAAQ,CACN,aAAc,CACZa,QAASM,OAAO6E,GAChBhG,OAAQnuB,EAAMyB,UAAUsxB,UAE1B,YAAe,OAGnB,aAAc,CACZ/D,QAASM,OAAO,KAAO8E,EAAW,IAAMC,EAAY,KACpDpF,YAAY,EACZd,OAAQ,CACN,YAAe,iBAGnB,mBAAoB,CAClBa,QAASM,OAAO,IAAM8E,EAAW,KACjCjG,OAAQ,CACN,eAAgB,CACda,QAASM,OAAO6E,GAChBrwB,MAAO,YACPqqB,OAAQnuB,EAAMyB,UAAUsxB,UAE1B,YAAe,SAKvB,KAAQ,CAAC,CAEP/D,QAAS,uFACTC,YAAY,EACZnrB,MAAO,WACN,CAGDkrB,QAAS,sBACTlrB,MAAO,WACN,CAIDkrB,QAAS,qBACTE,QAAQ,EACRf,OAAQ,CACN,aAAc,CACZa,QAAS,qDACTC,YAAY,GAEd,gBAAiB,CACfD,QAAS,WACTC,YAAY,GAEd,YAAe,SAGnB,MAAS,CAAC,CAKRD,QAAS,0CACTlrB,MAAO,YACPqqB,OAAQ,CACN0F,YAAa,cAEd,CAGD7E,QAAS,aACTC,YAAY,EACZnrB,MAAO,YACPqqB,OAAQ,CACN0F,YAAa,aAGjB,GAAM,CAKJ7E,QAAS,wCACTC,YAAY,EACZnrB,MAAO,eAET,KAAQ,CAKNkrB,QAAS,mCACTC,YAAY,EACZnrB,MAAO,eAET,gBAAiB,CAKfkrB,QAAS,qHACTb,OAAQ,CACN,SAAY,CACVa,QAAS,gBACTC,YAAY,GAEd,OAAU,+DACV,YAAe,kBAEjBnrB,MAAO,OAET,KAAQ,CAINkrB,QAASkF,EAAa,kGAAkG1zB,QACxHyuB,YAAY,EACZC,QAAQ,EACRf,OAAQ,CACN,QAAW,CACTa,QAAS,sBACTC,YAAY,EACZd,OAAQ,IAGV,YAAe,YAGnB,OAAU,CAIRa,QAASkF,EAAa,kGAAkG1zB,QACxHyuB,YAAY,EACZC,QAAQ,EACRf,OAAQ,CACN,QAAW,CACTa,QAAS,oBACTC,YAAY,EACZd,OAAQ,IAGV,YAAe,SAGnB,OAAU,CAGRa,QAASkF,EAAa,4BAA4B1zB,QAClDyuB,YAAY,EACZC,QAAQ,EACRf,OAAQ,CACN,QAAW,CACTa,QAAS,uBACTC,YAAY,EACZd,OAAQ,IAGV,YAAe,QAGnB,IAAO,CAILa,QAASkF,EAAa,mGAAmG1zB,QACzHyuB,YAAY,EACZC,QAAQ,EACRf,OAAQ,CACN,SAAY,KACZ,QAAW,CACTa,QAAS,oBACTC,YAAY,EACZd,OAAQ,IAGV,SAAY,CACVa,QAAS,6BACTC,YAAY,GAEd,IAAO,CACLD,QAAS,iBACTC,YAAY,GAEd,OAAU,CACRD,QAAS,oCACTC,YAAY,OAKpB,CAAC,MAAO,OAAQ,SAAU,UAAU14B,SAAQ,SAAUqM,GACpD,CAAC,MAAO,OAAQ,SAAU,UAAUrM,SAAQ,SAAU43B,GAChDvrB,IAAUurB,IACZnuB,EAAMyB,UAAUsxB,SAASnwB,GAAOurB,OAAOttB,QAAQstB,OAAOA,GAAUnuB,EAAMyB,UAAUsxB,SAAS5E,UAI/FnuB,EAAMmD,MAAMnC,IAAI,kBAAkB,SAAUiC,GACrB,aAAjBA,EAAI9B,UAA4C,OAAjB8B,EAAI9B,UAIvC,SAAS8wB,EAAW/uB,GAClB,GAAKA,GAA4B,iBAAXA,EAItB,IAAK,IAAIvF,EAAI,EAAGsY,EAAI/S,EAAOjH,OAAQ0B,EAAIsY,EAAGtY,IAAK,CAC7C,IAAIiF,EAAQM,EAAOvF,GAEnB,GAAmB,SAAfiF,EAAM9G,KAAV,CAmBA,IAAIy4B,EAAW3xB,EAAM/B,QAAQ,GACzB2zB,EAAY5xB,EAAM/B,QAAQ,GAE9B,GAAI0zB,GAAYC,GAA+B,kBAAlBD,EAASz4B,MAA+C,eAAnB04B,EAAU14B,MAAqD,iBAArBy4B,EAAS1zB,QAAsB,CAGzI,IAAIotB,EAAOsG,EAAS1zB,QAAQlQ,QAAQ,OAAQ,SAASA,QAAQ,UAAW,MAGpEmT,EAAQ,aADZmqB,GAAQ,eAAetX,KAAKsX,IAAS,CAAC,KAAK,GAAGnR,eAGzC0X,EAAU1wB,MAEuB,iBAApB0wB,EAAU1wB,MAC1B0wB,EAAU1wB,MAAQ,CAAC0wB,EAAU1wB,MAAOA,GAEpC0wB,EAAU1wB,MAAMlT,KAAKkT,GAJrB0wB,EAAU1wB,MAAQ,CAACA,SA9BrBmuB,EAAWrvB,EAAM/B,UAwCvBoxB,CAAWhvB,EAAIC,WAEjBlD,EAAMmD,MAAMnC,IAAI,QAAQ,SAAUiC,GAChC,GAAiB,eAAbA,EAAInH,KAAR,CAMA,IAFA,IAAIy4B,EAAW,GAEN52B,EAAI,EAAGsY,EAAIhT,EAAI6sB,QAAQ7zB,OAAQ0B,EAAIsY,EAAGtY,IAAK,CAClD,IAAIsrB,EAAMhmB,EAAI6sB,QAAQnyB,GAClB8X,EAAQ,gBAAgBkB,KAAKsS,GAEjC,GAAIxT,EAAO,CACT8e,EAAW9e,EAAM,GACjB,OAIJ,IAAIzS,EAAUhD,EAAMyB,UAAU8yB,GAE9B,GAAKvxB,EAYE,CAEL,IAAID,EAAOE,EAAIpC,QAAQlQ,QAAQ,QAAS,KAAKA,QAAQ,SAAU,KAC/DsS,EAAIpC,QAAUb,EAAMyuB,UAAU1rB,EAAMC,EAASuxB,QAd7C,GAAIA,GAAyB,SAAbA,GAAuBv0B,EAAMwuB,QAAQiG,WAAY,CAC/D,IAAI/T,EAAK,OAAQ,IAAIlV,MAAOkpB,UAAY,IAAMre,KAAKse,MAAsB,KAAhBte,KAAKue,UAC9D3xB,EAAI8sB,WAAe,GAAIrP,EACvB1gB,EAAMwuB,QAAQiG,WAAWI,cAAcN,GAAU,WAC/C,IAAIO,EAAMnsB,SAASyK,eAAesN,GAE9BoU,IACFA,EAAIC,UAAY/0B,EAAMyuB,UAAUqG,EAAIE,YAAah1B,EAAMyB,UAAU8yB,GAAWA,YAUtFv0B,EAAMyB,UAAUwzB,GAAKj1B,EAAMyB,UAAUsxB,SAtVvC,CAuVG/yB,GAIHA,EAAMyB,UAAUyzB,WAAal1B,EAAMyB,UAAUssB,OAAO,IAAK,CACvD,OAAU,qFACV,QAAW,wYACX,SAAY,iEAEP/tB,EAAMyB,UAAUyzB,WAAW,cAClCl1B,EAAMyB,UAAU0zB,KAAOn1B,EAAMyB,UAAUyzB,WAGvCl1B,EAAMyB,UAAU2zB,MAAQ,CACtB,QAAW,mBACX,OAAU,CAAC,CACTpG,QAAS,wBACTE,QAAQ,GACP,CACDF,QAAS,qDACTE,QAAQ,IAEV,OAAU,6EACV,UAAa,CACXF,QAAS,SACTlrB,MAAO,aAET,MAAS,CACPkrB,QAAS,SACTlrB,MAAO,YAET,gBAAiB,CACfkrB,QAAS,SACTlrB,MAAO,YAET,QAAW,CACTkrB,QAAS,OACTlrB,MAAO,YAET,OAAU,CACRkrB,QAAS,aACTlrB,MAAO,YAIT,QAAW,gSACX,QAAW,qBAEX,SAAY,8FACZ,YAAe,yBAIjB9D,EAAMyB,UAAU4zB,OAAS,CACvB,QAAW,CACTrG,QAAS,eACTC,YAAY,GAEd,uBAAwB,CACtBD,QAAS,sEACTE,QAAQ,EACRf,OAAQ,CACN,cAAiB,CAEfa,QAAS,2EACTC,YAAY,EACZd,OAAQ,CACN,cAAe,CACba,QAAS,qBACTC,YAAY,GAEd,oBAAqB,CACnBD,QAAS,kBACTlrB,MAAO,eAETxM,KAAM,OAGV,OAAU,YAGd,uBAAwB,CACtB03B,QAAS,uCACTE,QAAQ,EACRprB,MAAO,UAET,OAAU,CACRkrB,QAAS,mDACTE,QAAQ,GAEV,SAAY,CACVF,QAAS,4CACTC,YAAY,GAEd,aAAc,CACZD,QAAS,mBACTC,YAAY,GAEd,UAAa,CACXD,QAAS,yBACTC,YAAY,EACZnrB,MAAO,CAAC,aAAc,eACtBqqB,OAAQ,CACN,YAAe,OAGnB,QAAW,mMACX,QAAW,shBACX,QAAW,0BACX,OAAU,iGACV,SAAY,oDACZ,YAAe,iBAEjBnuB,EAAMyB,UAAU4zB,OAAO,wBAAwBlH,OAAsB,cAAEA,OAAO72B,KAAO0I,EAAMyB,UAAU4zB,OACrGr1B,EAAMyB,UAAU6zB,GAAKt1B,EAAMyB,UAAU4zB,OAGrCr1B,EAAMyB,UAAU8zB,OAASv1B,EAAMyB,UAAUssB,OAAO,QAAS,CACvD,OAAU,CACRiB,QAAS,sCACTE,QAAQ,GAGV,aAAc,aACd,QAAW,4RACX,SAAY,wGAEdlvB,EAAMyB,UAAUysB,aAAa,SAAU,aAAc,CACnD,UAAa,CACXc,QAAS,gEACTlrB,MAAO,UAET,YAAe,CAEbkrB,QAAS,wBACTlrB,MAAO,YAET,MAAS,CACPkrB,QAAS,mBACTlrB,MAAO,mBAIJ9D,EAAMyB,UAAU8zB,OAAOC,SAG9B,SAAWx1B,GACTA,EAAMyB,UAAUg0B,KAAOz1B,EAAMyB,UAAUssB,OAAO,MAAO,CAEnD,QAAW,CACTiB,QAAS,gDACTC,YAAY,KAGhBjvB,EAAMyB,UAAUysB,aAAa,OAAQ,SAAU,CAE7C,cAAe,CAEbc,QAAS,sBACTb,OAAQ,CACN,OAAU,+BAITnuB,EAAMyB,UAAUg0B,KAAKC,OAC5B,IAAI1E,EAAW,yBACX2E,EAAW,CAAC,2CAA4C,CAC1D3G,QAAS,eACTC,YAAY,IAEdjvB,EAAMyB,UAAUysB,aAAa,OAAQ,WAAY,CAE/C,gBAAiB,CACfc,QAAS,eACTb,OAAQ,CACN,YAAe,IACf,SAAY6C,EACZ,SAAY2E,IAIhB,gBAAiB,CACf3G,QAAS,qCACTb,OAAQ,CACN,SAAY,CAAC,kBAAmB,CAC9Ba,QAAS,aACTC,YAAY,IAEd,YAAe,IACf,SAAY+B,EACZ,SAAY2E,EACZ,UAAa31B,EAAMyB,UAAUg0B,KAAKG,qBAIjC51B,EAAMyB,UAAUg0B,KAAK/Y,gBACrB1c,EAAMyB,UAAUg0B,KAAKG,UAG5B51B,EAAMyB,UAAUysB,aAAa,OAAQ,cAAe,CAClD,SAAY,CACVc,QAAS,uHACTC,YAAY,KAxDlB,CA2DGjvB,GAIHA,EAAMyB,UAAUo0B,KAAO71B,EAAMyB,UAAUssB,OAAO,MAAO,CACnD,QAAW,CACTiB,QAAS,uCACTC,YAAY,GAEd,OAAU,CACRD,QAAS,sDACTb,OAAQ,CACN,KAAQ,YAKZ,IAAO,0BAQP,SAAY,CAEVa,QAAS,mGACTb,OAAQ,CACN,OAAU,CACRa,QAAS,IACTlrB,MAAO,aAET,YAAe,UACf,SAAY,2BAGhB,SAAY,CACVkrB,QAAS,2CACTb,OAAQ,CACN,SAAY,6BAIlBnuB,EAAMyB,UAAUysB,aAAa,OAAQ,SAAU,CAC7C,QAAW,CAAC,oHAAqH,CAC/Hc,QAAS,4BACTC,YAAY,MAGhBjvB,EAAMyB,UAAUysB,aAAa,OAAQ,YAAa,CAEhD,SAAY,2BAEdluB,EAAMyB,UAAUysB,aAAa,OAAQ,WAAY,CAC/C,kBAAmB,CACjBc,QAAS,6BACTlrB,MAAO,WAET,YAAe,CACbkrB,QAAS,UACTlrB,MAAO,YAET,UAAa,CACXkrB,QAAS,6BACTlrB,MAAO,WAET,QAAW,qBACX,KAAQ,CACNkrB,QAAS,WACTlrB,MAAO,WAET,SAAY,CACVkrB,QAAS,kDACTC,YAAY,KAGhBjvB,EAAMyB,UAAUo0B,KAAa,OAAE1H,OAAO72B,KAAO0I,EAAMyB,UAAUo0B,KAG7D71B,EAAMyB,UAAUq0B,IAAM,CACpB,QAAW,CACT9G,QAAS,gDACTC,YAAY,GAEd,SAAY,CAAC,CACXD,QAAS,sCACTE,QAAQ,GACP,YACH,OAAU,CACRF,QAAS,kDACTE,QAAQ,EACRD,YAAY,GAEd,SAAY,4FAEZ,QAAW,u9EACX,QAAW,2BACX,OAAU,4CACV,SAAY,yHACZ,YAAe,eAIjB,SAAWjvB,GACT,IAAI0xB,EAAO,CACT1C,QAAS,sBACTC,YAAY,GAGV0C,EAAS,CACX3C,QAAS,uCACTC,YAAY,GAEVd,EAAS,CACX,QAAW,CACTa,QAAS,uCACTC,YAAY,GAEd,IAAO,CACLD,QAAS,uBACTE,QAAQ,GAEV,OAAU,CACRF,QAAS,gDACTE,QAAQ,GAEV,cAAiB,KAEjB,KAAQ,KAER,UAAa,+BACb,QAAW,CACTF,QAAS,4DACTC,YAAY,GAEd,QAAW,iBACX,MAAS,CAAC,q5CAAs5C,CAC95CD,QAAS,4JACTb,OAAQ,CACN,KAAQuD,EACR,OAAUC,EACV,SAAY,eACZ,YAAe,WAGnB,OAAU,kBACV,KAAQD,EACR,QAAW,qBACX,SAAY,CAEZ,wGACA,OAAUC,EACV,YAAe,iBAEjBxD,EAAsB,cAAI,CACxBa,QAAS,iBACTlrB,MAAO,WACPqqB,OAAQ,CACN,UAAa,CACXa,QAAS,QACTlrB,MAAO,eAETxM,KAAM62B,IAGVA,EAAa,KAAI,CACfa,QAAS,oBACTb,OAAQ,CACN,SAAY,SACZ72B,KAAM62B,IAGVnuB,EAAMyB,UAAUs0B,OAAS,CACvB,qBAAsB,CACpB/G,QAAS,aACTC,YAAY,EACZd,OAAQ,CACN,OAAU,WACV72B,KAAM62B,IAGV,uBAAwB,CACtBa,QAAS,qDACTC,YAAY,EACZd,OAAQ,CACN,SAAY,OACZ72B,KAAM62B,IAGV,UAAa,CACXa,QAAS,iDACTC,YAAY,EACZd,OAAQ,CACN,QAAW,OACX72B,KAAM62B,IAKV,uBAAwB,CACtBa,QAAS,kIACTC,YAAY,EACZd,OAAQ,CACN,SAAY,CACVa,QAAS,WACTb,OAAQ,CACN,cAAiBA,EAAO7Q,gBAG5BhmB,KAAM62B,IAMV,SAAY,CACVa,QAAS,yOACTC,YAAY,EACZd,OAAQ,CACN,cAAiBA,EAAO7Q,cACxB,QAAW6Q,EAAOqE,QAClB,YAAe,UAGnB,KAAQrE,EAAO31B,KACf,OAAU21B,EAAOv7B,OACjB,QAAW,CACTo8B,QAAS,uCACTC,YAAY,EACZC,QAAQ,GAEV,cAAiBf,EAAO7Q,cACxB,YAAe,iBAjInB,CAmIGtd,GAIH,SAAWA,GACTA,EAAMyB,UAAUu0B,WAAah2B,EAAMyB,UAAUssB,OAAO,aAAc,CAChE,aAAc,CACZiB,QAAS,+KACTC,YAAY,EACZC,QAAQ,EACRf,OAAQ,MAIV,QAAW,6ZACX,QAAW,iGAGNnuB,EAAMyB,UAAUu0B,WAAsB,UAE7C,IAAIC,EAAaj2B,EAAMyB,UAAUssB,OAAO,aAAc,WAC/CkI,EAAW,cAClBj2B,EAAMyB,UAAUu0B,WAAW,cAAc7H,OAAS8H,EAClDj2B,EAAMyB,UAAUysB,aAAa,aAAc,WAAY,CACrD,mBAAoB,CAElBc,QAAS,yGACTE,QAAQ,EACRf,OAAQ,CACN,SAAY,4DACZ,QAAW,CACTa,QAAS,WAETlrB,MAAO,aACPqqB,OAAQ8H,OAKhBj2B,EAAMyB,UAAUy0B,GAAKl2B,EAAMyB,UAAUu0B,WAnCvC,CAoCGh2B,GAIH,SAAWA,GACT,IAAIg2B,EAAah2B,EAAMytB,KAAKG,MAAM5tB,EAAMyB,UAAUu0B,YAClDh2B,EAAMyB,UAAU00B,IAAMn2B,EAAMyB,UAAUssB,OAAO,MAAOiI,GAIpD,IAAInG,EAAM7vB,EAAMyB,UAAU00B,IAAItG,IAC9BA,EAAIb,QAAUM,OAAO,qBAAqB9uB,OAAS,MAAQqvB,EAAIb,QAAQxuB,OAAS,IAAKqvB,EAAIb,QAAQK,OACjGQ,EAAIZ,YAAa,EARnB,CASGjvB,GAIHA,EAAMyB,UAAU20B,KAAO,CACrB,QAAW,CAAC,iBAAkB,CAC5BpH,QAAS,OACTE,QAAQ,IAEV,OAAU,CACRF,QAAS,yBACTE,QAAQ,GAEV,QAAW,CAAC,CACVF,QAAS,sBACTb,OAAQ,CACN,SAAY,MAEb,CACDa,QAAS,ibACTb,OAAQ,CACN,YAAe,OAEhB,4QACH,SAAY,oCACZ,OAAU,kNACV,YAAe,QAIjB,SAAWnuB,GAGT,IAAIq2B,EAAgB,mBAEhBxG,EAAM,mFAENyG,EAAa,MAAQzG,EAAIrvB,OAAS,YAAc61B,EAAc71B,OAAS,MAAQ61B,EAAc71B,OAAS,YAAcqvB,EAAIrvB,OAAS,MAIjI+1B,EAAW,kJAAkJ/1B,OAAO7P,QAAQ,YAAY,WAC1L,MAAO,2EAA2E6P,UAEhF5N,EAAS,8CAA8C4N,OAQ3D,SAASg2B,EAAmB98B,EAAO21B,GACjCA,GAASA,GAAS,IAAI1+B,QAAQ,KAAM,IAAM,IAE1C,IAAIq+B,EAAU,uFAAuFxuB,OAAO7P,QAAQ,aAAa,WAC/H,OAAO2lC,KACN3lC,QAAQ,cAAc,WACvB,OAAO+I,KAET,OAAO41B,OAAON,EAASK,GAGzBrvB,EAAMyB,UAAU6yB,KAAO,CACrB,OAAU,CACRtF,QAASM,OAAO,6FAA6F9uB,OAAO7P,QAAQ,aAAa,WACvI,OAAO2lC,MAETrH,YAAY,EACZnrB,MAAO,UAET,QAAW,MACX,IAAO,CACLkrB,QAASM,OAAO,kEAAkE9uB,OAAO7P,QAAQ,aAAa,WAC5G,OAAO2lC,KACN3lC,QAAQ,YAAY,WACrB,MAAO,MAAQ4lC,EAAW,IAAM3jC,EAAS,QAE3Cq8B,YAAY,EACZC,QAAQ,EACRprB,MAAO,UAET,UAAa,CACXkrB,QAAS,gBACTC,YAAY,EACZnrB,MAAO,aAET,SAAY,CACVkrB,QAASwH,EAAmB,sJAAsJh2B,QAClLyuB,YAAY,EACZnrB,MAAO,UAET,QAAW,CACTkrB,QAASwH,EAAmB,aAAah2B,OAAQ,KACjDyuB,YAAY,EACZnrB,MAAO,aAET,KAAQ,CACNkrB,QAASwH,EAAmB,SAASh2B,OAAQ,KAC7CyuB,YAAY,EACZnrB,MAAO,aAET,OAAU,CACRkrB,QAASwH,EAAmB5jC,GAC5Bq8B,YAAY,EACZC,QAAQ,GAEV,OAAU,CACRF,QAASwH,EAAmB,kFAAkFh2B,OAAQ,KACtHyuB,YAAY,GAEd,IAAOY,EACP,UAAawG,EACb,YAAe,6BAEjBr2B,EAAMyB,UAAUg1B,IAAMz2B,EAAMyB,UAAU6yB,KArFxC,CAsFGt0B,GAEY,O,mBCtvFf,SAAS02B,EAAgB5oB,EAAGwR,GAO1B,OANA9kB,EAAOpK,QAAUsmC,EAAkB57B,OAAO6T,gBAAkB,SAAyBb,EAAGwR,GAEtF,OADAxR,EAAExK,UAAYgc,EACPxR,GAGTtT,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,EACjEqmC,EAAgB5oB,EAAGwR,GAG5B9kB,EAAOpK,QAAUsmC,EACjBl8B,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,qBCXxED,EAAQC,YAAa,EACrBD,EAAQumC,YAAS94B,EAEjB,IAAIyC,EAAWxF,OAAOyF,QAAU,SAAU9J,GACxC,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CACzC,IAAI6C,EAASpE,UAAUuB,GAEvB,IAAK,IAAIpE,KAAOiH,EACV1F,OAAOjG,UAAUwB,eAAe1C,KAAK6M,EAAQjH,KAC/C9C,EAAO8C,GAAOiH,EAAOjH,IAK3B,OAAO9C,GAGLmgC,EAAe,WACjB,SAASrwB,EAAiB9P,EAAQvD,GAChC,IAAK,IAAIyK,EAAI,EAAGA,EAAIzK,EAAM+I,OAAQ0B,IAAK,CACrC,IAAIC,EAAa1K,EAAMyK,GACvBC,EAAWuC,WAAavC,EAAWuC,aAAc,EACjDvC,EAAWwC,cAAe,EACtB,UAAWxC,IAAYA,EAAWyC,UAAW,GACjDvF,OAAOC,eAAetE,EAAQmH,EAAWrE,IAAKqE,IAIlD,OAAO,SAAU0Q,EAAauoB,EAAYC,GAGxC,OAFID,GAAYtwB,EAAiB+H,EAAYzZ,UAAWgiC,GACpDC,GAAavwB,EAAiB+H,EAAawoB,GACxCxoB,GAdQ,GAoBfyoB,EAAU7mC,EAFD,EAAQ,SAMjB8mC,EAAc9mC,EAFD,EAAQ,SAMrB+mC,EAAoB/mC,EAFD,EAAQ,SAM3BgnC,EAAqBhnC,EAFD,EAAQ,SAI5BinC,EAAe,EAAQ,QAEvBC,EAAmB,EAAQ,QAE/B,SAASlnC,EAAuBuK,GAC9B,OAAOA,GAAOA,EAAIpK,WAAaoK,EAAM,CACnC3J,QAAS2J,GAIb,SAAS+L,EAAyB/L,EAAK8C,GACrC,IAAI9G,EAAS,GAEb,IAAK,IAAIkH,KAAKlD,EACR8C,EAAKyE,QAAQrE,IAAM,GAClB7C,OAAOjG,UAAUwB,eAAe1C,KAAK8G,EAAKkD,KAC/ClH,EAAOkH,GAAKlD,EAAIkD,IAGlB,OAAOlH,EAGT,SAAS4X,EAAgBxY,EAAUyY,GACjC,KAAMzY,aAAoByY,GACxB,MAAM,IAAIV,UAAU,qCAIxB,SAASW,EAA2BC,EAAM7a,GACxC,IAAK6a,EACH,MAAM,IAAIC,eAAe,6DAG3B,OAAO9a,GAAyB,iBAATA,GAAqC,mBAATA,EAA8B6a,EAAP7a,EAmB5E,IAA6B2E,EACvBuX,EAAQC,EAoPVunB,GAAoB,EAAIJ,EAAkBnmC,SAASqmC,EAAavuB,mBAAoBuuB,EAAaG,wBAAyBH,EAAaruB,iBAAnH,EAJJ,WAClB,OAAO,QAILyuB,GAtPyBj/B,EAsPH++B,EAnPjBvnB,EAAQD,EAAS,SAAUpc,GAGhC,SAAS+jC,IAGP,OAFAnpB,EAAgBza,KAAM4jC,GAEfjpB,EAA2B3a,KAAMH,EAAiBgN,MAAM7M,KAAMwI,YA2LvE,OApNJ,SAAmBiN,EAAUC,GAC3B,GAA0B,mBAAfA,GAA4C,OAAfA,EACtC,MAAM,IAAIsE,UAAU,kEAAoEtE,GAG1FD,EAASxU,UAAYiG,OAAOsG,OAAOkI,GAAcA,EAAWzU,UAAW,CACrE0O,YAAa,CACX7J,MAAO2P,EACPlJ,YAAY,EACZE,UAAU,EACVD,cAAc,KAGdkJ,IAAYxO,OAAO6T,eAAiB7T,OAAO6T,eAAetF,EAAUC,GAAcD,EAAS/F,UAAYgG,GAOzGoF,CAAU8oB,EAAe/jC,GAQzB+jC,EAAc3iC,UAAU6U,sBAAwB,SAA+BC,GAC7E,QAAQ,EAAIutB,EAAmBpmC,SAAS8C,KAAKV,MAAOyW,IAGtD6tB,EAAc3iC,UAAU4iC,yBAA2B,SAAkCC,EAAOC,GAC1F,IAAKA,EACH,OAAO,KAGT,OAAQD,EAAM57B,MACZ,KAAKs7B,EAAiBQ,UAAUC,OAChC,KAAKT,EAAiBQ,UAAUE,SAC9B,MAAO,CACL/C,UAAW4C,GAGf,KAAKP,EAAiBQ,UAAUG,MAC9B,MAAO,CACLC,QAASL,GAIf,MAAM,IAAI5uB,MAAM,IAAM2uB,EAAM57B,KAAO,uGAGrC07B,EAAc3iC,UAAUojC,yBAA2B,SAAkCrmC,GACnF,IAAIV,EAEAwmC,EAAQ9lC,EAAK8lC,MACbQ,EAAoBtmC,EAAKsmC,kBACzBC,EAAgBvmC,EAAKumC,cACrBR,EAAiB/lC,EAAK+lC,eAC1B,OAAOr3B,EAAS,GAAI43B,IAAoBhnC,EAAY,IAAcwmC,EAAM57B,MAAQ,GAAG0B,OAAO06B,EAAkBR,EAAM57B,OAAS,GAAI,CAACwE,EAAS,GAAI63B,EAAevkC,KAAK6jC,yBAAyBC,EAAOC,MAAoBzmC,KAGvNsmC,EAAc3iC,UAAUujC,sBAAwB,SAA+B/kC,GAC7E,IAAIglC,EAAWC,EAEXZ,EAAQrkC,EAAMqkC,MACdtvB,EAAW/U,EAAM+U,SACjB+vB,EAAgB9kC,EAAM8kC,cACtBR,EAAiBtkC,EAAMskC,eAE3B,OAAQD,EAAM57B,MACZ,KAAKs7B,EAAiBQ,UAAUW,MAC9B,OAAOj4B,EAAS,GAAI8H,IAAWiwB,EAAY,IAAcX,EAAM57B,MAAQ67B,EAAgBU,EAAUG,gBAAkBl4B,EAAS,GAAI63B,GAAgBE,IAElJ,KAAKjB,EAAiBQ,UAAUa,KAC9B,OAAOn4B,EAAS,GAAI8H,EAAU,CAC5BswB,eAAgBp4B,EAAS,GAAI63B,KAGjC,KAAKf,EAAiBQ,UAAUe,KAC9B,OAAOr4B,EAAS,GAAI8H,EAAU,CAC5BwwB,eAAgBt4B,EAAS,GAAI63B,KAInC,OAAO73B,EAAS,GAAI8H,IAAWkwB,EAAY,IAAcZ,EAAM57B,MAAQwE,EAAS,GAAI63B,GAAgBG,KAGtGd,EAAc3iC,UAAUgkC,4BAA8B,SAAqCX,EAAmB9vB,GAC5G,IAAI0wB,EAAoBx4B,EAAS,GAAI8H,GAOrC,OALAtN,OAAOyC,KAAK26B,GAAmB3hC,SAAQ,SAAUwiC,GAC/C,IAAIC,EAEJF,EAAoBx4B,EAAS,GAAIw4B,IAAoBE,EAAY,IAAcD,GAAkBb,EAAkBa,GAAiBC,OAE/HF,GAGTtB,EAAc3iC,UAAUokC,sBAAwB,SAA+BvB,EAAOC,GAmBpF,OAAO,GAGTH,EAAc3iC,UAAUqkC,mBAAqB,SAA4Br2B,EAAUuF,GACjF,IAAIjS,EAASvC,KAETskC,EAAoB,GAyCxB,OAvCAnB,EAAQjmC,QAAQmhB,SAAS1b,QAAQsM,GAAU,SAAU60B,GACnD,GAAKA,GAAUA,EAAMxkC,MAArB,CAIA,IAAIimC,EAAezB,EAAMxkC,MACrBykC,EAAiBwB,EAAat2B,SAC9Bu2B,EAAa5yB,EAAyB2yB,EAAc,CAAC,aAErDhB,GAAgB,EAAIhB,EAAakC,mCAAmCD,GAIxE,OAFAjjC,EAAO8iC,sBAAsBvB,EAAOC,GAE5BD,EAAM57B,MACZ,KAAKs7B,EAAiBQ,UAAU0B,KAChC,KAAKlC,EAAiBQ,UAAU2B,KAChC,KAAKnC,EAAiBQ,UAAUE,SAChC,KAAKV,EAAiBQ,UAAUC,OAChC,KAAKT,EAAiBQ,UAAUG,MAC9BG,EAAoB/hC,EAAO8hC,yBAAyB,CAClDP,MAAOA,EACPQ,kBAAmBA,EACnBC,cAAeA,EACfR,eAAgBA,IAElB,MAEF,QACEvvB,EAAWjS,EAAOiiC,sBAAsB,CACtCV,MAAOA,EACPtvB,SAAUA,EACV+vB,cAAeA,EACfR,eAAgBA,SAMxBvvB,EAAWxU,KAAKilC,4BAA4BX,EAAmB9vB,IAIjEovB,EAAc3iC,UAAUgC,OAAS,WAC/B,IAAI2iC,EAAS5lC,KAAKV,MACd2P,EAAW22B,EAAO32B,SAClB3P,EAAQsT,EAAyBgzB,EAAQ,CAAC,aAE1CpxB,EAAW9H,EAAS,GAAIpN,GAM5B,OAJI2P,IACFuF,EAAWxU,KAAKslC,mBAAmBr2B,EAAUuF,IAGxC2uB,EAAQjmC,QAAQqC,cAAcmF,EAAW8P,IAGlDwuB,EAAaY,EAAe,KAAM,CAAC,CACjCj+B,IAAK,YAuBL2B,IAAK,SAAawN,GAChBpQ,EAAUoQ,UAAYA,MAInB8uB,EAjMe,CAkMtBT,EAAQjmC,QAAQwH,WAAYuX,EAAOtX,UAAY,CAC/CvG,KAAMglC,EAAYlmC,QAAQgC,OAC1B4lC,eAAgB1B,EAAYlmC,QAAQgC,OACpC+P,SAAUm0B,EAAYlmC,QAAQ2oC,UAAU,CAACzC,EAAYlmC,QAAQ4oC,QAAQ1C,EAAYlmC,QAAQqiB,MAAO6jB,EAAYlmC,QAAQqiB,OACpHwmB,aAAc3C,EAAYlmC,QAAQ8B,OAClCgnC,MAAO5C,EAAYlmC,QAAQkC,KAC3B6mC,wBAAyB7C,EAAYlmC,QAAQkC,KAC7C4lC,eAAgB5B,EAAYlmC,QAAQgC,OACpCstB,KAAM4W,EAAYlmC,QAAQ4oC,QAAQ1C,EAAYlmC,QAAQgC,QACtDgnC,KAAM9C,EAAYlmC,QAAQ4oC,QAAQ1C,EAAYlmC,QAAQgC,QACtDinC,SAAU/C,EAAYlmC,QAAQ4oC,QAAQ1C,EAAYlmC,QAAQgC,QAC1DknC,oBAAqBhD,EAAYlmC,QAAQ0H,KACzCyhC,OAAQjD,EAAYlmC,QAAQ4oC,QAAQ1C,EAAYlmC,QAAQgC,QACxDuB,MAAO2iC,EAAYlmC,QAAQ4oC,QAAQ1C,EAAYlmC,QAAQgC,QACvD8vB,MAAOoU,EAAYlmC,QAAQ8B,OAC3B4lC,gBAAiBxB,EAAYlmC,QAAQgC,OACrConC,cAAelD,EAAYlmC,QAAQ8B,QAClCid,EAAOrU,aAAe,CACvBo+B,OAAO,EACPC,yBAAyB,GACxBhqB,EAAOtG,KAAOjR,EAAUiR,KAAMsG,EAAOrG,OAAS,WAC/C,IAAI2wB,EAAc7hC,EAAUkR,SAmB5B,OAjBK2wB,IAEHA,GAAc,EAAIhD,EAAaruB,kBAAkB,CAC/CsxB,QAAS,GACT1B,eAAgB,GAChBmB,yBAAyB,EACzBjB,eAAgB,GAChByB,SAAU,GACVC,SAAU,GACVC,aAAc,GACdC,WAAY,GACZC,UAAW,GACX7X,MAAO,GACP4V,gBAAiB,MAId2B,GACNrqB,GASLynB,EAAamD,aAAenD,EAAa/tB,OACzCpZ,EAAQumC,OAASY,EACjBnnC,EAAQU,QAAUymC,G,kCC7VhB/8B,EAAOpK,QAAU,EAAQ,S,mBCG3BoK,EAAOpK,QANP,SAAgCqK,GAC9B,OAAOA,GAAOA,EAAIpK,WAAaoK,EAAM,CACnC,QAAWA,IAKfD,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,kDC8lBzD,MArmBf,SAAoBsqC,GAiUlB,SAASC,EAAErY,EAAG6O,EAAG35B,GACf,IAAI6kB,EAAI8U,EAAEyJ,OAAOv8B,MAAMw8B,GACvB1J,EAAI9U,EACJ,IAAI/D,EAAI+D,EAAErgB,OACN8+B,EAAIxY,EAAEtmB,OAEV,OAAQ8+B,GACN,KAAK,EACL,KAAK,EACH,IAAIviB,EAAI,EAER,IAAK+J,EAAI,IAAMwY,EAAI,GAAKxY,EAAE,GAAK,IAAK/J,EAAID,IAAKC,EAC3C4Y,EAAE5Y,GAAKwiB,EAAEzY,EAAG6O,EAAE5Y,GAAI/gB,GAAGojC,OAGvB,MAEF,QACE,IAAI/M,EAAItV,EAAI,EAEZ,IAAK4Y,EAAI,GAAI5Y,EAAID,IAAKC,EACpB,IAAK,IAAIxK,EAAI,EAAGA,EAAI+sB,IAAK/sB,EACvBojB,EAAEtD,KAAOkN,EAAEzY,EAAEvU,GAAK,IAAKsO,EAAE9D,GAAI/gB,GAAGojC,OAMxC,OAAOzJ,EAGT,SAAS4J,EAAEzY,EAAG6O,EAAG35B,GACf,IAAI6kB,EAAI8U,EAAEnkB,WAAW,GAGrB,OAFA,GAAKqP,IAAMA,GAAK8U,EAAIA,EAAEyJ,QAAQ5tB,WAAW,IAEjCqP,GACN,KAAK,GACH,OAAO8U,EAAEzgC,QAAQsqC,EAAG,KAAO1Y,EAAEsY,QAE/B,KAAK,GACH,OAAOtY,EAAEsY,OAASzJ,EAAEzgC,QAAQsqC,EAAG,KAAO1Y,EAAEsY,QAE1C,QACE,GAAI,EAAI,EAAIpjC,GAAK,EAAI25B,EAAEpvB,QAAQ,MAAO,OAAOovB,EAAEzgC,QAAQsqC,GAAI,KAAO1Y,EAAEtV,WAAW,GAAK,GAAK,MAAQsV,EAAEsY,QAGvG,OAAOtY,EAAI6O,EAGb,SAAS8J,EAAE3Y,EAAG6O,EAAG35B,EAAG6kB,GAClB,IAAI/D,EAAIgK,EAAI,IACRwY,EAAI,EAAI3J,EAAI,EAAI35B,EAAI,EAAI6kB,EAE5B,GAAI,MAAQye,EAAG,CACbxY,EAAIhK,EAAEvW,QAAQ,IAAK,GAAK,EACxB,IAAIwW,EAAID,EAAElF,UAAUkP,EAAGhK,EAAEtc,OAAS,GAAG4+B,OAErC,OADAriB,EAAID,EAAElF,UAAU,EAAGkP,GAAGsY,OAASriB,EAAI,IAC5B,IAAM2iB,GAAK,IAAMA,GAAKC,EAAE5iB,EAAG,GAAK,WAAaA,EAAIA,EAAIA,EAG9D,GAAI,IAAM2iB,GAAK,IAAMA,IAAMC,EAAE7iB,EAAG,GAAI,OAAOA,EAE3C,OAAQwiB,GACN,KAAK,KACH,OAAO,KAAOxiB,EAAEtL,WAAW,IAAM,WAAasL,EAAIA,EAAIA,EAExD,KAAK,IACH,OAAO,MAAQA,EAAEtL,WAAW,GAAK,WAAasL,EAAIA,EAAIA,EAExD,KAAK,IACH,OAAO,MAAQA,EAAEtL,WAAW,GAAK,WAAasL,EAAIA,EAAIA,EAExD,KAAK,KACH,GAAI,MAAQA,EAAEtL,WAAW,GAAI,MAE/B,KAAK,IACL,KAAK,IACH,MAAO,WAAasL,EAAIA,EAE1B,KAAK,IACH,MAAO,WAAaA,EAAI,QAAUA,EAAIA,EAExC,KAAK,KACL,KAAK,IACH,MAAO,WAAaA,EAAI,QAAUA,EAAI,OAASA,EAAIA,EAErD,KAAK,IACH,GAAI,KAAOA,EAAEtL,WAAW,GAAI,MAAO,WAAasL,EAAIA,EACpD,GAAI,EAAIA,EAAEvW,QAAQ,aAAc,IAAK,OAAOuW,EAAE5nB,QAAQ0qC,EAAI,gBAAkB9iB,EAC5E,MAEF,KAAK,IACH,GAAI,KAAOA,EAAEtL,WAAW,GAAI,OAAQsL,EAAEtL,WAAW,IAC/C,KAAK,IACH,MAAO,eAAiBsL,EAAE5nB,QAAQ,QAAS,IAAM,WAAa4nB,EAAI,OAASA,EAAE5nB,QAAQ,OAAQ,YAAc4nB,EAE7G,KAAK,IACH,MAAO,WAAaA,EAAI,OAASA,EAAE5nB,QAAQ,SAAU,YAAc4nB,EAErE,KAAK,GACH,MAAO,WAAaA,EAAI,OAASA,EAAE5nB,QAAQ,QAAS,kBAAoB4nB,EAE5E,MAAO,WAAaA,EAAI,OAASA,EAAIA,EAEvC,KAAK,IACH,MAAO,WAAaA,EAAI,YAAcA,EAAIA,EAE5C,KAAK,KACH,GAAI,KAAOA,EAAEtL,WAAW,GAAI,MAE5B,MAAO,oBADPuL,EAAID,EAAElF,UAAUkF,EAAEvW,QAAQ,IAAK,KAAKrR,QAAQ,QAAS,IAAIA,QAAQ,gBAAiB,YAClD,WAAa4nB,EAAI,gBAAkBC,EAAID,EAEzE,KAAK,KACH,OAAO+iB,EAAGtuB,KAAKuL,GAAKA,EAAE5nB,QAAQ4qC,EAAI,aAAehjB,EAAE5nB,QAAQ4qC,EAAI,UAAYhjB,EAAIA,EAEjF,KAAK,IAIH,OAFA6Y,GADA5Y,EAAID,EAAElF,UAAU,IAAIwnB,QACd74B,QAAQ,KAAO,EAEbwW,EAAEvL,WAAW,GAAKuL,EAAEvL,WAAWmkB,IACrC,KAAK,IACH5Y,EAAID,EAAE5nB,QAAQ6qC,EAAG,MACjB,MAEF,KAAK,IACHhjB,EAAID,EAAE5nB,QAAQ6qC,EAAG,SACjB,MAEF,KAAK,IACHhjB,EAAID,EAAE5nB,QAAQ6qC,EAAG,MACjB,MAEF,QACE,OAAOjjB,EAGX,MAAO,WAAaA,EAAI,OAASC,EAAID,EAEvC,KAAK,KACH,IAAK,IAAMA,EAAEvW,QAAQ,SAAU,GAAI,MAErC,KAAK,IAIH,OAHAovB,GAAK7Y,EAAIgK,GAAGtmB,OAAS,GAGb8+B,GAFRviB,GAAK,KAAOD,EAAEtL,WAAWmkB,GAAK7Y,EAAElF,UAAU,EAAG+d,GAAK7Y,GAAGlF,UAAUkP,EAAEvgB,QAAQ,IAAK,GAAK,GAAG64B,QAExE5tB,WAAW,IAAwB,EAAlBuL,EAAEvL,WAAW,KAC1C,KAAK,IACH,GAAI,IAAMuL,EAAEvL,WAAW,GAAI,MAE7B,KAAK,IACHsL,EAAIA,EAAE5nB,QAAQ6nB,EAAG,WAAaA,GAAK,IAAMD,EACzC,MAEF,KAAK,IACL,KAAK,IACHA,EAAIA,EAAE5nB,QAAQ6nB,EAAG,YAAc,IAAMuiB,EAAI,UAAY,IAAM,OAAS,IAAMxiB,EAAE5nB,QAAQ6nB,EAAG,WAAaA,GAAK,IAAMD,EAAE5nB,QAAQ6nB,EAAG,OAASA,EAAI,OAAS,IAAMD,EAG5J,OAAOA,EAAI,IAEb,KAAK,IACH,GAAI,KAAOA,EAAEtL,WAAW,GAAI,OAAQsL,EAAEtL,WAAW,IAC/C,KAAK,IACH,OAAOuL,EAAID,EAAE5nB,QAAQ,SAAU,IAAK,WAAa4nB,EAAI,eAAiBC,EAAI,YAAcA,EAAID,EAE9F,KAAK,IACH,MAAO,WAAaA,EAAI,iBAAmBA,EAAE5nB,QAAQ8qC,EAAI,IAAMljB,EAEjE,QACE,MAAO,WAAaA,EAAI,qBAAuBA,EAAE5nB,QAAQ,gBAAiB,IAAIA,QAAQ8qC,EAAI,IAAMljB,EAEpG,MAEF,KAAK,IACL,KAAK,IACH,GAAI,KAAOA,EAAEtL,WAAW,IAAM,MAAQsL,EAAEtL,WAAW,GAAI,MAEzD,KAAK,IACL,KAAK,IACH,IAAI,IAAOyuB,EAAG1uB,KAAKuV,GAAI,OAAO,OAAS/J,EAAI+J,EAAElP,UAAUkP,EAAEvgB,QAAQ,KAAO,IAAIiL,WAAW,GAAKiuB,EAAE3Y,EAAE5xB,QAAQ,UAAW,kBAAmBygC,EAAG35B,EAAG6kB,GAAG3rB,QAAQ,kBAAmB,YAAc4nB,EAAE5nB,QAAQ6nB,EAAG,WAAaA,GAAKD,EAAE5nB,QAAQ6nB,EAAG,QAAUA,EAAE7nB,QAAQ,QAAS,KAAO4nB,EACxQ,MAEF,KAAK,IACH,GAAIA,EAAI,WAAaA,GAAK,MAAQA,EAAEtL,WAAW,GAAK,OAASsL,EAAI,IAAMA,EAAG,MAAQ9gB,EAAI6kB,GAAK,MAAQ/D,EAAEtL,WAAW,KAAO,EAAIsL,EAAEvW,QAAQ,YAAa,IAAK,OAAOuW,EAAElF,UAAU,EAAGkF,EAAEvW,QAAQ,IAAK,IAAM,GAAGrR,QAAQgrC,EAAI,gBAAkBpjB,EAGvO,OAAOA,EAGT,SAAS6iB,EAAE7Y,EAAG6O,GACZ,IAAI35B,EAAI8qB,EAAEvgB,QAAQ,IAAMovB,EAAI,IAAM,KAC9B9U,EAAIiG,EAAElP,UAAU,EAAG,IAAM+d,EAAI35B,EAAI,IAErC,OADAA,EAAI8qB,EAAElP,UAAU5b,EAAI,EAAG8qB,EAAEtmB,OAAS,GAC3B2/B,EAAE,IAAMxK,EAAI9U,EAAIA,EAAE3rB,QAAQkrC,EAAI,MAAOpkC,EAAG25B,GAGjD,SAAS0K,EAAGvZ,EAAG6O,GACb,IAAI35B,EAAIyjC,EAAE9J,EAAGA,EAAEnkB,WAAW,GAAImkB,EAAEnkB,WAAW,GAAImkB,EAAEnkB,WAAW,IAC5D,OAAOxV,IAAM25B,EAAI,IAAM35B,EAAE9G,QAAQorC,EAAI,YAAY1oB,UAAU,GAAK,IAAM+d,EAAI,IAG5E,SAAS4K,EAAEzZ,EAAG6O,EAAG35B,EAAG6kB,EAAG/D,EAAGwiB,EAAGviB,EAAGsV,EAAG9f,EAAGyK,GACpC,IAAK,IAAkB0iB,EAAdc,EAAI,EAAGjV,EAAIoK,EAAM6K,EAAIC,IAAKD,EACjC,OAAQd,EAAIgB,EAAEF,GAAGtoC,KAAKyoC,EAAG7Z,EAAGyE,EAAGvvB,EAAG6kB,EAAG/D,EAAGwiB,EAAGviB,EAAGsV,EAAG9f,EAAGyK,IAClD,UAAK,EACL,KAAK,EACL,KAAK,EACL,KAAK,KACH,MAEF,QACEuO,EAAImU,EAIV,GAAInU,IAAMoK,EAAG,OAAOpK,EAmBtB,SAASqV,EAAE9Z,GAGT,YADA,KADAA,EAAIA,EAAE5wB,UACWiqC,EAAI,KAAMrZ,EAAI,mBAAsBA,EAAI4Y,EAAI,GAAKA,EAAI,EAAGS,EAAIrZ,GAAK4Y,EAAI,GAC/EkB,EAGT,SAASD,EAAE7Z,EAAG6O,GACZ,IAAI35B,EAAI8qB,EAKR,GAJA,GAAK9qB,EAAEwV,WAAW,KAAOxV,EAAIA,EAAEojC,QAE/BpjC,EAAI,CADAA,GAGA,EAAIykC,EAAG,CACT,IAAI5f,EAAI0f,GAAG,EAAG5K,EAAG35B,EAAGA,EAAG6kC,EAAGC,EAAG,EAAG,EAAG,EAAG,QACtC,IAAWjgB,GAAK,iBAAoBA,IAAM8U,EAAI9U,GAGhD,IAAI/D,EA3jBN,SAASikB,EAAEja,EAAG6O,EAAG35B,EAAG6kB,EAAG/D,GACrB,IAAK,IAAgCE,EAAGwjB,EAAiBl6B,EAAuE06B,EAAmCC,EAA1J3B,EAAI,EAAGviB,EAAI,EAAGsV,EAAI,EAAG9f,EAAI,EAASgZ,EAAI,EAAG2V,EAAI,EAAMC,EAAI76B,EAAI0W,EAAI,EAAGxC,EAAI,EAAG4mB,EAAI,EAAGC,EAAI,EAAGtJ,EAAI,EAAG4I,EAAI3kC,EAAEwE,OAAQ8gC,EAAIX,EAAI,EAAMY,EAAI,GAAI1d,EAAI,GAAI2b,EAAI,GAAIO,EAAI,GAAOvlB,EAAImmB,GAAI,CAI5K,GAHAH,EAAIxkC,EAAEwV,WAAWgJ,GACjBA,IAAM8mB,GAAK,IAAMvkB,EAAIxK,EAAI8f,EAAIiN,IAAM,IAAMviB,IAAMyjB,EAAI,KAAOzjB,EAAI,GAAK,IAAKxK,EAAI8f,EAAIiN,EAAI,EAAGqB,IAAKW,KAExF,IAAMvkB,EAAIxK,EAAI8f,EAAIiN,EAAG,CACvB,GAAI9kB,IAAM8mB,IAAM,EAAIF,IAAMG,EAAIA,EAAErsC,QAAQssC,EAAG,KAAM,EAAID,EAAEnC,OAAO5+B,QAAS,CACrE,OAAQggC,GACN,KAAK,GACL,KAAK,EACL,KAAK,GACL,KAAK,GACL,KAAK,GACH,MAEF,QACEe,GAAKvlC,EAAEqG,OAAOmY,GAGlBgmB,EAAI,GAGN,OAAQA,GACN,KAAK,IAKH,IAHAxjB,GADAukB,EAAIA,EAAEnC,QACA5tB,WAAW,GACjBlL,EAAI,EAECyxB,IAAMvd,EAAGA,EAAImmB,GAAI,CACpB,OAAQH,EAAIxkC,EAAEwV,WAAWgJ,IACvB,KAAK,IACHlU,IACA,MAEF,KAAK,IACHA,IACA,MAEF,KAAK,GACH,OAAQk6B,EAAIxkC,EAAEwV,WAAWgJ,EAAI,IAC3B,KAAK,GACL,KAAK,GACHsC,EAAG,CACD,IAAKqkB,EAAI3mB,EAAI,EAAG2mB,EAAIG,IAAKH,EACvB,OAAQnlC,EAAEwV,WAAW2vB,IACnB,KAAK,GACH,GAAI,KAAOX,GAAK,KAAOxkC,EAAEwV,WAAW2vB,EAAI,IAAM3mB,EAAI,IAAM2mB,EAAG,CACzD3mB,EAAI2mB,EAAI,EACR,MAAMrkB,EAGR,MAEF,KAAK,GACH,GAAI,KAAO0jB,EAAG,CACZhmB,EAAI2mB,EAAI,EACR,MAAMrkB,GAMdtC,EAAI2mB,GAKV,MAEF,KAAK,GACHX,IAEF,KAAK,GACHA,IAEF,KAAK,GACL,KAAK,GACH,KAAOhmB,IAAM8mB,GAAKtlC,EAAEwV,WAAWgJ,KAAOgmB,KAI1C,GAAI,IAAMl6B,EAAG,MACbkU,IAMF,OAHAlU,EAAItK,EAAE4b,UAAUmgB,EAAGvd,GACnB,IAAMwC,IAAMA,GAAKukB,EAAIA,EAAErsC,QAAQusC,EAAI,IAAIrC,QAAQ5tB,WAAW,IAElDwL,GACN,KAAK,GAIH,OAHA,EAAIokB,IAAMG,EAAIA,EAAErsC,QAAQssC,EAAG,KAC3BhB,EAAIe,EAAE/vB,WAAW,IAGf,KAAK,IACL,KAAK,IACL,KAAK,IACL,KAAK,GACH4vB,EAAIzL,EACJ,MAEF,QACEyL,EAAIM,EAMR,GAFA3J,GADAzxB,EAAIy6B,EAAEpL,EAAGyL,EAAG96B,EAAGk6B,EAAG1jB,EAAI,IAChBtc,OACN,EAAIigC,IAAsBQ,EAAIV,EAAE,EAAGj6B,EAAzB86B,EAAIjC,EAAEuC,EAAGH,EAAGF,GAAmB1L,EAAGkL,EAAGC,EAAG/I,EAAGyI,EAAG1jB,EAAG+D,GAAI0gB,EAAIH,EAAEzoC,KAAK,SAAK,IAAWsoC,GAAK,KAAOlJ,GAAKzxB,EAAI26B,EAAE7B,QAAQ5+B,UAAYggC,EAAI,EAAGl6B,EAAI,KAC5I,EAAIyxB,EAAG,OAAQyI,GACjB,KAAK,IACHe,EAAIA,EAAErsC,QAAQysC,EAAItB,GAEpB,KAAK,IACL,KAAK,IACL,KAAK,GACH/5B,EAAIi7B,EAAI,IAAMj7B,EAAI,IAClB,MAEF,KAAK,IAEHA,GADAi7B,EAAIA,EAAErsC,QAAQ0sC,EAAI,UACV,IAAMt7B,EAAI,IAClBA,EAAI,IAAMo5B,GAAK,IAAMA,GAAKC,EAAE,IAAMr5B,EAAG,GAAK,YAAcA,EAAI,IAAMA,EAAI,IAAMA,EAC5E,MAEF,QACEA,EAAIi7B,EAAIj7B,EAAG,MAAQua,IAAWgD,GAAKvd,EAAVA,EAAa,SACnCA,EAAI,GACX,MAEF,QACEA,EAAIy6B,EAAEpL,EAAGwJ,EAAExJ,EAAG4L,EAAGF,GAAI/6B,EAAGua,EAAG/D,EAAI,GAGnC0iB,GAAKl5B,EACLA,EAAI+6B,EAAID,EAAID,EAAInkB,EAAI,EACpBukB,EAAI,GACJf,EAAIxkC,EAAEwV,aAAagJ,GACnB,MAEF,KAAK,IACL,KAAK,GAEH,GAAI,GAAKud,GADTwJ,GAAK,EAAIH,EAAIG,EAAErsC,QAAQssC,EAAG,IAAMD,GAAGnC,QACpB5+B,QAAS,OAAQ,IAAM2gC,IAAMnkB,EAAIukB,EAAE/vB,WAAW,GAAI,KAAOwL,GAAK,GAAKA,GAAK,IAAMA,KAAO+a,GAAKwJ,EAAIA,EAAErsC,QAAQ,IAAK,MAAMsL,QAAS,EAAIigC,QAAK,KAAYQ,EAAIV,EAAE,EAAGgB,EAAG5L,EAAG7O,EAAG+Z,EAAGC,EAAGjd,EAAErjB,OAAQqgB,EAAG/D,EAAG+D,KAAO,KAAOkX,GAAKwJ,EAAIN,EAAE7B,QAAQ5+B,UAAY+gC,EAAI,QAAavkB,EAAIukB,EAAE/vB,WAAW,GAAIgvB,EAAIe,EAAE/vB,WAAW,GAAIwL,GAC9S,KAAK,EACH,MAEF,KAAK,GACH,GAAI,MAAQwjB,GAAK,KAAOA,EAAG,CACzBT,GAAKwB,EAAIvlC,EAAEqG,OAAOmY,GAClB,MAGJ,QACE,KAAO+mB,EAAE/vB,WAAWumB,EAAI,KAAOlU,GAAK4b,EAAE8B,EAAGvkB,EAAGwjB,EAAGe,EAAE/vB,WAAW,KAEhE6vB,EAAID,EAAID,EAAInkB,EAAI,EAChBukB,EAAI,GACJf,EAAIxkC,EAAEwV,aAAagJ,IAIzB,OAAQgmB,GACN,KAAK,GACL,KAAK,GACH,KAAOzjB,EAAIA,EAAI,EAAI,IAAM,EAAIC,GAAK,MAAQ6D,GAAK,EAAI0gB,EAAE/gC,SAAW4gC,EAAI,EAAGG,GAAK,MAC5E,EAAId,EAAIoB,GAAKtB,EAAE,EAAGgB,EAAG5L,EAAG7O,EAAG+Z,EAAGC,EAAGjd,EAAErjB,OAAQqgB,EAAG/D,EAAG+D,GACjDigB,EAAI,EACJD,IACA,MAEF,KAAK,GACL,KAAK,IACH,GAAI,IAAM9jB,EAAIxK,EAAI8f,EAAIiN,EAAG,CACvBwB,IACA,MAGJ,QAIE,OAHAA,IACAE,EAAIhlC,EAAEqG,OAAOmY,GAELgmB,GACN,KAAK,EACL,KAAK,GACH,GAAI,IAAMjuB,EAAI+sB,EAAIviB,EAAG,OAAQwO,GAC3B,KAAK,GACL,KAAK,GACL,KAAK,EACL,KAAK,GACHyV,EAAI,GACJ,MAEF,QACE,KAAOR,IAAMQ,EAAI,KAErB,MAEF,KAAK,EACHA,EAAI,MACJ,MAEF,KAAK,GACHA,EAAI,MACJ,MAEF,KAAK,GACHA,EAAI,MACJ,MAEF,KAAK,GACH,IAAMzuB,EAAIwK,EAAIuiB,IAAM8B,EAAIC,EAAI,EAAGL,EAAI,KAAOA,GAC1C,MAEF,KAAK,IACH,GAAI,IAAMzuB,EAAIwK,EAAIuiB,EAAIwC,GAAK,EAAIX,EAAG,OAAQ3mB,EAAI2mB,GAC5C,KAAK,EACH,MAAQ5V,GAAK,KAAOvvB,EAAEwV,WAAWgJ,EAAI,KAAOsnB,EAAIvW,GAElD,KAAK,EACH,MAAQ2V,IAAMY,EAAIZ,GAEtB,MAEF,KAAK,GACH,IAAM3uB,EAAIwK,EAAIuiB,IAAM6B,EAAI3mB,GACxB,MAEF,KAAK,GACH,IAAMuC,EAAIsV,EAAI9f,EAAI+sB,IAAM8B,EAAI,EAAGJ,GAAK,MACpC,MAEF,KAAK,GACL,KAAK,GACH,IAAMjkB,IAAMxK,EAAIA,IAAMiuB,EAAI,EAAI,IAAMjuB,EAAIiuB,EAAIjuB,GAC5C,MAEF,KAAK,GACH,IAAMA,EAAIwK,EAAIsV,GAAKiN,IACnB,MAEF,KAAK,GACH,IAAM/sB,EAAIwK,EAAIsV,GAAKiN,IACnB,MAEF,KAAK,GACH,IAAM/sB,EAAIwK,EAAIuiB,GAAKjN,IACnB,MAEF,KAAK,GACH,GAAI,IAAM9f,EAAIwK,EAAIuiB,EAAG,CACnB,GAAI,IAAMtiB,EAAG,OAAQ,EAAIuO,EAAI,EAAI2V,GAC/B,KAAK,IACH,MAEF,QACElkB,EAAI,EAERqV,IAGF,MAEF,KAAK,GACH,IAAMtV,EAAIsV,EAAI9f,EAAI+sB,EAAI6B,EAAI76B,IAAMA,EAAI,GACpC,MAEF,KAAK,GACL,KAAK,GACH,KAAM,EAAIiM,EAAI+sB,EAAIjN,GAAI,OAAQtV,GAC5B,KAAK,EACH,OAAQ,EAAIyjB,EAAI,EAAIxkC,EAAEwV,WAAWgJ,EAAI,IACnC,KAAK,IACHuC,EAAI,GACJ,MAEF,KAAK,IACHgb,EAAIvd,EAAGuC,EAAI,GAGf,MAEF,KAAK,GACH,KAAOyjB,GAAK,KAAOjV,GAAKwM,EAAI,IAAMvd,IAAM,KAAOxe,EAAEwV,WAAWumB,EAAI,KAAOlU,GAAK7nB,EAAE4b,UAAUmgB,EAAGvd,EAAI,IAAKwmB,EAAI,GAAIjkB,EAAI,IAIxH,IAAMA,IAAMwkB,GAAKP,GAGrBE,EAAI3V,EACJA,EAAIiV,EACJhmB,IAKF,GAAI,GAFJud,EAAIlU,EAAErjB,QAEK,CAET,GADA4gC,EAAIzL,EACA,EAAI8K,SAA2C,KAArCQ,EAAIV,EAAE,EAAG1c,EAAGud,EAAGta,EAAG+Z,EAAGC,EAAG/I,EAAGlX,EAAG/D,EAAG+D,KAAoB,KAAOgD,EAAIod,GAAGzgC,QAAS,OAAOu/B,EAAIlc,EAAI2b,EAGzG,GAFA3b,EAAIud,EAAEzoC,KAAK,KAAO,IAAMkrB,EAAI,IAExB,GAAM6b,EAAIoC,EAAG,CAGf,OAFA,IAAMpC,GAAKC,EAAE9b,EAAG,KAAOie,EAAI,GAEnBA,GACN,KAAK,IACHje,EAAIA,EAAE3uB,QAAQ6sC,EAAI,YAAcle,EAChC,MAEF,KAAK,IACHA,EAAIA,EAAE3uB,QAAQ8sC,EAAG,sBAAwBne,EAAE3uB,QAAQ8sC,EAAG,aAAene,EAAE3uB,QAAQ8sC,EAAG,iBAAmBne,EAGzGie,EAAI,GAIR,OAAO/B,EAAIlc,EAAI2b,EA8PPuB,CAAEW,EAAG1lC,EAAG25B,EAAG,EAAG,GAKtB,OAJA,EAAI8K,SAAmD,KAA7C5f,EAAI0f,GAAG,EAAGzjB,EAAG9gB,EAAGA,EAAG6kC,EAAGC,EAAGhkB,EAAEtc,OAAQ,EAAG,EAAG,MAAqBsc,EAAI+D,IACxE,GACJihB,EAAI,EACJhB,EAAID,EAAI,EACD/jB,EAGT,IAAI2kB,EAAK,QACLD,EAAI,YACJ1B,EAAK,OACLD,EAAK,UACLK,EAAK,sBACLb,EAAK,SACLG,EAAI,oBACJoC,EAAK,qBACLI,EAAI,aACJD,EAAK,gBACLhC,EAAI,qBACJ4B,EAAK,kBACLrB,EAAK,eACLN,EAAK,eACLI,EAAK,8BACLH,EAAK,mCACLL,EAAK,sBACLkB,EAAI,EACJD,EAAI,EACJiB,EAAI,EACJpC,EAAI,EACJgC,EAAI,GACJhB,EAAI,GACJD,EAAI,EACJN,EAAI,KACJ0B,EAAI,EAKR,OAHAlB,EAAEsB,IApEF,SAASC,EAAEpb,GACT,OAAQA,GACN,UAAK,EACL,KAAK,KACH2Z,EAAIC,EAAElgC,OAAS,EACf,MAEF,QACE,GAAI,mBAAsBsmB,EAAG4Z,EAAED,KAAO3Z,OAAO,GAAI,iBAAoBA,EAAG,IAAK,IAAI6O,EAAI,EAAG35B,EAAI8qB,EAAEtmB,OAAQm1B,EAAI35B,IAAK25B,EAC7GuM,EAAEpb,EAAE6O,SACCkM,EAAU,IAAJ/a,EAGjB,OAAOob,GAwDTvB,EAAElhC,IAAMmhC,OACR,IAAW1B,GAAK0B,EAAE1B,GACXyB,G,UCzlBT,SAASwB,EAAQC,GACXA,GACFC,EAAMvrC,QAAQm2B,OAAOmV,EAAQ,KAIjC,IAAIC,EAAQ,CACVvrC,QAAS,MAGPwrC,EAAY,SAAmB/sB,EAASnQ,EAASm9B,EAAWC,EAASr9B,EAAMs9B,EAAQjiC,EAAQkiC,EAAIC,EAAOC,GACxG,OAAQrtB,GAEN,KAAK,EAED,OAAQnQ,EAAQoM,WAAW,IACzB,KAAK,GAID,OADA6wB,EAAMvrC,QAAQm2B,OAAO7nB,EAAU,KACxB,GAIX,KAAK,IAID,GAA8B,KAA1BA,EAAQoM,WAAW,GACrB,MAAO,GAKf,MAIJ,KAAK,EAED,GAAW,IAAPkxB,EAAU,OAAOt9B,EA3Cb,QA4CR,MAIJ,KAAK,EAED,OAAQs9B,GAEN,KAAK,IACL,KAAK,IAGD,OADAL,EAAMvrC,QAAQm2B,OAAOsV,EAAU,GAAKn9B,GAC7B,GAGX,QAEI,OAAOA,GAAkB,IAAPw9B,EA7DhB,QA6DuC,IAKnD,KAAM,EAEFx9B,EAAQvC,MAnEHggC,UAmEiB/nC,QAAQqnC,KAsIvB,IAjIG,SAAqB1kC,QACrB2E,IAAZ3E,IAAuBA,EAAU,IACrC,IACIqlC,EADAhlC,EAAML,EAAQK,KAAO,WAGFsE,IAAnB3E,EAAQvH,SACV4sC,EAAgB,CACd5sC,OAAQuH,EAAQvH,SAIpB,IAAI6sC,EAAS,IAAI,EAAOD,GASxB,IAEIE,EAFAhW,EAAW,GAIbgW,EAAYvlC,EAAQulC,WAAa91B,SAAS+1B,KAC1C,IAcEC,EAdEC,EAAQj2B,SAASk2B,iBAAiB,sBAAwBtlC,EAAM,KACpE4O,MAAMtT,UAAU0B,QAAQ5C,KAAKirC,GAAO,SAAUzrB,GAC/BA,EAAK2rB,aAAa,gBAAkBvlC,GAE1C+E,MAAM,KAAK/H,SAAQ,SAAUmqB,GAClC+H,EAAS/H,IAAM,KAGbvN,EAAK4rB,aAAeN,GACtBA,EAAUO,YAAY7rB,MAQ1BqrB,EAAOd,IAAIxkC,EAAQ+lC,cAAnBT,CAAkCT,GAElCY,EAAU,SAAgBlN,EAAUjJ,EAAYG,EAAOuW,GACrD,IAAIljC,EAAOwsB,EAAWxsB,KACtB8hC,EAAMvrC,QAAUo2B,EAWhB6V,EAAO/M,EAAUjJ,EAAW9oB,QAExBw/B,IACF3kC,EAAMkuB,SAASzsB,IAAQ,IAqD7B,IAAIzB,EAAQ,CACVhB,IAAKA,EACLovB,MAAO,IAAI,IAAW,CACpBpvB,IAAKA,EACLklC,UAAWA,EACXU,MAAOjmC,EAAQimC,MACf/V,OAAQlwB,EAAQkwB,SAElB+V,MAAOjmC,EAAQimC,MACf1W,SAAUA,EACVpL,WAAY,GACZqL,OAAQiW,GAEV,OAAOpkC,I,wNC3MI6kC,EAAsB,CACjC1e,GAAG,mBACHrsB,MAAO,CACLyQ,SAAS,WACTu6B,IAAK,EACLjd,MAAO,EACPC,OAAQ,EACRid,QAAS,EACTC,SAAS,SACTC,KAAK,mBACLC,WAAW,SACXC,OAAQ,GAEV,YAAY,YACZ,cAAc,Q,oCCHVC,EAAc,IAAI3hC,IAClB4hC,EAAwB,IAAI5hC,IAUlC,SAAS6hC,EAAc7qC,GACrB,IAAI8qC,EAAWH,EAAYhlC,IAAI3F,GAK/B,OAJK8qC,IACHA,EAAWF,EAAsBjlC,IAAI3F,EAAS8nB,gBAGhC,MAAZgjB,IASFvrC,OAAO6E,WAAW0mC,EAASC,SACpB,GAxBXC,EAAUzpC,SAAQ,SAAAupC,GACZA,EAASG,WACXL,EAAsB1kC,IAAI4kC,EAASI,SAAUJ,GAE7CH,EAAYzkC,IAAI4kC,EAASI,SAAUJ,MA0BvC,IAAMK,EAAmB,SAAC7sC,EAAU8sC,GAC7BP,EAAcvsC,EAAS0B,WAC1BigB,oBAAU,mBAAoB,CAAE3hB,WAAU8sC,kBAIxCC,EAAgB,SAAC/sC,EAAU8sC,GAC1BP,EAAcvsC,EAAS0B,WAC1BigB,oBAAU,gBAAiB,CAAE3hB,WAAU8sC,kBAUrCvvC,EAAW,SAACqE,EAAIgE,GAIpB,QAJqC,IAAjBA,MAAU,IAI1B,iBAAOhE,EAAX,CAJqC,IAS/BF,EAAaxD,oBAAU0D,GAAvBF,SACF8qC,EAAWH,EAAYhlC,IAAI3F,GAc/B,GAbK8qC,IACHA,EAAWF,EAAsBjlC,IAAI3F,EAAS8nB,gBAK5CgjB,IACF5qC,EAAK4qC,EAASC,OACd/qC,EAAWxD,oBAAU0D,GAAIF,UAKvBT,OAAOqqB,aACTrqB,OAAOjB,SAAW0B,MADpB,CAOA,IAAMsrC,EAAYhvB,YAAW,WAC3BlM,IAAQM,KAAR,6BAA2C,CAAE1Q,aAC7CigB,oBAAU,uBAAwB,CAChC3hB,SAAUiB,OAAOjB,aAElB,KAEH0b,UAAOuxB,SAASvrC,GAAUqa,MAAK,SAAAsF,GAO7B,IAAKA,GAAiBA,EAAc6rB,SAAWC,qBAAmB13B,MAIhE,OAHAxU,OAAOmW,QAAQgB,aAAa,GAA5B,GAAoCpY,SAAS+E,MAC7C9D,OAAOjB,SAAW0B,OAClB0c,aAAa4uB,GAM8B3rB,GAEzCA,EAAcQ,KAAKurB,yBACnBnsC,OAAOosC,4BAIL,kBAAmBhlB,WACoB,OAAvCA,UAAU0C,cAAcM,YACxB,cAAAhD,UAAU0C,cAAcM,WAAWlqB,OAEnCknB,UAAU0C,cAAcM,WAAWiiB,YAAY,CAC7CC,UAAU,uBAIdtsC,OAAOjB,SAAW0B,GAGtB8rC,mBAAc5rC,EAAIgE,GAClBwY,aAAa4uB,YArEbzzB,IAAchc,SAASqE,IAyE3B,SAAS+d,EAAmBM,EAA5B,GAA4D,IAAD,OAAZjgB,EAAY,EAAZA,SACrC0B,EAAmB1B,EAAnB0B,SAAUmV,EAAS7W,EAAT6W,KACZ42B,EAAU9rB,oBAAU,qBAAsB,CAC9C1B,kBAEAve,WACAwe,YAAa,CAAElgB,YACf0tC,uBAAwB,SAAA7+B,GAAI,MAAI,CAC9B,EACA,EAAK0Q,cAAcvZ,KAAK6I,EAAMA,EAAK5I,SAGvC,GAAIwnC,EAAQ9kC,OAAS,EAGnB,OAAO8kC,EAAQA,EAAQ9kC,OAAS,GAGlC,GAAIsX,GAGEA,EADFjgB,SAAY0B,WAEMA,EAGlB,OAAOmV,EAAOM,UAAUN,EAAKjY,MAAM,IAAM,CAAC,EAAG,GAGjD,OAAO,E,IAkBH+uC,E,YACJ,WAAY/tC,GAAQ,IAAD,SACjB,cAAMA,IAAN,MACKguC,gBAAkB34B,IAAM44B,YAFZ,E,4CAKnB7rC,mBAAA,SAAmBC,EAAWoU,GAAY,IAAD,OACvCy3B,uBAAsB,WACpB,IAAIC,EAAQ,eAAkB,EAAKnuC,MAAMI,SAAS0B,SAC9C2T,SAASia,QACXye,EAAW14B,SAASia,OAEtB,IAAM0e,EAAe34B,SAASk2B,iBAAT,4BACjByC,GAAgBA,EAAarlC,SAC/BolC,EAAWC,EAAa,GAAGtM,aAE7B,IAAMuM,EAAe,gBAAmBF,EACpC,EAAKH,gBAAgB3uC,UACC,EAAK2uC,gBAAgB3uC,QAAQivC,YAC7BD,IACtB,EAAKL,gBAAgB3uC,QAAQivC,UAAYD,Q,EAMjD1qC,OAAA,WACE,OAAO,iCAASuoC,EAAT,CAA8BnpC,IAAKrC,KAAKstC,oB,GA3BtB34B,IAAMjQ,WA+B7BmpC,EAAuB,SAACrB,EAAcsB,GAAkB,IAAD,IAC3D,OAAItB,EAAa/nC,OAASqpC,EAAarpC,OAInC+nC,SAAA,UAAAA,EAAc3rC,aAAd,eAAqB8E,QAAQmoC,SAA7B,UAA6BA,EAAcjtC,aAA3C,aAA6B,EAAqB8E,MAQlDooC,E,YACJ,WAAYzuC,GAAQ,IAAD,SACjB,cAAMA,IAAN,KACAitC,EAAiBjtC,EAAMI,SAAU,MAFhB,E,4CAKnBmC,kBAAA,WACE4qC,EAAczsC,KAAKV,MAAMI,SAAU,O,EAGrCoW,sBAAA,SAAsBnU,GACpB,QAAIksC,EAAqBlsC,EAAUjC,SAAUM,KAAKV,MAAMI,YACtD6sC,EAAiBvsC,KAAKV,MAAMI,SAAUiC,EAAUjC,WACzC,I,EAKXgC,mBAAA,SAAmBC,GACbksC,EAAqBlsC,EAAUjC,SAAUM,KAAKV,MAAMI,WACtD+sC,EAAczsC,KAAKV,MAAMI,SAAUiC,EAAUjC,W,EAIjDuD,OAAA,WACE,OACE,YAAC,IAAM6Q,SAAP,KACG9T,KAAKV,MAAM2P,SACZ,YAAC,EAAD,CAAgBvP,SAAUA,a,GA5BPiV,IAAMjQ,W,6CCtOjC,SAASspC,EAAerpB,EAAGC,GACzB,IAAK,IAAI7a,KAAK4a,EACZ,KAAM5a,KAAK6a,GAAI,OAAO,EACvB,IAAK,IAAImF,KAAMnF,EACd,GAAID,EAAEoF,KAAQnF,EAAEmF,GAAK,OAAO,EAC7B,OAAO,E,6kBCyFKkkB,E,YA3Fb,WAAY3uC,GAAQ,IAAD,EACjB,qBADiB,IAETI,EAA4BJ,EAA5BI,SAAUqhB,EAAkBzhB,EAAlByhB,cAFD,OAGjB,EAAKlgB,MAAQ,CACXnB,SAAS,EAAD,GAAOA,GACfqhB,cAAeA,GAAiB3F,UAAO8yB,aAAaxuC,EAAS0B,WAL9C,E,mBASZ4G,yBAAP,WAA8CpG,GAAY,IAAxBlC,EAAuB,EAAvBA,SAChC,OAAIkC,EAAUlC,SAAS+E,OAAS/E,EAAS+E,KAEhC,CACLsc,cAFoB3F,UAAO8yB,aAAaxuC,EAAS0B,UAGjD1B,SAAS,EAAD,GAAOA,IAIZ,CACLA,SAAS,EAAD,GAAOA,K,2BAInByuC,cAAA,SAAcC,GAAU,IAAD,OACrBhzB,UAAOuxB,SAASyB,GAAS3yB,MAAK,SAAAsF,GACxBA,GAAiBA,EAAc6rB,SAAWC,qBAAmB13B,MAC/D,EAAK2H,SAAS,CACZpd,SAAS,EAAD,GAAOiB,OAAOjB,UACtBqhB,mBAGFpgB,OAAOmW,QAAQgB,aAAa,GAA5B,GAAoCpY,SAAS+E,MAC7C9D,OAAOjB,SAAW0uC,O,EAKxBt4B,sBAAA,SAAsBC,EAAWs4B,GAE/B,OAAKA,EAAUttB,cAcX/gB,KAAKa,MAAMkgB,gBAAkBstB,EAAUttB,gBAIzC/gB,KAAKa,MAAMkgB,cAAcjY,YAAculC,EAAUttB,cAAcjY,YAK7D9I,KAAKa,MAAMkgB,cAAcC,OAASqtB,EAAUttB,cAAcC,SAM5DhhB,KAAKa,MAAMnB,SAASiG,MAAQ0oC,EAAU3uC,SAASiG,MAC/C0oC,EAAUttB,cAAcQ,OACvB8sB,EAAUttB,cAAcQ,KAAKrW,YAC5BmjC,EAAUttB,cAAcQ,KAAK3kB,ODlErB,gBACd,OAAOoxC,EAAe/rC,EAAS3C,MAAOyW,IAAci4B,EAAe/rC,EAASpB,MAAOwtC,GCqE1EvpB,CAAe9kB,KAAM+V,EAAWs4B,OAnCrCruC,KAAKmuC,cAAcp4B,EAAUrW,SAAS0B,WAC/B,I,EAqCX6B,OAAA,WASE,OAAOjD,KAAKV,MAAM2P,SAASjP,KAAKa,Q,GAxFN8T,IAAMjQ,W,wBCwB9B0W,EAAS,IAAIkzB,aAAWC,IAAelkC,GAC7CmkC,oBAAUpzB,GACVA,EAAOqzB,aAAaptB,aAEpB1gB,OAAO4tC,cAAgBA,IACvB5tC,OAAO+tC,WAAal9B,IACpB7Q,OAAOa,UAAY8f,eH8IjBrI,IAAc7B,QAAO,SAAA7I,GACnBA,EAAK7O,SAAS6X,OAAShJ,EAAKgJ,UAG9B5W,OAAO4E,QAAU,SAAAjE,GAAE,OAAIrE,EAASqE,EAAI,CAAEvE,SAAS,KAC/C4D,OAAO6E,WAAa,SAAAlE,GAAE,OAAIrE,EAASqE,EAAI,CAAEvE,SAAS,KAClD4D,OAAO6D,YAAc,SAAClD,EAAIgE,GAAL,OAAiBrI,EAASqE,EAAIgE,IAGnD2mC,EAActrC,OAAOjB,SAAS0B,UGnJhCutC,yBAAe,iBAAiBlzB,MAAK,WAG/B4F,oBAAU,yBAAyBhZ,OAAS,GAC9C9L,EAAQ,QAWV,IAAMqyC,EAAe,SAAAtvC,GAAK,OACxB,YAAC,cAAYoU,SAAb,CACE5N,MAAO,CACL+oC,QAAQ,IACRC,SAAS,MAGX,YAAC,IAAiBxvC,KAIhByvC,EAAcp6B,IAAMxB,cAAc,IAElC67B,EA5BmC,kGA6BvC/rC,OAAA,WAAU,IACAgM,EAAajP,KAAKV,MAAlB2P,SACR,OACE,YAAC,WAAD,MACG,gBAAGvP,EAAH,EAAGA,SAAH,OACC,YAAC,EAAD,CAAiBA,SAAUA,IACxB,YAAkC,IAA/BqhB,EAA8B,EAA9BA,cAAerhB,EAAe,EAAfA,SACXuvC,EAAqBC,kCAC3B,OACE,YAAC,qBAAmBx7B,SAApB,CAA6B5N,MAAOmpC,GAClC,YAACF,EAAYr7B,SAAb,CAAsB5N,MAAO,CAAEib,gBAAerhB,aAC3CuP,WAxCoB,GA4BhB0F,IAAMjQ,WAwBzByqC,EApDmC,kGAqDvClsC,OAAA,WAAU,IAAD,OACP,OACE,YAAC8rC,EAAY3hB,SAAb,MACG,gBAAGrM,EAAH,EAAGA,cAAerhB,EAAlB,EAAkBA,SAAlB,OACC,YAAC,EAAD,CAAcA,SAAUA,GACtB,YAAC,gBAAD,CACEA,SAAUA,EACV2f,mBAAoBA,GAEpB,YAAC,SAAD,CACEyvB,SAAUtwC,GACVkB,SAAUA,EACVotB,GAAG,wBAEH,YAAC8hB,EAAD,aACEhyC,KACE,cAAAmkB,EAAcQ,KAAK3kB,KACf6N,YAAY/K,EAAS0B,SAAU5C,IAC/B+F,UACEwc,EAAcQ,KAAKrW,WACjB6V,EAAcQ,KAAK3kB,OAGzB,EAAK0C,MATX,CAUEI,SAAUA,EACVqhB,cAAeA,GACXA,EAAcC,cA/EK,GAoDXrM,IAAMjQ,WApDK,EA0FE/D,OAAnCyuC,EA1FiC,EA0FjCA,SAAoBC,EA1Fa,EA0FvB3vC,SAUhB0vC,GACA5wC,GAAgB4wC,IAAaC,EAAWjuC,YAEtCga,EAAOvQ,cAAcJ,YAAY4kC,EAAWjuC,SAAU5C,MAC9C,cAAR4wC,GACAA,EAASvtB,MAAM,eACfutB,EAASvtB,MAAM,8CAGjB5kB,mBAASuB,GAAgB4wC,EAAWC,EAAW/4B,OAAS+4B,EAAW94B,KAAM,CACvExZ,SAAS,IAIbukB,eAAaqrB,SAAS0C,EAAWjuC,UAAUqa,MAAK,SAAA8F,GAC9C,IAAKA,GAAQA,EAAKqrB,SAAWC,qBAAmB13B,MAC9C,MAAM,IAAIA,MAAJ,sBACkBk6B,EAAWjuC,SAD7B,mCAKRT,OAAOosC,0BAA4BxrB,EAAKA,KAAKurB,uBAE7C,IAAMwC,EAAWjuB,oBAAU,kBAEzB,CAAErB,QAAS,YAACmvB,EAAD,OACX,YAACA,EAAD,OACA,YACE,MAAO,CAAEnvB,QADK,EAAblE,WAGHxL,MAEIi/B,EAAM,kBAAM,YAACP,EAAD,KAAaM,IAEzBE,EAAWnuB,oBAAU,8BAEzBpX,EACAwlC,IAASpZ,SACT,GAEFqZ,KAAS,WACPF,EACE,YAACD,EAAD,MACA,oBAAO5uC,OACHoU,SAASyK,eAAT,kBACA,GACJ,WACE6B,oBAAU,sC,mBCzLpBza,EAAOpK,QAAU,syC,qBCAjB,IAAIue,EAAiB,EAAQ,QAQ7BnU,EAAOpK,QANP,SAAwBiZ,EAAUC,GAChCD,EAASxU,UAAYiG,OAAOsG,OAAOkI,EAAWzU,WAC9CwU,EAASxU,UAAU0O,YAAc8F,EACjCsF,EAAetF,EAAUC,IAI3B9O,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,kCCTxE,62BAeMkzC,EAAmBv0B,UAAO3Z,QAE1BmuC,EAAqBj7B,IAAMxB,cAAc,IAE/C,SAAS08B,EAAT,GAA4E,IAAzCC,EAAwC,EAAxCA,gBAAiBvc,EAAuB,EAAvBA,KAAMxP,EAAiB,EAAjBA,MAAO9gB,EAAU,EAAVA,OACzD8sC,EAAYxc,EACdA,EAAKA,KACLuc,EAAgB/rB,IAAU+rB,EAAgB/rB,GAAOwP,KAErD,OACE,YAAC,IAAMzf,SAAP,KACGi8B,GAAa9sC,EAAO8sC,IACnBA,GAAa,iDAKrB,IAAMC,EAAc,SAAA1wC,GAAU,IACpBi0B,EAAkCj0B,EAAlCi0B,KAAMxP,EAA4BzkB,EAA5BykB,MAAO9gB,EAAqB3D,EAArB2D,OAAQgM,EAAa3P,EAAb2P,SAE7B,OACE,YAAC2gC,EAAmBxiB,SAApB,MACG,SAAA0iB,GAAe,OACd,YAACD,EAAD,CACEtc,KAAMA,EACNxP,MAAOA,EACP9gB,OAAQA,GAAUgM,EAClB6gC,gBAAiBA,QAOrBG,EAAiB,SAAAlsB,GAAU,IAAD,EAErBpP,IAAM9D,WAQf,IAAMuM,EAAUzI,IAAM9D,WAAW++B,GAKjC,GAAIM,MAAMC,OAAOpsB,IACf,MAAM,IAAI5O,MAAJ,8KAIgB4O,EAJhB,SAQR,aAAI3G,EAAQ2G,UAAZ,OAAI,EAAgBwP,KAClB,OAAOnW,EAAQ2G,GAAOwP,KAEtB,MAAM,IAAIpe,MACR,yMAcN,SAAS+pB,IACP,MAAM,IAAI/pB,MACR,gV,mBCnFJvO,EAAOpK,QAVP,SAA2BilB,EAAKjT,IACnB,MAAPA,GAAeA,EAAMiT,EAAIpZ,UAAQmG,EAAMiT,EAAIpZ,QAE/C,IAAK,IAAI0B,EAAI,EAAGqmC,EAAO,IAAI77B,MAAM/F,GAAMzE,EAAIyE,EAAKzE,IAC9CqmC,EAAKrmC,GAAK0X,EAAI1X,GAGhB,OAAOqmC,GAITxpC,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,woBCXxE,IAAMkY,EAAQpY,EAAd,QACQs7B,EAAQt7B,EAAQ,QAAhBs7B,IACAle,EAAgBpd,EAAQ,QAAxBod,YAER/S,UAAiB,SAAqB,GAIlC,IAHFgT,EAGC,EAHDA,MACA3K,EAEC,EAFDA,SACG3P,EACF,0BACK+wC,EAAW12B,EADhB,GAIK22B,EAAM37B,EAAA,SAAc,WACxB,MACE,OAAO,KAGT,IAAM47B,EAAS,GAGb57B,MAHa,EAIbkjB,OAJF,GAQMluB,EAAOzC,YAAb,GACMspC,EAAS7mC,EAAA,KAAS,SAAAhE,GAAG,OAAI4qC,EAAJ,MAG3B,OAFQ,mCAAR,KAEOj/B,2BAAP,OACC,CAACrC,EAlBJ,IAoBA,OAAO0F,uBAAP,M,mBChCF/N,EAAOpK,QAAU,85C,iFCEjBoK,EAAOpK,QAAU0K,OAAOyF,Q,kCCFxB,m8BAAID,EAAWxF,OAAOyF,QAAU,SAAU9J,GAAU,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CAAE,IAAI6C,EAASpE,UAAUuB,GAAI,IAAK,IAAIpE,KAAOiH,EAAc1F,OAAOjG,UAAUwB,eAAe1C,KAAK6M,EAAQjH,KAAQ9C,EAAO8C,GAAOiH,EAAOjH,IAAY,OAAO9C,GAEvP,SAAS+P,EAAyB/L,EAAK8C,GAAQ,IAAI9G,EAAS,GAAI,IAAK,IAAIkH,KAAKlD,EAAW8C,EAAKyE,QAAQrE,IAAM,GAAkB7C,OAAOjG,UAAUwB,eAAe1C,KAAK8G,EAAKkD,KAAclH,EAAOkH,GAAKlD,EAAIkD,IAAM,OAAOlH,EAEnN,SAAS4X,EAAgBxY,EAAUyY,GAAe,KAAMzY,aAAoByY,GAAgB,MAAM,IAAIV,UAAU,qCAEhH,SAASW,EAA2BC,EAAM7a,GAAQ,IAAK6a,EAAQ,MAAM,IAAIC,eAAe,6DAAgE,OAAO9a,GAAyB,iBAATA,GAAqC,mBAATA,EAA8B6a,EAAP7a,EAElO,SAAS+a,EAAUrF,EAAUC,GAAc,GAA0B,mBAAfA,GAA4C,OAAfA,EAAuB,MAAM,IAAIsE,UAAU,kEAAoEtE,GAAeD,EAASxU,UAAYiG,OAAOsG,OAAOkI,GAAcA,EAAWzU,UAAW,CAAE0O,YAAa,CAAE7J,MAAO2P,EAAUlJ,YAAY,EAAOE,UAAU,EAAMD,cAAc,KAAekJ,IAAYxO,OAAO6T,eAAiB7T,OAAO6T,eAAetF,EAAUC,GAAcD,EAAS/F,UAAYgG,GAaje,IAAI+6B,EAAqB,SAA4BroC,EAAMsoC,GACzD,IAAIC,EAAM,IAAcD,GAExB,OADAC,EAAI9oC,YAAcO,EACXuoC,GAKLC,EAAkBH,EAAmB,YAIrCjxC,EAAW,SAAkBxB,GAC/B,IAAIiR,EAAWjR,EAAKiR,SACpB,OAAO,IAAM1P,cACXqxC,EAAgBxjB,SAChB,MACA,SAAUhQ,GACR,OAAOA,EAAUnO,EAASmO,GAAW,IAAM7d,cACzCsxC,EACA,KACA5hC,OAMJ4hC,EAAmB,SAAUhxC,GAG/B,SAASgxC,IACP,IAAI30B,EAAOpc,EAEX2a,EAAgBza,KAAM6wC,GAEtB,IAAK,IAAI9xB,EAAOvW,UAAUH,OAAQkG,EAAOgG,MAAMwK,GAAOC,EAAO,EAAGA,EAAOD,EAAMC,IAC3EzQ,EAAKyQ,GAAQxW,UAAUwW,GAGzB,OAAe9C,EAASpc,EAAQ6a,EAA2B3a,KAAMH,EAAiBE,KAAK8M,MAAMhN,EAAkB,CAACG,MAAM4J,OAAO2E,KAAiBzO,EAAMe,MAAQ,CAC1Juc,QAAStd,EAAMgxC,aACfC,KAAM,CAAEC,SAAU,OACTr2B,EAA2B7a,EAAnCoc,GAkEL,OAhFApB,EAAU+1B,EAAkBhxC,GAiB5BgxC,EAAiB5vC,UAAU6vC,WAAa,WACtC,IAAIG,EAAiBjxC,KAAKV,MAAMwX,QAIhC,MAAO,CAAE7Z,SAHMg0C,EAAeh0C,SAGDyC,SAFduxC,EAAevxC,WAKhCmxC,EAAiB5vC,UAAUiwC,kBAAoB,SAA2B11B,EAAO21B,GAC/E,IAAIC,EAAW51B,GAKb,MAAMA,GAFN61B,EAFgBrxC,KAAKV,MAAMwX,QAAQ7Z,UAEzBue,EAAM7C,IAAK,CAAE5b,SAAS,KAMpC8zC,EAAiB5vC,UAAUS,mBAAqB,SAA4BC,EAAWC,GACjFA,EAAUwb,QAAQ1d,WAAaM,KAAKa,MAAMuc,QAAQ1d,UACpDM,KAAKV,MAAMwX,QAAQK,yBAIvB05B,EAAiB5vC,UAAUY,kBAAoB,WAC7C,IAAIU,EAASvC,KAET+wC,EAAO/wC,KAAKa,MAAMkwC,KAClBj6B,EAAU9W,KAAKV,MAAMwX,QAEzBA,EAAQK,wBACR45B,EAAKC,SAAWl6B,EAAQM,QAAO,WAC7Ba,QAAQrZ,UAAU6c,MAAK,WAErB+xB,uBAAsB,WACfjrC,EAAO+uC,WACV/uC,EAAOua,UAAS,WACd,MAAO,CAAEM,QAAS7a,EAAOuuC,2BAQrCD,EAAiB5vC,UAAUa,qBAAuB,WAChD,IAAIivC,EAAO/wC,KAAKa,MAAMkwC,KAEtB/wC,KAAKsxC,WAAY,EACjBP,EAAKC,YAGPH,EAAiB5vC,UAAUgC,OAAS,WAClC,IAAIma,EAAUpd,KAAKa,MAAMuc,QACrBnO,EAAWjP,KAAKV,MAAM2P,SAE1B,OAAO,IAAM1P,cACXqxC,EAAgBl9B,SAChB,CAAE5N,MAAOsX,GACW,mBAAbnO,EAA0BA,EAASmO,GAAWnO,GAAY,OAI9D4hC,EAjFc,CAkFrB,IAAMnsC,WAKRmsC,EAAiBjpC,aAAe,CAC9BkP,QAAS,KAKX,IAAIy6B,EAAiB,SAAwB9xC,GAC3C,IAAIyrB,EAAMzrB,EAAMyrB,IACZjc,EAAWxP,EAAMwP,SAEjBoJ,EAAc6S,EAAI9c,QAAQ,KAE1BhN,OAAW,EACXkV,EAAS,GAUb,OAZmB+B,GAAe,GAMhCjX,EAAW8pB,EAAIzL,UAAU,EAAGpH,GAC5B/B,EAAS4U,EAAIzL,UAAUpH,IAEvBjX,EAAW8pB,EAGN,IAAM3rB,cACXqxC,EAAgBl9B,SAChB,CACE5N,MAAO,CACLpG,SAAU,CACR0B,SAAUA,EACVkV,OAAQA,EACRC,KAhBG,IAkBLtZ,SAAU,WACR,MAAM,IAAIkY,MAAM,6CAItBlG,IAKAuiC,EAAcf,EAAmB,OAAQ,CAAE5B,QAAS,IAAKC,SAAU,MAInE2C,EAAS,SAAgBnyC,GAC3B,OAAO,IAAMC,cACXiyC,EAAYpkB,SACZ,MACA,SAAUskB,GACR,OAAO,IAAMnyC,cACXC,EACA,MACA,SAAUmyC,GACR,OAAO,IAAMpyC,cAAcqyC,EAAYllC,EAAS,GAAIglC,EAAaC,EAAiBryC,WAOxFsyC,EAAa,SAAUC,GAGzB,SAASD,IAGP,OAFAn3B,EAAgBza,KAAM4xC,GAEfj3B,EAA2B3a,KAAM6xC,EAAqBhlC,MAAM7M,KAAMwI,YAgF3E,OArFAsS,EAAU82B,EAAYC,GAQtBD,EAAW3wC,UAAUgC,OAAS,WAC5B,IAAI2iC,EAAS5lC,KAAKV,MACdI,EAAWkmC,EAAOlmC,SAClBoyC,EAAalM,EAAO3oC,SACpB6xC,EAAWlJ,EAAOkJ,SAClBiD,EAAUnM,EAAOmM,QACjB9iC,EAAW22B,EAAO32B,SAElB+iC,GADUpM,EAAOiJ,QACEjJ,EAAO98B,WAC1BA,OAAiCmB,IAArB+nC,EAAiC,MAAQA,EACrDC,EAAWr/B,EAAyBgzB,EAAQ,CAAC,WAAY,WAAY,WAAY,UAAW,WAAY,UAAW,cAEnHhkB,EAAS,IAAMvD,SAAS6zB,QAAQjjC,GAAUvB,QAAO,SAAUykC,EAAOrO,GACpE,IAAIliB,EAASwwB,EAAYtD,EAAZsD,CAAsBtO,GACnC,OAAOqO,EAAMvoC,OAAOgY,KACnB,IACCxgB,EAAW1B,EAAS0B,SAGpBygB,EAAQ,eAAKD,EAAQxgB,GAEzB,GAAIygB,EAAO,CACT,IAAIrW,EAASqW,EAAMrW,OACfmN,EAAMkJ,EAAMlJ,IACZrN,EAAQuW,EAAMvW,MACd0U,EAAU6B,EAAMvW,MAAMxF,MAI1BgpC,EAAWxjC,EAAMpO,QAAU4xC,EAAWxjC,EAAM1O,KAAKG,QAAQ,MAAO,IAEhE,IAAIuC,EAAQoN,EAAS,GAAIlB,EAAQ,CAC/BmN,IAAKA,EACLjZ,SAAUA,EACVzC,SAAU,SAAkBqE,EAAIgE,GAC9B,OAAOwsC,EAAW,kBAAQxwC,EAAIqX,GAAMrT,MAIpC00B,EAAQ,IAAMqY,aAAaryB,EAAS1gB,EAAO0gB,EAAQ1gB,MAAM2P,SAAW,IAAM1P,cAC5EkyC,EACA,CAAE/xC,SAAUA,EAAUqyC,QAASA,GAC/B/xB,EAAQ1gB,MAAM2P,eACZhF,GAGAqoC,EAAeP,EAAUQ,EAAezpC,EAExC0pC,EAAeT,EAAUrlC,EAAS,CAAEiM,IAAKA,EAAKjZ,SAAUA,EAAUoJ,UAAWA,GAAampC,GAAYA,EAE1G,OAAO,IAAM1yC,cACXiyC,EAAY99B,SACZ,CAAE5N,MAAO,CAAE+oC,QAASl2B,EAAKm2B,SAAUA,IACnC,IAAMvvC,cACJ+yC,EACAE,EACAxY,IAiBJ,OAAO,MAIJ4X,EAtFQ,CAuFf,IAAMa,eAERb,EAAWhqC,aAAe,CACxBmqC,SAAS,GAIX,IAAIW,EAAejC,EAAmB,SAElC8B,EAAe,SAAsBryC,GACvC,IAAIyY,EAAMzY,EAAMyY,IACZjZ,EAAWQ,EAAMR,SACjBoJ,EAAY5I,EAAM4I,UAClBmpC,EAAWr/B,EAAyB1S,EAAO,CAAC,MAAO,WAAY,cAEnE,OAAO,IAAMX,cACXmzC,EAAatlB,SACb,MACA,SAAUulB,GACR,OAAO,IAAMpzC,cAAcqzC,EAAkBlmC,EAAS,GAAIulC,EAAU,CAClEnpC,UAAWA,EACX6pC,aAAcA,EACdh6B,IAAKA,EACLjZ,SAAUA,SAOdmzC,GAAgB,EAChBC,EAAoB,EAEpBF,EAAmB,SAAUz0B,GAG/B,SAASy0B,IACP,IAAIG,EAAQC,EAEZv4B,EAAgBza,KAAM4yC,GAEtB,IAAK,IAAI1c,EAAQ1tB,UAAUH,OAAQkG,EAAOgG,MAAM2hB,GAAQC,EAAQ,EAAGA,EAAQD,EAAOC,IAChF5nB,EAAK4nB,GAAS3tB,UAAU2tB,GAG1B,OAAgB4c,EAAUC,EAASr4B,EAA2B3a,KAAMme,EAAkBpe,KAAK8M,MAAMsR,EAAmB,CAACne,MAAM4J,OAAO2E,KAAkBykC,EAAOnyC,MAAQ,GAAImyC,EAAOL,aAAe,SAAUpzB,IAChMyzB,EAAOnyC,MAAMoyC,aAAe1zB,GAC/BA,EAAK2zB,SAEGv4B,EAA2Bq4B,EAApCD,GA4FL,OA3GAj4B,EAAU83B,EAAkBz0B,GAkB5By0B,EAAiB5qC,yBAA2B,SAAkC+N,EAAWnU,GAEvF,GAD+B,MAAjBA,EAAU+W,IAEtB,OAAOjM,EAAS,CACdumC,aAAa,GACZl9B,GAEH,IAAIo9B,EAAep9B,EAAU4C,MAAQ/W,EAAU+W,IAC3Cy6B,EAAkBxxC,EAAUlC,SAAS0B,WAAa2U,EAAUrW,SAAS0B,UAAY2U,EAAUrW,SAAS0B,WAAa2U,EAAU4C,IAC/H,OAAOjM,EAAS,CACdumC,YAAaE,GAAgBC,GAC5Br9B,IAIP68B,EAAiB3xC,UAAUY,kBAAoB,WAC7CixC,IACA9yC,KAAKkzC,SAGPN,EAAiB3xC,UAAUa,qBAAuB,WAEtB,MAD1BgxC,IAEED,GAAgB,IAIpBD,EAAiB3xC,UAAUS,mBAAqB,SAA4BC,EAAWC,GACjFD,EAAUjC,WAAaM,KAAKV,MAAMI,UAAYM,KAAKa,MAAMoyC,aAC3DjzC,KAAKkzC,SAITN,EAAiB3xC,UAAUiyC,MAAQ,WAQjC,IAAIP,EAAe3yC,KAAKV,MAAMqzC,aAG1BA,EACFA,EAAa3yC,KAAKuf,MAEdszB,EACFA,GAAgB,EACP7yC,KAAKuf,OAGTvf,KAAKuf,KAAK8zB,SAASt+B,SAASu+B,gBAC/BtzC,KAAKuf,KAAK2zB,UAMlBN,EAAiB3xC,UAAUgC,OAAS,WAClC,IAAIswC,EAASvzC,KAETwzC,EAAUxzC,KAAKV,MAEfmB,GADW+yC,EAAQvkC,SACXukC,EAAQ/yC,OAEhBgzC,GADeD,EAAQb,aACHa,EAAQ1qC,WAC5B4qC,OAA6BzpC,IAAtBwpC,EAAkC,MAAQA,EAGjDxB,GAFMuB,EAAQ76B,IACH66B,EAAQ9zC,SACRkT,EAAyB4gC,EAAS,CAAC,WAAY,QAAS,eAAgB,YAAa,MAAO,cAE3G,OAAO,IAAMj0C,cACXm0C,EACAhnC,EAAS,CACPjM,MAAOiM,EAAS,CAAEinC,QAAS,QAAUlzC,GACrCi0B,SAAU,KACVryB,IAAK,SAAa+X,GAChB,OAAOm5B,EAAOh0B,KAAOnF,IAEtB63B,GACH,IAAM1yC,cACJmzC,EAAah/B,SACb,CAAE5N,MAAO9F,KAAK2yC,cACd3yC,KAAKV,MAAM2P,YAKV2jC,EA5Gc,CA6GrB,IAAMluC,WAER,mBAASkuC,GAET,IAAIzkC,EAAI,aAGJ9I,EAAa,IAAMA,gBAEG,IAAfA,IACTA,EAAa,SAAoByjC,GAC/B,OAAOA,IAIX,IAAIllC,EAAOyB,GAAW,SAAUuuC,EAAOvxC,GACrC,IAAIG,EAAWoxC,EAAMpxC,SACjBlD,EAAQsT,EAAyBghC,EAAO,CAAC,aAE7C,OAAO,IAAMr0C,cACXiyC,EAAYpkB,SACZ,MACA,SAAUymB,GACOA,EAAM/E,SAArB,IACID,EAAUgF,EAAMhF,QACpB,OAAO,IAAMtvC,cACXC,EACA,MACA,SAAUs0C,GACR,IAAIp0C,EAAWo0C,EAAMp0C,SACjBzC,EAAW62C,EAAM72C,SAEjBqE,EAAKhC,EAAMgC,GACXT,EAAQvB,EAAMuB,MACd9D,EAAUuC,EAAMvC,QAChBg3C,EAAkBz0C,EAAM+D,SACxBA,OAA+B4G,IAApB8pC,EAAgC5lC,EAAI4lC,EAC/CC,EAAcphC,EAAyBtT,EAAO,CAAC,KAAM,QAAS,UAAW,aAEzEmF,EAAO,kBAAQnD,EAAIutC,GACnBoF,EAAc1vC,UAAUE,GACxBrE,EAAYV,EAAS0B,WAAa6yC,EAClC9zC,EAAqB,qBAAWT,EAAS0B,SAAU6yC,GAEvD,OAAO,IAAM10C,cAAc,IAAKmN,EAAS,CACvCrK,IAAKA,GAAOG,EACZ,eAAgBpC,EAAY,YAAS6J,GACpC+pC,EAAa3wC,EAAS,CAAEjD,UAAWA,EAAWD,mBAAoBA,EAAoBsE,KAAMA,EAAM/E,SAAUA,IAAa,CAC1H+E,KAAMA,EACNlB,QAAS,SAAiB2wC,GAExB,GADIF,EAAYzwC,SAASywC,EAAYzwC,QAAQ2wC,GACzCC,EAAeD,GAAQ,CACzBA,EAAM7vC,iBACN,IAAIC,EAAgBvH,EACpB,GAAuB,kBAAZA,GAAyBqD,EAAW,CAC7C,IAAIg0C,EAAkB1nC,EAAS,GAAIhN,EAASmB,OAExCwzC,GADMD,EAAgBzuC,IACViN,EAAyBwhC,EAAiB,CAAC,SAE3D9vC,EAAgB,yBAAeoI,EAAS,GAAI7L,GAAQwzC,GAEtDp3C,EAASwH,EAAM,CACb5D,MAAOA,EACP9D,QAASuH,kBAkB3B,SAASgwC,EAAgB37B,GACvB3Y,KAAK2Y,IAAMA,EARb/U,EAAKiE,YAAc,OAWnB,IAAIupC,EAAa,SAAoBl3B,GACnC,OAAOA,aAAao6B,GAGlBC,EAAa,SAAoBjzC,GACnC,MAAM,IAAIgzC,EAAgBhzC,IAGxBkzC,EAAe,SAAUC,GAG3B,SAASD,IAGP,OAFA/5B,EAAgBza,KAAMw0C,GAEf75B,EAA2B3a,KAAMy0C,EAAkB5nC,MAAM7M,KAAMwI,YAsCxE,OA3CAsS,EAAU05B,EAAcC,GASxBD,EAAavzC,UAAUY,kBAAoB,WACzC,IAAI6yC,EAAU10C,KAAKV,MACfrC,EAAWy3C,EAAQz3C,SACnBqE,EAAKozC,EAAQpzC,GAEbqzC,GADOD,EAAQp6B,KACGo6B,EAAQ33C,SAC1BA,OAA8BkN,IAApB0qC,GAAuCA,EACjD9zC,EAAQ6zC,EAAQ7zC,MAEhBguC,GADU6F,EAAQE,QACRF,EAAQ7F,SAClBvvC,EAAQsT,EAAyB8hC,EAAS,CAAC,WAAY,KAAM,OAAQ,UAAW,QAAS,UAAW,YAExGz8B,QAAQrZ,UAAU6c,MAAK,WACrB,IAAIo5B,EAAa,kBAAQvzC,EAAIutC,GAC7B5xC,EAAS,uBAAa43C,EAAYv1C,GAAQ,CAAEvC,QAASA,EAAS8D,MAAOA,QAIzE2zC,EAAavzC,UAAUgC,OAAS,WAC9B,IAAI6xC,EAAU90C,KAAKV,MAEfgC,GADWwzC,EAAQ73C,SACd63C,EAAQxzC,IAIbszC,GAHOE,EAAQx6B,KACLw6B,EAAQ/3C,QACV+3C,EAAQj0C,MACNi0C,EAAQF,SAClB/F,EAAUiG,EAAQjG,QAClBvvC,EAAQsT,EAAyBkiC,EAAS,CAAC,WAAY,KAAM,OAAQ,UAAW,QAAS,UAAW,YAEpGD,EAAa,kBAAQvzC,EAAIutC,GAE7B,OADK+F,GAASL,EAAW,uBAAaM,EAAYv1C,IAC3C,MAGFk1C,EA5CU,CA6CjB,IAAM9vC,WAEJqwC,EAAW,SAAkBz1C,GAC/B,OAAO,IAAMC,cACXiyC,EAAYpkB,SACZ,MACA,SAAU4nB,GACR,IAAInG,EAAUmG,EAAMnG,QACpB,OAAO,IAAMtvC,cACXC,EACA,MACA,SAAUmyC,GACR,OAAO,IAAMpyC,cAAci1C,EAAc9nC,EAAS,GAAIilC,EAAiB,CAAE9C,QAASA,GAAWvvC,WAanG21C,EAAQ,SAAeC,GACzB,IAAIt4C,EAAOs4C,EAAMt4C,KACbqS,EAAWimC,EAAMjmC,SACrB,OAAO,IAAM1P,cACXiyC,EAAYpkB,SACZ,MACA,SAAU+nB,GACR,IAAItG,EAAUsG,EAAMtG,QACpB,OAAO,IAAMtvC,cACXC,EACA,MACA,SAAU41C,GACR,IAAIn4C,EAAWm4C,EAAOn4C,SAClByC,EAAW01C,EAAO11C,SAElB21C,EAAe,kBAAQz4C,EAAMiyC,GAC7B/yB,EAAS,gBAAMu5B,EAAc31C,EAAS0B,UAC1C,OAAO6N,EAAS,CACdhS,SAAUA,EACVyC,SAAUA,EACVmiB,MAAO/F,EAASpP,EAAS,GAAIoP,EAAOtQ,OAAQ,CAC1CmN,IAAKmD,EAAOnD,IACZ/b,KAAMA,IACH,cAWbgU,EAAc,WAChB,IAAIwM,EAAU,qBAAWwzB,GAEzB,IAAKxzB,EACH,MAAM,IAAIjI,MAAM,8JAGlB,OAAOiI,EAAQ1d,UAGb41C,EAAc,WAChB,IAAIl4B,EAAU,qBAAWwzB,GAEzB,IAAKxzB,EACH,MAAM,IAAIjI,MAAM,8JAGlB,OAAOiI,EAAQngB,UAGbs4C,EAAY,WACd,IAAIn4B,EAAU,qBAAWo0B,GAEzB,IAAKp0B,EACH,MAAM,IAAIjI,MAAM,4JAGlB,IAAIzV,EAAWkR,IAEXu8B,EAAU,gBAAM/vB,EAAQ0xB,SAAUpvC,EAAS0B,UAE/C,OAAO+rC,EAAUA,EAAQ3hC,OAAS,MAGhCgqC,EAAW,SAAkB54C,GAC/B,IAAKA,EACH,MAAM,IAAIuY,MAAM,4EAElB,IAAIiI,EAAU,qBAAWo0B,GAEzB,IAAKp0B,EACH,MAAM,IAAIjI,MAAM,2JAGlB,IAAIzV,EAAWkR,IAEXykC,EAAe,kBAAQz4C,EAAMwgB,EAAQyxB,SACrC/yB,EAAS,gBAAMu5B,EAAc31C,EAAS0B,UAC1C,OAAO0a,EAASpP,EAAS,GAAIoP,EAAOtQ,OAAQ,CAC1CmN,IAAKmD,EAAOnD,IACZ/b,KAAMA,IACH,MAKH64C,EAAe,SAAsBhtB,GACvC,OAAOA,EAAI1rB,QAAQ,eAAgB,KAGjCq1C,EAAc,SAASA,EAAYtD,GACrC,OAAO,SAAU9uB,GACf,IAAKA,EACH,OAAO,KAGT,GAAIA,EAAQ9X,OAAS,IAAM4L,UAAYkM,EAAQ1gB,MAAM2P,SACnD,OAAO,IAAMoP,SAASpT,IAAI+U,EAAQ1gB,MAAM2P,SAAUmjC,EAAYtD,IAQhE,GANE9uB,EAAQ1gB,MAAM1C,MAAQojB,EAAQ1gB,MAAMpC,SAAW8iB,EAAQ9X,OAAS6sC,GAAuN,KAAU,GAEhS/0B,EAAQ9X,OAAS6sC,GAAc/0B,EAAQ1gB,MAAMgb,MAAS0F,EAAQ1gB,MAAMgC,IAAqN,KAAU,GAEnS0e,EAAQ9X,OAAS6sC,GAAa,2BAAiB/0B,EAAQ1gB,MAAMgb,KAAM0F,EAAQ1gB,MAAMgC,KAA4O,KAAU,GAEtU0e,EAAQ1gB,MAAMpC,QAChB,MAAO,CAAE4I,MAAOka,EAAS9iB,SAAS,GAGpC,IAAIw4C,EAAc11B,EAAQ9X,OAAS6sC,EAAW/0B,EAAQ1gB,MAAMgb,KAAO0F,EAAQ1gB,MAAM1C,KAE7EA,EAAuB,MAAhB84C,EAAsB5G,EAAW2G,EAAa3G,GAAY,IAAM2G,EAAaC,GAExF,MAAO,CACL5vC,MAAOka,EACP9iB,QAAS8iB,EAAQ1gB,MAAMpC,QACvBN,KAAMojB,EAAQ1gB,MAAM2P,SAAWwmC,EAAa74C,GAAQ,KAAOA,KAK7Du3C,EAAiB,SAAwBD,GAC3C,OAAQA,EAAMlwC,kBAAqC,IAAjBkwC,EAAMnwC,UAAkBmwC,EAAMjwC,SAAWiwC,EAAMhwC,QAAUgwC,EAAM/vC,SAAW+vC,EAAM9vC,Y,mBC3sBpHwC,EAAOpK,QAAU,syB,qBCAjB,IAAIglB,EAAmB,EAAQ,QAW/B5a,EAAOpK,QATP,SAAqC0d,EAAGC,GACtC,GAAKD,EAAL,CACA,GAAiB,iBAANA,EAAgB,OAAOsH,EAAiBtH,EAAGC,GACtD,IAAIC,EAAIlT,OAAOjG,UAAUoZ,SAASta,KAAKma,GAAG5b,MAAM,GAAI,GAEpD,MADU,WAAN8b,GAAkBF,EAAEvK,cAAayK,EAAIF,EAAEvK,YAAYvH,MAC7C,QAANgS,GAAqB,QAANA,EAAoB7F,MAAM+F,KAAKJ,GACxC,cAANE,GAAqB,2CAA2ChB,KAAKgB,GAAWoH,EAAiBtH,EAAGC,QAAxG,IAIFvT,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,kCCZzD,SAASk5C,EAAkBl0B,EAAKjT,IAClC,MAAPA,GAAeA,EAAMiT,EAAIpZ,UAAQmG,EAAMiT,EAAIpZ,QAE/C,IAAK,IAAI0B,EAAI,EAAGqmC,EAAO,IAAI77B,MAAM/F,GAAMzE,EAAIyE,EAAKzE,IAC9CqmC,EAAKrmC,GAAK0X,EAAI1X,GAGhB,OAAOqmC,EAPT,mC,qBCAAxpC,EAAOpK,QAAU,82C,mBCajBoK,EAAOpK,QAbP,WACE,GAAuB,oBAAZo5C,UAA4BA,QAAQC,UAAW,OAAO,EACjE,GAAID,QAAQC,UAAUC,KAAM,OAAO,EACnC,GAAqB,mBAAVC,MAAsB,OAAO,EAExC,IAEE,OADAx1C,QAAQU,UAAU6/B,QAAQ/gC,KAAK61C,QAAQC,UAAUt1C,QAAS,IAAI,iBACvD,EACP,MAAOsD,GACP,OAAO,IAKX+C,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,kCCZxE,IAAIiQ,EAAWxF,OAAOyF,QAAU,SAAU9J,GAAU,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CAAE,IAAI6C,EAASpE,UAAUuB,GAAI,IAAK,IAAIpE,KAAOiH,EAAc1F,OAAOjG,UAAUwB,eAAe1C,KAAK6M,EAAQjH,KAAQ9C,EAAO8C,GAAOiH,EAAOjH,IAAY,OAAO9C,GAEvPrG,EAAQiwC,cAAgB,SAAUzuC,GAChC,IAAI0B,EAAW1B,EAAK0B,SAEhBs2C,EAAar1C,OAAOs1C,kCACpBC,EAAYv1C,OAAOw1C,+BAAgC,EAEvD,GAAKH,GAAqC,mBAAhBr1C,OAAOy1C,KAAjC,CAIA,IAAIC,EAAc,GAEd32C,IACF22C,EAAc,GAAK32C,EAAS0B,SAAW1B,EAAS4W,OAAS5W,EAAS6W,MAGpE,IAAI+/B,EAAe,GACfJ,IACFI,EAAe,CAAEC,cAAc,IAGjC51C,OAAOy1C,KAAK,SAAUJ,EAAYtpC,EAAS,CACzC8pC,UAAWH,GACVC,O,kCCzBL,IAAIh5B,EAAU/I,MAAM+I,QAChBm5B,EAAUvvC,OAAOyC,KACjB+sC,EAAUxvC,OAAOjG,UAAUwB,eAC3Bk0C,EAAoC,oBAAZC,QAsE5BhwC,EAAOpK,QAAU,SAAuBmoB,EAAGC,GACzC,IACE,OAtEJ,SAASiyB,EAAMlyB,EAAGC,GAEhB,GAAID,IAAMC,EAAG,OAAO,EAEpB,GAAID,GAAKC,GAAiB,iBAALD,GAA6B,iBAALC,EAAe,CAC1D,IAEI7a,EACA1B,EACA1C,EAJAmxC,EAAOx5B,EAAQqH,GACfoyB,EAAOz5B,EAAQsH,GAKnB,GAAIkyB,GAAQC,EAAM,CAEhB,IADA1uC,EAASsc,EAAEtc,SACGuc,EAAEvc,OAAQ,OAAO,EAE/B,IAAK0B,EAAI1B,EAAgB,GAAR0B,KACf,IAAK8sC,EAAMlyB,EAAE5a,GAAI6a,EAAE7a,IAAK,OAAO,EAGjC,OAAO,EAGT,GAAI+sC,GAAQC,EAAM,OAAO,EACzB,IAAIC,EAAQryB,aAAa/M,KACrBq/B,EAAQryB,aAAahN,KACzB,GAAIo/B,GAASC,EAAO,OAAO,EAC3B,GAAID,GAASC,EAAO,OAAOtyB,EAAEuyB,WAAatyB,EAAEsyB,UAC5C,IAAIC,EAAUxyB,aAAa+W,OACvB0b,EAAUxyB,aAAa8W,OAC3B,GAAIyb,GAAWC,EAAS,OAAO,EAC/B,GAAID,GAAWC,EAAS,OAAOzyB,EAAEtK,YAAcuK,EAAEvK,WACjD,IAAI1Q,EAAO8sC,EAAQ9xB,GAEnB,IADAtc,EAASsB,EAAKtB,UACCouC,EAAQ7xB,GAAGvc,OAAQ,OAAO,EAEzC,IAAK0B,EAAI1B,EAAgB,GAAR0B,KACf,IAAK2sC,EAAQ32C,KAAK6kB,EAAGjb,EAAKI,IAAK,OAAO,EAMxC,GAAI4sC,GAAkBhyB,aAAaiyB,SAAWhyB,aAAagyB,QAAS,OAAOjyB,IAAMC,EAEjF,IAAK7a,EAAI1B,EAAgB,GAAR0B,KAGf,KAAY,YAFZpE,EAAMgE,EAAKI,KAEa4a,EAAE0yB,UAQnBR,EAAMlyB,EAAEhf,GAAMif,EAAEjf,KAAO,OAAO,EAMvC,OAAO,EAGT,OAAOgf,GAAMA,GAAKC,GAAMA,EAMfiyB,CAAMlyB,EAAGC,GAChB,MAAOpJ,GACP,GAAIA,EAAM87B,SAAW97B,EAAM87B,QAAQz1B,MAAM,sBAAyC,aAAlBrG,EAAMuiB,OAOpE,OADA74B,QAAQC,KAAK,mEAAoEqW,EAAMpT,KAAMoT,EAAM87B,UAC5F,EAIT,MAAM97B,K,mBC1FV,SAAShV,EAAQK,GAiBf,MAdsB,mBAAX0T,QAAoD,iBAApBA,OAAOC,UAChD5T,EAAOpK,QAAUgK,EAAU,SAAiBK,GAC1C,cAAcA,GAGhBD,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,IAExEmK,EAAOpK,QAAUgK,EAAU,SAAiBK,GAC1C,OAAOA,GAAyB,mBAAX0T,QAAyB1T,EAAI8I,cAAgB4K,QAAU1T,IAAQ0T,OAAOtZ,UAAY,gBAAkB4F,GAG3HD,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,GAGnE+J,EAAQK,GAGjBD,EAAOpK,QAAUgK,EACjBI,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,kCChBzD,SAASgO,EAAYge,EAAK1qB,GACvC,YADoD,IAAbA,MAAa,IAC/CA,EAID0qB,IAAQ1qB,EACJ,IAGJ0qB,EAAI3qB,WAAcC,EAAlB,KACK0qB,EAAInqB,MAAMP,EAAOsK,QAGnBogB,EAXEA,EAPX,mC,kCCEAjsB,EAAQC,YAAa,EACrBD,EAAQoB,UAER,SAAmBhB,GACjB,IAAIwE,EAAWxE,GAAQ,IACnB0Z,EAAS,GACTC,EAAO,GACPghC,EAAYn2C,EAASgN,QAAQ,MAEd,IAAfmpC,IACFhhC,EAAOnV,EAASmX,OAAOg/B,GACvBn2C,EAAWA,EAASmX,OAAO,EAAGg/B,IAGhC,IAAIl/B,EAAcjX,EAASgN,QAAQ,MAEd,IAAjBiK,IACF/B,EAASlV,EAASmX,OAAOF,GACzBjX,EAAWA,EAASmX,OAAO,EAAGF,IAGhC,MAAO,CACLjX,SAAUA,EACVkV,OAAmB,MAAXA,EAAiB,GAAKA,EAC9BC,KAAe,MAATA,EAAe,GAAKA,K,kCC1B9B,kDACe,SAASihC,EAAe/hC,EAAUC,GAC/CD,EAASxU,UAAYiG,OAAOsG,OAAOkI,EAAWzU,WAC9CwU,EAASxU,UAAU0O,YAAc8F,EACjC,YAAeA,EAAUC,K,uWCqDrB+hC,EAzDU,SAAUC,GACxB,GAAI,oBAAO3iC,SACT,OAAO,EAET,IAAM4iC,EAAW5iC,SAASxV,cAAT,QACjB,IACE,GAAIo4C,EAASC,SAAW,mBAAOD,EAASC,QAAQC,SAC9C,OAAOF,EAASC,QAAQC,SAASH,GAEnC,MAAO/7B,GACP,OAAO,EAET,OAAO,EA6CyBm8B,CAAQ,YA1Cb,SAAU5sB,EAAK5lB,GAC1C,OAAO,IAAI2S,SAAQ,SAACrZ,EAAS8f,GAC3B,GAAI,oBAAO3J,SAAX,CAKA,IAAMyX,EAAOzX,SAASxV,cAAT,QACbitB,EAAKurB,aAAL,kBACAvrB,EAAKurB,aAAL,OAA0B7sB,GAE1BhkB,OAAOyC,KAAKrE,GAAS3C,SAAQ,SAAAgD,GAC3B6mB,EAAKurB,aAAapyC,EAAKL,EAAQK,OAGjC6mB,EAAKwrB,OAASp5C,EACd4tB,EAAKyrB,QAAUv5B,GAGb3J,SAASmjC,qBAAT,QAAsC,IACtCnjC,SAASojC,kBAAT,UAAqC,GAAGhN,YAC5BC,YAAY5e,QAlBxB9N,QAsBsB,SAAUwM,GACpC,OAAO,IAAIjT,SAAQ,SAACrZ,EAAS8f,GAC3B,IAAM05B,EAAM,IAAIC,eAChBD,EAAIE,KAAJ,MAAgBptB,GAAK,GAErBktB,EAAIJ,OAAS,WACQ,MAAfI,EAAIxL,OACNhuC,IAEA8f,KAIJ05B,EAAIG,KAAK,UAQPC,EAAa,GAkBJC,EAhBE,SAAUvtB,EAAK5lB,GAC9B,OAAO,IAAI2S,SAAQ,SAAArZ,GACb45C,EAAWttB,GACbtsB,IAIF64C,EAA0BvsB,EAAK5lB,GAC5BmW,MAAK,WACJ7c,IACA45C,EAAWttB,IAAO,KAEnBxP,OAAM,mB,imBCpEN,IAAMmxB,EAAqB,CAIhC13B,MAAM,QAINujC,QAAQ,WAGJC,EAAgB,SAAAxR,GAAC,OAAKA,GAAKA,EAAEjqC,SAAYiqC,GAQzCyR,EAAoB,SAAAh8C,GACxB,IAP8BijC,EAQ9B,qBADsB,MAAJjjC,EAAA,QALlBijC,GADAA,EAAI,OAD0BA,EAOqCjjC,GAN7D,GAAaijC,EAAEvhC,MAAM,GAAKuhC,GAC1BxhC,SAAF,KAAkBwhC,EAAEvhC,MAAM,GAAI,GAAKuhC,GAMvC,mBAGF,SAASgZ,EAAQ3tB,EAAK4tB,GACpB,YADoC,IAAhBA,MAAgB,OAC7B,IAAI7gC,SAAQ,SAACrZ,EAAS8f,GAC3B,IAAM05B,EAAM,IAAIC,eAChBD,EAAIE,KAAKQ,EAAQ5tB,GAAK,GACtBktB,EAAIW,mBAAqB,WACD,GAAlBX,EAAI9vB,YACN1pB,EAAQw5C,IAGZA,EAAIG,KAAK,SAIb,IAucIt2C,EAxbE+2C,EAAkB,SAACC,EAAUnwC,QAAqB,IAArBA,MAAY,MAC7C,IAAMyY,EAAO,CACX23B,mBAAoBD,EAASC,mBAC7Bt8C,KAAMq8C,EAASr8C,KACfkwC,uBAAwBmM,EAASnM,uBACjC5hC,UAAW+tC,EAAS/tC,UACpBiuC,kBAAmBF,EAASE,mBAG9B,MAAO,CACLrwC,YACAkY,KAAMi4B,EAASn9B,OACfyF,SAIS63B,EAAb,WACE,WAAYC,EAAehvC,GAAa,KA0BxCivC,wBAA0B,IAAIlvC,IAV5BpK,KAAKu5C,OAAS,IAAInvC,IAClBpK,KAAKw5C,WAAa,IAAIpvC,IACtBpK,KAAKy5C,cAAgB,GACrBz5C,KAAK05C,WAAa,IAAItvC,IACtBpK,KAAK25C,kBAAoB,IAAIC,IAC7B55C,KAAK65C,kBAAoB,IAAID,IAC7B55C,KAAKq5C,cAAgBA,EACrBzuC,YAAcP,GAxBlB,2BA6BEyvC,YAAA,SAAY5uB,GAAM,IAAD,OACX6uB,EAAkB/5C,KAAKs5C,wBAAwBvyC,IAAImkB,GAQvD,OANK6uB,IACHA,EAAkBlB,EAAQ3tB,EAAD,OACzBlrB,KAAKs5C,wBAAwBhyC,IAAI4jB,EAAK6uB,IAIjCA,EACJt+B,MAAK,SAAAu+B,GAEJ,OADA,EAAKV,wBAAwBW,OAAO/uB,GAC7B8uB,KAERt+B,OAAM,SAAAC,GAEL,MADA,EAAK29B,wBAAwBW,OAAO/uB,GAC9BvP,MA7Cd,EAiDE8yB,aAAA,SAAaptB,GACXrhB,KAAKqhB,UAAYA,EACjBrhB,KAAKk6C,iBAAmB74B,EAAU,0BAA0B84B,MAAK,SAAAx1B,GAAC,OAAIA,MAnD1E,EAsDEy1B,kBAAA,SAAkBC,GAAU,IAAD,OACjBjL,EAA0BiL,EAA1BjL,SADiB,EACSiL,EAAhBC,eADO,MACG,EADH,EAEnBpvB,EAAM0tB,EAAkBxJ,GAC9B,OAAOpvC,KAAK85C,YAAY5uB,GAAKzP,MAAK,SAAA28B,GAAQ,IAChCxL,EAAyBwL,EAAzBxL,OAAQ2N,EAAiBnC,EAAjBmC,aAGhB,GAAe,MAAX3N,EACF,IACE,IAAM4N,EAAcv0C,KAAKC,MAAMq0C,GAC/B,QAAyBtwC,IAArBuwC,EAAY59C,KACd,MAAM,IAAIuY,MAAJ,iCAGR,OAAOjO,OAAOyF,OAAO0tC,EAAS,CAC5BzN,OAAQC,EAAmB6L,QAC3B+B,QAASD,IAEX,MAAO7+B,IAMX,OAAe,MAAXixB,GAA6B,MAAXA,EAER,cAARwC,EACKloC,OAAOyF,OAAO0tC,EAAS,CAC5BzN,OAAQC,EAAmB13B,QAMxB,EAAKilC,kBACVlzC,OAAOyF,OAAO0tC,EAAS,CAAEjL,SAAS,YAAcsL,UAAU,KAK/C,MAAX9N,EACK1lC,OAAOyF,OAAO0tC,EAAS,CAC5BzN,OAAQC,EAAmB13B,QAK3BmlC,EAAU,EACL,EAAKF,kBACVlzC,OAAOyF,OAAO0tC,EAAS,CAAEC,QAASA,EAAU,KAKzCpzC,OAAOyF,OAAO0tC,EAAS,CAC5BzN,OAAQC,EAAmB13B,YA7GnC,EAkHEwlC,iBAAA,SAAiBvM,GAAU,IAAD,OAClBgB,EAAW3jC,YAAS2iC,GAC1B,GAAIpuC,KAAK05C,WAAW5yC,IAAIsoC,GAAW,CACjC,IAAM6J,EAAWj5C,KAAK05C,WAAW3yC,IAAIqoC,GAEnC,OAAOn3B,QAAQrZ,QAAQq6C,GAI3B,OAAOj5C,KAAKo6C,kBAAkB,CAAEhL,aAAY3zB,MAAK,SAAAw9B,GAG/C,OAFA,EAAKS,WAAWpyC,IAAI8nC,EAAU6J,GAEvBA,MA9Hb,EAkIEpuC,cAAA,SAAcujC,GACZ,OAAOvjC,YAAcujC,IAnIzB,EAuIEzB,SAAA,SAASyB,GAAU,IAAD,OACVgB,EAAW3jC,YAAS2iC,GAC1B,GAAIpuC,KAAKu5C,OAAOzyC,IAAIsoC,GAAW,CAC7B,IAAM7tB,EAAOvhB,KAAKu5C,OAAOxyC,IAAIqoC,GAE3B,OAAOn3B,QAAQrZ,QAAQ2iB,EAAKk5B,SAIhC,GAAIz6C,KAAKw5C,WAAW1yC,IAAIsoC,GACtB,OAAOpvC,KAAKw5C,WAAWzyC,IAAIqoC,GAG7B,IAAM2K,EAAkB9hC,QAAQxG,IAAI,CAClCzR,KAAK46C,cACL56C,KAAK26C,iBAAiBvL,KACrB3zB,MAAK,SAAAo/B,GACN,IAAM/+B,EAAS++B,EAAQ,GACvB,GAAI/+B,EAAO8wB,SAAWC,EAAmB13B,MACvC,MAAO,CACLy3B,OAAQC,EAAmB13B,OAI/B,IAAI8jC,EAAWn9B,EAAO2+B,QARL,EASsCxB,EAA/CC,EATS,EASTA,mBATS,IASWC,yBATX,MAS+B,GAT/B,EAWX2B,EAAc,GAEdC,EAAwB,EAAK1B,cAAcH,GAAoBz9B,MACnE,SAAA3S,GAEE,IAAIiY,EAgBJ,OAjBA+5B,EAAYE,UAAY,IAAIpjC,KAEvB9O,GAGHgyC,EAAYlO,OAASC,EAAmB6L,SAChB,IAApB58B,EAAO4+B,WACTI,EAAYJ,UAAW,GAEzBzB,EAAW/xC,OAAOyF,OAAOssC,EAAU,CACjCnM,uBAAwB+N,EAAQ,GAC5BA,EAAQ,GAAG/N,uBADS,KAI1B/rB,EAAgBi4B,EAAgBC,EAAUnwC,IAX1CgyC,EAAYlO,OAASC,EAAmB13B,MAcnC4L,KAILk6B,EAA0BhjC,QAAQxG,IACtC0nC,EAAkBluC,KAAI,SAAAiwC,GAEpB,GAAI,EAAKzB,cAAcyB,GAAkB,CACvC,IAAMV,EAAc,EAAKf,cAAcyB,GACvC,MAAO,CAAEA,kBAAiBV,eAG5B,OAAO,EAAKV,YAAL,mBACgCoB,EADhC,SAELz/B,MAAK,SAAA28B,GACL,IAAMoC,EAAcv0C,KAAKC,MAAMkyC,EAAImC,cACnC,MAAO,CAAEW,kBAAiBV,sBAG9B/+B,MAAK,SAAAwzB,GACL,IAAMkM,EAAwB,GAO9B,OALAlM,EAAmBtsC,SAAQ,YAAuC,IAApCu4C,EAAmC,EAAnCA,gBAAiBV,EAAkB,EAAlBA,YAC7CW,EAAsBD,GAAmBV,EACzC,EAAKf,cAAcyB,GAAmBV,KAGjCW,KAGT,OAAOljC,QAAQxG,IAAI,CAACspC,EAAuBE,IAA0Bx/B,MACnE,YAA0C,IACpCg/B,EADJ15B,EAAuC,KAAxBkuB,EAAwB,KAavC,OAXIluB,IACF05B,EAAO,OAAQ15B,GAAR,IAAuBkuB,uBAC9B6L,EAAYL,QAAUA,EACtBjpC,IAAQM,KAAR,0BAAwC,CACtCyP,KAAMk5B,EACN15B,cAAe05B,KAInB,EAAKlB,OAAOjyC,IAAI8nC,EAAU0L,GAEnBL,QAgBb,OAXAV,EACGt+B,MAAK,SAAAu+B,GACJ,EAAKR,WAAWS,OAAO7K,MAExB1zB,OAAM,SAAAF,GAEL,MADA,EAAKg+B,WAAWS,OAAO7K,GACjB5zB,KAGVxb,KAAKw5C,WAAWlyC,IAAI8nC,EAAU2K,GAEvBA,GAnPX,EAuPE7L,aAAA,SAAaE,GACX,IAAMgB,EAAW3jC,YAAS2iC,GAC1B,GAAIpuC,KAAKu5C,OAAOzyC,IAAIsoC,GAElB,OADiBpvC,KAAKu5C,OAAOxyC,IAAIqoC,GAAUqL,SA1PjD,EAgQEW,eAAA,SAAehM,GAEb,QAjSkC,WACpC,GACE,eAAgBrnB,gBAChB,IAAOA,UAAUszB,WACjB,CACA,IAAKtzB,UAAUszB,WAAWC,eAArB,IAA0CxtC,SAA1C,MACH,OAAO,EAET,GAAIia,UAAUszB,WAAWE,SACvB,OAAO,EAGX,OAAO,EAqRAC,KAKDx7C,KAAKu5C,OAAOzyC,IAAIsoC,IAvQxB,EA8QEqJ,SAAA,SAASrJ,GAAW,IAAD,OACjB,IAAKpvC,KAAKo7C,eAAehM,GACvB,OAAO,EAWT,GANKpvC,KAAK25C,kBAAkB7yC,IAAIsoC,KAC9BpvC,KAAKqhB,UAAL,qBAAqC,CAAEjgB,SAAUguC,IACjDpvC,KAAK25C,kBAAkBvsC,IAAIgiC,IAIzBpvC,KAAKk6C,iBACP,OAAO,EAGT,IAAMuB,EAAWhwC,YAAS2jC,GAU1B,OAPApvC,KAAK07C,WAAWD,GAAUhgC,MAAK,WACxB,EAAKo+B,kBAAkB/yC,IAAIsoC,KAC9B,EAAK/tB,UAAL,yBAAyC,CAAEjgB,SAAUguC,IACrD,EAAKyK,kBAAkBzsC,IAAIgiC,QAIxB,GAzSX,EA4SEsM,WAAA,SAAWtM,GAAW,IAAD,OACbuM,EAAc/C,EAAkBxJ,GACtC,OAAOwM,EAAeD,EAAa,CACjCE,YAAY,YACZC,GAAG,UACFrgC,MAAK,kBAGN,EAAKk/B,iBAAiBvL,OApT5B,EAwTEtrC,SAAA,SAASsqC,GACPpuC,KAAK2sC,SAASyB,IAzTlB,EA4TE2N,2BAAA,SAA2B3N,GACzB,IAAMgB,EAAW3jC,YAAS2iC,GACpB7sB,EAAOvhB,KAAK05C,WAAW3yC,IAAIqoC,GACjC,GAAI7tB,EAAM,CACR,IAAMR,EAAgBi4B,EAAgBz3B,EAAKk5B,SAE3C,MAAM,GAAN,mBACKuB,EAAoBj7B,EAAcQ,KAAK23B,qBAD5C,CAEEN,EAAkBxJ,KAGpB,OAAO,MAvUb,EA2UE6M,eAAA,SAAe7N,GACb,IAAMgB,EAAW3jC,YAAS2iC,GACpB7sB,EAAOvhB,KAAKu5C,OAAOxyC,IAAIqoC,GAC7B,OAAQ7tB,GAAQA,EAAKm5B,UA9UzB,EAiVEE,YAAA,SAAYN,GAAc,IAAD,OACvB,YADuB,IAAbA,MAAU,GACbt6C,KAAK85C,YAAL,4BAA+Dr+B,MACpE,SAAA28B,GAAQ,IAGF8D,EAFItP,EAAyBwL,EAAzBxL,OAAQ2N,EAAiBnC,EAAjBmC,aAIhB,GAAe,MAAX3N,GAAkB0N,EAAU,EAE9B,OAAO,EAAKM,YAAYN,EAAU,GAIpC,GAAe,MAAX1N,EACF,IACE,IAAM4N,EAAcv0C,KAAKC,MAAMq0C,GAC/B,QAA2CtwC,IAAvCuwC,EAAY1N,uBACd,MAAM,IAAI33B,MAAJ,iCAGR+mC,EAAU1B,EACV,MAAO7+B,IAKX,OAAOugC,MA3Wf,KAiXMF,EAAsB,SAAA9C,GAAkB,OAC3Cv4C,OAAOw7C,gBAAgBjD,IAAuB,IAAIjuC,KACjD,SAAAmxC,GAAK,MAAI79C,GAAkB69C,MAGlB9N,EAAb,YACE,WAAYC,EAAelkC,GAAY,OASrC,aARsB,SAAAgyC,GAAS,OAC7B9N,EAAch7B,WAAW8oC,GACrB9N,EAAch7B,WAAW8oC,KACtB5gC,KAAKk9B,GAELj9B,OAAM,kBAAM,QACfzD,QAAQrZ,YAEOyL,IATgB,KADzC,4CAaEqxC,WAAA,SAAWtM,GACT,OAAO,YAAMsM,WAAN,UAAiBtM,GAAU3zB,MAAK,SAAAK,GACrC,GAAIA,EAAO8wB,SAAWC,EAAmB6L,QACvC,OAAOzgC,QAAQrZ,UAEjB,IAAMq6C,EAAWn9B,EAAO2+B,QAClB4B,EAAYpD,EAASC,mBACrBoD,EAAgBN,EAAoBK,GAC1C,OAAOpkC,QAAQxG,IAAI6qC,EAAcrxC,IAAI2wC,IAAiBngC,MAAK,kBAAMw9B,SArBvE,EAyBE0B,iBAAA,SAAiBvM,GACf,OAAO,YAAMuM,iBAAN,UAAuBvM,GAAS3yB,MAAK,SAAA8X,GAC1C,OAAIA,EAAKmnB,SAGA7B,EAAQzK,EAAD,QAAkB3yB,MAAK,SAAA28B,GACnC,OAAmB,MAAfA,EAAIxL,OAIC,CACLA,OAAQC,EAAmB13B,OAMxBoe,KAGJA,MA7Cb,GAAgC6lB,GAoDnB5K,EAAY,SAAA+N,GACvBt6C,EAAWs6C,GAGAj7B,EAAe,CAI1Bk7B,wBAAyB,SAAApO,GAIvB,OAHAlpC,QAAQC,KAAR,wEAGOlD,EAAS8H,EAAE4iC,SAASyB,IAE7BqO,4BAA6B,SAAArO,GAI3B,OAHAlpC,QAAQC,KAAR,gFAGOlD,EAAS8H,EAAEmkC,aAAaE,IAEjC3sC,QAAS,SAAA2sC,GAAO,OAAInsC,EAASw2C,SAASrK,IAGtC2N,2BAA4B,SAAA3N,GAAO,OACjCnsC,EAAS85C,2BAA2B3N,IACtCzB,SAAU,SAAAyB,GAAO,OAAInsC,EAAS0qC,SAASyB,IACvCF,aAAc,SAAAE,GAAO,OAAInsC,EAASisC,aAAaE,IAC/CqK,SAAU,SAAArK,GAAO,OAAInsC,EAASw2C,SAASrK,IACvC6N,eAAgB,SAAA7N,GAAO,OAAInsC,EAASg6C,eAAe7N,IACnDtqC,SAAU,SAAAsqC,GAAO,OAAInsC,EAAS6B,SAASsqC,IACvCwM,YAAa,kBAAM34C,EAAS24C,gBAGft5B,YAER,SAAS4tB,IACd,OAAIjtC,EACKA,EAASw3C,cAET,K,2JC5hBPiD,EAAUngD,UAAd,QACQ2K,mBADyK,G,qlBC4BjL,IAAMy1C,EAAN,GAQAC,mBAAmB,YAAkC,IAAD,IAA9BC,cAA8B,MAArB,GAAqB,EAAjBtpC,EAAiB,EAAjBA,WACjCrM,2BAAmC,YAAiC,IAA/B41C,EAA8B,KAAfp4C,EAAe,KAC7Di4C,EAAJ,GACEA,OAAyB,CAAEI,MAAOF,EAAT,GAAgCn4C,cAEzDi4C,KAAqC,CACnC,CAAEI,MAAOF,EAAT,GAAgCn4C,oBAMxC,IAAM6O,EAAarM,OAAA,gBACZ,YAAkB,IAAD,EAAfkB,EAAe,KAATqZ,EAAS,KACpB,OAAO,EAAP,OApBwB,SAAAA,GAAG,OAC7B,YAA0C,IAChC/c,EAAc+c,EAAA,MAAS,gBAAGs7B,EAAH,eAAgBA,GAAQA,EAAH,MADb,UAEvC,OAAO,cAAP,IAkBUC,CACNv7B,EAAA,OAAW,CAAEs7B,WAAF,EAAoBr4C,UAAW0D,KAF9C,KAFe,QAQT,cACN,OAAO,EAAP,aATJ,IAaM60C,EAAc7pC,6BAClB,gBAAe8pC,EAAf,aAAsCjuC,EAAtC,kBACE,gCAAkB8K,WAAYojC,GAC5B,2BAAa5pC,WAAU,cAF3B,OC7DW6pC,EDsEW,SAAC,GAAD,IAAGp9B,EAAH,iBAAiB,mBAAjB,K,kCExDT,IAfG,SAAqBpb,GAErC,IAAI+B,EAAQ,IAAID,QAChB,OAAO,SAAU6K,GACf,GAAI5K,EAAMG,IAAIyK,GAEZ,OAAO5K,EAAMI,IAAIwK,GAGnB,IAAIgP,EAAM3b,EAAK2M,GAEf,OADA5K,EAAMW,IAAIiK,EAAKgP,GACRA,K,kCCTX/jB,EAAQ6gD,gBAAkB9gD,EAAQ,S,mBCFlCqK,UAAiB,CAACg0B,QAAS,K,qBCA3Bp+B,EAAQC,YAAa,EACCD,EAAQ8gD,gBAAkB,CAC9CzY,KAAM,iBACNE,KAAM,iBACNJ,MAAO,mBAHT,IAKIX,EAAYxnC,EAAQwnC,UAAY,CAClCuZ,KAAM,OACN1Y,KAAM,OACN2Y,KAAM,OACNzY,KAAM,OACNW,KAAM,OACNC,KAAM,OACNzB,SAAU,WACVD,OAAQ,SACRE,MAAO,QACPQ,MAAO,SAiBL8Y,GAfkBjhD,EAAQkhD,gBAAkBx2C,OAAOyC,KAAKq6B,GAAW/4B,KAAI,SAAU7C,GACnF,OAAO47B,EAAU57B,MAEE5L,EAAQmhD,eAAiB,CAC5CC,QAAS,UACTC,SAAU,UACVC,KAAM,OACNC,UAAW,aACXC,WAAY,YACZC,UAAW,WACXC,KAAM,OACNC,SAAU,WACVC,IAAK,MACLC,IAAK,OAEa7hD,EAAQihD,cAAgB,CAC1Ca,UAAW,YACXC,QAAS,UACTC,MAAO,YACPC,gBAAiB,kBACjBC,YAAa,cACb,aAAc,YACdC,SAAU,WACVC,SAAU,aAEOpiD,EAAQqiD,aAAe,CACxCC,cAAe,eACfC,MAAO,QACPC,0BAA2B,0BAC3BC,uBAAwB,sBACxBC,eAAgB,iBAEC1iD,EAAQ2iD,aAAej4C,OAAOyC,KAAK8zC,GAAe/vC,QAAO,SAAU7G,EAAKlB,GAEzF,OADAkB,EAAI42C,EAAc93C,IAAQA,EACnBkB,IACN,IACqBrK,EAAQ4iD,kBAAoB,CAACpb,EAAUE,SAAUF,EAAUC,OAAQD,EAAUG,OAC9E3nC,EAAQ6iD,iBAAmB,qB,kCCrDlD,IAAIxgC,EAA0B,EAAQ,QAElCviB,EAAyB,EAAQ,QAErCE,EAAQC,YAAa,EACrBD,EAAQyV,qBAAkB,EAE1B,IAAI3U,EAAYhB,EAAuB,EAAQ,SAE3Ce,EAAkBf,EAAuB,EAAQ,SAEjDqY,EAAQkK,EAAwB,EAAQ,SAExCygC,EAAYhjD,EAAuB,EAAQ,SAE3CiB,EAAajB,EAAuB,EAAQ,SAE5CwU,EAAiB,EAAQ,QAEzBrT,EAAU,EAAQ,QAIlBkH,EAAY,CACd46C,UAAWhiD,EAAWL,QAAQ8B,OAAO6F,WACrCwa,mBAAoB9hB,EAAWL,QAAQ0H,KACvCqK,SAAU1R,EAAWL,QAAQ8iB,QAAQnb,YAInC26C,EAA6C,SAAU3/C,GAGzD,SAAS2/C,EAA8BlgD,GAUrC,OAPQO,EAAiBE,KAAKC,KAAMV,IAAUU,MALhD,EAAI3C,EAAgBH,SAASsiD,EAA+B3/C,GAe5D,IAAImB,EAASw+C,EAA8Bv+C,UAuB3C,OArBAD,EAAOa,kBAAoB,WACzB,IAAIU,EAASvC,KAGTuf,EAAO+/B,EAAUpiD,QAAQuiD,YAAYz/C,MAErCmD,EAAcnD,KAAKV,MACnBI,EAAWyD,EAAYzD,SACvB6/C,EAAYp8C,EAAYo8C,UAC5B,GAAKhgC,EAAL,CACAA,EAAK/H,iBAAiB,UAAU,WAC9BjV,EAAOjD,MAAM8d,QAAQjX,KAAKzG,EAAU6/C,EAAWhgC,EAAKlO,cAEtD,IAAIH,EAAWlR,KAAKV,MAAM8d,QAAQ1X,KAAKhG,EAAU6/C,GACjDhgC,EAAKpO,SAAS,EAAGD,GAAY,KAG/BlQ,EAAOiC,OAAS,WACd,OAAOjD,KAAKV,MAAM2P,UAGbuwC,EAvCwC,CAwC/C7qC,EAAMjQ,WAEJuN,EAAkB,SAAyB3S,GAC7C,OAAoBqV,EAAMpV,cAAc9B,EAAQ+B,SAAU,MAAM,SAAUxB,GACxE,IAAI0B,EAAW1B,EAAK0B,SACpB,OAAoBiV,EAAMpV,cAAcuR,EAAeC,cAAcqc,SAAU,MAAM,SAAUhQ,GAC7F,OAAoBzI,EAAMpV,cAAcigD,GAA+B,EAAIliD,EAAUJ,SAAS,GAAIoC,EAAO,CACvG8d,QAASA,EACT1d,SAAUA,YAMlBlD,EAAQyV,gBAAkBA,EAC1BA,EAAgBtN,UAAYA,G,kCCrF5B,IAAIrI,EAAyBC,EAAQ,QAErCC,EAAQC,YAAa,EACrBD,EAAQU,QAyLR,SAAkB8Q,EAAMyL,EAAenX,GACrC,IAAIo9C,EAAeC,EAAyBr9C,EAAImX,GAEhD,OADAzL,EAAKwJ,iBAAiB,QAASkoC,GACxB,WACL,OAAO1xC,EAAKyJ,oBAAoB,QAASioC,KA5L7CljD,EAAQmjD,yBAA2BnjD,EAAQojD,qBAAuBpjD,EAAQqjD,sBAAwBrjD,EAAQsjD,oBAAsBtjD,EAAQujD,0BAA4BvjD,EAAQwjD,gCAAkCxjD,EAAQyjD,kBAAoBzjD,EAAQ0jD,8BAAgC1jD,EAAQ2jD,gBAAkB3jD,EAAQ4jD,6BAA0B,EAE9U,IAAIC,EAAsB/jD,EAAuBC,EAAQ,SAErD+c,EAAU/c,EAAQ,QAElB6jD,EAA0B,SAAiClM,GAC7D,OAAwB,IAAjBA,EAAMnwC,QAAgBmwC,EAAMhwC,QAAUgwC,EAAM/vC,SAAW+vC,EAAMjwC,SAAWiwC,EAAM9vC,UAIvF5H,EAAQ4jD,wBAA0BA,EAElC,IAAID,EAAkB,SAAyB/+C,GAC7C,MAAuB,MAAhBA,EAAS,GAAaA,EAAW,IAAMA,GAGhD5E,EAAQ2jD,gBAAkBA,EAE1B,IAAID,EAAgC,SAAuChM,GACzE,OAAOA,EAAMlwC,kBAGfxH,EAAQ0jD,8BAAgCA,EAExC,IAAID,EAAoB,SAA2B1gC,GACjD,KAAOA,EAAK4rB,WAAY5rB,EAAOA,EAAK4rB,WAClC,GAAoC,MAAhC5rB,EAAK+gC,SAASp3B,cAChB,OAAO3J,EAIX,OAAO,MAGT/iB,EAAQyjD,kBAAoBA,EAE5B,IAAID,EAAkC,SAAyCO,GAC7E,OAEoC,IAAlCA,EAAOC,aAAa,WAUH,MAAjBD,EAAO19C,QAKP,CAAC,QAAS,IAAIiL,SAASyyC,EAAO19C,SAIZ,YAAlB09C,EAAO19C,UAA0B09C,EAAOE,cAAcC,YAAY1kB,QAClEukB,EAAOE,cAAcC,YAAY1kB,SAAWukB,EAAOE,cAAcC,cAAkC,SAAlBH,EAAO19C,UAAuB09C,EAAOE,cAAcC,YAAYjV,KAChJ8U,EAAOE,cAAcC,YAAYjV,MAAQ8U,EAAOE,cAAcC,cAIlElkD,EAAQwjD,gCAAkCA,EAE1C,IAAID,EAA4B,SAAmCQ,GACjE,OAKsC,IAApCA,EAAOC,aAAa,cAKwB,IAA5CR,EAAgCO,IAKpC/jD,EAAQujD,0BAA4BA,EAEpC,IAAID,EAAsB,SAA6BtpC,EAAQmqC,GAC7D,OAAOnqC,EAAOC,WAAakqC,EAAYlqC,UAEvCD,EAAOE,OAASiqC,EAAYjqC,MAG9Bla,EAAQsjD,oBAAsBA,EAE9B,IAAID,EAAwB,SAA+Bc,EAAaC,GAEtE,OAWiE,IAA/DA,EAAexnC,KAAK+mC,EAAgBQ,EAAYv/C,aAKS,IAAzDu/C,EAAYv/C,SAASkV,OAjBM,kCAqB/B9Z,EAAQqjD,sBAAwBA,EAEhC,IAAID,EAAuB,SAA8BppC,EAAQmqC,GAC/D,MAA4B,KAArBA,EAAYpqC,OAKM,KAAzBoqC,EAAYv/C,UAEZu/C,EAAYv/C,WAAaoV,EAAOpV,WAGlC5E,EAAQojD,qBAAuBA,EAE/B,IAAID,EAA2B,SAAkCkB,EAAapnC,GAC5E,OAAO,SAAUy6B,GACf,GAAIvzC,OAAOsqB,mBAAoB,OAAO,EACtC,GAAIm1B,EAAwBlM,GAAQ,OAAO,EAC3C,GAAIgM,EAA8BhM,GAAQ,OAAO,EACjD,IAAI4M,EAAgBb,EAAkB/L,EAAMrxC,QAC5C,GAAqB,MAAjBi+C,EAAuB,OAAO,EAClC,GAAIf,EAA0Be,GAAgB,OAAO,EAGrD,IAAIH,EAAc5rC,SAASxV,cAAc,KAGd,KAAvBuhD,EAAcr8C,OAChBk8C,EAAYl8C,KAAOq8C,EAAcr8C,MAG/B,sBAAuB9D,QAAUmgD,EAAcr8C,gBAAgBs8C,oBACjEJ,EAAYl8C,KAAOq8C,EAAcr8C,KAAKu8C,SASxC,IAAIxqC,EAASzB,SAASxV,cAAc,KAEpC,GADAiX,EAAO/R,KAAO9D,OAAOjB,SAAS+E,MACmB,IAA7Cq7C,EAAoBtpC,EAAQmqC,GAAwB,OAAO,EAE/D,IAAIC,EAAiB,IAAIllB,OAAO,KAAM,EAAI2kB,EAAoBnjD,UAAS,EAAIoc,EAAQ5c,YAAY,OAC/F,GAAImjD,EAAsBc,EAAaC,GAAiB,OAAO,EAC/D,GAAIhB,EAAqBppC,EAAQmqC,GAAc,OAAO,EAEtD,GAAIlnC,EAAcwnC,gBACG,IAAIvlB,OAAOjiB,EAAcwnC,gBAE3B7nC,KAAKunC,EAAYv/C,UAChC,OAAO,EAIX8yC,EAAM7vC,iBAGN,IAAI68C,EAAsBf,EAAgBQ,EAAYv/C,UAAUrE,QAAQ6jD,EAAgB,KAExF,OADAC,EAAY,GAAKK,EAAsBP,EAAYrqC,OAASqqC,EAAYpqC,OACjE,IAIX/Z,EAAQmjD,yBAA2BA,G,mBC7KnC/4C,EAAOpK,QAfP,SAAyBqK,EAAKlB,EAAKG,GAYjC,OAXIH,KAAOkB,EACTK,OAAOC,eAAeN,EAAKlB,EAAK,CAC9BG,MAAOA,EACPyG,YAAY,EACZC,cAAc,EACdC,UAAU,IAGZ5F,EAAIlB,GAAOG,EAGNe,GAITD,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,qBChBxE,IAAsB0qC,EAKpBvgC,EAAOpK,SALa2qC,EAKW5qC,EAAQ,UALR4qC,EAAEjqC,SAAYiqC,G,yBCsBvCh0B,EAAkB5W,EAAQ,QAA1B4W,cAERvM,EAAOpK,QAAU2W,EACjBvM,EAAOpK,QAAQU,QAAUiW,G,mBCzBzB,IAAMkc,EAAS,CACbC,OAAQ,CACNC,WAAY,IACZ+J,QAAS,gCACT6nB,aAAc,KACdxwB,eAAe,GAEjBmC,OAAQ,CACNiB,KAAM,GACNqtB,SAAU,gCACVpyB,MAAO,gEACPqyB,UAAW,GACXxtB,QAAS,GACTC,UAAW,GAiBXnB,MAAO,CAAC,CAAEhF,KAAM,GAAInB,KAAM,KAC1BlW,OAAQ,CACNyc,SAAS,EACTE,UAAW,YACXquB,aAAcC,aACdC,iBAAkBD,mCAClBE,gBAAiBF,GAAYG,oBAGjClyB,QAAS,CAEPsB,eAAgB,CACd,cACA,aACA,mCACA,uBACA,6BACA,yBACA,kCACA,yBACA,kBACA,0BACA,oCACA,yBACA,YACA,aAEFM,aAAc,CACZ,cACA,mCACA,mCACA,uBACA,6BACA,yBACA,kCACA,yBACA,kBACA,0BACA,oCACA,0BAEFuB,MAAO,CACL,CAAEhF,KAAM,SAAUnB,KAAM,6BACxB,CAAEmB,KAAM,8BAA+BnB,KAAM,wNAC7C,CAAEmB,KAAM,kDAAmDnB,KAAM,yGACjE,CACEmB,KAAM,0BACNnB,KAAM,0DAER,CACEmB,KAAM,qBACNnB,KACE,6FAGNm1B,WAAW,EACX1xB,aAAa,EACbjB,MAAO,IAET2E,aAAc,CACZ3E,MAAO,oBACP4yB,YAAa,kDACbC,QAAS,KACT7oB,aAAc,GACd8oB,QAAS,oEAEXC,IAAK,CACHhvB,SAAS,EACTivB,SAAU,CACR55C,KAAM,oBACN65C,WAAY,aACZC,UAAW,IACXC,iBAAkB,UAClBC,YAAa,UACbvzC,QAAS,aACTgtC,YAAa,kBACbwG,MAAO,CACL,CACEnuB,IAAK,kBACLouB,MAAM,UACNp6C,KAAK,iBAOftB,EAAOpK,QAAU6yB,G,kCCnHjB,IAAIkzB,EAAmB,sBAEvB37C,EAAOpK,QAAU,SAAUisB,GACzB,GAAmB,iBAARA,EACT,MAAM,IAAIzO,UAAU,qBAGtB,OAAOyO,EAAI1rB,QAAQwlD,EAAkB,U,mBCTvC,SAAS71C,IAgBP,OAfA9F,EAAOpK,QAAUkQ,EAAWxF,OAAOyF,QAAU,SAAU9J,GACrD,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CACzC,IAAI6C,EAASpE,UAAUuB,GAEvB,IAAK,IAAIpE,KAAOiH,EACV1F,OAAOjG,UAAUwB,eAAe1C,KAAK6M,EAAQjH,KAC/C9C,EAAO8C,GAAOiH,EAAOjH,IAK3B,OAAO9C,GAGT+D,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,EACjEiQ,EAASG,MAAM7M,KAAMwI,WAG9B5B,EAAOpK,QAAUkQ,EACjB9F,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,wRCfpE,EAAiByK,OAAOjG,UAAUwB,eAClC+/C,EAAmC,wBAMhB,oBAAhBC,YAA8B,cAAgB,MACjDC,EAA4B,wBAAc,IAG1C,GAFgBF,EAAoB9uC,SAEjB,SAA0B9O,GAC/C,IAAI3B,EAAS,SAAgB3D,EAAO+C,GAClC,OAAoB,wBAAcmgD,EAAoBp1B,SAAU,MAAM,SAAUzmB,GAC9E,OAAO/B,EAAKtF,EAAOqH,EAAOtE,OAK9B,OAAoB,qBAAWY,KAQ7B0/C,EAAe,qCAGfC,EAAqB,SAA4B16C,EAAM5I,GAMzD,IAAIkV,EAAW,GAEf,IAAK,IAAI7O,KAAOrG,EACV,EAAeS,KAAKT,EAAOqG,KAC7B6O,EAAS7O,GAAOrG,EAAMqG,IAwB1B,OApBA6O,EAASmuC,GAAgBz6C,EAoBlBsM,GAGL,EAAS,SAAgB7N,EAAOrH,EAAO+M,EAAOhK,GAChD,IAAIwgD,EAAoB,OAAVx2C,EAAiB/M,EAAM21B,IAAM31B,EAAM21B,IAAI5oB,GAI9B,iBAAZw2C,QAAsD54C,IAA9BtD,EAAM8iB,WAAWo5B,KAClDA,EAAUl8C,EAAM8iB,WAAWo5B,IAG7B,IAAI36C,EAAO5I,EAAMqjD,GACbztB,EAAmB,CAAC2tB,GACpBxiD,EAAY,GAEe,iBAApBf,EAAMe,UACfA,EAAY,YAAoBsG,EAAM8iB,WAAYyL,EAAkB51B,EAAMe,WAC9C,MAAnBf,EAAMe,YACfA,EAAYf,EAAMe,UAAY,KAGhC,IAAIu0B,EAAa,YAAgBM,GAUrB,YAAavuB,EAAOiuB,EAA4B,iBAAT1sB,GACnD7H,GAAasG,EAAMhB,IAAM,IAAMivB,EAAWxsB,KAC1C,IAAIoM,EAAW,GAEf,IAAK,IAAI7O,KAAOrG,EACV,EAAeS,KAAKT,EAAOqG,IAAgB,QAARA,GAAiBA,IAAQg9C,IAC9DnuC,EAAS7O,GAAOrG,EAAMqG,IAO1B,OAHA6O,EAASnS,IAAMA,EACfmS,EAASnU,UAAYA,EACE,wBAAc6H,EAAMsM,IAKzCsuC,EAAyB,GAAiB,SAAUxjD,EAAOqH,EAAOtE,GACpE,MAAyB,mBAAd/C,EAAM21B,IACK,wBAAcytB,EAAat1B,SAAU,MAAM,SAAU/gB,GACvE,OAAO,EAAO1F,EAAOrH,EAAO+M,EAAOhK,MAIhC,EAAOsE,EAAOrH,EAAO,KAAM+C,M,gBCnHrB,MARf,WACE,IAAK,IAAI0c,EAAOvW,UAAUH,OAAQkG,EAAO,IAAIgG,MAAMwK,GAAOC,EAAO,EAAGA,EAAOD,EAAMC,IAC/EzQ,EAAKyQ,GAAQxW,UAAUwW,GAGzB,OAAO,YAAgBzQ,ICIrB,EAAM,SAAarG,EAAM5I,GAC3B,IAAIiP,EAAO/F,UAEX,GAAa,MAATlJ,IAAkB,EAAeS,KAAKT,EAAO,OAE/C,OAAO,gBAAcuN,WAAM5C,EAAWsE,GAGxC,IAAI8F,EAAa9F,EAAKlG,OAClBiM,EAAwB,IAAIC,MAAMF,GACtCC,EAAsB,GAAKwuC,EAC3BxuC,EAAsB,GAAKsuC,EAAmB16C,EAAM5I,GAEpD,IAAK,IAAIyK,EAAI,EAAGA,EAAIsK,EAAYtK,IAC9BuK,EAAsBvK,GAAKwE,EAAKxE,GAIlC,OAAO,gBAAc8C,MAAM,KAAMyH,IAI/ByuC,EAAwB,GAAiB,SAAUzjD,EAAOqH,GAU5D,IAAImF,EAASxM,EAAMwM,OAEnB,GAAsB,mBAAXA,EACT,OAAoB,wBAAc42C,EAAat1B,SAAU,MAAM,SAAU/gB,GACvE,IAAIuoB,EAAa,YAAgB,CAAC9oB,EAAOO,KACzC,OAAoB,wBAAc,EAAa,CAC7CuoB,WAAYA,EACZjuB,MAAOA,OAKb,IAAIiuB,EAAa,YAAgB,CAAC9oB,IAClC,OAAoB,wBAAc,EAAa,CAC7C8oB,WAAYA,EACZjuB,MAAOA,OAMP,EAA2B,SAAU9G,GAGvC,SAASmjD,EAAY1jD,EAAO8d,EAAS6lC,GACnC,OAAOpjD,EAAiBE,KAAKC,KAAMV,EAAO8d,EAAS6lC,IAAYjjD,KAHjE,YAAegjD,EAAanjD,GAM5B,IAAImB,EAASgiD,EAAY/hD,UAoDzB,OAlDAD,EAAOa,kBAAoB,WACzB7B,KAAK+0B,MAAQ,IAAI,IAAW,CAC1BpvB,IAAK3F,KAAKV,MAAMqH,MAAMhB,IAAM,UAC5B4lC,MAAOvrC,KAAKV,MAAMqH,MAAMouB,MAAMwW,MAC9BV,UAAW7qC,KAAKV,MAAMqH,MAAMouB,MAAM8V,YAGpC,IAAItrB,EAAOxK,SAASmuC,cAAc,sBAAwBljD,KAAKV,MAAMqH,MAAMhB,IAAM,KAAQ3F,KAAKV,MAAMs1B,WAAWxsB,KAAO,MAEzG,OAATmX,GACFvf,KAAK+0B,MAAMouB,KAAKnmD,KAAKuiB,GAGnBvf,KAAKV,MAAMqH,MAAMouB,MAAMouB,KAAK96C,SAC9BrI,KAAK+0B,MAAMyF,OAASx6B,KAAKV,MAAMqH,MAAMouB,MAAMouB,KAAK,IAGlDnjD,KAAKy5B,gBAGPz4B,EAAOU,mBAAqB,SAA4BC,GAClDA,EAAUizB,WAAWxsB,OAASpI,KAAKV,MAAMs1B,WAAWxsB,MACtDpI,KAAKy5B,gBAITz4B,EAAOy4B,aAAe,WAMpB,QALmCxvB,IAA/BjK,KAAKV,MAAMs1B,WAAWtL,MAExB,YAAatpB,KAAKV,MAAMqH,MAAO3G,KAAKV,MAAMs1B,WAAWtL,MAAM,GAGzDtpB,KAAK+0B,MAAMouB,KAAK96C,OAAQ,CAE1B,IAAI2X,EAAUhgB,KAAK+0B,MAAMouB,KAAKnjD,KAAK+0B,MAAMouB,KAAK96C,OAAS,GAAG+6C,mBAC1DpjD,KAAK+0B,MAAMyF,OAASxa,EACpBhgB,KAAK+0B,MAAMwB,QAGbv2B,KAAKV,MAAMqH,MAAMmuB,OAAO,GAAI90B,KAAKV,MAAMs1B,WAAY50B,KAAK+0B,OAAO,IAGjE/zB,EAAOc,qBAAuB,WAC5B9B,KAAK+0B,MAAMwB,SAGbv1B,EAAOiC,OAAS,WACd,OAAO,MAGF+/C,EA3DsB,CA4D7B,aAgBE5tB,EAAa,SAASA,EAAW7mB,GAKnC,IAJA,IAAIC,EAAMD,EAAKlG,OACX0B,EAAI,EACJsrB,EAAM,GAEHtrB,EAAIyE,EAAKzE,IAAK,CACnB,IAAIwH,EAAMhD,EAAKxE,GACf,GAAW,MAAPwH,EAAJ,CACA,IAAI+jB,OAAQ,EAEZ,cAAe/jB,GACb,IAAK,UACH,MAEF,IAAK,SAED,GAAIgD,MAAM+I,QAAQ/L,GAChB+jB,EAAQF,EAAW7jB,QAInB,IAAK,IAAIpD,KAFTmnB,EAAQ,GAEM/jB,EACRA,EAAIpD,IAAMA,IACZmnB,IAAUA,GAAS,KACnBA,GAASnnB,GAKf,MAGJ,QAEImnB,EAAQ/jB,EAIV+jB,IACFD,IAAQA,GAAO,KACfA,GAAOC,IAIX,OAAOD,GAGT,SAASL,EAAMvL,EAAYwL,EAAK50B,GAC9B,IAAI60B,EAAmB,GACnBC,EAAe,YAAoB1L,EAAYyL,EAAkB70B,GAErE,OAAI60B,EAAiB7sB,OAAS,EACrBhI,EAGF80B,EAAeF,EAAIC,GAGX,GAAiB,SAAU51B,EAAO8d,GACjD,OAAoB,wBAAcslC,EAAat1B,SAAU,MAAM,SAAU/gB,GACvE,IAEI4oB,EAAM,WAKR,IAAK,IAAIlW,EAAOvW,UAAUH,OAAQkG,EAAO,IAAIgG,MAAMwK,GAAOC,EAAO,EAAGA,EAAOD,EAAMC,IAC/EzQ,EAAKyQ,GAAQxW,UAAUwW,GAGzB,IAAI4V,EAAa,YAAgBrmB,EAAM6O,EAAQqM,YAI/C,OAFE,YAAarM,EAASwX,GAAY,GAE7BxX,EAAQzX,IAAM,IAAMivB,EAAWxsB,MAepC6E,EAAU,CACZgoB,IAAKA,EACLU,GAdO,WAKP,IAAK,IAAIO,EAAQ1tB,UAAUH,OAAQkG,EAAO,IAAIgG,MAAM2hB,GAAQC,EAAQ,EAAGA,EAAQD,EAAOC,IACpF5nB,EAAK4nB,GAAS3tB,UAAU2tB,GAG1B,OAAOnB,EAAM5X,EAAQqM,WAAYwL,EAAKG,EAAW7mB,KAMjDlC,MAAOA,GAEL60B,EAAM5hC,EAAM2P,SAAShC,GAEzB,OADc,EACPi0B,S,kCCnOX,IAAItc,EAAI,mBAAsBrK,QAAUA,OAAO8oC,IAC3C7lB,EAAI5Y,EAAIrK,OAAO8oC,IAAI,iBAAmB,MACtC10B,EAAI/J,EAAIrK,OAAO8oC,IAAI,gBAAkB,MACrCx/C,EAAI+gB,EAAIrK,OAAO8oC,IAAI,kBAAoB,MACvCja,EAAIxkB,EAAIrK,OAAO8oC,IAAI,qBAAuB,MAC1Chb,EAAIzjB,EAAIrK,OAAO8oC,IAAI,kBAAoB,MACvC36B,EAAI9D,EAAIrK,OAAO8oC,IAAI,kBAAoB,MACvCl1C,EAAIyW,EAAIrK,OAAO8oC,IAAI,iBAAmB,MACtChhC,EAAIuC,EAAIrK,OAAO8oC,IAAI,oBAAsB,MACzClc,EAAIviB,EAAIrK,OAAO8oC,IAAI,yBAA2B,MAC9CjpC,EAAIwK,EAAIrK,OAAO8oC,IAAI,qBAAuB,MAC1C33B,EAAI9G,EAAIrK,OAAO8oC,IAAI,kBAAoB,MACvCx+B,EAAID,EAAIrK,OAAO8oC,IAAI,uBAAyB,MAC5Cpa,EAAIrkB,EAAIrK,OAAO8oC,IAAI,cAAgB,MACnCzjB,EAAIhb,EAAIrK,OAAO8oC,IAAI,cAAgB,MACnCnpB,EAAItV,EAAIrK,OAAO8oC,IAAI,eAAiB,MACpC9b,EAAI3iB,EAAIrK,OAAO8oC,IAAI,qBAAuB,MAC1CjwB,EAAIxO,EAAIrK,OAAO8oC,IAAI,mBAAqB,MACxCxa,EAAIjkB,EAAIrK,OAAO8oC,IAAI,eAAiB,MAExC,SAAS1a,EAAEhkB,GACT,GAAI,iBAAoBA,GAAK,OAASA,EAAG,CACvC,IAAIqkB,EAAIrkB,EAAE0yB,SAEV,OAAQrO,GACN,KAAKxL,EACH,OAAQ7Y,EAAIA,EAAEzc,MACZ,KAAKma,EACL,KAAK8kB,EACL,KAAKtjC,EACL,KAAKwkC,EACL,KAAKe,EACL,KAAK1d,EACH,OAAO/G,EAET,QACE,OAAQA,EAAIA,GAAKA,EAAE0yB,UACjB,KAAKlpC,EACL,KAAKiM,EACL,KAAKwlB,EACL,KAAKqJ,EACL,KAAKvgB,EACH,OAAO/D,EAET,QACE,OAAOqkB,GAKjB,KAAKra,EACH,OAAOqa,IAKf,SAASV,EAAE3jB,GACT,OAAOgkB,EAAEhkB,KAAOwiB,EAGlB3qC,EAAQ8mD,UAAYjhC,EACpB7lB,EAAQ+mD,eAAiBpc,EACzB3qC,EAAQgnD,gBAAkBr1C,EAC1B3R,EAAQinD,gBAAkB/6B,EAC1BlsB,EAAQo6C,QAAUpZ,EAClBhhC,EAAQwM,WAAaoR,EACrB5d,EAAQsX,SAAWjQ,EACnBrH,EAAQknD,KAAO9jB,EACfpjC,EAAQyM,KAAOggC,EACfzsC,EAAQmnD,OAASh1B,EACjBnyB,EAAQonD,SAAWvb,EACnB7rC,EAAQqnD,WAAaza,EACrB5sC,EAAQsnD,SAAWp4B,EAEnBlvB,EAAQunD,YAAc,SAAUp/B,GAC9B,OAAO2jB,EAAE3jB,IAAMgkB,EAAEhkB,KAAOtC,GAG1B7lB,EAAQwnD,iBAAmB1b,EAE3B9rC,EAAQynD,kBAAoB,SAAUt/B,GACpC,OAAOgkB,EAAEhkB,KAAOxW,GAGlB3R,EAAQ0nD,kBAAoB,SAAUv/B,GACpC,OAAOgkB,EAAEhkB,KAAO+D,GAGlBlsB,EAAQ2nD,UAAY,SAAUx/B,GAC5B,MAAO,iBAAoBA,GAAK,OAASA,GAAKA,EAAE0yB,WAAa7Z,GAG/DhhC,EAAQ4nD,aAAe,SAAUz/B,GAC/B,OAAOgkB,EAAEhkB,KAAOvK,GAGlB5d,EAAQ6nD,WAAa,SAAU1/B,GAC7B,OAAOgkB,EAAEhkB,KAAO9gB,GAGlBrH,EAAQ8nD,OAAS,SAAU3/B,GACzB,OAAOgkB,EAAEhkB,KAAOib,GAGlBpjC,EAAQuM,OAAS,SAAU4b,GACzB,OAAOgkB,EAAEhkB,KAAOskB,GAGlBzsC,EAAQ+nD,SAAW,SAAU5/B,GAC3B,OAAOgkB,EAAEhkB,KAAOgK,GAGlBnyB,EAAQgoD,WAAa,SAAU7/B,GAC7B,OAAOgkB,EAAEhkB,KAAO0jB,GAGlB7rC,EAAQioD,aAAe,SAAU9/B,GAC/B,OAAOgkB,EAAEhkB,KAAOykB,GAGlB5sC,EAAQkoD,WAAa,SAAU//B,GAC7B,OAAOgkB,EAAEhkB,KAAO+G,GAGlBlvB,EAAQmoD,mBAAqB,SAAUhgC,GACrC,MAAO,iBAAoBA,GAAK,mBAAsBA,GAAKA,IAAM9gB,GAAK8gB,IAAMwiB,GAAKxiB,IAAM0jB,GAAK1jB,IAAMykB,GAAKzkB,IAAM+G,GAAK/G,IAAME,GAAK,iBAAoBF,GAAK,OAASA,IAAMA,EAAE0yB,WAAazX,GAAKjb,EAAE0yB,WAAapO,GAAKtkB,EAAE0yB,WAAa3uB,GAAK/D,EAAE0yB,WAAalpC,GAAKwW,EAAE0yB,WAAaj9B,GAAKuK,EAAE0yB,WAAa9P,GAAK5iB,EAAE0yB,WAAajkB,GAAKzO,EAAE0yB,WAAaxO,GAAKlkB,EAAE0yB,WAAand,IAGtV19B,EAAQooD,OAASjc,G,kCC1IF,SAASr8B,EAAgBzF,EAAKlB,EAAKG,GAYhD,OAXIH,KAAOkB,EACTK,OAAOC,eAAeN,EAAKlB,EAAK,CAC9BG,MAAOA,EACPyG,YAAY,EACZC,cAAc,EACdC,UAAU,IAGZ5F,EAAIlB,GAAOG,EAGNe,EAZT,mC,oUCwBeg+C,UAlBU,SAAC,GAAkB,IAAhBnlD,EAAe,EAAfA,SACpBqhB,EAAgB3F,UAAO8yB,aAAaxuC,EAAS0B,UACnD,OAAK2f,EAGEpM,IAAMpV,cAAculD,I,yWAApB,EACLplD,WACAqhB,iBACGA,EAAcC,OALV,O,kCCTI,SAAS8hB,EAAgB5oB,EAAGwR,GAMzC,OALAoX,EAAkB57B,OAAO6T,gBAAkB,SAAyBb,EAAGwR,GAErE,OADAxR,EAAExK,UAAYgc,EACPxR,IAGcA,EAAGwR,GAN5B,mC,qBCAA,IAAI3Q,EAAiB,EAAQ,QAEzBgqC,EAA2B,EAAQ,QAEvC,SAASC,EAAWC,EAAQ12C,EAAM22C,GAiBhC,OAhBIH,KACFn+C,EAAOpK,QAAUwoD,EAAapP,QAAQC,UACtCjvC,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,IAExEmK,EAAOpK,QAAUwoD,EAAa,SAAoBC,EAAQ12C,EAAM22C,GAC9D,IAAIvgC,EAAI,CAAC,MACTA,EAAE3nB,KAAK6P,MAAM8X,EAAGpW,GAChB,IACItM,EAAW,IADGkjD,SAASpkD,KAAK8L,MAAMo4C,EAAQtgC,IAG9C,OADIugC,GAAOnqC,EAAe9Y,EAAUijD,EAAMjkD,WACnCgB,GAGT2E,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,GAGnEuoD,EAAWn4C,MAAM,KAAMrE,WAGhC5B,EAAOpK,QAAUwoD,EACjBp+C,EAAOpK,QAAiB,QAAIoK,EAAOpK,QAASoK,EAAOpK,QAAQC,YAAa,G,sBCzBxE,YAAAD,EAAA,cACAA,EAAQ2I,KAAO3I,EAAQgxC,sBAAwBhxC,EAAQwY,mBAAqBxY,EAAQ0Y,iBAAmB1Y,EAAQknC,wBAA0BlnC,EAAQipC,uCAAoCx7B,EAErL,IAAIzD,EAA4B,mBAAX+T,QAAoD,iBAApBA,OAAOC,SAAwB,SAAU3T,GAC5F,cAAcA,GACZ,SAAUA,GACZ,OAAOA,GAAyB,mBAAX0T,QAAyB1T,EAAI8I,cAAgB4K,QAAU1T,IAAQ0T,OAAOtZ,UAAY,gBAAkB4F,GAGvH6F,EAAWxF,OAAOyF,QAAU,SAAU9J,GACxC,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CACzC,IAAI6C,EAASpE,UAAUuB,GAEvB,IAAK,IAAIpE,KAAOiH,EACV1F,OAAOjG,UAAUwB,eAAe1C,KAAK6M,EAAQjH,KAC/C9C,EAAO8C,GAAOiH,EAAOjH,IAK3B,OAAO9C,GAKLsgC,EAAU7mC,EAFD,EAAQ,SAMjB8oD,EAAiB9oD,EAFD,EAAQ,SAIxBknC,EAAmB,EAAQ,QAE/B,SAASlnC,EAAuBuK,GAC9B,OAAOA,GAAOA,EAAIpK,WAAaoK,EAAM,CACnC3J,QAAS2J,GAIb,IAoKMw+C,EApKFpf,EAA0B,SAAiCxd,GAC7D,IAAIqR,IAAStxB,UAAUH,OAAS,QAAsB4B,IAAjBzB,UAAU,KAAmBA,UAAU,GAE5E,OAAe,IAAXsxB,EACKwrB,OAAO78B,GAGT68B,OAAO78B,GAAK1rB,QAAQ,KAAM,SAASA,QAAQ,KAAM,QAAQA,QAAQ,KAAM,QAAQA,QAAQ,KAAM,UAAUA,QAAQ,KAAM,WAG1HwoD,EAAwB,SAA+BC,GACzD,IAAIC,EAAiBC,EAAqBF,EAAWhiB,EAAiBQ,UAAUW,OAC5EghB,EAAoBD,EAAqBF,EAAWhiB,EAAiBqb,aAAaK,gBAEtF,GAAIyG,GAAqBF,EAEvB,OAAOE,EAAkB5oD,QAAQ,OAAO,WACtC,OAAO0oD,KAIX,IAAIG,EAAwBF,EAAqBF,EAAWhiB,EAAiBqb,aAAaC,eAC1F,OAAO2G,GAAkBG,QAAyB37C,GAGhD47C,EAAyB,SAAgCL,GAC3D,OAAOE,EAAqBF,EAAWhiB,EAAiBqb,aAAaI,yBAA2B,cAG9F6G,EAA6B,SAAoCC,EAASP,GAC5E,OAAOA,EAAUllD,QAAO,SAAUhB,GAChC,YAAiC,IAAnBA,EAAMymD,MACnB96C,KAAI,SAAU3L,GACf,OAAOA,EAAMymD,MACZr4C,QAAO,SAAUs4C,EAAUrnD,GAC5B,OAAO+N,EAAS,GAAIs5C,EAAUrnD,KAC7B,KAGDsnD,EAA0B,SAAiCC,EAAmBV,GAChF,OAAOA,EAAUllD,QAAO,SAAUhB,GAChC,YAAyD,IAA3CA,EAAMkkC,EAAiBQ,UAAUuZ,SAC9CtyC,KAAI,SAAU3L,GACf,OAAOA,EAAMkkC,EAAiBQ,UAAUuZ,SACvCxsB,UAAUrjB,QAAO,SAAUy4C,EAAkBlqB,GAC9C,IAAKkqB,EAAiB99C,OAGpB,IAFA,IAAIsB,EAAOzC,OAAOyC,KAAKsyB,GAEdlyB,EAAI,EAAGA,EAAIJ,EAAKtB,OAAQ0B,IAAK,CACpC,IACIq8C,EADez8C,EAAKI,GACiBmf,cAEzC,IAA0D,IAAtDg9B,EAAkB93C,QAAQg4C,IAAiCnqB,EAAImqB,GACjE,OAAOD,EAAiBv8C,OAAOqyB,GAKrC,OAAOkqB,IACN,KAGDE,EAAuB,SAA8B/pB,EAAS4pB,EAAmBV,GAEnF,IAAIc,EAAmB,GACvB,OAAOd,EAAUllD,QAAO,SAAUhB,GAChC,QAAIiV,MAAM+I,QAAQhe,EAAMg9B,WAIM,IAAnBh9B,EAAMg9B,IACfn3B,EAAK,WAAam3B,EAAU,mDAAwD91B,EAAQlH,EAAMg9B,IAAY,MAGzG,MACNrxB,KAAI,SAAU3L,GACf,OAAOA,EAAMg9B,MACZvL,UAAUrjB,QAAO,SAAU64C,EAAcC,GAC1C,IAAIC,EAAmB,GACvBD,EAAalmD,QAAO,SAAU27B,GAI5B,IAHA,IAAIyqB,OAAsB,EACtB/8C,EAAOzC,OAAOyC,KAAKsyB,GAEdlyB,EAAI,EAAGA,EAAIJ,EAAKtB,OAAQ0B,IAAK,CACpC,IAAI48C,EAAeh9C,EAAKI,GACpBq8C,EAAwBO,EAAaz9B,eAEiB,IAAtDg9B,EAAkB93C,QAAQg4C,IAAmCM,IAAwBljB,EAAiBma,eAAeS,KAAkD,cAA3CniB,EAAIyqB,GAAqBx9B,eAAoCk9B,IAA0B5iB,EAAiBma,eAAeS,KAAoD,eAA7CniB,EAAImqB,GAAuBl9B,gBACvRw9B,EAAsBN,IAIyB,IAA7CF,EAAkB93C,QAAQu4C,IAAyBA,IAAiBnjB,EAAiBma,eAAeK,YAAc2I,IAAiBnjB,EAAiBma,eAAeE,UAAY8I,IAAiBnjB,EAAiBma,eAAeM,YAClOyI,EAAsBC,GAI1B,IAAKD,IAAwBzqB,EAAIyqB,GAC/B,OAAO,EAGT,IAAI5gD,EAAQm2B,EAAIyqB,GAAqBx9B,cAUrC,OARKo9B,EAAiBI,KACpBJ,EAAiBI,GAAuB,IAGrCD,EAAiBC,KACpBD,EAAiBC,GAAuB,KAGrCJ,EAAiBI,GAAqB5gD,KACzC2gD,EAAiBC,GAAqB5gD,IAAS,GACxC,MAIRirB,UAAUpuB,SAAQ,SAAUs5B,GAC7B,OAAOsqB,EAAavpD,KAAKi/B,MAK3B,IAFA,IAAItyB,EAAOzC,OAAOyC,KAAK88C,GAEd18C,EAAI,EAAGA,EAAIJ,EAAKtB,OAAQ0B,IAAK,CACpC,IAAI48C,EAAeh9C,EAAKI,GACpB68C,GAAW,EAAIxB,EAAeloD,SAAS,GAAIopD,EAAiBK,GAAeF,EAAiBE,IAChGL,EAAiBK,GAAgBC,EAGnC,OAAOL,IACN,IAAIx1B,WAGL20B,EAAuB,SAA8BF,EAAW18B,GAClE,IAAK,IAAI/e,EAAIy7C,EAAUn9C,OAAS,EAAG0B,GAAK,EAAGA,IAAK,CAC9C,IAAIzK,EAAQkmD,EAAUz7C,GAEtB,GAAIzK,EAAMmD,eAAeqmB,GACvB,OAAOxpB,EAAMwpB,GAIjB,OAAO,MAqBL+9B,GACExB,EAAQztC,KAAKC,MACV,SAAU8iB,GACf,IAAImsB,EAAclvC,KAAKC,MAEnBivC,EAAczB,EAAQ,IACxBA,EAAQyB,EACRnsB,EAASmsB,IAETppC,YAAW,WACTmpC,EAAYlsB,KACX,KAKLosB,EAAc,SAAqBj6B,GACrC,OAAOhP,aAAagP,IAGlB0gB,EAA0C,oBAAX7sC,OAAyBA,OAAO6sC,uBAAyB7sC,OAAOqmD,6BAA+BrmD,OAAOsmD,0BAA4BJ,EAAcrrB,EAAOgS,uBAAyBqZ,EAC/MK,EAAyC,oBAAXvmD,OAAyBA,OAAOumD,sBAAwBvmD,OAAOwmD,4BAA8BxmD,OAAOymD,yBAA2BL,EAAcvrB,EAAO0rB,sBAAwBH,EAE1M5hD,EAAO,SAAckiD,GACvB,OAAOniD,SAAmC,mBAAjBA,QAAQC,MAAuBD,QAAQC,KAAKkiD,IAGnEC,EAAkB,KAmBlBC,EAAmB,SAA0BC,EAAUllD,GACzD,IAAIkkC,EAAUghB,EAAShhB,QACnB1B,EAAiB0iB,EAAS1iB,eAC1BE,EAAiBwiB,EAASxiB,eAC1ByB,EAAW+gB,EAAS/gB,SACpBC,EAAW8gB,EAAS9gB,SACpBC,EAAe6gB,EAAS7gB,aACxBP,EAAsBohB,EAASphB,oBAC/BQ,EAAa4gB,EAAS5gB,WACtBC,EAAY2gB,EAAS3gB,UACrB7X,EAAQw4B,EAASx4B,MACjB4V,EAAkB4iB,EAAS5iB,gBAC/B6iB,EAAiBjkB,EAAiBQ,UAAUa,KAAMC,GAClD2iB,EAAiBjkB,EAAiBQ,UAAUe,KAAMC,GAClD0iB,EAAY14B,EAAO4V,GACnB,IAAI+iB,EAAa,CACfnhB,QAASohB,EAAWpkB,EAAiBQ,UAAUuZ,KAAM/W,GACrDC,SAAUmhB,EAAWpkB,EAAiBQ,UAAU0B,KAAMe,GACtDC,SAAUkhB,EAAWpkB,EAAiBQ,UAAU2B,KAAMe,GACtDC,aAAcihB,EAAWpkB,EAAiBQ,UAAUE,SAAUyC,GAC9DC,WAAYghB,EAAWpkB,EAAiBQ,UAAUC,OAAQ2C,GAC1DC,UAAW+gB,EAAWpkB,EAAiBQ,UAAUG,MAAO0C,IAEtDghB,EAAY,GACZC,EAAc,GAClB5gD,OAAOyC,KAAKg+C,GAAYhlD,SAAQ,SAAUojD,GACxC,IAAIgC,EAAsBJ,EAAW5B,GACjCiC,EAAUD,EAAoBC,QAC9BC,EAAUF,EAAoBE,QAE9BD,EAAQ3/C,SACVw/C,EAAU9B,GAAWiC,GAGnBC,EAAQ5/C,SACVy/C,EAAY/B,GAAW4B,EAAW5B,GAASkC,YAG/C3lD,GAAMA,IACN8jC,EAAoBohB,EAAUK,EAAWC,IAGvCI,EAAe,SAAsBC,GACvC,OAAO5zC,MAAM+I,QAAQ6qC,GAAiBA,EAAc3nD,KAAK,IAAM2nD,GAG7DT,EAAc,SAAqB14B,EAAOmN,QACvB,IAAVnN,GAAyBja,SAASia,QAAUA,IACrDja,SAASia,MAAQk5B,EAAal5B,IAGhCy4B,EAAiBjkB,EAAiBQ,UAAUW,MAAOxI,IAGjDsrB,EAAmB,SAA0BnrB,EAASH,GACxD,IAAIisB,EAAarzC,SAASmjC,qBAAqB5b,GAAS,GAExD,GAAK8rB,EAAL,CASA,IALA,IAAIC,EAAwBD,EAAWld,aAAa1H,EAAiB6b,kBACjEiJ,EAAmBD,EAAwBA,EAAsB39C,MAAM,KAAO,GAC9E69C,EAAqB,GAAG3+C,OAAO0+C,GAC/BE,EAAgBthD,OAAOyC,KAAKwyB,GAEvBpyB,EAAI,EAAGA,EAAIy+C,EAAcngD,OAAQ0B,IAAK,CAC7C,IAAI0+C,EAAYD,EAAcz+C,GAC1BjE,EAAQq2B,EAAWssB,IAAc,GAEjCL,EAAWld,aAAaud,KAAe3iD,GACzCsiD,EAAWrQ,aAAa0Q,EAAW3iD,IAGQ,IAAzCwiD,EAAiBl6C,QAAQq6C,IAC3BH,EAAiBtrD,KAAKyrD,GAGxB,IAAIC,EAAcH,EAAmBn6C,QAAQq6C,IAExB,IAAjBC,GACFH,EAAmB12C,OAAO62C,EAAa,GAI3C,IAAK,IAAI3+B,EAAKw+B,EAAmBlgD,OAAS,EAAG0hB,GAAM,EAAGA,IACpDq+B,EAAWO,gBAAgBJ,EAAmBx+B,IAG5Cu+B,EAAiBjgD,SAAWkgD,EAAmBlgD,OACjD+/C,EAAWO,gBAAgBnlB,EAAiB6b,kBACnC+I,EAAWld,aAAa1H,EAAiB6b,oBAAsBmJ,EAAchoD,KAAK,MAC3F4nD,EAAWrQ,aAAavU,EAAiB6b,iBAAkBmJ,EAAchoD,KAAK,QAI9EonD,EAAa,SAAoB1/C,EAAMi7C,GACzC,IAAIyF,EAAc7zC,SAAS+1B,MAAQ/1B,SAASmuC,cAAc1f,EAAiBQ,UAAUwZ,MACjFqL,EAAWD,EAAY3d,iBAAiB/iC,EAAO,IAAMs7B,EAAiB6b,iBAAmB,KACzF4I,EAAU1zC,MAAMtT,UAAU3C,MAAMyB,KAAK8oD,GACrCb,EAAU,GACVc,OAAgB,EA0CpB,OAxCI3F,GAAQA,EAAK96C,QACf86C,EAAKxgD,SAAQ,SAAUs5B,GACrB,IAAI8sB,EAAah0C,SAASxV,cAAc2I,GAExC,IAAK,IAAIugD,KAAaxsB,EACpB,GAAIA,EAAIx5B,eAAegmD,GACrB,GAAIA,IAAcjlB,EAAiBma,eAAeK,WAChD+K,EAAW5nB,UAAYlF,EAAIkF,eACtB,GAAIsnB,IAAcjlB,EAAiBma,eAAeE,SACnDkL,EAAWC,WACbD,EAAWC,WAAW5kB,QAAUnI,EAAImI,QAEpC2kB,EAAW3d,YAAYr2B,SAASk0C,eAAehtB,EAAImI,cAEhD,CACL,IAAIt+B,OAAkC,IAAnBm2B,EAAIwsB,GAA6B,GAAKxsB,EAAIwsB,GAC7DM,EAAWhR,aAAa0Q,EAAW3iD,GAKzCijD,EAAWhR,aAAavU,EAAiB6b,iBAAkB,QAEvD4I,EAAQ9N,MAAK,SAAU+O,EAAajzC,GAEtC,OADA6yC,EAAgB7yC,EACT8yC,EAAWI,YAAYD,MAE9BjB,EAAQp2C,OAAOi3C,EAAe,GAE9Bd,EAAQhrD,KAAK+rD,MAKnBd,EAAQtlD,SAAQ,SAAUs5B,GACxB,OAAOA,EAAIkP,WAAWie,YAAYntB,MAEpC+rB,EAAQrlD,SAAQ,SAAUs5B,GACxB,OAAO2sB,EAAYxd,YAAYnP,MAE1B,CACLgsB,QAASA,EACTD,QAASA,IAITqB,EAAoC,SAA2CltB,GACjF,OAAOj1B,OAAOyC,KAAKwyB,GAAYzuB,QAAO,SAAU+a,EAAK9iB,GACnD,IAAI2jD,OAAkC,IAApBntB,EAAWx2B,GAAuBA,EAAM,KAAQw2B,EAAWx2B,GAAO,IAAO,GAAKA,EAChG,OAAO8iB,EAAMA,EAAM,IAAM6gC,EAAOA,IAC/B,KAuBDC,EAAuC,SAA8CptB,GACvF,IAAIqtB,EAAYhhD,UAAUH,OAAS,QAAsB4B,IAAjBzB,UAAU,GAAmBA,UAAU,GAAK,GACpF,OAAOtB,OAAOyC,KAAKwyB,GAAYzuB,QAAO,SAAU7G,EAAKlB,GAEnD,OADAkB,EAAI28B,EAAiBia,cAAc93C,IAAQA,GAAOw2B,EAAWx2B,GACtDkB,IACN2iD,IA6CDC,EAAmB,SAA0BvhD,EAAMi7C,EAAMrpB,GAC3D,OAAQ5xB,GACN,KAAKs7B,EAAiBQ,UAAUW,MAC9B,MAAO,CACL+kB,YAAa,WACX,OAvCuE16B,EAuC5Bm0B,EAAKn0B,MAvC8BmN,EAuCvBgnB,EAAKve,iBAnCnD+kB,EAAa,CAC5BhkD,IAAKqpB,IACOwU,EAAiB6b,mBAAoB,EAC/C//C,EAAQiqD,EAAqCptB,EADQwtB,GAElD,CAACxmB,EAAQjmC,QAAQqC,cAAcikC,EAAiBQ,UAAUW,MAAOrlC,EAAO0vB,IAR7C,IAA6CA,EAAOmN,EAClFwtB,EAMArqD,GAkCE+a,SAAU,WACR,OA9EkB,SAA+BnS,EAAM8mB,EAAOmN,EAAYrC,GAClF,IAAI8vB,EAAkBP,EAAkCltB,GACpD0tB,EAAiB3B,EAAal5B,GAClC,OAAO46B,EAAkB,IAAM1hD,EAAO,IAAMs7B,EAAiB6b,iBAAmB,WAAeuK,EAAkB,IAAM3jB,EAAwB4jB,EAAgB/vB,GAAU,KAAO5xB,EAAO,IAAM,IAAMA,EAAO,IAAMs7B,EAAiB6b,iBAAmB,WAAepZ,EAAwB4jB,EAAgB/vB,GAAU,KAAO5xB,EAAO,IA2EpT4hD,CAAsB5hD,EAAMi7C,EAAKn0B,MAAOm0B,EAAKve,gBAAiB9K,KAI3E,KAAK0J,EAAiB8Z,gBAAgBzY,KACtC,KAAKrB,EAAiB8Z,gBAAgBvY,KACpC,MAAO,CACL2kB,YAAa,WACX,OAAOH,EAAqCpG,IAE9C9oC,SAAU,WACR,OAAOgvC,EAAkClG,KAI/C,QACE,MAAO,CACLuG,YAAa,WACX,OAjDyB,SAAsCxhD,EAAMi7C,GAC7E,OAAOA,EAAKl4C,KAAI,SAAUgxB,EAAKlyB,GAC7B,IAAIggD,EAEAC,IAAaD,EAAa,CAC5BpkD,IAAKoE,IACOy5B,EAAiB6b,mBAAoB,EAAM0K,GAazD,OAZA7iD,OAAOyC,KAAKsyB,GAAKt5B,SAAQ,SAAU8lD,GACjC,IAAIwB,EAAkBzmB,EAAiBia,cAAcgL,IAAcA,EAEnE,GAAIwB,IAAoBzmB,EAAiBma,eAAeK,YAAciM,IAAoBzmB,EAAiBma,eAAeE,SAAU,CAClI,IAAI5wC,EAAUgvB,EAAIkF,WAAalF,EAAImI,QACnC4lB,EAAUv3B,wBAA0B,CAClCC,OAAQzlB,QAGV+8C,EAAUC,GAAmBhuB,EAAIwsB,MAG9BtlB,EAAQjmC,QAAQqC,cAAc2I,EAAM8hD,MA8B9BE,CAA6BhiD,EAAMi7C,IAE5C9oC,SAAU,WACR,OA7FiB,SAA8BnS,EAAMi7C,EAAMrpB,GACnE,OAAOqpB,EAAKz1C,QAAO,SAAU+a,EAAKwT,GAChC,IAAIkuB,EAAgBjjD,OAAOyC,KAAKsyB,GAAK37B,QAAO,SAAUmoD,GACpD,QAASA,IAAcjlB,EAAiBma,eAAeK,YAAcyK,IAAcjlB,EAAiBma,eAAeE,aAClHnwC,QAAO,SAAU1O,EAAQypD,GAC1B,IAAIa,OAAiC,IAAnBrtB,EAAIwsB,GAA6BA,EAAYA,EAAY,KAAQxiB,EAAwBhK,EAAIwsB,GAAY3uB,GAAU,IACrI,OAAO96B,EAASA,EAAS,IAAMsqD,EAAOA,IACrC,IACCc,EAAanuB,EAAIkF,WAAalF,EAAImI,SAAW,GAC7CimB,GAAsE,IAAtD7mB,EAAiB4b,kBAAkBhxC,QAAQlG,GAC/D,OAAOugB,EAAM,IAAMvgB,EAAO,IAAMs7B,EAAiB6b,iBAAmB,WAAe8K,GAAiBE,EAAgB,KAAO,IAAMD,EAAa,KAAOliD,EAAO,OAC3J,IAkFYoiD,CAAqBpiD,EAAMi7C,EAAMrpB,OAmClDt9B,EAAQipC,kCA1GgC,SAA2CnmC,GACjF,IAAIirD,EAAiB/hD,UAAUH,OAAS,QAAsB4B,IAAjBzB,UAAU,GAAmBA,UAAU,GAAK,GACzF,OAAOtB,OAAOyC,KAAKrK,GAAOoO,QAAO,SAAU7G,EAAKlB,GAE9C,OADAkB,EAAI28B,EAAiB2b,aAAax5C,IAAQA,GAAOrG,EAAMqG,GAChDkB,IACN0jD,IAsGL/tD,EAAQknC,wBApTsB,SAAiC8jB,GACzDF,GACFJ,EAAqBI,GAGnBE,EAASxhB,MACXshB,EAAkB9Z,GAAsB,WACtC+Z,EAAiBC,GAAU,WACzBF,EAAkB,YAItBC,EAAiBC,GACjBF,EAAkB,OAwStB9qD,EAAQ0Y,iBA/Be,SAA0BlX,GAC/C,IAAIwoC,EAAUxoC,EAAKwoC,QACf1B,EAAiB9mC,EAAK8mC,eACtBhL,EAAS97B,EAAK87B,OACdkL,EAAiBhnC,EAAKgnC,eACtByB,EAAWzoC,EAAKyoC,SAChBC,EAAW1oC,EAAK0oC,SAChBC,EAAe3oC,EAAK2oC,aACpBC,EAAa5oC,EAAK4oC,WAClBC,EAAY7oC,EAAK6oC,UACjB2jB,EAAaxsD,EAAKgxB,MAClBA,OAAuB/kB,IAAfugD,EAA2B,GAAKA,EACxC5lB,EAAkB5mC,EAAK4mC,gBAC3B,MAAO,CACLxmC,KAAMqrD,EAAiBjmB,EAAiBQ,UAAUuZ,KAAM/W,EAAS1M,GACjEgL,eAAgB2kB,EAAiBjmB,EAAiB8Z,gBAAgBzY,KAAMC,EAAgBhL,GACxFkL,eAAgBykB,EAAiBjmB,EAAiB8Z,gBAAgBvY,KAAMC,EAAgBlL,GACxFtN,KAAMi9B,EAAiBjmB,EAAiBQ,UAAU0B,KAAMe,EAAU3M,GAClEoM,KAAMujB,EAAiBjmB,EAAiBQ,UAAU2B,KAAMe,EAAU5M,GAClEqM,SAAUsjB,EAAiBjmB,EAAiBQ,UAAUE,SAAUyC,EAAc7M,GAC9EuM,OAAQojB,EAAiBjmB,EAAiBQ,UAAUC,OAAQ2C,EAAY9M,GACxEr5B,MAAOgpD,EAAiBjmB,EAAiBQ,UAAUG,MAAO0C,EAAW/M,GACrE9K,MAAOy6B,EAAiBjmB,EAAiBQ,UAAUW,MAAO,CACxD3V,MAAOA,EACP4V,gBAAiBA,GAChB9K,KAOPt9B,EAAQwY,mBArWiB,SAA4BwwC,GACnD,MAAO,CACLhf,QAASyf,EAAwB,CAACziB,EAAiBma,eAAeG,MAAO0H,GACzE1gB,eAAgBghB,EAA2BtiB,EAAiB8Z,gBAAgBzY,KAAM2gB,GAClFxf,MAAO0f,EAAqBF,EAAWhiB,EAAiBqb,aAAaE,OACrEjlB,OAAQ4rB,EAAqBF,EAAWhiB,EAAiBqb,aAAaG,2BACtEha,eAAgB8gB,EAA2BtiB,EAAiB8Z,gBAAgBvY,KAAMygB,GAClF/e,SAAU4f,EAAqB7iB,EAAiBQ,UAAU0B,KAAM,CAAClC,EAAiBma,eAAeS,IAAK5a,EAAiBma,eAAeG,MAAO0H,GAC7I9e,SAAU2f,EAAqB7iB,EAAiBQ,UAAU2B,KAAM,CAACnC,EAAiBma,eAAeO,KAAM1a,EAAiBma,eAAeC,QAASpa,EAAiBma,eAAeI,UAAWva,EAAiBma,eAAeQ,SAAU3a,EAAiBma,eAAeM,WAAYuH,GACjR7e,aAAc0f,EAAqB7iB,EAAiBQ,UAAUE,SAAU,CAACV,EAAiBma,eAAeK,YAAawH,GACtHpf,oBAAqByf,EAAuBL,GAC5C5e,WAAYyf,EAAqB7iB,EAAiBQ,UAAUC,OAAQ,CAACT,EAAiBma,eAAeU,IAAK7a,EAAiBma,eAAeK,YAAawH,GACvJ3e,UAAWwf,EAAqB7iB,EAAiBQ,UAAUG,MAAO,CAACX,EAAiBma,eAAeE,UAAW2H,GAC9Gx2B,MAAOu2B,EAAsBC,GAC7B5gB,gBAAiBkhB,EAA2BtiB,EAAiB8Z,gBAAgB3Y,MAAO6gB,KAwVxFhpD,EAAQgxC,sBAAwBA,EAChChxC,EAAQ2I,KAAOA,I,+EC/hBf,qFAMIslD,EAA2B,IAE3BC,EAA2B,SAAkC/kD,GAC/D,MAAe,UAARA,GAA2B,aAARA,GAGxBglD,EAA8B,SAAqC1uB,GACrE,MAAsB,iBAARA,GAGdA,EAAI5iB,WAAW,GAAK,GAAKoxC,EAA2BC,GAGtD,SAASr4C,EAAQnT,EAAQoT,GACvB,IAAI3I,EAAOzC,OAAOyC,KAAKzK,GAEvB,GAAIgI,OAAOiC,sBAAuB,CAChC,IAAIoJ,EAAUrL,OAAOiC,sBAAsBjK,GACvCoT,IAAgBC,EAAUA,EAAQjS,QAAO,SAAUkS,GACrD,OAAOtL,OAAOE,yBAAyBlI,EAAQsT,GAAKjG,eAEtD5C,EAAK3M,KAAK6P,MAAMlD,EAAM4I,GAGxB,OAAO5I,EAGT,SAASujB,EAAcrqB,GACrB,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CACzC,IAAI6C,EAAyB,MAAhBpE,UAAUuB,GAAavB,UAAUuB,GAAK,GAE/CA,EAAI,EACNsI,EAAQzF,GAAQ,GAAMjK,SAAQ,SAAUgD,GACtC,IAAgB9C,EAAQ8C,EAAKiH,EAAOjH,OAE7BuB,OAAOwL,0BAChBxL,OAAOyL,iBAAiB9P,EAAQqE,OAAOwL,0BAA0B9F,IAEjEyF,EAAQzF,GAAQjK,SAAQ,SAAUgD,GAChCuB,OAAOC,eAAetE,EAAQ8C,EAAKuB,OAAOE,yBAAyBwF,EAAQjH,OAKjF,OAAO9C,EA8IM,IAzII,SAAS+nD,EAAa3uB,EAAK32B,GAO5C,IAAIklB,EACAqgC,EACAC,OAEY7gD,IAAZ3E,IACFklB,EAAiBllB,EAAQorB,MACzBo6B,EAAkBxlD,EAAQzC,OAC1BgoD,EAAoB5uB,EAAI8uB,uBAAyBzlD,EAAQulD,kBAAoB,SAAUG,GACrF,OAAO/uB,EAAI8uB,sBAAsBC,IACjC1lD,EAAQulD,kBAAkBG,IACxB1lD,EAAQulD,mBAGd,IAAII,EAAShvB,EAAIivB,iBAAmBjvB,EAChCuK,EAAUykB,GAAUhvB,EAAIkvB,gBAAkBlvB,EAEb,mBAAtB4uB,GAAoCI,IAC7CJ,EAAoB5uB,EAAI8uB,uBAG1B,IAAIK,EAA2BP,GAAqBF,EAA4BnkB,GAC5E6kB,GAAeD,EAAyB,MAC5C,OAAO,WACL,IAAI78C,EAAO/F,UACPsD,EAASm/C,QAAmChhD,IAAzBgyB,EAAIrS,iBAAiCqS,EAAIrS,iBAAiBtrB,MAAM,GAAK,GAM5F,QAJuB2L,IAAnBugB,GACF1e,EAAO9O,KAAK,SAAWwtB,EAAiB,KAG3B,MAAXjc,EAAK,SAA8BtE,IAAhBsE,EAAK,GAAG+b,IAC7Bxe,EAAO9O,KAAK6P,MAAMf,EAAQyC,OACrB,CACD,EAIJzC,EAAO9O,KAAKuR,EAAK,GAAG,IAIpB,IAHA,IAAIC,EAAMD,EAAKlG,OACX0B,EAAI,EAEDA,EAAIyE,EAAKzE,IAKd+B,EAAO9O,KAAKuR,EAAKxE,GAAIwE,EAAK,GAAGxE,IAKjC,IAAIuhD,EAAS,aAAiB,SAAUhsD,EAAO8d,EAAS/a,GACtD,OAAO,wBAAc,IAAa+qB,SAAU,MAAM,SAAU/gB,GAC1D,IAAIk/C,EAAWF,GAAe/rD,EAAMw8C,IAAMtV,EACtCnmC,EAAY,GACZmrD,EAAsB,GACtBhiC,EAAclqB,EAElB,GAAmB,MAAfA,EAAM+M,MAAe,CAGvB,IAAK,IAAI1G,KAFT6jB,EAAc,GAEElqB,EACdkqB,EAAY7jB,GAAOrG,EAAMqG,GAG3B6jB,EAAYnd,MAAQA,EAGS,iBAApB/M,EAAMe,UACfA,EAAY,YAAoB+c,EAAQqM,WAAY+hC,EAAqBlsD,EAAMe,WACnD,MAAnBf,EAAMe,YACfA,EAAYf,EAAMe,UAAY,KAGhC,IAAIu0B,EAAa,YAAgB9oB,EAAOlC,OAAO4hD,GAAsBpuC,EAAQqM,WAAYD,GAC7E,YAAapM,EAASwX,EAAgC,iBAAb22B,GACrDlrD,GAAa+c,EAAQzX,IAAM,IAAMivB,EAAWxsB,UAEpB6B,IAApB6gD,IACFzqD,GAAa,IAAMyqD,GAGrB,IAAIW,EAAyBJ,QAAqCphD,IAAtB4gD,EAAkCF,EAA4BY,GAAYH,EAClH52C,EAAW,GAEf,IAAK,IAAIwK,KAAQ1f,EACX+rD,GAAwB,OAATrsC,GAGnBysC,EAAuBzsC,KACrBxK,EAASwK,GAAQ1f,EAAM0f,IAY3B,OARAxK,EAASnU,UAAYA,EACrBmU,EAASnS,IAAMA,GAAO/C,EAAMkD,SAMlB,wBAAc+oD,EAAU/2C,SAyBtC,OArBA82C,EAAOzjD,iBAAiCoC,IAAnBugB,EAA+BA,EAAiB,WAAgC,iBAAZgc,EAAuBA,EAAUA,EAAQ3+B,aAAe2+B,EAAQp+B,MAAQ,aAAe,IAChLkjD,EAAO1jD,aAAeq0B,EAAIr0B,aAC1B0jD,EAAOJ,eAAiBI,EACxBA,EAAOH,eAAiB3kB,EACxB8kB,EAAO1hC,iBAAmB9d,EAC1Bw/C,EAAOP,sBAAwBF,EAC/B3jD,OAAOC,eAAemkD,EAAQ,WAAY,CACxCxlD,MAAO,WAML,MAAO,IAAMglD,KAIjBQ,EAAOI,cAAgB,SAAUC,EAASC,GACxC,OAAOhB,EAAae,OAAyB1hD,IAAhB2hD,EAA4B1+B,EAAc,GAAI5nB,GAAW,GAAI,GAAIsmD,GAAetmD,GAASuH,WAAM,EAAQf,IAG/Hw/C,K,kCC5LI,SAAS5+C,IAetB,OAdAA,EAAWxF,OAAOyF,QAAU,SAAU9J,GACpC,IAAK,IAAIkH,EAAI,EAAGA,EAAIvB,UAAUH,OAAQ0B,IAAK,CACzC,IAAI6C,EAASpE,UAAUuB,GAEvB,IAAK,IAAIpE,KAAOiH,EACV1F,OAAOjG,UAAUwB,eAAe1C,KAAK6M,EAAQjH,KAC/C9C,EAAO8C,GAAOiH,EAAOjH,IAK3B,OAAO9C,IAGOgK,MAAM7M,KAAMwI,WAf9B,mC,qBCAA,IAAMoyB,EAAUr+B,EAAQ,Q,EAOpBA,EAAQ,QAAY+kB,aALtBk7B,E,EAAAA,wBACAC,E,EAAAA,4BACAV,E,EAAAA,2BACApP,E,EAAAA,SACAuB,E,EAAAA,aAGF1xC,EAAQ6kB,UAAY,SAACwqC,EAAKt9C,EAAWu9C,EAAeC,QAAiB,IAA3Cx9C,MAAO,IAY/B,IAAI4+B,EAAUvS,EAAQ3vB,KAAI,SAAAia,GACxB,GAAKA,EAAOA,OAAO2mC,GAAnB,CAKAt9C,EAAKkuC,4BAA8BA,EAEnCluC,EAAKiuC,wBAA0BA,EAC/BjuC,EAAKwtC,2BAA6BA,EAClCxtC,EAAKo+B,SAAWA,EAChBp+B,EAAK2/B,aAAeA,EAEpB,IAAMpyB,EAASoJ,EAAOA,OAAO2mC,GAAKt9C,EAAM2W,EAAO5f,SAI/C,OAHIwW,GAAUiwC,IACZx9C,EAAOw9C,EAAa,CAAEx9C,OAAMuN,SAAQoJ,YAE/BpJ,MAMT,OAFAqxB,EAAUA,EAAQ7sC,QAAO,SAAAwb,GAAM,YAAI,IAAOA,MAE9BzT,OAAS,EACZ8kC,EACE2e,EACF,CAACA,GAED,IAIXtvD,EAAQmyC,eAAiB,SAACkd,EAAKt9C,EAAMu9C,GAAZ,OACvBlxB,EAAQltB,QACN,SAACs+C,EAAU1iC,GAAX,OACEA,EAAKpE,OAAO2mC,GACRG,EAASvwC,MAAK,kBAAM6N,EAAKpE,OAAO2mC,GAAKt9C,EAAM+a,EAAKhkB,YAChD0mD,IACN/zC,QAAQrZ,a,kCCzDZ,IAMI44B,EAJuC2P,EAFvCxyB,EAAQpY,EAAQ,QAQpB,IAN2C4qC,EAOlB5qC,EAAQ0vD,QAA/Bz0B,EANO2P,GAAKA,EAAEjqC,SAAWiqC,EAOzB,MAAOtjC,GACP,MAA2D,IAAvDA,EAAEwW,WAAWjM,QAAQ,6BACjB,IAAI+G,MAAM,uOAIhBjQ,QAAQsW,MAAM3X,GACRA,GAKV+C,EAAOpK,QAAU,SAAUwB,GACzB,IAAIgiB,EAAUhiB,EAAKgiB,QACf1gB,EAAQtB,EAAKsB,MACjB,OAAoBqV,EAAMpV,cAAci4B,EAAQl4B,EAAO0gB,K,kCCqBzDpZ,EAAOpK,QA5BS,SAAS0vD,EAAWC,EAAQxnC,EAAGC,EAAG4Y,EAAG7O,EAAG9qB,EAAGulC,GAOzD,IAAK8iB,EAAW,CACd,IAAI1wC,EACJ,QAAevR,IAAXkiD,EACF3wC,EAAQ,IAAIrG,MACV,qIAGG,CACL,IAAI5G,EAAO,CAACoW,EAAGC,EAAG4Y,EAAG7O,EAAG9qB,EAAGulC,GACvBgjB,EAAW,GACf5wC,EAAQ,IAAIrG,MACVg3C,EAAOpvD,QAAQ,OAAO,WAAa,OAAOwR,EAAK69C,UAE3ChkD,KAAO,sBAIf,MADAoT,EAAM6wC,YAAc,EACd7wC,K,oCC5CV,kCAoDA,IAAI8wC,EAA0B,WAC5B,SAASA,EAAWhnD,GAClBtF,KAAKy1B,cAA8BxrB,IAAnB3E,EAAQkwB,QAA+DlwB,EAAQkwB,OAC/Fx1B,KAAKmjD,KAAO,GACZnjD,KAAKusD,IAAM,EACXvsD,KAAKurC,MAAQjmC,EAAQimC,MAErBvrC,KAAK2F,IAAML,EAAQK,IACnB3F,KAAK6qC,UAAYvlC,EAAQulC,UACzB7qC,KAAKw6B,OAAS,KAGhB,IAAIx5B,EAASsrD,EAAWrrD,UAiExB,OA/DAD,EAAO8zB,OAAS,SAAgB03B,GAI9B,GAAIxsD,KAAKusD,KAAOvsD,KAAKy1B,SAAW,KAAQ,IAAO,EAAG,CAChD,IAEI+E,EAFAiyB,EA/BV,SAA4BnnD,GAC1B,IAAI22B,EAAMlnB,SAASxV,cAAc,SAQjC,OAPA08B,EAAI8b,aAAa,eAAgBzyC,EAAQK,UAEnBsE,IAAlB3E,EAAQimC,OACVtP,EAAI8b,aAAa,QAASzyC,EAAQimC,OAGpCtP,EAAImP,YAAYr2B,SAASk0C,eAAe,KACjChtB,EAsBQywB,CAAmB1sD,MAK5Bw6B,EADuB,IAArBx6B,KAAKmjD,KAAK96C,OACHrI,KAAKw6B,OAELx6B,KAAKmjD,KAAKnjD,KAAKmjD,KAAK96C,OAAS,GAAGskD,YAG3C3sD,KAAK6qC,UAAUvQ,aAAamyB,EAAMjyB,GAClCx6B,KAAKmjD,KAAKnmD,KAAKyvD,GAGjB,IAAIxwB,EAAMj8B,KAAKmjD,KAAKnjD,KAAKmjD,KAAK96C,OAAS,GAEvC,GAAIrI,KAAKy1B,SAAU,CACjB,IAAIV,EAjEV,SAAqBkH,GACnB,GAAIA,EAAIlH,MAEN,OAAOkH,EAAIlH,MAMb,IAAK,IAAIhrB,EAAI,EAAGA,EAAIgL,SAAS63C,YAAYvkD,OAAQ0B,IAC/C,GAAIgL,SAAS63C,YAAY7iD,GAAG8iD,YAAc5wB,EAExC,OAAOlnB,SAAS63C,YAAY7iD,GAqDhB+iD,CAAY7wB,GAExB,IAKE,IAAI8wB,EAAsC,MAAvBP,EAAKnzC,WAAW,IAAqC,KAAvBmzC,EAAKnzC,WAAW,GAGjE0b,EAAMi4B,WAAWR,EASjBO,EAAe,EAAIh4B,EAAMk4B,SAAS5kD,QAClC,MAAOxE,GACH,QAKNo4B,EAAImP,YAAYr2B,SAASk0C,eAAeuD,IAG1CxsD,KAAKusD,OAGPvrD,EAAOu1B,MAAQ,WAEbv2B,KAAKmjD,KAAKxgD,SAAQ,SAAUs5B,GAC1B,OAAOA,EAAIkP,WAAWie,YAAYntB,MAEpCj8B,KAAKmjD,KAAO,GACZnjD,KAAKusD,IAAM,GAGND,EA7EqB,I,kCCpDf,SAASv5C,EAA8BnG,EAAQiG,GAC5D,GAAc,MAAVjG,EAAgB,MAAO,GAC3B,IAEIjH,EAAKoE,EAFLlH,EAAS,GACTiQ,EAAa5L,OAAOyC,KAAKiD,GAG7B,IAAK7C,EAAI,EAAGA,EAAI+I,EAAWzK,OAAQ0B,IACjCpE,EAAMmN,EAAW/I,GACb8I,EAASzE,QAAQzI,IAAQ,IAC7B9C,EAAO8C,GAAOiH,EAAOjH,IAGvB,OAAO9C,EAZT,oC","file":"app-03e333c274b6bc210459.js","sourcesContent":["\"use strict\";\n\nvar _interopRequireDefault = require(\"@babel/runtime/helpers/interopRequireDefault\");\n\nexports.__esModule = true;\nexports.withPrefix = withPrefix;\nexports.withAssetPrefix = withAssetPrefix;\nexports.navigateTo = exports.replace = exports.push = exports.navigate = exports.default = void 0;\n\nvar _objectWithoutPropertiesLoose2 = _interopRequireDefault(require(\"@babel/runtime/helpers/objectWithoutPropertiesLoose\"));\n\nvar _assertThisInitialized2 = _interopRequireDefault(require(\"@babel/runtime/helpers/assertThisInitialized\"));\n\nvar _inheritsLoose2 = _interopRequireDefault(require(\"@babel/runtime/helpers/inheritsLoose\"));\n\nvar _extends2 = _interopRequireDefault(require(\"@babel/runtime/helpers/extends\"));\n\nvar _propTypes = _interopRequireDefault(require(\"prop-types\"));\n\nvar _react = _interopRequireDefault(require(\"react\"));\n\nvar _router = require(\"@reach/router\");\n\nvar _utils = require(\"@reach/router/lib/utils\");\n\nvar _parsePath = require(\"./parse-path\");\n\nexports.parsePath = _parsePath.parsePath;\n\nvar isAbsolutePath = function isAbsolutePath(path) {\n return path === null || path === void 0 ? void 0 : path.startsWith(\"/\");\n};\n\nfunction withPrefix(path, prefix) {\n var _ref, _prefix;\n\n if (prefix === void 0) {\n prefix = getGlobalBasePrefix();\n }\n\n if (!isLocalLink(path)) {\n return path;\n }\n\n if (path.startsWith(\"./\") || path.startsWith(\"../\")) {\n return path;\n }\n\n var base = (_ref = (_prefix = prefix) !== null && _prefix !== void 0 ? _prefix : getGlobalPathPrefix()) !== null && _ref !== void 0 ? _ref : \"/\";\n return \"\" + ((base === null || base === void 0 ? void 0 : base.endsWith(\"/\")) ? base.slice(0, -1) : base) + (path.startsWith(\"/\") ? path : \"/\" + path);\n} // These global values are wrapped in typeof clauses to ensure the values exist.\n// This is especially problematic in unit testing of this component.\n\n\nvar getGlobalPathPrefix = function getGlobalPathPrefix() {\n return process.env.NODE_ENV !== \"production\" ? typeof __PATH_PREFIX__ !== \"undefined\" ? __PATH_PREFIX__ : undefined : __PATH_PREFIX__;\n};\n\nvar getGlobalBasePrefix = function getGlobalBasePrefix() {\n return process.env.NODE_ENV !== \"production\" ? typeof __BASE_PATH__ !== \"undefined\" ? __BASE_PATH__ : undefined : __BASE_PATH__;\n};\n\nvar isLocalLink = function isLocalLink(path) {\n return path && !path.startsWith(\"http://\") && !path.startsWith(\"https://\") && !path.startsWith(\"//\");\n};\n\nfunction withAssetPrefix(path) {\n return withPrefix(path, getGlobalPathPrefix());\n}\n\nfunction absolutify(path, current) {\n // If it's already absolute, return as-is\n if (isAbsolutePath(path)) {\n return path;\n }\n\n return (0, _utils.resolve)(path, current);\n}\n\nvar rewriteLinkPath = function rewriteLinkPath(path, relativeTo) {\n if (typeof path === \"number\") {\n return path;\n }\n\n if (!isLocalLink(path)) {\n return path;\n }\n\n return isAbsolutePath(path) ? withPrefix(path) : absolutify(path, relativeTo);\n};\n\nvar NavLinkPropTypes = {\n activeClassName: _propTypes.default.string,\n activeStyle: _propTypes.default.object,\n partiallyActive: _propTypes.default.bool\n}; // Set up IntersectionObserver\n\nvar createIntersectionObserver = function createIntersectionObserver(el, cb) {\n var io = new window.IntersectionObserver(function (entries) {\n entries.forEach(function (entry) {\n if (el === entry.target) {\n // Check if element is within viewport, remove listener, destroy observer, and run link callback.\n // MSEdge doesn't currently support isIntersecting, so also test for an intersectionRatio > 0\n if (entry.isIntersecting || entry.intersectionRatio > 0) {\n io.unobserve(el);\n io.disconnect();\n cb();\n }\n }\n });\n }); // Add element to the observer\n\n io.observe(el);\n return {\n instance: io,\n el: el\n };\n};\n\nfunction GatsbyLinkLocationWrapper(props) {\n return /*#__PURE__*/_react.default.createElement(_router.Location, null, function (_ref2) {\n var location = _ref2.location;\n return /*#__PURE__*/_react.default.createElement(GatsbyLink, (0, _extends2.default)({}, props, {\n _location: location\n }));\n });\n}\n\nvar GatsbyLink = /*#__PURE__*/function (_React$Component) {\n (0, _inheritsLoose2.default)(GatsbyLink, _React$Component);\n\n function GatsbyLink(props) {\n var _this;\n\n _this = _React$Component.call(this, props) || this; // Default to no support for IntersectionObserver\n\n _this.defaultGetProps = function (_ref3) {\n var isPartiallyCurrent = _ref3.isPartiallyCurrent,\n isCurrent = _ref3.isCurrent;\n\n if (_this.props.partiallyActive ? isPartiallyCurrent : isCurrent) {\n return {\n className: [_this.props.className, _this.props.activeClassName].filter(Boolean).join(\" \"),\n style: (0, _extends2.default)({}, _this.props.style, _this.props.activeStyle)\n };\n }\n\n return null;\n };\n\n var IOSupported = false;\n\n if (typeof window !== \"undefined\" && window.IntersectionObserver) {\n IOSupported = true;\n }\n\n _this.state = {\n IOSupported: IOSupported\n };\n _this.handleRef = _this.handleRef.bind((0, _assertThisInitialized2.default)(_this));\n return _this;\n }\n\n var _proto = GatsbyLink.prototype;\n\n _proto._prefetch = function _prefetch() {\n var currentPath = window.location.pathname; // reach router should have the correct state\n\n if (this.props._location && this.props._location.pathname) {\n currentPath = this.props._location.pathname;\n }\n\n var rewrittenPath = rewriteLinkPath(this.props.to, currentPath);\n var newPathName = (0, _parsePath.parsePath)(rewrittenPath).pathname; // Prefech is used to speed up next navigations. When you use it on the current navigation,\n // there could be a race-condition where Chrome uses the stale data instead of waiting for the network to complete\n\n if (currentPath !== newPathName) {\n ___loader.enqueue(newPathName);\n }\n };\n\n _proto.componentDidUpdate = function componentDidUpdate(prevProps, prevState) {\n // Preserve non IO functionality if no support\n if (this.props.to !== prevProps.to && !this.state.IOSupported) {\n this._prefetch();\n }\n };\n\n _proto.componentDidMount = function componentDidMount() {\n // Preserve non IO functionality if no support\n if (!this.state.IOSupported) {\n this._prefetch();\n }\n };\n\n _proto.componentWillUnmount = function componentWillUnmount() {\n if (!this.io) {\n return;\n }\n\n var _this$io = this.io,\n instance = _this$io.instance,\n el = _this$io.el;\n instance.unobserve(el);\n instance.disconnect();\n };\n\n _proto.handleRef = function handleRef(ref) {\n var _this2 = this;\n\n if (this.props.innerRef && this.props.innerRef.hasOwnProperty(\"current\")) {\n this.props.innerRef.current = ref;\n } else if (this.props.innerRef) {\n this.props.innerRef(ref);\n }\n\n if (this.state.IOSupported && ref) {\n // If IO supported and element reference found, setup Observer functionality\n this.io = createIntersectionObserver(ref, function () {\n _this2._prefetch();\n });\n }\n };\n\n _proto.render = function render() {\n var _this3 = this;\n\n var _this$props = this.props,\n to = _this$props.to,\n _this$props$getProps = _this$props.getProps,\n getProps = _this$props$getProps === void 0 ? this.defaultGetProps : _this$props$getProps,\n _onClick = _this$props.onClick,\n _onMouseEnter = _this$props.onMouseEnter,\n $activeClassName = _this$props.activeClassName,\n $activeStyle = _this$props.activeStyle,\n $innerRef = _this$props.innerRef,\n partiallyActive = _this$props.partiallyActive,\n state = _this$props.state,\n replace = _this$props.replace,\n _location = _this$props._location,\n rest = (0, _objectWithoutPropertiesLoose2.default)(_this$props, [\"to\", \"getProps\", \"onClick\", \"onMouseEnter\", \"activeClassName\", \"activeStyle\", \"innerRef\", \"partiallyActive\", \"state\", \"replace\", \"_location\"]);\n\n if (process.env.NODE_ENV !== \"production\" && !isLocalLink(to)) {\n console.warn(\"External link \" + to + \" was detected in a Link component. Use the Link component only for internal links. See: https://gatsby.dev/internal-links\");\n }\n\n var prefixedTo = rewriteLinkPath(to, _location.pathname);\n\n if (!isLocalLink(prefixedTo)) {\n return /*#__PURE__*/_react.default.createElement(\"a\", (0, _extends2.default)({\n href: prefixedTo\n }, rest));\n }\n\n return /*#__PURE__*/_react.default.createElement(_router.Link, (0, _extends2.default)({\n to: prefixedTo,\n state: state,\n getProps: getProps,\n innerRef: this.handleRef,\n onMouseEnter: function onMouseEnter(e) {\n if (_onMouseEnter) {\n _onMouseEnter(e);\n }\n\n ___loader.hovering((0, _parsePath.parsePath)(prefixedTo).pathname);\n },\n onClick: function onClick(e) {\n if (_onClick) {\n _onClick(e);\n }\n\n if (e.button === 0 && // ignore right clicks\n !_this3.props.target && // let browser handle \"target=_blank\"\n !e.defaultPrevented && // onClick prevented default\n !e.metaKey && // ignore clicks with modifier keys...\n !e.altKey && !e.ctrlKey && !e.shiftKey) {\n e.preventDefault();\n var shouldReplace = replace;\n\n var isCurrent = encodeURI(prefixedTo) === _location.pathname;\n\n if (typeof replace !== \"boolean\" && isCurrent) {\n shouldReplace = true;\n } // Make sure the necessary scripts and data are\n // loaded before continuing.\n\n\n window.___navigate(prefixedTo, {\n state: state,\n replace: shouldReplace\n });\n }\n\n return true;\n }\n }, rest));\n };\n\n return GatsbyLink;\n}(_react.default.Component);\n\nGatsbyLink.propTypes = (0, _extends2.default)({}, NavLinkPropTypes, {\n onClick: _propTypes.default.func,\n to: _propTypes.default.string.isRequired,\n replace: _propTypes.default.bool,\n state: _propTypes.default.object\n});\n\nvar showDeprecationWarning = function showDeprecationWarning(functionName, altFunctionName, version) {\n return console.warn(\"The \\\"\" + functionName + \"\\\" method is now deprecated and will be removed in Gatsby v\" + version + \". Please use \\\"\" + altFunctionName + \"\\\" instead.\");\n};\n\nvar _default = /*#__PURE__*/_react.default.forwardRef(function (props, ref) {\n return /*#__PURE__*/_react.default.createElement(GatsbyLinkLocationWrapper, (0, _extends2.default)({\n innerRef: ref\n }, props));\n});\n\nexports.default = _default;\n\nvar navigate = function navigate(to, options) {\n window.___navigate(rewriteLinkPath(to, window.location.pathname), options);\n};\n\nexports.navigate = navigate;\n\nvar push = function push(to) {\n showDeprecationWarning(\"push\", \"navigate\", 3);\n\n window.___push(rewriteLinkPath(to, window.location.pathname));\n};\n\nexports.push = push;\n\nvar replace = function replace(to) {\n showDeprecationWarning(\"replace\", \"navigate\", 3);\n\n window.___replace(rewriteLinkPath(to, window.location.pathname));\n}; // TODO: Remove navigateTo for Gatsby v3\n\n\nexports.replace = replace;\n\nvar navigateTo = function navigateTo(to) {\n showDeprecationWarning(\"navigateTo\", \"navigate\", 3);\n return push(to);\n};\n\nexports.navigateTo = navigateTo;","\"use strict\";\n\nexports.__esModule = true;\nexports.SessionStorage = void 0;\nvar STATE_KEY_PREFIX = \"@@scroll|\";\nvar GATSBY_ROUTER_SCROLL_STATE = \"___GATSBY_REACT_ROUTER_SCROLL\";\n\nvar SessionStorage = /*#__PURE__*/function () {\n function SessionStorage() {}\n\n var _proto = SessionStorage.prototype;\n\n _proto.read = function read(location, key) {\n var stateKey = this.getStateKey(location, key);\n\n try {\n var value = window.sessionStorage.getItem(stateKey);\n return value ? JSON.parse(value) : 0;\n } catch (e) {\n if (process.env.NODE_ENV !== \"production\") {\n console.warn(\"[gatsby-react-router-scroll] Unable to access sessionStorage; sessionStorage is not available.\");\n }\n\n if (window && window[GATSBY_ROUTER_SCROLL_STATE] && window[GATSBY_ROUTER_SCROLL_STATE][stateKey]) {\n return window[GATSBY_ROUTER_SCROLL_STATE][stateKey];\n }\n\n return 0;\n }\n };\n\n _proto.save = function save(location, key, value) {\n var stateKey = this.getStateKey(location, key);\n var storedValue = JSON.stringify(value);\n\n try {\n window.sessionStorage.setItem(stateKey, storedValue);\n } catch (e) {\n if (window && window[GATSBY_ROUTER_SCROLL_STATE]) {\n window[GATSBY_ROUTER_SCROLL_STATE][stateKey] = JSON.parse(storedValue);\n } else {\n window[GATSBY_ROUTER_SCROLL_STATE] = {};\n window[GATSBY_ROUTER_SCROLL_STATE][stateKey] = JSON.parse(storedValue);\n }\n\n if (process.env.NODE_ENV !== \"production\") {\n console.warn(\"[gatsby-react-router-scroll] Unable to save state in sessionStorage; sessionStorage is not available.\");\n }\n }\n };\n\n _proto.getStateKey = function getStateKey(location, key) {\n var stateKeyBase = \"\" + STATE_KEY_PREFIX + location.pathname;\n return key === null || typeof key === \"undefined\" ? stateKeyBase : stateKeyBase + \"|\" + key;\n };\n\n return SessionStorage;\n}();\n\nexports.SessionStorage = SessionStorage;","var _typeof = require(\"@babel/runtime/helpers/typeof\")[\"default\"];\n\nfunction _getRequireWildcardCache() {\n if (typeof WeakMap !== \"function\") return null;\n var cache = new WeakMap();\n\n _getRequireWildcardCache = function _getRequireWildcardCache() {\n return cache;\n };\n\n return cache;\n}\n\nfunction _interopRequireWildcard(obj) {\n if (obj && obj.__esModule) {\n return obj;\n }\n\n if (obj === null || _typeof(obj) !== \"object\" && typeof obj !== \"function\") {\n return {\n \"default\": obj\n };\n }\n\n var cache = _getRequireWildcardCache();\n\n if (cache && cache.has(obj)) {\n return cache.get(obj);\n }\n\n var newObj = {};\n var hasPropertyDescriptor = Object.defineProperty && Object.getOwnPropertyDescriptor;\n\n for (var key in obj) {\n if (Object.prototype.hasOwnProperty.call(obj, key)) {\n var desc = hasPropertyDescriptor ? Object.getOwnPropertyDescriptor(obj, key) : null;\n\n if (desc && (desc.get || desc.set)) {\n Object.defineProperty(newObj, key, desc);\n } else {\n newObj[key] = obj[key];\n }\n }\n }\n\n newObj[\"default\"] = obj;\n\n if (cache) {\n cache.set(obj, newObj);\n }\n\n return newObj;\n}\n\nmodule.exports = _interopRequireWildcard;\nmodule.exports[\"default\"] = module.exports, module.exports.__esModule = true;","'use strict';\n\nvar reactIs = require('react-is');\n/**\n * Copyright 2015, Yahoo! Inc.\n * Copyrights licensed under the New BSD License. See the accompanying LICENSE file for terms.\n */\n\n\nvar REACT_STATICS = {\n childContextTypes: true,\n contextType: true,\n contextTypes: true,\n defaultProps: true,\n displayName: true,\n getDefaultProps: true,\n getDerivedStateFromError: true,\n getDerivedStateFromProps: true,\n mixins: true,\n propTypes: true,\n type: true\n};\nvar KNOWN_STATICS = {\n name: true,\n length: true,\n prototype: true,\n caller: true,\n callee: true,\n arguments: true,\n arity: true\n};\nvar FORWARD_REF_STATICS = {\n '$$typeof': true,\n render: true,\n defaultProps: true,\n displayName: true,\n propTypes: true\n};\nvar MEMO_STATICS = {\n '$$typeof': true,\n compare: true,\n defaultProps: true,\n displayName: true,\n propTypes: true,\n type: true\n};\nvar TYPE_STATICS = {};\nTYPE_STATICS[reactIs.ForwardRef] = FORWARD_REF_STATICS;\nTYPE_STATICS[reactIs.Memo] = MEMO_STATICS;\n\nfunction getStatics(component) {\n // React v16.11 and below\n if (reactIs.isMemo(component)) {\n return MEMO_STATICS;\n } // React v16.12 and above\n\n\n return TYPE_STATICS[component['$$typeof']] || REACT_STATICS;\n}\n\nvar defineProperty = Object.defineProperty;\nvar getOwnPropertyNames = Object.getOwnPropertyNames;\nvar getOwnPropertySymbols = Object.getOwnPropertySymbols;\nvar getOwnPropertyDescriptor = Object.getOwnPropertyDescriptor;\nvar getPrototypeOf = Object.getPrototypeOf;\nvar objectPrototype = Object.prototype;\n\nfunction hoistNonReactStatics(targetComponent, sourceComponent, blacklist) {\n if (typeof sourceComponent !== 'string') {\n // don't hoist over string (html) components\n if (objectPrototype) {\n var inheritedComponent = getPrototypeOf(sourceComponent);\n\n if (inheritedComponent && inheritedComponent !== objectPrototype) {\n hoistNonReactStatics(targetComponent, inheritedComponent, blacklist);\n }\n }\n\n var keys = getOwnPropertyNames(sourceComponent);\n\n if (getOwnPropertySymbols) {\n keys = keys.concat(getOwnPropertySymbols(sourceComponent));\n }\n\n var targetStatics = getStatics(targetComponent);\n var sourceStatics = getStatics(sourceComponent);\n\n for (var i = 0; i < keys.length; ++i) {\n var key = keys[i];\n\n if (!KNOWN_STATICS[key] && !(blacklist && blacklist[key]) && !(sourceStatics && sourceStatics[key]) && !(targetStatics && targetStatics[key])) {\n var descriptor = getOwnPropertyDescriptor(sourceComponent, key);\n\n try {\n // Avoid failures from read-only properties\n defineProperty(targetComponent, key, descriptor);\n } catch (e) {}\n }\n }\n }\n\n return targetComponent;\n}\n\nmodule.exports = hoistNonReactStatics;","export default path => {\n if (path === undefined) {\n return path\n }\n if (path === `/`) {\n return `/`\n }\n if (path.charAt(path.length - 1) === `/`) {\n return path.slice(0, -1)\n }\n return path\n}\n","import { pick } from \"@reach/router/lib/utils\"\nimport stripPrefix from \"./strip-prefix\"\nimport normalizePagePath from \"./normalize-page-path\"\n\nconst pathCache = new Map()\nlet matchPaths = []\n\nconst trimPathname = rawPathname => {\n const pathname = decodeURIComponent(rawPathname)\n // Remove the pathPrefix from the pathname.\n const trimmedPathname = stripPrefix(pathname, __BASE_PATH__)\n // Remove any hashfragment\n .split(`#`)[0]\n // Remove search query\n .split(`?`)[0]\n\n return trimmedPathname\n}\n\nfunction absolutify(path) {\n // If it's already absolute, return as-is\n if (\n path.startsWith(`/`) ||\n path.startsWith(`https://`) ||\n path.startsWith(`http://`)\n ) {\n return path\n }\n // Calculate path relative to current location, adding a trailing slash to\n // match behavior of @reach/router\n return new URL(\n path,\n window.location.href + (window.location.href.endsWith(`/`) ? `` : `/`)\n ).pathname\n}\n\n/**\n * Set list of matchPaths\n *\n * @param {Array<{path: string, matchPath: string}>} value collection of matchPaths\n */\nexport const setMatchPaths = value => {\n matchPaths = value\n}\n\n/**\n * Return a matchpath url\n * if `match-paths.json` contains `{ \"/foo*\": \"/page1\", ...}`, then\n * `/foo?bar=far` => `/page1`\n *\n * @param {string} rawPathname A raw pathname\n * @return {string|null}\n */\nexport const findMatchPath = rawPathname => {\n const trimmedPathname = cleanPath(rawPathname)\n\n const pickPaths = matchPaths.map(({ path, matchPath }) => {\n return {\n path: matchPath,\n originalPath: path,\n }\n })\n\n const path = pick(pickPaths, trimmedPathname)\n\n if (path) {\n return normalizePagePath(path.route.originalPath)\n }\n\n return null\n}\n\n/**\n * Return a matchpath params from reach/router rules\n * if `match-paths.json` contains `{ \":bar/*foo\" }`, and the path is /baz/zaz/zoo\n * then it returns\n * { bar: baz, foo: zaz/zoo }\n *\n * @param {string} rawPathname A raw pathname\n * @return {object}\n */\nexport const grabMatchParams = rawPathname => {\n const trimmedPathname = cleanPath(rawPathname)\n\n const pickPaths = matchPaths.map(({ path, matchPath }) => {\n return {\n path: matchPath,\n originalPath: path,\n }\n })\n\n const path = pick(pickPaths, trimmedPathname)\n\n if (path) {\n return path.params\n }\n\n return {}\n}\n\n// Given a raw URL path, returns the cleaned version of it (trim off\n// `#` and query params), or if it matches an entry in\n// `match-paths.json`, its matched path is returned\n//\n// E.g. `/foo?bar=far` => `/foo`\n//\n// Or if `match-paths.json` contains `{ \"/foo*\": \"/page1\", ...}`, then\n// `/foo?bar=far` => `/page1`\nexport const findPath = rawPathname => {\n const trimmedPathname = trimPathname(absolutify(rawPathname))\n if (pathCache.has(trimmedPathname)) {\n return pathCache.get(trimmedPathname)\n }\n\n let foundPath = findMatchPath(trimmedPathname)\n\n if (!foundPath) {\n foundPath = cleanPath(rawPathname)\n }\n\n pathCache.set(trimmedPathname, foundPath)\n\n return foundPath\n}\n\n/**\n * Clean a url and converts /index.html => /\n * E.g. `/foo?bar=far` => `/foo`\n *\n * @param {string} rawPathname A raw pathname\n * @return {string}\n */\nexport const cleanPath = rawPathname => {\n const trimmedPathname = trimPathname(absolutify(rawPathname))\n\n let foundPath = trimmedPathname\n if (foundPath === `/index.html`) {\n foundPath = `/`\n }\n\n foundPath = normalizePagePath(foundPath)\n\n return foundPath\n}\n","// Duotone Dark\n// Author: Simurai, adapted from DuoTone themes for Atom (http://simurai.com/projects/2016/01/01/duotone-themes)\n// Conversion: Bram de Haan (http://atelierbram.github.io/Base2Tone-prism/output/prism/prism-base2tone-evening-dark.css)\n// Generated with Base16 Builder (https://github.com/base16-builder/base16-builder)\nvar theme = {\n plain: {\n backgroundColor: \"#2a2734\",\n color: \"#9a86fd\"\n },\n styles: [{\n types: [\"comment\", \"prolog\", \"doctype\", \"cdata\", \"punctuation\"],\n style: {\n color: \"#6c6783\"\n }\n }, {\n types: [\"namespace\"],\n style: {\n opacity: 0.7\n }\n }, {\n types: [\"tag\", \"operator\", \"number\"],\n style: {\n color: \"#e09142\"\n }\n }, {\n types: [\"property\", \"function\"],\n style: {\n color: \"#9a86fd\"\n }\n }, {\n types: [\"tag-id\", \"selector\", \"atrule-id\"],\n style: {\n color: \"#eeebff\"\n }\n }, {\n types: [\"attr-name\"],\n style: {\n color: \"#c4b9fe\"\n }\n }, {\n types: [\"boolean\", \"string\", \"entity\", \"url\", \"attr-value\", \"keyword\", \"control\", \"directive\", \"unit\", \"statement\", \"regex\", \"at-rule\", \"placeholder\", \"variable\"],\n style: {\n color: \"#ffcc99\"\n }\n }, {\n types: [\"deleted\"],\n style: {\n textDecorationLine: \"line-through\"\n }\n }, {\n types: [\"inserted\"],\n style: {\n textDecorationLine: \"underline\"\n }\n }, {\n types: [\"italic\"],\n style: {\n fontStyle: \"italic\"\n }\n }, {\n types: [\"important\", \"bold\"],\n style: {\n fontWeight: \"bold\"\n }\n }, {\n types: [\"important\"],\n style: {\n color: \"#c4b9fe\"\n }\n }]\n};\nexport default theme;","import Prism from '../prism/index.js';\nexport { default as Prism } from '../prism/index.js';\nimport theme from '../themes/duotoneDark';\nimport { Component } from 'react';\nvar defaultProps = {\n // $FlowFixMe\n Prism: Prism,\n theme: theme\n};\n\nfunction _defineProperty(obj, key, value) {\n if (key in obj) {\n Object.defineProperty(obj, key, {\n value: value,\n enumerable: true,\n configurable: true,\n writable: true\n });\n } else {\n obj[key] = value;\n }\n\n return obj;\n}\n\nfunction _extends() {\n _extends = Object.assign || function (target) {\n for (var i = 1; i < arguments.length; i++) {\n var source = arguments[i];\n\n for (var key in source) {\n if (Object.prototype.hasOwnProperty.call(source, key)) {\n target[key] = source[key];\n }\n }\n }\n\n return target;\n };\n\n return _extends.apply(this, arguments);\n}\n\nvar newlineRe = /\\r\\n|\\r|\\n/; // Empty lines need to contain a single empty token, denoted with { empty: true }\n\nvar normalizeEmptyLines = function normalizeEmptyLines(line) {\n if (line.length === 0) {\n line.push({\n types: [\"plain\"],\n content: \"\\n\",\n empty: true\n });\n } else if (line.length === 1 && line[0].content === \"\") {\n line[0].content = \"\\n\";\n line[0].empty = true;\n }\n};\n\nvar appendTypes = function appendTypes(types, add) {\n var typesSize = types.length;\n\n if (typesSize > 0 && types[typesSize - 1] === add) {\n return types;\n }\n\n return types.concat(add);\n}; // Takes an array of Prism's tokens and groups them by line, turning plain\n// strings into tokens as well. Tokens can become recursive in some cases,\n// which means that their types are concatenated. Plain-string tokens however\n// are always of type \"plain\".\n// This is not recursive to avoid exceeding the call-stack limit, since it's unclear\n// how nested Prism's tokens can become\n\n\nvar normalizeTokens = function normalizeTokens(tokens) {\n var typeArrStack = [[]];\n var tokenArrStack = [tokens];\n var tokenArrIndexStack = [0];\n var tokenArrSizeStack = [tokens.length];\n var i = 0;\n var stackIndex = 0;\n var currentLine = [];\n var acc = [currentLine];\n\n while (stackIndex > -1) {\n while ((i = tokenArrIndexStack[stackIndex]++) < tokenArrSizeStack[stackIndex]) {\n var content = void 0;\n var types = typeArrStack[stackIndex];\n var tokenArr = tokenArrStack[stackIndex];\n var token = tokenArr[i]; // Determine content and append type to types if necessary\n\n if (typeof token === \"string\") {\n types = stackIndex > 0 ? types : [\"plain\"];\n content = token;\n } else {\n types = appendTypes(types, token.type);\n\n if (token.alias) {\n types = appendTypes(types, token.alias);\n }\n\n content = token.content;\n } // If token.content is an array, increase the stack depth and repeat this while-loop\n\n\n if (typeof content !== \"string\") {\n stackIndex++;\n typeArrStack.push(types);\n tokenArrStack.push(content);\n tokenArrIndexStack.push(0);\n tokenArrSizeStack.push(content.length);\n continue;\n } // Split by newlines\n\n\n var splitByNewlines = content.split(newlineRe);\n var newlineCount = splitByNewlines.length;\n currentLine.push({\n types: types,\n content: splitByNewlines[0]\n }); // Create a new line for each string on a new line\n\n for (var i$1 = 1; i$1 < newlineCount; i$1++) {\n normalizeEmptyLines(currentLine);\n acc.push(currentLine = []);\n currentLine.push({\n types: types,\n content: splitByNewlines[i$1]\n });\n }\n } // Decreate the stack depth\n\n\n stackIndex--;\n typeArrStack.pop();\n tokenArrStack.pop();\n tokenArrIndexStack.pop();\n tokenArrSizeStack.pop();\n }\n\n normalizeEmptyLines(currentLine);\n return acc;\n};\n\nvar themeToDict = function themeToDict(theme, language) {\n var plain = theme.plain; // $FlowFixMe\n\n var base = Object.create(null);\n var themeDict = theme.styles.reduce(function (acc, themeEntry) {\n var languages = themeEntry.languages;\n var style = themeEntry.style;\n\n if (languages && !languages.includes(language)) {\n return acc;\n }\n\n themeEntry.types.forEach(function (type) {\n // $FlowFixMe\n var accStyle = _extends({}, acc[type], style);\n\n acc[type] = accStyle;\n });\n return acc;\n }, base); // $FlowFixMe\n\n themeDict.root = plain; // $FlowFixMe\n\n themeDict.plain = _extends({}, plain, {\n backgroundColor: null\n });\n return themeDict;\n};\n\nfunction objectWithoutProperties(obj, exclude) {\n var target = {};\n\n for (var k in obj) {\n if (Object.prototype.hasOwnProperty.call(obj, k) && exclude.indexOf(k) === -1) target[k] = obj[k];\n }\n\n return target;\n}\n\nvar Highlight = /*@__PURE__*/function (Component) {\n function Highlight() {\n var this$1 = this;\n var args = [],\n len = arguments.length;\n\n while (len--) {\n args[len] = arguments[len];\n }\n\n Component.apply(this, args);\n\n _defineProperty(this, \"getThemeDict\", function (props) {\n if (this$1.themeDict !== undefined && props.theme === this$1.prevTheme && props.language === this$1.prevLanguage) {\n return this$1.themeDict;\n }\n\n this$1.prevTheme = props.theme;\n this$1.prevLanguage = props.language;\n var themeDict = props.theme ? themeToDict(props.theme, props.language) : undefined;\n return this$1.themeDict = themeDict;\n });\n\n _defineProperty(this, \"getLineProps\", function (ref) {\n var key = ref.key;\n var className = ref.className;\n var style = ref.style;\n var rest$1 = objectWithoutProperties(ref, [\"key\", \"className\", \"style\", \"line\"]);\n var rest = rest$1;\n\n var output = _extends({}, rest, {\n className: \"token-line\",\n style: undefined,\n key: undefined\n });\n\n var themeDict = this$1.getThemeDict(this$1.props);\n\n if (themeDict !== undefined) {\n output.style = themeDict.plain;\n }\n\n if (style !== undefined) {\n output.style = output.style !== undefined ? _extends({}, output.style, style) : style;\n }\n\n if (key !== undefined) {\n output.key = key;\n }\n\n if (className) {\n output.className += \" \" + className;\n }\n\n return output;\n });\n\n _defineProperty(this, \"getStyleForToken\", function (ref) {\n var types = ref.types;\n var empty = ref.empty;\n var typesSize = types.length;\n var themeDict = this$1.getThemeDict(this$1.props);\n\n if (themeDict === undefined) {\n return undefined;\n } else if (typesSize === 1 && types[0] === \"plain\") {\n return empty ? {\n display: \"inline-block\"\n } : undefined;\n } else if (typesSize === 1 && !empty) {\n return themeDict[types[0]];\n }\n\n var baseStyle = empty ? {\n display: \"inline-block\"\n } : {}; // $FlowFixMe\n\n var typeStyles = types.map(function (type) {\n return themeDict[type];\n });\n return Object.assign.apply(Object, [baseStyle].concat(typeStyles));\n });\n\n _defineProperty(this, \"getTokenProps\", function (ref) {\n var key = ref.key;\n var className = ref.className;\n var style = ref.style;\n var token = ref.token;\n var rest$1 = objectWithoutProperties(ref, [\"key\", \"className\", \"style\", \"token\"]);\n var rest = rest$1;\n\n var output = _extends({}, rest, {\n className: \"token \" + token.types.join(\" \"),\n children: token.content,\n style: this$1.getStyleForToken(token),\n key: undefined\n });\n\n if (style !== undefined) {\n output.style = output.style !== undefined ? _extends({}, output.style, style) : style;\n }\n\n if (key !== undefined) {\n output.key = key;\n }\n\n if (className) {\n output.className += \" \" + className;\n }\n\n return output;\n });\n\n _defineProperty(this, \"tokenize\", function (Prism, code, grammar, language) {\n var env = {\n code: code,\n grammar: grammar,\n language: language,\n tokens: []\n };\n Prism.hooks.run(\"before-tokenize\", env);\n var tokens = env.tokens = Prism.tokenize(env.code, env.grammar, env.language);\n Prism.hooks.run(\"after-tokenize\", env);\n return tokens;\n });\n }\n\n if (Component) Highlight.__proto__ = Component;\n Highlight.prototype = Object.create(Component && Component.prototype);\n Highlight.prototype.constructor = Highlight;\n\n Highlight.prototype.render = function render() {\n var ref = this.props;\n var Prism = ref.Prism;\n var language = ref.language;\n var code = ref.code;\n var children = ref.children;\n var themeDict = this.getThemeDict(this.props);\n var grammar = Prism.languages[language];\n var mixedTokens = grammar !== undefined ? this.tokenize(Prism, code, grammar, language) : [code];\n var tokens = normalizeTokens(mixedTokens);\n return children({\n tokens: tokens,\n className: \"prism-code language-\" + language,\n style: themeDict !== undefined ? themeDict.root : {},\n getLineProps: this.getLineProps,\n getTokenProps: this.getTokenProps\n });\n };\n\n return Highlight;\n}(Component);\n\nexport default Highlight;\nexport { defaultProps };","module.exports = \"data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSIxMi41MTciIGhlaWdodD0iMTAuMTY2IiB2aWV3Qm94PSIwIDAgMTIuNTE3IDEwLjE2NiI+CiAgICA8ZGVmcz4KICAgICAgICA8c3R5bGU+CiAgICAgICAgICAgIC5jbHMtMXtmaWxsOiMyNDI5MmV9CiAgICAgICAgPC9zdHlsZT4KICAgIDwvZGVmcz4KICAgIDxwYXRoIGlkPSJ0d2l0dGVyLWJyYW5kcyIgZD0iTTExLjIzIDUwLjYxNmMuMDA4LjExMS4wMDguMjIyLjAwOC4zMzRhNy4yNDkgNy4yNDkgMCAwIDEtNy4zIDcuM0E3LjI0OSA3LjI0OSAwIDAgMSAwIDU3LjFhNS4zMDcgNS4zMDcgMCAwIDAgLjYxOS4wMzIgNS4xMzggNS4xMzggMCAwIDAgMy4xODUtMS4xIDIuNTcgMi41NyAwIDAgMS0yLjQtMS43NzkgMy4yMzUgMy4yMzUgMCAwIDAgLjQ4NC4wNCAyLjcxMyAyLjcxMyAwIDAgMCAuNjc1LS4wODcgMi41NjYgMi41NjYgMCAwIDEtMi4wNTUtMi41MTh2LS4wMzJhMi41ODQgMi41ODQgMCAwIDAgMS4xNi4zMjYgMi41NjkgMi41NjkgMCAwIDEtLjc5NC0zLjQzMSA3LjI5MiA3LjI5MiAwIDAgMCA1LjI5IDIuNjg0IDIuOSAyLjkgMCAwIDEtLjA2NC0uNTg4IDIuNTY4IDIuNTY4IDAgMCAxIDQuNDQtMS43NTUgNS4wNTEgNS4wNTEgMCAwIDAgMS42MjgtLjYxOSAyLjU1OCAyLjU1OCAwIDAgMS0xLjEyOCAxLjQxNCA1LjE0MyA1LjE0MyAwIDAgMCAxLjQ3Ny0uNCA1LjUxNSA1LjUxNSAwIDAgMS0xLjI4NyAxLjMyNnoiIGNsYXNzPSJjbHMtMSIgdHJhbnNmb3JtPSJ0cmFuc2xhdGUoMCAtNDguMDgyKSIvPgo8L3N2Zz4K\"","\"use strict\";\n\nexports.__esModule = true;\nexports.useScrollRestoration = useScrollRestoration;\n\nvar _scrollHandler = require(\"./scroll-handler\");\n\nvar _react = require(\"react\");\n\nvar _router = require(\"@reach/router\");\n\nfunction useScrollRestoration(identifier) {\n var location = (0, _router.useLocation)();\n var state = (0, _react.useContext)(_scrollHandler.ScrollContext);\n var ref = (0, _react.useRef)();\n (0, _react.useLayoutEffect)(function () {\n if (ref.current) {\n var position = state.read(location, identifier);\n ref.current.scrollTo(0, position || 0);\n }\n }, []);\n return {\n ref: ref,\n onScroll: function onScroll() {\n if (ref.current) {\n state.save(location, identifier, ref.current.scrollTop);\n }\n }\n };\n}","function memoize(fn) {\n var cache = {};\n return function (arg) {\n if (cache[arg] === undefined) cache[arg] = fn(arg);\n return cache[arg];\n };\n}\n\nexport default memoize;","// \n// An event handler can take an optional event argument\n// and should not return a value\n \n \n\n// An array of all currently registered event handlers for a type\n \n \n// A map of event types and their corresponding event handlers.\n \n \n \n \n\n/** Mitt: Tiny (~200b) functional event emitter / pubsub.\n * @name mitt\n * @returns {Mitt}\n */\nfunction mitt(all ) {\n\tall = all || Object.create(null);\n\n\treturn {\n\t\t/**\n\t\t * Register an event handler for the given type.\n\t\t *\n\t\t * @param {String} type\tType of event to listen for, or `\"*\"` for all events\n\t\t * @param {Function} handler Function to call in response to given event\n\t\t * @memberOf mitt\n\t\t */\n\t\ton: function on(type , handler ) {\n\t\t\t(all[type] || (all[type] = [])).push(handler);\n\t\t},\n\n\t\t/**\n\t\t * Remove an event handler for the given type.\n\t\t *\n\t\t * @param {String} type\tType of event to unregister `handler` from, or `\"*\"`\n\t\t * @param {Function} handler Handler function to remove\n\t\t * @memberOf mitt\n\t\t */\n\t\toff: function off(type , handler ) {\n\t\t\tif (all[type]) {\n\t\t\t\tall[type].splice(all[type].indexOf(handler) >>> 0, 1);\n\t\t\t}\n\t\t},\n\n\t\t/**\n\t\t * Invoke all handlers for the given type.\n\t\t * If present, `\"*\"` handlers are invoked after type-matched handlers.\n\t\t *\n\t\t * @param {String} type The event type to invoke\n\t\t * @param {Any} [evt] Any value (object is recommended and powerful), passed to each handler\n\t\t * @memberOf mitt\n\t\t */\n\t\temit: function emit(type , evt ) {\n\t\t\t(all[type] || []).slice().map(function (handler) { handler(evt); });\n\t\t\t(all['*'] || []).slice().map(function (handler) { handler(type, evt); });\n\t\t}\n\t};\n}\n\nexport default mitt;\n//# sourceMappingURL=mitt.es.js.map\n","import mitt from \"mitt\"\n\nconst emitter = mitt()\nexport default emitter\n","\"use strict\";\n\nexports.__esModule = true;\nexports.useScrollRestoration = exports.ScrollContainer = exports.ScrollContext = void 0;\n\nvar _scrollHandler = require(\"./scroll-handler\");\n\nexports.ScrollContext = _scrollHandler.ScrollHandler;\n\nvar _scrollContainer = require(\"./scroll-container\");\n\nexports.ScrollContainer = _scrollContainer.ScrollContainer;\n\nvar _useScrollRestoration = require(\"./use-scroll-restoration\");\n\nexports.useScrollRestoration = _useScrollRestoration.useScrollRestoration;","import React from 'react';\n\nfunction _defineProperty(obj, key, value) {\n if (key in obj) {\n Object.defineProperty(obj, key, {\n value: value,\n enumerable: true,\n configurable: true,\n writable: true\n });\n } else {\n obj[key] = value;\n }\n\n return obj;\n}\n\nfunction _extends() {\n _extends = Object.assign || function (target) {\n for (var i = 1; i < arguments.length; i++) {\n var source = arguments[i];\n\n for (var key in source) {\n if (Object.prototype.hasOwnProperty.call(source, key)) {\n target[key] = source[key];\n }\n }\n }\n\n return target;\n };\n\n return _extends.apply(this, arguments);\n}\n\nfunction ownKeys(object, enumerableOnly) {\n var keys = Object.keys(object);\n\n if (Object.getOwnPropertySymbols) {\n var symbols = Object.getOwnPropertySymbols(object);\n if (enumerableOnly) symbols = symbols.filter(function (sym) {\n return Object.getOwnPropertyDescriptor(object, sym).enumerable;\n });\n keys.push.apply(keys, symbols);\n }\n\n return keys;\n}\n\nfunction _objectSpread2(target) {\n for (var i = 1; i < arguments.length; i++) {\n var source = arguments[i] != null ? arguments[i] : {};\n\n if (i % 2) {\n ownKeys(Object(source), true).forEach(function (key) {\n _defineProperty(target, key, source[key]);\n });\n } else if (Object.getOwnPropertyDescriptors) {\n Object.defineProperties(target, Object.getOwnPropertyDescriptors(source));\n } else {\n ownKeys(Object(source)).forEach(function (key) {\n Object.defineProperty(target, key, Object.getOwnPropertyDescriptor(source, key));\n });\n }\n }\n\n return target;\n}\n\nfunction _objectWithoutPropertiesLoose(source, excluded) {\n if (source == null) return {};\n var target = {};\n var sourceKeys = Object.keys(source);\n var key, i;\n\n for (i = 0; i < sourceKeys.length; i++) {\n key = sourceKeys[i];\n if (excluded.indexOf(key) >= 0) continue;\n target[key] = source[key];\n }\n\n return target;\n}\n\nfunction _objectWithoutProperties(source, excluded) {\n if (source == null) return {};\n\n var target = _objectWithoutPropertiesLoose(source, excluded);\n\n var key, i;\n\n if (Object.getOwnPropertySymbols) {\n var sourceSymbolKeys = Object.getOwnPropertySymbols(source);\n\n for (i = 0; i < sourceSymbolKeys.length; i++) {\n key = sourceSymbolKeys[i];\n if (excluded.indexOf(key) >= 0) continue;\n if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue;\n target[key] = source[key];\n }\n }\n\n return target;\n}\n\nvar isFunction = function isFunction(obj) {\n return typeof obj === 'function';\n};\n\nvar MDXContext = /*#__PURE__*/React.createContext({});\n\nvar withMDXComponents = function withMDXComponents(Component) {\n return function (props) {\n var allComponents = useMDXComponents(props.components);\n return /*#__PURE__*/React.createElement(Component, _extends({}, props, {\n components: allComponents\n }));\n };\n};\n\nvar useMDXComponents = function useMDXComponents(components) {\n var contextComponents = React.useContext(MDXContext);\n var allComponents = contextComponents;\n\n if (components) {\n allComponents = isFunction(components) ? components(contextComponents) : _objectSpread2(_objectSpread2({}, contextComponents), components);\n }\n\n return allComponents;\n};\n\nvar MDXProvider = function MDXProvider(props) {\n var allComponents = useMDXComponents(props.components);\n return /*#__PURE__*/React.createElement(MDXContext.Provider, {\n value: allComponents\n }, props.children);\n};\n\nvar TYPE_PROP_NAME = 'mdxType';\nvar DEFAULTS = {\n inlineCode: 'code',\n wrapper: function wrapper(_ref) {\n var children = _ref.children;\n return /*#__PURE__*/React.createElement(React.Fragment, {}, children);\n }\n};\nvar MDXCreateElement = /*#__PURE__*/React.forwardRef(function (props, ref) {\n var propComponents = props.components,\n mdxType = props.mdxType,\n originalType = props.originalType,\n parentName = props.parentName,\n etc = _objectWithoutProperties(props, [\"components\", \"mdxType\", \"originalType\", \"parentName\"]);\n\n var components = useMDXComponents(propComponents);\n var type = mdxType;\n var Component = components[\"\".concat(parentName, \".\").concat(type)] || components[type] || DEFAULTS[type] || originalType;\n\n if (propComponents) {\n return /*#__PURE__*/React.createElement(Component, _objectSpread2(_objectSpread2({\n ref: ref\n }, etc), {}, {\n components: propComponents\n }));\n }\n\n return /*#__PURE__*/React.createElement(Component, _objectSpread2({\n ref: ref\n }, etc));\n});\nMDXCreateElement.displayName = 'MDXCreateElement';\n\nfunction createElement(type, props) {\n var args = arguments;\n var mdxType = props && props.mdxType;\n\n if (typeof type === 'string' || mdxType) {\n var argsLength = args.length;\n var createElementArgArray = new Array(argsLength);\n createElementArgArray[0] = MDXCreateElement;\n var newProps = {};\n\n for (var key in props) {\n if (hasOwnProperty.call(props, key)) {\n newProps[key] = props[key];\n }\n }\n\n newProps.originalType = type;\n newProps[TYPE_PROP_NAME] = typeof type === 'string' ? type : mdxType;\n createElementArgArray[1] = newProps;\n\n for (var i = 2; i < argsLength; i++) {\n createElementArgArray[i] = args[i];\n }\n\n return React.createElement.apply(null, createElementArgArray);\n }\n\n return React.createElement.apply(null, args);\n}\n\nexport { MDXContext, MDXProvider, createElement as mdx, useMDXComponents, withMDXComponents };","'use strict';\n\nfunction _interopDefault(ex) {\n return ex && typeof ex === 'object' && 'default' in ex ? ex['default'] : ex;\n}\n\nvar React = require('react');\n\nvar React__default = _interopDefault(React);\n\nvar shallowEqual = _interopDefault(require('shallowequal'));\n\nfunction _defineProperty(obj, key, value) {\n if (key in obj) {\n Object.defineProperty(obj, key, {\n value: value,\n enumerable: true,\n configurable: true,\n writable: true\n });\n } else {\n obj[key] = value;\n }\n\n return obj;\n}\n\nfunction _inheritsLoose(subClass, superClass) {\n subClass.prototype = Object.create(superClass.prototype);\n subClass.prototype.constructor = subClass;\n subClass.__proto__ = superClass;\n}\n\nvar canUseDOM = !!(typeof window !== 'undefined' && window.document && window.document.createElement);\n\nfunction withSideEffect(reducePropsToState, handleStateChangeOnClient, mapStateOnServer) {\n if (typeof reducePropsToState !== 'function') {\n throw new Error('Expected reducePropsToState to be a function.');\n }\n\n if (typeof handleStateChangeOnClient !== 'function') {\n throw new Error('Expected handleStateChangeOnClient to be a function.');\n }\n\n if (typeof mapStateOnServer !== 'undefined' && typeof mapStateOnServer !== 'function') {\n throw new Error('Expected mapStateOnServer to either be undefined or a function.');\n }\n\n function getDisplayName(WrappedComponent) {\n return WrappedComponent.displayName || WrappedComponent.name || 'Component';\n }\n\n return function wrap(WrappedComponent) {\n if (typeof WrappedComponent !== 'function') {\n throw new Error('Expected WrappedComponent to be a React component.');\n }\n\n var mountedInstances = [];\n var state;\n\n function emitChange() {\n state = reducePropsToState(mountedInstances.map(function (instance) {\n return instance.props;\n }));\n\n if (SideEffect.canUseDOM) {\n handleStateChangeOnClient(state);\n } else if (mapStateOnServer) {\n state = mapStateOnServer(state);\n }\n }\n\n var SideEffect = /*#__PURE__*/function (_Component) {\n _inheritsLoose(SideEffect, _Component);\n\n function SideEffect() {\n return _Component.apply(this, arguments) || this;\n } // Try to use displayName of wrapped component\n // Expose canUseDOM so tests can monkeypatch it\n\n\n SideEffect.peek = function peek() {\n return state;\n };\n\n SideEffect.rewind = function rewind() {\n if (SideEffect.canUseDOM) {\n throw new Error('You may only call rewind() on the server. Call peek() to read the current state.');\n }\n\n var recordedState = state;\n state = undefined;\n mountedInstances = [];\n return recordedState;\n };\n\n var _proto = SideEffect.prototype;\n\n _proto.shouldComponentUpdate = function shouldComponentUpdate(nextProps) {\n return !shallowEqual(nextProps, this.props);\n };\n\n _proto.componentWillMount = function componentWillMount() {\n mountedInstances.push(this);\n emitChange();\n };\n\n _proto.componentDidUpdate = function componentDidUpdate() {\n emitChange();\n };\n\n _proto.componentWillUnmount = function componentWillUnmount() {\n var index = mountedInstances.indexOf(this);\n mountedInstances.splice(index, 1);\n emitChange();\n };\n\n _proto.render = function render() {\n return React__default.createElement(WrappedComponent, this.props);\n };\n\n return SideEffect;\n }(React.Component);\n\n _defineProperty(SideEffect, \"displayName\", \"SideEffect(\" + getDisplayName(WrappedComponent) + \")\");\n\n _defineProperty(SideEffect, \"canUseDOM\", canUseDOM);\n\n return SideEffect;\n };\n}\n\nmodule.exports = withSideEffect;","function _objectWithoutPropertiesLoose(source, excluded) {\n if (source == null) return {};\n var target = {};\n var sourceKeys = Object.keys(source);\n var key, i;\n\n for (i = 0; i < sourceKeys.length; i++) {\n key = sourceKeys[i];\n if (excluded.indexOf(key) >= 0) continue;\n target[key] = source[key];\n }\n\n return target;\n}\n\nmodule.exports = _objectWithoutPropertiesLoose;\nmodule.exports[\"default\"] = module.exports, module.exports.__esModule = true;","exports.polyfill = Component => Component\n","var _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; };\n\nvar getLocation = function getLocation(source) {\n var _source$location = source.location,\n search = _source$location.search,\n hash = _source$location.hash,\n href = _source$location.href,\n origin = _source$location.origin,\n protocol = _source$location.protocol,\n host = _source$location.host,\n hostname = _source$location.hostname,\n port = _source$location.port;\n var pathname = source.location.pathname;\n\n\n if (!pathname && href && canUseDOM) {\n var url = new URL(href);\n pathname = url.pathname;\n }\n\n return {\n pathname: encodeURI(decodeURI(pathname)),\n search: search,\n hash: hash,\n href: href,\n origin: origin,\n protocol: protocol,\n host: host,\n hostname: hostname,\n port: port,\n state: source.history.state,\n key: source.history.state && source.history.state.key || \"initial\"\n };\n};\n\nvar createHistory = function createHistory(source, options) {\n var listeners = [];\n var location = getLocation(source);\n var transitioning = false;\n var resolveTransition = function resolveTransition() {};\n\n return {\n get location() {\n return location;\n },\n\n get transitioning() {\n return transitioning;\n },\n\n _onTransitionComplete: function _onTransitionComplete() {\n transitioning = false;\n resolveTransition();\n },\n listen: function listen(listener) {\n listeners.push(listener);\n\n var popstateListener = function popstateListener() {\n location = getLocation(source);\n listener({ location: location, action: \"POP\" });\n };\n\n source.addEventListener(\"popstate\", popstateListener);\n\n return function () {\n source.removeEventListener(\"popstate\", popstateListener);\n listeners = listeners.filter(function (fn) {\n return fn !== listener;\n });\n };\n },\n navigate: function navigate(to) {\n var _ref = arguments.length > 1 && arguments[1] !== undefined ? arguments[1] : {},\n state = _ref.state,\n _ref$replace = _ref.replace,\n replace = _ref$replace === undefined ? false : _ref$replace;\n\n if (typeof to === \"number\") {\n source.history.go(to);\n } else {\n state = _extends({}, state, { key: Date.now() + \"\" });\n // try...catch iOS Safari limits to 100 pushState calls\n try {\n if (transitioning || replace) {\n source.history.replaceState(state, null, to);\n } else {\n source.history.pushState(state, null, to);\n }\n } catch (e) {\n source.location[replace ? \"replace\" : \"assign\"](to);\n }\n }\n\n location = getLocation(source);\n transitioning = true;\n var transition = new Promise(function (res) {\n return resolveTransition = res;\n });\n listeners.forEach(function (listener) {\n return listener({ location: location, action: \"PUSH\" });\n });\n return transition;\n }\n };\n};\n\n////////////////////////////////////////////////////////////////////////////////\n// Stores history entries in memory for testing or other platforms like Native\nvar createMemorySource = function createMemorySource() {\n var initialPath = arguments.length > 0 && arguments[0] !== undefined ? arguments[0] : \"/\";\n\n var searchIndex = initialPath.indexOf(\"?\");\n var initialLocation = {\n pathname: searchIndex > -1 ? initialPath.substr(0, searchIndex) : initialPath,\n search: searchIndex > -1 ? initialPath.substr(searchIndex) : \"\"\n };\n var index = 0;\n var stack = [initialLocation];\n var states = [null];\n\n return {\n get location() {\n return stack[index];\n },\n addEventListener: function addEventListener(name, fn) {},\n removeEventListener: function removeEventListener(name, fn) {},\n\n history: {\n get entries() {\n return stack;\n },\n get index() {\n return index;\n },\n get state() {\n return states[index];\n },\n pushState: function pushState(state, _, uri) {\n var _uri$split = uri.split(\"?\"),\n pathname = _uri$split[0],\n _uri$split$ = _uri$split[1],\n search = _uri$split$ === undefined ? \"\" : _uri$split$;\n\n index++;\n stack.push({ pathname: pathname, search: search.length ? \"?\" + search : search });\n states.push(state);\n },\n replaceState: function replaceState(state, _, uri) {\n var _uri$split2 = uri.split(\"?\"),\n pathname = _uri$split2[0],\n _uri$split2$ = _uri$split2[1],\n search = _uri$split2$ === undefined ? \"\" : _uri$split2$;\n\n stack[index] = { pathname: pathname, search: search };\n states[index] = state;\n },\n go: function go(to) {\n var newIndex = index + to;\n\n if (newIndex < 0 || newIndex > states.length - 1) {\n return;\n }\n\n index = newIndex;\n }\n }\n };\n};\n\n////////////////////////////////////////////////////////////////////////////////\n// global history - uses window.history as the source if available, otherwise a\n// memory history\nvar canUseDOM = !!(typeof window !== \"undefined\" && window.document && window.document.createElement);\nvar getSource = function getSource() {\n return canUseDOM ? window : createMemorySource();\n};\n\nvar globalHistory = createHistory(getSource());\nvar navigate = globalHistory.navigate;\n\n////////////////////////////////////////////////////////////////////////////////\n\nexport { globalHistory, navigate, createHistory, createMemorySource };","import memoize from '@emotion/memoize';\nvar reactPropsRegex = /^((children|dangerouslySetInnerHTML|key|ref|autoFocus|defaultValue|defaultChecked|innerHTML|suppressContentEditableWarning|suppressHydrationWarning|valueLink|accept|acceptCharset|accessKey|action|allow|allowUserMedia|allowPaymentRequest|allowFullScreen|allowTransparency|alt|async|autoComplete|autoPlay|capture|cellPadding|cellSpacing|challenge|charSet|checked|cite|classID|className|cols|colSpan|content|contentEditable|contextMenu|controls|controlsList|coords|crossOrigin|data|dateTime|decoding|default|defer|dir|disabled|disablePictureInPicture|download|draggable|encType|form|formAction|formEncType|formMethod|formNoValidate|formTarget|frameBorder|headers|height|hidden|high|href|hrefLang|htmlFor|httpEquiv|id|inputMode|integrity|is|keyParams|keyType|kind|label|lang|list|loading|loop|low|marginHeight|marginWidth|max|maxLength|media|mediaGroup|method|min|minLength|multiple|muted|name|nonce|noValidate|open|optimum|pattern|placeholder|playsInline|poster|preload|profile|radioGroup|readOnly|referrerPolicy|rel|required|reversed|role|rows|rowSpan|sandbox|scope|scoped|scrolling|seamless|selected|shape|size|sizes|slot|span|spellCheck|src|srcDoc|srcLang|srcSet|start|step|style|summary|tabIndex|target|title|type|useMap|value|width|wmode|wrap|about|datatype|inlist|prefix|property|resource|typeof|vocab|autoCapitalize|autoCorrect|autoSave|color|inert|itemProp|itemScope|itemType|itemID|itemRef|on|results|security|unselectable|accentHeight|accumulate|additive|alignmentBaseline|allowReorder|alphabetic|amplitude|arabicForm|ascent|attributeName|attributeType|autoReverse|azimuth|baseFrequency|baselineShift|baseProfile|bbox|begin|bias|by|calcMode|capHeight|clip|clipPathUnits|clipPath|clipRule|colorInterpolation|colorInterpolationFilters|colorProfile|colorRendering|contentScriptType|contentStyleType|cursor|cx|cy|d|decelerate|descent|diffuseConstant|direction|display|divisor|dominantBaseline|dur|dx|dy|edgeMode|elevation|enableBackground|end|exponent|externalResourcesRequired|fill|fillOpacity|fillRule|filter|filterRes|filterUnits|floodColor|floodOpacity|focusable|fontFamily|fontSize|fontSizeAdjust|fontStretch|fontStyle|fontVariant|fontWeight|format|from|fr|fx|fy|g1|g2|glyphName|glyphOrientationHorizontal|glyphOrientationVertical|glyphRef|gradientTransform|gradientUnits|hanging|horizAdvX|horizOriginX|ideographic|imageRendering|in|in2|intercept|k|k1|k2|k3|k4|kernelMatrix|kernelUnitLength|kerning|keyPoints|keySplines|keyTimes|lengthAdjust|letterSpacing|lightingColor|limitingConeAngle|local|markerEnd|markerMid|markerStart|markerHeight|markerUnits|markerWidth|mask|maskContentUnits|maskUnits|mathematical|mode|numOctaves|offset|opacity|operator|order|orient|orientation|origin|overflow|overlinePosition|overlineThickness|panose1|paintOrder|pathLength|patternContentUnits|patternTransform|patternUnits|pointerEvents|points|pointsAtX|pointsAtY|pointsAtZ|preserveAlpha|preserveAspectRatio|primitiveUnits|r|radius|refX|refY|renderingIntent|repeatCount|repeatDur|requiredExtensions|requiredFeatures|restart|result|rotate|rx|ry|scale|seed|shapeRendering|slope|spacing|specularConstant|specularExponent|speed|spreadMethod|startOffset|stdDeviation|stemh|stemv|stitchTiles|stopColor|stopOpacity|strikethroughPosition|strikethroughThickness|string|stroke|strokeDasharray|strokeDashoffset|strokeLinecap|strokeLinejoin|strokeMiterlimit|strokeOpacity|strokeWidth|surfaceScale|systemLanguage|tableValues|targetX|targetY|textAnchor|textDecoration|textRendering|textLength|to|transform|u1|u2|underlinePosition|underlineThickness|unicode|unicodeBidi|unicodeRange|unitsPerEm|vAlphabetic|vHanging|vIdeographic|vMathematical|values|vectorEffect|version|vertAdvY|vertOriginX|vertOriginY|viewBox|viewTarget|visibility|widths|wordSpacing|writingMode|x|xHeight|x1|x2|xChannelSelector|xlinkActuate|xlinkArcrole|xlinkHref|xlinkRole|xlinkShow|xlinkTitle|xlinkType|xmlBase|xmlns|xmlnsXlink|xmlLang|xmlSpace|y|y1|y2|yChannelSelector|z|zoomAndPan|for|class|autofocus)|(([Dd][Aa][Tt][Aa]|[Aa][Rr][Ii][Aa]|x)-.*))$/; // https://esbench.com/bench/5bfee68a4cd7e6009ef61d23\n\nvar index = memoize(function (prop) {\n return reactPropsRegex.test(prop) || prop.charCodeAt(0) === 111\n /* o */\n && prop.charCodeAt(1) === 110\n /* n */\n && prop.charCodeAt(2) < 91;\n}\n/* Z+1 */\n);\nexport default index;","module.exports = \"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPCEtLSBHZW5lcmF0b3I6IEFkb2JlIElsbHVzdHJhdG9yIDIzLjAuMywgU1ZHIEV4cG9ydCBQbHVnLUluIC4gU1ZHIFZlcnNpb246IDYuMDAgQnVpbGQgMCkgIC0tPgo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkxheWVyXzEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiIHg9IjBweCIgeT0iMHB4IgoJIHZpZXdCb3g9IjAgMCAzNSAyNyIgc3R5bGU9ImVuYWJsZS1iYWNrZ3JvdW5kOm5ldyAwIDAgMzUgMjc7IiB4bWw6c3BhY2U9InByZXNlcnZlIj4KPHN0eWxlIHR5cGU9InRleHQvY3NzIj4KCS5zdDB7ZmlsbC1ydWxlOmV2ZW5vZGQ7Y2xpcC1ydWxlOmV2ZW5vZGQ7ZmlsbDojRkZGRkZGO30KPC9zdHlsZT4KPHBhdGggY2xhc3M9InN0MCIgZD0iTTE3LDcuMmwwLjEsMS4ybC0xLjMtMC4xYy00LjYtMC41LTguNi0yLjQtMTItNS41TDIuMSwxLjFMMS43LDIuM0MwLjgsNC44LDEuMyw3LjUsMy4yLDkuM2MxLDEsMC44LDEuMS0xLDAuNQoJQzEuNyw5LjcsMS4xLDkuNSwxLjEsOS42QzAuOSw5LjgsMS41LDExLjksMiwxMi44YzAuNywxLjIsMiwyLjQsMy41LDMuMWwxLjIsMC41bC0xLjUsMGMtMS40LDAtMS41LDAtMS4zLDAuNQoJYzAuNSwxLjUsMi41LDMuMiw0LjcsMy45bDEuNiwwLjVsLTEuNCwwLjhjLTIsMS4xLTQuNCwxLjctNi44LDEuOEMwLjksMjMuOSwwLDI0LDAsMjQuMWMwLDAuMiwzLjEsMS42LDQuOSwyLjEKCWM1LjQsMS41LDExLjgsMC45LDE2LjYtMS44YzMuNC0xLjksNi44LTUuNiw4LjQtOS4yYzAuOS0xLjksMS43LTUuNSwxLjctNy4xYzAtMS4xLDAuMS0xLjIsMS41LTIuNmMwLjgtMC44LDEuNi0xLjYsMS44LTEuOAoJYzAuMy0wLjUsMC4yLTAuNS0xLjEsMGMtMi4xLDAuNy0yLjUsMC42LTEuNC0wLjVjMC44LTAuOCwxLjctMi4xLDEuNy0yLjVjMC0wLjEtMC40LDAtMC44LDAuM2MtMC41LDAuMi0xLjUsMC42LTIuMiwwLjhsLTEuNCwwLjQKCWwtMS4yLTAuOGMtMC43LTAuNC0xLjYtMC45LTIuMS0xYy0xLjMtMC4zLTMuMy0wLjMtNC40LDAuMUMxOC44LDEuNCwxNi44LDQuMiwxNyw3LjJ6Ii8+Cjwvc3ZnPgo=\"","\"use strict\";\n\nvar _interopRequireDefault = require(\"@babel/runtime/helpers/interopRequireDefault\");\n\nvar _gatsby = require(\"gatsby\");\n\nvar _catchLinks = _interopRequireDefault(require(\"./catch-links\"));\n\nexports.onClientEntry = function (_, pluginOptions) {\n if (pluginOptions === void 0) {\n pluginOptions = {};\n }\n\n (0, _catchLinks.default)(window, pluginOptions, function (href) {\n (0, _gatsby.navigate)(href);\n });\n};","import React, { createContext, useContext } from \"react\"\n\nconst GatsbyMDXScopeContext = createContext({})\n\nexport const useMDXScope = scope => {\n const contextScope = useContext(GatsbyMDXScopeContext)\n return scope || contextScope\n}\n\nexport const MDXScopeProvider = ({ __mdxScope, children }) =>\n React.createElement(\n GatsbyMDXScopeContext.Provider,\n { value: __mdxScope },\n children\n )\n","function _nonIterableSpread() {\n throw new TypeError(\"Invalid attempt to spread non-iterable instance.\\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.\");\n}\n\nmodule.exports = _nonIterableSpread;\nmodule.exports[\"default\"] = module.exports, module.exports.__esModule = true;","import arrayLikeToArray from \"./arrayLikeToArray.js\";\nexport default function _unsupportedIterableToArray(o, minLen) {\n if (!o) return;\n if (typeof o === \"string\") return arrayLikeToArray(o, minLen);\n var n = Object.prototype.toString.call(o).slice(8, -1);\n if (n === \"Object\" && o.constructor) n = o.constructor.name;\n if (n === \"Map\" || n === \"Set\") return Array.from(o);\n if (n === \"Arguments\" || /^(?:Ui|I)nt(?:8|16|32)(?:Clamped)?Array$/.test(n)) return arrayLikeToArray(o, minLen);\n}","\"use strict\";\n\nvar _typeof = typeof Symbol === \"function\" && typeof Symbol.iterator === \"symbol\" ? function (obj) {\n return typeof obj;\n} : function (obj) {\n return obj && typeof Symbol === \"function\" && obj.constructor === Symbol && obj !== Symbol.prototype ? \"symbol\" : typeof obj;\n};\n\nfunction _classCallCheck(instance, Constructor) {\n if (!(instance instanceof Constructor)) {\n throw new TypeError(\"Cannot call a class as a function\");\n }\n}\n\nfunction _possibleConstructorReturn(self, call) {\n if (!self) {\n throw new ReferenceError(\"this hasn't been initialised - super() hasn't been called\");\n }\n\n return call && (typeof call === \"object\" || typeof call === \"function\") ? call : self;\n}\n\nfunction _inherits(subClass, superClass) {\n if (typeof superClass !== \"function\" && superClass !== null) {\n throw new TypeError(\"Super expression must either be null or a function, not \" + typeof superClass);\n }\n\n subClass.prototype = Object.create(superClass && superClass.prototype, {\n constructor: {\n value: subClass,\n enumerable: false,\n writable: true,\n configurable: true\n }\n });\n if (superClass) Object.setPrototypeOf ? Object.setPrototypeOf(subClass, superClass) : subClass.__proto__ = superClass;\n}\n\nvar React = require(\"react\");\n\nvar PropTypes = require(\"prop-types\");\n\nvar ALL_INITIALIZERS = [];\nvar READY_INITIALIZERS = [];\n\nfunction isWebpackReady(getModuleIds) {\n if ((typeof __webpack_modules__ === \"undefined\" ? \"undefined\" : _typeof(__webpack_modules__)) !== \"object\") {\n return false;\n }\n\n return getModuleIds().every(function (moduleId) {\n return typeof moduleId !== \"undefined\" && typeof __webpack_modules__[moduleId] !== \"undefined\";\n });\n}\n\nfunction load(loader) {\n var promise = loader();\n var state = {\n loading: true,\n loaded: null,\n error: null\n };\n state.promise = promise.then(function (loaded) {\n state.loading = false;\n state.loaded = loaded;\n return loaded;\n }).catch(function (err) {\n state.loading = false;\n state.error = err;\n throw err;\n });\n return state;\n}\n\nfunction loadMap(obj) {\n var state = {\n loading: false,\n loaded: {},\n error: null\n };\n var promises = [];\n\n try {\n Object.keys(obj).forEach(function (key) {\n var result = load(obj[key]);\n\n if (!result.loading) {\n state.loaded[key] = result.loaded;\n state.error = result.error;\n } else {\n state.loading = true;\n }\n\n promises.push(result.promise);\n result.promise.then(function (res) {\n state.loaded[key] = res;\n }).catch(function (err) {\n state.error = err;\n });\n });\n } catch (err) {\n state.error = err;\n }\n\n state.promise = Promise.all(promises).then(function (res) {\n state.loading = false;\n return res;\n }).catch(function (err) {\n state.loading = false;\n throw err;\n });\n return state;\n}\n\nfunction resolve(obj) {\n return obj && obj.__esModule ? obj.default : obj;\n}\n\nfunction render(loaded, props) {\n return React.createElement(resolve(loaded), props);\n}\n\nfunction createLoadableComponent(loadFn, options) {\n var _class, _temp;\n\n if (!options.loading) {\n throw new Error(\"react-loadable requires a `loading` component\");\n }\n\n var opts = Object.assign({\n loader: null,\n loading: null,\n delay: 200,\n timeout: null,\n render: render,\n webpack: null,\n modules: null\n }, options);\n var res = null;\n\n function init() {\n if (!res) {\n res = loadFn(opts.loader);\n }\n\n return res.promise;\n }\n\n ALL_INITIALIZERS.push(init);\n\n if (typeof opts.webpack === \"function\") {\n READY_INITIALIZERS.push(function () {\n if (isWebpackReady(opts.webpack)) {\n return init();\n }\n });\n }\n\n return _temp = _class = function (_React$Component) {\n _inherits(LoadableComponent, _React$Component);\n\n function LoadableComponent(props) {\n _classCallCheck(this, LoadableComponent);\n\n var _this = _possibleConstructorReturn(this, _React$Component.call(this, props));\n\n _this.retry = function () {\n _this.setState({\n error: null,\n loading: true,\n timedOut: false\n });\n\n res = loadFn(opts.loader);\n\n _this._loadModule();\n };\n\n init();\n _this.state = {\n error: res.error,\n pastDelay: false,\n timedOut: false,\n loading: res.loading,\n loaded: res.loaded\n };\n return _this;\n }\n\n LoadableComponent.preload = function preload() {\n return init();\n };\n\n LoadableComponent.prototype.componentWillMount = function componentWillMount() {\n this._mounted = true;\n\n this._loadModule();\n };\n\n LoadableComponent.prototype._loadModule = function _loadModule() {\n var _this2 = this;\n\n if (this.context.loadable && Array.isArray(opts.modules)) {\n opts.modules.forEach(function (moduleName) {\n _this2.context.loadable.report(moduleName);\n });\n }\n\n if (!res.loading) {\n return;\n }\n\n if (typeof opts.delay === \"number\") {\n if (opts.delay === 0) {\n this.setState({\n pastDelay: true\n });\n } else {\n this._delay = setTimeout(function () {\n _this2.setState({\n pastDelay: true\n });\n }, opts.delay);\n }\n }\n\n if (typeof opts.timeout === \"number\") {\n this._timeout = setTimeout(function () {\n _this2.setState({\n timedOut: true\n });\n }, opts.timeout);\n }\n\n var update = function update() {\n if (!_this2._mounted) {\n return;\n }\n\n _this2.setState({\n error: res.error,\n loaded: res.loaded,\n loading: res.loading\n });\n\n _this2._clearTimeouts();\n };\n\n res.promise.then(function () {\n update();\n }).catch(function (err) {\n update();\n });\n };\n\n LoadableComponent.prototype.componentWillUnmount = function componentWillUnmount() {\n this._mounted = false;\n\n this._clearTimeouts();\n };\n\n LoadableComponent.prototype._clearTimeouts = function _clearTimeouts() {\n clearTimeout(this._delay);\n clearTimeout(this._timeout);\n };\n\n LoadableComponent.prototype.render = function render() {\n if (this.state.loading || this.state.error) {\n return React.createElement(opts.loading, {\n isLoading: this.state.loading,\n pastDelay: this.state.pastDelay,\n timedOut: this.state.timedOut,\n error: this.state.error,\n retry: this.retry\n });\n } else if (this.state.loaded) {\n return opts.render(this.state.loaded, this.props);\n } else {\n return null;\n }\n };\n\n return LoadableComponent;\n }(React.Component), _class.contextTypes = {\n loadable: PropTypes.shape({\n report: PropTypes.func.isRequired\n })\n }, _temp;\n}\n\nfunction Loadable(opts) {\n return createLoadableComponent(load, opts);\n}\n\nfunction LoadableMap(opts) {\n if (typeof opts.render !== \"function\") {\n throw new Error(\"LoadableMap requires a `render(loaded, props)` function\");\n }\n\n return createLoadableComponent(loadMap, opts);\n}\n\nLoadable.Map = LoadableMap;\n\nvar Capture = function (_React$Component2) {\n _inherits(Capture, _React$Component2);\n\n function Capture() {\n _classCallCheck(this, Capture);\n\n return _possibleConstructorReturn(this, _React$Component2.apply(this, arguments));\n }\n\n Capture.prototype.getChildContext = function getChildContext() {\n return {\n loadable: {\n report: this.props.report\n }\n };\n };\n\n Capture.prototype.render = function render() {\n return React.Children.only(this.props.children);\n };\n\n return Capture;\n}(React.Component);\n\nCapture.propTypes = {\n report: PropTypes.func.isRequired\n};\nCapture.childContextTypes = {\n loadable: PropTypes.shape({\n report: PropTypes.func.isRequired\n }).isRequired\n};\nLoadable.Capture = Capture;\n\nfunction flushInitializers(initializers) {\n var promises = [];\n\n while (initializers.length) {\n var init = initializers.pop();\n promises.push(init());\n }\n\n return Promise.all(promises).then(function () {\n if (initializers.length) {\n return flushInitializers(initializers);\n }\n });\n}\n\nLoadable.preloadAll = function () {\n return new Promise(function (resolve, reject) {\n flushInitializers(ALL_INITIALIZERS).then(resolve, reject);\n });\n};\n\nLoadable.preloadReady = function () {\n return new Promise(function (resolve, reject) {\n // We always will resolve, errors should be handled within loading UIs.\n flushInitializers(READY_INITIALIZERS).then(resolve, resolve);\n });\n};\n\nmodule.exports = Loadable;","function _iterableToArray(iter) {\n if (typeof Symbol !== \"undefined\" && Symbol.iterator in Object(iter)) return Array.from(iter);\n}\n\nmodule.exports = _iterableToArray;\nmodule.exports[\"default\"] = module.exports, module.exports.__esModule = true;","\"use strict\";\n\nvar _interopRequireWildcard = require(\"@babel/runtime/helpers/interopRequireWildcard\");\n\nvar _interopRequireDefault = require(\"@babel/runtime/helpers/interopRequireDefault\");\n\nexports.__esModule = true;\nexports.ScrollHandler = exports.ScrollContext = void 0;\n\nvar _assertThisInitialized2 = _interopRequireDefault(require(\"@babel/runtime/helpers/assertThisInitialized\"));\n\nvar _inheritsLoose2 = _interopRequireDefault(require(\"@babel/runtime/helpers/inheritsLoose\"));\n\nvar React = _interopRequireWildcard(require(\"react\"));\n\nvar _propTypes = _interopRequireDefault(require(\"prop-types\"));\n\nvar _sessionStorage = require(\"./session-storage\");\n\nvar ScrollContext = /*#__PURE__*/React.createContext(new _sessionStorage.SessionStorage());\nexports.ScrollContext = ScrollContext;\nScrollContext.displayName = \"GatsbyScrollContext\";\n\nvar ScrollHandler = /*#__PURE__*/function (_React$Component) {\n (0, _inheritsLoose2.default)(ScrollHandler, _React$Component);\n\n function ScrollHandler() {\n var _this;\n\n for (var _len = arguments.length, args = new Array(_len), _key = 0; _key < _len; _key++) {\n args[_key] = arguments[_key];\n }\n\n _this = _React$Component.call.apply(_React$Component, [this].concat(args)) || this;\n _this._stateStorage = new _sessionStorage.SessionStorage();\n\n _this.scrollListener = function () {\n var key = _this.props.location.key;\n\n if (key) {\n _this._stateStorage.save(_this.props.location, key, window.scrollY);\n }\n };\n\n _this.windowScroll = function (position, prevProps) {\n if (_this.shouldUpdateScroll(prevProps, _this.props)) {\n window.scrollTo(0, position);\n }\n };\n\n _this.scrollToHash = function (hash, prevProps) {\n var node = document.getElementById(hash.substring(1));\n\n if (node && _this.shouldUpdateScroll(prevProps, _this.props)) {\n node.scrollIntoView();\n }\n };\n\n _this.shouldUpdateScroll = function (prevRouterProps, routerProps) {\n var shouldUpdateScroll = _this.props.shouldUpdateScroll;\n\n if (!shouldUpdateScroll) {\n return true;\n } // Hack to allow accessing this._stateStorage.\n\n\n return shouldUpdateScroll.call((0, _assertThisInitialized2.default)(_this), prevRouterProps, routerProps);\n };\n\n return _this;\n }\n\n var _proto = ScrollHandler.prototype;\n\n _proto.componentDidMount = function componentDidMount() {\n window.addEventListener(\"scroll\", this.scrollListener);\n var scrollPosition;\n var _this$props$location = this.props.location,\n key = _this$props$location.key,\n hash = _this$props$location.hash;\n\n if (key) {\n scrollPosition = this._stateStorage.read(this.props.location, key);\n }\n\n if (scrollPosition) {\n this.windowScroll(scrollPosition, undefined);\n } else if (hash) {\n this.scrollToHash(decodeURI(hash), undefined);\n }\n };\n\n _proto.componentWillUnmount = function componentWillUnmount() {\n window.removeEventListener(\"scroll\", this.scrollListener);\n };\n\n _proto.componentDidUpdate = function componentDidUpdate(prevProps) {\n var _this$props$location2 = this.props.location,\n hash = _this$props$location2.hash,\n key = _this$props$location2.key;\n var scrollPosition;\n\n if (key) {\n scrollPosition = this._stateStorage.read(this.props.location, key);\n }\n /** There are two pieces of state: the browser url and\n * history state which keeps track of scroll position\n * Native behaviour prescribes that we ought to restore scroll position\n * when a user navigates back in their browser (this is the `POP` action)\n * Currently, reach router has a bug that prevents this at https://github.com/reach/router/issues/228\n * So we _always_ stick to the url as a source of truth — if the url\n * contains a hash, we scroll to it\n */\n\n\n if (hash) {\n this.scrollToHash(decodeURI(hash), prevProps);\n } else {\n this.windowScroll(scrollPosition, prevProps);\n }\n };\n\n _proto.render = function render() {\n return /*#__PURE__*/React.createElement(ScrollContext.Provider, {\n value: this._stateStorage\n }, this.props.children);\n };\n\n return ScrollHandler;\n}(React.Component);\n\nexports.ScrollHandler = ScrollHandler;\nScrollHandler.propTypes = {\n shouldUpdateScroll: _propTypes.default.func,\n children: _propTypes.default.element.isRequired,\n location: _propTypes.default.object.isRequired\n};","export const onServiceWorkerUpdateReady = () => {\n const answer = window.confirm(\n `This tutorial has been updated. ` +\n `Reload to display the latest version?`\n )\n if (answer === true) {\n window.location.reload()\n }\n}","//\nmodule.exports = function shallowEqual(objA, objB, compare, compareContext) {\n var ret = compare ? compare.call(compareContext, objA, objB) : void 0;\n\n if (ret !== void 0) {\n return !!ret;\n }\n\n if (objA === objB) {\n return true;\n }\n\n if (typeof objA !== \"object\" || !objA || typeof objB !== \"object\" || !objB) {\n return false;\n }\n\n var keysA = Object.keys(objA);\n var keysB = Object.keys(objB);\n\n if (keysA.length !== keysB.length) {\n return false;\n }\n\n var bHasOwnProperty = Object.prototype.hasOwnProperty.bind(objB); // Test for A's keys different from B.\n\n for (var idx = 0; idx < keysA.length; idx++) {\n var key = keysA[idx];\n\n if (!bHasOwnProperty(key)) {\n return false;\n }\n\n var valueA = objA[key];\n var valueB = objB[key];\n ret = compare ? compare.call(compareContext, valueA, valueB, key) : void 0;\n\n if (ret === false || ret === void 0 && valueA !== valueB) {\n return false;\n }\n }\n\n return true;\n};","import React, { createElement } from \"react\"\nimport PropTypes from \"prop-types\"\nimport { publicLoader } from \"./loader\"\nimport { apiRunner } from \"./api-runner-browser\"\nimport { grabMatchParams } from \"./find-path\"\n\n// Renders page\nclass PageRenderer extends React.Component {\n render() {\n const props = {\n ...this.props,\n params: {\n ...grabMatchParams(this.props.location.pathname),\n ...this.props.pageResources.json.pageContext.__params,\n },\n pathContext: this.props.pageContext,\n }\n\n const [replacementElement] = apiRunner(`replaceComponentRenderer`, {\n props: this.props,\n loader: publicLoader,\n })\n\n const pageElement =\n replacementElement ||\n createElement(this.props.pageResources.component, {\n ...props,\n key: this.props.path || this.props.pageResources.page.path,\n })\n\n const wrappedPage = apiRunner(\n `wrapPageElement`,\n { element: pageElement, props },\n pageElement,\n ({ result }) => {\n return { element: result, props }\n }\n ).pop()\n\n return wrappedPage\n }\n}\n\nPageRenderer.propTypes = {\n location: PropTypes.object.isRequired,\n pageResources: PropTypes.object.isRequired,\n data: PropTypes.object,\n pageContext: PropTypes.object.isRequired,\n}\n\nexport default PageRenderer\n","var arrayLikeToArray = require(\"./arrayLikeToArray.js\");\n\nfunction _arrayWithoutHoles(arr) {\n if (Array.isArray(arr)) return arrayLikeToArray(arr);\n}\n\nmodule.exports = _arrayWithoutHoles;\nmodule.exports[\"default\"] = module.exports, module.exports.__esModule = true;","import * as React from 'react';\nexport default {\n React\n};","import arrayWithoutHoles from \"./arrayWithoutHoles.js\";\nimport iterableToArray from \"./iterableToArray.js\";\nimport unsupportedIterableToArray from \"./unsupportedIterableToArray.js\";\nimport nonIterableSpread from \"./nonIterableSpread.js\";\nexport default function _toConsumableArray(arr) {\n return arrayWithoutHoles(arr) || iterableToArray(arr) || unsupportedIterableToArray(arr) || nonIterableSpread();\n}","import arrayLikeToArray from \"./arrayLikeToArray.js\";\nexport default function _arrayWithoutHoles(arr) {\n if (Array.isArray(arr)) return arrayLikeToArray(arr);\n}","export default function _iterableToArray(iter) {\n if (typeof Symbol !== \"undefined\" && Symbol.iterator in Object(iter)) return Array.from(iter);\n}","export default function _nonIterableSpread() {\n throw new TypeError(\"Invalid attempt to spread non-iterable instance.\\nIn order to be iterable, non-array objects must have a [Symbol.iterator]() method.\");\n}","import invariant from \"invariant\";\n\n////////////////////////////////////////////////////////////////////////////////\n// startsWith(string, search) - Check if `string` starts with `search`\nvar startsWith = function startsWith(string, search) {\n return string.substr(0, search.length) === search;\n};\n\n////////////////////////////////////////////////////////////////////////////////\n// pick(routes, uri)\n//\n// Ranks and picks the best route to match. Each segment gets the highest\n// amount of points, then the type of segment gets an additional amount of\n// points where\n//\n// static > dynamic > splat > root\n//\n// This way we don't have to worry about the order of our routes, let the\n// computers do it.\n//\n// A route looks like this\n//\n// { path, default, value }\n//\n// And a returned match looks like:\n//\n// { route, params, uri }\n//\n// I know, I should use TypeScript not comments for these types.\nvar pick = function pick(routes, uri) {\n var match = void 0;\n var default_ = void 0;\n\n var _uri$split = uri.split(\"?\"),\n uriPathname = _uri$split[0];\n\n var uriSegments = segmentize(uriPathname);\n var isRootUri = uriSegments[0] === \"\";\n var ranked = rankRoutes(routes);\n\n for (var i = 0, l = ranked.length; i < l; i++) {\n var missed = false;\n var route = ranked[i].route;\n\n if (route.default) {\n default_ = {\n route: route,\n params: {},\n uri: uri\n };\n continue;\n }\n\n var routeSegments = segmentize(route.path);\n var params = {};\n var max = Math.max(uriSegments.length, routeSegments.length);\n var index = 0;\n\n for (; index < max; index++) {\n var routeSegment = routeSegments[index];\n var uriSegment = uriSegments[index];\n\n if (isSplat(routeSegment)) {\n // Hit a splat, just grab the rest, and return a match\n // uri: /files/documents/work\n // route: /files/*\n var param = routeSegment.slice(1) || \"*\";\n params[param] = uriSegments.slice(index).map(decodeURIComponent).join(\"/\");\n break;\n }\n\n if (uriSegment === undefined) {\n // URI is shorter than the route, no match\n // uri: /users\n // route: /users/:userId\n missed = true;\n break;\n }\n\n var dynamicMatch = paramRe.exec(routeSegment);\n\n if (dynamicMatch && !isRootUri) {\n var matchIsNotReserved = reservedNames.indexOf(dynamicMatch[1]) === -1;\n !matchIsNotReserved ? process.env.NODE_ENV !== \"production\" ? invariant(false, \" dynamic segment \\\"\" + dynamicMatch[1] + \"\\\" is a reserved name. Please use a different name in path \\\"\" + route.path + \"\\\".\") : invariant(false) : void 0;\n var value = decodeURIComponent(uriSegment);\n params[dynamicMatch[1]] = value;\n } else if (routeSegment !== uriSegment) {\n // Current segments don't match, not dynamic, not splat, so no match\n // uri: /users/123/settings\n // route: /users/:id/profile\n missed = true;\n break;\n }\n }\n\n if (!missed) {\n match = {\n route: route,\n params: params,\n uri: \"/\" + uriSegments.slice(0, index).join(\"/\")\n };\n break;\n }\n }\n\n return match || default_ || null;\n};\n\n////////////////////////////////////////////////////////////////////////////////\n// match(path, uri) - Matches just one path to a uri, also lol\nvar match = function match(path, uri) {\n return pick([{ path: path }], uri);\n};\n\n////////////////////////////////////////////////////////////////////////////////\n// resolve(to, basepath)\n//\n// Resolves URIs as though every path is a directory, no files. Relative URIs\n// in the browser can feel awkward because not only can you be \"in a directory\"\n// you can be \"at a file\", too. For example\n//\n// browserSpecResolve('foo', '/bar/') => /bar/foo\n// browserSpecResolve('foo', '/bar') => /foo\n//\n// But on the command line of a file system, it's not as complicated, you can't\n// `cd` from a file, only directories. This way, links have to know less about\n// their current path. To go deeper you can do this:\n//\n// \n// // instead of\n// \n//\n// Just like `cd`, if you want to go deeper from the command line, you do this:\n//\n// cd deeper\n// # not\n// cd $(pwd)/deeper\n//\n// By treating every path as a directory, linking to relative paths should\n// require less contextual information and (fingers crossed) be more intuitive.\nvar resolve = function resolve(to, base) {\n // /foo/bar, /baz/qux => /foo/bar\n if (startsWith(to, \"/\")) {\n return to;\n }\n\n var _to$split = to.split(\"?\"),\n toPathname = _to$split[0],\n toQuery = _to$split[1];\n\n var _base$split = base.split(\"?\"),\n basePathname = _base$split[0];\n\n var toSegments = segmentize(toPathname);\n var baseSegments = segmentize(basePathname);\n\n // ?a=b, /users?b=c => /users?a=b\n if (toSegments[0] === \"\") {\n return addQuery(basePathname, toQuery);\n }\n\n // profile, /users/789 => /users/789/profile\n if (!startsWith(toSegments[0], \".\")) {\n var pathname = baseSegments.concat(toSegments).join(\"/\");\n return addQuery((basePathname === \"/\" ? \"\" : \"/\") + pathname, toQuery);\n }\n\n // ./ /users/123 => /users/123\n // ../ /users/123 => /users\n // ../.. /users/123 => /\n // ../../one /a/b/c/d => /a/b/one\n // .././one /a/b/c/d => /a/b/c/one\n var allSegments = baseSegments.concat(toSegments);\n var segments = [];\n for (var i = 0, l = allSegments.length; i < l; i++) {\n var segment = allSegments[i];\n if (segment === \"..\") segments.pop();else if (segment !== \".\") segments.push(segment);\n }\n\n return addQuery(\"/\" + segments.join(\"/\"), toQuery);\n};\n\n////////////////////////////////////////////////////////////////////////////////\n// insertParams(path, params)\n\nvar insertParams = function insertParams(path, params) {\n var _path$split = path.split(\"?\"),\n pathBase = _path$split[0],\n _path$split$ = _path$split[1],\n query = _path$split$ === undefined ? \"\" : _path$split$;\n\n var segments = segmentize(pathBase);\n var constructedPath = \"/\" + segments.map(function (segment) {\n var match = paramRe.exec(segment);\n return match ? params[match[1]] : segment;\n }).join(\"/\");\n var _params$location = params.location;\n _params$location = _params$location === undefined ? {} : _params$location;\n var _params$location$sear = _params$location.search,\n search = _params$location$sear === undefined ? \"\" : _params$location$sear;\n\n var searchSplit = search.split(\"?\")[1] || \"\";\n constructedPath = addQuery(constructedPath, query, searchSplit);\n return constructedPath;\n};\n\nvar validateRedirect = function validateRedirect(from, to) {\n var filter = function filter(segment) {\n return isDynamic(segment);\n };\n var fromString = segmentize(from).filter(filter).sort().join(\"/\");\n var toString = segmentize(to).filter(filter).sort().join(\"/\");\n return fromString === toString;\n};\n\n////////////////////////////////////////////////////////////////////////////////\n// Junk\nvar paramRe = /^:(.+)/;\n\nvar SEGMENT_POINTS = 4;\nvar STATIC_POINTS = 3;\nvar DYNAMIC_POINTS = 2;\nvar SPLAT_PENALTY = 1;\nvar ROOT_POINTS = 1;\n\nvar isRootSegment = function isRootSegment(segment) {\n return segment === \"\";\n};\nvar isDynamic = function isDynamic(segment) {\n return paramRe.test(segment);\n};\nvar isSplat = function isSplat(segment) {\n return segment && segment[0] === \"*\";\n};\n\nvar rankRoute = function rankRoute(route, index) {\n var score = route.default ? 0 : segmentize(route.path).reduce(function (score, segment) {\n score += SEGMENT_POINTS;\n if (isRootSegment(segment)) score += ROOT_POINTS;else if (isDynamic(segment)) score += DYNAMIC_POINTS;else if (isSplat(segment)) score -= SEGMENT_POINTS + SPLAT_PENALTY;else score += STATIC_POINTS;\n return score;\n }, 0);\n return { route: route, score: score, index: index };\n};\n\nvar rankRoutes = function rankRoutes(routes) {\n return routes.map(rankRoute).sort(function (a, b) {\n return a.score < b.score ? 1 : a.score > b.score ? -1 : a.index - b.index;\n });\n};\n\nvar segmentize = function segmentize(uri) {\n return uri\n // strip starting/ending slashes\n .replace(/(^\\/+|\\/+$)/g, \"\").split(\"/\");\n};\n\nvar addQuery = function addQuery(pathname) {\n for (var _len = arguments.length, query = Array(_len > 1 ? _len - 1 : 0), _key = 1; _key < _len; _key++) {\n query[_key - 1] = arguments[_key];\n }\n\n query = query.filter(function (q) {\n return q && q.length > 0;\n });\n return pathname + (query && query.length > 0 ? \"?\" + query.join(\"&\") : \"\");\n};\n\nvar reservedNames = [\"uri\", \"path\"];\n\n/**\n * Shallow compares two objects.\n * @param {Object} obj1 The first object to compare.\n * @param {Object} obj2 The second object to compare.\n */\nvar shallowCompare = function shallowCompare(obj1, obj2) {\n var obj1Keys = Object.keys(obj1);\n return obj1Keys.length === Object.keys(obj2).length && obj1Keys.every(function (key) {\n return obj2.hasOwnProperty(key) && obj1[key] === obj2[key];\n });\n};\n\n////////////////////////////////////////////////////////////////////////////////\nexport { startsWith, pick, match, resolve, insertParams, validateRedirect, shallowCompare };","module.exports = [{\n plugin: require('../node_modules/gatsby-plugin-layout/gatsby-browser.js'),\n options: {\"plugins\":[],\"component\":\"/home/t42/Documents/programming/Projects/OT_Guide/IL-2 Guide/src/templates/docs.js\"},\n },{\n plugin: require('../node_modules/gatsby-plugin-catch-links/gatsby-browser.js'),\n options: {\"plugins\":[]},\n },{\n plugin: require('../node_modules/gatsby-plugin-mdx/gatsby-browser.js'),\n options: {\"plugins\":[],\"gatsbyRemarkPlugins\":[{\"resolve\":\"gatsby-remark-images\",\"options\":{\"maxWidth\":1035,\"sizeByPixelDensity\":true}},{\"resolve\":\"gatsby-remark-katex\",\"options\":{\"strict\":\"ignore\"}},{\"resolve\":\"gatsby-remark-copy-linked-files\"},{\"resolve\":\"gatsby-remark-acronyms\",\"options\":{\"acronyms\":{\"2Ltr\":\"2-Letter\",\"Blk\":\"Block\",\"Det\":\"Detachment\",\"Stan/Eval\":\"Standardization and Evaluation\",\"3DELRR\":\"Three Dimensional Expeditionary Long Range Radar\",\"3PS\":\"Third Party Source\",\"AAS\":\"Advisory and Assistance Services\",\"A3M\":\"Air Force and Army Anti-Jam Modem\",\"AA\":\"Adversarial Assessment\",\"AAIP\":\"Aircraft Availability Improvement Program\",\"AAR\":\"After-Action Review / Report\",\"AARGM\":\"Advanced Anti-Radiation Guided Missile\",\"AARI\":\"Air-to-air Range Infrastructure\",\"ABSD\":\"Airborne Strategic Deterrence\",\"AC\":\"Alternating Current\",\"ACAT\":\"Acquisition Category\",\"ACC\":\"Air Combat Command\",\"ACCM\":\"Alternative Compensatory Control Measure\",\"ACE\":\"Acquisition Center of Excellence\",\"ACES\":\"Automated Civil Engineer System\",\"ACPAT\":\"Air Force C4I Program Assessment Tool\",\"ACPINS\":\"Automated Computer Program Identification Number System\",\"ACPO\":\"Acquisition Chief Process Office\",\"ACTD\":\"Advanced Concept Technology Demonstration\",\"ACWP\":\"Actual Cost Work Performed\",\"ADM\":\"Acquisition Decision Memorandum\",\"ADS\":\"Advanced Distributed Simulation\",\"AEC\":\"United States Army Evaluation Center\",\"AECO\":\"Advance Engineering Change Order\",\"AECS\":\"Advanced Entry Control System OR AFOTEC Electronic Coordination System\",\"AEF\":\"Air and Space Expeditionary Force\",\"AEHF\":\"Advanced Extremely High Frequency\",\"AEP\":\"Accrued Expenditures Paid\",\"AESO\":\"Advance Engineering Supplemental Order\",\"AETC\":\"Air Education and Training Command\",\"AETF\":\"Army Evaluation Task Force\",\"AEU\":\"Accrued Expenditures Unpaid\",\"AF GCIC\":\"Air Force Global Cyberspace Integration Center\",\"AFMOASP\":\"Air Force Management and Oversight of Acquisition Services Process\",\"AF\":\"(US) Air Force\",\"AF/A10\":\"Assistant Chief of Staff for Strategic Deterrence and Nuclear Integration\",\"AF/A2\":\"Deputy Chief of Staff, Intelligence, Surveillance and Reconnaissance\",\"AF/A3/5\":\"Deputy Chief of Staff, Operations, Plans, and Requirements\",\"AF/A4/7\":\"Deputy Chief of Staff, Logistics, Installations, and Mission Support\",\"AF/A5/8\":\"HQ AF, Strategic Plans and Programs\",\"AF/A5R\":\"Air Force Requirements Office\",\"AF/A6\":\"Chief of Warfighting Integration and Chief Information Officer (CIO)\",\"AF/A8\":\"Headquarters, Air Force Strategic Plans and Programs\",\"AF/CC\":\"Chief of Staff, United States Air Force\",\"AF/CV\":\"Vice Chief of Staff, United States Air Force\",\"AF/SE\":\"Air Force Chief of Safety\",\"AF/TE\":\"Headquarters Air Force Test and Evaluation Directorate\",\"AFAE\":\"Air Force Acquisition Executive\",\"AFAMS\":\"Air Force Agency for Modeling and Simulation\",\"AFB\":\"Air Force Base\",\"AFC2IC\":\"Air Force Command & Control Integration Center\",\"AFC2ISRC\":\"Air Force Command and Control and Intelligence, Surveillance, and Reconnaissance Center (disestablished)\",\"AFCA\":\"Air Force Communications Agency\",\"AFCAA\":\"Air Force Cost Analysis Agency\",\"AFCAP\":\"Air Force Certification and Accreditation Program\",\"AFCD\":\"Air Force Capabilities Document\",\"AFCEC\":\"Air Force Civil Engineer Center\",\"AFCESA\":\"Air Force Civil Engineer Support Agency\",\"AFDD\":\"Air Force Doctrine Document\",\"AFDPO\":\"Air Force Departmental Publishing Office\",\"AF-EA\":\"Air Force Enterprise Architecture\",\"AFEE\":\"Air Force Element of Expense\",\"AFEWES\":\"Air Force Electronic Warfare Simulator\",\"AFFARS\":\"Air Force Federal Acquisition Regulation Supplement\",\"AFFMA\":\"Air Force Frequency Management Agency\",\"AFGK\":\"Air Force Gatekeeper\",\"AFGLSC\":\"Air Force Global Logistics Support Center\",\"AFGSC\":\"Air Force Global Strike Command\",\"AFI\":\"Air Force Instruction\",\"AFICE\":\"Air Force Integrated Collaborative Environment\",\"AFIOC\":\"Air Force Information Operations Center\",\"AFIPPS\":\"Air Force Integrated Personnel and Pay System\",\"AFIT\":\"Air Force Institute of Technology\",\"AFIWC\":\"Air Force Information Warfare Center (disestablished)\",\"AFJO\":\"Air Force Joint Test Program Office\",\"AFKN\":\"Air Force Knowledge Now\",\"AFL2P\":\"Air Force Lessons Learned Program\",\"AFLCMC\":\"Air Force Life Cycle Management Center\",\"AFLIRP\":\"Air Force Lesson Issue Resolution Program\",\"AFMAN\":\"Air Force Manual\",\"AFMC\":\"Air Force Material Command\",\"AFMD\":\"Air Force Mission Directive\",\"AFMETCAL\":\"Air Force Metrology and Calibration\",\"AFMSRR\":\"Air Force Modeling and Simulation Resource Repository\",\"AFNET\":\"Air Force Network\",\"AFNIC\":\"Air Force Network Integration Center\",\"AF-NNSA\":\"Air Force-National Nuclear Security Administration\",\"AFNWC\":\"Air Force Nuclear Weapons Center\",\"AFOSH\":\"Air Force Occupational and Environmental Safety, Fire Protection, and Health OR Air Force Office of Safety and Health\",\"AFOSI\":\"Air Force Office of Special Investigations\",\"AFOTEC\":\"Air Force Operational Test and Evaluation Center\",\"AFOTEC/A-1\":\"Manpower and Personnel Directorate\",\"AFOTEC/A-1T\":\"Training Division\",\"AFOTEC/A-1W\":\"Manpower and Personnel (Operations) Division\",\"AFOTEC/A-2/9\":\"Intelligence, Analyses, and Assessments Directorate\",\"AFOTEC/A-2N\":\"Intelligence Division\",\"AFOTEC/A-3\":\"Operations Directorate\",\"AFOTEC/A-3C\":\"Cyber Strategic Evaluation Division\",\"AFOTEC/A-3E\":\"Operations Mission Support Division\",\"AFOTEC/A-3F\":\"Test Operations Division\",\"AFOTEC/A-3I\":\"Cyberspace Test Division\",\"AFOTEC/A-3O\":\"Test Design Operations Division\",\"AFOTEC/A-3Z\":\"Special Access Programs Division\",\"AFOTEC/A-4/7\":\"Installations and Mission Support Directorate\",\"AFOTEC/A-4F\":\"Logistics and Facilities Management Division\",\"AFOTEC/A-5/8\":\"Plans and Programs Directorate\",\"AFOTEC/A-5R\":\"Test Infrastructure Division\",\"AFOTEC/A-6\":\"Communications and Information Directorate\",\"AFOTEC/A-6O\":\"Cyber Operations Division\",\"AFOTEC/A-6X\":\"Plans and Resources Division\",\"AFOTEC/A-6Z\":\"Special Access Programs Information Technology Division\",\"AFOTEC/A-7K\":\"Contracting Division\",\"AFOTEC/A-7R\":\"Financial Resources Division\",\"AFOTEC/A-8P\":\"Programming Division\",\"AFOTEC/A-8R\":\"Long Range Investments Division\",\"AFOTEC/A-8X\":\"Strategic Plans and Policy Division\",\"AFOTEC/A-9A\":\"Analysis and Assessments Division\",\"AFOTEC/A-9I\":\"Analysis Foundation and Integration Division\",\"AFOTEC/A-9X\":\"Methods and Tools Division\",\"AFOTEC/CA\":\"Technical Advisor\",\"AFOTEC/CC\":\"AFOTEC Commander\",\"AFOTEC/CCE\":\"Executive Officer\",\"AFOTEC/CCJ\":\"Graphics\",\"AFOTEC/CCP\":\"Protocol\",\"AFOTEC/CCS\":\"Secretary\",\"AFOTEC/CCX\":\"Commander’s Action Group\",\"AFOTEC/CEM\":\"Chief Enlisted Manager\",\"AFOTEC/CS\":\"Command Staff\",\"AFOTEC/CV\":\"Vice Commander\",\"AFOTEC/DS\":\"Director of Staff\",\"AFOTEC/ED\":\"Executive Director\",\"AFOTEC/HO\":\"History Office\",\"AFOTEC/IGI\":\"Inspector General (Inspections)\",\"AFOTEC/IP\":\"Information Protection\",\"AFOTEC/LC\":\"Legal Council\",\"AFOTEC/PA\":\"Public Affairs\",\"AFOTEC/SE\":\"Safety\",\"AFOTECI\":\"AFOTEC Instruction\",\"AFOTECPAM\":\"AFOTEC Pamphlet\",\"AFOTTP\":\"Air Force Operational Tactics, Techniques, and Procedures\",\"AFPAM\":\"Air Force Pamphlet\",\"AFPD\":\"Air Force Policy Directive\",\"AFPEO/CM\":\"Air Force Program Executive Officer/Combat and Mission Support\",\"AFRB\":\"Air Force Review Board\",\"AFRC\":\"Air Force Reserve Command\",\"AFRIMS RDS\":\"Air Force Information Management System Records Disposition Schedule\",\"AFRIMS\":\"Air Force Records Information Management System\",\"AFRL\":\"Air Force Research Laboratory\",\"AFROC\":\"Air Force Requirements Oversight Council\",\"AFROCC\":\"Air Force Requirements for Operational Capabilities Council\",\"AFROCM\":\"Air Force Requirements Oversight Council Memorandum\",\"AFRRG\":\"Air Force Requirements Review Group\",\"AFSC\":\"Air Force Specialty Code\",\"AFSEO\":\"Air Force SEEK EAGLE Office\",\"AFSFC\":\"Air Force Security Forces Center\",\"AFSIT\":\"Air Force System Interoperability Testing\",\"AFSOC\":\"Air Force Special Operations Command\",\"AFSPC\":\"Air Force Space Command\",\"AFSSI\":\"Air Force Systems Security Instruction\",\"AFTC\":\"Air Force Test Center\",\"AGL\":\"Above Ground Level\",\"AGM\":\"Air Ground Missile\",\"AGR\":\"Active Guard and Reserve\",\"AIM\":\"Air Intercept Missile\",\"AIM-120 Adv EPIP\":\"AIM-120C Advanced Electronic Protection Improvement Program\",\"AIM 120D SIP-3\":\"AIM-120D System Improvement Program\",\"AIP\":\"Aircraft Information Program\",\"AIR\":\"Acquisition Information Repository\",\"AIS\":\"Automated Information Systems\",\"AISR\":\"Airborne Intelligence, Surveillance, and Reconnaissance\",\"AIT\":\"Automatic Identification Technology\",\"ALC\":\"Air Logistics Center\",\"ALCM\":\"Air Launched Cruise Missile\",\"ALCS-R\":\"Airborne Launch Control System Replacement\",\"ALDT\":\"Administrative and Logistics Delay\",\"ALIS\":\"Autonomic Logistics Information System (F-35)\",\"AMARG\":\"Aerospace Maintenance and Regeneration Group\",\"AMAS\":\"AFOTEC Mission Applications Suite\",\"AMC\":\"Air Mobility Command\",\"AME\":\"Alternate Mission Equipment\",\"AML\":\"Acquisition Master List\",\"AMP\":\"C-130 Avionics Modernization Program\",\"AMSAA\":\"Army Materiel Systems Analysis Activity\",\"AN/PRC\":\"Army Navy/Portable Radio Communication\",\"ANG\":\"Air National Guard\",\"AO\":\"Area of Operations or Authorizing Official or Action Officer\",\"Ao\":\"Operational Availability\",\"AoA\":\"Analysis of Alternatives\",\"AOC WS\":\"Air Operations Center Weapon System\",\"AOTR\":\"Assessment of Operational Test Readiness\",\"APA\":\"Additional Performance Attribute\",\"APAT\":\"Acquisition Process Architecture Team\",\"APB\":\"Acquisition Program Baseline\",\"APDP\":\"Acquisition Professional Development Program\",\"APKWS\":\"Advanced Precision Kill Weapon System\",\"APM\":\"Acquisition Process Model\",\"APML\":\"Acquisition Program Master List\",\"APPG\":\"Annual Planning and Programming Guidance\",\"APSR\":\"Accountable Property Systems of Record\",\"APT\":\"Advanced Pilot Training\",\"APUC\":\"Average Unit Procurement Cost\",\"AR\":\"Analysis and Reporting Toolset OR Army Regulation\",\"ARM\":\"Anti-Radiation Missile\",\"ARRW\":\"Air-Launched Rapid Response Weapon\",\"ART\":\"Adaptive-Relevant Test\",\"ARTS\":\"Advanced Radar Threat System\",\"AS Tool Kit\":\"Acquisition and Sustainment Tool Kit\",\"AS\":\"Acquisition Strategy\",\"ASACMS\":\"Advanced Situational Awareness Countermeasures System\",\"ASACoE\":\"Application Software Assurance Center of Excellence\",\"ASAF\":\"Assistant Secretary of the Air Force\",\"ASD\":\"Acquisition Strategy Development OR Agile Software Development OR Assist Sec of Defense\",\"ASDNII\":\"Assistant Secretary of Defense (Network and Information Integration\",\"ASIP\":\"Airborne Signals Intelligence Payload OR Aircraft Structural Integrity Program\",\"ASP\":\"Acquisition Strategy Panel\",\"ASR\":\"Acquisition and Sustainment Reviews OR Alternative Systems Review\",\"ASTK\":\"Acquisition Sustainment Tool Kit\",\"ASuW\":\"Anti-Surface Warfare\",\"AT\":\"Anti-Tamper\",\"AT&L\":\"Acquisition, Technology, and Logistics\",\"ATAPPS\":\"Automated Time Attendance and Production System\",\"ATCALS\":\"Air Traffic Control and Landing Systems\",\"ATD\":\"Advanced Technology Demonstration (or Development)\",\"ATE\":\"Automatic Test Equipment\",\"ATEC\":\"Army Test and Evaluation Command\",\"ATO\":\"Air Tasking Order OR Authority to Operate\",\"ATOS\":\"Automated Technical Orders System\",\"ATPA\":\"AFOTEC Test Program Application\",\"ATP-SE\":\"Advanced Targeting Pod-Sensor Enhancement\",\"ATS\":\"Automatic Test System\",\"ATTIC\":\"Analyst Training and Technical Information Center\",\"AUTL\":\"Army Universal Task List\",\"AV\":\"All Viewpoint\",\"AVIP\":\"Aviation Integrity Program\",\"AVPOL\":\"Aviation Petroleum, Oil, and Lubricants\",\"AWACS\":\"Airborne Warning and Control System\",\"AWBS\":\"Air Warfare Battle Shaping\",\"AWIP\":\"Advanced Weapons Integration Program\",\"B-2 DMS\":\"Defensive Management System\",\"B-2 EHF SATCOM\":\"Extremely High Frequency Satellite Communications\",\"B-52 CERP\":\"B-52 Commercial Engine Replacement Program\",\"B-52 RMP\":\"B-52 Radar Modernization Program\",\"B61 LEP\":\"B61 Life Extension Program\",\"BAA\":\"Buy American Act\",\"BBP\":\"Bullet Background Paper\",\"BC\":\"Business Case\",\"BCA\":\"Business Case Analysis\",\"BCL\":\"Business Capability Lifecycle\",\"BCS\":\"Baseline Comparison System\",\"BCS-F\":\"Battle Control System-Fixed\",\"BDA\":\"Big Data Analytics; Bomb Damage Assessment\",\"BDRSK\":\"Battle Damage Repair Spares Kit\",\"BEA\":\"Business Enterprise Architecture\",\"BES\":\"Budget Estimate Submission\",\"BFT\":\"Blue Force Tracking\",\"BISS\":\"Base and Installation Security System\",\"BLOS C2\":\"Beyond-Line-of-Sight Command and Control\",\"BLOS\":\"Beyond Line of Sight\",\"BLU\":\"Bomb, Live Unit\",\"BMC2\":\"Battle Management Command and Control Communications\",\"BMD\":\"Ballistic Missile Defense\",\"BMDS\":\"Ballistic Missile Defense System\",\"BOS\":\"Base Operating Support\",\"BPAC\":\"Budget Program Activity Code\",\"BRU\":\"Bomb Release Units\",\"BU\":\"Block Update\",\"C&A\":\"Certification and Accreditation\",\"C&L\":\"Capabilities and Limitations\",\"C&LR\":\"Capabilities and Limitations Report\",\"C2\":\"Command and Control\",\"C2AOS\":\"Command and Control Air Operations Suite\",\"C2BMC\":\"Command, Control, Battle Management, and Communications\",\"C2D2\":\"Continuous Capability Development and Delivery\",\"C2IS\":\"Command and Control Information Services\",\"C4\":\"Command, Control, Communications, and Computers\",\"C4I\":\"Command, Control, Communications, Computers, and Intelligence\",\"C4ISP\":\"Command, Control, Communication, Computers, and Intelligence Support Plan\",\"C4ISR\":\"Cmd, Control, Comm, Computers, Intel, Surveillance, and Reconnaissance\",\"CA\":\"Command Technical Advisor OR Contract Award OR Criticality Analysis\",\"CAC\":\"Common Access Card \",\"CAD\":\"Computer-Aided Design (or Drafting)\",\"CAE\":\"Component Acquisition Executive\",\"CAFTOP\":\"Comprehensive Air Force Technical Order Plan\",\"CAG\":\"Commander’s Action Group\",\"CAGE\":\"Commercial and Government Entity\",\"CAIG\":\"Cost Analysis Improvement Group\",\"CALS\":\"Common Analytical Laboratory System\",\"CAM\":\"Centralized Asset Management\",\"CAOC\":\"Coalition Air Operations Center\",\"CAP\":\"Contractor Acquired Property OR Critical Acquisition Position\",\"CAPCO\":\"Controlled Access Program Coordinating Office\",\"CAPE\":\"Cost Assessment and Program Evaluation\",\"CAPES\":\"F-16 Combat Avionics Programmed Extension Suite\",\"CARD\":\"Cost Analysis Requirements Description\",\"CASS\":\"Close Air Support System\",\"CAT\":\"Category\",\"CBA\":\"Capabilities-Based Assessment\",\"CBDP\":\"Chemical and Biological Defense Program\",\"CBM\":\"Condition-Based Maintenance Plus\",\"CBP\":\"Capability-Based Planning\",\"CBR\":\"Chemical, Biological, and Radiological\",\"CBRD\":\"Capabilities-Based Requirements Document\",\"CBRN\":\"Chemical, Biological, Radiological and Nuclear\",\"CC\":\"Commander OR Critical Component\",\"CCA\":\"Clinger-Cohen Act OR Component Cost Analysis\",\"CCaR\":\"Comprehensive Cost and Requirement System\",\"CCCA\":\"Common Core Compliance Area\",\"CCD\":\"Combat Capability Document\",\"CCDR\":\"Combatant Commander\",\"CCJO\":\"Capstone Concept for Joint Operations\",\"CCMD\":\"Combatant Command\",\"CCP\":\"Command Control Points\",\"CCPE\":\"Corrosion Control Program Executive\",\"CCR\":\"Call Completion Rate\",\"C-CS\":\"Counter-Concealment Sensing\",\"CCT\":\"Capability Collaboration Teams\",\"CCTD\":\"Concept Characterization and Technical Description\",\"CCX\":\"Commander’s Action Group Office Symbol\",\"CD\":\"Capability Director (or Directorate) OR Deputy Commander\",\"CDA\":\"Current Design Activity\",\"CDD\":\"Capability Development Document\",\"CDP\":\"Capability Definition Package\",\"CDR\":\"Critical Design Review\",\"CDRL\":\"Contract Data Requirements List\",\"CDS\":\"Cross Domain Solution\",\"CDT\":\"Chief Developmental Tester\",\"CE\":\"Civil Engineer OR Conducted Emissions\",\"CEP\":\"Circular Error Probability\",\"CERT\":\"Certification\",\"CFL\":\"Core Function Lead\",\"CFLI\":\"Core Function Lead Integrator\",\"CFMP\":\"Core Function Master Plan\",\"CFO\":\"Chief Financial Officer\",\"CFP\":\"Capabilities Focused Planning\",\"CFR\":\"Code of Federal Regulations\",\"CFSR\":\"Contract Funds Status Report\",\"CGA\":\"Capability Gap Assessment\",\"CGM\":\"Common GPS Module\",\"CI\":\"Configuration Item OR Counterintelligence\",\"CICA\":\"Competition in Contracting Act\",\"CIDAS\":\"Contamination Indicator Decontamination Assurance System\",\"CIED\":\"Counter-Improvised Explosive Device\",\"CIMB\":\"Commander’s Inspection Management Board\",\"CIO\":\"Chief Information Officer\",\"CIP\":\"Critical Intelligence Parameter\",\"CIPS\":\"Cyberspace Infrastructure Planning System\",\"CIR\":\"Capital Investment Report\",\"CISP\":\"Counterintelligence Support Plan\",\"CITE\":\"Center of Industrial and Technical Excellence\",\"CJCS\":\"Chairman, Joint Chiefs of Staff\",\"CJCSI\":\"Chairman, Joint Chief of Staff Instruction\",\"CJCSM\":\"Chairman, Joint Chiefs of Staff Manual\",\"CJR\":\"COBRA JUDY Replacement\",\"CJTF\":\"Coalition Joint Task Force\",\"CL\":\"China Lake OR Civilian Leader OR Continuous Learning\",\"CLIN\":\"Contract Line Item Number\",\"CLS\":\"Contractor Logistics Support\",\"CM\":\"Configuration Management OR Consequence Management OR Constellation Management OR Corrective Maintenance\",\"CMBRE\":\"Common Munitions BIT Reprogramming Equipment\",\"CMC\":\"C-5 Core Mission Computer and Weather Radar Program\",\"CML\":\"Capability-Mission Lattice\",\"CMMI\":\"Capability Maturity Model Integration\",\"CMP\":\"Configuration Management Plan\",\"CMRS\":\"Collaboration and Measurements Requirements Summary\",\"CNA\":\"Computer Network Attack\",\"CNEO\":\"Change Notice Engineering Order\",\"CNSSI\":\"Committee on National Security Systems (CNSS) Instruction\",\"CNWDI\":\"Critical Nuclear Weapons Design Information\",\"CO\":\"Contracting Officer\",\"COA\":\"Course of Action\",\"CoC\":\"Certificate of Compliance\",\"COCOM\":\"Combatant Command\",\"COD\":\"Capability Development Document\",\"COI\":\"Critical Operational Issue\",\"COLISEUM\":\"Community On-Line Intelligence System for End Users and Managers\",\"COMAFFOR\":\"Commander Air Force Forces\",\"COMOPTEVFOR\":\"Naval Command Operational Test and Evaluation Force\",\"COMSEC\":\"Communications Security\",\"CoN\":\"Certificate of Networthiness\",\"CONECT\":\"B-52 Combat Network Communications Technology\",\"CONEMP\":\"Concept of Employment\",\"CONOPS\":\"Concept of Operations\",\"COOP\":\"Continuity of Operations Plan\",\"COP\":\"Common Operating Picture\",\"CoP\":\"Community of Practice\",\"COR\":\"Contracting Officer’s Representative\",\"CORE\":\"Critical Operational Issues and Criteria\",\"COTF\":\"Commander, Operational Test Force (OPTEVFOR)\",\"COTS\":\"Commercial Off-the-Shelf\",\"COTT\":\"Combined Operational Test Team\",\"CPA\":\"Chairman’s Program Assessment\",\"CPAF\":\"Cost-Plus Award Fee\",\"CPARS\":\"Contractor Performance Assessment Reporting System\",\"CPCP\":\"Corrosion Prevention and Control Plan\",\"CPD\":\"Capability Production Document\",\"CPI\":\"Crash Position Indicator OR Critical Program Information\",\"CPIF\":\"Cost Plus Incentive Fee\",\"CPM\":\"Capability Portfolio Manager\",\"CPR\":\"Chairman’s Program Recommendation\",\"CR\":\"Change Request\",\"CR6\":\"Hexavalent Chromium\",\"CRA\":\"Continuing Resolution Authority OR Cost Risk Assessment OR Chairman’s Risk Assessment\",\"CRD\":\"Capabilities Requirements Document \",\"CRDA\":\"Cooperative Research and Development Agreement\",\"CRH\":\"Combat Rescue Helicopter\",\"CRIIS\":\"Common Range Integrated Instrumentation System\",\"CRISP\":\"Cross Industry Standard Process for Data Mining\",\"CRM\":\"Component Resolution Matrix OR Crew Resource Management\",\"CRRA\":\"Capabilities Review and Risk Assessment\",\"CRS\":\"Chairman’s Readiness System\",\"CS\":\"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\",\"CSA\":\"Combat Support Agency\",\"CSAF\":\"Chief of Staff of the Air Force\",\"CSAG\":\"Consolidated Sustainment Activity Group\",\"CSAR\":\"Combat Search and Rescue\",\"CSARL\":\"Combat Search and Rescue Locator\",\"CSB\":\"Configuration Steering Board\",\"CSCI\":\"Computer Software Configuration Items\",\"CSE\":\"Center for Systems Engineering OR Common Support Equipment\",\"CSH\":\"Common Support Helicopter\",\"CSI\":\"Critical Safety Item\",\"CSO\":\"Commodity Strategy Official\",\"CSR\":\"Critical System Resources\",\"CSS\":\"Contract Sustainment Support\",\"C-sUAS\":\"Counter-small Unmanned Aerial Systems\",\"CSWS\":\"Contractor Supported Weapon System\",\"CT\":\"Contractor Testing OR Critical Technology\",\"CTA\":\"Capability Threat Assessments OR Center Test Authority\",\"CTE\":\"Critical Technology Element\",\"CTEIP\":\"Central Test & Evaluation Investment Program\",\"CTF\":\"Combined Task Force\",\"CTIC\":\"Contractor Technical Information Code\",\"CTM\":\"Capability Transition Memorandum\",\"CtO\":\"Certificate to Operate\",\"CTOM\":\"Centralized Technical Order Management\",\"CTP\":\"Critical Technical Parameter\",\"CTR\":\"Capability Transition Review\",\"CUI\":\"Controlled Unclassified Information\",\"CUMI\":\"Controlled Unclassified Military Information\",\"CV\":\"Vice Commander OR Capability Viewpoint\",\"CVI\":\"AFOTEC Information Protection/SAP Security (office symbol)\",\"CVLSP\":\"Common Vertical Lift Support Platform\",\"CVPA\":\"Cooperative Vulnerability and Penetration Assessment\",\"CVW\":\"Carrier Air Wing\",\"CWI\":\"Continuous Wave Illuminator\",\"CY\":\"Calendar Year\",\"D&F\":\"Determination and Findings\",\"D,ARA\":\"Director, Acquisition Resources, and Analysis\",\"D/CAPE\":\"Director, Cost Assessment, and Program Evaluation\",\"D/QT&E\":\"Development/Qualification Test and Evaluation\",\"DA\":\"Department of the Army\",\"DAA\":\"Designated Approval Authority\",\"DAB\":\"Defense Acquisition Board\",\"DAC\":\"Designated Acquisition Commander\",\"DACM\":\"Director, Acquisition Career Management\",\"DAE\":\"Defense Acquisition Executive\",\"DAES\":\"Defense Acquisition Executive Summary\",\"DAF\":\"Department of the Air Force\",\"DAG\":\"Defense Acquisition Guidebook\",\"DAMIR\":\"Defense Acquisition Management Information Retrieval\",\"DAO\":\"Designated Acquisition Officials\",\"DARC\":\"Deep Space Advanced Radar Concept\",\"DARPA\":\"Defense Advanced Research Projects Agency\",\"DART\":\"Data, Acquisition, Recording, and Telemetry OR Deficiency Analysis Ranking Technique\",\"DAS\":\"Defense Acquisition System\",\"DASD\":\"Deputy Assistant Secretary of Defense\",\"DATO\":\"Denial of Authorization to Operate\",\"DAU\":\"Defense Acquisition University\",\"DAWIA\":\"Defense Acquisition Workforce Improvement Act\",\"DBC\":\"Defense Business Council\",\"DBS\":\"Defense Business Systems\",\"DBSMC\":\"Defense Business Systems Management Committee\",\"DC\":\"Derivative Classifier OR Direct Current\",\"DCAA\":\"Defense Contract Audit Agency\",\"DCAPE\":\"Director of Cost Assessment and Program Evaluation\",\"DCAPES\":\"Deliberate and Crisis Action Planning and Execution Segments\",\"DCGS\":\"Distributed Common Ground System\",\"DCID\":\"Director of Central Intelligence Directive\",\"DCMA\":\"Defense Contract Management Agency\",\"DCPDS\":\"Defense Civilian Personnel Data System\",\"DCR\":\"DOTMLPF-P Change Recommendation\",\"DCS\":\"Deputy Chief of Staff\",\"DDNI/M\":\"Deputy Director of National Intelligence for Management\",\"DDR\":\"Deputy Director for Requirements OR Dismount Detection Radar\",\"DDT&E\":\"Director, Developmental Test and Evaluation\",\"DEAD\":\"Destruction of Enemy Air Defenses\",\"DEAMS\":\"Defense Enterprise Accounting and Management System\",\"DEF\":\"Developmental Evaluation Framework\",\"DepSecDef\":\"Deputy Secretary of Defense\",\"Det/CC\":\"Detachment Commander\",\"DEW\":\"Directed Energy Weapons\",\"DEWCB\":\"Directed Energy Weapons Certification Board\",\"DFARS\":\"Defense Federal Acquisition Regulation Supplement\",\"DFCN\":\"Dual Frequency Civil Navigation\",\"DFoS\":\"Decontamination Family of Systems\",\"DHMSM\":\"Defense Healthcare Management Systems Modernization\",\"DIA\":\"Defense Intelligence Agency\",\"DIACAP\":\"DoD Information Assurance Certification and Accreditation Process\",\"DID\":\"Data Item Description\",\"DIP\":\"DIACAP Implementation Plan\",\"DISA\":\"Defense Information Systems Agency\",\"DISR\":\"Department of Defense Information Technology Standards Registry\",\"DITSCAP\":\"Department of Defense Information Technology Security Certification and Accreditation Program\",\"DIV\":\"Data and Information Viewpoint\",\"DLA\":\"Defense Logistics Agency\",\"DLR\":\"Depot-Level Repairable\",\"DM\":\"Data Mining\",\"DMAP\":\"Data Management and Analysis Plan\",\"DMAWG\":\"Depot Maintenance Activation Working Group\",\"DMEA\":\"Defense Microelectronics Activity\",\"DMI\":\"Depot Maintenance Interservice\",\"DMIX JLV\":\"Defense Medical Information Exchange Joint Legacy Viewer\",\"DMS\":\"Defensive Management System OR Diminishing Manufacturing Sources\",\"DMSMS\":\"Diminishing Manufacturing Sources Material Shortages\",\"DNAD\":\"Domestic Non-Availability Determination\",\"DNI\":\"Director of National Intelligence\",\"DoD\":\"Department of Defense\",\"DODAAC\":\"Department of Defense Activity Code\",\"DODD\":\"Department of Defense Directive\",\"DODI\":\"Department of Defense Instruction\",\"DODIN\":\"Department of Defense Information Network\",\"DODIPP\":\"Department of Defense Intelligence Production Program\",\"DODISS\":\"Department of Defense Index of Specifications and Standards\",\"DODM\":\"Department of Defense Manual\",\"DOE\":\"Department of Energy OR Design of Experiments\",\"DoN\":\"Department of the Navy\",\"DOT&E\":\"Director of Operational Test and Evaluation\",\"DOTMLPF-P\":\"Doctrine, Organization, Training, materiel, Leadership Policy and Education, Personnel, Facilities, and Policy\",\"DP\":\"Development Planning\",\"DPAP\":\"Director of Procurement and Acquisition Policy\",\"DPAS\":\"Defense Priorities and Allocation System\",\"DPEM\":\"Depot Purchased Equipment Maintenance\",\"DPG\":\"Defense Planning Guidance\",\"DPGS\":\"Data Processing Ground Station\",\"DPPG\":\"Defense Planning and Programming Guidance\",\"DR SKO\":\"Dismounted Reconnaissance Sets, Kits, and Outfits\",\"DR\":\"Deficiency Report\",\"DRAGON\":\"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\",\"DRB\":\"Deficiency Review Board\",\"DREN\":\"Defense Research Engineering Network\",\"DRI\":\"Data Referential Integrity\",\"DRI&R\":\"Deficiency Reporting, Investigation and Resolution\",\"DRM\":\"DRAGON Requirements Memorandum\",\"DRMO\":\"Defense Reutilization Marketing Office\",\"DRR\":\"Design Readiness Review\",\"DRU\":\"Direct Reporting Unit\",\"DS&TI\":\"Designated Science and Technology Information\",\"DSA\":\"Direct Sales Agreement\",\"DSC\":\"Decision Support Question\",\"DSCA\":\"Defense Security Cooperation Agency\",\"DSM\":\"Development System Manager OR Digital System Model\",\"DSOR\":\"Depot Source of Repair\",\"DSOR-EM\":\"Depot Source of Repair-Electronic Manager\",\"DT\":\"Developmental Test\",\"DT&E\":\"Developmental Test and Evaluation\",\"DTD\":\"Data Type Definition\",\"DTIC\":\"Defense Technical Information Center\",\"DTM\":\"Directive-Type Memorandum\",\"DTP\":\"Detailed Test Plan\",\"DUSD\":\"Deputy Under Secretary of Defense\",\"E&S\":\"Effectiveness and Suitability\",\"E-3 DRAGON\":\"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\",\"E3\":\"Electromagnetic Environmental Effects\",\"EA\":\"Economic Analysis OR Electronic Attack OR Evolutionary Acquisition OR Executing Authority\",\"EAC\":\"Estimate at Completion\",\"ECD\":\"Estimated Completion Date\",\"ECM\":\"Electronic Countermeasures\",\"ECN\":\"Enclave Control Node\",\"ECSS\":\"Expeditionary Combat Support System\",\"ED\":\"Executive Director\",\"EDGC\":\"Engineering Data Guidance Conference\",\"EDM\":\"Engineering Data Manager (or Management) OR Engineering Development Model\",\"EDSC\":\"Engineering Data Service Center\",\"EEC\":\"Enterprise Engineering Center\",\"EEIC\":\"Element of Expense Investment Code\",\"EFF\":\"Essential Function Failure\",\"EHF\":\"Extremely High Frequency\",\"EIAP\":\"Environment Impact Analysis Process\",\"EIEMA\":\"Enterprise Information Environment Mission Area\",\"EIS\":\"Early Influence Strategy\",\"EIT\":\"Early Influence Team\",\"EITDR\":\"Enterprise Information Technology Data Repository\",\"EKMS\":\"Electronic Key Management System\",\"ELA\":\"Elevated Level of Assurance\",\"ELT\":\"Emergency Locator Transmitter\",\"EMA\":\"Expectation Management Agreement\",\"EMC\":\"Electromagnetic Compatibility\",\"EMC/EMI\":\"Electromagnetic Compatibility/Electromagnetic Interference\",\"EMD\":\"Engineering and Manufacturing Development\",\"EMI\":\"Electromagnetic Interference\",\"EMP\":\"Electromagnetic Pulse\",\"EMSEC\":\"Emission Security\",\"EMV\":\"Electromagnetic Vulnerability\",\"ENSIP\":\"Engine Structural Integrity Program\",\"EO\":\"Electro-Optical OR Executive Order OR Engineering Order\",\"EOA\":\"Early Operational Assessment\",\"EOD\":\"Explosive Ordnance Disposal\",\"EP\":\"Electronic Protection\",\"EPAWSS\":\"F-15 Eagle Passive and Active Warning and Survivability System\",\"EPG\":\"Electronic Proving Ground\",\"EPIP\":\"AIM-120C Advanced Electronic Protection Improvement Program\",\"EPS\":\"Enhanced Polar System\",\"EPVD\":\"Electromagnetically Enhanced Physical Vapor Deposition (gun tube coating\",\"ERF\":\"Electronic Remote Fill\",\"ERM\":\"Environmental Resources Manager\",\"ESC\":\"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\",\"ESOH\":\"Environment, Safety, and Occupational Health\",\"ESOHC\":\"Environment, Safety, and Occupational Health Council\",\"ESOHCB\":\"Environment, Safety, and Occupational Health Certification Board\",\"ESOH-MS\":\"Environment, Safety, and Occupational Health Management System\",\"ESP\":\"Emergency and Special Program\",\"ESS\":\"Effectiveness, Suitability, and Survivability OR Evolved Strategic Satellite Communications\",\"ESW\":\"Electronic Systems Wing OR Evaluation Summary Worksheet\",\"ETIMS\":\"Enhanced Technical Information Management System\",\"ETM\":\"Electronic Technical Manual\",\"ETO\":\"Executing Test Organization\",\"EU\":\"Engineering Units\",\"EUC\":\"End Use Certificate\",\"EV\":\"Evaluation View\",\"EVM\":\"Earned Value Management\",\"EVM-CR\":\"Earned Value Management-Central Repository\",\"EVMS\":\"Earned Value Management System\",\"EW\":\"Electronic Warfare\",\"EWIIP\":\"Electronic Warfare Infrastructure Improvement Program\",\"EWIR\":\"Electronic Warfare Integrated Reprogramming\",\"EWSR\":\"Executive Weapons System Review\",\"F-15 EPAWSS\":\"F-15 Eagle Passive and Active Warning and Survivability System\",\"F-15 IRST\":\"F-15 Infrared Search and Track System\",\"F3I\":\"Form, Fit, Function, or Interface\",\"FAA\":\"Federal Aviation Administration OR Functional Area Analysis\",\"FAB-T\":\"Family of Advanced Beyond Line Of Sight Terminals\",\"FAC-A\":\"Forward Air Controller-Airborne\",\"FAR\":\"Federal Acquisition Regulation\",\"FARM\":\"Functional Area Records Manager\",\"FAT\":\"First Article Test\",\"FCA\":\"Functional Configuration Audit\",\"FCB\":\"Functional Capabilities Board\",\"FCC\":\"Flagship Capability Concepts\",\"FCT\":\"Foreign Comparative Test\",\"FD\":\"Fielding Decision\",\"FD/SC\":\"Failure Definition/Scoring Criteria\",\"FDB\":\"Final Evaluation and Decision Brief\",\"FDD\":\"Full Deployment Decision\",\"FDDR\":\"Full Deployment Decision Review\",\"FDE\":\"Force Development Evaluation\",\"FDO\":\"Fee Determining Official\",\"FDR\":\"Final (or Formal) Design Review\",\"FET\":\"Force Element Terminal\",\"FFP\":\"Firm Fixed Price\",\"FFRDC\":\"Federally Funded Research and Development Centers\",\"FFT\":\"Friendly Force Tracking\",\"FH\":\"Flying Hours\",\"FIAR\":\"Financial Improvement and Audit Readiness\",\"FIP\":\"Federal Information Processing\",\"FISCAM\":\"Federal Information System Controls Audit Manual\",\"FISMA\":\"Federal Information Security Management Act of 2002\",\"FM\":\"Financial Management OR Frequency Modulation OR Functional Manager\",\"FMC\":\"Fully Mission Capable\",\"FMECA\":\"Failure Mode, Effects, and Criticality Analysis\",\"FMM\":\"Flight Manual Manager\",\"FMP\":\"Flight Manuals Program OR Foreign Materiel Program\",\"FMR\":\"Financial Management Regulation\",\"FMRS\":\"Financial Management Regulation System\",\"FMS\":\"Foreign Military Sales\",\"FMU-139 D/B\":\"Fuze Module Unit-139\",\"FNA\":\"Functional Needs Analysis\",\"FOA\":\"Field Operating Agency\",\"FOB\":\"Forward Operating Base\",\"FOC\":\"Full Operational Capability\",\"FOIA\":\"Freedom of Information Act\",\"FoM\":\"Follow-on Modernization\",\"FORGE\":\"Future Operationally Resilient Ground Evolution\",\"FoS\":\"Family of Systems\",\"FOT&E\":\"Follow-on Operational Test and Evaluation\",\"FOU\":\"Full Operational Utility\",\"FOUO\":\"For Official Use Only\",\"FOV\":\"Field of View\",\"FPAF\":\"Fixed-Price with Award Fee\",\"FPD\":\"Follow-on Production Decision\",\"FPDS-NG\":\"Federal Procurement data System-Next Generation\",\"FPIF\":\"Fixed-Price Incentive\",\"FPR\":\"Final Pricing Report OR Final Proposal Revision\",\"FPRA\":\"Forward Price Rate Agreements\",\"FQR\":\"Formal Qualification Review\",\"FRD\":\"Formerly Restricted Data\",\"FRP\":\"Full-Rate Production\",\"FRP/FD\":\"Full-Rate Production or Full Deployment\",\"FRPDR\":\"Full Rate Production Decision Review\",\"FRRB\":\"Functional Requirements Review Board\",\"FSA\":\"Functional Solution Analysis\",\"FSC\":\"Federal Supply Classification\",\"FSR\":\"Field Service Representative\",\"FTE\":\"Full Time Equivalent\",\"FTX\":\"Field Training Exercise\",\"FY\":\"Fiscal Year\",\"FYDP\":\"Future Years Defense Program\",\"G&A\":\"General and Administrative (Expense)\",\"GAO\":\"Government Accountability Office\",\"GAT\":\"Government Analysis Tool\",\"GBS\":\"Global Broadcast Service\",\"GBSD\":\"Ground Based Strategic Deterrent\",\"GBU\":\"Guided Bomb Unit\",\"GCIC\":\"Global Cyberspace Integration Center\",\"GCS\":\"Ground Control Stations\",\"GCSS-AF\":\"Global Combat Support System – Air Force\",\"GDT\":\"Government Development Test\",\"GEF\":\"Guidance for the Employment of the Force\",\"GEO\":\"Geosynchronous Earth Orbit\",\"GFE\":\"Government Furnished Equipment\",\"GFI\":\"Government Furnished Information\",\"GFM\":\"Global Force Management\",\"GFP\":\"Government Furnished Property\",\"GH GSMP\":\"Global Hawk Ground Segment Modernization Program\",\"GIDEP\":\"Government Industry Data Exchange Program\",\"GIG\":\"Global Information Grid\",\"GLSC\":\"Global Logistics Support Center\",\"GMT\":\"Ground Movement Terrain Radar\",\"GMTI\":\"Ground Moving Target Indicator\",\"GO\":\"General Officer\",\"GO/SES\":\"General Officer/Senior Executive Service\",\"GOCO\":\"Government Owned Contractor Operated\",\"GOSG\":\"General Officer Steering Group\",\"GOTS\":\"Government Off-the-Shelf\",\"GPA\":\"GPS Pulse-per-Second Adapter\",\"GPC\":\"Government Purchase Card\",\"GPD\":\"General Purpose Decontaminant Program\",\"GPLR\":\"Government Purpose License Rights\",\"GPR\":\"Government Purpose Rights\",\"GPS III COps\":\"Global Positioning System III Contingency Operations\",\"GPS MCEU\":\"Global Positioning System M-Code Early Use\",\"GPS MGUE\":\"Military GPS User Equipment\",\"GPS OCX\":\"GPS Next Generation Operational Control System\",\"GPS\":\"Global Positioning System\",\"GS\":\"General Schedule\",\"GSA\":\"Government Services Administration\",\"GSMP\":\"Ground Segment Modernization Program\",\"GTG-F\":\"Global Information Grid Technical Guidance Federation\",\"G-TSCMIS\":\"Global Theater Security Cooperative Management Information System\",\"GTV\":\"Guided Test Vehicle\",\"HAF\":\"Headquarters Air Force\",\"HAFMD\":\"Headquarters Air Force Mission Directive\",\"HAMS\":\"Hardness Assurance, Maintenance, and Surveillance\",\"HARPOON\":\"(AGM-84-Fixed Wing; RGM-Surface Ships; UGM-Submarine Launched)\",\"HCA\":\"Head of Contracting Activity (or Agency)\",\"HCI\":\"Human-Computer Interactions\",\"HCSP\":\"Human Capital Strategic Plan\",\"HCSW\":\"Hypersonic Conventional Strike Weapon\",\"HDF\":\"Hierarchical Data Format\",\"HEMP\":\"High-Altitude Electromagnetic Pulse\",\"HERF\":\"Hazards of Electromagnetic Radiation to Volatile Material\",\"HERO\":\"Hazards of Electromagnetic Radiation to Ordinance\",\"HERP\":\"Hazards of Electromagnetic Radiation to Personnel\",\"HFE\":\"Human Factors Engineering\",\"HITL\":\"Hardware in the Loop\",\"HM/HS\":\"Hardness Maintenance / Hardness Surveillance\",\"HMS\":\"Handheld, Manpack, and Small Form Fit\",\"HO\":\"HQ AFOTEC History Office\",\"HOI\":\"Headquarters Operating Instruction\",\"HPT\":\"High Performance Team\",\"HQ\":\"Headquarters\",\"HSI\":\"Human Systems Integration\",\"HSN\":\"High Speed Network\",\"HSP\":\"Health and Safety Plan\",\"HTM\":\"Hard Target Munitions\",\"HTVSF\":\"Hard Target Void Sensing Fuze\",\"HwA\":\"Hardware Assurance\",\"IA\":\"Information Assurance (replaced by “cybersecurity”)\",\"IAC\":\"International Armaments Cooperation\",\"IAD\":\"Integrated Air Defense\",\"IADS\":\"Integrated Air Defense System\",\"IAE\":\"Integrated Aircrew Ensemble\",\"IAMD\":\"Integrated Air and Missile Defense\",\"IATO\":\"Interim Authorization to Operate\",\"IATT\":\"Interim Authority to Test or Authorization to Test\",\"IAVA\":\"Information Assurance Vulnerability Alert\",\"IAW\":\"In Accordance With\",\"IB\":\"Involvement Briefing\",\"IBA\":\"Individual Body Armor\",\"IBBP\":\"Involvement Bullet Background Paper\",\"IBCT\":\"Infantry Brigade Combat Team\",\"IBDC2\":\"Integrated Base Defense Command and Control\",\"IBDSS\":\"Integrated Base Defense Security System\",\"IBR\":\"Integrated Baseline Review\",\"IBS\":\"Integrated Broadcast Service\",\"IC\":\"Intelligence Community\",\"ICADS\":\"Individual Combat Aircrew Display System\",\"ICBM\":\"Intercontinental Ballistic Missile\",\"ICCR\":\"Intelligence Community Capability Requirements\",\"ICD\":\"Initial Capabilities Document OR Interface Control Document\",\"iCDD\":\"initial Capability Development Document\",\"ICE\":\"Independent Cost Estimate\",\"ICEP\":\"Information Certification Evaluation Plan\",\"ICM\":\"Interim Contractor Support\",\"ICP\":\"Inventory Control Point\",\"ICS\":\"Interim Contract Support\",\"ICT\":\"Integrated Concept Team\",\"ID\":\"Identification\",\"ID/IQ\":\"Indefinite Delivery/Indefinite Quantity\",\"IDE\":\"Integrated Data Environment\",\"IDL\":\"Indentured Data List\",\"IDRL\":\"Integrated Data Requirements List\",\"IEB\":\"Initial Evaluation Briefing\",\"IED\":\"Improvised Explosive Device\",\"iEHR\":\"Integrated Electronic Health Records\",\"IER\":\"Information Exchange Requirements\",\"IETM\":\"Interactive Electronic Technical Manual\",\"IFC\":\"Integrated Functional Capability\",\"IFDL\":\"Intraflight Datalink\",\"IFM\":\"Intelligence in Force Modernization\",\"IFTU\":\"In-Flight Targeting Update\",\"IGF\":\"Inherently Governmental Function\",\"IITD\":\"Initial Integrated Test Design\",\"IL\":\"Involvement Letter\",\"ILCM\":\"Integrated Life Cycle Management\",\"ILS\":\"Instrument Landing System OR Integrated Logistics Support\",\"ILSP\":\"Integrated Logistics Support Plan\",\"IM\":\"Insensitive Munitions\",\"IMC\":\"Instrument Meteorological Conditions\",\"IMD\":\"Intelligence Mission Data\",\"IMDS\":\"Integrated Maintenance Data System\",\"IMET\":\"International Military Education and Training\",\"IMP\":\"Integrated Master Plan\",\"IMS\":\"Integrated Master Schedule\",\"IMT\":\"Information Management Tool\",\"IMTP\":\"Integrated Master Test Plan\",\"INC\":\"Increment\",\"INS\":\"Inertial Navigation System\",\"IO\":\"Information Operations\",\"IOC\":\"Initial Operational Capability\",\"IOT\":\"Initial Operational Test\",\"IOT&E\":\"Initial Operational Test and Evaluation\",\"IP\":\"Information Protection OR Initial Point OR Intellectual Property OR Internet Protocol\",\"IPA\":\"Independent Program Assessment\",\"IPAT\":\"Independent Program Assessment Team\",\"IPL\":\"Integrated Priority List\",\"IPMR\":\"Independent Program Management Report\",\"IPR\":\"In-Process Review\",\"IPS\":\"Integrated Program Summary OR Intellectual Property Strategy\",\"IPSS\":\"Initial Provisioning Performance Specifications\",\"IPT\":\"Integrated Product Team\",\"IR\":\"Infrared\",\"IRAD\":\"Independent Research and Development\",\"IRB\":\"Intelligence Resources Board OR Investment Review Board\",\"IRCM\":\"Infrared Countermeasures\",\"IRSS\":\"Information and Resource Support System\",\"IRST\":\"Infrared Search and Track System\",\"IS CDD\":\"Information System Capability Development Document\",\"IS ICD\":\"Information System Initial Capabilities Document\",\"IS\":\"Information System\",\"ISA\":\"International Standardization Agreement\",\"ISACA\":\"Information Systems Audit and Control Association\",\"ISO\":\"International Standards Organization\",\"ISOO\":\"Information Security Oversight Office\",\"ISP\":\"Information Support Plan\",\"ISPAN\":\"Integrated Strategic Planning and Analysis Network\",\"ISR\":\"Intelligence, Surveillance, and Reconnaissance OR Interim Summary Report\",\"ISSM\":\"Information System Security Manager\",\"ISWG\":\"Intelligence Support Working Group\",\"IT Lean\":\"Information Technology Lean\",\"IT\":\"Information Technology OR Integrated Testing\",\"IT&E\":\"Integrated Test and Evaluation\",\"IT/NSS\":\"Information Technology/National Security System\",\"ITA\":\"Interface Test Adapter\",\"ITAB\":\"Information Technology Acquisition Board\",\"ITC\":\"Integrated Test Concept\",\"ITD\":\"Initial Test Design\",\"ITEA\":\"Initial Threat Environment Assessment\",\"ITO\":\"Initial Tasking Order\",\"ITP\":\"Integrated Test Plan\",\"ITT\":\"Integrated Test Team\",\"IUID\":\"Item Unique Identification\",\"IUS\":\"Internal Use Software\",\"IW\":\"Information Warfare\",\"IWBU\":\"Internal Weapons Bay Upgrade\",\"IWSM\":\"Integrated Weapons System Management\",\"J&A\":\"Justification and Approval\",\"J-8/DDR\":\"Joint Staff J-8, Deputy Director for Requirements\",\"J-8/SAPCOORD\":\"Joint Staff J-8, Special Access Program Coordinator\",\"JAFAN\":\"Joint Air Force Army Navy\",\"JAGM\":\"Joint Air-to-Ground Missile\",\"JALN\":\"Joint Aerial Layered Network\",\"JASP\":\"Joint Aircraft Survivability Program\",\"JASSM\":\"Joint Air-to-Surface Standoff Missile\",\"JAWS\":\"Joint Avionics Workstation\",\"JBADS\":\"Joint Biological Agent Decontamination System\",\"JBTDS\":\"Joint Biological Tactical Detection System\",\"JCA\":\"Joint Capability Area\",\"JCAAMP\":\"Joint Improvised Explosive Device Defeat Capability Approval and Acquisition Management Process\",\"JCALS\":\"Joint Computer-Aided Acquisition and Logistic Support\",\"JCB\":\"Joint Capabilities Board\",\"JCC2\":\"Joint Cyber Command and Control\",\"JCCA\":\"Joint Combat Capability Assessment\",\"JCD\":\"Joint Capabilities Document\",\"JCIDS\":\"Joint Capabilities Integration and Development System\",\"JCPATE\":\"Joint C4I Program Assessment Tool-Empowered\",\"JCREW\":\"Joint Counter Radio-Controlled Improvised Explosive Device Electronic Warfare\",\"JCS\":\"Joint Chiefs of Staff\",\"JCTD\":\"Joint Capability Technology Demonstration\",\"JDAM\":\"Joint Direct Attack Munition\",\"JDMAG\":\"Joint Depot Maintenance Activities Group\",\"JDRS\":\"Joint Deficiency Reporting System\",\"JEDMICS\":\"Joint Engineering Data Management Information and Combat System\",\"JEM\":\"Joint Effects Model\",\"JENM\":\"Joint Enterprise Network Manager\",\"JEON\":\"Joint Emergent Operational Need\",\"JFC\":\"Joint Functional Concept\",\"JFCC\":\"Joint Functional Component Commander\",\"JIC\":\"Joint Integrating Concept\",\"JICO\":\"Joint Interface Control Officer\",\"JIE\":\"Joint Intelligence Estimate\",\"JIEDDF\":\"Joint Improvised Explosive Device Defeat Fund\",\"JIEDDO\":\"Joint Improvised Explosive Device Defeat Organization\",\"JITC\":\"Joint Interoperability Test Command\",\"JLE\":\"Joint Logistics Estimate\",\"JLLP\":\"Joint Lessons Learned Program\",\"JLTV\":\"Joint Light Tactical Vehicle\",\"JMC\":\"Joint Mission Computer\",\"JMETC\":\"Joint Mission Environment Test Capability\",\"JMM\":\"Joint Miniature Munitions\",\"JMS\":\"Joint Space Operations Center (JSpOC) Mission System\",\"JMT\":\"Joint Mission Thread\",\"JOC\":\"Joint Operating Concept\",\"JOMIS\":\"Joint Operational Medicine Information Systems\",\"JOpsC\":\"Joint Operations Concept\",\"JOTT\":\"JSF Operational Test Team\",\"JP\":\"Joint Publication\",\"JPALS\":\"Joint Precision Approach and Landing System\",\"JPD\":\"Joint Potential Designator\",\"JPE\":\"Joint Personnel Estimate\",\"JPG\":\"Joint Planning Guidance\",\"JPO\":\"Joint Strike fighter Program Office\",\"JRAC\":\"Joint Rapid Acquisition Cell\",\"JRMET\":\"Joint Reliability and Maintainability Evaluation Team\",\"JRO\":\"Joint Requirements Office\",\"JROC\":\"Joint Requirements Oversight Council\",\"JROCM\":\"Joint Requirements Oversight Council Memorandum\",\"JS\":\"Joint Staff\",\"JSA\":\"Joint Strategic Assessment\",\"JSAM-FW\":\"Joint Service Aircrew Mask-Fixed Wing\",\"JSAM-SA\":\"Joint Service Aircrew Mask-Strategic Aircraft\",\"JSAM-TA\":\"Joint Service Aircrew Mask-Tactical Aircraft\",\"JSD\":\"Joint Staffing Designator\",\"JSE\":\"Joint Simulation Environment\",\"JSEW\":\"Joint Sensitive Equipment Wipes (Decontamination Family of Systems)\",\"JSF\":\"Joint Strike Fighter\",\"JSIG\":\"Joint Special Access Program (SAP) Implementation Guide\",\"JSOW\":\"Joint Stand-Off Weapon\",\"JSpOC\":\"Joint Space Operations Center\",\"JSPS\":\"Joint Strategic Planning System\",\"JSR\":\"Joint Strategy Review\",\"JSS\":\"Joint Interface Control Officer (JICO) Support System\",\"JSTAR\":\"Joint System Threat Assessment Report\",\"JSTARS RECAP\":\"Joint Surveillance Target Attack Radar System Recapitalization\",\"JT&E\":\"Joint Test and Evaluation\",\"JTAC\":\"Joint Terminal Attack Controller\",\"JTR\":\"Joint Tactical Radio\",\"JTRS\":\"Joint Tactical Radio System\",\"JTRS-AMF\":\"Joint Tactical Radio System-Airborne Maritime Fixed\",\"JUON\":\"Joint Urgent Operational Need\",\"JUPITR\":\"Joint United States Forces Korea Portal and Integrated Threat Recognition\",\"JWARN\":\"Joint Warning & Reporting Network\",\"JWICS\":\"Joint Worldwide Intelligence Communications System\",\"KDP\":\"Key Decision Point\",\"KIP\":\"Key Interface Profile\",\"KLP\":\"Key Leadership Position\",\"KM/DS\":\"Knowledge Management/Decision Support\",\"KN\":\"Knowledge Now\",\"KPP\":\"Key Performance Parameter\",\"KSA\":\"Key System Attribute\",\"L2\":\"Lessons Learned\",\"LA\":\"Logistics Assessment\",\"LAT\":\"Lot Acceptance Test\",\"L-band\":\"Long Band\",\"LC\":\"HQ AFOTEC Legal Counsel\",\"LCB\":\"Lower Confidence Bound\",\"LCC\":\"Life Cycle Cost\",\"LCCE\":\"Life Cycle Cost Estimate\",\"LCMC\":\"Life Cycle Management Center\",\"LCMP\":\"Life Cycle Management Plan\",\"LCRM\":\"Life Cycle Risk Management\",\"LCS\":\"Launch and Checkout System\",\"LCSP\":\"Life Cycle Sustainment Plan\",\"LD\":\"Limited Deployment OR Logistics Demonstration\",\"LDC\":\"LAN Data Collector\",\"LDTO\":\"Lead Developmental Test Organization\",\"LED\":\"Light Emitting Diode\",\"LEO\":\"Low Earth Orbit\",\"LEP\":\"Life Extension Program\",\"LFD\":\"Limited Fielding Decision\",\"LFT&E\":\"Live Fire Test and Evaluation\",\"LHA\":\"Logistics Health Assessments\",\"LJDAM\":\"Laser Joint Direct Attack Munition (GBU-56)\",\"LM\":\"Lockheed Martin\",\"LMD\":\"Logistics MANPRINT Demonstration\",\"LMDP\":\"Life Cycle Mission Data Plan\",\"LNE\":\"Late Network Entry\",\"LNO\":\"Liaison Officers\",\"LOA\":\"Letter of Offer and Acceptance\",\"LORA\":\"Level of Repair Analysis\",\"LOS\":\"Line of Sight\",\"LR\":\"Limited Rights\",\"LRDR\":\"Long Range Discrimination Radar\",\"LRIP\":\"Low Rate Initial Production\",\"LRSO\":\"Long Range Standoff\",\"LRT\":\"Logistics Response Time\",\"LRU\":\"Line-Replaceable Unit\",\"LSC\":\"Logistics Support Concept\",\"LSE\":\"Lead Systems Engineer\",\"LSI\":\"Large Scale Integration OR Lead Systems Integrator\",\"LTE\":\"Last Test Event\",\"LTWG\":\"Logistics Test Working Group\",\"LUT\":\"Limited User Test\",\"LVC\":\"Live, Virtual, and Constructive\",\"M&S\":\"Modeling and Simulation\",\"M&S CO\":\"Modeling and Simulation Coordination Office\",\"MAAP\":\"Master Air Attack Plan\",\"MAAPTK\":\"Master Air Attack Planning Toolkit\",\"MAC\":\"Mission Assurance Category\",\"MACH\":\"Modular Air Crew Helmet\",\"MADL\":\"Multifunction Advanced Data Link\",\"MAF-DRC\":\"Mobility Air Forces-Dynamic Retasking Capability\",\"MAFPS\":\"Mobility Air Force Automated Flight Planning Service\",\"MAIS\":\"Major Automated Information System\",\"MAJCOM\":\"Major Command\",\"MALD-J\":\"Miniature Air Launched Decoy-Jammer\",\"MANPAD\":\"Man Portable Air Defense System\",\"MANPRINT\":\"Manpower and Personnel Integration\",\"MAnTSS\":\"Modular Analysis and Test Support System\",\"MAR\":\"Monthly Acquisition Report\",\"MAV\":\"Maverick\",\"MBITR\":\"Multiband Inter/Intra Team Radio\",\"MBTD\":\"Mission Based Test Design\",\"MC\":\"Mission Capable\",\"MCF\":\"Mission Critical Functions\",\"MCOTEA\":\"Marine Corps Operational Test and Evaluation Activity\",\"MCR\":\"Message Completion Rate\",\"MD\":\"Mission Directive\",\"MDA\":\"Milestone Decision Authority OR Missile Defense Agency\",\"MDAP\":\"Major Defense Acquisition Program\",\"MDD\":\"Maintenance Data Documentation OR Material Development Decision\",\"MDF\":\"Mission Data File\",\"MDS\":\"Mission Design Series\",\"MDT\":\"Mean Down Time\",\"ME/SE\":\"Maintenance Engineering/Sustaining Engineering\",\"MECSIP\":\"Mechanical Subsystems Integrity Plan\",\"MEDALS\":\"Military Engineering Data Asset Locator System\",\"MEFL\":\"Mission Essential Functions List\",\"MEO\":\"Medium Earth Orbit\",\"MER\":\"Manpower Estimate Report\",\"MESL\":\"Minimum Essential Subsystems List\",\"MEV\":\"Military Equipment Valuation\",\"MFOQA\":\"Military Flight Operations Quality Assurance\",\"MFP\":\"Major Force Program OR Materiel Fielding Plan\",\"MFR\":\"Memorandum for Record\",\"MFT\":\"Multi-Functional Team\",\"MGRS\":\"Military Grid Referencing System\",\"MGUE Inc 2 HH\":\"Military GPS User Equipment Hand Held\",\"MGUE\":\"Military GPS User Equipment\",\"MHS\":\"Modular Handgun System\",\"MHz\":\"Megahertz\",\"MIL-DTL\":\"Military Detail (Specification)\",\"MIL-HDBK\":\"Military Handbook\",\"MIL-PRF\":\"Military Performance (Specification)\",\"MIL-STD\":\"Military Standard\",\"MIP\":\"Materiel Improvement Program OR Military Intelligence Program\",\"MIPR\":\"Military Interdepartmental Purchase Request\",\"MIPRB\":\"Material Improvement Program Review Board\",\"MLS\":\"Multiple Levels of Security\",\"MMT\":\"Munitions, Missiles, and Target\",\"MNS\":\"Mission Needs Statement\",\"MOA\":\"Memorandum of Agreement\",\"MOASP\":\"Management and Oversight of Acquisition Services Process\",\"MOE\":\"Measure of Effectiveness\",\"MOEs\":\"Measures of Effectiveness\",\"MOP\":\"Measure of Performance\",\"MOPP\":\"Mission Oriented Protective Posture\",\"MORV\":\"Mission-Oriented Response Variables\",\"MOS\":\"Measure of Suitability OR Military Occupational Specialty\",\"MOSA\":\"Modular Open Systems Approach\",\"MOT&E\":\"Multiservice Operational Test and Evaluation\",\"MOU\":\"Memorandum of Understanding\",\"MP\":\"Mission Profile\",\"MPA\":\"Manpower Authorization\",\"MPE\":\"Mission Planning Element\",\"MPGPA\":\"Multipart GPS Pulse-per-Second Adapter\",\"MPS\":\"Master Program Schedule OR Mission Planning System\",\"MPTO\":\"Methods and Procedures Technical Order\",\"MRA\":\"Manufacturing Readiness Assessment\",\"MRB\":\"Mission Requirements Board\",\"MRDS\":\"Man-Portable Radiological Detection System\",\"MRL\":\"Manufacturing Readiness Level\",\"MROi\":\"Air Force Depot Maintenance, Repair, and Overhaul Initiative\",\"MRP\":\"Munitions Requirements Process\",\"MRR\":\"Materiel Release Review\",\"MRRB\":\"Maintenance Requirement Review Board\",\"MRSP\":\"Mobility Readiness Spares Package\",\"MRTFB\":\"Major Range and Test Facility Base\",\"MS\":\"Milestone\",\"MSA\":\"Materiel Solution Analysis\",\"MSIAC\":\"Modeling and Simulation Information Analysis Center\",\"MSL\":\"Mean Sea Level\",\"MSSP\":\"Modeling and Simulation Support Plan\",\"MTBEFF\":\"Mean Time Between Essential Function Failures\",\"MTTR\":\"Mean Time To Repair\",\"MUA\":\"Military Utility Assessment\",\"MUOS\":\"Mobile User Objective System\",\"MW\":\"Measures Workshop\",\"NAOC\":\"National Airborne Operations Center\",\"NASIC\":\"National Air and Space Intelligence Center\",\"NATO\":\"North Atlantic Treaty Organization\",\"NAVPLAN TPC\":\"Navigation Plan Tactical Pilotage Charts\",\"NBC\":\"Nuclear, Biological and Chemical\",\"NC2-ESI\":\"Nuclear Command and Control-Extremely Sensitive Information\",\"NC3\":\"Nuclear Command, Control, Communications\",\"NCOW\":\"Network-Centric Operations and Warfare\",\"NCOW RM\":\"Net-Centric Operations and Warfare Reference Model\",\"NDAA\":\"National Defense Authorization Act\",\"NDF\":\"Network Design Facility\",\"NDI\":\"Non-Developmental Item\",\"NDS\":\"National Defense Strategy\",\"NEPA\":\"National Environmental Policy Act\",\"NET\":\"New Equipment Training\",\"NetRA\":\"Network Risk Assessment\",\"NEW\":\"Network Enabled Weapon\",\"NGG\":\"Next Generation Geosynchronous Earth Orbit (GEO)\",\"NGP\":\"Next Generation Polar\",\"NGA\":\"National Geospatial-Intelligence Agency\",\"NGB\":\"National Guard Bureau\",\"NGCD\":\"Next Generation Chemical Detector\",\"NGDS\":\"Next Generation Diagnostic System\",\"NGREA\":\"National Guard and Reserve Equipment Account\",\"NGS\":\"Non-Government Standard (commercial)\",\"NID\":\"National Interest Determination\",\"NIP\":\"National Intelligence Program\",\"NIPRNet\":\"Non-Secure Internet Protocol Router Network\",\"NISPOM\":\"National Industrial Security Program Operating Manual\",\"NIST\":\"National Institute of Standards and Technology\",\"NKCE\":\"Non-Kinetic Counter Electronics\",\"NLT\":\"No or Not Later Than\",\"NM\":\"Network Management\",\"NMC\":\"Not Mission Capable\",\"NMS\":\"National Military Strategy\",\"NNMSB\":\"Nonnuclear Munitions Safety Board\",\"NNSA\":\"National Nuclear Security Administration\",\"NOU\":\"No Operational Utility\",\"NPES\":\"Nuclear Planning and Execution System Modernization\",\"NR KPP\":\"Net-Ready Key Performance Parameter\",\"NRE\":\"Non-Recurring Engineering\",\"NRO\":\"National Reconnaissance Office\",\"NSA\":\"National Security Agency\",\"NSL\":\"Near Strike Lightning\",\"NSN\":\"National Stock Number\",\"NSPS\":\"National Security Personnel System\",\"NSS\":\"National Security Space OR National Security Strategy OR National Security System\",\"NTTR\":\"Nevada Test and Training Range\",\"NWC\":\"Nuclear Weapons Council\",\"NWRM\":\"Nuclear Weapons Related Materiel\",\"O&M\":\"Operation and Maintenance\",\"O&S\":\"Operation and Support\",\"OA\":\"Operational Assessment OR Operational Availability\",\"OAG\":\"Operational Advisory Group (USN/USMC)\",\"OAR\":\"Open-Air Range\",\"OARL\":\"Operating at Risk List\",\"OAS\":\"Office of Aerospace Studies\",\"OASD/NII\":\"Office Assistant Secretary of Defense/Network and Information Integration\",\"OASuW\":\"Offensive Anti-Surface Weapon\",\"OC\":\"Operational Capability\",\"OCA\":\"Original Classification Authority\",\"OCC\":\"Occupational Specialty Code\",\"OCDD\":\"Operational Capability Development Document\",\"OCE\":\"Operational Concept of Employment\",\"OCR\":\"Office of Collateral Responsibility OR Operational Capability Requirement\",\"OCX\":\"GPS Next Generation Operational Control System\",\"OE\":\"Operational Effectiveness OR Operational Environment\",\"OEM\":\"Original Equipment Manufacturer\",\"OER\":\"Operational Test Agency Evaluation Report\",\"OFP\":\"Operational Flight Program\",\"OFS\":\"Operational Flight Software\",\"OIPT\":\"Overarching Integrated Product Team\",\"OL\":\"Operating Location\",\"OMB\":\"Office of Management and Budget\",\"OML\":\"Outer Mold Line\",\"OMS\":\"Operational Mission Summary OR Operational Mode Summary\",\"OND\":\"Operational Need Date\",\"OPIR\":\"Overhead Persistent Infrared\",\"OPLAN\":\"Operations Plan\",\"OPORD\":\"Operations Order\",\"OPR\":\"Office of Primary Responsibility\",\"OPSEC\":\"Operations Security\",\"OPTEMPO\":\"Operational Tempo\",\"OPTEVFOR\":\"Operational Test and Evaluation Force\",\"ORD\":\"Operational Requirements Document\",\"ORM\":\"Operational Risk Management\",\"OS\":\"Operational Suitability\",\"OSD\":\"Office of the Secretary of Defense\",\"OSHA\":\"Occupational Safety and Health Administration\",\"OSS&E\":\"Operational Safety, Suitability, and Effectiveness\",\"OT\":\"Operational Test\",\"OT&E\":\"Operational Test and Evaluation\",\"OTA\":\"Operational Test Agency OR Other Transactions Authority\",\"OTAR\":\"Over-the-Air Re-key\",\"OTB\":\"Over Target Baseline\",\"OTC\":\"United States Army Operational Test Command\",\"OTD\":\"Open Technology Development\",\"OTI\":\"Operational Training Infrastructure\",\"OTIF\":\"Operational Test Information Files\",\"OTO\":\"Operational Test Organization\",\"OTRR\":\"Operational Test Readiness Review\",\"OTS\":\"Over Target Schedule\",\"OU\":\"Operational Utility\",\"OUA\":\"Operational Utility Assessment\",\"OUE\":\"Operational Utility Evaluation\",\"OUSD\":\"Office of the Under Secretary of Defense\",\"OV\":\"Operational View (or Viewpoint)\",\"OWLP\":\"Overseas Workload Program\",\"P&D\":\"Production and Deployment (phase)\",\"P3I\":\"Pre-Planned Product Improvement\",\"PA\":\"Partnering Arrangement OR Preparing Activity OR Preparing Authority OR Program Authorization ORPublic Affairs\",\"PAA\":\"Phased Adaptive Approach\",\"PAD\":\"Program Action Directive\",\"PAM\":\"Pamphlet OR Performance Attributes Matrix\",\"PAR\":\"Presidential Aircraft Recapitalization OR Proposal Analysis Report\",\"PAS\":\"Personnel Accounting Symbol\",\"PAT&E\":\"Production Acceptance Test and Evaluation\",\"PAUC\":\"Program Acquisition Unit Cost\",\"PB\":\"President’s Budget\",\"PBA\":\"Performance Based Acquisition OR Performance Based Agreement\",\"PBCM\":\"Portable Biological Containment Module\",\"PBL\":\"Performance Based Logistics\",\"PBR\":\"Program/Budget Review\",\"PC\":\"Product Center\",\"PCC\":\"Program Control Chief\",\"PCO\":\"Procuring Contracting Officer\",\"PD\":\"Program Director\",\"PDAQ\":\"Product Data Acquisition\",\"PDM\":\"Program Decision Memorandum OR Programmed Depot Maintenance\",\"PDR\":\"Preliminary Design Review\",\"PE\":\"Program Element\",\"PEM\":\"Program Element Monitor\",\"PEO\":\"Program Executive Office / Officer\",\"PESD\":\"Personnel Electrostatic Discharge\",\"PESHE\":\"Programmatic Environment, Safety, and Occupational Health Evaluation\",\"PG\":\"Product Group\",\"PGI\":\"Procedures, Guidance, and Information\",\"PGL\":\"Program Guidance Letter\",\"PGM\":\"Precision Guided Munitions OR Product Group Manager\",\"PHS&T\":\"Packaging, Handling, Storage, and Transportation\",\"PIA\":\"Privacy Impact Assessment\",\"PID\":\"Program Introduction Document\",\"PII\":\"Personally Identifiable Information\",\"PIR\":\"Post-Implementation Review\",\"PISR\":\"Persistent Intelligence, Surveillance, and Reconnaissance\",\"PIT\":\"Platform Information Technology\",\"PL\":\"Public Law\",\"PLI\":\"Position Location Information\",\"PLMS\":\"Product Lifecycle Management System\",\"PLR\":\"Position Location Recorder\",\"PM\":\"Program Manager\",\"PM/MFT\":\"Program Management or Multi-Functional Team\",\"PMA\":\"Program Management Agreement\",\"PMB\":\"Performance Measurement Baseline\",\"PMC\":\"Partially Mission Capable\",\"PMCS\":\"Preventive Maintenance Checks and Services\",\"PMD\":\"Program Management Directive\",\"PML\":\"Program Management Listing\",\"PMO\":\"Program Management Office\",\"PMRT\":\"Program Management Resource Tools\",\"PMT\":\"Program Manager‘s Tool\",\"PNVC\":\"Presidential and National Voice Conferencing\",\"PO\":\"Program Office OR Project Officer\",\"POA&M\":\"Plan of Action & Milestones\",\"POC\":\"Point of Contact\",\"POE\":\"Program Office Estimates\",\"POM\":\"Program Objective Memorandum\",\"POMx\":\"Point of Maintenance\",\"PoPS\":\"Probability of Program Success\",\"PoR\":\"Program of Record\",\"POS\":\"Pre-Operational Support\",\"POU\":\"Partial Operational Utility\",\"PPBE\":\"Planning, Programming, Budgeting, and Execution\",\"P-PLAN\":\"Programming Plan\",\"PPLANS\":\"Programming Plans\",\"PPP\":\"Program Protection Plan OR Public-Private Partnership\",\"PPQT\":\"Pre-Production Qualification Test\",\"PPR\":\"Post-Publication Review\",\"PQT\":\"Production Qualification Test\",\"PRA\":\"Performance Risk Assessment\",\"PRO\":\"Portable Rugged Objected\",\"PRR\":\"Production Readiness Review\",\"PS-BCA\":\"Product Support Business Case Analysis\",\"PSEAG\":\"Physical Security Equipment Action Group\",\"PSI\":\"Product Support Integrator\",\"PSIP\":\"Propulsion Systems Integrity Program\",\"PSM\":\"Product Support Manager\",\"PSMP\":\"Product Support Management Plan\",\"PSN\":\"Publication Stock Number\",\"PSP\":\"Product Support Provider\",\"PSpec\":\"Preliminary Specification\",\"PSR\":\"Program Support Review\",\"PTES\":\"Protected Tactical Enterprise Services\",\"PTO\":\"Participating Test Organization OR Preliminary Technical Order\",\"PTS\":\"Protected Tactical SATCOM\",\"PTSS\":\"Precision Tracking Space System\",\"PV\":\"Project Viewpoint\",\"PVI\":\"Pilot Vehicle Interface\",\"PWS\":\"Performance Work Statement\",\"QDR\":\"Quadrennial Defense Review\",\"QoS\":\"Quality of Service\",\"QOT&E\":\"Qualification Operational Test and Evaluation\",\"QRC\":\"Quick Reaction Capability\",\"QRF\":\"Quick Reaction Fund\",\"QRG\":\"Quick Reference Guide\",\"QRIP\":\"Quick Reaction Instrumentation Package\",\"QT&E\":\"Qualification Test and Evaluation\",\"R&D\":\"Research and Development\",\"R&M\":\"Reliability and Maintainability\",\"R/T\":\"Request for Test\",\"RAA\":\"Rapid Acquisition Authority OR Required Assets Available\",\"RADAR\":\"Radio Detection and Ranging\",\"RAI\":\"Recorded Aircraft Information\",\"RALOT\":\"Risk Assessment Level of Test\",\"RAM\":\"Reliability, Availability, and Maintainability\",\"RAM&C\":\"Reliability, Availability, Maintainability, and Cost\",\"RAMPOD\":\"Reliability, Availability, Maintainability for Pods and Integrated Systems\",\"RAMS\":\"Reliability, Availability, Maintainability, and Supportability\",\"RAPIDS\":\"Rapid Analysis Processing Instrumentation Deployment System\",\"RC\":\"Recommended Changes\",\"RCA\":\"Regulatory Contracting Approval\",\"RCM\":\"Reliability Centered Maintenance\",\"RCN\":\"Report Control Number\",\"RCT\":\"Requirements Correlation Table\",\"RD\":\"Restricted Data\",\"RDGT\":\"Reliability Development/Growth Test\",\"RDS\":\"Radiological Detection System OR Records Disposition Schedule\",\"RDT&E\":\"Research, Development, Test and Evaluation\",\"REMIS\":\"Reliability and Maintainability Information System\",\"REP\":\"Resource Enhancement Program\",\"RF\":\"Radio Frequency\",\"RFID\":\"Radio Frequency Identification\",\"RFP\":\"Request for Proposal\",\"RGC\":\"Reliability Growth Curve\",\"RI3\":\"Risk Identification: Integration & -Ilities\",\"RICS2\":\"Remote Reconfigurable Intelligent Instrumentation to Control, Collect, Simulate and Stimulate\",\"RIID\":\"Radioisotope Identification Detector\",\"RLA\":\"Rotary Launcher Assembly\",\"RM\":\"Reference Manual OR Risk Management\",\"RM&A\":\"Reliability, Maintainability and Availability\",\"RMCT\":\"Requirements Management Certification Training\",\"RMD\":\"Requirements Management Division\",\"RMF\":\"Risk Management Framework\",\"RMP\":\"Radar Modernization Program OR Risk Management Plan\",\"ROM\":\"Rough Order of Magnitude\",\"RPA\":\"Remotely Piloted Aircraft\",\"RPIE\":\"Real Property Installed Equipment\",\"RQ-4B Bk 30 MSI\":\"RQ-4B Block 30 Multi-Spectral Intelligence\",\"RR\":\"Rifleman Radio\",\"RRB\":\"Requirements Review Board\",\"RRF\":\"Rapid Reaction Fund\",\"RRP\":\"Rapid Response Process\",\"RS\":\"Radiated Susceptibility\",\"RSE\":\"Radar Signal Emulator\",\"RSR\":\"Requirements Strategy Review\",\"RTKN\":\"Real Time Kill Notification\",\"RTO\":\"Radio Telephone Operator OR Ready for Transition to Operations ORResponsible Test Organization (now obsolete) OR Range Training Officer\",\"R-TOC\":\"Reduction of Total Ownership Cost\",\"RTT\":\"Readiness to Test\",\"S&T\":\"Science and Technology\",\"S2E2\":\"Space Based Infrared Sys (SBIRS) Survivable and Endurable Evolution\",\"SA\":\"Security Assistance OR Situational Awareness OR System Administrator\",\"SAASM\":\"Selective Availability Anti-Spoofing Module\",\"SAE\":\"Service Acquisition Executive\",\"SAF\":\"Secretary of the Air Force\",\"SAF/AQ\":\"Assistant Secretary of the Air Force (Acquisition)\",\"SAF/AQX\":\"Deputy Assistant Secretary for Acquisition Integration\",\"SAF/CIO A6\":\"Chief of Warfighting Integration and Chief Information Officer (CIO)\",\"SAF/FM\":\"Assistant Secretary of the Air Force (Financial Management)\",\"SAF/FMC\":\"Deputy Assistant Secretary (DAS) of the Air Force for Cost and Economics\",\"SAF/GC\":\"General Counsel of the Air Force\",\"SAF/GCQ\":\"Deputy General Counsel (Acquisition)\",\"SAF/IE\":\"Assistant Secretary of the Air Force (Installations, Environment, and Logistics\",\"SAF/IG\":\"Inspector General of the Air Force\",\"SAF/LL\":\"Assistant Secretary of the Air Force (Legislative Affairs)\",\"SAF/US\":\"Under Secretary of the Air Force\",\"SAF/XC\":\"Secretary of the Air Force Directorate (Warfighting Integration and Chief Information Officer)\",\"SAM\":\"Support Agreement Manager\",\"SAMP\":\"Single Acquisition Management Plan\",\"SAO\":\"Security Assistance Organizations\",\"SAP\":\"Security Assessment Plan OR Security Assistance Program OR Special Access Program\",\"SAPCO\":\"Special Access Program Control Office\",\"SAR\":\"Security Assessment Report OR Special Access Required OR Synthetic Aperture Radar OR System Assessment Report\",\"SATAF\":\"Site Activation Task Force\",\"SATCOM\":\"Satellite Communications\",\"SATOP\":\"Security Assistance Technical Order Program\",\"SB\":\"Small Business\",\"SBIR\":\"Small Business Innovation Research\",\"SBIRS\":\"Space Based Infrared System\",\"SBIRS F/O\":\"Space Based Infrared System Follow-on\",\"SBRA\":\"Smart Bomb Rack Assembly\",\"SBSS F/O\":\"Space Based Space Surveillance Follow-On\",\"SCD\":\"System Capabilities Document\",\"SCG\":\"Security Classification Guide\",\"SCI\":\"Sensitive Compartmented Information\",\"SCM\":\"Supply Chain Manager\",\"SCO\":\"Senior Contracting Official\",\"SCP\":\"Service Cost Position\",\"SCRM\":\"Supply Chain Risk Management\",\"SCWDL\":\"Strike Common Weapon Data Link\",\"SD\":\"Standardization Document\",\"SDB\":\"Small Diameter Bomb\",\"SDD\":\"System Development and Demonstration\",\"SDO\":\"Services Designated Official\",\"SDR\":\"System Design Review\",\"SE\":\"Safety OR Support Equipment OR Systems Engineering\",\"SE/ATS\":\"Support Equipment/Automatic Test System\",\"SEAD\":\"Suppression of Enemy Air Defenses\",\"SEAM\":\"Systems Engineering Assessment Model\",\"SECAF\":\"Secretary of the Air Force\",\"SECDEF\":\"Secretary of Defense\",\"SEI\":\"Software Engineering Institute\",\"SENSR\":\"Spectrum Efficient National Surveillance Radar System\",\"SEP\":\"System Evaluation Plan OR Systems Engineering Plan\",\"SERD\":\"Support Equipment Recommendation Data\",\"SES\":\"Senior Executive Service\",\"SESAME\":\"Selected Essential Item Stockage for Availability Methodology\",\"SF\":\"Security Forces OR Standard Form\",\"SFF\":\"Small Form Fit\",\"SFR\":\"System Functional Review\",\"SIAO\":\"Senior Information Assurance Official\",\"SIGINT\":\"Signals Intelligence\",\"SII\":\"Special Interest Item\",\"SIM\":\"Serialized Item Management\",\"SIMAF\":\"Simulation and Analysis Facility\",\"SIMCERT\":\"Simulator Certification\",\"SIMVAL\":\"Simulator Validation\",\"SIO\":\"Senior Intelligence Officer\",\"SIOP-ESI\":\"Single Integrated Operational Plan-Extremely Sensitive Information\",\"SIP\":\"System Identification Profile OR System Information Profile\",\"SIPC\":\"Service Intelligence Production Centers\",\"SIPRNET\":\"Secret Internet Protocol Router Network\",\"SISSU\":\"Security, Interoperability, Supportability, Sustainability, and Usability\",\"SITREP\":\"Situational Report\",\"SLA\":\"Service Level Agreements\",\"SLAM-ER\":\"Standoff Land Attack Missile Expanded Response\",\"SLEP\":\"Service Life Extension Program\",\"SLIN\":\"Sub-Line Item Number\",\"SM\":\"Security Manager OR Service Manager OR Single Manager\",\"SMART\":\"Science, Mathematics, And Research For Transformation OR System Metrics and Reporting Tool\",\"SMC\":\"Space and Missile Systems Center\",\"SMCA\":\"Single Manager for Conventional Ammunition\",\"SME\":\"Subject Matter Expert\",\"SMI\":\"Soldier-Machine Interface\",\"SMM\":\"System Maturity Matrix\",\"SOC RPA\":\"Standardized Operations Center Remotely Piloted Aircraft\",\"SOC\":\"Statement of Capabilities\",\"SOCOM\":\"Special Operations Command\",\"SOF\":\"Special Operations Forces\",\"SOI\":\"Statement of Intent\",\"SOO\":\"Statement of Objectives\",\"SO-P\":\"Special Operations-Peculiar\",\"SOR\":\"Source of Repair\",\"SORA\":\"Source of Repair Assignment\",\"SORAP\":\"Source of Repair Assignment Process\",\"SORN\":\"System of Record Notice\",\"SoS\":\"Speed of Service OR System of Systems\",\"SOTR\":\"Sufficiency of Operational Test Review OR Sufficiency of Test Report\",\"SOW\":\"Special Operations Wing OR Statement of Work\",\"SP\":\"Security Plan OR Special Publication\",\"SPA\":\"Single Point Adjustment\",\"SPD\":\"System Program Director\",\"SPE\":\"Senior Procurement Executive\",\"SPG\":\"Strategic Planning Guidance\",\"SPM\":\"System Program Manager\",\"SPML\":\"Sustainment Program Master List\",\"SPO\":\"System Program Office\",\"SpOC\":\"Space Operations Command\",\"SPT\":\"Systems Planning Team\",\"SQL\":\"Structured Query Language\",\"SRA\":\"Schedule Risk Assessment\",\"SRB\":\"Safety Review Board\",\"SRD\":\"Software or Systems Requirements Document\",\"SRR\":\"System Requirements Review OR Systems Readiness Review\",\"SRW\":\"Soldier Radio Waveform\",\"SSA\":\"Source Selection Authority\",\"SSAA\":\"Systems Security Authorization Agreement\",\"SSAEM\":\"Space Situational Awareness-Environmental Monitoring\",\"SSD\":\"Source Selection Decision\",\"SSDD\":\"Source Selection Decision Document\",\"SSE\":\"Systems Security Engineering\",\"SSET\":\"Source Selection Evaluation Team\",\"SSM\":\"System Sustainment Manager\",\"SSN\":\"Social Security Number\",\"SSOM\":\"Standard Surveillance Operating Manual\",\"SSOR\":\"Strategic Source of Repair\",\"SSP\":\"Source Selection Plan OR System Support Package\",\"SSS\":\"Staff Summary Sheet\",\"SSWG\":\"Systems Security Working Group\",\"STA\":\"System Threat Analysis OR System Threat Assessment\",\"STAR\":\"System Threat Assessment Report\",\"STARCOM\":\"Space Training and Readiness Command\",\"STAT\":\"Scientific Test and Analysis Techniques\",\"StdV\":\"Standards Viewpoint\",\"STEP\":\"Standard for Exchange of Product\",\"STIG\":\"Security Technical Implementation Guide\",\"STINFO\":\"Scientific and Technical Information\",\"STP\":\"Space Test Program OR System Training Plan\",\"STR\":\"Sea Test Range\",\"STT\":\"Strategy-To-Task\",\"STTR\":\"Small Business Technology Transfer\",\"SUT\":\"System Under Test\",\"SV\":\"System View\",\"SVAD\":\"Survivability, Vulnerability, and Assessment Directorate\",\"SvcV\":\"Services Viewpoint\",\"SVR\":\"System Verification Review\",\"SwA\":\"Software Assurance\",\"SYSCOM\":\"Systems Command\",\"T&E ITT\":\"Test and Evaluation Integrated Test Team\",\"T&E\":\"Test and Evaluation\",\"TA\":\"Technical Advisor OR Test Area\",\"TAA\":\"Technical Airworthiness Authority\",\"TACO\":\"Test and Checkout\",\"TACP\":\"Tactical Air Control Party\",\"TACP-M\":\"Tactical Air Control Party-Modernization\",\"TASS\":\"Tactical Automated Security System\",\"TBD\":\"To Be Determined\",\"TCM-TR\":\"TRADOC Capabilities Manager-Tactical Radios\",\"TCRA\":\"test capability readiness assessment\",\"TCRAs\":\"test capability readiness assessments\",\"TCT\":\"Total Contract Training\",\"TCTO\":\"Time Compliance Technical Order\",\"TD\":\"Test Director OR Technical Director OR Technology Development OR Technology Director\",\"TD&E\":\"Tactics Development and Evaluation\",\"TDM\":\"Test Design Manager\",\"TDP\":\"Technical Data Package\",\"TDR\":\"Test Design Requirement\",\"TDS\":\"Technology Development Strategy\",\"TDSB\":\"Test Data Scoring Board\",\"TDY\":\"Temporary Duty\",\"TE\":\"Technical Editor OR Test Evaluation\",\"TEI\":\"Text Element Identifiers\",\"TEMP\":\"Test and Evaluation Master Plan\",\"TEMPEST\":\"Transient Electromagnetic Pulse Surveillance Technology\",\"TEO\":\"Technology Executive Officers\",\"TES\":\"Test and Evaluation Strategy\",\"TFI\":\"Total Force Integration\",\"TIPP\":\"Test Investment Planning and Programming\",\"TIPT\":\"Test Integrated Product Team\",\"TIR\":\"Test Incident Report\",\"TIS\":\"Test Information Sheet\",\"TISP\":\"Tailored Information Support Plan\",\"TKA\":\"Tail Kit Assembly\",\"TLDHS\":\"Target Location, Designation, and Hand-Off System\",\"TLE\":\"Target Location Error\",\"TM\":\"Technical Manual OR Telemetry OR Test Manager\",\"TMCR\":\"Technical Manual Contract Requirement\",\"TMDE\":\"Test Measurement Diagnostic Equipment\",\"TMIPJ\":\"Theater Medical Information Program-Joint\",\"TMLA\":\"Triple Missile Launcher Adapter\",\"TMRR\":\"Technology Maturation & Risk Reduction (phase)\",\"TMSS\":\"Technical Manual Specifications and Standards\",\"TMT\":\"Task Management Tool\",\"TNMCM\":\"Total Not Mission Capable-Maintenance\",\"TNMCS\":\"Total Not Mission Capable-Supply\",\"TO\":\"Tasking Order OR Technical Order\",\"TOA\":\"Total Obligation Authority\",\"TOAC\":\"Technical Order Advisory Council\",\"TOC\":\"Tactical Operation Center OR Total Ownership Cost OR Table of Contents\",\"TODO\":\"Technical Order Distribution Office\",\"TOMA\":\"Technical Order Management Agency\",\"TPCF\":\"Test Program Case File\",\"TPM\":\"Technical Performance Measure OR Test Program Management\",\"TPP\":\"Technology Protection Plan\",\"TPS\":\"Test Program Set\",\"TPT\":\"Training Planning Team\",\"TPWG\":\"Test Plan Working Group\",\"TR\":\"Technical Review\",\"TRA\":\"Technology Readiness Assessment\",\"TRADOC\":\"Training and Doctrine Command (US Army)\",\"TRB\":\"Technical Review Board\",\"TRD\":\"Technical Requirements Document\",\"TRL\":\"Technology Readiness Level\",\"TRM\":\"Technology Reference Model OR Test Resource Manager\",\"TRMC\":\"Test Resource Management Center\",\"TRP\":\"Test Resource Plan\",\"TRR\":\"Test Readiness Review\",\"TS\":\"Test Squadron OR Top Secret\",\"TSN\":\"Trusted Systems & Networks\",\"TSP\":\"Test Support Plan OR Transfer Support Plan OR Transition Support Plan\",\"TS-PGM\":\"Training System Product Group Manager\",\"TSPI\":\"Time / Space / Position Information\",\"TSRA\":\"Training System Requirements Analysis\",\"TSWG\":\"Threat Systems Working Group\",\"TTCP\":\"The Technology Cooperation Program\",\"TTP\":\"Tactics, Techniques, and Procedures OR Technology Transition Plan\",\"TV\":\"Technical View\",\"TW\":\"Test Wing\",\"UAI\":\"Universal Armament\",\"UAS\":\"Unmanned Aerial Systems\",\"UAV\":\"Unmanned Aerial Vehicle\",\"UC\":\"Unified Capabilities\",\"UCA\":\"Undefinitized Contract Action\",\"UCC\":\"Unified Combatant Commander\",\"UHF\":\"Ultra-High Frequency\",\"UID\":\"Unique Identification number\",\"UIF\":\"Unfavorable Information File\",\"UII\":\"Unique Item Identifier\",\"UIPE\":\"Uniform Integrated Protection Ensemble\",\"UJTL\":\"Universal Joint Task List\",\"ULB\":\"Underwater Locator Beacon\",\"ULO\":\"Unliquidated Obligation\",\"UON\":\"Urgent Operational Need\",\"UOTT\":\"US Operational Test Team\",\"UP\":\"Unified Platform\",\"URA\":\"User Representative Agency\",\"URL\":\"Uniform Resource Locator\",\"URN\":\"Unit Reference Number\",\"USAF\":\"United States Air Force\",\"USAFWC\":\"United States Air Force Warfare Center\",\"USB\":\"Universal Serial Bus\",\"USC\":\"United States Code\",\"USD\":\"Undersecretary of Defense\",\"USecAF\":\"Under Secretary of the Air Force\",\"USMC\":\"United States Marine Corps\",\"USSF\":\"United States Space Force\",\"USSOCOM\":\"U.S. Special Operations Command\",\"UTC\":\"Coordinated Universal Time\",\"UTTR\":\"Utah Test and Training Range\",\"V&V\":\"Verification and Validation\",\"VCJCS\":\"Vice Chairman of the Joint Chiefs of Staff\",\"VCSAF\":\"Vice Chief of Staff of the United States Air Force\",\"VCSO\":\"Vice Chief of Space Operations\",\"VE\":\"Value Engineering\",\"VECP\":\"Value Engineering Change Proposal\",\"VEP\":\"Value Engineering Proposal\",\"VHF\":\"Very High Frequency\",\"VIDOC\":\"Visual Information Documentation\",\"VIM\":\"Visual Information Manager\",\"VMC\":\"Visual Meteorological Conditions\",\"VML\":\"Vulnerable to Move List\",\"VMP\":\"Vulnerability Management Process\",\"VOLT\":\"Validated Online Lifecycle Threat\",\"VPV\":\"Virtual Prime Vendor\",\"VSP\":\"Verification Status Page\",\"VSTAR\":\"Virtual System Threat Assessment Report\",\"VTC\":\"Video Teleconference\",\"VV&A\":\"Verification, Validation and Accreditation\",\"WAS\":\"Wide Area Surveillance\",\"WAWF\":\"Wide Area Workflow\",\"WBS\":\"Work Breakdown Schedule\",\"WCF\":\"Working Capital Fund\",\"WIPT\":\"Working\\u001eLevel Integrated Product Team\",\"WIT\":\"Watch Item Tracking\",\"WMA\":\"Warfighting Mission Area\",\"WMD\":\"weapons of mass destruction\",\"WRAP\":\"Warfighter Rapid Acquisition Process\",\"WS3 SLEP\":\"Weapons Storage and Security System Service Life Extension Program\",\"WSEP\":\"Weapon System Evaluation Program\",\"WSER\":\"Weapon System Enterprise Reviews\",\"WSF-EO/IR\":\"Weather Satellite Follow-on Electro-Optical /Infra-Red\",\"WSF-M\":\"Weather Satellite Follow-on Microwave\",\"WSI\":\"Weapon System Integration OR Weapon System Integrity\",\"WSIG\":\"Weapon System Integrity Guide\",\"WSIP\":\"Weapon System Integrity Program\",\"WSMR\":\"White Sands Missile Range\",\"WSSP\":\"Weapons System Support Program\",\"WX\":\"Weather\",\"XDR\":\"Extended Data Rate\",\"YTD\":\"Year to Date\"}}}],\"extensions\":[\".mdx\",\".md\"],\"defaultLayouts\":{},\"lessBabel\":false,\"remarkPlugins\":[],\"rehypePlugins\":[],\"mediaTypes\":[\"text/markdown\",\"text/x-markdown\"],\"root\":\"/home/t42/Documents/programming/Projects/OT_Guide/IL-2 Guide\"},\n },{\n plugin: require('../node_modules/gatsby-plugin-gtag/gatsby-browser.js'),\n options: {\"plugins\":[],\"trackingId\":null,\"head\":true,\"anonymize\":false},\n },{\n plugin: require('../gatsby-browser.js'),\n options: {\"plugins\":[]},\n }]\n","module.exports = __webpack_public_path__ + \"static/logo-8619e329fe17a156b627acc1b8227098.svg\";","var unitlessKeys = {\n animationIterationCount: 1,\n borderImageOutset: 1,\n borderImageSlice: 1,\n borderImageWidth: 1,\n boxFlex: 1,\n boxFlexGroup: 1,\n boxOrdinalGroup: 1,\n columnCount: 1,\n columns: 1,\n flex: 1,\n flexGrow: 1,\n flexPositive: 1,\n flexShrink: 1,\n flexNegative: 1,\n flexOrder: 1,\n gridRow: 1,\n gridRowEnd: 1,\n gridRowSpan: 1,\n gridRowStart: 1,\n gridColumn: 1,\n gridColumnEnd: 1,\n gridColumnSpan: 1,\n gridColumnStart: 1,\n msGridRow: 1,\n msGridRowSpan: 1,\n msGridColumn: 1,\n msGridColumnSpan: 1,\n fontWeight: 1,\n lineHeight: 1,\n opacity: 1,\n order: 1,\n orphans: 1,\n tabSize: 1,\n widows: 1,\n zIndex: 1,\n zoom: 1,\n WebkitLineClamp: 1,\n // SVG-related properties\n fillOpacity: 1,\n floodOpacity: 1,\n stopOpacity: 1,\n strokeDasharray: 1,\n strokeDashoffset: 1,\n strokeMiterlimit: 1,\n strokeOpacity: 1,\n strokeWidth: 1\n};\nexport default unitlessKeys;","/*!\n * domready (c) Dustin Diaz 2014 - License MIT\n * ie10 fix - Mikael Kristiansson 2019\n */\n!(function(name, definition) {\n if (typeof module != \"undefined\") module.exports = definition();\n else if (typeof define == \"function\" && typeof define.amd == \"object\")\n define(definition);\n else this[name] = definition();\n})(\"domready\", function() {\n var ie10 = false;\n if (navigator.appVersion.indexOf(\"MSIE 10\") !== -1) {\n ie10 = true;\n }\n\n var fns = [],\n listener,\n doc = typeof document === \"object\" && document,\n hack = ie10\n ? doc.documentElement.doScroll(\"left\")\n : doc.documentElement.doScroll,\n domContentLoaded = \"DOMContentLoaded\",\n loaded =\n doc && (hack ? /^loaded|^c/ : /^loaded|^i|^c/).test(doc.readyState);\n\n if (!loaded && doc)\n doc.addEventListener(\n domContentLoaded,\n (listener = function() {\n doc.removeEventListener(domContentLoaded, listener);\n loaded = 1;\n while ((listener = fns.shift())) listener();\n })\n );\n\n return function(fn) {\n loaded ? setTimeout(fn, 0) : fns.push(fn);\n };\n});\n","/* eslint-disable */\n// Inspired by https://github.com/garycourt/murmurhash-js\n// Ported from https://github.com/aappleby/smhasher/blob/61a0530f28277f2e850bfc39600ce61d02b518de/src/MurmurHash2.cpp#L37-L86\nfunction murmur2(str) {\n // 'm' and 'r' are mixing constants generated offline.\n // They're not really 'magic', they just happen to work well.\n // const m = 0x5bd1e995;\n // const r = 24;\n // Initialize the hash\n var h = 0; // Mix 4 bytes at a time into the hash\n\n var k,\n i = 0,\n len = str.length;\n\n for (; len >= 4; ++i, len -= 4) {\n k = str.charCodeAt(i) & 0xff | (str.charCodeAt(++i) & 0xff) << 8 | (str.charCodeAt(++i) & 0xff) << 16 | (str.charCodeAt(++i) & 0xff) << 24;\n k =\n /* Math.imul(k, m): */\n (k & 0xffff) * 0x5bd1e995 + ((k >>> 16) * 0xe995 << 16);\n k ^=\n /* k >>> r: */\n k >>> 24;\n h =\n /* Math.imul(k, m): */\n (k & 0xffff) * 0x5bd1e995 + ((k >>> 16) * 0xe995 << 16) ^\n /* Math.imul(h, m): */\n (h & 0xffff) * 0x5bd1e995 + ((h >>> 16) * 0xe995 << 16);\n } // Handle the last few bytes of the input array\n\n\n switch (len) {\n case 3:\n h ^= (str.charCodeAt(i + 2) & 0xff) << 16;\n\n case 2:\n h ^= (str.charCodeAt(i + 1) & 0xff) << 8;\n\n case 1:\n h ^= str.charCodeAt(i) & 0xff;\n h =\n /* Math.imul(h, m): */\n (h & 0xffff) * 0x5bd1e995 + ((h >>> 16) * 0xe995 << 16);\n } // Do a few final mixes of the hash to ensure the last few\n // bytes are well-incorporated.\n\n\n h ^= h >>> 13;\n h =\n /* Math.imul(h, m): */\n (h & 0xffff) * 0x5bd1e995 + ((h >>> 16) * 0xe995 << 16);\n return ((h ^ h >>> 15) >>> 0).toString(36);\n}\n\nexport default murmur2;","import hashString from '@emotion/hash';\nimport unitless from '@emotion/unitless';\nimport memoize from '@emotion/memoize';\nvar ILLEGAL_ESCAPE_SEQUENCE_ERROR = \"You have illegal escape sequence in your template literal, most likely inside content's property value.\\nBecause you write your CSS inside a JavaScript string you actually have to do double escaping, so for example \\\"content: '\\\\00d7';\\\" should become \\\"content: '\\\\\\\\00d7';\\\".\\nYou can read more about this here:\\nhttps://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals#ES2018_revision_of_illegal_escape_sequences\";\nvar UNDEFINED_AS_OBJECT_KEY_ERROR = \"You have passed in falsy value as style object's key (can happen when in example you pass unexported component as computed key).\";\nvar hyphenateRegex = /[A-Z]|^ms/g;\nvar animationRegex = /_EMO_([^_]+?)_([^]*?)_EMO_/g;\n\nvar isCustomProperty = function isCustomProperty(property) {\n return property.charCodeAt(1) === 45;\n};\n\nvar isProcessableValue = function isProcessableValue(value) {\n return value != null && typeof value !== 'boolean';\n};\n\nvar processStyleName = memoize(function (styleName) {\n return isCustomProperty(styleName) ? styleName : styleName.replace(hyphenateRegex, '-$&').toLowerCase();\n});\n\nvar processStyleValue = function processStyleValue(key, value) {\n switch (key) {\n case 'animation':\n case 'animationName':\n {\n if (typeof value === 'string') {\n return value.replace(animationRegex, function (match, p1, p2) {\n cursor = {\n name: p1,\n styles: p2,\n next: cursor\n };\n return p1;\n });\n }\n }\n }\n\n if (unitless[key] !== 1 && !isCustomProperty(key) && typeof value === 'number' && value !== 0) {\n return value + 'px';\n }\n\n return value;\n};\n\nif (process.env.NODE_ENV !== 'production') {\n var contentValuePattern = /(attr|calc|counters?|url)\\(/;\n var contentValues = ['normal', 'none', 'counter', 'open-quote', 'close-quote', 'no-open-quote', 'no-close-quote', 'initial', 'inherit', 'unset'];\n var oldProcessStyleValue = processStyleValue;\n var msPattern = /^-ms-/;\n var hyphenPattern = /-(.)/g;\n var hyphenatedCache = {};\n\n processStyleValue = function processStyleValue(key, value) {\n if (key === 'content') {\n if (typeof value !== 'string' || contentValues.indexOf(value) === -1 && !contentValuePattern.test(value) && (value.charAt(0) !== value.charAt(value.length - 1) || value.charAt(0) !== '\"' && value.charAt(0) !== \"'\")) {\n console.error(\"You seem to be using a value for 'content' without quotes, try replacing it with `content: '\\\"\" + value + \"\\\"'`\");\n }\n }\n\n var processed = oldProcessStyleValue(key, value);\n\n if (processed !== '' && !isCustomProperty(key) && key.indexOf('-') !== -1 && hyphenatedCache[key] === undefined) {\n hyphenatedCache[key] = true;\n console.error(\"Using kebab-case for css properties in objects is not supported. Did you mean \" + key.replace(msPattern, 'ms-').replace(hyphenPattern, function (str, _char) {\n return _char.toUpperCase();\n }) + \"?\");\n }\n\n return processed;\n };\n}\n\nvar shouldWarnAboutInterpolatingClassNameFromCss = true;\n\nfunction handleInterpolation(mergedProps, registered, interpolation, couldBeSelectorInterpolation) {\n if (interpolation == null) {\n return '';\n }\n\n if (interpolation.__emotion_styles !== undefined) {\n if (process.env.NODE_ENV !== 'production' && interpolation.toString() === 'NO_COMPONENT_SELECTOR') {\n throw new Error('Component selectors can only be used in conjunction with babel-plugin-emotion.');\n }\n\n return interpolation;\n }\n\n switch (typeof interpolation) {\n case 'boolean':\n {\n return '';\n }\n\n case 'object':\n {\n if (interpolation.anim === 1) {\n cursor = {\n name: interpolation.name,\n styles: interpolation.styles,\n next: cursor\n };\n return interpolation.name;\n }\n\n if (interpolation.styles !== undefined) {\n var next = interpolation.next;\n\n if (next !== undefined) {\n // not the most efficient thing ever but this is a pretty rare case\n // and there will be very few iterations of this generally\n while (next !== undefined) {\n cursor = {\n name: next.name,\n styles: next.styles,\n next: cursor\n };\n next = next.next;\n }\n }\n\n var styles = interpolation.styles + \";\";\n\n if (process.env.NODE_ENV !== 'production' && interpolation.map !== undefined) {\n styles += interpolation.map;\n }\n\n return styles;\n }\n\n return createStringFromObject(mergedProps, registered, interpolation);\n }\n\n case 'function':\n {\n if (mergedProps !== undefined) {\n var previousCursor = cursor;\n var result = interpolation(mergedProps);\n cursor = previousCursor;\n return handleInterpolation(mergedProps, registered, result, couldBeSelectorInterpolation);\n } else if (process.env.NODE_ENV !== 'production') {\n console.error('Functions that are interpolated in css calls will be stringified.\\n' + 'If you want to have a css call based on props, create a function that returns a css call like this\\n' + 'let dynamicStyle = (props) => css`color: ${props.color}`\\n' + 'It can be called directly with props or interpolated in a styled call like this\\n' + \"let SomeComponent = styled('div')`${dynamicStyle}`\");\n }\n\n break;\n }\n\n case 'string':\n if (process.env.NODE_ENV !== 'production') {\n var matched = [];\n var replaced = interpolation.replace(animationRegex, function (match, p1, p2) {\n var fakeVarName = \"animation\" + matched.length;\n matched.push(\"const \" + fakeVarName + \" = keyframes`\" + p2.replace(/^@keyframes animation-\\w+/, '') + \"`\");\n return \"${\" + fakeVarName + \"}\";\n });\n\n if (matched.length) {\n console.error('`keyframes` output got interpolated into plain string, please wrap it with `css`.\\n\\n' + 'Instead of doing this:\\n\\n' + [].concat(matched, [\"`\" + replaced + \"`\"]).join('\\n') + '\\n\\nYou should wrap it with `css` like this:\\n\\n' + (\"css`\" + replaced + \"`\"));\n }\n }\n\n break;\n } // finalize string values (regular strings and functions interpolated into css calls)\n\n\n if (registered == null) {\n return interpolation;\n }\n\n var cached = registered[interpolation];\n\n if (process.env.NODE_ENV !== 'production' && couldBeSelectorInterpolation && shouldWarnAboutInterpolatingClassNameFromCss && cached !== undefined) {\n console.error('Interpolating a className from css`` is not recommended and will cause problems with composition.\\n' + 'Interpolating a className from css`` will be completely unsupported in a future major version of Emotion');\n shouldWarnAboutInterpolatingClassNameFromCss = false;\n }\n\n return cached !== undefined && !couldBeSelectorInterpolation ? cached : interpolation;\n}\n\nfunction createStringFromObject(mergedProps, registered, obj) {\n var string = '';\n\n if (Array.isArray(obj)) {\n for (var i = 0; i < obj.length; i++) {\n string += handleInterpolation(mergedProps, registered, obj[i], false);\n }\n } else {\n for (var _key in obj) {\n var value = obj[_key];\n\n if (typeof value !== 'object') {\n if (registered != null && registered[value] !== undefined) {\n string += _key + \"{\" + registered[value] + \"}\";\n } else if (isProcessableValue(value)) {\n string += processStyleName(_key) + \":\" + processStyleValue(_key, value) + \";\";\n }\n } else {\n if (_key === 'NO_COMPONENT_SELECTOR' && process.env.NODE_ENV !== 'production') {\n throw new Error('Component selectors can only be used in conjunction with babel-plugin-emotion.');\n }\n\n if (Array.isArray(value) && typeof value[0] === 'string' && (registered == null || registered[value[0]] === undefined)) {\n for (var _i = 0; _i < value.length; _i++) {\n if (isProcessableValue(value[_i])) {\n string += processStyleName(_key) + \":\" + processStyleValue(_key, value[_i]) + \";\";\n }\n }\n } else {\n var interpolated = handleInterpolation(mergedProps, registered, value, false);\n\n switch (_key) {\n case 'animation':\n case 'animationName':\n {\n string += processStyleName(_key) + \":\" + interpolated + \";\";\n break;\n }\n\n default:\n {\n if (process.env.NODE_ENV !== 'production' && _key === 'undefined') {\n console.error(UNDEFINED_AS_OBJECT_KEY_ERROR);\n }\n\n string += _key + \"{\" + interpolated + \"}\";\n }\n }\n }\n }\n }\n }\n\n return string;\n}\n\nvar labelPattern = /label:\\s*([^\\s;\\n{]+)\\s*;/g;\nvar sourceMapPattern;\n\nif (process.env.NODE_ENV !== 'production') {\n sourceMapPattern = /\\/\\*#\\ssourceMappingURL=data:application\\/json;\\S+\\s+\\*\\//;\n} // this is the cursor for keyframes\n// keyframes are stored on the SerializedStyles object as a linked list\n\n\nvar cursor;\n\nvar serializeStyles = function serializeStyles(args, registered, mergedProps) {\n if (args.length === 1 && typeof args[0] === 'object' && args[0] !== null && args[0].styles !== undefined) {\n return args[0];\n }\n\n var stringMode = true;\n var styles = '';\n cursor = undefined;\n var strings = args[0];\n\n if (strings == null || strings.raw === undefined) {\n stringMode = false;\n styles += handleInterpolation(mergedProps, registered, strings, false);\n } else {\n if (process.env.NODE_ENV !== 'production' && strings[0] === undefined) {\n console.error(ILLEGAL_ESCAPE_SEQUENCE_ERROR);\n }\n\n styles += strings[0];\n } // we start at 1 since we've already handled the first arg\n\n\n for (var i = 1; i < args.length; i++) {\n styles += handleInterpolation(mergedProps, registered, args[i], styles.charCodeAt(styles.length - 1) === 46);\n\n if (stringMode) {\n if (process.env.NODE_ENV !== 'production' && strings[i] === undefined) {\n console.error(ILLEGAL_ESCAPE_SEQUENCE_ERROR);\n }\n\n styles += strings[i];\n }\n }\n\n var sourceMap;\n\n if (process.env.NODE_ENV !== 'production') {\n styles = styles.replace(sourceMapPattern, function (match) {\n sourceMap = match;\n return '';\n });\n } // using a global regex with .exec is stateful so lastIndex has to be reset each time\n\n\n labelPattern.lastIndex = 0;\n var identifierName = '';\n var match; // https://esbench.com/bench/5b809c2cf2949800a0f61fb5\n\n while ((match = labelPattern.exec(styles)) !== null) {\n identifierName += '-' + // $FlowFixMe we know it's not null\n match[1];\n }\n\n var name = hashString(styles) + identifierName;\n\n if (process.env.NODE_ENV !== 'production') {\n // $FlowFixMe SerializedStyles type doesn't have toString property (and we don't want to add it)\n return {\n name: name,\n styles: styles,\n map: sourceMap,\n next: cursor,\n toString: function toString() {\n return \"You have tried to stringify object returned from `css` function. It isn't supposed to be used directly (e.g. as value of the `className` prop), but rather handed to emotion so it can handle it (e.g. as value of `css` prop).\";\n }\n };\n }\n\n return {\n name: name,\n styles: styles,\n next: cursor\n };\n};\n\nexport { serializeStyles };","import { apiRunner } from \"./api-runner-browser\"\n\nif (\n window.location.protocol !== `https:` &&\n window.location.hostname !== `localhost`\n) {\n console.error(\n `Service workers can only be used over HTTPS, or on localhost for development`\n )\n} else if (`serviceWorker` in navigator) {\n navigator.serviceWorker\n .register(`${__BASE_PATH__}/sw.js`)\n .then(function (reg) {\n reg.addEventListener(`updatefound`, () => {\n apiRunner(`onServiceWorkerUpdateFound`, { serviceWorker: reg })\n // The updatefound event implies that reg.installing is set; see\n // https://w3c.github.io/ServiceWorker/#service-worker-registration-updatefound-event\n const installingWorker = reg.installing\n console.log(`installingWorker`, installingWorker)\n installingWorker.addEventListener(`statechange`, () => {\n switch (installingWorker.state) {\n case `installed`:\n if (navigator.serviceWorker.controller) {\n // At this point, the old content will have been purged and the fresh content will\n // have been added to the cache.\n\n // We set a flag so Gatsby Link knows to refresh the page on next navigation attempt\n window.___swUpdated = true\n // We call the onServiceWorkerUpdateReady API so users can show update prompts.\n apiRunner(`onServiceWorkerUpdateReady`, { serviceWorker: reg })\n\n // If resources failed for the current page, reload.\n if (window.___failedResources) {\n console.log(`resources failed, SW updated - reloading`)\n window.location.reload()\n }\n } else {\n // At this point, everything has been precached.\n // It's the perfect time to display a \"Content is cached for offline use.\" message.\n console.log(`Content is now available offline!`)\n\n // Post to service worker that install is complete.\n // Delay to allow time for the event listener to be added --\n // otherwise fetch is called too soon and resources aren't cached.\n apiRunner(`onServiceWorkerInstalled`, { serviceWorker: reg })\n }\n break\n\n case `redundant`:\n console.error(`The installing service worker became redundant.`)\n apiRunner(`onServiceWorkerRedundant`, { serviceWorker: reg })\n break\n\n case `activated`:\n apiRunner(`onServiceWorkerActive`, { serviceWorker: reg })\n break\n }\n })\n })\n })\n .catch(function (e) {\n console.error(`Error during service worker registration:`, e)\n })\n}\n","// prefer default export if available\nconst preferDefault = m => (m && m.default) || m\n\nexports.components = {\n \"component---src-pages-404-js\": () => import(\"./../../../src/pages/404.js\" /* webpackChunkName: \"component---src-pages-404-js\" */),\n \"component---src-templates-docs-js\": () => import(\"./../../../src/templates/docs.js\" /* webpackChunkName: \"component---src-templates-docs-js\" */)\n}\n\n","function _assertThisInitialized(self) {\n if (self === void 0) {\n throw new ReferenceError(\"this hasn't been initialised - super() hasn't been called\");\n }\n\n return self;\n}\n\nmodule.exports = _assertThisInitialized;\nmodule.exports[\"default\"] = module.exports, module.exports.__esModule = true;","'use strict';\n\nmodule.exports = function (url) {\n if (typeof url !== 'string') {\n throw new TypeError(\"Expected a `string`, got `\".concat(typeof url, \"`\"));\n } // Don't match Windows paths `c:\\`\n\n\n if (/^[a-zA-Z]:\\\\/.test(url)) {\n return false;\n } // Scheme: https://tools.ietf.org/html/rfc3986#section-3.1\n // Absolute URL: https://tools.ietf.org/html/rfc3986#section-4.3\n\n\n return /^[a-zA-Z][a-zA-Z\\d+\\-.]*:/.test(url);\n};","var arrayWithoutHoles = require(\"./arrayWithoutHoles.js\");\n\nvar iterableToArray = require(\"./iterableToArray.js\");\n\nvar unsupportedIterableToArray = require(\"./unsupportedIterableToArray.js\");\n\nvar nonIterableSpread = require(\"./nonIterableSpread.js\");\n\nfunction _toConsumableArray(arr) {\n return arrayWithoutHoles(arr) || iterableToArray(arr) || unsupportedIterableToArray(arr) || nonIterableSpread();\n}\n\nmodule.exports = _toConsumableArray;\nmodule.exports[\"default\"] = module.exports, module.exports.__esModule = true;","// Converted automatically using ./tools/themeFromVsCode\nvar theme = {\n plain: {\n color: \"#9CDCFE\",\n backgroundColor: \"#1E1E1E\"\n },\n styles: [{\n types: [\"prolog\"],\n style: {\n color: \"rgb(0, 0, 128)\"\n }\n }, {\n types: [\"comment\"],\n style: {\n color: \"rgb(106, 153, 85)\"\n }\n }, {\n types: [\"builtin\", \"changed\", \"keyword\"],\n style: {\n color: \"rgb(86, 156, 214)\"\n }\n }, {\n types: [\"number\", \"inserted\"],\n style: {\n color: \"rgb(181, 206, 168)\"\n }\n }, {\n types: [\"constant\"],\n style: {\n color: \"rgb(100, 102, 149)\"\n }\n }, {\n types: [\"attr-name\", \"variable\"],\n style: {\n color: \"rgb(156, 220, 254)\"\n }\n }, {\n types: [\"deleted\", \"string\", \"attr-value\"],\n style: {\n color: \"rgb(206, 145, 120)\"\n }\n }, {\n types: [\"selector\"],\n style: {\n color: \"rgb(215, 186, 125)\"\n }\n }, {\n // Fix tag color\n types: [\"tag\"],\n style: {\n color: \"rgb(78, 201, 176)\"\n }\n }, {\n // Fix tag color for HTML\n types: [\"tag\"],\n languages: [\"markup\"],\n style: {\n color: \"rgb(86, 156, 214)\"\n }\n }, {\n types: [\"punctuation\", \"operator\"],\n style: {\n color: \"rgb(212, 212, 212)\"\n }\n }, {\n // Fix punctuation color for HTML\n types: [\"punctuation\"],\n languages: [\"markup\"],\n style: {\n color: \"#808080\"\n }\n }, {\n types: [\"function\"],\n style: {\n color: \"rgb(220, 220, 170)\"\n }\n }, {\n types: [\"class-name\"],\n style: {\n color: \"rgb(78, 201, 176)\"\n }\n }, {\n types: [\"char\"],\n style: {\n color: \"rgb(209, 105, 105)\"\n }\n }]\n};\nexport default theme;","import * as React from 'react';\n\nconst LoadingProvider = ({ ...props }) => {\n return
;\n};\n\nexport default LoadingProvider;\n","import * as React from 'react';\nimport Highlight, { defaultProps } from 'prism-react-renderer';\nimport prismTheme from 'prism-react-renderer/themes/vsDark';\nimport Loadable from 'react-loadable';\nimport LoadingProvider from './loading';\n\n/** Removes the last token from a code example if it's empty. */\nfunction cleanTokens(tokens) {\n const tokensLength = tokens.length;\n\n if (tokensLength === 0) {\n return tokens;\n }\n const lastToken = tokens[tokensLength - 1];\n\n if (lastToken.length === 1 && lastToken[0].empty) {\n return tokens.slice(0, tokensLength - 1);\n }\n return tokens;\n}\n\nconst LoadableComponent = Loadable({\n loader: () => import('./LiveProvider'),\n loading: LoadingProvider,\n});\n\n/* eslint-disable react/jsx-key */\nconst CodeBlock = ({ children: exampleCode, ...props }) => {\n if (props['react-live']) {\n return ;\n } else {\n return (\n \n {({ className, style, tokens, getLineProps, getTokenProps }) => (\n
\n            {cleanTokens(tokens).map((line, i) => {\n              let lineClass = {};\n\n              let isDiff = false;\n\n              if (line[0] && line[0].content.length && line[0].content[0] === '+') {\n                lineClass = { backgroundColor: 'rgba(76, 175, 80, 0.2)' };\n                isDiff = true;\n              } else if (line[0] && line[0].content.length && line[0].content[0] === '-') {\n                lineClass = { backgroundColor: 'rgba(244, 67, 54, 0.2)' };\n                isDiff = true;\n              } else if (line[0] && line[0].content === '' && line[1] && line[1].content === '+') {\n                lineClass = { backgroundColor: 'rgba(76, 175, 80, 0.2)' };\n                isDiff = true;\n              } else if (line[0] && line[0].content === '' && line[1] && line[1].content === '-') {\n                lineClass = { backgroundColor: 'rgba(244, 67, 54, 0.2)' };\n                isDiff = true;\n              }\n              const lineProps = getLineProps({ line, key: i });\n\n              lineProps.style = lineClass;\n              const diffStyle = {\n                userSelect: 'none',\n                MozUserSelect: '-moz-none',\n                WebkitUserSelect: 'none',\n              };\n\n              let splitToken;\n\n              return (\n                
\n {line.map((token, key) => {\n if (isDiff) {\n if (\n (key === 0 || key === 1) &\n (token.content.charAt(0) === '+' || token.content.charAt(0) === '-')\n ) {\n if (token.content.length > 1) {\n splitToken = {\n types: ['template-string', 'string'],\n content: token.content.slice(1),\n };\n const firstChar = {\n types: ['operator'],\n content: token.content.charAt(0),\n };\n\n return (\n \n \n \n \n );\n } else {\n return ;\n }\n }\n }\n return ;\n })}\n
\n );\n })}\n
\n )}\n
\n );\n }\n};\n\nexport default CodeBlock;\n","import * as React from 'react';\n\nconst AnchorTag = ({ children: link, ...props }) => {\n if (link) {\n return (\n \n {link}\n \n );\n } else {\n return null;\n }\n};\n\nexport default AnchorTag;\n","import React from 'react';\nimport styled from '@emotion/styled';\n\nimport CodeBlock from './codeBlock';\nimport AnchorTag from './anchor';\n\nconst StyledPre = styled('pre')`\n padding: 16px;\n background: ${props => props.theme.colors.preFormattedText};\n`;\n\nexport default {\n h1: props => (\n

\n ),\n p: props =>

,\n pre: props => (\n \n

\n    \n  ),\n  code: CodeBlock,\n  a: AnchorTag,\n  // TODO add `img`\n  // TODO add `blockquote`\n  // TODO add `ul`\n  // TODO add `li`\n  // TODO add `table`\n};\n\n\n/*\n\n  h2: props => (\n    

\n ),\n h3: props => (\n

\n ),\n h4: props => (\n

\n ),\n h5: props => (\n

\n ),\n h6: props => (\n
\n ),\n */","import _defineProperty from '@babel/runtime/helpers/defineProperty';\nimport React__default, { createElement, forwardRef } from 'react';\nimport { ThemeContext } from '@emotion/core';\nimport weakMemoize from '@emotion/weak-memoize';\nimport _extends from '@babel/runtime/helpers/extends';\nimport hoistNonReactStatics from 'hoist-non-react-statics';\n\nfunction ownKeys(object, enumerableOnly) {\n var keys = Object.keys(object);\n\n if (Object.getOwnPropertySymbols) {\n var symbols = Object.getOwnPropertySymbols(object);\n if (enumerableOnly) symbols = symbols.filter(function (sym) {\n return Object.getOwnPropertyDescriptor(object, sym).enumerable;\n });\n keys.push.apply(keys, symbols);\n }\n\n return keys;\n}\n\nfunction _objectSpread(target) {\n for (var i = 1; i < arguments.length; i++) {\n var source = arguments[i] != null ? arguments[i] : {};\n\n if (i % 2) {\n ownKeys(source, true).forEach(function (key) {\n _defineProperty(target, key, source[key]);\n });\n } else if (Object.getOwnPropertyDescriptors) {\n Object.defineProperties(target, Object.getOwnPropertyDescriptors(source));\n } else {\n ownKeys(source).forEach(function (key) {\n Object.defineProperty(target, key, Object.getOwnPropertyDescriptor(source, key));\n });\n }\n }\n\n return target;\n}\n\nvar getTheme = function getTheme(outerTheme, theme) {\n if (typeof theme === 'function') {\n var mergedTheme = theme(outerTheme);\n\n if (process.env.NODE_ENV !== 'production' && (mergedTheme == null || typeof mergedTheme !== 'object' || Array.isArray(mergedTheme))) {\n throw new Error('[ThemeProvider] Please return an object from your theme function, i.e. theme={() => ({})}!');\n }\n\n return mergedTheme;\n }\n\n if (process.env.NODE_ENV !== 'production' && (theme == null || typeof theme !== 'object' || Array.isArray(theme))) {\n throw new Error('[ThemeProvider] Please make your theme prop a plain object');\n }\n\n return _objectSpread({}, outerTheme, {}, theme);\n};\n\nvar createCacheWithTheme = weakMemoize(function (outerTheme) {\n return weakMemoize(function (theme) {\n return getTheme(outerTheme, theme);\n });\n});\n\nvar ThemeProvider = function ThemeProvider(props) {\n return createElement(ThemeContext.Consumer, null, function (theme) {\n if (props.theme !== theme) {\n theme = createCacheWithTheme(theme)(props.theme);\n }\n\n return createElement(ThemeContext.Provider, {\n value: theme\n }, props.children);\n });\n}; // should we change this to be forwardRef/withCSSContext style so it doesn't merge with props?\n\n\nfunction withTheme(Component) {\n var componentName = Component.displayName || Component.name || 'Component';\n\n var render = function render(props, ref) {\n return createElement(ThemeContext.Consumer, null, function (theme) {\n return createElement(Component, _extends({\n theme: theme,\n ref: ref\n }, props));\n });\n }; // $FlowFixMe\n\n\n var WithTheme = forwardRef(render);\n WithTheme.displayName = \"WithTheme(\" + componentName + \")\";\n return hoistNonReactStatics(WithTheme, Component);\n}\n\nfunction useTheme() {\n return React__default.useContext(ThemeContext);\n}\n\nexport { ThemeProvider, useTheme, withTheme };","const baseTheme = {\n fonts: {\n mono: '\"SF Mono\", \"Roboto Mono\", Menlo, monospace',\n },\n};\n\nconst lightTheme = {\n ...baseTheme,\n colors: {\n background: '#fff',\n heading: '#000',\n text: '#3B454E',\n preFormattedText: 'rgb(245, 247, 249)',\n link: '#1000EE',\n },\n};\n\nconst darkTheme = {\n ...baseTheme,\n colors: {\n background: '#001933',\n heading: '#fff',\n text: '#fff',\n preFormattedText: '#000',\n link: '#2dc4f3',\n },\n};\n\nexport { lightTheme, darkTheme };\n","import React from 'react';\nimport { Link as GatsbyLink } from 'gatsby';\nimport isAbsoluteUrl from 'is-absolute-url';\n\nconst Link = ({ to, ...props }) =>\n isAbsoluteUrl(to) ? (\n \n {props.children}\n \n ) : (\n \n );\n\nexport default Link;\n","import React from 'react';\nimport styled from '@emotion/styled';\n\nimport NightImage from './images/night.png';\nimport DayImage from './images/day.png';\n\nconst StyledSwitch = styled('div')`\n display: flex;\n justify-content: flex-end;\n width: 100%;\n padding: 0 20px 0 25px;\n\n /* The switch - the box around the slider */\n .switch {\n position: relative;\n display: inline-block;\n width: 50px;\n height: 20px;\n }\n\n /* Hide default HTML checkbox */\n .switch input {\n opacity: 0;\n width: 0;\n height: 0;\n }\n\n /* The slider */\n .slider {\n position: absolute;\n cursor: pointer;\n top: 0;\n left: 0;\n right: 0;\n bottom: 0;\n background-color: #ccc;\n -webkit-transition: 0.4s;\n transition: 0.4s;\n }\n\n .slider:before {\n position: absolute;\n content: '';\n height: 30px;\n width: 30px;\n left: 0px;\n bottom: 4px;\n top: 0;\n bottom: 0;\n margin: auto 0;\n -webkit-transition: 0.4s;\n transition: 0.4s;\n box-shadow: 0 0px 15px #2020203d;\n background: white url(${NightImage});\n background-repeat: no-repeat;\n background-position: center;\n }\n\n input:checked + .slider {\n background: linear-gradient(to right, #fefb72, #f0bb31);\n }\n\n input:checked + .slider:before {\n -webkit-transform: translateX(24px);\n -ms-transform: translateX(24px);\n transform: translateX(24px);\n background: white url(${DayImage});\n background-repeat: no-repeat;\n background-position: center;\n }\n\n /* Rounded sliders */\n .slider.round {\n border-radius: 34px;\n }\n\n .slider.round:before {\n border-radius: 50%;\n }\n`;\n\nexport const DarkModeSwitch = ({ isDarkThemeActive, toggleActiveTheme }) => (\n \n \n \n);\n","import React from 'react';\n\nconst OpenedSvg = () => (\n \n \n \n);\n\nexport default OpenedSvg;\n","import React from 'react';\n\nconst ClosedSvg = () => (\n \n \n \n);\n\nexport default ClosedSvg;\n","import React from 'react';\nimport OpenedSvg from '../images/opened';\nimport ClosedSvg from '../images/closed';\nimport config from '../../../config';\nimport Link from '../link';\n\nconst TreeNode = ({ className = '', setCollapsed, collapsed, url, title, items, ...rest }) => {\n const isCollapsed = collapsed[url];\n\n const collapse = () => {\n setCollapsed(url);\n };\n\n const hasChildren = items.length !== 0;\n\n let location;\n\n if (typeof document != 'undefined') {\n location = document.location;\n }\n const active =\n location && (location.pathname === url || location.pathname === config.gatsby.pathPrefix + url);\n\n const calculatedClassName = `${className} item ${active ? 'active' : ''}`;\n\n return (\n
  • \n {title && (\n \n {title}\n {!config.sidebar.frontLine && title && hasChildren ? (\n \n ) : null}\n \n )}\n\n {!isCollapsed && hasChildren ? (\n
      \n {items.map((item, index) => (\n \n ))}\n
    \n ) : null}\n
  • \n );\n};\n\nexport default TreeNode;\n","import React, { useState } from 'react';\nimport config from '../../../config';\nimport TreeNode from './treeNode';\n\nconst calculateTreeData = edges => {\n const originalData = config.sidebar.ignoreIndex\n ? edges.filter(\n ({\n node: {\n fields: { slug },\n },\n }) => slug !== '/'\n )\n : edges;\n\n const tree = originalData.reduce(\n (\n accu,\n {\n node: {\n fields: { slug, title },\n },\n }\n ) => {\n const parts = slug.split('/');\n\n let { items: prevItems } = accu;\n\n const slicedParts =\n config.gatsby && config.gatsby.trailingSlash ? parts.slice(1, -2) : parts.slice(1, -1);\n\n for (const part of slicedParts) {\n let tmp = prevItems && prevItems.find(({ label }) => label == part);\n\n if (tmp) {\n if (!tmp.items) {\n tmp.items = [];\n }\n } else {\n tmp = { label: part, items: [] };\n prevItems.push(tmp);\n }\n prevItems = tmp.items;\n }\n const slicedLength =\n config.gatsby && config.gatsby.trailingSlash ? parts.length - 2 : parts.length - 1;\n\n const existingItem = prevItems.find(({ label }) => label === parts[slicedLength]);\n\n if (existingItem) {\n existingItem.url = slug;\n existingItem.title = title;\n } else {\n prevItems.push({\n label: parts[slicedLength],\n url: slug,\n items: [],\n title,\n });\n }\n return accu;\n },\n { items: [] }\n );\n\n const {\n sidebar: { forcedNavOrder = [] },\n } = config;\n\n const tmp = [...forcedNavOrder];\n\n if (config.gatsby && config.gatsby.trailingSlash) {\n }\n tmp.reverse();\n return tmp.reduce((accu, slug) => {\n const parts = slug.split('/');\n\n let { items: prevItems } = accu;\n\n const slicedParts =\n config.gatsby && config.gatsby.trailingSlash ? parts.slice(1, -2) : parts.slice(1, -1);\n\n for (const part of slicedParts) {\n let tmp = prevItems.find(item => item && item.label == part);\n\n if (tmp) {\n if (!tmp.items) {\n tmp.items = [];\n }\n } else {\n tmp = { label: part, items: [] };\n prevItems.push(tmp);\n }\n if (tmp && tmp.items) {\n prevItems = tmp.items;\n }\n }\n // sort items alphabetically.\n prevItems.map(item => {\n item.items = item.items.sort(function(a, b) {\n if (a.label < b.label) return -1;\n if (a.label > b.label) return 1;\n return 0;\n });\n });\n const slicedLength =\n config.gatsby && config.gatsby.trailingSlash ? parts.length - 2 : parts.length - 1;\n\n const index = prevItems.findIndex(({ label }) => label === parts[slicedLength]);\n\n if (prevItems.length) {\n accu.items.unshift(prevItems.splice(index, 1)[0]);\n }\n return accu;\n }, tree);\n};\n\nconst Tree = ({ edges }) => {\n let [treeData] = useState(() => {\n return calculateTreeData(edges);\n });\n\n const defaultCollapsed = {};\n\n treeData.items.forEach(item => {\n if (config.sidebar.collapsedNav && config.sidebar.collapsedNav.includes(item.url)) {\n defaultCollapsed[item.url] = true;\n } else {\n defaultCollapsed[item.url] = false;\n }\n });\n const [collapsed, setCollapsed] = useState(defaultCollapsed);\n\n const toggle = url => {\n setCollapsed({\n ...collapsed,\n [url]: !collapsed[url],\n });\n };\n\n return (\n \n );\n};\n\nexport default Tree;\n","function _extends() {\n _extends = Object.assign || function (target) {\n for (var i = 1; i < arguments.length; i++) {\n var source = arguments[i];\n\n for (var key in source) {\n if (Object.prototype.hasOwnProperty.call(source, key)) {\n target[key] = source[key];\n }\n }\n }\n\n return target;\n };\n\n return _extends.apply(this, arguments);\n}\n\nfunction _objectWithoutProperties(source, excluded) {\n if (source == null) return {};\n\n var target = _objectWithoutPropertiesLoose(source, excluded);\n\n var key, i;\n\n if (Object.getOwnPropertySymbols) {\n var sourceSymbolKeys = Object.getOwnPropertySymbols(source);\n\n for (i = 0; i < sourceSymbolKeys.length; i++) {\n key = sourceSymbolKeys[i];\n if (excluded.indexOf(key) >= 0) continue;\n if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue;\n target[key] = source[key];\n }\n }\n\n return target;\n}\n\nfunction _objectWithoutPropertiesLoose(source, excluded) {\n if (source == null) return {};\n var target = {};\n var sourceKeys = Object.keys(source);\n var key, i;\n\n for (i = 0; i < sourceKeys.length; i++) {\n key = sourceKeys[i];\n if (excluded.indexOf(key) >= 0) continue;\n target[key] = source[key];\n }\n\n return target;\n}\n\nimport React, { forwardRef } from 'react';\nvar ExternalLink = forwardRef(function (_ref, ref) {\n var _ref$color = _ref.color,\n color = _ref$color === void 0 ? 'currentColor' : _ref$color,\n _ref$size = _ref.size,\n size = _ref$size === void 0 ? 24 : _ref$size,\n rest = _objectWithoutProperties(_ref, [\"color\", \"size\"]);\n\n return /*#__PURE__*/React.createElement(\"svg\", _extends({\n ref: ref,\n xmlns: \"http://www.w3.org/2000/svg\",\n width: size,\n height: size,\n viewBox: \"0 0 24 24\",\n fill: \"none\",\n stroke: color,\n strokeWidth: \"2\",\n strokeLinecap: \"round\",\n strokeLinejoin: \"round\"\n }, rest), /*#__PURE__*/React.createElement(\"path\", {\n d: \"M18 13v6a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2V8a2 2 0 0 1 2-2h6\"\n }), /*#__PURE__*/React.createElement(\"polyline\", {\n points: \"15 3 21 3 21 9\"\n }), /*#__PURE__*/React.createElement(\"line\", {\n x1: \"10\",\n y1: \"14\",\n x2: \"21\",\n y2: \"3\"\n }));\n});\nExternalLink.displayName = 'ExternalLink';\nexport default ExternalLink;","import React from 'react';\nimport Tree from './tree';\nimport { StaticQuery, graphql } from 'gatsby';\nimport styled from '@emotion/styled';\nimport { ExternalLink } from 'react-feather';\nimport config from '../../../config';\n\n// eslint-disable-next-line no-unused-vars\nconst ListItem = styled(({ className, active, level, ...props }) => {\n return (\n
  • \n \n {props.children}\n \n
  • \n );\n})`\n list-style: none;\n\n a {\n color: #5c6975;\n text-decoration: none;\n font-weight: ${({ level }) => (level === 0 ? 700 : 400)};\n padding: 0.45rem 0 0.45rem ${props => 2 + (props.level || 0) * 1}rem;\n display: block;\n position: relative;\n\n &:hover {\n color: #2dc4f3 !important;\n }\n\n ${props =>\n props.active &&\n `\n // color: #663399;\n border-color: rgb(230,236,241) !important;\n border-style: solid none solid solid;\n border-width: 1px 0px 1px 1px;\n background-color: #fff;\n `} // external link icon\n svg {\n float: right;\n margin-right: 1rem;\n }\n }\n`;\n\nconst Sidebar = styled('aside')`\n width: 100%;\n height: 100vh;\n overflow: auto;\n position: fixed;\n padding-left: 0px;\n position: -webkit-sticky;\n position: -moz-sticky;\n position: sticky;\n top: 0;\n padding-right: 0;\n -webkit-box-shadow: -1px 0px 4px 1px rgba(175, 158, 232, 0.4);\n\n @media only screen and (max-width: 1023px) {\n width: 100%;\n /* position: relative; */\n height: 100vh;\n }\n\n @media (min-width: 767px) and (max-width: 1023px) {\n padding-left: 0;\n }\n\n @media only screen and (max-width: 767px) {\n padding-left: 0px;\n height: auto;\n }\n`;\n\nconst Divider = styled(props => (\n
  • \n
    \n
  • \n))`\n list-style: none;\n padding: 0.5rem 0;\n\n hr {\n margin: 0;\n padding: 0;\n border: 0;\n border-bottom: 1px solid #ede7f3;\n }\n`;\n\nconst SidebarLayout = ({ location }) => (\n {\n return (\n \n {config.sidebar.title ? (\n \n ) : null}\n
      \n \n {config.sidebar.links && config.sidebar.links.length > 0 && }\n {config.sidebar.links.map((link, key) => {\n if (link.link !== '' && link.text !== '') {\n return (\n \n {link.text}\n \n \n );\n }\n })}\n
    \n
    \n );\n }}\n />\n);\n\nexport default SidebarLayout;\n","import React from 'react';\nimport styled from '@emotion/styled';\nimport { StaticQuery, graphql } from 'gatsby';\nimport Link from './link';\nimport Loadable from 'react-loadable';\n\nimport config from '../../config.js';\nimport LoadingProvider from './mdxComponents/loading';\nimport { DarkModeSwitch } from './DarkModeSwitch';\n\nconst help = require('./images/help.svg');\n\nconst isSearchEnabled = config.header.search && config.header.search.enabled ? true : false;\n\nlet searchIndices = [];\n\nif (isSearchEnabled && config.header.search.indexName) {\n searchIndices.push({\n name: `${config.header.search.indexName}`,\n title: `Results`,\n hitComp: `PageHit`,\n });\n}\n\nimport Sidebar from './sidebar';\n\nconst LoadableComponent = Loadable({\n loader: () => import('./search/index'),\n loading: LoadingProvider,\n});\n\nfunction myFunction() {\n var x = document.getElementById('navbar');\n\n if (x.className === 'topnav') {\n x.className += ' responsive';\n } else {\n x.className = 'topnav';\n }\n}\n\nconst StyledBgDiv = styled('div')`\n height: 60px;\n box-shadow: 0 3px 6px 0 rgba(0, 0, 0, 0.16);\n background-color: #f8f8f8;\n position: relative;\n display: none;\n background: ${props => (props.isDarkThemeActive ? '#001932' : undefined)};\n\n @media (max-width: 767px) {\n display: block;\n }\n`;\n\nconst Header = ({ location, isDarkThemeActive, toggleActiveTheme }) => (\n {\n const logoImg = require('./images/logo.svg');\n\n const twitter = require('./images/twitter.svg');\n\n const discordBrandsBlock = require('./images/discord-brands-block.svg');\n\n const twitterBrandsBlock = require('./images/twitter-brands-block.svg');\n\n const {\n site: {\n siteMetadata: { headerTitle, helpUrl, tweetText, logo, headerLinks },\n },\n } = data;\n\n const finalLogoLink = logo.link !== '' ? logo.link : 'https://www.afotec.af.mil/';\n\n return (\n
    \n \n \n
    \n \n \n \n \n \n
    \n {isSearchEnabled ? (\n
    \n \n
    \n ) : null}\n
    \n
    \n );\n }}\n />\n);\n\nexport default Header;\n","import createCache from '@emotion/cache';\nimport { serializeStyles } from '@emotion/serialize';\nimport { getRegisteredStyles, insertStyles } from '@emotion/utils';\n\nfunction insertWithoutScoping(cache, serialized) {\n if (cache.inserted[serialized.name] === undefined) {\n return cache.insert('', serialized, cache.sheet, true);\n }\n}\n\nfunction merge(registered, css, className) {\n var registeredStyles = [];\n var rawClassName = getRegisteredStyles(registered, registeredStyles, className);\n\n if (registeredStyles.length < 2) {\n return className;\n }\n\n return rawClassName + css(registeredStyles);\n}\n\nvar createEmotion = function createEmotion(options) {\n var cache = createCache(options); // $FlowFixMe\n\n cache.sheet.speedy = function (value) {\n if (process.env.NODE_ENV !== 'production' && this.ctr !== 0) {\n throw new Error('speedy must be changed before any rules are inserted');\n }\n\n this.isSpeedy = value;\n };\n\n cache.compat = true;\n\n var css = function css() {\n for (var _len = arguments.length, args = new Array(_len), _key = 0; _key < _len; _key++) {\n args[_key] = arguments[_key];\n }\n\n var serialized = serializeStyles(args, cache.registered, undefined);\n insertStyles(cache, serialized, false);\n return cache.key + \"-\" + serialized.name;\n };\n\n var keyframes = function keyframes() {\n for (var _len2 = arguments.length, args = new Array(_len2), _key2 = 0; _key2 < _len2; _key2++) {\n args[_key2] = arguments[_key2];\n }\n\n var serialized = serializeStyles(args, cache.registered);\n var animation = \"animation-\" + serialized.name;\n insertWithoutScoping(cache, {\n name: serialized.name,\n styles: \"@keyframes \" + animation + \"{\" + serialized.styles + \"}\"\n });\n return animation;\n };\n\n var injectGlobal = function injectGlobal() {\n for (var _len3 = arguments.length, args = new Array(_len3), _key3 = 0; _key3 < _len3; _key3++) {\n args[_key3] = arguments[_key3];\n }\n\n var serialized = serializeStyles(args, cache.registered);\n insertWithoutScoping(cache, serialized);\n };\n\n var cx = function cx() {\n for (var _len4 = arguments.length, args = new Array(_len4), _key4 = 0; _key4 < _len4; _key4++) {\n args[_key4] = arguments[_key4];\n }\n\n return merge(cache.registered, css, classnames(args));\n };\n\n return {\n css: css,\n cx: cx,\n injectGlobal: injectGlobal,\n keyframes: keyframes,\n hydrate: function hydrate(ids) {\n ids.forEach(function (key) {\n cache.inserted[key] = true;\n });\n },\n flush: function flush() {\n cache.registered = {};\n cache.inserted = {};\n cache.sheet.flush();\n },\n // $FlowFixMe\n sheet: cache.sheet,\n cache: cache,\n getRegisteredStyles: getRegisteredStyles.bind(null, cache.registered),\n merge: merge.bind(null, cache.registered, css)\n };\n};\n\nvar classnames = function classnames(args) {\n var cls = '';\n\n for (var i = 0; i < args.length; i++) {\n var arg = args[i];\n if (arg == null) continue;\n var toAdd = void 0;\n\n switch (typeof arg) {\n case 'boolean':\n break;\n\n case 'object':\n {\n if (Array.isArray(arg)) {\n toAdd = classnames(arg);\n } else {\n toAdd = '';\n\n for (var k in arg) {\n if (arg[k] && k) {\n toAdd && (toAdd += ' ');\n toAdd += k;\n }\n }\n }\n\n break;\n }\n\n default:\n {\n toAdd = arg;\n }\n }\n\n if (toAdd) {\n cls && (cls += ' ');\n cls += toAdd;\n }\n }\n\n return cls;\n};\n\nexport default createEmotion;","import createEmotion from 'create-emotion';\n\nvar _createEmotion = createEmotion(),\n flush = _createEmotion.flush,\n hydrate = _createEmotion.hydrate,\n cx = _createEmotion.cx,\n merge = _createEmotion.merge,\n getRegisteredStyles = _createEmotion.getRegisteredStyles,\n injectGlobal = _createEmotion.injectGlobal,\n keyframes = _createEmotion.keyframes,\n css = _createEmotion.css,\n sheet = _createEmotion.sheet,\n cache = _createEmotion.cache;\n\nexport { cache, css, cx, flush, getRegisteredStyles, hydrate, injectGlobal, keyframes, merge, sheet };","import { injectGlobal } from 'emotion';\n\nexport const baseStyles = injectGlobal`\n @import url('https://fonts.googleapis.com/css?family=Roboto:300,400,500,700&display=swap');\n @import url('https://fonts.googleapis.com/css?family=Poppins:300,400,500,600&display=swap');\n * {\n margin: 0;\n padding: 0;\n box-sizing: border-box;\n font-display: swap;\n }\n ::-webkit-input-placeholder {\n /* Edge */\n color: #c2c2c2;\n }\n\n :-ms-input-placeholder {\n /* Internet Explorer */\n color: #c2c2c2;\n }\n\n ::placeholder {\n color: #c2c2c2;\n }\n html,\n body {\n font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', 'Roboto', 'Roboto Light', 'Oxygen',\n 'Ubuntu', 'Cantarell', 'Fira Sans', 'Droid Sans', 'Helvetica Neue', sans-serif,\n 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol';\n\n font-size: 16px;\n scroll-behavior: smooth;\n }\n\n a {\n transition: color 0.15s;\n /* color: #663399; */\n }\n\n body {\n font-family: 'Roboto';\n }\n .visibleMobile {\n display: none;\n }\n .visibleMobileView {\n display: none !important;\n }\n .video-responsive {\n position: relative;\n padding-bottom: 56.2%;\n }\n a {\n text-decoration: none;\n }\n a:hover {\n text-decoration: none;\n }\n .displayInline {\n display: inline-block;\n }\n .navBarToggle {\n border: 0px solid #fff;\n border-radius: 4px;\n width: 36px;\n height: 33px;\n position: absolute;\n right: 20px;\n padding: 8px 5px;\n display: none;\n }\n .navBarToggle .iconBar {\n display: block;\n width: 22px;\n height: 2px;\n border-radius: 1px;\n margin: 0 auto;\n margin-top: 4px;\n background-color: #001934;\n }\n .navBarToggle .iconBar:first-child {\n margin-top: 0px;\n }\n\n\n.mobileScrollUpButton {\n display: none !important;\n position: fixed;\n left: 0;\n bottom: 5px;\n background-color: #2dc4f3;\n border: none;\n outline: none;\n color: white;\n padding: 15px;\n text-align: center;\n text-decoration: none;\n display: inline-block;\n font-size: 16px;\n border-radius: 25px;\n }\n\n .fade {\n display: block !important;\n -webkit-animation: fadein 300ms linear forwards;\n animation: fadein 300ms linear forwards;\n }\n\n @keyframes darkenThenLightenButton {\n 0% {brightness: 100% }\n 50% {brightness: 75% }\n 100% { brightness: 100% }\n }\n\n @keyframes fadein {\n 0% { opacity: 0; }\n 100% { opacity: 1; }\n }\n\n .video-responsive iframe {\n position: absolute;\n width: 100%;\n height: 100%;\n }\n\n .diffNewLine {\n color: #22863a;\n background-color: #f0fff4;\n }\n\n .diffRemoveLine {\n color: red;\n background-color: #ffcccc;\n }\n .navBarParent {\n width: 100%;\n float: left;\n display: flex;\n align-items: center;\n }\n .divider {\n height: 30px;\n margin: 0 15px;\n border-right: 1px solid rgba(255, 255, 255, 0.3);\n }\n .navBarULRight {\n /* position: absolute;\n right: 30px; */\n }\n\n .navbar-default .navbar-toggle .icon-bar {\n background-color: #fff !important;\n }\n\n .navbar-default .navbar-toggle:focus,\n .navbar-default .navbar-toggle:hover {\n background-color: #001933;\n }\n\n .headerWrapper {\n border-bottom: 1px solid rgb(212, 218, 223);\n box-shadow: rgba(116, 129, 141, 0.1) 0px 1px 1px 0px;\n display: flex;\n align-items: center;\n }\n .formElement {\n background-color: transparent;\n padding: 4px;\n border-radius: 5px;\n position: relative;\n }\n .formElement:focus {\n outline: none;\n border: none;\n }\n .formElement svg path {\n fill: #2fd2c5;\n }\n .searchInput {\n width: 100%;\n background-color: rgba(28,211,198,.12) !important;\n border-width: 0 !important;\n color: #C2C2C2;\n padding: 10px;\n border-radius: 5px;\n color: #fff;\n opacity: .6;\n padding-left: 38px;\n max-width: 600px;\n }\n .searchInput:focus,\n .searchInput:visited,\n .searchInput:hover,\n .searchInput:focus-within {\n outline: none;\n border: 0;\n }\n .searchWrapper {\n padding-left: 40px;\n padding-right: 20px;\n flex: 1;\n position: relative;\n }\n .searchWrapper a {\n font-weight: 500;\n }\n .hitWrapper {\n background-color: #fff;\n padding: 0.7em 1em 0.4em;\n border-radius: 4px;\n position: absolute;\n width: 80vw;\n max-width: 30em;\n top: 40px;\n border: 1px solid #ccc;\n box-shadow: 0 1px 4px 0 rgba(0, 0, 0, 0.16);\n height: auto;\n max-height: 80vh;\n overflow: scroll;\n left: 0;\n }\n .hitWrapper ul li {\n margin-top: 0.7em;\n padding-top: 0.7em;\n border-top: 1px solid;\n list-style-type: none;\n }\n .hitWrapper ul li:first-child {\n border-top: 0px;\n margin-top: 0px;\n color: black !important;\n padding: 0px;\n }\n .showResults {\n display: block;\n }\n .hideResults {\n display: none;\n }\n .hitWrapper span {\n color: black;\n font-size: 14px;\n }\n .headerTitle {\n height: auto;\n font-size: 21px;\n line-height: 1.5;\n font-weight: 300;\n color: #fff !important;\n text-transform: uppercase;\n }\n .headerTitle a {\n color: #fff;\n }\n\n .headerTitle a:hover {\n text-decoration: none;\n opacity: 0.8;\n }\n .logoWrapper {\n padding: 21px 0;\n padding-left: 20px;\n }\n\n .logoContent {\n font-family: 'Roboto';\n margin-left: 16px;\n font-size: 28px;\n line-height: 1.5;\n font-weight: 500;\n padding-right: 10px;\n }\n\n .headerTitleReleasable {\n padding-right: 20px;\n height: auto;\n font-size: 10px;\n line-height: 1.5;\n font-weight: 300;\n color: #fff !important;\n text-transform: uppercase;\n }\n\n /* Header section starts here */\n .removePadd {\n padding: 0 !important;\n }\n .navBarDefault {\n background-color: #001934;\n border-radius: 0;\n border-top: 0;\n margin-bottom: 0;\n border: 0;\n display: flex;\n align-items: center;\n box-shadow: -1px 0px 4px 1px rgba(175, 158, 232, 0.4);\n -webkit-box-shadow: -1px 0px 4px 1px rgba(175, 158, 232, 0.4);\n -moz-box-shadow: -1px 0px 4px 1px rgba(175, 158, 232, 0.8);\n -o-box-shadow: -1px 0px 4px 1px rgba(175, 158, 232, 0.4);\n z-index: 1;\n padding: 15px;\n position: relative;\n height: 80px;\n }\n .navBarHeader {\n min-width: 335px;\n padding-right: 20px;\n display: flex;\n align-items: center;\n }\n .navBarBrand {\n padding: 0px 0px;\n display: flex;\n align-items: center;\n }\n .navBarBrand img {\n width: 55px;\n margin-right: 20px;\n display: inline-block;\n }\n .navBarUL li {\n list-style-type: none;\n }\n .navBarUL {\n -webkit-overflow-scrolling: touch;\n }\n .navBarUL li a {\n font-family: 'Roboto';\n color: #fff !important;\n font-size: 16px;\n font-weight: 500;\n line-height: 1em;\n opacity: 1;\n padding: 10px 15px;\n }\n .navBarNav {\n display: flex;\n align-items: center;\n }\n .navBarUL li a img,\n .navBarUL li a .shareIcon {\n width: 20px;\n }\n .navBarUL li a:hover {\n opacity: 0.7;\n }\n pre {\n border: 0 !important;\n background-color: rgb(245, 247, 249); /* !important; */\n }\n\n blockquote {\n color: rgb(116, 129, 141);\n margin: 0px 0px 24px;\n padding: 0px 0px 0px 12px;\n border-left: 4px solid rgb(230, 236, 241);\n border-color: rgb(230, 236, 241);\n }\n .socialWrapper {\n display: flex;\n align-items: center;\n }\n .socialWrapper li {\n display: inline-block;\n }\n .socialWrapper li a {\n display: contents;\n }\n .discordBtn, .twitterBtn {\n border-radius: 4px;\n border: solid 1px #d1d2d3;\n background-color: #f1f5f8;\n width: 20px;\n height: 20px;\n padding-top: 2px;\n margin-left: 8px;\n display: flex;\n align-items: center;\n justify-content: center;\n opacity: .8;\n cursor: pointer;\n }\n .twitterBtn img {\n width: 12px !important;\n }\n .discordBtn img {\n width: 10px !important;\n }\n .discordBtn:hover, .twitterBtn:hover {\n opacity: 1;\n }\n .discordBtn {\n img {\n width: 10px;\n }\n }\n .goHomeLink {\n margin-top: 5%;\n }\n /* Header section ends here */\n .sidebarTitle {\n /* box-shadow: 0 3px 6px 0 rgba(0, 0, 0, 0.16); */\n background-color: #f8f8f8;\n padding: 18px 16px;\n font-family: 'Poppins';\n font-size: 18px;\n font-weight: 600;\n color: #001934;\n display: flex;\n align-items: center;\n }\n\n .sideBarShow {\n display: none;\n }\n\n .sidebarTitle a {\n color: #001934;\n }\n\n .greenCircle {\n width: 8px;\n height: 8px;\n background-color: #1cd3c6;\n border-radius: 50%;\n margin: 0 12px;\n }\n\n .headerNav {\n font-family: 'Roboto';\n padding: 0px 24px;\n color: #001933;\n font-size: 16px;\n font-weight: 500;\n line-height: 1em;\n }\n\n .headerNav a {\n color: #001933;\n text-decoration: none;\n }\n\n .headerNav a:hover {\n text-decoration: none;\n }\n\n .logoWrapper img {\n width: 40px;\n }\n\n .sideBarUL {\n margin-top: 32px;\n }\n\n .sideBarUL li {\n list-style-type: none;\n width: auto;\n }\n\n .sideBarUL li a {\n /* color: #fff; */\n font-size: 14px;\n font-weight: 500;\n line-height: 1.5;\n padding: 7px 24px 7px 16px;\n padding-left: 10px;\n padding-right: 25px;\n border-style: solid none solid solid;\n border-width: 1px 0px 1px 1px;\n border-color: transparent currentcolor transparent transparent;\n }\n\n .hideFrontLine .collapser {\n background: transparent;\n border: none;\n outline: none;\n position: absolute;\n right: 20px;\n z-index: 1;\n cursor: pointer;\n }\n\n .hideFrontLine .active > a {\n background-color: #2dc4f3;\n color: #fff !important;\n }\n .firstLevel ul li .collapser svg path {\n fill: #fff !important;\n }\n .active .collapser > svg > path {\n fill: #001933 !important;\n }\n\n .firstLevel ul .item ul .item {\n border-left: 1px solid #e6ecf1;\n }\n\n .sideBarUL .item {\n list-style: none;\n padding: 0;\n }\n\n .sideBarUL .item > a {\n color: #2dc4f3;\n text-decoration: none;\n display: flex;\n align-items: center;\n position: relative;\n width: 100%;\n padding-right: 35px;\n padding-left: 15px;\n }\n\n .showFrontLine .item > a:hover {\n background-color: #001933;\n }\n\n .showFrontLine .active > a {\n /* color: #fff; */\n background-color: #001933;\n }\n\n .sideBarUL .item .item {\n margin-left: 16px;\n }\n\n .firstLevel > ul > .item {\n margin-left: 0 !important;\n }\n\n .showFrontLine .item .item {\n border-left: 1px solid #e6ecf1;\n border-left-color: rgb(230, 236, 241);\n padding: 0;\n width: calc(100% - 16px) !important;\n }\n\n .showFrontLine .item .active > a {\n border-color: rgb(230, 236, 241) !important;\n border-style: solid none solid solid;\n border-width: 1px 0px 1px 1px;\n background-color: #2dc4f3 !important;\n color: #fff;\n }\n\n .titleWrapper {\n display: flex;\n align-items: center;\n padding-bottom: 40px;\n border-bottom: 1px solid rgb(230, 236, 241);\n margin-bottom: 32px;\n }\n\n .gitBtn {\n height: 30px;\n min-height: 30px;\n display: flex;\n align-items: center;\n }\n\n .gitBtn img {\n width: 15px;\n display: inline-block;\n margin-right: 5px;\n }\n\n .addPaddTopBottom {\n padding: 50px 0;\n }\n\n .preRightWrapper {\n display: block;\n margin: 0px;\n flex: 1 1 0%;\n padding: 16px;\n text-align: right;\n }\n\n .smallContent {\n display: block;\n margin: 0px;\n padding: 0px;\n color: #6e6e6e;\n }\n\n .smallContent span {\n font-size: 12px;\n line-height: 1.625;\n font-weight: 400;\n }\n\n /* **************************** */\n\n .nextRightWrapper {\n display: block;\n margin: 0px;\n padding: 16px;\n flex: 1 1 0%;\n }\n\n /* tables.css */\n table {\n padding: 0;\n }\n\n table tr {\n border-top: 1px solid #cccccc;\n margin: 0;\n padding: 0;\n }\n\n table tr:nth-child(2n) {\n background-color: #f8f8f8;\n }\n\n table tr th {\n font-weight: bold;\n border: 1px solid #cccccc;\n text-align: left;\n margin: 0;\n padding: 6px 13px;\n }\n\n table tr td {\n border: 1px solid #cccccc;\n text-align: left;\n margin: 0;\n padding: 6px 13px;\n }\n\n table tr th :first-child,\n table tr td :first-child {\n margin-top: 0;\n }\n\n table tr th :last-child,\n table tr td :last-child {\n margin-bottom: 0;\n }\n /* end - tables.css */\n\n /* Image styling */\n img {\n max-width: 100%;\n }\n /* end image */\n\n .communitySection {\n font-size: 24px;\n font-weight: 700;\n }\n .authorSection {\n padding: 20px 0;\n }\n .authorSection,\n .authorName {\n display: flex;\n align-items: center;\n }\n .authorImg img {\n width: 75px;\n height: 75px;\n border-radius: 50%;\n min-width: 75px;\n max-width: 75px;\n min-height: 75px;\n max-height: 75px;\n }\n .authorDetails {\n padding-left: 10px;\n }\n .authorDesc {\n padding-top: 5px;\n font-size: 14px;\n }\n .authorName img {\n margin-left: 10px;\n display: inline-block;\n width: 20px;\n }\n .authorName img:hover {\n opacity: 0.7;\n }\n\n .heading1 {\n font-size: 26px;\n font-weight: 800;\n line-height: 1.5;\n margin-bottom: 16px;\n margin-top: 32px;\n }\n\n .heading2 {\n font-size: 24px;\n font-weight: 700;\n line-height: 1.5;\n margin-bottom: 16px;\n margin-top: 32px;\n }\n\n .heading3 {\n font-size: 20px;\n font-weight: 600;\n line-height: 1.5;\n margin-bottom: 16px;\n margin-top: 32px;\n }\n\n .heading4 {\n font-size: 18px;\n font-weight: 500;\n line-height: 1.5;\n margin-bottom: 16px;\n margin-top: 32px;\n }\n\n .heading5 {\n font-size: 16px;\n font-weight: 400;\n line-height: 1.5;\n margin-bottom: 16px;\n margin-top: 32px;\n }\n\n .heading6 {\n font-size: 14px;\n font-weight: 300;\n line-height: 1.5;\n margin-bottom: 16px;\n margin-top: 32px;\n }\n\n .paragraph {\n margin: 16px 0px 32px;\n line-height: 1.625;\n }\n\n .pre {\n font-size: 14px;\n margin: 0px;\n padding: 16px;\n overflow: auto;\n }\n\n .topnav {\n -webkit-transition: top 0.5s, bottom 0.5s;\n }\n\n @media (max-width: 767px) {\n .formElement svg path {\n fill: #001934;\n }\n .visibleMobileView {\n display: block !important;\n }\n .searchInput {\n color: #001934;\n }\n .socialWrapper {\n position: absolute;\n right: 10px;\n top: 29px;\n }\n .responsive {\n margin-top: 15px;\n position: relative;\n padding-bottom: 20px;\n border-top: 1px solid #fff;\n }\n .headerTitle {\n padding-right: 50px;\n font-size: 16px;\n }\n .navBarBrand {\n min-height: 40px;\n }\n .navBarBrand img {\n margin-right: 8px;\n }\n .topnav.responsive .visibleMobile {\n display: block;\n }\n .topnav .navBarUL {\n display: none;\n }\n .topnav.responsive .navBarUL {\n display: block;\n text-align: left;\n }\n .hiddenMobile {\n display: none !important;\n }\n hr {\n margin-top: 0;\n margin-bottom: 0;\n }\n .navBarParent {\n display: block;\n }\n .separator {\n margin-top: 20px;\n margin-bottom: 20px;\n }\n .navBarULRight {\n position: static;\n }\n .navBarUL {\n display: flex;\n align-items: center;\n margin: 7.5px 0px;\n }\n .navBarUL li {\n height: 37px;\n }\n .navBarUL li a {\n font-size: 14px;\n padding: 10px 15px;\n }\n\n .navBarDefault {\n display: block;\n height: auto;\n }\n\n .navBarToggle {\n margin-right: 0;\n display: block;\n position: absolute;\n left: 11px;\n top: 15px;\n background: #fff;\n }\n\n .navBarHeader {\n display: flex;\n min-width: auto;\n padding-right: 0;\n align-items: center;\n }\n\n .navBarBrand {\n font-size: 20px;\n padding: 0 0;\n padding-left: 0;\n flex: initial;\n padding-right: 15px;\n }\n\n .titleWrapper {\n padding: 0 15px;\n display: block;\n }\n\n .gitBtn {\n display: inline-block;\n }\n\n .mobileView {\n text-align: left !important;\n padding-left: 0 !important;\n }\n\n .searchWrapper {\n padding: 0px 0;\n padding-top: 0px;\n position: absolute;\n bottom: 0px;\n width: calc(100% - 70px);\n position: absolute;\n left: 40px;\n top: 8px;\n }\n .hitWrapper {\n width: 100%;\n right: 0;\n top: 35px;\n max-height: fit-content;\n position: static;\n }\n }\n\n @media (min-width: 768px) and (max-width: 991px) {\n .navBarDefault {\n padding: 10px;\n }\n .navBarBrand {\n font-size: 22px;\n }\n .navBarHeader {\n min-width: 240px;\n flex: initial;\n }\n .divider {\n margin: 0 5px;\n height: 20px;\n }\n .hitWrapper {\n max-width: 500px;\n }\n .navBarUL li a {\n padding: 10px 5px;\n }\n .searchWrapper {\n padding-left: 0px;\n }\n }\n`;\n","import * as React from 'react';\nimport { ThemeProvider as EmotionThemeProvider } from 'emotion-theming';\nimport { Global } from '@emotion/core';\n\nimport { lightTheme, darkTheme } from './index';\nimport Header from '../Header';\nimport { baseStyles } from '../styles/GlobalStyles';\n\nclass ThemeProvider extends React.Component {\n state = {\n isDarkThemeActive: false,\n };\n\n componentDidMount() {\n this.retrieveActiveTheme();\n }\n\n retrieveActiveTheme = () => {\n const isDarkThemeActive = JSON.parse(window.localStorage.getItem('isDarkThemeActive'));\n\n this.setState({ isDarkThemeActive });\n };\n\n toggleActiveTheme = () => {\n this.setState(prevState => ({ isDarkThemeActive: !prevState.isDarkThemeActive }));\n\n window.localStorage.setItem('isDarkThemeActive', JSON.stringify(!this.state.isDarkThemeActive));\n };\n\n render() {\n const { children, location } = this.props;\n\n const { isDarkThemeActive } = this.state;\n\n const currentActiveTheme = isDarkThemeActive ? darkTheme : lightTheme;\n\n return (\n
    \n \n \n {children}\n
    \n );\n }\n}\n\nexport default ThemeProvider;\n","import styled from '@emotion/styled';\n\nexport const Sidebar = styled('aside')`\n width: 100%;\n border-right: 1px solid #ede7f3;\n height: 100vh;\n overflow: auto;\n position: fixed;\n padding-left: 24px;\n position: -webkit-sticky;\n position: -moz-sticky;\n position: sticky;\n top: 0;\n\n background: ${props => props.theme.colors.background};\n\n .rightSideTitle {\n font-size: 10px;\n line-height: 1;\n font-weight: 700;\n text-transform: uppercase;\n letter-spacing: 1.2px;\n padding: 7px 24px 7px 16px;\n border-left: 1px solid #e6ecf1;\n border-left-color: rgb(230, 236, 241);\n\n color: ${props => props.theme.colors.text};\n }\n\n .rightSideBarUL {\n margin-top: 32px;\n }\n\n .rightSideBarUL li {\n list-style-type: none;\n border-left: 1px solid #e6ecf1;\n border-left-color: rgb(230, 236, 241);\n }\n\n .rightSideBarUL li a {\n font-size: 12px;\n font-weight: 500;\n line-height: 1.5;\n padding: 7px 24px 7px 16px;\n\n color: ${props => props.theme.colors.text};\n }\n\n @media only screen and (max-width: 50rem) {\n width: 100%;\n position: relative;\n }\n`;\n\nexport const ListItem = styled(({ className, active, level, ...props }) => {\n return (\n
  • \n \n {props.children}\n \n
  • \n );\n})`\n list-style: none;\n\n a {\n color: #5c6975;\n text-decoration: none;\n font-weight: ${({ level }) => (level === 0 ? 700 : 400)};\n padding: 0.45rem 0 0.45rem ${props => 2 + (props.level || 0) * 1}rem;\n display: block;\n position: relative;\n\n &:hover {\n color: #2dc4f3 !important;\n }\n\n ${props =>\n props.active &&\n `\n color: #2dc4f3;\n border-color: rgb(230,236,241) !important;\n border-style: solid none solid solid;\n border-width: 1px 0px 1px 1px;\n background-color: #fff;\n `} // external link icon\n svg {\n float: right;\n margin-right: 1rem;\n }\n }\n`;\n","import React from 'react';\nimport { StaticQuery, graphql } from 'gatsby';\n\n// import Link from './link';\nimport config from '../../config';\nimport { Sidebar, ListItem } from './styles/Sidebar';\n\nconst SidebarLayout = ({ location }) => (\n {\n let navItems = [];\n\n let finalNavItems;\n\n if (allMdx.edges !== undefined && allMdx.edges.length > 0) {\n const navItems = allMdx.edges.map((item, index) => {\n let innerItems;\n\n if (item !== undefined) {\n if (\n item.node.fields.slug === location.pathname ||\n config.gatsby.pathPrefix + item.node.fields.slug === location.pathname\n ) {\n if (item.node.tableOfContents.items) {\n innerItems = item.node.tableOfContents.items.map((innerItem, index) => {\n const itemId = innerItem.title\n ? innerItem.title.replace(/\\s+/g, '').toLowerCase()\n : '#';\n\n return (\n \n {innerItem.title}\n \n );\n });\n }\n }\n }\n if (innerItems) {\n finalNavItems = innerItems;\n }\n });\n }\n\n if (finalNavItems && finalNavItems.length) {\n return (\n \n
      \n
    • CONTENTS
    • \n {finalNavItems}\n
    \n
    \n );\n } else {\n return (\n \n
      \n
      \n );\n }\n }}\n />\n);\n\nexport default SidebarLayout;\n","import React from 'react';\nimport styled from '@emotion/styled';\nimport { MDXProvider } from '@mdx-js/react';\n\nimport ThemeProvider from './theme/themeProvider';\nimport mdxComponents from './mdxComponents';\nimport Sidebar from './sidebar';\nimport RightSidebar from './rightSidebar';\nimport config from '../../config.js';\n\nimport \"katex/dist/katex.min.css\"\n\nconst Wrapper = styled('div')`\n display: flex;\n justify-content: space-between;\n background: ${({ theme }) => theme.colors.background};\n\n .sideBarUL li a {\n color: ${({ theme }) => theme.colors.text};\n }\n\n .sideBarUL .item > a:hover {\n background-color: #2dc4f3;\n color: #fff !important;\n\n /* background: #F8F8F8 */\n }\n\n @media only screen and (max-width: 767px) {\n display: block;\n }\n`;\n\nconst Content = styled('main')`\n display: flex;\n flex-grow: 1;\n margin: 0px 88px;\n padding-top: 3rem;\n background: ${({ theme }) => theme.colors.background};\n\n table tr {\n background: ${({ theme }) => theme.colors.background};\n }\n\n @media only screen and (max-width: 1023px) {\n padding-left: 0;\n margin: 0 10px;\n padding-top: 3rem;\n }\n`;\n\nconst MaxWidth = styled('div')`\n @media only screen and (max-width: 50rem) {\n width: 100%;\n position: relative;\n }\n`;\n\nconst LeftSideBarWidth = styled('div')`\n width: 298px;\n`;\n\nconst RightSideBarWidth = styled('div')`\n width: 224px;\n`;\n\nconst Layout = ({ children, location }) => (\n \n \n \n \n \n \n {config.sidebar.title ? (\n \n ) : null}\n \n {children}\n \n \n \n \n \n \n \n);\n\nexport default Layout;\n","import styled from '@emotion/styled';\n\nexport const StyledNextPrevious = styled('div')`\n margin: 0px;\n padding: 0px;\n width: auto;\n display: grid;\n grid-template-rows: auto;\n column-gap: 24px;\n grid-template-columns: calc(50% - 8px) calc(50% - 8px);\n\n .previousBtn {\n cursor: pointer;\n -moz-box-align: center;\n -moz-box-direction: normal;\n -moz-box-orient: horizontal;\n margin: 0px;\n padding: 0px;\n position: relative;\n display: flex;\n flex-direction: row;\n align-items: center;\n place-self: stretch;\n border-radius: 3px;\n border: 1px solid rgb(230, 236, 241);\n transition: border 200ms ease 0s;\n box-shadow: rgba(116, 129, 141, 0.1) 0px 3px 8px 0px;\n text-decoration: none;\n\n background-color: ${props => props.theme.colors.background};\n color: ${props => props.theme.colors.text};\n }\n\n .nextBtn {\n cursor: pointer;\n -moz-box-align: center;\n -moz-box-direction: normal;\n -moz-box-orient: horizontal;\n margin: 0px;\n padding: 0px;\n position: relative;\n display: flex;\n flex-direction: row;\n align-items: center;\n place-self: stretch;\n border-radius: 3px;\n border: 1px solid rgb(230, 236, 241);\n transition: border 200ms ease 0s;\n box-shadow: rgba(116, 129, 141, 0.1) 0px 3px 8px 0px;\n text-decoration: none;\n\n background-color: ${props => props.theme.colors.background};\n color: ${props => props.theme.colors.text};\n }\n\n .nextBtn:hover,\n .previousBtn:hover {\n text-decoration: none;\n border: 1px solid #2dc4f3;\n }\n\n .nextBtn:hover .rightArrow,\n .previousBtn:hover .leftArrow {\n color: #2dc4f3;\n }\n\n .leftArrow {\n display: block;\n margin: 0px;\n color: rgb(157, 170, 182);\n flex: 0 0 auto;\n font-size: 24px;\n transition: color 200ms ease 0s;\n padding: 16px;\n padding-right: 16px;\n }\n\n .rightArrow {\n flex: 0 0 auto;\n font-size: 24px;\n transition: color 200ms ease 0s;\n padding: 16px;\n padding-left: 16px;\n display: block;\n margin: 0px;\n color: rgb(157, 170, 182);\n }\n\n .nextPreviousTitle {\n display: block;\n margin: 0px;\n padding: 0px;\n transition: color 200ms ease 0s;\n }\n\n .nextPreviousTitle span {\n font-size: 16px;\n line-height: 1.5;\n font-weight: 500;\n }\n\n @media (max-width: 767px) {\n display: block;\n padding: 0 15px;\n\n .previousBtn {\n margin-bottom: 20px;\n }\n }\n`;\n","import React from 'react';\nimport Link from './link';\n\nimport { StyledNextPrevious } from './styles/PageNavigationButtons';\n\nconst NextPrevious = ({ mdx, nav }) => {\n let currentIndex;\n\n const currentPaginationInfo = nav.map((el, index) => {\n if (el && el.url === mdx.fields.slug) {\n currentIndex = index;\n }\n });\n\n const nextInfo = {};\n\n const previousInfo = {};\n\n if (currentIndex === undefined) {\n // index\n if (nav[0]) {\n nextInfo.url = nav[0].url;\n nextInfo.title = nav[0].title;\n }\n previousInfo.url = null;\n previousInfo.title = null;\n currentIndex = -1;\n } else if (currentIndex === 0) {\n // first page\n nextInfo.url = nav[currentIndex + 1] ? nav[currentIndex + 1].url : null;\n nextInfo.title = nav[currentIndex + 1] ? nav[currentIndex + 1].title : null;\n previousInfo.url = null;\n previousInfo.title = null;\n } else if (currentIndex === nav.length - 1) {\n // last page\n nextInfo.url = null;\n nextInfo.title = null;\n previousInfo.url = nav[currentIndex - 1] ? nav[currentIndex - 1].url : null;\n previousInfo.title = nav[currentIndex - 1] ? nav[currentIndex - 1].title : null;\n } else if (currentIndex) {\n // any other page\n nextInfo.url = nav[currentIndex + 1].url;\n nextInfo.title = nav[currentIndex + 1].title;\n if (nav[currentIndex - 1]) {\n previousInfo.url = nav[currentIndex - 1].url;\n previousInfo.title = nav[currentIndex - 1].title;\n }\n }\n\n return (\n \n {previousInfo.url && currentIndex >= 0 ? (\n \n
      \n \n \n \n \n \n \n
      \n
      \n
      \n Previous\n
      \n
      \n {nav[currentIndex - 1].title}\n
      \n
      \n \n ) : null}\n {nextInfo.url && currentIndex >= 0 ? (\n \n
      \n
      \n Next\n
      \n
      \n {nav[currentIndex + 1] && nav[currentIndex + 1].title}\n
      \n
      \n
      \n \n \n \n \n \n \n
      \n \n ) : null}\n
      \n );\n};\n\nexport default NextPrevious;\n","import styled from '@emotion/styled';\n\nexport const StyledHeading = styled('h1')`\n font-size: 32px;\n line-height: 1.5;\n font-weight: 500;\n border-left: 2px solid #2dc4f3;\n padding: 0 16px;\n flex: 1;\n margin-top: 0;\n padding-top: 0;\n color: ${props => props.theme.colors.heading};\n`;\n\nexport const Edit = styled('div')`\n padding: 1rem 1.5rem;\n text-align: right;\n\n a {\n font-size: 14px;\n font-weight: 500;\n line-height: 1em;\n text-decoration: none;\n color: #555;\n border: 1px solid rgb(211, 220, 228);\n cursor: pointer;\n border-radius: 3px;\n transition: all 0.2s ease-out 0s;\n text-decoration: none;\n color: rgb(36, 42, 49);\n background-color: rgb(255, 255, 255);\n box-shadow: rgba(116, 129, 141, 0.1) 0px 1px 1px 0px;\n height: 30px;\n padding: 5px 16px;\n &:hover {\n background-color: rgb(245, 247, 249);\n }\n }\n`;\n\nexport const StyledMainWrapper = styled.div`\n max-width: 750px;\n color: ${props => props.theme.colors.text};\n\n ul,\n ol {\n -webkit-padding-start: 40px;\n -moz-padding-start: 40px;\n -o-padding-start: 40px;\n margin: 24px 0px;\n padding: 0px 0px 0px 2em;\n\n li {\n font-size: 16px;\n line-height: 1.8;\n font-weight: 400;\n }\n }\n\n a {\n transition: color 0.15s;\n color: ${props => props.theme.colors.link};\n }\n\n code {\n border: 1px solid #ede7f3;\n border-radius: 4px;\n padding: 2px 6px;\n font-size: 0.9375em;\n\n background: ${props => props.theme.colors.background};\n }\n\n @media (max-width: 767px) {\n padding: 0 15px;\n }\n`;\n","import React, { useEffect, useState } from 'react';\n\nconst MobileScrollUpButton = () => {\n const [hideButton, setHideButton] = useState(true);\n\n const [prevScrollHeight, setPrevScrollHeight] = useState(0);\n\n const showOrHide = () => {\n window.scrollY > prevScrollHeight ? setHideButton(true) : setHideButton(false);\n setPrevScrollHeight(window.scrollY);\n };\n\n useEffect(() => {\n window.addEventListener('scroll', showOrHide);\n //Make button disappear once scroll to top is complete\n window.onscroll = () => {\n if (window.scrollY === 0) {\n setHideButton(true);\n setPrevScrollHeight(0);\n }\n };\n return function cleanup() {\n window.removeEventListener('scroll', showOrHide);\n };\n });\n\n const handleClick = () => {\n window.scroll(0, 0);\n };\n\n return (\n \n );\n};\n\nexport default MobileScrollUpButton;\n","import React, { Component } from 'react';\nimport Helmet from 'react-helmet';\nimport { graphql, Link } from 'gatsby';\nimport MDXRenderer from 'gatsby-plugin-mdx/mdx-renderer';\n\nimport { Layout } from '$components';\nimport NextPrevious from '../components/NextPrevious';\nimport config from '../../config';\nimport { Edit, StyledHeading, StyledMainWrapper } from '../components/styles/Docs';\n\nimport 'katex/dist/katex.min.css';\nimport MobileScrollUpButton from './MobileScrollUpButton';\n\nconst forcedNavOrder = config.sidebar.forcedNavOrder;\n\nexport default class MDXRuntimeTest extends Component {\n render() {\n const { data } = this.props;\n\n if (!data) {\n return null;\n }\n if (!data.site) {\n //markdown page not found\n return (\n \n

      Page not found

      \n

      \n Go home\n

      \n
      \n );\n }\n const {\n allMdx,\n mdx,\n site: {\n siteMetadata: { docsLocation, title },\n },\n } = data;\n\n const navItems = allMdx.edges\n .map(({ node }) => node.fields.slug)\n .filter(slug => slug !== '/')\n .sort()\n .reduce(\n (acc, cur) => {\n if (forcedNavOrder.find(url => url === cur)) {\n return { ...acc, [cur]: [cur] };\n }\n\n let prefix = cur.split('/')[1];\n\n if (config.gatsby && config.gatsby.trailingSlash) {\n prefix = prefix + '/';\n }\n\n if (prefix && forcedNavOrder.find(url => url === `/${prefix}`)) {\n return { ...acc, [`/${prefix}`]: [...acc[`/${prefix}`], cur] };\n } else {\n return { ...acc, items: [...acc.items, cur] };\n }\n },\n { items: [] }\n );\n\n const nav = forcedNavOrder\n .reduce((acc, cur) => {\n return acc.concat(navItems[cur]);\n }, [])\n .concat(navItems.items)\n .map(slug => {\n if (slug) {\n const { node } = allMdx.edges.find(({ node }) => node.fields.slug === slug);\n\n return { title: node.fields.title, url: node.fields.slug };\n }\n });\n\n // meta tags\n const metaTitle = mdx.frontmatter.metaTitle;\n\n const metaDescription = mdx.frontmatter.metaDescription;\n\n let canonicalUrl = config.gatsby.siteUrl;\n\n canonicalUrl =\n config.gatsby.pathPrefix !== '/' ? canonicalUrl + config.gatsby.pathPrefix : canonicalUrl;\n canonicalUrl = canonicalUrl + mdx.fields.slug;\n\n return (\n \n \n {metaTitle ? {metaTitle} : null}\n {metaTitle ? : null}\n {metaDescription ? : null}\n {metaTitle ? : null}\n {metaDescription ? : null}\n {metaTitle ? : null}\n {metaDescription ? (\n \n ) : null}\n \n \n
      \n {mdx.fields.title}\n \n
      \n \n {mdx.body}\n \n
      \n \n
      \n \n
      \n );\n }\n}\n\nexport const pageQuery = graphql`\n query($id: String!) {\n site {\n siteMetadata {\n title\n docsLocation\n }\n }\n mdx(fields: { id: { eq: $id } }) {\n fields {\n id\n title\n slug\n }\n body\n tableOfContents\n parent {\n ... on File {\n relativePath\n }\n }\n frontmatter {\n metaTitle\n metaDescription\n }\n }\n allMdx {\n edges {\n node {\n fields {\n slug\n title\n }\n }\n }\n }\n }\n`;\n","var isBrowser = \"object\" !== 'undefined';\n\nfunction getRegisteredStyles(registered, registeredStyles, classNames) {\n var rawClassName = '';\n classNames.split(' ').forEach(function (className) {\n if (registered[className] !== undefined) {\n registeredStyles.push(registered[className]);\n } else {\n rawClassName += className + \" \";\n }\n });\n return rawClassName;\n}\n\nvar insertStyles = function insertStyles(cache, serialized, isStringTag) {\n var className = cache.key + \"-\" + serialized.name;\n\n if ( // we only need to add the styles to the registered cache if the\n // class name could be used further down\n // the tree but if it's a string tag, we know it won't\n // so we don't have to add it to registered cache.\n // this improves memory usage since we can avoid storing the whole style string\n (isStringTag === false || // we need to always store it if we're in compat mode and\n // in node since emotion-server relies on whether a style is in\n // the registered cache to know whether a style is global or not\n // also, note that this check will be dead code eliminated in the browser\n isBrowser === false && cache.compat !== undefined) && cache.registered[className] === undefined) {\n cache.registered[className] = serialized.styles;\n }\n\n if (cache.inserted[serialized.name] === undefined) {\n var current = serialized;\n\n do {\n var maybeStyles = cache.insert(\".\" + className, current, cache.sheet, true);\n current = current.next;\n } while (current !== undefined);\n }\n};\n\nexport { getRegisteredStyles, insertStyles };","/**\n * Prism: Lightweight, robust, elegant syntax highlighting\n * MIT license http://www.opensource.org/licenses/mit-license.php/\n * @author Lea Verou http://lea.verou.me\n */\n\n/**\n * prism-react-renderer:\n * This file has been modified to remove:\n * - globals and window dependency\n * - worker support\n * - highlightAll and other element dependent methods\n * - _.hooks helpers\n * - UMD/node-specific hacks\n * It has also been run through prettier\n */\nvar Prism = function () {\n var uniqueId = 0;\n var _ = {\n util: {\n encode: function encode(tokens) {\n if (tokens instanceof Token) {\n return new Token(tokens.type, _.util.encode(tokens.content), tokens.alias);\n } else if (_.util.type(tokens) === \"Array\") {\n return tokens.map(_.util.encode);\n } else {\n return tokens.replace(/&/g, \"&\").replace(/ text.length) {\n // Something went terribly wrong, ABORT, ABORT!\n return;\n }\n\n if (str instanceof Token) {\n continue;\n }\n\n if (greedy && i != strarr.length - 1) {\n pattern.lastIndex = pos;\n var match = pattern.exec(text);\n\n if (!match) {\n break;\n }\n\n var from = match.index + (lookbehind ? match[1].length : 0),\n to = match.index + match[0].length,\n k = i,\n p = pos;\n\n for (var len = strarr.length; k < len && (p < to || !strarr[k].type && !strarr[k - 1].greedy); ++k) {\n p += strarr[k].length; // Move the index i to the element in strarr that is closest to from\n\n if (from >= p) {\n ++i;\n pos = p;\n }\n } // If strarr[i] is a Token, then the match starts inside another Token, which is invalid\n\n\n if (strarr[i] instanceof Token) {\n continue;\n } // Number of tokens to delete and replace with the new match\n\n\n delNum = k - i;\n str = text.slice(pos, p);\n match.index -= pos;\n } else {\n pattern.lastIndex = 0;\n var match = pattern.exec(str),\n delNum = 1;\n }\n\n if (!match) {\n if (oneshot) {\n break;\n }\n\n continue;\n }\n\n if (lookbehind) {\n lookbehindLength = match[1] ? match[1].length : 0;\n }\n\n var from = match.index + lookbehindLength,\n match = match[0].slice(lookbehindLength),\n to = from + match.length,\n before = str.slice(0, from),\n after = str.slice(to);\n var args = [i, delNum];\n\n if (before) {\n ++i;\n pos += before.length;\n args.push(before);\n }\n\n var wrapped = new Token(token, inside ? _.tokenize(match, inside) : match, alias, match, greedy);\n args.push(wrapped);\n\n if (after) {\n args.push(after);\n }\n\n Array.prototype.splice.apply(strarr, args);\n\n if (delNum != 1) {\n _.matchGrammar(text, strarr, grammar, i, pos, true, token);\n }\n\n if (oneshot) {\n break;\n }\n }\n }\n }\n },\n hooks: {\n add: function add() {},\n run: function run(name, env) {}\n },\n tokenize: function tokenize(text, grammar, language) {\n var strarr = [text];\n var rest = grammar.rest;\n\n if (rest) {\n for (var token in rest) {\n grammar[token] = rest[token];\n }\n\n delete grammar.rest;\n }\n\n _.matchGrammar(text, strarr, grammar, 0, 0, false);\n\n return strarr;\n }\n };\n\n var Token = _.Token = function (type, content, alias, matchedStr, greedy) {\n this.type = type;\n this.content = content;\n this.alias = alias; // Copy of the full string this token was created from\n\n this.length = (matchedStr || \"\").length | 0;\n this.greedy = !!greedy;\n };\n\n Token.stringify = function (o, language, parent) {\n if (typeof o == \"string\") {\n return o;\n }\n\n if (_.util.type(o) === \"Array\") {\n return o.map(function (element) {\n return Token.stringify(element, language, o);\n }).join(\"\");\n }\n\n var env = {\n type: o.type,\n content: Token.stringify(o.content, language, parent),\n tag: \"span\",\n classes: [\"token\", o.type],\n attributes: {},\n language: language,\n parent: parent\n };\n\n if (o.alias) {\n var aliases = _.util.type(o.alias) === \"Array\" ? o.alias : [o.alias];\n Array.prototype.push.apply(env.classes, aliases);\n }\n\n var attributes = Object.keys(env.attributes).map(function (name) {\n return name + '=\"' + (env.attributes[name] || \"\").replace(/\"/g, \""\") + '\"';\n }).join(\" \");\n return \"<\" + env.tag + ' class=\"' + env.classes.join(\" \") + '\"' + (attributes ? \" \" + attributes : \"\") + \">\" + env.content + \"\";\n };\n\n return _;\n}();\n/* This content is auto-generated to include some prismjs language components: */\n\n/* \"prismjs/components/prism-markup\" */\n\n\nPrism.languages.markup = {\n 'comment': //,\n 'prolog': /<\\?[\\s\\S]+?\\?>/,\n 'doctype': {\n // https://www.w3.org/TR/xml/#NT-doctypedecl\n pattern: /\"'[\\]]|\"[^\"]*\"|'[^']*')+(?:\\[(?:[^<\"'\\]]|\"[^\"]*\"|'[^']*'|<(?!!--)|)*\\]\\s*)?>/i,\n greedy: true,\n inside: {\n 'internal-subset': {\n pattern: /(\\[)[\\s\\S]+(?=\\]>$)/,\n lookbehind: true,\n greedy: true,\n inside: null // see below\n\n },\n 'string': {\n pattern: /\"[^\"]*\"|'[^']*'/,\n greedy: true\n },\n 'punctuation': /^$|[[\\]]/,\n 'doctype-tag': /^DOCTYPE/,\n 'name': /[^\\s<>'\"]+/\n }\n },\n 'cdata': //i,\n 'tag': {\n pattern: /<\\/?(?!\\d)[^\\s>\\/=$<%]+(?:\\s(?:\\s*[^\\s>\\/=]+(?:\\s*=\\s*(?:\"[^\"]*\"|'[^']*'|[^\\s'\">=]+(?=[\\s>]))|(?=[\\s/>])))+)?\\s*\\/?>/,\n greedy: true,\n inside: {\n 'tag': {\n pattern: /^<\\/?[^\\s>\\/]+/,\n inside: {\n 'punctuation': /^<\\/?/,\n 'namespace': /^[^\\s>\\/:]+:/\n }\n },\n 'attr-value': {\n pattern: /=\\s*(?:\"[^\"]*\"|'[^']*'|[^\\s'\">=]+)/,\n inside: {\n 'punctuation': [{\n pattern: /^=/,\n alias: 'attr-equals'\n }, /\"|'/]\n }\n },\n 'punctuation': /\\/?>/,\n 'attr-name': {\n pattern: /[^\\s>\\/]+/,\n inside: {\n 'namespace': /^[^\\s>\\/:]+:/\n }\n }\n }\n },\n 'entity': [{\n pattern: /&[\\da-z]{1,8};/i,\n alias: 'named-entity'\n }, /&#x?[\\da-f]{1,8};/i]\n};\nPrism.languages.markup['tag'].inside['attr-value'].inside['entity'] = Prism.languages.markup['entity'];\nPrism.languages.markup['doctype'].inside['internal-subset'].inside = Prism.languages.markup; // Plugin to make entity title show the real entity, idea by Roman Komarov\n\nPrism.hooks.add('wrap', function (env) {\n if (env.type === 'entity') {\n env.attributes['title'] = env.content.replace(/&/, '&');\n }\n});\nObject.defineProperty(Prism.languages.markup.tag, 'addInlined', {\n /**\n * Adds an inlined language to markup.\n *\n * An example of an inlined language is CSS with `PURPOSE

      PURPOSE

      This guide was developed for technical editors, but will help all AFOTEC +personnel write and edit final test plans and reports that meet our goal +of providing relevant, credible, and timely feedback to the acquisition +community and Air Force leaders.

      *Note : This editing guide applies to final AFOTEC test plans and +reports. It is not designed to take the place of, nor conflict with, +writing guidance for other products, such as OPRs/EPRs, memos, or +other AFOTEC test products. Please adhere to the writing guidelines, +authorities, and templates that apply to the specific product you are +producing.*

      This guide follows the grammar and punctuation rules from the following +authorities: Air Force Handbook (AFH) 33-337, Tongue and Quill , 27 +May 15 (Incorporating Change 1, 19 Nov 15), and the Air University +Press, Air University Style and Author Guide (Maxwell AFB AL, 2005), +unless otherwise indicated. While you should explore and review +reference materials you feel are helpful in developing your editing +skills, the rules outlined herein take precedence over other +writing/editing guidance.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices/index.html b/sites/oteguide/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices/index.html new file mode 100644 index 00000000..1a35e346 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices/index.html @@ -0,0 +1,30 @@ +Executive Summary, Body, and Appendices

      Executive Summary, Body, and Appendices

      Edit the executive summary, the body, and the appendices as separate +documents. The appendices will be created first because they contain the +technical information and details of the assessment or evaluation. In +the appendices, symbols, equations, and technical terms are appropriate, +just as they are in tables. The body is a synopsis of the information +contained in the appendices. It is written as a formal document in which +symbols, abbreviations, and technical terms are spelled out and is +intended for a wider audience.

      Executive Summary . While the executive summary is usually written +last, it is the most crucial part of the document because it is intended +for and read by the wider acquisition community. If written as intended, +the executive summary will capture the critical components of the +assessment or evaluation in a brief but thorough summary.

      The executive summary is written from the Commander's perspective, as +though he or she is personally addressing the audience. It describes the +system under test, type of test, decision maker, and decision supported, +and summarizes the system's effectiveness, suitability, mission +capability, critical deficiencies, and AFOTEC's recommendations (in +order of their significance) to correct those deficiencies. It is +written as a formal document in which symbols, abbreviations, and +technical terms are spelled out, and although it is acceptable to use +acronyms in the executive summary, writers should limit their use to +promote a smoother read.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/1-4-Consistency-is-Key/index.html b/sites/oteguide/editing_reports_guide/1-4-Consistency-is-Key/index.html new file mode 100644 index 00000000..26105c86 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/1-4-Consistency-is-Key/index.html @@ -0,0 +1,13 @@ +Consistency is Key

      Consistency is Key

      In regards to subjective writing preferences, ensure the author applies +them consistently, i.e., benchmark, bench mark, and bench-mark should +not appear in the same document. When such variations occur, choose the +most frequently used or best option and change other instances to match.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/1-5-One-Voice/index.html b/sites/oteguide/editing_reports_guide/1-5-One-Voice/index.html new file mode 100644 index 00000000..503c0d9b --- /dev/null +++ b/sites/oteguide/editing_reports_guide/1-5-One-Voice/index.html @@ -0,0 +1,14 @@ +One Voice

      One Voice

      Several different test team members collaborate on writing each plan or +report. Edit the mechanics of each part of the document separately, but +it is important to read the plan or report as a whole document to +confirm that it reads as "one voice" rather than as a conglomeration of +different sections by different authors.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/1-6-Templates/index.html b/sites/oteguide/editing_reports_guide/1-6-Templates/index.html new file mode 100644 index 00000000..e74b3d4e --- /dev/null +++ b/sites/oteguide/editing_reports_guide/1-6-Templates/index.html @@ -0,0 +1,24 @@ +Templates

      Templates

      Templates for each type of test plan and report are posted on +SharePoint. AFOTEC encourages the use of templates because they are a +good guide to ensure the test team includes all necessary planning and +reporting elements. Test teams may find it necessary to deviate from the +templates and include different information or exclude information not +pertinent to their program. They should feel free to innovate as needed +as long as they meet the ultimate goal of creating a comprehensive +document that meets AFOTEC's planning and reporting obligations. +Templates include blue instructional text to assist the test team in +populating various sections, but if writers have questions not covered +in the instructional text, have them contact A-3 for additional +guidance.

      The templates are dynamic and change as guidance and reporting +requirements change. A-3 attempts to make template changes in real time, +but this is not always possible. If you are unsure whether a template +reflects the latest changes, contact the A-3 technical editor.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/1-7-Microsoft-Word-Options/index.html b/sites/oteguide/editing_reports_guide/1-7-Microsoft-Word-Options/index.html new file mode 100644 index 00000000..29c50b03 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/1-7-Microsoft-Word-Options/index.html @@ -0,0 +1,17 @@ +Microsoft Word Options

      Microsoft Word Options

      Set the following "options" to ensure Microsoft Word works in harmony +with our templates. Setting these options from the start will solve a +lot of formatting problems before they begin.

      Display:

      • All formatting marks

      Proofing:

      • AutoCorrect: remove ALL checks

      • AutoFormat: remove all checks except for "smart quotes" ( Note : +AFOTEC does not use superscript for ordinals; superscript is only +used for fractional factorial notations in factor tables)

      • AutoFormat As You Type: remove all checks except for "smart quotes"

      • Spelling and Grammar Settings:

        • Grammar and style options: Require (comma: always); +(punctuation: inside); (spaces: 1)

      Advanced:

      • Enable Click and Type

      • Default Paragraph Style: AFOTEC Body

      • Insert pictures "in line with text"

      • Cut, copy, and paste

        • Show Paste Options button when content is pasted

        • Use smart cut and paste (Word 2002-2010)

        • Pasting between documents when style definitions conflict---Use +Destination Styles (Default)

      • Show Bookmarks

      • Field Shading--always

      • Style area pane width in Draft and Outline views--2"

      • Compatibility should be Word 2010 (DO NOT check any of the layout +options)

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/1-8-Focus-Areas/index.html b/sites/oteguide/editing_reports_guide/1-8-Focus-Areas/index.html new file mode 100644 index 00000000..42e814fa --- /dev/null +++ b/sites/oteguide/editing_reports_guide/1-8-Focus-Areas/index.html @@ -0,0 +1,12 @@ +Focus Areas

      Focus Areas

      Enforce the following standards to ensure AFOTEC produces uniform +documents. These areas are not listed in order of importance, but are an +overall view of the editing process.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/1-9-Styles/index.html b/sites/oteguide/editing_reports_guide/1-9-Styles/index.html new file mode 100644 index 00000000..af5ac265 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/1-9-Styles/index.html @@ -0,0 +1,40 @@ +Styles

      Styles

      AFOTEC templates are designed with unique Microsoft Word styles that +work in tandem with the page numbering and the table of contents. That +is why it is critical to ensure the styles are not removed or corrupted +during the writing process. Unless a writer deliberately changes or +corrupts a style by deleting a heading or subheading, the templates are +user-friendly and low maintenance. The body style is designed to be +"justified" and to have the optimal amount of white space to make it +easy to read and distinguish between paragraphs. AFOTEC uses one space +after end-of-sentence punctuation because that prevents excessive +spreading between letters and words when using justified alignment .

      Problems can arise when writers copy and paste information from other +sources into the template document, which can introduce styles from that +source. In those cases, you will have to clear the styles and reapply +the appropriate AFOTEC styles. Teach writers to use the "use destination +styles" option on the pasting clipboard to eliminate this problem.

      To confirm the styles are correct and uncorrupted, open the document in +Draft view. Reapply appropriate AFOTEC styles where necessary. Modify +corrupted styles if it is something simple to correct such as left align +versus justified, tab spacing, font size, etc. If more than one style is +corrupt or you cannot modify them easily, use the following steps to +import styles from a document in which AFOTEC styles are sound and +uncorrupted (i.e., plan or report template):

      • Click on the third icon in bottom left corner of "Styles" pane +called "Manage Styles."

      • Click "Import/Export" on bottom left corner of the Edit tab.

      • On the right side pane of the "Organizer" window that opens, close +the "In Normal" file and open a document with all the uncorrupted +AFOTEC styles by clicking "open file." Locate and open that file. +All the styles from that document will populate the right side pane.

      • Copy all AFOTEC styles you wish to replace from the right side to +the "to Document 1" left side. (Note: if you have set your "Normal" +template to contain AFOTEC styles [recommended], just copy the +necessary styles from there to the "to Document 1" left side and +omit the step of closing the "Normal" file and finding a file with +uncorrupted AFOTEC styles.)

      • Click "yes" or "yes to all" when prompted as to whether you want to +overwrite the existing styles in the document.

      • Close the "Normal" file or the file you copied styles from on the +right side pane.

      • Close out of the "Organizer" window.

      • The corrected styles will appear in your style pane.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/2-1-Acronyms/index.html b/sites/oteguide/editing_reports_guide/2-1-Acronyms/index.html new file mode 100644 index 00000000..ade84bbd --- /dev/null +++ b/sites/oteguide/editing_reports_guide/2-1-Acronyms/index.html @@ -0,0 +1,45 @@ +Acronyms

      Acronyms

      Define an acronym the first time it appears in each section (i.e., +executive summary, body, appendices [as a whole, not each appendix as a +separate section]), then use the acronym thereafter. Edit these three +distinct parts of the plan or report as separate documents.

      Add all acronyms in the document to the acronym table in the designated +appendix. If an acronym is only used one or two times, delete it from +the document and the acronym table and spell it out.

      Define acronyms in tables and figures in the acronym table, not within +the table or figure ; the only exception is a measure table that +displays a "mean" as the metric. To help readers make the connection to +a standard term (i.e., "mean time between failures"), add the standard +acronym in parenthesis following the measure title, then define it below +"*KPP or supports KPP or \^ Identified Standard" if applicable (or in a +merged row at the bottom of the table as shown in the following +example). Then, add the acronym to the acronym table.

      Example:

      (FOUO)
      Operational Capability: Reliability
      MeasureMetricThreshold
      MOS 3.8: Time Between Failures (MTBF)Mean>= 8,736 hours
      MTBF–mean time between failures

      Some acronyms are more easily recognized than the words they represent +(e.g., NASA, NATO). In those cases, do not remove the acronym from the +document, nor from the acronym table even if it is used only once. This +is a judgment call so consult your test team's SME, TD, or TA if in +doubt as to whether you should remove a particular acronym.

      Acronyms use the same vowel/consonant rules as regular words (i.e., use +"a" before a consonant; use "an" before a vowel), except that with +acronyms the beginning "sound" rather than the beginning "letter" is +what determines the article you will use. If the beginning sound is a +vowel sound, you will use "an." If it is a consonant sound, use "a."

      Examples:

      • an OA report (beginning sound--long o vowel sound)

      • a NASA rocket (beginning sound--consonant n)

      • an MOT&E (beginning sound--short e vowel sound)

      Follow regular capitalization rules when defining acronyms and +capitalize only those words that are proper nouns. The only exception to +this rule is the acronym table, which should use the following "title +case" capitalization rules for uniformity:

      • Capitalize the principal words, including prepositions and +conjunctions of four or more letters.

      • Capitalize an article---the, a, an---or words of fewer than four +letters if it is the first or last word in a title.

      Performing the acronym scrub is the most time-intensive part of the +edit, but it must be done, and is ultimately the technical editor's +responsibility. Do not cheat!

      Perform a spell check, but before you begin, go into Microsoft Word +options/Proofing and uncheck the Custom Dictionary "Custom Dic" button; +select "English (United States)" as your language.

      Make sure each acronym spell-check catches was defined in the acronym +table. If not, add it and define it. Begin with the first acronym in the +table and perform the following:

      • Highlight the acronym

      • Copy it (ctrl c)

      • Open find (ctrl f)

      • Paste (ctrl v)

      • Go to top of doc (ctrl home)

      • Enter "find next"

      • Make sure the acronym is defined the first time it shows up in the +body and appendices, and that the definition is the same as what is +in the acronym table

      • Repeat this process for each acronym

      In addition to this, remove acronyms from the table that were not used +in the plan or report. The acronyms provided in the templates will not +necessarily pertain to the document you are editing.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/2-2-Commas/index.html b/sites/oteguide/editing_reports_guide/2-2-Commas/index.html new file mode 100644 index 00000000..0d1c69d5 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/2-2-Commas/index.html @@ -0,0 +1,15 @@ +Commas

      Commas

      Technical writing requires the use of the "serial" comma (sometimes +called the oxford comma), which is the comma used immediately preceding +a coordinating conjunction (usually, and, or, or sometimes nor), or the +final item in a series of three or more items. This is important because +the meaning of a sentence can change when commas are omitted or used +incorrectly.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/2-3-Next-Page-and-Page-Breaks/index.html b/sites/oteguide/editing_reports_guide/2-3-Next-Page-and-Page-Breaks/index.html new file mode 100644 index 00000000..de900ba8 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/2-3-Next-Page-and-Page-Breaks/index.html @@ -0,0 +1,22 @@ +Next Page and Page Breaks

      Next Page and Page Breaks

      Use "next page" breaks when you separate a page to change its +orientation from portrait to landscape, or when you create a blank page +or a new appendix. Use regular "page" breaks versus "next page" breaks +between new sections in the body and between measures in appendix B. The +frugal use of "next page" breaks prevents the problem of a document +containing too many sections, which inhibits printing a customized range +of pages within a document.

      NEVER use "continuous" page breaks in AFOTEC documents. "Continuous" +page breaks are hard to remove. If you try to delete them, you will +begin a domino affect of formatting difficulties. Use the following +method to remove "continuous" page breaks successfully:

      • Place cursor at beginning of document

      • Scroll to end of document while holding mouse button down to select +everything (do not use Ctrl A) (this can take a while on a long +document, but there is no short cut so be patient)

      • Hold down shift button and do a left click on mouse

      • Go to Page Layout/Page Setup

      • On layout pick "New Page"

      • And "selected sections"

      • Push OK button

      You should have all "next page" page breaks in place of the "continuous" +page breaks when you complete this process.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/2-4-Headers-and-Footers/index.html b/sites/oteguide/editing_reports_guide/2-4-Headers-and-Footers/index.html new file mode 100644 index 00000000..1276f00d --- /dev/null +++ b/sites/oteguide/editing_reports_guide/2-4-Headers-and-Footers/index.html @@ -0,0 +1,23 @@ +Headers and Footers

      Headers and Footers

      Headers. All headers on AFOTEC plans and reports should be connected +("linked to previous") with the exception of the SF298 (only applicable +to reports). This enables consistent classification markings on every +page.

      Footers. All footers on AFOTEC plans and reports should be connected, +with the exception of the cover page (which is not numbered) and the +SF298 (only applicable to reports). This enables consistent +classification markings on every page.

      Header/Footer on SF298. Keep information on the Standard Form (SF) 298 +at the unclassified level whenever possible. It will usually have a +different classification marking or none at all. However, even when its +classification is the same as that of the plan or report, do not connect +the header or footer because the form also requires different margins +and header/footer settings and does not have page numbers (technically, +it is not part of the report and should not be included in the number of +pages in a report).

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/2-5-Page-Numbering/index.html b/sites/oteguide/editing_reports_guide/2-5-Page-Numbering/index.html new file mode 100644 index 00000000..fcb096be --- /dev/null +++ b/sites/oteguide/editing_reports_guide/2-5-Page-Numbering/index.html @@ -0,0 +1,15 @@ +Page Numbering

      Page Numbering

      The templates were designed with automatic page numbering that populates +the table of contents automatically. However, when you add a "next page" +break, you may have to click into the footer and go to "format page +numbers." Click the radial button and choose "continue from previous +section" so that the page numbering will continue instead of restarting +at page 1.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/2-6-Blank-Pages/index.html b/sites/oteguide/editing_reports_guide/2-6-Blank-Pages/index.html new file mode 100644 index 00000000..48aa926b --- /dev/null +++ b/sites/oteguide/editing_reports_guide/2-6-Blank-Pages/index.html @@ -0,0 +1,18 @@ +Blank Pages

      Blank Pages

      Insert or remove a blank page (i.e., Page intentionally blank) as +necessary so that the following pages are always right facing (which +will present on the left side of the screen in the 2-page layout view):

      • Executive Summary

      • Table of Contents

      • First page of the body of the report, which begins with +"Introduction"

      • First page of Appendix A

      The SF298 Report Documentation Page (applicable for reports only) should +always be left facing, (which will appear on the right side of the +screen in the 2-page layout view) to ensure the form stays on the front +and back of the same page.

      A blank page should continue the page numbering of the section it +follows (A-12 is followed by the blank page A-13). The section that +follows the blank page will begin with page number one (B-1).

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/2-7-Capitalization/index.html b/sites/oteguide/editing_reports_guide/2-7-Capitalization/index.html new file mode 100644 index 00000000..9ce4487a --- /dev/null +++ b/sites/oteguide/editing_reports_guide/2-7-Capitalization/index.html @@ -0,0 +1,26 @@ +Capitalization

      Capitalization

      Use capitalization appropriately. Writers have a tendency to capitalize +nonspecific titles of documents and things, even acronym definitions.

      Capitalize:

      • The title of a document when used in conjunction with the program's +proper name:

        • "initial operational test and evaluation" becomes "RQ-4 Initial +Operational Test and Evaluation"
      • The production decision when used in conjunction with the decision +maker's proper title:

        • "full-rate production decision" becomes the "Under Secretary of +Defense for Acquisition, Technology and Logistics' (USD[AT&L]) +Full-Rate Production decision"
      • Cross-references (table or figure) when used at the beginning of a +sentence, but not in the middle of a sentence:

        • "Table (Figure) 1 contains the details."

        • "...as shown in table (figure) X."

      Frame COIs as questions. Write them as a sentence punctuated with a +question mark ( Example : COI 1: Does the KC-46 support refueling?). +Write MOEs and MOSs in title case ( Example : MOE 1.8: Percent of +Reports and Queries Generated Successfully).

      The acronym list is considered a table. Use title case capitalization +for style continuity. In all other parts of the document, follow regular +capitalization rules for words acronyms represent. Joint Publication +(JP) 1-02, Department of Defense Dictionary of Military and Associated +Terms , 12 Apr 01 (amended through Apr 10), Appendix A, contains a +comprehensive list of abbreviations and acronyms. Refer to this +publication for clarification on when to, or not to, capitalize words.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases/index.html b/sites/oteguide/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases/index.html new file mode 100644 index 00000000..3f2ace52 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases/index.html @@ -0,0 +1,16 @@ +Citing Air Force (or Other Military) Bases

      Citing Air Force (or Other Military) Bases

      Verify military bases are cited properly. The first time a base is +mentioned, spell out the name, type of base, and state or country (ex: +Edwards Air Force Base, California; Ramstein Air Base, Germany; Royal +Air Force Lakenheath, England). Thereafter, use the name of the base +only, or the name in conjunction with the type of base (ex: Edwards or +Edwards AFB; Ramstein or Ramstein AB; Lakenheath or RAF Lakenheath). In +tables and figures, use only the abbreviated form.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/2-9-Vertical-Lists/index.html b/sites/oteguide/editing_reports_guide/2-9-Vertical-Lists/index.html new file mode 100644 index 00000000..431df112 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/2-9-Vertical-Lists/index.html @@ -0,0 +1,18 @@ +Vertical Lists

      Vertical Lists

      Validate proper punctuation, capitalization, and structure of vertical +(bulleted) lists, depending on how the information was structured.

      Example 1:

      The test team will assess the following capabilities:

      • Data conversion

      • Upgrade integration

      • Operability

      Example 2:

      The test team will assess the

      • multiple data conversions necessary to transition from the legacy +system to the upgraded system;

      • integration of the upgrade at every location (all six Air Force +bases); and

      • operability at Peterson Air Force Base, Colorado; Kirtland Air Force +Base, New Mexico; and Wright-Patterson Air Force Base, Ohio.

      The type of vertical list used will depend on the complexity and length +of the ideas presented. Example 1 is good for a simple list. Example 2 +is a good choice for a complex sentence that contains various types of +punctuation and could be confusing when expressed in one very long, +linear sentence.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/3-1-Numbering-Tables-and-Figures/index.html b/sites/oteguide/editing_reports_guide/3-1-Numbering-Tables-and-Figures/index.html new file mode 100644 index 00000000..91956baa --- /dev/null +++ b/sites/oteguide/editing_reports_guide/3-1-Numbering-Tables-and-Figures/index.html @@ -0,0 +1,15 @@ +Numbering Tables and Figures

      Numbering Tables and Figures

      Number tables and figures sequentially and cross-reference them in the +preceding text. In the body, number tables and figures consecutively +throughout (Use Navigation Pane on View Tab). Then, restart the table +and figure numbering in each appendix, adding the appendix letter as a +prefix. For example, "Table A-5" would be the fifth table in "Appendix +A."

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/3-2-Tables/index.html b/sites/oteguide/editing_reports_guide/3-2-Tables/index.html new file mode 100644 index 00000000..ef7fd35e --- /dev/null +++ b/sites/oteguide/editing_reports_guide/3-2-Tables/index.html @@ -0,0 +1,32 @@ +Tables

      Tables

      The most important aspect of editing tables is to ensure the contents +reflect the information in the accompanying text accurately. Check each +of the following standards:

      • Apply AFOTEC Table Header + Rating and AFOTEC Table Text styles

      • Verify table properties: preferred width: 100%; default cell +margins: top/bottom: 0", left/right: 0.08"; borders: 1 pt

      • Align cells left/center

      • Add classification by inserting a merged row above the header +row--apply the AFOTEC Caption + Class style to classification +portion marking

      • Ensure classification and header rows repeat by highlighting +classification and header rows and selecting "repeat header rows" in +"Layout" tab

      • Ensure tables break across the next page when necessary; avoid +excess white space whenever possible, particularly in classified +documents

      • Make sure ratings in tables match ratings in accompanying narrative

      • Ensure changes made to COIs, MOEs, and MOSs are rolled into all the +tables (especially the evaluation summary chart or ESC) in which +they appear, and into affected narratives

      • Ensure ratings are uniform in color and size (copy and paste from +template ratings)

      • Confirm tables use percent sign, dollar sign, numbers, and other +symbols

      • Do not define acronyms within the table except when it includes a +standard mean term in parenthesis (i.e., MTBF)--add the acronym and +its definition below "*KPP or supports KPP or \^ Identified +Standard" if applicable (or in a merged row at the bottom of the +table)--add the acronym to the acronym table

      • Align numbers on decimal (use decimal tab on ruler).

      • Add footnotes to the bottom of table in an inserted/merged row or +shift/enter below KPP or Identified Standard, if applicable.

      • Eliminate repetitive symbols or labels (e.g., $, %, hrs) by adding +them to the table header and deleting them from text cells, when +appropriate

      • Capitalize cross-references at the beginning of a sentence: "Table 1 +contains the details." Do not capitalize them in the middle of a +sentence: "...as shown in table X."

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/3-3-Figures/index.html b/sites/oteguide/editing_reports_guide/3-3-Figures/index.html new file mode 100644 index 00000000..cfc76788 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/3-3-Figures/index.html @@ -0,0 +1,26 @@ +Figures

      Figures

      Ensure contents of a figure reflects the information in the accompanying +text accurately. Check each of the following standards:

      • Apply AFOTEC Caption + Class style to caption and classification

      • Apply 1-pt black border

      • Do not copy/paste a figure from another document, but save it as a +".png" or ".jpg" file and insert it as a picture. Alternatively, use +the "snip and sketch" tool to save any image--the image will remain +sharp and clear because it is a scan of the image rather than a +conversion. Before "capturing" your image, unselect the "show all +formatting marks" so that you will not capture the marks with the +picture.

      • Do not duplicate figures in the body and appendices. The body is a +concise presentation of the most important facts taken from the +appendices. Appendices contain the comprehensive details and are the +better choice for detailed figures describing a system or test.

      • Eliminate text boxes, symbols, figures, etc., inserted on top of +figures by following the procedures above for converting pasted +pictures to a .png or .jpg file. Reinsert them as a picture with all +add-ons captured as part of the picture.

      • Ensure all acronyms used in figures were added to and defined in the +acronym table.

      • Capitalize cross-references at the beginning of a sentence: "Figure +1 contains the details." Do not capitalize them in the middle of a +sentence: "...as shown in figure X."

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/3-4-Passive-Voice/index.html b/sites/oteguide/editing_reports_guide/3-4-Passive-Voice/index.html new file mode 100644 index 00000000..434c8340 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/3-4-Passive-Voice/index.html @@ -0,0 +1,14 @@ +Passive Voice

      Passive Voice

      Change passive voice to active voice, when appropriate. You can +recognize a sentence with passive voice because a form of the verb to be +(is, are, was, were, be, being, or been) is followed by a past +participle verb (a verb ending in ed, en, or t). A sentence written in +passive voice always contains both.

      VerbPassive SentenceActive Sentence
      isAdequate planning is required for successful OT&E.Successful OT&E requires adequate planning.
      areDetails are contained in appendix D.Appendix D contains details.
      wasThe course was taughby the instructor.The instructor taught the course.
      wereThe results were written in active voice.They wrote the results in active voice ,or if subject is known,The test team wrote the results in active voice.
      beAnnual maintenance will be performed on the system.Maintainers will perform annual maintenance on the systemorMaintainers will perform maintenance on the system annually.
      beingPart A was being substituted for part B as a workaround.The workaround substituted part A for part B.
      beenThe data was given to the analyst.The analyst received the data,or if subject is known,The test director gave the analyst the data.
      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/3-5-Copyrights-and-Trademarks/index.html b/sites/oteguide/editing_reports_guide/3-5-Copyrights-and-Trademarks/index.html new file mode 100644 index 00000000..b49643b6 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/3-5-Copyrights-and-Trademarks/index.html @@ -0,0 +1,25 @@ +Copyrights and Trademarks

      Copyrights and Trademarks

      In accordance with the following authorities, AFOTEC is not required to +use the designated markings for copyrights and trademarks in our +documents because we are not a commercial entity and we do not +distribute our documents publically. We are, however, required to use +the proper spelling and capitalization for these trademarks (e.g., +Microsoft PowerPoint, Microsoft Word).

      The Copyeditor's Handbook states:

      "There is no need to include such designations as ^TM^ (trademark), +^SM^ (service mark), ® (registered trademark), or © (copyright) in +running text. Indeed, it is preferable not to use these symbols +because they may interfere with the line spacing of the final +document."

      --Einsohn, Amy. The Copyeditor's Handbook , 2d ed. University of +California Press: Berkeley. 2006.

      The Gregg Manual Reference Manual states:

      "If you refer to other organizations' trademarks in material of a +commercial nature that will be publically distributed, use a raised +symbol after each trademark. In all other documents, the symbols are +not necessary, but do use the proper spelling and capitalization for +these trademarks."

      -- Gregg Manual Reference Manual , 10th ed., McGraw-Hill: New York. +2005. p 114.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/3-6-Wordiness/index.html b/sites/oteguide/editing_reports_guide/3-6-Wordiness/index.html new file mode 100644 index 00000000..39789481 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/3-6-Wordiness/index.html @@ -0,0 +1,12 @@ +Wordiness

      Wordiness

      Remove extra words that add nothing to the meaning of the sentence, as +shown in the following examples:

      • IOC plus 10-year period ---IOC plus 10 years

      • Over a 5-year time period---Over a 5-year period or Over 5 +years

      • Program was first launched---Program was launched

      • In order to avoid confusion---To avoid confusion

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes/index.html b/sites/oteguide/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes/index.html new file mode 100644 index 00000000..1f3fb1cd --- /dev/null +++ b/sites/oteguide/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes/index.html @@ -0,0 +1,33 @@ +Hyphens, En Dashes, and Em Dashes

      Hyphens, En Dashes, and Em Dashes

      Hyphens, en dashes, and em dashes all have their proper place in +technical writing, and should not be used interchangeably. Hyphens and +en dashes are the "mechanics" of punctuation and have clear-cut rules +for their use. The em dash, on the other hand, is a stylistic choice +that the writer chooses over other forms of punctuation to make a +distinct point.

      Hyphens: Hyphens are used to connect and to separate textual +elements.

      Examples:

      • It was a 2-year program.

      • Wright-Patterson Air Force Base, Ohio; Northrop-Grumman Corporation

      As connectors, hyphens join the parts of compound modifiers.

      Examples:

      • The well-known author gave an interview.

      • The equipment emitted a high-frequency signal.

      Hyphens separate numbers that are not inclusive (i.e., not within a +range).

      Example:

      • My phone number is 500-111-2222.

      The trend is moving toward using the hyphen less frequently.

      Examples:

      • Email versus e-mail

      • Multifunctional versus multi-functional

      Retain the hyphen if its absence makes a word or its meaning unclear.

      Example:

      • Re-cover versus recover (to reapply a covering versus to come back +from; different meaning)

      Retain the hyphen when the prefix ends with the same letter with which +the word begins.

      Example:

      • Re-emerge versus reemerge; re-evaluate versus reevaluate (double-e +can be confusing)

      Some program titles contain the hyphenated "multi-" as part of a program +or system title. In those cases, leave the hyphen in place.

      When one element of a compound modifier ends in "ing" or "ed," use a +hyphen.

      Example:

      • Fast-burning fuel; self-contained module

      When two or more related compounds have a common basic element, retain +the hyphen with all parts.

      Example:

      • 10- to 20-page report; long- and short-term memory

      En Dashes: En dashes connect numbers within a range (including +number ranges in tables) or take the place of the word "to."

      Examples:

      • The years 1995--1996 were interesting ones for most government +workers.

      • The Las Vegas--Albuquerque flight departs in 1 hour.

      • The test team assessed MOEs 2.3--2.6.

      Em Dashes: "Em dashes involve a choice writers and editors make when +other options might be commas, a colon, or a set of parentheses. The em +dash can be used singly or in pairs. Its most common purpose is to set +off an amplifying or explanatory element of the sentence. It is also +used to indicate a sudden break in thought or an interruption in +dialogue." ( Chicago Manual of Style, 16th Edition , pages 333--336)

      Example:

      • The weapon failed the test---the trigger jammed.

      Em dashes are also used to set off explanatory elements that already +contain internal punctuation (i.e., commas).

      Example:

      • Boeing's system offers improvements---better navigation, streamlined +maintenance, and greater reliability---that no other vendor can +promise.
      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/3-8-Apostrophes/index.html b/sites/oteguide/editing_reports_guide/3-8-Apostrophes/index.html new file mode 100644 index 00000000..cf50ac35 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/3-8-Apostrophes/index.html @@ -0,0 +1,17 @@ +Apostrophes

      Apostrophes

      Use apostrophes to show singular possessives (belonging to a single +entity) or plural possessives (belonging to one or more entities). Do +not use apostrophes for a plural expression that is not used in the +possessive form.

      The word "its" means belonging to it and is never expressed as a +possessive. "It's" is a contraction that means "it is" or "it has." If +you cannot replace the word it's with it is or it has, do not use an +apostrophe. The following table contains examples of when to, or not to +use an apostrophe.

      Apostrophe Not RequiredApostrophe Required
      The test teams’ wrote the report. (plural)AFOTEC published the test teams’ report. (plural possessive)
      In the 1970s, Journey was a popular rock band. (plural)Journey was a popular 1970’s rock band. (possessive)
      Several MC-130s are parked on the flightline. (plural)Examine the MC-130’s payload. (possessive)
      They examined its contents. (belonging to it, not a contraction)It’s a windy day. (contraction for it is)
      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/3-9-Choppy-Sentences/index.html b/sites/oteguide/editing_reports_guide/3-9-Choppy-Sentences/index.html new file mode 100644 index 00000000..06bb243c --- /dev/null +++ b/sites/oteguide/editing_reports_guide/3-9-Choppy-Sentences/index.html @@ -0,0 +1,14 @@ +Choppy Sentences

      Choppy Sentences

      Rewrite choppy sentences into ones that flow better by adding +punctuation and conjunctions, when appropriate. However, be careful not +to change the meaning or context when doing so.

      Examples:

      Original : The test team wrote the report. The report informed the 14 +November 2014 full-rate production decision.

      Edit : The test team wrote the report, which informed the 14 November +2014 full-rate production decision.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/4-1-Numbers/index.html b/sites/oteguide/editing_reports_guide/4-1-Numbers/index.html new file mode 100644 index 00000000..b4bbe749 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/4-1-Numbers/index.html @@ -0,0 +1,13 @@ +Numbers

      Numbers

      Express numbers referring to time, measurements, or money as figures +(e.g., 8 hours, 2 feet, 5 dollars). Use ordinal numbers when spelling +out a unit's name. AFOTEC does not use superscript for ordinals.

      Examples:

      • Correct : 21st Space Wing (21 SW); subsequent use: 21 SW

      • Incorrect : 21st Space Wing (SW); 21st SW; 21 ^st^ SW; 21 ^st^ +Space Wing

      Do not use an "n" or "r" for second and third ordinals

      Examples:

      • Correct : 43d Test Squadron; 302d Airlift Wing

      • Incorrect : 43rd Test Squadron; 302nd Airlift Wing

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/4-2-Dates/index.html b/sites/oteguide/editing_reports_guide/4-2-Dates/index.html new file mode 100644 index 00000000..90e80798 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/4-2-Dates/index.html @@ -0,0 +1,19 @@ +Dates

      Dates

      Write dates differently depending on the context in which you use them. +In general, use the complete date format (full day, month and four-digit +year). However, abbreviate dates in tables, figures, and document or +publication references. Do not mix complete and abbreviated date +formats.

      Examples:

      • Correct : 20 Jul 04 or 20 July 2004

      • Incorrect : 20 Jul 2004 or 20 July 04

      When the terms fiscal or calendar year are spelled out, the four-digit +year should be used.

      Examples:

      • Correct : fiscal year 2001; calendar year 2001

      • Incorrect : fiscal year 01; calendar year 01

      When they are abbreviated, the year should also be abbreviated without a +space between the term and the year.

      Example:

      • Correct : FY01; CY01

      • Incorrect : FY 01; CY 01

      Use the words "to" or "through" instead of an en dash when dates are +preceded by words "between" or "from."

      Examples:

      • Correct : from 15 through 30 July; between 15 to 30 July and 1 to +5 August; 15--30 July; 15--30 July and 1--5 August

      • Incorrect : from 15--30 July; between 15--30 July and 1--5 August

      The only exceptions are tables and figures; always abbreviate dates +and use an en dash.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/4-3-Abbreviations/index.html b/sites/oteguide/editing_reports_guide/4-3-Abbreviations/index.html new file mode 100644 index 00000000..03c46477 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/4-3-Abbreviations/index.html @@ -0,0 +1,13 @@ +Abbreviations

      Abbreviations

      Common units of measure (e.g., ft, in, sec, nm) or common symbols (e.g., +percent, degrees) are abbreviations, not acronyms. Spell them out or +define them the first time you use them. Do not add them to the acronym +table.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/4-4-Terms/index.html b/sites/oteguide/editing_reports_guide/4-4-Terms/index.html new file mode 100644 index 00000000..62ad6ebe --- /dev/null +++ b/sites/oteguide/editing_reports_guide/4-4-Terms/index.html @@ -0,0 +1,20 @@ +Terms

      Terms

      Do not use terms "i.e.," and "e.g.," in conjunction with "etc." and, +most importantly, do not use them interchangeably. Always follow "i.e.," +and "e.g.," with a comma.

      The term "e.g.," means "for example." It is not a finite list ; +there are more possibilities than the ones stated.

      Correct:

      • They brought fruit (e.g., apples, oranges, bananas)

      • They brought fruit (apples, oranges, bananas, etc.)

      Incorrect:

      • They brought fruit (e.g., apples, oranges, bananas, etc.)

      • They brought fruit (e.g., the apples were crunchy)

      The term "i.e." means "in other words" and is used to add extra +information that clarifies. It is finite; it is the only possibility +that could be listed.

      Correct:

      • The hurricane affected two of the Hawaiian islands (i.e., Oahu and +Kauai) with winds over 130 mph.

      • Several personnel (i.e., active-duty and civilian) were promoted at +the ceremony.

      • He corrected the problem (i.e., tightened down the screw) and the +rattling stopped.

      • Four of the tech giants (i.e., Google, Amazon, Facebook, Apple) +hired promising new employees at the job fair.

      Incorrect:

      • Several tech giants (i.e., Google, Facebook) hired promising new +employees.
      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/4-5-Symbols-and-Units-of-Measure/index.html b/sites/oteguide/editing_reports_guide/4-5-Symbols-and-Units-of-Measure/index.html new file mode 100644 index 00000000..7d50696c --- /dev/null +++ b/sites/oteguide/editing_reports_guide/4-5-Symbols-and-Units-of-Measure/index.html @@ -0,0 +1,12 @@ +Symbols and Units of Measure

      Symbols and Units of Measure

      Use symbols and abbreviated units of measure in appendices, figures, and +tables, but spell them out in the executive summary and body of the +document.

      Examples:

      • Executive Summary and Body : percent, greater than, nautical mile

      • Appendix, Figure, or Table : %, >, nm

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/4-6-Verb-Tenses/index.html b/sites/oteguide/editing_reports_guide/4-6-Verb-Tenses/index.html new file mode 100644 index 00000000..b06a230c --- /dev/null +++ b/sites/oteguide/editing_reports_guide/4-6-Verb-Tenses/index.html @@ -0,0 +1,13 @@ +Verb Tenses

      Verb Tenses

      Be consistent in the use of verb tenses throughout the plan or report. A +plan describes how AFOTEC will execute a test and is written in future +tense. A report contains results, ratings, and operational impacts and +is written in past tense.

      PlanReport
      Describes how AFOTEC will execute the testContains results and ratings of the system under test, and the operational impact of those results and ratings
      Will happen, future tenseHas happened, past tense
      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/4-7-Embedded-Files/index.html b/sites/oteguide/editing_reports_guide/4-7-Embedded-Files/index.html new file mode 100644 index 00000000..901c323c --- /dev/null +++ b/sites/oteguide/editing_reports_guide/4-7-Embedded-Files/index.html @@ -0,0 +1,17 @@ +Embedded Files

      Embedded Files

      If the test teams follow the templates, you should not discover an +embedded file or link (PowerPoint, Excel spreadsheet, etc.) in the +document, because embedding documents into our plans or reports is not +permitted. However, if you discover such a file or link (i.e., a test +plan or report from another entity) within the document, you will have +to open and save it as a separate file, then forward it along with the +AFOTEC document so it can be included as an attachment to the completed +.pdf file that AFOTEC publishes and distributes.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/4-8-Converting-Pictures/index.html b/sites/oteguide/editing_reports_guide/4-8-Converting-Pictures/index.html new file mode 100644 index 00000000..64c4743a --- /dev/null +++ b/sites/oteguide/editing_reports_guide/4-8-Converting-Pictures/index.html @@ -0,0 +1,24 @@ +Converting Pictures

      Converting Pictures

      Do not copy/paste a picture from another document; instead, save it as a +".png" or ".jpg" file and insert it as a picture. Alternatively, use the +"snip and sketch" tool to save any image, table, text, equation, or +whatever you want to capture from a page and change into a picture. +Before "capturing" your image, unselect the "show all formatting marks" +so that you will not capture the marks with the picture. The "snip and +sketch" tool avoids the conversion process that makes pictures appear +grainy.

      You can also transfer a pasted picture to PowerPoint (directions below) +to change it into a ".png" or ".jpg" file, then delete the original +image and reinsert the picture you created.

      Procedures for converting a pasted picture into a .jpg or .png using +PowerPoint:

      • Capture picture and all text blocks or other objects placed within +it or on top of it, and copy the group of images (Ctrl C)

      • Paste into PowerPoint (Ctrl V), the select all (Ctrl A) or "group"

      • Right click, save as a picture (.png or .jpg)

      • Delete embedded object from document

      • In its place, position cursor and insert picture from where you +saved it

      • Center picture, then add a 1-pt black border (some flow charts or +similar figures may be disrupted by a border and, therefore, are +exempt)

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/4-9-References-and-Documentation/index.html b/sites/oteguide/editing_reports_guide/4-9-References-and-Documentation/index.html new file mode 100644 index 00000000..7e419785 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/4-9-References-and-Documentation/index.html @@ -0,0 +1,24 @@ +References and Documentation

      References and Documentation

      Cite references (documentation) correctly. A good authority is the Air +University Press, Air University Style and Author Guide (Maxwell AFB +AL, 2005), Part 1, Appendix B, Bibliographic Entries. You can access +this publication on the Internet. Suggestion : print out or save the +appendix and have it available for reference when you are editing. In +general, official publications with unlimited distribution (e.g., AFIs, +directives) are italicized:

      • AFI 99-103, Capabilities Based Test and Evaluation , 16 Oct 13

      Reports and other publications with limited distribution (e.g., AFOTEC +reports, threat documents) are enclosed in quotation marks:

      • Executive Order (EO) 13526, "Classified National Security +Information," 29 Dec 09

      • "Defense Enterprise Accounting and Management System (DEAMS) +(Increment 1 Release 3) Initial Operational Test and Evaluation +(IOT&E) Plan," 4 Aug 14

      Memos and standard forms (SF) are cited without italics or quotes. For +memos, state the entity who wrote the memo, the date, and the subject:

      • DOT&E Memo, 1 Aug 14, Procedures for Operational Test and Evaluation +of Cybersecurity in Acquisition Programs

      • SF298, Report Documentation Page

      The table below contains examples of the correct way to cite different +types of reference documents. Use the long citation the first time the +document is referenced and the short version for subsequent citings.

      TypeFirst UseSubsequent Use
      United States CodeTitle 10, United States Code, Section 236610 USC §2366
      Executive OrderEO 13526, “Classified National Security Information,” 29 Dec 09EO 13526
      DoD DirectiveDoDD 8500.01,Cybersecurity, 7 Mar 14DoDD 8500.01
      DoD RegulationDoD 5400.7-R,DoD Freedom of Information Act (FOIA) Program, Sep 98DoD 5400.7-R
      Chairman of the Joint Chiefs of Staff InstructionCJCSI 6212.01E,Interoperability and Supportability of Information Technology and National Security Systems,15 Dec 08CJCSI 6212.01E
      Air Force HandbookAir Force Handbook 33‑337,The Tongue and Quill, 27 May 15 (Incorporating Change 1, 19 Nov 15)Tongue and Quillor AFH 33‑337
      Air Force InstructionAFI 99‑103,Capabilities Based Test and Evaluation,16 Oct 13AFI 99‑103
      AFOTEC InstructionAFOTECI 99‑101,Conduct of Operational Test and Evaluation,1 May 07AFOTECI 99‑101
      AFOTEC ManualAFOTECMAN 99-101,Operational Test Processes and Procedures, 11 Oct 12AFOTECMAN 99‑101
      Military StandardMIL-STD-130N,Identification Marking of U.S. Military Property,16 Nov 12 (with change 1)MIL‑STD‑130N
      Technical OrderTO 00‑35D‑54,USAF Deficiency Reporting, Investigation, and Resolution,1 Nov 11TO 00‑35D‑54
      Concept of Operations“Combat Survivor Evader Locator (CSEL) Concept of Operations,” 4 Jul 05CSEL CONOPS
      System Threat Assessment ReportNASIC-1574-0210-03, “Automated Information Systems Threat Environment Description,” Dec 02AI STAR
      Published AFOTEC document“Defense Enterprise Accounting and Management System (DEAMS) (Increment 1 Release 3) Initial Operational Test and Evaluation (IOT&E) Plan,” 4 Aug 14DEAMS IOT&E Plan or the IOT&E plan
      Official MemorandumDOT&E Memo, 1 Aug 14, Procedures for Operational Test and Evaluation of Cybersecurity in Acquisition ProgramsDOT&E Memo on Policy for OT&E of Cybersecurity
      Standard FormStandard Form 298, Report Documentation PageSF 298
      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/5-1-Patches/index.html b/sites/oteguide/editing_reports_guide/5-1-Patches/index.html new file mode 100644 index 00000000..f3b717ff --- /dev/null +++ b/sites/oteguide/editing_reports_guide/5-1-Patches/index.html @@ -0,0 +1,16 @@ +Patches

      Patches

      Verify OTA patches on multiservice operational test and evaluation +(MOT&E) plan or report cover pages are correct. Patches should be in +same order of precedence as the signature page (Ref: AFMAN 36-2203), +which is army, marine corps, navy, air force, coast guard. However, when +AFOTEC is the lead OTA, our patch and our Commander's signature will go +first, followed by the other services in the correct order of +precedence.

      \ No newline at end of file diff --git a/sites/oteguide/fn_guides/test_capability_guide/index.html b/sites/oteguide/editing_reports_guide/5-2-Classification-Markings/index.html similarity index 84% rename from sites/oteguide/fn_guides/test_capability_guide/index.html rename to sites/oteguide/editing_reports_guide/5-2-Classification-Markings/index.html index d446fc43..5fc961e2 100644 --- a/sites/oteguide/fn_guides/test_capability_guide/index.html +++ b/sites/oteguide/editing_reports_guide/5-2-Classification-Markings/index.html @@ -1,29 +1,25 @@ -Test Capability Guide

      Test Capability Guide

      31 July 2020

      Last Updated/Reviewed: 26 February 2021

      Originating Office: AFOTEC A-5/8

      PURPOSE

      Enable ART and reduce risk by identifying, supporting, and advocating -for AFOTEC test capability requirements.

      Definition

      The infrastructure or support system necessary to enable an operator to -exercise a system in a combat realistic environment to include threats -and targets for the purpose of conducting an operational test or -assessment and/or an integrated developmental/operational test.

      Support Goals

      • Provide accurate reference data on test range and facilities -capabilities.

      • Provide research and analysis on existing test capabilities to -support operational test planning needs.

      • Identify gaps in test capability that need to be filled to support -future operational test needs.

      • Prioritize, advocate, track, and report on solutions to test -capability gaps.

      • Provide feedback and support on weapons, munitions, and targets -planning and allocation programming.

      • Provide feedback on test resource plan (TRP) requirements to ensure -accurate support levels are being planned for and reported.

      TEST RANGE AND FACILITY CAPABILITIES

      Provide reference information on the capabilities of test ranges and -facilities to enable the planning and execution of operational tests and -assessments in combat realistic environments to include threats and -targets.

      • Test Range and Facilities Database (Capabilities, POCs, etc)

      • TRMC Database

        • AF/TE List
      • Test Range and Facilities Briefs

      • Range Commanders Council (RCC) Briefs

      • Program Introduction Documents (PID)/Statement of Capability (SOC)

      • List of Training / Joint Exercises

      EXISTING TEST CAPABILITY IDENTIFICATION

      Provide support to test directors and the test team’s requests for test -capability research and analysis, identifying existing test capabilities -to enable operational test planning and execution.

      • Test Capability Readiness Assessment

      • Request a new TCRA for your Test Program

      • TCRA Status Dashboard

      • Completed TCRA Archive

      • Nevada Test and Training Range Test Capabilities

      • Contact A-8Z

      • Test Capabilities Slide

      • Briefing Template (Contact A-3)

      • Test Resource Plan support

      • AMAS (SharePoint Link)

      TEST CAPABILITY GAP IDENTIFICATION

      Provide support to identify test capability gaps to support multiple -operational test programs. Leveraging Intelligence data, emerging -technologies research, and operator experience to document AFOTEC test -capability current and future needs.

      • Threat Intelligence Research

      • VOLT & TTL (Contact A-2N)

      • Test Capability Gap Research

      • Gap Database

      • AFOTEC Test Team Input

      TEST CAPABILITY GAP SUPPORT AND REPORTING

      Provide support and advocate for projects which address AFOTEC test -capability gaps. Supporting and tracking all applicable test capability -investment programs and the foreign material acquisition process.

      • Time-Phased Investment Document (T-PhID)

      • Monthly Report

      • Test Capabilities Investment Programs

      • Central Test & Evaluation Investment Program (CTEIP)

      • Requirements Call / Submission

      • Joint Aircraft Survivability Program (JASP

      • Requirements Call / Submission

      • Resource Enhancement Program (REP)

      • Requirements Call / Submission

      • Threat Systems Working Group (TSWG)

      • Requirements Call / Submission

      • Test Investment Planning and Programming (TIPP)

      • Requirements Call / Submission

      • Foreign Material Acquisition (FMA)

      • Requirements Call / Submission

      • Submission

      MUNITIONS MANAGEMENT

      Provide support to test directors and the test teams to properly -forecast ammunitions, munitions, and aerial targets necessary to plan -and execute operational tests and assessments.

      • MMT Allocation Requests

      • MMT Support and Feedback on Test Resource Plans

      TEST RESOURCE PLAN REQUIREMENTS VERIFICATION AND FEEDBACK

      Provide support to test teams by soliciting, tracking, and reporting -test resource needs and enabling program objective memorandum (POM) -inputs, the Resource Requirements Board (RRB), and data justification -for PEO funding letters.

      • Test Resource Plan Support

      • AMAS (Contact TRM and/or A-8P)

      • Requirements Review Board

      • PEO Funding Letters

      • Contractor Request Review Panel

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/5-4-SF298-Report-Documentation-Page/index.html b/sites/oteguide/editing_reports_guide/5-4-SF298-Report-Documentation-Page/index.html new file mode 100644 index 00000000..2d1c55df --- /dev/null +++ b/sites/oteguide/editing_reports_guide/5-4-SF298-Report-Documentation-Page/index.html @@ -0,0 +1,41 @@ +SF298 Report Documentation Page

      SF298 Report Documentation Page

      AFOTEC reports (not plans) must include an SF298 attached to the end of +the document. Defense Technical Information Center (DTIC) uses this form +to archive official reports, as required. The SF298 should be maintained +at the unclassified level, if possible, so avoid details that would make +it classified. If not possible, ensure it is marked appropriately in the +header and footer and wherever classification information is required.

      Ensure the test team completes the form, because it is often neglected +in the writing process. Complete the blocks with the following +information:

      • Block 1--Must match date on cover page; use format described (i.e., +12082014, not 12 Aug 14)

      • Block 2--Type of report

      • Block 3--Dates covered are from beginning of testing period to date +of report; use format described (i.e., 09032014--12082014, not 9 Mar +14 - 12 Aug 14)

      • Block 4--Full title from cover page; should match exactly

      • Blocks 5a--5f--Leave blank

      • Block 6--Complete address of AFOTEC Detachment that produced the +report

      • Block 7--AFOTEC HQ address (i.e., AFOTEC, 1251 Wyoming Blvd SE, +Kirtland AFB NM 87117)

      • Blocks 8--11--Leave blank

      • Block 12--Distribution statement must match cover page +exactly---copy and paste from cover page, then reapply "SF298 text" +style

      • Block 13--If there is a classified annex or other supplemental +document for the report, add that information in this block---i.e., +This report is associated with "Annex 1 to the Joint Air-to-Surface +Standoff Missile-Extended Range (JASSM‑ER) Initial Operational Test +and Evaluation (IOT&E) Report," 8 Jan 13 (classified).

      • Block 14--Add a synopsis of the report---i.e., AFOTEC conducted an +OA to assess JASSM‑ER's progress toward operational effectiveness +and suitability in supporting the long-range, standoff precision +strike mission. Additionally, AFOTEC assessed the program's +readiness for OT&E. This OA report will inform the USD(AT&L)'s +7 Dec 10, MS C decision.

      • Block 15--Add the search engine terms a person would likely use on +the Internet to find our report; this information will be added to +the document properties in the published pdf

      • Block 16--Verify that the security classifications for the following +are stated accurately:

        • a. Report--classification of report

        • b. Abstract--classification of abstract (should be +unclassified, if possible)

        • c. This Page--classification of the SF298 front page (should be +unclassified, if possible)

      • Block 17--Limitation of Abstract

        • Unclassified abstract---should read UU (for unclassified, +unlimited distribution)

        • Secret abstract---should read S or same as report (SAR); when it +is not possible to keep the abstract at the unclassified level

      • Block 18--Enter total number of pages, minus the SF298 because it +does not count as part of the report

      • Block 19a--Enter AFOTEC/HO

      • Block 19b--Enter AFOTEC/HO phone number: (505) 846-2484

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/5-5-Spell-Check/index.html b/sites/oteguide/editing_reports_guide/5-5-Spell-Check/index.html new file mode 100644 index 00000000..140def9d --- /dev/null +++ b/sites/oteguide/editing_reports_guide/5-5-Spell-Check/index.html @@ -0,0 +1,12 @@ +Spell Check

      Spell Check

      ALWAYS run a final spell check before the final save at the end of the +editing process. It might seem obvious, but this step is often +overlooked.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/5-6-Configuration-Control/index.html b/sites/oteguide/editing_reports_guide/5-6-Configuration-Control/index.html new file mode 100644 index 00000000..90b1bdce --- /dev/null +++ b/sites/oteguide/editing_reports_guide/5-6-Configuration-Control/index.html @@ -0,0 +1,27 @@ +Configuration Control

      Configuration Control

      The hardest part of a technical editor's job is maintaining +configuration control. It is critical you maintain a constant line of +communication with Det test team members to ensure their final edited +version is the ONLY version to which changes are being made.

      After the 2-letter adjudication process, the Det turns the document over +to HQ, via AFOTEC Collaborative Action Platform (ACAP), for command +section coordination. At this point, configuration control of the +document converts from the Det technical editor to the A-3 technical +editor. Detachment personnel should cease working on the document, and +pass any additional changes they wish to make to their A-3 point of +contact. If the Det continues to work on the document they submitted, +which is no longer the valid version, that work will likely have to be +reaccomplished or, worst case, will be omitted inadvertently. The +document will be reviewed by members of the command staff (including the +Commander, Executive Director, Vice Commander, and Technical Advisor) +who will make comments and changes. The A-3 technical editor will +incorporate those changes into the configuration control version.

      Good communication is key to successful configuration control. Never +assume you have the correct version of a document unless the person with +whom the control resides confirms that it is the latest version.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/5-7-Table-of-Contents/index.html b/sites/oteguide/editing_reports_guide/5-7-Table-of-Contents/index.html new file mode 100644 index 00000000..6d168c17 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/5-7-Table-of-Contents/index.html @@ -0,0 +1,14 @@ +Table of Contents

      Table of Contents

      Do not attempt to hand-jam changes to the table of contents (TOC). It is +designed to work in tandem with AFOTEC styles---which is why it is +important to ensure the correct styles are applied---and will update +automatically. To update the TOC, go to the References tab, select +Update Table, then select Update Entire Table.

      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/5-8-Standardization-Checklist/index.html b/sites/oteguide/editing_reports_guide/5-8-Standardization-Checklist/index.html new file mode 100644 index 00000000..5cb78c34 --- /dev/null +++ b/sites/oteguide/editing_reports_guide/5-8-Standardization-Checklist/index.html @@ -0,0 +1,12 @@ +Standardization Checklist

      Standardization Checklist

      The following checklist can be a handy guide when editing an AFOTEC plan +or report. Print it out to ensure you perform a thorough check of all +areas of emphasis.

      AFOTEC STANDARDIZATION CHECKLIST
      Were AFOTEC styles applied?
      Did you perform an acronym scrub?
      Did you replace “continuous” page breaks with “next page” breaks?
      Did you ensure the serial comma was used consistently throughout the document?
      Did you verify headers and footers were standardized and contained correct classification, if necessary?
      Did you check page numbering to ensure there were no disconnects?
      Were blank pages added or deleted, as required?
      Did you correct capitalization errors?
      Did you verify military and Air Force Bases were cited correctly?
      Did you examine vertical lists for correct structure and punctuation?
      Did you confirm tables and figures were in sequential order?
      Did you verify each table and figure followed AFOTEC standards?
      Did you eliminate inappropriate passive voice?
      Did you rewrite wordy and choppy sentences?
      Did you ensure hyphens, en dashes, and em dashes were used correctly?
      Did you correct apostrophes that were applied incorrectly?
      Did you confirm number rules were followed?
      Were dates written correctly, according to the context in which they were used?
      Did you ensure only acceptable abbreviations were used?
      Did you verify whether the terms i.e., e.g., and etc. were used correctly?
      Did you ensure symbols and units of measure were spelled out in the executive summary and body?
      Did you correct errors in verb tenses?
      Did you eliminate embedded files?
      Did you convert copy/pasted pictures into .jpg or .png files and reinsert them?
      Did you verify documentation was cited correctly throughout the document?
      Did you verify whether classification markings, portion markings, and carry-over marks were applied correctly?
      Did you verify that the distribution list was compiled IAW template guidance, and includes all pertinent addressees?
      Did you check the SF298 to ensure it was accurate and complete?
      Did you perform a final spell check?
      Did you update the table of contents?
      MAINTAIN CONFIGURATION CONTROL! Do not password protect documents in 2-letter and CS coordination. Do not continue to work the version of the document you have at the detachment while it is in 2-letter or CS coordination. Instead, contact your A-3 POC about changes that need to be incorporated.
      \ No newline at end of file diff --git a/sites/oteguide/editing_reports_guide/index.html b/sites/oteguide/editing_reports_guide/index.html new file mode 100644 index 00000000..b85a9fee --- /dev/null +++ b/sites/oteguide/editing_reports_guide/index.html @@ -0,0 +1,13 @@ +Editing Guide

      Editing Guide

      "I cannot think of anybody who doesn't need an editor, even though +some people claim they don't." ~ Toni Morrison

      "Clever words are not as good as straight talk." ~ Chinese proverb

      "Like stones, words are laborious and unforgiving, and the fitting of +them together, like the fitting of stones, demands great patience and +strength of purpose and particular skill." ~ Edmund Morrison

      Last Updated/Reviewed: 08 December 2020

      Originating Office: AFOTEC A-3

      \ No newline at end of file diff --git a/sites/oteguide/evaluation_and_reporting_guide/2-INTRODUCTION/index.html b/sites/oteguide/evaluation_and_reporting_guide/2-INTRODUCTION/index.html new file mode 100644 index 00000000..fd0f9072 --- /dev/null +++ b/sites/oteguide/evaluation_and_reporting_guide/2-INTRODUCTION/index.html @@ -0,0 +1,18 @@ +INTRODUCTION

      INTRODUCTION

      + + + image2 + +

      This guide focuses on the analysis, evaluation, and reporting of AFOTEC +OT&E activities. It covers the products and processes you must follow to +complete this final phase of test execution successfully. Submit +suggested changes to: AFOTEC.A3.Workflow\@us.af.mil.

      \ No newline at end of file diff --git a/sites/oteguide/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE/index.html b/sites/oteguide/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE/index.html new file mode 100644 index 00000000..18acc46a --- /dev/null +++ b/sites/oteguide/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE/index.html @@ -0,0 +1,19 @@ +TEST ACTIVITY SEQUENCE

      TEST ACTIVITY SEQUENCE

      During a test activity, you will carry out a sequence of five steps:

      • determine what to test
      • design a test plan
      • execute the test and collect data
      • analyze and evaluate test results
      • report conclusions (Figure 1).

      The success of this activity depends largely on +the robustness of the earlier steps to ensure an OT effort that is +operationally sufficient and technically adequate. This guide focuses on +the analysis and evaluation of results and how to report test +conclusions.

      Figure 1. Test Activity 5-Step Sequence

      + + + image3 + +

      \ No newline at end of file diff --git a/sites/oteguide/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING/index.html b/sites/oteguide/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING/index.html new file mode 100644 index 00000000..c12eb45f --- /dev/null +++ b/sites/oteguide/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING/index.html @@ -0,0 +1,45 @@ +ANALYSIS, EVALUATION, AND REPORTING

      ANALYSIS, EVALUATION, AND REPORTING

      AFOTEC produces a test report that provides results of its analysis and +evaluation of operational test data. Time constraints are a constant and +compounding factor because OT&E reports often inform a milestone or +fielding decision with a hard need-date. Test teams must analyze data, +evaluate impacts to the mission, draw conclusions, and draft and +coordinate a test report as expeditiously as possible so the findings +are relevant and timely.

      Analysis

      Analysis is the detailed examination and application of disciplined +techniques (e.g., mathematics, statistics) to understand or determine +essential features of complex problems. AFOTEC employs an +operations-based approach to analyzing system performance. Sound +analysis produces technical adequacy and credibility. Test teams +typically rely on measures of performance (MOP) and measures of +suitability (MOS) to analyze system performance. Measures of +effectiveness (MOE) are used to analyze operational performance. They +may compare performance at the measures level against a criteria or +identified standard threshold to determine whether there are shortfalls.

      AFOTEC operational evaluations are not based on findings attributed to +operational unit or operator performance shortfalls.

      Analysis provides the foundation or basis for evaluation. While we +separate analysis and evaluation into different steps, there is no +distinct "line" between them.

      Evaluation

      Evaluation is intended to be the judgment of a system's operational +effectiveness and suitability when exposed to representative threats +while being operated and maintained in a realistic operational +environment by typical operators and maintainers. Evaluations require +operational experience to apply judgment and place system performance in +the context of intended operations.

      Operational evaluation determines the impact or significance of MOP/MOS +shortfalls by considering operational effects defined by MOEs. +Similarly, the operational evaluation of MOEs are in the context of the +operations defined by the critical operational issues (COI). After +evaluating COIs and measures, the test team has a basis for evaluating +(determining) a system's operational effectiveness and suitability.

      Reporting

      Reporting is dependent on numerous factors: the OT&E activity, the +goal of the activity, time constraints, and the status of OT&E (is OT&E +ongoing or complete). However, regardless of the OT&E activity or +driving need, AFOTEC will produce credible reports that are accurate, +balanced, and timely.

      • Accurate: The test team analyzes and evaluates test data

        meticulously to ensure the report's narrative and ratings are +consistent and conclusions are defendable.

      • Balanced: The report's narrative highlights both system

        capabilities and system limitations ( what the system did well +and what it did not do so well ) to enable mission effects.

      • Timely: AFOTEC delivers the report to decision makers to

        allow them time to review and understand results prior to a +decision date.

      \ No newline at end of file diff --git a/sites/oteguide/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION/index.html b/sites/oteguide/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION/index.html new file mode 100644 index 00000000..60551209 --- /dev/null +++ b/sites/oteguide/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION/index.html @@ -0,0 +1,79 @@ +STRUCTURE OF AN EVALUATION

      STRUCTURE OF AN EVALUATION

      AFOTEC structures a test program to facilitate an evaluation of the +operational effectiveness and suitability (E&S) of a system under test +(SUT); therefore, all activities leading to analysis, evaluation, and +reporting support a determination of E&S. Figure 2 illustrates how +AFOTEC structures an evaluation of a SUT.

      Figure 2. Structure of an AFOTEC Test Evaluation

      + + + image4 + +

      The test team composes COIs that ask whether a SUT can accomplish its +critical mission elements or operational objectives. Then, they develop +a variety of measures within each COI to evaluate the SUT's mission +effects, capabilities, functions, properties, or structure. MOEs +evaluate performance-driven mission effects and MOPs/MOSs capture system +capabilities and attributes.

      Evaluation Structure

      The OT&E evaluation structure is a subset of the OT&E construct. The +structure uses the following elements to report results of a SUT's +evaluation.

      • Operational Effectiveness. Measurement of the system's overall +ability to accomplish a mission when used by representative +personnel in the expected/planned operational environment +considering organization, doctrine, supportability, survivability, +vulnerability, and threat. (AFI 99-103, Capability Based Test and +Evaluation ).

      • Operational Suitability . The degree to which a system can be +placed satisfactorily for use in the field considering its +availability, compatibility, transportability, interoperability, +reliability, wartime usage rates, maintainability, safety, human +factors, manpower supportability, logistics supportability, natural +environmental effects and impacts, documentation, and training +requirements. (AFI 99-103).

      • Critical Operational Issues . A COI addresses a critical mission +element or operational objective examined during OT&E to determine +the system's overall capability to support mission accomplishment +(often referred to as operations-based COIs).

      • Operations. A COI is composed of one or more operations. +Operations describe the actions, activities, or phases of a mission +needed to accomplish the COI. With two or more operations, the +overarching operational objective is the same; however, the steps +and/or conditions to achieve the COI are different between +operations.

      • Mission Effects. Mission effects are outcomes or results of +conducting an operation.

      • Measures. Measures are designed to convey information about a +system's effect, capabilities, functions, properties, or structure +being addressed.

      • Measure of Effectiveness. "Are measures designed to +correspond to accomplishment of mission objectives and achievement +of desired results? They quantify the results to be obtained by a +system and may be expressed as probabilities that the system will +perform as required. MOEs may be further decomposed into measures of +performance and measures of suitability." ( Defense Acquisition +Guidebook ). "A criterion used to assess changes in system +behavior, capability, or operational environment that is tied to +measuring the attainment of an end state, achievement of an +objective, or creation of an effect." (JP 1-02, DoD Dictionary of +Military and Associated Terms , As Amended Through 15 Feb 16 ).

      • Measure of Performance. Measure of a system's performance +expressed as speed, payload, range, time-on-station, frequency, or +other distinctly quantifiable performance features. Several MOPs +and/or MOSs may be related to the achievement of a particular MOE. ( +Defense Acquisition Guidebook )

      • Measure of Suitability. Measure of an item's ability to be +supported in its intended operational environment. MOSs typically +relate to readiness or operational availability and, hence, +reliability, maintainability, and the item's support structure. +Several MOSs and/or MOPs may be related to the achievement of a +particular measure of effectiveness or multiple measures of +effectiveness. ( Defense Acquisition Guidebook )

      • Data/Data Element. Data is any measurement or information +used to determine the value of a measure. Data may be quantitative +or qualitative, subjective or objective.

      The evaluation summary chart (ESC) is a concise presentation of the OT&E +evaluation structure. It summarizes the mission statement, COIs, and +measures using colored indicators to rate each element. Figure 3 is a +representative ESC.

      Figure 3. Example Evaluation Summary Chart

      + + + image5 + +

      Note : Operational capabilities (OC) are depicted for context, but are +NOT rated or assigned colored indicators.

      \ No newline at end of file diff --git a/sites/oteguide/evaluation_and_reporting_guide/index.html b/sites/oteguide/evaluation_and_reporting_guide/index.html new file mode 100644 index 00000000..d1179196 --- /dev/null +++ b/sites/oteguide/evaluation_and_reporting_guide/index.html @@ -0,0 +1,10 @@ +Evaluation and Reporting Guide

      Evaluation and Reporting Guide

      Originating Office: OPR is AFOTEC/A-3 and OCR is AFOTEC/A-2/9

      \ No newline at end of file diff --git a/sites/oteguide/fn_guides/OTE_construct_development_guide/index.html b/sites/oteguide/fn_guides/OTE_construct_development_guide/index.html deleted file mode 100644 index ef66c6b8..00000000 --- a/sites/oteguide/fn_guides/OTE_construct_development_guide/index.html +++ /dev/null @@ -1,1100 +0,0 @@ -OT&E Test Construct Development Guide

      OT&E Test Construct Development Guide

      11 February 2021

      - - - image2 - -

      Last Updated: 26 February 2021

      Originating Office: OPR is AFOTEC A-3 and OCR is AFOTEC A-2/9

      INTRODUCTION

      This document contains information pertaining to the first two steps of -five major steps that define the overarching OT&E test activity. -Although the five major steps of a generic test activity can be applied -to various level of test (e.g., testing system functions, components, -sub-systems, and capabilities), this guide focuses on developing the -OT&E Construct to capture mission effects and the subsequent, -overarching test activity.

      The first step is “defining the what;” in the context of the OT&E -Construct, this is commonly described as battlespace development. It -answers the following questions: What are the operations under test; -what is the intended use of the system(s) in the operation; what are -the operational conditions they will be employed/supported under -(operations and conditions); and what do you need to measure to -determine combat capability or mission effects. Battlespace development -provides a strong operations-based foundation to build upon during test -design and when executing and reporting operational test.

      This guide also addresses the second of the five major steps, test -design. Test design determines the goals of the test and how to achieve -them. This includes considerations of creating an operationally -realistic environment, executing representative scenarios, and the means -to collect the resulting data.

      When answering these questions with discipline, the output is a strong -foundation for operationally sufficient and technically adequate -operational test and evaluation (OT&E).

      Submit suggested changes to AFOTEC DRU A-3E Workflow at -AFOTEC.A3E.Workflow@us.af.mil

      The Operational Test and Evaluation Construct

      The OT&E Construct is the framework for conducting operational test. It -identifies the following elements of an operational test and their -relationship to one another:

      • Operational Effectiveness:  Measure of the *overall capability

        to accomplish a mission when used by representative personnel in -the environment planned or expected for operational employment of -the system considering organization, doctrine, supportability, -survivability, vulnerability and threat. (AFI 99‑103, -Capability‑Based Test and Evaluation*, 6 Apr 17)

      • Operational Suitability:  The *degree to which a system can be

        placed satisfactorily in field use with consideration given to -availability, compatibility, transportability, interoperability, -reliability, wartime usage rates, maintainability, safety, human -factors, manpower supportability, logistics supportability, -natural environmental effects and impacts, documentation and -training requirements. (AFI 99-103, Capabilities-Based Test and -Evaluation*, 6 Apr 17)

      • Mission Statement: Mission statements are written at a high,

        overarching level consistent with the mission the system is -intended to support or enable.

      • Critical Operational Issues (COI): A COI addresses a *critical

        mission element or operational objective* examined during OT&E to -determine the system’s overall capability to support mission -accomplishment (often referred to as operations-based COIs).

      • Operations: A COI is composed of one or more operations.

        Operations describe the actions, activities, or phases of a -mission needed to accomplish the COI. With two or more -operations, the overarching operational objective is the same; -however, the steps and/or conditions to achieve the COI are -different between operations.

      • Mission Effects: Mission effects are outcomes or results of

        conducting an operation.

      • Operational Capabilities: OCs provide operational context for

        system capabilities or attributes of high interest or importance -within an operation. It may be useful to distinguish between -system capabilities (i.e., the potential to perform some action) -and system attributes (i.e., the functions, properties, structure) -of a system. Operational capabilities provide the means to conduct -an operation and achieve effects.

      • Operational (User) Requirements: A *system capability,

        attribute, or characteristic required to accomplish approved -capability needs*. Operational requirements (including -suitability) are typically performance attributes, but they may -also be derived from cost and schedule (AFI 10-601). Typically -referred to as “requirements.”

      • Operational Conditions: Operational conditions are identified

        for each COI or operation and depict the operational battlespace. -An operational condition is defined by a set of factors, each set -at a given level. A factor is a variable of the environment that -may affect task performance. A level is a set value within the -range of values a factor can hold.

      • Measures: Measures are designed to convey information about a

        system’s effect, capabilities, functions, properties, or structure -being addressed.

      • Data/Data Element: Data is *any measurement or information used

        to determine the value of a measure*. Data may be quantitative, -qualitative, subjective, or objective.

      • Test Design: The test design is a set of test events for each

        operation and battlespace condition, including the rationale for -selecting the test events.

      • Test Event: A test event is a *single execution of an operation

        or sequence/set of operations* under specified conditions for the -operations.

      This guide provides methods to develop these elements of the OT&E -Construct for the overarching goal of determining effectiveness and -suitability.

      Operational Sufficiency and Technical Adequacy

      Operational sufficiency and technical adequacy are two basic AFOTEC -tenets leading to an adequate and credible test.

      Operational Sufficiency addresses the breadth of the operations and -conditions addressed while employing new or modified capabilities within -the context of representative employment and support concepts. An -operational test and evaluation (OT&E) is considered operationally -sufficient if it provides the decision maker and the warfighter with -results from test events executed across sufficient operations and -conditions to identify the capabilities and limitations associated with -employment and support, and enables an effectiveness and suitability -determination.

      Ensuring operational sufficiency requires a thorough understanding and -identification of the operational employment and support environment and -conditions, to include operational threats. AFOTEC core teams address -operational sufficiency while designing test events to ensure -capabilities and concepts are adequately addressed within the -operational evaluation. Core teams are one tool to address operational -sufficiency by using operational perspective, experience, and judgment -to ensure test events are evaluated within the context of envisioned -operations and support. This allows AFOTEC to characterize systems’ -capabilities and mission effects.

      Technical Adequacy addresses the relevance of the technical information -produced by the test in relation to the purpose of the test (i.e., test -events address operationally relevant questions). This includes test -design, test measures, relevant threat environments, data collection -methods, scoring, analysis, modeling and simulation, and test capability -accreditation. A test is technically adequate if the test data -evaluation provides the acquisition decision maker information to inform -the relevant decision.

      Operational Test and Evaluation Test Activity Cycles

      A general test activity is the sequence of determining what to test, how -to test, executing the test and collecting data, analyzing the results, -and reporting the conclusions (see figure 1). The success of this -activity depends largely on an initial understanding of the battlespace, -the capabilities under test, and how the capabilities fit within the -battlespace. All subsequent activities build on a test team’s basic -understanding of the expected capabilities under test, in what -operational conditions the capabilities will be employed and supported, -and what needs to be measured. This is called “Defining the What.” Using -more operational terminology, this effort is commonly referred to as -battlespace development and should be the first step for the OT&E -Construct test activity.

      Figure 1. Steps in the OT&E Construct Test Activity

      - - - image3 - - Developing -a battlespace is the first of five major steps in the AFOTEC OT&E -Construct and is accomplished in conjunction with Test Design (discussed -in this guide with more detail in the Analyst Test Design Guide). This -step frames the OT&E by answering four fundamental questions. *What* are -the capabilities under test; *what* is the intended use of the -capabilities; in *what* operational conditions will the capabilities be -employed/supported (operations and conditions); and *what* do you need -to measure to determine combat capability?

      Test teams have latitude in how they develop the battlespace. However, -this guide presents a long-standing and proven approach test teams -should consider before proceeding with test design. It is systematic and -can quickly take test teams from limited operational understanding to -credible OT&E Constructs. This AFOTEC default approach to battlespace -development will provide a sound foundation for the second step, Test -Design. Figure 2 generalizes this approach. Although depicted as a -sequence of steps, the process is iterative and adaptive.

      Figure 2. Battlespace Development Within the OT&E Construct

      - - - image4 - -

      Battlespace development provides the foundation for operationally -sufficient and technically adequate OT&E by ensuring operations-based -test designs. It supports the later application of scientific methods of -testing needed to design and analyze tests across the operational -battlespace to ensure credibility. A key element of the scientific -method of operational test is mission thread analysis, which includes -identifying the operational conditions and considering test constraints, -thereby leading to a set of high-return test events. These events will -lead to a defensible basis for resource estimations (test articles, -personnel, etc.) early in an acquisition and OT&E lifecycle. It also -aids the development of test execution methodologies (field test, -modeling and simulation, hybrid), identifying test capability -requirements and shortfalls, and refining OT activities and schedule -(Integrated Test & Evaluation).

      Using a Core Team Approach.

      The core team is an AFOTEC-led working group established to support -program test activities. Examples include battlespace development, test -design, measures workshops, and technical reviews. The core team is -composed of all AFOTEC stakeholders (Test Team, Detachment and -Headquarters staff). The core team is led by the responsible test -director (TD). It includes any AFOTEC Detachment subject matter -expertise (SME) the TD believes is needed (e.g., logistics and cyber -SMEs). AFOTEC/A3 typically facilitates the process. An AFOTEC -directorate’s core team member’s general responsibilities include -ensuring their directorate’s intent and expertise is considered as early -as possible. It also aids the staff awareness and support during later -activities and staffing actions. External stakeholders are also invited -to support OT&E Construct development. Key external representatives come -from operational users, program offices, development test, and other -OTAs (for Multi-service OT). DOT&E action officers (or support -contractors, typically the Institute for Defense Analyses (IDA)) should -also be invited if the program is on the DOT&E oversight list. External -involvement during the OT&E Construct development is significant in -terms of early buy-in on AFOTEC’s foundational planning effort, and it -builds relationships at the earliest possible opportunity. The OT&E -Construct can be developed without externals, and with some rapid test -activities it may be required to keep a program moving quickly. However, -OT&E Constructs are typically better if external stakeholder -interests/inputs are considered. Figure 3 reflects a typical CT -composition and potential external stakeholders.

      Figure 3. Core Team Composition

      - - - C:\Users\James.Thomas\Desktop\ITD Brief\CT Picture.png - -

      The typical roles and responsibilities for core team members and -external stakeholders are addressed in table 1.

      Table 1. Core team and External participant Roles and Responsibilities

      Core TeamExternal Participants.

      Detachment TD:

      - Serves as the overall lead for all core/test team activities from program involvement through OT closeout

      - Produces well-written documents and well-prepared briefings

      - Serves as primary briefer for the program

      Note: Det/CC has operational control of the testing process from TO through OT closeout

      Battlespace development facilitator:

      - Facilitates the battlespace development and assists TD with developing the test design

      - Documents the OT&E Construct

      - Co-facilitates test events, methodologies, and scenarios

      A-2/9 Staff:

      - Co-facilitates test events, methodologies, and scenarios

      - Assesses program’s intelligence sensitivity

      - Provides assistance with development of realistic threat scenarios

      - Provides specialized support to team in the effectiveness analysis, suitability analysis, modeling and simulation expertise, test design expertise, weather, intelligence, and human factors

      A-5/8 Staff: Provides policy guidance, test capability, and range identification

      SE Staff: Provides environmental, safety, and health guidance

      - Warfighters bring operational currency, background information and clarity when addressing operational requirements and concepts of operations

      - Program office participants bring program information (schedules, technical risk areas, funding, etc.) Gain insight into OT expectations; know potential impact to contract awards with OT flavor

      - Lead Developmental test organization (LDTO)/CTA participants bring developmental test (DT) information, gain insight into OT expectations, identify operationally representative OT events that DT can fulfill, know potential impact on capability requirements clarification start provide insight into integrated test challenges

      - Other agencies provide insight into test capabilities, expectations, plans, limitations

      -- Director, Operational Test and Evaluation (DOT&E) fulfills an oversight function

      -- Other OTAs address their Service equities for MOT&Es

      --- Army Test and Evaluation Center (ATEC)

      --- Operational Test and Evaluation Force (OPTEVFOR)

      --- Marine Corps Operational Test and Evaluation Agency (MCOTEA)

      Construct Development Meetings

      Battlespace development typically occurs in a formal meeting(s) -environment. It is closely tied to the test design and is often -accomplished during the same meeting(s). In most cases, an A3 test -design manager (TDM) will accomplish pre-work with the TD prior to the -formal battlespace development meeting. The pre-work, coupled with A3 -facilitation, allows the meeting to be executed quickly and efficiently. -Successful battlespace development typically takes a couple of days -allowing a transition into the test design activity during the same -formal meeting. Optimally, one battlespace development/test design -meeting is required with follow-on activities for measures development -(measures workshop) and execution planning activities.

      Battlespace Development

      The Battlespace development steps are captured in the subsequent -paragraphs.

      Researching the Capability or System Being Acquired

      Core team members and external stakeholders should strive for maximum -understanding of the capability being acquired, the mission(s) it -supports, and how it will be employed and supported before the formal -meeting. To prepare for the battlespace development/test design meeting, -research capability-based requirements (e.g., draft ICD, CDD) and any -available system information from various sources (e.g., SRD, TRD). -Other documents critical to operational understanding are CONOPS, TTPs -and threat documentation. This research results in knowledge of where -and how the system fits into the envisioned battlespace and the intended -operational capabilities. Gaining this knowledge can be inherently -difficult early in a program’s acquisition cycle with only a draft ICD -and a limited, or no written CONOPS. The operational significance of the -required capabilities and their impact on the battlespace need to be -understood sufficiently in order to properly scope the overall -operational evaluation.

      The CT should strive to understand:

      • The mission the system is designed to support

      • Operational objectives required to accomplish the mission

      • The critical elements of the mission the system supports

      • Information/data cyber dependencies which enable the mission

      • Bounds of the “system” acquisition and the T&E processes (i.e., “to

        what extent are other systems impacted, beyond the system being -acquired, within the T&E processes?”)

      • Threat environment (kinetic and non-kinetic) in which the system is

        expected to operate

      • Limitations and issues that are resolved to support the acquisition

        and T&E processes (technical as well as operational)

      • Program documentation:

      • System CONOPS

      • Capability requirements documents

      • Program acquisition strategy (DoDI 5000.02 model being employed -

        hardware- or software-centric; additional documents may be used, -as required)

      • AFOTEC battlespace development process

      • AFOTEC test design process

      - - - image6 - - To -facilitate common understanding a series of briefings are typically -provided at the start of a battlespace development /test design meeting. -The briefings cover the Acquisition, CONOPS, capability requirements and -threats. Generally, the program office, warfighting user, and -intelligence representatives provide the briefings. Once the team -understands the battlespace and how the SUT will support the operation -in that battlespace, the team can examine how the required capabilities -map to the operational activities. The AFOTEC approach to ensure the -core team understands the capability and system being acquired is to -build battlespace depiction in the form of an Evaluation View (EV).

      Battlespace Depiction

      - - - image7 - -

      When -developing the battlespace depiction, the core team should consider the -type of capability being acquired, what actions the capability enables, -what objective(s) the capability supports, and the objective’s -dependencies on other systems. For example, if accomplishment of an -operational objective depends on numerous other systems and operational -factors, it may be difficult to provide a credible answer about the -system’s contribution to the objective; in this case the scope or level -of test could be too high (e.g., operational level of conflict, table 4) -versus a more credible tactical level of conflict. These considerations -will help guide the level of detail for the nodes in the evaluation view -and define the scope of the test.

      The Evaluation View

      The evaluation view (EV) (Figure 5) is one method used to aid -operational understanding; it is a facilitation tool to get the core -team and external participants to a point of common battlespace -understanding before jumping into operational test design. The EV -illustrates three important OT fundamentals: where in the operation the -system will likely influence operational outcome; where and when -OT-relevant data will likely be generated; and where the operational -environment could affect the system’s capability.

      The EV is not intended to be a literal depiction. The core team should -understand that the battlespace depiction is not perfect, but that it -meets the needs of process facilitation. The core team will need to have -a degree of understanding and latitude as they progress through the -process because they will have to reach a consensus on the level of -detail they deem sufficient to proceed to the next step.

      There are other methods to gain operational understanding, but using the -EV has proven successful over several hundred test efforts and is -typically the tool of choice to facilitate the majority of battlespace -development efforts. It has advantages over various other tools such as -the DoD Architecture Framework (DODAF) views. Although DODAF views are -useful for different levels of planning, they are oftentimes not -available for the early AFOTEC planning efforts. The DODAF system views -(SV) and technical views (TV) are very specific in purpose and do not -provide an overall picture of the battlespace. A DODAF operational view -1 (OV-1) is often useful; however, it normally only addresses the -pointy-edge of the operation and does not typically address logistics to -an acceptable level of detail. When an EV is complete, and done -properly, it should reflect a tailored battlespace depiction that shows:

      • Major battlespace phases

      • Elements of the operation (primary nodes)

      • Mission statement

      • Critical operational issues (COI) and subordinate operations

      • Capability requirements mapping

      • Information sources/references

      • Inherently addresses both effectiveness and suitability elements

      • Provides equal consideration to logistics-centric operations

      The Evaluation View 1

      - - - image8 - -

      Building -an EV can look challenging on the surface, but it is initially framed by -an A-3 Test Design Manager (TDM) skilled in their development. The TDM -works hand-in-hand with the TD in all pre-work activities and the -initial framing occurs prior to any formal meetings. The EV-1 forms a -system-of-systems depiction of the Joint and/or Air Force doctrinal -mission area that the new/modified capability is intended to support. It -is developed using the broad knowledge gained from early involvement, -studying Joint and Air Force doctrine and researching all available -program documentation (e.g., AoA, system CONOPS, ICD, CDD/IS CDD, T&E -strategy, Air Force & Joint CONOPS & Doctrine, associated DODAF -architectures). The EV consists of typical operational nodes linked -together using a “necessary conditions” methodology. Primary nodes are -significant elements of the operation. Major phases are logical -groupings of primary nodes and are used to add clarity and understanding -to differing phases of the operation. Major phases of the operation -usually become apparent after the primary nodes are linked and are -further differentiated using different colors to associate the primary -nodes with their respective major phase.

      The Evaluation View 2

      EV-2s are a near-seamless evolution of EV-1s and differ in three primary -areas. The EV-2 has capability requirements, critical operational issues -(COI) and subordinate operations mapped into the battlespace.

      Capability Requirements Mapping

      The EV 2 (Figure 6) builds on the operational environment depicted on -EV-1. The EV-2 is developed by mapping operational capability -requirements into the depiction where the operational performance data -would likely be generated during a typical operations. Operational -capability requirements are found in a variety of documents (e.g., draft -ICD, CDD and CONOPS). Operational capability requirements usually -contain key characteristics (attributes) with appropriate parameters and -metrics. However, they may be described with only the characteristic -(e.g., “the system must possess high reliability”). Other times there -may not be any documented capability requirements and in these cases -there will be greater reliance on current operational expertise to -define the material solution (system under test). This is the most -extreme case for defining the battlespace and system under test and -would require documenting capability documentation shortfalls. While -mapping requirements, keep in mind that teams often identify -requirements shortfalls that should be mapped as derived capabilities.

      Derived capabilities are usually the result of some inferences in the -ICD or CDD, or could result from an interpretation of the CONOPS and -capabilities relationship and understanding that certain performance -characteristics must exist for a system to meet its overall mission -need. Derived capabilities do not have associated criteria or -references, but generally influence the overall effectiveness and/or -suitability determinations (The TD must validate capabilities derived -during the core team process with the user).

      To help teams readily identify cybersecurity interest areas. The nodes -with cyber dependencies will be identified by a blue border and will -have applicable requirements and verbiage detailing the cyber dependency -mapped into it. The purpose of this step is to generate discussion and -identify area for further investigation into possible test implications -concerning Cybersecurity.

      During DT/OT, the test team should monitor/assist with cybersecurity -test events, pursuing test events using standard scenarios based on real -procedures, real operators, and production-representative equipment. If -viable, the team should plan accordingly and reflect the plan in the -TEMP and other test-planning documentation. The team must incorporate -the CDD/CPD and system CONOPS as testing evolves.

      Mission Statement

      Mission statements are written at a high, overarching level consistent -with the mission the system is intended to support. For example, “Combat -Search and Rescue Locator (CSARL) supports the combat search and rescue -mission.” The team should ask, “What mission is the system intended to -execute or support?” or “Why are the capabilities being acquired?” -Mission statements should be consistent with wording from published -documents like the ICD/IS ICD, CDD/IS CDD, CONOPS, doctrine, etc. The -mission statement should also trace to the capability gaps identified in -the ICD. The Detachment TD and A-3 TDM develop a recommended mission -statement in the pre-work and present it to the team during the meeting.

      Critical Operational Issues

      A critical operational issues (COI) is an operational question. AFOTEC -defines a COI as a critical mission element or operational objective -that is examined during OT&E to determine the system’s overall -capability to support mission accomplishment as determined by -effectiveness and suitability. Put simply, COIs are operations, and -should clearly speak to the warfighter. When answered, the operational -impact is clear. For COIs, the team should ask, “What are the critical -elements of the mission?” or “What warfighter goals, major operations, -or activities are intended to be accomplished?”

      A COI may be composed of more than one type of operation and may -describe the operation in a set of activities or phases of a mission -needed to accomplish the COI. An example is the KC-46 COI, “Can KC-46 -provide refueling?” There are at least two distinct activities or -operations within this COI: air-to-air refueling and forward area -refueling point (FARP), which is forward ground refueling. Although the -overarching goal is the same (to provide refueling), the activities and -the conditions to do this are different. Identifying operations allows -for designing test around the unique operations and associated -operational conditions. The major phases identified on the EV should -provide a logical COI structure. The COIs and any breakout of -subordinate operations are documented on the EV near logically group -operational nodes.

      COIs are operations, not functions, system characteristics, or enable -characteristics. Figure 7 illustrates some basic COI tenants.

      Figure 7. COI Tenets

      - - - image9 - -

      As with all things, there are exceptions. Given the emphasis on -cybersecurity, teams have the option to address cybersecurity as a -separate COI. This is typically done because teams believe there are -test reporting advantages. For some systems, a cyber COI may be helpful -for reporting cyber effects to warfighters and acquisition community -separate from system performance in an uncontested cyber environment. -Reporting this way highlights cyber during OT&E by more narrowly -focusing on what needs to be corrected, why, and the impact if not -corrected from a cyber perspective. In these cases, a separate COI to -capture cybersecurity concerns, may be warranted. Considerations that -could justify a separate cyber COI are characteristics of the SUT (e.g., -common architecture across all COIs, a software/network focus, and -potential catastrophic node), characteristics of the operating -environment (e.g., significant documented cyber threats or reliance on -out of boundary systems or connections), or when cyber effects are not -fully captured in traditional ops-based COIs. Test teams can choose from -three OT&E constructs (integrated, stand-alone, and hybrid) to capture -and report cyber impacts in a manner that ensures stakeholders -understands performance and mission impacts in a cyber-contested -environment. Cyber considerations do not mandate a cyber-centric COI; -however, core teams have flexibility should they desire a different -cyber reporting approach.

      The integrated approach (commonly referred to as traditional or -Ops-based) would only have a cyber-centric COI if there was a defined -cyber operation introduced by the SUT. Cyber elements (operational -conditions, threats, test measures, etc.) are addressed within the -context of the missions or operations-based COIs (wherever cyber can -affect operational outcome). Using the integrated approach, any notable -issues identified that extend beyond the SUT (e.g., do not affect the -degree of mission accomplishment of the SUT or the ability to place in -field use) may be addressed in a separate annex to the OT&E report, if -warranted.

      The stand-alone approach addresses all of the operations-based COIs in -an uncontested cyber environment; the stand-alone, cyber-centric COI -addresses the operations in a cyber-contested environment. This approach -allows the baselining of uncontested performance, as compared to -contested performance of the SUT. The Stand-alone Cyber COI essentially -embeds and executes the operations documented in the traditional COIs in -a cyber COI that has a contested environment. All cyber contested -elements (e.g., operational conditions, threats, test measures, and test -events) are addressed within the cyber COI. Additional cyber-specific -measures address the system’s cyber operational capabilities.

      The hybrid approach applies elements of both the integrated and -stand-alone approaches, addressing cyber both within the -operations-based COIs and a separate cyber-centric COI. Cyber elements -(e.g., operational conditions, threats, test measures, and test events) -are addressed within the context of the missions or operations-based -COIs, the cyber COI is functionally focused (e.g., cybersecurity -operational capabilities) and also addresses effects not seen within the -missions or operations-based COIs (i.e., indirect effects, 2nd/3rd order -effects). This may also be used to expand cyber reporting beyond the -SUT, if warranted.

      Operations

      Based on different activities or different operational conditions within -a COI, multiple subordinate operations may be identified under a COI. An -example COI for the KC-46 was, “Can KC-46 provide refueling?” There are -at least two distinct activities or operations within this COI: -air-to-air refueling and forward area refueling point (FARP). Although -the overarching goal is the same (to provide refueling), the activities -and the conditions to achieve this are different. Another example could -be sustainment operations that has a subordinate maintenance operation, -deployed operation, and training operation. Again the need for breaking -down various operations become obvious when identifying the various -conditions associated with the different operations.

      Operational Employment and Support Conditions

      Measures of Effectiveness

      MOEs (very similar to the previous Mission-Oriented Response Variables -or MORV) are developed for each COI or for each operation. An MOE is a -measure of a system’s (or operation’s) degree of mission success and -will be commensurate with the level of test. It is a dependent variable -which gauges the achievement of a desired effect (aka measure of -effect). MOEs also guide the development of factors and levels by -assessing factors’ expected impact on the MOEs.

      Ideally, an MOE should be continuous, but could also be binary—was the -effect achieved or not. While a categorical or binary MOE may be a -strong indicator of mission success, it might also drive considerably -more testing and resource requirements than a continuous MOE would -require to achieve the same statistical significance.

      Examples of MOEs for a notional Combat Search and Rescue system’s -operation of Recover Personnel might be:

      • Binary: “Percentage of Rescue Attempts that are Successful”

      • Continuous: “Proportion of Survivors Rescued”

        Note the measure of effectiveness reflects the outcome or effect of -an operation.

      Operational Conditions (Factors and Levels)

      Operational conditions define the system’s operations and support -environment. After MOEs have been developed, operational conditions that -potentially have a significant influence on outcome of the operations -are identified. Operational conditions are identified for each COI or -operation within a COI and depict the operational battlespace identified -to support development of test events and scenarios. An operational -condition is defined by a set of factors, each set at a given level. A -factor is a variable of the environment that affects task performance. A -level is a set value within the range of values that a factor can hold. -It is important to understand the factors influencing task performance -in order to initially capture representative operational conditions in -the OT&E Construct. The terminology (conditions, factors, and levels) is -derived from CJCSM 3500.04D.

      The set of factors and levels forms the relevant set of operational -conditions. These conditions are contained in the test design -worksheets. As an example, the Mode of Travel, Battery Type, Terrain, -Time of Day, and Threat are all factors (Table 3) potentially -influencing the outcome of the operation as defined by the MOE: -Percentage of Rescue Attempts that are Successful. No Vehicle, -Rechargeable, Flat, Night, and High are one level for each factor, -respectively. A single condition for the survivor/evader navigation COI -can be described by a specific combination of factors and levels. For -example, one possible combination or single condition can be described -as mode is no vehicle, battery is non-rechargeable, terrain is -mountainous, time of day is night and the threat is high. Another -operational condition can be described as the terrain is flat, time of -day is daytime, and the threat is low. Cyber threats have the potential -to impact most systems. The cyber factors in table 2 are generally -sufficient for test designs; however, other cyber focused factors may be -appropriate depending on the COIs and/or subordinate operations.

      Table 2. COI 2, Survivor/Evader Navigation

      Operational Conditions
      FactorsLevels
      Mode of TravelVehicleNo vehicle
      Battery TypeRechargeableNon-rechargeable
      TerrainFlatMountainousLittoral
      Time of DayNightDayTransition
      ThreatHighLow
      Disruptive Cyber threatYesNo
      Non Disruptive Cyber threatYesNo

      Identify Factors and Levels.

      Factors and levels are identified through a number of methods. If -studies (such as an AoA) have been conducted, they could provide insight -on potential factors. If requirements have been mapped on the EV, they -could provide specific factors of interest (e.g., for “the system shall -operate day and night” the factor would be time of day). The CT, -composed of the users, developers, operators, analysts, etc., brings a -great deal of knowledge and expertise to the task of brainstorming ideas -on factors.

      To identify factors, the team reviews each COI and asks the question, -“What factors potentially influence the outcome of the COI or operation -captured by the MOEs?” Some of these factors may be an explicit part of -the environment in which the system will be employed (e.g., altitude, -weather, network load.) Other factors may not seem as directly related -to the employment environment, such as manning level, technical orders, -skill level. Yet, others may appear as inherent system factors that will -likely be “as-is” when the system is employed. Examples of this include -memory size, number of display screens, and seat positions, we identify -these as a “Given” level within the design. While this list is not -exhaustive set of factors, it is important to document all of the -factors identified for future reference. For OT purposes, attempt to -focus on the sets that will have a potential effect on the outcome of -the operation and are likely to vary the operational environment or the -user/operator.

      After the core team documents the factors, appropriate levels will be -added to each factor. When identifying the levels, it is desirable to -capture the range of possible levels. The decision on exactly which -levels to test will be made later during test design. At this point, it -may be recognized that several of the factors, particularly the inherent -system factors, may be given for operational test. In the example, the -factors are software version and training. It is not necessary to -identify levels for those factors (although, the developer may wish to -do so). Table 3 expands on the navigation COI example discussed in table -3.

      The last two factors highlight the point of documenting all identified -factors. In the illustrated example, these particular factors were -previously recognized as going to be “given” or “as-is” when the system -is delivered. Therefore, they are not prioritized since there is no -possibility for them to change. The software version factor is important -to document since it is part of the operation and is measured and -reported. The last two factors (software version/training) is at a set -value for the OT&E.

      Table 3. COI 2, Survivor/Evader Navigation

      Operational Conditions
      FactorsLevels
      Mode of TravelVehicleNo vehicle
      Battery TypeRechargeableNon-rechargeable
      TerrainFlatMountainousLittoral
      Time of DayNightDayTransition
      ThreatHighLow
      Disruptive Cyber threatYesNo
      Non-Disruptive Cyber threatYesNo
      Software VersionGiven
      TrainingGiven

      Prioritizing Factors

      The table of factors may include factors in the operational environment -which may not influence the SUT, but are used to describe an operational -environment. As a result, a prioritization process is used to rank -factors based on their impact against each COI’s operations by -considering their effect on the MOEs. This is a subjective determination -made by the Core Team and is intended to identify those operational -conditions that have the most impact to mission success and are -therefore more important from a test design perspective. This is a -two-step process for each factor and is accomplished during the -Battlespace Development meeting, using operator/SME input. The -prioritization process begins with determining the likelihood or -frequency of encountering each level of each factor in the operational -environments and continues by determining the estimated magnitude of -impact varying the levels of a factor has on the MOE.

      The first step determines the likelihood of encountering the particular -levels for each factor. This is based on the potential to encounter a -particular factor/level in the operational environment (e.g., the -probability of recovery from mountains is high, but the probability of -recovery from Flat is low). This may be done with specific probabilities -or percentages or with qualitative statements (e.g., likely, frequently, -seldom). The combinations of the factors, levels, and the likelihood of -encountering each level describes the possible battlespace conditions -the system under test could operate within when conducting the -activities depicted by the COI or Operation.

      The second step estimates the magnitude of impact and assigns a “high,” -“medium,” “low,” or “none” rating for each MOE for each factor. The -impact is assigned after considering the potential size of the change in -the MOE when the factor is varied between its levels, leading to a -significant change in the outcome of the operation with consideration of -the MOE. Table 4 shows the prioritized factors highlighted in grey.

      Table 4. Factor Prioritization

      COI 1: Can CSARL enable survivor/evader navigation to a rendezvous location?
      Operation 1: Rescue Survivor

      MOE 1: Timeliness of Rescue;

      MOE 2 Accuracy of Pick-up Point

      FactorLevelsPrioritizationFactor MgmtWhy factor is operationally important; Why level is selectedNotes
      Likelihood of EncounteringMagnitude of Impact
      MOE 1MOE 2
      Mode of Travel

      Vehicle

      No Vehicle

      Frequent

      Seldom

      HHAffects the survivor’s ability to move from the area.
      Battery Type

      Rechargeable

      Non Rechargeable

      Frequent

      Seldom

      HHAbility of the survivor/evader to have communications.
      Terrain

      Flat

      Mountainous

      Littoral

      BalancedHHDifference in the terrain could affect the survivors’ ability to move or platform recovery.
      Time of Day

      Day

      Night

      Transition

      BalancedMMNight time could affect the ability to see the survivor/evader.The CT should document notes for each F&L set.
      Threat

      High

      Low

      BalancedHHThis would affect the platforms ability to reach location.
      Disruptive Cyber Threat

      Yes

      No

      CommonHHWill have to look at mission planer vulnerabilities.
      Non Disruptive Cyber Threat

      Yes

      No

      CommonMMLook at possible mission effects.
      Software VersionGivenGivens not prioritizedComplete instructions on how to plan and operate system, also affects maintenance.Latest version.
      TrainingGivenGivens not prioritizedPlatform dependent, survival or equipment related capabilities.Both survivor and recovery team have training.

      The last two factors highlight the point of documenting all identified -factors. In this example, these particular factors are seen as “given” -upon system delivery. Therefore, they are not prioritized because there -is no possibility they will change. The technical data factor is -important to document because it is part of the operation and will be -measured and reported. The last factor will be at a set value for the -OT&E. The team has determined this factor is unlikely to have an impact; -nonetheless, it is documented as part of the set of factors. The last -two factors and the factor “threat” are not removed from the list—they -are still needed to ensure the test environment is operationally -representative. Consideration should be given to them for resource -planning and test execution.

      Operational Capabilities (OC)

      An OC is a system attribute or grouping of attributes users or SMEs -identified as having value or that are crucial to the system to satisfy -the capability gap within the context of the operations defined by the -COIs. They provide operational context for attributes of high interest -or importance within the operation. OCs are identified by reviewing the -system’s requirements documents and by SMEs identifying system -capability attributes that can significantly influence achieving the -COIs.

      Cybersecurity and cyber resiliency are high-interest attributes and -are assessed/evaluated as applicable across all operations.

      The OCs are not part of the rating structure or evaluation at the end of -test, but serve instead to highlight possible trends/patterns of -operational impact along a particular capability. For instance, if in -the final evaluation, multiple measures fail across the OC -“Interoperability”, then this potential capability impact is highlighted -to leadership and decision makers. OCs are captured as a short phrase or -topic. Although the identification of OCs is a facilitated effort by the -A3 TDM, table 5 shows which areas to examine when developing OCs.

      Table 5. Operational Capability Areas

      OCArea to Examine
      Operational PerformanceWhat are the measures of desired effects (e.g., timeliness)?
      What operational performance attributes are listed (e.g., precision, responsiveness)?
      What operational performance attributes are associated with the key performance parameters (KPP) and key system attributes (KSA) (e.g., accuracy)?
      What attributes are high risk (e.g., lethality; cybersecurity, dependent on new technology)?
      System SupportWhat support attributes are listed (e.g., reliability, maintainability, availability, compatibility)?
      What are the support‑related attributes associated with the KPPs and KSAs (e.g., cybersecurity)?
      What attributes are high risk (e.g., reliability; dependent on new manufacturing techniques)?

      On the ESC, OCs allow some logical grouping of the operational -capabilities or capability requirements (e.g., from an ICD or CDD). The -relationship between operations (defined by the COIs), operational -capabilities and capability requirements are clearly depicted.

      Evaluation Summary Chart

      The team presents the program’s OT&E Construct in an Evaluation Summary -Chart (ESC). The chart will vary slightly depending on the COI approach -(see tables 6-8). The ESC identifies the various elements of an -operational test and the relationship of the individual elements to each -other. The initial elements of the OT&E Construct are the Mission -Statement (optional), COIs, Mission Effects (as MOEs), OCs, and -Operational Requirements; these form the first version of the ESC -labeled an ESC-1. The ESC-1 is intended to be a concise presentation -tool for summarizing the focus and scope of the test and relationship of -COIs and operational capabilities. The TD presents the ESC as part of an -Initial Test Design (ITD) Briefing.

      Table 6. Evaluation Summary Chart-1 (Integrated COI Approach)

      Mission Statement: The CSARL supports the combat search and rescue mission.

      Critical Operational Issues

      COI 1: Can CSARL enable rescue team navigation to a survivor/evader’s location?COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?COI 3: Does CSARL support worldwide search and rescue operations?

      Mission Effects →

      Operational

      Capabilities ↓

      MOE 1.1, 1.2MOE 2.1, 2.2, 2.3MOE 3.1, 3.2, 3.3
      Accuracy4.3, 7.4
      Situational Awareness4.1, 4.24.1, 4.2, 4.9
      Timeliness4.4, 4.54.4, 4.5, 4.6
      Mission Planning4.9–4.124.10–4.13
      Cyber Resiliency/ Survivability*4.21*4.21*4.21
      Interoperability4.294.30–4.324.33–4.35
      Reliability4.254.254.26–4.28
      Compatibility4.22, 4.244.22, 4.23
      Availability4.39
      Maintainability4.40–4.43
      Ground Equipment4.44
      *KPP or supports KPPEffectiveness CentricSuitability Centric

      Table 7. Evaluation Summary Chart-1 (Hybrid COI Approach)

      Mission Statement: The CSARL supports the combat search and rescue mission.
      Critical Operational Issues →COI 1: Can CSARL enable rescue team navigation to a survivor/evader’s location?COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?COI 3: Does CSARL support worldwide search and rescue operations?COI 4: Does CSARL Cyber Ops enable support Mission Assurance?

      Mission Effects →

      Operational

      Capabilities ↓

      MOE 1.1, 1.2MOE 2.1, 2.2, 2.3MOE 3.1, 3.2, 3.3MOE 4.1, 4.2, 4.3
      Accuracy4.3, 7.4
      ...
      Cyber Resiliency/ Survivability*4.21*4.21*4.21*4.21
      ....
      *KPP or supports KPPEffectiveness CentricSuitability Centric

      Table 8. Evaluation Summary Chart-1 (Stand-Alone COI Approach)

      Mission Statement: The CSARL supports the combat search and rescue mission.
      Critical Operational Issues →COI 1: Can CSARL enable rescue team navigation to a survivor/evader’s location?COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?COI 3: Does CSARL support worldwide search and rescue operations?COI 4: Can CSARL operate in a cyber contested environment?

      Mission Effects →

      Operational

      Capabilities ↓

      MOE 1.1, 1.2MOE 2.1, 2.2, 2.3MOE 3.1, 3.2, 3.3MOE 4.1, 4.2, 4.3
      Accuracy4.3, 7.4

      4.1-4.13, 7.4.

      Note: Will require later development of COI 1, COI 2, and COI 3 composite MOP/MOS

      Situational Awareness4.1, 4.24.1, 4.2, 4.9
      Timeliness4.4, 4.54.4, 4.5, 4.6
      Mission Planning4.9–4.124.10–4.13
      Cyber Resiliency/ Survivability*4.21*4.21*4.21*4.21
      Interoperability4.294.30–4.324.33–4.35

      4.29-4.44

      Note: Will address in later COI 1, COI 2, and COI 3 composite MOP/MOS

      Reliability4.254.254.26–4.28
      ............
      *KPP or supports KPPEffectiveness CentricSuitability Centric

      Mission Statement in an Evaluation Summary Chart

      The mission statement (optional) is copied and pasted into the -Evaluation Summary Chart.

      Critical Operational Issues in an Evaluation Summary Chart

      COIs are copied and pasted into the Evaluation Summary Chart.

      Mission Effects in an Evaluation Summary Chart

      Mission effects, captured as MOEs for the COIs, are listed on the -Evaluation Summary Chart

      Operational Capability Requirements in an Evaluation Summary Chart

      Operational capability requirements paragraph references from the ICD/IS -ICD/CDD/IS CDD are copied into the first version of the Evaluation -Summary Chart (ESC-1) based on their relationship to the COIs on the -EV-2. This provides a clear understanding of how the COIs and -operational capability requirements relate to the operational and -support‑related performance attributes of the system and provide the -capability required by the warfighter. They are intended as high‑level -placeholders for operational test measures (MOEs/MOPs/MOSs) to be -developed later during the measures workshop and refined during test -concept development.

      Note: Operations and conditions (factors and levels) are not depicted -on an Evaluation Summary Chart. However, they are part of the overall -OT&E Construct and are typically provided in the test design and test -concept briefings.

      Test Design

      Test design is the second step in a test activity (see figure 8). For -the OT&E Construct test activity, the focus is on the test design for -evaluating achievement of the mission effects. The test design addresses -the following areas.

      Test Design Goals

      The SUT, the level of test and the kind of answer required, determine -the test design goals for each COI/operation and each may have multiple -goals and therefore designs. In general, AFOTEC uses three types of test -design goals: characterize, compare, and problem identification.

      Types of Test Design

      Choosing the most appropriate test design(s) requires expertise on the -system and the operational application it supports. An AFOTEC test -program will likely have combinations of the designs presented here. -Each COI or operation has its own test design and may have more than one -design. The result of a test design is a set of design points and the -rationale for choosing them. The following are typical types of design.

      • Demonstrations.  Demonstration test designs are used to

        demonstrate whether something is possible or not.

      • Space‑Filling Designs.  Space‑filling designs use a variety of

        techniques and criteria to select design points to provide -coverage across the possible set of conditions.

      • Combinatorial Designs. A combinatorial design employs the

        science of systematically selecting combinations of factors and -levels to provide the best chance of identifying problems. This is -most often used in testing software intensive systems.

      • Case Designs.  Case designs are used to demonstrate the

        capabilities of a system and operation under a specified set of -conditions. Several cases may be created using multiple methods.

      • Worst Case/Best Case Design.  One method may be “worst case,”

        where the conditions chosen are those perceived to be the most -stressing.

      • Special Cases Design.  Some special cases may be of particular

        interest to someone (e.g., the user, OSD, Congress). The -underlying reason for the special case should be documented, -because experience has shown the underlying goal is to prove it -either works or it does not work under some specific condition of -interest.

      • Operational Profiles Case Design.  Select cases based on the

        expected frequency of encountering the particular conditions -during planned operations (e.g., from the CONOPS). The rationale -(besides operationally realistic) is that this would be the -fastest way to reveal the most operationally‑relevant problems.

      **
      -**

      Figure 8. Test Design Within the OT&E Construct

      - - - image10 - -

      Factor Management.

      Within the test design, for each operation, operational factors are -managed at specified levels. How they are managed will depend on the -test design goal, the likelihood of encountering levels, and the -magnitude of operational impacts when a levels are changed. Table 9 -illustrates the factor management logic.

      • Vary factor. If a factor management is “Vary,” that factor’s

        levels will be changed in accordance with the test design by the -test team.

      • Fixed factor. “Fixed” factors will be set and will not change

        throughout the test.

      • Log (Record) Factor. Those factors labeled “Log” are not

        actively managed, but the setting of that factor will be recorded -during the execution of test events for possible use during -post-test data analysis.

      Table 9. Factor Management Logic

      - - - image11 - -

      Table 10 reflects the typical factor management resulting from the -factor prioritization discussed earlier in the guide.

      **
      -**

      Table 10. Factor Management

      COI 1: Can CSARL enable survivor/evader navigation to a rendezvous location?
      Operation 1: Rescue Survivor
      MOE 1: Timeliness of Rescue; MOE 2 Accuracy of Pick-up Point
      FactorLevelsPrioritizationFactor MgmtWhy factor is operationally important; Why level is selectedNotes
      Likelihood of EncounteringMagnitude of Impact
      MOE 1MOE 2
      Mode of Travel

      Vehicle

      No Vehicle

      Frequent

      Seldom

      HHVary VaryAffects the survivor’s ability to move from the area.
      Battery Type

      Rechargeable

      Non Rechargeable

      Frequent

      Seldom

      HHVary VaryAbility of the survivor/evader to have communications.
      Terrain

      Flat

      Mountainous

      Littoral

      BalancedHH

      Vary Vary

      Demo

      Difference in the terrain could affect the survivors’ ability to move or platform recovery.
      Time of Day

      Day

      Night

      Transition

      BalancedMMVary Vary DemoNight time could affect the ability to see the survivor/evader.The CT should document notes for each F&L set.
      Threat

      High

      Low

      BalancedHHVary VaryThis would affect the platforms ability to reach location.
      Disruptive Cyber Threat

      Yes

      No

      CommonHH

      Fix

      Demo

      Will have to look at mission planer vulnerabilities.Fix at Yes.
      Non Disruptive Cyber Threat

      Yes

      No

      CommonMM

      Fix

      Demo

      Look at possible mission effects.Fix at Yes.
      Software VersionGivenGivens not prioritizedLogComplete instructions on how to plan and operate system, also affects maintenance.Latest version.
      TrainingGivenGivens not prioritizedLogPlatform dependent, survival or equipment related capabilities.Both survivor and recovery team have training.

      Unconstrained and Constrained events

      In prioritizing the factors and determining factor management, the -entire set of possible test conditions has been filtered into a smaller, -more manageable and executable set of test conditions. The process -continues by introducing constraints and picking an appropriate test -design or set of test designs. Test design requires a discussion on -factor constraints. The core team will examine all of the possible -combinations of factor levels and specify which are infeasible due to -operational or physical constraints.

      Statistical Measures of Merit

      All test designs have associated measures of merit, or quality -indicators, and most are grounded in scientific statistical -methodologies. The measures of merit should be considered when deciding -on a test design. Regardless of chosen design type, there is a related -measure of merit which should be a consideration addressed in the test -plan documentation. The AFOTEC Test Design Guide has more information on -statistical measures of merit and their applicability to different -design types.

      Test Events

      Any single design results in a set of test events. A single test event -is defined as a single execution of a test to collect data with the -operational factors set at a single, given level (i.e., a single -condition or design point). Table 11 continues the survivor/evader -navigation example introduced earlier. In this example, the team has -decided the type of answer they wanted to provide was to characterize -the system’s behavior. Consequently, a characterize design matches well -with the desired type of answer. Other factors are fixed.

      Table 11. Example COI Test Events to Recover Isolated Personnel

      Test EventMode of TravelBattery TypeTerrainTime of DayThreat
      Characterize
      1No VehicleRechargeableMountainTransitionLow
      2VehicleNon-rechargeableFlatNightLow
      3No VehicleNon-rechargeableLittoralNightHigh
      4No VehicleNon-rechargeableMountainDayHigh
      5VehicleRechargeableLittoralDayHigh
      6No VehicleNon-rechargeableFlatTransitionHigh
      7VehicleRechargeableMountainNightHigh
      8VehicleNon-rechargeableLittoralTransitionLow
      9No VehicleRechargeableMountainTransitionLow
      10VehicleNon-rechargeableFlatNightLow
      11No VehicleNon-rechargeableLittoralNightHigh
      12No VehicleNon-rechargeableMountainDayHigh
      Problem ID
      13VehicleRechargeableLittoralDayHigh
      14No VehicleNon-rechargeableFlatTransitionHigh
      15VehicleRechargeableNightHigh

      If multiple test designs are created, such as a characterize design -supplemented with a case design, the total number of test events -increases. Similarly, the total number of test events increases in -accordance with test events that are replicated.

      Test Design Validations

      Testing evolves continuously and it is expected that test designs will -change. Most of the design evolution is managed by the test teams during -the normal testing ops. However, a test design validation is a more -formal effort that generally occurs at the request of a Detachment TD -and is usually employed when the test design is significantly outdated, -when there have been major changes in the scope of an acquisition, or -when earlier test design documentation is not sufficient/available. The -scope of a design validation depends on the test team needs. It could -require all of the step leading to a test design or only specific pieces -of the test design to be readdressed. When making a design validation -scope determination, keep in mind that most of the steps build on one -another. Formal test design validations should be requested by the -Detachment through the A‑3 PM.

      Measures Development

      This section discusses the process for refining MOEs, developing -measures of performance (MOP), and measures of suitability (MOS), and -identifying the associated data elements. MOEs are identified during the -earlier battlespace development effort and refined during a measures -workshop (MW). See the AFOTEC Measures Guide for additional details. In -AFOTEC, measures are developed using a top-down and bottom-up approach. -The top down approach is most useful for MOE development and the -bottom-up approach is effective when developing MOPs and MOSs. Figure 9 -illustrates where measures fit in the OT&E construct.

      Figure 9. Measure development in the OT&E Construct

      - - - image12 - -

      Measures of performance and suitability (MOP/MOS) are initially -developed in a MW facilitated by A‑2/9 with A‑3 and Detachment -participation. The optimal time for a MW after the initial OT&E -Construct is approved and a draft CDD/IS CDD, or an equivalent document, -(e.g., AF Form 1067, A‑spec) is available as the source document for -capability requirements. Measures development can also be triggered by -immediate need.

      Measures are expected for RFP and MS B/C TEMPs, test concept -briefings, and all AFOTEC assessment and test plans. For RFP TEMPs -that are too early for a Measures Workshop, an initial measure set -will be developed by A-2/9 (working with the detachment and the Test -Team as input to the RFP TEMP.

      Measures of effectiveness (MOE) are the measures related to the -capability to accomplish an operation. MOEs directly determine the -degree of the desired effect achieved for a COI.

      Measures may also be associated with the operational capabilities that -contribute to a COI being satisfied. Measures of Performance (MOP) are -the measures related to the system’s capabilities, features, functions, -and properties enabling the effects to be achieved. Measures of -suitability (MOS) are the measures related to the degree to which a -system can be placed satisfactorily into field use. Additional -information on MOPs and MOSs can be found in AFI 63‑101/20‑101_AFGM -2016-01, Life Cycle Management, 9 May 17; AFI 99‑103, Capabilities -Based Test and Evaluation, 6 Apr 17; and AFOTECPAM 99‑104, AFOTEC -Operational Suitability Test and Evaluation Guide, 24 Sep 13, etc.). -Test teams should consult the AFOTEC Measures Guide, their Detachment -TA, and A‑2/9 for current best practices on the development of measures. -Proposed exceptions to these best practices should be discussed with -A‑2/9 before developing measures. Generally, the desired outcome of a MW -is a complete set of measures for the test activity with defined scopes -for each measure.

      The MW are meetings facilitated by A-2/9 and A-3. Major stakeholders in -the acquisition program are invited: the user community, the program -office (PO), DOT&E, system developers, and developmental testers. All -participants apply their subject matter expertise toward the goal of -developing a measure set and test designs. Generally, the Detachment, -A‑2/9 and A‑3 do “homework” prior to the workshop. A‑2/9, with inputs -from the Detachment TD or technical advisor, develops draft measures in -preparation for the MW meeting. The purpose of MW preparation before -holding the MW meeting is to save time and level of effort.

      Test Execution Planning

      The AFOTEC core team members will usually meet informally to continue -building upon the information compiled during the Battlespace -Development, initial test design, and measures development. This is -referred to as execution planning (see figure 10). The purpose of these -follow-on meetings is to finalize the test construct such as refining -test design worksheets, identifying test methodologies, creating test -scenarios, and identifying resources.

      Figure 10. Test execution Planning in the OT&E Construct

      - - - image13 - -

      Test Methodology

      Test events may be executed through a variety of methods. Replicating a -realistic mission or mission segment should be used whenever feasible. -Replicating a realistic mission does not have to focus on the engagement -or battle outcome level (full engagement level of testing can be cost -prohibitive), but should provide the means to evaluate the operational -effectiveness and suitability of the system or subsystem in -operationally realistic conditions. Additionally, it should provide a -means to determine overall mission capability. Testers create controlled -test scenarios to reflect the conditions that best evaluate the system. -Field testing is a good, initial choice for operational testing as it -provides the most operationally realistic environment. However, field -testing is not always feasible to capture all test events. M&S provides -another venue for executing test events (USC, Title 10 imposes -constraints on the use of M&S during operational testing) and may -include distributed test applications using live, virtual and -constructive (LVC) simulation assets. M&S requirements should be -determined early in order to become part of the system development -contract. Other test methods include studies and analysis, exercises and -training opportunities. The test methodologies may be a combination of -these methods during DT, IT&E and OT. For example, early in a program, -you might use M&S to help identify important operational factors to -include in an Early Operational Assessment (EOA) or Operational -Assessment (OA). Execution of test events during the EOA/OA is followed -by some analysis highlighting that some factors may not be important -(and possibly identify new factors). The revised set of operational -factors is then used in the OT&E.

      If test capability requirements (to include modeling and simulation) are -identified during OT&E Construct development, accreditation activities -are required. Identification of test capability requirements will result -in the development of an accreditation memo. The memo identifies the -test capability requirements, accreditation documentation requirements -and format, timelines, the accreditation authority and other pertinent -information. The memo is increasingly important because it initiates -development of the accreditation plans and begins tracking VV&A resource -expenditures including manpower and dollars.

      Test Scenarios

      Test scenarios capture the end‑to‑end flow and reintroduce the factors -identified during the battlespace development and test design. During -those earlier steps the operational factors were used to identify -condition based test events. These events must be translated into -representative operational test scenarios (figure 11). Test events -should be executed in in the most representative scenarios possible. -This allows the best evaluation of a system by replicating a realistic -mission or mission segment. Test scenarios should allow all key factors -identified in the condition-based test event to be exercised.

      Figure 11. Test Events and Scenario Linkage

      - - - image14 - -

      Test scenarios may include test events supporting multiple measures or -COIs. Thus, one scenario may satisfy the completion of multiple test -events simultaneously (Figure X). Evaluating a system by replicating a -realistic mission or mission segment should be used whenever feasible. -Mission replication should provide the means to evaluate the operational -effectiveness and suitability of the system or subsystem in -operationally realistic conditions. Realistic threats, including cyber -threats, should be drawn from the latest intelligence sources for the -employing commands. Core teams create controlled test scenarios that -reflect the operationally realistic conditions to best evaluate the -system. Defense business systems testing will include theft/fraud test -scenarios.

      The intent is to identify test scenarios that allow for an end‑to‑end -flow from one COI to the next, as well as for concurrent COIs. Within -the test scenarios, factors are set to the appropriate levels called for -by each test design. It is important to realize that the levels may be -different or vary from scenario to scenario. For example, an F‑16 -conducting a CSAR scenario is unlikely to fly at high altitudes; thus, -the level for altitude is set to low and another scenario (such as a -strike scenario) is used to capture altitude at its high level. Another -approach would be to select a set of test scenarios that allow all the -test events (described by the factors and levels) to be executed within -the scenarios. Selecting test scenarios appropriately allows for -efficient use of test resources, as well as presenting an operationally -realistic test environment. Proper scenario selection also helps avoid -testing in independent segments (e.g., COIs) when there are actually -interactions between these segments. However, not all test events are -likely to be executable as part of one overall scenario or set of -scenarios. Expect some test events to require separate, specific -portions of a scenario to establish the necessary operational -conditions. A consequence of identifying end‑to‑end flow and interaction -between COIs is that test events are overlapping and occurring -simultaneously. For example, the same F‑16 sortie that captures two -targeting test events (one in mountainous terrain, the other in flat -terrain) also captures a mission‑planning test event and a weapons -load‑time test event. These events all take place within the context of -a CSAR scenario where the particular operational factors are set to -levels consistent with a CSAR scenario. Figure 12 reflects this concept -of end-to-end threads across COIs

      Figure 12. End-to-end threads across COIs

      - - - image15 - -

      Test scenarios also allow the re‑introduction of the operational factors -that were set aside earlier. These are the operational factors likely to -exist in the operational environment, but at a given level or minimally -related to the system. These are included in the test scenarios to -ensure operationally realistic conditions.

      Test Capability Needs and Shortfalls

      Execution of operationally relevant OT&E will normally require test -capabilities. This section only discusses test capabilities and -accreditation to the extent needed for an initial test design. For more -details see the AFOTEC Test Capabilities Guide and the AFOTEC -Accreditation Guide. AFOTEC does not own or operate test ranges, -facilities, or assets and must identify test capability resource -requirements as early as possible to ensure they are available, and -technically and operationally sufficient, for OT&E purposes. The -battlespace development and test design processes defined the test scope -and methodologies and is the foundation for identifying test capability -requirements. Table 10 shows typical test capability requirements.

      Table 10. Typical Test Capabilities

      • Test articles

      • Test sites

      • Test instrumentation

      • Test support equipment

      • Threat representation

      • Test targets and expendables

      • Operational force test support

      • Models, simulations, and test beds

      • Joint operational test environment

      • Special requirements

      Requirements that cannot be met by existing test infrastructure and -capabilities must be identified to A-5R. Gaps/shortfalls associated with -NTTR should be addressed through A-8Z. Test capability requirements are -addressed in the AFOTEC Test Resource Plan (TRP) and the AFOTEC uses a -Time-Phased Investment Planning Document process to advocate for test -capability development. For test capabilities that may require foreign -threat capability, contact AFOTEC A-2N to request and advocate for -foreign assets through the AF foreign materiel program (FMP) process. -This process acquires and exploits foreign systems for testing, training -and intelligence purposes and may satisfy a threat test capability need.

      Time-Phased Investment Document

      The AFOTEC T-PhID (formerly Test Capability Roadmap) serves as the -cornerstone of AFOTEC’s test capability investment strategy. AFOTEC must -communicate OT requirements to AF and DoD investment forums. Test -capability development must be funded in appropriate investment -portfolios to ensure the needed capabilities will be in place, verified, -and validated in time to support the test. A-5R continuously gathers OT -requirements (test capability gaps/shortfalls) through:

      • Individual program test capability readiness assessments (TCRAs)

      • SharePoint interface used for spontaneous/asynchronous -identification of requirements by test teams

      • An annual requirements call closely aligned with the AFOTEC RRB

      Test capability requirements priorities are approved by AFOTEC CC -annually, in time to support AF and DoD investment planning processes. -Some of the test capability investment forums are listed below.

      • Test Investment Planning and Programming (TIPP)

      • Central Test and Evaluation Investment Program (CTEIP)

      • Resource Enhancement Program (REP)

      • Threat Systems Working Group (TSWG)

      • Joint Aircraft Survivability Program (JASP)

      A-5R coordinates communication of AFOTEC test capability requirements to -these investment forums, coordinates review of development proposals to -identify those that may satisfy AFOTEC needs, and monitors program -development ensuring fulfillment of AFOTEC needs including completion of -capability verification and validation. There are numerous range -capability requirements that must be addressed as early as possible.

      Determining Range Requirements

      In building a mission scenario and determining range requirements, the -tester needs to know, for example, the type of target, the number of -aircraft attacking a target and weapons employed. The tester also needs -to consider the range’s ability to accommodate the operational test -without environmental impact. The system CONOPS should contain -information such as specific tactics and techniques to be employed -against certain targets and threat systems. Ensure that range personnel -have a full understanding of the specific OT objectives. The core team -should consult with A‑8Z (OL‑NN post-tasking order) for testing -considerations at NTTR and A‑5R for any other test range or facilities.

      Range Requirement Identification

      Carefully thought‑out mission scenarios provide the test team with -preliminary test range resource requirements (e.g., threat simulators -and instrumentation packages). Early identification of these -requirements is extremely important for advanced range scheduling, test -resource plan (TRP) development, and incorporation of new range -requirements into the various range improvement programs and other -investment forums (need at least 1 year lead time). In support of the -core team, A‑5R (A‑8Z for NTTR) provides information on current and -legacy DoD T&E databases that archive data on existing T&E test assets -and is the Air Force’s focal point for integrating new T&E range -requirements into the range improvements program. All potential test -sites should be considered before the final selection is made.

      Range Selection Considerations

      The Test Team may have to give special consideration to test range -selection and use. Usually, flight test programs require scheduling of -and coordinating with test ranges for some or all test sorties. Test -teams need to ensure range availability at the time of their scheduled -test. All major ranges and centers are subject to the DoD uniform -funding policy and require formal documentation of the test and the -support needed. The range, in turn, provides a statement of their -capability to support the test. The range process can take 6 months or -more. Although documentation requirements vary among the ranges and -centers, most require the development of a Program Introduction Document -(PID). When selecting a range, ensure the availability of applicable -range data is considered. To determine specific range initiation -requirements, consult the Universal Documentation System Handbook -501‑08, available from Secretariat, Range Commanders Council, -TEDT‑WS‑RCC, White Sands Missile Range, New Mexico 88002‑5110.

      National Cyber Range Considerations

      The National Cyber Range (NCR) provides test teams with a capability to -accomplish system training and perform disruptive and non-disruptive -cyber-attacks on a complete or sub-component of a system under test at -multiple classification levels. The NCR’s system reset capabilities make -it possible for cyber attackers to completely disable or even -catastrophically damage a system without the risk of negatively -impacting operational users or causing unrecoverable damage to the test -environment. This environment also provides a means for cyber offensive -and defensive training as well as basic user training before or during -test execution (to include cybersecurity assessments). As the NCR is a -contained range, connections with outside systems may need to be -emulated. Having said that, events can occur exclusively at NCR, or in -conjunction with other Joint Mission Environment Test Capability or -Joint Information Operations Range nodes. However, programs using unique -systems (i.e., components that won’t be used by any other programs in -the future) may incur a cost of purchasing the necessary hardware and/or -software. Test Directors interested in learning more about the NCR or -seeing if the NCR can support their program can contact the NCR directly -at osd.pentagon.ousd-atl.mbx.trmc-ncr@mail.mil.

      Test Targets

      Test targets, when applicable, should be realistic; they should be -operationally representative and challenging. The TD should coordinate -with the applicable MAJCOM to develop the target list. Through A‑2N, -coordinate with the appropriate intelligence agency on the design of -selected targets, existing and newly developed. A‑5R maintains current -lists of available aerial test targets in the inventory and is the POC -for obtaining target allocations. A‑5R also maintains contacts for other -target types such as surface targets. Funding for target‑related -expenditures must be included in the TRP.

      Range Safety Considerations

      Ranges and test centers are sensitive to safety considerations and may -require special test procedures, hardware, or software to reduce the -risk of a mishap during the test. Ranges and test centers frequently -require safety review boards before start of testing. The TD should -allow sufficient time to support these safety reviews. SE can assist in -resolving range safety issues or support in safety reviews. When -identifying required test resources and range requirements, test teams -should ensure weather warnings and advisories are considered in support -requirements (contact A‑2/9 for assistance).

      Range Instrumentation Considerations

      Instrumentation varies widely among ranges. Therefore, the test team -should carefully select a range to ensure instrumentation is available -to provide the required information and to allow the most realistic -representation of the operational environment.

      Range Data Processing Considerations

      Data processing capabilities and times are considered when the test -schedule is prepared. The range equipment user’s guide, facilities -handbook, or the test support contact may be consulted for typical -processing times. TDs must also consider the method by which test data -is transmitted for analysis (SIPRNET, courier, etc.).

      Test Article Instrumentation

      Identify the test article instrumentation requirements early to ensure -that instrumentation is sufficient to support test events. There is a -fine balance between not compromising the production‑representative test -article and obtaining telemetry from an instrumentation package. Test -article instrumentation should be compatible with the range or test -facility telemetry and data collection systems, with sufficient accuracy -and sample rates to enable verification of system performance. If the -test article needs to transmit instrumentation data, the instrumentation -package needs to be compatible with the MIL‑STD‑1553 multiplex data bus.

      Program Introduction Document Release Authority

      PIDs are executing direction approved in TRPs for obtaining test range -support. Det/CCs are authorized to release PIDs to range agencies. -Copies of all PIDs are sent to the AFOTEC/CC, A‑3 and A‑5/8 when -released to range support agencies by the Det/CC. Issues identified -during subsequent PID coordination with the supporting range are -highlighted during the Detachment Commander Monthly Program Update.

      The Use of Modeling and Simulation

      M&S includes, but is not limited to, digital M&S, hardware‑in‑the‑loop -(HITL) virtual simulations and test drivers such as data injectors and -stimulators. M&S also includes physical models of targets, threat -representations and combinations of simulations. Testers (DT&E, LFT&E, -OT&E) should collaborate early with the program manager’s (PM) M&S -proponent on planned uses of M&S for the purpose of identifying OT M&S -requirements, necessary verification and validation (V&V) activities, -and for securing program office M&S funding (as applicable) IAW -DODI 5000.02 and AFI 63‑101/20‑101, 9 May 17.

      AFOTEC uses digital M&S for two primary purposes: prediction of SUT -performance and extension of field test results. AFOTEC uses HITL -virtual simulations (and facilities) and test drivers to test system -performance under conditions that cannot be reproduced on an open‑air -range or on actual operational equipment. The OT&E Construct, test -concept and test plan should identify and explicitly describe the use of -M&S to include the use of distributed capabilities for executing -operational test events.

      M&S can play a helpful role in optimizing limited open‑air range (OAR) -or ground test facility test time. In addition, testers can examine -various configurations of the OAR and SUT. Resulting information -provides insight to maximize return from limited range time and to -investigate areas of principle interest to the warfighter.

      With an adequate representation of the SUT, the test team can use M&S -assets to predict SUT performance and optimize field test events by -estimating SUT performance boundaries. The optimization enables -tailoring of field testing to address those areas that merit further -evaluation or are of special interest to the user.

      M&S can fill in gaps associated with field testing in cases where it -would be too expensive or impossible due to lack of capability to -conduct an OAR‑only evaluation. The test team would first use M&S to -rehearse and construct valid OAR events and ensure a common baseline. -Then once the M&S is appropriately accredited, the test team can use it -to run events beyond the scope of OAR events.

      As an example, consider testing an air‑to‑air missile system, where -the primary target of interest is a foreign fighter. Since it would be -impractical or impossible to fire the SUT missile at an actual foreign -aircraft, OAR events may consist of firing the SUT missile at a USAF -fighter configured as a surrogate foreign aircraft. M&S would then -repeat the OAR drone aircraft firings and “extend” the results to the -foreign aircraft of interest by executing the M&S with a -representation of the foreign aircraft signature and other parameters -of interest, provided by an external organization (NASIC, MSIC, etc.). -AFOTEC could then provide the user information regarding SUT -performance versus real threats.

      Other reasons for using M&S are safety concerns, environmental concerns -(hazmat), treaty limitations, OPSEC concerns, or support concept -limitations.

      Whenever the test team intends to use M&S results to capture information -in an OT&E Final Report, they need to ensure proper M&S accreditation. -Test teams are encouraged to contact A‑2/9 early in the life of a -program, primarily after the OT&E Construct is completed, for assistance -in determining M&S applicability and VV&A requirements. A‑2/9 and A-5/8 -maintains information on various DoD and AF M&S and VV&A applications, -including OT&E‑specific M&S/VV&A guidance.

      Test Capability Accreditation

      AFOTEC often uses test capabilities to create a pseudo-employment or -combat environment in which to conduct the operational testing. These -test capabilities may include M&S of the employment environment as well -as M&S of the SUT. The AFOTEC Accreditation Guide provides actionable -information for Test Directors, analysts, engineers, and program -managers on how best to plan, execute, and report accreditation of M&S -systems. The accreditation process involves:

      • Developing an executable plan, assessment, and report with focus on

        documenting the results of the accreditation assessment

      • Documenting the recommendations in support of the accreditation

        decision, and

      • Documenting lessons learned during accreditation

      Accreditation is applicable when a test capability is used directly or -indirectly to provide information that appears in an OT&E Final Report. -If a TD intends to draw weapon system capability conclusions (i.e., rate -measures) based upon the use of a test capability, accreditation is -required. AFOTEC accreditation policy exists to ensure standardization -across test teams and a consistent level of rigor in determining -adequacy of test capabilities. Accreditation activities should not -excessively burden test teams or lead to inordinate expense. The AFOTEC -staff lead for Accreditation is A-2/9. Refer questions about -Verification, Validation, and Accreditation to -UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil.

      Test capabilities used solely for test‑planning purposes and assessments -(such as observations, EOAs) do not require a formal accreditation, -although the analyst should exercise a similar process to ensure that -the test capability is adequate and to identify risks involved and how -they may affect the overall test. Any informal accreditation -investigation procedures (peer review, analyst investigations, etc.) -should be documented to ensure continuity when program personnel change.

      AFOTEC’s mission is to Deliver Combat Capability through Operational -Test. AFOTEC often uses test capabilities to create a pseudo-employment -or combat environment in which to conduct the operational testing. These -test capabilities may include M&S of the employment environment as well -as M&S of the SUT. The test capabilities used in a given test do not -always represent the employment environment with 100% accuracy. There -are usually some differences in fidelity between the actual combat -systems and test representations. Given these differences, AFOTEC is -careful in drawing conclusions about SUT capabilities and ensures that -the representation of the employment environment is adequate to draw -credible conclusions. Inherently, AFOTEC assumes some degree of risk -when using test capabilities to represent an employment environment or -SUT to determine SUT capabilities. The purpose of accreditation is to -characterize that risk and ensure the risk is acceptable.

      See the AFOTEC Accreditation Guide accreditation details.

      Test Constraints and Limitations

      Limitations may be identified at any point in a program, however the -earlier a potential limitation is identified, the more likely it can be -resolved without impacting OT&E credibility. The TD and core team -including A-5R and/or A‑8Z are encouraged to identify limitations as -early as possible. The documentation provides justification for -continued improvement and modernization of test capabilities that -ultimately lead to more useful and relevant T&E reports and better -systems delivered to the warfighter. A limitation is something that -would influence being able to accomplish a credible operational -evaluation.

      • Limitation: A limitation affects the ability to evaluate certain

        aspects of a weapon system or to re‑create certain aspects of the -operational environment. Limitations can be due to differences in -the scenario (operational versus test), test capabilities such as -threat simulation, range restrictions (safety, physical airspace), -specific test measurement constraints, numbers of test articles, -or the threat lay down (types and numbers). Limitations, once -identified, are carried throughout all phases of the test program -unless the underlying factors are no longer applicable. A system -that is not production representative for an OT&E may be -identified as a limitation.

      • Mitigation: Each limitation requires the team to plan a

        mitigation to reduce the risk to the evaluation of the system. -Mitigation is intended to reduce the impact of the limitation to -the point where the evaluation is still credible. There are -typically few, if any, limitations in conducting credible EOAs and -OAs. However, when there are limitations, mitigation may be -different for an EOA, OA, or IOT&E. M&S is one method used to -mitigate a limitation. Teams should actively pursue mitigation of -a limitation in order to have an adequate test.

      • Impact (of a limitation after mitigation): The impact should

        describe the extent to which the limitation will (for a plan) or -did (for a report) affect the quality, completeness and/or -confidence of our evaluation of the system under test’s -effectiveness, suitability and mission capability. The intent is -to acknowledge limitations and inform the decision‑maker and -warfighter of the extent to which the limitations will or did -affect our ability to report weapon system performance. The impact -should clearly state what characteristics or attributes of the -evaluation are affected.

      Table 12 provides some example limitations, mitigations, and impacts.

      Table 12. Examples of Limitations

      LimitationMitigationImpact
      Limited UAS System Availability

      Coordination with operational unit to share assets between the field training unit and IOT&E test

      Leverage combat missions

      Inability to fully evaluate all measures

      Cybersecurity not evaluated

      Limited Flight Hours for Reliability, Maintainability and Availability EvaluationUse reliability availability logistics operations modelReported values may not reflect actual values in operational use
      Limited capability of Red Team to test weapon system via data link while in flightCoordinated with AFTC to emulate mission parameters in anechoic chamber to allow Red Team cyber attacks

      Cyber-exploitation effects not fully evaluated

      Inability to fully evaluate all measures

      Lack of Threat Systems at Test FacilitiesNoneInability to report system effectiveness versus some threats
      No integration of Lynx Radar Capability in Mobile Ground Control StationNoneUnable to evaluate Lynx synthetic aperture radar

      Basis of Estimate for Test Resources

      Together, the set of test events, test methodologies and test scenarios -form the basis of estimate. They describe why you are testing, what you -are going to do and how you are going to do it. Underlying the basis of -estimate is a set of assumptions that are validated to the extent -possible and documented. For the OT&E Construct, particular focus is -placed on the high cost (which includes high level of effort) and -long‑lead items. Typical examples of such items are threats, -instrumentation and M&S efforts. Some of these items have been -identified throughout the preceding steps. In forming the basis of -estimate, these previously identified items are consolidated and test -designs are reviewed to identify new items. Collectively, there may be -overlap between the resources required for each COI. These should be -identified and a consolidated list of resources should be provided (with -traceability and rationale).

      Table 13 contains the basis of estimate contents.

      Table 13. Contents of Basis of Estimate

      Content AreaContent Expectations
      COIsThe COIs define the operations that need to be exercised during OT&E and provide 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.
      Test EventsFor the particular test design(s) underlying the test events, a review of the factors and levels provide 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.
      Test MethodologyHow 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.
      Test ScenariosTest 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.
      AssumptionsAlthough assumptions may not directly drive resources, they provide indicators of potential risks and disconnects with other organizations.

      Initial Resource Estimates

      The core team uses the OT&E Construct basis of estimate to refine -initial resource estimates documented in the initial TRP. The Detachment -TRM updates the TRP to support the ITD Brief. The TD and Det TRM review -each resource category of the TRP to determine which line items need -costing and which ones need to be paid for by AFOTEC. Table 14 contains -the OT&E support costs breakdown.

      Table14. Operational T&E Support Costs

      AFOTEC PaysAFOTEC Does Not Pay
      • Range costs

      • Equipment Rental

      • Printing and reproduction

      • Communications

      • Real property maintenance and construction

      • Contractor support for OT&E

      • Data reduction

      • Special supplies and equipment

      • Leases

      • Civilian pay for (temporary over hires)

      • Per diem and travel

      • Transportation of equipment required for test

      • Supplies and equipment

      • Dry run planning

      • Test preparation

      • COTS M&S supporting test planning and reporting (including accreditation)

      • Cybersecurity testing (cooperative vulnerability & penetration assessment/ adversarial assessment)

      • Acquisition/modification of the system

      • Aircraft flying hours (other than range support aircraft)

      • Acquisition costs for major test vehicles

      • 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.

      • Missiles, munitions and targets

      • Telemetry kits

      • Range infrastructure

      • Type 1 (contractor) training

      • Digital M&S that produces data for OT&E

      • M&S V&V

      Identifying Resources. To move from the basis of estimate to a -completed test resource plan (TRP) takes a significant amount of effort. -This is an iterative process, and teams will generally refine the -initially planned events/activities based on resource availability, -realism, cost, etc., which are focused on arriving at the best -cost-benefit solution.

      The actual costing of resources, developing agreements, and many other -detailed steps required to source and cost are not captured here. These -specifics depend on acquisition and test approaches (joint, OT lead, -resource types, participants, funding strategies, time-to-test start, -infrastructure developmental needs, etc.), and teams rely on the -Headquarters and Detachment resource managers to support each OT&E -Construct effort.

      Documenting the Operational Test and Evaluation Construct

      Documentation cannot be overstated. Too many programs efforts have been -lost and needed to be re-accomplished because they were not properly -documented or in some cases, not documented at all. Each of the process -steps above have a recommended documentation approach. Why documentation -important?

      • The only constant with acquisition programs and the people who work -them, is change. Personnel come and go, and programs evolve. When -new people start a program, questions about how and why the OT&E -looks the way it does.

      • Leadership often ask why OT&E is doing various activities

      • DOT&E often has questions about the OT&E approach

      • Integrating testing is best served by robust OT&E documentation

      • Provides the foundational products and narrative for TEMP and OT&E -plan inputs

      Following the test design development, the TDM provides the test design -products to the TD. Using these products, the TD then begins developing -the ITD Briefing with support from his core team for presentation to the -AFOTEC/CC on the date specified in the tasking order. This briefing will -be developed and coordinated electronically for 2‑letter approval. The -briefing is an internal‑only AFOTEC product (i.e. it is not presented to -DOT&E). The purpose of the ITD Briefing is to convey to the AFOTEC/CC, -with a high degree of confidence, the complete beginning‑to‑end scope of -OT activities, resources, and costs with rationale. The ITD Briefing -indicates the specific acquisition events that the planned OT activities -support. The Detachment TD presents the acquisition information in a -briefing to the AFOTEC/CC for approval. Tailor the level of detail in -each area within the briefing to fit the specific program circumstances. -If a particular subject area in the ITD Briefing template does not apply -to a program, do not include that subject area in the briefing. -Significant issues should be resolved with appropriate HQ directorates -before the formal ITD Briefing. The ITD Briefing must include all -supporting information by using embedded documents, as described in the -briefing template. Following completion of the briefing, the OT&E -Construct is updated as required by the Detachment TD to reflect the -decisions made. The detailed ITD Briefing template is found on the -AFOTEC SharePoint.

      The OT&E Construct supports early integration and promotes the -combining, where appropriate, of DT and OT events to satisfy both DT and -OT objectives. Remember that throughout IT&E planning and execution, the -individual DT and OT objectives should not be compromised. Early -integration of DT and OT planning provides the foundation for the MS A -(and beyond) Test and Evaluation Master Plan development and supports -identification T&E requirements needed for RFPs. The TEMP is an -opportunity to document integration with the DT community and reduce -dedicated OT events when they have been accomplished satisfactorily in -IT&E. These events are only removed from dedicated OT when OT -requirements have been met.

      \ No newline at end of file diff --git a/sites/oteguide/fn_guides/analyst_test_design_guide/index.html b/sites/oteguide/fn_guides/analyst_test_design_guide/index.html deleted file mode 100644 index 40cb87d5..00000000 --- a/sites/oteguide/fn_guides/analyst_test_design_guide/index.html +++ /dev/null @@ -1,1621 +0,0 @@ -Analyst Test Design Guide

      Analyst Test Design Guide

      Last Updated/Reviewed: 08 December 2020

      Originating Office: AFOTEC A-2/9

      - - - image1 - -

      OVERVIEW

      This guide is an overview of test design, with a strong focus on the -types of designs that are most often used in AFOTEC. It is intended to -serve as a reference for both new and senior analysts and assumes -familiarity with the AFOTEC OT&E Guide. It is meant to be consulted -several times during the life of a test program. The guide begins by -presenting an overview of AFOTEC's Initial Test Design Framework. The -bulk of this guide presents the types of test designs typically used at -AFOTEC, their strengths and weaknesses, and their measures of merit. The -remainder of the guide discusses common situations encountered in test -design along with suggested remedies, as well as best practices and -pitfalls.

      AFOTEC is charged with evaluating the operational effectiveness, -suitability, and mission capability of a system under test (SUT). That -evaluation must be technically credible; i.e., the results must be -accurate and sufficient to support and defend the conclusions the test -team reports.

      Operational sufficiency and technical adequacy are the foundation for -technical credibility. Operational sufficiency addresses the breadth of -operations and conditions, test execution, and whether the test was -conducted in an operationally realistic and representative environment. -The focus of this guide is on the second critical area: technical -adequacy. A test is technically adequate if analysis of the test data -provides the user/warfighter with sufficient information to make -fielding and employment decisions. This guide provides information to -create a statistically rigorous test design that will lead to a -technically adequate test.

      Creating statistically rigorous test designs takes careful planning. All -tests are designed; some are designed well and some are designed poorly. -The principles and concepts of design of experiments (DOE) provide -time-tested statistical tools and methods for maximizing the information -obtained from a test. Using this test design guide, a test analyst can -make design choices based on a sound understanding of DOE principles. As -a result, the analyst will be able to collect and analyze the -appropriate data leading to an objective and defensible report.

      The AFOTEC process to execute an operationally sufficient and -technically adequate test is grounded in the seven-step design of -experiments process (Montgomery, 2013). Table 1 lists the seven steps on -the left and AFOTEC's coinciding steps and events on the right.

      Table 1. The DOE and AFOTEC Processes

      DOE Process StepAFOTEC ProcessAFOTEC Event
      1. Recognize and state the problem

      Understand missions and battlespace through the development of the EV-1, requirements/EV-2, COIs/operations/OCs, and ESC

      Determine the purpose/goal of test

      ITD Meeting
      2. Select the response variableDefine mission oriented response variables (MORV)ITD Meeting
      Develop MeasuresMeasures Workshop
      3. Choose the factors, levels and range

      Develop factors and levels

      Apply factor management

      ITD Meeting
      4. Choose the experimental design

      Choose and evaluate the design based on the goal of the test, factors and levels, and factor management

      Develop scenarios and test events

      Post ITD Meeting
      Develop Scenario-measures-test event linkageTest Concept Brief Preparation
      5. Perform the experimentExecute the testTest Execution
      6. Analyze the dataAnalyze the dataPost Execution
      7. Draw conclusions and make recommendationsReportReporting

      This guide briefly discusses DOE process steps 1 through 3 framed within -the AFOTEC test planning process, but focuses on step 4: the process of -selecting an appropriate test design.

      ELEMENTS OF THE TEST PLANNING PROCESS

      Critical Operational Issues and Operations

      The AFOTEC process begins with a thorough understanding of the missions -that the SUT is expected to enable or support; the AFOTEC OT&E Guide -provides an overview of this process. Once the mission is defined, the -core team identifies the COI and subordinate operations. Operations are the distinct activities or -processes that occur within a COI and are the focus of test design. Each -COI will have at least one operation.

      Response Variables

      Each operation under a COI shall have at least one Mission Oriented -Response Variable (MORV). A MORV is an indicator that a system under -test can successfully accomplish its mission in the operational -environment. MORVs are the dependent variables that guide the initial -test design (ITD) process. Ideally, a MORV should be quantitative -1 . If a MORV is qualitative -2 an analyst should develop one or more -continuous response variables (measures) to complement it. While a -qualitative MORV may be a satisfactory indicator of mission success, it -might also require considerably more testing and resources than a -quantitative MORV. In statistical terms, for a given test size, the -population parameter 3 -estimates 4 for a continuous -response have less variability than estimates for the population -parameter for a binary response. Therefore tests using binary MORVs must -have a significantly larger sample 5 size than tests using continuous MORVs; i.e., more runs -are required to achieve equivalent statistical quality and precision of -the parameter estimates. Thus qualitative MORVs should be used with -caution.

      Ideally, a MORV should be written as a measure (see the Measures Guide -for further guidance on writing measures). However, it is not necessary -that a measure threshold be identified for a MORV. If a MORV becomes a -measure during the measures workshop, the appropriate detail is then -added.

      Factors, Levels, and Prioritization

      A key event in the AFOTEC process is the initial test design (ITD) -meeting. The following organizations send representatives to this -week-long event: AFOTEC headquarters; the detachment conducting the -operational test; Director, Operational Test and Evaluation (DOT&E); the -Institute for Defense Analysis (IDA); the program office (PO); the -developmental test organization; and subject matter experts from the -user community.

      An ITD has several phases. In the first phase the COIs, operations, and -MORVs are refined and vetted. In the second phase the ITD participants -develop a list of factors 6 and -levels 7 (F&L) that apply to each -MORV under an operation. Factors are the independent variables that -define the battlespace---with a range of values called levels---that may -affect a MORV when the factor's level is changed.

      The AFOTEC Operational Test & Evaluation (OT&E) Guide has several -examples of desirable factor characteristics that should be considered -during the test design process. There are attributes of the factors -(quantitative data type, qualitative data type, number of levels, etc.) -which will significantly affect the size and quality of the test design. -These attributes should be considered by the analyst as they facilitate -the F&L discussion during the ITD process.

      In addition to the characteristics and examples in the AFOTEC OT&E -Guide, the facilitator should consider the following:

      • It is a best practice to use quantitative factors with numeric -values for levels (e.g., Altitude: 10,000 ft and 30,000 ft) instead -of categorical factor levels (e.g., Altitude: Low and High).

      • Factor levels must be mutually exclusive, meaning that two levels of -the same factor describe conditions that cannot simultaneously -occur.

      In phase three, the ITD participants determine two things: the magnitude -of a factor's impact on each MORV, and the likelihood of each factor -level occurring in the operational environment. Based on the combination -of a factor's impact and the likelihood of occurrence for each of its -levels, the test team chooses one of four methods for incorporating that -factor in the test design.

      1. Vary -- The factor is deliberately manipulated during the test

      2. Fix -- The factor level is held constant during the test

      3. Log -- During a test run, the level of this factor is recorded -as an observation

      4. Demo -- The level will be incorporated into a test run that is -executed and analyzed separately from the design incorporating the -varied factors

      Choosing one of the four methods for each factor is referred to as -factor management. Figure 1 gives general guidance on which of the four -management methods to select for a factor level given a combination of -the factor's magnitude of impact and the likelihood of encountering the -factor level.

      Figure 1. Factor Management Guidance

      - - - image3 - -

      The test team should keep in mind that the factor level likelihood -should be determined in the context of the system conducting its -mission, not the likelihood the level occurs in general. For example, a -factor level related to a nuclear weapon system may be very unlikely in -peacetime, but may be very likely in the context of a nuclear weapon -employment. The latter is the likelihood that should be documented.

      It is important to remember that even if a factor's levels occur in -unequal proportions in the operational environment, the frequency that -the levels occur in the test design may not coincide with those -proportions. Factor levels that occur disproportionally frequently (or -infrequently) in the test design could create an unrepresentative sample -of the system's overall performance across a typical set of operational -conditions. Consequently, the test design could cause an overly -pessimistic or optimistic assessment of the SUT.

      Test Design Workbook

      The major product from an ITD that summarizes the test planning elements -and F&Ls is the Test Design Workbook (TDW). Figure 2 shows the F&L tab -for COI 1 from the TDW for the X-100 Block Upgrade 1.1 (X-100 is a -fictitious program). COI 1, Does X-100 1.1 support Airland operations -, is shown at the top. This COI had three operations: Takeoff & -Departure, Enroute, and Arrival . Operation 1, Takeoff & Departure -, is shown underneath COI 1. The MORV for Operation 1 is Delta Time -between Planned and Actual Take-Off Time .

      The test team developed a list of 23 factors for Operation 1 at the ITD. -However, only two will be strategically controlled (varied) during the -operational test. The other factors will either have their levels -demonstrated (demo), fixed during the test runs -8, or logged. Typically factors will -be logged because the levels cannot be controlled. However, for some -factors that are controllable but judged to be inconsequential, the -analyst may choose to log the levels in case the factors are actually -significant.

      Four of 23 factors are shown: two factors to be varied and two factors -that cannot be controlled (which will be logged.) In the columns under -prioritization, the test team noted the magnitude of impact of the -factor, and the likelihood of encountering each factor level.

      Figure 2. F&L Tab of TDW

      Accurately selecting and prioritizing factors, levels, and their impact -on the system's MORVs is extremely important to ensure the test design -selected will achieve the test goal.

      GOALS AND TYPES OF TEST

      Before selecting the test design, the goal of the test must be -established. The goal not only determines how the test is designed and -executed but how it is reported as well. Within AFOTEC, there are -generally three goals of a test:

      • characterize system performance

      • compare system performance to a requirement or to another system

      • identify problems with the system

      A test program may include up to all three test design goals. Generally, -each goal will have its own collection of test events based on one of -the design types outlined later in this guide. The above list states the -common goals in AFOTEC testing, but it is not all-inclusive. If a test -team has a different goal for their operational test, they should -provide an explanation including the unique nature of the desired test -goal and how it affects the design, execution, and reporting of the -test.

      Characterize

      When characterizing a system, the test goal is to analyze the system's -measures across the operational conditions (battlespace) defined by the -factors and levels. In addition, the test team quantifies the -effect 9 that changing factor -levels (and combinations of factor levels) have on the measures. To -accomplish this test teams use test designs that allow the estimation of -the factors' main effects 10 -and the factor interactions 11 -.

      Designs used to characterize the system vary the levels of multiple -factors simultaneously with the intent of testing and reporting the -performance of a system under different operational conditions. They -also enable an analyst to determine which factors are most influential -on system performance. The data produced by these designs can be used in -future testing and for the development of operational Tactics, -Techniques and Procedures.

      Compare

      When the goal of a test is to compare, the test team gathers data on a -system and compares it to data from another system, to a requirement -threshold, or to some other criterion. System comparisons do not provide -information about the system's performance across the battlespace.

      Problem Identification

      When one of the test goals is problem-identification, the test team -attempts to determine whether a "success" or "failure" occurs at one or -more factor level combinations that define the battlespace. One approach -is to use combinatorial designs; these designs efficiently combine -factor levels so that problems caused by specific factor level -combinations can be identified with less resources than designs used for -system characterization. However, combinatorial designs do not generally -provide data that can be analyzed with statistical modeling (system -characterization.)

      Another approach is to demonstrate (demo) strategically chosen (and -usually infrequently occurring) factor level combinations. The data from -these demo runs are analyzed separately from the data associated with -test runs used to characterize the system performance. The analysis -essentially determines if a failure occurred during the demo.

      TYPES OF TEST DESIGNS

      Choosing the most appropriate test design is a combination of science -and art. The choice requires expertise on the SUT, the operational -mission it supports, and DOE principles . Each -of the designs in this section has strengths and weaknesses depending on -the test goal and the nature of the SUT.

      An AFOTEC test program may use a combination of the designs presented in -this section. It is typical to use a separate test design for each -operation under a COI, as factors and levels are often different between -operations. Some MORVs may even require a separate test design.

      Test designs have associated quality indicators; within AFOTEC these -indicators are referred to as measures of merit. Measures of merit -provide a basis for comparison when choosing between multiple designs. -Also, measures of merit are used as evidence that a test design meets -the AFOTEC standards for technical adequacy. The Test Design Measures of Merit section of this guide presents a -more detailed explanation of the measures most often used at AFOTEC.

      Factorials

      A factorial design 12 is a list -of test runs in which multiple factors are varied simultaneously from -run to run. This list of runs is called a test event matrix (TEM). The -special structure of the factor level combinations in the TEM enables -the tester to estimate the main factor effects and interactions between -factors. The following sections discuss two types of factorial designs: -full factorials and fractional factorials.

      Full Factorial

      A full factorial is a test design that includes every possible -combination of the levels across all factors. Full factorial designs -have the following desirable properties:

      • Every factor level occurs equally often in the test matrix. For -example, if a factor has 4 levels and there are 16 test runs, each -factor level will occur in 4 runs. This property is related to -balance 13 , and it -ensures that factor levels do not have a disproportionate influence -on the analytical results.

      • The design includes every possible factor level combination in the -TEM. This ensures that system performance can be analyzed over the -entire battlespace and we can identify factor level combinations -that lead to exceptionally negative or positive performance.

      • The effects (main effects and all interactions) are completely -uncorrelated in the TEM. This means the estimation of each effect is -not biased (influenced) by other main effects and interactions.

      Full factorials are orthogonal 14 , balanced, and easy to construct with or without -software. Since every possible factor level combination must be present -in a full factorial, these designs are not applicable to test scenarios -with disallowed combinations 15 -of factors.

      Use the following process to construct a full factorial design in JMP -13. The example shown in figure 3 a/b is for the X-100 Block Upgrade 1.1 -program.

      Creating Full Factorial Designs in JMP 13:

      1. From the DOE menu, select Classical , then select Full -Factorial Design (figure 3a)

      2. Specify the Factors and levels. In the Factors section, add the -continuous and categorical factors using the drop down menu. Specify -the number of levels for each factor. The factors and levels can be -given appropriate names. Figure 3b shows the input for the X-100 BU -1 example.

      3. Click Continue when all of the factors and levels have been -entered.

        Figure 3a. Creating a Full Factorial in JMP Figure 3b. Enter the Factors and Levels

        - - - image5 - - - - - image6 - -

      4. Specify your Run Order ; JMP can output your design runs in -random order, or sorted from left to right (or right to left) by -factor level. The number of runs is the product of the number of -levels for each factor---in this example the number of runs is -3x4x4x3=144.

      5. Choose the number of center points 16 (only applicable when using continuous factors).

      6. Choose the number of replicates . The number of replicates is -the number of times you want the original full factorial design -repeated. Thus 1 replicate implies 2 copies of the full factorial. -Note that when reporting the number of replicates in a test design -worksheet (TDW), the AFOTEC convention is to state the number of -replicates as the number of copies; thus, on a TDW, 2 replicates -implies 2 copies.

      7. Click Make Table (figure 4a)

      8. JMP outputs a new design table (figure 4b)

        Figure 4a. Output Options Figure 4b. The Design Table - - - - image7 - - - - - image8 - -

      The main weakness of a full factorial design is that the run size grows -rapidly with the addition of factors. The number of runs in a full -factorial design is equal to the product of the number of levels of each -factor in the design. In the X-100 BU 1.1 example, if we added just one -additional 2‑level factor, the number of runs in the design would double -from 3x4x4x3=144 runs to 288 runs! Because the number of runs increases -so rapidly, a full factorial design is infeasible for many test programs -unless there are only a small number of varied factors.

      Rather than reducing the number of varied factors in order to enable the -use of a full factorial design, we recommend using one of the other -design types that are discussed in the subsequent sections. This -recommendation is rooted in the concept that AFOTEC tests should also be -operationally sufficient as well as technically adequate. A test is -operationally sufficient if it provides both the decision maker and the -warfighter with results drawn from test events executed across a -sufficiently broad set of operational conditions.

      Fractional Factorial

      A fractional factorial design is a strategically selected fraction -(typically ½ or ¼) of the runs in a full factorial design. These designs -have many of the same advantageous characteristics of a full factorial. -Depending on the degree of fractionation, fractional factorials can -yield the same information about main effects and two-factor -interactions (2FI) with fewer test runs. They are easy to construct, -orthogonal, balanced, and are an economical alternative to full -factorials.

      As an example, suppose the X-100 BU 1.1 program chose to vary four -two-level factors, as shown in figure 5.

      Figure 5. Sample of F&Ls for X-100 BU 1.1

      - - - image9 - -

      The full factorial test design matrix would look like the design in -figure 6a. However, if test resources were not available to execute 16 -test runs, a fractional factorial design could be used to execute the -test in 8 runs---a ½ fraction of the original full factorial. The test -design matrix would look like the design in figure 6b. It is important -to note that this example is only intended to illustrate the concept of -a fractional factorial; practically speaking the design in figure 6b -should not be used at AFOTEC since main effects are confounded with 2FI. -How to choose appropriate fractional factorials is covered in the next -section.

      Figure 6a. Full Factorial Figure 6b. Fractional Factorial


      - - - image10 - - - - - image11 - -

      Observe that columns are balanced in both the full factorial and -fractional factorial figures; i.e., each factor level occurs the same -number of times. Also, for the runs involving a specific level of one -factor, the other factors' levels are also balanced. For example, in the -first four runs of figure 6b where the departure type factor is set to -the instrument level, there are 2 occurrences of each of the other -factor levels: 2xDay, 2xNight, 2xLocal, 2xNon-local, 2xOff, and 2xOn. -Recall that this means the fractional factorial is an orthogonal design.

      Fractional factorials have the projection 17 property; if a factor in the design is determined to be -insignificant and its associated design column removed, the degree of -fractionation is reduced. In figure 6b, if Autopilot was not an -active effect 18 (significant -factor), the resulting design is no longer a ½ fraction, but a full -factorial in the three remaining factors. If the fractional factorial -was a ¼ fraction, removing one insignificant factor creates a ½ -fraction.

      The strategy of using only a fraction of the runs in a full factorial is -based on the Sparsity‑of‑Effects 19 principle. The principle implies that the effect of the -higher order (3-factor or greater) interactions are likely negligible. -Although there is strong evidence that this principle applies in OT, it -is not always true and therefore should be assumed with caution. It is -wise to verify this assumption by discussing the issue with system -experts.

      Although fractional factorial designs save resources and have many of -the same properties as full factorials (balance, orthogonality), these -designs have less information than full factorials and may not allow the -independent estimation of the main effects and 2FI if the fractionated -design is too small. The next section discusses how fractional -factorials are classified based on the degree to which independent -factor estimation is impeded.

      Resolution, Aliasing, and Confounding

      A central issue in experimental design is minimizing the degree to which -factors are correlated 20 with -each other while adhering to the test resource constraints. To -illustrate the problem with correlated factors, figure 7a shows three -possible designs for two varied factors in the X-100 BU 1.1 test. -Suppose the average response for runs 1-4 was higher than the average -for runs 5‑8.

      Figure 7a. Perfect Aliasing Figure 7b. Partial Aliasing Figure 7c. Orthogonality - - - - image12 - - - - - image13 - - - - - image14 - -

      The problem with the first design in figure 7a is that every time the -Departure Type factor is set at the Instrument level, the Takeoff -Procedure factor is set at the Normal level. Also, every time the -Departure Type factor is set at the Tactical level, the Takeoff -Procedure factor is set at the Adjusted Max Effort level. Since both -factors' levels were changed at the same time, it cannot be determined -if the higher response in runs 5-8 was due to changing the Departure -Type factor, or due to changing the Takeoff Procedure factor---or -perhaps the increase was due to changing both factors.

      This ambiguity is because Departure Type and Takeoff Procedure are -perfectly correlated; i.e., a level of Departure Type is always -matched with the same level of Takeoff Procedure . In the terminology -of DOE, these factors are perfectly aliased 21. It is also equivalent to say that Departure Type and -Takeoff Procedure are confounded 22.

      The second design in figure 7b is also not ideal. Although the factors -are no longer perfectly aliased (perfectly correlated), they are still -correlated, i.e. when Departure Type is set to the Instrument level, -it is more common that Takeoff Procedure is set to the Normal level. -In this scenario, Departure Type and Takeoff Procedure are partially -aliased; which means the estimate of the effect of Departure Type on -the response will be influenced by the effect of Takeoff Procedure .

      The ideal case is the third design shown in figure 7c. When Departure -Type is set to the Instrument level, the two levels of Takeoff -Procedure appear equally often (2x each)---likewise for the Tactical -level. Thus the two factors are uncorrelated and therefore this design -is orthogonal. The effect of changing the level of the Departure Type -factor from Instrument to Tactical can be independently determined -because the effect of changing from the Normal level of Takeoff -Procedure to the Adjusted Max Effort level will average out over each -level of Departure Type .

      Aliasing and confounding are sometimes used interchangeably, but -confounding conventionally refers to perfect aliasing. Any time a test -design is not a full factorial, there are some effects--- main effects -or interactions of some degree---that are aliased/confounded. Fractional -factorials do not have any partially aliased effects; the effects are -either orthogonal or completely confounded.

      Note that the use of full and fractional factorials assumes that the -levels of factors can be chosen independently; i.e., If level 1 for -factor A is chosen, that does not constrain what level is chosen for -factor B. Occasionally the levels of two factor cannot be independently -chosen, perhaps due to some physical constraint---in other words these -factors are naturally correlated. For example, if one factor is user -weight and a second factor is user height (each with two levels, low and -high), it may be difficult to find military users who are relatively -short and relatively heavy; likewise it may be hard to find military -users who are relatively tall and relatively light. In this situation it -may not be possible to have separate factors for weight and height since -all of the possible level combinations cannot be effectively covered in -the test.

      The resolution 23 of fractional -factorial designs gives information about the type of effects that are -confounded; the convention is to use roman numerals to signify the -resolution. Table 2 shows which types of effects are confounded at the -three common design resolutions. The size of a design increases as the -resolution increases. Thus test teams may not have enough resources to -use the ideal resolution V design.

      Table 2. Design Resolution

      ResolutionAliasing of Effects
      III

      Some/all main effects are aliased with 2FI

      Some/all 2FI are aliased with other 2FI

      IV

      All main effects are orthogonal to 2FI

      Some/all 2FI are aliased with other 2FI

      V

      All main effects are orthogonal to 2FI

      All 2FI are orthogonal to other 2FI

      Since main effects are confounded with 2-factor interactions in -Resolution III designs, these designs are not recommended for use at -AFOTEC. Resolution III fractional factorials are typically used as -screening designs 24 . They are -intended for experiments where the intent is to determine the active -main effects before subsequent testing is conducted to de-alias and -estimate the active 2FI. Since AFOTEC does not typically conduct -follow-on testing, resolution III designs do not provide enough -information during a test event and are not suitable for operational -test. If it is not feasible to use a larger resolution IV design, then -an optimal design (discussed later in this section) is a better design -choice.

      Resolution IV designs are an appropriate choice when resource -constraints are a significant concern and a larger resolution V design -cannot be executed. Main effects can be accurately estimated because -they are uncorrelated with any 2FI. However 2FI are correlated with -other 2FI. Since it is often the case that multiple 2FI are active, -these designs do may not facilitate an adequate characterization of the -system in the battlespace.

      Resolution V designs are the most popular choice. If the -Sparsity-of-Effects principle is valid, three-factor interactions or -higher are likely negligible, so main effects and 2FI are most likely -the only important effects required to characterize a system. Since both -main effects and 2FI are orthogonal to other main effects and 2FI in -resolution V designs, these are more efficient designs (require fewer -resources) for characterizing a SUT than full factorials.

      Any test design higher than resolution V is likely a waste of test -resources and any design less than resolution V represents an increased -risk of not discovering or accurately estimating all of the active -effects. The goal within AFOTEC is to minimize or eliminate the -aliasing/confounding for the main effects and all 2FI. When this is not -possible, a balance must be struck between what can be estimated and the -test resources available.

      Creating Fractional Factorial Designs in JMP 13:

      1. From the main JMP menu, choose DOE then Classical , then -Screening Design

      Figure 8. Creating Fractional Factorials in JMP 13

      - - - image15 - -

      1. In the Factors section, add the continuous and categorical -factors using the drop down menu. Specify the number of levels for -each factor. The factors and levels can be given appropriate names. -Figures 9a/b shows the input for the X-100 BU 1 example.

      2. Click Continue .

      3. Select " Choose from a list of fractional factorial designs " -(figure 9b).

        Figure 9a. Enter Factors and Levels Figure 9b. Request a List of Fractional Factorials - - - - image16 - - - - - image17 - -

      4. Figure 10a shows the fractional factorial design list provided in -JMP 13. Notice that JMP states the resolution of each design -(although they do not use roman numerals.) You can choose a standard -fractional factorial or you can choose a fractional factorial with -blocks (Blocks are discussed in the section of this guide titled, " -The Three Principles of DOE " Note that -the full factorial is also available as an option, since there are -no resolution V designs smaller than the full factorial.

      5. Select a design and click Continue .

      6. JMP presents menu options to evaluate and modify your design (figure -10b). The Aliasing of Effects output shows which effects are -aliased (confounded) with which other effects. Figure 11a shows that -in the X-100 BU 1.1 example, the ½ fractional factorial -(resolution IV) has 3 pairs of 2FI that are aliased.

        Figure 10a. Fractional Factorial Options Figure 10b. Additional Diagnostics and Options - - - - image18 - - - - - image19 - -

      7. Specify your Run Order ; JMP provides options to sort (or -randomize) the run order and add replicates to your design.

      8. Click Make Table to create the fractional factorial design -(figure 11b)

        Figure 11a. Aliasing of Effects Figure 11b. Fractional Factorial Design - - - - image20 - - - - - image21 - -

      JMP can only create fractional factorials if every factor is restricted -to two levels. There are methodologies for fractionating designs -involving factors with more than two levels, but that topic is beyond -the scope of this design guide. When it is not applicable to use -fractional factorials with 2-level factors, AFOTEC analysts typically -use JMP to create an optimal design; these designs are discussed in a -subsequent part of this section. The National Institute of Standards and -Technology has a comprehensive list of 2-level fractional factorial -designs here: -http://www.itl.nist.gov/div898/handbook/pri/section3/pri3347.htm

      For more information on fractional factorials and design resolution see -Chapter 8 of Montgomery, D. C. (2013). Design and Analysis of -Experiments, 8th Edition. Hoboken, NJ: John Wiley & Sons, Inc.

      Optimal Designs (Computer Generated Designs)

      An Optimal design 25, -sometimes referred to as computer generated design (CGD), is a test -design whose levels are combined in a way that optimizes a specified -statistical criterion that is a function of the design matrix. Unlike -factorial designs, which are constructed using a standard method that -guarantees balance and orthogonality, optimal designs are constructed by -a computer implementing an algorithm. Design construction algorithms -combine factor levels into test runs with the goal of optimizing some -design quality criterion. The optimization incorporates constraints such -as run size or disallowed combinations of factors.

      Optimal design construction algorithms may not always find the "best" -design. One reason is that the algorithm may not be allowed to run long -enough to find the optimal combination of factor levels. Another reason -is that there may be multiple designs which have the same optimal value -of the chosen criterion. The generated design may be optimal for the -specified criterion, but another design (with the same optimal value) -may be superior in terms of a different un-evaluated criterion. As a -consequence, optimal designs must be evaluated for quality by a -knowledgeable test analyst. The test team should also modify the default -settings of the construction algorithm---as an example, the algorithm -run time---if a generated design has flaws.

      An optimal design is constructed based on a model specified by the -analyst. The analyst may include in the model any number of main -effects, two-factor interactions, or higher-order terms if necessary; -three-factor interactions and higher are not generally included at -AFOTEC based on the Sparsity‑of‑Effects principle.

      The optimality criterion chosen to create the design depends on the test -goal. The following are optimal designs that can be created with JMP -software.

      1. D-optimal designs - Used when an analyst places a priority on -accurate effect estimates. This is because D-optimal designs -minimize the joint variance of the parameters in the statistical -model. For example, when using continuous factors, these designs -minimize the joint variance of the linear regression -26 coefficients \widehat{\mathbf{\beta}} . When model -parameter estimates have low variance, we can expect the estimates -to be close to the true value (assuming we are using unbiased -estimates.) D-optimal designs are used most often in OT as they are -ideal for characterizing a system.

      2. I-optimal designs - Used when an analyst prioritizes accurate -predictions from a statistical model. These designs minimize the -average prediction variance of statistical models. Unlike D-optimal -designs which have test points located at the extremes of the design -space, some test points in I-optimal designs may be spread -throughout the design space (when continuous factors are used.) -These points improve a model's predictive capability across the -whole design space.

      3. Alias-optimal designs - Used when an analyst prioritizes -minimizing bias in the parameter estimates from un-modeled factors. -These designs minimize the aliasing (correlation) between the -specified model effects and other terms not included in the model. -This optimality criterion is typically used when a design is -constructed to estimate main effects only, but the analyst wants to -insure against 2FI which may be active (but are not included in the -model).

      Creating a D-Optimal design in JMP 13:

      1. From the main JMP menu, choose DOE then Custom Design -(figure 12a)

      2. Add the response variables

        a. One response variable is included by default. Change the -response name by clicking on "Y"

        b. For additional responses, use the Add Response drop down -menu in the Responses box. You can choose whether the -response should be maximized, match a target value, minimized, -or none of these

      3. Add the factors

        a. In the Factors box, use the Add Factor drop down menu to -add the appropriate type of factor. AFOTEC typically uses -categorical factors, although continuous factors are ideal; the -number of levels must be specified for Categorical and -Discrete Numeric factors

        b. For adding multiple factors of the same type and number of -levels, input the appropriate number in the Add N Factors -box

        c. If you have created a JMP table of your factors and levels, you -can populate them in the Factors box by clicking on the red -triangle to the left of Custom Design and choosing Load -Factors

      4. In the Specify Factors box, click Continue

      5. Linear constraints on continuous factors, or disallowed combinations -of categorical factors can be added in the Define Factor -Constraints box

      6. Only the main effects are loaded by default in the Model box -(figure 12b). To add more model terms click on the Interactions -drop down menu and choose 2nd (this will load all 2-factor -interactions -- if you want higher order interactions, choose those -as well)

        Figure 12a. Creating a D-optimal Design Figure 12b. Adding 2-way Interactions to Model - - - - image22 - - - - - image23 - -

      7. Input the number of runs. Select either the Minimum (determined -by the model terms you entered in the Model box), Default, -or enter the number of runs you want in User Specified (figure -13a)

      8. Click on the red triangle to the left of Custom Design

        a. Choose Optimality Criterion , then Make D-Optimal Design -(figure 13b)

        b. Choose Number of Starts ; enter an appropriate number and -choose OK

        c. Choose Design Search Time; enter an appropriate number and -choose OK

      9. Click on Make Design

        Figure 13a. Specify the Number of Runs Figure 13b. Specify the Optimality Criterion - - - - image24 - - - - - image25 - -

      10. At the bottom of the new window, set Run Order to Sort Left to -Right

      11. Click on Make Table . Notice that unlike when using a Full -Factorial or Screening design, there is no Pattern column

      12. To assess the designs balance, JMP has graphically see the results -(balance) of the design:

        a. From the JMP main menu, click on Analyze then -Distribution

        b. Under Select Columns , select all the factors except Y -(the response variable) and click on Y, Columns to add all -the factors to that box

        c. Click on OK

        d. The bar charts can be used to determine if each factor has -balanced levels, and whether the other factors' levels are -balanced over a factor level.

      Creating optimal designs requires a sound understanding of design -principles. Analysts can create an optimal design to meet the -requirements of almost any test situation, but should review the test -design to ensure the following:

      1. There is no excessive aliasing/confounding between main effects and -two-factor interactions; A good rule of thumb is to have -correlations below 0.5 as much as possible and not exceed 0.7.

      2. There are enough degrees of freedom (dof) for error estimation; a -good rule of thumb is to have at least 5 dof to estimate error.

      The aliasing structure in an optimal design can be very complex, which -results in biased effect estimates. The D-optimality criterion is most -frequently used at AFOTEC, as it minimizes the bias in the effect -estimates that results from correlation between the specified model -effects. When JMP is used to construct an optimal design, the design -diagnostics which can be used to evaluate the correlation structure are -provided under the Design Evaluation header.

      An analyst should create several optimal designs and compare them using -the Test Design Measures of Merit. The -algorithm that generates the optimal design may not always produce the -"best" design. Optimal designs are usually created based on a single -optimization criterion. In contrast, full and fractional factorials are -optimal over several optimality criteria; when fitting a model with main -effects and two-factor interactions, factorials are D-optimal, -I-optimal, and Alias-optimal. If the number of runs in a test is a power -of two and all factors have two levels, then the optimal design is a -full or fractional factorial.

      Unfortunately, it is possible an optimal design algorithm may not -produce a factorial when appropriate. As mentioned earlier in this -section, this may be due to insufficient run time for the algorithm or -another design has an equivalent value of the specified optimality -criterion. Consequently, it is wise to verify that the software used to -generate an optimal design actually produces a factorial design when -applicable.

      The number of runs in the test design can have a significant impact on -the quality of a design produced by a construction algorithm. Suppose -you have a design with two three-level factors and one four-level -factor. If you require a design with fewer runs than the full factorial -with 36 runs, you should choose a design size that is evenly divisible -by the number of levels in as many factors as possible. By doing this, -you make it more likely the factor levels are balanced. For example, if -the chosen design size is 26 it is impossible to balance both the -three-level and four-level factors. However, if the design size is 24, -then the design could be balanced; each level of the three-level factors -could be in eight runs, and each level of the four-level factor could be -in six runs.

      Augmented Designs

      When a test plan changes during execution, the uncompleted portion of -the design should be updated ( augmented 27 ) with new runs; optimal designs in particular may not be -robust to lost or altered test runs. Designs can be created and -augmented quickly with software, but logistical constraints may make it -difficult to adjust test events in real time. The following describes -how to augment designs in JMP 13. Note that JMP assumes that data is -entered in the response column.

      1. Augmenting a design in JMP 13:

      2. Open the existing design table in JMP

      3. From the main JMP menu, choose DOE then Augment Design

      4. Drag the response to the Y, Response box

      5. Drag the factors to the X, Factor box

      6. In the Action box, click OK

        Figure 14a. Augmenting a Design in JMP Figure 14b. Enter the Response and Factors - - - - image26 - - - - - image27 - -

      7. If the existing design has already been executed, it is a best -practice to check the box next to "Group new runs into separate -block" (See the blocking discussion.)

      8. Linear constraints on continuous factors, or disallowed combinations -of categorical factors can be added in the Define Factor -Constraints box

      9. To replicate the existing design, choose Replicate in the -Augmentation Choices box

      10. To add center points to the existing design, choose Add -Centerpoints in the Augmentation Choices box

      11. Otherwise choose Augment in the Augmentation Choices box

        a. Only the main effects are loaded by default in the Model -box. To add more model terms click on the Interactions drop -down menu and choose 2nd (this will load all 2-factor -interactions); If you want higher order interactions, choose -those as well)

        b. Under the Design Generation header, enter the total number -of runs in the design AFTER augmentation; e.g., given a -design with 20 completed runs, if you want to augment it with 10 -additional runs then enter 30 runs.

      12. Click the red triangle next to Augment Design , select -Optimality Criterion and select Make D-Optimal Design

      13. Click Make Design

        Figure 15a. Select an Augmentation Choice Figure 15b. Define the Model and Enter # of Runs - - - - image28 - - - - - image29 - -

      14. Click on Make Table

      15. To graphically see the results (balance) of the design:

        a. From the JMP main menu, click on Analyze then -Distribution

        b. Under Select Columns , select all the factors except Y -(the response variable) and click on Y, Columns to add all -the factors to that box

        c. Click on OK

        d. The bar charts can be used to determine if each factor has -balanced levels, and whether the other factors' levels are -balanced over a factor level.

      Designs for Computer Experiments

      Data for some test programs are obtained from simulation models, many of -which are deterministic 28. -This means that the simulation output does not change if the inputs are -held constant. In other words, a single observation obtained from a -given combination of factor levels (test point) provides all of the -information available about that test point.

      When obtaining data from deterministic simulations (or software systems -which have deterministic outputs) using a factorial design may not be -the best experimental design strategy. An efficient design strategy for -deterministic systems uses the following two principles:

      1. Designs should not replicate test design runs; one run provides -complete information about the response variable at that test point -because there is no variance in the response.

      2. Designs should allow for the fitting of complex models by providing -information about the response variable at all areas of the design -region.

      The next section discusses some alternative designs that follow the -above principles.

      Space-Filling Designs

      Space-filling designs are constructed so that they spread design points -evenly throughout a design region. These designs are used when the test -factors are continuous. The following are general construction methods:

      1. Disperse the design points as uniformly as possible in the design -region using distance measures.

      2. Obtain design points using sampling methods in the design region

      3. Utilize a hybrid distance measure/sampling approach

      Common construction algorithms for these designs include Uniform -sampling, Sphere Packing, and Latin Hypercube sampling.

      1. Uniform space-filling designs -- Design points are randomly selected -from a uniform distribution 29 -defined over the range of a factor. They are simple to construct and -augment (just add more randomly selected points to the space.) -However these designs tend to leave gaps in the design coverage when -the points are unevenly distributed---particularly when the number -of test points is small relative to the size of the design space.

      2. Sphere packing space-filling designs -- Algorithms pack circles, -spheres or hyper spheres of equal radii into the design space and -use the center of each as the design point. Sphere packing designs -give even coverage across the design space but are difficult to -augment because the spheres have already been optimally "packed" -into the design space and any new points would upset the -distribution of existing points.

      3. Latin Hypercube Designs -- Each continuous factor is divided into n -evenly spaced intervals, creating a grid of hypercubes (in the -two-dimensional case this is a square grid with n2 squares.) The -design points are chosen so that each of the n subintervals are -chosen exactly once in each dimension. The worst case scenario, if -this process is done completely at random, is that all of the design -points fall along the diagonal of the hypercube (figure 16a). To -avoid this, the algorithm is usually modified to create designs more -like figure 16b.

        Figure 16a. Worst Case Space Filling Design Figure 16b. Desirable Space Filling Design - - - - image30 - - - - - image31 - -

      You can create Space Filling Designs in JMP 13 by going to the DOE -menu and selecting the Special Purpose option, then Space Filling -Design (figure 17a). JMP 13 provides 7 design construction methods -(figure 17b).

      Figure 17a. Opening the Space Filling Design Platform Figure 17b. Space Filling Design Methods in JMP 13 - - - - image32 - - - - - image33 - -

      For specific questions that are not addressed here or in the JMP help -files, feel free to contact the Intelligence, Analysis and Assessments -Directorate (A-2/9).

      Test Designs for Comparing Systems

      Comparison tests are conducted to test the hypothesis that a system -meets a specified threshold, to compare system performance under two or -more different conditions, or to compare the performance of two or more -systems. When designing a comparison test, there are two important -issues to address:

      1. When data is grouped by the systems being compared, or the different -operational conditions for which performance is compared, it is a -best practice to have an equal number of test points in each group. -This will facilitate a more effective comparison of the group means.

      2. The number of test points in each group gives appropriate power to -detect the delta (difference between the group means) of interest.

      For more information please contact the Test Design and Analyses -Division of A-2/9.

      Test Designs for Problem Identification

      Test designs for problem identification are constructed using different -design principles than those used for system characterization. The -designs, called combinatorial designs or covering arrays, are used when -the SUT is assumed to have a deterministic response variable; i.e., -replicating the design points is not necessary. They are typically not -suitable for characterization of system performance in the battlespace, -but they generally require fewer runs than designs used for performance -characterization. These designs are a useful tool for designing test -runs for "demo'd" factor levels; i.e., for test runs representing rare -operational conditions. Consequently, an AFOTEC test may involve designs -for both characterization and problem identification.

      Combinatorial Designs (Covering Arrays)

      Combinatorial Designs or Covering Arrays (CA), terms sometimes used -interchangeably, employ the science of systematically selecting -combinations of factors and levels to provide the best chance of -identifying problems. They are constructed to efficiently evaluate a -system at all possible level combinations for subsets of t factors, -where t is usually small relative to the total number of factors. Note -that a combination of levels for t factors is called a t -tuple -30. Combinatorial designs are often -used in testing software intensive systems with a deterministic binomial -response variable (a pass/fail response which will not change no matter -how many times the design point is replicated.) However, these designs -can also be applied to testing other types of systems where problem -identification is the primary goal.

      Combinatorial designs have advantages and disadvantages. The drawback of -combinatorial designs is that they do not allow for the effect of a -factor to be estimated nor do they allow for statistical modeling; they -are rarely balanced or orthogonal. The advantage of these designs is -that they can be used with a large number of factors---even if they have -many levels---as the size of the design can be controlled.

      Design size is determined by adjusting construction parameters called -strength 31 and coverage -32. Combinatorial designs have -strength t if every possible t -tuple of factor levels appears at -least once in the design. The notion of combinatorial design coverage is -used to quantify what percentage of the possible factor level t --tuples occur in the design. Intuitively, 100% coverage at strength t -means that all possible t ‑tuples appear in the design at least once. -A test team may choose a design with less than 100% coverage at strength -t , rather than 100% coverage at strength t-1 . The benefit is that -even though the design only partially covers the possible t -tuple -combinations, the probability of finding a fault caused by a t-way -interaction of factors is higher than when using the smaller design of -strength t‑1 (with 100% coverage); therefore the overall effectiveness -of the design at finding faults is higher.

      A combinatorial design can be constructed for any combination of -categorical factors and levels (continuous factors must be converted to -categorical). Disallowed combinations of levels can be removed from the -designs, but this may increase the size of the design for a given -strength and coverage. Industry has embraced combinatorial designs for -software testing as an efficient method of finding software problems -when the possible input (factor) space is large (Kacker, Kuhn, & -Lawrence, 2013). During an operational test for a software intensive -system, a combinatorial design may be an option to evaluate -deterministic measures. However, data for any stochastic -33 measures (those having random -variation) should be collected using other types of designs.

      The National Institute of Standards and Technology has a free tool for -creating Covering Arrays and Combinatorial Designs: Automated -Combinatorial Testing System (ACTS). The tool takes the factor and level -inputs from a test design, and provides the minimal factor covering -array at the desired strength and coverage. The tool is located at:

      http://csrc.nist.gov/groups/SNS/acts/documents/comparison-report.html -.

      JMP does not have a platform for constructing combinatorial designs.

      Creating a Combinatorial Design in ACTS:

      Note: when entering factor or level names, do not use commas, spaces, or -special characters.

      1. Select System , then select New (figure 18a)

      2. Enter the name of the system in the System Name box

      3. Enter a factor (ACTS refers to factors as parameters)

        a. Type the factor name in the Parameter Name box

        b. Enter the nature of the levels and the level names

        i. If the factor is a Boolean type (true/false, yes/no,
        > pass/fail)
        -
        1. Select **Boolean** in the **Parameter Type** drop down
        > menu
        -
        2. The factor levels are automatically named **true** and
        > **false**
        -
        ii. If the factor is categorical
        -
        1. Select **Enum** in the **Parameter Type** drop down menu
        -
        2. Type the level name in the **Simple Value** box
        -
        3. Click **Add**
        -
        4. Repeat steps 2-3 for all factor levels
        -
        iii. If the factor is continuous
        -
        1. Select **Number** in the **Parameter Type** drop down
        > menu
        -
        2. Type the level value as an integer in the **Simple
        > Value** box
        -
        3. Click **Add**
        -
        4. Repeat steps 2-3 for all factor levels
        -
        iv. If the factor is categorical or continuous and the levels
        > are labeled by consecutive integers
        -
        1. Select **Range** in the **Parameter Type** drop down
        > menu
        -
        2. Type the first integer value in the left **Range Value**
        > box
        -
        3. Type the last integer value in the right **Range Value**
        > box
        -
        4. Click **Add**

        c. Click Add to Table

      4. Repeat Step 3 for all factors

        Figure 18a. Creating a Combinatorial Design Figure 18b. Enter the Factors and Levels - - - - image34 - - - - - image35 - -

      5. Click Add System when all factors are entered (figure 18b)

      6. Create the combinatorial design by opening the Operations menu -and clicking Build (figure 19a)

        a. Specify the algorithm in the Algorithm box (the recommended

        > one is **IPOG** )

        b. In the Strength box, indicate the strength of the

        > combinatorial array (1-6)

        c. In the Mode box

        i. Select **Scratch** to create a new combinatorial array
        -
        ii. Select **Extend** to extend an existing array

        d. In the Constraint Handling box, select how the algorithm

        > incorporates disallowed combinations of levels; the default
        > method is recommended

        e. Check the Show Progress box if you want to see the

        > algorithm's progress

        f. Check the Ignore Constraints box if you have entered

        > constraints but want to compare the design with constraints to
        > a design without constraints

        g. Uncheck the Randomize DontCare Values box unless you have

        > constraints

        h. Click Build (figure 19b)

        Figure 19a. Build the Combinatorial Design Figure 19b. Select the Design Options - - - - image36 - - - - - image37 - -

      7. Check the design statistics (figure 20)

        a. Click on the Statistics tab

        b. Click Graph to see a graph of the coverage ratio vs. the -number of test runs.

      Figure 20. Checking the Combinatorial Design Statistics

      - - - image38 - -

      Example of a Combinatorial Design

      Suppose AFOTEC is testing an enterprise software system. There is a -pass/fail deterministic response variable that indicates whether the -operator was able to successfully use the system under a specified -condition defined by a combination of factor levels. There are six -three-level categorical factors, so a full factorial requires [ 3 ^6^ -= 729 ]{.math .inline} runs. The test team cannot afford that many runs, -so they use ACTS to investigate how a combinatorial design can reduce -the size of the test. Table 3 shows the number of runs required for a -design of strength t , for t = 1 to 6 .

      Table 3. Number of Runs Required for Strength t

      StrengthNumber of Runs
      13
      215
      348
      4140
      5318
      6729

      Suppose the test team has resources for a test with 100 runs. Then if -the test team wants 100% coverage of the t -tuples, they should use -the combinatorial design of strength 3 with 48 runs. However, since they -have the budget to conduct a test twice that size, the test team -considers using a subset of the strength 4 design and accepting partial -coverage of the 1215 possible 4‑tuples. Checking the graph of the -coverage ratio vs. the number of test runs (figure 20), the test team -learns that using 100 runs from the strength four design will give -approximately 90% coverage of the 4-tuples; this is a very good design -option. For more information on combinatorial designs contact the Test -Design and Analyses Division of A-2/9.

      Demonstrations

      Demonstrations are the simplest of the problem identification test -designs. They are usually single events demonstrating that a system can -successfully operate under a particular condition of interest (a single -factor level or specific combination of levels). Demonstrations should -only be used to supplement more statistically rigorous test designs, not -used as the primary test design. The test team should methodically -select the factor levels for the demonstration test points using prior -knowledge from SMEs.

      It is unlikely that any meaningful inferential conclusions can be drawn -from demonstrations alone, as the principles of DOE are rarely applied -to these runs. There is usually little to no replication of the factor -level being evaluated, so it is difficult to characterize the average -performance of the response at the demo'd factor level. Also, for the -factors that are not of interest in a demo run, there is a tendency for -their levels to be randomly selected during execution. Also, if there -are several factors with levels marked for demonstration, these levels -may be combined into a single demo run. These practices add significant -ambiguity concerning the attribution of system performance to the demo'd -factor's level. If there are several demo runs in a test, it is a best -practice to fix the levels of the factors that are not of interest. This -allows the impact of the demo levels to be more easily determined in the -analysis.

      Cases

      Cases are like demonstrations but have several specific combinations of -factors and levels that are intended to be examined together. Types of -case designs include examining the worst or best case configuration of -the factors and levels. The belief is that if a problem exists, it will -exhibit itself when the system is operated under the worst possible or -best possible scenario. Sometimes a case design is executed for a -special-interest item or even political reasons. As with single -demonstrations, it is unlikely the data recorded from these events can -be statistically analyzed.

      Observational Studies

      A pure observational study is a rigorous investigation of treatments and -the effects they cause, but differs from a designed experiment (or test) -in that the investigator cannot control the assignment of factor levels -(treatments) to the items under test. Consequently, the analysis of the -treatment effects must consider any possible bias due to confounded -factors. When using statistics to draw inferences about a population, it -is commonly said, "Correlation does not equal causation." This is -especially important to remember when using an observational study to -draw conclusions about the performance of a system. Since the test team -does not change factor level settings and then directly observe a -response, it is more difficult to attribute the change in a measure -(response variable) to the change of a particular factor's level. This -difficulty is caused by the increased likelihood that nuisance factors -are strongly correlated with test factors in an observational study, -which prevents clear attribution of cause and effect between factors and -the measures.

      During some AFOTEC tests, it is impossible to control the test -conditions. However, there are combinations of factors and levels that -the test team wants to see at some point during the test event. It is a -best practice to create a test event matrix (TEM) for observational -studies which includes all of the factor/level combinations that the -test team desires to see. Then the goal of test planning is to maximize -the probability that each level combination is observed a sufficient -number of times.

      For example, figure 21 shows a portion of the TEM for the notional New -Air Force Electronic Pay System (NAFEPS). NAFEPS will replace the Air -Force's legacy human resource (HR) software system. Factors in the test -include the HR business process, the user role executing the process -(e.g., HR specialist), the affected member's total force component -(e.g., Air Force Reserve), the affected member's classification (e.g., -officer), and the organization level at which the business process is -executed (e.g., base level).

      Figure 21. TEM for the New Air Force Electronic Pay System (NAFEPS)

      - - - image39 - -

      During OT, the system will be live and capable of altering real-world -databases. Without the "sandbox" environment of DT, the test team is -unable to direct users to process fictitious paperwork, such as -recording disciplinary actions or retirements. Consequently, the test -team can only observe users executing various HR business processes -during the course of their normal duty.

      The TEM aids the test team in determining where and when to observe the -SUT in order to maximize the probability of observing the factor level -combinations of interest. For example, the test team could choose to -send a team to the Air Reserve Personnel Center (ARPC) at Buckley Air -Force Base, CO to observe ARPC HR specialists processing retirement -paperwork. For business practices that peak in frequency at various -times of the year, the test teams will time the site visits accordingly.

      Another important question the test team must answer is how long to -observe the SUT in order to see all of the factor level combinations of -interest. Some factor level combinations may be relatively rare, such as -design point 1. "Record Disciplinary Actions" against Regular Air Force -cadets. Fortunately there are some simple formulas that can be used for -planning the duration of observational studies.

      If the factor level combinations of interest occur at a predictable rate -during some period of time, but completely at random during the time -period, then the test event can be modeled as a Poisson Process. Poisson -processes are used to model situations like the arrivals of customers to -a store, or the number of car accidents in a certain area. The important -assumptions are:

      1. The events occur at a certain rate but completely at random within -an interval (e.g., on average, 5 customers arrive at a store per -hour; but when they arrive within the hour is completely random)

      2. The number of events in some interval of length t is independent of -and identically distributed as the number of events in another -(disjoint) interval of length t (e.g., the average number of -customers arriving to the store between 0900 and 1000 is the same -average number arriving between 1100 and 1200)

      In the context of observational studies, the arrivals of interest are -the rare factor level combinations. It suffices to focus on the -probabilities of the rare factor level combinations, as the -probabilities of observing the more common events will be greater and -therefore are not limiting factors.

      Example 1: Calculating the Time to Observe One Rare Event with -Specified Probability. Suppose we want to know the test time t that -gives a probability of 80% (p = 0.8) that the test team will observe a -rare factor level combination.

      The first step is to estimate the rate [ λ ]{.math .inline} of the -average number of events per time period. Suppose a rare factor level -combination occurs randomly 1 time every 3 working days (on average) -while a system is operating. Assuming an 8 hour work day, this is 1 -event every 24 working hours, implying [ λ ]{.math .inline} = 0.042 -events per hour.

      \frac{\mathbf{1}\ \mathbf{\text{event}}}{\mathbf{24}\ \mathbf{\text{hours}}}\overset{\Rightarrow}{\ }\mathbf{\lambda} = \mathbf{0}.\mathbf{042}\ \mathbf{\text{events}}/\mathbf{\text{hour}}

      Step 2 is to convert 80% into the decimal p = 0.8 and use the following -formula to calculate the test time t.

      \mathbf{t} = \frac{- \mathbf{\ln}\left( \mathbf{1} - \mathbf{p} \right)}{\mathbf{\lambda}}

      \mathbf{t} = \frac{- \mathbf{\ln}\left( \mathbf{1} - \mathbf{0}.\mathbf{8} \right)}{\mathbf{0}.\mathbf{042}} = \mathbf{38}.\mathbf{3}\ \mathbf{\text{hours}}

      The analysis shows that 38.3 test hours are required to have an 80% -chance of observing a factor level combination that occurs randomly 1 -time every 24 hours (on average.)

      Example 2: Calculating the Time to Observe k Rare Events with -Specified Probability. Suppose we want to know the test time t that -gives us an 80% probability (p = 0.8) chance of observing k = 3 -occurrences of a rare factor level combination that occurs randomly 1 -time every 3 working days (on average). We already calculated that [ -λ ]{.math .inline} = 0.042 events per hour. In this example a more -complicated formula is required:

      \mathbf{1} - \mathbf{p} = \sum\_{\mathbf{n} = \mathbf{0}}^{\mathbf{k} - \mathbf{1}}{\frac{\mathbf{1}}{\mathbf{n}!}\mathbf{e}^{- \mathbf{\lambda}\mathbf{t}}\left( \mathbf{\lambda}\mathbf{t} \right)^{\mathbf{n}}}

      Plugging in the values we know (p = 0.8, k = 3, [ λ ]{.math .inline} -= 0.042) we have

      \mathbf{0}.\mathbf{20} = \mathbf{e}^{- \mathbf{0}.\mathbf{042}\mathbf{t}} + \mathbf{e}^{- \mathbf{0}.\mathbf{042}\mathbf{t}}\left( \mathbf{0}.\mathbf{042}\mathbf{t} \right) + \frac{\mathbf{1}}{\mathbf{2}}\mathbf{e}^{- \mathbf{0}.\mathbf{042}\mathbf{t}}\left( \mathbf{0}.\mathbf{042}\mathbf{t} \right)^{\mathbf{2}}

      A simple way to solve this equation for t is to use Excel's solver -function to find the value for t that minimizes the difference between -the equation's right hand side and the left hand side (0.2 in this -example.) The solver reports that t = 71.3 hours. This means we must -observe the system 71.3 hours in order to have an 80% chance of seeing 3 -occurrences of a rare factor level combination that occurs 1 time every -3 working days (on average.)

      Example 3: Calculating the Probability of Observing a Rare Event with -Specified Time. Suppose the resource constraints have imposed a limit -of 4 working days (32 hours) for the observational study. Given a fixed -test time t = 32 hours, we want to determine the probability of -observing a rare factor level combination that occurs randomly 1 time -every 3 working days. In other words, if [ T ~1~ ]{.math .inline} is -the time of the first occurrence of the rare event, then we want the -probability that [ T ~1~ ]{.math .inline} is less than t : P [ ( T -~1~ \< t ) ]{.math .inline} . Recall that [ λ ]{.math .inline} -= 0.042 events per hour. The formula to use is:

      **P** ( **T** **1** **<** **t** ) **=** **1** **** **e** **** (λt)
      -
      **P** ( **T** **1** **<** **32** ) **=** **1** **** **e** **** **(** **0.042** **)** **(** **32** **)** **=** **0.74**

      Therefore we have a 74% chance of seeing the rare event during the 32 -hour test.

      In summary, the three formulas in Examples 1-3 provide probability -assessments that can be used to plan the duration of observational -studies, as well as characterize the risk of not observing important -factor level combinations.

      An observational study should only be used when it is impossible to -control the factor levels. They must have sufficient documentation to -prove the test team will gather the appropriate data to answer all of -the desired questions. While an observational study is not the ideal -test scenario, with proper planning these tests can provide data to -characterize the performance of the system. For more information on the -use of an observational study for an AFOTEC test program, and the theory -behind the use of Poisson Process modeling, please contact the Test -Design and Analyses Division of A-2/9.

      TEST DESIGN MEASURES OF MERIT

      All test designs have associated measures of merit, or quality -indicators, which should be considered when deciding on a test design. -Test design measures of merit include power, optimality efficiency, -correlation, prediction variance, resolution, strength, and coverage. -The most commonly encountered and generally applicable test design -measures of merit are presented in this section. Note that some measures -of merit which pertain to specific design types (like strength and -coverage for combinatorial designs) are discussed in the sections of -this guide corresponding to the relevant designs.

      Power

      In a hypothesis test, power is a measure of the probability the null -hypothesis will be correctly rejected when it is false. In the context -of statistical modeling, the null hypothesis is that a factor is not -active (has no effect on the response); therefore in that context power -refers to the probability the test data will correctly identify a factor -as active. Power is a function of the test design, significance level, -signal (e.g., difference in the response between factor levels), and -noise (natural variation in the measure for a given test run.)

      AFOTEC calculates power over a range of signal to noise ratios (SNR) at -a significance level of [ α = 0.2 ]{.math .inline} . SNR refers to the -ratio of the minimum desired detectable difference, delta (δ), and the -standard deviation of the response values at a given design point, sigma -(σ). AFOTEC typically evaluates power for 0 \< δ/σ \<  3.5; the range of -interest for AFOTEC and DOT&E is usually between 1 \< δ/σ \< 2. Rather -than using a SNR, power can also be calculated by using SMEs, -requirements documents, and previous system data (from a legacy system -or DT) to identify appropriate values for δ and σ.

      A rule of thumb is to employ designs with a minimum power of 80% for -effects of interest. Power analysis for a designed experiment requires -the following information:

      1. The test design matrix metadata (which includes the number of -factors, levels for each factor, and sample size)

      2. The proposed statistical model

      3. The significant level (α)

      4. The desired detectable change in the response (δ)

      5. The standard deviation of the response value at a given design point -(σ); the assumption for power analysis is that σ is the same at all -design points.

      List items 4 and 5 can be combined into a SNR value.

      Power calculations for binary response variables are different than -those for continuous response variables. More information on calculating -power for binomial response variables can be found here:

      http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdf -. (Ortiz, 2014)

      For guidance on creating power curves or power calculations in AFOTEC -refer to the November 2014 guide, Power Analysis Tutorial for -Experimental Design Software, which can be found on the AFOTEC -SharePoint in the Analyst and Engineer Community. Contact the Test -Design and Analyses Division of A-2/9 for assistance creating or -interpreting power curves.

      Optimality (Efficiency)

      An important measure of merit for optimal designs is the optimality -efficiency. The optimality relates to the criteria used to determine the -"best" design during execution of the design construction algorithm. JMP -calculates efficiencies for the D 34, G 35 and A 36 optimality criteria, which were discussed in the Optimal Designs section of this guide. The efficiencies are -the ratio of the optimality criterion value of the evaluated design to -the optimal value of an ideal (perhaps unobtainable) design of the same -dimensions. When JMP constructs a computer generated design, it reports -the D, G, and A efficiencies under the Design Diagnostics header under -" Design Evaluation " (figure 22).

      Figure 22. Optimality Efficiencies under Design Diagnostics

      - - - image40 - -

      The efficiency values will range from 0-100% with 100% being the best. -For more information, please consult the JMP documentation or contact -the Test Design and Analyses Division of A-2/9.

      Correlation (Multicollinearity)

      Correlation between two factors is a statistical measure that indicates -the extent to which the levels of those factors vary together. A -positive correlation indicates that factors increase or decrease in -parallel; a negative correlation indicates that one factor increases as -the other decreases.

      It is undesirable to have correlated factors in a test design. First, -when two active factors are perfectly correlated, it is not possible to -quantify the independent effect of each factor on the response. Second, -correlated factors increase the variance of the estimates of the -statistical model parameters and the estimates of the mean response -value.

      Bias due to multicollinearity can be unintentionally introduced when -influential and controllable factors that are not of interest -operationally are allowed to vary randomly during the test event. This -situation may occur when the test team decides to exclude medium impact -factors from the list of varied factors in order to prevent the design -from becoming too large, or to prevent the test from having low power. -It is poor practice to label these excluded factors as "logged" factors, -as the chances of biased data becomes far more likely. Instead, include -these factors in an "off-line" test design (that will be used for test -execution) if you think post-test analysis might possibly involve them. -These factors can be omitted from the reported design for the purposes -of calculating measures of merit like power.

      A correlation matrix shows the linear relationship between any pair of -factors. If any of the values in the correlation matrix is above 0.5, -the design should be adjusted if possible to reduce the correlation. JMP -will produce a "Color Map on Correlations" in the "Design Diagnostics" -tab. Figure 23 shows two "Color Map on Correlations" plots from JMP.

      Figure 23. Examples of Color Maps

      - - - image41 - - - - - image42 - -

      The horizontal labels across the top are the main effects and the -2-factor interactions. The labels on the vertical axis are not shown but -are the same as the horizontal axis. The scale on the right indicates -the amount of pair-wise correlation. Royal blue indicates no correlation -and red indicates perfect correlation. The plot on the left is the -optimal, and depicts no correlation between any of the factors or their -2-factor interactions (the red diagonal is the correlation of each -factor with itself and therefore shows red for perfect correlation.)

      The color map on the right shows a plot with some partial correlation -between the main effects and one or more 2-factor interactions, as -indicated by the grey color. The upper left 4x4 portion of the map (in -the black square) shows us that no main effect is correlated with any -other main effect. If a completely blue map (apart from the diagonal) -cannot be achieved, attempt to make the correlation between main effects -as small as possible.

      Prediction Variance

      Prediction variance is a test design measure of merit which provides -information regarding the variability in the estimate of the response -variable at a particular point in the design space. It essentially -quantifies how precise the model is in estimating the true average -response. If the prediction variance is large, the true average response -value may be quite different from the model's estimate.

      Prediction variance is a function of both natural system variation ( [ -σ ^2^ ) ]{.math .inline} and the structure of the experimental design. -Relative prediction variance considers only the experimental design's -influence on the prediction variance (independent of natural system -variation). Although we do not usually create predictive statistical -models at AFOTEC, this metric can still be useful because the predictive -variance is indicative of the design quality.

      JMP provides graphical tools that are useful for assessing the -prediction variance of a test design. They are the " Prediction -Variance Profiler " (2D and 3D) and the " Fraction of the Design -Space " (FDS) plot.

      Figure 24. Example of JMP\'s 2D Prediction Variance Profiler

      - - - image43 - -

      The prediction variance profiler (figure 24) in JMP plots the relative -variance of prediction as a function of each factor level. These plots -can be used to identify combination of factor levels with high -prediction variance. It is ideal for the prediction variance to be small -throughout the design region. Generally, the prediction variance drops -as the sample size increases.

      A fraction of the design space (FDS) plot (figure 25) may be created in -JMP to show what proportion of the design space has prediction variance -at or below a given level.

      Figure 25. Fraction of Design Space Plot

      - - - image44 - -

      The figure shows that 50% of the design region has a relative prediction -variance below 0.039. The "flatness" of the plot is an indication of the -prediction variance stability; i.e., the prediction variance does not -significantly increase in some portion of the design region. Comparing -the FDS plot for two designs side-by-side is one way to compare two -designs; the preferred design is the one with lower prediction variance -on average throughout the design space.

      Comparing Measures of Merit

      JMP has created the Compare Designs platform to provide a convenient -way to compare two or three designs.

      Comparing Designs in JMP

      1. From the menu above one of the design tables, launch the platform by -selecting DOE , then Design Diagnostics , then Compare -Designs (figure 26a).

      2. In the Compare Reference Design With box, select the -other designs to be compared (figure 26b).

        Figure 26a. Comparing Designs in JMP Figure 26b. Choosing Designs to Compare - - - - image45 - - - - - image46 - -

      3. In the Matching Specification Box, you can specify which columns -are equivalent (matched) in the two designs. Click the gray triangle -to reveal the Match button. Highlight a factor in each design and -click Match .

      4. Click OK in the Action box (figure 27a).

      5. Measures of Merit for all of the designs such as power (figure 27b), -prediction variance, FDS plots, and optimality efficiencies are -provided in the output.

        Figure 27a. Matching Columns of Multiple Designs Figure 27b. Comparing Power of Two Designs - - - - image47 - - - - - image48 - -

      For more information on the design comparison platform, see JMP's help -documentation or contact the Test Design and Analyses Division of A-2/9.

      THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS

      For many AFOTEC tests the response data has variability; i.e., if two -test runs are conducted while holding the factor levels constant, we -will likely measure two different response values. There are three basic -principles of DOE that help us compensate for, quantify, and control -variability in our response data: randomization, replication, and -blocking.

      Randomization

      Randomization is a principle of DOE used to average out the effects of -unknown and uncontrollable nuisance factors. Randomization refers to -both the random allocation of test material to a test run, and to the -order in which the test runs are executed. If possible, the order of -test runs should be randomized to avoid biasing the factor effect -estimates with the effects of the unknown nuisance variables.

      For example, suppose we have one two-level factor of interest. Our test -is conducted over a morning and afternoon with 4 test runs in the -morning and 4 test runs in the afternoon. Suppose the temperature in the -morning is 15 degrees cooler than in the afternoon, and the response -value increases as the temperature increases. The test is not randomized -and factor level 1 is run in the morning and factor level 2 is run in -the afternoon. The test data show that the response is higher for factor -level 2 than for factor level 1. Unfortunately the test team cannot be -certain whether the increase in the response was due to changing from -factor level 1 to factor level 2, or due to the increase in the ambient -temperature from the morning to the afternoon.

      If the test was randomized, the runs in the morning would involve both -factor level 1 and level 2 (and likewise for the afternoon.) Ideally the -effect of the ambient temperature will average out over each level of -the factor, and we remove its influence on the estimate of the factor -effect.

      Replication

      Replication is an independent, repeated run of a factor level -combination (as opposed to measuring the result of a single test run -twice---this is a repeated measure.) Replicating factor level -combinations is the best method for obtaining an estimate of run-to-run -variability, which is often called experimental noise. An important -benefit of factorial experimentation is that there is hidden replication -in the test design. This means that even if a factorial design for k -factors is unreplicated, if one factor is determined to be -insignificant, the resulting design is a replicated design for k-1 -factors.

      Since statistical analysis of test data using ANOVA -37 or linear regression involves -evaluating a ratio of an estimated factor effect to the experimental -noise, replication is important to enabling accurate analysis. While -there are methods to estimate experimental noise without replication, -these methods produce estimates that are generally inferior to those -produced by repeating factor level combinations.

      Blocking

      Blocking is one of the fundamental principles of Design of Experiments -(DOE) that allows us to account for the variability in our response data -caused by controllable nuisance factors---factors that are not of -interest but can be controlled. In the absence of blocking, variability -caused by nuisance variables is attributed to experimental noise and may -also bias factor effect estimates; this inflates the experimental noise -estimate and makes it more difficult to determine if factors of interest -have an effect on the response variable.

      During operational test, there is almost always a nuisance factor that -is a source of variability that could and should be controlled. Some -typical operational test nuisance factors are the day of the test, -shifts of operators, pilots, tail numbers, terminal/position numbers, -and ranges. These factors can impact the response variable -significantly, sometimes even more than the factors of interest.

      Blocking is simply incorporating a nuisance factor into the test design -as a blocking factor. Just as with the factors of interest, the goal is -to make the blocking factor orthogonal to the other factors. If the -levels of a blocking factor are time based, such as the day of the test -or a shift of operators, then the blocking factor creates a restriction -on randomization. This is because the blocking factor level is held -constant for some period of time.

      One way to add a blocking factor in JMP is through the Custom Design -Menu. Suppose we have a test with three 2-level categorical factors and -one 3-level categorical factor. If an 18 run test was planned over three -days, it may improve the analysis to block on the day of the test. Doing -so would account for the variability from nuisance factors that vary -day-to-day, such as precipitation, humidity, sunlight, and temperature. -Figure 28 shows the JMP Custom Design Menu. To add blocking factor for -Test Day, under the Factors box, select Add Factors , then -Blocking , then Other. By selecting 6 runs per block, we can -divide the 18 test runs among the three days such that all of the levels -of the factors of interest occur equally often on each day. Thus any -differences between each test day will average out across the levels of -the factors of interest. Now the estimates of the factors of interest -will be independent of any effect on the response caused by the test day -conditions. Also, the error estimate will be reduced, as the variability -associated with each test day would have been included in the error -estimate if the test was unblocked.

      Figure 28. Adding Blocking Factors in JMP

      - - - image49 - -

      Blocking can also be employed as a strategy to hedge against the -negative impact on analysis resulting from lost test data. The levels of -the factors of interest should be balanced across the levels of the -blocking factors; the consequence of this is that all blocks typically -contain data for every factor level. In the above example with a three -day test, if one test day was lost due to weather or an equipment -malfunction, the test runs from the other test days will still be -balanced. Also, the factors of interest will likely be less correlated -than they would be in a scenario where a random set of 6 test runs were -lost.

      JMP's help files have useful information on building blocking factors -into a test design. The rule of thumb is: "Block what you know, -randomize the rest!"

      TYPICAL SITUATIONS

      The next section covers some typical situations that may be encountered -in AFOTEC and some suggested remedies.

      How do I Select a Design?

      Table of commonly encountered design scenarios and possible design matches.Full Factorial2kFractional FactorialOrthogonal ArraysCovering Array/Combinatorial DesignComputer Generated Design (Optimal)Split/Strip Plot DesignsSpace Filling DesignsDemonstrationCases
      Factor Considerations
      All continuous factorsXXXXXX31XX
      All 2-level factors (mixed continuous and/or categorical)XXXXXXXX
      Mixed level factors (mixed continuous and/or categorical)XX [38](#fn38)XXXXXX
      Disallowed combinationsXXXX
      Modeling Considerations
      Quadratic termsXX [39](#fn39)
      Two-factor interaction termsXXX [40](#fn40)XXX
      Three-factor or higher interaction termsXX [41](#fn41)XXXX
      Response Variable Considerations
      Random VariationXXXXX
      DeterministicXX31XX

      If all of the factors in your test have only 2-levels or are all -continuous, you can choose almost any design type. It is most desirable -to select a design with a run size that is a power of 2 (8, 16, 32, -etc.) If resource constraints prevent this, choose a D-Optimal design.

      When a test involves categorical factors with more than 2 levels, it is -most common to create a full factorial or D-Optimal design. Create -several design options and compare them using the test design measures -of merit presented in this guide.

      When a test involves a deterministic response, use a combinatorial -design to find factor level combinations that cause problems in the -system. If you plan to characterize the system, choose a space filling -design.

      I Have Factors that Are Hard to Change

      It is the rare operational test scenario where the runs in the test -event matrix can be executed in an entirely randomized order. It is -common that a group of runs involving a particular factor level must be -executed consecutively because of constraints imposed by the range, test -asset availability, or feasible tactics. It is these cases when the -design should be set up, run and analyzed using a split plot -configuration.

      Split Plot designs can be created from an existing design type -(typically a computer generated design) by identifying the -hard‑to‑change factors and easy‑to‑change factors. The hard‑to‑change -factors are those that cannot be arbitrarily changed from run to run. -These factors are arranged into groups of runs called Whole Plots. Whole -Plots contain equally sized (usually) sets of runs and the levels of the -easy‑to‑change factors are randomized. Figure 29 shows a Split Plot -configuration with one hard‑to‑change and two easy‑to‑change factors.

      Figure 29. Split Plot with One Hard to Change Factor

      - - - image50 - -

      If there are two hard‑to‑change factors (one will be specified as -very‑hard‑to‑change and the other hard‑to‑change) the -very‑hard‑to‑change factor will determine the whole plots and the -hard‑to‑change factor will be used to create sub plots within the whole -plots. The easy‑to‑change factors will be randomized within the subplots -as shown in figure 30.

      Figure 30. Split Plot with a Very Hard and Hard to Change Factor

      - - - image51 - -

      The consequence of designing the test in this manner is that we can no -longer use a common estimate of error to evaluate both the -hard‑to‑change and easy‑to‑change factors. There is more variability in -the average response between the levels of the hard‑to‑change factors -than between the easy‑to‑change factor levels. Hence the power for the -hard‑to‑change factors will be lower than for the easy‑to‑change -factors. To improve the power of the hard‑to‑change factors, the test -should include multiple whole plots for each hard‑to‑change factor -level. The resulting test will be larger than if a completely randomized -design was used.

      To construct a split plot design in JMP's custom designer, open the -Custom Designer tab, and enter the desired factors as usual. Under -the Changes column for the factors, change Easy to Hard . -Very Hard is used if there are two hard-to-change factors and there -will be subplots within the whole plots; the subplot factor will be -labeled Hard . Specify the desired model.

      Specify the number of runs in each whole plot. Under Design -Generation , enter the Number of Whole Plots , which will -determine the number of times the levels of the Hard factor (if -there is only one hard-to-change factor) or Very Hard factor is -replicated. In figure 31 the very hard-to-change factor will have each -factor level replicated 2 times; 4 whole plots divided by 2 levels -equals 2 whole plots for each level.

      Specify the Number of Subplots (if necessary because there are 2 -hard-to-change factors). Each whole plot will have 2 subplots; 8 -subplots divided by 4 whole plots equals 2 subplots per whole plot. -Ensure that analysis is done in the table created by JMP, as several -important factor properties have been changed to enable a proper -analysis.

      Figure 31. Creating a Split Plot Design in JMP

      - - - image52 - -

      For more specific information on the construction and analysis of Split -Plot designs, check the JMP help files or contact the Test Design and -Analyses Division of A-2/9.

      Can I Combine Developmental Test and Operational Test Data?

      Developmental and Operational Test data can be combined if the -developmental test is determined to be operationally representative. -During test planning, if the analyst thinks that combining developmental -test (DT) data with operational test (OT) data may be a possibility, -there are some important considerations to discuss with the DT team.

      To combine any data to be used for characterization, the DT events -should have factors that correspond to the factors for the OT event. The -DT test articles must also be the "same" as the OT test articles. Any -variability caused by small changes to the SUT may be addressed with an -additional blocking variable. Another very important requirement is that -the DT events must be "operational" in nature. Lab tests, chamber tests -or table top tests are not usually operational and so cannot be -considered for combined DT/OT data.

      During test planning and test design, discussion of the possibility of -combining the DT/OT data is essential to ensure that the future -combination will be feasible. Ultimately, it may not be possible to -combine the data because of the evolution of the SUT, but proper -planning will maintain the possibility. The same considerations can be -applied when planning the combination of data from Initial and Follow-on -Test & Evaluations.

      There are several advantages to combining DT and OT data. First, -combining data makes the "Test-Analyze-Test" strategy viable. DT test -data can be used to determine the significant main effects so that later -in OT the test event matrix can be more focused on the relevant factors -and their interactions. Second, OT test events are usually planned and -executed for the "minimum" data needed, so DT data is an attractive way -to increase the sample size of the data for OT analysis. To obtain more -information on combining DT and OT data, contact the Test Design and -Analyses Division of A-2/9.

      I Have Disallowed Combinations

      One of the reasons optimal designs have skyrocketed in popularity at -AFOTEC is the ability to deal with disallowed combinations. A disallowed -combination occurs when one level of a factor cannot occur -simultaneously with a level of another factor. The JMP Custom Design -platform allows you to specify disallowed combinations using a script or -filter.

      Keep in mind that if the operation/MORV in question has a large number -of disallowed combinations, you may need to make some modifications to -the test design. One solution could be to add another operation to the -COI in order to separate the factor list into two groups for separate -test events. Perhaps the factor prioritization and management may need -to be reevaluated to determine if a factor can be removed from the test. -The factors in question may not be independent enough to be separate -factors, and combining the factors into a super factor could be the best -approach. For more information on these or other techniques to avoid or -overcome disallowed combinations contact the Test Design and Analyses -Division of A-2/9.

      My Power Is Too Low

      You have created the test event matrix, created the power curves, and -determined that the power for either your main effects or two-factor -interactions is not sufficient. A straight-forward solution is to -increase the test size, but this is often not feasible due to resource -constraints. Another common solution is to eliminate factors. This -solution results in a less-thorough exploration of the battlespace and -could result in undetected system problems. Fortunately, there are some -other options to consider:

      • Keep the same test plan and explain why this added risk is -acceptable for the test program.

      • Split a factor into two factors: As an example, splitting a 4 level -factor into two 2 level factors will increase the estimation power -of a design without any additional runs. This can be an option for -many factors that are amalgamations of multiple factors.

      • Reexamine the likelihood and magnitude of impact for the two-factor -interactions; if some are not as important or less likely to exist, -include the important ones and remove the other interactions from -the power analysis.

      • Report the power on the main effects only and explain why the added -risk of not detecting two-factor interactions is acceptable for the -test program.

      • Make sure the categorical factors really are categorical; if factors -can be changed to continuous, the levels can be reduced to two (but -add some center points). Fewer levels will increase the power for -those factors.

      • Ask someone outside the program for their thoughts. Creating test -designs only within the test team can lead to "group think," and -external advice may provide another point of view and a solution.

      Whatever the option chosen, it is important to document the rationale in -the Test and Evaluation Master Plan to keep interested parties informed. -In the end, if the power is too low and there are not any realistic -options to increase the power, it is better to report the low power and -the associated risk, than to eliminate factors which may be crucial to -the warfighter's situational awareness. For guidance on creating power -curves or power calculations in AFOTEC, see the November 2014 guide, -Power Analysis Tutorial for Experimental Design Software.

      I Have Factor Levels that Depend on Other Factor Levels

      The traditional nested design occurs when the levels of one factor are -similar but not identical for the levels of another factor. These types -of designs are also called hierarchical designs (Montgomery, 2013). In -operational test they might resemble figure 32.

      Figure 32. Example of a Traditional Nested Design in Operational Test

      - - - image53 - -

      Each aircraft has four power ports which may be used during test, but -the power port "A" on the AC-130 is different than the power ports "A" -on the A-10 and the F-15. The response variable can still be analyzed -under both factors but the analysis model must be set up differently -than a traditional ANOVA model; e.g., do not include an interaction term -between the parent and nested factor. In the design construction in JMP -change the attribute of the nested factor to "nested". Include in the -test design documentation that "Power Port" is nested within "Aircraft".

      Within AFOTEC, there is a type of test design called a sub-design. As an -example, a test with a sub-design might occur when examining terrain. -Maritime terrain has sea states, while desert and mountain terrain does -not. See figure 33.

      Figure 33. Example of an AFOTEC Sub-Design

      - - - image54 - -

      There are two primary ways to deal with a scenario such as this one; one -approach would require a computer generated design while the second -would allow the choice of any other appropriate design type.

      The design could be constructed as an optimal design with specified -disallowed combinations for the Sea State and Terrain factors. The -optimal design would then only contain runs where the Mountain/Desert -levels were paired with the Sea State = 0 level. Figure 34 shows how the -" Define Factor Constraints " box in the JMP Custom Design tool -can be used to specify disallowed combinations using a script. In the -resulting design, only the Maritime factor will have a sea state other -than 0.

      Figure 34. Computer Generated Design with Disallowed Combinations

      - - - image55 - -

      Another way to address the scenario would be to create a "super" factor -of Terrain and Sea State. The factor would have a level for each of the -allowed combinations of Terrain and Sea State (7 total levels.) The -super factor has seven levels, so the test size will need to increase to -obtain the same effect power that the former five level Terrain factor -had. Figure 35 shows the super factor, "Terrain" as described in this -example.

      Figure 35. Super Factor to Address a Nested Factor Scenario

      - - - image56 - -

      For more information on nested factors, refer to the JMP help files or -contact the Test Design and Analyses Division of A-2/9.

      Best Practices/Pitfalls in Test Design

      • When possible, make factors continuous.

      • If you use a continuous factor and you suspect a nonlinear -relationship between the factor and the response, use three levels -for the factor. Most textbooks advocate using two levels and -including center points in the design, but this assumes a sequential -test-analyze-test approach.

      • Use continuous MORVs when possible. Continuous MORVs offer several -advantages to binary MORVs. First, for the same size test, power -will be higher using a continuous MORV. Second, more information is -contained in continuous data; a continuous MORV can be turned into a -binary MORV, but the reverse is not true. If a binary/discrete MORV -is used, consider developing other continuous MORVs for power -calculations.

      • Your first design option should be a full factorial. Consider other -options only if the full factorial is infeasible or inefficient -(i.e., many more runs than required to estimate a main effect and -two-factor interaction model).

      • Create two or three test designs that meet your needs and use the -measures of merit to compare them.

      • Control the nuisance variability you know about with blocking; -average out the unknown nuisance variability with randomization.

      • Ask for help, advice or sanity checks. Even the most experienced -analyst may not have thought of the best way to do something.

      Pitfalls:

      • Be cautious with disallowed combinations. If you have a lot, you may -require additional operations under a COI.

      • Don't limit your design because you believe you won't be able to -test it. Things change all the time and the capability may exist by -the time you go to test or may be developed just for your test.

      • Just because you generate a design in JMP's Custom Designer, doesn't -mean it is the optimal design! Run the design generation algorithm -several times and check multiple measures of merit.

      • Don't just turn the crank on JMP or the Test Design Suite. It is -your job to understand the output and what methods are used to -generate the results.

      • Never change a design point without re-evaluating the design's -capability to estimate the main effects and two-factor interactions.

      Appendices

      Glossary
      Active EffectA term used to describe a main effect (factor) or interaction that causes a statistically significant difference in the response variable when the factor levels are changed.
      AliasingA condition where the effect estimate of one factor includes the influence of one or more other effects (main effect or higher-order interactions).
      ANalysis Of VAriance (ANOVA)A mathematical process for evaluating the variation in data between groups and within groups in order to determine whether there is a differences between the group means. This procedure can be used to compare multiple systems, or determine if there are differences in the mean response between levels of a factor.
      AugmentationThe process of strategically adding new runs to an existing test design after some data has been collected.
      BalanceA column in a test design matrix is balanced if every factor level occurs an equal number of times. A test design is balanced if every possible factor level combination occurs an equal number of times.
      BlockingBlocking is one of the fundamental principles of Design of Experiments (DOE) that allows us to account for the variability in our response data caused by nuisance factors—factors that are not of interest but can be controlled. Blocking factors become part of a test event matrix.
      Center PointsA test run where every continuous factor is set to the value halfway between its minimum and maximum factor levels.
      ConfoundingSynonymous with aliasing: a condition where the effect estimate of one factor includes the influence of one or more other effects (main effect or higher-order interactions).
      CorrelationA statistical measure on a scale from -1 to 1 that indicates how close two variables are to having a linear relationship with each other. Two factors are perfectly correlated when the value of one factor’s level can be precisely determined by knowing the value of the other factor’s level.
      CoverageDescribes the percentage of possible factor level combinations (after removing the disallowed combinations from the complete combination space) that a combinatorial design includes at a given strength.
      DeterministicA deterministic system or model will always produce the same output from a given starting condition (level settings of the independent variables.)
      Disallowed CombinationA combination of the levels of two or more factors that cannot be feasibly executed together in a test run.
      DistributionA listing or function showing all the possible values of a data set and how often they occur.
      EffectThe average change in a response variable produced by changing the level of a factor.
      EstimationAn attempt to gain insight about an unknown population parameter based on information obtained from sample data. At AFOTEC we typically estimate means and variances of measures, factor effects, and proportions of failures.
      FactorAn independent variable which may affect the performance of a system when its levels are changed
      FactorialA test plan consisting of two or more factors, each with discrete possible values (or levels). A full factorial is a design whose experimental units (runs) take on all possible combinations of these levels. A design which includes a strategically selected subset of the possible combinations is called a fractional factorial.
      InteractionA situation where the effect of one factor on a response depends on the level of another factor.
      LevelA specific setting of a factor during a test or experiment.
      Main EffectThe effect of a factor (independent variable) on a measure (dependent variable) averaging across the levels of the other factors.
      Optimal DesignsA test design whose levels are combined in a way that optimizes some statistical design quality criterion that is a function of the design matrix.
      OrthogonalityA test design is orthogonal if each factor can be evaluated independently of all the other factors. This is possible if, for the test runs involving any level of any factor, the levels of the other factors are present in equal amounts. When an orthogonal test design has two-level factors coded -1 and +1, the inner (dot) product of any two columns is 0.
      Population ParameterA quantity or statistical measure that for a given population is fixed, such as a mean or a variance. The parameter is used in some general distribution or frequency function (e.g., a Normal Distribution) to make it descriptive of that population.
      Prior DistributionThe probability distribution that expresses beliefs about an unknown quantity before testing takes place. Within AFOTEC this distribution could be based on the performance of a similar system, the performance of a previous version of a system, or SME knowledge.
      Posterior DistributionThe conditional probability distribution that describes an unknown quantity after test or experimental data is taken into account.
      ProjectionA property of factorial designs where the degree of replication doubles when a design column is removed (such as when a factor is determined to be insignificant). With fractional factorial designs the degree of fractionation is reduced.
      QualitativeA term used to describe data that is descriptive or subjective; the values are ordinal or nominal in nature; e.g., red, blue and green.
      QuantitativeA term used to describe data that is measured on a numeric or quantitative scale; interval and ratio scales are quantitative. The data may be discrete or continuous.
      RandomizationA principle of DOE used to average out the effects of unknown and uncontrollable nuisance factors.
      RegressionA statistical process to model the change in the mean value of a continuous dependent variable (e.g., measure) as the values of one or more continuous independent variables change.
      ReplicationReplication is an independent, repeated run of a factor level combination (as opposed to measuring the result of a single test run twice—this is a repeated measure.) In JMP, requesting one replicate will create a design with two of each design point.
      ResolutionAn indication of the ability to independently estimate main effects and interactions in a fractional factorial design.
      RunOne combination of factor levels used for collecting data on one or more measures; a test design point.
      SampleA set of data collected from a population. In operational test, it is usually impossible to test the entire population of a new system, so a sample is tested.
      Screening DesignsDesigns that focus on the identification of active main effects. The goal is to reduce an initially large list of potential factors to only those that are influential on the response variable. Using screening designs decreases the size of subsequent tests conducted to estimate two-factor interactions or higher-order effects.
      Sparsity-of-Effects PrincipleThe principle that a system is usually dominated by main effects and low-order interactions. Thus it is very likely that main effects (single factor) and two-factor interactions are the only significant effects when analyzing data from a test; higher-order interactions such as three-factor interactions are very rare.
      StochasticRandomly determined; Any process or system that has a random probability distribution or pattern which may be analyzed statistically, but not predicted perfectly.
      StrengthAn integer between 2 and the total number of factors in the test design. For combinatorial designs, strength t means that for every possible subset of t factors, every possible t-tuple of level combinations is present in the design at least one time.
      t-tuple

      A combination of the levels of t factors selected from a design. Suppose there is a design with four two-level factors with levels coded as +1 and -1.

      There are four possible 2-tuples, e.g. (+1,-1).

      There are eight possible 3-tuples, e.g. (+1,-1,+1).

      There are sixteen possible 4-tuples, e.g. (+1,-1,+1,+1).

      Test Design Guidance

      The following documents have more information and guidance from the -Department of Defense and the Air Force on the use of Design of -Experiments in OT&E. They are all accessible on the AFOTEC SharePoint or -in the AFOTEC Analyst and Engineer Community.

      • MOA between the service Operational Test Agencies (ATEC, OPTEVFOR, -AFOTEC, JTIC and DOT&E), 20 Feb 09, Using Design of Experiments for -Operational Test and Evaluation

      • OSD DOT&E Memo, 19 Oct 10, Guidance on the use of Design of -Experiments (DOE) in Operational Test and Evaluation

      • OSD DOT&E Memo, 23 Jul 13, Best Practices for Assessing the -Statistical Adequacy of Experimental Designs Used in Operational -Test and Evaluation

      • "AFOTEC OT&E Guide," Apr 20

      • Institute for Defense Analyses paper, Nov 14, Power Analysis -Tutorial for Experimental Design Software

      • AFOTEC Operational Test Information File, 17 Feb 15, Statistical -Power for Test Designs

      • DODI 5000.02, Operation of the Defense Acquisition System , 7 Jan -15

      Technical References and Citations

      Best Practices for Assessing the Statistical -Adequacy of Experimental Designs Used in Operational Test and -Evaluation. Washington, D.C.: OSD.Freeman, L. J., Johnson, T. H., & -Simpson, J. R. (2014).

      Power Analysis Tutorial for Experimental Design -Software. Alexandria, Virginia: INSTITUTE FOR DEFENSE ANALYSES.Hartman, -M. (2014, August 19).

      Test Design Comparison and Slection Method Best -Practice. Retrieved March 3, 2015, from AFIT STAT COE: -http://www.afit.edu/docs/Test%20Design%20Comparison%20and%20Selection-Best%20Practice.pdfKacker,

      R. N., Kuhn, R. D., & Lawrence, J. F. (2013). Combinatorial testing for -software: An adaptation of design of experiments.

      Measurement, 46 (9), -3745-3752.Kruschke, J. K. (2012, May 31).

      Bayesian Estimation -supercedes the t test. Retrieved March 17, 2015, from Indiana -University, Bloomington: -http://www.indiana.edu/\~kruschke/BEST/BEST.pdfKuhn, K. L. (2010).

      Practical Combinatorial Testing. NIST, U.S. Department of -Commerce.Montgomery, D. C. (2009).

      Design and Analysis of Experiments, -7th Edition. New York: Wiley and Sons.Myers, M. A.-C. (2009).

      Response -Surface Methodology. Hoboken, NJ: John Wiley & Sons, Inc.NIST1. (n.d.).

      Engineering Statistics Handbook . Retrieved from -http://math.nist.gov/coveringarrays/coveringarray.htmlNIST2. (n.d.).

      Engineering Statistics Handbook . Retrieved from What are John\'s 3/4 -fractional factorial designs?: -http://www.itl.nist.gov/div898/handbook/pri/section5/pri57.htmNIST3. -(n.d.).

      Plackett-Burman Designs . Retrieved from Engineering -Statistics Handbook: -http://www.itl.nist.gov/div898/handbook/pri/section3/pri335.htmNIST4. -(n.d.).

      Central Composite Designs (CCD) . Retrieved from Engineering -Statistics Handbook: -http://www.itl.nist.gov/div898/handbook/pri/section3/pri3361.htmOrtiz, -F. (2014).

      Dealing with Categorical Data Types in a Designed Experiment -Part II: Sizing a Designed Experiment when Using a Binary Response. -Retrieved March 3, 2015, from AFIT STAT COE: -http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdfRosenbaum, -P. R. (2002).

      Observational Studies Second Edition. New York: -Springer-Verlag Inc. .Winkler, R. L. (2003).

      An Introduction to -Bayesian Inference and Decision, 2nd Edition. Gainsville, FL: -Probabalistic Publishing (www.decisions-books.com).

      Footnotes

      fn1

      1. Quantitative -- A term used to describe data that is measured on a -numeric or quantitative scale; interval and ratio scales are -quantitative. The data may be discrete or continuous.

      fn2

      1. Qualitative -- A term used to describe data that is descriptive or -subjective; the values are ordinal or nominal in nature; e.g., red, -blue and green.

      fn3

      1. Population parameter -- A quantity or statistical measure that for a -given population is fixed, such as a mean or a variance. The -parameter is used in some general distribution or frequency function -(e.g., a Normal Distribution) to make it descriptive of that -population.

      fn4

      1. Estimation -- An attempt to gain insight about an unknown population -parameter based on information obtained from sample data. At AFOTEC -we typically estimate means and variances of measures, factor -effects, and proportions of failures.

      fn5

      1. Sample -- A set of data collected from a population.

      fn6

      1. Factor -- An independent variable which may affect the performance -of a system when its levels are changed.

      fn7

      1. Level -- A specific setting of a factor during a test or experiment.

      fn8

      1. Run -- One combination of factor levels used for collecting data on -one or more measures; a test design point.

      fn9

      1. Effect - The average change in a response variable produced by -changing the level of a factor.

      fn10

      1. Main Effect - The effect of a factor (independent variable) on a -measure (dependent variable) averaging across the levels of the -other factors.

      fn11

      1. Interaction -- A situation where the effect of one factor on a -response depends on the level of another factor.

      fn12

      1. Factorial Design -- A test plan consisting of two or more factors, -each with discrete possible values (or levels). A full factorial is -a design whose experimental units (runs) take on all possible -combinations of these levels. A design which includes a -strategically selected subset of the possible combinations is called -a fractional factorial.

      fn13

      1. Balance -- A column in a test design matrix is balanced if every -factor level occurs an equal number of times. A test design is -balanced if every possible factor level combination occurs an equal -number of times.

      fn14

      1. Orthogonal - A test design is orthogonal if each factor can be -evaluated independently of all the other factors. This is possible -if, for the test runs involving any level of any factor, the levels -of the other factors are present in equal amounts. When an -orthogonal test design has two-level factors coded -1 and +1, the -inner (dot) product of any two columns is 0.

      fn15

      1. Disallowed Combinations - A combination of the levels of two or more -factors that cannot be feasibly executed together in a test run.

      fn16

      1. Center Point -- A test run where every continuous factor is set to -the value halfway between its minimum and maximum factor levels.

      fn17

      1. Projection -- A property of factorial designs where the degree of -replication doubles when a design column is removed (such as when a -factor is determined to be insignificant). With fractional factorial -designs the degree of fractionation is reduced.

      fn18

      1. Active Effect -- A term used to describe a main effect (factor) or -interaction that causes a statistically significant difference in -the response variable when the factor levels are changed.

      fn19

      1. Sparsity-of-Effects Principle -- The principle that a system is -usually dominated by main effects and low-order interactions. Thus -it is very likely that main effects (single factor) and two-factor -interactions are the only significant effects when analyzing data -from a test; higher-order interactions such as three-factor -interactions are very rare.

      fn20

      1. Correlation -- A statistical measure on a scale from -1 to 1 that -indicates how close two variables are to having a linear -relationship with each other. Two factors are perfectly correlated -when the value of one factor's level can be precisely determined by -knowing the value of the other factor's level.

      fn21

      1. Aliasing - A condition where the effect estimate of one factor -includes the influence of one or more other effects (main effect or -higher-order interactions).

      fn22

      1. Confounding -- Synonymous with aliasing: a condition where the -effect estimate of one factor includes the influence of one or more -other effects (main effect or higher-order interactions).

      fn23

      1. Resolution -- An indication of the ability to independently estimate -main effects and interactions in a fractional factorial design.

      fn24

      1. Screening design -- Designs that focus on the identification of -active main effects. The goal is to reduce an initially large list -of potential factors to only those that are influential on the -response variable. Using screening designs decreases the size of -subsequent test designs used to estimate two factor interactions or -higher-order effects.

      fn25

      1. Optimal Designs -- A test design whose levels are combined in a way -that optimizes some statistical design quality criterion that is a -function of the design matrix.

      fn26

      1. Linear Regression -- A statistical process to model the change in -the mean value of a continuous dependent variable (e.g., measure) as -the values of one or more continuous independent variables change.

      fn27

      1. Augmentation -- The process of strategically adding new runs to an -existing test design after some data has been collected.

      fn28

      1. Deterministic -- A deterministic system or model will always produce -the same output from a given starting condition (level settings of -the independent variables.)

      fn29

      1. Distribution -- A table or function showing all the possible values -of a data set and how often they occur.

      fn30

      1. t -tuples - A combination of the levels of t factors selected from -a design. Suppose there is a design with four two-level factors with -levels coded as +1 and -1. There are four possible 2-tuples, e.g. -(+1,-1). There are eight possible 3-tuples, e.g. (+1,-1,+1). There -are sixteen possible 4-tuples, e.g. (+1,-1,+1,+1).

      fn31

      1. Strength - An integer between 2 and the total number of factors in -the test design. For combinatorial designs, strength t means that -for every possible subset of t factors, every possible t -tuple of -level combinations is present in the design at least one time.

      fn32

      1. Coverage - Describes the percentage of possible factor level -combinations (after removing the disallowed combinations from the -complete combination space) that a combinatorial design includes at -a given strength.

      fn33

      1. Stochastic - Randomly determined; any process or system that has a -random probability distribution or pattern which may be analyzed -statistically, but not predicted perfectly.

      fn34

      1. D-Efficiency is calculated as follows: = 100 \times \left( \frac{\left| X^{'}X \right|^{\frac{1}{p}}}{N} \right) where p is the number of columns in X matrix and N -is the number of runs.

      fn35

      1. G-Efficiency is calculated as follows: = 100 \times \left( \frac{\sqrt{\frac{p}{N}}}{\sigma\_{M}} \right) where p is the number of columns in X matrix, N is the -number of runs and [ σ ~M~ ]{.math .inline} is the maximum -standard error for prediction across the space. The X matrix is the -de-correlated X matrix.

      fn36

      1. A-Efficiency is calculated as follows: = 100 \times \left( \frac{p}{\text{trace}\left( N \times \left( X^{'}X \right)^{- 1} \right)} \right) where p is the -number of columns in X matrix and N is the number of runs. The X -matrix is the de-correlated X matrix.

      fn37

      1. ANOVA -- A mathematical process for evaluating the variation in data -between groups and within groups in order to determine whether there -is a differences between the group means. This procedure can be used -to compare multiple systems, or determine if there are differences -in the mean response between levels of a factor.

      fn38

      1. An orthogonal array may not exist for the required number of factors -and levels ↩︎

      fn39

      1. All factors must be continuous

      fn40

      1. Strength 4 and higher

      fn41

      1. Resolution VI or higher is required to analyze 3 factor interactions
      \ No newline at end of file diff --git a/sites/oteguide/fn_guides/editing_reports_guide/index.html b/sites/oteguide/fn_guides/editing_reports_guide/index.html deleted file mode 100644 index 5dadc7be..00000000 --- a/sites/oteguide/fn_guides/editing_reports_guide/index.html +++ /dev/null @@ -1,470 +0,0 @@ -Editing Guide

      Editing Guide

      "I cannot think of anybody who doesn't need an editor, even though -some people claim they don't." ~ Toni Morrison

      "Clever words are not as good as straight talk." ~ Chinese proverb

      "Like stones, words are laborious and unforgiving, and the fitting of -them together, like the fitting of stones, demands great patience and -strength of purpose and particular skill." ~ Edmund Morrison

      Last Updated/Reviewed: 08 December 2020

      Originating Office: AFOTEC A-3

      PURPOSE

      This guide was developed for technical editors, but will help all AFOTEC -personnel write and edit final test plans and reports that meet our goal -of providing relevant, credible, and timely feedback to the acquisition -community and Air Force leaders.

      *Note : This editing guide applies to final AFOTEC test plans and -reports. It is not designed to take the place of, nor conflict with, -writing guidance for other products, such as OPRs/EPRs, memos, or -other AFOTEC test products. Please adhere to the writing guidelines, -authorities, and templates that apply to the specific product you are -producing.*

      This guide follows the grammar and punctuation rules from the following -authorities: Air Force Handbook (AFH) 33-337, Tongue and Quill , 27 -May 15 (Incorporating Change 1, 19 Nov 15), and the Air University -Press, Air University Style and Author Guide (Maxwell AFB AL, 2005), -unless otherwise indicated. While you should explore and review -reference materials you feel are helpful in developing your editing -skills, the rules outlined herein take precedence over other -writing/editing guidance.

      Executive Summary, Body, and Appendices

      Edit the executive summary, the body, and the appendices as separate -documents. The appendices will be created first because they contain the -technical information and details of the assessment or evaluation. In -the appendices, symbols, equations, and technical terms are appropriate, -just as they are in tables. The body is a synopsis of the information -contained in the appendices. It is written as a formal document in which -symbols, abbreviations, and technical terms are spelled out and is -intended for a wider audience.

      Executive Summary . While the executive summary is usually written -last, it is the most crucial part of the document because it is intended -for and read by the wider acquisition community. If written as intended, -the executive summary will capture the critical components of the -assessment or evaluation in a brief but thorough summary.

      The executive summary is written from the Commander's perspective, as -though he or she is personally addressing the audience. It describes the -system under test, type of test, decision maker, and decision supported, -and summarizes the system's effectiveness, suitability, mission -capability, critical deficiencies, and AFOTEC's recommendations (in -order of their significance) to correct those deficiencies. It is -written as a formal document in which symbols, abbreviations, and -technical terms are spelled out, and although it is acceptable to use -acronyms in the executive summary, writers should limit their use to -promote a smoother read.

      Consistency is Key

      In regards to subjective writing preferences, ensure the author applies -them consistently, i.e., benchmark, bench mark, and bench-mark should -not appear in the same document. When such variations occur, choose the -most frequently used or best option and change other instances to match.

      One Voice

      Several different test team members collaborate on writing each plan or -report. Edit the mechanics of each part of the document separately, but -it is important to read the plan or report as a whole document to -confirm that it reads as "one voice" rather than as a conglomeration of -different sections by different authors.

      Templates

      Templates for each type of test plan and report are posted on -SharePoint. AFOTEC encourages the use of templates because they are a -good guide to ensure the test team includes all necessary planning and -reporting elements. Test teams may find it necessary to deviate from the -templates and include different information or exclude information not -pertinent to their program. They should feel free to innovate as needed -as long as they meet the ultimate goal of creating a comprehensive -document that meets AFOTEC's planning and reporting obligations. -Templates include blue instructional text to assist the test team in -populating various sections, but if writers have questions not covered -in the instructional text, have them contact A-3 for additional -guidance.

      The templates are dynamic and change as guidance and reporting -requirements change. A-3 attempts to make template changes in real time, -but this is not always possible. If you are unsure whether a template -reflects the latest changes, contact the A-3 technical editor.

      Microsoft Word Options

      Set the following "options" to ensure Microsoft Word works in harmony -with our templates. Setting these options from the start will solve a -lot of formatting problems before they begin.

      Display:

      • All formatting marks

      Proofing:

      • AutoCorrect: remove ALL checks

      • AutoFormat: remove all checks except for "smart quotes" ( Note : -AFOTEC does not use superscript for ordinals; superscript is only -used for fractional factorial notations in factor tables)

      • AutoFormat As You Type: remove all checks except for "smart quotes"

      • Spelling and Grammar Settings:

        • Grammar and style options: Require (comma: always); -(punctuation: inside); (spaces: 1)

      Advanced:

      • Enable Click and Type

      • Default Paragraph Style: AFOTEC Body

      • Insert pictures "in line with text"

      • Cut, copy, and paste

        • Show Paste Options button when content is pasted

        • Use smart cut and paste (Word 2002-2010)

        • Pasting between documents when style definitions conflict---Use -Destination Styles (Default)

      • Show Bookmarks

      • Field Shading--always

      • Style area pane width in Draft and Outline views--2"

      • Compatibility should be Word 2010 (DO NOT check any of the layout -options)

      Focus Areas

      Enforce the following standards to ensure AFOTEC produces uniform -documents. These areas are not listed in order of importance, but are an -overall view of the editing process.

      Styles

      AFOTEC templates are designed with unique Microsoft Word styles that -work in tandem with the page numbering and the table of contents. That -is why it is critical to ensure the styles are not removed or corrupted -during the writing process. Unless a writer deliberately changes or -corrupts a style by deleting a heading or subheading, the templates are -user-friendly and low maintenance. The body style is designed to be -"justified" and to have the optimal amount of white space to make it -easy to read and distinguish between paragraphs. AFOTEC uses one space -after end-of-sentence punctuation because that prevents excessive -spreading between letters and words when using justified alignment .

      Problems can arise when writers copy and paste information from other -sources into the template document, which can introduce styles from that -source. In those cases, you will have to clear the styles and reapply -the appropriate AFOTEC styles. Teach writers to use the "use destination -styles" option on the pasting clipboard to eliminate this problem.

      To confirm the styles are correct and uncorrupted, open the document in -Draft view. Reapply appropriate AFOTEC styles where necessary. Modify -corrupted styles if it is something simple to correct such as left align -versus justified, tab spacing, font size, etc. If more than one style is -corrupt or you cannot modify them easily, use the following steps to -import styles from a document in which AFOTEC styles are sound and -uncorrupted (i.e., plan or report template):

      • Click on the third icon in bottom left corner of "Styles" pane -called "Manage Styles."

      • Click "Import/Export" on bottom left corner of the Edit tab.

      • On the right side pane of the "Organizer" window that opens, close -the "In Normal" file and open a document with all the uncorrupted -AFOTEC styles by clicking "open file." Locate and open that file. -All the styles from that document will populate the right side pane.

      • Copy all AFOTEC styles you wish to replace from the right side to -the "to Document 1" left side. (Note: if you have set your "Normal" -template to contain AFOTEC styles [recommended], just copy the -necessary styles from there to the "to Document 1" left side and -omit the step of closing the "Normal" file and finding a file with -uncorrupted AFOTEC styles.)

      • Click "yes" or "yes to all" when prompted as to whether you want to -overwrite the existing styles in the document.

      • Close the "Normal" file or the file you copied styles from on the -right side pane.

      • Close out of the "Organizer" window.

      • The corrected styles will appear in your style pane.

      Acronyms

      Define an acronym the first time it appears in each section (i.e., -executive summary, body, appendices [as a whole, not each appendix as a -separate section]), then use the acronym thereafter. Edit these three -distinct parts of the plan or report as separate documents.

      Add all acronyms in the document to the acronym table in the designated -appendix. If an acronym is only used one or two times, delete it from -the document and the acronym table and spell it out.

      Define acronyms in tables and figures in the acronym table, not within -the table or figure ; the only exception is a measure table that -displays a "mean" as the metric. To help readers make the connection to -a standard term (i.e., "mean time between failures"), add the standard -acronym in parenthesis following the measure title, then define it below -"*KPP or supports KPP or \^ Identified Standard" if applicable (or in a -merged row at the bottom of the table as shown in the following -example). Then, add the acronym to the acronym table.

      Example:

      (FOUO)
      Operational Capability: Reliability
      MeasureMetricThreshold
      MOS 3.8: Time Between Failures (MTBF)Mean>= 8,736 hours
      MTBF–mean time between failures

      Some acronyms are more easily recognized than the words they represent -(e.g., NASA, NATO). In those cases, do not remove the acronym from the -document, nor from the acronym table even if it is used only once. This -is a judgment call so consult your test team's SME, TD, or TA if in -doubt as to whether you should remove a particular acronym.

      Acronyms use the same vowel/consonant rules as regular words (i.e., use -"a" before a consonant; use "an" before a vowel), except that with -acronyms the beginning "sound" rather than the beginning "letter" is -what determines the article you will use. If the beginning sound is a -vowel sound, you will use "an." If it is a consonant sound, use "a."

      Examples:

      • an OA report (beginning sound--long o vowel sound)

      • a NASA rocket (beginning sound--consonant n)

      • an MOT&E (beginning sound--short e vowel sound)

      Follow regular capitalization rules when defining acronyms and -capitalize only those words that are proper nouns. The only exception to -this rule is the acronym table, which should use the following "title -case" capitalization rules for uniformity:

      • Capitalize the principal words, including prepositions and -conjunctions of four or more letters.

      • Capitalize an article---the, a, an---or words of fewer than four -letters if it is the first or last word in a title.

      Performing the acronym scrub is the most time-intensive part of the -edit, but it must be done, and is ultimately the technical editor's -responsibility. Do not cheat!

      Perform a spell check, but before you begin, go into Microsoft Word -options/Proofing and uncheck the Custom Dictionary "Custom Dic" button; -select "English (United States)" as your language.

      Make sure each acronym spell-check catches was defined in the acronym -table. If not, add it and define it. Begin with the first acronym in the -table and perform the following:

      • Highlight the acronym

      • Copy it (ctrl c)

      • Open find (ctrl f)

      • Paste (ctrl v)

      • Go to top of doc (ctrl home)

      • Enter "find next"

      • Make sure the acronym is defined the first time it shows up in the -body and appendices, and that the definition is the same as what is -in the acronym table

      • Repeat this process for each acronym

      In addition to this, remove acronyms from the table that were not used -in the plan or report. The acronyms provided in the templates will not -necessarily pertain to the document you are editing.

      Commas

      Technical writing requires the use of the "serial" comma (sometimes -called the oxford comma), which is the comma used immediately preceding -a coordinating conjunction (usually, and, or, or sometimes nor), or the -final item in a series of three or more items. This is important because -the meaning of a sentence can change when commas are omitted or used -incorrectly.

      "Next Page" and "Page" Breaks

      Use "next page" breaks when you separate a page to change its -orientation from portrait to landscape, or when you create a blank page -or a new appendix. Use regular "page" breaks versus "next page" breaks -between new sections in the body and between measures in appendix B. The -frugal use of "next page" breaks prevents the problem of a document -containing too many sections, which inhibits printing a customized range -of pages within a document.

      NEVER use "continuous" page breaks in AFOTEC documents. "Continuous" -page breaks are hard to remove. If you try to delete them, you will -begin a domino affect of formatting difficulties. Use the following -method to remove "continuous" page breaks successfully:

      • Place cursor at beginning of document

      • Scroll to end of document while holding mouse button down to select -everything (do not use Ctrl A) (this can take a while on a long -document, but there is no short cut so be patient)

      • Hold down shift button and do a left click on mouse

      • Go to Page Layout/Page Setup

      • On layout pick "New Page"

      • And "selected sections"

      • Push OK button

      You should have all "next page" page breaks in place of the "continuous" -page breaks when you complete this process.

      Headers and Footers

      Headers. All headers on AFOTEC plans and reports should be connected -("linked to previous") with the exception of the SF298 (only applicable -to reports). This enables consistent classification markings on every -page.

      Footers. All footers on AFOTEC plans and reports should be connected, -with the exception of the cover page (which is not numbered) and the -SF298 (only applicable to reports). This enables consistent -classification markings on every page.

      Header/Footer on SF298. Keep information on the Standard Form (SF) 298 -at the unclassified level whenever possible. It will usually have a -different classification marking or none at all. However, even when its -classification is the same as that of the plan or report, do not connect -the header or footer because the form also requires different margins -and header/footer settings and does not have page numbers (technically, -it is not part of the report and should not be included in the number of -pages in a report).

      Page Numbering

      The templates were designed with automatic page numbering that populates -the table of contents automatically. However, when you add a "next page" -break, you may have to click into the footer and go to "format page -numbers." Click the radial button and choose "continue from previous -section" so that the page numbering will continue instead of restarting -at page 1.

      Blank Pages

      Insert or remove a blank page (i.e., Page intentionally blank) as -necessary so that the following pages are always right facing (which -will present on the left side of the screen in the 2-page layout view):

      • Executive Summary

      • Table of Contents

      • First page of the body of the report, which begins with -"Introduction"

      • First page of Appendix A

      The SF298 Report Documentation Page (applicable for reports only) should -always be left facing, (which will appear on the right side of the -screen in the 2-page layout view) to ensure the form stays on the front -and back of the same page.

      A blank page should continue the page numbering of the section it -follows (A-12 is followed by the blank page A-13). The section that -follows the blank page will begin with page number one (B-1).

      Capitalization

      Use capitalization appropriately. Writers have a tendency to capitalize -nonspecific titles of documents and things, even acronym definitions.

      Capitalize:

      • The title of a document when used in conjunction with the program's -proper name:

        • "initial operational test and evaluation" becomes "RQ-4 Initial -Operational Test and Evaluation"
      • The production decision when used in conjunction with the decision -maker's proper title:

        • "full-rate production decision" becomes the "Under Secretary of -Defense for Acquisition, Technology and Logistics' (USD[AT&L]) -Full-Rate Production decision"
      • Cross-references (table or figure) when used at the beginning of a -sentence, but not in the middle of a sentence:

        • "Table (Figure) 1 contains the details."

        • "...as shown in table (figure) X."

      Frame COIs as questions. Write them as a sentence punctuated with a -question mark ( Example : COI 1: Does the KC-46 support refueling?). -Write MOEs and MOSs in title case ( Example : MOE 1.8: Percent of -Reports and Queries Generated Successfully).

      The acronym list is considered a table. Use title case capitalization -for style continuity. In all other parts of the document, follow regular -capitalization rules for words acronyms represent. Joint Publication -(JP) 1-02, Department of Defense Dictionary of Military and Associated -Terms , 12 Apr 01 (amended through Apr 10), Appendix A, contains a -comprehensive list of abbreviations and acronyms. Refer to this -publication for clarification on when to, or not to, capitalize words.

      Citing Air Force (or Other Military) Bases

      Verify military bases are cited properly. The first time a base is -mentioned, spell out the name, type of base, and state or country (ex: -Edwards Air Force Base, California; Ramstein Air Base, Germany; Royal -Air Force Lakenheath, England). Thereafter, use the name of the base -only, or the name in conjunction with the type of base (ex: Edwards or -Edwards AFB; Ramstein or Ramstein AB; Lakenheath or RAF Lakenheath). In -tables and figures, use only the abbreviated form.

      Vertical Lists

      Validate proper punctuation, capitalization, and structure of vertical -(bulleted) lists, depending on how the information was structured.

      Example 1:

      The test team will assess the following capabilities:

      • Data conversion

      • Upgrade integration

      • Operability

      Example 2:

      The test team will assess the

      • multiple data conversions necessary to transition from the legacy -system to the upgraded system;

      • integration of the upgrade at every location (all six Air Force -bases); and

      • operability at Peterson Air Force Base, Colorado; Kirtland Air Force -Base, New Mexico; and Wright-Patterson Air Force Base, Ohio.

      The type of vertical list used will depend on the complexity and length -of the ideas presented. Example 1 is good for a simple list. Example 2 -is a good choice for a complex sentence that contains various types of -punctuation and could be confusing when expressed in one very long, -linear sentence.

      Numbering Tables and Figures

      Number tables and figures sequentially and cross-reference them in the -preceding text. In the body, number tables and figures consecutively -throughout (Use Navigation Pane on View Tab). Then, restart the table -and figure numbering in each appendix, adding the appendix letter as a -prefix. For example, "Table A-5" would be the fifth table in "Appendix -A."

      Tables

      The most important aspect of editing tables is to ensure the contents -reflect the information in the accompanying text accurately. Check each -of the following standards:

      • Apply AFOTEC Table Header + Rating and AFOTEC Table Text styles

      • Verify table properties: preferred width: 100%; default cell -margins: top/bottom: 0", left/right: 0.08"; borders: 1 pt

      • Align cells left/center

      • Add classification by inserting a merged row above the header -row--apply the AFOTEC Caption + Class style to classification -portion marking

      • Ensure classification and header rows repeat by highlighting -classification and header rows and selecting "repeat header rows" in -"Layout" tab

      • Ensure tables break across the next page when necessary; avoid -excess white space whenever possible, particularly in classified -documents

      • Make sure ratings in tables match ratings in accompanying narrative

      • Ensure changes made to COIs, MOEs, and MOSs are rolled into all the -tables (especially the evaluation summary chart or ESC) in which -they appear, and into affected narratives

      • Ensure ratings are uniform in color and size (copy and paste from -template ratings)

      • Confirm tables use percent sign, dollar sign, numbers, and other -symbols

      • Do not define acronyms within the table except when it includes a -standard mean term in parenthesis (i.e., MTBF)--add the acronym and -its definition below "*KPP or supports KPP or \^ Identified -Standard" if applicable (or in a merged row at the bottom of the -table)--add the acronym to the acronym table

      • Align numbers on decimal (use decimal tab on ruler).

      • Add footnotes to the bottom of table in an inserted/merged row or -shift/enter below KPP or Identified Standard, if applicable.

      • Eliminate repetitive symbols or labels (e.g., $, %, hrs) by adding -them to the table header and deleting them from text cells, when -appropriate

      • Capitalize cross-references at the beginning of a sentence: "Table 1 -contains the details." Do not capitalize them in the middle of a -sentence: "...as shown in table X."

      Figures

      Ensure contents of a figure reflects the information in the accompanying -text accurately. Check each of the following standards:

      • Apply AFOTEC Caption + Class style to caption and classification

      • Apply 1-pt black border

      • Do not copy/paste a figure from another document, but save it as a -".png" or ".jpg" file and insert it as a picture. Alternatively, use -the "snip and sketch" tool to save any image--the image will remain -sharp and clear because it is a scan of the image rather than a -conversion. Before "capturing" your image, unselect the "show all -formatting marks" so that you will not capture the marks with the -picture.

      • Do not duplicate figures in the body and appendices. The body is a -concise presentation of the most important facts taken from the -appendices. Appendices contain the comprehensive details and are the -better choice for detailed figures describing a system or test.

      • Eliminate text boxes, symbols, figures, etc., inserted on top of -figures by following the procedures above for converting pasted -pictures to a .png or .jpg file. Reinsert them as a picture with all -add-ons captured as part of the picture.

      • Ensure all acronyms used in figures were added to and defined in the -acronym table.

      • Capitalize cross-references at the beginning of a sentence: "Figure -1 contains the details." Do not capitalize them in the middle of a -sentence: "...as shown in figure X."

      Passive Voice

      Change passive voice to active voice, when appropriate. You can -recognize a sentence with passive voice because a form of the verb to be -(is, are, was, were, be, being, or been) is followed by a past -participle verb (a verb ending in ed, en, or t). A sentence written in -passive voice always contains both.

      VerbPassive SentenceActive Sentence
      isAdequate planning is required for successful OT&E.Successful OT&E requires adequate planning.
      areDetails are contained in appendix D.Appendix D contains details.
      wasThe course was taughby the instructor.The instructor taught the course.
      wereThe results were written in active voice.They wrote the results in active voice ,or if subject is known,The test team wrote the results in active voice.
      beAnnual maintenance will be performed on the system.Maintainers will perform annual maintenance on the systemorMaintainers will perform maintenance on the system annually.
      beingPart A was being substituted for part B as a workaround.The workaround substituted part A for part B.
      beenThe data was given to the analyst.The analyst received the data,or if subject is known,The test director gave the analyst the data.

      Copyrights/Trademarks

      In accordance with the following authorities, AFOTEC is not required to -use the designated markings for copyrights and trademarks in our -documents because we are not a commercial entity and we do not -distribute our documents publically. We are, however, required to use -the proper spelling and capitalization for these trademarks (e.g., -Microsoft PowerPoint, Microsoft Word).

      The Copyeditor's Handbook states:

      "There is no need to include such designations as ^TM^ (trademark), -^SM^ (service mark), ® (registered trademark), or © (copyright) in -running text. Indeed, it is preferable not to use these symbols -because they may interfere with the line spacing of the final -document."

      --Einsohn, Amy. The Copyeditor's Handbook , 2d ed. University of -California Press: Berkeley. 2006.

      The Gregg Manual Reference Manual states:

      "If you refer to other organizations' trademarks in material of a -commercial nature that will be publically distributed, use a raised -symbol after each trademark. In all other documents, the symbols are -not necessary, but do use the proper spelling and capitalization for -these trademarks."

      -- Gregg Manual Reference Manual , 10th ed., McGraw-Hill: New York. -2005. p 114.

      Wordiness

      Remove extra words that add nothing to the meaning of the sentence, as -shown in the following examples:

      • IOC plus 10-year period ---IOC plus 10 years

      • Over a 5-year time period---Over a 5-year period or Over 5 -years

      • Program was first launched---Program was launched

      • In order to avoid confusion---To avoid confusion

      Hyphens, En Dashes, and Em Dashes

      Hyphens, en dashes, and em dashes all have their proper place in -technical writing, and should not be used interchangeably. Hyphens and -en dashes are the "mechanics" of punctuation and have clear-cut rules -for their use. The em dash, on the other hand, is a stylistic choice -that the writer chooses over other forms of punctuation to make a -distinct point.

      Hyphens: Hyphens are used to connect and to separate textual -elements.

      Examples:

      • It was a 2-year program.

      • Wright-Patterson Air Force Base, Ohio; Northrop-Grumman Corporation

      As connectors, hyphens join the parts of compound modifiers.

      Examples:

      • The well-known author gave an interview.

      • The equipment emitted a high-frequency signal.

      Hyphens separate numbers that are not inclusive (i.e., not within a -range).

      Example:

      • My phone number is 500-111-2222.

      The trend is moving toward using the hyphen less frequently.

      Examples:

      • Email versus e-mail

      • Multifunctional versus multi-functional

      Retain the hyphen if its absence makes a word or its meaning unclear.

      Example:

      • Re-cover versus recover (to reapply a covering versus to come back -from; different meaning)

      Retain the hyphen when the prefix ends with the same letter with which -the word begins.

      Example:

      • Re-emerge versus reemerge; re-evaluate versus reevaluate (double-e -can be confusing)

      Some program titles contain the hyphenated "multi-" as part of a program -or system title. In those cases, leave the hyphen in place.

      When one element of a compound modifier ends in "ing" or "ed," use a -hyphen.

      Example:

      • Fast-burning fuel; self-contained module

      When two or more related compounds have a common basic element, retain -the hyphen with all parts.

      Example:

      • 10- to 20-page report; long- and short-term memory

      En Dashes: En dashes connect numbers within a range (including -number ranges in tables) or take the place of the word "to."

      Examples:

      • The years 1995--1996 were interesting ones for most government -workers.

      • The Las Vegas--Albuquerque flight departs in 1 hour.

      • The test team assessed MOEs 2.3--2.6.

      Em Dashes: "Em dashes involve a choice writers and editors make when -other options might be commas, a colon, or a set of parentheses. The em -dash can be used singly or in pairs. Its most common purpose is to set -off an amplifying or explanatory element of the sentence. It is also -used to indicate a sudden break in thought or an interruption in -dialogue." ( Chicago Manual of Style, 16th Edition , pages 333--336)

      Example:

      • The weapon failed the test---the trigger jammed.

      Em dashes are also used to set off explanatory elements that already -contain internal punctuation (i.e., commas).

      Example:

      • Boeing's system offers improvements---better navigation, streamlined -maintenance, and greater reliability---that no other vendor can -promise.

      Apostrophes

      Use apostrophes to show singular possessives (belonging to a single -entity) or plural possessives (belonging to one or more entities). Do -not use apostrophes for a plural expression that is not used in the -possessive form.

      The word "its" means belonging to it and is never expressed as a -possessive. "It's" is a contraction that means "it is" or "it has." If -you cannot replace the word it's with it is or it has, do not use an -apostrophe. The following table contains examples of when to, or not to -use an apostrophe.

      Apostrophe Not RequiredApostrophe Required
      The test teams’ wrote the report. (plural)AFOTEC published the test teams’ report. (plural possessive)
      In the 1970s, Journey was a popular rock band. (plural)Journey was a popular 1970’s rock band. (possessive)
      Several MC-130s are parked on the flightline. (plural)Examine the MC-130’s payload. (possessive)
      They examined its contents. (belonging to it, not a contraction)It’s a windy day. (contraction for it is)

      Choppy Sentences

      Rewrite choppy sentences into ones that flow better by adding -punctuation and conjunctions, when appropriate. However, be careful not -to change the meaning or context when doing so.

      Examples:

      Original : The test team wrote the report. The report informed the 14 -November 2014 full-rate production decision.

      Edit : The test team wrote the report, which informed the 14 November -2014 full-rate production decision.

      Numbers

      Express numbers referring to time, measurements, or money as figures -(e.g., 8 hours, 2 feet, 5 dollars). Use ordinal numbers when spelling -out a unit's name. AFOTEC does not use superscript for ordinals.

      Examples:

      • Correct : 21st Space Wing (21 SW); subsequent use: 21 SW

      • Incorrect : 21st Space Wing (SW); 21st SW; 21 ^st^ SW; 21 ^st^ -Space Wing

      Do not use an "n" or "r" for second and third ordinals

      Examples:

      • Correct : 43d Test Squadron; 302d Airlift Wing

      • Incorrect : 43rd Test Squadron; 302nd Airlift Wing

      Dates

      Write dates differently depending on the context in which you use them. -In general, use the complete date format (full day, month and four-digit -year). However, abbreviate dates in tables, figures, and document or -publication references. Do not mix complete and abbreviated date -formats.

      Examples:

      • Correct : 20 Jul 04 or 20 July 2004

      • Incorrect : 20 Jul 2004 or 20 July 04

      When the terms fiscal or calendar year are spelled out, the four-digit -year should be used.

      Examples:

      • Correct : fiscal year 2001; calendar year 2001

      • Incorrect : fiscal year 01; calendar year 01

      When they are abbreviated, the year should also be abbreviated without a -space between the term and the year.

      Example:

      • Correct : FY01; CY01

      • Incorrect : FY 01; CY 01

      Use the words "to" or "through" instead of an en dash when dates are -preceded by words "between" or "from."

      Examples:

      • Correct : from 15 through 30 July; between 15 to 30 July and 1 to -5 August; 15--30 July; 15--30 July and 1--5 August

      • Incorrect : from 15--30 July; between 15--30 July and 1--5 August

      The only exceptions are tables and figures; always abbreviate dates -and use an en dash.

      Abbreviations

      Common units of measure (e.g., ft, in, sec, nm) or common symbols (e.g., -percent, degrees) are abbreviations, not acronyms. Spell them out or -define them the first time you use them. Do not add them to the acronym -table.

      Terms

      Do not use terms "i.e.," and "e.g.," in conjunction with "etc." and, -most importantly, do not use them interchangeably. Always follow "i.e.," -and "e.g.," with a comma.

      The term "e.g.," means "for example." It is not a finite list ; -there are more possibilities than the ones stated.

      Correct:

      • They brought fruit (e.g., apples, oranges, bananas)

      • They brought fruit (apples, oranges, bananas, etc.)

      Incorrect:

      • They brought fruit (e.g., apples, oranges, bananas, etc.)

      • They brought fruit (e.g., the apples were crunchy)

      The term "i.e." means "in other words" and is used to add extra -information that clarifies. It is finite; it is the only possibility -that could be listed.

      Correct:

      • The hurricane affected two of the Hawaiian islands (i.e., Oahu and -Kauai) with winds over 130 mph.

      • Several personnel (i.e., active-duty and civilian) were promoted at -the ceremony.

      • He corrected the problem (i.e., tightened down the screw) and the -rattling stopped.

      • Four of the tech giants (i.e., Google, Amazon, Facebook, Apple) -hired promising new employees at the job fair.

      Incorrect:

      • Several tech giants (i.e., Google, Facebook) hired promising new -employees.

      Symbols and Units of Measure

      Use symbols and abbreviated units of measure in appendices, figures, and -tables, but spell them out in the executive summary and body of the -document.

      Examples:

      • Executive Summary and Body : percent, greater than, nautical mile

      • Appendix, Figure, or Table : %, >, nm

      Verb Tenses

      Be consistent in the use of verb tenses throughout the plan or report. A -plan describes how AFOTEC will execute a test and is written in future -tense. A report contains results, ratings, and operational impacts and -is written in past tense.

      PlanReport
      Describes how AFOTEC will execute the testContains results and ratings of the system under test, and the operational impact of those results and ratings
      Will happen, future tenseHas happened, past tense

      Embedded Files

      If the test teams follow the templates, you should not discover an -embedded file or link (PowerPoint, Excel spreadsheet, etc.) in the -document, because embedding documents into our plans or reports is not -permitted. However, if you discover such a file or link (i.e., a test -plan or report from another entity) within the document, you will have -to open and save it as a separate file, then forward it along with the -AFOTEC document so it can be included as an attachment to the completed -.pdf file that AFOTEC publishes and distributes.

      Converting Pictures

      Do not copy/paste a picture from another document; instead, save it as a -".png" or ".jpg" file and insert it as a picture. Alternatively, use the -"snip and sketch" tool to save any image, table, text, equation, or -whatever you want to capture from a page and change into a picture. -Before "capturing" your image, unselect the "show all formatting marks" -so that you will not capture the marks with the picture. The "snip and -sketch" tool avoids the conversion process that makes pictures appear -grainy.

      You can also transfer a pasted picture to PowerPoint (directions below) -to change it into a ".png" or ".jpg" file, then delete the original -image and reinsert the picture you created.

      Procedures for converting a pasted picture into a .jpg or .png using -PowerPoint:

      • Capture picture and all text blocks or other objects placed within -it or on top of it, and copy the group of images (Ctrl C)

      • Paste into PowerPoint (Ctrl V), the select all (Ctrl A) or "group"

      • Right click, save as a picture (.png or .jpg)

      • Delete embedded object from document

      • In its place, position cursor and insert picture from where you -saved it

      • Center picture, then add a 1-pt black border (some flow charts or -similar figures may be disrupted by a border and, therefore, are -exempt)

      References/Documentation

      Cite references (documentation) correctly. A good authority is the Air -University Press, Air University Style and Author Guide (Maxwell AFB -AL, 2005), Part 1, Appendix B, Bibliographic Entries. You can access -this publication on the Internet. Suggestion : print out or save the -appendix and have it available for reference when you are editing. In -general, official publications with unlimited distribution (e.g., AFIs, -directives) are italicized:

      • AFI 99-103, Capabilities Based Test and Evaluation , 16 Oct 13

      Reports and other publications with limited distribution (e.g., AFOTEC -reports, threat documents) are enclosed in quotation marks:

      • Executive Order (EO) 13526, "Classified National Security -Information," 29 Dec 09

      • "Defense Enterprise Accounting and Management System (DEAMS) -(Increment 1 Release 3) Initial Operational Test and Evaluation -(IOT&E) Plan," 4 Aug 14

      Memos and standard forms (SF) are cited without italics or quotes. For -memos, state the entity who wrote the memo, the date, and the subject:

      • DOT&E Memo, 1 Aug 14, Procedures for Operational Test and Evaluation -of Cybersecurity in Acquisition Programs

      • SF298, Report Documentation Page

      The table below contains examples of the correct way to cite different -types of reference documents. Use the long citation the first time the -document is referenced and the short version for subsequent citings.

      TypeFirst UseSubsequent Use
      United States CodeTitle 10, United States Code, Section 236610 USC §2366
      Executive OrderEO 13526, “Classified National Security Information,” 29 Dec 09EO 13526
      DoD DirectiveDoDD 8500.01,Cybersecurity, 7 Mar 14DoDD 8500.01
      DoD RegulationDoD 5400.7-R,DoD Freedom of Information Act (FOIA) Program, Sep 98DoD 5400.7-R
      Chairman of the Joint Chiefs of Staff InstructionCJCSI 6212.01E,Interoperability and Supportability of Information Technology and National Security Systems,15 Dec 08CJCSI 6212.01E
      Air Force HandbookAir Force Handbook 33‑337,The Tongue and Quill, 27 May 15 (Incorporating Change 1, 19 Nov 15)Tongue and Quillor AFH 33‑337
      Air Force InstructionAFI 99‑103,Capabilities Based Test and Evaluation,16 Oct 13AFI 99‑103
      AFOTEC InstructionAFOTECI 99‑101,Conduct of Operational Test and Evaluation,1 May 07AFOTECI 99‑101
      AFOTEC ManualAFOTECMAN 99-101,Operational Test Processes and Procedures, 11 Oct 12AFOTECMAN 99‑101
      Military StandardMIL-STD-130N,Identification Marking of U.S. Military Property,16 Nov 12 (with change 1)MIL‑STD‑130N
      Technical OrderTO 00‑35D‑54,USAF Deficiency Reporting, Investigation, and Resolution,1 Nov 11TO 00‑35D‑54
      Concept of Operations“Combat Survivor Evader Locator (CSEL) Concept of Operations,” 4 Jul 05CSEL CONOPS
      System Threat Assessment ReportNASIC-1574-0210-03, “Automated Information Systems Threat Environment Description,” Dec 02AI STAR
      Published AFOTEC document“Defense Enterprise Accounting and Management System (DEAMS) (Increment 1 Release 3) Initial Operational Test and Evaluation (IOT&E) Plan,” 4 Aug 14DEAMS IOT&E Plan or the IOT&E plan
      Official MemorandumDOT&E Memo, 1 Aug 14, Procedures for Operational Test and Evaluation of Cybersecurity in Acquisition ProgramsDOT&E Memo on Policy for OT&E of Cybersecurity
      Standard FormStandard Form 298, Report Documentation PageSF 298

      Patches

      Verify OTA patches on multiservice operational test and evaluation -(MOT&E) plan or report cover pages are correct. Patches should be in -same order of precedence as the signature page (Ref: AFMAN 36-2203), -which is army, marine corps, navy, air force, coast guard. However, when -AFOTEC is the lead OTA, our patch and our Commander's signature will go -first, followed by the other services in the correct order of -precedence.

      Classification Markings

      Ensure writers follow the guidance in DoDM 5200.01, V2, IC 4, DoD -Information Security Program: Marking Information, 28 Jul 20 , and DoDI -5200.48, Controlled Unclassified Information , 6 Mar 20 when they -apply required classification markings to classified documents. Perform -the following actions:

      • Verify the correct distribution statement and derivative, -declassification, and destruction information were included on cover -page.

      • Ensure the Controlled Unclassified Information (CUI) designation -block is included on the lower right-hand side of the cover page, if -needed

      • Ensure every page was marked with the highest overall classification -of the document.

      • Make sure every portion was marked with the applicable portion -marking.

      • Ensure portion marks were carried over ("carry-over marks") when a -paragraph broke and continued onto the following page; insert a -manual line break (shift/enter) at end of the last sentence on the -page, then copy the carry-over mark (that applies to the broken -paragraph) onto the top of next page. This method helps locate -carry-over marks to place them in the correct spot at the top of the -page when they shift to another part of the page due to additions -and/or deletions of information during rewrites/editing.

      • Find carry-over marks that might have moved to the middle of a page -or paragraph by using (ctrl F, special--manual line break). Move -each shifted carry-over mark by deleting the carry-over mark and its -corresponding manual line break, and reapplying them to the top of -the page where they belong.

      Distribution List

      The test team must compile a distribution list that contains members of -the acquisition and AF community with an interest in their particular -program's test plan or report. Those contacts are usually listed in -their program's ITT charter and/or TEMP. The template includes permanent -members who receive each document (e.g., OSD DOT&E, HQ USAF/TE) and -suggests other personnel the team should consider adding (in blue -instructional text). The test team should also add whatever additional -personnel they deem appropriate. The distribution list must contain -personal email addresses, not workflows, for purposes of accountability.

      SF298 Report Documentation Page

      AFOTEC reports (not plans) must include an SF298 attached to the end of -the document. Defense Technical Information Center (DTIC) uses this form -to archive official reports, as required. The SF298 should be maintained -at the unclassified level, if possible, so avoid details that would make -it classified. If not possible, ensure it is marked appropriately in the -header and footer and wherever classification information is required.

      Ensure the test team completes the form, because it is often neglected -in the writing process. Complete the blocks with the following -information:

      • Block 1--Must match date on cover page; use format described (i.e., -12082014, not 12 Aug 14)

      • Block 2--Type of report

      • Block 3--Dates covered are from beginning of testing period to date -of report; use format described (i.e., 09032014--12082014, not 9 Mar -14 - 12 Aug 14)

      • Block 4--Full title from cover page; should match exactly

      • Blocks 5a--5f--Leave blank

      • Block 6--Complete address of AFOTEC Detachment that produced the -report

      • Block 7--AFOTEC HQ address (i.e., AFOTEC, 1251 Wyoming Blvd SE, -Kirtland AFB NM 87117)

      • Blocks 8--11--Leave blank

      • Block 12--Distribution statement must match cover page -exactly---copy and paste from cover page, then reapply "SF298 text" -style

      • Block 13--If there is a classified annex or other supplemental -document for the report, add that information in this block---i.e., -This report is associated with "Annex 1 to the Joint Air-to-Surface -Standoff Missile-Extended Range (JASSM‑ER) Initial Operational Test -and Evaluation (IOT&E) Report," 8 Jan 13 (classified).

      • Block 14--Add a synopsis of the report---i.e., AFOTEC conducted an -OA to assess JASSM‑ER's progress toward operational effectiveness -and suitability in supporting the long-range, standoff precision -strike mission. Additionally, AFOTEC assessed the program's -readiness for OT&E. This OA report will inform the USD(AT&L)'s -7 Dec 10, MS C decision.

      • Block 15--Add the search engine terms a person would likely use on -the Internet to find our report; this information will be added to -the document properties in the published pdf

      • Block 16--Verify that the security classifications for the following -are stated accurately:

        • a. Report--classification of report

        • b. Abstract--classification of abstract (should be -unclassified, if possible)

        • c. This Page--classification of the SF298 front page (should be -unclassified, if possible)

      • Block 17--Limitation of Abstract

        • Unclassified abstract---should read UU (for unclassified, -unlimited distribution)

        • Secret abstract---should read S or same as report (SAR); when it -is not possible to keep the abstract at the unclassified level

      • Block 18--Enter total number of pages, minus the SF298 because it -does not count as part of the report

      • Block 19a--Enter AFOTEC/HO

      • Block 19b--Enter AFOTEC/HO phone number: (505) 846-2484

      Spell Check

      ALWAYS run a final spell check before the final save at the end of the -editing process. It might seem obvious, but this step is often -overlooked.

      Configuration Control

      The hardest part of a technical editor's job is maintaining -configuration control. It is critical you maintain a constant line of -communication with Det test team members to ensure their final edited -version is the ONLY version to which changes are being made.

      After the 2-letter adjudication process, the Det turns the document over -to HQ, via AFOTEC Collaborative Action Platform (ACAP), for command -section coordination. At this point, configuration control of the -document converts from the Det technical editor to the A-3 technical -editor. Detachment personnel should cease working on the document, and -pass any additional changes they wish to make to their A-3 point of -contact. If the Det continues to work on the document they submitted, -which is no longer the valid version, that work will likely have to be -reaccomplished or, worst case, will be omitted inadvertently. The -document will be reviewed by members of the command staff (including the -Commander, Executive Director, Vice Commander, and Technical Advisor) -who will make comments and changes. The A-3 technical editor will -incorporate those changes into the configuration control version.

      Good communication is key to successful configuration control. Never -assume you have the correct version of a document unless the person with -whom the control resides confirms that it is the latest version.

      Table of Contents

      Do not attempt to hand-jam changes to the table of contents (TOC). It is -designed to work in tandem with AFOTEC styles---which is why it is -important to ensure the correct styles are applied---and will update -automatically. To update the TOC, go to the References tab, select -Update Table, then select Update Entire Table.

      Standardization Checklist

      The following checklist can be a handy guide when editing an AFOTEC plan -or report. Print it out to ensure you perform a thorough check of all -areas of emphasis.

      AFOTEC STANDARDIZATION CHECKLIST
      Were AFOTEC styles applied?
      Did you perform an acronym scrub?
      Did you replace “continuous” page breaks with “next page” breaks?
      Did you ensure the serial comma was used consistently throughout the document?
      Did you verify headers and footers were standardized and contained correct classification, if necessary?
      Did you check page numbering to ensure there were no disconnects?
      Were blank pages added or deleted, as required?
      Did you correct capitalization errors?
      Did you verify military and Air Force Bases were cited correctly?
      Did you examine vertical lists for correct structure and punctuation?
      Did you confirm tables and figures were in sequential order?
      Did you verify each table and figure followed AFOTEC standards?
      Did you eliminate inappropriate passive voice?
      Did you rewrite wordy and choppy sentences?
      Did you ensure hyphens, en dashes, and em dashes were used correctly?
      Did you correct apostrophes that were applied incorrectly?
      Did you confirm number rules were followed?
      Were dates written correctly, according to the context in which they were used?
      Did you ensure only acceptable abbreviations were used?
      Did you verify whether the terms i.e., e.g., and etc. were used correctly?
      Did you ensure symbols and units of measure were spelled out in the executive summary and body?
      Did you correct errors in verb tenses?
      Did you eliminate embedded files?
      Did you convert copy/pasted pictures into .jpg or .png files and reinsert them?
      Did you verify documentation was cited correctly throughout the document?
      Did you verify whether classification markings, portion markings, and carry-over marks were applied correctly?
      Did you verify that the distribution list was compiled IAW template guidance, and includes all pertinent addressees?
      Did you check the SF298 to ensure it was accurate and complete?
      Did you perform a final spell check?
      Did you update the table of contents?
      MAINTAIN CONFIGURATION CONTROL! Do not password protect documents in 2-letter and CS coordination. Do not continue to work the version of the document you have at the detachment while it is in 2-letter or CS coordination. Instead, contact your A-3 POC about changes that need to be incorporated.
      \ No newline at end of file diff --git a/sites/oteguide/fn_guides/evaluation_and_reporting_guide/index.html b/sites/oteguide/fn_guides/evaluation_and_reporting_guide/index.html deleted file mode 100644 index 822dd5d3..00000000 --- a/sites/oteguide/fn_guides/evaluation_and_reporting_guide/index.html +++ /dev/null @@ -1,1054 +0,0 @@ -Evaluation and Reporting Guide

      Evaluation and Reporting Guide

      - - - image2 - -

      Originating Office: OPR is AFOTEC/A-3 and OCR is AFOTEC/A-2/9

      INTRODUCTION

      This guide focuses on the analysis, evaluation, and reporting of AFOTEC -OT&E activities. It covers the products and processes you must follow to -complete this final phase of test execution successfully. Submit -suggested changes to: AFOTEC.A3.Workflow\@us.af.mil.

      TEST ACTIVITY SEQUENCE

      During a test activity, you will carry out a sequence of five steps:

      • determine what to test
      • design a test plan
      • execute the test and collect data
      • analyze and evaluate test results
      • report conclusions (Figure 1).

      The success of this activity depends largely on -the robustness of the earlier steps to ensure an OT effort that is -operationally sufficient and technically adequate. This guide focuses on -the analysis and evaluation of results and how to report test -conclusions.

      Figure 1. Test Activity 5-Step Sequence

      - - - image3 - -

      ANALYSIS, EVALUATION, AND REPORTING

      AFOTEC produces a test report that provides results of its analysis and -evaluation of operational test data. Time constraints are a constant and -compounding factor because OT&E reports often inform a milestone or -fielding decision with a hard need-date. Test teams must analyze data, -evaluate impacts to the mission, draw conclusions, and draft and -coordinate a test report as expeditiously as possible so the findings -are relevant and timely.

      Analysis

      Analysis is the detailed examination and application of disciplined -techniques (e.g., mathematics, statistics) to understand or determine -essential features of complex problems. AFOTEC employs an -operations-based approach to analyzing system performance. Sound -analysis produces technical adequacy and credibility. Test teams -typically rely on measures of performance (MOP) and measures of -suitability (MOS) to analyze system performance. Measures of -effectiveness (MOE) are used to analyze operational performance. They -may compare performance at the measures level against a criteria or -identified standard threshold to determine whether there are shortfalls.

      AFOTEC operational evaluations are not based on findings attributed to -operational unit or operator performance shortfalls.

      Analysis provides the foundation or basis for evaluation. While we -separate analysis and evaluation into different steps, there is no -distinct "line" between them.

      Evaluation

      Evaluation is intended to be the judgment of a system's operational -effectiveness and suitability when exposed to representative threats -while being operated and maintained in a realistic operational -environment by typical operators and maintainers. Evaluations require -operational experience to apply judgment and place system performance in -the context of intended operations.

      Operational evaluation determines the impact or significance of MOP/MOS -shortfalls by considering operational effects defined by MOEs. -Similarly, the operational evaluation of MOEs are in the context of the -operations defined by the critical operational issues (COI). After -evaluating COIs and measures, the test team has a basis for evaluating -(determining) a system's operational effectiveness and suitability.

      Reporting

      Reporting is dependent on numerous factors: the OT&E activity, the -goal of the activity, time constraints, and the status of OT&E (is OT&E -ongoing or complete). However, regardless of the OT&E activity or -driving need, AFOTEC will produce credible reports that are accurate, -balanced, and timely.

      • Accurate: The test team analyzes and evaluates test data

        meticulously to ensure the report's narrative and ratings are -consistent and conclusions are defendable.

      • Balanced: The report's narrative highlights both system

        capabilities and system limitations ( what the system did well -and what it did not do so well ) to enable mission effects.

      • Timely: AFOTEC delivers the report to decision makers to

        allow them time to review and understand results prior to a -decision date.

      STRUCTURE OF AN EVALUATION

      AFOTEC structures a test program to facilitate an evaluation of the -operational effectiveness and suitability (E&S) of a system under test -(SUT); therefore, all activities leading to analysis, evaluation, and -reporting support a determination of E&S. Figure 2 illustrates how -AFOTEC structures an evaluation of a SUT.

      Figure 2. Structure of an AFOTEC Test Evaluation

      - - - image4 - -

      The test team composes COIs that ask whether a SUT can accomplish its -critical mission elements or operational objectives. Then, they develop -a variety of measures within each COI to evaluate the SUT's mission -effects, capabilities, functions, properties, or structure. MOEs -evaluate performance-driven mission effects and MOPs/MOSs capture system -capabilities and attributes.

      OT&E Evaluation Structure

      The OT&E evaluation structure is a subset of the OT&E construct. The -structure uses the following elements to report results of a SUT's -evaluation.

      • Operational Effectiveness. Measurement of the system's overall -ability to accomplish a mission when used by representative -personnel in the expected/planned operational environment -considering organization, doctrine, supportability, survivability, -vulnerability, and threat. (AFI 99-103, Capability Based Test and -Evaluation ).

      • Operational Suitability . The degree to which a system can be -placed satisfactorily for use in the field considering its -availability, compatibility, transportability, interoperability, -reliability, wartime usage rates, maintainability, safety, human -factors, manpower supportability, logistics supportability, natural -environmental effects and impacts, documentation, and training -requirements. (AFI 99-103).

      • Critical Operational Issues . A COI addresses a critical mission -element or operational objective examined during OT&E to determine -the system's overall capability to support mission accomplishment -(often referred to as operations-based COIs).

      • Operations. A COI is composed of one or more operations. -Operations describe the actions, activities, or phases of a mission -needed to accomplish the COI. With two or more operations, the -overarching operational objective is the same; however, the steps -and/or conditions to achieve the COI are different between -operations.

      • Mission Effects. Mission effects are outcomes or results of -conducting an operation.

      • Measures. Measures are designed to convey information about a -system's effect, capabilities, functions, properties, or structure -being addressed.

      • Measure of Effectiveness. "Are measures designed to -correspond to accomplishment of mission objectives and achievement -of desired results? They quantify the results to be obtained by a -system and may be expressed as probabilities that the system will -perform as required. MOEs may be further decomposed into measures of -performance and measures of suitability." ( Defense Acquisition -Guidebook ). "A criterion used to assess changes in system -behavior, capability, or operational environment that is tied to -measuring the attainment of an end state, achievement of an -objective, or creation of an effect." (JP 1-02, DoD Dictionary of -Military and Associated Terms , As Amended Through 15 Feb 16 ).

      • Measure of Performance. Measure of a system's performance -expressed as speed, payload, range, time-on-station, frequency, or -other distinctly quantifiable performance features. Several MOPs -and/or MOSs may be related to the achievement of a particular MOE. ( -Defense Acquisition Guidebook )

      • Measure of Suitability. Measure of an item's ability to be -supported in its intended operational environment. MOSs typically -relate to readiness or operational availability and, hence, -reliability, maintainability, and the item's support structure. -Several MOSs and/or MOPs may be related to the achievement of a -particular measure of effectiveness or multiple measures of -effectiveness. ( Defense Acquisition Guidebook )

      • Data/Data Element. Data is any measurement or information -used to determine the value of a measure. Data may be quantitative -or qualitative, subjective or objective.

      The evaluation summary chart (ESC) is a concise presentation of the OT&E -evaluation structure. It summarizes the mission statement, COIs, and -measures using colored indicators to rate each element. Figure 3 is a -representative ESC.

      Figure 3. Example Evaluation Summary Chart

      - - - image5 - -

      Note : Operational capabilities (OC) are depicted for context, but are -NOT rated or assigned colored indicators.

      RATING TENETS/PRINCIPLES

      The following discusses some basic tenets or principles as applied by -AFOTEC.

      Rating

      Rating (a verb) is the process of analyzing, evaluating, and informing -on "something"---for AFOTEC, the "something" are the E&S, COIs, and -Measures elements of the OT&E Construct forming the OT&E Evaluation -Structure. Typically, the results or conclusions are done with a -rating (a noun)---a shorthand to communicate the conclusions from the -analysis and evaluation.

      Terminology

      The term rating is a general term. Based on various guidance (e.g., -Title 10), the particular levels of the OT&E Evaluation Structure use -specific terminology:

      • We Determine E&S

      • We Answer COIs

      • We Rate Measures

      We use a rating to summarize the conclusions for each of these.

      Report

      A report is the tool used to package and communicate results of test -events. An AFOTEC test report can come a wide variety of formats---an -email, a memorandum, a briefing, or a lengthy structured document. -AFOTEC provides standardized forms or templates test teams use, or -tailor, to create a report.

      Ratings and Visual Indicators

      Within rating taxonomies, the definition corresponds to the visual -indicator (color code) differently depending on which level of the OT&E -evaluation structure it applies to. AFOTEC applies visual indicators to -ratings at various levels to give readers a basic understanding of the -conclusion without having to read the complete narrative (Figure 4). -However, the words associated with the colors are different at each -level so test teams must familiarize themselves with the actual rating -and avoid phrases such as, "The MOP was rated Yellow."

      Figure 4. Rating Definitions vs Visual Indicator

      - - - image6 - -

      Rating Taxonomy

      AFOTEC uses the rating taxonomy to indicate results from analyzing, -evaluating, and rating a test activity across levels of the OT&E -evaluation structure. It provides the traceability and rationale for -conclusions drawn at each level. Currently, there are three pre-defined -rating taxonomies that support established test activities (OT&E/OUE, -EOA/OA, and OUA). These taxonomies enable consistency when reporting -test results. A brief summary of each follows.

      OT&E and OUE Rating Taxonomy

      This taxonomy is used for programs acquired within one of the six -adaptive acquisition pathways ("AFOTEC OT&E Guide" contains info on -pathways). OT&Es for these acquisitions inform development activities -and acquisition decisions. Effectiveness and suitability is determined -and reported.

      EOA and OA Rating Taxonomy

      This taxonomy is used for test activities where progress toward both -effectiveness and suitability and programmatic progress are being -determined and reported. EOA/OAs are broken into two areas.

      • Area 1. Used to rate system/capability progress and assesses -progress toward operational capabilities (E&S).

      • Area 2. Used to rate programmatic progress and assess progress -toward delivery of combat capability. The test team assesses major -impacts affecting the progress toward PEO certification of final -OT&E activities by assessing three separate programmatic topics as -organized in AFMAN 63‑119. The three topics are test planning and -documentation, system design and performance, and test assets and -support.

      Operational Utility Assessment (OUA) Rating Taxonomy

      This taxonomy is used for non-traditional programs (joint concept -technology demonstrations) when operational utility is being determined -and reported. OUAs provide the test team's judgment of a system's -military utility when exposed to representative threats while being -operated and maintained in a realistic operational environment by -typical operators and maintainers.

      Ratings for Continuous and Cumulative Feedback

      The majority of AFOTEC programs require continuous feedback during -system development due to agile software development approaches with -rapid release and fielding cycles. However, AFOTEC provides some degree -of continuous feedback on all programs to inform development activities. -In these cases, AFOTEC provides MOE impacts when practical, but rarely -provides COI and E&S ratings. Reporting results in a timely manner is -critical and limits the amount of analysis and results AFOTEC can -provide beyond the MOP/MOS level. Furthermore, stakeholders may not need -feedback beyond the MOP/MOS level at that time.

      RATING MEASURES

      Rating measures consists of analyzing, evaluating, and informing -results. In most cases, analysis should be concurrent with test -execution. During execution, test teams should verify continuously that -they are associating data with the correct measures or supporting -measures, and that analytical techniques and data management procedures -are working.

      General Methods for Rating Measures

      The test team must synthesize ratings of individual MOEs in order to -rate COIs. Accordingly, MOEs may depend on rating MOPs and MOSs. -Measures form a credible basis for rating COIs, effectiveness, and -suitability. The two primary methods for analyzing and rating measures -are direct measurement and reasonable inference.

      Direct Measurement

      Direct measurement is evidence observed during testing that supports the -conclusion that the SUT will be similarly successful when employed by -the warfighter in an operational environment. MOEs document operational -effects that can be summarized as a proportion, percentage, or rate of -success. In other words, if 80% of targets are destroyed, the overall -determination of operational impact (defined by the COI) is likely -positive. In this case, we have direct evidence of the SUT's (mission) -effectiveness. However, if the test is small and 4 out of 5 targets are -destroyed, the test team should be more cautious when rating the COI. -For example, 4 or more successes in 5 trials will occur 19% of time if -the actual success rate is 50%. When the sample size is small, it is -important to use MOPs and MOSs as clues to determine how -unrepresentative (lucky or unlucky) the MOE data might be.

      Reasonable Inference

      Reasonable inference is evidence that supports the logical conclusion -that the system will successfully (or unsuccessfully) achieve desired -effects and accomplish the mission in an operational environment. -Reasonable inference depends on the degree to which the system satisfies -requirements and performs necessary MOP/MOS operations/tasks. MOPs and -MOS are often formally stated or derived from requirements documents, -and therefore have associated performance criteria that must be met by -the SUT's developers. Test results for a MOP/MOS can be compared to the -performance criteria, and the test team can infer that the SUT will or -will not be successful (relative to what the MOP/MOS actually -measures) in the actual operational environment.

      One drawback of using MOP/MOS for an evaluation based on reasonable -inference is that requirement performance thresholds (criteria), the -guiding star for reasonable inference, may not accurately represent the -performance required for desired effects. For example, a requirement may -state that the average miss distance of a weapon (an MOP measure) must -be less than 30 meters. During the test, the average miss distance was -35 meters, but 80% of targets were destroyed, demonstrating the -requirement was overly conservative. To overcome the uncertainty -concerning the validity of the stated requirements, a well designed test -should explicitly plan for the collection and evaluation of effects -(MOEs).

      Types of Measures

      AFOTEC uses three types of measures---MOE, MOP, and MOS. They are the -data (sets) used to rate mission effects or operational impact, and are -evidence of the system's positive performance characteristics, -capabilities, and deficiencies. MOPs and MOSs indicate specific -strengths and weaknesses of a system, mitigate statistical issues -associated with the typically small sample size of MOE data, and support -or refute MOE conclusions. MOPs and MOSs are useful for quantifying SUT -performance and, as they are often continuous data, can be used to -create analysis of variance or regression models of SUT performance -across variable battlespace conditions. In addition, MOPs and MOSs are -often used as evidence to validate Deficiency Reports (DR) at a review -board. A common analogy is that MOPs/MOSs provide a perspective on -individual trees, but MOEs provide a perspective on the forest.

      Measures Worksheet

      The measures worksheet is used to document and organize details of a -measure. Measures worksheets contain significant detail about a measure -and how the data will be collected. For example, the scope section -defines and qualifies the measurement attribute of interest. -Understanding the data in the header of a measures worksheet will be -sufficient for purposes of this guide, but a complete discussion of the -contents of a measures worksheet can be found in the AFOTEC Measures -Guide.

      The header of the measures worksheet contains a concise summary of the -important information regarding a measure. It states the attribute of -the SUT that the test team is measuring (operational capability), a -short title (measure statement) describing what is being measured that -conveys information about the attribute, how it will be computed (the -metric), and the basis for judging the metric (the threshold, if -available). Table 1 is an example of a measures worksheet header within -an AFOTEC report.

      Table 1. Standard Measures Worksheet Header

      - - - - - - - - - - - - - - - - - - - - - - - - - -
      - Operational Capability: Accuracy - - - - -
      - Measure - - Metric - - Threshold - - Results - - Rating -
      - MOP 2.1: Miss Distance - - Mean - - ≤20 meters - - 20.5 Meters - - - - - image7 - - -



      Rating Measures of Effectiveness

      MOEs measure the degree to which the SUT can directly achieve desired -operational effects. MOEs communicate operational effects to -stakeholders (e.g., SPO, warfighter) and how successful the SUT is at -conducting its mission. The operations and associated MOEs are -considered anchors for the OT&E construct and the evaluation structure. -When rating MOEs, the test team must consider the significance of the -effect demonstrated, through direct measurement, as well as test -conditions, DRs, and application of operations experience and judgment. -The test team night have to use reasonable inference to rate -MOP/MOS performance.

      Figure 5 depicts the rating logic for MOEs. MOEs may or may not have an -associated criteria (or ID standard). If there is a criteria/standard, -determine whether it was met or there was a capability shortfall. This -is a mechanical step and the outcome may not be operationally -significant, but external agencies (e.g., SPO and developer) are -interested in knowing whether user criteria was satisfied. If there is -no associated criteria/standard, document the demonstrated effects -without comparing to a criteria/standard. If there were no shortfalls or -negative effects, rate the MOE as "No Shortfall" or "No Negative -Effect." If there was a capability shortfall or negative effect that did -not impact mission accomplishment, rate the MOE as "Shortfall, Not -Significant" or "Negative Effects, Not Significant." If a shortfall or -negative effect impacted mission accomplishment, rate the MOE as -"Shortfall, Significant" or "Negative Effects, Significant."

      Figure 5. MOE Rating Logic

      - - - image8 - -

      Figure 6 contains MOE ratings and visual indicators, and includes an -"Inconclusive" rating, which should be used only when analysis does not -allow a credible effects determination. MOE Notable findings are -addressed later in this section.

      Figure 6. MOE Ratings and Visual Indicators

      - - - image9 - -

      Basis for MOE Evaluation

      Test teams use the following considerations when evaluating MOEs:

      Effect Criteria or Identified Standard

      When a threshold (criteria or identified standard) for an effect is -provided, it should be the basis of a test team's evaluation of the MOE. -Test team judgment is still important because some thresholds of -performance are overly conservative while others underestimate the -required effectiveness.

      A significant challenge in evaluating an MOE is that they may lack an -authoritative threshold from which to base a rating of the measure data. -In other words, if the success rate during a test was 75%, there is -seldom a requirement that states the minimum acceptable success rate is -80%. In addition, MAJCOMs are unaccustomed to providing an identified -standard such as "the success rate should be at least 80%." Test team -judgement and expertise is required to rate an MOE without an -authoritative threshold.

      If a SUT is conducting the same mission as a legacy system, then attempt -to derive MOE effect thresholds from the relevant operator community.

      Feedback from Test Participants

      Test participant feedback on usability of the SUT should contribute -significantly to an MOE rating. An operator is trained to perform system -tasks in order to achieve operational objectives; and if the SUT is -usable and effective at enabling them to perform system tasks, the test -participant feedback should be very positive and the MOE rating should -be No Shortfall or Negative Effect (Green). If participants struggle to -use the system to complete the test scenarios, the rating should be -Shortfall or Negative Effect, NOT Significant (Yellow). If participants -are unable to complete the mission during testing, the rating should be -Shortfall or Negative Effect, Significant (Red).

      Problems/Deficiencies

      The number and significance of problems and deficiencies discovered -during testing should contribute to the MOE's rating. Systems that -accomplish the mission but have problems that must be addressed by the -developer are likely not worthy of a "Green" MOE rating.

      Required Workarounds

      Although OT should be conducted per established employment and support -concepts, TT&Ps and tech data workarounds are common. The significance -of workarounds to accomplish the mission should factor into the rating. -Mission effects may not tell the whole story, because operators and -maintainers are conditioned to accomplish the mission by overcoming -adversity, including system constraints. Workarounds can affect test -scenarios, performance results, safety, and skew operational effects -during OT. Workarounds may also be reasonable as a short term fix during -combat operations, but are unacceptable during ongoing peacetime -operations.

      Statistical Confidence

      It takes a relatively large amount of test data to be statistically -confident the point estimate of the proportion of successes and failures -(from the test of a system with variable performance) is close to the -true success rate that will be observed in the field. For example, -suppose the true success rate of the system was 50% and the test -has 5 test events.

      There is a 0.62 probability (0.31 + 0.31) that test results will be -within 10% of the true success rate of 50% (i.e., 2 or three successes). -Furthermore, it is impossible with a sample size of 5 to accurately -estimate a success rate of 50%; the closest possible outcomes are 2 -successes out of 5 (40%) or 3 successes out of 5 (60%). To have a 0.80 -chance that the test results are within the range 40-60%, the test would -require 30 pass/fail events. If the sample of mission successes and -failures is small, other sources of data become much more important in -the evaluation of an MOE.

      Reasonable Inference of MOP and MOS Impacts

      Test teams may use reasonable inference to develop an estimate of -results for an MOE (i.e., the MOE is not directly measurable) or may be -used to bolster results for an MOE (i.e., small sample size). A variety -of techniques are available for this, such as rationale argument, -weighting schemes (discouraged), algorithms/formulas, models, and -simulations. This is sometimes referred to as "rolling up" or -aggregating to an MOE or possibly a COI. The preferred approach is to -use direct measurement---aggregating can raise questions about the -validity of the conclusion.

      Key Performance Parameters

      Key performance parameters (KPP) are not a significant consideration -when rating MOEs. While they highlight important characteristics of SUT -performance, the test team should place them into the context of the -operation to evaluate operational effect no differently than any other -capability requirement. If a KPP threshold appears contrary to -operational effects (or MOE rating), the test team should recognize the -differences and document to communicate the rationale.

      MOE Notable Findings

      The test team may document notable findings at the MOE level of the -evaluation for two potential situations. First, there was an additional -observation made on one or more MOP/MOS that had an operational effect -measured by an MOE. Second, an operational effect was recorded, but -there was no corresponding MOE. MOE notable findings are included along -with the MOE as part of the process of evaluating a COI.

      Rating MOPs and MOSs

      Typically, test teams analyze MOPs and MOSs by summarizing the measure -data (with an average, percentile, median, user rating, etc.) and then -comparing that value to a threshold value (provided by the operational -user as a criteria in capability requirements documents) or an -AFOTEC-formulated identified standard. Rating an MOP/MOS is a two-step -process (Figure 7).

      Figure 7. MOP/MOS Rating Logic

      - - - image10 - -

      Step 1 is somewhat mechanical and documents that the system performance -met or did not meet the threshold. The program office relies on AFOTEC -discerning whether the benchmark for our rating is user-provided -criteria or a standard developed by AFOTEC as a test planning standard -(the "AFOTEC Measures Guide" contains more info on thresholds). For -purposes of this guide, criteria and identified standards are used -synonymously as a threshold unless stated specifically.

      When SUT performance meets user-established criteria, the MOP/MOS rating -will be "Met Threshold." It is not operationally important whether or -not a SUT meets a threshold---AFOTEC's focus is performance-driven -mission effects. However, this information is provided because it is -important to external agencies such as the users and program offices. -When a measure does not meet criteria, the system is said to have a -shortfall. The test team must determine whether the shortfall is -operationally significant to the user community.

      Step 2 of the MOP/MOS rating logic addresses the operational -significance of performance shortfalls. Operational significance is the -consequence or impact on an operation's outcome if a performance -threshold is not met. A MOP/MOS can fail to meet a threshold, but not -have a significant operational impact. Ultimately, the operational -impact on an MOE determines whether a shortfall is significant. A -shortfall having little to no impact on the MOE is rated "Did Not Meet -Criteria, Not Significant." A shortfall that has mission effect is rated -"Did not meet Criteria, Significant." Operational significance is the -primary technique for rating the MOP/MOS; however, the test team should -consider the operational significance of other factors, such as DRs, and -apply operational experience/judgment to determine significance. The -following paragraphs present additional considerations in determining -operational significance.

      Test Conditions

      Performance measures may meet criteria under some conditions, but not -all, or a system may only be tested in a small set of conditions. In -these cases, team judgement should be applied when -determining/projecting the operational significance. If the shortfall -only appears under certain operational conditions (e.g., certain -altitudes, specific weather phenomena, cyber environment), the test team -uses available information such as CONOPS and OPLANS together with -operational experience/judgment to determine its impact. If mission -effects described by the MOE were significant and impacted the operation -(described by the COI) substantially, the measure may be rated "Did Not -Meet Criteria---Significant Shortfall." Conversely, if the system was -tested across a wide variety of conditions and the impact on the MOE was -not substantial, even if it sometimes did not meet the threshold -criteria, the variation may justify a Not Significant determination.

      Deficiency Reports

      At times, DRs are associated with specific measures. These DRs may or -may not align with performance outcomes and effects on the MOEs/COIs. -When demonstrated effects of performance shortfalls differ from expected -effects documented in a DR, the team must apply experience/judgement, -but will likely rate the measure to be consistent with the MOP/MOS -rating. For more information on the DR process, see TO 00-35D-54 and the -AFOTEC Deficiency Reporting Tool on the AFOTEC intranet Library.

      Beyond the Point Estimate

      When analyzing a MOP/MOS that involves interval or ratio data (e.g., -time, temperature, distance), it is important to consider more than just -the summarized value, known as a point estimate by statisticians, and -should be identified as the metric in the measures worksheet. Point -estimates provide the best guess about some population parameter such as -the overall performance average. However, the dispersion of data around -the point estimate, or variability, also provides useful information to -the test team and the warfighter. While variance or standard deviation -are metrics of choice for statisticians to summarize how data are -dispersed around an average, a more interpretable metric is the range of -the data, i.e., the difference between the highest and lowest data -value. When the data are normally distributed (and therefore the average -is at the center of the distribution) one can estimate that roughly 99% -of the data will be within a range of plus or minus three standard -deviations of the average. However, it is not easy to heuristically -translate a standard deviation into a range if the average is not near -the center of the distribution. Hence the range is a more general and -straightforward way of describing the degree of dispersion in the data. -Using both the average and the range can facilitate a more thorough -assessment of the system. Suppose a system and its users take an average -of 10 minutes to accomplish a task and the range is 2 minutes. Then the -warfighter can be told to expect the system to consistently require -around 10 minutes for task completion (9 to 11 minutes if the average is -centered in the range.) However, suppose the average is 10 minutes and -the range is 12 minutes. Furthermore, suppose the average is not -centered in the range and the test data show the task takes between 8 -and 20 minutes. Then the warfighter may need a warning about the -variability in performance; it may be that waiting 10 extra minutes is -the difference between life and death. Your evaluation of the measure -should take the range of the data into account.

      Operational Experience/Judgement

      The test team's experience/judgment is the cornerstone to credible OT -analysis, evaluation, and reporting. It will be the deciding factor when -determining operational significance throughout the rating levels. In -particular, test teams leverage their operational experience/judgment -when they determine whether a shortfall is operationally significant. -Test team judgment should be informed by credible, and preferably, -verifiable information. Examples of different information types are -overall performance of the SUT during test scenarios, recorded feedback -and ratings provided by users during testing, modeling and simulation -results, system CONOPS, knowledge of legacy system performance (if -applicable), and DRs.

      Key Performance Parameters

      KPPs are not significant considerations when rating MOPs/MOSs. While -they highlight specific system performance, and meeting or not meeting a -threshold criteria is of great interest to the user and SPO, they are -treated no differently than any other capability requirement. It is not -uncommon that a SUT fails to meet a KPP criteria, but there is little to -no operational impact. Test teams evaluate KPP-based operational effects -in the context of various operations and operational conditions, no -differently than other capability requirements. The KPP performance is -documented in MOP/MOS ratings, identified as KPPs, and rated based on -the analysis of significance. If a KPP threshold appears contrary to -operational effects (or MOE rating), the test team should recognize and -document these differences and communicate the rationale.

      Additional Observations

      Sometimes teams learn noteworthy information while evaluating a measure -that was not previously considered during test planning (e.g., unplanned -data collection, interviews, user comments or DRs), nor within the scope -of the measure. While additional observations may not affect the rating -of the measure, they are included in the narrative of the test report. -The test team might identify a shortfall if they measure an aspect of -the SUT not addressed by the criteria. For example, suppose a -requirement states that a system must have an average assembly time of -20 minutes. The test team realizes that disassembly time is also -operationally relevant and not likely to be the same as the assembly -time, so they create a separate measure without a threshold. They can -determine whether a shortfall exists by observing distinct steps of the -disassembly process and the level of difficulty operators experience -while disassembling the system. In addition, when the test team talks to -operators during testing, they can include the average disassembly time -in context and determine if there are negative impacts to the mission. -Figure 8 shows MOP/MOS ratings and visual indicators, including the -"Inconclusive" rating, which should only be used when analysis does not -allow a credible performance determination.

      Figure 8. MOP/MOS Ratings and Visual Indicators

      - - - image11 - -

      RATING CRITICAL OPERATIONAL ISSUES

      The measures, notably MOEs, form the basis for evaluating and rating a -COI. Test team judgment is key to rating a COI and is based on test team -members' prior operational experience, military training, and -experiences during test events. However, it is also informed by -battlespace development, test design, measurement, analysis using formal -statistics, measurement and evaluation logic, etc.

      COI evaluation determines the impact effects had on operations defined -by COIs. After MOEs are rated individually, the evaluation shifts to -collective effects (or operational impacts) on operations. Primarily, -COI ratings are based on evaluating MOEs mapped to each COI, and -judgment of the test team. The COI rating taxonomy has four tiers and -each tier addresses a different operational impact. In addition to -effects addressed in MOEs, the test team should consider the impact of -notable findings for each MOE.

      Each COI rating must be supported by a defensible narrative and an -associated visual indicator. When there are no negative effects -resulting in operational impacts, the COI is rated "No E&S Shortfalls." -When there are operational impacts, the three potential operational -ratings are Minimal, Substantial, and Severe. Figure 9 depicts the COI -ratings logic.

      Figure 9. COI Rating Logic

      - - - image12 - -

      Use the following as a general guideline for rating COIs:

      • No E&S Shortfalls, No impact. There were no negative MOE -effects resulting in operational impact

      • E&S Shortfalls, Minimal impact. Use this rating if the MOE -effects indicate operational personnel will be able to accomplish -the operation defined by the COI with no significant impact. -Generally, this means that all operational tasks can be accomplished -without any (or minimal) limitations and workarounds.

      • E&S Shortfalls, Substantial impact. Use this rating if the -MOE effects indicate operational personnel will be able to -accomplish the operation with significant operational impact. This -may mean the majority or all operational tasks can be accomplished, -but with significant limitations or operational workarounds. -Examples of substantial impact would be: operations accomplished -with a manageable reduction in accuracy; an acceptable increase in -time, assets, and manpower; or minor changes to tactics/ training.

      • E&S Shortfalls, Severe impact. Use this rating if MOE effects -indicate operational personnel will not be able to accomplish the -operation in the projected operational environment. This may mean -the majority or all operational tasks cannot be accomplished, even -with significant limitations or operational workarounds. Examples of -severe impact would be: Unacceptable lethality or reliability; -unacceptable increase in time, assets, and manpower; or unacceptable -cybersecurity.

      Figure 10 illustrates COI ratings and visual indicators, including the -"Inconclusive" rating, which should only be used when analysis does not -allow a credible determination of operational impact at the COI level. -COI Notable findings are addressed later in this section.

      Figure 10. COI Ratings and Visual Indicators

      - - - image13 - -

      Basis for COI Evaluations

      The following paragraphs capture elements test teams must consider when -determining operational impact.

      Preponderance of Measures Meeting Criteria

      MOEs are indicators of whether and how well a COI can be achieved. If -numerous measures indicate success, the operation defined by the COI is -likely to be achieved. However, avoid using a simple numeric that 4 out -of 5 MOEs have no significant effect on the operation to make a -determination. Take advantage of the operational experience and judgment -of the test team.

      Prominent Measures

      There may be one or more measures that are have a greater influence and -impact on a COI. While these measures are usually identified prior to -testing, particularly as a desired effect, test results sometimes reveal -the unexpected importance of a particular measure. For example, even if -a preponderance of MOEs reflect positive effects, a single prominent -measure (effect) could indicate a substantial/severe operational impact.

      Operational Conditions

      It is not uncommon for a system to perform well under some conditions, -but poorly under others. Test results combined with conditions provide -an indication of system robustness. A limitation or poor performance -under certain conditions may justify a severe operational impact, but if -the likelihood of employing/sustaining the SUT under those certain -conditions is rare, it may warrant a rating of substantial, rather than -severe, impact.

      Cyber Effects

      Cyber threats are not more important than any other condition or threat, -but are differentiated and highlighted for two reasons. First, and most -importantly, cyber threats are always present and active during ongoing -operations, including during peacetime. Second, cyber receives a -disproportionate level of external attention, which warrants special -emphasis and highlighting in test reports. Using cyber threat -conditions, test teams estimate cybersecurity protection, detection, and -restoration risks at the MOP/MOS level, and confidentiality, integrity, -and availability effects at the MOE level. Then, they determine -operational impacts of cyber effects on the various operations defined -by COIs.

      Interaction of Results

      Occasionally, prominent measures may have interdependencies that make it -difficult to draw conclusions regarding a specific COI (i.e., "You can -plan a mission quickly, but it isn't complete," or "You can create a -complete mission plan, but it takes an unacceptable amount of time."). -Such interactions must be understood and discussed to determine their -significance and operational impact.

      Holistic Considerations

      Test teams must consider all MOEs under a COI. In conjunction with MOEs -that express desired effects, there may be MOEs or notable findings that -express undesirable effects. Collectively, the operational impact of -these effects will determine the consequent rating of the COI. In -addition, some MOPs/MOSs may have additional observations and DRs to -consider when determining operational impact. For example, consider an -overly complex and timely maintenance action to remove and replace a -component. This alone could result in negative operational effects, but -if the reliability of the component was well beyond the predicted -reliability, and the component would rarely need to be changed, this -could mitigate the negative operational effects. The team would have to -consider other factors in the aggregation, such as confidence in the -reliability predictions, criticality of the component, and operational -tempo.

      COI Notable Findings

      Under rare circumstances, the team may identify a significant shortfall -(additional observation) and/or significant effect (MOE notable finding) -that was not addressed in the original OT&E construct. If the shortfall -has substantial/severe impact on the operational outcome, it is -identified as a Notable Finding and considered when determining the COI -rating.

      RATING OPERATIONAL EFFECTIVENESS AND SUITABILITY

      At the conclusion of OT&E (initial OT&E, qualification OT&E, follow-on -OT&E and multiservice OT&E), an AFOTEC report documents the operational -effectiveness and operational suitability (E&S) determination for the -SUT. The definitions of effectiveness and suitability are fairly -specific, but generally foreign to those without an acquisition and/or -test background. Although the terms come across as acquisition jargon, -the definitions are warfighter-centric and succinctly address the major -operational warfighting considerations. Figure 11 contains E&S -definitions. Effectiveness is synonymous with mission accomplishment and -is defined by the mission statement and documented early in the planning -process. It subsumes all operations defined by COIs and factors in -employment concepts and operational conditions. Suitability is defined -by support concepts, operational conditions, and COI context.

      Figure 11. Effectiveness and Suitability Definitions

      - - - image14 - -

      Rating Effectiveness and Suitability

      By now, it should be clear that determining a SUT's E&S begins at the -measures level and carries through to COIs. After the test team rates -COIs individually, they determine the E&S rating. The E&S rating is -based on the collective operational (or aggregate) impact of COI ratings -on mission accomplishment, and whether the SUT can be fielded and -sustained. The E&S rating taxonomy has four tiers and each tier -addresses a different operational impact. The E&S ratings (or -determination) should be supported by a defensible narrative and -assigned an associated visual indicator. Figure 12 depicts the E&S -rating logic. Use the following guidelines to rate E&S:

      • Rating: Fully Effective . Applied if all aspects of the -mission can be accomplished in the intended operational environment

      • Rating: Effective . Applied if the all aspects of the mission -can be accomplished, but with increased operational costs

      • Rating: Partially Effective . Applied if only some aspects of -the mission can be accomplished AND/OR the mission can only be -accomplished under some operational conditions

      • Rating: Not Effective . Applied is the mission cannot be -satisfactorily accomplished

      • Rating: Fully Suitable . System can be fielded/sustained in -the intended operational environment

      • Rating: Suitable . System can be fielded/sustained, but with -increased operational costs

      • Rating: Partially Suitable . Only some aspects of system -fielding/sustainment can be accomplished AND/OR fielding/sustainment -can only be accomplished under some operational conditions

      • Rating: Not Suitable . Fielding/sustainment cannot be -satisfactorily accomplished

      Figure 12. Effectiveness and Suitability Rating Logic

      - - - image15 - -

      Mission Capability Determination (Optional)

      An overall mission capability (MC) rating may accompany the E&S rating -in the final OT&E report. The MC determination is an optional rating for -AFOTEC test teams that is intended to provide a determination of the -SUT's overall capability to execute or support tasked missions. The MC -rating must consider operational costs (manpower, time, ease of use, -supplies, workarounds and risks), limitations associated with aspects or -portions of the mission, and mission accomplishment across a variety of -operational conditions. Like the E&S determination, it uses a four tier -rating scale (see Figure 13). The MC determination merges E&S -conclusions into a single rating. If the team applies the optional MC -rating, it is in addition to, not in lieu of, the E&S rating. The MC -determination uses the same analysis and evaluation information used to -rate the E&S and the following definitions apply:

      • Rating: Fully Mission Capable . Applied if all aspects of the -mission can be accomplished in the intended operational environment

      • Rating: Mission Capable . Applied if the all aspects of the -mission can be accomplished, but with increased operational costs

      • Rating: Partially Mission Capable . Applied if only some -aspects of the mission can be accomplished AND/OR the mission can -only be accomplished under some operational conditions

      • Rating: Not Mission Capable . Applied is the mission cannot be -satisfactorily accomplished

      Figure 13. Mission Capability Rating Logic

      - - - image16 - -

      TEST REPORTING

      AFOTEC's test report communicates results of our operational -assessment/evaluation and the impact of those results to the warfighter -(the "so what"). The test team reports test findings/results in various -formats and on different timelines depending on the test activity, test -purpose, and external needs. Depending on the nature of the program, -reports inform specified milestones, releases of capability to the -field, progress or status to the program office, or feedback to -developers and testers. Test reporting is the primary enabler for -continuous and cumulative feedback. The OT&E reporting strategy should -be tailored to the acquisition strategy and adapted during OT&E, if -warranted. OT&E reporting has evolved and taken on various formats. With -an increased emphasis on early and continuous OT feedback, reports are -smaller, document less analysis, are generated more quickly, approved at -lower levels, and may not inform defined decisions. There are numerous -types of OT&E reports. Some have established content expectations with -existing templates, while others are heavily tailored to specific -situations. Some reports are written at the end of test, some -immediately after test as quick interim summaries, and some reports are -provided during test execution. OT&E reports can be generated to report -anything from problems or progress, up to a final determination of -effectiveness and suitability. Some reports also include briefings to -communicate results to various stakeholders.

      Provide feedback in writing. In the past, AFOTEC test teams provided -continuous relevant operational feedback during various -functions/forums, but delivered limited written feedback/information. -Valuable information is easily forgotten, lost, or dismissed if not -provided in writing.

      Although reporting choices are dependent on numerous factors, all AFOTEC -reports should adhere to some fundamental OT&E tenets. They should be -accurate, balanced, and timely, and they should be operationally -sufficient, technical adequate, and credible.

      • Accurate: Information will be precise in analysis and -evaluation to ensure the narrative and ratings are consistent and -the conclusions are defendable.

      • Balanced: Balanced reports highlight system capabilities and -limitations (strengths and weaknesses). This can be especially -challenging when focusing on shortfalls.

      • Timely: Timely reporting is broken into two categories. -First, reports delivered to decision makers with time to review and -understand the results prior to decision dates. Second, reporting -operationally relevant information to stakeholders in time to affect -capability development.

      • Operational Sufficiency: The breadth of the operations -addressed while employing new or modified capabilities within the -context of representative employment and support concepts. The -evaluation is considered operationally sufficient if it provides the -decision maker and the warfighter with results from test events -executed across sufficient operational conditions to identify the -capabilities and limitations associated with employment as well as -to determine the effectiveness and suitability.

      • Technical Adequacy: Addresses the relevance of the technical -information produced by the test in relation to the purpose of the -test (i.e., the operationally relevant questions being addressed by -the test activity). A test is technically adequate if the test data -evaluation provides the acquisition decision maker with the -information to inform the appropriate decision.

      • Technical Credibility: Addresses the depth and accuracy of -the technical information produced by the test. AFOTEC products must -be credible and the Commander must have confidence in the conclusion -when reporting OT&E. The report addresses risk with an acceptable -degree of certainty in test results. Acceptable certainty starts -with sound, defendable processes from ITD through OT&E analysis and -reporting.

      Test reporting is broken into two broad categories: continuous reporting -and final reporting.

      Continuous Reporting

      Continuous and cumulative feedback ensures AFOTEC provides timely -feedback throughout the life of a program, to include early acquisition -stages. Test directors should continuously deliver timely, relevant -written information/findings to stakeholders (e.g., developers and -program offices) as soon as available. Test teams provide continuous -feedback in small, tailorable reports (e.g., status reports, significant -event reports, periodic reports, observation reports, and quick look -briefs). TDs may also provide the more structured progress reports -(e.g., operational assessments) at specified milestones, depending on -the acquisition strategy. Reporting deliverables may be cumulative, -containing all OT feedback captured prior to a particular milestone or -decision point. Continuous feedback shifts the impression of an OT -"final exam" to highlighting continuous OT, collaborative discovery, and -information exchange. Thus, AFOTEC better integrates and is a partner in -system development and delivering combat capability through timely -independent feedback.

      Test directors should be acutely aware of their responsibility to keep -their leadership (Det/CCs) apprised of test progress, status, and any -potential issues. Detachment commanders should ensure AFOTEC senior -leadership is aware of any potential controversy that could surface -during reporting. As staff POC, A-3 provides feedback and recommended -courses of action to Detachments and the Command Section during test -execution and reporting. There are several recognized formats for -providing continuous written feedback. Although continuous reporting -fundamentals are common across the various AFOTEC programs, test teams -exercise significant latitude in reporting. Report titles vary from -Detachment to Detachment and contain subtle differences in internal -format. Teams are not limited to currently recognized and helpful -reporting templates.

      Operational Assessment Reports

      EOAs/OAs analyze and assess progress toward E&S and delivering combat -capability. EOAs/OAs are most commonly used for Major Capability -Acquisitions (see DoDI 5000.02), but may be suited for some Middle Tier -Acquisitions (see DoDI 5000.80). Assessment areas are structured around -AFMAN 63-119 templates that address acquisition, development, and -testing. The "AFOTEC OT&E Guide" and corresponding functional guides -(e.g., Test Execution Guide, Cybersecurity Guide) contain guidance on -EOAs/OAs. These assessment reports contain results for two distinct -areas. Area 1 assesses progress toward operational capabilities (E&S). -Area 2 assesses progress towards delivery of combat capability in three -areas: test planning and documentation, system design and performance, -and test assets and support. EOA/OA tools and report templates are -available in the AFOTEC Intranet Library. Approval authority is carried -out in accordance with (IAW) the signature delegation memorandum on the -AFOTEC Intranet Library.

      Status Reports

      Status reports provide updates and important test findings during OT&E. -Status reports are in the form of a letter, normally very short (no more -than several pages) and are not intended to be a mini final report. -Status reports may be periodic (monthly, quarterly, or as required), -associated with specific (planned) test events, or in response to an -external organization's request for test status. Optimally, the OT&E -plan documented the intent to produce a status report, and how often. -The status report approval level is provided in the current AFOTEC -signature delegation memorandum on the AFOTEC Intranet Library. A status -report template is provided as a starting point and is posted in the -AFOTEC Intranet Library. Approval authority is carried out IAW the -signature delegation memorandum on the AFOTEC Intranet Library.

      Periodic Reporting

      Periodic reporting allows frequent reporting on a pre-planned, -continuous interval. These reports are generally small and quick to -produce given the content is limited. They are generally written in a -memo format and the content and level of detail is tailored to the -program needs. Briefings are by exception. Currently, there is no -periodic report template. Contact AFOTEC A-3 for latest guidance and -examples of periodic reports. Approval authority is carried out IAW the -signature delegation memorandum on the AFOTEC Intranet Library.

      Observation Reports

      Observation reports provide OT&E observations of key acquisition -activities and test events, which do not have to be integrated. -Observation reports are usually associated with an observation plan, but -not always. The report summarizes the scope of the observation, to -include the acquisition activities and developmental testing observed. -It describes key activities observed (e.g., development laboratory -testing, modeling and simulation events) and applied data collection -methods (e.g., direct observation, questionnaires, interviews, and -research). It also provides notable observations (significant positive -and negative observations) of interest to decision makers and -developers, and makes recommendations to address those observations. -Observation report briefings are provided by exception, if -requested/directed. Observation reports communicate the status -(acquisition or performance), operational relevance, and results of -significant activities/events. See the observation report template on -the AFOTEC Intranet Library. Approval authority is carried out IAW the -signature delegation memorandum on the AFOTEC Intranet Library.

      Significant Event Reports

      Significant event reports briefly describe results of significant test -events, as determined by the TD and Det/CC, during OT activities. They -are usually not provided in pre-planned intervals. The Det/CC submits -these reports via email to the AFOTEC/CC. The AFOTEC/A-3 receives these -reports and submits them, as appropriate, to the PM, HQ USAF/TE, PEM, -PEO, LDTO, PTOs, operational MAJCOM, and others, within 24 hours of any -significant test event, as described in the test plan.

      Operational Test Situation Reports

      OT SITREPs are used to keep leadership informed of test execution -progress, test team status, and upcoming events. Typically, they are not -provided for continuous reporting, but test teams should be aware of -this type of report. Although uncommon, some teams have used a modified -SITREP format as a method of providing continuous feedback for -exceptionally fast-paced development efforts. Usually, SITREPs are -signed out by the TD, but it is important to elevate approval authority -when SITREPs provide cumulative results for later OT buy-down or draw -conclusions that inform a fielding decision. See the AFOTEC OT&E Guide, -the AFOTEC Test Execution Guide, and the SITREP templates (to include -SAP) for more information.

      Final Reporting

      The final report is the culmination of the OT&E process and is often -considered the most important product AFOTEC produces. The final report -provides a determination of effectiveness and suitability for formal -acquisitions (and operational utility determinations for technology -demonstrations--see OUA tool in the AFOTEC Intranet Library). Final -reports include a briefing, which are general officer-level summaries of -the test report. A final OT&E report is a cumulative document that -contains operationally relevant feedback (periodic reporting) from all -previous OT. It includes a determination of the SUT's operational -effectiveness and suitability while it is operated and maintained in a -realistic operational environment (including exposure to representative -threats) by typical operators and maintainers. Evaluations require -operational experience to apply judgment and determine system -performance and operational impact in the context of intended -operations. Various report templates are available in the AFOTEC -Intranet Library to aid teams when writing final reports (e.g., OUE, -M/I/Q/FOT&E, and OUA). Report templates are a guide to ensure important -content is included. The instructional text describes expectations for -content and format. Approval authority is carried out IAW the signature -delegation memorandum on the AFOTEC Intranet Library.

      Effectiveness and Suitability Final Reporting

      E&S is determined and documented in one of the following final reports.

      • Operational utility evaluation (OUE) report

      • Initial operational test and evaluation (IOT&E) report

      • Qualification operational test and evaluation (QOT&E) report

      • Follow-on operational test and evaluation (FOT&E) report

      • Multiservice operational test and evaluation (MOT&E) report

      OUE Final Reporting

      Although OUEs occur continuously during the OT&E timeframe, they are -intended to provide an E&S determination. They are conducted to -demonstrate or validate new operational concepts or capabilities, -upgraded components, or expanded mission/capabilities of existing or -modified systems. OUEs may support operational decisions (i.e., fielding -a system with less than full capability, including but not limited to -integrated testing of releases and increments of capabilities) or -acquisition-related decisions, whenever appropriate throughout the -system's lifecycle. The OUE M/I/Q/FOT&E report and classified report -annex templates posted in the AFOTEC Intranet Library contain more -information. Also see the "AFOTEC OT&E Guide," 11th ed. for staffing -guidelines.

      IOT&E Final Reporting

      IOT&E is the final dedicated phase of OT&E, which precedes a full-rate -production (FRP) decision. It is the final evaluation that entails -dedicated operational testing of production representative test articles -and uses typical operational scenarios that are as realistic as -possible. IOT&E is conducted by an operational test agency (OTA) -independent of the contractor, program management office, or developing -agency. AFOTEC commonly conducts IOT&Es to inform the FRP/initial -operational capability (IOC)/full operational capability (FOC) and -fielding decisions. IOT&E will likely include developmental (contractor -or government) test and integrated test results deemed operationally -relevant. The OUE M/I/Q/FOT&E report and classified report annex -templates posted on the AFOTEC Intranet Library contain more -information. Also see the "AFOTEC OT&E Guide," 11th ed. for staffing -guidelines.

      QOT&E Final Reporting

      QOT&E is conducted by an operational test and evaluation agency (OTA) -independent of the contractor, program management office, or developing -agency. When programs lack RDT&E funding (e.g., commercial -off-the-shelf, nondevelopmental items, and government furnished -equipment), AFOTEC performs a QOT&E. QOT&Es are independent and -dedicated operational tests that AFOTEC conducts in as realistic an -operational environment as possible to evaluate a system's operational -capability as determined by its effectiveness and suitability in its -intended operational environment. QOT&E is the final dedicated phase of -OT&E preceding a full-rate production (FRP) decision. AFOTEC can conduct -QOT&Es to inform the FRP/initial operational capability (IOC)/full -operational capability (FOC) and fielding decisions. The OUE M/I/Q/FOT&E -report and classified report annex templates posted on the AFOTEC -Intranet Library contain more information. Also see the "AFOTEC OT&E -Guide," 11th ed. for staffing guidelines.

      FOT&E Final Reporting

      FOT&E, a continuation of IOT&E or QOT&E, answers specific questions -about unresolved COIs and test issues, verifies resolution of -deficiencies determined to have substantial or severe impact on mission -operations, or completes areas not finished during the I/QOT&E. -Requirements for FOT&E are documented in an approved AFOTEC OT&E report -prior to planning the FOT&E. The OUE M/I/Q/FOT&E report and classified -report annex templates posted on the AFOTEC Intranet Library contain -more information. Also see the "AFOTEC OT&E Guide," 11th ed. for -staffing guidelines. In addition, DoDI 5000.02, and AFI 99-103 contain -details on FOT&Es.

      MOT&E Final Reporting

      MOT&Es are essentially OT&Es involving more than one military Service. A -standing MOT&E MOA, signed by the four Service OTAs and the Joint -Interoperability Test Command (JITC), outlines roles, responsibilities -and event-driven deliverables for participating Service OTAs. Test team -members should review the MOA prior to MOT&E reporting activities. MOT&E -report coordination is generally more challenging and takes longer. Per -the MOA, supporting OTAs will use the lead OTA's processes and products -during the OT&E activities. However, even in a supporting role, AFOTEC -TDs still have the responsibility to know, understand, and be able to -present overall test results. The Multiservice MOA, the OUE M/I/Q/FOT&E -report and classified report annex templates posted on the AFOTEC -Intranet Library contain more information. Also see the "AFOTEC OT&E -Guide," 11th ed. for staffing guidelines.

      Interim Summary Report

      An ISR is provided to the appropriate AFOTEC signature authority within -10 calendar days of completion of the final phase of OT&E (OUE, IOT&E, -etc.). An ISR is a time-sensitive alternative to a final report (with an -expedited review cycle) used to meet a decision date that occurs before -AFOTEC can complete its final report. It is a short (15 pages maximum) -summary that provides preliminary results of the test team's significant -findings to credibly inform the decision maker about the system's -effectiveness and suitability. Distribution is limited to essential -addressees; however, expanded external circulation may be appropriate -for programs with high interest or upon request or direction. ISRs are -staffed following the product review procedures in the "AFOTEC OT&E -Guide," 11th ed.

      Operational Utility Assessment Final Reporting

      An operational utility assessments (OUA) is a judgment of a system's -military utility when exposed to representative threats while -operated/maintained in realistic operational environments by typical -operators/maintainers. The AFOTEC OUA tool and OUA report template -posted to the AFOTEC Intranet Library contain more information.

      COORDINATION AND PUBLISHING

      With the ever evolving acquisition environment, reduced resources, and -expanding AFOTEC roles, it is imperative that AFOTEC optimize its final -report routing process, while maintaining both technical and -administrative quality. AFOTEC leadership expects the Det technical -advisor (TA) to ensure that each report is technically accurate and -supportable and that it was reviewed by the Det's technical editor (TE) -prior to forwarding it to HQ for coordination. Emphasis is placed on -using final report templates to establish the foundation of the final -report prior to test start. A strawman of the final report should be -ready for review at the TRR briefing. Remaining sections of the final -report should be written as test events are completed to meet the -timeline from last test event to submission of the final report for -staffing and signature. The Det test director, Det TA, and Det/CC are -responsible for ensuring that all reports (e.g., SITREP, status, and -significant event) are ready for signature when they enter 2-letter -and/or CS coordination. See the AFOTEC OT&E Guide for coordination -details.

      Controversial Information

      Potentially controversial information must be passed up the AFOTEC chain -of command before it is shared outside of AFOTEC, and preferably before -official coordination begins. Delaying discussion of issues found early -in the evaluation and reporting phase can limit AFOTEC's options to -respond to those issues.

      Signature/Approval Levels

      The approval levels are documented in the AFOTEC delegation memorandum -posted in the AFOTEC Intranet Library. See this site for current -delegation guidance. All reports should have the Det test director, Det -TA, and Det CC's signature.

      Coordination Method

      The AFOTEC Collaborative Action Platform (ACAP) system is the preferred -coordination tool. AFOTEC A-3 (A-3Z for SAP) is the staff-lead for -coordinating all test reports. However, in certain, time-sensitive -cases, email or other methods may be used. Discuss coordination methods -as soon as possible with A-3 if ACAP will not be used to coordinate. All -reports should be posted on the program's test management page.

      History Office

      The Det TE or HQ TE will transmit a copy of all reports they distribute -to the HO.

      Technical Editor Role

      The Detachment technical editor (TE) works with their leadership to -ensure the final report complies with current AFOTEC template, writing, -formatting, and style requirements. The TE maintains configuration -control of the draft final report and provides guidance to test teams. -At a minimum, the TE is involved in the following three stages of the -writing process: provide the test team instruction and current template -guidance prior to writing; format and review the final report before or -after AO coordination; perform a final edit prior to submission into -2-ltr coordination. Once the final report enters CS coordination, the -A-3 TE maintains configuration control. The OA/OUA/OUE/OT&E report -templates reside on the AFOTEC SharePoint.

      Report Medium

      Reports are coordinated using ACAP, unless the Det obtains CS approval -to use another method.

      Report Timeline Exceptions

      Coordination could take longer on some programs (i.e., classified) or -require an expedited process due to shortened time between completion of -testing (i.e., LTE) and the decision date. If the timelines outlined in -Attachment C need to be modified to meet requirements of a particular -reporting situation, contact A-3 early in the reporting process to -develop an agreeable alternative.

      Final Report Publishing

      The TD is responsible for ensuring the distribution list documented in -the final report contains accurate and up-to-date NIPRNet and SIPRNet -addresses for program-specific personnel (individuals, not workflow -addresses). Once the AFOTEC/CC has signed the final product (keeping in -mind the timeline for staff coordination outlined in Attachment C), the -following procedures are followed to publish the final report:

      • If the TD wishes to include additional files (briefings, -videos/photos, interviews, related reports, etc.) with the final -report, the additional files will be included as supporting -documentation during ACAP 2-ltr coordination. The Det TE ensures -these additional files are in a format compatible with the final -report file.

      • Following final review and approval/signature by the AFOTEC/CC, the -report and all attachments, annexes, and appendices are considered -final; no further changes are authorized without the AFOTEC/CC's -approval.

      • The A-3 TE converts the master report file into an electronic ".pdf" -file, including additional files as requested by the TD.

      • The A-3 TE transmits the file to individuals indicated on the -document's distribution list. If the file is classified, or if there -is a classified annex to the file, the A-3 TE provides NIPRNet -notification to the same individuals stating the file was -distributed via SIPRNet.

      • The A-3 PM posts these files to the program's NIPRNet test -management page (and SIPRNet, if applicable) and removes all -previous versions.

      • The A-3 TE transmits a copy of the file to DTIC for processing.

      Report Briefings

      Report briefings should be in the approved format found on the AFOTEC -SharePoint. If the template formally changes after the TRR briefing, the -previous template can be used unless AFOTEC/CC directs significant -changes requiring use of a draft template. Additionally, the command -section may require modified, new, or deleted information that requires -updating slides in the existing template. Briefings to OSD and agencies -outside the Air Force are normally briefed to AF/TE first. The user and -program office are normally represented. The briefing is reviewed and -coordinated, as documented in Attachment C, and externals (program -office, AFMC, operating command, HQ USAF) are pre-briefed, as -appropriate.

      The report briefing is staffed with the written report as a package. An -electronic copy of the briefing is maintained on the program's test -management page. Detailed backup slides are not transmitted outside of -AFOTEC. The AFOTEC/CC approves briefings required by OSD or other -external agencies before they are presented outside of AFOTEC.

      The briefing trail begins with internal briefings that lead to an -AFOTEC/CC-approved and coordinated presentation. Consistent with the -AFOTEC/CC's "no surprises" policy, the test team should encourage -participation in the AFOTEC/CC presentation by personally inviting the -user and developer communities. Prior to inviting any "externals" to the -CC's briefing, the proposed attendees must be approved by the command -section. Include proposed external invitees on the briefing request -form. Every attempt should be made to include the user and program -office via video-teleconference or telephone conference. Attachment C -contains the product review process for staffing the report briefing.

      There is a need for persistent communication and coordination with our -mission partners and our chain of command to achieve an uneventful final -report briefing to DOT&E.

      • Flexibility and prior preparation are keys to a successful final -report briefing. Know your audience and anticipate their concerns. -Work closely with your DOT&E action officer to know what they will -brief to the Director and ask for feedback after the briefing.

      • Prior coordination is key to final preparations. After AFOTEC/CC -approves, ensure briefings are reviewed and coordinated with our -mission partners and our chain of command. We strive to achieve a -unified Air Force position with no surprises.

      • Coordinate responses to anticipated questions prior to the briefing. -You should answer only questions pertaining to OT&E results or -observations made during testing. It is imperative to have the right -people (normally the user/program office) available to address -questions outside of our lane.

      • Coordinate with the using MAJCOM, program office, SAF/AQ and others -to establish a clear understanding of each participant's -responsibilities. Questions about CONOPS and operational impact -should go to the user representative. Questions concerning funding, -continued development, or plans for correcting deficiencies should -be answered by the program office.

      • Have contingency plans and additional briefings by the proper -attendee ready to address issues you know are important to your -audience or to facilitate discussions. For example, the program -office may need to prepare a briefing describing their plan for -correcting deficiencies following OT&E. These special briefings -should also be coordinated at the GO level well before the briefing. -The additional briefs may not be needed, but you should have them -available in case they are required.

      • Always stay in your lane. Do not answer rhetorical questions or -offer opinions unless specifically asked, and remember you are -speaking for the AFOTEC Commander.

      \ No newline at end of file diff --git a/sites/oteguide/fn_guides/index.html b/sites/oteguide/fn_guides/index.html index 65d528e8..ed2dd1ef 100644 --- a/sites/oteguide/fn_guides/index.html +++ b/sites/oteguide/fn_guides/index.html @@ -1,4 +1,4 @@ -Functional Guides

      Functional Guides

      Following is a list of functional guides and tools detailing the "how" +Functional Guides

      Functional Guides

      Following is a list of functional guides and tools detailing the "how" of conducting operational testing. The list is not all-inclusive and is dynamic; Directorates and Detachments may have additional functional guides and tools. Use these functional guides and tools in conjunction @@ -11,7 +11,7 @@ test events.

      Risk Assessment and Level of Test (RALOT) Guide Details when and how to conduct a RALOT to guide the degree of expected -reporting.

      \ No newline at end of file diff --git a/sites/oteguide/lessons_learned_guide/1-4-Policy-Guidance/index.html b/sites/oteguide/lessons_learned_guide/1-4-Policy-Guidance/index.html new file mode 100644 index 00000000..7dda7ed5 --- /dev/null +++ b/sites/oteguide/lessons_learned_guide/1-4-Policy-Guidance/index.html @@ -0,0 +1,11 @@ +Policy Guidance

      Policy Guidance

      USAF Lessons Learned policy is captured in AFI 10-1302, Air Force +Lessons Learned Program .

      \ No newline at end of file diff --git a/sites/oteguide/lessons_learned_guide/1-5-PROCESS/index.html b/sites/oteguide/lessons_learned_guide/1-5-PROCESS/index.html new file mode 100644 index 00000000..908f1f16 --- /dev/null +++ b/sites/oteguide/lessons_learned_guide/1-5-PROCESS/index.html @@ -0,0 +1,33 @@ +PROCESS

      PROCESS

      The AFOTEC LL process, illustrated in figure 2, adheres to the broad +strokes defined by policy and implements them in a mixed pull +(interviews/surveys) and push process (SharePoint).

      Figure 2. AFOTEC Lessons Learned Process

      + + + image3 + +

      The stand-alone LL submissions form can be found on the LL +Sharepoint +site (example in Appendix A), along with contact information for the +current LL manager. The submission of LL by team members can be +performed at any time during a test program, and is encouraged while +memory of an event is still fresh. This process has a number of +benefits. For interviews it ensures that test directors, having +completed a test event and necessary reporting, are prepared and have +the necessary bandwidth to thoughtfully consider any lessons or problems +they encounter during the test program. Test team members are encouraged +to step back and give the organization its best opportunity to learn +from the challenges they encounter and solutions developed. Surveys +offer a focused opportunity to be directed by questions through the +different aspects of their duties and highlight issues they've +encountered in each. Finally, self-reported observations offer out-of- +sequence opportunities for team members to identify issues and solutions +they have uncovered during the normal accomplishment of their duties.

      \ No newline at end of file diff --git a/sites/oteguide/lessons_learned_guide/index.html b/sites/oteguide/lessons_learned_guide/index.html new file mode 100644 index 00000000..64492999 --- /dev/null +++ b/sites/oteguide/lessons_learned_guide/index.html @@ -0,0 +1,10 @@ +Lessons Learned Guide

      Lessons Learned Guide

      Last Updated/Reviewed: 08 December 2020

      Originating Office: AFOTEC A-2/9

      \ No newline at end of file diff --git a/sites/oteguide/measures_guide/2-INTRODUCTION/index.html b/sites/oteguide/measures_guide/2-INTRODUCTION/index.html new file mode 100644 index 00000000..763b0b59 --- /dev/null +++ b/sites/oteguide/measures_guide/2-INTRODUCTION/index.html @@ -0,0 +1,19 @@ +INTRODUCTION

      INTRODUCTION

      Measurement is central to conducting operational test and evaluation +(OT&E). This technical guide supplements the “AFOTEC OT&E Guide” and +provides AFOTEC personnel the necessary background and specific +directions on how to write and develop measures. The first section is a +general overview of the fundamentals of measurement. Section 2 describes +how AFOTEC develops measures. Sections 3 provides details of measure +documentation. Appendix A provides examples of the types of continuous +and discrete measures. Appendix B provides checklists to ensure measures +are properly written. Appendix C discusses AFOTEC’s process for writing +cyber measures.

      Submit suggested changes to: AFOTEC.A2A9.Workflow@us.af.mil

      \ No newline at end of file diff --git a/sites/oteguide/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT/index.html b/sites/oteguide/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT/index.html new file mode 100644 index 00000000..747ee956 --- /dev/null +++ b/sites/oteguide/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT/index.html @@ -0,0 +1,85 @@ +SECTION 1 FUNDAMENTALS OF MEASUREMENT

      SECTION 1 FUNDAMENTALS OF MEASUREMENT

      Measures Overview

      Test measures are the basis of the evaluation of a system under test +(SUT); they are the data used to assess effectiveness and suitability +and serve as evidence of system deficiencies. Operational effectiveness +and operational suitability are defined as follows:

      • Operational Effectiveness – The overall degree of mission +accomplishment of a system when used by representative personnel in +the environment planned or expected for operational employment

      • Operational Suitability – The degree to which a system can be +satisfactorily placed into field use. Examples of issues evaluated +under operational suitability:

        • Reliability, maintainability, availability

        • Compatibility and interoperability

        • Supportability

        • Transportability

        • Human factors

        • Training requirements

      There are three general types of measures developed for Operational Test +(OT): Measures of effectiveness (MOE), Measures of Performance (MOP), +and Measures of Suitability (MOS). MOEs provide direct evidence that a +user can successfully employ the SUT to accomplish a mission. MOEs can +be used to evaluate the system as soon as it is feasible to test the +system in an operational environment.

      • Measure of Effectiveness (MOE) - Measures designed to +assess the degree to which the SUT can accomplish mission objectives +and achieve desired mission effects. If appropriate, they may +quantify success as a proportion of successful test events, rate of +success, or the probability that the system will achieve some +result.

      MOPs and MOSs can be used to evaluate the system throughout development +and OT&E. Capabilities and functions of a system are evaluated using +both MOPs and MOSs. The supportability and sustainability of a system is +evaluated using MOSs.

      • Measures of Performance (MOP) - Measure a system’s +capabilities. They may quantify performance such as speed, payload, +range, time-on-station, frequency, rating or other distinctly +observable and/or quantifiable performance features. They may also +document whether or not a system can successfully complete a task. +Finally, MOPs may document user ratings of system attributes.

      • Measures of Suitability (MOS) - Measure of the ability to +support the SUT in its intended operational environment. MOSs +typically relate to readiness or supportability and hence include +measures concerning reliability, availability, maintainability, the +quality of system documentation, the quality of training, and the +SUT logistics infrastructure.

      All three types of measures (MOE, MOP, and MOS) are used by the test +team to determine if a system can accomplish a mission, which is stated +as a Critical Operational Issue (COI). For example, the C-130J has two +primary missions: conduct tactical airlift and conduct airdrop +operations. The following are two of the COIs from the C-130J test +program; note that the convention is to phrase COIs in the form of a +question.

      • COI 1: Can the SUT conduct tactical airlift

      • COI 2: Can the C-130J conduct airdrop operations

      When developing measures for a SUT, it is useful to visualize the system +as having four layers that may require measurement and assessment: +Mission Effects, System Capabilities, System Functions and Properties, +and System Structure. Figure 1-1 depicts these four levels in a pyramid +and provides definitions.

      Figure 1. The Pyramid: Evaluation Levels of a SUT

      + + + image7 + +

      Measures can be used to evaluate the SUT at each level of the pyramid. +MOEs are used to evaluate mission effects, while MOPs and MOSs are +typically used to evaluate system capabilities, system functions and +properties, and system structure.

      Qualities of a Good Measure Set

      The following are qualities of a good measures set:

      • Measures should be operationally relevant, necessary, and sufficient

      • Measures should represent something quantifiable or observable, not +a goal or objective

      • The data satisfying a measure should be observable, or at least +inferable

      • Measures should be clear and concise

      Measures should be operationally relevant, necessary, and sufficient. +Measures should only be included in a data set if they provide +significant support to one of three goals: delivering combat capability, +discovering system deficiencies, and evaluating the effectiveness and +suitability of the SUT. Measures required by engineers during system +development may not be relevant to AFOTEC testers.

      Avoid the trap of writing too many measures. The resources required to +collect data for measures varies, but at a minimum every measure +requires the time and attention—limited resources—of a data collector. +Therefore, be discerning when searching requirement documents for +potential measures; requirements are written for system developers, not +necessarily operational testers.

      Measures should represent something quantifiable or observable.

      • Poor measure: No friendly fighter losses

      • Better measure: Number of friendly fighters destroyed or damaged

      The goal for friendly fighter losses (zero) can be included in the +measure as a threshold used as the basis for an evaluation of acceptable +SUT performance.

      The data satisfying a measure should be observable. Observable data can +be either quantitative (numerical) or qualitative (descriptive). A +measurement can be objective (independently verifiable by 2 or more +people) or subjective (an opinion or perception of an individual).

      • Poor measure: Pilot’s opinion about the aircraft

      • Better measure: Pilot’s rating (on a 5 point scale) of aircraft +maneuverability

      Measures should be clear and concise. Measures should be written in +language that is understandable by someone with a limited knowledge of +the system or CONOPS.

      • Poor measure: Status of enemy fighters

      • Better measure: Percentage of enemy fighters destroyed or rendered +combat ineffective

      Measures sets can evolve as measures are added or deleted due to +insights gained by the test team from test activities. The first measure +sets are developed relatively early in the continuum of AFOTEC +involvement with system development. The test strategy should promote +regular updates, additions, and modifications to the measures sets +throughout the test lifecycle. The next section discusses the AFOTEC +process for measures development.

      \ No newline at end of file diff --git a/sites/oteguide/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT/index.html b/sites/oteguide/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT/index.html new file mode 100644 index 00000000..fcc44c6f --- /dev/null +++ b/sites/oteguide/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT/index.html @@ -0,0 +1,132 @@ +SECTION 2 MEASURES DEVELOPMENT

      SECTION 2 MEASURES DEVELOPMENT

      This section discusses the AFOTEC process for developing MOEs, MOPs, and +MOSs. From the perspective of the pyramid in figure 1, one can think of +developing measures using a top-down or bottom-up approach. The top down +approach is most useful for MOE development since it focuses on the +Mission Effect, and the bottom up approach is effective when developing +MOPs and MOSs since it focuses on the SUT.

      There are opportunities to bring stakeholders together through two +formal meetings, the Initial Test Design (ITD) and the Measures Workshop +(MW), where measures are developed. These meetings are just one type of +venue facilitated by the test team, A-2/9, and A‑3 to develop, refine, +and socialize measures. Major stakeholders in the acquisition program +are invited: the user community, the System Program Office (SPO), DOT&E, +system developers, and developmental testers. All participants apply +their subject matter expertise toward the goal of developing a measure +set and test designs. MOEs are developed at the Initial Test Design +(ITD) meeting, although they may be developed at a Measures Workshop +(MW) if that occurs first. MOPs and MOS are developed at a MW.

      Developing Measures of Effectiveness

      Developing MOEs using the top-down approach is typically done using a +CONOPS document, SUT Evaluation View (developed by AFOTEC/A3), mission +documentation and scenario development, SME inputs, empirical results +from test events, etc. The CONOPS describes the SUT mission, how the +system will be employed, and what effects the user is trying to achieve. +The Evaluation View (EV) describes the necessary conditions and +activities that must be accomplished for the system to provide its +capabilities, contribute to mission accomplishment, and ultimately +support national strategic objectives.

      Using an appropriate combination of the methods above, one can identify +desired and undesired mission effects in the analysis of the system. For +example, target damage from a bomb is a desired effect, while collateral +damage is an undesired effect. It may be appropriate to also include an +operational context for the sake of scope or clarity.

      The definition of mission and mission effect are important in developing +MOEs.

      Mission: 1) The task, together with the purpose, that clearly +indicates the action to be taken and the reason therefore (JP 3-0); 2) +In common usage, especially when applied to lower military units, a duty +assigned to an individual or unit; a task (JP 3-0); 3) The dispatching +of one or more aircraft to accomplish one particular task (JP 3-0).

      Mission Effect: The result, outcome, or consequence of an action, at +its appropriate mission level, typically tactical, represents the +mission effect or outcome. Mission effects are considered within the +context of Concept of Operations / Operational Mode Summary / Mission +Profile/Employment (derived from JP 1-02, Department of Defense +Dictionary of Military and Associated Terms, As amended through 15 Feb +16). Mission effects may include desired and undesired effects.

      An MOE may incorporate both the mission (action taken) and the effect; +for some systems the effect and the action are one in the same.

      • MOE x.y: Recover personnel

      • MOE x.y: Ingress area to reach pick-up point

      • MOE x.y: Maintain aircraft to achieve required availability

      • MOE x.y: Defeat high value advisory targets

      Once we have identified the actions and outcomes of interest for a +system it may be necessary to include additional components in order to +communicate metrics and evaluation criteria. These components will be +included within the measures worksheet but are not necessary to include +within measures summary tables.

      The components of an MOE may include the following (note some +components are optional):

      • The method of summarizing the observed sequence of successes and +failures (e.g., proportion, rate, or probability)

      • A description of the mission effect (outcome) that will be defined +as a success; an optional standard of success can be explicitly +included

      • An optional operational context for the desired mission effect

      • An optional basis for evaluating the observed proportion of +successes and failures

      Figure 2 shows the basic structure of an MOE.

      Figure 2. Components of an MOE

      + + + image8 + +

      Example 1: Desired Mission Effects. Suppose the CONOPS for a +silo-based missile system stated the mission is to provide a safe, +secure, responsive, on-time, and on-target nuclear deterrent force. +Using a top-down approach to MOE development, one MOE is required to +support an assessment that the system delivers a nuclear warhead to the +intended target. Another MOE is required to support an assessment that +the system is responsive to launch commands. Other MOEs may be required, +but two will suffice for this example.

      The following are possible MOEs, and the components of each measure are +color coded to be consistent with figure 2.

      • MOE 1.1: Proportion of adversary high-value strategic targets +defeated meets planning factor

      • MOE 1.2: Proportion of missiles that are launched in defensive +scenario meets OPLAN requirements

      Example 2: Undesired Mission Effects. Tanker aircraft engage in a +variety of missions, but the most common is air refueling of receiver +aircraft. When receiver aircraft are properly refueled and consequently +in a return-to-mission status, a desired effect has been achieved. There +are circumstances, however, in which a tanker boom may cause damage to +receiver aircraft during air refueling; and this damage may create a +risk to mission accomplishment. The following MOE incorporates these +undesired effects into the measure.

      • MOE x.y: Proportion of boom-damaged, mission-compromised aircraft.

      Developing Measures of Performance and Measures of Suitability

      MOPs can be developed using a bottom-up or top-down approach. Using the +bottom-up approach, the test team reviews the available requirement +documents, identified standards, and acquisition documents (ICD/CDD/CPD) +to determine what MOPs are required to evaluate the SUT. These documents +may also provide information about the expected level of reliability, +availability, maintainability, and other logistics aspects related to +SUT employment and sustainment; these suitability issues are used to +develop MOSs. Using the top-down approach, the test team starts with the +MOPs and asks what performance characteristics are most relevant to +mission success.

      It is important for the test team to consider the following when +developing measures:

      • What aspects of SUT performance are important to enabling the +operation or mission?

      • What aspects of employment and sustainment are important to enabling +the mission?

      • How can the desired performance or aspect of suitability be +measured?

      • What is the best way to summarize performance (e.g., average, +percentile, etc.)

      • What degree of performance is required by the user?

      • Does the degree of performance required depend on certain +conditions?

      Common SUT attributes that MOPs typically measure (not all +inclusive):

      • Accuracy

      • Timeliness

      • Completeness

      • Workload

      Common SUT attributes that MOSs typically measure (not all +inclusive):

      • Reliability

      • Availability

      • Maintainability

      • Usability

      Systems may have other attributes that need to be evaluated such as +lethality, interoperability, trainability, etc. The CONOPS, the EV, and +the requirements documents are used to determine the relevant system +attributes to evaluate with measures.

      Example 3: The Joint Biological Agent Decontamination System (JBADS) +is a capability designed to meet Air Mobility Command (AMC) and United +States Transportation Command (USTRANSCOM) needs for decontamination of +aircraft against biological warfare agents (BWA) and other biological +agents of concern.

      MOPs need to be developed for the following COI:

      • COI-2: Can JBADS be assembled and disassembled at deployed +locations?

      There are 2 MOEs:

      • MOE 1: Percentage of correctly assembled JBADS

      • MOE 2: Percentage of correctly disassembled JBADS

      The user community at the MW noted that the timeliness of +assembly/disassembly has operational impact. The CDD stated that the +assembly time should be less than 30 minutes. There was no requirement +for disassembly. The user community noted that in the operational +environment, disassembly time was an important safety and security +issue. The following MOPs were created:

      • MOP 1: Assembly time

      • MOP 2: Disassembly time

      The user community also noted that it is important that the JBADS system +is reliable. The following MOS related to reliability was created:

      • MOS 1: Mean time to failure (MTTF)

      COI-Operations-Measures-Data Hierarchy. The resulting structure of +the COI, MOEs, MOSs and MOPs can be organized in several ways depending +on the type of evaluation methods utilized. Figure 3 depicts some of +possibilities.

      Figure 3. Measure Hierarchies

      + + + image9 + +

      MOEs, MOPs, and MOSs are used synergistically to evaluate the +effectiveness and suitability of a SUT. MOEs directly measure the degree +to which the SUT can achieve mission effects and successfully conduct +operations; MOEs are the primary method of evaluating the question posed +by the COI. Per the DAG, several MOPs and/or MOSs may be related to the +achievement of a particular mission effect. MOPs and MOSs are not +subordinate to the MOEs, nor are they required to calculate the MOEs. +However, MOPs and MOSs are an important part of determining the +effectiveness and suitability of a SUT. MOPs and MOSs indicate specific +strengths and weaknesses of a system, mitigate the statistical issues +associated with the typically small sample size of MOE data, and support +or refute the conclusions drawn from MOE data. The next section +discusses the AFOTEC format for documenting the details of MOEs, MOPs +and MOSs.

      \ No newline at end of file diff --git a/sites/oteguide/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION/index.html b/sites/oteguide/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION/index.html new file mode 100644 index 00000000..aa62e798 --- /dev/null +++ b/sites/oteguide/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION/index.html @@ -0,0 +1,99 @@ +SECTION 3 MEASURE DOCUMENTATION

      SECTION 3 MEASURE DOCUMENTATION

      Measures Worksheet Overview

      The Measures Worksheet is a template used to document and organize the +following details of a measure:

      • Measure: A measure statement that describes what type of data is +being collected

      • Metric(s): The metric used to summarize the data (mean, +percentile, etc.)

      • Threshold (Optional): The threshold of performance used to +evaluate the effectiveness of the SUT

      • Results: The results attributed to observed and calculated data +procured during test execution

      • Rating (Optional): The comparison of Results against the +Threshold, communicating any E&S shortfall

      • Operational Capability: Attribute of the SUT being measured +(MOPs/MOSs only)

      • References: The source document that motivated the creation of +the measure

      • Scope: The scope of the measure

      • Test Methodology: The test methodology used to generate the data

      • Test Design: The test design used to generate the data

      • Data and Analysis: Data that may be required to compute the +measure, formulas required, and the intended method of analysis

      Table 1 shows the measures worksheet template.

      Table 1. Measures Worksheet Template

      Operational Capability: State the OC (attribute)
      MeasureMetricThreshold
      MOE/P/S X.Y: State the Measure (In Title Case)State the specific metricProvide the value/units and any conditions/subsets specified

      * KPP or Supports KPP (include as required)

      ^ Identified Standard (include as required)

      References: Provide the requirement source (stated or derived). Specify the paragraph, section, line, etc.

      Scope: Describe the measure and how it relates to the operation in terms of duration, procedures, start/end times, limitations, etc… If the language in the measure or metric is not self-explanatory or is ambiguous, provide definition(s). For instance, define users, operators, successful or unsuccessful, and linkages to other measures. Concisely discuss operational relevance of the measure.

      Test Methodology: Describe how the data used to support the measure is generated (modeling and simulation, open-air testing, analysis).

      Test Design: Since tests are designed at the operation/COI level, this section will generally refer back to that level with the statement “Uses the overarching operation/COI test design.” However, if unique factors and levels for this measure are identified in the Test Conditions section above, then a separate test design for the measure is required and should be summarized here.

      Data and Analysis: Identify the minimum data required to compute the metric(s). Describe how the data will be collected, the sources of the data, and instrumentation required to collect the data. Provide an overview of the expected analysis method(s), equations, algorithms, and tools necessary for analysis.

      Measures Worksheet Header

      The header of the measures worksheet contains a concise summary of the +most important information regarding a measure. It states the attribute +of the SUT the test team is interested in evaluating (operational +capability), a short title (measure statement) describing what is being +measured that will convey information about the attribute, how it will +be computed (the metric), and what will serve as the basis for judging +the metric (the threshold). Table 2 is an example of the standard format +for the measures worksheet header.

      Table 2. Standard Measures Worksheet Header

      Operational Capability: Accuracy
      MeasureMetricThreshold
      MOP 2.1: Miss DistanceMean≤20 meters

      The header can be expanded to accommodate more detailed requirements. +For instance, a requirement may provide context, such as an operational +condition, for a threshold of performance. The AFOTEC convention is to +denote these specific conditions with the “@” symbol trailing the +threshold and preceding the condition. For example, if the miss distance +for a particular munition is specified for a particular wind speed +(condition), the measure would be as shown in table 3.

      Table 3. Measures Worksheet Header with Conditions

      Operational Capability: Accuracy
      MeasureMetricThreshold
      MOP 2.1: Miss DistanceMean≤20 meters @ 30 knots wind speed

      Sometimes the threshold of the metric changes depending on which +subcomponent or subset of the SUT is being evaluated. In this case the +convention is to add the word “for” after the threshold and specify the +relevant subcomponent or subset. Consider the following requirements.

      • “The system shall send deliver priority 1 messages within 30 +seconds”

      • “The system shall send deliver priority 2 messages within 5 minutes”

      • “The system shall send deliver priority 3 messages within 15 +minutes”

      • “The system shall send deliver priority 4 messages within 1 hour”

      • “The system shall send deliver standard messages within 6 hours”

      Table 4 shows these five requirements can be combined into one measure, +rather than five separate measures.

      Table 4. Measures Worksheet Header with Combined Conditions

      Operational Capability: Timeliness
      MeasureMetricThreshold
      MOP 2.1: Time to Deliver MessagesMean≤30 seconds for Priority 1
      ≤5 minutes for Priority 2
      ≤15 minutes for Priority 3
      ≤1 hour for Priority 4
      ≤6 hours for Standard

      This construct can be extended to create more complex measures that +include multiple metrics, thresholds, conditions, and subsets. Table 5 +is an example of a multi metric/threshold measure.

      Table 5. Measures Worksheet Header with Multi Metric/Threshold

      Operational Capability: Timeliness
      MeasureMetricThreshold
      MOP 2.1: Time to Deliver Messages50th Percentile≤1 minute for Priority 1
      80th Percentile≤8 minutes for all others
      ≤3 minutes @ Wartime for Priority 1
      99th Percentile≤10 minutes for Priority 1
      ≤20 minutes for all others

      Combining thresholds for different conditions and subsets of the SUT has +advantages and disadvantages. One advantage is the reduction in +documentation. One disadvantage is that each measure is rated only once +in a report, even if it has multiple thresholds. Thus if there is a mix +of good and bad results within one measure, the good news, the bad news, +or both may be hidden behind the single summary rating.

      A measure is read aloud in a specific way to accurately convey its +contents. The measure is read: “The <metric> of the +<measure> is <threshold>.” For instance, the measure shown +in table 6 is read: “The mean of the miss distance is

      less than or equal to 20 meters.”

      Table 6. Reading a Measure

      Operational Capability: Accuracy
      MeasureMetricThreshold
      MOP 2.1: Miss DistanceMean≤20 meters

      Body of the Measures Worksheet

      The body of the measures worksheet contains five sections: References; +Scope; Test Methodology; Test Design; Data and Analysis.

      References: Provide the requirement source (stated or derived). +Specify the paragraph, section, line, etc.

      Scope: Describe the measure and how it relates to the operation in +terms of duration, procedures, start/end times, limitations, etc. If the +language in the measure or metric is not self-explanatory or is +ambiguous, provide definitions. For instance, define users, operators, +successful or unsuccessful, and linkages to other measures. Concisely +discuss operational relevance of the measure.

      Test Methodology: Describe how the data used to support the measure +is generated (modeling and simulation, open-air testing, analysis).

      Test Design: Since tests are designed at the operation/COI level, +this section will generally refer back to that level with the statement +“Uses the overarching operation/COI test design.” However, if unique +factors and levels for this measure are identified in the test +conditions section above, then a separate test design for the measure is +required and should be summarized here.

      Data and Analysis: Identify the minimum data required to compute the +metrics. Describe how the data will be collected, the sources of the +data, and instrumentation required to collect the data. Provide an +overview of the expected analysis methods, equations, algorithms, and +tools necessary for analysis.

      Formatting Measures

      The following are formatting conventions for the measures worksheet.

      Measure Statement. Write measures statements in title case, i.e., +use capital letters for all principal words. Articles, conjunctions and +prepositions do not get capital letters unless they start the measure +statement. All acronyms are spelled out in each measure, regardless if +they have been used before in the document; this enables the measures +worksheet, and the header when separated from the full worksheet, to be +comprehensible without other documentation. Table 7 shows a properly +formatted measure statement with acronyms.

      Table 7. Acronym Usage

      Operational Capability: Timeliness
      MeasureMetricThreshold
      MOP 2.4: Electro-Optical (EO) National Imagery Interpretation Rating Scale (NIIRS) RatingMinimum≥ NIIRS 6 @ 450 km

      Key Performance Parameter (KPP): If the measure is derived from a +KPP or supports a KPP, the measure designator is preceded by an asterisk +(*). Additionally, a legend with the text “* KPP or Supports KPP” is +added as another row at the bottom of the measure table, as shown in +table 8.

      Table 8. Identifying a KPP

      Operational Capability: Reliability
      MeasureMetricThreshold
      *MOS 4.1: Time Between FailuresMean≥50 hours
      *KPP or Supports KPP

      Identified Standards: If a test team must develop a measure from a +requirement that fails to provide a clear metric or threshold of +performance, the test team can ask the user community for an appropriate +metric or threshold; this value is known as an identified standard. +There is a convention to highlighting and documenting identified +standards on a measures worksheet. AFOTEC denotes an identified standard +by placing a carrot symbol (^) to the top left of the user-created +metric or threshold. The source of the identified standard must be +explained in the References section of the measures worksheet, which +should start with the phrase “Derived from…”

      Example: The requirement states: “The miss distance shall be less +than or equal to 15 meters.”

      While the measure statement (miss distance) and threshold (less than or +equal to 15 meters) are provided, the requirement does not explicitly +state what the metric should be. The test team consults with the user +and determines the correct metric is circular error probable (CEP). +Since this was not explicitly stated in the requirements document, CEP +is an identified standard and must be annotated with a carrot symbol +(^CEP). Additionally a legend with the text “^ Identified Standard” is +added as another row at the bottom of the measures worksheet header. +Table 9 shows how the additional information is incorporated.

      Table 9. Indicating an Identified Standard

      Operational Capability: Accuracy
      MeasureMetricThreshold
      *MOP 2.1: Miss Distance^ CEP≤ 15 meters
      * KPP or Supports KPP
      ^ Identified Standard

      References: Derived from weapon system subject matter expert (SME) +judgement based on operational experience on legacy systems and +“Technical Requirements Document (TRD): Air Force (AF) Munition X 16 Dec +15, table 14, items 3.1.8 and 5.0.13-5.0.15

      Threshold: If the measure is quantitative or ordinal, the threshold +must be preceded by an equality or inequality mathematical symbol (=, ≤ +or ≥).

      \ No newline at end of file diff --git a/sites/oteguide/fn_guides/measures_guide/index.html b/sites/oteguide/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES/index.html similarity index 58% rename from sites/oteguide/fn_guides/measures_guide/index.html rename to sites/oteguide/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES/index.html index 3c06ecd2..0896ba30 100644 --- a/sites/oteguide/fn_guides/measures_guide/index.html +++ b/sites/oteguide/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES/index.html @@ -1,299 +1,4 @@ -Measures Guide

      Measures Guide

      March 2021

      Last Updated/Reviewed: 25 March 2021

      Originating Office: AFOTEC A-2/9

      INTRODUCTION

      Measurement is central to conducting operational test and evaluation -(OT&E). This technical guide supplements the “AFOTEC OT&E Guide” and -provides AFOTEC personnel the necessary background and specific -directions on how to write and develop measures. The first section is a -general overview of the fundamentals of measurement. Section 2 describes -how AFOTEC develops measures. Sections 3 provides details of measure -documentation. Appendix A provides examples of the types of continuous -and discrete measures. Appendix B provides checklists to ensure measures -are properly written. Appendix C discusses AFOTEC’s process for writing -cyber measures.

      Submit suggested changes to: AFOTEC.A2A9.Workflow@us.af.mil

      SECTION 1 FUNDAMENTALS OF MEASUREMENT

      Measures Overview

      Test measures are the basis of the evaluation of a system under test -(SUT); they are the data used to assess effectiveness and suitability -and serve as evidence of system deficiencies. Operational effectiveness -and operational suitability are defined as follows:

      • Operational Effectiveness – The overall degree of mission -accomplishment of a system when used by representative personnel in -the environment planned or expected for operational employment

      • Operational Suitability – The degree to which a system can be -satisfactorily placed into field use. Examples of issues evaluated -under operational suitability:

        • Reliability, maintainability, availability

        • Compatibility and interoperability

        • Supportability

        • Transportability

        • Human factors

        • Training requirements

      There are three general types of measures developed for Operational Test -(OT): Measures of effectiveness (MOE), Measures of Performance (MOP), -and Measures of Suitability (MOS). MOEs provide direct evidence that a -user can successfully employ the SUT to accomplish a mission. MOEs can -be used to evaluate the system as soon as it is feasible to test the -system in an operational environment.

      • Measure of Effectiveness (MOE) - Measures designed to -assess the degree to which the SUT can accomplish mission objectives -and achieve desired mission effects. If appropriate, they may -quantify success as a proportion of successful test events, rate of -success, or the probability that the system will achieve some -result.

      MOPs and MOSs can be used to evaluate the system throughout development -and OT&E. Capabilities and functions of a system are evaluated using -both MOPs and MOSs. The supportability and sustainability of a system is -evaluated using MOSs.

      • Measures of Performance (MOP) - Measure a system’s -capabilities. They may quantify performance such as speed, payload, -range, time-on-station, frequency, rating or other distinctly -observable and/or quantifiable performance features. They may also -document whether or not a system can successfully complete a task. -Finally, MOPs may document user ratings of system attributes.

      • Measures of Suitability (MOS) - Measure of the ability to -support the SUT in its intended operational environment. MOSs -typically relate to readiness or supportability and hence include -measures concerning reliability, availability, maintainability, the -quality of system documentation, the quality of training, and the -SUT logistics infrastructure.

      All three types of measures (MOE, MOP, and MOS) are used by the test -team to determine if a system can accomplish a mission, which is stated -as a Critical Operational Issue (COI). For example, the C-130J has two -primary missions: conduct tactical airlift and conduct airdrop -operations. The following are two of the COIs from the C-130J test -program; note that the convention is to phrase COIs in the form of a -question.

      • COI 1: Can the SUT conduct tactical airlift

      • COI 2: Can the C-130J conduct airdrop operations

      When developing measures for a SUT, it is useful to visualize the system -as having four layers that may require measurement and assessment: -Mission Effects, System Capabilities, System Functions and Properties, -and System Structure. Figure 1-1 depicts these four levels in a pyramid -and provides definitions.

      Figure 1. The Pyramid: Evaluation Levels of a SUT

      - - - image7 - -

      Measures can be used to evaluate the SUT at each level of the pyramid. -MOEs are used to evaluate mission effects, while MOPs and MOSs are -typically used to evaluate system capabilities, system functions and -properties, and system structure.

      Qualities of a Good Measure Set

      The following are qualities of a good measures set:

      • Measures should be operationally relevant, necessary, and sufficient

      • Measures should represent something quantifiable or observable, not -a goal or objective

      • The data satisfying a measure should be observable, or at least -inferable

      • Measures should be clear and concise

      Measures should be operationally relevant, necessary, and sufficient. -Measures should only be included in a data set if they provide -significant support to one of three goals: delivering combat capability, -discovering system deficiencies, and evaluating the effectiveness and -suitability of the SUT. Measures required by engineers during system -development may not be relevant to AFOTEC testers.

      Avoid the trap of writing too many measures. The resources required to -collect data for measures varies, but at a minimum every measure -requires the time and attention—limited resources—of a data collector. -Therefore, be discerning when searching requirement documents for -potential measures; requirements are written for system developers, not -necessarily operational testers.

      Measures should represent something quantifiable or observable.

      • Poor measure: No friendly fighter losses

      • Better measure: Number of friendly fighters destroyed or damaged

      The goal for friendly fighter losses (zero) can be included in the -measure as a threshold used as the basis for an evaluation of acceptable -SUT performance.

      The data satisfying a measure should be observable. Observable data can -be either quantitative (numerical) or qualitative (descriptive). A -measurement can be objective (independently verifiable by 2 or more -people) or subjective (an opinion or perception of an individual).

      • Poor measure: Pilot’s opinion about the aircraft

      • Better measure: Pilot’s rating (on a 5 point scale) of aircraft -maneuverability

      Measures should be clear and concise. Measures should be written in -language that is understandable by someone with a limited knowledge of -the system or CONOPS.

      • Poor measure: Status of enemy fighters

      • Better measure: Percentage of enemy fighters destroyed or rendered -combat ineffective

      Measures sets can evolve as measures are added or deleted due to -insights gained by the test team from test activities. The first measure -sets are developed relatively early in the continuum of AFOTEC -involvement with system development. The test strategy should promote -regular updates, additions, and modifications to the measures sets -throughout the test lifecycle. The next section discusses the AFOTEC -process for measures development.

      SECTION 2 MEASURES DEVELOPMENT

      This section discusses the AFOTEC process for developing MOEs, MOPs, and -MOSs. From the perspective of the pyramid in figure 1, one can think of -developing measures using a top-down or bottom-up approach. The top down -approach is most useful for MOE development since it focuses on the -Mission Effect, and the bottom up approach is effective when developing -MOPs and MOSs since it focuses on the SUT.

      There are opportunities to bring stakeholders together through two -formal meetings, the Initial Test Design (ITD) and the Measures Workshop -(MW), where measures are developed. These meetings are just one type of -venue facilitated by the test team, A-2/9, and A‑3 to develop, refine, -and socialize measures. Major stakeholders in the acquisition program -are invited: the user community, the System Program Office (SPO), DOT&E, -system developers, and developmental testers. All participants apply -their subject matter expertise toward the goal of developing a measure -set and test designs. MOEs are developed at the Initial Test Design -(ITD) meeting, although they may be developed at a Measures Workshop -(MW) if that occurs first. MOPs and MOS are developed at a MW.

      Developing MOEs

      Developing MOEs using the top-down approach is typically done using a -CONOPS document, SUT Evaluation View (developed by AFOTEC/A3), mission -documentation and scenario development, SME inputs, empirical results -from test events, etc. The CONOPS describes the SUT mission, how the -system will be employed, and what effects the user is trying to achieve. -The Evaluation View (EV) describes the necessary conditions and -activities that must be accomplished for the system to provide its -capabilities, contribute to mission accomplishment, and ultimately -support national strategic objectives.

      Using an appropriate combination of the methods above, one can identify -desired and undesired mission effects in the analysis of the system. For -example, target damage from a bomb is a desired effect, while collateral -damage is an undesired effect. It may be appropriate to also include an -operational context for the sake of scope or clarity.

      The definition of mission and mission effect are important in developing -MOEs.

      Mission: 1) The task, together with the purpose, that clearly -indicates the action to be taken and the reason therefore (JP 3-0); 2) -In common usage, especially when applied to lower military units, a duty -assigned to an individual or unit; a task (JP 3-0); 3) The dispatching -of one or more aircraft to accomplish one particular task (JP 3-0).

      Mission Effect: The result, outcome, or consequence of an action, at -its appropriate mission level, typically tactical, represents the -mission effect or outcome. Mission effects are considered within the -context of Concept of Operations / Operational Mode Summary / Mission -Profile/Employment (derived from JP 1-02, Department of Defense -Dictionary of Military and Associated Terms, As amended through 15 Feb -16). Mission effects may include desired and undesired effects.

      An MOE may incorporate both the mission (action taken) and the effect; -for some systems the effect and the action are one in the same.

      • MOE x.y: Recover personnel

      • MOE x.y: Ingress area to reach pick-up point

      • MOE x.y: Maintain aircraft to achieve required availability

      • MOE x.y: Defeat high value advisory targets

      Once we have identified the actions and outcomes of interest for a -system it may be necessary to include additional components in order to -communicate metrics and evaluation criteria. These components will be -included within the measures worksheet but are not necessary to include -within measures summary tables.

      The components of an MOE may include the following (note some -components are optional):

      • The method of summarizing the observed sequence of successes and -failures (e.g., proportion, rate, or probability)

      • A description of the mission effect (outcome) that will be defined -as a success; an optional standard of success can be explicitly -included

      • An optional operational context for the desired mission effect

      • An optional basis for evaluating the observed proportion of -successes and failures

      Figure 2 shows the basic structure of an MOE.

      Figure 2. Components of an MOE

      - - - image8 - -

      Example 1: Desired Mission Effects. Suppose the CONOPS for a -silo-based missile system stated the mission is to provide a safe, -secure, responsive, on-time, and on-target nuclear deterrent force. -Using a top-down approach to MOE development, one MOE is required to -support an assessment that the system delivers a nuclear warhead to the -intended target. Another MOE is required to support an assessment that -the system is responsive to launch commands. Other MOEs may be required, -but two will suffice for this example.

      The following are possible MOEs, and the components of each measure are -color coded to be consistent with figure 2.

      • MOE 1.1: Proportion of adversary high-value strategic targets -defeated meets planning factor

      • MOE 1.2: Proportion of missiles that are launched in defensive -scenario meets OPLAN requirements

      Example 2: Undesired Mission Effects. Tanker aircraft engage in a -variety of missions, but the most common is air refueling of receiver -aircraft. When receiver aircraft are properly refueled and consequently -in a return-to-mission status, a desired effect has been achieved. There -are circumstances, however, in which a tanker boom may cause damage to -receiver aircraft during air refueling; and this damage may create a -risk to mission accomplishment. The following MOE incorporates these -undesired effects into the measure.

      • MOE x.y: Proportion of boom-damaged, mission-compromised aircraft.

      Developing MOPs and MOSs

      MOPs can be developed using a bottom-up or top-down approach. Using the -bottom-up approach, the test team reviews the available requirement -documents, identified standards, and acquisition documents (ICD/CDD/CPD) -to determine what MOPs are required to evaluate the SUT. These documents -may also provide information about the expected level of reliability, -availability, maintainability, and other logistics aspects related to -SUT employment and sustainment; these suitability issues are used to -develop MOSs. Using the top-down approach, the test team starts with the -MOPs and asks what performance characteristics are most relevant to -mission success.

      It is important for the test team to consider the following when -developing measures:

      • What aspects of SUT performance are important to enabling the -operation or mission?

      • What aspects of employment and sustainment are important to enabling -the mission?

      • How can the desired performance or aspect of suitability be -measured?

      • What is the best way to summarize performance (e.g., average, -percentile, etc.)

      • What degree of performance is required by the user?

      • Does the degree of performance required depend on certain -conditions?

      Common SUT attributes that MOPs typically measure (not all -inclusive):

      • Accuracy

      • Timeliness

      • Completeness

      • Workload

      Common SUT attributes that MOSs typically measure (not all -inclusive):

      • Reliability

      • Availability

      • Maintainability

      • Usability

      Systems may have other attributes that need to be evaluated such as -lethality, interoperability, trainability, etc. The CONOPS, the EV, and -the requirements documents are used to determine the relevant system -attributes to evaluate with measures.

      Example 3: The Joint Biological Agent Decontamination System (JBADS) -is a capability designed to meet Air Mobility Command (AMC) and United -States Transportation Command (USTRANSCOM) needs for decontamination of -aircraft against biological warfare agents (BWA) and other biological -agents of concern.

      MOPs need to be developed for the following COI:

      • COI-2: Can JBADS be assembled and disassembled at deployed -locations?

      There are 2 MOEs:

      • MOE 1: Percentage of correctly assembled JBADS

      • MOE 2: Percentage of correctly disassembled JBADS

      The user community at the MW noted that the timeliness of -assembly/disassembly has operational impact. The CDD stated that the -assembly time should be less than 30 minutes. There was no requirement -for disassembly. The user community noted that in the operational -environment, disassembly time was an important safety and security -issue. The following MOPs were created:

      • MOP 1: Assembly time

      • MOP 2: Disassembly time

      The user community also noted that it is important that the JBADS system -is reliable. The following MOS related to reliability was created:

      • MOS 1: Mean time to failure (MTTF)

      COI-Operations-Measures-Data Hierarchy. The resulting structure of -the COI, MOEs, MOSs and MOPs can be organized in several ways depending -on the type of evaluation methods utilized. Figure 3 depicts some of -possibilities.

      Figure 3. Measure Hierarchies

      - - - image9 - -

      MOEs, MOPs, and MOSs are used synergistically to evaluate the -effectiveness and suitability of a SUT. MOEs directly measure the degree -to which the SUT can achieve mission effects and successfully conduct -operations; MOEs are the primary method of evaluating the question posed -by the COI. Per the DAG, several MOPs and/or MOSs may be related to the -achievement of a particular mission effect. MOPs and MOSs are not -subordinate to the MOEs, nor are they required to calculate the MOEs. -However, MOPs and MOSs are an important part of determining the -effectiveness and suitability of a SUT. MOPs and MOSs indicate specific -strengths and weaknesses of a system, mitigate the statistical issues -associated with the typically small sample size of MOE data, and support -or refute the conclusions drawn from MOE data. The next section -discusses the AFOTEC format for documenting the details of MOEs, MOPs -and MOSs.

      SECTION 3 MEASURE DOCUMENTATION

      Measures Worksheet Overview

      The Measures Worksheet is a template used to document and organize the -following details of a measure:

      • Measure: A measure statement that describes what type of data is -being collected

      • Metric(s): The metric used to summarize the data (mean, -percentile, etc.)

      • Threshold (Optional): The threshold of performance used to -evaluate the effectiveness of the SUT

      • Results: The results attributed to observed and calculated data -procured during test execution

      • Rating (Optional): The comparison of Results against the -Threshold, communicating any E&S shortfall

      • Operational Capability: Attribute of the SUT being measured -(MOPs/MOSs only)

      • References: The source document that motivated the creation of -the measure

      • Scope: The scope of the measure

      • Test Methodology: The test methodology used to generate the data

      • Test Design: The test design used to generate the data

      • Data and Analysis: Data that may be required to compute the -measure, formulas required, and the intended method of analysis

      Table 1 shows the measures worksheet template.

      Table 1. Measures Worksheet Template

      Operational Capability: State the OC (attribute)
      MeasureMetricThreshold
      MOE/P/S X.Y: State the Measure (In Title Case)State the specific metricProvide the value/units and any conditions/subsets specified

      * KPP or Supports KPP (include as required)

      ^ Identified Standard (include as required)

      References: Provide the requirement source (stated or derived). Specify the paragraph, section, line, etc.

      Scope: Describe the measure and how it relates to the operation in terms of duration, procedures, start/end times, limitations, etc… If the language in the measure or metric is not self-explanatory or is ambiguous, provide definition(s). For instance, define users, operators, successful or unsuccessful, and linkages to other measures. Concisely discuss operational relevance of the measure.

      Test Methodology: Describe how the data used to support the measure is generated (modeling and simulation, open-air testing, analysis).

      Test Design: Since tests are designed at the operation/COI level, this section will generally refer back to that level with the statement “Uses the overarching operation/COI test design.” However, if unique factors and levels for this measure are identified in the Test Conditions section above, then a separate test design for the measure is required and should be summarized here.

      Data and Analysis: Identify the minimum data required to compute the metric(s). Describe how the data will be collected, the sources of the data, and instrumentation required to collect the data. Provide an overview of the expected analysis method(s), equations, algorithms, and tools necessary for analysis.

      Measures Worksheet Header

      The header of the measures worksheet contains a concise summary of the -most important information regarding a measure. It states the attribute -of the SUT the test team is interested in evaluating (operational -capability), a short title (measure statement) describing what is being -measured that will convey information about the attribute, how it will -be computed (the metric), and what will serve as the basis for judging -the metric (the threshold). Table 2 is an example of the standard format -for the measures worksheet header.

      Table 2. Standard Measures Worksheet Header

      Operational Capability: Accuracy
      MeasureMetricThreshold
      MOP 2.1: Miss DistanceMean≤20 meters

      The header can be expanded to accommodate more detailed requirements. -For instance, a requirement may provide context, such as an operational -condition, for a threshold of performance. The AFOTEC convention is to -denote these specific conditions with the “@” symbol trailing the -threshold and preceding the condition. For example, if the miss distance -for a particular munition is specified for a particular wind speed -(condition), the measure would be as shown in table 3.

      Table 3. Measures Worksheet Header with Conditions

      Operational Capability: Accuracy
      MeasureMetricThreshold
      MOP 2.1: Miss DistanceMean≤20 meters @ 30 knots wind speed

      Sometimes the threshold of the metric changes depending on which -subcomponent or subset of the SUT is being evaluated. In this case the -convention is to add the word “for” after the threshold and specify the -relevant subcomponent or subset. Consider the following requirements.

      • “The system shall send deliver priority 1 messages within 30 -seconds”

      • “The system shall send deliver priority 2 messages within 5 minutes”

      • “The system shall send deliver priority 3 messages within 15 -minutes”

      • “The system shall send deliver priority 4 messages within 1 hour”

      • “The system shall send deliver standard messages within 6 hours”

      Table 4 shows these five requirements can be combined into one measure, -rather than five separate measures.

      Table 4. Measures Worksheet Header with Combined Conditions

      Operational Capability: Timeliness
      MeasureMetricThreshold
      MOP 2.1: Time to Deliver MessagesMean≤30 seconds for Priority 1
      ≤5 minutes for Priority 2
      ≤15 minutes for Priority 3
      ≤1 hour for Priority 4
      ≤6 hours for Standard

      This construct can be extended to create more complex measures that -include multiple metrics, thresholds, conditions, and subsets. Table 5 -is an example of a multi metric/threshold measure.

      Table 5. Measures Worksheet Header with Multi Metric/Threshold

      Operational Capability: Timeliness
      MeasureMetricThreshold
      MOP 2.1: Time to Deliver Messages50th Percentile≤1 minute for Priority 1
      80th Percentile≤8 minutes for all others
      ≤3 minutes @ Wartime for Priority 1
      99th Percentile≤10 minutes for Priority 1
      ≤20 minutes for all others

      Combining thresholds for different conditions and subsets of the SUT has -advantages and disadvantages. One advantage is the reduction in -documentation. One disadvantage is that each measure is rated only once -in a report, even if it has multiple thresholds. Thus if there is a mix -of good and bad results within one measure, the good news, the bad news, -or both may be hidden behind the single summary rating.

      A measure is read aloud in a specific way to accurately convey its -contents. The measure is read: “The <metric> of the -<measure> is <threshold>.” For instance, the measure shown -in table 6 is read: “The mean of the miss distance is

      less than or equal to 20 meters.”

      Table 6. Reading a Measure

      Operational Capability: Accuracy
      MeasureMetricThreshold
      MOP 2.1: Miss DistanceMean≤20 meters

      Body of the Measures Worksheet

      The body of the measures worksheet contains five sections: References; -Scope; Test Methodology; Test Design; Data and Analysis.

      References: Provide the requirement source (stated or derived). -Specify the paragraph, section, line, etc.

      Scope: Describe the measure and how it relates to the operation in -terms of duration, procedures, start/end times, limitations, etc. If the -language in the measure or metric is not self-explanatory or is -ambiguous, provide definitions. For instance, define users, operators, -successful or unsuccessful, and linkages to other measures. Concisely -discuss operational relevance of the measure.

      Test Methodology: Describe how the data used to support the measure -is generated (modeling and simulation, open-air testing, analysis).

      Test Design: Since tests are designed at the operation/COI level, -this section will generally refer back to that level with the statement -“Uses the overarching operation/COI test design.” However, if unique -factors and levels for this measure are identified in the test -conditions section above, then a separate test design for the measure is -required and should be summarized here.

      Data and Analysis: Identify the minimum data required to compute the -metrics. Describe how the data will be collected, the sources of the -data, and instrumentation required to collect the data. Provide an -overview of the expected analysis methods, equations, algorithms, and -tools necessary for analysis.

      Formatting Measures

      The following are formatting conventions for the measures worksheet.

      Measure Statement. Write measures statements in title case, i.e., -use capital letters for all principal words. Articles, conjunctions and -prepositions do not get capital letters unless they start the measure -statement. All acronyms are spelled out in each measure, regardless if -they have been used before in the document; this enables the measures -worksheet, and the header when separated from the full worksheet, to be -comprehensible without other documentation. Table 7 shows a properly -formatted measure statement with acronyms.

      Table 7. Acronym Usage

      Operational Capability: Timeliness
      MeasureMetricThreshold
      MOP 2.4: Electro-Optical (EO) National Imagery Interpretation Rating Scale (NIIRS) RatingMinimum≥ NIIRS 6 @ 450 km

      Key Performance Parameter (KPP): If the measure is derived from a -KPP or supports a KPP, the measure designator is preceded by an asterisk -(*). Additionally, a legend with the text “* KPP or Supports KPP” is -added as another row at the bottom of the measure table, as shown in -table 8.

      Table 8. Identifying a KPP

      Operational Capability: Reliability
      MeasureMetricThreshold
      *MOS 4.1: Time Between FailuresMean≥50 hours
      *KPP or Supports KPP

      Identified Standards: If a test team must develop a measure from a -requirement that fails to provide a clear metric or threshold of -performance, the test team can ask the user community for an appropriate -metric or threshold; this value is known as an identified standard. -There is a convention to highlighting and documenting identified -standards on a measures worksheet. AFOTEC denotes an identified standard -by placing a carrot symbol (^) to the top left of the user-created -metric or threshold. The source of the identified standard must be -explained in the References section of the measures worksheet, which -should start with the phrase “Derived from…”

      Example: The requirement states: “The miss distance shall be less -than or equal to 15 meters.”

      While the measure statement (miss distance) and threshold (less than or -equal to 15 meters) are provided, the requirement does not explicitly -state what the metric should be. The test team consults with the user -and determines the correct metric is circular error probable (CEP). -Since this was not explicitly stated in the requirements document, CEP -is an identified standard and must be annotated with a carrot symbol -(^CEP). Additionally a legend with the text “^ Identified Standard” is -added as another row at the bottom of the measures worksheet header. -Table 9 shows how the additional information is incorporated.

      Table 9. Indicating an Identified Standard

      Operational Capability: Accuracy
      MeasureMetricThreshold
      *MOP 2.1: Miss Distance^ CEP≤ 15 meters
      * KPP or Supports KPP
      ^ Identified Standard

      References: Derived from weapon system subject matter expert (SME) -judgement based on operational experience on legacy systems and -“Technical Requirements Document (TRD): Air Force (AF) Munition X 16 Dec -15, table 14, items 3.1.8 and 5.0.13-5.0.15

      Threshold: If the measure is quantitative or ordinal, the threshold -must be preceded by an equality or inequality mathematical symbol (=, ≤ -or ≥).

      APPENDIX A CATEGORIES OF MEASURES

      The primary goal of creating a well-written measure is to maximize the +APPENDIX A CATEGORIES OF MEASURES

      APPENDIX A CATEGORIES OF MEASURES

      The primary goal of creating a well-written measure is to maximize the amount and quality of information obtained and to communicate the purpose of a measure as effectively as possible. There are two different categories of measures used in AFOTEC testing: continuous, and discrete. @@ -304,7 +9,7 @@ the system under test.

      image10 -

      Continuous Measures

      Quantitative measures with data collected objectively tend to be the +

      Continuous Measures

      Quantitative measures with data collected objectively tend to be the most informative and easiest to substantiate because they enable broader statistical applications. This is because they often have the property of being continuous, where the resulting measure and metric have an @@ -430,7 +135,7 @@ Second, since probability is the metric for the measure, the cells below the headers for “Metric” and “Threshold” are merged (while maintaining the header cells) and the threshold is entered with the appropriate inequality (≥, ≤) and a value between 0 and 1. The examples in tables -A-8 and A-9 are typical probability measures.

      Table A-8. Probability Measure 1

      Operational Capability: Availability
      MeasureMetricThreshold
      MOS 4.2: Probability of Operational Availability (Ao)≥0.90

      Table A-9. Probability Measure 2

      Operational Capability: Lethality
      MeasureMetricThreshold
      MOE 1.5: Probability of Kill (PK)≥0.95
      AFOTEC Keys to Probability Measures

      Writing:

      • Is the threshold a value between 0 and 1?

      • Does the threshold include an inequality, either ≥ or ≤?

      • Are the metric and threshold cells merged?

      • Does the measure name include the phrase “Probability of”?

      Planning for Analysis:

      • Is the sample size sufficient to determine a probability with a reasonable confidence interval?

      • Is a probability meaningful for the operational scenario?

      Discrete Measures

      Discrete measures are those where the measure and metric have a finite +A-8 and A-9 are typical probability measures.

      Table A-8. Probability Measure 1

      Operational Capability: Availability
      MeasureMetricThreshold
      MOS 4.2: Probability of Operational Availability (Ao)≥0.90

      Table A-9. Probability Measure 2

      Operational Capability: Lethality
      MeasureMetricThreshold
      MOE 1.5: Probability of Kill (PK)≥0.95
      AFOTEC Keys to Probability Measures

      Writing:

      • Is the threshold a value between 0 and 1?

      • Does the threshold include an inequality, either ≥ or ≤?

      • Are the metric and threshold cells merged?

      • Does the measure name include the phrase “Probability of”?

      Planning for Analysis:

      • Is the sample size sufficient to determine a probability with a reasonable confidence interval?

      • Is a probability meaningful for the operational scenario?

      Discrete Measures

      Discrete measures are those where the measure and metric have a finite number of possible values and can only take specific values in a range. Discrete measures are typically counted in whole numbers. For example, suppose a requirement states that the number of C-17s required to deploy @@ -781,7 +486,7 @@ described in this section. Further discussion of cyber measures and examples can be found in Appendix C.

      The AFOTEC Questionnaire Guide provides a complete description of how to analyze and report rating measures and should be consulted by the test team. In addition, the test team should contact A-2/9 with any -questions or concerns on analyzing or reporting information.

      AFOTEC Keys to Rating Measures

      Writing:

      • Is the measure written to evaluate some attribute of the human interaction with the system?

      • Is the correct format used for the specific attribute the measure is concerned with?

      • Is the “user” clearly defined in the measure title and/or Scope section of the worksheet?

      • The measure title should never start with “Test Team Rating of…”

        • Test team judgement is already accounted for in the AFOTEC rating taxonomy

      • Are the Metric and Threshold cells merged, while maintaining the header cells?

      • Is the criteria statement formatted correctly?

      • Should the criteria statement be preceded with the identified standard symbol (^)?

      • Does the measure follow one of the pitfalls described in the ratings measures Section?

        • Measure should not be a “Catch-all” or used to “Cover all the bases”

        • Measure should not attempt to evaluate something that can be answered with objectively collected quantitative data

        • Measure should not be so broad as to evaluate the entire system or COI

        • Measure should not attempt to roll up other measures in the measure set

      Planning for Analysis:

      • Are there any additional data elements that can be added to aid in the evaluation of the measure?

      • Plan to look for a convergence or harmony of responses when evaluating these types of measures.

      Composite Measures

      While a traditional measure evaluates a single attribute of a system, a +questions or concerns on analyzing or reporting information.

      AFOTEC Keys to Rating Measures

      Writing:

      • Is the measure written to evaluate some attribute of the human interaction with the system?

      • Is the correct format used for the specific attribute the measure is concerned with?

      • Is the “user” clearly defined in the measure title and/or Scope section of the worksheet?

      • The measure title should never start with “Test Team Rating of…”

        • Test team judgement is already accounted for in the AFOTEC rating taxonomy

      • Are the Metric and Threshold cells merged, while maintaining the header cells?

      • Is the criteria statement formatted correctly?

      • Should the criteria statement be preceded with the identified standard symbol (^)?

      • Does the measure follow one of the pitfalls described in the ratings measures Section?

        • Measure should not be a “Catch-all” or used to “Cover all the bases”

        • Measure should not attempt to evaluate something that can be answered with objectively collected quantitative data

        • Measure should not be so broad as to evaluate the entire system or COI

        • Measure should not attempt to roll up other measures in the measure set

      Planning for Analysis:

      • Are there any additional data elements that can be added to aid in the evaluation of the measure?

      • Plan to look for a convergence or harmony of responses when evaluating these types of measures.

      Composite Measures

      While a traditional measure evaluates a single attribute of a system, a composite measure is a single evaluation of multiple attributes of a system. In industry, these types of measures are called indexes, ratings, compound or complex measures. Some well-known examples include @@ -896,321 +601,7 @@ team observations, reported operational impacts, ARO evidence-based ratings, ARO workload ratings, selected video and audio data, and interview data converge in the same, positive direction (i.e., triangulation of data sets). If strict convergence is not met, the MOP -will be resolved according to the preponderance of the total evidence.

      APPENDIX B MEASURE REVIEW QUICK REFERENCE

      AFOTEC Keys to Mean Measures

      Writing:

      • Does the threshold include an inequality, either ≥ or ≤?

      • Does the threshold include the units of measure?

      Example:

      • ???

      Planning for Analysis:

      • Keep in mind that the arithmetic mean can be sensitive to every value in the data set, including extremes. This effect is especially noticeable when the sample size is small.

      AFOTEC Keys to Error Probable Measures

      Writing:

      • Does the threshold include an inequality, either ≥ or ≤?

      • Does the threshold include the units of measure?

      • Does the metric include the probability?

      Example:

      • ???

      Planning for Analysis:

      • Are the underlying assumptions about the metric realistic for the operational scenario?

      AFOTEC Keys to Percentile Measures

      Writing:

      • Does the threshold include an inequality, either ≥ or ≤?

      • Does the threshold include the units of measure?

      • Does the metric include the percentile value (not just the word “Percentile”)

      Example:

      • ???

      Planning for Analysis:

      • Is a percentile applicable to the requirement or is there another metric more appropriate?

      • Does the team intend to report the percentile of the empirical data or of a fitted distribution?

      • Is the sample size sufficient for a percentile to be meaningful?

      AFOTEC Keys to Probability Measures

      Writing:

      • Is the threshold a value between 0 and 1?

      • Does the threshold include an inequality, either ≥ or ≤?

      • Are the metric and threshold cells merged?

      • Does the measure name include the phrase “Probability of”?

      Example:

      • ???

      Planning for Analysis:

      • Is the sample size sufficient to determine a probability with a reasonable confidence interval?

      • Is a probability meaningful for the operational scenario?

      AFOTEC Keys to Continuous Minimum/Maximum Measures

      Writing:

      • Does the threshold include an inequality or equal sign, either ≥, ≤ or =?

      • Is the sign appropriate for the metric (“≤” for a Maximum, “≥” for a Minimum, or an equals sign “=” in certain cases)?

      • Is the metric spelled out completely (no “Min” or “Max”)?

      Example:

      • ???

      Planning for Analysis:

      • Is a minimum/maximum metric operationally relevant?

      AFOTEC Keys to Discrete Minimum/Maximum Measures

      Writing:

      • Does the threshold include an inequality or equal sign, either ≥, ≤ or =?

      • Is the sign appropriate for the metric (“≤” for a Maximum, “≥” for a Minimum, or an equals sign “=” in certain cases)?

      • Is the metric spelled out completely (no “Min” or “Max”)?

      Example:

      • ???

      Planning for Analysis:

      • Is a minimum/maximum metric/threshold operationally relevant?

      • Can the measure be made continuous?

      AFOTEC Keys to Proportion Measures

      Writing:

      • Does the measure clearly express a relationship between the “whole” and the “part”?

      • Is the “whole” listed first and the “part” listed second?

      • Are the words “that are” used to convey the relationship?

      • Are both parts of the relationship clearly and concisely expressed with no double meaning?

      • Are the words “out of” used to convey the relationship in the threshold?

      • Alternatively a division symbol can be used (3/5)

      Example:

      • ???

      Planning for Analysis:

      • Can the measure be made continuous?

      • Does the expected sample size support the decision to use a proportion metric?

      • Do not report proportion measure results in decimal form alone. If the requirement is given in a decimal or percentage, report the result as a proportion and annotate the decimal/percentage notation for comparison to the threshold of the requirement.

      • Do not report results in vague quantitative terms such as “a majority of targets were correctly identified.” Always include the actual quantitative values.

      AFOTEC Keys to Percentage Measures

      Writing:

      • Does the measure clearly express a relationship between the “whole” and the “part”?

      • Is the “whole” listed first and the “part” listed second?

      • Are the words “that are” used to convey the relationship?

      • Are both parts of the relationship clearly and concisely expressed with no double meaning?

      • Does the threshold include an inequality or equal sign, either ≥ or ≤?

      Planning for Analysis:

      • Is there a continuous threshold hidden in the requirement that can used to convert the Percentage measure into a continuous Percentile measure?

      • Can a continuous identified standard be determined for the requirement?

      • Does the expected sample size support the decision to use a percentage metric?

      • Do not report results in vague quantitative terms such as “a majority of targets were correctly identified.” Always include the actual quantitative values.

      AFOTEC Keys to Rating Measures

      Writing:

      • Is the measure written to evaluate some attribute of the human interaction with the system?

      • Is the correct format used for the specific attribute the measure is concerned with?

      • Is the “user” clearly defined in the measure title and/or Scope section of the worksheet?

      • The measure title should never start with “Test Team Rating of…”

      • Test team judgement is already accounted for in the AFOTEC rating taxonomy

      • Are the Metric and Threshold cells merged, while maintaining the header cells?

      • Is the criteria statement formatted correctly?

      • Should the criteria statement be preceded with the identified standard symbol (^)?

      • Does the measure follow one of the pitfalls described in the Ratings measures Section?

      • Measure should not be a “Catch-all” or used to “Cover all the bases”

      • Measure should not attempt to evaluate something that can be answered with objectively collected quantitative data

      • Measure should not be so broad as to evaluate the entire system or COI

      • Measure should not attempt to roll up other measures in the measure set

      Planning for Analysis:

      • Are there any additional data elements that can be added to aid in the evaluation of the measure?

      • Plan to look for a convergence or harmony of responses when evaluating these types of measures.

      APPENDIX C CYBER-RELATED MEASURES

      [1]

      Cybersecurity T&E is used to describe the activities that encompass all -cybersecurity test and evaluation activities, including vulnerability -assessments, security controls testing, penetration testing, adversarial -testing, and cybersecurity testing related to a system’s operational -resilience and system cyber survivability capabilities within a mission -context.[2]

      AFOTEC considers cyber survivability, resiliency and security critical -mission enabling capabilities of a system under test (SUT). So the -expectation is that these capabilities will be fully integrated and -comprehensively tested components of every test program. AFOTEC A-2/9, -A-3I, and Detachment analysts will ensure that cyber-related measures -are developed for each program as necessary.

      Usage note: the focus of this appendix is on how to write a -cyber-related measure—refer to the AFOTEC Cyber Test Guide (CTG) for how -to rate and score cyber-related measures using operationally relevant -data.

      Measures Overview

      Test measures are the basis of the evaluation of a system under test -(SUT). They drive the data needs, collection, and analysis used to -evaluate effectiveness and suitability and serve as evidence of -capability performance and mission effects. There are three general -types of measures developed for Operational Test (OT):

      • Measures of Effectiveness (MOE) - Measures designed to assess -the degree to which the system under test can accomplish mission -objectives and achieve desired mission effects.

      • Measures of Performance (MOP) - Measure a system’s capabilities. -They may quantify performance such as speed, payload, range, -time-on-station, frequency, rating, or other distinctly observable -and/or quantifiable performance features. They may also document -whether or not a system can successfully complete a task.

      • Measures of Suitability (MOS) - Measure of the ability to -support the system under test in its intended operational -environment. MOSs typically relate to readiness, supportability, -logistics infrastructure and cost of ownership of the SUT.

      Composite Measures

      Composite measures aggregate and summarize data from multiple -attributes. The multidimensional nature and complexity of cyber-related -testing make adoption of composite measures very beneficial. A composite -measure facilitates evaluation of multiple attributes of the SUT by -consolidating results into a single score.

      To prevent deceptively obtuse and irrelevant results, it is critical -that all attribute measurements contributing to a composite measure be -well defined. Additionally, the test team’s evaluation and aggregation -strategy should be thoroughly documented in each of the composite -measure worksheets and be credible and supportable.

      Clarity, transparency, and accountability are required from all -stakeholders in composite cyber-related measures development and -documentation, as evidenced in the associated measures worksheets, to -better reduce distinct quality measures into a single summary indicator.

      See the main body of the AFOTEC Measures Guide for a complete -description and guidance on Composite Measures. See COI-4 Stand Alone -COI Construct ESC Example where they are used to aggregate effects of -operating within a cyber-contested environment for COIs 1, 2 and 3.

      Cyber-Related Measures. Capabilities and functions of a system are -evaluated using both MOPs and MOSs. When developing cyber-related -measures for a SUT, it is useful to visualize the system as having four -layers that may require measurement and assessment: Mission Effects, -System Capabilities, System Functions and Properties, and System -Structure. Figure C-1 depicts these four levels in a pyramid and how -they could relate to cyber-related measures.

      Figure C-1. The Pyramid—Evaluation Levels of a SUT

      - - - image13 - -

      The Confidentiality, Integrity, and Availability (CIA) triad and the -Prevent, Mitigate, and Recover (PMR) constructs are useful in mapping -cyber to the four layers in the pyramid. The CIA triad can be thought of -as the desired effects akin to Mission Effects for a system that enables -or performs cyber defense operations, while the attributes associated -with the PMR construct can be thought of as enabling the CIA effects and -akin to System Capabilities, System Functions and Properties, and System -Structure. Therefore, the CIA triad leads to cyber-related MOEs, since -they look at achieving desired effects. The PMR attributes lead to -cyber-related MOPs/MOSs, since they address required system -capabilities, functions, characteristics, and logistics. This guide -should act as a guideline for measures evaluating cybersecurity, cyber -survivability and cyber resiliency of a system can take any of the three -measure forms (MOE, MOP, and MOS).

      Cyber related considerations for OT&E COI Design Constructs. AFOTEC -typically uses one of three different COI design constructs for planning -and reporting cyber-related effects as part of the overall OT&E. The -appropriate COI design construct is typically determined/developed when -building the OT&E Construct. The choice of the COI construct for cyber -has an impact on the selection of MOEs, MOPs, and MOSs and where they -are placed in the COI construct. The three COI constructs are designated -as Integrated, Stand-Alone, and Hybrid. Descriptions of the -cyber-related COI design constructs follow with examples of evaluation -summary charts (ESC) for each.

      Integrated Construct. For integrated constructs (commonly referred -to as traditional or Ops-based), the test team covers cyber effects -within the measures under each operational COIs.

      Cyber operational conditions, cyber threats, and cyber-related measures -are addressed within the context of each mission or operations-based COI -(wherever cyber can affect operational outcome). Cyber-related MOPs/MOSs -cover all attributes associated with PMR and the ten CSAs (cyber -survivability attributes). This COI construct also allows for -cyber-related MOE’s addressing CIA to be outlined separately across the -operational COIs, if needed.

      Using the integrated COI construct, identified/ notable cyber-related -issues that extend beyond the SUT (i.e., do not affect the degree of -mission accomplishment of the SUT or the ability to place in field use) -may be addressed in an annex to the OT&E report, if warranted. Figure -C-2 shows an ESC example for the Integrated COI Construct.

      Figure C-2. Integrated COI Construct ESC Example

      - - - image14 - -

      Stand-Alone Construct. In the stand-alone COI construct, a -separate Cyber COI unifies and/or compartmentalizes the impacts to -mission and/or operations of the SUT when employed within a -cyber-contested environment. This COI construct allows the baselining of -uncontested performance in a cyber benign environment, as compared to -performance of the SUT in a cyber-contested environment. All -cyber-contested operational conditions, threats, measures, and test -events are addressed within the separate cyber COI. The separate cyber -COI captures all cyber survivability, cyber resiliency and -cybersecurity-related measures. These cyber-related measures cover all -attributes associated with CIA, PMR, and the ten CSAs.

      Composite Measures (COI 4 in Figure C-3) are used to collect and -aggregate the effects of a cyber-contested environment on measures from -the operational COIs. There should be a composite measure for each of -the operational COIs. Additional cyber-specific measures address the -system’s cyber operational capabilities.

      Figure C-3. Stand Alone COI Construct ESC Example

      - - - image15 - -

      Hybrid Construct. The Hybrid COI construct applies elements of -both the Integrated and Stand-Alone COI constructs. Similar to the -Integrated COI construct, cyber effects are addressed within the -operations-based COIs. Additionally, a separate cyber COI is created to -allow the test team to focus on capturing non-disruptive and/or indirect -cyber effects or the underlying/common cyber aspects across the system.

      Cyber operational conditions, cyber threats, cyber-related measures, and -cyber test events are addressed within the context of the operational -COIs. The separate cyber COI is functionally focused (i.e., cyber -related operational capabilities) and also addresses effects not seen -within the missions or operational COIs (e.g., indirect effects, 2nd/3rd -order effects, exfiltration). The separate cyber COI may also be used to -expand cyber reporting beyond the SUT, if warranted. Figure C-4 shows an -example ESC for the Hybrid COI construct.

      Figure C-4. Hybrid Construct ESC Example

      - - - image16 - -

      Measures Development. Regardless of what COI construct is selected, -test teams must develop measures addressing cyber survivability, cyber -resiliency, and cybersecurity for their SUTs.

      The selection of the COI construct (and development of MOEs) is -accomplished as part of the OT&E Construct. At the Measures Workshop -MOEs are refined, and MOSs and MOPs are developed. The TD, Detachment -cyber analysts, the detachment test team, cyber test subject matter -experts (SME) from A-3I, and analysts from A-2/9 collaborate on -developing system-specific, mission-centric cyber-related measures.

      Developing quantitative and observable qualitative operationally -relevant measures is a complex challenge that requires careful -collaboration with all stakeholders. As teams develop measures to suit -specific systems under test, the cyber teams develop cyber-related -measures that address and evaluate: effects, capabilities, -attributes, and characteristics that contribute to the SUT’s -degree of cyber survivability, cyber resiliency and cybersecurity.

      Cyber survivability, resiliency and security can be represented with the -CIA triad of effects and the PMR associated attributes. A cyber-related -measure addressing CIA effects and/or PMR related attributes may be -included, or CIA effects and/or PMR related attributes may be aggregated -into composite measures. Table C-1 contains definitions for CIA. Table -C-2 contains definitions for PMR and CSA’s. Note: if a separate cyber -COI is employed the test team must still address PMR and CIA.

      Table C-1. CIA Defined[3]

      CIAConfidentialityPreserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information.
      IntegrityGuarding against improper information modification or destruction and ensuring information non-repudiation and authenticity.
      Data IntegrityThe property that data has not been altered in an unauthorized manner. Data integrity covers data in storage, during processing, and while in transit.
      System IntegrityThe quality that a system has when it performs its intended function in an unimpaired manner, free from unauthorized manipulation of the system, whether intentional or accidental.
      AvailabilityEnsuring timely and reliable access to and use of information.

      Table C-2. System Survivability (SS) Key Performance Parameter (KPP) -Pillars[4] Defined and Mapped to their Cyber Survivability Attributes -(CSA)

      SS KPPDescriptionCyber Survivability Attribute
      PMRPreventDesign principles and operations that enable or provide protection of the systems mission functions from most likely cyber threatsCSA-01 – Control AccessCSA-10 – Actively Manage System Configurations to Counter Vulnerabilities at Tactically Relevant Speeds
      CSA-02 – Reduce System’s Cyber Detectability
      CSA-03 – Secure Transmissions and Communications
      CSA-04 – Protect System’s Information from Exploitation
      CSA-05 – Partition and Ensure Critical Functions at Mission Completion Performance Levels
      CSA-06 – Minimize and Harden Attack Surfaces
      MitigateDesign principles and operations that enable or provide detection and responding to cyber-attacks, enabling the system to survive, operate in a degraded environment, and complete the missionCSA-07 – Baseline & Monitor Systems and Detect Anomalies
      CSA-08 – Manage System Performance if Degraded by Cyber Events
      RecoverDesign principles and operations that enable or provide recovery from cyber-attacks and prepare mission systems for the next fightCSA-09 – Recover System Capabilities

      The goal of measures development is to produce operationally relevant -quantitative and qualitative measures. Each system is examined to -determine whether additional operationally relevant measures need to be -applied. Keep in mind that the structure and placement of cyber-related -measures will depend on choice of the COI construct (Integrated, -Stand-Alone, or Hybrid) made during the initial OT&E construct (ITD) -meeting.

      Cyber-Related Measures Rating Options. The Cyber-related Measures -Appendix is not intended to detail or specify how to rate cyber -measures. Refer to the AFOTEC Cyber Test Guide for guidance on how to -score measures using operationally relevant data. The options presented -in the tables and figures that follow are provided to help cyber -analysts look ahead to how measures are rated, while developing the -measures.

      One needs to establish an expected result for each operationally -relevant measure. Rating of each measure will be based on the degree to -which test results meet expectations and requirements.

      Measure Rating: Tier Set Option. The following Cyber Tier Set Rating -Scale is the first option provided to help influence cyber-related -measures development. Tables C-3 and C-4 show examples of tier sets, -threshold levels, ratings and their descriptions for measures addressing -cyber survivability.

      Detachment cyber analysts have the autonomy to modify input for best -practice and with locally approved language that is defensible. Consider -these to simply be a menu of AFOTEC approved tier sets and approaches.

      Table C-3. Ratings for Cyber-Related Measures for Cyber Survivability

      Tier SetThreshold LevelRatingRating Description
      SecurityVHighly EffectiveActs that bypass security policies, practices, or procedures are rapidly detected, cleaned and prevented from happening again. They do not degrade mission effects.
      IVEffectiveSecurity breaches have minimal impact to System Capabilities, System Functions and Properties, but no degradation of Mission Effects.
      IIIAppears to be adequateSecurity breaches impact System Capabilities, System Functions and Properties, or System Structure, and minimally degrade Mission Effects.
      IIMinimal with breachesSecurity breaches impact System Capabilities, System Functions and Properties, or System Structure, and significantly degrade Mission Effects.
      INoneThere are no security policies, practices, or procedures in place to prevent breaches. This leads to no mission accomplishment.
      Proactive ProtectionVProtectedSystem-wide protection has proactive processes in identifying and mitigating disruptions. System is alert to new disruptions and puts corrective measures in place immediately.
      IVProtection measures in placeSystem has many protective measures in place. It is not totally proactive in its corrective action. However, it is able to identify problems and react appropriately and swiftly to ensure mission accomplishment.
      IIISome system-wide protection availableSystem has elementary protection measures. Primary mode of correction is reactionary to disruptions. Little time is available to be proactive. Although impacted, some system-wide protection remains.
      IIMinimal, isolated protectionNo system-wide protection in place. Disruptions circumvent any protection measures attempted. Fixes turn out to be temporary in addressing symptoms and not causes.
      INo protectionSystem has little or no protection at all.
      Vigilance (Detection)VMaintains awareness of new vulnerabilitiesSystem enables operators/defenders to maintain awareness of all known vulnerabilities, actively researches and identifies potentials for new vulnerabilities, and is able to project vulnerabilities that result from new technology development.
      IVAble to react to new vulnerabilitiesSystem enables operators/defenders to address all known sources of disruption and/or vulnerabilities. The ability to address the surfacing of new sources of disruption and/or vulnerabilities is a reactive, but effective, process.
      IIIAble to mitigate most vulnerabilitiesSystem enables operators/defenders to identify existing vulnerabilities, mitigate most major vulnerabilities and react to disruptions. Although impacted, some awareness of attacks remains.
      IINot able to address new vulnerabilitiesSystem enables operators/defenders to have a basic understanding of vulnerabilities and has cursory awareness of them. Provides no ability to address new vulnerabilities ahead of disruptions.
      IUnaware of vulnerabilitiesSystem’s design specification provides no consideration for detection of abnormal/malicious activity.
      Mitigations (Response)VSuccessful in mitigating or avoiding all known attacksAll known attacks did not affect operational availability of accurate data or lead to the unauthorized disclosure of data. System was able to tolerate and mitigate and continue operations as normal.
      IVSuccessful in mitigating or avoiding most attacksAttacks are present, but do not affect successful completion of mission. Specific actions need to be taken; however, they are successful in mitigating any effects.
      IIISome proactive measures in placeAttacks are serious and cannot be ignored. More reactive than proactive measures are necessary. Many consequences of attacks are unexpected. Although impacted, some protective measures/capabilities remain.
      IIReactive measures takenAttacks are critical to the system operation and mission accomplishment. The reactive measures do not handle all of the attacks.
      INo measures availableAttacks are catastrophic and result in system shutdown.
      RecoveryVImmediate RecoveryThe system is able to recover after attacks immediately such that there is no critical or non-critical mission impact.
      IVRapid RecoveryThere is observable downtime after an attack, but the system is able to recover before a critical mission impact occurs (non-critical mission impacts may occur).
      IIITimely RecoveryThere is minimal impact to critical mission after an attack due to downtime.
      IICan Recover EventuallySignificant effort is required to recover after an attack resulting in severe mission impact.
      IUnrecoverableThe system is completely unrecoverable after an attack.

      Continuity of Operations

      (Transfer and Continue Ops)

      VMaximumSystem successfully transfers full functionality. System remains highly capable of completing the mission.
      IVAble to operate effectivelySystem is able to transfer functionality required to meet most mission requirements. System may experience some minor problems, but effectively accomplishes the mission.
      IIIMeeting minimum requirementsSystem is able to transfer only minimal functionality. System is struggling, but meets minimum mission requirements.
      IIFailingTransfer is unable to meet most mission requirements. Delays and/or the lack of functionality are a distraction to the mission.
      IComplete breakdownSystem is unable to transfer functionality, and is unable to continue operations.
      Normal OperationsVFull capabilities onlineSystem is highly capable of completing the mission. System is running all subsystems, processes and applications with no problems. System-wide protection has proactive processes in identifying and mitigating disruptions. System confidence is high.
      IVMaintains normal operations, reaches new equilibriumSystem experiences some minor problems but effectively accomplishes the mission. System is running normal operations; however, it is continuously adjusting for disruptions. System has many protective measures in place. System confidence is adequate.
      IIIStruggles to stay ahead of problemsSystem is struggling to meet mission requirements. Subsystems, processes and applications are occasionally failing. System has elementary protection measures. System confidence is moderate illustrating concern over mission accomplishment and integrity of the system. Although impacted, minimum mission accomplishment continues.
      IIExperiencing outages, delays and blackoutsSystem cannot meet most mission requirements, is impacted by problems, and cannot keep up with mitigating actions. System is spending more time addressing disruptions than accomplishing the mission. No system-wide protection is in place. Low confidence that the system can be counted on to do the mission.
      ISystem failureSystem cannot meet mission requirements. System crashes or is near to crashing under the weight of disruptions. System has little or no protection at all. No confidence that the system can be counted on to do the mission.

      Table C-4. Ratings and Descriptions for PMR and Associated CSAs

      Tier SetThreshold LevelRatingRating Description
      Prevent, Mitigate, Recover, and/or All-EncompassingVExceeds Capability StandardGoes above and beyond the CSRC associated required capability standard to ensure the most secure cyber posture possible.
      IVMeets Capability StandardMeets the CSRC associated required capability standard for effective cyber-security.
      IIApproaches Capability StandardCSRC associated required capability standard is not met, however the system is close to achieving the standard.
      IIFails Capability StandardCSRC associated required capability standard is not close to being met and the system needs significant improvement in its cyber posture.
      IEntirely Fails Capability StandardSystem has no cybersecurity capability whatsoever and lacks even the most basic components to pass the CSRC associated required capability standard.

      Measure Rating: Tier Threshold to Mission Impact Heat Chart Option. -The following scale is the second menu option provided to help influence -cyber-related measures development. Here cyber-related impacts to the -mission correlate to tier thresholds and the mission of the SUT through -the use of a heat chart. Tables C-5 and C-6 contain risk based scales to -influence cyber-related measures development.

      Table C-5. Tier Threshold to Mission Impact Comparison Heat Chart

      Tier Threshold
      IIIIIIIVV
      Impact4CatastrophicHighHighHighMediumMedium
      3MajorHighHighMediumMediumLow
      2ModerateHighMediumMediumLowLow
      1NegligibleMediumLowLowLowLow

      Table C-6. Mission Impact Descriptions

      LevelImpactDescription
      1NegligibleLittle to no mission degradation
      2ModeratePartial mission degradation
      3MajorCritical mission degradation
      4CatastrophicComplete mission failure

      Measure Rating: Cyber Survivability Risk Category (CSRC) Heat Chart -Option. In this option the SUT’s assigned CSRC will drive selection of -the required/expected metric and threshold for each cyber-related -measure. Definitions of the CSRCs and a description of the process used -to select the appropriate CSRC for a SUT can be found in the JCS Cyber -Survivability Endorsement Implementation Guide (CSEIG), Version 1.01. In -general, The CSRC is determined from a combination of the SUT’s Mission -Type (MT), Cyber Dependence Level (CDL), Adversary Threat Tier (ATT), -and Impact of System Compromise (IL). Levels vary from 1 through 4. -Their associated required capability standards are detailed in Table -C-7.

      Table C-7. Tiers and Descriptions of Associated Capability Standards

      TierDescription of Capability Standards (Tiers)
      VVery High: Mitigations rely on best available countermeasures, to include custom DoD protections, commensurate against assumed threat capabilities.
      IVHigh: Mitigations include Enhanced Assurance – redundancy, TTPs, and strong COTS/GOTS securely configured in layered architectures – with DoD added technology, as needed.
      IIIModerate: Mitigations include COTS/GOTS cybersecurity products and technologies, with potential DoD technology additions, with best practices, strong DoD layered defenses, and selective use of DoD technology.
      IILow: Mitigations include COTS with best practices if commercially hosted, or strong DoD layered defenses, possible use of DoD technology if DoD hosted
      IPoor: Mitigations do not exists or are totally ineffective

      Similar to the tier rating scale, a heat chart could also be used in -conjunction with the program’s assigned CSRC. After determination of the -associated CSRC Level, a correlation to a low, medium, or high (e.g., -green, yellow, red) reporting standard can easily be mapped against the -tier threshold (Table C-8).

      Table C-8. Tier Threshold to CSRC Comparison Heat Chart

      Tier Threshold
      I (Poor)II (Low)III (Moderate)IV (High)V (Very High)
      CSRC Level4HighHighHighMediumMedium
      3HighHighMediumMediumLow
      2HighMediumMediumLowLow
      1HighLowLowLowLow

      Examples of Cyber-related Measures. In general, it is up to the -detachment and test team to determine the appropriate format for their -SUT’s cyber-related COI programs cybersecurity construct and associated -measures.

      What follows are two example cyber-related measures. This section is not -meant to be an all-inclusive list of cyber-related measures. Nor is it -intended to be a checklist, or a cut-and-paste template. Rather, this -section is intended to demonstrate acceptable cyber-related measures and -what should be included in a cyber-related measure worksheet. Test teams -are encouraged to develop and use variations of these cyber-related -measures (or new cyber-related measures) in order to best suit the needs -of their individual SUTs.

      The cyber-related measures in the Measures Summary (Tables C-9 and C-10) -and the Cyber-related Measure Worksheets (Tables C-11 thru C-14) are -examples of how to evaluate the cyber risk to a system for the separate -Cyber COI in the “Stand Alone” or “Hybrid” COI Construct. They use a -kind of behaviorally anchored rating scale (i.e., tiers and heat charts) -to identify the levels of effectiveness and performance. These anchors -can be tailored to a particular system or test program and ideally would -be defined such that they are observable, measureable and independently -verifiable (i.e., via an inter-observer agreement).

      Table C-9. Example of a Separate Cyber COI, Tier Based
      -Cyber-related Measures Summary Table

      MeasureTier SetMetricThreshold Level
      *MOE 4.1: Rating of NG DRAGON’s Confidentiality of Data and System Information (C)ConfidentialityMinimum^ ≥ Tier IV
      *MOE 4.2: Rating of NG DRAGON’s Integrity of Data and System (I)IntegrityMinimum^ ≥ Tier IV
      *MOE 4.3: Rating of NG DRAGON’s Availability of Data and System (A)AvailabilityMinimum^ ≥ Tier IV
      *MOP 1: Rating of NG Dragon’s Capabilities, Functions, Properties, and Structure Enabling Operational Users and Service Providers Management of Cybersecurity Risk to Systems, Assets, Data, and CapabilitiesSecurityMinimum^ ≥ Tier IV
      *MOP 2: Rating of NG DRAGON’s Physical Security / Protection Against Physical ThreatsSecurityMinimum^ ≥ Tier IV
      *MOP 3: Rating of NG DRAGON’s Detection of Abnormal/Malicious ActivityVigilanceMinimum^ ≥ Tier IV
      *MOP 4: Rating of NG DRAGON’s Response to Abnormal / Malicious Activity Without Degrading Capabilities (Incident Response)MitigationsMinimum^ ≥ Tier IV
      *MOP 5: Rating of NG DRAGON’s Restoring Sustained, Operationally Acceptable Capabilities after Abnormal/Malicious Activity (Mission Restoration)RecoveryMinimum^ ≥ Tier IV
      *MOP 6: Rating of NG DRAGON’s Capability to Recover Operationally Acceptable Data after Abnormal/Malicious Activity (Data Recovery)RecoveryMinimum^ ≥ Tier IV
      *MOP 7: Rating of NG DRAGON’s Transfer of Mission, Continuity of Operations after Abnormal/Malicious ActivityCOOPMinimum^ ≥ Tier IV
      MOP 8: Rating of NG DRAGON’s Capabilities, Functions, Properties, and Structure Enabling Depot Maintenance Planning in a Contested Cyber EnvironmentNormal OperationsMinimum^ ≥ Tier IV
      MOP 9: Rating of NG DRAGON’s Capabilities, Functions, Properties, and Structure Enabling Depot Maintenance Scheduling in a Contested Cyber EnvironmentNormal OperationsMinimum^ ≥ Tier IV
      MOP 10: Rating of NG DRAGON’s Capabilities, Functions, Properties, and Structure Enabling Depot Maintenance Execution in a Disruptive Cyber EnvironmentNormal OperationsMinimum^ ≥ Tier IV
      MOP 11: Rating of NG DRAGON Providing Enterprise Standardization and Visibility in a Disruptive Cyber EnvironmentNormal OperationsMinimum^ ≥ Tier IV
      MOS 1: Rating of NG DRAGON’s Capabilities, Functions, Properties, and Structure Enabling it to be Maintained (Maintainability) in a Disruptive Cyber EnvironmentNormal OperationsMinimum^ ≥ Tier IV
      MOS 2: Rating of NG DRAGON’s Capabilities, Functions, Properties, and Structure Enabling it to be Supported (Supportability) in a Disruptive Cyber EnvironmentNormal OperationsMinimum^ ≥ Tier IV
      MOS 3: Rating of NG DRAGON’s Capabilities, Functions, Properties, and Structure Enabling it to Operate Within The Operational Infrastructure in a Disruptive Cyber EnvironmentNormal OperationsMinimum^ ≥ Tier IV
      *MOP 12: Instances when NG DRAGON Does Not Process (Input/Output) Critical IERsMaximum^ Zero
      *MOP 13: Non-Critical IER Exchanges that Process Successfully (Input/Output) on the First TryPercentage^ ≥ 90%
      MOS 4: Rating of the Supply Chain Management (HW/SW) of NG DRAGONSecurityMinimum^ ≥ Tier IV
      MOP 14: Rating of the Configuration Control of NG DRAGONSecurityMinimum^ ≥ Tier IV
      MOS 5: Rating of Awareness Training for the Users of NG DRAGONProtectionMinimum^ ≥ Tier IV
      MOP 15: Rating of the Security of NG DRAGON’s Architecture/NetworkProtectionMinimum^ ≥ Tier IV
      MOP 16: Rating of the Software Security of NG DRAGONSecurityMinimum^ ≥ Tier IV
      MOP 17: Rating of the Boundary Protection (External Protection) of NG DRAGONProtectionMinimum^ ≥ Tier IV
      MOP 18: Rating of the Access Management (Internal Protection) of NG DRAGONProtectionMinimum^ ≥ Tier IV
      MOP 19: Rating of Situational Awareness (Indications and Warnings) of NG DRAGONVigilanceMinimum^ ≥ Tier IV
      * KPP or Supports KPP
      ^ AFOTEC Identified Standard (i.e., not specified in requirement documents)

      Table C-10. Example - Cyber-related Measures and
      -Cyber Survivability Tier Threshold Summary

      MeasureTier SetVIVIIIIII
      *MOE 4.1ConfidentialityVery HighHighModerateLowPoor
      *MOE 4.2IntegrityVery HighHighModerateLowPoor
      *MOE 4.3AvailabilityVery HighHighModerateLowPoor

      *MOP 1

      *MOP 2

      MOS 4

      MOP 16

      MOP 18

      SecurityHighly EffectiveEffectiveAppears to be adequateMinimal with breachesNone

      MOS 5

      MOP 15

      MOP 17

      MOP 18

      ProtectionProtectedProtection measures in placeSome system-wide protection availableMinimal, isolated protectionNo protection

      *MOP 3

      MOP 19

      VigilanceMaintains awareness of new vulnerabilitiesAble to react to new vulnerabilitiesAble to mitigate most vulnerabilitiesNot able to address new vulnerabilitiesUnaware of vulnerabilities
      *MOP 4MitigationsAttacks have little or no effect on operationsSuccessful in mitigating or avoiding most attacksSome proactive measures in placeReactive measures takenNo measures available
      *MOP 7COOPMaximumAble to operate effectivelyMeeting minimum requirementsFailingComplete breakdown

      *MOP 5

      *MOP 6

      RecoveryImmediate recoveryRapid recoveryTimely recoveryCan recover eventuallyUnrecoverable

      MOP 8

      MOP 9

      MOP 10

      MOP 11

      MOS 1

      MOS 2

      MOS 3

      Normal OperationsFull capabilities onlineMaintains normal operations, reaches new equilibriumStruggles to stay ahead of problemsExperiencing outages, delays, and blackoutsSystem failure
      *KPP or Supports KPP

      Table C-11. AFOTEC Tier Based Cyber-Related Measure Worksheet Example

      (See the main body of this guide for template and content -requirements)

      Operational Capability: Cybersecurity
      MeasureMetricThresholdResultsRating
      *MOE 4.2: Rating of NG DRAGON’s Integrity of Data and SystemsMinimum^ ≥ Tier IVTBDTBD
      * KPP or Supports KPP
      ^ Identified Standard

      References: Provide the requirement source (stated or derived). -Specify the paragraph, section, line, etc. This is part of the -example and references could be out of date.

      Derived from DOT&E Memo, 3 Apr 18, Procedures for Operational Test and -Evaluation of Cybersecurity in Acquisition Programs; Department of -Defense (DoD) 8510.01, Risk Management Framework (RMF) for Department of -Defense (DoD) Information Technology (IT), 12 Mar 14; National Institute -of Standards and Technology (NIST) Special Publication (SP) 800-53, -Security and Privacy Controls for Federal Information Systems and -Organizations, Rev. 4, 30 Apr 13.

      Scope: This cyber-related measure addresses the degree NG DRAGON’s -PMR capabilities, functions, and structure enable or provide data and -system integrity. Data integrity is the property that data has not been -altered in an unauthorized manner while in storage, during processing, -or while in transit. System integrity is the quality that a system has -when performing the intended function in an unimpaired manner, free from -unauthorized manipulation. This measure will also consider what “impact -adversary and unauthorized modification or destruction of system -information” has on “functions to the mission” (“CSE Implementation -Guide Version 1.01”, pg. 17). This measure evaluates the following -protection metrics:

      • Account Management

      • Least Privilege

      • Identification and Authentication

      • Continuous Monitoring

      • Device Identification and Authentication

      • Authenticator Management

      • Default Authenticators

      • Physical Access Control

      • Boundary Protection

      • Secure Network Communications

      • Update Management

      • Malicious Code Prevention

      Test Methodology: The test team will coordinate with Blue & Red -Teams to conduct the Cooperative Vulnerability and Penetration -Assessment (CVPA) and the Adversarial Assessment (AA) respectively. The -test team will review documentation, observe the system, and conduct the -CVPA and AA during system use by operational users in a realistic -operational environment, as described in the overarching COI 4 test -methodology. The test team will identify, verify, and attempt to exploit -vulnerabilities in the NG DRAGON system in accordance with identified -DOT&E cybersecurity test requirements. They will leverage -vulnerabilities highlighted in prior risk assessments, system audit -reports, vulnerability and penetration team findings, and direct -observation of the application of the cybersecurity controls. It is -assumed that the AA will disrupt and/or even deny operations, therefore -effectiveness and suitability test data must be collected prior to -cyber-attack. The CVPA and the AA are expected to last approximately 2 -weeks each.

      Test Design: Uses overarching COI 4 test design.

      Data and Analysis: The test team will compare system protection -information to requirements set forth in various laws, doctrine, and -policies. For each instance where the SUT is unable to provide the -integrity of data or the system, the test team will assess the -corresponding mission impact using a simple scale (High, Medium, Low, or -equivalent), operational experience, and judgment to rate the measure -against the identified standard (Integrity tier sets). The mission -impact scale will be related to RMF categorization for integrity. In the -event that exploitation of a vulnerability is precluded due to critical -mission requirements or safety concerns, the test team will estimate -mission impact based on technical expertise, operational experience, and -relevant operational subject matter expert input.

      The test team will present cybersecurity control findings and aggregated -results in the final report. Each control will be assigned a rating -(Met, Partially Met, Not Met, or Not Applicable) presented in table -format. Cybersecurity findings will be detailed in the report narrative, -to include associated recommendations for risk mitigation, vulnerability -reduction, and TTP modification. The number of users interviewed, the -overall trend of responses from interviews, and highlight comments and -observations concerning the cybersecurity posture will also be included -in the report. The test team will log and bin the total number of -illicit attempts according to their category level. They will also log -the total number of attempts, in conjunction with illicit attempts that -were defended successfully. Manual and automated intrusion methods will -be delineated and logged. The “time to achieve access” will be -calculated via the delta between the initial attempt to access and when -access is achieved. The “time to achieve elevated access” will be -calculated via the delta between access and acquisition of an elevated -privilege. The report will include a description of the exploitation -method and maneuver. SME analysis will categorize tool sophistication as -either Novice or Advanced. The overall integrity protection rating will -be based on a combination of the number of instances and each instance’s -impact to the mission.

      Table C-12. Example of an AFOTEC Risk Based Cyber-Related Measure -Worksheet

      Operational Capability: Cybersecurity
      MeasureMetricThresholdResultsRating
      MOP 1.1: Risk to Joint OH Data (JOD) Communications in the AOR Due to Cyber Effects^ Low riskTBDTBD
      ^ Identified Standard

      References: Provide the requirement source (stated or derived). -Specify the paragraph, section, line, etc. The following is part of -the example and references could be out of date.

      Derived from DOT&E Memo. 3 Apr 18, Procedures for Operational Test and -Evaluation (OT&E) of Cybersecurity in Acquisition Programs; DOT&E Memo, -27 Jul 16, Cybersecurity Operational Test and Evaluation Priorities and -Improvements; DoD Cybersecurity T&E Guidebook, Version 2.0 Change 1, 10 -Feb 2020; AFOTEC Cyber Test Guide, XX Dec 2020

      Scope: This measure evaluates the risk to JOD’s ability to enable -secure and survivable communications in a contested cyberspace -environment. The risk must be “low”. The test team will determine the -risk rating by evaluation the likelihood of an adversary exploiting -vulnerabilities and the resulting impact to EPS’ ability to enable -secure and survivable communications in a contested cyberspace -environment.

      Test Methodology: The test team mapped the mission of JOD to mission -essential functions and the components which support their operation. -This nodal analysis will allow the test team to identify critical nodes -within JOD. Using this information the test team will commission the -346TS to conduct a cooperative vulnerability and penetration assessment -(CVPA) before integrated test activities (IT). The test team will -commission the 177 IAS, an NSA certified cyber red team, to conduct an -adversarial assessment (AA) during IT and OT.

      The test team will evaluate the risk of cyber-effects to JOD’s ability -to enable secure and survivable communications in a contested cyberspace -environment as follows:

      Table C-13. Example of an AFOTEC Risk Based Cyber-Related Measure -Worksheet

      Likelihood
      54321
      Near CertainHighMediumLowNegligible
      Impact4CatastrophicHighHighHigh RiskMediumMedium
      3MajorHighHighMediumMediumLow
      2ModerateHighMediumMediumLowLow
      1NegligibleMediumLowLowLowLow

      Table C-14

      LevelLikelihoodDescription
      1NegligibleLittle to no capability for adversary to exploit
      2LowHigh cost for adversary to exploit
      3MediumMedium cost for adversary to exploit
      4HighLow cost for adversary to exploit
      5Near CertainLittle to no cost for adversary to exploit
      LevelImpactDescription
      1NegligibleLittle to no mission degradation
      2ModeratePartial mission degradation
      3MajorCritical mission degradation
      4CatastrophicComplete mission failure

      Test Design: Uses overarching COI test design.

      Data and Analysis: Data will consist of results from the Mission -Risk Assessment Process for Cyber (MRAP-C), the CVPA, and AA. During -test execution, the test team will also collect performance data for all -measures within COI.

      The test team will record all data on test team logs and will store all -results in the appropriately classified test team OT&E database. Where -unable to collect quantitative data, the test team will collect end user -and SME qualitative data. The test team will collect data according to -each measure within COI 1. The test team will note periods of time when -cyber-effects were generated by the AA team. After test execution, the -test team will evaluate the impacts of disruptive and non-disruptive -cyber-effects to each measure within COI 1. The test team will consult -with AFOTEC A-2 to determine the likelihood of the demonstrated and -speculated cyber-effects from the AA. The test team will then provide a -risk rating of each effect. Using each risk rating as input, the test -team will then provide the overall risk rating to this measure.

      [1] Cyber test and evaluation is a rapidly evolving concept. Be sure to -reference the most current guidance as it may change more frequently -than this AFOTEC Measures Guide.

      [2] DoD Cybersecurity Test and Evaluation Guidebook, Version 2.0, Change -1, 10 Feb 20

      [3] NIST SP 800-12, “An Introduction to Information Security,” Rev. 1, -Jun 17

      [4] System Survivability Key Performance Parameter (SS KPP) Pillars are -defined in the JCS Cyber Survivability Endorsement Implementation Guide, -Version 1.01

      \ No newline at end of file diff --git a/sites/oteguide/fn_guides/accreditation_guide/index.html b/sites/oteguide/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES/index.html similarity index 57% rename from sites/oteguide/fn_guides/accreditation_guide/index.html rename to sites/oteguide/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES/index.html index a150e0e0..925f45f1 100644 --- a/sites/oteguide/fn_guides/accreditation_guide/index.html +++ b/sites/oteguide/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES/index.html @@ -1,371 +1,318 @@ -Accreditation Guide

      Accreditation Guide

      08 December 2020

      Originating Office: AFOTEC A-2/9

      INTRODUCTION

      The AFOTEC Accreditation Guide provides actionable information for test -directors (TD), analysts, engineers, and program managers on how best to -plan, execute, and report accreditation of modeling and simulation (M&S) -systems. The accreditation process involves:

      • Developing an executable plan, assessment, and report with focus on -documenting the results of the accreditation assessment

      • Documenting the recommendations in support of the accreditation -decision, and

      • Documenting lessons learned during accreditation

      Accreditation is applicable when a test capability is used directly or -indirectly to provide information that appears in an operational test -(OT) final report. If a TD intends -to draw weapon system capability conclusions (i.e., rate measures) based -upon the use of a test capability, accreditation is required. AFOTEC -accreditation policy exists to ensure standardization across test teams -and a consistent level of rigor in determining adequacy of test -capabilities. Accreditation activities should not excessively burden -test teams or lead to inordinate expense. The AFOTEC staff lead for -Accreditation is A-2/9. Email questions about verification, validation, -and accreditation to A-2/9 workflow at: -UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil .

      Test Capability Accreditation

      AFOTEC's mission is to deliver combat capability through operational -test. AFOTEC often uses test capabilities to create a pseudo-employment -or combat environment in which to conduct the operational testing. These -test capabilities may include M&S of the employment environment as well -as M&S of the system under test (SUT). The test capabilities used in a -given test do not always represent the employment environment with 100% -accuracy. There are usually some differences in fidelity between the -actual combat systems and test representations. Given these differences, -AFOTEC is careful in drawing conclusions about SUT capabilities and -ensures that the representation of the employment environment is -adequate to draw credible conclusions. Inherently, AFOTEC assumes some -degree of risk when using test capabilities to represent an employment -environment or SUT to determine SUT capabilities. The purpose of -accreditation is to characterize that risk and ensure the risk is -acceptable.

      The Use of Modeling and Simulation

      The "AFOTEC OT&E Guide," 11th ed. states that whenever M&S is used to -capture information in an OT&E Final Report, proper M&S accreditation is -required. M&S includes, but is not limited to, digital M&S, -hardware-in-the-loop (HITL) virtual simulations and test drivers such as -data injectors and stimulators. M&S also includes physical models of -targets, threat representations and combinations of simulations. Test -planners (DT&E, LFT&E, OT&E) should collaborate early with the program -manager's (PM) M&S proponent on planned uses of M&S for the purpose of -identifying OT M&S requirements, necessary verification and validation -(V&V) activities, and for securing program office M&S funding (as -applicable) IAW DoDI 5000.02 and AFI 63-101/20-101, 9 May 17.

      AFOTEC uses digital M&S for three primary purposes: test planning, -prediction of SUT performance, and extension of field test results. -AFOTEC uses HITL virtual simulations (and facilities) and test drivers -to test system performance under conditions that cannot be reproduced on -an open‑air range or on actual operational equipment. The ITD, test -concept and test plan should identify and explicitly describe the use of -M&S to include the use of distributed capabilities for executing -operational test events.

      Verification, Validation and Accreditation Definitions

      Definitions are based on DoDI 5000.61, DoD M&S Verification, Validation -& Accreditation (VV&A)

      • Verification. The process of determining that a test capability -accurately represents the developer's conceptual description and -specifications. Verification addresses whether the M&S works as -planned. Verification is typically accomplished by the model -developer (SPO, system contractor or facility/M&S owner).

      • Validation. The process of determining the degree to which a test -capability provides an accurate representation of the real world -from the perspective of the intended uses of the test capability. -Validation addresses whether the M&S represents reality. Validation -is typically accomplished by the model developer (Program Office -(PO), system contractor or facility/M&S owner).

      • Accreditation. The official certification that a test capability is -acceptable for use with a specific application. Accreditation -addresses whether the M&S is acceptable for a specific use. -Accreditation is accomplished by AFOTEC.

      The accreditation requirement applies to I/Q/F/MOT&Es and Operational -Utility Evaluations (UOUEs). Typical test capabilities requiring -accreditation may include open air range (OAR) assets, ground test -facilities, M&S, foreign materiel acquisition, test drivers, threat -simulators, targets, blue weapons used as threat surrogates and kill -removal systems.

      Acquisition Implications of Verification, Validation and Accreditation

      With the inception of agile acquisition, sprints, and rapid testing, it -is likely that there will be a unique acquisition approach for each -system under test. The AFOTEC OT&E Guide states: "There is no single -acquisition approach for a given type of system. The approach is -influenced by the urgency of need, the technology development -requirements, the amount of money allocated to the program, or any of a -variety of other influences."

      Accreditation Concepts

      Test teams should plan to accomplish the accreditation and publish the -accreditation report prior to test readiness review (TRR). AFOTEC will -be able to begin the test execution phase with confidence that the M&S -is credible. It may not always be possible to complete the accreditation -report prior to TRR but that should be the goal.

      Accreditation is about characterizing risk. Specifically, it is about -ensuring that the risk of using a model and/or simulation to determine -and report SUT effectiveness/suitability in an OT&E final report is -acceptable. Keeping this fundamental principle in mind will help keep -accreditation efforts on track. Test teams are encouraged to focus the -accreditation effort and documentation describing the risks. The -accreditation authority will ultimately decide whether or not to accept -the risks.

      Risk Matrix: Example

      The following excerpt is from the Accreditation Report for the Radar -Simulation Suite (RSS) used in the Cobra Judy Replacement Multi-Service -Operational Test and Evaluation (MOT&E), 12 Mar 14.

      The test team assessed the impacts to OT and the probability of -occurrence using the Air Force operational risk management general -assessment practices and definitions presented in Table 5-9, in -accordance with the 'Risk Management Guide for DOD Acquisition,' 6th -edition, Aug 06.

      For each identified risk, the test team has provided a narrative -discussion and identified major issues. The test team provided an -overall risk assessment for the use of RSS in OT." Table 5-9 defines the -severity of each risk ratings (low, low/medium, medium, medium/high, and -high). Table 5-10 identifies the assigned risk assessment by the test -team: Figure 5-5 shows the risk management rating scale (RMRS) with -green (low), yellow (medium) and red (high) ratings. "After rating each -primary risk, the test team populated the RMRS with the associated risk -number". "Risk 1 was identified as L/M impact and M/H probability of -occurrence.

      Table 5-9. Risk Severity Definitions

      Impact to OTDefinitionProbability of OccurrenceDefinition
      LNoneLUnlikely
      L/MNegligibleL/MSeldom
      MModerateMOccasional
      M/HCriticalM/HLikely
      HCatastrophicHFrequent

      Figure 5-5. Risk Management Rating Scale

      - - - image2 +APPENDIX C CYBER-RELATED MEASURES

      APPENDIX C CYBER-RELATED MEASURES

      [1]

      Cybersecurity T&E is used to describe the activities that encompass all +cybersecurity test and evaluation activities, including vulnerability +assessments, security controls testing, penetration testing, adversarial +testing, and cybersecurity testing related to a system’s operational +resilience and system cyber survivability capabilities within a mission +context.[2]

      AFOTEC considers cyber survivability, resiliency and security critical +mission enabling capabilities of a system under test (SUT). So the +expectation is that these capabilities will be fully integrated and +comprehensively tested components of every test program. AFOTEC A-2/9, +A-3I, and Detachment analysts will ensure that cyber-related measures +are developed for each program as necessary.

      Usage note: the focus of this appendix is on how to write a +cyber-related measure—refer to the AFOTEC Cyber Test Guide (CTG) for how +to rate and score cyber-related measures using operationally relevant +data.

      Measures Overview

      Test measures are the basis of the evaluation of a system under test +(SUT). They drive the data needs, collection, and analysis used to +evaluate effectiveness and suitability and serve as evidence of +capability performance and mission effects. There are three general +types of measures developed for Operational Test (OT):

      • Measures of Effectiveness (MOE) - Measures designed to assess +the degree to which the system under test can accomplish mission +objectives and achieve desired mission effects.

      • Measures of Performance (MOP) - Measure a system’s capabilities. +They may quantify performance such as speed, payload, range, +time-on-station, frequency, rating, or other distinctly observable +and/or quantifiable performance features. They may also document +whether or not a system can successfully complete a task.

      • Measures of Suitability (MOS) - Measure of the ability to +support the system under test in its intended operational +environment. MOSs typically relate to readiness, supportability, +logistics infrastructure and cost of ownership of the SUT.

      Composite Measures

      Composite measures aggregate and summarize data from multiple +attributes. The multidimensional nature and complexity of cyber-related +testing make adoption of composite measures very beneficial. A composite +measure facilitates evaluation of multiple attributes of the SUT by +consolidating results into a single score.

      To prevent deceptively obtuse and irrelevant results, it is critical +that all attribute measurements contributing to a composite measure be +well defined. Additionally, the test team’s evaluation and aggregation +strategy should be thoroughly documented in each of the composite +measure worksheets and be credible and supportable.

      Clarity, transparency, and accountability are required from all +stakeholders in composite cyber-related measures development and +documentation, as evidenced in the associated measures worksheets, to +better reduce distinct quality measures into a single summary indicator.

      See the main body of the AFOTEC Measures Guide for a complete +description and guidance on Composite Measures. See COI-4 Stand Alone +COI Construct ESC Example where they are used to aggregate effects of +operating within a cyber-contested environment for COIs 1, 2 and 3.

      Cyber-Related Measures. Capabilities and functions of a system are +evaluated using both MOPs and MOSs. When developing cyber-related +measures for a SUT, it is useful to visualize the system as having four +layers that may require measurement and assessment: Mission Effects, +System Capabilities, System Functions and Properties, and System +Structure. Figure C-1 depicts these four levels in a pyramid and how +they could relate to cyber-related measures.

      Figure C-1. The Pyramid—Evaluation Levels of a SUT

      + + + image13 -

      AFOTEC should strive to publish the accreditation plan early in the test -program lifecycle (shortly after measures are defined). The -accreditation plan establishes acceptance criteria, to which the -validation plans and reports should respond. Publishing the -accreditation plan early ensures AFOTECs opportunity to influence the -scope and nature of subsequent V&V activities and products, and to enter -discussions early with the developer of the M&S capability. DOT&E -expects the TEMP to include details on the VV&A approach, or a reference -to such details IAW DOT&E memo, 14 Mar 16.

      Known baseline. To the extent possible, the accreditation acceptance -criteria should be based upon comparing model output to a known -baseline. For example, for a threat, the known baseline may be the -Intelligence community assessment of threat behavior. For a target drone -aircraft the known baseline may be measured signature data of a foreign -aircraft. Strive to establish quantitative criteria whenever possible.

      Previous Accreditation

      There may be an opportunity to use M&S that has been accredited in the -past, either by AFOTEC or by another organization. For example, if -AFOTEC or another organization has used the intended M&S for similar -purposes, it may be possible to focus the accreditation effort on "delta -accreditation." In this case, the accreditation team will need to -articulate how the M&S has changed, if at all, since last accredited. In -addition, the team must illustrate how use of the previously accredited -model compares to the proposed use.

      AFOTEC does not make blanket or class accreditations. However, if "delta -accreditation" is feasible or the upcoming test, a new accreditation -report is not required. Depending on the intended use of the M&S, the -accreditation effort may consist of a comprehensive new report or a -one-page memo for record. When beginning any accreditation effort, it is -best to examine what has been done in order to avoid potential -duplication of effort or unnecessary documentation and staffing. Consult -with HQ A-2/9 to help decide the best route to take. Table 2 describes -the AFOTEC offices that have a role in the Accreditation process as well -as the correlation (if any) to VV&A roles as outlined in AFI 16-1001, -and associated responsibilities.

      Table 2. VV&A Roles and Documentation Responsibilities

      OfficeAFI Role CorrelationResponsibilities
      AFOTEC (typically the TD)Requiring AgencyEstablish the need for M&S for use in a particular program
      AFOTEC Technical Advisor (CA)*Accreditation AuthorityApproves AFOTEC accreditation plans and reports
      Det Technical Advisor (TA)Accreditation AgentReview and sign accreditation plans and reports prior to submission to CA
      Det Commander*Accreditation AuthorityApproves and signs accreditation plans/reports originating from his/her Detachment
      Det TDAccreditation Agent
      • Reviews/signs accreditation plans/reports documenting adequacy of test capabilities to support OT&E

      • Briefs M&S developer on Accreditation Plan and ensures V&V plans/reports meet Accreditation requirements identified in Accreditation Plan

      • Briefs the accreditation approach to A‑2/9 during the TR

      • Ensures that all test capabilities are accredited

      • Sends signed copies of accreditation plans and reports to A‑3 and HO for records management and archiving

      Det AnalystAccreditation AgentAuthors, signs and executes accreditation plans and authors accreditation reports for all test capabilities
      Operations Directorate (A‑3)None
      • Reviews accreditation plans/reports documenting adequacy of test capabilities to support OT&E

      • Validates test capability requirements

      Intelligence, Analyses and Assessments Directorate (A‑2/9)None
      • Assists the TD with the accreditation process as directed in the program tasking order

      • Advises on VV&A policy and process

      • Post final accreditation plans/reports to AFOTEC‑SharePoint site.

      • Records the decision on whether accreditation is required or not in a memo for the Det/TD post ITD

      • Reviews accreditation plans/reports for technical adequacy and advises CA accordingly

      • Staffs plans/reports through HQ via SSS; tracks comments and revisions, obtains CA signature

      • Monitors AF and DoD VV&A policy and communicates policy changes within AFOTEC

      Special Projects Division for NTTR (A‑8Z)None
      • Assists the TD as directed in the program tasking order

      • Maintains cognizance of accreditation activities associated with NTTR assets

      • Advises test team on the likelihood of successful accreditation for specific test capabilities

      • Maintains library of accreditation plans/reports associated with NTTR

      A-5RNoneMonitors test capability through participation in AF and DoD investment processes ensuring V&V plans support accreditation, are fully funded, and are included in the project management plans
      HONone
      • Receives copies of accreditation plans/reports from the TD

      • Maintains library of all AFOTEC accreditation plans/reports

      • Maintains a library of verification and validation reports for facilities AFOTEC commonly uses

      V&V ManagerNoneN/A
      V&V AgentNoneN/A
      PM/DeveloperNoneN/A
      *For the F-35 program and BMDS, the AFOTEC Commander (as a member of the F-35 Executive Committee) serves as the accreditation authority

      Verification and validation are the responsibility of the M&S -developer/owner. Figure 1 illustrates an overview of the VV&A process, -including the roles/responsibilities associated with VV&A. The bold -vertical line indicates the distinction between the capability owner -(V&V manager & V&V agent) V&V) and the capability user (Accreditation -Agent & Accreditation Authority).

      Figure 1. VV&A Overview

      - - - image3 +

      The Confidentiality, Integrity, and Availability (CIA) triad and the +Prevent, Mitigate, and Recover (PMR) constructs are useful in mapping +cyber to the four layers in the pyramid. The CIA triad can be thought of +as the desired effects akin to Mission Effects for a system that enables +or performs cyber defense operations, while the attributes associated +with the PMR construct can be thought of as enabling the CIA effects and +akin to System Capabilities, System Functions and Properties, and System +Structure. Therefore, the CIA triad leads to cyber-related MOEs, since +they look at achieving desired effects. The PMR attributes lead to +cyber-related MOPs/MOSs, since they address required system +capabilities, functions, characteristics, and logistics. This guide +should act as a guideline for measures evaluating cybersecurity, cyber +survivability and cyber resiliency of a system can take any of the three +measure forms (MOE, MOP, and MOS).

      Cyber related considerations for OT&E COI Design Constructs. AFOTEC +typically uses one of three different COI design constructs for planning +and reporting cyber-related effects as part of the overall OT&E. The +appropriate COI design construct is typically determined/developed when +building the OT&E Construct. The choice of the COI construct for cyber +has an impact on the selection of MOEs, MOPs, and MOSs and where they +are placed in the COI construct. The three COI constructs are designated +as Integrated, Stand-Alone, and Hybrid. Descriptions of the +cyber-related COI design constructs follow with examples of evaluation +summary charts (ESC) for each.

      Integrated Construct. For integrated constructs (commonly referred +to as traditional or Ops-based), the test team covers cyber effects +within the measures under each operational COIs.

      Cyber operational conditions, cyber threats, and cyber-related measures +are addressed within the context of each mission or operations-based COI +(wherever cyber can affect operational outcome). Cyber-related MOPs/MOSs +cover all attributes associated with PMR and the ten CSAs (cyber +survivability attributes). This COI construct also allows for +cyber-related MOE’s addressing CIA to be outlined separately across the +operational COIs, if needed.

      Using the integrated COI construct, identified/ notable cyber-related +issues that extend beyond the SUT (i.e., do not affect the degree of +mission accomplishment of the SUT or the ability to place in field use) +may be addressed in an annex to the OT&E report, if warranted. Figure +C-2 shows an ESC example for the Integrated COI Construct.

      Figure C-2. Integrated COI Construct ESC Example

      + + + image14 -

      Accreditation Process

      The Det will email unclassified accreditation plans/reports to the A-2/9 -workflow address: UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil . If the -plan/report is classified, contact the A-2/9 POC or workflow for -instructions. The A-2/9 POC will place accreditation plans/reports into -2-ltr coordination for 5 days and adjudicate all comments. Upon -completion, the A-2/9 POC will place accreditation plans/reports into CS -coordination for review and signature by the CA. The "AFOTEC OT&E Guide" -shows AFOTEC's accreditation process (Figure 2 below). Accreditation -activities begin during the OT&E Construct development with -identification of test capability requirements, followed by development -of an accreditation memo.

      Figure 2. AFOTEC Accreditation Process

      - - - image4 +

      Stand-Alone Construct. In the stand-alone COI construct, a +separate Cyber COI unifies and/or compartmentalizes the impacts to +mission and/or operations of the SUT when employed within a +cyber-contested environment. This COI construct allows the baselining of +uncontested performance in a cyber benign environment, as compared to +performance of the SUT in a cyber-contested environment. All +cyber-contested operational conditions, threats, measures, and test +events are addressed within the separate cyber COI. The separate cyber +COI captures all cyber survivability, cyber resiliency and +cybersecurity-related measures. These cyber-related measures cover all +attributes associated with CIA, PMR, and the ten CSAs.

      Composite Measures (COI 4 in Figure C-3) are used to collect and +aggregate the effects of a cyber-contested environment on measures from +the operational COIs. There should be a composite measure for each of +the operational COIs. Additional cyber-specific measures address the +system’s cyber operational capabilities.

      Figure C-3. Stand Alone COI Construct ESC Example

      + + + image15 -

      The memo from the Director, A‑2/9 to the detachment commander identifies -the test capability requirements, accreditation documentation -requirements, initial timelines, and relevant VV&A documents available. -Upon receipt of this memo, the TD (and designated test team members/with -HQ assistance) begins tracking VV&A resource expenditures including -manpower and dollars.

      During each Test Concept Technical Review, the TD will discuss the test -capabilities to be used and how the accreditation will be accomplished -based on the guidelines for use of the capability. A‑2/9 advises whether -accreditation is required or not. Throughout test planning, the TD -should inform A‑2/9 on the accreditation approach during scheduled -technical reviews, including proposed level of effort, completion dates -and accreditation resource requirements. The information enables A‑2/9 -to ensure technical adequacy on the overall accreditation approach and -prevent unnecessary expenditure of resources. As the program progresses, -the test team should identify planned use of test capabilities and the -associated accreditation approach in ITD and test concept briefings.

      The next step is an accreditation concept discussion, typically -conducted via VTC. This discussion is between the test team and A-2/9. -The purpose is to initiate dialogue and agree on assumptions and the -overall accreditation approach before initiating development of the -accreditation plan. The topics shown in Figure 5-8 help frame this -dialogue. After internal AFOTEC discussion it is a good idea to discuss -the accreditation concept with the DOT&E action officer, if DOT&E is -involved, to ensure there are no disconnects between AFOTEC and DOT&E -with respect to VV&A.

      Following completion of the accreditation concept discussion the test -team initiates development of the accreditation plan(s). Many test -capabilities have existing validation and/or accreditation reports that -may be useful for current and future VV&A efforts. A‑8Z, A‑2/9 and the -History Office (HO) may have copies of previous VV&A documents. The -accreditation plan establishes the benchmark for all remaining V&V -activities. Per AFI 16-1001, "Acceptability criteria are the most -important content of the accreditation plan and should be presented as -minimum criteria for accreditation." The team should place priority on -developing meaningful accreditation acceptance criteria. The TD submits -the plan to A-2/9, who reviews and coordinates the plan and submits the -plan to CA for approval.

      Once the plan is approved, the TD distributes the plan to M&S capability -owners so they can prepare V&V plans/reports that will produce data to -allow AFOTEC to determine whether or not the acceptance criteria have -been met. Following receipt of the V&V reports, the test team executes -the accreditation plan. This step primarily involves comparing the -results of the V&V to the acceptance criteria.

      Test Capability Accreditation Concept

      Discussion Topics

      • Describe system under test and its CONOPS

      • Include threats, targets and/or situations likely to require M&S

        • Describe what must be simulated and why (much simulate moving -vehicle targets; insufficient quantity at test ranges, etc.
      • Explain why you selected a particular test capability

      • Identify measures that require test capability to rate

      • Describe the risks of using a specific test capability in terms of -the effect on rating specific measures of effectiveness (MOEs), -measures of performance (MOPs), and measures of suitability (MOSs).

      • What is the likelihood of drawing an incorrect conclusion on -effectiveness/suitability?

      • Explain how you will convince yourself the capability is acceptable -for use in a specific test

      • Identify accreditation criteria

      • Typically involves comparison of test capability performance to some -known or expected values

      • Explain your accreditation timing

      • What V&V information is available or missing?

      • What are the risks of accrediting before the start of OT&E versus -after?

      Based upon review of the V&V reports, the test team produces an -accreditation report. The accreditation report summarizes the V&V report -findings and concludes with a recommendation to either: accredit, -accredit with limitations, or do not accredit the M&S. The typical -outcome will be accredit--accredit with limitations will be by -exception. The accreditation report should include a summary statement -that the M&S is accredited for a specific OT&E to address specific -MOEs/MOPs/MOSs. The test team submits the accreditation report to A-2/9 -for review and coordination and then A-2/9 submits the report to CA for -approval.

      From a timing standpoint the team should strive to publish the -accreditation report prior to test readiness review (TRR). This ensures -AFOTEC leadership is aware of all risks associated with using M&S prior -to the use of the M&S. Sometimes it is not possible to publish the -accreditation report prior to TRR. In this case the TD should include -information in the TRR briefing characterizing the risk associated with -using M&S and any mitigating factors, and include information regarding -when the accreditation report will be published.

      Next, the test team will use M&S as planned (e.g. execute the test), -consider lessons learned associated with the VV&A process, and document -those lessons learned in the OT&E final report.

      Finally, A-2/9 reviews the lessons learned and considers adjustments to -the VV&A process as needed. A-2/9 ensures the accreditation -plans/reports are archived and submits any necessary metadata to the -appropriate agency.

      Accreditation Plan and Report Format

      A sample format for accreditation plans and reports is located on the -AFOTEC SharePoint.

      The format is based upon MIL‑STD‑3022, DoD Standard Practice -Documentation of VV&A for Models and Simulations. Accreditation -documentation need not be voluminous, but should provide sufficient -information to enable the accreditation authority to make the -accreditation decision. The selected format (determined collaboratively -by the test team and A-2/9) will depend on past use of the test -capability, the number of measures impacted, resources needed for -accreditation, the test schedule and other factors. If the plan or -report is distributed outside of AFOTEC, it needs to be properly marked -along with the appropriate distribution statement.

      Accreditation References and Resources

      The following are organizations that the accreditation team can -reference for assistance in gathering pertinent accreditation -information.

      Air Force Agency for Modeling and Simulation

      The Air Force Agency for Modeling and Simulation (AFAMS) ( -http://www.afams.af.mil ) is a field operating agency of the Deputy -Chief of Staff for Operations, Plans and Requirements, Headquarters U.S. -Air Force. The Agency is located in Orlando\'s Central Florida Research -Park, with DoD, Joint, service, contractor, and educational -organizations focused on modeling and simulation (M&S). AFAMS\' mission -is to provide seamless integration of cross-functional Live Virtual -Constructive-Operational Training environments that allow warfighters to -maximize performance and decision making. AFAMS works closely with -Combatant Commands, Major Commands, the Air Force Reserve Command, the -Air National Guard, the Air Force Headquarters, Direct Reporting Units, -and Field Operating Agencies to provide the necessary development and -implementation standards for common access and interoperability within -the Live, Virtual and Constructive (LVC) Training domains for efficient -and secure global operations.

      Modeling and Simulation Coordination Office

      The Department of Defense (DoD) Modeling and Simulation Coordination -Office (M&SCO) ( http://www.msco.mil) is the focal point for -coordinating all matters regarding modeling and simulation across the -DoD for the Undersecretary of Defense (Acquisition, Technology and -Logistics) (USD(AT&L)) . M&SCO recommends -policies, plans, and programs to the USD(AT&L) that supports the M&S -Strategic Vision and DoD priorities. Among other documents, MSCO -maintains the DoD VV&A Recommended Practices Guide.

      AFOTEC provides the M&SCO a descriptive summary and metadata for all -accredited models or simulations that can potentially be reused by other -programs.

      On 18 March 2020, M&SCO released a new M&S Guidebook. The guidebook is a -compendium of short articles that capture key concepts in the M&S realm. -According to their website, the intent of the guidebook is to "provide -DoD M&S practitioners an information resource to leverage existing -knowledge, past experience, and available tools."

      Organizations supported by M&S need visibility into the tools, data and -services that meet their requirements. The DOD M&S steering committee -has established a web based search capability to provide a card catalog -level of detail about M&S tools, data and services. The catalog is -operated by the DMSC. Register to view this catalog here: -MSCatalogHelpDesk@mscatalog.msco.mil

      Best Practices

      • It is OK to conclude that the test capability is inadequate or to -recommend that the test capability not be accredited for use; -include justification and documentation. Establish acceptance -criteria in terms of comparison to known baseline. Can recommend -Accredit, accredit w/ limitations, don't accredit

      • Computer-based constructive models must be approved for use on Air -Force networks; start early

      • Ensure that a clear link exists between test capability use and test -limitations

      • Convince the Accreditation Authority the level of risk is -acceptable. Answer the question: "To what extent is this -representation adequate for purposes of a given test?"

      Summary

      Models and simulations will not be 100% accurate and there is risk -associated with drawing inferences about the models and their -applicability to actual systems. There is potential to draw incorrect -conclusions about SUT performance based on use of a particular test -capability. Remember AFOTECs credibility is at stake with every report. -Ensuring due diligence will result in a robust and valid accreditation -process. Inherently, AFOTEC assumes some degree of risk when using test -capabilities to represent an employment environment to determine SUT -capabilities. The purpose of accreditation is to assess and document -that risk.

      Remember that acceptability criteria are the most important concepts of -Accreditation. Make sure to consider the following: How confident are -you that the proposed test capability is acceptable for use during the -OT? List the pros and cons. What acceptability criteria did you -establish? What research/analysis did you perform? How did you reach -your conclusions? The accreditation plan and report configuration is at -the discretion of the test team. It is acceptable to have one plan and -multiple reports, or multiple plans and multiple reports. The AFOTEC -SharePoint site contains current accreditation information and -templates, including the DoD VV&A Recommended Practices Guide.

      References and Resources

      AFOTEC Accreditation Statement. "AFOTEC accredits [model] for use -in [SUT] OT&E to address the following -MOEs:_______________"

      Example "Delta Accreditation" Memo

      Documents from Recommended Practices Guide

      Governance

      DoDI 5000.02, 7 Jan 15: "Every distinct use of a model or simulation in -support of an operational evaluation will be accredited by an OTA, and, -for programs under DOT&E Oversight, its use for the operational -evaluation will be approved by DOT&E."

      DoDI 5000.61, DoD Modeling and Simulation (M&S) Verification, -Validation, and Accreditation (VV&A) , 9 Dec 09, para 4.a-b: "Models, -simulations, and associated data used to support DoD processes, -products, and decisions shall undergo verification and validation (V&V) -throughout their lifecycles. Models, simulations, and associated data -used to support DoD processes, products, and decisions shall be -accredited for an intended use."

      AFI 16-1001, Verification, Validation and Accreditation (VV&A) , 29 -Apr 2020, para 2.3: \"Air Force M&S applications will be accredited for -their intended purpose when supporting major DoD decision-making -organizations or processes, joint training, and joint exercises. All -executed V&V activities will support the model acceptance and -accreditation requirements defined by the accreditation authority.\"

      Points of Contact

      \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/1-1-introduction/page-data.json b/sites/oteguide/page-data/OT&E_Guide/1-1-introduction/page-data.json index ae799a4c..fd0256a0 100644 --- a/sites/oteguide/page-data/OT&E_Guide/1-1-introduction/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/1-1-introduction/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"5bcee507-8b11-50e8-b753-8734ea73dab5"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"5bcee507-8b11-50e8-b753-8734ea73dab5"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/1-3-fielding-combat-capes/page-data.json b/sites/oteguide/page-data/OT&E_Guide/1-3-fielding-combat-capes/page-data.json index d5870302..48324f1b 100644 --- a/sites/oteguide/page-data/OT&E_Guide/1-3-fielding-combat-capes/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/1-3-fielding-combat-capes/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"916a1c87-2165-5cd0-abac-2a89862a0827"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"916a1c87-2165-5cd0-abac-2a89862a0827"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/1-5-acquisition-pathways/page-data.json b/sites/oteguide/page-data/OT&E_Guide/1-5-acquisition-pathways/page-data.json index c1f61e5a..f79679be 100644 --- a/sites/oteguide/page-data/OT&E_Guide/1-5-acquisition-pathways/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/1-5-acquisition-pathways/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"a2590483-ccb9-5d11-9338-40de89299f9a"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"a2590483-ccb9-5d11-9338-40de89299f9a"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/1-6-art-principles/page-data.json b/sites/oteguide/page-data/OT&E_Guide/1-6-art-principles/page-data.json index 83fbaac3..edc43f67 100644 --- a/sites/oteguide/page-data/OT&E_Guide/1-6-art-principles/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/1-6-art-principles/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"ee79253f-c411-5876-ad66-740741663bb9"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"ee79253f-c411-5876-ad66-740741663bb9"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/2-test-lifecycle-overview/page-data.json b/sites/oteguide/page-data/OT&E_Guide/2-test-lifecycle-overview/page-data.json index 214ecf62..29314fd9 100644 --- a/sites/oteguide/page-data/OT&E_Guide/2-test-lifecycle-overview/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/2-test-lifecycle-overview/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"9b6a1db0-15c1-5059-b854-50aa0bbefefe"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"9b6a1db0-15c1-5059-b854-50aa0bbefefe"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/3-1-involvement-decision/page-data.json b/sites/oteguide/page-data/OT&E_Guide/3-1-involvement-decision/page-data.json index fb1b2ed6..a2f0ac0a 100644 --- a/sites/oteguide/page-data/OT&E_Guide/3-1-involvement-decision/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/3-1-involvement-decision/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"273bd704-aac8-5277-aa7f-cf5039ef23b3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"273bd704-aac8-5277-aa7f-cf5039ef23b3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/3-2-standing-activities/page-data.json b/sites/oteguide/page-data/OT&E_Guide/3-2-standing-activities/page-data.json index e7b03f3f..eaca2f7b 100644 --- a/sites/oteguide/page-data/OT&E_Guide/3-2-standing-activities/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/3-2-standing-activities/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"b6c783b3-d703-5514-8e99-609f0b9192d3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"b6c783b3-d703-5514-8e99-609f0b9192d3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/3-3-test-strategy/page-data.json b/sites/oteguide/page-data/OT&E_Guide/3-3-test-strategy/page-data.json index 9c37703f..15cfa430 100644 --- a/sites/oteguide/page-data/OT&E_Guide/3-3-test-strategy/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/3-3-test-strategy/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"3029582e-9c99-5851-86bf-34dc275d68eb"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"3029582e-9c99-5851-86bf-34dc275d68eb"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/4-1-levels-of-test/page-data.json b/sites/oteguide/page-data/OT&E_Guide/4-1-levels-of-test/page-data.json index 3e2c9373..462cf35d 100644 --- a/sites/oteguide/page-data/OT&E_Guide/4-1-levels-of-test/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/4-1-levels-of-test/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"836464f8-1d28-50a6-9f67-4696c3f77a06"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"836464f8-1d28-50a6-9f67-4696c3f77a06"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/4-2-OT-test-activity-cycles/page-data.json b/sites/oteguide/page-data/OT&E_Guide/4-2-OT-test-activity-cycles/page-data.json index e05ae2ff..6600973b 100644 --- a/sites/oteguide/page-data/OT&E_Guide/4-2-OT-test-activity-cycles/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/4-2-OT-test-activity-cycles/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"28dc0493-e6d2-51fc-abc3-bfd04ede6533"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"28dc0493-e6d2-51fc-abc3-bfd04ede6533"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/4-3-OT-construct/page-data.json b/sites/oteguide/page-data/OT&E_Guide/4-3-OT-construct/page-data.json index ff29aede..12de7ea4 100644 --- a/sites/oteguide/page-data/OT&E_Guide/4-3-OT-construct/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/4-3-OT-construct/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"0b71c49c-d37d-5497-a1c8-7b722e49381c"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"0b71c49c-d37d-5497-a1c8-7b722e49381c"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/4-4-building-the-ot-construct/page-data.json b/sites/oteguide/page-data/OT&E_Guide/4-4-building-the-ot-construct/page-data.json index 485655eb..93c3a372 100644 --- a/sites/oteguide/page-data/OT&E_Guide/4-4-building-the-ot-construct/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/4-4-building-the-ot-construct/page-data.json @@ -1 +1 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/4-4-building-the-ot-construct","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"569fa7a3-8313-5802-84bd-105136da21b7","title":"Building the OT&E Construct and Test Activities","slug":"/OT&E_Guide/4-4-building-the-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\": \"Building the OT&E Construct and Test Activities\",\n \"metaTitle\": \"Building the OT&E Construct and Test Activities\",\n \"metaDescription\": \"Building the OT&E Construct and Test 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, \"Define the \\\"What\\\"\"), mdx(\"h2\", null, \"System Under Test\"), mdx(\"p\", null, \"Generically, we test a system that will provide a warfighting\\ncapability, known as the system under test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"). However, we can refine\\ntesting the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" to various levels beyond the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" by designing individual\\ntest activities around effects, capabilities, functions/properties, and\\nstructure based on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"Initially, you should start at the top of the level-of-test\\npyramid\", \"-\", \"-mission effects encompassed by COIs and operations\", \"-\", \"-supported\\nby \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", tactics, techniques, and procedures (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactics, Techniques, and Procedures OR Technology Transition Plan\"\n }, \"TTP\"), \"), and threat\\ndocuments. When you understand these documents, you will know where and\\nhow the system fits into the envisioned battlespace and its intended use\\nand operational capabilities. The evaluation view (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \") is a tool that\\nguides development of COIs and operations. It helps you define what is\\nbeing tested at the mission-effects level. Figure 4-8 depicts an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \".\"), mdx(\"p\", null, \"Figure 4\\u20118. Example of an Evaluation View\"), 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\": \"1009px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/087a3dcf9411f4c543ecf559b09989b5/f6f7a/image14.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\": \"91.5057915057915%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAASCAYAAABb0P4QAAAACXBIWXMAABcRAAAXEQHKJvM/AAAFL0lEQVQ4yz2UeVCTRxjGn4+EKKEMQlCCoIUISKSoHIIcpSAqKlppBVRORWXk0AoqFVEJR0RBAwijKBCCGCRQ5NIkBA0hIOEqglK877Ziq3U6Ov2rNt0Pj535ze68u/vsPO/7zgKPooDBMJgeD3bkiaP8HcXRPs6SLb72VVG+CyRxPnMkmwMMd3nYMcVrcl0UKS89rvxw368j/a5d67ZXqFixHfUhYDaGMvB53PqOgno12DmBOXMrNo44VEVp+OLYHoLWqTKmx+Zc+Cgj07uIUbYixbY5TsOTxSr4l7Zd5sgitDizfAPqAkGJE5nQ64FXBHOiaUGwUi6j5a0I3I8hGwJLTw6aDG8EQ7Jmj1fHj2Pe8oy+oM7sHvvWnTdRuTwc5fHAPiJ0uAFIqyRXaOV+PUxztLQgk2BMmPZxNqCDz+kzWyvdcKK/HzmqEQiUIygZUxt8k8nFoVouyoa4EN+hcFJDARPkcI8eM4QtPPbpgSXG50YWs8uHXNkVN1zZ5wjlw57srEYecpvskNvSiP3iy0ivbsfxjgswo6ZB0JyAo4osVN8FCq6S5+/oKQzpYXzsSrZB2eAwI0OqYRxu0DIyL2oZB6U9jJLrNwxyW08hrcKROv9ARxV0jlAnu8ao2oftKLi2HoXqQ3ANMieiByDSfgtbormDICL2zIB5s4FZHOBLksCZkSSH39P2XxAXp0d5qLijQp6yGwXdGtQ+lyGxyA+Z9cHwCpkBoTwQp3R8rKLLACMMR5vQixkEojdVq5lTGzAxpePmm3Yvtc6puWGdWjhmk148bF3YdG36HHsb1n/ksbBc4OBF4MhPwHZnik48WxTCTbgSZVnSmbxI2Jnqna/e6yPsTXM/MpgwO6txk9UmRTAc/07j3n4l9Jv8TeD17mmixZNUN6YdbF3N7MxZVoYcSwvwXFkwYoK4ZDAbNnIju2PMS3pT+MK+NPf862ke+dpkvqgr2rxess50X7q3sZNsx+LEM8mr1knSw7zq4xe46OW7cb8wFH9luUx1iKHBlCvMBSi0RFphYCsHz3J88W91JB4IfElHlaItwqz4RJCJqzbWIqppg2lc+yrMeXzITf6wYK3qkXBZ9wtRiPrJITelNoJpO9VuFEVNJ4tZTnbWnBVezhZ7wgO+oJtZkcC364i2PFoYMtuTbsM8f6P5yg3T07ShWPZoz9zCiUzPsyMZPpLRrKCa3p28mqSlHHfi1Agcy6mqgBah+TRIiczPemA9n1SeLk7YQjPXsljPowkx4etNk2Q8g4Ak+w/3xqD/R4ou3QCcgqMB+cRLihaq6egLk6p/Pi660JJdLG0VFtUrBIKLmrQq1VD+2WZVXPXAY+dL43/+UaXsf1+t6NUrbj17nS0qnkffvdTVz5ePPYvIKZey8Z4E3hIq2zQR51WDhcV1l3NOyRS5pTJFnqimSSiW954406yOldZc47Xp7mnKpPK+8oarfR0jv8rTdwpn0YKlDcpYsaJPUFTXzvps9RP3JvV4+kaPN+/0+OXxh9jBt/1A7eqMhR0pN90Vu3UB6gO91u2x4yj/OqYH81n1uvH8Os2or/r+a5KEB5sp6EJhcmxlnr0kZoIv2TKwsGbb0Fc1W4dcJPEDtpKoCZbAv5R8X8mObQndjg3xqkUtSXJuY3QPyoLCDM+vw2S3HseqGiDrHSefQ5sPed0TzL1eXEa23/xp2f4O5G904AiDyRzgwMoP4GOJmRlLsjZ7kWLX757K1HFf1f5x+7btk6hcGQ/ZWgS2CgyrlTqq4/Yk/gdnnypP5b6YRAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image14\",\n \"title\": \"image14\",\n \"src\": \"/static/087a3dcf9411f4c543ecf559b09989b5/f6f7a/image14.png\",\n \"srcSet\": [\"/static/087a3dcf9411f4c543ecf559b09989b5/a2ead/image14.png 259w\", \"/static/087a3dcf9411f4c543ecf559b09989b5/6b9fd/image14.png 518w\", \"/static/087a3dcf9411f4c543ecf559b09989b5/f6f7a/image14.png 1009w\"],\n \"sizes\": \"(max-width: 1009px) 100vw, 1009px\",\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 test team may use other tools to develop these portions of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct and define what is being tested at the mission-effects level\\n(\", mdx(\"em\", {\n parentName: \"p\"\n }, \"see\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct Guide). A description or requirement of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is\\nuseful and you may find this information in capability-based documents\\nsuch as a capabilities development document (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \")/ information system\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \") \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \".\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Requirements\"), \"-\", \"-should not be the primary method of developing COIs,\\noperations, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \". Initially, you should use a top-down approach to\\ncapture the intended use of the system and what combat capability it\\nprovides. You may use requirements later to highlight system\\nattributes and characteristics.\")), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools.\"), \" Evaluation view, evaluation summary chart, core teams,\\ninitial test design, use-cases, cause-effect diagrams, top-down,\\nbottom-up, five-whys, brainstorming.\"), mdx(\"h2\", null, \"Measures\"), mdx(\"p\", null, \"After establishing COIs and operations (defining \\\"what\\\" is being\\ntested), the test team will develop measures.\"), mdx(\"p\", null, \"A measure conveys information about a system's effect, capabilities,\\nfunctions, properties, or the structure being addressed. Measures may be\\nthe quality, presence/absence, capacity, amount, quantity, dimensions,\\net. al. of the effects, capabilities, functions, properties, or\\nstructure. Measures serve as the basis for evaluating the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" and\\nidentifying data needs and collection procedures during a test. Measures\\nalso guide development of battlespace conditions.\"), mdx(\"p\", null, \"There are several different types or forms of measures (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"see\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://cs2.eis.af.mil/sites/10008/library/jobaidsguides/AFOTEC%20Measures%20Guide.docx?Web=1\"\n }, \"Measures\\nGuide\"), \".\\nInitially, you develop a set of measures for mission effects of the\\nlevels-of-test pyramid for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or Operation established.\"), mdx(\"p\", null, \"Measures at mission-effects level are based on achieving the desired\\neffect from conducting the operations. Documents such as the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \",\\nTTPs, and OPLANs, in addition to subject matter experts (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \") knowledge\\nand experience, can help define these effects-based measures. The\\n\\\"Defense Acquisition Guidebook\\\" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 1-02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Dictionary,\"), \" define\\nthese as measures as effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \").\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"[Measure of Effectiveness.]\", \"{.ul} \\\"Are measures designed to\\ncorrespond to accomplishment of mission objectives and achievement\\nof desired results? They quantify the results to be obtained by a\\nsystem and may be expressed as probabilities that the system will\\nperform as required. \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may be further decomposed into measures of\\nperformance and measures of suitability.\\\" (\", mdx(\"em\", {\n parentName: \"li\"\n }, \"Defense Acquisition\\nGuidebook\"), \"). \\\"A criterion used to assess changes in system behavior,\\ncapability, or operational environment that is tied to measuring the\\nattainment of an end state, achievement of an objective, or creation\\nof an effect.\\\" (\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \"\\xA01-02, \", mdx(\"em\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Dictionary of Military and Associated\\nTerms\"), \", \", mdx(\"em\", {\n parentName: \"li\"\n }, \"As Amended Through 15 Feb 16\"), \").\")), mdx(\"p\", null, \"In determining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", ask yourself, \\\"What are the important components\\n(action, activity, task, et al.) of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"/operation indicating\\nsuccessful accomplishment of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"/operation?\\\" This is similar to the\\nquestion \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \"\\xA03-0, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Joint Operations\"), \", asks: \\\"Are we creating the effects\\nor conditions in the operational environment that we desire?\\\" The\\nemphasis is on the effects or outcomes (desired or undesired). State the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" as the desired effect you wish to achieve. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": When appropriate,\\nyou may state the \\\"undesired\\\" effects you wish to avoid.\"), mdx(\"p\", null, \"Data elements for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" are data required to determine whether an\\neffect has been achieved (or to what degree). A data element may be a\\ndirect measurement of the count of times the effect is achieved,\\nexpressed as a proportion, percentage, or probability.\"), mdx(\"p\", null, \"Ideally, for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, measures of effectiveness and a direct measurement\\nwould suffice to determine the combat capability of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". However,\\nadditional data below the mission level of test (i.e., at the system\\nlevel) may be required to determine whether an effect can be achieved.\\nConsequently, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" could also have a set of measures of performance\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \") and measures of suitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \"). Consistent with the Defense\\nAcquisition Guidebook, \\\"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may be further decomposed into measures of\\nperformance and measures of suitability.\\\" MOPs and MOSs may also be\\nuseful to explain why a mission effect was or was not achieved and to\\naddress the suitability of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing\"), \". As part of the integrate and combine\\ncollection/test principle, developing MOPs and MOSs can provide focus\\nand insight to the integrated team on what to measure and what data to\\ncollect to ensure the combat capability.\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"[Measure of Performance:]\", \"{.ul} Measure of a system's performance\\nexpressed as speed, payload, range, time-on-station, frequency, or\\nother distinctly quantifiable performance features. Several MOPs\\nand/or MOSs may be related to the achievement of a particular \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \".\\n(\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition Guidebook\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"[Measure of Suitability:]\", \"{.ul} Measure of an item's ability to be\\nsupported in its intended operational environment. MOSs typically\\nrelate to readiness or operational availability and, hence,\\nreliability, maintainability, and the item's support structure.\\nSeveral MOSs and/or MOPs may be related to the achievement of a\\nparticular measure of effectiveness or multiple measures of\\neffectiveness. (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition Guidebook\"), \")\"))), mdx(\"p\", null, \"MOPs and MOSs may also be useful as part of matching a test strategy to\\nan acquisition strategy. Applying the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles of early\\ninvolvement and integrated testing, you may employ MOPs and MOSs during\\nlower-level testing (e.g., sprints, spirals, increments, releases).\\nHowever, they should always be in support of ultimately achieving\\nmission effects\", \"-\", \"-measures of effectiveness. Figure 4-9 depicts the\\nlevels-of-test pyramid for measures.\"), mdx(\"p\", null, \"Figure 4\\u20119. Levels of Test Pyramid\"), 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\": \"987px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/aab3cfaf55f58c2c331d70f14b021b56/d1d24/image15.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,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAACHVAAAh1QEEnLSdAAADqklEQVQ4y3WT3U/aZxTHD2KWLNmyZFn2B2xLL3q1a5fsolua9W5ZerNdrMnSNptbx9bRaLUqWumLTX0hoqAgTqSgICv8eBWqCK2AiLb4AliBH+Dvh7VYqzV04+V39sCutmQnORfPOXk+3/PyPAD/Mb0+DYhY895eqp6EeLlc8QNyfiOdzoHHc1B/504eCoUCUBQD/2tisQVMJhbM5iy0tIzwqrEq9MyZL29NTFhfORxBx9HR0fvBIIJKtc33egu8SKQC4fAxDA7u/RsmFPrh7t0kKJU0yOWJuirI5zsAiyUuoKgwqtVO1Gqd6HbHmECg/Pnk5E5NTC5/yT91ioGZmVekmzycPTsO0NW1AWNjCAMDeZBIMnyJZBkaGpDADqTT0/uo1+9xdvt+2WZL5inqEJXKBBGIDRLgWwrFn9DdneNPTKd5jReS8MnHEYD0oQsaTiAMjdL17dficO7c5NsaDWMzGo9weHijLBJZOak0htWzXL5RlsliqNPlsb+fid+6/eKL775lQaGMgcGZ5lerBs/yItwzPa8fUiSgpydxQizOxbq6dvHmTeYviWSnMjpa9aecXr9PPMNpNC9KYjFTEAq3sK0ti9c7nyul0rX3KC9NhtcB8L3gmGews9A/tHa66zpz0NyUw19/iRcvX47jD41+7jfhGnfjxl6lr4+tyGSZ1+3tdFEgeIKXLgXLV4SZSq90G52h9O7S02dfd4+7ALzRZ+CLpBudoSxOO2kc1dBFcU8UhVdWuZ9+DOGF8w+JwCY2X2U5kYjhCBAFP0ewtWWHU2gTZddjuji7soPuxww+WKFV4AjEO1wrWXSRwPw6S5wkImxR794qK3RbXK90i2u6Guaam1J4rXWX6xTlKh2dGU5nT1QsgSg3bnpUcoazaAkkkpPW4GegMno+0jlXvrnvjSosi9spx3IWbcEUKmbm8HdqAWdXaXKBLU056MqQKsX1D8eLZl+Ko/zRypjRxzlCaTQ/2rJ19MjfNcyRLauph/DHQhQiuwgXBa1vqin/p/oHEZFudmVR6wgXrIEkup+wtern1nYq7tVUybPGluyhDFZhpJDu6nYHVPcJZ5MPI1NOHgny44dY1yIehHu2JXCtMpAoIWjtoQ+J6nmS11n9SdZBILPhDM6T8diX6EOS/8q/fVx75Gpqsc7ki/3zvao2MuUGhWEONLZgnXdzv/amiCKQ9iH+EqHttuwdkjs9M78uNXvXFxSG+ZOkVVhKveb3KY21uzpnGP4G6UKLdfNLM10AAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image15\",\n \"title\": \"image15\",\n \"src\": \"/static/aab3cfaf55f58c2c331d70f14b021b56/d1d24/image15.png\",\n \"srcSet\": [\"/static/aab3cfaf55f58c2c331d70f14b021b56/a2ead/image15.png 259w\", \"/static/aab3cfaf55f58c2c331d70f14b021b56/6b9fd/image15.png 518w\", \"/static/aab3cfaf55f58c2c331d70f14b021b56/d1d24/image15.png 987w\"],\n \"sizes\": \"(max-width: 987px) 100vw, 987px\",\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(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing.\"), \" Measures may be an iterative process,\\ntailored and adapting continuously as the test program progresses. At\\nthe mission effects level, measures should be developed to capture the\\neffects of conducting the operations; this helps guide the test design\\nprocess by highlighting the relevant conditions (factors and levels)\\nto test under. After designing the mission effects test points,\\nadditional measures may be developed for the capabilities and\\nfunctions/properties/structure. This may be done all at once or\\niteratively---adapting to what is learned as testing progresses or\\ntailoring to the development process.\")), mdx(\"h2\", null, \"Criteria and Thresholds\"), mdx(\"p\", null, \"Usually, measures of performance and suitability have criteria and\\nthresholds, but often measures of effectiveness do not. This is\\nconsistent with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E's goal of telling the user what a system is capable\\nof achieving (characterize). For measures without established criteria,\\nyou may use thresholds, referred to as user-established criteria, from\\nthe requirements document, or you may define an identified standard\\nbased on historical performance, TTPs, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", etc. It is possible to\\nhave a measure that does not have criteria, but some criteria is helpful\\nas a basis for evaluating the operational impact.\"), mdx(\"h2\", null, \"Data and Data Elements\"), mdx(\"p\", null, \"One of the primary purposes of measures is to identify the data needed.\\nThe individual types of data required by a measure are referred to as\\ndata elements. A data element may be a direct measurement (e.g., count\\nof targets destroyed, range at detection), an indirect measurement, or\\nset of measurements. Indirect measurements could be MOPs or MOSs and you\\ncan use them to calculate, infer, or deduce the supported measure's\\nvalue.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Collection\"), \"-\", \"-Measures help identify the data needs so the test\\nteam can plan to meet those needs. Do not depend on an approach of \\\"we\\nwill collect all of the data (and sort it out later).\\\" There may not\\nbe instrumentation to collect the data, thus it will need to be\\ndeveloped or a limitation identified. Data may by relatively\\ninexpensive to collect, or it may be complex and expensive to\\ncollect\", \"-\", \"-collecting \\\"all the data\\\" may be inefficient and wasteful if\\nnot actually needed.\")), mdx(\"p\", null, \"Common types of data include:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Measurements to answer a measure directly, or are used in a\\ncalculation. For example, both time and distance are physical\\nproperties measured directly.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Data may also be the measurements of the operational conditions\\n(e.g., time of day, altitude). This data supports the analysis of\\nthe outcome described by the measure.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"User comments are often gathered using instruments such as surveys,\\nquestionnaires, formal interviews, and focus groups. However, user\\ncomments can be unstructured, possibly unsolicited feedback from the\\noperators and users.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test team observations made during the test are also considered\\ndata. The observations could be unexpected or unplanned data to\\nsupport a measure.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Other information provided with deficiency reports, other agency\\nreports, studies, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" results, etc., may provide pertinent data. Data\\nmay include information in the form of measurements obtained during\\nor post-test from other parties (e.g., the developer, ranges, other\\nservices or test agencies) and open-ended, exploratory\\nquestionnaires.\"))), mdx(\"h2\", null, \"Effectiveness and Suitability\"), mdx(\"p\", null, \"Measures (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \") and data elements contribute to\\neffectiveness or suitability. In general, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" is effectiveness\\ncentric, and an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" is suitability centric. You can designate data\\nelements as you deem appropriate.\"), mdx(\"h2\", null, \"\", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"-Operations-Measures-Data Hierarchy\"), mdx(\"p\", null, \"You can organize elements of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct in several ways. Figure\\n4-10 depicts some possibilities.\"), mdx(\"p\", null, \"Figure 4\\u201110. Possible Ways to Structure\\nElements\"), 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/0897fe9f6289962841a4aa44a01dd96f/07a6a/image16.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\": \"59.07335907335908%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAABcRAAAXEQHKJvM/AAACsElEQVQoz11SXUiTYRQ+37ctv4uGkZJDzX4gQrQboSKCLpUg8KKrxq6S7saI7CqFbgVzV9IMR120YXQRonSxYWJq+/9hc07346Zjm6IiU9lw6ljP+ZhYfvDwvT/nPOc5z3lpZWWlLx6Pv97a2lIUi0U6Pj5+CdhOT09bcrkcbW5udiwtLQ3l8/nOUChE2WxWtba2Juzs7NDh4SENDg7Sf5/f7/8UDAZ/VKtVBQcVCoXnpVLpA+8BSiQS3YuLi5FkMtlzcnJC0WiUz5hY5HvkUzgcPidcXV0lENDY2BhBiZhOpzngMYoYnU5nAydNTEwQ/z0eTztiPqZSqfvlcplQQNDpdDQ+Pn5OyIGQrTAYDGSz2cTp6WlW8RaEv3F3xW6309TUlLLWbhfOfbCim88DgYDocrlkjoWFBdJqtcSLrz6fL7GxsdGGAJqfn1cCZLVam6EwCYLP/f39NDs7K3JrUEewwOT1ejNY3+VCmIGg1+uJLaOZmZlXCHjHVSqVCnsiMjFUtczNzQ2BtDcSicgqDg4OBO4K5H0o+h5DvMQ54BAwPAGDE2STTSbTZVQJoaVvNfkiJ+7u7nKBZ1BSQJsvkMTESi4wMDAgwX8ncqycw7H7+/tE6+vr5Ha7W5eXl79nMpk3qCarAc6m2BuLxWyIewRb6Gz6k5OTrZj8H5yNbm9v09HRUdPe3t4tqqura4QYCWBVV1UqVQv+GuBafX19I5sNvwjvlFBUqBUjs9l83eFwROC/rBDTd+CFRLmzdoVC0aZWqx9KkvQU+3vADaAVaDIajSIev/JfMsbIyIgGXv/E3TDv0f4ouvjChA+YFHgCMGEP0AV0As104YNPAh4/WSyWm1BYhPpfOBagMAqFWaqp4TZvA3dq+44apIuEmDBh8rKX8FADIjXaJyhtwrNq+AtpxgXmd12FCQAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image16\",\n \"title\": \"image16\",\n \"src\": \"/static/0897fe9f6289962841a4aa44a01dd96f/e3189/image16.png\",\n \"srcSet\": [\"/static/0897fe9f6289962841a4aa44a01dd96f/a2ead/image16.png 259w\", \"/static/0897fe9f6289962841a4aa44a01dd96f/6b9fd/image16.png 518w\", \"/static/0897fe9f6289962841a4aa44a01dd96f/e3189/image16.png 1035w\", \"/static/0897fe9f6289962841a4aa44a01dd96f/07a6a/image16.png 1095w\"],\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, \"Consider the following when contemplating how to structure elements:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Do not confuse an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" with an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" (or an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \"/MOSs do not\\ndescribe the desired effect, but may contribute to determining the\\neffect or explaining the effect.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The same or similar \", 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\"), \", or data element may contribute to more\\nthan one \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \". This can be portrayed or documented several different\\nways. Realize the context may change (i.e., an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" on documentation\\nwill differ between an operator and a maintainer).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Effectiveness and suitability determination is NOT based on the NAME\\nof the measure or data element, rather on what attribute it is\\nmeasuring\", \"-\", \"-effectiveness or suitability.\"))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools.\"), \" Measures workshop, evaluation view, operational\\ncapabilities, cause and effect diagram, brainstorming.\"), mdx(\"h2\", null, \"Conditions\"), mdx(\"p\", null, \"After developing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", you will develop operational conditions.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Conditions\"), \"-\", \"-You do not have to use MOPs and MOSs to establish\\nbattlespace conditions or establish a subsequent test design to\\ndetermine mission effects. You can use only \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" to develop the test\\ndesign for mission effects. Consequently, it is not necessary to\\ndevelop MOPs and MOSs prior to developing the test design for mission\\neffects.\")), mdx(\"p\", null, \"An operational condition is defined by a set of factors, each at a given\\nlevel. A factor is a variable of the environment. A level is a set value\\nwithin the range of values that a factor can hold. Table 4-1 contains an\\nexample of a set of factors.\"), mdx(\"p\", null, \"Table 4\\u20111. Example of a Set of Factors\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Factors\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Levels\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mode of Travel\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle; Foot\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Speed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5--30 mph\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Battery Type\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable; Non-rechargeable\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Terrain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat; Mountainous; Littoral\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Time of day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night; Day; Transition\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High; Low\")))), mdx(\"p\", null, \"Together, the set of factors and levels forms the relevant set of\\noperational conditions. Table 4-2 contains an example of a single,\\nparticular condition.\"), mdx(\"p\", null, \"Table 4\\u20112. Example of a Single Condition\"), mdx(\"p\", null, \" Condition:\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Factor\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Level\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mode of Travel\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Speed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"25 mph\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Battery Type\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Terrain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Time of day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")))), mdx(\"p\", null, \"Potentially, factors and levels influence measures of particular\\ninterest. However, they can also be part of the battlespace, regardless\\nof whether they impact the outcome. Operational conditions support the\\nselection of test points as well as fulfilling operational sufficiency\\nin terms of breadth of the conditions.\"), mdx(\"p\", null, \"If working at the mission-effects level, identify operational conditions\\nfor each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or Operation. If working at the systems level, identify\\ndifferent conditions than those at the mission-effects level, but ensure\\nthey are related to mission-effects conditions.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Mission Factors\"), \"-\", \"-The mission-effects level Factor may be\\n\\\\\", \". At a system level, the corresponding factor may be\\n\\\\\", \".\")), mdx(\"p\", null, \"You may identify factors and levels using various methods. A study, such\\nas an analysis of alternatives (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \"), may provide insight on potential\\nfactors. Requirements mapped on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" may provide specific factors of\\ninterest (e.g., \\\"the system shall operate day and night,\\\" in which case\\nthe factor is time of day.) The core team\", \"-\", \"-composed of users,\\ndevelopers, operators, maintainers, analysts, Director, Operational Test\\nand Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \") reps, etc.\", \"-\", \"-brings a great deal of knowledge and\\nexpertise to brainstorm ideas on factors. You may find more rigorous\\nmethods, such as \\\"fishbone diagrams\\\" or cause-effect diagrams, helpful.\\n(\", mdx(\"em\", {\n parentName: \"p\"\n }, \"see\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/analyst_test_design_guide/\"\n }, \"Analyst Test Design\\nGuide\")), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing.\"), \" Defining conditions is an iterative\\nprocess that allows you to tailor and adapt continuously as the test\\nprogram progresses. Tailor the five steps for capabilities and\\nfunctions/properties/structure all at once, or iteratively, by\\nadapting to what you learn as testing progresses or tailoring to the\\ndevelopmental process.\")), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools.\"), \" Evaluation view, brainstorming\"), mdx(\"h2\", null, \"Operational Capabilities\"), mdx(\"p\", null, \"The material solution must possess operational capabilities to satisfy\\nthe capability gap within the context of the operation. Collectively,\\nOCs form a set of system capabilities, functions/parameters structured\\nto achieve mission effects. Identify OCs and their associated MOPs and\\nMOSs, during early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E planning steps and update them as testing\\nprogresses. Although requirements documents (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \") are a common\\nsource for developing OCs, OCs are tailored to the program, not obtained\\nfrom a canned list. See the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct Guide posted in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nIntranet Library.\"), mdx(\"h1\", null, \"Test Design\"), mdx(\"p\", null, \"A test design is a selection of design points within the possible set of\\nconditions, for a given operation, capability, or\\nfeature/function/structure being tested, and the rationale for choosing\\nthem. A design point is a single, particular set of conditions (set of\\nfactors with each factor at a specified level).\"), mdx(\"h2\", null, \"Test Design Goal\"), mdx(\"p\", null, \"The test design goal depends on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", level of test, and what\\nquestions need answers. Choose test design techniques and test points\\nbased on the test design goal, which could be problem identification,\\ncharacterization, comparison, discovery, learning, confirmation,\\nregression, prediction, optimization, etc. Table 4-3 contains two types\\nof test design goals \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" focuses on\", \"-\", \"-characterize and problem\\nidentification.\"), mdx(\"p\", null, \"Table 4\\u20113. Two Types of Test Design Goals\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Goal\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Definition\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Characterize\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Describe and distinguish the elements of something; to show the differing results or outcomes under differing conditions.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Problem Identification\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Find problem cases impeding achievement of operational objectives; no intent to confirm the outcome is repeatable.\")))), mdx(\"p\", null, \"In general, testing mission effects is to characterize while\\nsystem-level testing is working toward the goal of problem\\nidentification.\"), mdx(\"h2\", null, \"Test Designs\"), mdx(\"p\", null, \"Choosing the appropriate test design requires having a source of\\nexpertise on the system and its operational application. Each type of\\ntest design has strengths and weaknesses depending on the goal, type of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", and level of test. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test programs will likely have\\ncombinations of the following principal design techniques to meet\\n\\\"characterize\\\" and \\\"problem identification\\\" goals. See the \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/analyst_test_design_guide/\"\n }, \"Analyst Test\\nDesign\\nGuide\"), \"\\nfor a comprehensive list and discussion.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Designs Supporting Characterization.\"), \" Techniques or types of\\ntest designs for \\\"characterization\\\" provide a structured approach to\\nidentifying and managing operational conditions in a test\\nenvironment so you can make statements and conclusions about their\\neffect on the outcome. Design of experiments (DoE) is a broad set of\\ntechniques that accomplish this. DoE guides the selection of design\\npoints and test events so a rigorous analysis of the results leads\\nto credible statements and conclusions. Some examples of designs\\nused to support characterization are factorial designs, orthogonal\\narrays, screening designs, optimal designs, response surface designs\\nand observational studies.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Designs Supporting Problem Identification.\"), \" Designs\\nconstructed and analyzed to identify and possibly locate or explain\\nproblems to achieving desired mission effects are known as \\\"problem\\nidentification.\\\" The goal is not to estimate effects of battlespace\\nconditions or create a predictive model from test data, but to\\ndetermine whether \\\"something\\\" happens or a problem occurs under\\nspecific conditions. There is no intent to conduct a statistical\\nanalysis of results; although, you can use statistical techniques to\\nselect design points. Some examples of designs used to support\\n\\\"problem identification\\\" are demonstrations, cases (worst, best,\\nstressing), operational profiles, orthogonal arrays, and\\nspace-filling designs.\"))), mdx(\"p\", null, \"Test designs define when the test is complete. Establish exit criteria\\nto verify \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities are complete at macroscopic or microcosm levels.\\nBase exit criteria on time, events, performance, or test plan\\nexpectations. Exit criteria may be a singular criterion or several\\ncriteria, as influenced by the type and timing of test activities.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing\"), \". Developing the test design is an\\niterative process that you tailor and adapt continuously as the test\\nprogram progresses. At the mission-effects level, develop designs that\\ncapture effects of conducting operations under various operational\\nconditions (characterize). After designing mission-effects test\\nevents, develop additional designs for capabilities and\\nfunctions/properties/structure with the goal of characterization\\nand/or problem identification. Do this all at once, or iteratively, by\\nadapting to what you learn as testing progresses or tailoring to the\\ndevelopmental process.\")), mdx(\"p\", null, \"The result is a set of test events, which depicts an action taken under\\na set of conditions. This action may be at the mission-effects level or\\nany of the system-levels of test. The set of test events is typically\\ndepicted as some form of a test event matrix, as shown in Table 4-4.\"), mdx(\"p\", null, \"Table 4\\u20114. Test Event Matrix\"), mdx(\"table\", null, mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Test Event\")), mdx(\"td\", null, mdx(\"strong\", null, \"Mode of Travel\")), mdx(\"td\", null, mdx(\"strong\", null, \"Battery Type\")), mdx(\"td\", null, mdx(\"strong\", null, \"Terrain\")), mdx(\"td\", null, mdx(\"strong\", null, \"Time of Day\")), mdx(\"td\", null, mdx(\"strong\", null, \"Threat\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Characterize\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"1\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Mountain\"), mdx(\"td\", null, \"Transition\"), mdx(\"td\", null, \"Low\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"2\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Flat\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"Low\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"3\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"4\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Mountain\"), mdx(\"td\", null, \"Day\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"5\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Day\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"6\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Flat\"), mdx(\"td\", null, \"Transition\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"7\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Mountain\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"8\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Transition\"), mdx(\"td\", null, \"Low\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"9\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Mountain\"), mdx(\"td\", null, \"Transition\"), mdx(\"td\", null, \"Low\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"10\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Flat\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"Low\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"11\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"12\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Mountain\"), mdx(\"td\", null, \"Day\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Problem ID\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"13\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Day\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"14\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Flat\"), mdx(\"td\", null, \"Transition\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"15\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"High\")))), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test\"), \" \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Events\"), \"-\", \"-A test event may also be referred to as a \\\"test\\npoint\\\"; though, this may imply a system-level test event. The term\\n\\\"test event\\\" is preferred as being more inclusive of both mission and\\nsystem-level tests.\")), mdx(\"p\", null, \"Collaborate with other parties\", \"-\", \"-particularly other test agencies\", \"-\", \"-when\\ndesigning \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E events to capitalize on early involvement and integrated\\ntesting.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools:\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", mission essential task lists, requirements,\\ntechnical review, factor prioritization, design of experiments, demos.\"), mdx(\"h1\", null, \"Test Execution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" executes testing as established in previous steps of this Guide.\\nWe generate and collect data called for by the test design and measures.\\nAt the mission level, we operate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" in its intended operational\\nenvironment/conditions. We also execute testing at the system level.\\nThere are many considerations we must plan for prior to conducting\\ntesting.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant\"), \" Testing. Test teams have the flexibility to\\nadjust as needed to field capability as rapidly as possible. This\\nincludes modifying and streamlining processes, products, and\\nrequirements in advance or even after test execution has commenced.\")), mdx(\"h2\", null, \"Test Capabilities\"), mdx(\"p\", null, \"Test capabilities provide venues and resources to execute operations\\nunder realistic conditions in order to generate and collect\\noperationally relevant data. Identify test capabilities early to obtain\\nnecessary resources and avoid delays due to long-lead times. Test\\ncapabilities are categorized into the following four general areas:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Articles.\"), \" The test article is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". This may be a simple\\ndevice or a complex system encompassing communication links, trainers,\\nsupport equipment, etc.\"), mdx(\"p\", null, \"Ideally, you would have the actual, physical article for test. This\\nrequires early planning and coordination to identify how many are\\nneeded, who will fund and provide the test articles, the schedule for\\nwhen they are needed, the configuration of the test articles, etc.\"), mdx(\"p\", null, \"In addition to actual, physical test articles, you may require modeling\\nand simulation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \") of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" or portions of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Typically, these\\nrequire long lead times to develop so you should plan early. Whenever\\nyou use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to capture information in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final report, you must\\nobtain proper \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" accreditation.\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" predicting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance can help optimize field test events by\\nestimating \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance boundaries and characterization. This enables\\ntailoring field testing to address those areas that merit further\\nevaluation or are of special interest to the user.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing.\"), \" Test articles (physical and models or\\nsimulations) are a key opportunity to apply the principle of early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\ninvolvement by integrating and combining testing and data collection.\\nAt this point, finding problems is a primary goal.\")), mdx(\"p\", null, \"To satisfy \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E conclusions, a test article must be \\\"operationally\\nrepresentative.\\\" This does not mean the test article (i.e., component,\\nsub-system, or entire system) is in its final, production-representative\\nconfiguration, only that it is operationally representative for the\\nconclusions we derive.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Methodology/Environment.\"), \" Test methodology involves creating an\\noperationally realistic environment. This includes physical and cyber\\nenvironments the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" operates in (e.g., weather, terrain), targets and\\nother expendables, threats (including operational \\\"red\\\" forces and\\ncyber), and operational forces (personnel, rules of engagement, support\\nstructures, etc.). You may create an operationally realistic environment\\nusing the following methods:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Field Testing\"), \" is a good, initial choice for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" because it provides\\nthe most operationally realistic environment. It involves physical\\nand cyber elements. A common resource for field testing are\\n\\\"open-air ranges\\\" (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \") such as the Nevada Test and Training Range,\\nWhite Sands Missile Range, and the Utah Test and Training Range.\\nAnother resource are training exercises routinely conducted by the\\nservices. Ranges often include instrumentation, another test\\ncapability consideration. However, field testing is not always\\nfeasible to capture all test events.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Modeling and Simulation (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \")\"), \" provides another venue for executing\\ntest events. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" includes, but is not limited to, digital model or\\nsimulation, hardware-in-the-loop virtual simulations and test\\ndrivers such as data injectors and stimulators. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" also includes\\nphysical models of targets, threat representations, and combinations\\nof simulations. You must determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" requirements early to ensure\\ntheir inclusion in the system developments contract. When you use\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to capture information in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final report, you must obtain\\nproper \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" accreditation (see \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/accreditation_guide/\"\n }, \"Accreditation\\nGuide\"), \".\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"During test planning, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" can play a helpful role in optimizing\\nlimited \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" or ground test facility time. In addition, test planners\\ncan examine various configurations of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Resulting\\ninformation provides insight to maximize return from limited range\\ntime and to investigate areas of principle interest to the\\nwarfighter.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Studies and Analysis\"), \" may be based on theoretical principles,\\nphysics, component specifications, etc. Such studies may be useful\\nin planning a test or the development of a system, but are not\\nadequate to answer \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E \", mdx(\"em\", {\n parentName: \"p\"\n }, \"unless\"), \" they are based on empirical data\\n(i.e., field testing). Studies and their analysis may help develop\\nmodels and simulations of either the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" or the test environment.\"))), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"United States Code\"\n }, \"USC\"), \", Title 10\"), \" imposes constraints on the use of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" and studies and\\nanalysis during operational testing\", \"-\", \"-conclusions may not be based\\nexclusively on computer modeling, simulation, or analysis of\\ninformation contained in program documents.\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"em\", {\n parentName: \"li\"\n }, \"Hybrid\"), \" is a combination of test methodologies used during testing.\\nLive, virtual, and constructive (\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \") simulations combine actual\\ntest articles in a virtual environment (i.e., weather, terrain are\\nsimulated inputs to the live article) based on constructive physics\\nmodels. Typically, they are performed in real-time and may include\\ndistributed test applications. Creating joint test environments\\nrequiring numerous players may not be viable with field\\ntesting\", \"-\", \"-\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \" simulations can overcome this. \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \" simulations require\\na great deal of planning and coordination.\")), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Collection.\"), \" The purpose of executing a test is to generate and\\ncollect data, which requires some form of instrumentation.\\nInstrumentation is any form of data collection, not necessarily the\\n\\\"orange wires\\\" or \\\"data pumps\\\" commonly used for electronic\\ninstrumentation. You may require instrumentation to establish \\\"truth\\ndata,\\\" which is the actual state of the environment as well as the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\\nThe measures you develop are the basis for what data you will need and\\nwhat instrumentation you will use to collect that data. Generally,\\ninstrumentation does not require accreditation, but you should establish\\nthe fidelity and precision of instrumentation against data requirements.\\nInstrumentation comes in the following forms:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Articles:\"), \" Test articles may be instrumented, usually in the\\nform of a telemetry package or onboard data collection and storage\\npackage. There is a fine balance between not compromising an\\noperationally representative test article and obtaining data from an\\ninstrumentation package. Plan early because test article\\ninstrumentation requires close coordination with the developer of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" and the test environment (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \").\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Methodology/Environment:\"), \" You may require instrumentation of\\nthe environment for the data your measures identify and for\\nconditions or truth data. Field test instrumentation commonly\\nprovides time-space-positioning information (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Time / Space / Position Information\"\n }, \"TSPI\"), \"), but may also\\nrequire supplemental information such as weather conditions,\\nillumination, obscurations, electro-magnetic environment, signals,\\netc. Consider what environmental data you need and what\\ninstrumentation you need to collect it.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Models and Simulations:\"), \" Models and simulations require\\ninstrumentation similar to or the same as instrumentation described\\nfor test articles and the test environment. Establish\\ninstrumentation requirements early, when you identify your \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nrequirements.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Human:\"), \" Personnel involved in the test---operators, maintainers,\\ntesters, data collectors, observers, etc.---are an important source\\nof data. Instrumentation capturing this data may be surveys,\\nquestionnaires, interviews, audio/video recordings, and data\\ncollection forms. Consider the impact on an operator's workload and\\nwhether they will have the capacity to log test data.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Reliability, Maintainability, Availability:\"), \" RMA instrumentation is\\na special form of instrumentation needed for the test article and\\nthe test environment. Although the data has some commonality with\\neffectiveness measures, you will need additional instrumentation to\\ncapture data such as operating time, time of failures, failure\\nmodes, maintenance crew size, etc.\"))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Infrastructure (Enabling Test Capabilities).\"), \" The infrastructure\\nrequired to enable a test is a varied and diverse set of capabilities.\\nThe following examples are not all inclusive: radios, telephones, data\\nand communication links, transportation, site surveys, information\\ntechnology (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \") equipment, data processing, databases, and analysis\\ntools. While many of these are common across programs, individual\\nprograms will likely have their own unique infrastructure requirements.\"), mdx(\"h2\", null, \"Verification, Validation, and Accreditation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" accomplishes accreditation, which is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s official\\ncertification that a model or simulation is acceptable to use for a\\nspecific application.\"), mdx(\"p\", null, \"Accreditation of models and simulations is mandatory to ensure the\\nmodel/simulation is working correctly and it properly reflects the\\nappropriate operational environment or test article for a given test.\\nModeling or simulations create a pseudo-employment or combat environment\\nto conduct operational testing. The models or simulations used in a\\ngiven test do not always represent the employment environment with 100%\\naccuracy. There are usually some differences in fidelity between actual\\ncombat systems and environment and test representations. Given these\\ndifferences, we must ensure representation of the employment environment\\nis adequate to draw credible conclusions about the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Inherently, we\\nassume some degree of risk when using test capabilities to represent an\\nemployment environment or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". The purpose of accreditation is to\\ncharacterize and ensure that risk is acceptable.\"), mdx(\"p\", null, \"Accreditation is applicable when a test capability is used directly or\\nindirectly to provide information appearing in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final report.\\nTypical models/simulations that require accreditation are \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" assets,\\nground test facilities, foreign materiel acquisition, test drivers,\\nthreat simulators, targets, blue weapons used as threat surrogates and\\nkill removal systems.\"), mdx(\"p\", null, \"Models and simulations used solely for test-planning purposes do not\\nrequire a formal accreditation. However, use a similar process to ensure\\nthe model/simulation is adequate, and to identify risks involved and how\\nthey may affect the overall test.\"), mdx(\"p\", null, \"Accreditation is based on verification and validation of a model or\\nsimulation.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Verification\"), \". The process for determining whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nrepresents the developer's conceptual description and specifications\\naccurately, i.e., whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" works as planned. Typically, the\\nmodel's developer (system program office \", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \"\", \"]\", \", system contractor,\\nor facility/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" owner) provides verification.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Validation\"), \". The process for determining the degree to which the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" represents the real world accurately from the perspective of it\\nintended use, i.e., whether it represents reality. Typically, the\\nmodel's developer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \", system contractor or facility/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" owner)\\nprovides validation.\"))), mdx(\"p\", null, \"In addition to an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" plan and report for accreditation, we use plans\\nand reports for verification and validation. See the \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/accreditation_guide/\"\n }, \"Accreditation\\nGuide\"), \"\\nfor details of conducting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \".\"), mdx(\"h2\", null, \"Data Management\"), mdx(\"p\", null, \"How we collect and manage data is key to successful test execution.\\nEstablish a plan for data collection, storage, and analysis before you\\nbegin testing. Data management procedures describe methods of data\\ncollection, data control, verification, storage, and information\\nretrieval. Consider the following:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Collection.\"), \" You may need to train personnel how to use data\\ncollection tools (instrumentation). This includes data obtained from\\nthird parties (e.g., ranges, contractors) as well as instrumentation\\noperated directly by the test team. Data collectors should be familiar\\nwith the various data collection forms (paper or electronic). To prevent\\nloss of data, clearly label and duplicate it as soon as you collect it.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Quality Assurance and Control.\"), \" Verify data for quality and\\nquantity continuously. During the first level of verification, inspect\\ndata for content, format, and continuity. During the second level of\\nverification, compare recorded data to the data you expected to collect.\\nAs testing progresses, evaluate data continuously to determine whether\\nyou have collected and categorized a sufficient amount of data to answer\\nmeasures and COIs.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Filing and Storage.\"), \" Organize data so you can identify and\\nretrieve it easily. How you store test data will depend on the amount of\\ndata you need for a specific test, how often you obtain it, and how long\\nit takes to analyze and report it. The types of data storage vary from\\nsimple paper data collection forms to complex, relational databases, and\\nbig data techniques. Ensure you have data filing and storage needs in\\nplace before you begin executing tests.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Processing, Reduction, and Analysis.\"), \" Data processing and\\nreduction is how we handle data from its source to its input into the\\nactivity that reduces and analyzes it. These actions form the core of\\nthe data management system. The test team will monitor data analysis\\nwhile executing tests. Before testing, make sure data reduction tools,\\nand backup data reduction tools, are available and you have used them\\nduring an exercise before you execute your test.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Marking and Protecting Data.\"), \" Use the program security classification\\nguide (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \") to classify data properly prior to distribution. Ensure data\\nis marked appropriately for distribution. Carefully consider possible\\nconsequences of aggregating information from multiple sources.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Additional Data.\"), \" In addition to data required to answer measures, you\\nwill find the following forms of data useful or necessary:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"System configuration: As the system is developed, document the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s\\nconfiguration (software versions, hardware changes, control and\\ndisplay changes, etc.) for testing. This will help you determine\\nwhether additional testing is required because the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" or a portion\\nof the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is no longer operationally representative (or conversely,\\nit remains operationally representative).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Visual information documentation: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Documentation\"\n }, \"VIDOC\"), \", including still photos,\\nvideotape and related forms of imagery is one of the most versatile\\nways to collect data during test. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Documentation\"\n }, \"VIDOC\"), \" is recorded, as necessary,\\nfor analysis to illustrate test methods and results in briefings and\\nreports and for historical purposes.\"))), mdx(\"p\", null, \"A Data Management and Analysis Plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Management and Analysis Plan\"\n }, \"DMAP\"), \") is a tool that provides\\ndetailed procedures for the collection, reduction, quality assurance,\\ncollation, analysis, storage, and disposition of data.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Management and Analysis Plan\"\n }, \"DMAP\"), \", Joint Reliability and Maintainability Evaluation\\nTeam (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \"), Test Data Scoring Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Data Scoring Board\"\n }, \"TDSB\"), \"), data status matrix, dry\\nruns.\"), mdx(\"h2\", null, \"Detailed Test Procedures\"), mdx(\"p\", null, \"The test team writes and maintains detailed test procedures (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detailed Test Plan\"\n }, \"DTP\"), \"), which\\nare living documents that describe how they will execute a test. DTPs\\nare working-level reference documents that provide guidance to the test\\nteam on what to do for any test activity. They also provide an audit\\ntrail of planning decisions, rationale and records. DTPs are intended\\nfor use by the test team only and do not require external coordination.\\nHowever, there may be situations when the test site/range needs to\\nreview DTPs to ensure safety, security, and operational integrity.\"), mdx(\"h2\", null, \"Limitations\"), mdx(\"p\", null, \"Limitations affect the test team's ability to evaluate certain aspects\\nof a weapon system or to re-create certain aspects of the operational\\nenvironment. Limitations can be due to differences in the scenario\\n(operational versus test), test capabilities such as threat simulation,\\nrange restrictions (safety, physical airspace), specific test\\nmeasurement constraints, numbers of test articles, or the threat lay\\ndown (types and numbers). A limitation is something that inhibits our\\nability to accomplish a complete operational evaluation. Table 4-5\\ncontains examples of limitations.\"), mdx(\"p\", null, \"Table 4\\u20115. Limitations Example\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Limitation\"), mdx(\"th\", null, \"Mitigation\"), mdx(\"th\", null, \"Impact\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Limited MQ\\u20119 system availability\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Coordination with operational unit to share assets between the field training unit and IOT&E test;\")), mdx(\"li\", null, mdx(\"p\", null, \"Leverage combat missions\")))), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Inability to fully evaluate all measures;\")), mdx(\"li\", null, mdx(\"p\", null, \"Cybersecurity not evaluated\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Limited flight hours for reliability, maintainability and availability evaluation\"), mdx(\"td\", null, \"Use reliability availability logistics operations model\"), mdx(\"td\", null, \"Reported values may not reflect actual values in operational use\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Limited capability of Red Team to test weapon system via data link while in flight\"), mdx(\"td\", null, \"Coordinated with AFTC to emulate mission parameters in anechoic chamber to allow Red Team cyber attacks\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Cyber-exploitation effects not fully evaluated;\")), mdx(\"li\", null, mdx(\"p\", null, \"Inability to fully evaluate all measures\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Lack of threat systems at test facilities\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"Inability to report system effectiveness versus some threats\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"No integration of Lynx radar capability in mobile ground control station\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"Unable to evaluate Lynx synthetic aperture radar\")))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Mitigation\"), \". The test team must plan a way to mitigate the risk of each\\nlimitation to our evaluation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Mitigation must reduce the\\nimpact of the limitation enough to ensure our evaluation is still\\ncredible. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is one method you can use to mitigate a limitation.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Impact (of a Limitation after Mitigation)\"), \". The impact describes the\\nextent the limitation will (for a plan) or did (for a report) affect the\\nquality, completeness, and/or confidence of our evaluation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s\\neffectiveness and suitability. Our intent is to acknowledge limitations\\nand inform the decision maker and warfighter of the extent the\\nlimitations will or did affect our ability to report combat capability.\\nWe must state clearly what portions of the evaluation were affected by\\nthe impact.\"), mdx(\"p\", null, \"We may identify limitations at any point in a program. Of course, the\\nearlier we identify a limitation, the more likely it will be resolved.\\nWe must document limitations to provide justification for continued\\nimprovement and modernization of test capabilities, which will lead to\\nmore useful and relevant \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" reports and better systems being delivered\\nto the warfighter. Once we identify limitations, we carry them\\nthroughout all phases of the test program unless the program resolves\\nthem and they no longer apply.\"), mdx(\"h2\", null, \"Resourcing Test Events\"), mdx(\"p\", null, \"Test events, methodologies, and activities comprise the information we\\nuse to base the estimate of resources we need to execute operational\\ntests. Typically, resource estimates are documented in a test resource\\nplan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \").\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing.\"), \" Early in involvement, particular focus\\nis placed on the high cost (including high level of effort) and long\\nlead items. Typical examples of such items are threats,\\ninstrumentation, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" efforts.\")), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools\"), \": Test resource plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"), requirements review board,\\nfinancial review board.\"), mdx(\"h2\", null, \"Technical Reviews\"), mdx(\"p\", null, \"The test team conducts a technical review for each test activity prior\\nto executing it. A technical review is not a planning or directing\\nsession; rather, it is a quality assurance step to verify the test team\\napplied adequate technical focus to test planning. A key tenet of\\ntechnical reviews is validating evolution of the test's goal, design,\\nmeasures, and capabilities. Test activities must be operationally\\nsufficient and technically adequate.\"), mdx(\"h2\", null, \"Test Plans\"), mdx(\"p\", null, \"A test plan documents, at a minimum, the first three aspects of an\\noperational test: 1) system under test; 2) test design; and 3) test\\nexecution. These form the core parts of a test plan. However, there are\\nnumerous forms of plans from simple \\\"one page\\\" plans to complex,\\nintricate plans that require extensive coordination. We tailor each test\\nplan to the particular test activity. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"See\"), \" Business Processes for\\nprocess, format, and coordination of test plans.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools\"), \": 2-letter reviews, technical reviews.\"), mdx(\"h2\", null, \"Administrative Considerations\"), mdx(\"p\", null, \"The Business Processes chapter discusses administrative topics such as\\nmemorandums of agreement (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \"), non-disclosure agreements, TRPs,\\nauthorities to operate (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Tasking Order OR Authority to Operate\"\n }, \"ATO\"), \"), etc.\"), mdx(\"h2\", null, \"Executing the Test\"), mdx(\"p\", null, \"Executing the test is unique to each test activity. This guide does not\\nattempt to tell a test team how to actually execute their tests, but the\\nfollowing are some common best practices across programs:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test readiness reviews\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Dry runs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Situation reports\"))), mdx(\"p\", null, \"See the Test Execution Guide for best practices on executing test\\nactivities in real time.\"), mdx(\"h1\", null, \"Analysis and Evaluation\"), mdx(\"h2\", null, \"Inspection\"), mdx(\"p\", null, \"An initial step in analyzing and evaluating the test is to inspect the\\ndata. This is a continuation of data management activities during\\nexecution. Inspect the quality and completeness of data, gaps in data,\\nunexpected or unusual values or results, how and when the test team\\ncollected data, what activities they used to collect data, and what\\nconditions they were under when they collected data. This is not an\\nall-inclusive list\", \"-\", \"-apply experience and judgement when you inspect\\ndata.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Analysis\"), \"-\", \"-Analyze data continuously throughout test execution. Do\\nnot view it as a separate, independent step.\")), mdx(\"h2\", null, \"Analysis\"), mdx(\"p\", null, \"Analysis begins with the data, data elements, and measures. The intent\\nis to analyze the data consistent with the goal of the test. In\\naddition, you should always perform exploratory analysis of unexpected\\nor unusual data, outliers, anomalies, additional observations, and\\nnotable findings.\"), mdx(\"p\", null, \"During first-order analysis, describe results, usually with descriptive\\nstatistics such as the average, mean, range, and variance of the data.\\nIn addition, describe conditions for results\", \"-\", \"-whether to characterize\\nor identify problems. If a data element or a measure has a threshold,\\nstate whether it met or did not meet the threshold.\"), mdx(\"p\", null, \"Although not required for operational evaluation, you may perform some\\ndegree of root-cause analysis. Describe conditions for the results as a\\nbridge to root-cause analysis. Root-cause analysis may include analyzing\\nprocesses and procedures, and explaining how conditions and events may\\nhave led up to a particular outcome.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Depth of Analysis\", \"-\", \"-\"), \"As part of an integrated team, we can provide\\ninsight into root-cause analysis, particularly from operations and\\nconditions. However, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" typically does not engage in detailed,\\nengineering and physics-based root cause analysis.\")), mdx(\"p\", null, \"Analyze COIs/operations data at the mission-effects level in preparation\\nfor evaluating results for COIs/operations. Also, analyze effectiveness\\nand suitability data in preparation for evaluating results for\\neffectiveness and suitability.\"), mdx(\"h2\", null, \"Evaluation\"), mdx(\"p\", null, \"During evaluation, analyze consequences and impacts of results, which\\nwill lead to determining whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can achieve combat capability.\"), mdx(\"p\", null, \"Analyze and draw conclusions about the impact or \\\"so what\\\" of each data\\nelement or measure's ability to achieve effects for an operation or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \".\\nDrawing on analysis for COIs/operations, evaluate the performance of\\neach \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or operation. Evaluate the \\\"so what\\\" in terms of the degree or\\naspects of accomplishment, as well as conditions and costs (not just\\ndollars) of the accomplishment.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"So What\", \"-\", \"-\"), \"The \\\"so what\\\" evaluation depends on what we are\\nevaluating. For data elements and MOPs/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \", the so what is relative to\\nachieving the measure of effect. For \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", the so what is relative to\\nconducting the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"/Operation.\")), mdx(\"h2\", null, \"Effectiveness and Suitability\"), mdx(\"p\", null, \"We include a determination of effectiveness and suitability in our final\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report. We base our evaluation on measure outcomes, and the\\nsignificance of identified effectiveness and suitability shortfalls and\\ntheir degree of operational impact. We also consider deficiency reports\\nand other observations based on operational experience to determine the\\ndegree of operational impact and operational effectiveness and\\nsuitability. We cannot determine effectiveness or suitability prior to\\nour final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report because, until then, we do not have all the\\nnecessary information to draw an overall conclusion for the entire \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"h2\", null, \"Reporting Ratings\"), mdx(\"p\", null, \"We evaluate and rate effectiveness, suitability, COIs, and measures. We\\nuse ratings to communicate results and operational impacts concisely. We\\ndepict ratings with colored indicators and define what each color means\\n(\", mdx(\"em\", {\n parentName: \"p\"\n }, \"see\"), \" Evaluation and Reporting Guide), or through narratives that\\naddress results, analysis, and our evaluation.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools.\"), \" Descriptive statistics, exploratory analysis, analysis\\nof variance, linear regression, root cause, etc.\"), mdx(\"h2\", null, \"Deficiency Reporting\"), mdx(\"p\", null, \"The Deficiency Reporting, Investigation and Resolution (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Referential Integrity\"\n }, \"DRI\"), \"&R) process\\npromotes the ability to identify and correct deficiencies in Air Force\\nsystems or equipment before they impact the mission. Successful\\nimplementation drives resolution decisions, tempered by total ownership\\ncost, to correct, mitigate and/or accept risk of conditions impacting\\noperational safety, suitability, and effectiveness. Success is based\\nupon the following two premises: (1) the user, operator or maintainer\\nwill report deficiencies on their assigned systems and (2) the program\\nmanager (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \") will establish a proactive process to analyze data and act\\naccordingly to implement solutions after coordination with the\\nuser/sponsor.\"), mdx(\"h2\", null, \"Exit Criteria Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assesses results of our test activities to determine whether we\\nfulfilled our exit criteria. Our assessment reveals whether we need to\\nexecute additional test activities or not. We must meet our exit\\ncriteria to accomplish our test reporting deliverables.\"), mdx(\"h1\", null, \"Conclusions and Documenting\"), mdx(\"p\", null, \"The purpose of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s test report is to communicate test results, our\\noperational evaluation of those results, and their impact to the\\nwarfighter (the \\\"so what\\\"). The test team reports results using various\\nformats and on different timelines depending on the test activity,\\npurpose, and external needs. Test reporting is impacted significantly by\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles. Depending on the nature of the program, reports may\\ninform specific milestones or releases of capability to the field, or\\nprovide progress/status to program offices or feedback to developers and\\ntesters.\"), mdx(\"p\", null, \"Continuous feedback during early and integrated testing is fundamental\\nto reporting operationally relevant discovery early and delivering\\ncapability at the speed of relevance. The test team provides continuous\\nfeedback in small, tailorable reports (e.g., operational finding\\nreports, status reports, significant event reports, periodic reports,\\nquick look briefs) during ongoing acquisition and developmental\\nactivities. The purpose of these reports varies, but in general they\\nprovide feedback on capabilities and limitations rather than on the\\nsystem's effectiveness and suitability. Short, effective reports inform\\nthe developer and the program manager of test results as fast as they\\noccur. Whether in a verbal or written narrative or briefing format, they\\ncommunicate operational findings identified by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test teams through\\nparticipation in early and continuous development activities. In order\\nto provide relevant information, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will provide continuous and\\ncumulative feedback to the program office and all stakeholders regarding\\nfindings.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools\"), \". Rating taxonomies, evaluation and reporting guide.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#define-the-what","title":"Define the \"What\"","items":[{"url":"#system-under-test","title":"System Under Test"},{"url":"#measures","title":"Measures"},{"url":"#criteria-and-thresholds","title":"Criteria and Thresholds"},{"url":"#data-and-data-elements","title":"Data and Data Elements"},{"url":"#effectiveness-and-suitability","title":"Effectiveness and Suitability"},{"url":"#coi-operations-measures-data-hierarchy","title":"COI-Operations-Measures-Data Hierarchy"},{"url":"#conditions","title":"Conditions"},{"url":"#operational-capabilities","title":"Operational Capabilities"}]},{"url":"#test-design","title":"Test Design","items":[{"url":"#test-design-goal","title":"Test Design Goal"},{"url":"#test-designs","title":"Test Designs"}]},{"url":"#test-execution","title":"Test Execution","items":[{"url":"#test-capabilities","title":"Test Capabilities"},{"url":"#verification-validation-and-accreditation","title":"Verification, Validation, and Accreditation"},{"url":"#data-management","title":"Data Management"},{"url":"#detailed-test-procedures","title":"Detailed Test Procedures"},{"url":"#limitations","title":"Limitations"},{"url":"#resourcing-test-events","title":"Resourcing Test Events"},{"url":"#technical-reviews","title":"Technical Reviews"},{"url":"#test-plans","title":"Test Plans"},{"url":"#administrative-considerations","title":"Administrative Considerations"},{"url":"#executing-the-test","title":"Executing the Test"}]},{"url":"#analysis-and-evaluation","title":"Analysis and Evaluation","items":[{"url":"#inspection","title":"Inspection"},{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#effectiveness-and-suitability-1","title":"Effectiveness and Suitability"},{"url":"#reporting-ratings","title":"Reporting Ratings"},{"url":"#deficiency-reporting","title":"Deficiency Reporting"},{"url":"#exit-criteria-assessment","title":"Exit Criteria Assessment"}]},{"url":"#conclusions-and-documenting","title":"Conclusions and Documenting"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/4-4-building-the-ot-construct.md"},"frontmatter":{"metaTitle":"Building the OT&E Construct and Test Activities","metaDescription":"Building the OT&E Construct and Test Activities"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"569fa7a3-8313-5802-84bd-105136da21b7"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/4-4-building-the-ot-construct","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"569fa7a3-8313-5802-84bd-105136da21b7","title":"Building the OT&E Construct and Test Activities","slug":"/OT&E_Guide/4-4-building-the-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\": \"Building the OT&E Construct and Test Activities\",\n \"metaTitle\": \"Building the OT&E Construct and Test Activities\",\n \"metaDescription\": \"Building the OT&E Construct and Test 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, \"Define the \\\"What\\\"\"), mdx(\"h2\", null, \"System Under Test\"), mdx(\"p\", null, \"Generically, we test a system that will provide a warfighting\\ncapability, known as the system under test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"). However, we can refine\\ntesting the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" to various levels beyond the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" by designing individual\\ntest activities around effects, capabilities, functions/properties, and\\nstructure based on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"Initially, you should start at the top of the level-of-test\\npyramid\", \"-\", \"-mission effects encompassed by COIs and operations\", \"-\", \"-supported\\nby \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", tactics, techniques, and procedures (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactics, Techniques, and Procedures OR Technology Transition Plan\"\n }, \"TTP\"), \"), and threat\\ndocuments. When you understand these documents, you will know where and\\nhow the system fits into the envisioned battlespace and its intended use\\nand operational capabilities. The evaluation view (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \") is a tool that\\nguides development of COIs and operations. It helps you define what is\\nbeing tested at the mission-effects level. Figure 4-8 depicts an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \".\"), mdx(\"p\", null, \"Figure 4\\u20118. Example of an Evaluation View\"), 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\": \"1009px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/087a3dcf9411f4c543ecf559b09989b5/f6f7a/image14.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\": \"91.5057915057915%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAASCAYAAABb0P4QAAAACXBIWXMAABcRAAAXEQHKJvM/AAAFL0lEQVQ4yz2UeVCTRxjGn4+EKKEMQlCCoIUISKSoHIIcpSAqKlppBVRORWXk0AoqFVEJR0RBAwijKBCCGCRQ5NIkBA0hIOEqglK877Ziq3U6Ov2rNt0Pj535ze68u/vsPO/7zgKPooDBMJgeD3bkiaP8HcXRPs6SLb72VVG+CyRxPnMkmwMMd3nYMcVrcl0UKS89rvxw368j/a5d67ZXqFixHfUhYDaGMvB53PqOgno12DmBOXMrNo44VEVp+OLYHoLWqTKmx+Zc+Cgj07uIUbYixbY5TsOTxSr4l7Zd5sgitDizfAPqAkGJE5nQ64FXBHOiaUGwUi6j5a0I3I8hGwJLTw6aDG8EQ7Jmj1fHj2Pe8oy+oM7sHvvWnTdRuTwc5fHAPiJ0uAFIqyRXaOV+PUxztLQgk2BMmPZxNqCDz+kzWyvdcKK/HzmqEQiUIygZUxt8k8nFoVouyoa4EN+hcFJDARPkcI8eM4QtPPbpgSXG50YWs8uHXNkVN1zZ5wjlw57srEYecpvskNvSiP3iy0ivbsfxjgswo6ZB0JyAo4osVN8FCq6S5+/oKQzpYXzsSrZB2eAwI0OqYRxu0DIyL2oZB6U9jJLrNwxyW08hrcKROv9ARxV0jlAnu8ao2oftKLi2HoXqQ3ANMieiByDSfgtbormDICL2zIB5s4FZHOBLksCZkSSH39P2XxAXp0d5qLijQp6yGwXdGtQ+lyGxyA+Z9cHwCpkBoTwQp3R8rKLLACMMR5vQixkEojdVq5lTGzAxpePmm3Yvtc6puWGdWjhmk148bF3YdG36HHsb1n/ksbBc4OBF4MhPwHZnik48WxTCTbgSZVnSmbxI2Jnqna/e6yPsTXM/MpgwO6txk9UmRTAc/07j3n4l9Jv8TeD17mmixZNUN6YdbF3N7MxZVoYcSwvwXFkwYoK4ZDAbNnIju2PMS3pT+MK+NPf862ke+dpkvqgr2rxess50X7q3sZNsx+LEM8mr1knSw7zq4xe46OW7cb8wFH9luUx1iKHBlCvMBSi0RFphYCsHz3J88W91JB4IfElHlaItwqz4RJCJqzbWIqppg2lc+yrMeXzITf6wYK3qkXBZ9wtRiPrJITelNoJpO9VuFEVNJ4tZTnbWnBVezhZ7wgO+oJtZkcC364i2PFoYMtuTbsM8f6P5yg3T07ShWPZoz9zCiUzPsyMZPpLRrKCa3p28mqSlHHfi1Agcy6mqgBah+TRIiczPemA9n1SeLk7YQjPXsljPowkx4etNk2Q8g4Ak+w/3xqD/R4ou3QCcgqMB+cRLihaq6egLk6p/Pi660JJdLG0VFtUrBIKLmrQq1VD+2WZVXPXAY+dL43/+UaXsf1+t6NUrbj17nS0qnkffvdTVz5ePPYvIKZey8Z4E3hIq2zQR51WDhcV1l3NOyRS5pTJFnqimSSiW954406yOldZc47Xp7mnKpPK+8oarfR0jv8rTdwpn0YKlDcpYsaJPUFTXzvps9RP3JvV4+kaPN+/0+OXxh9jBt/1A7eqMhR0pN90Vu3UB6gO91u2x4yj/OqYH81n1uvH8Os2or/r+a5KEB5sp6EJhcmxlnr0kZoIv2TKwsGbb0Fc1W4dcJPEDtpKoCZbAv5R8X8mObQndjg3xqkUtSXJuY3QPyoLCDM+vw2S3HseqGiDrHSefQ5sPed0TzL1eXEa23/xp2f4O5G904AiDyRzgwMoP4GOJmRlLsjZ7kWLX757K1HFf1f5x+7btk6hcGQ/ZWgS2CgyrlTqq4/Yk/gdnnypP5b6YRAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image14\",\n \"title\": \"image14\",\n \"src\": \"/static/087a3dcf9411f4c543ecf559b09989b5/f6f7a/image14.png\",\n \"srcSet\": [\"/static/087a3dcf9411f4c543ecf559b09989b5/a2ead/image14.png 259w\", \"/static/087a3dcf9411f4c543ecf559b09989b5/6b9fd/image14.png 518w\", \"/static/087a3dcf9411f4c543ecf559b09989b5/f6f7a/image14.png 1009w\"],\n \"sizes\": \"(max-width: 1009px) 100vw, 1009px\",\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 test team may use other tools to develop these portions of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct and define what is being tested at the mission-effects level\\n(\", mdx(\"em\", {\n parentName: \"p\"\n }, \"see\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct Guide). A description or requirement of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is\\nuseful and you may find this information in capability-based documents\\nsuch as a capabilities development document (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \")/ information system\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \") \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \".\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Requirements\"), \"-\", \"-should not be the primary method of developing COIs,\\noperations, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \". Initially, you should use a top-down approach to\\ncapture the intended use of the system and what combat capability it\\nprovides. You may use requirements later to highlight system\\nattributes and characteristics.\")), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools.\"), \" Evaluation view, evaluation summary chart, core teams,\\ninitial test design, use-cases, cause-effect diagrams, top-down,\\nbottom-up, five-whys, brainstorming.\"), mdx(\"h2\", null, \"Measures\"), mdx(\"p\", null, \"After establishing COIs and operations (defining \\\"what\\\" is being\\ntested), the test team will develop measures.\"), mdx(\"p\", null, \"A measure conveys information about a system's effect, capabilities,\\nfunctions, properties, or the structure being addressed. Measures may be\\nthe quality, presence/absence, capacity, amount, quantity, dimensions,\\net. al. of the effects, capabilities, functions, properties, or\\nstructure. Measures serve as the basis for evaluating the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" and\\nidentifying data needs and collection procedures during a test. Measures\\nalso guide development of battlespace conditions.\"), mdx(\"p\", null, \"There are several different types or forms of measures (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"see\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://cs2.eis.af.mil/sites/10008/library/jobaidsguides/AFOTEC%20Measures%20Guide.docx?Web=1\"\n }, \"Measures\\nGuide\"), \".\\nInitially, you develop a set of measures for mission effects of the\\nlevels-of-test pyramid for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or Operation established.\"), mdx(\"p\", null, \"Measures at mission-effects level are based on achieving the desired\\neffect from conducting the operations. Documents such as the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \",\\nTTPs, and OPLANs, in addition to subject matter experts (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \") knowledge\\nand experience, can help define these effects-based measures. The\\n\\\"Defense Acquisition Guidebook\\\" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 1-02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Dictionary,\"), \" define\\nthese as measures as effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \").\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"[Measure of Effectiveness.]\", \"{.ul} \\\"Are measures designed to\\ncorrespond to accomplishment of mission objectives and achievement\\nof desired results? They quantify the results to be obtained by a\\nsystem and may be expressed as probabilities that the system will\\nperform as required. \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may be further decomposed into measures of\\nperformance and measures of suitability.\\\" (\", mdx(\"em\", {\n parentName: \"li\"\n }, \"Defense Acquisition\\nGuidebook\"), \"). \\\"A criterion used to assess changes in system behavior,\\ncapability, or operational environment that is tied to measuring the\\nattainment of an end state, achievement of an objective, or creation\\nof an effect.\\\" (\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \"\\xA01-02, \", mdx(\"em\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Dictionary of Military and Associated\\nTerms\"), \", \", mdx(\"em\", {\n parentName: \"li\"\n }, \"As Amended Through 15 Feb 16\"), \").\")), mdx(\"p\", null, \"In determining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", ask yourself, \\\"What are the important components\\n(action, activity, task, et al.) of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"/operation indicating\\nsuccessful accomplishment of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"/operation?\\\" This is similar to the\\nquestion \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \"\\xA03-0, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Joint Operations\"), \", asks: \\\"Are we creating the effects\\nor conditions in the operational environment that we desire?\\\" The\\nemphasis is on the effects or outcomes (desired or undesired). State the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" as the desired effect you wish to achieve. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": When appropriate,\\nyou may state the \\\"undesired\\\" effects you wish to avoid.\"), mdx(\"p\", null, \"Data elements for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" are data required to determine whether an\\neffect has been achieved (or to what degree). A data element may be a\\ndirect measurement of the count of times the effect is achieved,\\nexpressed as a proportion, percentage, or probability.\"), mdx(\"p\", null, \"Ideally, for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, measures of effectiveness and a direct measurement\\nwould suffice to determine the combat capability of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". However,\\nadditional data below the mission level of test (i.e., at the system\\nlevel) may be required to determine whether an effect can be achieved.\\nConsequently, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" could also have a set of measures of performance\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \") and measures of suitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \"). Consistent with the Defense\\nAcquisition Guidebook, \\\"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may be further decomposed into measures of\\nperformance and measures of suitability.\\\" MOPs and MOSs may also be\\nuseful to explain why a mission effect was or was not achieved and to\\naddress the suitability of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing\"), \". As part of the integrate and combine\\ncollection/test principle, developing MOPs and MOSs can provide focus\\nand insight to the integrated team on what to measure and what data to\\ncollect to ensure the combat capability.\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"[Measure of Performance:]\", \"{.ul} Measure of a system's performance\\nexpressed as speed, payload, range, time-on-station, frequency, or\\nother distinctly quantifiable performance features. Several MOPs\\nand/or MOSs may be related to the achievement of a particular \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \".\\n(\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition Guidebook\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"[Measure of Suitability:]\", \"{.ul} Measure of an item's ability to be\\nsupported in its intended operational environment. MOSs typically\\nrelate to readiness or operational availability and, hence,\\nreliability, maintainability, and the item's support structure.\\nSeveral MOSs and/or MOPs may be related to the achievement of a\\nparticular measure of effectiveness or multiple measures of\\neffectiveness. (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition Guidebook\"), \")\"))), mdx(\"p\", null, \"MOPs and MOSs may also be useful as part of matching a test strategy to\\nan acquisition strategy. Applying the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles of early\\ninvolvement and integrated testing, you may employ MOPs and MOSs during\\nlower-level testing (e.g., sprints, spirals, increments, releases).\\nHowever, they should always be in support of ultimately achieving\\nmission effects\", \"-\", \"-measures of effectiveness. Figure 4-9 depicts the\\nlevels-of-test pyramid for measures.\"), mdx(\"p\", null, \"Figure 4\\u20119. Levels of Test Pyramid\"), 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\": \"987px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/aab3cfaf55f58c2c331d70f14b021b56/d1d24/image15.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,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAACHVAAAh1QEEnLSdAAADqklEQVQ4y3WT3U/aZxTHD2KWLNmyZFn2B2xLL3q1a5fsolua9W5ZerNdrMnSNptbx9bRaLUqWumLTX0hoqAgTqSgICv8eBWqCK2AiLb4AliBH+Dvh7VYqzV04+V39sCutmQnORfPOXk+3/PyPAD/Mb0+DYhY895eqp6EeLlc8QNyfiOdzoHHc1B/504eCoUCUBQD/2tisQVMJhbM5iy0tIzwqrEq9MyZL29NTFhfORxBx9HR0fvBIIJKtc33egu8SKQC4fAxDA7u/RsmFPrh7t0kKJU0yOWJuirI5zsAiyUuoKgwqtVO1Gqd6HbHmECg/Pnk5E5NTC5/yT91ioGZmVekmzycPTsO0NW1AWNjCAMDeZBIMnyJZBkaGpDADqTT0/uo1+9xdvt+2WZL5inqEJXKBBGIDRLgWwrFn9DdneNPTKd5jReS8MnHEYD0oQsaTiAMjdL17dficO7c5NsaDWMzGo9weHijLBJZOak0htWzXL5RlsliqNPlsb+fid+6/eKL775lQaGMgcGZ5lerBs/yItwzPa8fUiSgpydxQizOxbq6dvHmTeYviWSnMjpa9aecXr9PPMNpNC9KYjFTEAq3sK0ti9c7nyul0rX3KC9NhtcB8L3gmGews9A/tHa66zpz0NyUw19/iRcvX47jD41+7jfhGnfjxl6lr4+tyGSZ1+3tdFEgeIKXLgXLV4SZSq90G52h9O7S02dfd4+7ALzRZ+CLpBudoSxOO2kc1dBFcU8UhVdWuZ9+DOGF8w+JwCY2X2U5kYjhCBAFP0ewtWWHU2gTZddjuji7soPuxww+WKFV4AjEO1wrWXSRwPw6S5wkImxR794qK3RbXK90i2u6Guaam1J4rXWX6xTlKh2dGU5nT1QsgSg3bnpUcoazaAkkkpPW4GegMno+0jlXvrnvjSosi9spx3IWbcEUKmbm8HdqAWdXaXKBLU056MqQKsX1D8eLZl+Ko/zRypjRxzlCaTQ/2rJ19MjfNcyRLauph/DHQhQiuwgXBa1vqin/p/oHEZFudmVR6wgXrIEkup+wtern1nYq7tVUybPGluyhDFZhpJDu6nYHVPcJZ5MPI1NOHgny44dY1yIehHu2JXCtMpAoIWjtoQ+J6nmS11n9SdZBILPhDM6T8diX6EOS/8q/fVx75Gpqsc7ki/3zvao2MuUGhWEONLZgnXdzv/amiCKQ9iH+EqHttuwdkjs9M78uNXvXFxSG+ZOkVVhKveb3KY21uzpnGP4G6UKLdfNLM10AAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image15\",\n \"title\": \"image15\",\n \"src\": \"/static/aab3cfaf55f58c2c331d70f14b021b56/d1d24/image15.png\",\n \"srcSet\": [\"/static/aab3cfaf55f58c2c331d70f14b021b56/a2ead/image15.png 259w\", \"/static/aab3cfaf55f58c2c331d70f14b021b56/6b9fd/image15.png 518w\", \"/static/aab3cfaf55f58c2c331d70f14b021b56/d1d24/image15.png 987w\"],\n \"sizes\": \"(max-width: 987px) 100vw, 987px\",\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(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing.\"), \" Measures may be an iterative process,\\ntailored and adapting continuously as the test program progresses. At\\nthe mission effects level, measures should be developed to capture the\\neffects of conducting the operations; this helps guide the test design\\nprocess by highlighting the relevant conditions (factors and levels)\\nto test under. After designing the mission effects test points,\\nadditional measures may be developed for the capabilities and\\nfunctions/properties/structure. This may be done all at once or\\niteratively---adapting to what is learned as testing progresses or\\ntailoring to the development process.\")), mdx(\"h2\", null, \"Criteria and Thresholds\"), mdx(\"p\", null, \"Usually, measures of performance and suitability have criteria and\\nthresholds, but often measures of effectiveness do not. This is\\nconsistent with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E's goal of telling the user what a system is capable\\nof achieving (characterize). For measures without established criteria,\\nyou may use thresholds, referred to as user-established criteria, from\\nthe requirements document, or you may define an identified standard\\nbased on historical performance, TTPs, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", etc. It is possible to\\nhave a measure that does not have criteria, but some criteria is helpful\\nas a basis for evaluating the operational impact.\"), mdx(\"h2\", null, \"Data and Data Elements\"), mdx(\"p\", null, \"One of the primary purposes of measures is to identify the data needed.\\nThe individual types of data required by a measure are referred to as\\ndata elements. A data element may be a direct measurement (e.g., count\\nof targets destroyed, range at detection), an indirect measurement, or\\nset of measurements. Indirect measurements could be MOPs or MOSs and you\\ncan use them to calculate, infer, or deduce the supported measure's\\nvalue.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Collection\"), \"-\", \"-Measures help identify the data needs so the test\\nteam can plan to meet those needs. Do not depend on an approach of \\\"we\\nwill collect all of the data (and sort it out later).\\\" There may not\\nbe instrumentation to collect the data, thus it will need to be\\ndeveloped or a limitation identified. Data may by relatively\\ninexpensive to collect, or it may be complex and expensive to\\ncollect\", \"-\", \"-collecting \\\"all the data\\\" may be inefficient and wasteful if\\nnot actually needed.\")), mdx(\"p\", null, \"Common types of data include:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Measurements to answer a measure directly, or are used in a\\ncalculation. For example, both time and distance are physical\\nproperties measured directly.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Data may also be the measurements of the operational conditions\\n(e.g., time of day, altitude). This data supports the analysis of\\nthe outcome described by the measure.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"User comments are often gathered using instruments such as surveys,\\nquestionnaires, formal interviews, and focus groups. However, user\\ncomments can be unstructured, possibly unsolicited feedback from the\\noperators and users.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test team observations made during the test are also considered\\ndata. The observations could be unexpected or unplanned data to\\nsupport a measure.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Other information provided with deficiency reports, other agency\\nreports, studies, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" results, etc., may provide pertinent data. Data\\nmay include information in the form of measurements obtained during\\nor post-test from other parties (e.g., the developer, ranges, other\\nservices or test agencies) and open-ended, exploratory\\nquestionnaires.\"))), mdx(\"h2\", null, \"Effectiveness and Suitability\"), mdx(\"p\", null, \"Measures (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \") and data elements contribute to\\neffectiveness or suitability. In general, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" is effectiveness\\ncentric, and an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" is suitability centric. You can designate data\\nelements as you deem appropriate.\"), mdx(\"h2\", null, \"\", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"-Operations-Measures-Data Hierarchy\"), mdx(\"p\", null, \"You can organize elements of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct in several ways. Figure\\n4-10 depicts some possibilities.\"), mdx(\"p\", null, \"Figure 4\\u201110. Possible Ways to Structure\\nElements\"), 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/0897fe9f6289962841a4aa44a01dd96f/07a6a/image16.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\": \"59.07335907335908%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAABcRAAAXEQHKJvM/AAACsElEQVQoz11SXUiTYRQ+37ctv4uGkZJDzX4gQrQboSKCLpUg8KKrxq6S7saI7CqFbgVzV9IMR120YXQRonSxYWJq+/9hc07346Zjm6IiU9lw6ljP+ZhYfvDwvT/nPOc5z3lpZWWlLx6Pv97a2lIUi0U6Pj5+CdhOT09bcrkcbW5udiwtLQ3l8/nOUChE2WxWtba2Juzs7NDh4SENDg7Sf5/f7/8UDAZ/VKtVBQcVCoXnpVLpA+8BSiQS3YuLi5FkMtlzcnJC0WiUz5hY5HvkUzgcPidcXV0lENDY2BhBiZhOpzngMYoYnU5nAydNTEwQ/z0eTztiPqZSqfvlcplQQNDpdDQ+Pn5OyIGQrTAYDGSz2cTp6WlW8RaEv3F3xW6309TUlLLWbhfOfbCim88DgYDocrlkjoWFBdJqtcSLrz6fL7GxsdGGAJqfn1cCZLVam6EwCYLP/f39NDs7K3JrUEewwOT1ejNY3+VCmIGg1+uJLaOZmZlXCHjHVSqVCnsiMjFUtczNzQ2BtDcSicgqDg4OBO4K5H0o+h5DvMQ54BAwPAGDE2STTSbTZVQJoaVvNfkiJ+7u7nKBZ1BSQJsvkMTESi4wMDAgwX8ncqycw7H7+/tE6+vr5Ha7W5eXl79nMpk3qCarAc6m2BuLxWyIewRb6Gz6k5OTrZj8H5yNbm9v09HRUdPe3t4tqqura4QYCWBVV1UqVQv+GuBafX19I5sNvwjvlFBUqBUjs9l83eFwROC/rBDTd+CFRLmzdoVC0aZWqx9KkvQU+3vADaAVaDIajSIev/JfMsbIyIgGXv/E3TDv0f4ouvjChA+YFHgCMGEP0AV0As104YNPAh4/WSyWm1BYhPpfOBagMAqFWaqp4TZvA3dq+44apIuEmDBh8rKX8FADIjXaJyhtwrNq+AtpxgXmd12FCQAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image16\",\n \"title\": \"image16\",\n \"src\": \"/static/0897fe9f6289962841a4aa44a01dd96f/e3189/image16.png\",\n \"srcSet\": [\"/static/0897fe9f6289962841a4aa44a01dd96f/a2ead/image16.png 259w\", \"/static/0897fe9f6289962841a4aa44a01dd96f/6b9fd/image16.png 518w\", \"/static/0897fe9f6289962841a4aa44a01dd96f/e3189/image16.png 1035w\", \"/static/0897fe9f6289962841a4aa44a01dd96f/07a6a/image16.png 1095w\"],\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, \"Consider the following when contemplating how to structure elements:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Do not confuse an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" with an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" (or an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \"/MOSs do not\\ndescribe the desired effect, but may contribute to determining the\\neffect or explaining the effect.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The same or similar \", 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\"), \", or data element may contribute to more\\nthan one \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \". This can be portrayed or documented several different\\nways. Realize the context may change (i.e., an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" on documentation\\nwill differ between an operator and a maintainer).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Effectiveness and suitability determination is NOT based on the NAME\\nof the measure or data element, rather on what attribute it is\\nmeasuring\", \"-\", \"-effectiveness or suitability.\"))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools.\"), \" Measures workshop, evaluation view, operational\\ncapabilities, cause and effect diagram, brainstorming.\"), mdx(\"h2\", null, \"Conditions\"), mdx(\"p\", null, \"After developing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", you will develop operational conditions.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Conditions\"), \"-\", \"-You do not have to use MOPs and MOSs to establish\\nbattlespace conditions or establish a subsequent test design to\\ndetermine mission effects. You can use only \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" to develop the test\\ndesign for mission effects. Consequently, it is not necessary to\\ndevelop MOPs and MOSs prior to developing the test design for mission\\neffects.\")), mdx(\"p\", null, \"An operational condition is defined by a set of factors, each at a given\\nlevel. A factor is a variable of the environment. A level is a set value\\nwithin the range of values that a factor can hold. Table 4-1 contains an\\nexample of a set of factors.\"), mdx(\"p\", null, \"Table 4\\u20111. Example of a Set of Factors\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Factors\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Levels\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mode of Travel\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle; Foot\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Speed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5--30 mph\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Battery Type\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable; Non-rechargeable\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Terrain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat; Mountainous; Littoral\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Time of day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night; Day; Transition\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High; Low\")))), mdx(\"p\", null, \"Together, the set of factors and levels forms the relevant set of\\noperational conditions. Table 4-2 contains an example of a single,\\nparticular condition.\"), mdx(\"p\", null, \"Table 4\\u20112. Example of a Single Condition\"), mdx(\"p\", null, \" Condition:\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Factor\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Level\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mode of Travel\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Speed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"25 mph\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Battery Type\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Terrain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Time of day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")))), mdx(\"p\", null, \"Potentially, factors and levels influence measures of particular\\ninterest. However, they can also be part of the battlespace, regardless\\nof whether they impact the outcome. Operational conditions support the\\nselection of test points as well as fulfilling operational sufficiency\\nin terms of breadth of the conditions.\"), mdx(\"p\", null, \"If working at the mission-effects level, identify operational conditions\\nfor each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or Operation. If working at the systems level, identify\\ndifferent conditions than those at the mission-effects level, but ensure\\nthey are related to mission-effects conditions.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Mission Factors\"), \"-\", \"-The mission-effects level Factor may be\\n\\\\\", \". At a system level, the corresponding factor may be\\n\\\\\", \".\")), mdx(\"p\", null, \"You may identify factors and levels using various methods. A study, such\\nas an analysis of alternatives (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \"), may provide insight on potential\\nfactors. Requirements mapped on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" may provide specific factors of\\ninterest (e.g., \\\"the system shall operate day and night,\\\" in which case\\nthe factor is time of day.) The core team\", \"-\", \"-composed of users,\\ndevelopers, operators, maintainers, analysts, Director, Operational Test\\nand Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \") reps, etc.\", \"-\", \"-brings a great deal of knowledge and\\nexpertise to brainstorm ideas on factors. You may find more rigorous\\nmethods, such as \\\"fishbone diagrams\\\" or cause-effect diagrams, helpful.\\n(\", mdx(\"em\", {\n parentName: \"p\"\n }, \"see\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/analyst_test_design_guide/\"\n }, \"Analyst Test Design\\nGuide\")), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing.\"), \" Defining conditions is an iterative\\nprocess that allows you to tailor and adapt continuously as the test\\nprogram progresses. Tailor the five steps for capabilities and\\nfunctions/properties/structure all at once, or iteratively, by\\nadapting to what you learn as testing progresses or tailoring to the\\ndevelopmental process.\")), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools.\"), \" Evaluation view, brainstorming\"), mdx(\"h2\", null, \"Operational Capabilities\"), mdx(\"p\", null, \"The material solution must possess operational capabilities to satisfy\\nthe capability gap within the context of the operation. Collectively,\\nOCs form a set of system capabilities, functions/parameters structured\\nto achieve mission effects. Identify OCs and their associated MOPs and\\nMOSs, during early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E planning steps and update them as testing\\nprogresses. Although requirements documents (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \") are a common\\nsource for developing OCs, OCs are tailored to the program, not obtained\\nfrom a canned list. See the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct Guide posted in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nIntranet Library.\"), mdx(\"h1\", null, \"Test Design\"), mdx(\"p\", null, \"A test design is a selection of design points within the possible set of\\nconditions, for a given operation, capability, or\\nfeature/function/structure being tested, and the rationale for choosing\\nthem. A design point is a single, particular set of conditions (set of\\nfactors with each factor at a specified level).\"), mdx(\"h2\", null, \"Test Design Goal\"), mdx(\"p\", null, \"The test design goal depends on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", level of test, and what\\nquestions need answers. Choose test design techniques and test points\\nbased on the test design goal, which could be problem identification,\\ncharacterization, comparison, discovery, learning, confirmation,\\nregression, prediction, optimization, etc. Table 4-3 contains two types\\nof test design goals \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" focuses on\", \"-\", \"-characterize and problem\\nidentification.\"), mdx(\"p\", null, \"Table 4\\u20113. Two Types of Test Design Goals\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Goal\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Definition\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Characterize\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Describe and distinguish the elements of something; to show the differing results or outcomes under differing conditions.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Problem Identification\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Find problem cases impeding achievement of operational objectives; no intent to confirm the outcome is repeatable.\")))), mdx(\"p\", null, \"In general, testing mission effects is to characterize while\\nsystem-level testing is working toward the goal of problem\\nidentification.\"), mdx(\"h2\", null, \"Test Designs\"), mdx(\"p\", null, \"Choosing the appropriate test design requires having a source of\\nexpertise on the system and its operational application. Each type of\\ntest design has strengths and weaknesses depending on the goal, type of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", and level of test. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test programs will likely have\\ncombinations of the following principal design techniques to meet\\n\\\"characterize\\\" and \\\"problem identification\\\" goals. See the \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/analyst_test_design_guide/\"\n }, \"Analyst Test\\nDesign\\nGuide\"), \"\\nfor a comprehensive list and discussion.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Designs Supporting Characterization.\"), \" Techniques or types of\\ntest designs for \\\"characterization\\\" provide a structured approach to\\nidentifying and managing operational conditions in a test\\nenvironment so you can make statements and conclusions about their\\neffect on the outcome. Design of experiments (DoE) is a broad set of\\ntechniques that accomplish this. DoE guides the selection of design\\npoints and test events so a rigorous analysis of the results leads\\nto credible statements and conclusions. Some examples of designs\\nused to support characterization are factorial designs, orthogonal\\narrays, screening designs, optimal designs, response surface designs\\nand observational studies.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Designs Supporting Problem Identification.\"), \" Designs\\nconstructed and analyzed to identify and possibly locate or explain\\nproblems to achieving desired mission effects are known as \\\"problem\\nidentification.\\\" The goal is not to estimate effects of battlespace\\nconditions or create a predictive model from test data, but to\\ndetermine whether \\\"something\\\" happens or a problem occurs under\\nspecific conditions. There is no intent to conduct a statistical\\nanalysis of results; although, you can use statistical techniques to\\nselect design points. Some examples of designs used to support\\n\\\"problem identification\\\" are demonstrations, cases (worst, best,\\nstressing), operational profiles, orthogonal arrays, and\\nspace-filling designs.\"))), mdx(\"p\", null, \"Test designs define when the test is complete. Establish exit criteria\\nto verify \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities are complete at macroscopic or microcosm levels.\\nBase exit criteria on time, events, performance, or test plan\\nexpectations. Exit criteria may be a singular criterion or several\\ncriteria, as influenced by the type and timing of test activities.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing\"), \". Developing the test design is an\\niterative process that you tailor and adapt continuously as the test\\nprogram progresses. At the mission-effects level, develop designs that\\ncapture effects of conducting operations under various operational\\nconditions (characterize). After designing mission-effects test\\nevents, develop additional designs for capabilities and\\nfunctions/properties/structure with the goal of characterization\\nand/or problem identification. Do this all at once, or iteratively, by\\nadapting to what you learn as testing progresses or tailoring to the\\ndevelopmental process.\")), mdx(\"p\", null, \"The result is a set of test events, which depicts an action taken under\\na set of conditions. This action may be at the mission-effects level or\\nany of the system-levels of test. The set of test events is typically\\ndepicted as some form of a test event matrix, as shown in Table 4-4.\"), mdx(\"p\", null, \"Table 4\\u20114. Test Event Matrix\"), mdx(\"table\", null, mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Test Event\")), mdx(\"td\", null, mdx(\"strong\", null, \"Mode of Travel\")), mdx(\"td\", null, mdx(\"strong\", null, \"Battery Type\")), mdx(\"td\", null, mdx(\"strong\", null, \"Terrain\")), mdx(\"td\", null, mdx(\"strong\", null, \"Time of Day\")), mdx(\"td\", null, mdx(\"strong\", null, \"Threat\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Characterize\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"1\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Mountain\"), mdx(\"td\", null, \"Transition\"), mdx(\"td\", null, \"Low\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"2\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Flat\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"Low\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"3\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"4\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Mountain\"), mdx(\"td\", null, \"Day\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"5\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Day\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"6\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Flat\"), mdx(\"td\", null, \"Transition\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"7\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Mountain\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"8\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Transition\"), mdx(\"td\", null, \"Low\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"9\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Mountain\"), mdx(\"td\", null, \"Transition\"), mdx(\"td\", null, \"Low\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"10\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Flat\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"Low\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"11\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"12\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Mountain\"), mdx(\"td\", null, \"Day\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Problem ID\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"13\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Day\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"14\"), mdx(\"td\", null, \"No Vehicle\"), mdx(\"td\", null, \"Non-rechargeable\"), mdx(\"td\", null, \"Flat\"), mdx(\"td\", null, \"Transition\"), mdx(\"td\", null, \"High\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"15\"), mdx(\"td\", null, \"Vehicle\"), mdx(\"td\", null, \"Rechargeable\"), mdx(\"td\", null, \"Littoral\"), mdx(\"td\", null, \"Night\"), mdx(\"td\", null, \"High\")))), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test\"), \" \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Events\"), \"-\", \"-A test event may also be referred to as a \\\"test\\npoint\\\"; though, this may imply a system-level test event. The term\\n\\\"test event\\\" is preferred as being more inclusive of both mission and\\nsystem-level tests.\")), mdx(\"p\", null, \"Collaborate with other parties\", \"-\", \"-particularly other test agencies\", \"-\", \"-when\\ndesigning \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E events to capitalize on early involvement and integrated\\ntesting.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools:\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", mission essential task lists, requirements,\\ntechnical review, factor prioritization, design of experiments, demos.\"), mdx(\"h1\", null, \"Test Execution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" executes testing as established in previous steps of this Guide.\\nWe generate and collect data called for by the test design and measures.\\nAt the mission level, we operate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" in its intended operational\\nenvironment/conditions. We also execute testing at the system level.\\nThere are many considerations we must plan for prior to conducting\\ntesting.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant\"), \" Testing. Test teams have the flexibility to\\nadjust as needed to field capability as rapidly as possible. This\\nincludes modifying and streamlining processes, products, and\\nrequirements in advance or even after test execution has commenced.\")), mdx(\"h2\", null, \"Test Capabilities\"), mdx(\"p\", null, \"Test capabilities provide venues and resources to execute operations\\nunder realistic conditions in order to generate and collect\\noperationally relevant data. Identify test capabilities early to obtain\\nnecessary resources and avoid delays due to long-lead times. Test\\ncapabilities are categorized into the following four general areas:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Articles.\"), \" The test article is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". This may be a simple\\ndevice or a complex system encompassing communication links, trainers,\\nsupport equipment, etc.\"), mdx(\"p\", null, \"Ideally, you would have the actual, physical article for test. This\\nrequires early planning and coordination to identify how many are\\nneeded, who will fund and provide the test articles, the schedule for\\nwhen they are needed, the configuration of the test articles, etc.\"), mdx(\"p\", null, \"In addition to actual, physical test articles, you may require modeling\\nand simulation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \") of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" or portions of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Typically, these\\nrequire long lead times to develop so you should plan early. Whenever\\nyou use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to capture information in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final report, you must\\nobtain proper \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" accreditation.\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" predicting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance can help optimize field test events by\\nestimating \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance boundaries and characterization. This enables\\ntailoring field testing to address those areas that merit further\\nevaluation or are of special interest to the user.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing.\"), \" Test articles (physical and models or\\nsimulations) are a key opportunity to apply the principle of early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\ninvolvement by integrating and combining testing and data collection.\\nAt this point, finding problems is a primary goal.\")), mdx(\"p\", null, \"To satisfy \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E conclusions, a test article must be \\\"operationally\\nrepresentative.\\\" This does not mean the test article (i.e., component,\\nsub-system, or entire system) is in its final, production-representative\\nconfiguration, only that it is operationally representative for the\\nconclusions we derive.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Methodology/Environment.\"), \" Test methodology involves creating an\\noperationally realistic environment. This includes physical and cyber\\nenvironments the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" operates in (e.g., weather, terrain), targets and\\nother expendables, threats (including operational \\\"red\\\" forces and\\ncyber), and operational forces (personnel, rules of engagement, support\\nstructures, etc.). You may create an operationally realistic environment\\nusing the following methods:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Field Testing\"), \" is a good, initial choice for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" because it provides\\nthe most operationally realistic environment. It involves physical\\nand cyber elements. A common resource for field testing are\\n\\\"open-air ranges\\\" (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \") such as the Nevada Test and Training Range,\\nWhite Sands Missile Range, and the Utah Test and Training Range.\\nAnother resource are training exercises routinely conducted by the\\nservices. Ranges often include instrumentation, another test\\ncapability consideration. However, field testing is not always\\nfeasible to capture all test events.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Modeling and Simulation (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \")\"), \" provides another venue for executing\\ntest events. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" includes, but is not limited to, digital model or\\nsimulation, hardware-in-the-loop virtual simulations and test\\ndrivers such as data injectors and stimulators. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" also includes\\nphysical models of targets, threat representations, and combinations\\nof simulations. You must determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" requirements early to ensure\\ntheir inclusion in the system developments contract. When you use\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to capture information in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final report, you must obtain\\nproper \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" accreditation (see \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/accreditation_guide/\"\n }, \"Accreditation\\nGuide\"), \".\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"During test planning, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" can play a helpful role in optimizing\\nlimited \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" or ground test facility time. In addition, test planners\\ncan examine various configurations of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Resulting\\ninformation provides insight to maximize return from limited range\\ntime and to investigate areas of principle interest to the\\nwarfighter.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Studies and Analysis\"), \" may be based on theoretical principles,\\nphysics, component specifications, etc. Such studies may be useful\\nin planning a test or the development of a system, but are not\\nadequate to answer \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E \", mdx(\"em\", {\n parentName: \"p\"\n }, \"unless\"), \" they are based on empirical data\\n(i.e., field testing). Studies and their analysis may help develop\\nmodels and simulations of either the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" or the test environment.\"))), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"United States Code\"\n }, \"USC\"), \", Title 10\"), \" imposes constraints on the use of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" and studies and\\nanalysis during operational testing\", \"-\", \"-conclusions may not be based\\nexclusively on computer modeling, simulation, or analysis of\\ninformation contained in program documents.\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"em\", {\n parentName: \"li\"\n }, \"Hybrid\"), \" is a combination of test methodologies used during testing.\\nLive, virtual, and constructive (\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \") simulations combine actual\\ntest articles in a virtual environment (i.e., weather, terrain are\\nsimulated inputs to the live article) based on constructive physics\\nmodels. Typically, they are performed in real-time and may include\\ndistributed test applications. Creating joint test environments\\nrequiring numerous players may not be viable with field\\ntesting\", \"-\", \"-\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \" simulations can overcome this. \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \" simulations require\\na great deal of planning and coordination.\")), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Collection.\"), \" The purpose of executing a test is to generate and\\ncollect data, which requires some form of instrumentation.\\nInstrumentation is any form of data collection, not necessarily the\\n\\\"orange wires\\\" or \\\"data pumps\\\" commonly used for electronic\\ninstrumentation. You may require instrumentation to establish \\\"truth\\ndata,\\\" which is the actual state of the environment as well as the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\\nThe measures you develop are the basis for what data you will need and\\nwhat instrumentation you will use to collect that data. Generally,\\ninstrumentation does not require accreditation, but you should establish\\nthe fidelity and precision of instrumentation against data requirements.\\nInstrumentation comes in the following forms:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Articles:\"), \" Test articles may be instrumented, usually in the\\nform of a telemetry package or onboard data collection and storage\\npackage. There is a fine balance between not compromising an\\noperationally representative test article and obtaining data from an\\ninstrumentation package. Plan early because test article\\ninstrumentation requires close coordination with the developer of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" and the test environment (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \").\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Methodology/Environment:\"), \" You may require instrumentation of\\nthe environment for the data your measures identify and for\\nconditions or truth data. Field test instrumentation commonly\\nprovides time-space-positioning information (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Time / Space / Position Information\"\n }, \"TSPI\"), \"), but may also\\nrequire supplemental information such as weather conditions,\\nillumination, obscurations, electro-magnetic environment, signals,\\netc. Consider what environmental data you need and what\\ninstrumentation you need to collect it.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Models and Simulations:\"), \" Models and simulations require\\ninstrumentation similar to or the same as instrumentation described\\nfor test articles and the test environment. Establish\\ninstrumentation requirements early, when you identify your \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nrequirements.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Human:\"), \" Personnel involved in the test---operators, maintainers,\\ntesters, data collectors, observers, etc.---are an important source\\nof data. Instrumentation capturing this data may be surveys,\\nquestionnaires, interviews, audio/video recordings, and data\\ncollection forms. Consider the impact on an operator's workload and\\nwhether they will have the capacity to log test data.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Reliability, Maintainability, Availability:\"), \" RMA instrumentation is\\na special form of instrumentation needed for the test article and\\nthe test environment. Although the data has some commonality with\\neffectiveness measures, you will need additional instrumentation to\\ncapture data such as operating time, time of failures, failure\\nmodes, maintenance crew size, etc.\"))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Infrastructure (Enabling Test Capabilities).\"), \" The infrastructure\\nrequired to enable a test is a varied and diverse set of capabilities.\\nThe following examples are not all inclusive: radios, telephones, data\\nand communication links, transportation, site surveys, information\\ntechnology (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \") equipment, data processing, databases, and analysis\\ntools. While many of these are common across programs, individual\\nprograms will likely have their own unique infrastructure requirements.\"), mdx(\"h2\", null, \"Verification, Validation, and Accreditation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" accomplishes accreditation, which is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s official\\ncertification that a model or simulation is acceptable to use for a\\nspecific application.\"), mdx(\"p\", null, \"Accreditation of models and simulations is mandatory to ensure the\\nmodel/simulation is working correctly and it properly reflects the\\nappropriate operational environment or test article for a given test.\\nModeling or simulations create a pseudo-employment or combat environment\\nto conduct operational testing. The models or simulations used in a\\ngiven test do not always represent the employment environment with 100%\\naccuracy. There are usually some differences in fidelity between actual\\ncombat systems and environment and test representations. Given these\\ndifferences, we must ensure representation of the employment environment\\nis adequate to draw credible conclusions about the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Inherently, we\\nassume some degree of risk when using test capabilities to represent an\\nemployment environment or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". The purpose of accreditation is to\\ncharacterize and ensure that risk is acceptable.\"), mdx(\"p\", null, \"Accreditation is applicable when a test capability is used directly or\\nindirectly to provide information appearing in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final report.\\nTypical models/simulations that require accreditation are \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" assets,\\nground test facilities, foreign materiel acquisition, test drivers,\\nthreat simulators, targets, blue weapons used as threat surrogates and\\nkill removal systems.\"), mdx(\"p\", null, \"Models and simulations used solely for test-planning purposes do not\\nrequire a formal accreditation. However, use a similar process to ensure\\nthe model/simulation is adequate, and to identify risks involved and how\\nthey may affect the overall test.\"), mdx(\"p\", null, \"Accreditation is based on verification and validation of a model or\\nsimulation.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Verification\"), \". The process for determining whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nrepresents the developer's conceptual description and specifications\\naccurately, i.e., whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" works as planned. Typically, the\\nmodel's developer (system program office \", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \"\", \"]\", \", system contractor,\\nor facility/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" owner) provides verification.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Validation\"), \". The process for determining the degree to which the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" represents the real world accurately from the perspective of it\\nintended use, i.e., whether it represents reality. Typically, the\\nmodel's developer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \", system contractor or facility/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" owner)\\nprovides validation.\"))), mdx(\"p\", null, \"In addition to an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" plan and report for accreditation, we use plans\\nand reports for verification and validation. See the \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"/accreditation_guide/\"\n }, \"Accreditation\\nGuide\"), \"\\nfor details of conducting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \".\"), mdx(\"h2\", null, \"Data Management\"), mdx(\"p\", null, \"How we collect and manage data is key to successful test execution.\\nEstablish a plan for data collection, storage, and analysis before you\\nbegin testing. Data management procedures describe methods of data\\ncollection, data control, verification, storage, and information\\nretrieval. Consider the following:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Collection.\"), \" You may need to train personnel how to use data\\ncollection tools (instrumentation). This includes data obtained from\\nthird parties (e.g., ranges, contractors) as well as instrumentation\\noperated directly by the test team. Data collectors should be familiar\\nwith the various data collection forms (paper or electronic). To prevent\\nloss of data, clearly label and duplicate it as soon as you collect it.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Quality Assurance and Control.\"), \" Verify data for quality and\\nquantity continuously. During the first level of verification, inspect\\ndata for content, format, and continuity. During the second level of\\nverification, compare recorded data to the data you expected to collect.\\nAs testing progresses, evaluate data continuously to determine whether\\nyou have collected and categorized a sufficient amount of data to answer\\nmeasures and COIs.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Filing and Storage.\"), \" Organize data so you can identify and\\nretrieve it easily. How you store test data will depend on the amount of\\ndata you need for a specific test, how often you obtain it, and how long\\nit takes to analyze and report it. The types of data storage vary from\\nsimple paper data collection forms to complex, relational databases, and\\nbig data techniques. Ensure you have data filing and storage needs in\\nplace before you begin executing tests.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Data Processing, Reduction, and Analysis.\"), \" Data processing and\\nreduction is how we handle data from its source to its input into the\\nactivity that reduces and analyzes it. These actions form the core of\\nthe data management system. The test team will monitor data analysis\\nwhile executing tests. Before testing, make sure data reduction tools,\\nand backup data reduction tools, are available and you have used them\\nduring an exercise before you execute your test.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Marking and Protecting Data.\"), \" Use the program security classification\\nguide (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \") to classify data properly prior to distribution. Ensure data\\nis marked appropriately for distribution. Carefully consider possible\\nconsequences of aggregating information from multiple sources.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Additional Data.\"), \" In addition to data required to answer measures, you\\nwill find the following forms of data useful or necessary:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"System configuration: As the system is developed, document the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s\\nconfiguration (software versions, hardware changes, control and\\ndisplay changes, etc.) for testing. This will help you determine\\nwhether additional testing is required because the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" or a portion\\nof the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is no longer operationally representative (or conversely,\\nit remains operationally representative).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Visual information documentation: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Documentation\"\n }, \"VIDOC\"), \", including still photos,\\nvideotape and related forms of imagery is one of the most versatile\\nways to collect data during test. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Documentation\"\n }, \"VIDOC\"), \" is recorded, as necessary,\\nfor analysis to illustrate test methods and results in briefings and\\nreports and for historical purposes.\"))), mdx(\"p\", null, \"A Data Management and Analysis Plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Management and Analysis Plan\"\n }, \"DMAP\"), \") is a tool that provides\\ndetailed procedures for the collection, reduction, quality assurance,\\ncollation, analysis, storage, and disposition of data.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Management and Analysis Plan\"\n }, \"DMAP\"), \", Joint Reliability and Maintainability Evaluation\\nTeam (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \"), Test Data Scoring Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Data Scoring Board\"\n }, \"TDSB\"), \"), data status matrix, dry\\nruns.\"), mdx(\"h2\", null, \"Detailed Test Procedures\"), mdx(\"p\", null, \"The test team writes and maintains detailed test procedures (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detailed Test Plan\"\n }, \"DTP\"), \"), which\\nare living documents that describe how they will execute a test. DTPs\\nare working-level reference documents that provide guidance to the test\\nteam on what to do for any test activity. They also provide an audit\\ntrail of planning decisions, rationale and records. DTPs are intended\\nfor use by the test team only and do not require external coordination.\\nHowever, there may be situations when the test site/range needs to\\nreview DTPs to ensure safety, security, and operational integrity.\"), mdx(\"h2\", null, \"Limitations\"), mdx(\"p\", null, \"Limitations affect the test team's ability to evaluate certain aspects\\nof a weapon system or to re-create certain aspects of the operational\\nenvironment. Limitations can be due to differences in the scenario\\n(operational versus test), test capabilities such as threat simulation,\\nrange restrictions (safety, physical airspace), specific test\\nmeasurement constraints, numbers of test articles, or the threat lay\\ndown (types and numbers). A limitation is something that inhibits our\\nability to accomplish a complete operational evaluation. Table 4-5\\ncontains examples of limitations.\"), mdx(\"p\", null, \"Table 4\\u20115. Limitations Example\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Limitation\"), mdx(\"th\", null, \"Mitigation\"), mdx(\"th\", null, \"Impact\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Limited MQ\\u20119 system availability\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Coordination with operational unit to share assets between the field training unit and IOT&E test;\")), mdx(\"li\", null, mdx(\"p\", null, \"Leverage combat missions\")))), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Inability to fully evaluate all measures;\")), mdx(\"li\", null, mdx(\"p\", null, \"Cybersecurity not evaluated\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Limited flight hours for reliability, maintainability and availability evaluation\"), mdx(\"td\", null, \"Use reliability availability logistics operations model\"), mdx(\"td\", null, \"Reported values may not reflect actual values in operational use\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Limited capability of Red Team to test weapon system via data link while in flight\"), mdx(\"td\", null, \"Coordinated with AFTC to emulate mission parameters in anechoic chamber to allow Red Team cyber attacks\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Cyber-exploitation effects not fully evaluated;\")), mdx(\"li\", null, mdx(\"p\", null, \"Inability to fully evaluate all measures\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Lack of threat systems at test facilities\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"Inability to report system effectiveness versus some threats\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"No integration of Lynx radar capability in mobile ground control station\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"Unable to evaluate Lynx synthetic aperture radar\")))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Mitigation\"), \". The test team must plan a way to mitigate the risk of each\\nlimitation to our evaluation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Mitigation must reduce the\\nimpact of the limitation enough to ensure our evaluation is still\\ncredible. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is one method you can use to mitigate a limitation.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Impact (of a Limitation after Mitigation)\"), \". The impact describes the\\nextent the limitation will (for a plan) or did (for a report) affect the\\nquality, completeness, and/or confidence of our evaluation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s\\neffectiveness and suitability. Our intent is to acknowledge limitations\\nand inform the decision maker and warfighter of the extent the\\nlimitations will or did affect our ability to report combat capability.\\nWe must state clearly what portions of the evaluation were affected by\\nthe impact.\"), mdx(\"p\", null, \"We may identify limitations at any point in a program. Of course, the\\nearlier we identify a limitation, the more likely it will be resolved.\\nWe must document limitations to provide justification for continued\\nimprovement and modernization of test capabilities, which will lead to\\nmore useful and relevant \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" reports and better systems being delivered\\nto the warfighter. Once we identify limitations, we carry them\\nthroughout all phases of the test program unless the program resolves\\nthem and they no longer apply.\"), mdx(\"h2\", null, \"Resourcing Test Events\"), mdx(\"p\", null, \"Test events, methodologies, and activities comprise the information we\\nuse to base the estimate of resources we need to execute operational\\ntests. Typically, resource estimates are documented in a test resource\\nplan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \").\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Adaptive, Relevant Testing.\"), \" Early in involvement, particular focus\\nis placed on the high cost (including high level of effort) and long\\nlead items. Typical examples of such items are threats,\\ninstrumentation, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" efforts.\")), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools\"), \": Test resource plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \"), requirements review board,\\nfinancial review board.\"), mdx(\"h2\", null, \"Technical Reviews\"), mdx(\"p\", null, \"The test team conducts a technical review for each test activity prior\\nto executing it. A technical review is not a planning or directing\\nsession; rather, it is a quality assurance step to verify the test team\\napplied adequate technical focus to test planning. A key tenet of\\ntechnical reviews is validating evolution of the test's goal, design,\\nmeasures, and capabilities. Test activities must be operationally\\nsufficient and technically adequate.\"), mdx(\"h2\", null, \"Test Plans\"), mdx(\"p\", null, \"A test plan documents, at a minimum, the first three aspects of an\\noperational test: 1) system under test; 2) test design; and 3) test\\nexecution. These form the core parts of a test plan. However, there are\\nnumerous forms of plans from simple \\\"one page\\\" plans to complex,\\nintricate plans that require extensive coordination. We tailor each test\\nplan to the particular test activity. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"See\"), \" Business Processes for\\nprocess, format, and coordination of test plans.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools\"), \": 2-letter reviews, technical reviews.\"), mdx(\"h2\", null, \"Administrative Considerations\"), mdx(\"p\", null, \"The Business Processes chapter discusses administrative topics such as\\nmemorandums of agreement (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \"), non-disclosure agreements, TRPs,\\nauthorities to operate (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Tasking Order OR Authority to Operate\"\n }, \"ATO\"), \"), etc.\"), mdx(\"h2\", null, \"Executing the Test\"), mdx(\"p\", null, \"Executing the test is unique to each test activity. This guide does not\\nattempt to tell a test team how to actually execute their tests, but the\\nfollowing are some common best practices across programs:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test readiness reviews\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Dry runs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Situation reports\"))), mdx(\"p\", null, \"See the Test Execution Guide for best practices on executing test\\nactivities in real time.\"), mdx(\"h1\", null, \"Analysis and Evaluation\"), mdx(\"h2\", null, \"Inspection\"), mdx(\"p\", null, \"An initial step in analyzing and evaluating the test is to inspect the\\ndata. This is a continuation of data management activities during\\nexecution. Inspect the quality and completeness of data, gaps in data,\\nunexpected or unusual values or results, how and when the test team\\ncollected data, what activities they used to collect data, and what\\nconditions they were under when they collected data. This is not an\\nall-inclusive list\", \"-\", \"-apply experience and judgement when you inspect\\ndata.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Analysis\"), \"-\", \"-Analyze data continuously throughout test execution. Do\\nnot view it as a separate, independent step.\")), mdx(\"h2\", null, \"Analysis\"), mdx(\"p\", null, \"Analysis begins with the data, data elements, and measures. The intent\\nis to analyze the data consistent with the goal of the test. In\\naddition, you should always perform exploratory analysis of unexpected\\nor unusual data, outliers, anomalies, additional observations, and\\nnotable findings.\"), mdx(\"p\", null, \"During first-order analysis, describe results, usually with descriptive\\nstatistics such as the average, mean, range, and variance of the data.\\nIn addition, describe conditions for results\", \"-\", \"-whether to characterize\\nor identify problems. If a data element or a measure has a threshold,\\nstate whether it met or did not meet the threshold.\"), mdx(\"p\", null, \"Although not required for operational evaluation, you may perform some\\ndegree of root-cause analysis. Describe conditions for the results as a\\nbridge to root-cause analysis. Root-cause analysis may include analyzing\\nprocesses and procedures, and explaining how conditions and events may\\nhave led up to a particular outcome.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Depth of Analysis\", \"-\", \"-\"), \"As part of an integrated team, we can provide\\ninsight into root-cause analysis, particularly from operations and\\nconditions. However, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" typically does not engage in detailed,\\nengineering and physics-based root cause analysis.\")), mdx(\"p\", null, \"Analyze COIs/operations data at the mission-effects level in preparation\\nfor evaluating results for COIs/operations. Also, analyze effectiveness\\nand suitability data in preparation for evaluating results for\\neffectiveness and suitability.\"), mdx(\"h2\", null, \"Evaluation\"), mdx(\"p\", null, \"During evaluation, analyze consequences and impacts of results, which\\nwill lead to determining whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can achieve combat capability.\"), mdx(\"p\", null, \"Analyze and draw conclusions about the impact or \\\"so what\\\" of each data\\nelement or measure's ability to achieve effects for an operation or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \".\\nDrawing on analysis for COIs/operations, evaluate the performance of\\neach \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or operation. Evaluate the \\\"so what\\\" in terms of the degree or\\naspects of accomplishment, as well as conditions and costs (not just\\ndollars) of the accomplishment.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"So What\", \"-\", \"-\"), \"The \\\"so what\\\" evaluation depends on what we are\\nevaluating. For data elements and MOPs/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \", the so what is relative to\\nachieving the measure of effect. For \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", the so what is relative to\\nconducting the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"/Operation.\")), mdx(\"h2\", null, \"Effectiveness and Suitability\"), mdx(\"p\", null, \"We include a determination of effectiveness and suitability in our final\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report. We base our evaluation on measure outcomes, and the\\nsignificance of identified effectiveness and suitability shortfalls and\\ntheir degree of operational impact. We also consider deficiency reports\\nand other observations based on operational experience to determine the\\ndegree of operational impact and operational effectiveness and\\nsuitability. We cannot determine effectiveness or suitability prior to\\nour final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report because, until then, we do not have all the\\nnecessary information to draw an overall conclusion for the entire \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"h2\", null, \"Reporting Ratings\"), mdx(\"p\", null, \"We evaluate and rate effectiveness, suitability, COIs, and measures. We\\nuse ratings to communicate results and operational impacts concisely. We\\ndepict ratings with colored indicators and define what each color means\\n(\", mdx(\"em\", {\n parentName: \"p\"\n }, \"see\"), \" Evaluation and Reporting Guide), or through narratives that\\naddress results, analysis, and our evaluation.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools.\"), \" Descriptive statistics, exploratory analysis, analysis\\nof variance, linear regression, root cause, etc.\"), mdx(\"h2\", null, \"Deficiency Reporting\"), mdx(\"p\", null, \"The Deficiency Reporting, Investigation and Resolution (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Referential Integrity\"\n }, \"DRI\"), \"&R) process\\npromotes the ability to identify and correct deficiencies in Air Force\\nsystems or equipment before they impact the mission. Successful\\nimplementation drives resolution decisions, tempered by total ownership\\ncost, to correct, mitigate and/or accept risk of conditions impacting\\noperational safety, suitability, and effectiveness. Success is based\\nupon the following two premises: (1) the user, operator or maintainer\\nwill report deficiencies on their assigned systems and (2) the program\\nmanager (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \") will establish a proactive process to analyze data and act\\naccordingly to implement solutions after coordination with the\\nuser/sponsor.\"), mdx(\"h2\", null, \"Exit Criteria Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assesses results of our test activities to determine whether we\\nfulfilled our exit criteria. Our assessment reveals whether we need to\\nexecute additional test activities or not. We must meet our exit\\ncriteria to accomplish our test reporting deliverables.\"), mdx(\"h1\", null, \"Conclusions and Documenting\"), mdx(\"p\", null, \"The purpose of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s test report is to communicate test results, our\\noperational evaluation of those results, and their impact to the\\nwarfighter (the \\\"so what\\\"). The test team reports results using various\\nformats and on different timelines depending on the test activity,\\npurpose, and external needs. Test reporting is impacted significantly by\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" principles. Depending on the nature of the program, reports may\\ninform specific milestones or releases of capability to the field, or\\nprovide progress/status to program offices or feedback to developers and\\ntesters.\"), mdx(\"p\", null, \"Continuous feedback during early and integrated testing is fundamental\\nto reporting operationally relevant discovery early and delivering\\ncapability at the speed of relevance. The test team provides continuous\\nfeedback in small, tailorable reports (e.g., operational finding\\nreports, status reports, significant event reports, periodic reports,\\nquick look briefs) during ongoing acquisition and developmental\\nactivities. The purpose of these reports varies, but in general they\\nprovide feedback on capabilities and limitations rather than on the\\nsystem's effectiveness and suitability. Short, effective reports inform\\nthe developer and the program manager of test results as fast as they\\noccur. Whether in a verbal or written narrative or briefing format, they\\ncommunicate operational findings identified by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test teams through\\nparticipation in early and continuous development activities. In order\\nto provide relevant information, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will provide continuous and\\ncumulative feedback to the program office and all stakeholders regarding\\nfindings.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Sample Tools\"), \". Rating taxonomies, evaluation and reporting guide.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#define-the-what","title":"Define the \"What\"","items":[{"url":"#system-under-test","title":"System Under Test"},{"url":"#measures","title":"Measures"},{"url":"#criteria-and-thresholds","title":"Criteria and Thresholds"},{"url":"#data-and-data-elements","title":"Data and Data Elements"},{"url":"#effectiveness-and-suitability","title":"Effectiveness and Suitability"},{"url":"#coi-operations-measures-data-hierarchy","title":"COI-Operations-Measures-Data Hierarchy"},{"url":"#conditions","title":"Conditions"},{"url":"#operational-capabilities","title":"Operational Capabilities"}]},{"url":"#test-design","title":"Test Design","items":[{"url":"#test-design-goal","title":"Test Design Goal"},{"url":"#test-designs","title":"Test Designs"}]},{"url":"#test-execution","title":"Test Execution","items":[{"url":"#test-capabilities","title":"Test Capabilities"},{"url":"#verification-validation-and-accreditation","title":"Verification, Validation, and Accreditation"},{"url":"#data-management","title":"Data Management"},{"url":"#detailed-test-procedures","title":"Detailed Test Procedures"},{"url":"#limitations","title":"Limitations"},{"url":"#resourcing-test-events","title":"Resourcing Test Events"},{"url":"#technical-reviews","title":"Technical Reviews"},{"url":"#test-plans","title":"Test Plans"},{"url":"#administrative-considerations","title":"Administrative Considerations"},{"url":"#executing-the-test","title":"Executing the Test"}]},{"url":"#analysis-and-evaluation","title":"Analysis and Evaluation","items":[{"url":"#inspection","title":"Inspection"},{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#effectiveness-and-suitability-1","title":"Effectiveness and Suitability"},{"url":"#reporting-ratings","title":"Reporting Ratings"},{"url":"#deficiency-reporting","title":"Deficiency Reporting"},{"url":"#exit-criteria-assessment","title":"Exit Criteria Assessment"}]},{"url":"#conclusions-and-documenting","title":"Conclusions and Documenting"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/4-4-building-the-ot-construct.md"},"frontmatter":{"metaTitle":"Building the OT&E Construct and Test Activities","metaDescription":"Building the OT&E Construct and Test 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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"569fa7a3-8313-5802-84bd-105136da21b7"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/5-test-lifecycle-exit/page-data.json b/sites/oteguide/page-data/OT&E_Guide/5-test-lifecycle-exit/page-data.json index fd289fb1..d3ebb84c 100644 --- a/sites/oteguide/page-data/OT&E_Guide/5-test-lifecycle-exit/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/5-test-lifecycle-exit/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"df270c7b-4f84-539a-a079-d3fadad09785"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"df270c7b-4f84-539a-a079-d3fadad09785"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/6-0-ot-business-practices/page-data.json b/sites/oteguide/page-data/OT&E_Guide/6-0-ot-business-practices/page-data.json index 74ee4f66..5c653666 100644 --- a/sites/oteguide/page-data/OT&E_Guide/6-0-ot-business-practices/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/6-0-ot-business-practices/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"48e1e761-73cd-59aa-8cde-8166a475e5bb"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"48e1e761-73cd-59aa-8cde-8166a475e5bb"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/6-1-1-tasking/page-data.json b/sites/oteguide/page-data/OT&E_Guide/6-1-1-tasking/page-data.json index c3baecde..9cb6bd65 100644 --- a/sites/oteguide/page-data/OT&E_Guide/6-1-1-tasking/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/6-1-1-tasking/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"20bd56bd-5943-5a4b-922f-f71eb7ca8a2b"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"20bd56bd-5943-5a4b-922f-f71eb7ca8a2b"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/6-1-2-team-standup/page-data.json b/sites/oteguide/page-data/OT&E_Guide/6-1-2-team-standup/page-data.json index 8fa30ff1..fbfa71d2 100644 --- a/sites/oteguide/page-data/OT&E_Guide/6-1-2-team-standup/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/6-1-2-team-standup/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"ad9c781a-9549-5d22-b383-547869f5fed7"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"ad9c781a-9549-5d22-b383-547869f5fed7"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/6-1-3-team-training/page-data.json b/sites/oteguide/page-data/OT&E_Guide/6-1-3-team-training/page-data.json index 3c633d25..9d14f291 100644 --- a/sites/oteguide/page-data/OT&E_Guide/6-1-3-team-training/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/6-1-3-team-training/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"11c599a2-b29d-54b9-b0e1-74929d1e6266"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"11c599a2-b29d-54b9-b0e1-74929d1e6266"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/6-2-risk-management/page-data.json b/sites/oteguide/page-data/OT&E_Guide/6-2-risk-management/page-data.json index f3b80cba..3d94d460 100644 --- a/sites/oteguide/page-data/OT&E_Guide/6-2-risk-management/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/6-2-risk-management/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"30d2e7cc-66ef-5a19-b4fe-1693c6c2b194"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"30d2e7cc-66ef-5a19-b4fe-1693c6c2b194"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/6-3-resources/page-data.json b/sites/oteguide/page-data/OT&E_Guide/6-3-resources/page-data.json index 2cb4a803..2fdc41ab 100644 --- a/sites/oteguide/page-data/OT&E_Guide/6-3-resources/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/6-3-resources/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"912205be-c578-5818-a620-3d648c16f8af"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"912205be-c578-5818-a620-3d648c16f8af"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/6-4-coordination-across-afotec/page-data.json b/sites/oteguide/page-data/OT&E_Guide/6-4-coordination-across-afotec/page-data.json index 1713dcf7..68c444c6 100644 --- a/sites/oteguide/page-data/OT&E_Guide/6-4-coordination-across-afotec/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/6-4-coordination-across-afotec/page-data.json @@ -1 +1 @@ -{"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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"7a8a0eda-6ef1-52d2-940b-21ffd416e153"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"7a8a0eda-6ef1-52d2-940b-21ffd416e153"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/6-5-continuous-and-cumulative-feedback/page-data.json b/sites/oteguide/page-data/OT&E_Guide/6-5-continuous-and-cumulative-feedback/page-data.json index 7ef453fa..2658354d 100644 --- a/sites/oteguide/page-data/OT&E_Guide/6-5-continuous-and-cumulative-feedback/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/6-5-continuous-and-cumulative-feedback/page-data.json @@ -1 +1 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ac819743-f69b-5156-a08d-29a3babcbc51","title":"Continuous and Cumulative Feedback","slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback"},"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\": \"Continuous and Cumulative Feedback\",\n \"metaTitle\": \"Continuous and Cumulative Feedback\",\n \"metaDescription\": \"Continuous and Cumulative Feedback\"\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 part of the Continuous and Cumulative Feedback principle, the test\\nteam provides timely feedback throughout the life of a program. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ncontinuously delivers timely, relevant information to developers,\\nprogram offices, and associated stakeholders regarding our current\\nfindings, data, or other relevant information as soon as it is\\navailable.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" testers maintain an atmosphere of openness when collecting test\\ndata, which contributes to an integrated approach. System contractors\\nand program office personnel may observe data collection at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"'s\\ndiscretion, and contractors may request formal release of data collected\\nthrough the program office. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" public law, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" personnel are\\nauthorized immediate access to raw test data collected by the test team\\nand support contractors.\"), mdx(\"p\", null, \"As early as possible prior to test, test teams are encouraged to share\\ntest plans/procedures and establish procedures and rules for data\\nsharing in an agreement (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" charter, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Understanding\"\n }, \"MOU\"), \", etc.). The agreement\\nspecifies what data the test team expects to collect and under what\\nconditions the contractor/program office may be present to observe test\\nevents. Parties establish ground rules for access (i.e., what data is\\nprovided and when), limitations (e.g., information subject to the Export\\nControl Act, Privacy Act, classified, source selection-sensitive,\\nproprietary restrictions, or not within data reduction capabilities) and\\nuse of raw data. The test team can only share data that is under\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s control. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" may not control or release data from sources\\nother than direct \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". TDs coordinate these rules/procedures with their\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" for approval and include procedures as part of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \" briefing.\\nCircumstances might prevent establishing procedures prior to test\\nexecution, so parties must agree upon ground rules before a test event\\ncommences.\"), mdx(\"p\", null, \"The toolbox lists various communication tools to convey important\\ninformation to the user, program office, or other key stakeholder\\ncommunities. It is fundamental that test teams use these communication\\ntools to provide continuous feedback during early and integrated\\ntesting, which ensures they report operationally relevant discovery\\nearly and deliver combat capability at the speed of relevance. The test\\nteam provides continuous feedback in small, tailorable reports (e.g.,\\noperational finding reports, status reports, significant event reports,\\nquick look briefs) during ongoing acquisition and developmental\\nactivities. The purpose of these reports varies, but in general they\\nprovide feedback on capabilities and limitations rather than on the\\nsystem's effectiveness and suitability. Short, effective reports provide\\nthe developer and program manager test results as fast as they occur.\\nReporting on trends the test team saw during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \" activities gives\\nthe program office lead time to address fixes that should be\\naccomplished before fielding the system. Whether in a written narrative\\nor a briefing format, they communicate operational findings identified\\nby \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test teams through participation in early and continuous\\ndevelopmental activities. When test teams report interim test results/\\ninformation, they must report only fact-based information and cannot\\nproject or speculate about the final evaluation of a system's\\noperational effectiveness and suitability. Final evaluations are\\nreserved for the final report itself. Report writers should also\\nexercise sound judgment when determining coordination requirements. Many\\ncommunication tools can be approved at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" level, others are\\napproved by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" after 2-ltr coord, and others are approved by the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" after 2-ltr coord. In most cases, test teams should consult\\nwith the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Staff prior to providing information to an\\nintended recipient.\"), mdx(\"h1\", null, \"Handling Information Requests\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" cannot establish firm guidelines that cover all situations in\\nwhich a test team might release test information. There are two basic\\ntypes of requests:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Data (test results)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Published plans/reports\"))), mdx(\"p\", null, \"Coordinate each request for test information with appropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" staff,\\nas described in Table 6-5. When the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" releases information, they are\\nacting under authority of 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\"), \" and must use caution and\\njudgment when answering questions and providing test information.\"), mdx(\"p\", null, \"Table 6\\u20115. Data/Information Release Guidance\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Requestor\"), mdx(\"th\", null, \"Procedure\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Congress or their representatives\"), mdx(\"td\", null, \"The AFOTEC/CC is the release authority and determines whether SECAF approval is required. If so, the reply is routed to the SECAF Legislative Liaison for release (Ref: AFI 90\\u2011401 \", mdx(\"em\", null, \"Air Force Relations with Congress\"), \", 14 Jun 12). Otherwise, the AFOTEC/CC determines release. If authorized, the Detachment releases the data directly to the requestor.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"GAO, OMB, DOD IG, audit agencies\"), mdx(\"td\", null, \"A-3 is the release authority. A\\u20117R is the action office/OPR for oversight visits. AFOTEC personnel cooperate as directed with agency representatives and, through A\\u20117R, gain CC authorization for release to keep the CC and staff informed (Ref: AFI 65\\u2011401, \", mdx(\"em\", null, \"Relations with the Government Accountability Office [GAO]\"), \", 16\\xA0Feb 16; AFI\\xA065\\u2011402, \", mdx(\"em\", null, \"Relations with the Department of Defense, Office of the Assistant Inspector Generals for Auditing, and Analysis and Follow Up\"), \", 19\\xA0Jul\\xA094)\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"OSD (except DOT&E)\"), mdx(\"td\", null, \"AFOTEC/CC is the release authority. OSD submits a request in writing to AF/TE. AF/TE in turn forwards the request to AFOTEC. AFOTEC sends response to AF/TE. AF/TE forwards response to OSD.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"DOT&E\"), mdx(\"td\", null, \"The TD may release only raw data (Level I and II data); the AFOTEC/CC is the release authority for final reports, results, or conclusions (Level III data). DOT&E may request and receive test data/documents directly from AFOTEC. The TD ensures markings are IAW information protection procedures for secondary release. The TD informs A\\u20113 of the request for Level I and II data and actions taken.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Other DoD Offices, Agencies, and Contractors\"), mdx(\"td\", null, \"Requests may come from an agency/office/government contractor with a need for the data. The TD ensures information protection procedures are followed and applicable release markings are applied.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOT&E\"), mdx(\"td\", null, \"Lead OTA procedures apply. Each participating OTA has the same and equal access to verified data as the lead OTA. Data is shared among the test team regardless of OTA affiliation, but is not released to other agencies prior to promulgation of the final test and evaluation report.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"FOIA Requests\"), mdx(\"td\", null, \"Public requests to inspect, review, or receive copies of USAF records are made IAW DoDD\\xA05400.7, \", mdx(\"em\", null, \"DoD Freedom of Information Act (FOIA) Program\"), \", 2\\xA0Jan\\xA015, as supplemented. The AFOTEC FOIA officer resides in A\\u20116.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Requests for Information (media)\"), mdx(\"td\", null, \"The AFOTEC public affairs office is the only release authority for all media requests IAW AFI\\xA035\\u2011104, \", mdx(\"em\", null, \"Media Operations\"), \", 13\\xA0Jul\\xA015.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Requests for Information (non\\u2011media)\"), mdx(\"td\", null, \"Requests for government information or records from the public that do not refer to the FOIA are forwarded to the AFOTEC FOIA officer for processing IAW DoD 5400.7.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Security and Policy Review\"), mdx(\"td\", null, \"PA is the clearance authority for any official DoD information intended for public release pertaining to military matters, national security issues, or subjects of significant concern to the DoD. Security and policy review ensures that material proposed for release does not contain classified material and does not conflict with established AF, DoD or U.S. Government policies. Information includes speeches, presentations, papers, multimedia material, material proposed for public release, and material publicly accessible on worldwide web sites. (Ref: DoDD 5230.9, \", mdx(\"em\", null, \"Clearance of DoD Information for Public Release,\"), \" 16 Mar 16; AFI\\xA035\\u2011101, \", mdx(\"em\", null, \"Public Affairs Responsibilities and Management\"), \", 12\\xA0Jan\\xA016)\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Foreign Disclosure\"), mdx(\"td\", null, \"A foreign government or international organization requesting test information must make an official request through its embassy to the appropriate USAF agency, i.e., SAF/IA, FMS desk, for release of test information. The request will be forwarded to the AFOTEC Command FDO for action. Ref: AFI\\xA016\\u2011201_AFGM2018\\u201101, \", mdx(\"em\", null, \"Air Force Foreign Disclosure and Technology Transfer Program\"), \", 1\\xA0Nov\\xA018, is the governing directive. Test information is not released to foreign governments or international organizations without approval of the AFOTEC Command FDO.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Classified Information\"), mdx(\"td\", null, \"Classified information is not releasable except as specified in Ref: DoD\\xA05200.1\\u2011M, \", mdx(\"em\", null, \"DoD Information Security Program\"), \", Vols 1\\u20114, and in AFI\\xA016-1404, \", mdx(\"em\", null, \"Air Force Information Security Program\"), \", 29\\xA0May\\xA015.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Source Selection\\u2011Sensitive OT&E Information\"), mdx(\"td\", null, \"AFOTEC/CC is the release authority. The request is coordinated through LC/PA prior to release. Data or information developed through OT&E that could influence a source selection process is protected as source selection\\u2011sensitive information according to DoDR 5400.7, as supplemented.\")))), mdx(\"h1\", null, \"Marking and Protecting Data\"), mdx(\"p\", null, \"Recipients of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" data are not authorized to reproduce and distribute\\nthat data without \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s permission. TDs must ensure that data\\nreleased prior to 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 approval of the final report is\\nmarked: \\\"Level I, II or III test data (as appropriate)\", \"-\", \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\nconclusions are not final, not for release or duplication without\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s permission.\\\" Use the program's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \" and consult the security\\nmanager to classify data properly prior to distribution.\"), mdx(\"h1\", null, \"Distribution Statements\"), mdx(\"p\", null, \"Distribution statements protect documents and are especially important\\nwhen time passes and the original test team members who produced the\\ndocuments are no longer around. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Freedom of Information Act\"\n }, \"FOIA\"), \" requests come in and management\\nmust release documents relying on the distribution statement assigned to\\nthe document at the time of its creation. Accordingly, address \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Security\"\n }, \"OPSEC\"), \"\\nconcerns when selecting the appropriate distribution statement. Refer\\nrequests for release of a published document to \", 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\"), \", and requests\\nfor release of a draft document to A-3. You can find information on the\\nappropriate distribution statement to use in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 61-201, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Management of\\nScientific and Technical Information (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Scientific and Technical Information\"\n }, \"STINFO\"), \")\"), \", 29\\xA0Jan\\xA016. Contact A-2/9\\nfor more information.\"), mdx(\"h1\", null, \"Test Program Case File\"), mdx(\"p\", null, \"The official test program case file is the repository for the final\\napproved records. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" must work with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"'s functional area\\nrecords manager (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Area Records Manager\"\n }, \"FARM\"), \") to ensure they store the \\\"cradle to grave\\\"\\nhistory of the test program in the test program case files. When it is\\ntime to close out the program, 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\": \"Functional Area Records Manager\"\n }, \"FARM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-6 records\\nmanager work together to transfer the complete official file to A-3. It\\nis important that TDs understand test program case files consist not\\nonly of records \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" creates, but also of records we receive for the\\nprogram.\"), mdx(\"h1\", null, \"Impact of System Modifications\"), mdx(\"p\", null, \"The test team must be cognizant of and understand modifications made to\\na system during developmental and operational testing. If \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ndetermines modifications (software modifications, hardware changes,\\ncontrol and display changes, etc.) made to a system could potentially\\nimpact its operational effectiveness or suitability, we will conduct\\nappropriate re-testing since new data will not be representative of\\nprevious data collected. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will coordinate changes 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\"), \"\\nand outline them in data management procedures to ensure differentiation\\nbetween old and new data sets. Discuss modifications made to a system\\n(and resultant impacts) between \", 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, or during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, in our\\nfinal report.\"), mdx(\"h1\", null, \"Visual Information Documentation\"), mdx(\"p\", null, \"Forward photos and videos of key test events to Multimedia Services\\n(CCJ) for use in command-level briefings, reports, publications, and\\npossible submission to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \". CCJ retains all original material in the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Documentation\"\n }, \"VIDOC\"), \" library. The visual information manager closely monitors the\\nprogress of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E programs through SharePoint and may contact test teams\\nto obtain these materials. TDs/teams must contact CCJ first for all\\ntheir \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Documentation\"\n }, \"VIDOC\"), \" needs, including equipment purchases and training.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#handling-information-requests","title":"Handling Information Requests"},{"url":"#marking-and-protecting-data","title":"Marking and Protecting Data"},{"url":"#distribution-statements","title":"Distribution Statements"},{"url":"#test-program-case-file","title":"Test Program Case File"},{"url":"#impact-of-system-modifications","title":"Impact of System Modifications"},{"url":"#visual-information-documentation","title":"Visual Information Documentation"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-5-continuous-and-cumulative-feedback.md"},"frontmatter":{"metaTitle":"Continuous and Cumulative Feedback","metaDescription":"Continuous and Cumulative Feedback"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"ac819743-f69b-5156-a08d-29a3babcbc51"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ac819743-f69b-5156-a08d-29a3babcbc51","title":"Continuous and Cumulative Feedback","slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback"},"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\": \"Continuous and Cumulative Feedback\",\n \"metaTitle\": \"Continuous and Cumulative Feedback\",\n \"metaDescription\": \"Continuous and Cumulative Feedback\"\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 part of the Continuous and Cumulative Feedback principle, the test\\nteam provides timely feedback throughout the life of a program. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ncontinuously delivers timely, relevant information to developers,\\nprogram offices, and associated stakeholders regarding our current\\nfindings, data, or other relevant information as soon as it is\\navailable.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" testers maintain an atmosphere of openness when collecting test\\ndata, which contributes to an integrated approach. System contractors\\nand program office personnel may observe data collection at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"'s\\ndiscretion, and contractors may request formal release of data collected\\nthrough the program office. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" public law, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" personnel are\\nauthorized immediate access to raw test data collected by the test team\\nand support contractors.\"), mdx(\"p\", null, \"As early as possible prior to test, test teams are encouraged to share\\ntest plans/procedures and establish procedures and rules for data\\nsharing in an agreement (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \" charter, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Understanding\"\n }, \"MOU\"), \", etc.). The agreement\\nspecifies what data the test team expects to collect and under what\\nconditions the contractor/program office may be present to observe test\\nevents. Parties establish ground rules for access (i.e., what data is\\nprovided and when), limitations (e.g., information subject to the Export\\nControl Act, Privacy Act, classified, source selection-sensitive,\\nproprietary restrictions, or not within data reduction capabilities) and\\nuse of raw data. The test team can only share data that is under\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s control. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" may not control or release data from sources\\nother than direct \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". TDs coordinate these rules/procedures with their\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" for approval and include procedures as part of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \" briefing.\\nCircumstances might prevent establishing procedures prior to test\\nexecution, so parties must agree upon ground rules before a test event\\ncommences.\"), mdx(\"p\", null, \"The toolbox lists various communication tools to convey important\\ninformation to the user, program office, or other key stakeholder\\ncommunities. It is fundamental that test teams use these communication\\ntools to provide continuous feedback during early and integrated\\ntesting, which ensures they report operationally relevant discovery\\nearly and deliver combat capability at the speed of relevance. The test\\nteam provides continuous feedback in small, tailorable reports (e.g.,\\noperational finding reports, status reports, significant event reports,\\nquick look briefs) during ongoing acquisition and developmental\\nactivities. The purpose of these reports varies, but in general they\\nprovide feedback on capabilities and limitations rather than on the\\nsystem's effectiveness and suitability. Short, effective reports provide\\nthe developer and program manager test results as fast as they occur.\\nReporting on trends the test team saw during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \" activities gives\\nthe program office lead time to address fixes that should be\\naccomplished before fielding the system. Whether in a written narrative\\nor a briefing format, they communicate operational findings identified\\nby \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test teams through participation in early and continuous\\ndevelopmental activities. When test teams report interim test results/\\ninformation, they must report only fact-based information and cannot\\nproject or speculate about the final evaluation of a system's\\noperational effectiveness and suitability. Final evaluations are\\nreserved for the final report itself. Report writers should also\\nexercise sound judgment when determining coordination requirements. Many\\ncommunication tools can be approved at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" level, others are\\napproved by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" after 2-ltr coord, and others are approved by the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" after 2-ltr coord. In most cases, test teams should consult\\nwith the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Staff prior to providing information to an\\nintended recipient.\"), mdx(\"h1\", null, \"Handling Information Requests\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" cannot establish firm guidelines that cover all situations in\\nwhich a test team might release test information. There are two basic\\ntypes of requests:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Data (test results)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Published plans/reports\"))), mdx(\"p\", null, \"Coordinate each request for test information with appropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" staff,\\nas described in Table 6-5. When the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" releases information, they are\\nacting under authority of 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\"), \" and must use caution and\\njudgment when answering questions and providing test information.\"), mdx(\"p\", null, \"Table 6\\u20115. Data/Information Release Guidance\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Requestor\"), mdx(\"th\", null, \"Procedure\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Congress or their representatives\"), mdx(\"td\", null, \"The AFOTEC/CC is the release authority and determines whether SECAF approval is required. If so, the reply is routed to the SECAF Legislative Liaison for release (Ref: AFI 90\\u2011401 \", mdx(\"em\", null, \"Air Force Relations with Congress\"), \", 14 Jun 12). Otherwise, the AFOTEC/CC determines release. If authorized, the Detachment releases the data directly to the requestor.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"GAO, OMB, DOD IG, audit agencies\"), mdx(\"td\", null, \"A-3 is the release authority. A\\u20117R is the action office/OPR for oversight visits. AFOTEC personnel cooperate as directed with agency representatives and, through A\\u20117R, gain CC authorization for release to keep the CC and staff informed (Ref: AFI 65\\u2011401, \", mdx(\"em\", null, \"Relations with the Government Accountability Office [GAO]\"), \", 16\\xA0Feb 16; AFI\\xA065\\u2011402, \", mdx(\"em\", null, \"Relations with the Department of Defense, Office of the Assistant Inspector Generals for Auditing, and Analysis and Follow Up\"), \", 19\\xA0Jul\\xA094)\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"OSD (except DOT&E)\"), mdx(\"td\", null, \"AFOTEC/CC is the release authority. OSD submits a request in writing to AF/TE. AF/TE in turn forwards the request to AFOTEC. AFOTEC sends response to AF/TE. AF/TE forwards response to OSD.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"DOT&E\"), mdx(\"td\", null, \"The TD may release only raw data (Level I and II data); the AFOTEC/CC is the release authority for final reports, results, or conclusions (Level III data). DOT&E may request and receive test data/documents directly from AFOTEC. The TD ensures markings are IAW information protection procedures for secondary release. The TD informs A\\u20113 of the request for Level I and II data and actions taken.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Other DoD Offices, Agencies, and Contractors\"), mdx(\"td\", null, \"Requests may come from an agency/office/government contractor with a need for the data. The TD ensures information protection procedures are followed and applicable release markings are applied.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOT&E\"), mdx(\"td\", null, \"Lead OTA procedures apply. Each participating OTA has the same and equal access to verified data as the lead OTA. Data is shared among the test team regardless of OTA affiliation, but is not released to other agencies prior to promulgation of the final test and evaluation report.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"FOIA Requests\"), mdx(\"td\", null, \"Public requests to inspect, review, or receive copies of USAF records are made IAW DoDD\\xA05400.7, \", mdx(\"em\", null, \"DoD Freedom of Information Act (FOIA) Program\"), \", 2\\xA0Jan\\xA015, as supplemented. The AFOTEC FOIA officer resides in A\\u20116.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Requests for Information (media)\"), mdx(\"td\", null, \"The AFOTEC public affairs office is the only release authority for all media requests IAW AFI\\xA035\\u2011104, \", mdx(\"em\", null, \"Media Operations\"), \", 13\\xA0Jul\\xA015.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Requests for Information (non\\u2011media)\"), mdx(\"td\", null, \"Requests for government information or records from the public that do not refer to the FOIA are forwarded to the AFOTEC FOIA officer for processing IAW DoD 5400.7.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Security and Policy Review\"), mdx(\"td\", null, \"PA is the clearance authority for any official DoD information intended for public release pertaining to military matters, national security issues, or subjects of significant concern to the DoD. Security and policy review ensures that material proposed for release does not contain classified material and does not conflict with established AF, DoD or U.S. Government policies. Information includes speeches, presentations, papers, multimedia material, material proposed for public release, and material publicly accessible on worldwide web sites. (Ref: DoDD 5230.9, \", mdx(\"em\", null, \"Clearance of DoD Information for Public Release,\"), \" 16 Mar 16; AFI\\xA035\\u2011101, \", mdx(\"em\", null, \"Public Affairs Responsibilities and Management\"), \", 12\\xA0Jan\\xA016)\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Foreign Disclosure\"), mdx(\"td\", null, \"A foreign government or international organization requesting test information must make an official request through its embassy to the appropriate USAF agency, i.e., SAF/IA, FMS desk, for release of test information. The request will be forwarded to the AFOTEC Command FDO for action. Ref: AFI\\xA016\\u2011201_AFGM2018\\u201101, \", mdx(\"em\", null, \"Air Force Foreign Disclosure and Technology Transfer Program\"), \", 1\\xA0Nov\\xA018, is the governing directive. Test information is not released to foreign governments or international organizations without approval of the AFOTEC Command FDO.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Classified Information\"), mdx(\"td\", null, \"Classified information is not releasable except as specified in Ref: DoD\\xA05200.1\\u2011M, \", mdx(\"em\", null, \"DoD Information Security Program\"), \", Vols 1\\u20114, and in AFI\\xA016-1404, \", mdx(\"em\", null, \"Air Force Information Security Program\"), \", 29\\xA0May\\xA015.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Source Selection\\u2011Sensitive OT&E Information\"), mdx(\"td\", null, \"AFOTEC/CC is the release authority. The request is coordinated through LC/PA prior to release. Data or information developed through OT&E that could influence a source selection process is protected as source selection\\u2011sensitive information according to DoDR 5400.7, as supplemented.\")))), mdx(\"h1\", null, \"Marking and Protecting Data\"), mdx(\"p\", null, \"Recipients of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" data are not authorized to reproduce and distribute\\nthat data without \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s permission. TDs must ensure that data\\nreleased prior to 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 approval of the final report is\\nmarked: \\\"Level I, II or III test data (as appropriate)\", \"-\", \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\nconclusions are not final, not for release or duplication without\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s permission.\\\" Use the program's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \" and consult the security\\nmanager to classify data properly prior to distribution.\"), mdx(\"h1\", null, \"Distribution Statements\"), mdx(\"p\", null, \"Distribution statements protect documents and are especially important\\nwhen time passes and the original test team members who produced the\\ndocuments are no longer around. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Freedom of Information Act\"\n }, \"FOIA\"), \" requests come in and management\\nmust release documents relying on the distribution statement assigned to\\nthe document at the time of its creation. Accordingly, address \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Security\"\n }, \"OPSEC\"), \"\\nconcerns when selecting the appropriate distribution statement. Refer\\nrequests for release of a published document to \", 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\"), \", and requests\\nfor release of a draft document to A-3. You can find information on the\\nappropriate distribution statement to use in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 61-201, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Management of\\nScientific and Technical Information (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Scientific and Technical Information\"\n }, \"STINFO\"), \")\"), \", 29\\xA0Jan\\xA016. Contact A-2/9\\nfor more information.\"), mdx(\"h1\", null, \"Test Program Case File\"), mdx(\"p\", null, \"The official test program case file is the repository for the final\\napproved records. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" must work with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"'s functional area\\nrecords manager (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Area Records Manager\"\n }, \"FARM\"), \") to ensure they store the \\\"cradle to grave\\\"\\nhistory of the test program in the test program case files. When it is\\ntime to close out the program, 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\": \"Functional Area Records Manager\"\n }, \"FARM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-6 records\\nmanager work together to transfer the complete official file to A-3. It\\nis important that TDs understand test program case files consist not\\nonly of records \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" creates, but also of records we receive for the\\nprogram.\"), mdx(\"h1\", null, \"Impact of System Modifications\"), mdx(\"p\", null, \"The test team must be cognizant of and understand modifications made to\\na system during developmental and operational testing. If \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ndetermines modifications (software modifications, hardware changes,\\ncontrol and display changes, etc.) made to a system could potentially\\nimpact its operational effectiveness or suitability, we will conduct\\nappropriate re-testing since new data will not be representative of\\nprevious data collected. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will coordinate changes 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\"), \"\\nand outline them in data management procedures to ensure differentiation\\nbetween old and new data sets. Discuss modifications made to a system\\n(and resultant impacts) between \", 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, or during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, in our\\nfinal report.\"), mdx(\"h1\", null, \"Visual Information Documentation\"), mdx(\"p\", null, \"Forward photos and videos of key test events to Multimedia Services\\n(CCJ) for use in command-level briefings, reports, publications, and\\npossible submission to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \". CCJ retains all original material in the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Documentation\"\n }, \"VIDOC\"), \" library. The visual information manager closely monitors the\\nprogress of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E programs through SharePoint and may contact test teams\\nto obtain these materials. TDs/teams must contact CCJ first for all\\ntheir \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Documentation\"\n }, \"VIDOC\"), \" needs, including equipment purchases and training.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#handling-information-requests","title":"Handling Information Requests"},{"url":"#marking-and-protecting-data","title":"Marking and Protecting Data"},{"url":"#distribution-statements","title":"Distribution Statements"},{"url":"#test-program-case-file","title":"Test Program Case File"},{"url":"#impact-of-system-modifications","title":"Impact of System Modifications"},{"url":"#visual-information-documentation","title":"Visual Information Documentation"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-5-continuous-and-cumulative-feedback.md"},"frontmatter":{"metaTitle":"Continuous and Cumulative Feedback","metaDescription":"Continuous and Cumulative Feedback"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"ac819743-f69b-5156-a08d-29a3babcbc51"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/6-6-acap/page-data.json b/sites/oteguide/page-data/OT&E_Guide/6-6-acap/page-data.json index 02fb8ffa..707ae81f 100644 --- a/sites/oteguide/page-data/OT&E_Guide/6-6-acap/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/6-6-acap/page-data.json @@ -1 +1 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-6-acap","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"fe9b9be0-0210-5e55-ae7c-3914388b15ed","title":"AFOTEC Collaborative Action Platform (ACAP)","slug":"/OT&E_Guide/6-6-acap"},"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\": \"AFOTEC Collaborative Action Platform (ACAP)\",\n \"metaTitle\": \"AFOTEC Collaborative Action Platform (ACAP)\",\n \"metaDescription\": \"AFOTEC Collaborative Action Platform (ACAP)\"\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, \"ACAP is an automated document coordination and suspense tracking system\\navailable on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet/Homepage/applications. Typically, the\\nsuspense for commenting and editing an ACAP tasker is 8 calendar days\\nafter submission. For classified documents, ACAP notifies reviewers to\\ncheck the appropriate classified network to coordinate the document.\"), mdx(\"h1\", null, \"2 Letter Coord of Air Force Operation Test and Evaluation Center-Produced Documents/Briefings (8 Work Days)\"), mdx(\"p\", null, \"2-ltr coord in ACAP is a formal process (shown in Figure 6-1) that an\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \", on behalf of their Director or Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \", initiates to obtain\\nother directorates' review and comments on their document. Before an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \"\\nsubmits 2-ltr taskers, they must comply with their internal coordination\\nprocess and receive their Director or Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s approval to do so.\"), mdx(\"p\", null, \"Figure 6\\u20111. 2-Ltr 8-Work Day Coord Process\"), 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\": \"977px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/f33d91fad1445b1d812c92f877cab611/339e3/image17.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.934362934362944%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAAA7DAAAOwwHHb6hkAAACQUlEQVQ4y4VTaW9SQRR9/z8xpjXaWmOBgm1TWYuAxkRU/GABaVkLFMq+lsJ7D3gsBY9nHksATfxwMjN35p67zLnSB2WGvyA/rffGZAEHwTgOQwm8r3bh7f/eut+FpF+usCJbwqPOYc5UdLLDcBLOB023bb3d8ZHEAxF16+FGpt4+4BsAXsKzS7JcdQ5xz1WytwawNRTYW/3tkv+HDTJbQ4XlrgZHewDJnK3iuf+nblhnuZnpv4g27MLnKJLG/o9fMN2WIFnrMl6HU7godxalqTNiDs/Kgc6bWNhW4Lk7gaszgqs9ZIZD9pBGF41OZY7zugJjroHTag9OeQZ7ZwwrYWD25uIDHLQ5+PasKuM4XYG5xCQKbbyhEjysVPyFdMmIn1oqUoMpYsoIN90B4oqGiDxCoK0gSntEHSOijPW9vyUj1p8gNXxCUpshnCki1OjAnynDzYAknMHX7iOqkowPr3tDxOgY7GkI0DnOfVTWeD/W8aUpI8y7aG/AoBpC2RKSTOB7vr4gFD0RWdq7UxzF83h1ncHBTRYWluimZGyPE7wIJlhWES6enb0pDNkaXoZvYco34aRKxGqj6NfCFp9gY/8MJLRQyKZUEe9yNb0nhngOzz4HsPftSv+4j0PA3lRxHLvjZ2g4Zx/3vl7hbSyHS/ZXWknB9TjWJ0JISIya0Kb4sNP7JowMcJzIw8qgurRoF8EExDjuB8IwJO43Ro8bN0s5K7RwwgxP0uUF4XKKhJx8y0lY6U+8F+eLSlfPTvgJnj/lA5sb9Y09agAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image17\",\n \"title\": \"image17\",\n \"src\": \"/static/f33d91fad1445b1d812c92f877cab611/339e3/image17.png\",\n \"srcSet\": [\"/static/f33d91fad1445b1d812c92f877cab611/a2ead/image17.png 259w\", \"/static/f33d91fad1445b1d812c92f877cab611/6b9fd/image17.png 518w\", \"/static/f33d91fad1445b1d812c92f877cab611/339e3/image17.png 977w\"],\n \"sizes\": \"(max-width: 977px) 100vw, 977px\",\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, mdx(\"strong\", {\n parentName: \"p\"\n }, \"4 Work Days:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" or DO approve products for submission into 2-ltr coord\\nand the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \" sends to their A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" receives the document and its associated briefing from the\\nDetachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \", and enters the products into 2-ltr coord, via an ACAP\\ntasker.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Assigned 2-ltr directorates review and comment within the 4-workday\\nsuspense.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" assumes configuration control of the document and briefing\\nand edits them with a \\\"find it/fix it\\\" methodology and track\\nchanges.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"1 Work Day:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" adjudicates directorates' comments entered into the comment\\nreview matrix (\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \") and updates document and briefing in ACAP via\\ntracked changes. \", mdx(\"em\", {\n parentName: \"li\"\n }, \"Note\"), \": A-3 \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" consults the Detachment test team\\nbefore incorporating substantive content changes into configuration\\ncontrol document and briefing.\")), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"2 Work Days:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \" reviews document and briefing for completeness and accuracy,\\nand ensures all comments were adjudicated.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" performs final edit.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"1 Work Day Release to \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" Coord:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 Director of Operations certifies documents are ready 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\"), \"'s approval and signature.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" enters documents into \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coord in ACAP.\"))), mdx(\"h1\", null, \"Commander/Executive Director Briefing Request\"), mdx(\"p\", null, \"After initiating 2-ltr coord, or 3 weeks prior to the desired briefing\\ndate (whichever comes first), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" must send a briefing request (the\\nform is posted on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet/Library/Job Aids and\\nGuides(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E)/Template) to the A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" and courtesy copy the A-3 workflow\\naccount. A-3 personnel will coordinate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"/Executive Director (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \")\\nbriefing, as applicable, with the Commander's Action Group (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group\"\n }, \"CAG\"), \"), and\\nnotify the Detachment if the desired briefing date is unavailable.\"), mdx(\"h1\", null, \"Command Section Coord Process (Maximum of 7 Work Days)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coord in ACAP is a formal process (shown in Figure 6-2) initiated to\\nobtain the Commander (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \") or Executive Director (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \") approval and/or\\nsignature for a document/briefing. A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coord tasker is either a\\ncontinuation of a 2-ltr coord tasker or an entirely new tasker.\"), mdx(\"p\", null, \"Figure 6\\u20112. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" 7-Work Day Coord Process\"), 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/cf99617231e01f6210357220e355297c/d7ba6/image18.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\": \"51.35135135135135%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAKCAYAAAC0VX7mAAAACXBIWXMAAA7DAAAOwwHHb6hkAAABzklEQVQoz2VSXVPaUBDl/784Y/XFqQwyU6AWSZGAr31QagVUYMa2gqhF5COEkIQAAfX07AUkjA9ndu/u3rPn7t2Qbs+RdV4/QLdfoA/n7zZLmzanOPjzD+FqHZ/Lt4g/9JBz3hZ1y9qQON+NMVJdV1mt5ylkAmTBC+FKHZ/OLrFLHD4ayI2waCgiaBXhUdvBl0aHXWuI1VrQmib0ga9UrbFQmWFccNwbIU0Rx6L65gFRKhe1ijDrvuHEmkHvjqAxmLZfoVlUToJY00X0zlJ+ijXKDmZIUESk3kG00UO8NYRmeKqhItRFLsnyTQNF7wUFx9+EO0NpNEeJuSL9fN9F0Z7itOXgJ+8V6GeHs/UMFSHn9uvJQMWb49qZokyisuvj0nRx3u4vYaLK/AVjBWuMa5twJrgYeNAtP0Aow+dcNHZLmj6O+lMkCXniIWN71Qa2zq4Q/vukRvG14yJpTNTTUzyLn7FWCgPrIUE1dOlGXxpovJzuT9Twc87yU2SWfFHsro3EfZf58ftGhDbWQ6z8KEdw8PsR26cl7OSvsPXjXJ1XNZKPkyjC343c3CPB9VkTLqVu7BuRfLbVKuxz7/YrNXxrWQjWCqnsoGC1g5L7D7kjyYXWJ+UKAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image18\",\n \"title\": \"image18\",\n \"src\": \"/static/cf99617231e01f6210357220e355297c/e3189/image18.png\",\n \"srcSet\": [\"/static/cf99617231e01f6210357220e355297c/a2ead/image18.png 259w\", \"/static/cf99617231e01f6210357220e355297c/6b9fd/image18.png 518w\", \"/static/cf99617231e01f6210357220e355297c/e3189/image18.png 1035w\", \"/static/cf99617231e01f6210357220e355297c/d7ba6/image18.png 1107w\"],\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, mdx(\"strong\", {\n parentName: \"p\"\n }, \"5 Work Days:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" enters the document and briefing into ACAP for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" personnel\\nreview, i.e., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group\"\n }, \"CAG\"), \" (office symbol-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group Office Symbol\"\n }, \"CCX\"), \") and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s Technical Advisor\\n(office symbol-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \"), with a minimum 5-workday suspense.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" adjudicates \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \" comments.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" incorporate administrative changes from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s\\nbriefing.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" coordinates content changes from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s briefing with\\nDetachment, and provides A\\u20113/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" narrative changes for incorporation\\ninto document and briefing.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" finalize the document and briefing.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"2 Work Days:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group\"\n }, \"CAG\"), \" personnel provide final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" version of documents to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" for review\\n2 work days prior to the briefing date.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Commander OR Capability Viewpoint\"\n }, \"CV\"), \" review, comment, and approve document and briefing.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" provides a soft copy of configuration control documents\\n(ACAP's final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" version) to the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \" so they can\\ncross-check content changes and prepare their briefing to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \".\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Post \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" Coord:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"If \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" requests plan/report briefing, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group\"\n }, \"CAG\"), \" schedules the\\nbriefing with \", 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\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" and sends approved briefing 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\"), \"\\nwho will forward it to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" distributes signed plan/report \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s \\\"Publication and\\nDistribution Process.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" posts published plans/reports and approved briefings to Test\\nManagement page.\"))), mdx(\"h1\", null, \"Other Product Review Processes\"), mdx(\"p\", null, \"Figure 6-3 shows the process for reviewing ISRs and status reports.\"), mdx(\"p\", null, \"Figure 6\\u20113. Process to Review ISRs and Status\\nReports\"), 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/51cdad38080f803a99b6a1ef92faae94/b94e3/image19.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.91505791505792%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAAA7DAAAOwwHHb6hkAAACgElEQVQoz22TaXPSUBSG+/+/OY6O26jVWtDWCqWb2IUMTVnSKoWwBbIQQiApISxVx9r6eIl174dn7pk79773vOecu5AaX7Ax+crGfI34yvrZjK3RJ970AmJth1XbZ8UakOiHbIr9pDcmFc7vXUbnI+axYOFFy2NJ84kZQ2JmwKvuhIQrLnYs3rRarGkasdIHVms1kobOjmOz3nVJ/RT5VzBujLgtGTwpD3hpzXjWHBO3zpHsKrvtD2Q6KttqjrR2wp5R5v2wyVbfYy2EzcnfYtcZDrlf6LJY9VjWZyzXulQDlSOziKQdsV+XSZ/ukWkccqQXyBsKzVGFjGeTCK/+E11Y1gPuyhZPKx4rvY+smH3KQZ2KX6bQUTioZ9kt73FQkyj1S6hnKlqosu+7JG8SjJshj05clprBteURinNKzclS6crU+3lOTQlVxNVejpKVperIbPsBqem3GyxrQx4UHRZVj7g54YUxYce2qfSPObGLETlN4tjK8b6rUHEVZKfKevD55qYsVgfc2m/z8Nghpo953p6y5fg0hiUKZh6lU0BuSihCUDHy1Acn5H1d2L38bfcPoqbcyZpRDZd1kaE2Im5fsNsqC3sS2ZpoSGmLw9ouxVYGxZRJDMZsTK9+ZbZ5TZThSyvktfuR1d45r+ypmMMxyeCSA69HwW+z0y6TNsTotE6RnAb5wGJjJOzO6ycEUoLk6ILE6Es0mwtLoob38l0elwaR6NpAWBavr08hOYGsLoRbHQ4bBnLDFPW0kNU6uWqDYqOForXRgxB3MkNyh8Jye/5TfhC3hqx5M5H+VfQNNwXprs87y+Wt2SM9J4pd3nUG0ZpxA/LhJ4qC9Nk53wFWh0iX7KuBAwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image19\",\n \"title\": \"image19\",\n \"src\": \"/static/51cdad38080f803a99b6a1ef92faae94/e3189/image19.png\",\n \"srcSet\": [\"/static/51cdad38080f803a99b6a1ef92faae94/a2ead/image19.png 259w\", \"/static/51cdad38080f803a99b6a1ef92faae94/6b9fd/image19.png 518w\", \"/static/51cdad38080f803a99b6a1ef92faae94/e3189/image19.png 1035w\", \"/static/51cdad38080f803a99b6a1ef92faae94/b94e3/image19.png 1126w\"],\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 6-4 shows the process for reviewing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \" reports.\"), mdx(\"p\", null, \"Figure 6\\u20114. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \" Product Review\"), 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/952e46dab0e112cb3b8f384611e0f7a2/bb2fd/image20.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\": \"64.47876447876449%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAAA7DAAAOwwHHb6hkAAAC7UlEQVQ4y02T21IiVxSGecrkDfIouU9VJkmlypqME40o4wEPk8ixaU4DM4iogDTHBrpbuoEGRJwZ9cvqNjG5+GuvtS/W/g9rBw7dL+zbK8KTew6nn6W+IzRcSC29+0B4DuHpV/5aPLBnuoT6DifuPSezBw7cJw7nTxy5XzmS3kNgs2XzU7bNz4KN5ogNzea3S5PN9piwNSPmjIgYfTJ2n+N6mf1KAcXskLB0Tk2D07HL4ezxeagg8PrC4MdUix9iDV5fDNkZzAn2XLZ6c3bbI/JmjWizLDjntFEiop0Ra1WItSuovQope0B49vTfwJ2hy569ZLPl4A3fbDocjO8IyuAdbYTaKpLUCj6i1QzxWvafvkhKyxMzeiKbF9mBvdFS/PrCO/OWbX0mDMW/yWdC5pJ9fUy5/4EPjQTFpkKuFiNbjZKrx+UuyVlbIT0e+gyP/2W4ay38QLZ1kdmd+ghPVoQMkd6do7ZLpOoplOsMyVrKR1rLkaynyWlp/rTF6/976A3ctZYv3m33Zz7b0HAm9ZLEsEehqZK+lkH1JLlGinwzQ16Ts3/OydRL/EnwyLEnOSQe/iGJbnUmkrLj1xuaI73c6SuO5MGPeoGUMExcKSSrygs75abHtqxayBG/nQV70xWBdyJtq+Mxe2YY7HoPTOUU9Fe8N0Z8aqtkhVmmliArLLMNVfyME+2e8Z2h8m05yDfXu3xvX8tAc4Yne6Np86ZqsV6zRK7n34T1xpL3usW5nkW5jKNcREhWIn5d1JLkjSvWRg5r5pC1G5OtyZxAsDeWAGas103Wyjq/Nyz2nVu8+7faLQljwOX4iky3RKJZJC5QOiVKdpWPk7bv3cktHC8E4mXAk/pK7fBLXhfZLm9rNr8WBr78g/H985eS9MKyWlHLJTqwifRtOR2/jhkOyRuXtD0nOrkj4P3dN1c3stATPPlBfep/P2/hD8YrefXRH+r9Z7U7lJRbkniLTKONWtPEzzafdIOqZZORYP4Gsn6H/DHvPnoAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image20\",\n \"title\": \"image20\",\n \"src\": \"/static/952e46dab0e112cb3b8f384611e0f7a2/e3189/image20.png\",\n \"srcSet\": [\"/static/952e46dab0e112cb3b8f384611e0f7a2/a2ead/image20.png 259w\", \"/static/952e46dab0e112cb3b8f384611e0f7a2/6b9fd/image20.png 518w\", \"/static/952e46dab0e112cb3b8f384611e0f7a2/e3189/image20.png 1035w\", \"/static/952e46dab0e112cb3b8f384611e0f7a2/bb2fd/image20.png 1058w\"],\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 6-5 shows the process for reviewing a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-led\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \".\"), mdx(\"p\", null, \"Figure 6\\u20115. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" Review for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-led \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \"\"), 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/04e965d0b9fddd09d1dcbd8dc14bb15c/fd84e/image21.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\": \"60.61776061776062%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAAA7DAAAOwwHHb6hkAAAClUlEQVQoz01TaVPaUBTl//+AfutMl6lVtOzoqBiRLQkJa4clSICEkIWQEBChWvX05sVx+uHMufdlcubcLfZ9ZOCT0MG3oYb89hXZ4AUF18GtM8ftckEwGHO2gRub3hwD3NJCLviL7OaVcW7z8oFYfO7jWHNxons4377gar2DsmpDtcpoqzfoTm4gDy8YN++voTpVjFcSCn5AYs+R0H+iJOjhc2eEo6mLhLZAyx1CMLqoqgKEWR014vKoQrEEUZPAT0Xw9P13oJLoGpng3eU7YmeLAGHZodOks0PCPYAzp+xHUW+iNpVwp1TAz+QI9F62VHLzyhzlt2/IP7whR8wc/rK2iBs+zhZregQK2z3GXhONyR1k9Q4NAj+4hjQuQrovQp6UoLoiuGCDjPcHaXOF1GKFjO0j7+8RSzgPSLl7JOwHNpCst0dK6SM57DGEcbzbfM/7LM+Oh/gx0nDpbXBlznHUbKDgWCg+PkUOw5JPyWV8sUHeWqJhdlCdNSAabfBaE9VJHbzeYnlNa7FWcN6K9ewiIJfOFufBE/KE2JlJPVTmOKXhxK1HlJZzjBwBA0dC3xIhKBzqIwKV29Yq9FaHYvOQfA0p7xlpy0PaDojXVN0BsRN9ha+DGY4mNrL+Abe2jmxPRnbYYUh0ZRxLFaT7LWQGbeSULnL9BuVNXLkuLk2DSpbB0e5yu6doDz937vFz5iJJzeXmCkrzHmSNpjwTUSfmxxXUKRanAmS9jqrRQ8me4trf4Hx9YO4u1vuo5FOa7pf+DKHTMD42d+AWKgkKqI5rEEikOiqDnwgM4qSGiq0iQxvBhhhEqxNyjhBLLh/ZQBK0g2nqQYgbx0TR0encdDo1nbUhiun0bA0cnV/o5uNK2KVE+AcLc0fpg+v55AAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image21\",\n \"title\": \"image21\",\n \"src\": \"/static/04e965d0b9fddd09d1dcbd8dc14bb15c/e3189/image21.png\",\n \"srcSet\": [\"/static/04e965d0b9fddd09d1dcbd8dc14bb15c/a2ead/image21.png 259w\", \"/static/04e965d0b9fddd09d1dcbd8dc14bb15c/6b9fd/image21.png 518w\", \"/static/04e965d0b9fddd09d1dcbd8dc14bb15c/e3189/image21.png 1035w\", \"/static/04e965d0b9fddd09d1dcbd8dc14bb15c/fd84e/image21.png 1056w\"],\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 6-6 shows the process for reviewing a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" for a non-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \".\"), mdx(\"p\", null, \"Figure 6\\u20116. Non-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" Review\"), 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/764d67a66acd1cbd239b2603ce02fe6a/4ef40/image22.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\": \"61.003861003861005%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAAA7DAAAOwwHHb6hkAAACm0lEQVQoz2WTWXPaShSE/f/f83YfknuTVEK8A4qNwGBWs5gtLJZkMAIJIYEsycYLtpMvg3AlqdyHrjk6mjrT092z9WFg8easxX/KhKj3RCx4QfIeke0p8uwVtkXyFfLM5NgNwn0x/3mDdf2KrfeayT9NlX8vxhy6j0QDSPh3jN0zOqMT2sMknauUgKgFJosCNd9gX+yL/zUsHLjnLPmsL9izl0QMn0PbJ29pZCYXZKcqOQF50OLUVEiHPY2C2SfpuuLw779ZvmJrd3bLmuWOdSMQsOM8kDY0ynqNitHibFwnq5UoG03OJo3wuzhpE3fvBaPv/2f4xfB419cFyzlfrFvk+RzFqdKbnNLRT2kOUtSU43Bdo2/kUKZ5zgOT/WuhudA75q3E9Z+EByu2Nsw27A68F5Jzh3OzQWFUJzeskejmOWpnSHRypLUyRb1OTfxP6x1kf8meqhLp9fhqGsjBw3pgEDq8bXpEzICjkYb0rUDsW4mkds5Rv0y8nedYrAmlhtQpIXXLHLSK5B8e+Wov2NaGZJb3JJdPa1PuiExc9oU5kdkdVUflyjpl4JTQrDzNS5mGeizcTtHV02FvMM2izutEbY9dy+fADtidXnO4uN9o+LZ7xaeRw/ZsiTTRObk8J6lUBKpEm1kO6xlirVzIUr4oczKoIyktMr6PNB6x3euScmakbsWVI8Z1aMrHoR2e9tleUXSGqEL4jlWhbZSoaGnqozx9u0bPEH27ERqSuFkh2ddELsdhdo8CYcquyN8n4XBozDRgLUF05lFeXKH7dTpGkYqSpDUuMHSrqDcil94tUiBc9V/C6MRvfoT1GptgjxfhwHW4D4QOO/MV8sLlIlBpOD2ygyoVs00/UKiJuOx5P4j/+fR+PcFnfgIod0nDK59oTAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image22\",\n \"title\": \"image22\",\n \"src\": \"/static/764d67a66acd1cbd239b2603ce02fe6a/e3189/image22.png\",\n \"srcSet\": [\"/static/764d67a66acd1cbd239b2603ce02fe6a/a2ead/image22.png 259w\", \"/static/764d67a66acd1cbd239b2603ce02fe6a/6b9fd/image22.png 518w\", \"/static/764d67a66acd1cbd239b2603ce02fe6a/e3189/image22.png 1035w\", \"/static/764d67a66acd1cbd239b2603ce02fe6a/4ef40/image22.png 1057w\"],\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, \"Things to Consider when Producing Documents for Coordination/Review\"), mdx(\"p\", null, \"Depending on the type of document and level of review required, the\\nstaffing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" can be an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \" from a Detachment or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \". Some ACAP taskers\\nstaff a final, approved document for informational purposes only. POCs\\nmust consider the following requirements when staffing a product for\\nreview and approval.\"), mdx(\"h2\", null, \"Drafting Plans/Reports and Briefings:\"), mdx(\"p\", null, \"The test team should develop the plan/report and associated briefing\\nwith active support from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" experts (A-3 cybersecurity test and\\nstandardization/format, A-2/9 analysis and test design, A-5/8 policy\\nreview). They should involve \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" AOs early by hosting regular reviews of\\ndraft documents and analysis (via email or telecom) to achieve faster\\ncoordination and issue resolution.\"), mdx(\"p\", null, \"The Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" maintains configuration control of documents\\nthroughout all phases of Detachment coord until they release the\\ndocuments to A-3 for 2-ltr coord in ACAP. Throughout 2-ltr and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coord,\\nthe A-3/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" assumes configuration control, integrates changes, and\\nprovides format continuity when multiple agencies/personnel coordinate\\ndocuments in parallel.\"), mdx(\"h2\", null, \"Actionable Comments\"), mdx(\"p\", null, \"The deliverable for some taskers is a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \". Although \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \" formats vary\\namongst organizations and Services, the basic intent is the same\", \"-\", \"-to\\nprovide actionable comments with supporting rationale. The document's\\nreviewer (comment originator) and the staffing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" (staffing lead's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \")\\nprovide actionable comments \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" their specific responsibilities.\\nDocument reviewers must provide sufficient information in the required\\nformat. If they do not, the staffing lead will adjudicate comments,\\nincluding rewriting them, to obtain approval to release the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \" to\\nexternals. Prior to release, CRMs must contain:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Comments that are actionable, respectful, acceptable, appropriate,\\nreasonable, and most of all release-ready. The staff lead should be\\nable to \\\"cut and paste\\\" rather than spend time trying to discern a\\nreviewer's intent.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \" attachments with proper classification markings.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"No duplicate comments, nor comments intended for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" only.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Comments organized in page order of the document being reviewed.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Adjudicated comments when there are disagreements within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Adjudicated comments that meet expected requirements for sufficiency\\nand format when the originator did not meet those expectations.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Clearly referenced attachments linked to specific comments.\"))), mdx(\"h2\", null, \"Meeting External Suspenses\"), mdx(\"p\", null, \"TDs must manage their test program to produce strategies, plans, and\\nreports that ensure maximum impact and usefulness to the warfighter,\\nprogram office, and developmental teams.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Plans: Plans must be signed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"No or Not Later Than\"\n }, \"NLT\"), \" 60 days prior to test start to meet\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" test adequacy determination (Ref: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 99-103,\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Capabilities-Based Test and Evaluation\"), \", Atch 2, Table A2.1).\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s standard 60-day suspense also applies to plans that are not\\non \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" oversight.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Reports: Final reports must be completed and signed 45 days, or\\nsooner, prior to acquisition decision. A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" must begin writing the\\nfinal report as far in advance of the last test event (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Last Test Event\"\n }, \"LTE\"), \") as\\npractical, because staff personnel need time between the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Last Test Event\"\n }, \"LTE\"), \" and\\n2-ltr coord to refine the report's analysis, conclusions, and\\noverall quality.\"))), mdx(\"h1\", null, \"Accreditation Plans/Reports\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" will send accreditation plans/reports to the A-2/9 workflow\\naccounts. The A-2/9 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will put the accreditation plans/reports into\\n2-ltr \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Entry Control System OR AFOTEC Electronic Coordination System\"\n }, \"AECS\"), \" coordination for 5 days and adjudicate all comments. Upon\\ncompletion, the A-2/9 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will put the accreditation plans/reports into\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coordination for review and signature by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \".\"), mdx(\"h1\", null, \"Joint Reliability, Maintainability Evaluation Team Charters\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" will send the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \" Charter to the A-3 workflow account. The A-3\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will put the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \" Charter, which is a sub group of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" that\\nevaluates data and how data is scored, into 2-ltr \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Entry Control System OR AFOTEC Electronic Coordination System\"\n }, \"AECS\"), \" coordination for\\n5 days and adjudicate all comments. Upon completion, the A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will\\nsend the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \" Charter back to the Detachment for Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"\\nsignature.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#2-letter-coord-of-air-force-operation-test-and-evaluation-center-produced-documentsbriefings-8-work-days","title":"2 Letter Coord of Air Force Operation Test and Evaluation Center-Produced Documents/Briefings (8 Work Days)"},{"url":"#commanderexecutive-director-briefing-request","title":"Commander/Executive Director Briefing Request"},{"url":"#command-section-coord-process-maximum-of-7-work-days","title":"Command Section Coord Process (Maximum of 7 Work Days)"},{"url":"#other-product-review-processes","title":"Other Product Review Processes"},{"url":"#things-to-consider-when-producing-documents-for-coordinationreview","title":"Things to Consider when Producing Documents for Coordination/Review","items":[{"url":"#drafting-plansreports-and-briefings","title":"Drafting Plans/Reports and Briefings:"},{"url":"#actionable-comments","title":"Actionable Comments"},{"url":"#meeting-external-suspenses","title":"Meeting External Suspenses"}]},{"url":"#accreditation-plansreports","title":"Accreditation Plans/Reports"},{"url":"#joint-reliability-maintainability-evaluation-team-charters","title":"Joint Reliability, Maintainability Evaluation Team Charters"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-6-acap.md"},"frontmatter":{"metaTitle":"AFOTEC Collaborative Action Platform (ACAP)","metaDescription":"AFOTEC Collaborative Action Platform (ACAP)"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"fe9b9be0-0210-5e55-ae7c-3914388b15ed"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-6-acap","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"fe9b9be0-0210-5e55-ae7c-3914388b15ed","title":"AFOTEC Collaborative Action Platform (ACAP)","slug":"/OT&E_Guide/6-6-acap"},"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\": \"AFOTEC Collaborative Action Platform (ACAP)\",\n \"metaTitle\": \"AFOTEC Collaborative Action Platform (ACAP)\",\n \"metaDescription\": \"AFOTEC Collaborative Action Platform (ACAP)\"\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, \"ACAP is an automated document coordination and suspense tracking system\\navailable on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet/Homepage/applications. Typically, the\\nsuspense for commenting and editing an ACAP tasker is 8 calendar days\\nafter submission. For classified documents, ACAP notifies reviewers to\\ncheck the appropriate classified network to coordinate the document.\"), mdx(\"h1\", null, \"2 Letter Coord of Air Force Operation Test and Evaluation Center-Produced Documents/Briefings (8 Work Days)\"), mdx(\"p\", null, \"2-ltr coord in ACAP is a formal process (shown in Figure 6-1) that an\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \", on behalf of their Director or Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \", initiates to obtain\\nother directorates' review and comments on their document. Before an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \"\\nsubmits 2-ltr taskers, they must comply with their internal coordination\\nprocess and receive their Director or Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s approval to do so.\"), mdx(\"p\", null, \"Figure 6\\u20111. 2-Ltr 8-Work Day Coord Process\"), 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\": \"977px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/f33d91fad1445b1d812c92f877cab611/339e3/image17.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.934362934362944%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAAA7DAAAOwwHHb6hkAAACQUlEQVQ4y4VTaW9SQRR9/z8xpjXaWmOBgm1TWYuAxkRU/GABaVkLFMq+lsJ7D3gsBY9nHksATfxwMjN35p67zLnSB2WGvyA/rffGZAEHwTgOQwm8r3bh7f/eut+FpF+usCJbwqPOYc5UdLLDcBLOB023bb3d8ZHEAxF16+FGpt4+4BsAXsKzS7JcdQ5xz1WytwawNRTYW/3tkv+HDTJbQ4XlrgZHewDJnK3iuf+nblhnuZnpv4g27MLnKJLG/o9fMN2WIFnrMl6HU7godxalqTNiDs/Kgc6bWNhW4Lk7gaszgqs9ZIZD9pBGF41OZY7zugJjroHTag9OeQZ7ZwwrYWD25uIDHLQ5+PasKuM4XYG5xCQKbbyhEjysVPyFdMmIn1oqUoMpYsoIN90B4oqGiDxCoK0gSntEHSOijPW9vyUj1p8gNXxCUpshnCki1OjAnynDzYAknMHX7iOqkowPr3tDxOgY7GkI0DnOfVTWeD/W8aUpI8y7aG/AoBpC2RKSTOB7vr4gFD0RWdq7UxzF83h1ncHBTRYWluimZGyPE7wIJlhWES6enb0pDNkaXoZvYco34aRKxGqj6NfCFp9gY/8MJLRQyKZUEe9yNb0nhngOzz4HsPftSv+4j0PA3lRxHLvjZ2g4Zx/3vl7hbSyHS/ZXWknB9TjWJ0JISIya0Kb4sNP7JowMcJzIw8qgurRoF8EExDjuB8IwJO43Ro8bN0s5K7RwwgxP0uUF4XKKhJx8y0lY6U+8F+eLSlfPTvgJnj/lA5sb9Y09agAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image17\",\n \"title\": \"image17\",\n \"src\": \"/static/f33d91fad1445b1d812c92f877cab611/339e3/image17.png\",\n \"srcSet\": [\"/static/f33d91fad1445b1d812c92f877cab611/a2ead/image17.png 259w\", \"/static/f33d91fad1445b1d812c92f877cab611/6b9fd/image17.png 518w\", \"/static/f33d91fad1445b1d812c92f877cab611/339e3/image17.png 977w\"],\n \"sizes\": \"(max-width: 977px) 100vw, 977px\",\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, mdx(\"strong\", {\n parentName: \"p\"\n }, \"4 Work Days:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" or DO approve products for submission into 2-ltr coord\\nand the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \" sends to their A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" receives the document and its associated briefing from the\\nDetachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \", and enters the products into 2-ltr coord, via an ACAP\\ntasker.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Assigned 2-ltr directorates review and comment within the 4-workday\\nsuspense.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" assumes configuration control of the document and briefing\\nand edits them with a \\\"find it/fix it\\\" methodology and track\\nchanges.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"1 Work Day:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" adjudicates directorates' comments entered into the comment\\nreview matrix (\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \") and updates document and briefing in ACAP via\\ntracked changes. \", mdx(\"em\", {\n parentName: \"li\"\n }, \"Note\"), \": A-3 \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" consults the Detachment test team\\nbefore incorporating substantive content changes into configuration\\ncontrol document and briefing.\")), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"2 Work Days:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \" reviews document and briefing for completeness and accuracy,\\nand ensures all comments were adjudicated.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" performs final edit.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"1 Work Day Release to \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" Coord:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 Director of Operations certifies documents are ready 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\"), \"'s approval and signature.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" enters documents into \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coord in ACAP.\"))), mdx(\"h1\", null, \"Commander/Executive Director Briefing Request\"), mdx(\"p\", null, \"After initiating 2-ltr coord, or 3 weeks prior to the desired briefing\\ndate (whichever comes first), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" must send a briefing request (the\\nform is posted on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet/Library/Job Aids and\\nGuides(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E)/Template) to the A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" and courtesy copy the A-3 workflow\\naccount. A-3 personnel will coordinate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"/Executive Director (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \")\\nbriefing, as applicable, with the Commander's Action Group (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group\"\n }, \"CAG\"), \"), and\\nnotify the Detachment if the desired briefing date is unavailable.\"), mdx(\"h1\", null, \"Command Section Coord Process (Maximum of 7 Work Days)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coord in ACAP is a formal process (shown in Figure 6-2) initiated to\\nobtain the Commander (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \") or Executive Director (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \") approval and/or\\nsignature for a document/briefing. A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coord tasker is either a\\ncontinuation of a 2-ltr coord tasker or an entirely new tasker.\"), mdx(\"p\", null, \"Figure 6\\u20112. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" 7-Work Day Coord Process\"), 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/cf99617231e01f6210357220e355297c/d7ba6/image18.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\": \"51.35135135135135%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAKCAYAAAC0VX7mAAAACXBIWXMAAA7DAAAOwwHHb6hkAAABzklEQVQoz2VSXVPaUBDl/784Y/XFqQwyU6AWSZGAr31QagVUYMa2gqhF5COEkIQAAfX07AUkjA9ndu/u3rPn7t2Qbs+RdV4/QLdfoA/n7zZLmzanOPjzD+FqHZ/Lt4g/9JBz3hZ1y9qQON+NMVJdV1mt5ylkAmTBC+FKHZ/OLrFLHD4ayI2waCgiaBXhUdvBl0aHXWuI1VrQmib0ga9UrbFQmWFccNwbIU0Rx6L65gFRKhe1ijDrvuHEmkHvjqAxmLZfoVlUToJY00X0zlJ+ijXKDmZIUESk3kG00UO8NYRmeKqhItRFLsnyTQNF7wUFx9+EO0NpNEeJuSL9fN9F0Z7itOXgJ+8V6GeHs/UMFSHn9uvJQMWb49qZokyisuvj0nRx3u4vYaLK/AVjBWuMa5twJrgYeNAtP0Aow+dcNHZLmj6O+lMkCXniIWN71Qa2zq4Q/vukRvG14yJpTNTTUzyLn7FWCgPrIUE1dOlGXxpovJzuT9Twc87yU2SWfFHsro3EfZf58ftGhDbWQ6z8KEdw8PsR26cl7OSvsPXjXJ1XNZKPkyjC343c3CPB9VkTLqVu7BuRfLbVKuxz7/YrNXxrWQjWCqnsoGC1g5L7D7kjyYXWJ+UKAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image18\",\n \"title\": \"image18\",\n \"src\": \"/static/cf99617231e01f6210357220e355297c/e3189/image18.png\",\n \"srcSet\": [\"/static/cf99617231e01f6210357220e355297c/a2ead/image18.png 259w\", \"/static/cf99617231e01f6210357220e355297c/6b9fd/image18.png 518w\", \"/static/cf99617231e01f6210357220e355297c/e3189/image18.png 1035w\", \"/static/cf99617231e01f6210357220e355297c/d7ba6/image18.png 1107w\"],\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, mdx(\"strong\", {\n parentName: \"p\"\n }, \"5 Work Days:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" enters the document and briefing into ACAP for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" personnel\\nreview, i.e., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group\"\n }, \"CAG\"), \" (office symbol-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group Office Symbol\"\n }, \"CCX\"), \") and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s Technical Advisor\\n(office symbol-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \"), with a minimum 5-workday suspense.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" adjudicates \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \" comments.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" incorporate administrative changes from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s\\nbriefing.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" coordinates content changes from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s briefing with\\nDetachment, and provides A\\u20113/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" narrative changes for incorporation\\ninto document and briefing.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" finalize the document and briefing.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"2 Work Days:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group\"\n }, \"CAG\"), \" personnel provide final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" version of documents to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" for review\\n2 work days prior to the briefing date.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Commander OR Capability Viewpoint\"\n }, \"CV\"), \" review, comment, and approve document and briefing.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" provides a soft copy of configuration control documents\\n(ACAP's final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" version) to the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \" so they can\\ncross-check content changes and prepare their briefing to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \".\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Post \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" Coord:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"If \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" requests plan/report briefing, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group\"\n }, \"CAG\"), \" schedules the\\nbriefing with \", 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\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" and sends approved briefing 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\"), \"\\nwho will forward it to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" distributes signed plan/report \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s \\\"Publication and\\nDistribution Process.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" posts published plans/reports and approved briefings to Test\\nManagement page.\"))), mdx(\"h1\", null, \"Other Product Review Processes\"), mdx(\"p\", null, \"Figure 6-3 shows the process for reviewing ISRs and status reports.\"), mdx(\"p\", null, \"Figure 6\\u20113. Process to Review ISRs and Status\\nReports\"), 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/51cdad38080f803a99b6a1ef92faae94/b94e3/image19.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.91505791505792%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAAA7DAAAOwwHHb6hkAAACgElEQVQoz22TaXPSUBSG+/+/OY6O26jVWtDWCqWb2IUMTVnSKoWwBbIQQiApISxVx9r6eIl174dn7pk79773vOecu5AaX7Ax+crGfI34yvrZjK3RJ970AmJth1XbZ8UakOiHbIr9pDcmFc7vXUbnI+axYOFFy2NJ84kZQ2JmwKvuhIQrLnYs3rRarGkasdIHVms1kobOjmOz3nVJ/RT5VzBujLgtGTwpD3hpzXjWHBO3zpHsKrvtD2Q6KttqjrR2wp5R5v2wyVbfYy2EzcnfYtcZDrlf6LJY9VjWZyzXulQDlSOziKQdsV+XSZ/ukWkccqQXyBsKzVGFjGeTCK/+E11Y1gPuyhZPKx4rvY+smH3KQZ2KX6bQUTioZ9kt73FQkyj1S6hnKlqosu+7JG8SjJshj05clprBteURinNKzclS6crU+3lOTQlVxNVejpKVperIbPsBqem3GyxrQx4UHRZVj7g54YUxYce2qfSPObGLETlN4tjK8b6rUHEVZKfKevD55qYsVgfc2m/z8Nghpo953p6y5fg0hiUKZh6lU0BuSihCUDHy1Acn5H1d2L38bfcPoqbcyZpRDZd1kaE2Im5fsNsqC3sS2ZpoSGmLw9ouxVYGxZRJDMZsTK9+ZbZ5TZThSyvktfuR1d45r+ypmMMxyeCSA69HwW+z0y6TNsTotE6RnAb5wGJjJOzO6ycEUoLk6ILE6Es0mwtLoob38l0elwaR6NpAWBavr08hOYGsLoRbHQ4bBnLDFPW0kNU6uWqDYqOForXRgxB3MkNyh8Jye/5TfhC3hqx5M5H+VfQNNwXprs87y+Wt2SM9J4pd3nUG0ZpxA/LhJ4qC9Nk53wFWh0iX7KuBAwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image19\",\n \"title\": \"image19\",\n \"src\": \"/static/51cdad38080f803a99b6a1ef92faae94/e3189/image19.png\",\n \"srcSet\": [\"/static/51cdad38080f803a99b6a1ef92faae94/a2ead/image19.png 259w\", \"/static/51cdad38080f803a99b6a1ef92faae94/6b9fd/image19.png 518w\", \"/static/51cdad38080f803a99b6a1ef92faae94/e3189/image19.png 1035w\", \"/static/51cdad38080f803a99b6a1ef92faae94/b94e3/image19.png 1126w\"],\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 6-4 shows the process for reviewing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \" reports.\"), mdx(\"p\", null, \"Figure 6\\u20114. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \" Product Review\"), 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/952e46dab0e112cb3b8f384611e0f7a2/bb2fd/image20.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\": \"64.47876447876449%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAAA7DAAAOwwHHb6hkAAAC7UlEQVQ4y02T21IiVxSGecrkDfIouU9VJkmlypqME40o4wEPk8ixaU4DM4iogDTHBrpbuoEGRJwZ9cvqNjG5+GuvtS/W/g9rBw7dL+zbK8KTew6nn6W+IzRcSC29+0B4DuHpV/5aPLBnuoT6DifuPSezBw7cJw7nTxy5XzmS3kNgs2XzU7bNz4KN5ogNzea3S5PN9piwNSPmjIgYfTJ2n+N6mf1KAcXskLB0Tk2D07HL4ezxeagg8PrC4MdUix9iDV5fDNkZzAn2XLZ6c3bbI/JmjWizLDjntFEiop0Ra1WItSuovQope0B49vTfwJ2hy569ZLPl4A3fbDocjO8IyuAdbYTaKpLUCj6i1QzxWvafvkhKyxMzeiKbF9mBvdFS/PrCO/OWbX0mDMW/yWdC5pJ9fUy5/4EPjQTFpkKuFiNbjZKrx+UuyVlbIT0e+gyP/2W4ay38QLZ1kdmd+ghPVoQMkd6do7ZLpOoplOsMyVrKR1rLkaynyWlp/rTF6/976A3ctZYv3m33Zz7b0HAm9ZLEsEehqZK+lkH1JLlGinwzQ16Ts3/OydRL/EnwyLEnOSQe/iGJbnUmkrLj1xuaI73c6SuO5MGPeoGUMExcKSSrygs75abHtqxayBG/nQV70xWBdyJtq+Mxe2YY7HoPTOUU9Fe8N0Z8aqtkhVmmliArLLMNVfyME+2e8Z2h8m05yDfXu3xvX8tAc4Yne6Np86ZqsV6zRK7n34T1xpL3usW5nkW5jKNcREhWIn5d1JLkjSvWRg5r5pC1G5OtyZxAsDeWAGas103Wyjq/Nyz2nVu8+7faLQljwOX4iky3RKJZJC5QOiVKdpWPk7bv3cktHC8E4mXAk/pK7fBLXhfZLm9rNr8WBr78g/H985eS9MKyWlHLJTqwifRtOR2/jhkOyRuXtD0nOrkj4P3dN1c3stATPPlBfep/P2/hD8YrefXRH+r9Z7U7lJRbkniLTKONWtPEzzafdIOqZZORYP4Gsn6H/DHvPnoAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image20\",\n \"title\": \"image20\",\n \"src\": \"/static/952e46dab0e112cb3b8f384611e0f7a2/e3189/image20.png\",\n \"srcSet\": [\"/static/952e46dab0e112cb3b8f384611e0f7a2/a2ead/image20.png 259w\", \"/static/952e46dab0e112cb3b8f384611e0f7a2/6b9fd/image20.png 518w\", \"/static/952e46dab0e112cb3b8f384611e0f7a2/e3189/image20.png 1035w\", \"/static/952e46dab0e112cb3b8f384611e0f7a2/bb2fd/image20.png 1058w\"],\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 6-5 shows the process for reviewing a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-led\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \".\"), mdx(\"p\", null, \"Figure 6\\u20115. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" Review for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-led \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \"\"), 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/04e965d0b9fddd09d1dcbd8dc14bb15c/fd84e/image21.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\": \"60.61776061776062%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAAA7DAAAOwwHHb6hkAAAClUlEQVQoz01TaVPaUBTl//+AfutMl6lVtOzoqBiRLQkJa4clSICEkIWQEBChWvX05sVx+uHMufdlcubcLfZ9ZOCT0MG3oYb89hXZ4AUF18GtM8ftckEwGHO2gRub3hwD3NJCLviL7OaVcW7z8oFYfO7jWHNxons4377gar2DsmpDtcpoqzfoTm4gDy8YN++voTpVjFcSCn5AYs+R0H+iJOjhc2eEo6mLhLZAyx1CMLqoqgKEWR014vKoQrEEUZPAT0Xw9P13oJLoGpng3eU7YmeLAGHZodOks0PCPYAzp+xHUW+iNpVwp1TAz+QI9F62VHLzyhzlt2/IP7whR8wc/rK2iBs+zhZregQK2z3GXhONyR1k9Q4NAj+4hjQuQrovQp6UoLoiuGCDjPcHaXOF1GKFjO0j7+8RSzgPSLl7JOwHNpCst0dK6SM57DGEcbzbfM/7LM+Oh/gx0nDpbXBlznHUbKDgWCg+PkUOw5JPyWV8sUHeWqJhdlCdNSAabfBaE9VJHbzeYnlNa7FWcN6K9ewiIJfOFufBE/KE2JlJPVTmOKXhxK1HlJZzjBwBA0dC3xIhKBzqIwKV29Yq9FaHYvOQfA0p7xlpy0PaDojXVN0BsRN9ha+DGY4mNrL+Abe2jmxPRnbYYUh0ZRxLFaT7LWQGbeSULnL9BuVNXLkuLk2DSpbB0e5yu6doDz937vFz5iJJzeXmCkrzHmSNpjwTUSfmxxXUKRanAmS9jqrRQ8me4trf4Hx9YO4u1vuo5FOa7pf+DKHTMD42d+AWKgkKqI5rEEikOiqDnwgM4qSGiq0iQxvBhhhEqxNyjhBLLh/ZQBK0g2nqQYgbx0TR0encdDo1nbUhiun0bA0cnV/o5uNK2KVE+AcLc0fpg+v55AAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image21\",\n \"title\": \"image21\",\n \"src\": \"/static/04e965d0b9fddd09d1dcbd8dc14bb15c/e3189/image21.png\",\n \"srcSet\": [\"/static/04e965d0b9fddd09d1dcbd8dc14bb15c/a2ead/image21.png 259w\", \"/static/04e965d0b9fddd09d1dcbd8dc14bb15c/6b9fd/image21.png 518w\", \"/static/04e965d0b9fddd09d1dcbd8dc14bb15c/e3189/image21.png 1035w\", \"/static/04e965d0b9fddd09d1dcbd8dc14bb15c/fd84e/image21.png 1056w\"],\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 6-6 shows the process for reviewing a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" for a non-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \".\"), mdx(\"p\", null, \"Figure 6\\u20116. Non-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" Review\"), 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/764d67a66acd1cbd239b2603ce02fe6a/4ef40/image22.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\": \"61.003861003861005%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAAA7DAAAOwwHHb6hkAAACm0lEQVQoz2WTWXPaShSE/f/f83YfknuTVEK8A4qNwGBWs5gtLJZkMAIJIYEsycYLtpMvg3AlqdyHrjk6mjrT092z9WFg8easxX/KhKj3RCx4QfIeke0p8uwVtkXyFfLM5NgNwn0x/3mDdf2KrfeayT9NlX8vxhy6j0QDSPh3jN0zOqMT2sMknauUgKgFJosCNd9gX+yL/zUsHLjnLPmsL9izl0QMn0PbJ29pZCYXZKcqOQF50OLUVEiHPY2C2SfpuuLw779ZvmJrd3bLmuWOdSMQsOM8kDY0ynqNitHibFwnq5UoG03OJo3wuzhpE3fvBaPv/2f4xfB419cFyzlfrFvk+RzFqdKbnNLRT2kOUtSU43Bdo2/kUKZ5zgOT/WuhudA75q3E9Z+EByu2Nsw27A68F5Jzh3OzQWFUJzeskejmOWpnSHRypLUyRb1OTfxP6x1kf8meqhLp9fhqGsjBw3pgEDq8bXpEzICjkYb0rUDsW4mkds5Rv0y8nedYrAmlhtQpIXXLHLSK5B8e+Wov2NaGZJb3JJdPa1PuiExc9oU5kdkdVUflyjpl4JTQrDzNS5mGeizcTtHV02FvMM2izutEbY9dy+fADtidXnO4uN9o+LZ7xaeRw/ZsiTTRObk8J6lUBKpEm1kO6xlirVzIUr4oczKoIyktMr6PNB6x3euScmakbsWVI8Z1aMrHoR2e9tleUXSGqEL4jlWhbZSoaGnqozx9u0bPEH27ERqSuFkh2ddELsdhdo8CYcquyN8n4XBozDRgLUF05lFeXKH7dTpGkYqSpDUuMHSrqDcil94tUiBc9V/C6MRvfoT1GptgjxfhwHW4D4QOO/MV8sLlIlBpOD2ygyoVs00/UKiJuOx5P4j/+fR+PcFnfgIod0nDK59oTAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image22\",\n \"title\": \"image22\",\n \"src\": \"/static/764d67a66acd1cbd239b2603ce02fe6a/e3189/image22.png\",\n \"srcSet\": [\"/static/764d67a66acd1cbd239b2603ce02fe6a/a2ead/image22.png 259w\", \"/static/764d67a66acd1cbd239b2603ce02fe6a/6b9fd/image22.png 518w\", \"/static/764d67a66acd1cbd239b2603ce02fe6a/e3189/image22.png 1035w\", \"/static/764d67a66acd1cbd239b2603ce02fe6a/4ef40/image22.png 1057w\"],\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, \"Things to Consider when Producing Documents for Coordination/Review\"), mdx(\"p\", null, \"Depending on the type of document and level of review required, the\\nstaffing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" can be an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \" from a Detachment or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \". Some ACAP taskers\\nstaff a final, approved document for informational purposes only. POCs\\nmust consider the following requirements when staffing a product for\\nreview and approval.\"), mdx(\"h2\", null, \"Drafting Plans/Reports and Briefings:\"), mdx(\"p\", null, \"The test team should develop the plan/report and associated briefing\\nwith active support from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" experts (A-3 cybersecurity test and\\nstandardization/format, A-2/9 analysis and test design, A-5/8 policy\\nreview). They should involve \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" AOs early by hosting regular reviews of\\ndraft documents and analysis (via email or telecom) to achieve faster\\ncoordination and issue resolution.\"), mdx(\"p\", null, \"The Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" maintains configuration control of documents\\nthroughout all phases of Detachment coord until they release the\\ndocuments to A-3 for 2-ltr coord in ACAP. Throughout 2-ltr and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coord,\\nthe A-3/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" assumes configuration control, integrates changes, and\\nprovides format continuity when multiple agencies/personnel coordinate\\ndocuments in parallel.\"), mdx(\"h2\", null, \"Actionable Comments\"), mdx(\"p\", null, \"The deliverable for some taskers is a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \". Although \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \" formats vary\\namongst organizations and Services, the basic intent is the same\", \"-\", \"-to\\nprovide actionable comments with supporting rationale. The document's\\nreviewer (comment originator) and the staffing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" (staffing lead's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \")\\nprovide actionable comments \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" their specific responsibilities.\\nDocument reviewers must provide sufficient information in the required\\nformat. If they do not, the staffing lead will adjudicate comments,\\nincluding rewriting them, to obtain approval to release the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \" to\\nexternals. Prior to release, CRMs must contain:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Comments that are actionable, respectful, acceptable, appropriate,\\nreasonable, and most of all release-ready. The staff lead should be\\nable to \\\"cut and paste\\\" rather than spend time trying to discern a\\nreviewer's intent.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \" attachments with proper classification markings.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"No duplicate comments, nor comments intended for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" only.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Comments organized in page order of the document being reviewed.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Adjudicated comments when there are disagreements within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Adjudicated comments that meet expected requirements for sufficiency\\nand format when the originator did not meet those expectations.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Clearly referenced attachments linked to specific comments.\"))), mdx(\"h2\", null, \"Meeting External Suspenses\"), mdx(\"p\", null, \"TDs must manage their test program to produce strategies, plans, and\\nreports that ensure maximum impact and usefulness to the warfighter,\\nprogram office, and developmental teams.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Plans: Plans must be signed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"No or Not Later Than\"\n }, \"NLT\"), \" 60 days prior to test start to meet\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" test adequacy determination (Ref: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 99-103,\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Capabilities-Based Test and Evaluation\"), \", Atch 2, Table A2.1).\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s standard 60-day suspense also applies to plans that are not\\non \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" oversight.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Reports: Final reports must be completed and signed 45 days, or\\nsooner, prior to acquisition decision. A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" must begin writing the\\nfinal report as far in advance of the last test event (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Last Test Event\"\n }, \"LTE\"), \") as\\npractical, because staff personnel need time between the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Last Test Event\"\n }, \"LTE\"), \" and\\n2-ltr coord to refine the report's analysis, conclusions, and\\noverall quality.\"))), mdx(\"h1\", null, \"Accreditation Plans/Reports\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" will send accreditation plans/reports to the A-2/9 workflow\\naccounts. The A-2/9 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will put the accreditation plans/reports into\\n2-ltr \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Entry Control System OR AFOTEC Electronic Coordination System\"\n }, \"AECS\"), \" coordination for 5 days and adjudicate all comments. Upon\\ncompletion, the A-2/9 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will put the accreditation plans/reports into\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coordination for review and signature by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \".\"), mdx(\"h1\", null, \"Joint Reliability, Maintainability Evaluation Team Charters\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" will send the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \" Charter to the A-3 workflow account. The A-3\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will put the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \" Charter, which is a sub group of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" that\\nevaluates data and how data is scored, into 2-ltr \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Entry Control System OR AFOTEC Electronic Coordination System\"\n }, \"AECS\"), \" coordination for\\n5 days and adjudicate all comments. Upon completion, the A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will\\nsend the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \" Charter back to the Detachment for Detachment/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"\\nsignature.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#2-letter-coord-of-air-force-operation-test-and-evaluation-center-produced-documentsbriefings-8-work-days","title":"2 Letter Coord of Air Force Operation Test and Evaluation Center-Produced Documents/Briefings (8 Work Days)"},{"url":"#commanderexecutive-director-briefing-request","title":"Commander/Executive Director Briefing Request"},{"url":"#command-section-coord-process-maximum-of-7-work-days","title":"Command Section Coord Process (Maximum of 7 Work Days)"},{"url":"#other-product-review-processes","title":"Other Product Review Processes"},{"url":"#things-to-consider-when-producing-documents-for-coordinationreview","title":"Things to Consider when Producing Documents for Coordination/Review","items":[{"url":"#drafting-plansreports-and-briefings","title":"Drafting Plans/Reports and Briefings:"},{"url":"#actionable-comments","title":"Actionable Comments"},{"url":"#meeting-external-suspenses","title":"Meeting External Suspenses"}]},{"url":"#accreditation-plansreports","title":"Accreditation Plans/Reports"},{"url":"#joint-reliability-maintainability-evaluation-team-charters","title":"Joint Reliability, Maintainability Evaluation Team Charters"}]},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-6-acap.md"},"frontmatter":{"metaTitle":"AFOTEC Collaborative Action Platform (ACAP)","metaDescription":"AFOTEC Collaborative Action Platform (ACAP)"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"fe9b9be0-0210-5e55-ae7c-3914388b15ed"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/6-7-case-study/page-data.json b/sites/oteguide/page-data/OT&E_Guide/6-7-case-study/page-data.json index 6326bc1f..37e7d2e7 100644 --- a/sites/oteguide/page-data/OT&E_Guide/6-7-case-study/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/6-7-case-study/page-data.json @@ -1 +1 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-7-case-study","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"eed0ff38-60e4-5b6c-acf0-459146dc1f58","title":"Case Study Review","slug":"/OT&E_Guide/6-7-case-study"},"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\": \"Case Study Review\",\n \"metaTitle\": \"Case Study Review\",\n \"metaDescription\": \"Case Study Review\"\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 Case Study Review is a separate functional guide that contains \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \"\\nand test team best practices for using tools and communicating more\\neffectively. While there is no singular format for an effective case\\nstudy, most contain similar elements. Evidence arising from multiple\\ntest cases is stronger and more reliable than evidence from a single\\ntest case. Review multiple case studies and compare their similarities\\nand differences. This comprehensive exploration of test approaches will\\nshow you that what was considered a solid test design for one program\\nwill not necessarily work for your program. These studies are problem\\nand solution centric and serve as the foundation for the \\\"why.\\\"\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is in the process of identifying and documenting Case Studies. We\\nwill formalize these studies in a separate functional guide and post it\\non \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s Sharepoint for reference. Our intent is to have an\\nestablished bi-annual meeting with all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" elements to identify,\\ncapture, and document these best practices.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-7-case-study.md"},"frontmatter":{"metaTitle":"Case Study Review","metaDescription":"Case Study Review"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"eed0ff38-60e4-5b6c-acf0-459146dc1f58"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide/6-7-case-study","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"eed0ff38-60e4-5b6c-acf0-459146dc1f58","title":"Case Study Review","slug":"/OT&E_Guide/6-7-case-study"},"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\": \"Case Study Review\",\n \"metaTitle\": \"Case Study Review\",\n \"metaDescription\": \"Case Study Review\"\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 Case Study Review is a separate functional guide that contains \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \"\\nand test team best practices for using tools and communicating more\\neffectively. While there is no singular format for an effective case\\nstudy, most contain similar elements. Evidence arising from multiple\\ntest cases is stronger and more reliable than evidence from a single\\ntest case. Review multiple case studies and compare their similarities\\nand differences. This comprehensive exploration of test approaches will\\nshow you that what was considered a solid test design for one program\\nwill not necessarily work for your program. These studies are problem\\nand solution centric and serve as the foundation for the \\\"why.\\\"\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is in the process of identifying and documenting Case Studies. We\\nwill formalize these studies in a separate functional guide and post it\\non \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s Sharepoint for reference. Our intent is to have an\\nestablished bi-annual meeting with all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" elements to identify,\\ncapture, and document these best practices.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide/6-7-case-study.md"},"frontmatter":{"metaTitle":"Case Study Review","metaDescription":"Case Study Review"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"eed0ff38-60e4-5b6c-acf0-459146dc1f58"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OT&E_Guide/page-data.json b/sites/oteguide/page-data/OT&E_Guide/page-data.json index 6144413f..a835426e 100644 --- a/sites/oteguide/page-data/OT&E_Guide/page-data.json +++ b/sites/oteguide/page-data/OT&E_Guide/page-data.json @@ -1 +1 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"256b72ad-14c0-54ad-b6f3-f12c68f26507","title":"OT&E Guide","slug":"/OT&E_Guide"},"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 Guide\",\n \"metaTitle\": \"OT&E Guide\",\n \"metaDescription\": \"OT&E Guide\"\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, \"(expand this tab to see all the topics)\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide.md"},"frontmatter":{"metaTitle":"OT&E Guide","metaDescription":"OT&E Guide"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"256b72ad-14c0-54ad-b6f3-f12c68f26507"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"componentChunkName":"component---src-templates-docs-js","path":"/OT&E_Guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"256b72ad-14c0-54ad-b6f3-f12c68f26507","title":"OT&E Guide","slug":"/OT&E_Guide"},"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 Guide\",\n \"metaTitle\": \"OT&E Guide\",\n \"metaDescription\": \"OT&E Guide\"\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, \"(expand this tab to see all the topics)\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OT&E_Guide.md"},"frontmatter":{"metaTitle":"OT&E Guide","metaDescription":"OT&E Guide"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"256b72ad-14c0-54ad-b6f3-f12c68f26507"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/1-2-INTRODUCTION/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/1-2-INTRODUCTION/page-data.json new file mode 100644 index 00000000..63d5542a --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/1-2-INTRODUCTION/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/1-2-INTRODUCTION","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"865882d7-8382-59cd-a6ec-38753a166675","title":"INTRODUCTION","slug":"/OTE_construct_development_guide/1-2-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\": \"INTRODUCTION\",\n \"metaDescription\": \"INTRODUCTION\"\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(\"span\", {\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/d1cb86a64fbd92e448b7cbc0614256b0/45662/image2.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\": \"64.86486486486486%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAADpElEQVQ4y2VSb2gbZRz+tas4xCFCoeyDMoYgq2IV+0FhOsF/c+KHiYwiggiK84PgYMo+jVpGECluFeYmbszixnCVujFTR2vNTLM0ySW5yyWX3OVy/3LJXXJ3SS6Xu6RJm72+KXNf/PDwvC937/O+z/P8wHE7qCBXUZQSkFKyUMNuoWPTl/YBwEMzc9dfiaVEg2QUK5GWDAwzkZbNOGYiJeqyam4VpNLn7U4XbKe9Y//BjwD0ai2aYZVYJJlPYI6r5Upo9oeF3QghkNXKrjgtmlRWQaygobxUQZygI7agoVxBu6sbNpKK+pXBvxhDCzdWAe5t8IPggf/Wx32/wmpE2l5HSSFAZYvbYmLRxDCQpJpIKVuobntI1UwWYHT48AfHgUzzABXTedNquAdDcX7KdjpvadXGawj1RwY3BNYZiCR5XzjBIQwrRLD2AESqYGfzakOv1l21bJTmzl8Zm796ExZvrg6B02qjJka5Uke24+EMHXT0xLknAV56BGsOLfgjRylG5rH1eCItkmKxSqqaRWqVerJq2phryb+C8eeCYQrWIqlhkIvatKLqMwSV/0aUyzOSUjp57Ov5x/YeOLF3YDlEcG/jMrq4BDdBi24yI3mpnOIVy5bXsF2nYjRQgmKn4hQLiRS3YxA8eJ67nVfFqIOq1Z/Hh0rrSd5kOGXlK9/lSWw3TFCFeIzkiTsESwSjWYLMSAR+XbiEM0wxhc/sVhda7a3hgdCDDFfcefjTuTFvoz+SYvjHA6HkO8uB2Ks3lm5Pwu53d+KRyiczMkqzqoNLaWHbrZJea7e8zqbX6SLs8Ld7hY78r+XNzR7QGRZ6W2ifbroTZt19MRSl35j78drTwXX6CEHmprC194Pr5KFT354dG93zwq7BWdfbgN5mH6DR9H7G8zSfyqkLVcv5pdZwzn1/8Y8nsJVYghYK6ZwiSIr25+XfQy8XyyYlFSsUZi5J8z+dvnjr0f5d9HG705ttuR1ft9d/Hbz2BjJrze3BNawmajotNHt+cbxq2adwq2cZTj3D8sqXZy74nxJk3RenhdOcoF3Agp+ksvKHZs1BvKQjQakOJqQC/uXQMyuB9Qn/8toE5meXlv8Z/2L60mjVqC9GyfxKji+x+MI+K+hLhuWgYISJ0FnpNsOK3w0iohl+XJTV97Js4dDVa9fHIBShIBqnIRhOYk7DWjgBWPB+tsFIeg8eYDbDFXH42p3JA0cedjro/ncsDJJSBo6XwH/rb/gXpYD4s61ku5YAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image2\",\n \"title\": \"image2\",\n \"src\": \"/static/d1cb86a64fbd92e448b7cbc0614256b0/e3189/image2.png\",\n \"srcSet\": [\"/static/d1cb86a64fbd92e448b7cbc0614256b0/a2ead/image2.png 259w\", \"/static/d1cb86a64fbd92e448b7cbc0614256b0/6b9fd/image2.png 518w\", \"/static/d1cb86a64fbd92e448b7cbc0614256b0/e3189/image2.png 1035w\", \"/static/d1cb86a64fbd92e448b7cbc0614256b0/45662/image2.png 1410w\"],\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, \"This document contains information pertaining to the first two steps of\\nfive major steps that define the overarching \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E test activity.\\nAlthough the five major steps of a generic test activity can be applied\\nto various level of test (e.g., testing system functions, components,\\nsub-systems, and capabilities), this guide focuses on developing the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct to capture mission effects and the subsequent,\\noverarching test activity.\"), mdx(\"p\", null, \"The first step is \\u201Cdefining the what;\\u201D in the context of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct, this is commonly described as battlespace development. It\\nanswers the following questions: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"What\"), \" are the operations under test;\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"what\"), \" is the intended use of the system(s) in the operation; \", mdx(\"em\", {\n parentName: \"p\"\n }, \"what\"), \" are\\nthe operational conditions they will be employed/supported under\\n(operations and conditions); and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"what\"), \" do you need to measure to\\ndetermine combat capability or mission effects. Battlespace development\\nprovides a strong operations-based foundation to build upon during test\\ndesign and when executing and reporting operational test.\"), mdx(\"p\", null, \"This guide also addresses the second of the five major steps, test\\ndesign. Test design determines the goals of the test and how to achieve\\nthem. This includes considerations of creating an operationally\\nrealistic environment, executing representative scenarios, and the means\\nto collect the resulting data.\"), mdx(\"p\", null, \"When answering these questions with discipline, the output is a strong\\nfoundation for operationally sufficient and technically adequate\\noperational test and evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E).\"), mdx(\"p\", null, \"Submit suggested changes to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Direct Reporting Unit\"\n }, \"DRU\"), \" A-3E Workflow at\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:AFOTEC.A3E.Workflow@us.af.mil\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".A3E.Workflow@us.af.mil\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/1-2-INTRODUCTION.md"},"frontmatter":{"metaTitle":"INTRODUCTION","metaDescription":"INTRODUCTION"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"865882d7-8382-59cd-a6ec-38753a166675"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct/page-data.json new file mode 100644 index 00000000..bb727996 --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"2f9d89d5-f496-54dc-a04a-4d849b012178","title":"The Operational Test and Evaluation Construct","slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-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\": \"The Operational Test and Evaluation Construct\",\n \"metaTitle\": \"The Operational Test and Evaluation Construct\",\n \"metaDescription\": \"The Operational Test and Evaluation 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 one another:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Effectiveness:\\xA0\\xA0\"), \"Measure of the *overall capability\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"to accomplish a mission\", mdx(\"em\", {\n parentName: \"p\"\n }, \" when used by representative personnel in\\nthe environment planned or expected for operational employment of\\nthe system considering organization, doctrine, supportability,\\nsurvivability, vulnerability and threat. (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\xA099\\u2011103,\\n\"), \"Capability\\u2011Based Test and Evaluation*, 6\\xA0Apr\\xA017)\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Suitability:\"), \"\\xA0\\xA0The *degree to which a system can be\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"placed satisfactorily in field use\", mdx(\"em\", {\n parentName: \"p\"\n }, \" with consideration given to\\navailability, compatibility, transportability, interoperability,\\nreliability, wartime usage rates, maintainability, safety, human\\nfactors, manpower supportability, logistics supportability,\\nnatural environmental effects and impacts, documentation and\\ntraining requirements. (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 99-103, \"), \"Capabilities-Based Test and\\nEvaluation*, 6\\xA0Apr\\xA017)\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission Statement:\"), \" Mission statements are written at a high,\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"overarching level consistent with the mission the system is\\nintended to support or enable.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Critical Operational Issues (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"):\"), \" A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" addresses a *critical\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"mission element or operational objective* examined during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to\\ndetermine the system\\u2019s 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(\"strong\", {\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.\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"Operations describe \", mdx(\"em\", {\n parentName: \"p\"\n }, \"the actions, activities, or phases of a\\nmission\"), \" needed to accomplish the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". With two or more\\noperations, the overarching operational objective is the same;\\nhowever, the steps and/or conditions to achieve the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" are\\ndifferent between operations.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission Effects:\"), \" Mission effects are \", mdx(\"em\", {\n parentName: \"p\"\n }, \"outcomes or results\"), \" of\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"conducting an operation.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Capabilities:\"), \" OCs provide operational context for\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"system capabilities or attributes of high interest or importance\"), \"\\nwithin an operation. It may be useful to distinguish between\\nsystem capabilities (i.e., the potential to perform some action)\\nand system attributes (i.e., the functions, properties, structure)\\nof a system. Operational capabilities provide the means to conduct\\nan operation and achieve effects.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational (User) Requirements:\"), \" A *system capability,\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"attribute, or characteristic required to accomplish approved\\ncapability needs*. Operational requirements (including\\nsuitability) are typically performance attributes, but they may\\nalso be derived from cost and schedule (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-601). Typically\\nreferred to as \\u201Crequirements.\\u201D\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Conditions:\"), \" Operational conditions are identified\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or operation and depict the operational battlespace.\\nAn operational condition is defined by \", mdx(\"em\", {\n parentName: \"p\"\n }, \"a set of factors, each set\\nat a given level\"), \". A factor is a variable of the environment that\\nmay affect task performance. A level is a set value within the\\nrange of values a factor can hold.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures:\"), \" Measures are designed to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"convey information\"), \" about a\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"system\\u2019s effect, capabilities, functions, properties, or structure\\nbeing addressed.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data/Data Element:\"), \" Data is *any measurement or information used\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"to determine 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(\"strong\", {\n parentName: \"p\"\n }, \"Test Design:\"), \" The test design is a \", mdx(\"em\", {\n parentName: \"p\"\n }, \"set of test events\"), \" for each\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"operation and battlespace condition, including \", mdx(\"em\", {\n parentName: \"p\"\n }, \"the rationale for\\nselecting the test events\"), \".\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Event:\"), \" A test event is a *single execution of an operation\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"or sequence/set of operations* under specified conditions for the\\noperations.\")))), mdx(\"p\", null, \"This guide provides methods to develop these elements of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct for the overarching goal of determining effectiveness and\\nsuitability.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct.md"},"frontmatter":{"metaTitle":"The Operational Test and Evaluation Construct","metaDescription":"The Operational Test and Evaluation 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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"2f9d89d5-f496-54dc-a04a-4d849b012178"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy/page-data.json new file mode 100644 index 00000000..95997cb7 --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"e22c23d4-97d9-5fc0-8d27-14d6434d34bc","title":"Operational Sufficiency and Technical Adequacy","slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy"},"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\": \"Operational Sufficiency and Technical Adequacy\",\n \"metaTitle\": \"Operational Sufficiency and Technical Adequacy\",\n \"metaDescription\": \"Operational Sufficiency and Technical Adequacy\"\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, \"Operational sufficiency and technical adequacy are two basic \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntenets leading to an adequate and credible test.\"), mdx(\"p\", null, \"Operational Sufficiency addresses the breadth of the operations and\\nconditions addressed while employing new or modified capabilities within\\nthe context of representative employment and support concepts. An\\noperational test and evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) is considered operationally\\nsufficient if it provides the decision maker and the warfighter with\\nresults from test events executed across sufficient operations and\\nconditions to identify the capabilities and limitations associated with\\nemployment and support, and enables an effectiveness and suitability\\ndetermination.\"), mdx(\"p\", null, \"Ensuring operational sufficiency requires a thorough understanding and\\nidentification of the operational employment and support environment and\\nconditions, to include operational threats. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" core teams address\\noperational sufficiency while designing test events to ensure\\ncapabilities and concepts are adequately addressed within the\\noperational evaluation. Core teams are one tool to address operational\\nsufficiency by using operational perspective, experience, and judgment\\nto ensure test events are evaluated within the context of envisioned\\noperations and support. This allows \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" to characterize systems\\u2019\\ncapabilities and mission effects.\"), mdx(\"p\", null, \"Technical Adequacy addresses the relevance of the technical information\\nproduced by the test in relation to the purpose of the test (i.e., test\\nevents address operationally relevant questions). This includes test\\ndesign, test measures, relevant threat environments, data collection\\nmethods, scoring, analysis, modeling and simulation, and test capability\\naccreditation. A test is technically adequate if the test data\\nevaluation provides the acquisition decision maker information to inform\\nthe relevant decision.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy.md"},"frontmatter":{"metaTitle":"Operational Sufficiency and Technical Adequacy","metaDescription":"Operational Sufficiency and Technical Adequacy"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"e22c23d4-97d9-5fc0-8d27-14d6434d34bc"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles/page-data.json new file mode 100644 index 00000000..606eda8d --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"df8d60e1-8779-5154-9756-449e79b8f8e5","title":"Operational Test and Evaluation Test Activity Cycles","slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-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\": \"Operational Test and Evaluation Test Activity Cycles\",\n \"metaTitle\": \"Operational Test and Evaluation Test Activity Cycles\",\n \"metaDescription\": \"Operational Test and Evaluation 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(\"p\", null, \"A general test activity is the sequence of determining what to test, how\\nto test, executing the test and collecting data, analyzing the results,\\nand reporting the conclusions (see figure 1). The success of this\\nactivity depends largely on an initial understanding of the battlespace,\\nthe capabilities under test, and how the capabilities fit within the\\nbattlespace. All subsequent activities build on a test team\\u2019s basic\\nunderstanding of the expected capabilities under test, in what\\noperational conditions the capabilities will be employed and supported,\\nand what needs to be measured. This is called \\u201CDefining the What.\\u201D Using\\nmore operational terminology, this effort is commonly referred to as\\nbattlespace development and should be the first step for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct test activity.\"), mdx(\"p\", null, \"Figure 1. Steps in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct Test Activity\"), mdx(\"undefined\", null, mdx(\"span\", {\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/0af8f41b7293a3dced7f85fd09684cbb/6c2de/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\": \"21.235521235521233%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAECAYAAACOXx+WAAAACXBIWXMAABcRAAAXEQHKJvM/AAABLElEQVQY0z3MyU7CQAAG4D6SRE2fwnj1oIA+hicfQhMRCCV4MCbGQ1VcgNGiLGMXusyUmVIpSylxARu5jyMHD9/h/5P/F1InHSmZNblO6c92Ri+l82YplTOL6bwt7Rzr0ubBhbSxfyrt8rxXQFI6Z/1L8S1XTGaMwtYhvBTaJMQ3dRXLoEUUg1IUxlTvTahGQ1f1Jrgb/WASxhjiAeKcNgocPJw57vh7CQ2+HDv4tHnnQu+9IihOnz00LQYgYopOGBrFzOhNGXSHrMVZwznDoznTvYipZLzs+QF77njsSeuyhvXG+UsajWKh/EoSR+fyav6qJmbliihrRKz7U7HR/1iHwSwBdH+l3ERr5mB+1o0W9UeN1O4aFqhCF9w3bXCtaOD2xQQqjYA7WVR/Afny8o7kNCZ6AAAAAElFTkSuQmCC')\",\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/0af8f41b7293a3dced7f85fd09684cbb/e3189/image3.png\",\n \"srcSet\": [\"/static/0af8f41b7293a3dced7f85fd09684cbb/a2ead/image3.png 259w\", \"/static/0af8f41b7293a3dced7f85fd09684cbb/6b9fd/image3.png 518w\", \"/static/0af8f41b7293a3dced7f85fd09684cbb/e3189/image3.png 1035w\", \"/static/0af8f41b7293a3dced7f85fd09684cbb/6c2de/image3.png 1334w\"],\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 \"), \"Developing\\na battlespace is the first of five major steps in the AFOTEC OT&E\\nConstruct and is accomplished in conjunction with Test Design (discussed\\nin this guide with more detail in the Analyst Test Design Guide). This\\nstep frames the OT&E by answering four fundamental questions. *What* are\\nthe capabilities under test; *what* is the intended use of the\\ncapabilities; in *what* operational conditions will the capabilities be\\nemployed/supported (operations and conditions); and *what* do you need\\nto measure to determine combat capability?\"), mdx(\"p\", null, \"Test teams have latitude in how they develop the battlespace. However,\\nthis guide presents a long-standing and proven approach test teams\\nshould consider before proceeding with test design. It is systematic and\\ncan quickly take test teams from limited operational understanding to\\ncredible \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Constructs. This \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" default approach to battlespace\\ndevelopment will provide a sound foundation for the second step, Test\\nDesign. Figure 2 generalizes this approach. Although depicted as a\\nsequence of steps, the process is iterative and adaptive.\"), mdx(\"p\", null, \"Figure 2. Battlespace Development Within the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct\"), mdx(\"span\", {\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/3712e01ffbfebd9b130c15c6a7fd1b5c/73a2e/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\": \"64.09266409266408%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAADuElEQVQ4y1VSXWgcVRQ+6Z8SbW2rQvSlDyKWlkgVRU01UEQo+JCWIhGlWixoqaASFAvWx/RBxb9YKk0aW1FDINqqSWx22WQ3mf2Z2d2ZnZmdmd3Z2d3Zndn//9ndye4mcr0TqeDDxznn3nO+c+53LrTN7o+ikun9tcrlvaxSzJYqxvU/HCMAcN+pj756ct7FeFcoMe4KSJElNx91+IQojvllUgha5wQtXEQIwQc3JnfufvcVADWXv06xscafjqDuIHgtpeXLpD98zEoCGN3ucIv0KhlFJBNHAS6JvLSyBStmwikkyOkVK/flq5fuuvvcyV0Azxzux5V9sP/k/odhYJvlkzgBJ21bWGHBvhaevu3iUIBP/i3IGSQpWcRJ2pZNpEsok6ukJ6dv7dtwV+ChsdP94AyJj1Kx2HPTv7uO++X408sMf8ROB+7FxLA4zwMRiJ51eASEUcdoLnsxPILBCGpdUPSGli8Zv9y2DVpTvnNtYgd0uhv23sYmypcaqNpoo7a5jmYWXa9aGgLcs+fTidkRJxlWbUSIt7tZkWRlkZfVsBTXGCmWDsaSGcnmpIaXfAFAlc0+0LLFc7lC+QYvqVNYvyt6tnDNvuI/BDD8gNXV6YkcCkf1CiulTSGqNwVZb0Xj2VauWGu3zY7RbK2jsJR4T88UQU5o2y2t4N8FwE7LTv08v5eT0j53QE5EFJ344vtbQ0uu0M01UmRWSZFcdvOUbZWl3H6JiqtZN4ZIc/InGiZMZ4pbhBbRrtNjkwOW3+l0H3R62Dfn7eRrToI+hRvtwBt1hMQUCke1biJd7KlaqafnKptGy0TrnS7K5ssea5m4/n8T9t3xWUGx7O5IsjoQSZYOkLT04oKNGCJI7gQbjo1ygjJKs5ETDqf38dnfFh+59Pnl+3ubCBpNE6DWaJ+tG+YV/CWuFsrGN3WjPTG34D5cKNVnY8lcDmumFEo1//Ts8gvZQs2eL9aEYrkhxtXczaeOj+3BjV9qmd2Pjeb6BXO9dxRMs+NoGG38QXWk6iXUbLaRzRkcEWXtbZpXpihG/hqLPj7+7dwgJyYvYu0maD4+haf+0L7KjlTrLYQbY+RRuVIvAOELHfTT4WEnERzyBfijVJB7/sz7X+7LFaqXOUn1BViFqdabPbyoX/EL2j5alvwhhYgl9J+eOPZWfyqdHdT0/BvJlP76mpt8DAIhCXgxBh6KA4aPAstH4LPvZv7T9sL4D3srNYNJaCWkZ4vVmbnFg3fuDjx7HhKqDlomD5gQfBQN/wA4Gt/Lr1Q70gAAAABJRU5ErkJggg==')\",\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/3712e01ffbfebd9b130c15c6a7fd1b5c/e3189/image4.png\",\n \"srcSet\": [\"/static/3712e01ffbfebd9b130c15c6a7fd1b5c/a2ead/image4.png 259w\", \"/static/3712e01ffbfebd9b130c15c6a7fd1b5c/6b9fd/image4.png 518w\", \"/static/3712e01ffbfebd9b130c15c6a7fd1b5c/e3189/image4.png 1035w\", \"/static/3712e01ffbfebd9b130c15c6a7fd1b5c/73a2e/image4.png 1439w\"],\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, \"Battlespace development provides the foundation for operationally\\nsufficient and technically adequate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E by ensuring operations-based\\ntest designs. It supports the later application of scientific methods of\\ntesting needed to design and analyze tests across the operational\\nbattlespace to ensure credibility. A key element of the scientific\\nmethod of operational test is mission thread analysis, which includes\\nidentifying the operational conditions and considering test constraints,\\nthereby leading to a set of high-return test events. These events will\\nlead to a defensible basis for resource estimations (test articles,\\npersonnel, etc.) early in an acquisition and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E lifecycle. It also\\naids the development of test execution methodologies (field test,\\nmodeling and simulation, hybrid), identifying test capability\\nrequirements and shortfalls, and refining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities and schedule\\n(Integrated Test & Evaluation).\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles.md"},"frontmatter":{"metaTitle":"Operational Test and Evaluation Test Activity Cycles","metaDescription":"Operational Test and Evaluation 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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"df8d60e1-8779-5154-9756-449e79b8f8e5"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach./page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach./page-data.json new file mode 100644 index 00000000..8abec915 --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach./page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach.","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"5f2de220-9ff9-5175-a022-f0d79a7d56a8","title":"Using a Core Team Approach.","slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach."},"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\": \"Using a Core Team Approach.\",\n \"metaTitle\": \"Using a Core Team Approach.\",\n \"metaDescription\": \"Using a Core Team Approach.\"\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 core team is an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-led working group established to support\\nprogram test activities. Examples include battlespace development, test\\ndesign, measures workshops, and technical reviews. The core team is\\ncomposed of all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" stakeholders (Test Team, Detachment and\\nHeadquarters staff). The core team is led by the responsible test\\ndirector (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"). It includes any \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachment subject matter\\nexpertise (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \") the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" believes is needed (e.g., logistics and cyber\\nSMEs). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A3 typically facilitates the process. An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ndirectorate\\u2019s core team member\\u2019s general responsibilities include\\nensuring their directorate\\u2019s intent and expertise is considered as early\\nas possible. It also aids the staff awareness and support during later\\nactivities and staffing actions. External stakeholders are also invited\\nto support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct development. Key external representatives come\\nfrom operational users, program offices, development test, and other\\nOTAs (for Multi-service \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" action officers (or support\\ncontractors, typically the Institute for Defense Analyses (IDA)) should\\nalso be invited if the program is on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" oversight list. External\\ninvolvement during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct development is significant in\\nterms of early buy-in on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\u2019s foundational planning effort, and it\\nbuilds relationships at the earliest possible opportunity. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct can be developed without externals, and with some rapid test\\nactivities it may be required to keep a program moving quickly. However,\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Constructs are typically better if external stakeholder\\ninterests/inputs are considered. Figure 3 reflects a typical \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \"\\ncomposition and potential external stakeholders.\"), mdx(\"p\", null, \"Figure 3. Core Team Composition\"), mdx(\"span\", {\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/baccd1277005f889d1667dc7557661fa/0d6fe/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\": \"67.95366795366795%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAYAAAAvxDzwAAAACXBIWXMAABcSAAAXEgFnn9JSAAAEE0lEQVQ4yy1UyU/bVxh8KX9ED73mVKmHRuqlV3qIcomiKFEpRCJELGE3a5ogxQWDnZA0jgNq1BBScM1iG0jCauMFb9iAsY1XvLLWYJCJsc3mn/2mP9R+0tye5s1o5vsIYYfPl+Xdvl1PuFwpuXWr5GphYUP9/fuPxtvbRYGODlGayxXmeLyeUw6nM1xU1PS5uLilpaCg6tvHjyXk3r1fiVA4lXf9+i+kuPgJIVKp/6vW1gGWqPrqw4cCSW3ti7Pq6udobBRieloDtVoPpXIBer0Jvb0SlJd3obJSgIqKrkxZGW+8sLDpu+bmQWK3n1y5caOUkFevNKS6uqegv3/2dHZWj48f51mSRWZwUMFMTxtzLCE1may0p2eCCgTS3IcPCkYu1zNymR7v+2bB549mGxreVgwPu0gkkr5CRKKZn4eHzdBoXLDbPRmTaZVarS6q0dhgMLjp9PQKdDoX3O4NHCfSlOaySBwnaWQrStc84Uw4/A8rwAOhcKZmdNRKyOTkZsLp3ILZbGMMBhtMJge9xNKSA0ajF1NTm9jfTyGVTiEQ3kF0L4at7V1qYT/VmVYROzjIgh2fL0o7O4d+IOu+fSwvOxin0w+X84D6fGFYV5xwODyw2cLY3U1evkcsdoAlqxserx8n6SRCG1EsmN1UbXRjLxbPUpqFdsG8ShSqTcyrQnRWGaRK9R6UqggU8yHMKYOwWKI4OkoiGNmB07uBYHgLqVQSmUwG8S/H0Fm8WLT66fn5OVjk9vf3QPrEIQyPbdPR8W06PLYBiew/9EvC0BnOcBRPQ2eyQm92wOZws+pSyDLMpSoodGvQLnrol0QSDMPQSCQCYjFfIBQ8ZNwuLzzuAHWueal/PYAlyxHUqjQCgRRrOIOd3X1WZRhe/wZOT0+wshZmLXupxuTGemg3xzAXGBwcCRCpzLerUESg1a5n1GofVCo/1WgD1GjcYi3vYX5+B8FgHKHIJuyudfgDYRweHlJvYIvG43HW/lnu7OyUzs1Z2O52/USePh3Jn5hYvgyGJbBeKJUrVKGwUq12kU15mcrlRioSaTE2ZoFt1U9jsUNssykbFm1sveyMybRGBwbmweW++00gGCfs2nwmzc3C/I6OgVh7uxhDQ2pMTi4y/yP3+vU4lUhUVCrTUZlsIScUyrN8vpjpfi5Be/sA2treoaXl9ycCwRqJRkFIX58ur63tLblz58HXpaXcXrF4LDE6OgGxWAaZ7BO6u//C6qqdLf0K2zUXnj17j9LSDtTU8GltLU9RX//ox6amPnJwAFJVVXG5y8vscfg77+bNB6Su7g25di3/m7t3q8qKihokhYUcd0lJa4LPf8O8fPnHiUj0Z4TD4c4UF3PaKivrvq+r+0TKy5sIjzeSx+FUkPr6RvIvHykvyUyNP9cAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"C:\\\\Users\\\\James.Thomas\\\\Desktop\\\\ITD Brief\\\\CT Picture.png\",\n \"title\": \"C:\\\\Users\\\\James.Thomas\\\\Desktop\\\\ITD Brief\\\\CT Picture.png\",\n \"src\": \"/static/baccd1277005f889d1667dc7557661fa/e3189/image5.png\",\n \"srcSet\": [\"/static/baccd1277005f889d1667dc7557661fa/a2ead/image5.png 259w\", \"/static/baccd1277005f889d1667dc7557661fa/6b9fd/image5.png 518w\", \"/static/baccd1277005f889d1667dc7557661fa/e3189/image5.png 1035w\", \"/static/baccd1277005f889d1667dc7557661fa/0d6fe/image5.png 1115w\"],\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 typical roles and responsibilities for core team members and\\nexternal stakeholders are addressed in table 1.\"), mdx(\"p\", null, \"Table 1. Core team and External participant Roles and Responsibilities\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, mdx(\"strong\", null, \"Core Team\")), mdx(\"th\", null, mdx(\"strong\", null, \"External Participants\"), \".\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Detachment TD:\"), mdx(\"p\", null, \"- Serves as the overall lead for all core/test team activities from program involvement through OT closeout\"), mdx(\"p\", null, \"- Produces well-written documents and well-prepared briefings\"), mdx(\"p\", null, \"- Serves as primary briefer for the program\"), mdx(\"p\", null, \"Note: Det/CC has operational control of the testing process from TO through OT closeout\"), mdx(\"p\", null, \"Battlespace development facilitator:\"), mdx(\"p\", null, \"- Facilitates the battlespace development and assists TD with developing the test design\"), mdx(\"p\", null, \"- Documents the OT&E Construct\"), mdx(\"p\", null, \"- Co-facilitates test events, methodologies, and scenarios\"), mdx(\"p\", null, \"A-2/9 Staff:\"), mdx(\"p\", null, \"- Co-facilitates test events, methodologies, and scenarios\"), mdx(\"p\", null, \"- Assesses program\\u2019s intelligence sensitivity\"), mdx(\"p\", null, \"- Provides assistance with development of realistic threat scenarios\"), mdx(\"p\", null, \"- Provides specialized support to team in the effectiveness analysis, suitability analysis, modeling and simulation expertise, test design expertise, weather, intelligence, and human factors\"), mdx(\"p\", null, \"A-5/8 Staff: Provides policy guidance, test capability, and range identification\"), mdx(\"p\", null, \"SE Staff: Provides environmental, safety, and health guidance\")), mdx(\"td\", null, mdx(\"p\", null, \"- Warfighters bring operational currency, background information and clarity when addressing operational requirements and concepts of operations\"), mdx(\"p\", null, \"- Program office participants bring program information (schedules, technical risk areas, funding, etc.) Gain insight into OT expectations; know potential impact to contract awards with OT flavor\"), mdx(\"p\", null, \"- Lead Developmental test organization (LDTO)/CTA participants bring developmental test (DT) information, gain insight into OT expectations, identify operationally representative OT events that DT can fulfill, know potential impact on capability requirements clarification start provide insight into integrated test challenges\"), mdx(\"p\", null, \"- Other agencies provide insight into test capabilities, expectations, plans, limitations\"), mdx(\"p\", null, \"-- Director, Operational Test and Evaluation (DOT&E) fulfills an oversight function\"), mdx(\"p\", null, \"-- Other OTAs address their Service equities for MOT&Es\"), mdx(\"p\", null, \"--- Army Test and Evaluation Center (ATEC)\"), mdx(\"p\", null, \"--- Operational Test and Evaluation Force (OPTEVFOR)\"), mdx(\"p\", null, \"--- Marine Corps Operational Test and Evaluation Agency (MCOTEA)\"))))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach..md"},"frontmatter":{"metaTitle":"Using a Core Team Approach.","metaDescription":"Using a Core Team Approach."}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"5f2de220-9ff9-5175-a022-f0d79a7d56a8"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/1-7-Construct-Development-Meetings/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/1-7-Construct-Development-Meetings/page-data.json new file mode 100644 index 00000000..5d8b9be1 --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/1-7-Construct-Development-Meetings/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"2413675a-203d-59bb-8715-6e3efa32c726","title":"Construct Development Meetings","slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings"},"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\": \"Construct Development Meetings\",\n \"metaTitle\": \"Construct Development Meetings\",\n \"metaDescription\": \"Construct Development Meetings\"\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, \"Battlespace development typically occurs in a formal meeting(s)\\nenvironment. It is closely tied to the test design and is often\\naccomplished during the same meeting(s). In most cases, an A3 test\\ndesign manager (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \") will accomplish pre-work with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" prior to the\\nformal battlespace development meeting. The pre-work, coupled with A3\\nfacilitation, allows the meeting to be executed quickly and efficiently.\\nSuccessful battlespace development typically takes a couple of days\\nallowing a transition into the test design activity during the same\\nformal meeting. Optimally, one battlespace development/test design\\nmeeting is required with follow-on activities for measures development\\n(measures workshop) and execution planning activities.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/1-7-Construct-Development-Meetings.md"},"frontmatter":{"metaTitle":"Construct Development Meetings","metaDescription":"Construct Development Meetings"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"2413675a-203d-59bb-8715-6e3efa32c726"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/1-8-Battlespace-Development/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/1-8-Battlespace-Development/page-data.json new file mode 100644 index 00000000..ad55b19e --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/1-8-Battlespace-Development/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/1-8-Battlespace-Development","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"5acb1c8b-03fe-5cf0-b8c6-48ce304ee900","title":"Battlespace Development","slug":"/OTE_construct_development_guide/1-8-Battlespace-Development"},"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\": \"Battlespace Development\",\n \"metaTitle\": \"Battlespace Development\",\n \"metaDescription\": \"Battlespace Development\"\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 Battlespace development steps are captured in the subsequent\\nparagraphs.\"), mdx(\"h1\", null, \"Researching the Capability or System Being Acquired\"), mdx(\"p\", null, \"Core team members and external stakeholders should strive for maximum\\nunderstanding of the capability being acquired, the mission(s) it\\nsupports, and how it will be employed and supported before the formal\\nmeeting. To prepare for the battlespace development/test design meeting,\\nresearch capability-based requirements (e.g., draft \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \") and any\\navailable system information from various sources (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Software or Systems Requirements Document\"\n }, \"SRD\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Requirements Document\"\n }, \"TRD\"), \").\\nOther documents critical to operational understanding are \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", TTPs\\nand threat documentation. This research results in knowledge of where\\nand how the system fits into the envisioned battlespace and the intended\\noperational capabilities. Gaining this knowledge can be inherently\\ndifficult early in a program\\u2019s acquisition cycle with only a draft \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \"\\nand a limited, or no written \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \". The operational significance of the\\nrequired capabilities and their impact on the battlespace need to be\\nunderstood sufficiently in order to properly scope the overall\\noperational evaluation.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \" should strive to understand:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The mission the system is designed to support\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Operational objectives required to accomplish the mission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The critical elements of the mission the system supports\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Information/data cyber dependencies which enable the mission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Bounds of the \\u201Csystem\\u201D acquisition and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" processes (i.e., \\u201Cto\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"what extent are other systems impacted, beyond the system being\\nacquired, within the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" processes?\\u201D)\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Threat environment (kinetic and non-kinetic) in which the system is\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"expected to operate\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Limitations and issues that are resolved to support the acquisition\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" processes (technical as well as operational)\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Program documentation:\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"System \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capability requirements documents\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Program acquisition strategy (DoDI 5000.02 model being employed -\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"hardware- or software-centric; additional documents may be used,\\nas required)\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" battlespace development process\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test design process\"))), mdx(\"undefined\", null, mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"858px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/64a5740f114bce09bca2bf11f9a2d76e/42d54/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\": \"55.5984555984556%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAYAAAB/Ca1DAAAACXBIWXMAABcRAAAXEQHKJvM/AAADLUlEQVQoz32Sy08TURTGr5IYRQQU8IEmqBsXrtwQF/4L/gFujMREwbhjoyZGSA1aHpUpAWkLfak4QFvoY2baUvoY6IMBWvoeSi0gta/plJZCiiGm3jZx6+K7597N757zfQdwudxGg8EwiGHYp5mZGZ5areapVKohgiD4eoPhXT0ANcgue02Vz5DEcc77dZteF3gp92TI454Iut3z+8k1vMRGZtg0v1wuA8Dj8a6TJMmYTKYCBO5DYEWs2Ww+spFk8OHt67XDicPLs7n0guYwuyKJBO0Cv9sh3gw4xr1rjql4bEl3xHq/Z1KDVWDl+J+G3BHwwb976Vs61avMZweFdIiLrFL9os1wP8/l7Ifvj6oCy5clkh1V4MDAwHkcxzt1Ot0L2FmXVqutqBOO/BLD8ccAgFO8GFPpUAE7MagPGFwU2iDG3CuE7EeYwI4LOk2RsaFMurcKRBDkhtVqLWk0mj9w5BMIPZmbm/sNPylbbbadR/funh/+dXBlNpexqAuZdWk0vCKOBClhwEOJQl4KTe66tIdscCqT+lQFdnd31wiFwja5XH5TKpW2VSSRSKp1dHy81fK7DDjb2UZVIduvOWRGYWd8Me0bqQjeR+QxGsFLORHKpDr/hQIsFguAIQCYNlhcXAQwILC8vAycpgUQI821X6iNW8r0L66WTY4YSgXkC4SMrjsRbTHLx48LwzAswXSOeVYF9vX1XYAr8wb69sZoNPZW1gW+EXgfwQnirfx9T4PEv3VHwSQ3NPupbVUmviWn/dEJD7U1n4yltGziAMunGDQRF1eBKIq222y26pooFIoi9LCoVCqL0NcT6GG4/Qw4O5QuNSvzzLz+pLj4bS9qGHaSRoFv3Ti2saqfz6cx43GenE4m+pTfNa1Ar9e3icXim9DHFplM1gxrE5/Pr+dwOA2venrr1QkWvD8qN8njO1Zh0BMURwI+aTTkn9z0+2XRUHgi5A1LI4G9qfhPkQrFroJAIHCapulzLpfrot1uvwRrI0VRdR6Pp87t89XZTQstmN15H/V5X39eXuoSrK50jDnsTwWU66nA5XwudDq6Jp1LT2Qh+kHL1WnwF2foUxQh3RHmAAAAAElFTkSuQmCC')\",\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/64a5740f114bce09bca2bf11f9a2d76e/42d54/image6.png\",\n \"srcSet\": [\"/static/64a5740f114bce09bca2bf11f9a2d76e/a2ead/image6.png 259w\", \"/static/64a5740f114bce09bca2bf11f9a2d76e/6b9fd/image6.png 518w\", \"/static/64a5740f114bce09bca2bf11f9a2d76e/42d54/image6.png 858w\"],\n \"sizes\": \"(max-width: 858px) 100vw, 858px\",\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 \"), \"To\\nfacilitate common understanding a series of briefings are typically\\nprovided at the start of a battlespace development /test design meeting.\\nThe briefings cover the Acquisition, CONOPS, capability requirements and\\nthreats. Generally, the program office, warfighting user, and\\nintelligence representatives provide the briefings. Once the team\\nunderstands the battlespace and how the SUT will support the operation\\nin that battlespace, the team can examine how the required capabilities\\nmap to the operational activities. The AFOTEC approach to ensure the\\ncore team understands the capability and system being acquired is to\\nbuild battlespace depiction in the form of an Evaluation View (EV).\"), mdx(\"h1\", null, \"Battlespace Depiction\"), mdx(\"span\", {\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/fa6e66c528a61855f6c7099891e53bcb/e4ab3/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\": \"86.48648648648648%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAARCAYAAADdRIy+AAAACXBIWXMAAC4jAAAuIwF4pT92AAAEEklEQVQ4yz1T+0/bVhTOX7afp/0wadqj0tSqUjdpZVXLtlJ1pRrQSusK1abB6PqgK6CNtpTSqUCFgNCBNsYr4ZEXIWDnQRLbcYzzcBzHcc6345D1Wp+/4+N7zzn3O/d6qtVqw7JrNJ4I0OPULg0zRlo86vJRgEbELRLzMn0TW6K2/UVqC83T1/t/0ZnwLC0oAoEf26mTaZrkqds21RsOvgssoi08j4vhBcY8LjG3My649vYsoqqEz/fncTo6jU/Dr3Bu/zXeDUxgRjmEOxqMWq0Gj80BDaMMJZUhNZkhLS1RQVIpcxCnHH9TxSI4oLpl0qgg0I1wgjpX/dSzE6PvoyKlzSJxLOIXVS2LPByVmingMDvM9VY+p8WuWWN3FUuigc7lPDqno7juTePejoGsWsTyUbkZEQ2bK+SAjQZhOKjRT/48+n059DP/vKk08eOGCxl6oYg1xULXioxubwxdSwk8ihSxkSnhj50skvkSIkoJTQ0rpolJ/yE988XxdD2GJ2sxjG8eYnIrjtlYHnOCDsuqIqJZGNkrY2gjiZGAihmueHw3i6hcQETS8SwgnWjI3YGWTVNRycAq6TjOHiEtxKDLGZjHOZRUmQUyMCc10OGr4itvAu3LCvqiDvLHOpy6zQqyPA5v+X8NLXbpLFverKFYJ1TYZ/CfEvsKDDdpauUN9t4swD/1EisTT7H2fAzKwR6MitmU2nK7XOPOSGoe0cFuynedQXHgCor9l1Ee6EB58CrMXzpQuP0F5K1/gbsdcK6+D7P3POiHc0D3KRixANw+y9kMDMOAR5FlknMqqtt/U3FqGAXvCxQWJqDPTzRt7c8hZMb6kd0PQ+cqxK11ZHovIX+/B+XRXtj3roH+mYJRb0A8PISnUqmQJEko2Q61Dsnb4X6rj29BE6KwhBCk327BOggAV96Dc+M0rJtn4Xz5DrSHPcjqJeiadtIUHjAKBdJzOZSPj2GVy6iaVejP7yL9ZBClcgWaIiM5NQZp4BqKSQGycAAtIUJOCFB5nV2vg2OdaOhWc1ytkmpZyJZKiKsqEnkNIk8WkyIiyRRSmSz8cRET8zMYX13FgiBigysyG/R2R3bz6nGX646D34MBuh8I4MHODh7u7mIoGMTDUAgPgiH86vNB5cVrhTLuRGK4s7qBvnUfHglJZDhx3axgU1Gwy5V6rFaFYA1hs2pNOCeotcDHyOakg6kd3E74cTO6gr64Dz3xDfi1DMiy8Soex54b0L0p7uTz26/pg+AUPg4wgtP4iPkU84ehaXyyOcnXKo3r4go6hGW0Rxbw7eEyPovOwasIzeQS36QSn1WPxdrVWMyZZIQmUiG8SDKYJ1Nhxon9Mh5EWs+jI7aEC/uLuLjnxWW2z4Zn4c3FW0eiAY6F/wBE8KpheY1VdAAAAABJRU5ErkJggg==')\",\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/fa6e66c528a61855f6c7099891e53bcb/e3189/image7.png\",\n \"srcSet\": [\"/static/fa6e66c528a61855f6c7099891e53bcb/a2ead/image7.png 259w\", \"/static/fa6e66c528a61855f6c7099891e53bcb/6b9fd/image7.png 518w\", \"/static/fa6e66c528a61855f6c7099891e53bcb/e3189/image7.png 1035w\", \"/static/fa6e66c528a61855f6c7099891e53bcb/44d59/image7.png 1553w\", \"/static/fa6e66c528a61855f6c7099891e53bcb/a6d66/image7.png 2070w\", \"/static/fa6e66c528a61855f6c7099891e53bcb/e4ab3/image7.png 2883w\"],\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, \"When\\ndeveloping the battlespace depiction, the core team should consider the\\ntype of capability being acquired, what actions the capability enables,\\nwhat objective(s) the capability supports, and the objective\\u2019s\\ndependencies on other systems. For example, if accomplishment of an\\noperational objective depends on numerous other systems and operational\\nfactors, it may be difficult to provide a credible answer about the\\nsystem\\u2019s contribution to the objective; in this case the scope or level\\nof test could be too high (e.g., operational level of conflict, table 4)\\nversus a more credible tactical level of conflict. These considerations\\nwill help guide the level of detail for the nodes in the evaluation view\\nand define the scope of the test.\"), mdx(\"h2\", null, \"The Evaluation View\"), mdx(\"p\", null, \"The evaluation view (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \") (Figure 5) is one method used to aid\\noperational understanding; it is a facilitation tool to get the core\\nteam and external participants to a point of common battlespace\\nunderstanding before jumping into operational test design. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"\\nillustrates three important \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" fundamentals: where in the operation the\\nsystem will likely influence operational outcome; where and when\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"-relevant data will likely be generated; and where the operational\\nenvironment could affect the system\\u2019s capability.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" is \", mdx(\"em\", {\n parentName: \"p\"\n }, \"not\"), \" intended to be a literal depiction. The core team should\\nunderstand that the battlespace depiction is not perfect, but that it\\nmeets the needs of process facilitation. The core team will need to have\\na degree of understanding and latitude as they progress through the\\nprocess because they will have to reach a consensus on the level of\\ndetail they deem sufficient to proceed to the next step.\"), mdx(\"p\", null, \"There are other methods to gain operational understanding, but using the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" has proven successful over several hundred test efforts and is\\ntypically the tool of choice to facilitate the majority of battlespace\\ndevelopment efforts. It has advantages over various other tools such as\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Architecture Framework (DODAF) views. Although DODAF views are\\nuseful for different levels of planning, they are oftentimes not\\navailable for the early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" planning efforts. The DODAF system views\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System View\"\n }, \"SV\"), \") and technical views (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical View\"\n }, \"TV\"), \") are very specific in purpose and do not\\nprovide an overall picture of the battlespace. A DODAF operational view\\n1 (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational View (or Viewpoint)\"\n }, \"OV\"), \"-1) is often useful; however, it normally only addresses the\\npointy-edge of the operation and does not typically address logistics to\\nan acceptable level of detail. When an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" is complete, and done\\nproperly, it should reflect a tailored battlespace depiction that shows:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Major battlespace phases\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Elements of the operation (primary nodes)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Mission statement\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Critical operational issues (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \") and subordinate operations\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capability requirements mapping\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Information sources/references\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Inherently addresses both effectiveness and suitability elements\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provides equal consideration to logistics-centric operations\"))), mdx(\"h2\", null, \"The Evaluation View 1\"), mdx(\"span\", {\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/c5ad4772ebefa2bbe29a9a2f738fa756/412e0/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\": \"83.01158301158301%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAARCAYAAADdRIy+AAAACXBIWXMAAC4jAAAuIwF4pT92AAAEDUlEQVQ4y21US28bVRQeEAKExAZRYMsGsegPQMAGCcSCDUJIbKCbCoREQUKlUUWBIugChWcjirooLAKoEKFAlCbkQdIkSpo4duw4rvMyjieJ7bFn7JnxvO48z8exUySQekZXdx73fvN95zvnSnEcJ4Zp0kp5mxZKRVr8e5PmdgqktDTyhSDXdcl2HYIf0bvpMfokN0MIY34XkWVF5Hkm+b7B6wQ/JyTFUUS252KmtovRw02MV7cwIuehOia6QXx1o+U7eDn1K05lRxAFBNdOod0+jmLxXqRSd6NUegSa9hWkMAwpCAJ4gv/qBOR6CQ9QkvSQKOGrO8usoi89T5+t3yBbBBQGVepY/dRsvkO12lvUbp8lw7jODOOYHMfF7NY+XSs0MZKt4OfFceS3pxCIGsKoRxB5xcI3GRtX1nR0RIzbRcRrewyjyO+pi8QMKHwAnnUnNvJ3wHEklvU8EmGh1DAxkFHwfbaORqsJQ3+FZUosV0I2K6HZfAG23TgCDEOvq48sOwvDfAYbhWO88H6UK4/CtN8D4gDXKwb6FlUMpBX4fgDhjULXP0BdOc1g5xhsGEK4kKKoC3gr/xycOxB1Xwh+cIHg6NPQ+gE+navgN55j3uDHtzb8J4Ig7DIEJ/UC8vljtLN9F1ZX70Fl7wnUqssYSqu4kqogVyzB6Ri9TQd2hNOzhzi77KHUug0gJ5J0fRoNtY8a6uuo1t+EpvezdBnLaS6jqXnIuyWQcOBtZqCsLmC3vI+y8hea2hdQ6hdY8ucseZwl22CXuThZWXU2S/LIPKoTK6hem0O7rkH88DHUN56GNvYjjJ0NqGdeRLP/FIJ2E457EvuyhPSqhPWcBEV5EpYldxnGJLwOOuo0qfJ3qJcvQq38BOErsItrqA1+CW1qCK7w0Sis4eDqJbg3JhA4ESLOo4gUhGj17rteMEOQpi3AtB6knTKXQUZidyW0OmdgzM1CPf8q5IH3obOzemYO2vkTaH37IRx1C3bnNXh7j8PdfQyu8RwMK/1vHXJFJjrFfhZJuMJjjy0MewYrjoec2sLXhQ2M7B/ADGPozMRPVHTazyIsP4yw9BDc5nHonXn0OsVyHGTkQ1quNJCSVSyU9tGxHXaxhYtrLNtghwWjdFxMVmRc3tnCXkOD7xXQNi6hbV2GI2R2Gd0cRnxa+PA8j1wGdl2HO8RBl3VCBFsILhmLGS7gZOp3jO3mwL0O1bgKryEhKfC4KcHU7mPJxSNAjzctKXs0zSfObL2EycNttD3nfzX29vqfeGppEDmjftS3ic0nziCEcQ6e8RF3zgT8wD+S3Gq3Mbm9Tn9srmF0K4vhm6uQG3V4fGiYtgXftHBiZRgvLf0CSzdgOzbXnculAzaTM2GDlfHMSv4BV4m1gWnAPDQAAAAASUVORK5CYII=')\",\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/c5ad4772ebefa2bbe29a9a2f738fa756/e3189/image8.png\",\n \"srcSet\": [\"/static/c5ad4772ebefa2bbe29a9a2f738fa756/a2ead/image8.png 259w\", \"/static/c5ad4772ebefa2bbe29a9a2f738fa756/6b9fd/image8.png 518w\", \"/static/c5ad4772ebefa2bbe29a9a2f738fa756/e3189/image8.png 1035w\", \"/static/c5ad4772ebefa2bbe29a9a2f738fa756/44d59/image8.png 1553w\", \"/static/c5ad4772ebefa2bbe29a9a2f738fa756/a6d66/image8.png 2070w\", \"/static/c5ad4772ebefa2bbe29a9a2f738fa756/412e0/image8.png 2990w\"],\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, \"Building\\nan \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" can look challenging on the surface, but it is initially framed by\\nan A-3 Test Design Manager (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \") skilled in their development. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \"\\nworks hand-in-hand with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" in all pre-work activities and the\\ninitial framing occurs prior to any formal meetings. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-1 forms a\\nsystem-of-systems depiction of the Joint and/or Air Force doctrinal\\nmission area that the new/modified capability is intended to support. It\\nis developed using the broad knowledge gained from early involvement,\\nstudying Joint and Air Force doctrine and researching all available\\nprogram documentation (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \", system \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \", \", 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\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \"\\nstrategy, Air Force & Joint \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" & Doctrine, associated DODAF\\narchitectures). The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" consists of typical operational nodes linked\\ntogether using a \\u201Cnecessary conditions\\u201D methodology. Primary nodes are\\nsignificant elements of the operation. Major phases are logical\\ngroupings of primary nodes and are used to add clarity and understanding\\nto differing phases of the operation. Major phases of the operation\\nusually become apparent after the primary nodes are linked and are\\nfurther differentiated using different colors to associate the primary\\nnodes with their respective major phase.\"), mdx(\"h2\", null, \"The Evaluation View 2\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-2s are a near-seamless evolution of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-1s and differ in three primary\\nareas. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-2 has capability requirements, critical operational issues\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \") and subordinate operations mapped into the battlespace.\"), mdx(\"h2\", null, \"Capability Requirements Mapping\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" 2 (Figure 6) builds on the operational environment depicted on\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-1. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-2 is developed by mapping operational capability\\nrequirements into the depiction where the operational performance data\\nwould likely be generated during a typical operations. Operational\\ncapability requirements are found in a variety of documents (e.g., draft\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"). Operational capability requirements usually\\ncontain key characteristics (attributes) with appropriate parameters and\\nmetrics. However, they may be described with only the characteristic\\n(e.g., \\u201Cthe system must possess high reliability\\u201D). Other times there\\nmay not be any documented capability requirements and in these cases\\nthere will be greater reliance on current operational expertise to\\ndefine the material solution (system under test). This is the most\\nextreme case for defining the battlespace and system under test and\\nwould require documenting capability documentation shortfalls. While\\nmapping requirements, keep in mind that teams often identify\\nrequirements shortfalls that should be mapped as derived capabilities.\"), mdx(\"p\", null, \"Derived capabilities are usually the result of some inferences in the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \", or could result from an interpretation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" and\\ncapabilities relationship and understanding that certain performance\\ncharacteristics must exist for a system to meet its overall mission\\nneed. Derived capabilities do not have associated criteria or\\nreferences, but generally influence the overall effectiveness and/or\\nsuitability determinations (The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" must validate capabilities derived\\nduring the core team process with the user).\"), mdx(\"p\", null, \"To help teams readily identify cybersecurity interest areas. The nodes\\nwith cyber dependencies will be identified by a blue border and will\\nhave applicable requirements and verbiage detailing the cyber dependency\\nmapped into it. The purpose of this step is to generate discussion and\\nidentify area for further investigation into possible test implications\\nconcerning Cybersecurity.\"), mdx(\"p\", null, \"During \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \", the test team should monitor/assist with cybersecurity\\ntest events, pursuing test events using standard scenarios based on real\\nprocedures, real operators, and production-representative equipment. If\\nviable, the team should plan accordingly and reflect the plan in the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" and other test-planning documentation. The team must incorporate\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Production Document\"\n }, \"CPD\"), \" and system \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" as testing evolves.\"), mdx(\"h2\", null, \"Mission Statement\"), mdx(\"p\", null, \"Mission statements are written at a high, overarching level consistent\\nwith the mission the system is intended to support. For example, \\u201CCombat\\nSearch and Rescue Locator (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue Locator\"\n }, \"CSARL\"), \") supports the combat search and rescue\\nmission.\\u201D The team should ask, \\u201CWhat mission is the system intended to\\nexecute or support?\\u201D or \\u201CWhy are the capabilities being acquired?\\u201D\\nMission statements should be consistent with wording from published\\ndocuments like 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\"), \", \", 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\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", doctrine, etc. The\\nmission statement should also trace to the capability gaps identified in\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \". The Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \" develop a recommended mission\\nstatement in the pre-work and present it to the team during the meeting.\"), mdx(\"h2\", null, \"Critical Operational Issues\"), mdx(\"p\", null, \"A critical operational issues (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \") is an operational question. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ndefines a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" as a critical mission element or operational objective\\nthat is examined during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to determine the system\\u2019s overall\\ncapability to support mission accomplishment as determined by\\neffectiveness and suitability. Put simply, COIs are operations, and\\nshould clearly speak to the warfighter. When answered, the operational\\nimpact is clear. For COIs, the team should ask, \\u201CWhat are the critical\\nelements of the mission?\\u201D or \\u201CWhat warfighter goals, major operations,\\nor activities are intended to be accomplished?\\u201D\"), mdx(\"p\", null, \"A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" may be composed of more than one type of operation and may\\ndescribe the operation in a set of activities or phases of a mission\\nneeded to accomplish the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". An example is the KC-46 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \", \\u201CCan KC-46\\nprovide refueling?\\u201D There are at least two distinct activities or\\noperations within this \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \": air-to-air refueling and forward area\\nrefueling point (FARP), which is forward ground refueling. Although the\\noverarching goal is the same (to provide refueling), the activities and\\nthe conditions to do this are different. Identifying operations allows\\nfor designing test around the unique operations and associated\\noperational conditions. The major phases identified on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" should\\nprovide a logical \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" structure. The COIs and any breakout of\\nsubordinate operations are documented on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" near logically group\\noperational nodes.\"), mdx(\"p\", null, \"COIs are operations, not functions, system characteristics, or enable\\ncharacteristics. Figure 7 illustrates some basic \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" tenants.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 7. \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Tenets\")), mdx(\"span\", {\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/9d82dda1880573be3bd02ea6f57a4533/e3829/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\": \"47.10424710424711%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAJCAYAAAAywQxIAAAACXBIWXMAABcRAAAXEQHKJvM/AAACMUlEQVQoz13Sy08TURQH4NMqA5RoiSRYfEQpKlGoAj4ixWd04cYFDakLw19BXJi4wGDSjdGNLEgKpZJ0rExrO6jQMtZO23n1kRZQN1SjiZhKYogmsPFxPbe5TYxNvtzJzM3vnnNPAQA45EDdqAf1oZOoCx2n6jiuF9f26YR+UEopWkh8/mFeSqzHMrm7XzfyTk2LVaLRwCfDyJRxH5jRYTSATqNT6CxbafAFepjJBHZcrcQzBLBJuLbXExY4ACZCqiyozu0mUAvsYBXSqg6hY+goe0eDrXTjpctXIJvNehQ9IyVfiW7V0CYURZ6UFuVhVU1H4vH4bbpvOwuhrZ5D/awqWqWNHsbVNzR7FzWI5pfhvs/v9D8ZH3rsDXT4Q4IrGPa6Zvx8dyQyORwI+C7WAu3sHjtZlRS9t9372u30e/2z4qqDX/l87c7Kl71dNwm8SC7Ab70ErhsEFPUB8PxPUFWj2nIDu/ye/4ZCD7HtamnZT1uOKnlhPpkmUn55dkMkEEoXRsKp3Hgox3d+W7vXWiqFR8vlVLVljt0ZDTrzTzit0rbTam3DtXlGzg/OpbSXC4YuFD+KzmAi7feJsaRYlK8TMuWIxadlWQ4maOA2NoB+1iYNO4Gc6AjaY7E0Nr1b/wElQ4FiKXhL14W5N0tT52fDS2DovKwoT9cKhYe9lUoOaj866SbUiHawZwubLoV/DQJvCznz5tZ7+PPrOxCyhYhZEDx9Xu/o1UzmUevY2AD8BeKh4qdGpySTAAAAAElFTkSuQmCC')\",\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/9d82dda1880573be3bd02ea6f57a4533/e3189/image9.png\",\n \"srcSet\": [\"/static/9d82dda1880573be3bd02ea6f57a4533/a2ead/image9.png 259w\", \"/static/9d82dda1880573be3bd02ea6f57a4533/6b9fd/image9.png 518w\", \"/static/9d82dda1880573be3bd02ea6f57a4533/e3189/image9.png 1035w\", \"/static/9d82dda1880573be3bd02ea6f57a4533/e3829/image9.png 1077w\"],\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, \"As with all things, there are exceptions. Given the emphasis on\\ncybersecurity, teams have the option to address cybersecurity as a\\nseparate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". This is typically done because teams believe there are\\ntest reporting advantages. For some systems, a cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" may be helpful\\nfor reporting cyber effects to warfighters and acquisition community\\nseparate from system performance in an uncontested cyber environment.\\nReporting this way highlights cyber during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E by more narrowly\\nfocusing on what needs to be corrected, why, and the impact if not\\ncorrected from a cyber perspective. In these cases, a separate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" to\\ncapture cybersecurity concerns, may be warranted. Considerations that\\ncould justify a separate cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" are characteristics of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" (e.g.,\\ncommon architecture across all COIs, a software/network focus, and\\npotential catastrophic node), characteristics of the operating\\nenvironment (e.g., significant documented cyber threats or reliance on\\nout of boundary systems or connections), or when cyber effects are not\\nfully captured in traditional ops-based COIs. Test teams can choose from\\nthree \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E constructs (integrated, stand-alone, and hybrid) to capture\\nand report cyber impacts in a manner that ensures stakeholders\\nunderstands performance and mission impacts in a cyber-contested\\nenvironment. Cyber considerations do not mandate a cyber-centric \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \";\\nhowever, core teams have flexibility should they desire a different\\ncyber reporting approach.\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"integrated approach\"), \" (commonly referred to as \", mdx(\"em\", {\n parentName: \"p\"\n }, \"traditional\"), \" or\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Ops-based\"), \") would only have a cyber-centric \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" if there was a defined\\ncyber operation introduced by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Cyber elements (operational\\nconditions, threats, test measures, etc.) are addressed within the\\ncontext of the missions or operations-based COIs (wherever cyber can\\naffect operational outcome). Using the integrated approach, any notable\\nissues identified that extend beyond the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" (e.g., do not affect the\\ndegree of mission accomplishment of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" or the ability to place in\\nfield use) may be addressed in a separate annex to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report, if\\nwarranted.\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"stand-alone approach\"), \" addresses all of the operations-based COIs in\\nan uncontested cyber environment; the stand-alone, cyber-centric \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\naddresses the operations in a cyber-contested environment. This approach\\nallows the baselining of uncontested performance, as compared to\\ncontested performance of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". The Stand-alone Cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" essentially\\nembeds and executes the operations documented in the traditional COIs in\\na cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" that has a contested environment. All cyber contested\\nelements (e.g., operational conditions, threats, test measures, and test\\nevents) are addressed within the cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". Additional cyber-specific\\nmeasures address the system\\u2019s cyber operational capabilities.\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"hybrid approach\"), \" applies elements of both the integrated and\\nstand-alone approaches, addressing cyber both within the\\noperations-based COIs and a separate cyber-centric \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". Cyber elements\\n(e.g., operational conditions, threats, test measures, and test events)\\nare addressed within the context of the missions or operations-based\\nCOIs, the cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is functionally focused (e.g., cybersecurity\\noperational capabilities) and also addresses effects not seen within the\\nmissions or operations-based COIs (i.e., indirect effects, 2nd/3rd order\\neffects). This may also be used to expand cyber reporting beyond the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", if warranted.\"), mdx(\"h2\", null, \"Operations\"), mdx(\"p\", null, \"Based on different activities or different operational conditions within\\na \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \", multiple subordinate operations may be identified under a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". An\\nexample \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" for the KC-46 was, \\u201CCan KC-46 provide refueling?\\u201D There are\\nat least two distinct activities or operations within this \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \":\\nair-to-air refueling and forward area refueling point (FARP). Although\\nthe overarching goal is the same (to provide refueling), the activities\\nand the conditions to achieve this are different. Another example could\\nbe sustainment operations that has a subordinate maintenance operation,\\ndeployed operation, and training operation. Again the need for breaking\\ndown various operations become obvious when identifying the various\\nconditions associated with the different operations.\"), mdx(\"h1\", null, \"Operational Employment and Support Conditions\"), mdx(\"h2\", null, \"Measures of Effectiveness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" (very similar to the previous Mission-Oriented Response Variables\\nor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \") are developed for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or for each operation. An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" is a\\nmeasure of a system\\u2019s (or operation\\u2019s) degree of mission success and\\nwill be commensurate with the level of test. It is a dependent variable\\nwhich gauges the achievement of a desired effect (aka measure of\\neffect). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" also guide the development of factors and levels by\\nassessing factors\\u2019 expected impact on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \".\"), mdx(\"p\", null, \"Ideally, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" should be continuous, but could also be binary\\u2014was the\\neffect achieved or not. While a categorical or binary \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" may be a\\nstrong indicator of mission success, it might also drive considerably\\nmore testing and resource requirements than a continuous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" would\\nrequire to achieve the same statistical significance.\"), mdx(\"p\", null, \"Examples of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" for a notional Combat Search and Rescue system\\u2019s\\noperation of Recover Personnel might be:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Binary: \\u201CPercentage of Rescue Attempts that are Successful\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Continuous: \\u201CProportion of Survivors Rescued\\u201D\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Note the measure of effectiveness reflects the outcome or effect of\\nan operation.\"))), mdx(\"h2\", null, \"Operational Conditions (Factors and Levels)\"), mdx(\"p\", null, \"Operational conditions define the system\\u2019s operations and support\\nenvironment. After \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" have been developed, operational conditions that\\npotentially have a significant influence on outcome of the operations\\nare identified. Operational conditions are identified for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or\\noperation within a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" and depict the operational battlespace identified\\nto support development of test events and scenarios. An operational\\ncondition is defined by a set of factors, each set at a given level. A\\nfactor is a variable of the environment that affects task performance. A\\nlevel is a set value within the range of values that a factor can hold.\\nIt is important to understand the factors influencing task performance\\nin order to initially capture representative operational conditions in\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct. The terminology (conditions, factors, and levels) is\\nderived from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman, Joint Chiefs of Staff Manual\"\n }, \"CJCSM\"), \"\\xA03500.04D.\"), mdx(\"p\", null, \"The set of factors and levels forms the relevant set of operational\\nconditions. These conditions are contained in the test design\\nworksheets. As an example, the Mode of Travel, Battery Type, Terrain,\\nTime of Day, and Threat are all factors (Table 3) potentially\\ninfluencing the outcome of the operation as defined by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \":\\nPercentage of Rescue Attempts that are Successful. No Vehicle,\\nRechargeable, Flat, Night, and High are one level for each factor,\\nrespectively. A single condition for the survivor/evader navigation \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\ncan be described by a specific combination of factors and levels. For\\nexample, one possible combination or single condition can be described\\nas mode is no vehicle, battery is non-rechargeable, terrain is\\nmountainous, time of day is night and the threat is high. Another\\noperational condition can be described as the terrain is flat, time of\\nday is daytime, and the threat is low. Cyber threats have the potential\\nto impact most systems. The cyber factors in table 2 are generally\\nsufficient for test designs; however, other cyber focused factors may be\\nappropriate depending on the COIs and/or subordinate operations.\"), mdx(\"p\", null, \"Table 2. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 2, Survivor/Evader Navigation\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Conditions\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Factors\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Levels\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mode of Travel\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Battery Type\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Terrain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountainous\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Time of Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Disruptive Cyber threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Yes\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non Disruptive Cyber threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Yes\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"h2\", null, \"Identify Factors and Levels.\"), mdx(\"p\", null, \"Factors and levels are identified through a number of methods. If\\nstudies (such as an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \") have been conducted, they could provide insight\\non potential factors. If requirements have been mapped on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \", they\\ncould provide specific factors of interest (e.g., for \\u201Cthe system shall\\noperate day and night\\u201D the factor would be time of day). The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \",\\ncomposed of the users, developers, operators, analysts, etc., brings a\\ngreat deal of knowledge and expertise to the task of brainstorming ideas\\non factors.\"), mdx(\"p\", null, \"To identify factors, the team reviews each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" and asks the question,\\n\\u201CWhat factors potentially influence the outcome of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or operation\\ncaptured by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"?\\u201D Some of these factors may be an explicit part of\\nthe environment in which the system will be employed (e.g., altitude,\\nweather, network load.) Other factors may not seem as directly related\\nto the employment environment, such as manning level, technical orders,\\nskill level. Yet, others may appear as inherent system factors that will\\nlikely be \\u201Cas-is\\u201D when the system is employed. Examples of this include\\nmemory size, number of display screens, and seat positions, we identify\\nthese as a \\u201CGiven\\u201D level within the design. While this list is not\\nexhaustive set of factors, it is important to document all of the\\nfactors identified for future reference. For \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" purposes, attempt to\\nfocus on the sets that will have a potential effect on the outcome of\\nthe operation and are likely to vary the operational environment or the\\nuser/operator.\"), mdx(\"p\", null, \"After the core team documents the factors, appropriate levels will be\\nadded to each factor. When identifying the levels, it is desirable to\\ncapture the range of possible levels. The decision on exactly which\\nlevels to test will be made later during test design. At this point, it\\nmay be recognized that several of the factors, particularly the inherent\\nsystem factors, may be given for operational test. In the example, the\\nfactors are software version and training. It is not necessary to\\nidentify levels for those factors (although, the developer may wish to\\ndo so). Table 3 expands on the navigation \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" example discussed in table\\n3.\"), mdx(\"p\", null, \"The last two factors highlight the point of documenting all identified\\nfactors. In the illustrated example, these particular factors were\\npreviously recognized as going to be \\u201Cgiven\\u201D or \\u201Cas-is\\u201D when the system\\nis delivered. Therefore, they are not prioritized since there is no\\npossibility for them to change. The software version factor is important\\nto document since it is part of the operation and is measured and\\nreported. The last two factors (software version/training) is at a set\\nvalue for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E.\"), mdx(\"p\", null, \"Table 3. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 2, Survivor/Evader Navigation\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Conditions\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Factors\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Levels\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mode of Travel\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Battery Type\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Terrain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountainous\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Time of Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Disruptive Cyber threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Yes\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-Disruptive Cyber threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Yes\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Software Version\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Given\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Training\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Given\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"h2\", null, \"Prioritizing Factors\"), mdx(\"p\", null, \"The table of factors may include factors in the operational environment\\nwhich may not influence the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", but are used to describe an operational\\nenvironment. As a result, a prioritization process is used to rank\\nfactors based on their impact against each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\u2019s operations by\\nconsidering their effect on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \". This is a subjective determination\\nmade by the Core Team and is intended to identify those operational\\nconditions that have the most impact to mission success and are\\ntherefore more important from a test design perspective. This is a\\ntwo-step process for each factor and is accomplished during the\\nBattlespace Development meeting, using operator/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" input. The\\nprioritization process begins with determining the likelihood or\\nfrequency of encountering each level of each factor in the operational\\nenvironments and continues by determining the estimated magnitude of\\nimpact varying the levels of a factor has on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \".\"), mdx(\"p\", null, \"The first step determines the likelihood of encountering the particular\\nlevels for each factor. This is based on the potential to encounter a\\nparticular factor/level in the operational environment (e.g., the\\nprobability of recovery from mountains is high, but the probability of\\nrecovery from Flat is low). This may be done with specific probabilities\\nor percentages or with qualitative statements (e.g., likely, frequently,\\nseldom). The combinations of the factors, levels, and the likelihood of\\nencountering each level describes the possible battlespace conditions\\nthe system under test could operate within when conducting the\\nactivities depicted by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or Operation.\"), mdx(\"p\", null, \"The second step estimates the magnitude of impact and assigns a \\u201Chigh,\\u201D\\n\\u201Cmedium,\\u201D \\u201Clow,\\u201D or \\u201Cnone\\u201D rating for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" for each factor. The\\nimpact is assigned after considering the potential size of the change in\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" when the factor is varied between its levels, leading to a\\nsignificant change in the outcome of the operation with consideration of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \". Table 4 shows the prioritized factors highlighted in grey.\"), mdx(\"p\", null, \"Table 4. Factor Prioritization\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"COI 1: Can CSARL enable survivor/evader navigation to a rendezvous location?\"), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operation 1: Rescue Survivor\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"MOE 1: Timeliness of Rescue;\"), mdx(\"p\", null, \"MOE 2 Accuracy of Pick-up Point\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Factor\")), mdx(\"td\", null, mdx(\"strong\", null, \"Levels\")), mdx(\"td\", null, mdx(\"strong\", null, \"Prioritization\")), mdx(\"td\", null, mdx(\"strong\", null, \"Factor Mgmt\")), mdx(\"td\", null, mdx(\"strong\", null, \"Why factor is operationally important; Why level is selected\")), mdx(\"td\", null, mdx(\"strong\", null, \"Notes\")), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, mdx(\"strong\", null, \"Likelihood of Encountering\")), mdx(\"td\", null, mdx(\"strong\", null, \"Magnitude of Impact\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 1\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 2\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Mode of Travel\"), mdx(\"td\", null, mdx(\"p\", null, \"Vehicle\"), mdx(\"p\", null, \"No Vehicle\")), mdx(\"td\", null, mdx(\"p\", null, \"Frequent\"), mdx(\"p\", null, \"Seldom\")), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null), mdx(\"td\", null, \"Affects the survivor\\u2019s ability to move from the area.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Battery Type\"), mdx(\"td\", null, mdx(\"p\", null, \"Rechargeable\"), mdx(\"p\", null, \"Non Rechargeable\")), mdx(\"td\", null, mdx(\"p\", null, \"Frequent\"), mdx(\"p\", null, \"Seldom\")), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null), mdx(\"td\", null, \"Ability of the survivor/evader to have communications.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Terrain\"), mdx(\"td\", null, mdx(\"p\", null, \"Flat\"), mdx(\"p\", null, \"Mountainous\"), mdx(\"p\", null, \"Littoral\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null), mdx(\"td\", null, \"Difference in the terrain could affect the survivors\\u2019 ability to move or platform recovery.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Time of Day\"), mdx(\"td\", null, mdx(\"p\", null, \"Day\"), mdx(\"p\", null, \"Night\"), mdx(\"p\", null, \"Transition\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null), mdx(\"td\", null, \"Night time could affect the ability to see the survivor/evader.\"), mdx(\"td\", null, \"The CT should document notes for each F&L set.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"High\"), mdx(\"p\", null, \"Low\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null), mdx(\"td\", null, \"This would affect the platforms ability to reach location.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Disruptive Cyber Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"Yes\"), mdx(\"p\", null, \"No\")), mdx(\"td\", null, \"Common\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null), mdx(\"td\", null, \"Will have to look at mission planer vulnerabilities.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Non Disruptive Cyber Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"Yes\"), mdx(\"p\", null, \"No\")), mdx(\"td\", null, \"Common\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null), mdx(\"td\", null, \"Look at possible mission effects.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Software Version\"), mdx(\"td\", null, \"Given\"), mdx(\"td\", null, \"Givens not prioritized\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"Complete instructions on how to plan and operate system, also affects maintenance.\"), mdx(\"td\", null, \"Latest version.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Training\"), mdx(\"td\", null, \"Given\"), mdx(\"td\", null, \"Givens not prioritized\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"Platform dependent, survival or equipment related capabilities.\"), mdx(\"td\", null, \"Both survivor and recovery team have training.\")))), mdx(\"p\", null, \"The last two factors highlight the point of documenting all identified\\nfactors. In this example, these particular factors are seen as \\u201Cgiven\\u201D\\nupon system delivery. Therefore, they are not prioritized because there\\nis no possibility they will change. The technical data factor is\\nimportant to document because it is part of the operation and will be\\nmeasured and reported. The last factor will be at a set value for the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. The team has determined this factor is unlikely to have an impact;\\nnonetheless, it is documented as part of the set of factors. The last\\ntwo factors and the factor \\u201Cthreat\\u201D are not removed from the list\\u2014they\\nare still needed to ensure the test environment is operationally\\nrepresentative. Consideration should be given to them for resource\\nplanning and test execution.\"), mdx(\"h1\", null, \"Operational Capabilities\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Capability\"\n }, \"OC\"), \" is a system attribute or grouping of attributes users or SMEs\\nidentified as having value or that are crucial to the system to satisfy\\nthe capability gap within the context of the operations defined by the\\nCOIs. They provide operational context for attributes of high interest\\nor importance within the operation. OCs are identified by reviewing the\\nsystem\\u2019s requirements documents and by SMEs identifying system\\ncapability attributes that can significantly influence achieving the\\nCOIs.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"Cybersecurity and cyber resiliency are high-interest attributes and\\nare assessed/evaluated as applicable across all operations.\")), mdx(\"p\", null, \"The OCs are not part of the rating structure or evaluation at the end of\\ntest, but serve instead to highlight possible trends/patterns of\\noperational impact along a particular capability. For instance, if in\\nthe final evaluation, multiple measures fail across the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Capability\"\n }, \"OC\"), \"\\n\\u201CInteroperability\\u201D, then this potential capability impact is highlighted\\nto leadership and decision makers. OCs are captured as a short phrase or\\ntopic. Although the identification of OCs is a facilitated effort by the\\nA3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \", table 5 shows which areas to examine when developing OCs.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 5. Operational Capability Areas\")), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"th\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Capability\"\n }, \"OC\"), \"\")), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"th\"\n }, \"Area to Examine\")))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Performance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What are the measures of desired effects (e.g., timeliness)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What operational performance attributes are listed (e.g., precision, responsiveness)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What operational performance attributes are associated with the key performance parameters (\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \") and key system attributes (\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Key System Attribute\"\n }, \"KSA\"), \") (e.g., accuracy)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What attributes are high risk (e.g., lethality; cybersecurity, dependent on new technology)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"System Support\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What support attributes are listed (e.g., reliability, maintainability, availability, compatibility)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What are the support\\u2011related attributes associated with the KPPs and KSAs (e.g., cybersecurity)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What attributes are high risk (e.g., reliability; dependent on new manufacturing techniques)?\")))), mdx(\"p\", null, \"On the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \", OCs allow some logical grouping of the operational\\ncapabilities or capability requirements (e.g., from an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \"). The\\nrelationship between operations (defined by the COIs), operational\\ncapabilities and capability requirements are clearly depicted.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#researching-the-capability-or-system-being-acquired","title":"Researching the Capability or System Being Acquired"},{"url":"#battlespace-depiction","title":"Battlespace Depiction","items":[{"url":"#the-evaluation-view","title":"The Evaluation View"},{"url":"#the-evaluation-view-1","title":"The Evaluation View 1"},{"url":"#the-evaluation-view-2","title":"The Evaluation View 2"},{"url":"#capability-requirements-mapping","title":"Capability Requirements Mapping"},{"url":"#mission-statement","title":"Mission Statement"},{"url":"#critical-operational-issues","title":"Critical Operational Issues"},{"url":"#operations","title":"Operations"}]},{"url":"#operational-employment-and-support-conditions","title":"Operational Employment and Support Conditions","items":[{"url":"#measures-of-effectiveness","title":"Measures of Effectiveness"},{"url":"#operational-conditions-factors-and-levels","title":"Operational Conditions (Factors and Levels)"},{"url":"#identify-factors-and-levels","title":"Identify Factors and Levels."},{"url":"#prioritizing-factors","title":"Prioritizing Factors"}]},{"url":"#operational-capabilities","title":"Operational Capabilities"}]},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/1-8-Battlespace-Development.md"},"frontmatter":{"metaTitle":"Battlespace Development","metaDescription":"Battlespace Development"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"5acb1c8b-03fe-5cf0-b8c6-48ce304ee900"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart/page-data.json new file mode 100644 index 00000000..57a395e0 --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"b096ea35-16f4-507e-bc2d-b7b0446c88d9","title":"Evaluation Summary Chart","slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart"},"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\": \"Evaluation Summary Chart\",\n \"metaTitle\": \"Evaluation Summary Chart\",\n \"metaDescription\": \"Evaluation Summary Chart\"\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 team presents the program\\u2019s \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct in an Evaluation Summary\\nChart (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \"). The chart will vary slightly depending on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" approach\\n(see tables 6-8). The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" identifies the various elements of an\\noperational test and the relationship of the individual elements to each\\nother. The initial elements of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct are the Mission\\nStatement (optional), COIs, Mission Effects (as \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"), OCs, and\\nOperational Requirements; these form the first version of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \"\\nlabeled an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \"-1. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \"-1 is intended to be a concise presentation\\ntool for summarizing the focus and scope of the test and relationship of\\nCOIs and operational capabilities. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" presents the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" as part of an\\nInitial Test Design (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \") Briefing.\"), mdx(\"p\", null, \"Table 6. Evaluation Summary Chart-1 (Integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Approach)\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, mdx(\"strong\", null, \"Mission Statement: The CSARL supports the combat search and rescue mission.\")), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, mdx(\"strong\", null, \"Critical Operational Issues\")), mdx(\"p\", null, mdx(\"strong\", null, \"\\u2192\"))), mdx(\"td\", null, mdx(\"strong\", null, \"COI 1: Can CSARL enable rescue team navigation to a survivor/evader\\u2019s location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 3: Does CSARL support worldwide search and rescue operations?\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, mdx(\"strong\", null, \"Mission Effects \\u2192\")), mdx(\"p\", null, mdx(\"strong\", null, \"Operational\")), mdx(\"p\", null, mdx(\"strong\", null, \"Capabilities \\u2193\"))), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 1.1, 1.2\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 2.1, 2.2, 2.3\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 3.1, 3.2, 3.3\"))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Accuracy\"), mdx(\"td\", null, \"4.3, 7.4\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Situational Awareness\"), mdx(\"td\", null, \"4.1, 4.2\"), mdx(\"td\", null, \"4.1, 4.2, 4.9\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Timeliness\"), mdx(\"td\", null, \"4.4, 4.5\"), mdx(\"td\", null, \"4.4, 4.5, 4.6\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Mission Planning\"), mdx(\"td\", null, \"4.9\\u20134.12\"), mdx(\"td\", null, \"4.10\\u20134.13\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Cyber Resiliency/ Survivability\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Interoperability\"), mdx(\"td\", null, \"4.29\"), mdx(\"td\", null, \"4.30\\u20134.32\"), mdx(\"td\", null, \"4.33\\u20134.35\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Reliability\"), mdx(\"td\", null, \"4.25\"), mdx(\"td\", null, \"4.25\"), mdx(\"td\", null, \"4.26\\u20134.28\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Compatibility\"), mdx(\"td\", null, \"4.22, 4.24\"), mdx(\"td\", null, \"4.22, 4.23\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Availability\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"4.39\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Maintainability\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"4.40\\u20134.43\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Ground Equipment\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"4.44\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*KPP or supports KPP\"), mdx(\"td\", null, \"Effectiveness Centric\"), mdx(\"td\", null, \"Suitability Centric\"), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 7. Evaluation Summary Chart-1 (Hybrid \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Approach)\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, mdx(\"strong\", null, \"Mission Statement: The CSARL supports the combat search and rescue mission.\")), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Critical Operational Issues \\u2192\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 1: Can CSARL enable rescue team navigation to a survivor/evader\\u2019s location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 3: Does CSARL support worldwide search and rescue operations?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 4: Does CSARL Cyber Ops enable support Mission Assurance?\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, mdx(\"strong\", null, \"Mission Effects \\u2192\")), mdx(\"p\", null, mdx(\"strong\", null, \"Operational\")), mdx(\"p\", null, mdx(\"strong\", null, \"Capabilities \\u2193\"))), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 1.1, 1.2\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 2.1, 2.2, 2.3\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 3.1, 3.2, 3.3\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 4.1, 4.2, 4.3\"))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Accuracy\"), mdx(\"td\", null, \"4.3, 7.4\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"...\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Cyber Resiliency/ Survivability\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"....\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*KPP or supports KPP\"), mdx(\"td\", null, \"Effectiveness Centric\"), mdx(\"td\", null, \"Suitability Centric\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 8. Evaluation Summary Chart-1 (Stand-Alone \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Approach)\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, mdx(\"strong\", null, \"Mission Statement: The CSARL supports the combat search and rescue mission.\")), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Critical Operational Issues \\u2192\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 1: Can CSARL enable rescue team navigation to a survivor/evader\\u2019s location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 3: Does CSARL support worldwide search and rescue operations?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 4: Can CSARL operate in a cyber contested environment?\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, mdx(\"strong\", null, \"Mission Effects \\u2192\")), mdx(\"p\", null, mdx(\"strong\", null, \"Operational\")), mdx(\"p\", null, mdx(\"strong\", null, \"Capabilities \\u2193\"))), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 1.1, 1.2\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 2.1, 2.2, 2.3\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 3.1, 3.2, 3.3\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 4.1, 4.2, 4.3\"))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Accuracy\"), mdx(\"td\", null, \"4.3, 7.4\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, mdx(\"p\", null, \"4.1-4.13, 7.4.\"), mdx(\"p\", null, mdx(\"em\", null, \"Note: Will require later development of COI 1, COI 2, and COI 3 composite MOP/MOS\")))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Situational Awareness\"), mdx(\"td\", null, \"4.1, 4.2\"), mdx(\"td\", null, \"4.1, 4.2, 4.9\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Timeliness\"), mdx(\"td\", null, \"4.4, 4.5\"), mdx(\"td\", null, \"4.4, 4.5, 4.6\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Mission Planning\"), mdx(\"td\", null, \"4.9\\u20134.12\"), mdx(\"td\", null, \"4.10\\u20134.13\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Cyber Resiliency/ Survivability\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Interoperability\"), mdx(\"td\", null, \"4.29\"), mdx(\"td\", null, \"4.30\\u20134.32\"), mdx(\"td\", null, \"4.33\\u20134.35\"), mdx(\"td\", null, mdx(\"p\", null, \"4.29-4.44\"), mdx(\"p\", null, mdx(\"em\", null, \"Note: Will address in later COI 1, COI 2, and COI 3 composite MOP/MOS\")))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Reliability\"), mdx(\"td\", null, \"4.25\"), mdx(\"td\", null, \"4.25\"), mdx(\"td\", null, \"4.26\\u20134.28\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"...\"), mdx(\"td\", null, \"...\"), mdx(\"td\", null, \"...\"), mdx(\"td\", null, \"...\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*KPP or supports KPP\"), mdx(\"td\", null, \"Effectiveness Centric\"), mdx(\"td\", null, \"Suitability Centric\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"h2\", null, \"Mission Statement in an Evaluation Summary Chart\"), mdx(\"p\", null, \"The mission statement (optional) is copied and pasted into the\\nEvaluation Summary Chart.\"), mdx(\"h2\", null, \"Critical Operational Issues in an Evaluation Summary Chart\"), mdx(\"p\", null, \"COIs are copied and pasted into the Evaluation Summary Chart.\"), mdx(\"h2\", null, \"Mission Effects in an Evaluation Summary Chart\"), mdx(\"p\", null, \"Mission effects, captured as \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" for the COIs, are listed on the\\nEvaluation Summary Chart\"), mdx(\"h2\", null, \"Operational Capability Requirements in an Evaluation Summary Chart\"), mdx(\"p\", null, \"Operational capability requirements paragraph references from 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\"\n }, \"IS\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \"/\", 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\"), \" are copied into the first version of the Evaluation\\nSummary Chart (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \"-1) based on their relationship to the COIs on the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-2. This provides a clear understanding of how the COIs and\\noperational capability requirements relate to the operational and\\nsupport\\u2011related performance attributes of the system and provide the\\ncapability required by the warfighter. They are intended as high\\u2011level\\nplaceholders for operational test measures (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"/MOPs/MOSs) to be\\ndeveloped later during the measures workshop and refined during test\\nconcept development.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"Note: Operations and conditions (factors and levels) are not depicted\\non an Evaluation Summary Chart. However, they are part of the overall\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct and are typically provided in the test design and test\\nconcept briefings.\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#mission-statement-in-an-evaluation-summary-chart","title":"Mission Statement in an Evaluation Summary Chart"},{"url":"#critical-operational-issues-in-an-evaluation-summary-chart","title":"Critical Operational Issues in an Evaluation Summary Chart"},{"url":"#mission-effects-in-an-evaluation-summary-chart","title":"Mission Effects in an Evaluation Summary Chart"},{"url":"#operational-capability-requirements-in-an-evaluation-summary-chart","title":"Operational Capability Requirements in an Evaluation Summary Chart"}]},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/1-9-Evaluation-Summary-Chart.md"},"frontmatter":{"metaTitle":"Evaluation Summary Chart","metaDescription":"Evaluation Summary Chart"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"b096ea35-16f4-507e-bc2d-b7b0446c88d9"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/2-1-Test-Design/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/2-1-Test-Design/page-data.json new file mode 100644 index 00000000..abf9f455 --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/2-1-Test-Design/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/2-1-Test-Design","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"34731e94-1473-5758-af40-a8f2dd77472b","title":"Test Design","slug":"/OTE_construct_development_guide/2-1-Test-Design"},"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 Design\",\n \"metaTitle\": \"Test Design\",\n \"metaDescription\": \"Test Design\"\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, \"Test design is the second step in a test activity (see figure 8). For\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct test activity, the focus is on the test design for\\nevaluating achievement of the mission effects. The test design addresses\\nthe following areas.\"), mdx(\"h1\", null, \"Test Design Goals\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", the level of test and the kind of answer required, determine\\nthe test design goals for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"/operation and each may have multiple\\ngoals and therefore designs. In general, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses three types of test\\ndesign goals: characterize, compare, and problem identification.\"), mdx(\"h1\", null, \"Types of Test Design\"), mdx(\"p\", null, \"Choosing the most appropriate test design(s) requires expertise on the\\nsystem and the operational application it supports. An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\nprogram will likely have combinations of the designs presented here.\\nEach \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or operation has its own test design and may have more than one\\ndesign. The result of a test design is a set of design points and the\\nrationale for choosing them. The following are typical types of design.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Demonstrations.\\xA0\\xA0\"), \"Demonstration test designs are used to\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"demonstrate whether something is possible or not.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Space\\u2011Filling Designs.\\xA0\\xA0\"), \"Space\\u2011filling designs use a variety of\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"techniques and criteria to select design points to provide\\ncoverage across the possible set of conditions.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Combinatorial Designs.\"), \" A combinatorial design employs the\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"science of systematically selecting combinations of factors and\\nlevels to provide the best chance of identifying problems. This is\\nmost often used in testing software intensive systems.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Case Designs.\\xA0\\xA0\"), \"Case designs are used to demonstrate the\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"capabilities of a system and operation under a specified set of\\nconditions. Several cases may be created using multiple methods.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Worst Case/Best Case Design.\\xA0\\xA0\"), \"One method may be \\u201Cworst case,\\u201D\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"where the conditions chosen are those perceived to be the most\\nstressing.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Special Cases Design.\\xA0\\xA0\"), \"Some special cases may be of particular\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"interest to someone (e.g., the user, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \", Congress). The\\nunderlying reason for the special case should be documented,\\nbecause experience has shown the underlying goal is to prove it\\neither works or it does not work under some specific condition of\\ninterest.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Profiles Case Design.\\xA0\\xA0\"), \"Select cases based on the\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"expected frequency of encountering the particular conditions\\nduring planned operations (e.g., from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"). The rationale\\n(besides operationally realistic) is that this would be the\\nfastest way to reveal the most operationally\\u2011relevant problems.\")))), mdx(\"p\", null, \"**\", mdx(\"br\", {\n parentName: \"p\"\n }), \"\\n\", \"**\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 8. Test Design Within the \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct\")), mdx(\"span\", {\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/3c52401eb66650bf114cbd98cbac9881/45662/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\": \"64.86486486486486%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAADsklEQVQ4y2VSW2gcVRg+hailGEUohD4oVQRpKkYwIILUglJrig+KlOKLLypFEY1Q8iYxtGkoa5oKNVVba7VG2mKMYGJITDbZ28zuzt5md247Mzu33Zmdnb3N7Oxusrkczwbtiw8f3zmcc77z/9//AcdtQ0E2YTgpQiVfhrV6Aw6P3jwCADgwdmXueCSVKyUopRxLSyUEK5aWLQJxNJUzZM3aFqT8J9s7EJCCs0+VsgAYZiWcYZUIHs/GEBNaoRjwfHPvEIQQyFqxlyBzVpJWICvqMCsVIScakBV0yAj6rlGqQ0kxZrp3EQ5oMv8I+HeDCgIP/Lc+N34H/I1Le+twQvQmaXVPLKeW9iBpFlQKZVipuzBvVBj09sGfZmbnQnhUAoZlv16tN09icfGM29p8Qzdrr0G409P9YQ2jkSA/jsWzEItlyyGCqwcRoimhTme1ml6sNHWzqpwaOnn0gudaeH7JbwOn0YLlqgNziglLZRt56MCzI9PPAPDyo0hz38xc8CwS5INRjljHmQQnFhJqwUogobhp1VOmZROXPJPHL341vb64EiwBWTVGc0phDIsxE5ygjklK/ovhL289/uSxkac6Gy5YCVKnvCF6czVEuatByvVidNMXZptpVm2iAhqomN1fZu58PDH53crKGr4BFK0I6raz55emW0DVqy/EM1Iei/MWxSnLI+O3B1GroUiCJ1D7UX+EifrCdJRICdG8bmGoUmZ51T98YWLyh0Aw5O8KPZRh1f1vfXilz3Y7PSmKf8IbiL+55I28+sfC2iA49PZ+FKlsIiPDNKs5aCiNLgrFastttrda7U1kV+E3ZE/v559+1Pu/KW9tdQCZYUFnGx4xLHfAqrovBXDyxNS3d5/1YeTpSII5E0tx7/pCiaHzl672HTz8Yi9628OyHMjnCwDU7OaPKE+3Uox2zyw7P1dqzvTXN/58GrUTiZGikGYUUVL0v27/HjiGhpGU1GISMRcn+e8v31h8bGcXvt9sdzx2o3VxY3PrBGi2NqBVsfeC252y7TSg59psv1mun4+lc1cpTptieeXc1PX5o6JsjBOkeJkT9etI8IMULb9nVRzISwYUUUpQQopgfinw3LIXG0AZGkD8/MLSev9nozcPmqXqbDiRXWb4PIs+3GFFY6FUdqAPp3CSltYoNjfZtYik+P6crL1Ds8LQr3fn+kAAT4IwQQJfKI44DfyhGECC97314enDhlllM5wKFU0PDr5y+mGnDe+fI2EgKQXA8RKYX1wF/wDyIfaJxTCoJQAAAABJRU5ErkJggg==')\",\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/3c52401eb66650bf114cbd98cbac9881/e3189/image10.png\",\n \"srcSet\": [\"/static/3c52401eb66650bf114cbd98cbac9881/a2ead/image10.png 259w\", \"/static/3c52401eb66650bf114cbd98cbac9881/6b9fd/image10.png 518w\", \"/static/3c52401eb66650bf114cbd98cbac9881/e3189/image10.png 1035w\", \"/static/3c52401eb66650bf114cbd98cbac9881/45662/image10.png 1410w\"],\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, \"Factor Management\"), mdx(\"p\", null, \"Within the test design, for each operation, operational factors are\\nmanaged at specified levels. How they are managed will depend on the\\ntest design goal, the likelihood of encountering levels, and the\\nmagnitude of operational impacts when a levels are changed. Table 9\\nillustrates the factor management logic.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Vary factor.\"), \" If a factor management is \\u201CVary,\\u201D that factor\\u2019s\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"levels will be changed in accordance with the test design by the\\ntest team.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Fixed factor.\"), \" \\u201CFixed\\u201D factors will be set and will not change\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"throughout the test.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Log (Record) Factor.\"), \" Those factors labeled \\u201CLog\\u201D are not\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"actively managed, but the setting of that factor will be recorded\\nduring the execution of test events for possible use during\\npost-test data analysis.\")))), mdx(\"p\", null, \"Table 9. Factor Management Logic\"), mdx(\"span\", {\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/068278f9f8136483e8e782c16d2689d4/289dd/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\": \"58.301158301158296%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAABcRAAAXEQHKJvM/AAABk0lEQVQoz4VSPU/CUBRtC6190JZ+QC1SPwEFE1E0DIYEJkkIA4mLixuOht1fQEJYSBhIiCTGxcUYjYOr/8z76ql5YZAmJ33v9tzTc897krT+0QhVQomwTdglhIR91A4I6XUiKsEB0SBsEgqEIqFCOIJYiLoFrvmfYBFNFbiw0cQFAuw3UOPCW6KgvCKoEHIEH0Q+ZhYiZUSQg3MXPAdrsqNqeVmWz2l5QkhBkIHI/67j77HDHfBsfAvAVePQPcIF4QxjMDRk4IwhywRqLtYG+FnUVKlevzxsNq9avd4NP8EkRmRYJ9EkCXnl4dqBoxRGD6L9aPR4N5+/f0ynL0Pe5Hm+TuOnQNQgrkHYQWOIEeOTLfwZabe71U7nutvv35Z/M5H3MFYCQpbgkMFhARxNcB1EnMnkebBcfr2Ry3vuyrLsNDk0hbF1YXQPzXmcson84qvkSKXSsd9otE5rtUZ0Soqi2MjGhICPt44YXOwtOEzCrRPdjvH4abhYfH7PZq8PvIkcGuQwzsZEoyFcm8xKjQlc9gPldyrI+L2lyQAAAABJRU5ErkJggg==')\",\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/068278f9f8136483e8e782c16d2689d4/e3189/image11.png\",\n \"srcSet\": [\"/static/068278f9f8136483e8e782c16d2689d4/a2ead/image11.png 259w\", \"/static/068278f9f8136483e8e782c16d2689d4/6b9fd/image11.png 518w\", \"/static/068278f9f8136483e8e782c16d2689d4/e3189/image11.png 1035w\", \"/static/068278f9f8136483e8e782c16d2689d4/289dd/image11.png 1409w\"],\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, \"Table 10 reflects the typical factor management resulting from the\\nfactor prioritization discussed earlier in the guide.\"), mdx(\"p\", null, \"**\", mdx(\"br\", {\n parentName: \"p\"\n }), \"\\n\", \"**\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 10. Factor Management\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"COI 1: Can CSARL enable survivor/evader navigation to a rendezvous location?\"), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operation 1: Rescue Survivor\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOE 1: Timeliness of Rescue; MOE 2 Accuracy of Pick-up Point\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Factor\")), mdx(\"td\", null, mdx(\"strong\", null, \"Levels\")), mdx(\"td\", null, mdx(\"strong\", null, \"Prioritization\")), mdx(\"td\", null, mdx(\"strong\", null, \"Factor Mgmt\")), mdx(\"td\", null, mdx(\"strong\", null, \"Why factor is operationally important; Why level is selected\")), mdx(\"td\", null, mdx(\"strong\", null, \"Notes\")), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, mdx(\"strong\", null, \"Likelihood of Encountering\")), mdx(\"td\", null, mdx(\"strong\", null, \"Magnitude of Impact\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 1\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 2\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Mode of Travel\"), mdx(\"td\", null, mdx(\"p\", null, \"Vehicle\"), mdx(\"p\", null, \"No Vehicle\")), mdx(\"td\", null, mdx(\"p\", null, \"Frequent\"), mdx(\"p\", null, \"Seldom\")), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"Vary Vary\"), mdx(\"td\", null, \"Affects the survivor\\u2019s ability to move from the area.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Battery Type\"), mdx(\"td\", null, mdx(\"p\", null, \"Rechargeable\"), mdx(\"p\", null, \"Non Rechargeable\")), mdx(\"td\", null, mdx(\"p\", null, \"Frequent\"), mdx(\"p\", null, \"Seldom\")), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"Vary Vary\"), mdx(\"td\", null, \"Ability of the survivor/evader to have communications.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Terrain\"), mdx(\"td\", null, mdx(\"p\", null, \"Flat\"), mdx(\"p\", null, \"Mountainous\"), mdx(\"p\", null, \"Littoral\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, mdx(\"p\", null, \"Vary Vary\"), mdx(\"p\", null, \"Demo\")), mdx(\"td\", null, \"Difference in the terrain could affect the survivors\\u2019 ability to move or platform recovery.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Time of Day\"), mdx(\"td\", null, mdx(\"p\", null, \"Day\"), mdx(\"p\", null, \"Night\"), mdx(\"p\", null, \"Transition\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"Vary Vary Demo\"), mdx(\"td\", null, \"Night time could affect the ability to see the survivor/evader.\"), mdx(\"td\", null, \"The CT should document notes for each F&L set.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"High\"), mdx(\"p\", null, \"Low\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"Vary Vary\"), mdx(\"td\", null, \"This would affect the platforms ability to reach location.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Disruptive Cyber Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"Yes\"), mdx(\"p\", null, \"No\")), mdx(\"td\", null, \"Common\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, mdx(\"p\", null, \"Fix\"), mdx(\"p\", null, \"Demo\")), mdx(\"td\", null, \"Will have to look at mission planer vulnerabilities.\"), mdx(\"td\", null, \"Fix at Yes.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Non Disruptive Cyber Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"Yes\"), mdx(\"p\", null, \"No\")), mdx(\"td\", null, \"Common\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, mdx(\"p\", null, \"Fix\"), mdx(\"p\", null, \"Demo\")), mdx(\"td\", null, \"Look at possible mission effects.\"), mdx(\"td\", null, \"Fix at Yes.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Software Version\"), mdx(\"td\", null, \"Given\"), mdx(\"td\", null, \"Givens not prioritized\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"Log\"), mdx(\"td\", null, \"Complete instructions on how to plan and operate system, also affects maintenance.\"), mdx(\"td\", null, \"Latest version.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Training\"), mdx(\"td\", null, \"Given\"), mdx(\"td\", null, \"Givens not prioritized\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"Log\"), mdx(\"td\", null, \"Platform dependent, survival or equipment related capabilities.\"), mdx(\"td\", null, \"Both survivor and recovery team have training.\")))), mdx(\"h1\", null, \"Unconstrained and Constrained events\"), mdx(\"p\", null, \"In prioritizing the factors and determining factor management, the\\nentire set of possible test conditions has been filtered into a smaller,\\nmore manageable and executable set of test conditions. The process\\ncontinues by introducing constraints and picking an appropriate test\\ndesign or set of test designs. Test design requires a discussion on\\nfactor constraints. The core team will examine all of the possible\\ncombinations of factor levels and specify which are infeasible due to\\noperational or physical constraints.\"), mdx(\"h1\", null, \"Statistical Measures of Merit\"), mdx(\"p\", null, \"All test designs have associated measures of merit, or quality\\nindicators, and most are grounded in scientific statistical\\nmethodologies. The measures of merit should be considered when deciding\\non a test design. Regardless of chosen design type, there is a related\\nmeasure of merit which should be a consideration addressed in the test\\nplan documentation. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Design Guide has more information on\\nstatistical measures of merit and their applicability to different\\ndesign types.\"), mdx(\"h1\", null, \"Test Events\"), mdx(\"p\", null, \"Any single design results in a set of test events. A single test event\\nis defined as a single execution of a test to collect data with the\\noperational factors set at a single, given level (i.e., a single\\ncondition or design point). Table 11 continues the survivor/evader\\nnavigation example introduced earlier. In this example, the team has\\ndecided the type of answer they wanted to provide was to characterize\\nthe system\\u2019s behavior. Consequently, a characterize design matches well\\nwith the desired type of answer. Other factors are fixed.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 11. Example \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Test Events to Recover Isolated Personnel\")), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Test Event\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Mode of Travel\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Battery Type\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Terrain\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Time of Day\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Threat\"))), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Characterize\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\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 }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), 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 }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), 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 }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), 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 }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"6\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"7\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"8\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"9\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"10\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"11\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"12\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Problem \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Identification\"\n }, \"ID\"), \"\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"13\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"14\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"15\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"If multiple test designs are created, such as a characterize design\\nsupplemented with a case design, the total number of test events\\nincreases. Similarly, the total number of test events increases in\\naccordance with test events that are replicated.\"), mdx(\"h1\", null, \"Test Design Validations\"), mdx(\"p\", null, \"Testing evolves continuously and it is expected that test designs will\\nchange. Most of the design evolution is managed by the test teams during\\nthe normal testing ops. However, a test design validation is a more\\nformal effort that generally occurs at the request of a Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"\\nand is usually employed when the test design is significantly outdated,\\nwhen there have been major changes in the scope of an acquisition, or\\nwhen earlier test design documentation is not sufficient/available. The\\nscope of a design validation depends on the test team needs. It could\\nrequire all of the step leading to a test design or only specific pieces\\nof the test design to be readdressed. When making a design validation\\nscope determination, keep in mind that most of the steps build on one\\nanother. Formal test design validations should be requested by the\\nDetachment through the A\\u20113 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \".\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#test-design-goals","title":"Test Design Goals"},{"url":"#types-of-test-design","title":"Types of Test Design"},{"url":"#factor-management","title":"Factor Management"},{"url":"#unconstrained-and-constrained-events","title":"Unconstrained and Constrained events"},{"url":"#statistical-measures-of-merit","title":"Statistical Measures of Merit"},{"url":"#test-events","title":"Test Events"},{"url":"#test-design-validations","title":"Test Design Validations"}]},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/2-1-Test-Design.md"},"frontmatter":{"metaTitle":"Test Design","metaDescription":"Test Design"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"34731e94-1473-5758-af40-a8f2dd77472b"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/2-2-Measures-Development/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/2-2-Measures-Development/page-data.json new file mode 100644 index 00000000..3af88cf8 --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/2-2-Measures-Development/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/2-2-Measures-Development","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"fcb6db43-6662-54bb-95d1-c94f9536bf27","title":"Measures Development","slug":"/OTE_construct_development_guide/2-2-Measures-Development"},"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\": \"Measures Development\",\n \"metaTitle\": \"Measures Development\",\n \"metaDescription\": \"Measures Development\"\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 discusses the process for refining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", developing\\nmeasures of performance (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \"), and measures of suitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \"), and\\nidentifying the associated data elements. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are identified during the\\nearlier battlespace development effort and refined during a measures\\nworkshop (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \"). See the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Measures Guide for additional details. In\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", measures are developed using a top-down and bottom-up approach.\\nThe top down approach is most useful for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" development and the\\nbottom-up approach is effective when developing MOPs and MOSs. Figure 9\\nillustrates where measures fit in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E construct.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 9. Measure development in the \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct\")), mdx(\"span\", {\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/884fffcade99ca845f2e3cc372cc89d9/45662/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\": \"64.86486486486486%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAADq0lEQVQ4y2VSa2gcVRj9kkYsYrFCIYgPRARpFKM0goJowVet+qMgJYgggooVhIr1R/0hIUgoGKwRWoNGa5EYNRKiddOaNOa1u5nNzuy8dnZnH7Pz2p3Z2ZnNzs7u7Gbzut4NtX/8cTj3MnPPvd85B7x6E2UVC0UYCal5B1XcGvpo4NJhALhtcGT66BqbK9GC6lC8XMKwKV6xScxRNmcqur2dlfMfNpotcL3GvqePvQ1gWuVIXFTXiFiawkzqhWJw+OLkXQghUPTiAZLL2UxCRaJkoLRcRCnJRGLWQMmssWuWXCRr5nj7X4yOyT/mAW5s8IPglv/WZ4Z+hXlC3ltHaGmBSWh7YjnNxighWbeRWnDQuusj3bBFgEOdJ948AzSfASja3ktOpX4sSGb6Xa/5smFVnkdoq6t9w+JqAohYZihMpRCGE4yKbhtRNusm0nrFtNbreqGUHxkd7748cQWmrsx3gFdroCpGobiOXM/HHnrog7OjDwEcvQNrdkwGiPdpQcng0UmKz9E5zaJ1w6ELxXLMsl3awHx9iXx8OczACsF2gqIZA6puDkaZ9DlJKQzKav6zU5+O3Xv3kx8/0B45RKZficXlFsXl6jFerjOC4vOi5ufNsl+p1r1iqYIoRuwnGREoNrWvbTz4fn3Pr7zpQDJrHpkPCfmZBdaO0Om5s+d+7rse5MNLRIJcjiSjcytc9OoCHV1cFaJaoRTGZ0RWyJ5yay2oNbY720K3Cilt/4n3Rrp3EOqK0sn7/l5Ye+3Pa6Hnfpma64ODr+6fW4mnl4gkwq/1OFGrJdL5Gk69YZe9rebGJlI08/cbgXb9L+VWawMiFA/bu+iwVfZ7nYr/VCjCvTh8YeKRxTB7EifZz8azb0RI/vjXF3/oPnjPEwfaZ+v+Bmxu7QBUqv6PuE+X2aQ+aTneT+WK983I9389iOuwRnFSlk+qkqwaV8enQ8/oBZvJqUVGK9gpik1/98W3M3fu7KJ3Gs3N4Vq9OdTa3HkB/MYGssvVveKWnCqqejU0PDrVYznu5zjVC0JK/0rMqJ+cHws8LCnmEMlJ51OSMRbjMu+yCeUtPDbKyCaSVKvdkCIEZoOPzi2s9gZmV3oxPzYzu9RzeuDSIau0PtUOJZnJi/jCHVEyZ0qOh5YJgeAS8qIg5r5sW8QJmZ6cor+eELPHJ36b7oYgwUCE5GA5HMPMw0qYAix409tlgr8fF1iMpzSk6kao79mTt3tNdPM7FgZZLUAqI0Pg2j/wL0UM9nHBBaToAAAAAElFTkSuQmCC')\",\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/884fffcade99ca845f2e3cc372cc89d9/e3189/image12.png\",\n \"srcSet\": [\"/static/884fffcade99ca845f2e3cc372cc89d9/a2ead/image12.png 259w\", \"/static/884fffcade99ca845f2e3cc372cc89d9/6b9fd/image12.png 518w\", \"/static/884fffcade99ca845f2e3cc372cc89d9/e3189/image12.png 1035w\", \"/static/884fffcade99ca845f2e3cc372cc89d9/45662/image12.png 1410w\"],\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, \"Measures of performance 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\"), \") are initially\\ndeveloped in a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" facilitated by A\\u20112/9 with A\\u20113 and Detachment\\nparticipation. The optimal time for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" after the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct is approved and a draft \", 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\"), \", or an equivalent document,\\n(e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Form 1067, A\\u2011spec) is available as the source document for\\ncapability requirements. Measures development can also be triggered by\\nimmediate need.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"Measures are expected for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" B/C TEMPs, test concept\\nbriefings, and all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assessment and test plans. For \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \" TEMPs\\nthat are too early for a Measures Workshop, an initial measure set\\nwill be developed by A-2/9 (working with the detachment and the Test\\nTeam as input to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \".\")), mdx(\"p\", null, \"Measures of effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \") are the measures related to the\\ncapability to accomplish an operation. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" directly determine the\\ndegree of the desired effect achieved for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \".\"), mdx(\"p\", null, \"Measures may also be associated with the operational capabilities that\\ncontribute to a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" being satisfied. Measures of Performance (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \") are\\nthe measures related to the system\\u2019s capabilities, features, functions,\\nand properties enabling the effects to be achieved. Measures of\\nsuitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \") are the measures related to the degree to which a\\nsystem can be placed satisfactorily into field use. Additional\\ninformation on MOPs and MOSs can be found in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\xA063\\u2011101/20\\u2011101\", \"_\", \"AFGM\\n2016-01, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Life Cycle Management\"), \", 9\\xA0May\\xA017; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\xA099\\u2011103, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Capabilities\\nBased Test and Evaluation\"), \", 6\\xA0Apr\\xA017; and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Pamphlet\"\n }, \"AFOTECPAM\"), \"\\xA099\\u2011104, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nOperational Suitability Test and Evaluation Guide\"), \", 24 Sep 13, etc.).\\nTest teams should consult the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Measures Guide, their Detachment\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \", and A\\u20112/9 for current best practices on the development of measures.\\nProposed exceptions to these best practices should be discussed with\\nA\\u20112/9 before developing measures. Generally, the desired outcome of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \"\\nis a complete set of measures for the test activity with defined scopes\\nfor each measure.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" are meetings facilitated by A-2/9 and A-3. Major stakeholders in\\nthe acquisition program are invited: the user community, the program\\noffice (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Office OR Project Officer\"\n }, \"PO\"), \"), \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \", system developers, and developmental testers. All\\nparticipants apply their subject matter expertise toward the goal of\\ndeveloping a measure set and test designs. Generally, the Detachment,\\nA\\u20112/9 and A\\u20113 do \\u201Chomework\\u201D prior to the workshop. A\\u20112/9, with inputs\\nfrom the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" or technical advisor, develops draft measures in\\npreparation for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" meeting. The purpose of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" preparation before\\nholding the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" meeting is to save time and level of effort.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/2-2-Measures-Development.md"},"frontmatter":{"metaTitle":"Measures Development","metaDescription":"Measures Development"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"fcb6db43-6662-54bb-95d1-c94f9536bf27"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/2-3-Test-Execution-Planning/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/2-3-Test-Execution-Planning/page-data.json new file mode 100644 index 00000000..796197ad --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/2-3-Test-Execution-Planning/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"bb524d46-cf10-5b52-a8ba-2fbdf2a39f93","title":"Test Execution Planning","slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning"},"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 Execution Planning\",\n \"metaTitle\": \"Test Execution Planning\",\n \"metaDescription\": \"Test Execution Planning\"\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\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" core team members will usually meet informally to continue\\nbuilding upon the information compiled during the Battlespace\\nDevelopment, initial test design, and measures development. This is\\nreferred to as execution planning (see figure 10). The purpose of these\\nfollow-on meetings is to finalize the test construct such as refining\\ntest design worksheets, identifying test methodologies, creating test\\nscenarios, and identifying resources.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 10. Test execution Planning in the \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct\")), mdx(\"span\", {\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/3ff8742e484549c66f3022e8c4ce41e9/45662/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\": \"67.56756756756756%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAYAAAAvxDzwAAAACXBIWXMAABcRAAAXEQHKJvM/AAAD9klEQVQ4y01Ta4hUZRh+XUf8YQtFEYoU3aAflUWWFmkhRau0Bom74iZtWllpUCFSsKkRBmtQQoSZJN1cNXdbXXWN2WWdy87szM7MnrmcuZ2ZPdc595lz5nJmxnXX5es7g1QHXt7ng4/ne973eQ5Y9TlEZkU0Q3JILVZRuWKJDzy3936Atvb+H692hBOsEc8IxViKLxJJ7t/C97U8q87xBW0IIQS42jq3vwsgKsUYQdLxqUiWpGgxIyn6lXUd++9yeachnmJXhhOMHkvzKJ2XEMUoKDMrt7BdvFRCimbSO/Z83t774SE4Pzy2BG6zA/5W/IdXgStILbFxgJidno7RLYJZTkNYVaszgt6aSNXLyOWLrnH7oxCOZduAEYrPiIr57OBoaLOiV9dRjPy4zW6TnbscACLJfjtDsrciCaYYjtNmKEabsRRn5hjF1EqVYrlaXwhH050FSQdZLbXBwq1FVK01kaxX0NzNBWTVm9q9a3ofvGftp3dj3uW/D3k/8oezlDuQjLgDKSKeZgm8GiLPSATNyRFWUCl/iHybF3XA1QaKVhoQZX0gRfEXMB4UJbUf4JE7ATasqDcaMBmitiayAsJG1HBvxNN8I5UTGwXZaFStZq1mNRE1K5xSNANzGUv/v8M77J7OCa/jEZORBJukOeX0/r5T67FCT5CgfNPR3KR3Ou3zBlM29hVk3YPHnMnRwonbPC1Tltm1ufe7VQDtQGa5F8e90f7RichRbyC+9+DRX1fjBwysEMergPDuWsbYphhlC1mNG0jWjNrxEwMrt791AMdGLQMrlmyFyzjRAIZXYcxDwE9//A3n/hq3H3T4Q8kt2MkeIkH1SLK6S5SUXRwv9pDpfHeMpLZNBohXbIU0J7UIu3AMdji95Pu8ZPRIivGy0x19givo5IQ/SeHIzMqqMXj2oudRnENnOi8GKVoJkRn+ChbhsJVgX9ffmJt/tVxtrIZavYkIkkW+cA7xYgnVrHr5k8MnHyMz3JfXffFjnmDyWDiaPbSv7/SGwEy2PziT+SYSzx93T8UP/jbo2qSXqlYCr8L+00TFWARR0o4wnHQkm+cPFyTta5oV3js/MvkUdjA7FckJyZyomRWLJEjmQEEx2Ql/SgzFGEXRyuFQNPfwzfmFd1TdPKsVzQuCqH4B1VoDZM3EAdegUmuCpBShIPBL/xy+9tAbvX33OV2RN3mxiFyBDGJ4BZ0ZHHvt0qjrY+eEX73qnBwfueYewudLuF8fvnj5AzArdYekmg6uUHSUTMuBY+BAi/MwMuqC738ehs++Ogl8QX6JSOT2Jcj0pjPDHhj45YflW7Z2Pd3R2fV8d8+ejV07d7+wrbt3Y1f3zif/AXmSHjeEvrexAAAAAElFTkSuQmCC')\",\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/3ff8742e484549c66f3022e8c4ce41e9/e3189/image13.png\",\n \"srcSet\": [\"/static/3ff8742e484549c66f3022e8c4ce41e9/a2ead/image13.png 259w\", \"/static/3ff8742e484549c66f3022e8c4ce41e9/6b9fd/image13.png 518w\", \"/static/3ff8742e484549c66f3022e8c4ce41e9/e3189/image13.png 1035w\", \"/static/3ff8742e484549c66f3022e8c4ce41e9/45662/image13.png 1410w\"],\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, \"Test Methodology\"), mdx(\"p\", null, \"Test events may be executed through a variety of methods. Replicating a\\nrealistic mission or mission segment should be used whenever feasible.\\nReplicating a realistic mission does not have to focus on the engagement\\nor battle outcome level (full engagement level of testing can be cost\\nprohibitive), but should provide the means to evaluate the operational\\neffectiveness and suitability of the system or subsystem in\\noperationally realistic conditions. Additionally, it should provide a\\nmeans to determine overall mission capability. Testers create controlled\\ntest scenarios to reflect the conditions that best evaluate the system.\\nField testing is a good, initial choice for operational testing as it\\nprovides the most operationally realistic environment. However, field\\ntesting is not always feasible to capture all test events. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" provides\\nanother venue for executing test events (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"United States Code\"\n }, \"USC\"), \", Title 10\"), \" imposes\\nconstraints on the use of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" during operational testing) and may\\ninclude distributed test applications using live, virtual and\\nconstructive (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \") simulation assets. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" requirements should be\\ndetermined early in order to become part of the system development\\ncontract. Other test methods include studies and analysis, exercises and\\ntraining opportunities. The test methodologies may be a combination of\\nthese methods during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". For example, early in a program,\\nyou might use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to help identify important operational factors to\\ninclude in an Early Operational Assessment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \") or Operational\\nAssessment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \"). Execution of test events during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \" is followed\\nby some analysis highlighting that some factors may not be important\\n(and possibly identify new factors). The revised set of operational\\nfactors is then used in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E.\"), mdx(\"p\", null, \"If test capability requirements (to include modeling and simulation) are\\nidentified during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct development, accreditation activities\\nare required. Identification of test capability requirements will result\\nin the development of an accreditation memo. The memo identifies the\\ntest capability requirements, accreditation documentation requirements\\nand format, timelines, the accreditation authority and other pertinent\\ninformation. The memo is increasingly important because it initiates\\ndevelopment of the accreditation plans and begins tracking \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" resource\\nexpenditures including manpower and dollars.\"), mdx(\"h1\", null, \"Test Scenarios\"), mdx(\"p\", null, \"Test scenarios capture the end\\u2011to\\u2011end flow and reintroduce the factors\\nidentified during the battlespace development and test design. During\\nthose earlier steps the operational factors were used to identify\\ncondition based test events. These events must be translated into\\nrepresentative operational test scenarios (figure 11). Test events\\nshould be executed in in the most representative scenarios possible.\\nThis allows the best evaluation of a system by replicating a realistic\\nmission or mission segment. Test scenarios should allow all key factors\\nidentified in the condition-based test event to be exercised.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 11. Test Events and Scenario Linkage\")), mdx(\"span\", {\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/7816b04b8896b481dd69bc60ce7b5cae/c1b63/image14.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\": \"31.27413127413127%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAGCAYAAADDl76dAAAACXBIWXMAABcRAAAXEQHKJvM/AAABlklEQVQY0zWRz0sCQRTHpwihe5fAS5oEgf9Mhy4dpJPHTl2Ejh6joFQCO4TgPZUuogdDjUz8RSvtqgcV8UfmllE7u7Pz+q7QwJf3mHnzfZ95w7LZ7Em9Xr9otVqXUtJKhiEuLVNeWJaMCCFPiZbrRMQ0TVubzWas0+l4e73ewXA4PO/3+8nBYJBHfhUOhzdYtVolVVWpVqvRYqET5ybBlCwhESXZtlRhtu73+1g8HmeZTGabc/6ORYAgRVGo2+2SEMLJo6zdbj/N53OJyBXl1VTVNxMXTHgZMEOh/RIIHG36fHsuh3I0Gt0iEkCMQqEgisWiyOfzHFsSYN+sUqmsujQaDVouv0n//KJfwwQZrQgty26GQmeuYDD4b3ht4xAAJghls9kU4/GYAEXpdPqelcvl4+l0OptMpl+o03FJBz0kPyAOykfnyQwrGo2wXC7nwdweIMI8MaaFYz7GKO6chiyRSDAkO5DXMCzPzw9HFF58iAd7u5Bb056dGlYqldbwIas8Fovtp1Kpw2QyeeN2u7d0XXd6sj/dNXcDy+eY5QAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image14\",\n \"title\": \"image14\",\n \"src\": \"/static/7816b04b8896b481dd69bc60ce7b5cae/e3189/image14.png\",\n \"srcSet\": [\"/static/7816b04b8896b481dd69bc60ce7b5cae/a2ead/image14.png 259w\", \"/static/7816b04b8896b481dd69bc60ce7b5cae/6b9fd/image14.png 518w\", \"/static/7816b04b8896b481dd69bc60ce7b5cae/e3189/image14.png 1035w\", \"/static/7816b04b8896b481dd69bc60ce7b5cae/c1b63/image14.png 1200w\"],\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, \"Test scenarios may include test events supporting multiple measures or\\nCOIs. Thus, one scenario may satisfy the completion of multiple test\\nevents simultaneously (Figure X). Evaluating a system by replicating a\\nrealistic mission or mission segment should be used whenever feasible.\\nMission replication should provide the means to evaluate the operational\\neffectiveness and suitability of the system or subsystem in\\noperationally realistic conditions. Realistic threats, including cyber\\nthreats, should be drawn from the latest intelligence sources for the\\nemploying commands. Core teams create controlled test scenarios that\\nreflect the operationally realistic conditions to best evaluate the\\nsystem. Defense business systems testing will include theft/fraud test\\nscenarios.\"), mdx(\"p\", null, \"The intent is to identify test scenarios that allow for an end\\u2011to\\u2011end\\nflow from one \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" to the next, as well as for concurrent COIs. Within\\nthe test scenarios, factors are set to the appropriate levels called for\\nby each test design. It is important to realize that the levels may be\\ndifferent or vary from scenario to scenario. For example, an F\\u201116\\nconducting a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue\"\n }, \"CSAR\"), \" scenario is unlikely to fly at high altitudes; thus,\\nthe level for altitude is set to low and another scenario (such as a\\nstrike scenario) is used to capture altitude at its high level. Another\\napproach would be to select a set of test scenarios that allow all the\\ntest events (described by the factors and levels) to be executed within\\nthe scenarios. Selecting test scenarios appropriately allows for\\nefficient use of test resources, as well as presenting an operationally\\nrealistic test environment. Proper scenario selection also helps avoid\\ntesting in independent segments (e.g., COIs) when there are actually\\ninteractions between these segments. However, not all test events are\\nlikely to be executable as part of one overall scenario or set of\\nscenarios. Expect some test events to require separate, specific\\nportions of a scenario to establish the necessary operational\\nconditions. A consequence of identifying end\\u2011to\\u2011end flow and interaction\\nbetween COIs is that test events are overlapping and occurring\\nsimultaneously. For example, the same F\\u201116 sortie that captures two\\ntargeting test events (one in mountainous terrain, the other in flat\\nterrain) also captures a mission\\u2011planning test event and a weapons\\nload\\u2011time test event. These events all take place within the context of\\na \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue\"\n }, \"CSAR\"), \" scenario where the particular operational factors are set to\\nlevels consistent with a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue\"\n }, \"CSAR\"), \" scenario. Figure 12 reflects this concept\\nof end-to-end threads across COIs\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 12. End-to-end threads across COIs\")), mdx(\"span\", {\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/99815a5456ca70df67c2d114b4552b48/29c1d/image15.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\": \"31.27413127413127%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAGCAYAAADDl76dAAAACXBIWXMAABcRAAAXEQHKJvM/AAAB00lEQVQY02OYuG8Tw/plK/hu3bxZd//evbWvXr5c8OLlS5X///8zLLl8jiln7lYmEBuGZ9w/y5h3Yitjy9r9EPGfXxk+P3/N0HXzBAPDfzkGBue7K4QW7jm+f/Pha/+3n7z+//rLZ3+fPnrkVPf8GEPlod0Mfv0bQAYJA7EoELP23j3JkH1yK0PbhkMgce7//36Ifn/+VrDw2kEGvhdrGRjSru20O3XkRNfpk2cPXLtw5fj+Z3dSV908F73vzuWApWdPuh25fn/6tcev7j148+bzjVdP5yy5fMJqw9VznrvOXp146trdl5fv3v926/GD/unnDnM/vHuPn8H0wnKdNacvxV64/+LEnWdvH116/fTziptno4U/r+SaumNPwMbdZ/5v2nP+/+lrd75f/foyguvgZP7SvZvVeubtnNM7d8+aGWsO1Na/2CPMsKWBBRQEDP8X/GdYsHHv5nXbT/zfsOvE/6uPHq5jEGFg6N6/niErKFRy9pSJ8fNmTMmqKsi3AWmwW9XPMO3/L3B4AgEjiO7avwZoEANErGTVdIY9K5cor1g4y29yd5sfUBHvoq5ehhWXjzGBdMAiAwSK+9uZE/+/YSi5fhhkEBwvunKYkaEZohYAcogmu/WFLxAAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image15\",\n \"title\": \"image15\",\n \"src\": \"/static/99815a5456ca70df67c2d114b4552b48/e3189/image15.png\",\n \"srcSet\": [\"/static/99815a5456ca70df67c2d114b4552b48/a2ead/image15.png 259w\", \"/static/99815a5456ca70df67c2d114b4552b48/6b9fd/image15.png 518w\", \"/static/99815a5456ca70df67c2d114b4552b48/e3189/image15.png 1035w\", \"/static/99815a5456ca70df67c2d114b4552b48/29c1d/image15.png 1375w\"],\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, \"Test scenarios also allow the re\\u2011introduction of the operational factors\\nthat were set aside earlier. These are the operational factors likely to\\nexist in the operational environment, but at a given level or minimally\\nrelated to the system. These are included in the test scenarios to\\nensure operationally realistic conditions.\"), mdx(\"h1\", null, \"Test Capability Needs and Shortfalls\"), mdx(\"p\", null, \"Execution of operationally relevant \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E will normally require test\\ncapabilities. This section only discusses test capabilities and\\naccreditation to the extent needed for an initial test design. For more\\ndetails see the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Capabilities Guide and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nAccreditation Guide. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not own or operate test ranges,\\nfacilities, or assets and must identify test capability resource\\nrequirements as early as possible to ensure they are available, and\\ntechnically and operationally sufficient, for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E purposes. The\\nbattlespace development and test design processes defined the test scope\\nand methodologies and is the foundation for identifying test capability\\nrequirements. Table 10 shows typical test capability requirements.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 10. Typical Test Capabilities\")), mdx(\"table\", null, mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Test articles\")), mdx(\"li\", null, mdx(\"p\", null, \"Test sites\")), mdx(\"li\", null, mdx(\"p\", null, \"Test instrumentation\")), mdx(\"li\", null, mdx(\"p\", null, \"Test support equipment\")), mdx(\"li\", null, mdx(\"p\", null, \"Threat representation\")))), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Test targets and expendables\")), mdx(\"li\", null, mdx(\"p\", null, \"Operational force test support\")), mdx(\"li\", null, mdx(\"p\", null, \"Models, simulations, and test beds\")), mdx(\"li\", null, mdx(\"p\", null, \"Joint operational test environment\")), mdx(\"li\", null, mdx(\"p\", null, \"Special requirements\"))))))), mdx(\"p\", null, \"Requirements that cannot be met by existing test infrastructure and\\ncapabilities must be identified to A-5R. Gaps/shortfalls associated with\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \" should be addressed through A-8Z. Test capability requirements are\\naddressed in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Resource Plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \") and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses a\\nTime-Phased Investment Planning Document process to advocate for test\\ncapability development. For test capabilities that may require foreign\\nthreat capability, contact \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2N to request and advocate for\\nforeign assets through the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" foreign materiel program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Flight Manuals Program OR Foreign Materiel Program\"\n }, \"FMP\"), \") process.\\nThis process acquires and exploits foreign systems for testing, training\\nand intelligence purposes and may satisfy a threat test capability need.\"), mdx(\"h2\", null, \"Time-Phased Investment Document\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" T-PhID (formerly Test Capability Roadmap) serves as the\\ncornerstone of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\u2019s test capability investment strategy. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" must\\ncommunicate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" requirements 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\"), \" investment forums. Test\\ncapability development must be funded in appropriate investment\\nportfolios to ensure the needed capabilities will be in place, verified,\\nand validated in time to support the test. A-5R continuously gathers \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nrequirements (test capability gaps/shortfalls) through:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Individual program test capability readiness assessments (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessments\"\n }, \"TCRAs\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"SharePoint interface used for spontaneous/asynchronous\\nidentification of requirements by test teams\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"An annual requirements call closely aligned with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \"\"))), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"Test capability requirements priorities are approved by \", 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\"), \"\\nannually, in time to support \", 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\"), \" investment planning processes.\\nSome of the test capability investment forums are listed below.\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Investment Planning and Programming (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Investment Planning and Programming\"\n }, \"TIPP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Central Test and Evaluation Investment Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Central Test & Evaluation Investment Program\"\n }, \"CTEIP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Resource Enhancement Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Resource Enhancement Program\"\n }, \"REP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Threat Systems Working Group (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Threat Systems Working Group\"\n }, \"TSWG\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Joint Aircraft Survivability Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Aircraft Survivability Program\"\n }, \"JASP\"), \")\"))), mdx(\"p\", null, \"A-5R coordinates communication of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test capability requirements to\\nthese investment forums, coordinates review of development proposals to\\nidentify those that may satisfy \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" needs, and monitors program\\ndevelopment ensuring fulfillment of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" needs including completion of\\ncapability verification and validation. There are numerous range\\ncapability requirements that must be addressed as early as possible.\"), mdx(\"h2\", null, \"Determining Range Requirements\"), mdx(\"p\", null, \"In building a mission scenario and determining range requirements, the\\ntester needs to know, for example, the type of target, the number of\\naircraft attacking a target and weapons employed. The tester also needs\\nto consider the range\\u2019s ability to accommodate the operational test\\nwithout environmental impact. The system \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" should contain\\ninformation such as specific tactics and techniques to be employed\\nagainst certain targets and threat systems. Ensure that range personnel\\nhave a full understanding of the specific \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives. The core team\\nshould consult with A\\u20118Z (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \"\\u2011NN post-tasking order) for testing\\nconsiderations at \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \" and A\\u20115R for any other test range or facilities.\"), mdx(\"h2\", null, \"Range Requirement Identification\"), mdx(\"p\", null, \"Carefully thought\\u2011out mission scenarios provide the test team with\\npreliminary test range resource requirements (e.g., threat simulators\\nand instrumentation packages). Early identification of these\\nrequirements is extremely important for advanced range scheduling, test\\nresource plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \") development, and incorporation of new range\\nrequirements into the various range improvement programs and other\\ninvestment forums (need at least 1 year lead time). In support of the\\ncore team, A\\u20115R (A\\u20118Z for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \") provides information on current and\\nlegacy \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" databases that archive data on existing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" test assets\\nand is the Air Force\\u2019s focal point for integrating new \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" range\\nrequirements into the range improvements program. All potential test\\nsites should be considered before the final selection is made.\"), mdx(\"h2\", null, \"Range Selection Considerations\"), mdx(\"p\", null, \"The Test Team may have to give special consideration to test range\\nselection and use. Usually, flight test programs require scheduling of\\nand coordinating with test ranges for some or all test sorties. Test\\nteams need to ensure range availability at the time of their scheduled\\ntest. All major ranges and centers are subject to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" uniform\\nfunding policy and require formal documentation of the test and the\\nsupport needed. The range, in turn, provides a statement of their\\ncapability to support the test. The range process can take 6 months or\\nmore. Although documentation requirements vary among the ranges and\\ncenters, most require the development of a Program Introduction Document\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Introduction Document\"\n }, \"PID\"), \"). When selecting a range, ensure the availability of applicable\\nrange data is considered. To determine specific range initiation\\nrequirements, consult the Universal Documentation System Handbook\\n501\\u201108, available from Secretariat, Range Commanders Council,\\nTEDT\\u2011WS\\u2011RCC, White Sands Missile Range, New Mexico 88002\\u20115110.\"), mdx(\"h2\", null, \"National Cyber Range Considerations\"), mdx(\"p\", null, \"The National Cyber Range (NCR) provides test teams with a capability to\\naccomplish system training and perform disruptive and non-disruptive\\ncyber-attacks on a complete or sub-component of a system under test at\\nmultiple classification levels. The NCR\\u2019s system reset capabilities make\\nit possible for cyber attackers to completely disable or even\\ncatastrophically damage a system without the risk of negatively\\nimpacting operational users or causing unrecoverable damage to the test\\nenvironment. This environment also provides a means for cyber offensive\\nand defensive training as well as basic user training before or during\\ntest execution (to include cybersecurity assessments). As the NCR is a\\ncontained range, connections with outside systems may need to be\\nemulated. Having said that, events can occur exclusively at NCR, or in\\nconjunction with other Joint Mission Environment Test Capability or\\nJoint Information Operations Range nodes. However, programs using unique\\nsystems (i.e., components that won\\u2019t be used by any other programs in\\nthe future) may incur a cost of purchasing the necessary hardware and/or\\nsoftware. Test Directors interested in learning more about the NCR or\\nseeing if the NCR can support their program can contact the NCR directly\\nat \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:osd.pentagon.ousd-atl.mbx.trmc-ncr@mail.mil\"\n }, \"osd.pentagon.ousd-atl.mbx.trmc-ncr@mail.mil\"), \".\"), mdx(\"h2\", null, \"Test Targets\"), mdx(\"p\", null, \"Test targets, when applicable, should be realistic; they should be\\noperationally representative and challenging. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should coordinate\\nwith the applicable \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" to develop the target list. Through A\\u20112N,\\ncoordinate with the appropriate intelligence agency on the design of\\nselected targets, existing and newly developed. A\\u20115R maintains current\\nlists of available aerial test targets in the inventory and is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \"\\nfor obtaining target allocations. A\\u20115R also maintains contacts for other\\ntarget types such as surface targets. Funding for target\\u2011related\\nexpenditures must be included in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \".\"), mdx(\"h2\", null, \"Range Safety Considerations\"), mdx(\"p\", null, \"Ranges and test centers are sensitive to safety considerations and may\\nrequire special test procedures, hardware, or software to reduce the\\nrisk of a mishap during the test. Ranges and test centers frequently\\nrequire safety review boards before start of testing. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should\\nallow sufficient time to support these safety reviews. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" can assist in\\nresolving range safety issues or support in safety reviews. When\\nidentifying required test resources and range requirements, test teams\\nshould ensure weather warnings and advisories are considered in support\\nrequirements (contact A\\u20112/9 for assistance).\"), mdx(\"h2\", null, \"Range Instrumentation Considerations\"), mdx(\"p\", null, \"Instrumentation varies widely among ranges. Therefore, the test team\\nshould carefully select a range to ensure instrumentation is available\\nto provide the required information and to allow the most realistic\\nrepresentation of the operational environment.\"), mdx(\"h2\", null, \"Range Data Processing Considerations\"), mdx(\"p\", null, \"Data processing capabilities and times are considered when the test\\nschedule is prepared. The range equipment user\\u2019s guide, facilities\\nhandbook, or the test support contact may be consulted for typical\\nprocessing times. TDs must also consider the method by which test data\\nis transmitted for analysis (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secret Internet Protocol Router Network\"\n }, \"SIPRNET\"), \", courier, etc.).\"), mdx(\"h2\", null, \"Test Article Instrumentation\"), mdx(\"p\", null, \"Identify the test article instrumentation requirements early to ensure\\nthat instrumentation is sufficient to support test events. There is a\\nfine balance between not compromising the production\\u2011representative test\\narticle and obtaining telemetry from an instrumentation package. Test\\narticle instrumentation should be compatible with the range or test\\nfacility telemetry and data collection systems, with sufficient accuracy\\nand sample rates to enable verification of system performance. If the\\ntest article needs to transmit instrumentation data, the instrumentation\\npackage needs to be compatible with the MIL\\u2011STD\\u20111553 multiplex data bus.\"), mdx(\"h2\", null, \"Program Introduction Document Release Authority\"), mdx(\"p\", null, \"PIDs are executing direction approved in TRPs for obtaining test range\\nsupport. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/CCs are authorized to release PIDs to range agencies.\\nCopies of all PIDs are sent to 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\"), \", A\\u20113 and A\\u20115/8 when\\nreleased to range support agencies by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \". Issues identified\\nduring subsequent \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Introduction Document\"\n }, \"PID\"), \" coordination with the supporting range are\\nhighlighted during the Detachment Commander Monthly Program Update.\"), mdx(\"h1\", null, \"The Use of Modeling and Simulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" includes, but is not limited to, digital \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \", hardware\\u2011in\\u2011the\\u2011loop\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware in the Loop\"\n }, \"HITL\"), \") virtual simulations and test drivers such as data injectors and\\nstimulators. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" also includes physical models of targets, threat\\nrepresentations and combinations of simulations. Testers (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live Fire Test and Evaluation\"\n }, \"LFT&E\"), \",\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) should collaborate early with the program manager\\u2019s (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \") \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nproponent on planned uses of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" for the purpose of identifying \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nrequirements, necessary verification and validation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \") activities,\\nand for securing program office \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" funding (as applicable) \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Instruction\"\n }, \"DODI\"), \"\\xA05000.02 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\xA063\\u2011101/20\\u2011101, 9\\xA0May\\xA017.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses digital \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" for two primary purposes: prediction of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\nperformance and extension of field test results. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware in the Loop\"\n }, \"HITL\"), \"\\nvirtual simulations (and facilities) and test drivers to test system\\nperformance under conditions that cannot be reproduced on an open\\u2011air\\nrange or on actual operational equipment. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct, test\\nconcept and test plan should identify and explicitly describe the use of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to include the use of distributed capabilities for executing\\noperational test events.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" can play a helpful role in optimizing limited open\\u2011air range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \")\\nor ground test facility test time. In addition, testers can examine\\nvarious configurations of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Resulting information\\nprovides insight to maximize return from limited range time and to\\ninvestigate areas of principle interest to the warfighter.\"), mdx(\"p\", null, \"With an adequate representation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", the test team can use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nassets to predict \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance and optimize field test events by\\nestimating \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance boundaries. The optimization enables\\ntailoring of field testing to address those areas that merit further\\nevaluation or are of special interest to the user.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" can fill in gaps associated with field testing in cases where it\\nwould be too expensive or impossible due to lack of capability to\\nconduct an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \"\\u2011only evaluation. The test team would first use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to\\nrehearse and construct valid \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" events and ensure a common baseline.\\nThen once the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is appropriately accredited, the test team can use it\\nto run events beyond the scope of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" events.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"As an example, consider testing an air\\u2011to\\u2011air missile system, where\\nthe primary target of interest is a foreign fighter. Since it would be\\nimpractical or impossible to fire the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" missile at an actual foreign\\naircraft, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" events may consist of firing the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" missile at a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \"\\nfighter configured as a surrogate foreign aircraft. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" would then\\nrepeat the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" drone aircraft firings and \\u201Cextend\\u201D the results to the\\nforeign aircraft of interest by executing the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" with a\\nrepresentation of the foreign aircraft signature and other parameters\\nof interest, provided by an external organization (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Air and Space Intelligence Center\"\n }, \"NASIC\"), \", MSIC, etc.).\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" could then provide the user information regarding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\nperformance versus real threats.\")), mdx(\"p\", null, \"Other reasons for using \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" are safety concerns, environmental concerns\\n(hazmat), treaty limitations, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Security\"\n }, \"OPSEC\"), \" concerns, or support concept\\nlimitations.\"), mdx(\"p\", null, \"Whenever the test team intends to use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" results to capture information\\nin an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Final Report, they need to ensure proper \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" accreditation.\\nTest teams are encouraged to contact A\\u20112/9 early in the life of a\\nprogram, primarily after the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct is completed, for assistance\\nin determining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" applicability and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" requirements. A\\u20112/9 and A-5/8\\nmaintains information on various \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" applications,\\nincluding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\u2011specific \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" guidance.\"), mdx(\"h1\", null, \"Test Capability Accreditation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" often uses test capabilities to create a pseudo-employment or\\ncombat environment in which to conduct the operational testing. These\\ntest capabilities may include \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the employment environment as well\\nas \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Accreditation Guide provides actionable\\ninformation for Test Directors, analysts, engineers, and program\\nmanagers on how best to plan, execute, and report accreditation of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nsystems. The accreditation process involves:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Developing an executable plan, assessment, and report with focus on\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"documenting the results of the accreditation assessment\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Documenting the recommendations in support of the accreditation\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"decision, and\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Documenting lessons learned during accreditation\"))), mdx(\"p\", null, \"Accreditation is applicable when a test capability is used directly or\\nindirectly to provide information that appears in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Final Report.\\nIf a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" intends to draw weapon system capability conclusions (i.e., rate\\nmeasures) based upon the use of a test capability, accreditation is\\nrequired. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" accreditation policy exists to ensure standardization\\nacross test teams and a consistent level of rigor in determining\\nadequacy of test capabilities. Accreditation activities should not\\nexcessively burden test teams or lead to inordinate expense. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nstaff lead for Accreditation is A-2/9. Refer questions about\\nVerification, Validation, and Accreditation to\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"\n }, \"UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"), \".\"), mdx(\"p\", null, \"Test capabilities used solely for test\\u2011planning purposes and assessments\\n(such as observations, EOAs) do not require a formal accreditation,\\nalthough the analyst should exercise a similar process to ensure that\\nthe test capability is adequate and to identify risks involved and how\\nthey may affect the overall test. Any informal accreditation\\ninvestigation procedures (peer review, analyst investigations, etc.)\\nshould be documented to ensure continuity when program personnel change.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\u2019s mission is to Deliver Combat Capability through Operational\\nTest. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" often uses test capabilities to create a pseudo-employment\\nor combat environment in which to conduct the operational testing. These\\ntest capabilities may include \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the employment environment as well\\nas \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". The test capabilities used in a given test do not\\nalways represent the employment environment with 100% accuracy. There\\nare usually some differences in fidelity between the actual combat\\nsystems and test representations. Given these differences, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is\\ncareful in drawing conclusions about \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" capabilities and ensures that\\nthe representation of the employment environment is adequate to draw\\ncredible conclusions. Inherently, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assumes some degree of risk\\nwhen using test capabilities to represent an employment environment or\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" to determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" capabilities. The purpose of accreditation is to\\ncharacterize that risk and ensure the risk is acceptable.\"), mdx(\"p\", null, \"See the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Accreditation Guide accreditation details.\"), mdx(\"h1\", null, \"Test Constraints and Limitations\"), mdx(\"p\", null, \"Limitations may be identified at any point in a program, however the\\nearlier a potential limitation is identified, the more likely it can be\\nresolved without impacting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E credibility. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and core team\\nincluding A-5R and/or A\\u20118Z are encouraged to identify limitations as\\nearly as possible. The documentation provides justification for\\ncontinued improvement and modernization of test capabilities that\\nultimately lead to more useful and relevant \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" reports and better\\nsystems delivered to the warfighter. A limitation is something that\\nwould influence being able to accomplish a credible operational\\nevaluation.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Limitation:\"), \" A limitation affects the ability to evaluate certain\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"aspects of a weapon system or to re\\u2011create certain aspects of the\\noperational environment. Limitations can be due to differences in\\nthe scenario (operational versus test), test capabilities such as\\nthreat simulation, range restrictions (safety, physical airspace),\\nspecific test measurement constraints, numbers of test articles,\\nor the threat lay down (types and numbers). Limitations, once\\nidentified, are carried throughout all phases of the test program\\nunless the underlying factors are no longer applicable. A system\\nthat is not production representative for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E may be\\nidentified as a limitation.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mitigation:\"), \" Each limitation requires the team to plan a\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"mitigation to reduce the risk to the evaluation of the system.\\nMitigation is intended to reduce the impact of the limitation to\\nthe point where the evaluation is still credible. There are\\ntypically few, if any, limitations in conducting credible EOAs and\\nOAs. However, when there are limitations, mitigation may be\\ndifferent for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \", or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is one method used to\\nmitigate a limitation. Teams should actively pursue mitigation of\\na limitation in order to have an adequate test.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Impact\"), \" (of a limitation after mitigation): The impact should\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"describe the extent to which the limitation will (for a plan) or\\ndid (for a report) affect the quality, completeness and/or\\nconfidence of our evaluation of the system under test\\u2019s\\neffectiveness, suitability and mission capability. The intent is\\nto acknowledge limitations and inform the decision\\u2011maker and\\nwarfighter of the extent to which the limitations will or did\\naffect our ability to report weapon system performance. The impact\\nshould clearly state what characteristics or attributes of the\\nevaluation are affected.\")))), mdx(\"p\", null, \"Table 12 provides some example limitations, mitigations, and impacts.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 12. Examples of Limitations\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Limitation\"), mdx(\"th\", null, \"Mitigation\"), mdx(\"th\", null, \"Impact\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Limited UAS System Availability\"), mdx(\"td\", null, mdx(\"p\", null, \"Coordination with operational unit to share assets between the field training unit and IOT&E test\"), mdx(\"p\", null, \"Leverage combat missions\")), mdx(\"td\", null, mdx(\"p\", null, \"Inability to fully evaluate all measures\"), mdx(\"p\", null, \"Cybersecurity not evaluated\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Limited Flight Hours for Reliability, Maintainability and Availability Evaluation\"), mdx(\"td\", null, \"Use reliability availability logistics operations model\"), mdx(\"td\", null, \"Reported values may not reflect actual values in operational use\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Limited capability of Red Team to test weapon system via data link while in flight\"), mdx(\"td\", null, \"Coordinated with AFTC to emulate mission parameters in anechoic chamber to allow Red Team cyber attacks\"), mdx(\"td\", null, mdx(\"p\", null, \"Cyber-exploitation effects not fully evaluated\"), mdx(\"p\", null, \"Inability to fully evaluate all measures\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Lack of Threat Systems at Test Facilities\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"Inability to report system effectiveness versus some threats\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"No integration of Lynx Radar Capability in Mobile Ground Control Station\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"Unable to evaluate Lynx synthetic aperture radar\")))), mdx(\"h1\", null, \"Basis of Estimate for Test Resources\"), mdx(\"p\", null, \"Together, the set of test events, test methodologies and test scenarios\\nform the basis of estimate. They describe why you are testing, what you\\nare going to do and how you are going to do it. Underlying the basis of\\nestimate is a set of assumptions that are validated to the extent\\npossible and documented. For the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct, particular focus is\\nplaced on the high cost (which includes high level of effort) and\\nlong\\u2011lead items. Typical examples of such items are threats,\\ninstrumentation and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" efforts. Some of these items have been\\nidentified throughout the preceding steps. In forming the basis of\\nestimate, these previously identified items are consolidated and test\\ndesigns are reviewed to identify new items. Collectively, there may be\\noverlap between the resources required for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". These should be\\nidentified and a consolidated list of resources should be provided (with\\ntraceability and rationale).\"), mdx(\"p\", null, \"Table 13 contains the basis of estimate contents.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 13. Contents of Basis of Estimate\")), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Content Area\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Content Expectations\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"COIs\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"The COIs define the operations that need to be exercised during \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E and provide 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.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Test Events\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"For the particular test design(s) underlying the test events, a review of the factors and levels provide insight into the resources to establish the conditions. Man\\u2011made 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\\u2011lead 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 parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Test Methodology\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"How a set of test events are executed also provides the rationale or basis for resources. Field\\u2011testing may incur range costs, or possibly even the development of new range capabilities. \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" incurs both costs and potentially long\\u2011lead development. Reviewing the test methodologies provides insight on what might be needed to execute the test events.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Test Scenarios\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"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\\u2011is factors, need to be measured and resources identified in order to collect and analyze data when executing the test scenario.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Assumptions\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"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 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct basis of estimate to refine\\ninitial resource estimates documented in the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". The Detachment\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" updates 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\\neach resource category of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" to determine which line items need\\ncosting and which ones need to be paid for by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \". Table 14 contains\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E support costs breakdown.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table14. Operational \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" Support Costs\")), mdx(\"table\", null, mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"AFOTEC Pays\"), mdx(\"td\", null, \"AFOTEC Does Not Pay\")), mdx(\"tr\", {\n className: \"even\"\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 & penetration assessment/ adversarial assessment)\")))), 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\")), 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(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Identifying Resources\"), \". To move from the basis of estimate to a\\ncompleted test resource plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \") takes a significant amount of effort.\\nThis is an iterative process, and teams will generally refine the\\ninitially planned events/activities based on resource availability,\\nrealism, cost, etc., which are focused on arriving at the best\\ncost-benefit solution.\"), mdx(\"p\", null, \"The actual costing of resources, developing agreements, and many other\\ndetailed steps required to source and cost are not captured here. These\\nspecifics depend on acquisition and test approaches (joint, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" lead,\\nresource types, participants, funding strategies, time-to-test start,\\ninfrastructure developmental needs, etc.), and teams rely on the\\nHeadquarters and Detachment resource managers to support each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct effort.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#test-methodology","title":"Test Methodology"},{"url":"#test-scenarios","title":"Test Scenarios"},{"url":"#test-capability-needs-and-shortfalls","title":"Test Capability Needs and Shortfalls","items":[{"url":"#time-phased-investment-document","title":"Time-Phased Investment Document"},{"url":"#determining-range-requirements","title":"Determining Range Requirements"},{"url":"#range-requirement-identification","title":"Range Requirement Identification"},{"url":"#range-selection-considerations","title":"Range Selection Considerations"},{"url":"#national-cyber-range-considerations","title":"National Cyber Range Considerations"},{"url":"#test-targets","title":"Test Targets"},{"url":"#range-safety-considerations","title":"Range Safety Considerations"},{"url":"#range-instrumentation-considerations","title":"Range Instrumentation Considerations"},{"url":"#range-data-processing-considerations","title":"Range Data Processing Considerations"},{"url":"#test-article-instrumentation","title":"Test Article Instrumentation"},{"url":"#program-introduction-document-release-authority","title":"Program Introduction Document Release Authority"}]},{"url":"#the-use-of-modeling-and-simulation","title":"The Use of Modeling and Simulation"},{"url":"#test-capability-accreditation","title":"Test Capability Accreditation"},{"url":"#test-constraints-and-limitations","title":"Test Constraints and Limitations"},{"url":"#basis-of-estimate-for-test-resources","title":"Basis of Estimate for Test Resources"},{"url":"#initial-resource-estimates","title":"Initial Resource Estimates"}]},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/2-3-Test-Execution-Planning.md"},"frontmatter":{"metaTitle":"Test Execution Planning","metaDescription":"Test Execution Planning"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"bb524d46-cf10-5b52-a8ba-2fbdf2a39f93"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct/page-data.json new file mode 100644 index 00000000..a92428f2 --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"b1925b18-844a-542f-b884-0e0b49b23cb5","title":"Documenting the Operational Test and Evaluation Construct ","slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-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\": \"Documenting the Operational Test and Evaluation Construct \",\n \"metaTitle\": \"Documenting the Operational Test and Evaluation Construct \",\n \"metaDescription\": \"Documenting the Operational Test and Evaluation 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, \"Documentation cannot be overstated. Too many programs efforts have been\\nlost and needed to be re-accomplished because they were not properly\\ndocumented or in some cases, not documented at all. Each of the process\\nsteps above have a recommended documentation approach. Why documentation\\nimportant?\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The only constant with acquisition programs and the people who work\\nthem, is change. Personnel come and go, and programs evolve. When\\nnew people start a program, questions about how and why the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nlooks the way it does.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Leadership often ask why \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E is doing various activities\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" often has questions about the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E approach\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Integrating testing is best served by robust \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E documentation\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provides the foundational products and narrative for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nplan inputs\"))), mdx(\"p\", null, \"Following the test design development, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \" provides the test design\\nproducts to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \". Using these products, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" then begins developing\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing with support from his core team for presentation to 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\"), \" on the date specified in the tasking order. This briefing will\\nbe developed and coordinated electronically for 2\\u2011letter approval. The\\nbriefing is an internal\\u2011only \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" product (i.e. it is not presented to\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \"). The purpose of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing is to convey to 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\"), \",\\nwith a high degree of confidence, the complete beginning\\u2011to\\u2011end scope of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities, resources, and costs with rationale. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing\\nindicates the specific acquisition events that the planned \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities\\nsupport. The Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" presents the acquisition information in a\\nbriefing to 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\"), \" for approval. Tailor the level of detail in\\neach area within the briefing to fit the specific program circumstances.\\nIf a particular subject area in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing template does not apply\\nto a program, do not include that subject area in the briefing.\\nSignificant issues should be resolved with appropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" directorates\\nbefore the formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing must include all\\nsupporting information by using embedded documents, as described in the\\nbriefing template. Following completion of the briefing, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct is updated as required by the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" to reflect the\\ndecisions made. The detailed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing template is found on the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct supports early integration and promotes the\\ncombining, where appropriate, of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events to satisfy both \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives. Remember that throughout \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E planning and execution, the\\nindividual \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives should not be compromised. Early\\nintegration of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" planning provides the foundation for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" A\\n(and beyond) Test and Evaluation Master Plan development and supports\\nidentification \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" requirements needed for RFPs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" is an\\nopportunity to document integration with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" community and reduce\\ndedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events when they have been accomplished satisfactorily in\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E. These events are only removed from dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" when \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nrequirements have been met.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct.md"},"frontmatter":{"metaTitle":"Documenting the Operational Test and Evaluation Construct ","metaDescription":"Documenting the Operational Test and Evaluation 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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"b1925b18-844a-542f-b884-0e0b49b23cb5"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/OTE_construct_development_guide/page-data.json b/sites/oteguide/page-data/OTE_construct_development_guide/page-data.json new file mode 100644 index 00000000..3e0e32b3 --- /dev/null +++ b/sites/oteguide/page-data/OTE_construct_development_guide/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/OTE_construct_development_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"b2dc3f9d-e4b8-5397-bef0-b7b849020a47","title":"OT&E Test Construct Development Guide","slug":"/OTE_construct_development_guide"},"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 Construct Development Guide\",\n \"metaTitle\": \"OT&E Test Construct Development Guide\",\n \"metaDescription\": \"OT&E Test Construct Development Guide\"\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, \"11 February 2021\"), mdx(\"p\", null, \"Last Updated: 26 February 2021\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Primary Responsibility\"\n }, \"OPR\"), \" is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-3 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Collateral Responsibility OR Operational Capability Requirement\"\n }, \"OCR\"), \" is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"OTE_construct_development_guide.md"},"frontmatter":{"metaTitle":"OT&E Test Construct Development Guide","metaDescription":"OT&E Test Construct Development Guide"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"b2dc3f9d-e4b8-5397-bef0-b7b849020a47"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/1-2-INTRODUCTION/page-data.json b/sites/oteguide/page-data/accreditation_guide/1-2-INTRODUCTION/page-data.json new file mode 100644 index 00000000..81f1f6c0 --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/1-2-INTRODUCTION/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/1-2-INTRODUCTION","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"83ad36d5-384d-569c-98bc-dc0438a073b4","title":"INTRODUCTION","slug":"/accreditation_guide/1-2-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\": \"INTRODUCTION\",\n \"metaDescription\": \"INTRODUCTION\"\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\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Accreditation Guide provides actionable information for test\\ndirectors (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"), analysts, engineers, and program managers on how best to\\nplan, execute, and report accreditation of modeling and simulation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \")\\nsystems. The accreditation process involves:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Developing an executable plan, assessment, and report with focus on\\ndocumenting the results of the accreditation assessment\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Documenting the recommendations in support of the accreditation\\ndecision, and\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Documenting lessons learned during accreditation\"))), mdx(\"p\", null, \"Accreditation is applicable when a test capability is used directly or\\nindirectly to provide information that appears in an operational test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \") final report. If a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" intends\\nto draw weapon system capability conclusions (i.e., rate measures) based\\nupon the use of a test capability, accreditation is required. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\naccreditation policy exists to ensure standardization across test teams\\nand a consistent level of rigor in determining adequacy of test\\ncapabilities. Accreditation activities should not excessively burden\\ntest teams or lead to inordinate expense. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" staff lead for\\nAccreditation is A-2/9. Email questions about verification, validation,\\nand accreditation to A-2/9 workflow at:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"\n }, \"UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"), \" .\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/1-2-INTRODUCTION.md"},"frontmatter":{"metaTitle":"INTRODUCTION","metaDescription":"INTRODUCTION"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"83ad36d5-384d-569c-98bc-dc0438a073b4"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/1-3-Test-Capability-Accreditation/page-data.json b/sites/oteguide/page-data/accreditation_guide/1-3-Test-Capability-Accreditation/page-data.json new file mode 100644 index 00000000..4ab34caa --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/1-3-Test-Capability-Accreditation/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/1-3-Test-Capability-Accreditation","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"706007f0-47e3-5f60-ae61-9e1f19f84996","title":"Test Capability Accreditation","slug":"/accreditation_guide/1-3-Test-Capability-Accreditation"},"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 Capability Accreditation\",\n \"metaTitle\": \"Test Capability Accreditation\",\n \"metaDescription\": \"Test Capability Accreditation\"\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\"), \"'s mission is to deliver combat capability through operational\\ntest. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" often uses test capabilities to create a pseudo-employment\\nor combat environment in which to conduct the operational testing. These\\ntest capabilities may include \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the employment environment as well\\nas \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the system under test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"). The test capabilities used in a\\ngiven test do not always represent the employment environment with 100%\\naccuracy. There are usually some differences in fidelity between the\\nactual combat systems and test representations. Given these differences,\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is careful in drawing conclusions about \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" capabilities and\\nensures that the representation of the employment environment is\\nadequate to draw credible conclusions. Inherently, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assumes some\\ndegree of risk when using test capabilities to represent an employment\\nenvironment or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" to determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" capabilities. The purpose of\\naccreditation is to characterize that risk and ensure the risk is\\nacceptable.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/1-3-Test-Capability-Accreditation.md"},"frontmatter":{"metaTitle":"Test Capability Accreditation","metaDescription":"Test Capability Accreditation"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"706007f0-47e3-5f60-ae61-9e1f19f84996"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation/page-data.json b/sites/oteguide/page-data/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation/page-data.json new file mode 100644 index 00000000..15be690b --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"071cffba-5695-53b4-ba0c-53d04035b465","title":"The Use of Modeling and Simulation","slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation"},"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\": \"The Use of Modeling and Simulation\",\n \"metaTitle\": \"The Use of Modeling and Simulation\",\n \"metaDescription\": \"The Use of Modeling and Simulation\"\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\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide,\\\" 11th ed. states that whenever \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is used to\\ncapture information in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Final Report, proper \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" accreditation is\\nrequired. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" includes, but is not limited to, digital \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \",\\nhardware-in-the-loop (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware in the Loop\"\n }, \"HITL\"), \") virtual simulations and test drivers such as\\ndata injectors and stimulators. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" also includes physical models of\\ntargets, threat representations and combinations of simulations. Test\\nplanners (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live Fire Test and Evaluation\"\n }, \"LFT&E\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) should collaborate early with the program\\nmanager's (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \") \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" proponent on planned uses of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" for the purpose of\\nidentifying \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" requirements, necessary verification and validation\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \") activities, and for securing program office \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" funding (as\\napplicable) \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" DoDI\\xA05000.02 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 63-101/20-101, 9 May 17.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses digital \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" for three primary purposes: test planning,\\nprediction of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance, and extension of field test results.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware in the Loop\"\n }, \"HITL\"), \" virtual simulations (and facilities) and test drivers\\nto test system performance under conditions that cannot be reproduced on\\nan open\\u2011air range or on actual operational equipment. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \", test\\nconcept and test plan should identify and explicitly describe the use of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to include the use of distributed capabilities for executing\\noperational test events.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation.md"},"frontmatter":{"metaTitle":"The Use of Modeling and Simulation","metaDescription":"The Use of Modeling and Simulation"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"071cffba-5695-53b4-ba0c-53d04035b465"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions/page-data.json b/sites/oteguide/page-data/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions/page-data.json new file mode 100644 index 00000000..12f8e6aa --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"265e51ab-54fa-5273-95a0-7da430273af9","title":"Verification, Validation and Accreditation Definitions","slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions"},"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\": \"Verification, Validation and Accreditation Definitions\",\n \"metaTitle\": \"Verification, Validation and Accreditation Definitions\",\n \"metaDescription\": \"Verification, Validation and Accreditation Definitions\"\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, \"Definitions are based on DoDI 5000.61, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" Verification, Validation\\n& Accreditation (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \")\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Verification. The process of determining that a test capability\\naccurately represents the developer's conceptual description and\\nspecifications. Verification addresses whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" works as\\nplanned. Verification is typically accomplished by the model\\ndeveloper (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \", system contractor or facility/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" owner).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Validation. The process of determining the degree to which a test\\ncapability provides an accurate representation of the real world\\nfrom the perspective of the intended uses of the test capability.\\nValidation addresses whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" represents reality. Validation\\nis typically accomplished by the model developer (Program Office\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Office OR Project Officer\"\n }, \"PO\"), \"), system contractor or facility/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" owner).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Accreditation. The official certification that a test capability is\\nacceptable for use with a specific application. Accreditation\\naddresses whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is acceptable for a specific use.\\nAccreditation is accomplished by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".\"))), mdx(\"p\", null, \"The accreditation requirement applies to I/Q/F/MOT&Es and Operational\\nUtility Evaluations (UOUEs). Typical test capabilities requiring\\naccreditation may include open air range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \") assets, ground test\\nfacilities, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \", foreign materiel acquisition, test drivers, threat\\nsimulators, targets, blue weapons used as threat surrogates and kill\\nremoval systems.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions.md"},"frontmatter":{"metaTitle":"Verification, Validation and Accreditation Definitions","metaDescription":"Verification, Validation and Accreditation Definitions"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"265e51ab-54fa-5273-95a0-7da430273af9"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation/page-data.json b/sites/oteguide/page-data/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation/page-data.json new file mode 100644 index 00000000..7acae680 --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ccc26af3-452a-5187-81c4-b9c17653a67a","title":"Acquisition Implications of Verification, Validation and Accreditation","slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation"},"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 Implications of Verification, Validation and Accreditation\",\n \"metaTitle\": \"Acquisition Implications of Verification, Validation and Accreditation\",\n \"metaDescription\": \"Acquisition Implications of Verification, Validation and Accreditation\"\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, \"With the inception of agile acquisition, sprints, and rapid testing, it\\nis likely that there will be a unique acquisition approach for each\\nsystem under test. The \", 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 Guide states: \\\"There is no single\\nacquisition approach for a given type of system. The approach is\\ninfluenced by the urgency of need, the technology development\\nrequirements, the amount of money allocated to the program, or any of a\\nvariety of other influences.\\\"\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation.md"},"frontmatter":{"metaTitle":"Acquisition Implications of Verification, Validation and Accreditation","metaDescription":"Acquisition Implications of Verification, Validation and Accreditation"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"ccc26af3-452a-5187-81c4-b9c17653a67a"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/1-7-Accreditation-Concepts/page-data.json b/sites/oteguide/page-data/accreditation_guide/1-7-Accreditation-Concepts/page-data.json new file mode 100644 index 00000000..014207d9 --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/1-7-Accreditation-Concepts/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/1-7-Accreditation-Concepts","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"75584262-1b62-59dd-953e-4ed6a5ccd6fa","title":"Accreditation Concepts","slug":"/accreditation_guide/1-7-Accreditation-Concepts"},"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\": \"Accreditation Concepts\",\n \"metaTitle\": \"Accreditation Concepts\",\n \"metaDescription\": \"Accreditation Concepts\"\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, \"Test teams should plan to accomplish the accreditation and publish the\\naccreditation report prior to test readiness review (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will\\nbe able to begin the test execution phase with confidence that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nis credible. It may not always be possible to complete the accreditation\\nreport prior to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \" but that should be the goal.\"), mdx(\"p\", null, \"Accreditation is about characterizing risk. Specifically, it is about\\nensuring that the risk of using a model and/or simulation to determine\\nand report \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" effectiveness/suitability in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final report is\\nacceptable. Keeping this fundamental principle in mind will help keep\\naccreditation efforts on track. Test teams are encouraged to focus the\\naccreditation effort and documentation describing the risks. The\\naccreditation authority will ultimately decide whether or not to accept\\nthe risks.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/1-7-Accreditation-Concepts.md"},"frontmatter":{"metaTitle":"Accreditation Concepts","metaDescription":"Accreditation Concepts"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"75584262-1b62-59dd-953e-4ed6a5ccd6fa"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/1-8-Risk-Matrix:-Example/page-data.json b/sites/oteguide/page-data/accreditation_guide/1-8-Risk-Matrix:-Example/page-data.json new file mode 100644 index 00000000..a9106dde --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/1-8-Risk-Matrix:-Example/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/1-8-Risk-Matrix:-Example","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"55bd8b8b-e04c-5c97-8a48-792ef1196e16","title":"Risk Matrix: Example","slug":"/accreditation_guide/1-8-Risk-Matrix:-Example"},"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 Matrix: Example\",\n \"metaTitle\": \"Risk Matrix: Example\",\n \"metaDescription\": \"Risk Matrix: Example\"\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 following excerpt is from the Accreditation Report for the Radar\\nSimulation Suite (RSS) used in the Cobra Judy Replacement Multi-Service\\nOperational Test and Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \"), 12 Mar 14.\"), mdx(\"p\", null, \"The test team assessed the impacts to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" and the probability of\\noccurrence using the Air Force operational risk management general\\nassessment practices and definitions presented in Table 5-9, in\\naccordance with the 'Risk Management Guide for DOD Acquisition,' 6th\\nedition, Aug 06.\"), mdx(\"p\", null, \"For each identified risk, the test team has provided a narrative\\ndiscussion and identified major issues. The test team provided an\\noverall risk assessment for the use of RSS in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \".\\\" Table 5-9 defines the\\nseverity of each risk ratings (low, low/medium, medium, medium/high, and\\nhigh). Table 5-10 identifies the assigned risk assessment by the test\\nteam: Figure 5-5 shows the risk management rating scale (RMRS) with\\ngreen (low), yellow (medium) and red (high) ratings. \\\"After rating each\\nprimary risk, the test team populated the RMRS with the associated risk\\nnumber\\\". \\\"Risk 1 was identified as L/M impact and M/H probability of\\noccurrence.\"), mdx(\"p\", null, \"Table 5-9. Risk Severity Definitions\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Impact to OT\"), mdx(\"th\", null, \"Definition\"), mdx(\"th\", null, \"Probability of Occurrence\"), mdx(\"th\", null, \"Definition\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"L\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"L\"), mdx(\"td\", null, \"Unlikely\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"L/M\"), mdx(\"td\", null, \"Negligible\"), mdx(\"td\", null, \"L/M\"), mdx(\"td\", null, \"Seldom\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"Moderate\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"Occasional\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"M/H\"), mdx(\"td\", null, \"Critical\"), mdx(\"td\", null, \"M/H\"), mdx(\"td\", null, \"Likely\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"Catastrophic\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"Frequent\")))), mdx(\"p\", null, \"Figure 5-5. Risk Management Rating Scale\"), 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\": \"705px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/0a7706806fc964c1e3039be52acc7070/d2cbc/image2.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.204633204633204%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAHCAYAAAAIy204AAAACXBIWXMAABcRAAAXEQHKJvM/AAAB+klEQVQozy2SX0hTYRjGn52zYY10i50txoKtbbnpOfvXJgqthCQpMJMksYvuDIMIjC6iCCTIVtSNQTdB7KKbugq6LtyFXYXkxS5Sjw5S0bmtuXX2p6P59g68+PHj+3h5no/v+3DUjDYA4sBlofPRjBh5nBKVh09FJZWC8pJ59Q7ysA1XLgHXbwCDI8DQlBk9sxLkFzaEnh2B8hwIvQa6bwG9OG5FBBDsahZP9Apor4qqVkAtv4NakV3Qoa3Porkdg164iOZWHxrbQK0MaCX2FlMyQtsVUMsJKKPdZgjwCY+9yUrT6V8OSq879t/nJGrWQfSP2QPpDRzohIN9AjXKIO0BF98FNdkVhQ1eMzvAX4hWY5ADbac+RWZOz8XJl0lQ15cYTS546X7WQxM/fPRxxUr1KqhQESj/20AlLinqoCoXFL+D/qRB9Q+gjbcgmOwmFweawp/le/H5aD7xLbocy0RU/9f4qj+TWHPP9ajJ+dDSzcXO5dGFoDqx6FvaLAgrlSLWdovIlTSoGmGVyW1q+AnBLIgcaLSct0iOcYdHuiZ5XJNOZ/i2zeXsNcedsbaz6LcHcOakjIC9DwNu7+CQoftcEsnhq5Cnp+C8MwL3aD+6xi7Az1nogAArW2Jathy6gznBhA38evwVFCZoZPNelPG27v5wtkV7a/4/D8HL4EHCE0QAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image2\",\n \"title\": \"image2\",\n \"src\": \"/static/0a7706806fc964c1e3039be52acc7070/d2cbc/image2.png\",\n \"srcSet\": [\"/static/0a7706806fc964c1e3039be52acc7070/a2ead/image2.png 259w\", \"/static/0a7706806fc964c1e3039be52acc7070/6b9fd/image2.png 518w\", \"/static/0a7706806fc964c1e3039be52acc7070/d2cbc/image2.png 705w\"],\n \"sizes\": \"(max-width: 705px) 100vw, 705px\",\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, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" should strive to publish the accreditation plan early in the test\\nprogram lifecycle (shortly after measures are defined). The\\naccreditation plan establishes acceptance criteria, to which the\\nvalidation plans and reports should respond. Publishing the\\naccreditation plan early ensures AFOTECs opportunity to influence the\\nscope and nature of subsequent \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" activities and products, and to enter\\ndiscussions early with the developer of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" capability. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \"\\nexpects the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" to include details on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" approach, or a reference\\nto such details \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" memo, 14 Mar 16.\"), mdx(\"p\", null, \"Known baseline. To the extent possible, the accreditation acceptance\\ncriteria should be based upon comparing model output to a known\\nbaseline. For example, for a threat, the known baseline may be the\\nIntelligence community assessment of threat behavior. For a target drone\\naircraft the known baseline may be measured signature data of a foreign\\naircraft. Strive to establish quantitative criteria whenever possible.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/1-8-Risk-Matrix:-Example.md"},"frontmatter":{"metaTitle":"Risk Matrix: Example","metaDescription":"Risk Matrix: Example"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"55bd8b8b-e04c-5c97-8a48-792ef1196e16"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/1-9-Previous-Accreditation/page-data.json b/sites/oteguide/page-data/accreditation_guide/1-9-Previous-Accreditation/page-data.json new file mode 100644 index 00000000..87fcad13 --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/1-9-Previous-Accreditation/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/1-9-Previous-Accreditation","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"a61a91f7-77e2-51e0-895c-e2340e36dd8e","title":"Previous Accreditation","slug":"/accreditation_guide/1-9-Previous-Accreditation"},"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\": \"Previous Accreditation\",\n \"metaTitle\": \"Previous Accreditation\",\n \"metaDescription\": \"Previous Accreditation\"\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, \"There may be an opportunity to use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" that has been accredited in the\\npast, either by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" or by another organization. For example, if\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" or another organization has used the intended \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" for similar\\npurposes, it may be possible to focus the accreditation effort on \\\"delta\\naccreditation.\\\" In this case, the accreditation team will need to\\narticulate how the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" has changed, if at all, since last accredited. In\\naddition, the team must illustrate how use of the previously accredited\\nmodel compares to the proposed use.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not make blanket or class accreditations. However, if \\\"delta\\naccreditation\\\" is feasible or the upcoming test, a new accreditation\\nreport is not required. Depending on the intended use of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \", the\\naccreditation effort may consist of a comprehensive new report or a\\none-page memo for record. When beginning any accreditation effort, it is\\nbest to examine what has been done in order to avoid potential\\nduplication of effort or unnecessary documentation and staffing. Consult\\nwith \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" A-2/9 to help decide the best route to take. Table 2 describes\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" offices that have a role in the Accreditation process as well\\nas the correlation (if any) to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" roles as outlined in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 16-1001,\\nand associated responsibilities.\"), mdx(\"p\", null, \"Table 2. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" Roles and Documentation Responsibilities\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Office\"), mdx(\"th\", null, \"AFI Role Correlation\"), mdx(\"th\", null, \"Responsibilities\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"AFOTEC (typically the TD)\"), mdx(\"td\", null, \"Requiring Agency\"), mdx(\"td\", null, \"Establish the need for M&S for use in a particular program\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"AFOTEC Technical Advisor (CA)*\"), mdx(\"td\", null, \"Accreditation Authority\"), mdx(\"td\", null, \"Approves AFOTEC accreditation plans and reports\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Det Technical Advisor (TA)\"), mdx(\"td\", null, \"Accreditation Agent\"), mdx(\"td\", null, \"Review and sign accreditation plans and reports prior to submission to CA\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Det Commander*\"), mdx(\"td\", null, \"Accreditation Authority\"), mdx(\"td\", null, \"Approves and signs accreditation plans/reports originating from his/her Detachment\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Det TD\"), mdx(\"td\", null, \"Accreditation Agent\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Reviews/signs accreditation plans/reports documenting adequacy of test capabilities to support OT&E\")), mdx(\"li\", null, mdx(\"p\", null, \"Briefs M&S developer on Accreditation Plan and ensures V&V plans/reports meet Accreditation requirements identified in Accreditation Plan\")), mdx(\"li\", null, mdx(\"p\", null, \"Briefs the accreditation approach to A\\u20112/9 during the TR\")), mdx(\"li\", null, mdx(\"p\", null, \"Ensures that all test capabilities are accredited\")), mdx(\"li\", null, mdx(\"p\", null, \"Sends signed copies of accreditation plans and reports to A\\u20113 and HO for records management and archiving\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Det Analyst\"), mdx(\"td\", null, \"Accreditation Agent\"), mdx(\"td\", null, \"Authors, signs and executes accreditation plans and authors accreditation reports for all test capabilities\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operations Directorate (A\\u20113)\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Reviews accreditation plans/reports documenting adequacy of test capabilities to support OT&E\")), mdx(\"li\", null, mdx(\"p\", null, \"Validates test capability requirements\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Intelligence, Analyses and Assessments Directorate (A\\u20112/9)\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Assists the TD with the accreditation process as directed in the program tasking order\")), mdx(\"li\", null, mdx(\"p\", null, \"Advises on VV&A policy and process\")), mdx(\"li\", null, mdx(\"p\", null, \"Post final accreditation plans/reports to AFOTEC\\u2011SharePoint site.\")), mdx(\"li\", null, mdx(\"p\", null, \"Records the decision on whether accreditation is required or not in a memo for the Det/TD post ITD\")), mdx(\"li\", null, mdx(\"p\", null, \"Reviews accreditation plans/reports for technical adequacy and advises CA accordingly\")), mdx(\"li\", null, mdx(\"p\", null, \"Staffs plans/reports through HQ via SSS; tracks comments and revisions, obtains CA signature\")), mdx(\"li\", null, mdx(\"p\", null, \"Monitors AF and DoD VV&A policy and communicates policy changes within AFOTEC\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Special Projects Division for NTTR (A\\u20118Z)\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Assists the TD as directed in the program tasking order\")), mdx(\"li\", null, mdx(\"p\", null, \"Maintains cognizance of accreditation activities associated with NTTR assets\")), mdx(\"li\", null, mdx(\"p\", null, \"Advises test team on the likelihood of successful accreditation for specific test capabilities\")), mdx(\"li\", null, mdx(\"p\", null, \"Maintains library of accreditation plans/reports associated with NTTR\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"A-5R\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"Monitors test capability through participation in AF and DoD investment processes ensuring V&V plans support accreditation, are fully funded, and are included in the project management plans\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"HO\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Receives copies of accreditation plans/reports from the TD\")), mdx(\"li\", null, mdx(\"p\", null, \"Maintains library of all AFOTEC accreditation plans/reports\")), mdx(\"li\", null, mdx(\"p\", null, \"Maintains a library of verification and validation reports for facilities AFOTEC commonly uses\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"V&V Manager\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"N/A\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"V&V Agent\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"N/A\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"PM/Developer\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"N/A\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*For the F-35 program and BMDS, the AFOTEC Commander (as a member of the F-35 Executive Committee) serves as the accreditation authority\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, \"Verification and validation are the responsibility of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\ndeveloper/owner. Figure 1 illustrates an overview of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" process,\\nincluding the roles/responsibilities associated with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \". The bold\\nvertical line indicates the distinction between the capability owner\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" manager & \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" agent) \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \") and the capability user (Accreditation\\nAgent & Accreditation Authority).\"), mdx(\"p\", null, \"Figure 1. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" 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\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/12f6c67135c455d9270eed34e455ee4c/b9024/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\": \"58.687258687258684%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAACHVAAAh1QEEnLSdAAAC70lEQVQoz0WTTW8bVRSGza9gw5oVEgsqUNQVEisE/wFSiUioZAESlaBNKK2qdoUqUASFNsFNgkqhjYOJkiZOHNsNSVyPP8dj7PlyJuOx59NNEKzg4Y7TqItX956jc885997nJGxnwMD16A/ckZxY/XjvjeQ8W3vCl9nceh7rusIXcOjE8keKzyZczyMMAoJnOh6GRGFEWY3YafqUtZCKFuG4EflcFt8PGA4jdKPL1Suf8uXUBFenzzN96WNMwxAJRcWTZD6u51PXHErtHk2jP7I1a0Dxzx414d/c2iIMA1EwEF0OaDYkVnMFvkhuMJ3MsNs8IBFfwfd9joY+skjy4V2F8VmFG+mO6Dbg60c6k4ttzs3K3P51nadRiGm7mD2faHjMstRnPKkxsaAznzdJeKILz4+IomPaVsDUQ40bKwazORM/8FgoyFxcanE5pTO3lKXvhULivdw+fx+F5OUB799p8dFChxXpkITd66HqXSLtLkfKZYLmddS9axS2l1F2b+HKF9nY+Ry/doXVB19h2RZNpYrZ7VBSs9jyN3RrM9j1mxyouyQ0w6b6ZJ3/pDGonCUqvcmje6/QLi0S5cdwC6/zT/EN3NQLJOfO44d/0ajXMLoOVvUS/z45A8238FdfQtn7joTR7VEpbqAtv4qZPkPt/svM/zBGtfGY0oN3aKTeRk6/y87iWZIPv6V7YAipGJaDmnkPa+U1rNUx9u68SEfOiA51g0q1TkVRSOX2uZUu0JD2kSoya9k/SOckZtZa4p2HbGY2kaQilUpZdFmnXJXYEfbt37dptGSB0xEJ0zQp1xSmUl3Oid+a/EnDC4csFS0m7+l8cl/ng2RLoGTzuJDHDZ9yKJj0BKvfZy0m5nXGf1TZb7sjKka/bDsuc9s6N9c0ZtY1jMMBqf0uF35uce03lc9+abGr2GSyeSznZIpCwW0ccz2tCnUEpz2BVPAc7HhaYh5jwE/t0ZgJxUXjBPlcbgT2aczpMHj+iR2f/x/Aai7Zqmjx/AAAAABJRU5ErkJggg==')\",\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/12f6c67135c455d9270eed34e455ee4c/e3189/image3.png\",\n \"srcSet\": [\"/static/12f6c67135c455d9270eed34e455ee4c/a2ead/image3.png 259w\", \"/static/12f6c67135c455d9270eed34e455ee4c/6b9fd/image3.png 518w\", \"/static/12f6c67135c455d9270eed34e455ee4c/e3189/image3.png 1035w\", \"/static/12f6c67135c455d9270eed34e455ee4c/b9024/image3.png 1203w\"],\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":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/1-9-Previous-Accreditation.md"},"frontmatter":{"metaTitle":"Previous Accreditation","metaDescription":"Previous Accreditation"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"a61a91f7-77e2-51e0-895c-e2340e36dd8e"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/2-1-Accreditation-Process/page-data.json b/sites/oteguide/page-data/accreditation_guide/2-1-Accreditation-Process/page-data.json new file mode 100644 index 00000000..7553a79d --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/2-1-Accreditation-Process/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/2-1-Accreditation-Process","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"7b85e05c-e001-56c8-af9a-e4b06eb103c7","title":"Accreditation Process","slug":"/accreditation_guide/2-1-Accreditation-Process"},"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\": \"Accreditation Process\",\n \"metaTitle\": \"Accreditation Process\",\n \"metaDescription\": \"Accreditation Process\"\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\": \"Detachment\"\n }, \"Det\"), \" will email unclassified accreditation plans/reports to the A-2/9\\nworkflow address: \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"\n }, \"UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"), \" . If the\\nplan/report is classified, contact the A-2/9 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" or workflow for\\ninstructions. The A-2/9 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will place accreditation plans/reports into\\n2-ltr coordination for 5 days and adjudicate all comments. Upon\\ncompletion, the A-2/9 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will place accreditation plans/reports into \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \"\\ncoordination for review and signature by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \". The \\\"\", 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 Guide\\\"\\nshows \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s accreditation process (Figure 2 below). Accreditation\\nactivities begin during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct development with\\nidentification of test capability requirements, followed by development\\nof an accreditation memo.\"), mdx(\"p\", null, \"Figure 2. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Accreditation Process\"), 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/36b9575e92d08f0fe1b26f2d1ff7bef4/d5b59/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\": \"54.440154440154444%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAYAAAB/Ca1DAAAACXBIWXMAACHVAAAh1QEEnLSdAAADhklEQVQozwF7A4T8AGt/jxN3jqAYdoyeF01hbw1viJsShJ6zF2h+jw4AAAAAWm59GlhndCR1dXbPfXt85IB9fNR+e3zafXx+435+f+prbnJdAAAAAADL/wBihqcAAFWHteBbj8D2W5DB+kR3prdTh7fhW428+1CFt+M/c6SXVoe08liKuPZkmMn8Vo3A5nV3fFtce5idW468/1+OufNgkb39WIy8zigrMgn//wAAAF2Lr+hfh6T/Y5Gz/2uYt9lhjKv0WIGf/1+Lrv9llLfdXIyx+FN/o/5Tha7/VpHF9nB9hmZZg6mdRX2w/z5xofpFfrP/T4/K+QBX2wuRaVMAAFqMtvNah6z/XI20/2CPs+Bhkrn9YZG4/2SUuv9mk7TiZJGz/2CJpv9plLP/caHD/5SppH+Ao7S0ZpKx/2ONrP9khqH/ZYGc9KxpPk3DYB0tAEh+r6ZEe660RXuvtz5xoI9OisGsT43Ht0uHwLRAdqmHQnipnT5xoaJBdaShSH2tokdtjhZZhalNVI/Apo+Mi7nDfkr/t4FU/L9+S//KcDLRAFaVhgD///8B//+xAwB/ngBOn5oA/4QAAv+ZIwQAAP8APYKNAAJwogAtn94Aad3/ANv//wDJ//8A7cfDALZWC0u+YB//uWAk/rl+Tv/IgEvWADpfInxMbjfeUHE54EVrLLkwVRlhUnY72lV6POJRdzjONlsihVl8Q81bf0XNYIRL1lNzP5hcfEmzc5Rj4YOXauXAlGD80JZm9NqSWf/VdzXBAF+CS9Nqilj/X4NK/2mPUv9qjFfbZYhR/2aIUv9wlVr/cJFc+nWYYP93mGP/eZtm/3ycafd3l2T4bpBZ/22SVv+Nm3xNu492GpxJFCSHQRQRAGqMVsJ2lGX/YYBP+miJVPpukFvRZolS9l5/S/1hhUz8YYZK61V4P/hGZjL7TXMz/VB7NOo9XybmOl4j/0NsJ/UTPQAgeX5LAONPDwCfSxYAAEdvK8tAZij/PWIi/0ZxKf9BaiXKQGcl/j1jJP9Hcir/RnEq8URsKf9IcSz/TXkw/0t2L/NGbSzyUn40/1SBNf88WCcrI1gaAHNkLgOsXyoBAEZsLKtDZyrjR20t2k54MtpDZyusR20t00hvLtpKci/aRGorxE13MctPezLPUHwy0UdtLb9JcS63UHwyy0pzLsIvSR0fNFEhADdWIwEAAAAA7O+2KeUEI+AAAAAASUVORK5CYII=')\",\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/36b9575e92d08f0fe1b26f2d1ff7bef4/e3189/image4.png\",\n \"srcSet\": [\"/static/36b9575e92d08f0fe1b26f2d1ff7bef4/a2ead/image4.png 259w\", \"/static/36b9575e92d08f0fe1b26f2d1ff7bef4/6b9fd/image4.png 518w\", \"/static/36b9575e92d08f0fe1b26f2d1ff7bef4/e3189/image4.png 1035w\", \"/static/36b9575e92d08f0fe1b26f2d1ff7bef4/d5b59/image4.png 1370w\"],\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 memo from the Director, A\\u20112/9 to the detachment commander identifies\\nthe test capability requirements, accreditation documentation\\nrequirements, initial timelines, and relevant \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" documents available.\\nUpon receipt of this memo, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" (and designated test team members/with\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" assistance) begins tracking \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" resource expenditures including\\nmanpower and dollars.\"), mdx(\"p\", null, \"During each Test Concept Technical Review, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" will discuss the test\\ncapabilities to be used and how the accreditation will be accomplished\\nbased on the guidelines for use of the capability. A\\u20112/9 advises whether\\naccreditation is required or not. Throughout test planning, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"\\nshould inform A\\u20112/9 on the accreditation approach during scheduled\\ntechnical reviews, including proposed level of effort, completion dates\\nand accreditation resource requirements. The information enables A\\u20112/9\\nto ensure technical adequacy on the overall accreditation approach and\\nprevent unnecessary expenditure of resources. As the program progresses,\\nthe test team should identify planned use of test capabilities and the\\nassociated accreditation approach in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" and test concept briefings.\"), mdx(\"p\", null, \"The next step is an accreditation concept discussion, typically\\nconducted via \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Video Teleconference\"\n }, \"VTC\"), \". This discussion is between the test team and A-2/9.\\nThe purpose is to initiate dialogue and agree on assumptions and the\\noverall accreditation approach before initiating development of the\\naccreditation plan. The topics shown in Figure 5-8 help frame this\\ndialogue. After internal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" discussion it is a good idea to discuss\\nthe accreditation concept with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" action officer, if \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" is\\ninvolved, to ensure there are no disconnects between \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \"\\nwith respect to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \".\"), mdx(\"p\", null, \"Following completion of the accreditation concept discussion the test\\nteam initiates development of the accreditation plan(s). Many test\\ncapabilities have existing validation and/or accreditation reports that\\nmay be useful for current and future \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" efforts. A\\u20118Z, A\\u20112/9 and the\\nHistory Office (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"HQ AFOTEC History Office\"\n }, \"HO\"), \") may have copies of previous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" documents. The\\naccreditation plan establishes the benchmark for all remaining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \"\\nactivities. Per \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\xA016-1001, \\\"Acceptability criteria are the most\\nimportant content of the accreditation plan and should be presented as\\nminimum criteria for accreditation.\\\" The team should place priority on\\ndeveloping meaningful accreditation acceptance criteria. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" submits\\nthe plan to A-2/9, who reviews and coordinates the plan and submits the\\nplan to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \" for approval.\"), mdx(\"p\", null, \"Once the plan is approved, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" distributes the plan to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" capability\\nowners so they can prepare \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" plans/reports that will produce data to\\nallow \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" to determine whether or not the acceptance criteria have\\nbeen met. Following receipt of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" reports, the test team executes\\nthe accreditation plan. This step primarily involves comparing the\\nresults of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" to the acceptance criteria.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/2-1-Accreditation-Process.md"},"frontmatter":{"metaTitle":"Accreditation Process","metaDescription":"Accreditation Process"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"7b85e05c-e001-56c8-af9a-e4b06eb103c7"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/2-2-Test-Capability-Accreditation-Concept/page-data.json b/sites/oteguide/page-data/accreditation_guide/2-2-Test-Capability-Accreditation-Concept/page-data.json new file mode 100644 index 00000000..deaba12b --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/2-2-Test-Capability-Accreditation-Concept/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"4791a062-9943-5fbd-88e4-49693e4bb498","title":"Test Capability Accreditation Concept","slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept"},"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 Capability Accreditation Concept\",\n \"metaTitle\": \"Test Capability Accreditation Concept\",\n \"metaDescription\": \"Test Capability Accreditation Concept\"\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, \"Discussion Topics\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Describe system under test and its \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Include threats, targets and/or situations likely to require \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Describe what must be simulated and why (much simulate moving\\nvehicle targets; insufficient quantity at test ranges, etc.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Explain why you selected a particular test capability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identify measures that require test capability to rate\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Describe the risks of using a specific test capability in terms of\\nthe effect on rating specific measures of effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"),\\nmeasures of performance (MOPs), and measures of suitability (MOSs).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What is the likelihood of drawing an incorrect conclusion on\\neffectiveness/suitability?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Explain how you will convince yourself the capability is acceptable\\nfor use in a specific test\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identify accreditation criteria\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Typically involves comparison of test capability performance to some\\nknown or expected values\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Explain your accreditation timing\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" information is available or missing?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What are the risks of accrediting before the start of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E versus\\nafter?\"))), mdx(\"p\", null, \"Based upon review of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" reports, the test team produces an\\naccreditation report. The accreditation report summarizes the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" report\\nfindings and concludes with a recommendation to either: accredit,\\naccredit with limitations, or do not accredit the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \". The typical\\noutcome will be accredit\", \"-\", \"-accredit with limitations will be by\\nexception. The accreditation report should include a summary statement\\nthat the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is accredited for a specific \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to address specific\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"/MOPs/MOSs. The test team submits the accreditation report to A-2/9\\nfor review and coordination and then A-2/9 submits the report to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \" for\\napproval.\"), mdx(\"p\", null, \"From a timing standpoint the team should strive to publish the\\naccreditation report prior to test readiness review (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \"). This ensures\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" leadership is aware of all risks associated with using \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" prior\\nto the use of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \". Sometimes it is not possible to publish the\\naccreditation report prior to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \". In this case the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should include\\ninformation in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \" briefing characterizing the risk associated with\\nusing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" and any mitigating factors, and include information regarding\\nwhen the accreditation report will be published.\"), mdx(\"p\", null, \"Next, the test team will use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" as planned (e.g. execute the test),\\nconsider lessons learned associated with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" process, and document\\nthose lessons learned in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final report.\"), mdx(\"p\", null, \"Finally, A-2/9 reviews the lessons learned and considers adjustments to\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" process as needed. A-2/9 ensures the accreditation\\nplans/reports are archived and submits any necessary metadata to the\\nappropriate agency.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/2-2-Test-Capability-Accreditation-Concept.md"},"frontmatter":{"metaTitle":"Test Capability Accreditation Concept","metaDescription":"Test Capability Accreditation Concept"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"4791a062-9943-5fbd-88e4-49693e4bb498"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format/page-data.json b/sites/oteguide/page-data/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format/page-data.json new file mode 100644 index 00000000..8dae078f --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"556977b4-e902-5298-824d-e46f15fbb644","title":"Accreditation Plan and Report Format","slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format"},"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\": \"Accreditation Plan and Report Format\",\n \"metaTitle\": \"Accreditation Plan and Report Format\",\n \"metaDescription\": \"Accreditation Plan and Report Format\"\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 sample format for accreditation plans and reports is located on the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint.\"), mdx(\"p\", null, \"The format is based upon MIL\\u2011STD\\u20113022, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Standard Practice\\nDocumentation of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" for Models and Simulations. Accreditation\\ndocumentation need not be voluminous, but should provide sufficient\\ninformation to enable the accreditation authority to make the\\naccreditation decision. The selected format (determined collaboratively\\nby the test team and A-2/9) will depend on past use of the test\\ncapability, the number of measures impacted, resources needed for\\naccreditation, the test schedule and other factors. If the plan or\\nreport is distributed outside of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", it needs to be properly marked\\nalong with the appropriate distribution statement.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/2-3-Accreditation-Plan-and-Report-Format.md"},"frontmatter":{"metaTitle":"Accreditation Plan and Report Format","metaDescription":"Accreditation Plan and Report Format"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"556977b4-e902-5298-824d-e46f15fbb644"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/2-4-Accreditation-References-and-Resources/page-data.json b/sites/oteguide/page-data/accreditation_guide/2-4-Accreditation-References-and-Resources/page-data.json new file mode 100644 index 00000000..4e7db4ce --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/2-4-Accreditation-References-and-Resources/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/2-4-Accreditation-References-and-Resources","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"7f2ba1ce-ef28-551b-a259-6b411d664dc9","title":"Accreditation References and Resources","slug":"/accreditation_guide/2-4-Accreditation-References-and-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\": \"Accreditation References and Resources\",\n \"metaTitle\": \"Accreditation References and Resources\",\n \"metaDescription\": \"Accreditation References and 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, \"The following are organizations that the accreditation team can\\nreference for assistance in gathering pertinent accreditation\\ninformation.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/2-4-Accreditation-References-and-Resources.md"},"frontmatter":{"metaTitle":"Accreditation References and Resources","metaDescription":"Accreditation References and 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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"7f2ba1ce-ef28-551b-a259-6b411d664dc9"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation/page-data.json b/sites/oteguide/page-data/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation/page-data.json new file mode 100644 index 00000000..3ed97dba --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"03aff94c-3d0a-5976-9281-db20f6cbf914","title":"Air Force Agency for Modeling and Simulation","slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation"},"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\": \"Air Force Agency for Modeling and Simulation\",\n \"metaTitle\": \"Air Force Agency for Modeling and Simulation\",\n \"metaDescription\": \"Air Force Agency for Modeling and Simulation\"\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 Air Force Agency for Modeling and Simulation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Agency for Modeling and Simulation\"\n }, \"AFAMS\"), \") (\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.afams.af.mil\"\n }, \"http://www.afams.af.mil\"), \" ) is a field operating agency of the Deputy\\nChief of Staff for Operations, Plans and Requirements, Headquarters U.S.\\nAir Force. The Agency is located in Orlando\\\\'s Central Florida Research\\nPark, with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \", Joint, service, contractor, and educational\\norganizations focused on modeling and simulation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Agency for Modeling and Simulation\"\n }, \"AFAMS\"), \"\\\\' mission\\nis to provide seamless integration of cross-functional Live Virtual\\nConstructive-Operational Training environments that allow warfighters to\\nmaximize performance and decision making. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Agency for Modeling and Simulation\"\n }, \"AFAMS\"), \" works closely with\\nCombatant Commands, Major Commands, the Air Force Reserve Command, the\\nAir National Guard, the Air Force Headquarters, Direct Reporting Units,\\nand Field Operating Agencies to provide the necessary development and\\nimplementation standards for common access and interoperability within\\nthe Live, Virtual and Constructive (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \") Training domains for efficient\\nand secure global operations.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation.md"},"frontmatter":{"metaTitle":"Air Force Agency for Modeling and Simulation","metaDescription":"Air Force Agency for Modeling and Simulation"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"03aff94c-3d0a-5976-9281-db20f6cbf914"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office/page-data.json b/sites/oteguide/page-data/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office/page-data.json new file mode 100644 index 00000000..b19f856c --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"f7ebe556-8d76-58b1-84da-4e3bf22cc7e0","title":"Modeling and Simulation Coordination Office","slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office"},"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\": \"Modeling and Simulation Coordination Office\",\n \"metaTitle\": \"Modeling and Simulation Coordination Office\",\n \"metaDescription\": \"Modeling and Simulation Coordination Office\"\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 Department of Defense (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \") Modeling and Simulation Coordination\\nOffice (M&\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Contracting Official\"\n }, \"SCO\"), \") ( \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.msco.mil)\"\n }, \"http://www.msco.mil)\"), \" is the focal point for\\ncoordinating all matters regarding modeling and simulation across the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" for the Undersecretary of Defense (Acquisition, Technology and\\nLogistics) \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.acq.osd.mil/\"\n }, \"(\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \"(\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L))\"), \" . M&\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Contracting Official\"\n }, \"SCO\"), \" recommends\\npolicies, plans, and programs to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \"(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L) that supports the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nStrategic Vision and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" priorities. Among other documents, MSCO\\nmaintains the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" Recommended Practices Guide.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" provides the M&\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Contracting Official\"\n }, \"SCO\"), \" a descriptive summary and metadata for all\\naccredited models or simulations that can potentially be reused by other\\nprograms.\"), mdx(\"p\", null, \"On 18 March 2020, M&\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Contracting Official\"\n }, \"SCO\"), \" released a new \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" Guidebook. The guidebook is a\\ncompendium of short articles that capture key concepts in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" realm.\\nAccording to their website, the intent of the guidebook is to \\\"provide\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" practitioners an information resource to leverage existing\\nknowledge, past experience, and available tools.\\\"\"), mdx(\"p\", null, \"Organizations supported by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" need visibility into the tools, data and\\nservices that meet their requirements. The DOD \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" steering committee\\nhas established a web based search capability to provide a card catalog\\nlevel of detail about \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" tools, data and services. The catalog is\\noperated by the DMSC. Register to view this catalog here:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:MSCatalogHelpDesk@mscatalog.msco.mil\"\n }, \"MSCatalogHelpDesk@mscatalog.msco.mil\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office.md"},"frontmatter":{"metaTitle":"Modeling and Simulation Coordination Office","metaDescription":"Modeling and Simulation Coordination Office"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"f7ebe556-8d76-58b1-84da-4e3bf22cc7e0"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/2-7-Best-Practices/page-data.json b/sites/oteguide/page-data/accreditation_guide/2-7-Best-Practices/page-data.json new file mode 100644 index 00000000..c24bd58e --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/2-7-Best-Practices/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/2-7-Best-Practices","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"929e3581-edd2-5a33-9e0a-e08d4ce97a38","title":"Best Practices","slug":"/accreditation_guide/2-7-Best-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\": \"Best Practices\",\n \"metaTitle\": \"Best Practices\",\n \"metaDescription\": \"Best Practices\"\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(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"It is OK to conclude that the test capability is inadequate or to\\nrecommend that the test capability not be accredited for use;\\ninclude justification and documentation. Establish acceptance\\ncriteria in terms of comparison to known baseline. Can recommend\\nAccredit, accredit w/ limitations, don't accredit\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Computer-based constructive models must be approved for use on Air\\nForce networks; start early\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure that a clear link exists between test capability use and test\\nlimitations\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Convince the Accreditation Authority the level of risk is\\nacceptable. Answer the question: \\\"To what extent is this\\nrepresentation adequate for purposes of a given test?\\\"\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/2-7-Best-Practices.md"},"frontmatter":{"metaTitle":"Best Practices","metaDescription":"Best Practices"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"929e3581-edd2-5a33-9e0a-e08d4ce97a38"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/2-8-Summary/page-data.json b/sites/oteguide/page-data/accreditation_guide/2-8-Summary/page-data.json new file mode 100644 index 00000000..f883952b --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/2-8-Summary/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/2-8-Summary","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"0e1df3ab-9dc8-56e2-a3d3-1cd03dbfedc7","title":"Summary","slug":"/accreditation_guide/2-8-Summary"},"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\": \"Summary\",\n \"metaTitle\": \"Summary\",\n \"metaDescription\": \"Summary\"\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, \"Models and simulations will not be 100% accurate and there is risk\\nassociated with drawing inferences about the models and their\\napplicability to actual systems. There is potential to draw incorrect\\nconclusions about \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance based on use of a particular test\\ncapability. Remember AFOTECs credibility is at stake with every report.\\nEnsuring due diligence will result in a robust and valid accreditation\\nprocess. Inherently, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assumes some degree of risk when using test\\ncapabilities to represent an employment environment to determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\ncapabilities. The purpose of accreditation is to assess and document\\nthat risk.\"), mdx(\"p\", null, \"Remember that acceptability criteria are the most important concepts of\\nAccreditation. Make sure to consider the following: How confident are\\nyou that the proposed test capability is acceptable for use during the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"? List the pros and cons. What acceptability criteria did you\\nestablish? What research/analysis did you perform? How did you reach\\nyour conclusions? The accreditation plan and report configuration is at\\nthe discretion of the test team. It is acceptable to have one plan and\\nmultiple reports, or multiple plans and multiple reports. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nSharePoint site contains current accreditation information and\\ntemplates, including the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" Recommended Practices Guide.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/2-8-Summary.md"},"frontmatter":{"metaTitle":"Summary","metaDescription":"Summary"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"0e1df3ab-9dc8-56e2-a3d3-1cd03dbfedc7"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/2-9-References-and-Resources/page-data.json b/sites/oteguide/page-data/accreditation_guide/2-9-References-and-Resources/page-data.json new file mode 100644 index 00000000..8d01f289 --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/2-9-References-and-Resources/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/2-9-References-and-Resources","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"908c250b-faf5-5552-9ffe-e6ad786cc8bc","title":"References and Resources","slug":"/accreditation_guide/2-9-References-and-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\": \"References and Resources\",\n \"metaTitle\": \"References and Resources\",\n \"metaDescription\": \"References and 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, mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Accreditation Statement.\"), \" \\\"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" accredits \", \"[\", \"model\", \"]\", \" for use\\nin \", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\", \"]\", \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to address the following\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \":\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"\\\"\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example \\\"Delta Accreditation\\\" Memo\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://www.msco.mil/DocumentLibrary/MSReferences/PolicyGuidance/DMSRA_Ver1_0_Dist_A.pdf\"\n }, \"Defense Modeling and Simulation Reference Architecture, Version\\n1.0\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/513401p.pdf\"\n }, \"DoDD 5134.01, Under Secretary of Defense for Acquisition,\\nTechnology, and Logistics (\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \"(\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L), April 1,\\n2008\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/500059p.pdf\"\n }, \"DoDD 5000.59, \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Modeling and Simulation (\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \") Management, August\\n8,\\n2007\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/832002p.pdf\"\n }, \"DoDD 8320.02, Data Sharing in a Net-Centric Department of Defense,\\nApril 23,\\n2007\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500061p.pdf\"\n }, \"DoDI 5000.61, \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Modeling and Simulation (\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \") Verification,\\nValidation, and Accreditation (\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \"), December 9,\\n2009\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500070_2012_ch1.pdf\"\n }, \"DoDI 5000.70, Management of \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Modeling and Simulation Activities,\\nMay 10 2012. Incorporating Change 1, Effective March 19,\\n2014\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://www.msco.mil/MSReferences/MSResourceDiscovery.aspx\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" Community of Interest Discovery Metadata Specification\\n(MSC-\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Defensive Management System OR Diminishing Manufacturing Sources\"\n }, \"DMS\"), \")\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Documents from Recommended Practices Guide\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/UserLegacy/user-leg-pr.pdf\"\n }, \"User's Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of Legacy\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/VVAgentLegacy/vv-leg-pr.pdf\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" Agent\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of Legacy\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/AccAgentLegacy/aa-leg-pr.pdf\"\n }, \"Accreditation Agent\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of Legacy\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/UserNew/user-new-pr.pdf\"\n }, \"User\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/DeveloperNew/dev-new-pr.pdf\"\n }, \"Developer\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/ManagerNew/pm-new-pr.pdf\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \"\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/VVAgentNew/vv-new-pr.pdf\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" Agent\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/AccAgentNew/aa-new-pr.pdf\"\n }, \"Accreditation Agent\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Conceptual/conceptual-pr.pdf\"\n }, \"Conceptual Model Development and\\nValidation\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/DataVV-New/DataVV-new-pr.pdf\"\n }, \"Data \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" for New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/DataVV-Leg/DataVV-Leg.pdf\"\n }, \"Data \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" for Legacy\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Fidelity/fidelity-pr.pdf\"\n }, \"Fidelity\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/HBR-Validation/hbr-validation-pr.pdf\"\n }, \"Human Behavior Representation\\nValidation\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Paradigm/dev-paradigm-pr.pdf\"\n }, \"Paradigms for \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nDevelopment\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Requirements/Requirements-pr.pdf\"\n }, \"Requirements\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Risk/Risk-pr.pdf\"\n }, \"Risk and Its Impact on\\n\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \"\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/SME/sme-pr.pdf\"\n }, \"Subject Matter Experts and\\n\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \"\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Validation/Validation-pr.pdf\"\n }, \"Validation\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/environment/environment-pr.pdf\"\n }, \"Foundations for \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" of the Natural Environment in a\\nSimulation\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/measures/measures-pr.pdf\"\n }, \"Measures\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Ref_Docs/HBR/beh-ref-pr.pdf\"\n }, \"Human Behavior Representation (HBR) Literature\\nReview\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Ref_Docs/Datadefs/Datadefs-pr.pdf\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" Data Concepts and\\nTerms\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Ref_Docs/Val_Lawref/Val-LawRef-pr.pdf\"\n }, \"A Practitioner\\\\'s Perspective on Simulation\\nValidation\")))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/2-9-References-and-Resources.md"},"frontmatter":{"metaTitle":"References and Resources","metaDescription":"References and 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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"908c250b-faf5-5552-9ffe-e6ad786cc8bc"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/3-1-Governance/page-data.json b/sites/oteguide/page-data/accreditation_guide/3-1-Governance/page-data.json new file mode 100644 index 00000000..59b974b3 --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/3-1-Governance/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/3-1-Governance","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"08395801-beb4-5a95-b2ad-607dbe955458","title":"Governance","slug":"/accreditation_guide/3-1-Governance"},"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\": \"Governance\",\n \"metaTitle\": \"Governance\",\n \"metaDescription\": \"Governance\"\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, \"DoDI\\xA05000.02, 7 Jan 15: \\\"Every distinct use of a model or simulation in\\nsupport of an operational evaluation will be accredited by an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \", and,\\nfor programs under \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Oversight, its use for the operational\\nevaluation will be approved by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \".\\\"\"), mdx(\"p\", null, \"DoDI 5000.61, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Modeling and Simulation (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \") Verification,\\nValidation, and Accreditation (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \")\"), \" , 9 Dec 09, para 4.a-b: \\\"Models,\\nsimulations, and associated data used to support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" processes,\\nproducts, and decisions shall undergo verification and validation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \")\\nthroughout their lifecycles. Models, simulations, and associated data\\nused to support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" processes, products, and decisions shall be\\naccredited for an intended use.\\\"\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 16-1001, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Verification, Validation and Accreditation (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \")\"), \" , 29\\nApr 2020, para 2.3: \\\\\\\"Air Force \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" applications will be accredited for\\ntheir intended purpose when supporting major \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" decision-making\\norganizations or processes, joint training, and joint exercises. All\\nexecuted \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" activities will support the model acceptance and\\naccreditation requirements defined by the accreditation authority.\\\\\\\"\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/3-1-Governance.md"},"frontmatter":{"metaTitle":"Governance","metaDescription":"Governance"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"08395801-beb4-5a95-b2ad-607dbe955458"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/3-2-Points-of-Contact/page-data.json b/sites/oteguide/page-data/accreditation_guide/3-2-Points-of-Contact/page-data.json new file mode 100644 index 00000000..f0eeedc0 --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/3-2-Points-of-Contact/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide/3-2-Points-of-Contact","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"338cce59-6f03-59d5-b589-04e40280c7a7","title":"Points of Contact ","slug":"/accreditation_guide/3-2-Points-of-Contact"},"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\": \"Points of Contact \",\n \"metaTitle\": \"Points of Contact \",\n \"metaDescription\": \"Points of Contact \"\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(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"The \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" staff lead for Accreditation is A-2/9. Refer questions\\nabout Verification, Validation, and Accreditation to\\n\", mdx(\"a\", {\n parentName: \"li\",\n \"href\": \"mailto:UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"\n }, \"UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"), \" .\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide/3-2-Points-of-Contact.md"},"frontmatter":{"metaTitle":"Points of Contact ","metaDescription":"Points of Contact "}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"338cce59-6f03-59d5-b589-04e40280c7a7"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/accreditation_guide/page-data.json b/sites/oteguide/page-data/accreditation_guide/page-data.json new file mode 100644 index 00000000..e429d0e2 --- /dev/null +++ b/sites/oteguide/page-data/accreditation_guide/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/accreditation_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"5f93ff4a-ec68-5044-9524-ae6478d135a3","title":"Accreditation Guide","slug":"/accreditation_guide"},"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\": \"Accreditation Guide\",\n \"metaTitle\": \"Accreditation Guide\",\n \"metaDescription\": \"Accreditation Guide\"\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, \"08 December 2020\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"accreditation_guide.md"},"frontmatter":{"metaTitle":"Accreditation Guide","metaDescription":"Accreditation Guide"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"5f93ff4a-ec68-5044-9524-ae6478d135a3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/acronyms/page-data.json b/sites/oteguide/page-data/acronyms/page-data.json index 5e0931af..6222f963 100644 --- a/sites/oteguide/page-data/acronyms/page-data.json +++ b/sites/oteguide/page-data/acronyms/page-data.json @@ -1 +1 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/acronyms","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"3c246e82-b17b-5afa-aacd-40f5e182c186","title":"Acronyms","slug":"/acronyms"},"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\": \"Acronyms\",\n \"metaTitle\": \"Acronyms\",\n \"metaDescription\": \"Acronyms\"\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, \"If you're just searching for the meaning of an ancroym, here's the place.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"2-Letter\"\n }, \"2Ltr\"), \": 2-Letter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block\"\n }, \"Blk\"), \": Block\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \": Detachment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standardization and Evaluation\"\n }, \"Stan/Eval\"), \": Standardization and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Three Dimensional Expeditionary Long Range Radar\"\n }, \"3DELRR\"), \": Three Dimensional Expeditionary Long Range Radar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Third Party Source\"\n }, \"3PS\"), \": Third Party Source\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advisory and Assistance Services\"\n }, \"AAS\"), \": Advisory and Assistance Services\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force and Army Anti-Jam Modem\"\n }, \"A3M\"), \": Air Force and Army Anti-Jam Modem\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \": Adversarial Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Aircraft Availability Improvement Program\"\n }, \"AAIP\"), \": Aircraft Availability Improvement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"After-Action Review / Report\"\n }, \"AAR\"), \": After-Action Review / Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Anti-Radiation Guided Missile\"\n }, \"AARGM\"), \": Advanced Anti-Radiation Guided Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air-to-air Range Infrastructure\"\n }, \"AARI\"), \": Air-to-air Range Infrastructure\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Airborne Strategic Deterrence\"\n }, \"ABSD\"), \": Airborne Strategic Deterrence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Alternating Current\"\n }, \"AC\"), \": Alternating Current\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Category\"\n }, \"ACAT\"), \": Acquisition Category\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Combat Command\"\n }, \"ACC\"), \": Air Combat Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Alternative Compensatory Control Measure\"\n }, \"ACCM\"), \": Alternative Compensatory Control Measure\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Center of Excellence\"\n }, \"ACE\"), \": Acquisition Center of Excellence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automated Civil Engineer System\"\n }, \"ACES\"), \": Automated Civil Engineer System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force C4I Program Assessment Tool\"\n }, \"ACPAT\"), \": Air Force \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Communications, Computers, and Intelligence\"\n }, \"C4I\"), \" Program Assessment Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automated Computer Program Identification Number System\"\n }, \"ACPINS\"), \": Automated Computer Program Identification Number System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Chief Process Office\"\n }, \"ACPO\"), \": Acquisition Chief Process Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Concept Technology Demonstration\"\n }, \"ACTD\"), \": Advanced Concept Technology Demonstration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Actual Cost Work Performed\"\n }, \"ACWP\"), \": Actual Cost Work Performed\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Decision Memorandum\"\n }, \"ADM\"), \": Acquisition Decision Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Distributed Simulation\"\n }, \"ADS\"), \": Advanced Distributed Simulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Army Evaluation Center\"\n }, \"AEC\"), \": United States Army Evaluation Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advance Engineering Change Order\"\n }, \"AECO\"), \": Advance Engineering Change Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Entry Control System OR AFOTEC Electronic Coordination System\"\n }, \"AECS\"), \": Advanced Entry Control System OR \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Electronic Coordination System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air and Space Expeditionary Force\"\n }, \"AEF\"), \": Air and Space Expeditionary Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Extremely High Frequency\"\n }, \"AEHF\"), \": Advanced Extremely High Frequency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Accrued Expenditures Paid\"\n }, \"AEP\"), \": Accrued Expenditures Paid\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advance Engineering Supplemental Order\"\n }, \"AESO\"), \": Advance Engineering Supplemental Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Education and Training Command\"\n }, \"AETC\"), \": Air Education and Training Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Evaluation Task Force\"\n }, \"AETF\"), \": Army Evaluation Task Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Accrued Expenditures Unpaid\"\n }, \"AEU\"), \": Accrued Expenditures Unpaid\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Global Cyberspace Integration Center\"\n }, \"AF GCIC\"), \": Air Force Global Cyberspace Integration Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Management and Oversight of Acquisition Services Process\"\n }, \"AFMOASP\"), \": Air Force Management and Oversight of Acquisition Services Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \": (US) Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A10: Assistant Chief of Staff for Strategic Deterrence and Nuclear Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A2: Deputy Chief of Staff\\nIntelligence\\nSurveillance and Reconnaissance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A3/5: Deputy Chief of Staff\\nOperations\\nPlans\\nand Requirements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A4/7: Deputy Chief of Staff\\nLogistics\\nInstallations\\nand Mission Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A5/8: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"\\nStrategic Plans and Programs\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A5R: Air Force Requirements Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A6: Chief of Warfighting Integration and Chief Information Officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Information Officer\"\n }, \"CIO\"), \")\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A8: Headquarters\\nAir Force Strategic Plans and Programs\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \": Chief of Staff\\nUnited States Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Commander OR Capability Viewpoint\"\n }, \"CV\"), \": Vice Chief of Staff\\nUnited States Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \": Air Force Chief of Safety\"), mdx(\"p\", null, \"\", 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\"), \": Headquarters Air Force Test and Evaluation Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Acquisition Executive\"\n }, \"AFAE\"), \": Air Force Acquisition Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Agency for Modeling and Simulation\"\n }, \"AFAMS\"), \": Air Force Agency for Modeling and Simulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Base\"\n }, \"AFB\"), \": Air Force Base\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Command & Control Integration Center\"\n }, \"AFC2IC\"), \": Air Force Command & Control Integration Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Command and Control and Intelligence, Surveillance, and Reconnaissance Center (disestablished)\"\n }, \"AFC2ISRC\"), \": Air Force Command and Control and Intelligence\\nSurveillance\\nand Reconnaissance Center (disestablished)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Communications Agency\"\n }, \"AFCA\"), \": Air Force Communications Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Cost Analysis Agency\"\n }, \"AFCAA\"), \": Air Force Cost Analysis Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Certification and Accreditation Program\"\n }, \"AFCAP\"), \": Air Force Certification and Accreditation Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Capabilities Document\"\n }, \"AFCD\"), \": Air Force Capabilities Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Civil Engineer Center\"\n }, \"AFCEC\"), \": Air Force Civil Engineer Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Civil Engineer Support Agency\"\n }, \"AFCESA\"), \": Air Force Civil Engineer Support Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Doctrine Document\"\n }, \"AFDD\"), \": Air Force Doctrine Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Departmental Publishing Office\"\n }, \"AFDPO\"), \": Air Force Departmental Publishing Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Economic Analysis OR Electronic Attack OR Evolutionary Acquisition OR Executing Authority\"\n }, \"EA\"), \": Air Force Enterprise Architecture\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Element of Expense\"\n }, \"AFEE\"), \": Air Force Element of Expense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Electronic Warfare Simulator\"\n }, \"AFEWES\"), \": Air Force Electronic Warfare Simulator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Federal Acquisition Regulation Supplement\"\n }, \"AFFARS\"), \": Air Force Federal Acquisition Regulation Supplement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Frequency Management Agency\"\n }, \"AFFMA\"), \": Air Force Frequency Management Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Gatekeeper\"\n }, \"AFGK\"), \": Air Force Gatekeeper\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Global Logistics Support Center\"\n }, \"AFGLSC\"), \": Air Force Global Logistics Support Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Global Strike Command\"\n }, \"AFGSC\"), \": Air Force Global Strike Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \": Air Force Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Integrated Collaborative Environment\"\n }, \"AFICE\"), \": Air Force Integrated Collaborative Environment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Information Operations Center\"\n }, \"AFIOC\"), \": Air Force Information Operations Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Integrated Personnel and Pay System\"\n }, \"AFIPPS\"), \": Air Force Integrated Personnel and Pay System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Institute of Technology\"\n }, \"AFIT\"), \": Air Force Institute of Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Information Warfare Center (disestablished)\"\n }, \"AFIWC\"), \": Air Force Information Warfare Center (disestablished)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Joint Test Program Office\"\n }, \"AFJO\"), \": Air Force Joint Test Program Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Knowledge Now\"\n }, \"AFKN\"), \": Air Force Knowledge Now\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Lessons Learned Program\"\n }, \"AFL2P\"), \": Air Force Lessons Learned Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Life Cycle Management Center\"\n }, \"AFLCMC\"), \": Air Force Life Cycle Management Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Lesson Issue Resolution Program\"\n }, \"AFLIRP\"), \": Air Force Lesson Issue Resolution Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \": Air Force Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Material Command\"\n }, \"AFMC\"), \": Air Force Material Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Mission Directive\"\n }, \"AFMD\"), \": Air Force Mission Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Metrology and Calibration\"\n }, \"AFMETCAL\"), \": Air Force Metrology and Calibration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Modeling and Simulation Resource Repository\"\n }, \"AFMSRR\"), \": Air Force Modeling and Simulation Resource Repository\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Network\"\n }, \"AFNET\"), \": Air Force Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Network Integration Center\"\n }, \"AFNIC\"), \": Air Force Network Integration Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Nuclear Security Administration\"\n }, \"NNSA\"), \": Air Force-National Nuclear Security Administration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Nuclear Weapons Center\"\n }, \"AFNWC\"), \": Air Force Nuclear Weapons Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Occupational and Environmental Safety, Fire Protection, and Health OR Air Force Office of Safety and Health\"\n }, \"AFOSH\"), \": Air Force Occupational and Environmental Safety\\nFire Protection\\nand Health OR Air Force Office of Safety and Health\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Office of Special Investigations\"\n }, \"AFOSI\"), \": Air Force Office of Special Investigations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \": Air Force Operational Test and Evaluation Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-1: Manpower and Personnel Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-1T: Training Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-1W: Manpower and Personnel (Operations) Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-2/9: Intelligence\\nAnalyses\\nand Assessments Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-2N: Intelligence Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3: Operations Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3C: Cyber Strategic Evaluation Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3E: Operations Mission Support Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3F: Test Operations Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3I: Cyberspace Test Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3O: Test Design Operations Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3Z: Special Access Programs Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-4/7: Installations and Mission Support Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-4F: Logistics and Facilities Management Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-5/8: Plans and Programs Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-5R: Test Infrastructure Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-6: Communications and Information Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-6O: Cyber Operations Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-6X: Plans and Resources Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-6Z: Special Access Programs Information Technology Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-7K: Contracting Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-7R: Financial Resources Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-8P: Programming Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-8R: Long Range Investments Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-8X: Strategic Plans and Policy Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-9A: Analysis and Assessments Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-9I: Analysis Foundation and Integration Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-9X: Methods and Tools Division\"), 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\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \": Technical Advisor\"), 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\": \"Commander OR Critical Component\"\n }, \"CC\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/CCE: Executive Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/CCJ: Graphics\"), 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\": \"Command Control Points\"\n }, \"CCP\"), \": Protocol\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/CCS: Secretary\"), 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\": \"Commander’s Action Group Office Symbol\"\n }, \"CCX\"), \": Commander\\u2019s Action Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/CEM: Chief Enlisted Manager\"), 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\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \": Command Staff\"), 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\": \"Vice Commander OR Capability Viewpoint\"\n }, \"CV\"), \": Vice Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/DS: Director of Staff\"), 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\": \"Executive Director\"\n }, \"ED\"), \": Executive Director\"), 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\": \"HQ AFOTEC History Office\"\n }, \"HO\"), \": History Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/IGI: Inspector General (Inspections)\"), 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\": \"Information Protection OR Initial Point OR Intellectual Property OR Internet Protocol\"\n }, \"IP\"), \": Information Protection\"), 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\": \"HQ AFOTEC Legal Counsel\"\n }, \"LC\"), \": Legal Council\"), 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\": \"Partnering Arrangement OR Preparing Activity OR Preparing Authority OR Program Authorization ORPublic Affairs\"\n }, \"PA\"), \": Public Affairs\"), 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\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \": Safety\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Instruction\"\n }, \"AFOTECI\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Pamphlet\"\n }, \"AFOTECPAM\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Pamphlet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Tactics, Techniques, and Procedures\"\n }, \"AFOTTP\"), \": Air Force Operational Tactics\\nTechniques\\nand Procedures\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Pamphlet\"\n }, \"AFPAM\"), \": Air Force Pamphlet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Policy Directive\"\n }, \"AFPD\"), \": Air Force Policy Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Program Executive Officer/Combat and Mission Support\"\n }, \"AFPEO/CM\"), \": Air Force Program Executive Officer/Combat and Mission Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Review Board\"\n }, \"AFRB\"), \": Air Force Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Reserve Command\"\n }, \"AFRC\"), \": Air Force Reserve Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Information Management System Records Disposition Schedule\"\n }, \"AFRIMS RDS\"), \": Air Force Information Management System Records Disposition Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Records Information Management System\"\n }, \"AFRIMS\"), \": Air Force Records Information Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Research Laboratory\"\n }, \"AFRL\"), \": Air Force Research Laboratory\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Requirements Oversight Council\"\n }, \"AFROC\"), \": Air Force Requirements Oversight Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Requirements for Operational Capabilities Council\"\n }, \"AFROCC\"), \": Air Force Requirements for Operational Capabilities Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Requirements Oversight Council Memorandum\"\n }, \"AFROCM\"), \": Air Force Requirements Oversight Council Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Requirements Review Group\"\n }, \"AFRRG\"), \": Air Force Requirements Review Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Specialty Code\"\n }, \"AFSC\"), \": Air Force Specialty Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force SEEK EAGLE Office\"\n }, \"AFSEO\"), \": Air Force SEEK EAGLE Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Security Forces Center\"\n }, \"AFSFC\"), \": Air Force Security Forces Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force System Interoperability Testing\"\n }, \"AFSIT\"), \": Air Force System Interoperability Testing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Special Operations Command\"\n }, \"AFSOC\"), \": Air Force Special Operations Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Space Command\"\n }, \"AFSPC\"), \": Air Force Space Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Systems Security Instruction\"\n }, \"AFSSI\"), \": Air Force Systems Security Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Test Center\"\n }, \"AFTC\"), \": Air Force Test Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Above Ground Level\"\n }, \"AGL\"), \": Above Ground Level\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Ground Missile\"\n }, \"AGM\"), \": Air Ground Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Active Guard and Reserve\"\n }, \"AGR\"), \": Active Guard and Reserve\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \": Air Intercept Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \"-120 Adv \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AIM-120C Advanced Electronic Protection Improvement Program\"\n }, \"EPIP\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \"-120C Advanced Electronic Protection Improvement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \" 120D \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Identification Profile OR System Information Profile\"\n }, \"SIP\"), \"-3: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \"-120D System Improvement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Aircraft Information Program\"\n }, \"AIP\"), \": Aircraft Information Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Information Repository\"\n }, \"AIR\"), \": Acquisition Information Repository\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automated Information Systems\"\n }, \"AIS\"), \": Automated Information Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Airborne Intelligence, Surveillance, and Reconnaissance\"\n }, \"AISR\"), \": Airborne Intelligence\\nSurveillance\\nand Reconnaissance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automatic Identification Technology\"\n }, \"AIT\"), \": Automatic Identification Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Logistics Center\"\n }, \"ALC\"), \": Air Logistics Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Launched Cruise Missile\"\n }, \"ALCM\"), \": Air Launched Cruise Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Airborne Launch Control System Replacement\"\n }, \"ALCS-R\"), \": Airborne Launch Control System Replacement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Administrative and Logistics Delay\"\n }, \"ALDT\"), \": Administrative and Logistics Delay\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Autonomic Logistics Information System (F-35)\"\n }, \"ALIS\"), \": Autonomic Logistics Information System (F-35)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Aerospace Maintenance and Regeneration Group\"\n }, \"AMARG\"), \": Aerospace Maintenance and Regeneration Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Mission Applications Suite\"\n }, \"AMAS\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Mission Applications Suite\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Mobility Command\"\n }, \"AMC\"), \": Air Mobility Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Alternate Mission Equipment\"\n }, \"AME\"), \": Alternate Mission Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Master List\"\n }, \"AML\"), \": Acquisition Master List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"C-130 Avionics Modernization Program\"\n }, \"AMP\"), \": C-130 Avionics Modernization Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Materiel Systems Analysis Activity\"\n }, \"AMSAA\"), \": Army Materiel Systems Analysis Activity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Navy/Portable Radio Communication\"\n }, \"AN/PRC\"), \": Army Navy/Portable Radio Communication\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air National Guard\"\n }, \"ANG\"), \": Air National Guard\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \": Area of Operations or Authorizing Official or Action Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Availability\"\n }, \"Ao\"), \": Operational Availability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \": Analysis of Alternatives\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Operations Center Weapon System\"\n }, \"AOC WS\"), \": Air Operations Center Weapon System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Assessment of Operational Test Readiness\"\n }, \"AOTR\"), \": Assessment of Operational Test Readiness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Additional Performance Attribute\"\n }, \"APA\"), \": Additional Performance Attribute\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Process Architecture Team\"\n }, \"APAT\"), \": Acquisition Process Architecture Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Program Baseline\"\n }, \"APB\"), \": Acquisition Program Baseline\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Professional Development Program\"\n }, \"APDP\"), \": Acquisition Professional Development Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Precision Kill Weapon System\"\n }, \"APKWS\"), \": Advanced Precision Kill Weapon System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Process Model\"\n }, \"APM\"), \": Acquisition Process Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Program Master List\"\n }, \"APML\"), \": Acquisition Program Master List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Annual Planning and Programming Guidance\"\n }, \"APPG\"), \": Annual Planning and Programming Guidance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Accountable Property Systems of Record\"\n }, \"APSR\"), \": Accountable Property Systems of Record\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Pilot Training\"\n }, \"APT\"), \": Advanced Pilot Training\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Average Unit Procurement Cost\"\n }, \"APUC\"), \": Average Unit Procurement Cost\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis and Reporting Toolset OR Army Regulation\"\n }, \"AR\"), \": Analysis and Reporting Toolset OR Army Regulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Radiation Missile\"\n }, \"ARM\"), \": Anti-Radiation Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air-Launched Rapid Response Weapon\"\n }, \"ARRW\"), \": Air-Launched Rapid Response Weapon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \": Adaptive-Relevant Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Radar Threat System\"\n }, \"ARTS\"), \": Advanced Radar Threat System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition and Sustainment Tool Kit\"\n }, \"AS Tool Kit\"), \": Acquisition and Sustainment Tool Kit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Strategy\"\n }, \"AS\"), \": Acquisition Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Situational Awareness Countermeasures System\"\n }, \"ASACMS\"), \": Advanced Situational Awareness Countermeasures System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Application Software Assurance Center of Excellence\"\n }, \"ASACoE\"), \": Application Software Assurance Center of Excellence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Assistant Secretary of the Air Force\"\n }, \"ASAF\"), \": Assistant Secretary of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Strategy Development OR Agile Software Development OR Assist Sec of Defense\"\n }, \"ASD\"), \": Acquisition Strategy Development OR Agile Software Development OR Assist Sec of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Assistant Secretary of Defense (Network and Information Integration\"\n }, \"ASDNII\"), \": Assistant Secretary of Defense (Network and Information Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Airborne Signals Intelligence Payload OR Aircraft Structural Integrity Program\"\n }, \"ASIP\"), \": Airborne Signals Intelligence Payload OR Aircraft Structural Integrity Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Strategy Panel\"\n }, \"ASP\"), \": Acquisition Strategy Panel\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition and Sustainment Reviews OR Alternative Systems Review\"\n }, \"ASR\"), \": Acquisition and Sustainment Reviews OR Alternative Systems Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Sustainment Tool Kit\"\n }, \"ASTK\"), \": Acquisition Sustainment Tool Kit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Surface Warfare\"\n }, \"ASuW\"), \": Anti-Surface Warfare\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \": Anti-Tamper\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L: Acquisition\\nTechnology\\nand Logistics\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automated Time Attendance and Production System\"\n }, \"ATAPPS\"), \": Automated Time Attendance and Production System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Traffic Control and Landing Systems\"\n }, \"ATCALS\"), \": Air Traffic Control and Landing Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Technology Demonstration (or Development)\"\n }, \"ATD\"), \": Advanced Technology Demonstration (or Development)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automatic Test Equipment\"\n }, \"ATE\"), \": Automatic Test Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Test and Evaluation Command\"\n }, \"ATEC\"), \": Army Test and Evaluation Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Tasking Order OR Authority to Operate\"\n }, \"ATO\"), \": Air Tasking Order OR Authority to Operate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automated Technical Orders System\"\n }, \"ATOS\"), \": Automated Technical Orders System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Test Program Application\"\n }, \"ATPA\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Program Application\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Targeting Pod-Sensor Enhancement\"\n }, \"ATP-SE\"), \": Advanced Targeting Pod-Sensor Enhancement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automatic Test System\"\n }, \"ATS\"), \": Automatic Test System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analyst Training and Technical Information Center\"\n }, \"ATTIC\"), \": Analyst Training and Technical Information Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Universal Task List\"\n }, \"AUTL\"), \": Army Universal Task List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"All Viewpoint\"\n }, \"AV\"), \": All Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Aviation Integrity Program\"\n }, \"AVIP\"), \": Aviation Integrity Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Aviation Petroleum, Oil, and Lubricants\"\n }, \"AVPOL\"), \": Aviation Petroleum\\nOil\\nand Lubricants\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Airborne Warning and Control System\"\n }, \"AWACS\"), \": Airborne Warning and Control System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Warfare Battle Shaping\"\n }, \"AWBS\"), \": Air Warfare Battle Shaping\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Weapons Integration Program\"\n }, \"AWIP\"), \": Advanced Weapons Integration Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defensive Management System\"\n }, \"B-2 DMS\"), \": Defensive Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Extremely High Frequency Satellite Communications\"\n }, \"B-2 EHF SATCOM\"), \": Extremely High Frequency Satellite Communications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"B-52 Commercial Engine Replacement Program\"\n }, \"B-52 CERP\"), \": B-52 Commercial Engine Replacement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"B-52 Radar Modernization Program\"\n }, \"B-52 RMP\"), \": B-52 Radar Modernization Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"B61 Life Extension Program\"\n }, \"B61 LEP\"), \": B61 Life Extension Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Buy American Act\"\n }, \"BAA\"), \": Buy American Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Bullet Background Paper\"\n }, \"BBP\"), \": Bullet Background Paper\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Business Case\"\n }, \"BC\"), \": Business Case\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Business Case Analysis\"\n }, \"BCA\"), \": Business Case Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Business Capability Lifecycle\"\n }, \"BCL\"), \": Business Capability Lifecycle\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Baseline Comparison System\"\n }, \"BCS\"), \": Baseline Comparison System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Baseline Comparison System\"\n }, \"BCS\"), \"-F: Battle Control System-Fixed\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Big Data Analytics; Bomb Damage Assessment\"\n }, \"BDA\"), \": Big Data Analytics; Bomb Damage Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Battle Damage Repair Spares Kit\"\n }, \"BDRSK\"), \": Battle Damage Repair Spares Kit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Business Enterprise Architecture\"\n }, \"BEA\"), \": Business Enterprise Architecture\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Budget Estimate Submission\"\n }, \"BES\"), \": Budget Estimate Submission\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Blue Force Tracking\"\n }, \"BFT\"), \": Blue Force Tracking\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Base and Installation Security System\"\n }, \"BISS\"), \": Base and Installation Security System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Beyond-Line-of-Sight Command and Control\"\n }, \"BLOS C2\"), \": Beyond-Line-of-Sight Command and Control\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Beyond Line of Sight\"\n }, \"BLOS\"), \": Beyond Line of Sight\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Bomb, Live Unit\"\n }, \"BLU\"), \": Bomb\\nLive Unit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Battle Management Command and Control Communications\"\n }, \"BMC2\"), \": Battle Management Command and Control Communications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ballistic Missile Defense\"\n }, \"BMD\"), \": Ballistic Missile Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ballistic Missile Defense System\"\n }, \"BMDS\"), \": Ballistic Missile Defense System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Base Operating Support\"\n }, \"BOS\"), \": Base Operating Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Budget Program Activity Code\"\n }, \"BPAC\"), \": Budget Program Activity Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Bomb Release Units\"\n }, \"BRU\"), \": Bomb Release Units\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \": Block Update\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Certification and Accreditation\"\n }, \"C&A\"), \": Certification and Accreditation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities and Limitations\"\n }, \"C&L\"), \": Capabilities and Limitations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities and Limitations Report\"\n }, \"C&LR\"), \": Capabilities and Limitations Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command and Control\"\n }, \"C2\"), \": Command and Control\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command and Control Air Operations Suite\"\n }, \"C2AOS\"), \": Command and Control Air Operations Suite\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Battle Management, and Communications\"\n }, \"C2BMC\"), \": Command\\nControl\\nBattle Management\\nand Communications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Continuous Capability Development and Delivery\"\n }, \"C2D2\"), \": Continuous Capability Development and Delivery\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command and Control Information Services\"\n }, \"C2IS\"), \": Command and Control Information Services\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Communications, and Computers\"\n }, \"C4\"), \": Command\\nControl\\nCommunications\\nand Computers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Communications, Computers, and Intelligence\"\n }, \"C4I\"), \": Command\\nControl\\nCommunications\\nComputers\\nand Intelligence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Communication, Computers, and Intelligence Support Plan\"\n }, \"C4ISP\"), \": Command\\nControl\\nCommunication\\nComputers\\nand Intelligence Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cmd, Control, Comm, Computers, Intel, Surveillance, and Reconnaissance\"\n }, \"C4ISR\"), \": Cmd\\nControl\\nComm\\nComputers\\nIntel\\nSurveillance\\nand Reconnaissance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \": Command Technical Advisor OR Contract Award OR Criticality Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Access Card \"\n }, \"CAC\"), \": Common Access Card \"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Computer-Aided Design (or Drafting)\"\n }, \"CAD\"), \": Computer-Aided Design (or Drafting)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Acquisition Executive\"\n }, \"CAE\"), \": Component Acquisition Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Comprehensive Air Force Technical Order Plan\"\n }, \"CAFTOP\"), \": Comprehensive Air Force Technical Order Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group\"\n }, \"CAG\"), \": Commander\\u2019s Action Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commercial and Government Entity\"\n }, \"CAGE\"), \": Commercial and Government Entity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cost Analysis Improvement Group\"\n }, \"CAIG\"), \": Cost Analysis Improvement Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Analytical Laboratory System\"\n }, \"CALS\"), \": Common Analytical Laboratory System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Centralized Asset Management\"\n }, \"CAM\"), \": Centralized Asset Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Coalition Air Operations Center\"\n }, \"CAOC\"), \": Coalition Air Operations Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Acquired Property OR Critical Acquisition Position\"\n }, \"CAP\"), \": Contractor Acquired Property OR Critical Acquisition Position\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Controlled Access Program Coordinating Office\"\n }, \"CAPCO\"), \": Controlled Access Program Coordinating Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cost Assessment and Program Evaluation\"\n }, \"CAPE\"), \": Cost Assessment and Program Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"F-16 Combat Avionics Programmed Extension Suite\"\n }, \"CAPES\"), \": F-16 Combat Avionics Programmed Extension Suite\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cost Analysis Requirements Description\"\n }, \"CARD\"), \": Cost Analysis Requirements Description\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Close Air Support System\"\n }, \"CASS\"), \": Close Air Support System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Category\"\n }, \"CAT\"), \": Category\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities-Based Assessment\"\n }, \"CBA\"), \": Capabilities-Based Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chemical and Biological Defense Program\"\n }, \"CBDP\"), \": Chemical and Biological Defense Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Condition-Based Maintenance Plus\"\n }, \"CBM\"), \": Condition-Based Maintenance Plus\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability-Based Planning\"\n }, \"CBP\"), \": Capability-Based Planning\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chemical, Biological, and Radiological\"\n }, \"CBR\"), \": Chemical\\nBiological\\nand Radiological\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities-Based Requirements Document\"\n }, \"CBRD\"), \": Capabilities-Based Requirements Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chemical, Biological, Radiological and Nuclear\"\n }, \"CBRN\"), \": Chemical\\nBiological\\nRadiological and Nuclear\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \": Commander OR Critical Component\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Clinger-Cohen Act OR Component Cost Analysis\"\n }, \"CCA\"), \": Clinger-Cohen Act OR Component Cost Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Comprehensive Cost and Requirement System\"\n }, \"CCaR\"), \": Comprehensive Cost and Requirement System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Core Compliance Area\"\n }, \"CCCA\"), \": Common Core Compliance Area\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Capability Document\"\n }, \"CCD\"), \": Combat Capability Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combatant Commander\"\n }, \"CCDR\"), \": Combatant Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capstone Concept for Joint Operations\"\n }, \"CCJO\"), \": Capstone Concept for Joint Operations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combatant Command\"\n }, \"CCMD\"), \": Combatant Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Control Points\"\n }, \"CCP\"), \": Command Control Points\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Corrosion Control Program Executive\"\n }, \"CCPE\"), \": Corrosion Control Program Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Call Completion Rate\"\n }, \"CCR\"), \": Call Completion Rate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Counter-Concealment Sensing\"\n }, \"C-CS\"), \": Counter-Concealment Sensing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Collaboration Teams\"\n }, \"CCT\"), \": Capability Collaboration Teams\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept Characterization and Technical Description\"\n }, \"CCTD\"), \": Concept Characterization and Technical Description\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group Office Symbol\"\n }, \"CCX\"), \": Commander\\u2019s Action Group Office Symbol\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Director (or Directorate) OR Deputy Commander\"\n }, \"CD\"), \": Capability Director (or Directorate) OR Deputy Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Current Design Activity\"\n }, \"CDA\"), \": Current Design Activity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \": Capability Development Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Definition Package\"\n }, \"CDP\"), \": Capability Definition Package\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Design Review\"\n }, \"CDR\"), \": Critical Design Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contract Data Requirements List\"\n }, \"CDRL\"), \": Contract Data Requirements List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cross Domain Solution\"\n }, \"CDS\"), \": Cross Domain Solution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Developmental Tester\"\n }, \"CDT\"), \": Chief Developmental Tester\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Civil Engineer OR Conducted Emissions\"\n }, \"CE\"), \": Civil Engineer OR Conducted Emissions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \": Circular Error Probability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Certification\"\n }, \"CERT\"), \": Certification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Core Function Lead\"\n }, \"CFL\"), \": Core Function Lead\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Core Function Lead Integrator\"\n }, \"CFLI\"), \": Core Function Lead Integrator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Core Function Master Plan\"\n }, \"CFMP\"), \": Core Function Master Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Financial Officer\"\n }, \"CFO\"), \": Chief Financial Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities Focused Planning\"\n }, \"CFP\"), \": Capabilities Focused Planning\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Code of Federal Regulations\"\n }, \"CFR\"), \": Code of Federal Regulations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contract Funds Status Report\"\n }, \"CFSR\"), \": Contract Funds Status Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Gap Assessment\"\n }, \"CGA\"), \": Capability Gap Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common GPS Module\"\n }, \"CGM\"), \": Common \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" Module\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Configuration Item OR Counterintelligence\"\n }, \"CI\"), \": Configuration Item OR Counterintelligence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Competition in Contracting Act\"\n }, \"CICA\"), \": Competition in Contracting Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contamination Indicator Decontamination Assurance System\"\n }, \"CIDAS\"), \": Contamination Indicator Decontamination Assurance System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Counter-Improvised Explosive Device\"\n }, \"CIED\"), \": Counter-Improvised Explosive Device\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Inspection Management Board\"\n }, \"CIMB\"), \": Commander\\u2019s Inspection Management Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Information Officer\"\n }, \"CIO\"), \": Chief Information Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Intelligence Parameter\"\n }, \"CIP\"), \": Critical Intelligence Parameter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cyberspace Infrastructure Planning System\"\n }, \"CIPS\"), \": Cyberspace Infrastructure Planning System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capital Investment Report\"\n }, \"CIR\"), \": Capital Investment Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Counterintelligence Support Plan\"\n }, \"CISP\"), \": Counterintelligence Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Center of Industrial and Technical Excellence\"\n }, \"CITE\"), \": Center of Industrial and Technical Excellence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman, Joint Chiefs of Staff\"\n }, \"CJCS\"), \": Chairman\\nJoint Chiefs of Staff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman, Joint Chief of Staff Instruction\"\n }, \"CJCSI\"), \": Chairman\\nJoint Chief of Staff Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman, Joint Chiefs of Staff Manual\"\n }, \"CJCSM\"), \": Chairman\\nJoint Chiefs of Staff Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"COBRA JUDY Replacement\"\n }, \"CJR\"), \": COBRA JUDY Replacement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Coalition Joint Task Force\"\n }, \"CJTF\"), \": Coalition Joint Task Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"China Lake OR Civilian Leader OR Continuous Learning\"\n }, \"CL\"), \": China Lake OR Civilian Leader OR Continuous Learning\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contract Line Item Number\"\n }, \"CLIN\"), \": Contract Line Item Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Logistics Support\"\n }, \"CLS\"), \": Contractor Logistics Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Configuration Management OR Consequence Management OR Constellation Management OR Corrective Maintenance\"\n }, \"CM\"), \": Configuration Management OR Consequence Management OR Constellation Management OR Corrective Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Munitions BIT Reprogramming Equipment\"\n }, \"CMBRE\"), \": Common Munitions BIT Reprogramming Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"C-5 Core Mission Computer and Weather Radar Program\"\n }, \"CMC\"), \": C-5 Core Mission Computer and Weather Radar Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability-Mission Lattice\"\n }, \"CML\"), \": Capability-Mission Lattice\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Maturity Model Integration\"\n }, \"CMMI\"), \": Capability Maturity Model Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Configuration Management Plan\"\n }, \"CMP\"), \": Configuration Management Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Collaboration and Measurements Requirements Summary\"\n }, \"CMRS\"), \": Collaboration and Measurements Requirements Summary\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Computer Network Attack\"\n }, \"CNA\"), \": Computer Network Attack\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Change Notice Engineering Order\"\n }, \"CNEO\"), \": Change Notice Engineering Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Committee on National Security Systems (CNSS) Instruction\"\n }, \"CNSSI\"), \": Committee on National Security Systems (CNSS) Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Nuclear Weapons Design Information\"\n }, \"CNWDI\"), \": Critical Nuclear Weapons Design Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer\"\n }, \"CO\"), \": Contracting Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Course of Action\"\n }, \"COA\"), \": Course of Action\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Certificate of Compliance\"\n }, \"CoC\"), \": Certificate of Compliance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combatant Command\"\n }, \"COCOM\"), \": Combatant Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"COD\"), \": Capability Development Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \": Critical Operational Issue\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Community On-Line Intelligence System for End Users and Managers\"\n }, \"COLISEUM\"), \": Community On-Line Intelligence System for End Users and Managers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander Air Force Forces\"\n }, \"COMAFFOR\"), \": Commander Air Force Forces\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Naval Command Operational Test and Evaluation Force\"\n }, \"COMOPTEVFOR\"), \": Naval Command Operational Test and Evaluation Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Communications Security\"\n }, \"COMSEC\"), \": Communications Security\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Certificate of Networthiness\"\n }, \"CoN\"), \": Certificate of Networthiness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"B-52 Combat Network Communications Technology\"\n }, \"CONECT\"), \": B-52 Combat Network Communications Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Employment\"\n }, \"CONEMP\"), \": Concept of Employment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \": Concept of Operations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Continuity of Operations Plan\"\n }, \"COOP\"), \": Continuity of Operations Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Operating Picture\"\n }, \"COP\"), \": Common Operating Picture\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Community of Practice\"\n }, \"CoP\"), \": Community of Practice\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \": Contracting Officer\\u2019s Representative\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issues and Criteria\"\n }, \"CORE\"), \": Critical Operational Issues and Criteria\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander, Operational Test Force (OPTEVFOR)\"\n }, \"COTF\"), \": Commander\\nOperational Test Force (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test and Evaluation Force\"\n }, \"OPTEVFOR\"), \")\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commercial Off-the-Shelf\"\n }, \"COTS\"), \": Commercial Off-the-Shelf\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Operational Test Team\"\n }, \"COTT\"), \": Combined Operational Test Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman’s Program Assessment\"\n }, \"CPA\"), \": Chairman\\u2019s Program Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cost-Plus Award Fee\"\n }, \"CPAF\"), \": Cost-Plus Award Fee\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Performance Assessment Reporting System\"\n }, \"CPARS\"), \": Contractor Performance Assessment Reporting System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Corrosion Prevention and Control Plan\"\n }, \"CPCP\"), \": Corrosion Prevention and Control Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Production Document\"\n }, \"CPD\"), \": Capability Production Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Crash Position Indicator OR Critical Program Information\"\n }, \"CPI\"), \": Crash Position Indicator OR Critical Program Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cost Plus Incentive Fee\"\n }, \"CPIF\"), \": Cost Plus Incentive Fee\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Portfolio Manager\"\n }, \"CPM\"), \": Capability Portfolio Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman’s Program Recommendation\"\n }, \"CPR\"), \": Chairman\\u2019s Program Recommendation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Change Request\"\n }, \"CR\"), \": Change Request\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hexavalent Chromium\"\n }, \"CR6\"), \": Hexavalent Chromium\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Continuing Resolution Authority OR Cost Risk Assessment OR Chairman’s Risk Assessment\"\n }, \"CRA\"), \": Continuing Resolution Authority OR Cost Risk Assessment OR Chairman\\u2019s Risk Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities Requirements Document \"\n }, \"CRD\"), \": Capabilities Requirements Document \"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Research and Development Agreement\"\n }, \"CRDA\"), \": Cooperative Research and Development Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Rescue Helicopter\"\n }, \"CRH\"), \": Combat Rescue Helicopter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Range Integrated Instrumentation System\"\n }, \"CRIIS\"), \": Common Range Integrated Instrumentation System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cross Industry Standard Process for Data Mining\"\n }, \"CRISP\"), \": Cross Industry Standard Process for Data Mining\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \": Component Resolution Matrix OR Crew Resource Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities Review and Risk Assessment\"\n }, \"CRRA\"), \": Capabilities Review and Risk Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman’s Readiness System\"\n }, \"CRS\"), \": Chairman\\u2019s Readiness System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \": Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \": Combat Support Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff of the Air Force\"\n }, \"CSAF\"), \": Chief of Staff of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Consolidated Sustainment Activity Group\"\n }, \"CSAG\"), \": Consolidated Sustainment Activity Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue\"\n }, \"CSAR\"), \": Combat Search and Rescue\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue Locator\"\n }, \"CSARL\"), \": Combat Search and Rescue Locator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Configuration Steering Board\"\n }, \"CSB\"), \": Configuration Steering Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Computer Software Configuration Items\"\n }, \"CSCI\"), \": Computer Software Configuration Items\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Center for Systems Engineering OR Common Support Equipment\"\n }, \"CSE\"), \": Center for Systems Engineering OR Common Support Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Support Helicopter\"\n }, \"CSH\"), \": Common Support Helicopter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Safety Item\"\n }, \"CSI\"), \": Critical Safety Item\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commodity Strategy Official\"\n }, \"CSO\"), \": Commodity Strategy Official\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical System Resources\"\n }, \"CSR\"), \": Critical System Resources\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contract Sustainment Support\"\n }, \"CSS\"), \": Contract Sustainment Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Counter-small Unmanned Aerial Systems\"\n }, \"C-sUAS\"), \": Counter-small Unmanned Aerial Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Supported Weapon System\"\n }, \"CSWS\"), \": Contractor Supported Weapon System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \": Contractor Testing OR Critical Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Threat Assessments OR Center Test Authority\"\n }, \"CTA\"), \": Capability Threat Assessments OR Center Test Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Technology Element\"\n }, \"CTE\"), \": Critical Technology Element\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Central Test & Evaluation Investment Program\"\n }, \"CTEIP\"), \": Central Test & Evaluation Investment Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \": Combined Task Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Technical Information Code\"\n }, \"CTIC\"), \": Contractor Technical Information Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Transition Memorandum\"\n }, \"CTM\"), \": Capability Transition Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Certificate to Operate\"\n }, \"CtO\"), \": Certificate to Operate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Centralized Technical Order Management\"\n }, \"CTOM\"), \": Centralized Technical Order Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Technical Parameter\"\n }, \"CTP\"), \": Critical Technical Parameter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Transition Review\"\n }, \"CTR\"), \": Capability Transition Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Controlled Unclassified Information\"\n }, \"CUI\"), \": Controlled Unclassified Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Controlled Unclassified Military Information\"\n }, \"CUMI\"), \": Controlled Unclassified Military Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Commander OR Capability Viewpoint\"\n }, \"CV\"), \": Vice Commander OR Capability Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Information Protection/SAP Security (office symbol)\"\n }, \"CVI\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Information Protection/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" Security (office symbol)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Vertical Lift Support Platform\"\n }, \"CVLSP\"), \": Common Vertical Lift Support Platform\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \": Cooperative Vulnerability and Penetration Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Carrier Air Wing\"\n }, \"CVW\"), \": Carrier Air Wing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Continuous Wave Illuminator\"\n }, \"CWI\"), \": Continuous Wave Illuminator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Calendar Year\"\n }, \"CY\"), \": Calendar Year\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Determination and Findings\"\n }, \"D&F\"), \": Determination and Findings\"), mdx(\"p\", null, \"D\\nARA: Director\\nAcquisition Resources\\nand Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director, Cost Assessment, and Program Evaluation\"\n }, \"D/CAPE\"), \": Director\\nCost Assessment\\nand Program Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Development/Qualification Test and Evaluation\"\n }, \"D/QT&E\"), \": Development/Qualification Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of the Army\"\n }, \"DA\"), \": Department of the Army\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Designated Approval Authority\"\n }, \"DAA\"), \": Designated Approval Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Board\"\n }, \"DAB\"), \": Defense Acquisition Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Designated Acquisition Commander\"\n }, \"DAC\"), \": Designated Acquisition Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director, Acquisition Career Management\"\n }, \"DACM\"), \": Director\\nAcquisition Career Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Executive\"\n }, \"DAE\"), \": Defense Acquisition Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Executive Summary\"\n }, \"DAES\"), \": Defense Acquisition Executive Summary\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of the Air Force\"\n }, \"DAF\"), \": Department of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Guidebook\"\n }, \"DAG\"), \": Defense Acquisition Guidebook\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Management Information Retrieval\"\n }, \"DAMIR\"), \": Defense Acquisition Management Information Retrieval\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Designated Acquisition Officials\"\n }, \"DAO\"), \": Designated Acquisition Officials\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deep Space Advanced Radar Concept\"\n }, \"DARC\"), \": Deep Space Advanced Radar Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Advanced Research Projects Agency\"\n }, \"DARPA\"), \": Defense Advanced Research Projects Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data, Acquisition, Recording, and Telemetry OR Deficiency Analysis Ranking Technique\"\n }, \"DART\"), \": Data\\nAcquisition\\nRecording\\nand Telemetry OR Deficiency Analysis Ranking Technique\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition System\"\n }, \"DAS\"), \": Defense Acquisition System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Assistant Secretary of Defense\"\n }, \"DASD\"), \": Deputy Assistant Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Denial of Authorization to Operate\"\n }, \"DATO\"), \": Denial of Authorization to Operate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition University\"\n }, \"DAU\"), \": Defense Acquisition University\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Workforce Improvement Act\"\n }, \"DAWIA\"), \": Defense Acquisition Workforce Improvement Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Business Council\"\n }, \"DBC\"), \": Defense Business Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Business Systems\"\n }, \"DBS\"), \": Defense Business Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Business Systems Management Committee\"\n }, \"DBSMC\"), \": Defense Business Systems Management Committee\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Derivative Classifier OR Direct Current\"\n }, \"DC\"), \": Derivative Classifier OR Direct Current\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Contract Audit Agency\"\n }, \"DCAA\"), \": Defense Contract Audit Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Cost Assessment and Program Evaluation\"\n }, \"DCAPE\"), \": Director of Cost Assessment and Program Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deliberate and Crisis Action Planning and Execution Segments\"\n }, \"DCAPES\"), \": Deliberate and Crisis Action Planning and Execution Segments\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Distributed Common Ground System\"\n }, \"DCGS\"), \": Distributed Common Ground System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Central Intelligence Directive\"\n }, \"DCID\"), \": Director of Central Intelligence Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Contract Management Agency\"\n }, \"DCMA\"), \": Defense Contract Management Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Civilian Personnel Data System\"\n }, \"DCPDS\"), \": Defense Civilian Personnel Data System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"DOTMLPF-P Change Recommendation\"\n }, \"DCR\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Doctrine, Organization, Training, materiel, Leadership Policy and Education, Personnel, Facilities, and Policy\"\n }, \"DOTMLPF-P\"), \" Change Recommendation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Chief of Staff\"\n }, \"DCS\"), \": Deputy Chief of Staff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Director of National Intelligence for Management\"\n }, \"DDNI/M\"), \": Deputy Director of National Intelligence for Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Director for Requirements OR Dismount Detection Radar\"\n }, \"DDR\"), \": Deputy Director for Requirements OR Dismount Detection Radar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director, Developmental Test and Evaluation\"\n }, \"DDT&E\"), \": Director\\nDevelopmental Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Destruction of Enemy Air Defenses\"\n }, \"DEAD\"), \": Destruction of Enemy Air Defenses\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Enterprise Accounting and Management System\"\n }, \"DEAMS\"), \": Defense Enterprise Accounting and Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Evaluation Framework\"\n }, \"DEF\"), \": Developmental Evaluation Framework\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Secretary of Defense\"\n }, \"DepSecDef\"), \": Deputy Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \": Detachment Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Directed Energy Weapons\"\n }, \"DEW\"), \": Directed Energy Weapons\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Directed Energy Weapons Certification Board\"\n }, \"DEWCB\"), \": Directed Energy Weapons Certification Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Federal Acquisition Regulation Supplement\"\n }, \"DFARS\"), \": Defense Federal Acquisition Regulation Supplement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Dual Frequency Civil Navigation\"\n }, \"DFCN\"), \": Dual Frequency Civil Navigation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Decontamination Family of Systems\"\n }, \"DFoS\"), \": Decontamination Family of Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Healthcare Management Systems Modernization\"\n }, \"DHMSM\"), \": Defense Healthcare Management Systems Modernization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Intelligence Agency\"\n }, \"DIA\"), \": Defense Intelligence Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"DoD Information Assurance Certification and Accreditation Process\"\n }, \"DIACAP\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Information Assurance Certification and Accreditation Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Item Description\"\n }, \"DID\"), \": Data Item Description\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"DIACAP Implementation Plan\"\n }, \"DIP\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"DoD Information Assurance Certification and Accreditation Process\"\n }, \"DIACAP\"), \" Implementation Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Information Systems Agency\"\n }, \"DISA\"), \": Defense Information Systems Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Information Technology Standards Registry\"\n }, \"DISR\"), \": Department of Defense Information Technology Standards Registry\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Information Technology Security Certification and Accreditation Program\"\n }, \"DITSCAP\"), \": Department of Defense Information Technology Security Certification and Accreditation Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data and Information Viewpoint\"\n }, \"DIV\"), \": Data and Information Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Logistics Agency\"\n }, \"DLA\"), \": Defense Logistics Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot-Level Repairable\"\n }, \"DLR\"), \": Depot-Level Repairable\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Mining\"\n }, \"DM\"), \": Data Mining\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Management and Analysis Plan\"\n }, \"DMAP\"), \": Data Management and Analysis Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot Maintenance Activation Working Group\"\n }, \"DMAWG\"), \": Depot Maintenance Activation Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Microelectronics Activity\"\n }, \"DMEA\"), \": Defense Microelectronics Activity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot Maintenance Interservice\"\n }, \"DMI\"), \": Depot Maintenance Interservice\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Medical Information Exchange Joint Legacy Viewer\"\n }, \"DMIX JLV\"), \": Defense Medical Information Exchange Joint Legacy Viewer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defensive Management System OR Diminishing Manufacturing Sources\"\n }, \"DMS\"), \": Defensive Management System OR Diminishing Manufacturing Sources\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Diminishing Manufacturing Sources Material Shortages\"\n }, \"DMSMS\"), \": Diminishing Manufacturing Sources Material Shortages\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Domestic Non-Availability Determination\"\n }, \"DNAD\"), \": Domestic Non-Availability Determination\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of National Intelligence\"\n }, \"DNI\"), \": Director of National Intelligence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \": Department of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Activity Code\"\n }, \"DODAAC\"), \": Department of Defense Activity Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Directive\"\n }, \"DODD\"), \": Department of Defense Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Instruction\"\n }, \"DODI\"), \": Department of Defense Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Information Network\"\n }, \"DODIN\"), \": Department of Defense Information Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Intelligence Production Program\"\n }, \"DODIPP\"), \": Department of Defense Intelligence Production Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Index of Specifications and Standards\"\n }, \"DODISS\"), \": Department of Defense Index of Specifications and Standards\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Manual\"\n }, \"DODM\"), \": Department of Defense Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \": Department of Energy OR Design of Experiments\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of the Navy\"\n }, \"DoN\"), \": Department of the Navy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \": Director of Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Doctrine, Organization, Training, materiel, Leadership Policy and Education, Personnel, Facilities, and Policy\"\n }, \"DOTMLPF-P\"), \": Doctrine\\nOrganization\\nTraining\\nmateriel\\nLeadership Policy and Education\\nPersonnel\\nFacilities\\nand Policy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Development Planning\"\n }, \"DP\"), \": Development Planning\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Procurement and Acquisition Policy\"\n }, \"DPAP\"), \": Director of Procurement and Acquisition Policy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Priorities and Allocation System\"\n }, \"DPAS\"), \": Defense Priorities and Allocation System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot Purchased Equipment Maintenance\"\n }, \"DPEM\"), \": Depot Purchased Equipment Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Planning Guidance\"\n }, \"DPG\"), \": Defense Planning Guidance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Processing Ground Station\"\n }, \"DPGS\"), \": Data Processing Ground Station\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Planning and Programming Guidance\"\n }, \"DPPG\"), \": Defense Planning and Programming Guidance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Dismounted Reconnaissance Sets, Kits, and Outfits\"\n }, \"DR SKO\"), \": Dismounted Reconnaissance Sets\\nKits\\nand Outfits\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deficiency Report\"\n }, \"DR\"), \": Deficiency Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"\n }, \"DRAGON\"), \": E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deficiency Review Board\"\n }, \"DRB\"), \": Deficiency Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Research Engineering Network\"\n }, \"DREN\"), \": Defense Research Engineering Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Referential Integrity\"\n }, \"DRI\"), \": Data Referential Integrity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Referential Integrity\"\n }, \"DRI\"), \"&R: Deficiency Reporting\\nInvestigation and Resolution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"DRAGON Requirements Memorandum\"\n }, \"DRM\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"\n }, \"DRAGON\"), \" Requirements Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Reutilization Marketing Office\"\n }, \"DRMO\"), \": Defense Reutilization Marketing Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Design Readiness Review\"\n }, \"DRR\"), \": Design Readiness Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Direct Reporting Unit\"\n }, \"DRU\"), \": Direct Reporting Unit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Designated Science and Technology Information\"\n }, \"DS&TI\"), \": Designated Science and Technology Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Direct Sales Agreement\"\n }, \"DSA\"), \": Direct Sales Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Decision Support Question\"\n }, \"DSC\"), \": Decision Support Question\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Security Cooperation Agency\"\n }, \"DSCA\"), \": Defense Security Cooperation Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Development System Manager OR Digital System Model\"\n }, \"DSM\"), \": Development System Manager OR Digital System Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot Source of Repair\"\n }, \"DSOR\"), \": Depot Source of Repair\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot Source of Repair\"\n }, \"DSOR\"), \"-EM: Depot Source of Repair-Electronic Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \": Developmental Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E: Developmental Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Type Definition\"\n }, \"DTD\"), \": Data Type Definition\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Technical Information Center\"\n }, \"DTIC\"), \": Defense Technical Information Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Directive-Type Memorandum\"\n }, \"DTM\"), \": Directive-Type Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detailed Test Plan\"\n }, \"DTP\"), \": Detailed Test Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Under Secretary of Defense\"\n }, \"DUSD\"), \": Deputy Under Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \": Effectiveness and Suitability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"\n }, \"E-3 DRAGON\"), \": E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Environmental Effects\"\n }, \"E3\"), \": Electromagnetic Environmental Effects\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Economic Analysis OR Electronic Attack OR Evolutionary Acquisition OR Executing Authority\"\n }, \"EA\"), \": Economic Analysis OR Electronic Attack OR Evolutionary Acquisition OR Executing Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Estimate at Completion\"\n }, \"EAC\"), \": Estimate at Completion\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Estimated Completion Date\"\n }, \"ECD\"), \": Estimated Completion Date\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Countermeasures\"\n }, \"ECM\"), \": Electronic Countermeasures\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enclave Control Node\"\n }, \"ECN\"), \": Enclave Control Node\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Expeditionary Combat Support System\"\n }, \"ECSS\"), \": Expeditionary Combat Support System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \": Executive Director\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engineering Data Guidance Conference\"\n }, \"EDGC\"), \": Engineering Data Guidance Conference\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engineering Data Manager (or Management) OR Engineering Development Model\"\n }, \"EDM\"), \": Engineering Data Manager (or Management) OR Engineering Development Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engineering Data Service Center\"\n }, \"EDSC\"), \": Engineering Data Service Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enterprise Engineering Center\"\n }, \"EEC\"), \": Enterprise Engineering Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Element of Expense Investment Code\"\n }, \"EEIC\"), \": Element of Expense Investment Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Essential Function Failure\"\n }, \"EFF\"), \": Essential Function Failure\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Extremely High Frequency\"\n }, \"EHF\"), \": Extremely High Frequency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment Impact Analysis Process\"\n }, \"EIAP\"), \": Environment Impact Analysis Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enterprise Information Environment Mission Area\"\n }, \"EIEMA\"), \": Enterprise Information Environment Mission Area\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Influence Strategy\"\n }, \"EIS\"), \": Early Influence Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Influence Team\"\n }, \"EIT\"), \": Early Influence Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enterprise Information Technology Data Repository\"\n }, \"EITDR\"), \": Enterprise Information Technology Data Repository\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Key Management System\"\n }, \"EKMS\"), \": Electronic Key Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Elevated Level of Assurance\"\n }, \"ELA\"), \": Elevated Level of Assurance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Emergency Locator Transmitter\"\n }, \"ELT\"), \": Emergency Locator Transmitter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Expectation Management Agreement\"\n }, \"EMA\"), \": Expectation Management Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Compatibility\"\n }, \"EMC\"), \": Electromagnetic Compatibility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Compatibility\"\n }, \"EMC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Interference\"\n }, \"EMI\"), \": Electromagnetic Compatibility/Electromagnetic Interference\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engineering and Manufacturing Development\"\n }, \"EMD\"), \": Engineering and Manufacturing Development\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Interference\"\n }, \"EMI\"), \": Electromagnetic Interference\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Pulse\"\n }, \"EMP\"), \": Electromagnetic Pulse\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Emission Security\"\n }, \"EMSEC\"), \": Emission Security\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Vulnerability\"\n }, \"EMV\"), \": Electromagnetic Vulnerability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engine Structural Integrity Program\"\n }, \"ENSIP\"), \": Engine Structural Integrity Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electro-Optical OR Executive Order OR Engineering Order\"\n }, \"EO\"), \": Electro-Optical OR Executive Order OR Engineering Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \": Early Operational Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Explosive Ordnance Disposal\"\n }, \"EOD\"), \": Explosive Ordnance Disposal\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Protection\"\n }, \"EP\"), \": Electronic Protection\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"F-15 Eagle Passive and Active Warning and Survivability System\"\n }, \"EPAWSS\"), \": F-15 Eagle Passive and Active Warning and Survivability System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Proving Ground\"\n }, \"EPG\"), \": Electronic Proving Ground\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AIM-120C Advanced Electronic Protection Improvement Program\"\n }, \"EPIP\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \"-120C Advanced Electronic Protection Improvement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enhanced Polar System\"\n }, \"EPS\"), \": Enhanced Polar System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetically Enhanced Physical Vapor Deposition (gun tube coating\"\n }, \"EPVD\"), \": Electromagnetically Enhanced Physical Vapor Deposition (gun tube coating\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Remote Fill\"\n }, \"ERF\"), \": Electronic Remote Fill\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environmental Resources Manager\"\n }, \"ERM\"), \": Environmental Resources Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \": Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \": Environment\\nSafety\\nand Occupational Health\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Council\"\n }, \"ESOHC\"), \": Environment\\nSafety\\nand Occupational Health Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \": Environment\\nSafety\\nand Occupational Health Certification Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \": Environment\\nSafety\\nand Occupational Health Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Emergency and Special Program\"\n }, \"ESP\"), \": Emergency and Special Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness, Suitability, and Survivability OR Evolved Strategic Satellite Communications\"\n }, \"ESS\"), \": Effectiveness\\nSuitability\\nand Survivability OR Evolved Strategic Satellite Communications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Systems Wing OR Evaluation Summary Worksheet\"\n }, \"ESW\"), \": Electronic Systems Wing OR Evaluation Summary Worksheet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enhanced Technical Information Management System\"\n }, \"ETIMS\"), \": Enhanced Technical Information Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Technical Manual\"\n }, \"ETM\"), \": Electronic Technical Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executing Test Organization\"\n }, \"ETO\"), \": Executing Test Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engineering Units\"\n }, \"EU\"), \": Engineering Units\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"End Use Certificate\"\n }, \"EUC\"), \": End Use Certificate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \": Evaluation View\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Earned Value Management\"\n }, \"EVM\"), \": Earned Value Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Earned Value Management\"\n }, \"EVM\"), \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Change Request\"\n }, \"CR\"), \": Earned Value Management-Central Repository\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Earned Value Management System\"\n }, \"EVMS\"), \": Earned Value Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Warfare\"\n }, \"EW\"), \": Electronic Warfare\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Warfare Infrastructure Improvement Program\"\n }, \"EWIIP\"), \": Electronic Warfare Infrastructure Improvement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Warfare Integrated Reprogramming\"\n }, \"EWIR\"), \": Electronic Warfare Integrated Reprogramming\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Weapons System Review\"\n }, \"EWSR\"), \": Executive Weapons System Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"F-15 Eagle Passive and Active Warning and Survivability System\"\n }, \"F-15 EPAWSS\"), \": F-15 Eagle Passive and Active Warning and Survivability System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"F-15 Infrared Search and Track System\"\n }, \"F-15 IRST\"), \": F-15 Infrared Search and Track System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Form, Fit, Function, or Interface\"\n }, \"F3I\"), \": Form\\nFit\\nFunction\\nor Interface\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Aviation Administration OR Functional Area Analysis\"\n }, \"FAA\"), \": Federal Aviation Administration OR Functional Area Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Family of Advanced Beyond Line Of Sight Terminals\"\n }, \"FAB-T\"), \": Family of Advanced Beyond Line Of Sight Terminals\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Forward Air Controller-Airborne\"\n }, \"FAC-A\"), \": Forward Air Controller-Airborne\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Acquisition Regulation\"\n }, \"FAR\"), \": Federal Acquisition Regulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Area Records Manager\"\n }, \"FARM\"), \": Functional Area Records Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"First Article Test\"\n }, \"FAT\"), \": First Article Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Configuration Audit\"\n }, \"FCA\"), \": Functional Configuration Audit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Capabilities Board\"\n }, \"FCB\"), \": Functional Capabilities Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Flagship Capability Concepts\"\n }, \"FCC\"), \": Flagship Capability Concepts\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Foreign Comparative Test\"\n }, \"FCT\"), \": Foreign Comparative Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fielding Decision\"\n }, \"FD\"), \": Fielding Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fielding Decision\"\n }, \"FD\"), \"/SC: Failure Definition/Scoring Criteria\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Final Evaluation and Decision Brief\"\n }, \"FDB\"), \": Final Evaluation and Decision Brief\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Deployment Decision\"\n }, \"FDD\"), \": Full Deployment Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Deployment Decision Review\"\n }, \"FDDR\"), \": Full Deployment Decision Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Force Development Evaluation\"\n }, \"FDE\"), \": Force Development Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fee Determining Official\"\n }, \"FDO\"), \": Fee Determining Official\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Final (or Formal) Design Review\"\n }, \"FDR\"), \": Final (or Formal) Design Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Force Element Terminal\"\n }, \"FET\"), \": Force Element Terminal\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Firm Fixed Price\"\n }, \"FFP\"), \": Firm Fixed Price\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federally Funded Research and Development Centers\"\n }, \"FFRDC\"), \": Federally Funded Research and Development Centers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Friendly Force Tracking\"\n }, \"FFT\"), \": Friendly Force Tracking\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Flying Hours\"\n }, \"FH\"), \": Flying Hours\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Financial Improvement and Audit Readiness\"\n }, \"FIAR\"), \": Financial Improvement and Audit Readiness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Information Processing\"\n }, \"FIP\"), \": Federal Information Processing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Information System Controls Audit Manual\"\n }, \"FISCAM\"), \": Federal Information System Controls Audit Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Information Security Management Act of 2002\"\n }, \"FISMA\"), \": Federal Information Security Management Act of 2002\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Financial Management OR Frequency Modulation OR Functional Manager\"\n }, \"FM\"), \": Financial Management OR Frequency Modulation OR Functional Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fully Mission Capable\"\n }, \"FMC\"), \": Fully Mission Capable\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Failure Mode, Effects, and Criticality Analysis\"\n }, \"FMECA\"), \": Failure Mode\\nEffects\\nand Criticality Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Flight Manual Manager\"\n }, \"FMM\"), \": Flight Manual Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Flight Manuals Program OR Foreign Materiel Program\"\n }, \"FMP\"), \": Flight Manuals Program OR Foreign Materiel Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Financial Management Regulation\"\n }, \"FMR\"), \": Financial Management Regulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Financial Management Regulation System\"\n }, \"FMRS\"), \": Financial Management Regulation System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Foreign Military Sales\"\n }, \"FMS\"), \": Foreign Military Sales\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fuze Module Unit-139\"\n }, \"FMU-139 D/B\"), \": Fuze Module Unit-139\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Needs Analysis\"\n }, \"FNA\"), \": Functional Needs Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Field Operating Agency\"\n }, \"FOA\"), \": Field Operating Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Forward Operating Base\"\n }, \"FOB\"), \": Forward Operating Base\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Operational Capability\"\n }, \"FOC\"), \": Full Operational Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Freedom of Information Act\"\n }, \"FOIA\"), \": Freedom of Information Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Modernization\"\n }, \"FoM\"), \": Follow-on Modernization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Future Operationally Resilient Ground Evolution\"\n }, \"FORGE\"), \": Future Operationally Resilient Ground Evolution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Family of Systems\"\n }, \"FoS\"), \": Family of Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \": Follow-on Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Operational Utility\"\n }, \"FOU\"), \": Full Operational Utility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"For Official Use Only\"\n }, \"FOUO\"), \": For Official Use Only\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Field of View\"\n }, \"FOV\"), \": Field of View\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fixed-Price with Award Fee\"\n }, \"FPAF\"), \": Fixed-Price with Award Fee\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Production Decision\"\n }, \"FPD\"), \": Follow-on Production Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Procurement data System-Next Generation\"\n }, \"FPDS-NG\"), \": Federal Procurement data System-Next Generation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fixed-Price Incentive\"\n }, \"FPIF\"), \": Fixed-Price Incentive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Final Pricing Report OR Final Proposal Revision\"\n }, \"FPR\"), \": Final Pricing Report OR Final Proposal Revision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Forward Price Rate Agreements\"\n }, \"FPRA\"), \": Forward Price Rate Agreements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Formal Qualification Review\"\n }, \"FQR\"), \": Formal Qualification Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Formerly Restricted Data\"\n }, \"FRD\"), \": Formerly Restricted Data\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full-Rate Production\"\n }, \"FRP\"), \": Full-Rate Production\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full-Rate Production\"\n }, \"FRP\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fielding Decision\"\n }, \"FD\"), \": Full-Rate Production or Full Deployment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Rate Production Decision Review\"\n }, \"FRPDR\"), \": Full Rate Production Decision Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Requirements Review Board\"\n }, \"FRRB\"), \": Functional Requirements Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Solution Analysis\"\n }, \"FSA\"), \": Functional Solution Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Supply Classification\"\n }, \"FSC\"), \": Federal Supply Classification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Field Service Representative\"\n }, \"FSR\"), \": Field Service Representative\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Time Equivalent\"\n }, \"FTE\"), \": Full Time Equivalent\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Field Training Exercise\"\n }, \"FTX\"), \": Field Training Exercise\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fiscal Year\"\n }, \"FY\"), \": Fiscal Year\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Future Years Defense Program\"\n }, \"FYDP\"), \": Future Years Defense Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General and Administrative (Expense)\"\n }, \"G&A\"), \": General and Administrative (Expense)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Accountability Office\"\n }, \"GAO\"), \": Government Accountability Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Analysis Tool\"\n }, \"GAT\"), \": Government Analysis Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Broadcast Service\"\n }, \"GBS\"), \": Global Broadcast Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ground Based Strategic Deterrent\"\n }, \"GBSD\"), \": Ground Based Strategic Deterrent\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Guided Bomb Unit\"\n }, \"GBU\"), \": Guided Bomb Unit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Cyberspace Integration Center\"\n }, \"GCIC\"), \": Global Cyberspace Integration Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ground Control Stations\"\n }, \"GCS\"), \": Ground Control Stations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Combat Support System – Air Force\"\n }, \"GCSS-AF\"), \": Global Combat Support System \\u2013 Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Development Test\"\n }, \"GDT\"), \": Government Development Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Guidance for the Employment of the Force\"\n }, \"GEF\"), \": Guidance for the Employment of the Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Geosynchronous Earth Orbit\"\n }, \"GEO\"), \": Geosynchronous Earth Orbit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Furnished Equipment\"\n }, \"GFE\"), \": Government Furnished Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Furnished Information\"\n }, \"GFI\"), \": Government Furnished Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Force Management\"\n }, \"GFM\"), \": Global Force Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Furnished Property\"\n }, \"GFP\"), \": Government Furnished Property\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Hawk Ground Segment Modernization Program\"\n }, \"GH GSMP\"), \": Global Hawk Ground Segment Modernization Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Industry Data Exchange Program\"\n }, \"GIDEP\"), \": Government Industry Data Exchange Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Information Grid\"\n }, \"GIG\"), \": Global Information Grid\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Logistics Support Center\"\n }, \"GLSC\"), \": Global Logistics Support Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ground Movement Terrain Radar\"\n }, \"GMT\"), \": Ground Movement Terrain Radar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ground Moving Target Indicator\"\n }, \"GMTI\"), \": Ground Moving Target Indicator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Officer\"\n }, \"GO\"), \": General Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Officer\"\n }, \"GO\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Executive Service\"\n }, \"SES\"), \": General Officer/Senior Executive Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Owned Contractor Operated\"\n }, \"GOCO\"), \": Government Owned Contractor Operated\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Officer Steering Group\"\n }, \"GOSG\"), \": General Officer Steering Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Off-the-Shelf\"\n }, \"GOTS\"), \": Government Off-the-Shelf\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"GPS Pulse-per-Second Adapter\"\n }, \"GPA\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" Pulse-per-Second Adapter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \": Government Purchase Card\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Purpose Decontaminant Program\"\n }, \"GPD\"), \": General Purpose Decontaminant Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purpose License Rights\"\n }, \"GPLR\"), \": Government Purpose License Rights\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purpose Rights\"\n }, \"GPR\"), \": Government Purpose Rights\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System III Contingency Operations\"\n }, \"GPS III COps\"), \": Global Positioning System III Contingency Operations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System M-Code Early Use\"\n }, \"GPS MCEU\"), \": Global Positioning System M-Code Early Use\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military GPS User Equipment\"\n }, \"GPS MGUE\"), \": Military \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" User Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"GPS Next Generation Operational Control System\"\n }, \"GPS OCX\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" Next Generation Operational Control System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \": Global Positioning System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Schedule\"\n }, \"GS\"), \": General Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Services Administration\"\n }, \"GSA\"), \": Government Services Administration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ground Segment Modernization Program\"\n }, \"GSMP\"), \": Ground Segment Modernization Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Information Grid Technical Guidance Federation\"\n }, \"GTG-F\"), \": Global Information Grid Technical Guidance Federation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Theater Security Cooperative Management Information System\"\n }, \"G-TSCMIS\"), \": Global Theater Security Cooperative Management Information System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Guided Test Vehicle\"\n }, \"GTV\"), \": Guided Test Vehicle\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters Air Force\"\n }, \"HAF\"), \": Headquarters Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters Air Force Mission Directive\"\n }, \"HAFMD\"), \": Headquarters Air Force Mission Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardness Assurance, Maintenance, and Surveillance\"\n }, \"HAMS\"), \": Hardness Assurance\\nMaintenance\\nand Surveillance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(AGM-84-Fixed Wing; RGM-Surface Ships; UGM-Submarine Launched)\"\n }, \"HARPOON\"), \": (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Ground Missile\"\n }, \"AGM\"), \"-84-Fixed Wing; RGM-Surface Ships; UGM-Submarine Launched)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Head of Contracting Activity (or Agency)\"\n }, \"HCA\"), \": Head of Contracting Activity (or Agency)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Human-Computer Interactions\"\n }, \"HCI\"), \": Human-Computer Interactions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Human Capital Strategic Plan\"\n }, \"HCSP\"), \": Human Capital Strategic Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hypersonic Conventional Strike Weapon\"\n }, \"HCSW\"), \": Hypersonic Conventional Strike Weapon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hierarchical Data Format\"\n }, \"HDF\"), \": Hierarchical Data Format\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"High-Altitude Electromagnetic Pulse\"\n }, \"HEMP\"), \": High-Altitude Electromagnetic Pulse\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hazards of Electromagnetic Radiation to Volatile Material\"\n }, \"HERF\"), \": Hazards of Electromagnetic Radiation to Volatile Material\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hazards of Electromagnetic Radiation to Ordinance\"\n }, \"HERO\"), \": Hazards of Electromagnetic Radiation to Ordinance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hazards of Electromagnetic Radiation to Personnel\"\n }, \"HERP\"), \": Hazards of Electromagnetic Radiation to Personnel\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Human Factors Engineering\"\n }, \"HFE\"), \": Human Factors Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware in the Loop\"\n }, \"HITL\"), \": Hardware in the Loop\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardness Maintenance / Hardness Surveillance\"\n }, \"HM/HS\"), \": Hardness Maintenance / Hardness Surveillance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Handheld, Manpack, and Small Form Fit\"\n }, \"HMS\"), \": Handheld\\nManpack\\nand Small Form Fit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"HQ AFOTEC History Office\"\n }, \"HO\"), \": \", 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\"), \" History Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters Operating Instruction\"\n }, \"HOI\"), \": Headquarters Operating Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"High Performance Team\"\n }, \"HPT\"), \": High Performance Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \": Headquarters\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Human Systems Integration\"\n }, \"HSI\"), \": Human Systems Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"High Speed Network\"\n }, \"HSN\"), \": High Speed Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \": Health and Safety Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hard Target Munitions\"\n }, \"HTM\"), \": Hard Target Munitions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hard Target Void Sensing Fuze\"\n }, \"HTVSF\"), \": Hard Target Void Sensing Fuze\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware Assurance\"\n }, \"HwA\"), \": Hardware Assurance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Assurance (replaced by “cybersecurity”)\"\n }, \"IA\"), \": Information Assurance (replaced by \\u201Ccybersecurity\\u201D)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"International Armaments Cooperation\"\n }, \"IAC\"), \": International Armaments Cooperation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Air Defense\"\n }, \"IAD\"), \": Integrated Air Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Air Defense System\"\n }, \"IADS\"), \": Integrated Air Defense System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Aircrew Ensemble\"\n }, \"IAE\"), \": Integrated Aircrew Ensemble\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Air and Missile Defense\"\n }, \"IAMD\"), \": Integrated Air and Missile Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interim Authorization to Operate\"\n }, \"IATO\"), \": Interim Authorization to Operate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interim Authority to Test or Authorization to Test\"\n }, \"IATT\"), \": Interim Authority to Test or Authorization to Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Assurance Vulnerability Alert\"\n }, \"IAVA\"), \": Information Assurance Vulnerability Alert\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \": In Accordance With\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Involvement Briefing\"\n }, \"IB\"), \": Involvement Briefing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Individual Body Armor\"\n }, \"IBA\"), \": Individual Body Armor\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Involvement Bullet Background Paper\"\n }, \"IBBP\"), \": Involvement Bullet Background Paper\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Infantry Brigade Combat Team\"\n }, \"IBCT\"), \": Infantry Brigade Combat Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Base Defense Command and Control\"\n }, \"IBDC2\"), \": Integrated Base Defense Command and Control\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Base Defense Security System\"\n }, \"IBDSS\"), \": Integrated Base Defense Security System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Baseline Review\"\n }, \"IBR\"), \": Integrated Baseline Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Broadcast Service\"\n }, \"IBS\"), \": Integrated Broadcast Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Community\"\n }, \"IC\"), \": Intelligence Community\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Individual Combat Aircrew Display System\"\n }, \"ICADS\"), \": Individual Combat Aircrew Display System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intercontinental Ballistic Missile\"\n }, \"ICBM\"), \": Intercontinental Ballistic Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Community Capability Requirements\"\n }, \"ICCR\"), \": Intelligence Community Capability Requirements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \": Initial Capabilities Document OR Interface Control Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"initial Capability Development Document\"\n }, \"iCDD\"), \": initial Capability Development Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Independent Cost Estimate\"\n }, \"ICE\"), \": Independent Cost Estimate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Certification Evaluation Plan\"\n }, \"ICEP\"), \": Information Certification Evaluation Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interim Contractor Support\"\n }, \"ICM\"), \": Interim Contractor Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Inventory Control Point\"\n }, \"ICP\"), \": Inventory Control Point\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interim Contract Support\"\n }, \"ICS\"), \": Interim Contract Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Concept Team\"\n }, \"ICT\"), \": Integrated Concept Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Identification\"\n }, \"ID\"), \": Identification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Identification\"\n }, \"ID\"), \"/IQ: Indefinite Delivery/Indefinite Quantity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Data Environment\"\n }, \"IDE\"), \": Integrated Data Environment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Indentured Data List\"\n }, \"IDL\"), \": Indentured Data List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Data Requirements List\"\n }, \"IDRL\"), \": Integrated Data Requirements List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Evaluation Briefing\"\n }, \"IEB\"), \": Initial Evaluation Briefing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Improvised Explosive Device\"\n }, \"IED\"), \": Improvised Explosive Device\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Electronic Health Records\"\n }, \"iEHR\"), \": Integrated Electronic Health Records\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Exchange Requirements\"\n }, \"IER\"), \": Information Exchange Requirements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interactive Electronic Technical Manual\"\n }, \"IETM\"), \": Interactive Electronic Technical Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Functional Capability\"\n }, \"IFC\"), \": Integrated Functional Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intraflight Datalink\"\n }, \"IFDL\"), \": Intraflight Datalink\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence in Force Modernization\"\n }, \"IFM\"), \": Intelligence in Force Modernization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In-Flight Targeting Update\"\n }, \"IFTU\"), \": In-Flight Targeting Update\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Inherently Governmental Function\"\n }, \"IGF\"), \": Inherently Governmental Function\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Integrated Test Design\"\n }, \"IITD\"), \": Initial Integrated Test Design\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \": Involvement Letter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Life Cycle Management\"\n }, \"ILCM\"), \": Integrated Life Cycle Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Instrument Landing System OR Integrated Logistics Support\"\n }, \"ILS\"), \": Instrument Landing System OR Integrated Logistics Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Logistics Support Plan\"\n }, \"ILSP\"), \": Integrated Logistics Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Insensitive Munitions\"\n }, \"IM\"), \": Insensitive Munitions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Instrument Meteorological Conditions\"\n }, \"IMC\"), \": Instrument Meteorological Conditions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Mission Data\"\n }, \"IMD\"), \": Intelligence Mission Data\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Maintenance Data System\"\n }, \"IMDS\"), \": Integrated Maintenance Data System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"International Military Education and Training\"\n }, \"IMET\"), \": International Military Education and Training\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Master Plan\"\n }, \"IMP\"), \": Integrated Master Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Master Schedule\"\n }, \"IMS\"), \": Integrated Master Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Management Tool\"\n }, \"IMT\"), \": Information Management Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Master Test Plan\"\n }, \"IMTP\"), \": Integrated Master Test Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Increment\"\n }, \"INC\"), \": Increment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Inertial Navigation System\"\n }, \"INS\"), \": Inertial Navigation System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Operations\"\n }, \"IO\"), \": Information Operations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Capability\"\n }, \"IOC\"), \": Initial Operational Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \": Initial Operational Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E: Initial Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Protection OR Initial Point OR Intellectual Property OR Internet Protocol\"\n }, \"IP\"), \": Information Protection OR Initial Point OR Intellectual Property OR Internet Protocol\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Independent Program Assessment\"\n }, \"IPA\"), \": Independent Program Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Independent Program Assessment Team\"\n }, \"IPAT\"), \": Independent Program Assessment Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Priority List\"\n }, \"IPL\"), \": Integrated Priority List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Independent Program Management Report\"\n }, \"IPMR\"), \": Independent Program Management Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In-Process Review\"\n }, \"IPR\"), \": In-Process Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Program Summary OR Intellectual Property Strategy\"\n }, \"IPS\"), \": Integrated Program Summary OR Intellectual Property Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Provisioning Performance Specifications\"\n }, \"IPSS\"), \": Initial Provisioning Performance Specifications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Product Team\"\n }, \"IPT\"), \": Integrated Product Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Infrared\"\n }, \"IR\"), \": Infrared\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Independent Research and Development\"\n }, \"IRAD\"), \": Independent Research and Development\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Resources Board OR Investment Review Board\"\n }, \"IRB\"), \": Intelligence Resources Board OR Investment Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Infrared Countermeasures\"\n }, \"IRCM\"), \": Infrared Countermeasures\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information and Resource Support System\"\n }, \"IRSS\"), \": Information and Resource Support System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Infrared Search and Track System\"\n }, \"IRST\"), \": Infrared Search and Track System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System Capability Development Document\"\n }, \"IS CDD\"), \": Information System Capability Development Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System Initial Capabilities Document\"\n }, \"IS ICD\"), \": Information System Initial Capabilities Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \": Information System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"International Standardization Agreement\"\n }, \"ISA\"), \": International Standardization Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Systems Audit and Control Association\"\n }, \"ISACA\"), \": Information Systems Audit and Control Association\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"International Standards Organization\"\n }, \"ISO\"), \": International Standards Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Security Oversight Office\"\n }, \"ISOO\"), \": Information Security Oversight Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Support Plan\"\n }, \"ISP\"), \": Information Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Strategic Planning and Analysis Network\"\n }, \"ISPAN\"), \": Integrated Strategic Planning and Analysis Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence, Surveillance, and Reconnaissance OR Interim Summary Report\"\n }, \"ISR\"), \": Intelligence\\nSurveillance\\nand Reconnaissance OR Interim Summary Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System Security Manager\"\n }, \"ISSM\"), \": Information System Security Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Support Working Group\"\n }, \"ISWG\"), \": Intelligence Support Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology Lean\"\n }, \"IT Lean\"), \": Information Technology Lean\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \": Information Technology OR Integrated Testing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E: Integrated Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Space OR National Security Strategy OR National Security System\"\n }, \"NSS\"), \": Information Technology/National Security System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interface Test Adapter\"\n }, \"ITA\"), \": Interface Test Adapter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology Acquisition Board\"\n }, \"ITAB\"), \": Information Technology Acquisition Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Concept\"\n }, \"ITC\"), \": Integrated Test Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \": Initial Test Design\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Threat Environment Assessment\"\n }, \"ITEA\"), \": Initial Threat Environment Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Tasking Order\"\n }, \"ITO\"), \": Initial Tasking Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Plan\"\n }, \"ITP\"), \": Integrated Test Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \": Integrated Test Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Item Unique Identification\"\n }, \"IUID\"), \": Item Unique Identification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Internal Use Software\"\n }, \"IUS\"), \": Internal Use Software\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Warfare\"\n }, \"IW\"), \": Information Warfare\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Internal Weapons Bay Upgrade\"\n }, \"IWBU\"), \": Internal Weapons Bay Upgrade\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Weapons System Management\"\n }, \"IWSM\"), \": Integrated Weapons System Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Justification and Approval\"\n }, \"J&A\"), \": Justification and Approval\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Staff J-8, Deputy Director for Requirements\"\n }, \"J-8/DDR\"), \": Joint Staff J-8\\nDeputy Director for Requirements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Staff J-8, Special Access Program Coordinator\"\n }, \"J-8/SAPCOORD\"), \": Joint Staff J-8\\nSpecial Access Program Coordinator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Air Force Army Navy\"\n }, \"JAFAN\"), \": Joint Air Force Army Navy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Air-to-Ground Missile\"\n }, \"JAGM\"), \": Joint Air-to-Ground Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Aerial Layered Network\"\n }, \"JALN\"), \": Joint Aerial Layered Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Aircraft Survivability Program\"\n }, \"JASP\"), \": Joint Aircraft Survivability Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Air-to-Surface Standoff Missile\"\n }, \"JASSM\"), \": Joint Air-to-Surface Standoff Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Avionics Workstation\"\n }, \"JAWS\"), \": Joint Avionics Workstation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \": Joint Biological Agent Decontamination System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Tactical Detection System\"\n }, \"JBTDS\"), \": Joint Biological Tactical Detection System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capability Area\"\n }, \"JCA\"), \": Joint Capability Area\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Improvised Explosive Device Defeat Capability Approval and Acquisition Management Process\"\n }, \"JCAAMP\"), \": Joint Improvised Explosive Device Defeat Capability Approval and Acquisition Management Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Computer-Aided Acquisition and Logistic Support\"\n }, \"JCALS\"), \": Joint Computer-Aided Acquisition and Logistic Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Board\"\n }, \"JCB\"), \": Joint Capabilities Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Cyber Command and Control\"\n }, \"JCC2\"), \": Joint Cyber Command and Control\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Combat Capability Assessment\"\n }, \"JCCA\"), \": Joint Combat Capability Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Document\"\n }, \"JCD\"), \": Joint Capabilities Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Integration and Development System\"\n }, \"JCIDS\"), \": Joint Capabilities Integration and Development System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint C4I Program Assessment Tool-Empowered\"\n }, \"JCPATE\"), \": Joint \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Communications, Computers, and Intelligence\"\n }, \"C4I\"), \" Program Assessment Tool-Empowered\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Counter Radio-Controlled Improvised Explosive Device Electronic Warfare\"\n }, \"JCREW\"), \": Joint Counter Radio-Controlled Improvised Explosive Device Electronic Warfare\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Chiefs of Staff\"\n }, \"JCS\"), \": Joint Chiefs of Staff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capability Technology Demonstration\"\n }, \"JCTD\"), \": Joint Capability Technology Demonstration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Direct Attack Munition\"\n }, \"JDAM\"), \": Joint Direct Attack Munition\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Depot Maintenance Activities Group\"\n }, \"JDMAG\"), \": Joint Depot Maintenance Activities Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Deficiency Reporting System\"\n }, \"JDRS\"), \": Joint Deficiency Reporting System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Engineering Data Management Information and Combat System\"\n }, \"JEDMICS\"), \": Joint Engineering Data Management Information and Combat System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Effects Model\"\n }, \"JEM\"), \": Joint Effects Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Enterprise Network Manager\"\n }, \"JENM\"), \": Joint Enterprise Network Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Emergent Operational Need\"\n }, \"JEON\"), \": Joint Emergent Operational Need\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Functional Concept\"\n }, \"JFC\"), \": Joint Functional Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Functional Component Commander\"\n }, \"JFCC\"), \": Joint Functional Component Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Integrating Concept\"\n }, \"JIC\"), \": Joint Integrating Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interface Control Officer\"\n }, \"JICO\"), \": Joint Interface Control Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Intelligence Estimate\"\n }, \"JIE\"), \": Joint Intelligence Estimate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Improvised Explosive Device Defeat Fund\"\n }, \"JIEDDF\"), \": Joint Improvised Explosive Device Defeat Fund\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Improvised Explosive Device Defeat Organization\"\n }, \"JIEDDO\"), \": Joint Improvised Explosive Device Defeat Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interoperability Test Command\"\n }, \"JITC\"), \": Joint Interoperability Test Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Logistics Estimate\"\n }, \"JLE\"), \": Joint Logistics Estimate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Lessons Learned Program\"\n }, \"JLLP\"), \": Joint Lessons Learned Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Light Tactical Vehicle\"\n }, \"JLTV\"), \": Joint Light Tactical Vehicle\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Mission Computer\"\n }, \"JMC\"), \": Joint Mission Computer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Mission Environment Test Capability\"\n }, \"JMETC\"), \": Joint Mission Environment Test Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Miniature Munitions\"\n }, \"JMM\"), \": Joint Miniature Munitions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Space Operations Center (JSpOC) Mission System\"\n }, \"JMS\"), \": Joint Space Operations Center (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Space Operations Center\"\n }, \"JSpOC\"), \") Mission System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Mission Thread\"\n }, \"JMT\"), \": Joint Mission Thread\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Operating Concept\"\n }, \"JOC\"), \": Joint Operating Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Operational Medicine Information Systems\"\n }, \"JOMIS\"), \": Joint Operational Medicine Information Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Operations Concept\"\n }, \"JOpsC\"), \": Joint Operations Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"JSF Operational Test Team\"\n }, \"JOTT\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strike Fighter\"\n }, \"JSF\"), \" Operational Test Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \": Joint Publication\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Precision Approach and Landing System\"\n }, \"JPALS\"), \": Joint Precision Approach and Landing System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Potential Designator\"\n }, \"JPD\"), \": Joint Potential Designator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Personnel Estimate\"\n }, \"JPE\"), \": Joint Personnel Estimate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Planning Guidance\"\n }, \"JPG\"), \": Joint Planning Guidance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strike fighter Program Office\"\n }, \"JPO\"), \": Joint Strike fighter Program Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Rapid Acquisition Cell\"\n }, \"JRAC\"), \": Joint Rapid Acquisition Cell\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \": Joint Reliability and Maintainability Evaluation Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Requirements Office\"\n }, \"JRO\"), \": Joint Requirements Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Requirements Oversight Council\"\n }, \"JROC\"), \": Joint Requirements Oversight Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Requirements Oversight Council Memorandum\"\n }, \"JROCM\"), \": Joint Requirements Oversight Council Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Staff\"\n }, \"JS\"), \": Joint Staff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strategic Assessment\"\n }, \"JSA\"), \": Joint Strategic Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Service Aircrew Mask-Fixed Wing\"\n }, \"JSAM-FW\"), \": Joint Service Aircrew Mask-Fixed Wing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Service Aircrew Mask-Strategic Aircraft\"\n }, \"JSAM-SA\"), \": Joint Service Aircrew Mask-Strategic Aircraft\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Service Aircrew Mask-Tactical Aircraft\"\n }, \"JSAM-TA\"), \": Joint Service Aircrew Mask-Tactical Aircraft\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Staffing Designator\"\n }, \"JSD\"), \": Joint Staffing Designator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Simulation Environment\"\n }, \"JSE\"), \": Joint Simulation Environment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Sensitive Equipment Wipes (Decontamination Family of Systems)\"\n }, \"JSEW\"), \": Joint Sensitive Equipment Wipes (Decontamination Family of Systems)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strike Fighter\"\n }, \"JSF\"), \": Joint Strike Fighter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Special Access Program (SAP) Implementation Guide\"\n }, \"JSIG\"), \": Joint Special Access Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \") Implementation Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Stand-Off Weapon\"\n }, \"JSOW\"), \": Joint Stand-Off Weapon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Space Operations Center\"\n }, \"JSpOC\"), \": Joint Space Operations Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strategic Planning System\"\n }, \"JSPS\"), \": Joint Strategic Planning System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strategy Review\"\n }, \"JSR\"), \": Joint Strategy Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interface Control Officer (JICO) Support System\"\n }, \"JSS\"), \": Joint Interface Control Officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interface Control Officer\"\n }, \"JICO\"), \") Support System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint System Threat Assessment Report\"\n }, \"JSTAR\"), \": Joint System Threat Assessment Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Surveillance Target Attack Radar System Recapitalization\"\n }, \"JSTARS RECAP\"), \": Joint Surveillance Target Attack Radar System Recapitalization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Test and Evaluation\"\n }, \"JT&E\"), \": Joint Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Terminal Attack Controller\"\n }, \"JTAC\"), \": Joint Terminal Attack Controller\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Tactical Radio\"\n }, \"JTR\"), \": Joint Tactical Radio\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Tactical Radio System\"\n }, \"JTRS\"), \": Joint Tactical Radio System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Tactical Radio System\"\n }, \"JTRS\"), \"-AMF: Joint Tactical Radio System-Airborne Maritime Fixed\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Urgent Operational Need\"\n }, \"JUON\"), \": Joint Urgent Operational Need\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint United States Forces Korea Portal and Integrated Threat Recognition\"\n }, \"JUPITR\"), \": Joint United States Forces Korea Portal and Integrated Threat Recognition\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Warning & Reporting Network\"\n }, \"JWARN\"), \": Joint Warning & Reporting Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Worldwide Intelligence Communications System\"\n }, \"JWICS\"), \": Joint Worldwide Intelligence Communications System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Decision Point\"\n }, \"KDP\"), \": Key Decision Point\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Interface Profile\"\n }, \"KIP\"), \": Key Interface Profile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Leadership Position\"\n }, \"KLP\"), \": Key Leadership Position\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Knowledge Management/Decision Support\"\n }, \"KM/DS\"), \": Knowledge Management/Decision Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Knowledge Now\"\n }, \"KN\"), \": Knowledge Now\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \": Key Performance Parameter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key System Attribute\"\n }, \"KSA\"), \": Key System Attribute\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lessons Learned\"\n }, \"L2\"), \": Lessons Learned\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics Assessment\"\n }, \"LA\"), \": Logistics Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lot Acceptance Test\"\n }, \"LAT\"), \": Lot Acceptance Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Long Band\"\n }, \"L-band\"), \": Long Band\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"HQ AFOTEC Legal Counsel\"\n }, \"LC\"), \": \", 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\"), \" Legal Counsel\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lower Confidence Bound\"\n }, \"LCB\"), \": Lower Confidence Bound\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Cost\"\n }, \"LCC\"), \": Life Cycle Cost\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Cost Estimate\"\n }, \"LCCE\"), \": Life Cycle Cost Estimate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Management Center\"\n }, \"LCMC\"), \": Life Cycle Management Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Management Plan\"\n }, \"LCMP\"), \": Life Cycle Management Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Risk Management\"\n }, \"LCRM\"), \": Life Cycle Risk Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Launch and Checkout System\"\n }, \"LCS\"), \": Launch and Checkout System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Sustainment Plan\"\n }, \"LCSP\"), \": Life Cycle Sustainment Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Limited Deployment OR Logistics Demonstration\"\n }, \"LD\"), \": Limited Deployment OR Logistics Demonstration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"LAN Data Collector\"\n }, \"LDC\"), \": LAN Data Collector\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lead Developmental Test Organization\"\n }, \"LDTO\"), \": Lead Developmental Test Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Light Emitting Diode\"\n }, \"LED\"), \": Light Emitting Diode\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Low Earth Orbit\"\n }, \"LEO\"), \": Low Earth Orbit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Extension Program\"\n }, \"LEP\"), \": Life Extension Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Limited Fielding Decision\"\n }, \"LFD\"), \": Limited Fielding Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live Fire Test and Evaluation\"\n }, \"LFT&E\"), \": Live Fire Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics Health Assessments\"\n }, \"LHA\"), \": Logistics Health Assessments\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Laser Joint Direct Attack Munition (GBU-56)\"\n }, \"LJDAM\"), \": Laser Joint Direct Attack Munition (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Guided Bomb Unit\"\n }, \"GBU\"), \"-56)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lockheed Martin\"\n }, \"LM\"), \": Lockheed Martin\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics MANPRINT Demonstration\"\n }, \"LMD\"), \": Logistics \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower and Personnel Integration\"\n }, \"MANPRINT\"), \" Demonstration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Mission Data Plan\"\n }, \"LMDP\"), \": Life Cycle Mission Data Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Late Network Entry\"\n }, \"LNE\"), \": Late Network Entry\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Liaison Officers\"\n }, \"LNO\"), \": Liaison Officers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Letter of Offer and Acceptance\"\n }, \"LOA\"), \": Letter of Offer and Acceptance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Level of Repair Analysis\"\n }, \"LORA\"), \": Level of Repair Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Line of Sight\"\n }, \"LOS\"), \": Line of Sight\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Limited Rights\"\n }, \"LR\"), \": Limited Rights\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Long Range Discrimination Radar\"\n }, \"LRDR\"), \": Long Range Discrimination Radar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Low Rate Initial Production\"\n }, \"LRIP\"), \": Low Rate Initial Production\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Long Range Standoff\"\n }, \"LRSO\"), \": Long Range Standoff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics Response Time\"\n }, \"LRT\"), \": Logistics Response Time\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Line-Replaceable Unit\"\n }, \"LRU\"), \": Line-Replaceable Unit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics Support Concept\"\n }, \"LSC\"), \": Logistics Support Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lead Systems Engineer\"\n }, \"LSE\"), \": Lead Systems Engineer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Large Scale Integration OR Lead Systems Integrator\"\n }, \"LSI\"), \": Large Scale Integration OR Lead Systems Integrator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Last Test Event\"\n }, \"LTE\"), \": Last Test Event\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics Test Working Group\"\n }, \"LTWG\"), \": Logistics Test Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Limited User Test\"\n }, \"LUT\"), \": Limited User Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \": Live\\nVirtual\\nand Constructive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \": Modeling and Simulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer\"\n }, \"CO\"), \": Modeling and Simulation Coordination Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Master Air Attack Plan\"\n }, \"MAAP\"), \": Master Air Attack Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Master Air Attack Planning Toolkit\"\n }, \"MAAPTK\"), \": Master Air Attack Planning Toolkit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Assurance Category\"\n }, \"MAC\"), \": Mission Assurance Category\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modular Air Crew Helmet\"\n }, \"MACH\"), \": Modular Air Crew Helmet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multifunction Advanced Data Link\"\n }, \"MADL\"), \": Multifunction Advanced Data Link\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mobility Air Forces-Dynamic Retasking Capability\"\n }, \"MAF-DRC\"), \": Mobility Air Forces-Dynamic Retasking Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mobility Air Force Automated Flight Planning Service\"\n }, \"MAFPS\"), \": Mobility Air Force Automated Flight Planning Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Automated Information System\"\n }, \"MAIS\"), \": Major Automated Information System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \": Major Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Miniature Air Launched Decoy-Jammer\"\n }, \"MALD-J\"), \": Miniature Air Launched Decoy-Jammer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Man Portable Air Defense System\"\n }, \"MANPAD\"), \": Man Portable Air Defense System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower and Personnel Integration\"\n }, \"MANPRINT\"), \": Manpower and Personnel Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modular Analysis and Test Support System\"\n }, \"MAnTSS\"), \": Modular Analysis and Test Support System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Monthly Acquisition Report\"\n }, \"MAR\"), \": Monthly Acquisition Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Maverick\"\n }, \"MAV\"), \": Maverick\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiband Inter/Intra Team Radio\"\n }, \"MBITR\"), \": Multiband Inter/Intra Team Radio\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Based Test Design\"\n }, \"MBTD\"), \": Mission Based Test Design\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Capable\"\n }, \"MC\"), \": Mission Capable\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Critical Functions\"\n }, \"MCF\"), \": Mission Critical Functions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Marine Corps Operational Test and Evaluation Activity\"\n }, \"MCOTEA\"), \": Marine Corps Operational Test and Evaluation Activity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Message Completion Rate\"\n }, \"MCR\"), \": Message Completion Rate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Directive\"\n }, \"MD\"), \": Mission Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone Decision Authority OR Missile Defense Agency\"\n }, \"MDA\"), \": Milestone Decision Authority OR Missile Defense Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Defense Acquisition Program\"\n }, \"MDAP\"), \": Major Defense Acquisition Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Maintenance Data Documentation OR Material Development Decision\"\n }, \"MDD\"), \": Maintenance Data Documentation OR Material Development Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Data File\"\n }, \"MDF\"), \": Mission Data File\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Design Series\"\n }, \"MDS\"), \": Mission Design Series\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mean Down Time\"\n }, \"MDT\"), \": Mean Down Time\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Maintenance Engineering/Sustaining Engineering\"\n }, \"ME/SE\"), \": Maintenance Engineering/Sustaining Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mechanical Subsystems Integrity Plan\"\n }, \"MECSIP\"), \": Mechanical Subsystems Integrity Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Engineering Data Asset Locator System\"\n }, \"MEDALS\"), \": Military Engineering Data Asset Locator System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Essential Functions List\"\n }, \"MEFL\"), \": Mission Essential Functions List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Medium Earth Orbit\"\n }, \"MEO\"), \": Medium Earth Orbit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower Estimate Report\"\n }, \"MER\"), \": Manpower Estimate Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Minimum Essential Subsystems List\"\n }, \"MESL\"), \": Minimum Essential Subsystems List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Equipment Valuation\"\n }, \"MEV\"), \": Military Equipment Valuation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Flight Operations Quality Assurance\"\n }, \"MFOQA\"), \": Military Flight Operations Quality Assurance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Force Program OR Materiel Fielding Plan\"\n }, \"MFP\"), \": Major Force Program OR Materiel Fielding Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum for Record\"\n }, \"MFR\"), \": Memorandum for Record\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multi-Functional Team\"\n }, \"MFT\"), \": Multi-Functional Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Grid Referencing System\"\n }, \"MGRS\"), \": Military Grid Referencing System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military GPS User Equipment Hand Held\"\n }, \"MGUE Inc 2 HH\"), \": Military \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" User Equipment Hand Held\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military GPS User Equipment\"\n }, \"MGUE\"), \": Military \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" User Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modular Handgun System\"\n }, \"MHS\"), \": Modular Handgun System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Megahertz\"\n }, \"MHz\"), \": Megahertz\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Detail (Specification)\"\n }, \"MIL-DTL\"), \":Military Detail (Specification)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Handbook\"\n }, \"MIL-HDBK\"), \":Military Handbook\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Performance (Specification)\"\n }, \"MIL-PRF\"), \":Military Performance (Specification)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Standard\"\n }, \"MIL-STD\"), \":Military Standard\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Materiel Improvement Program OR Military Intelligence Program\"\n }, \"MIP\"), \": Materiel Improvement Program OR Military Intelligence Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Interdepartmental Purchase Request\"\n }, \"MIPR\"), \": Military Interdepartmental Purchase Request\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Material Improvement Program Review Board\"\n }, \"MIPRB\"), \": Material Improvement Program Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiple Levels of Security\"\n }, \"MLS\"), \": Multiple Levels of Security\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions, Missiles, and Target\"\n }, \"MMT\"), \": Munitions\\nMissiles\\nand Target\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Needs Statement\"\n }, \"MNS\"), \": Mission Needs Statement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \": Memorandum of Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Management and Oversight of Acquisition Services Process\"\n }, \"MOASP\"), \": Management and Oversight of Acquisition Services Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \": Measure of Effectiveness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \": Measures of Effectiveness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \": Measure of Performance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Oriented Protective Posture\"\n }, \"MOPP\"), \": Mission Oriented Protective Posture\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \": Mission-Oriented Response Variables\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \": Measure of Suitability OR Military Occupational Specialty\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modular Open Systems Approach\"\n }, \"MOSA\"), \": Modular Open Systems Approach\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \": Multiservice Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Understanding\"\n }, \"MOU\"), \": Memorandum of Understanding\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Profile\"\n }, \"MP\"), \": Mission Profile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower Authorization\"\n }, \"MPA\"), \": Manpower Authorization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Planning Element\"\n }, \"MPE\"), \": Mission Planning Element\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multipart GPS Pulse-per-Second Adapter\"\n }, \"MPGPA\"), \": Multipart \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" Pulse-per-Second Adapter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Master Program Schedule OR Mission Planning System\"\n }, \"MPS\"), \": Master Program Schedule OR Mission Planning System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Methods and Procedures Technical Order\"\n }, \"MPTO\"), \": Methods and Procedures Technical Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manufacturing Readiness Assessment\"\n }, \"MRA\"), \": Manufacturing Readiness Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Requirements Board\"\n }, \"MRB\"), \": Mission Requirements Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Man-Portable Radiological Detection System\"\n }, \"MRDS\"), \": Man-Portable Radiological Detection System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manufacturing Readiness Level\"\n }, \"MRL\"), \": Manufacturing Readiness Level\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Depot Maintenance, Repair, and Overhaul Initiative\"\n }, \"MROi\"), \": Air Force Depot Maintenance\\nRepair\\nand Overhaul Initiative\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions Requirements Process\"\n }, \"MRP\"), \": Munitions Requirements Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Materiel Release Review\"\n }, \"MRR\"), \": Materiel Release Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Maintenance Requirement Review Board\"\n }, \"MRRB\"), \": Maintenance Requirement Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mobility Readiness Spares Package\"\n }, \"MRSP\"), \": Mobility Readiness Spares Package\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Range and Test Facility Base\"\n }, \"MRTFB\"), \": Major Range and Test Facility Base\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \": Milestone\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Materiel Solution Analysis\"\n }, \"MSA\"), \": Materiel Solution Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation Information Analysis Center\"\n }, \"MSIAC\"), \": Modeling and Simulation Information Analysis Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mean Sea Level\"\n }, \"MSL\"), \": Mean Sea Level\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation Support Plan\"\n }, \"MSSP\"), \": Modeling and Simulation Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mean Time Between Essential Function Failures\"\n }, \"MTBEFF\"), \": Mean Time Between Essential Function Failures\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mean Time To Repair\"\n }, \"MTTR\"), \": Mean Time To Repair\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Utility Assessment\"\n }, \"MUA\"), \": Military Utility Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mobile User Objective System\"\n }, \"MUOS\"), \": Mobile User Objective System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \": Measures Workshop\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Airborne Operations Center\"\n }, \"NAOC\"), \": National Airborne Operations Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Air and Space Intelligence Center\"\n }, \"NASIC\"), \": National Air and Space Intelligence Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"North Atlantic Treaty Organization\"\n }, \"NATO\"), \": North Atlantic Treaty Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Navigation Plan Tactical Pilotage Charts\"\n }, \"NAVPLAN TPC\"), \": Navigation Plan Tactical Pilotage Charts\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear, Biological and Chemical\"\n }, \"NBC\"), \": Nuclear\\nBiological and Chemical\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear Command and Control-Extremely Sensitive Information\"\n }, \"NC2-ESI\"), \": Nuclear Command and Control-Extremely Sensitive Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear Command, Control, Communications\"\n }, \"NC3\"), \": Nuclear Command\\nControl\\nCommunications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network-Centric Operations and Warfare\"\n }, \"NCOW\"), \": Network-Centric Operations and Warfare\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network-Centric Operations and Warfare\"\n }, \"NCOW\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \": Net-Centric Operations and Warfare Reference Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Defense Authorization Act\"\n }, \"NDAA\"), \": National Defense Authorization Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network Design Facility\"\n }, \"NDF\"), \": Network Design Facility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Developmental Item\"\n }, \"NDI\"), \": Non-Developmental Item\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Defense Strategy\"\n }, \"NDS\"), \": National Defense Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Environmental Policy Act\"\n }, \"NEPA\"), \": National Environmental Policy Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"New Equipment Training\"\n }, \"NET\"), \": New Equipment Training\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network Risk Assessment\"\n }, \"NetRA\"), \": Network Risk Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network Enabled Weapon\"\n }, \"NEW\"), \": Network Enabled Weapon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Next Generation Geosynchronous Earth Orbit (GEO)\"\n }, \"NGG\"), \": Next Generation Geosynchronous Earth Orbit (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Geosynchronous Earth Orbit\"\n }, \"GEO\"), \")\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Next Generation Polar\"\n }, \"NGP\"), \": Next Generation Polar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Geospatial-Intelligence Agency\"\n }, \"NGA\"), \": National Geospatial-Intelligence Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Guard Bureau\"\n }, \"NGB\"), \": National Guard Bureau\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Next Generation Chemical Detector\"\n }, \"NGCD\"), \": Next Generation Chemical Detector\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Next Generation Diagnostic System\"\n }, \"NGDS\"), \": Next Generation Diagnostic System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Guard and Reserve Equipment Account\"\n }, \"NGREA\"), \": National Guard and Reserve Equipment Account\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Government Standard (commercial)\"\n }, \"NGS\"), \": Non-Government Standard (commercial)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Interest Determination\"\n }, \"NID\"), \": National Interest Determination\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Intelligence Program\"\n }, \"NIP\"), \": National Intelligence Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \": Non-Secure Internet Protocol Router Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Industrial Security Program Operating Manual\"\n }, \"NISPOM\"), \": National Industrial Security Program Operating Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Institute of Standards and Technology\"\n }, \"NIST\"), \": National Institute of Standards and Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Kinetic Counter Electronics\"\n }, \"NKCE\"), \": Non-Kinetic Counter Electronics\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"No or Not Later Than\"\n }, \"NLT\"), \": No or Not Later Than\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network Management\"\n }, \"NM\"), \": Network Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Not Mission Capable\"\n }, \"NMC\"), \": Not Mission Capable\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Military Strategy\"\n }, \"NMS\"), \": National Military Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nonnuclear Munitions Safety Board\"\n }, \"NNMSB\"), \": Nonnuclear Munitions Safety Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Nuclear Security Administration\"\n }, \"NNSA\"), \": National Nuclear Security Administration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"No Operational Utility\"\n }, \"NOU\"), \": No Operational Utility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear Planning and Execution System Modernization\"\n }, \"NPES\"), \": Nuclear Planning and Execution System Modernization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Net-Ready Key Performance Parameter\"\n }, \"NR KPP\"), \": Net-Ready Key Performance Parameter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Recurring Engineering\"\n }, \"NRE\"), \": Non-Recurring Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Reconnaissance Office\"\n }, \"NRO\"), \": National Reconnaissance Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Agency\"\n }, \"NSA\"), \": National Security Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Near Strike Lightning\"\n }, \"NSL\"), \": Near Strike Lightning\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Stock Number\"\n }, \"NSN\"), \": National Stock Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Personnel System\"\n }, \"NSPS\"), \": National Security Personnel System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Space OR National Security Strategy OR National Security System\"\n }, \"NSS\"), \": National Security Space OR National Security Strategy OR National Security System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \": Nevada Test and Training Range\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear Weapons Council\"\n }, \"NWC\"), \": Nuclear Weapons Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear Weapons Related Materiel\"\n }, \"NWRM\"), \": Nuclear Weapons Related Materiel\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operation and Maintenance\"\n }, \"O&M\"), \": Operation and Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operation and Support\"\n }, \"O&S\"), \": Operation and Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \": Operational Assessment OR Operational Availability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Advisory Group (USN/USMC)\"\n }, \"OAG\"), \": Operational Advisory Group (USN/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Marine Corps\"\n }, \"USMC\"), \")\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \": Open-Air Range\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating at Risk List\"\n }, \"OARL\"), \": Operating at Risk List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Aerospace Studies\"\n }, \"OAS\"), \": Office of Aerospace Studies\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office Assistant Secretary of Defense/Network and Information Integration\"\n }, \"OASD/NII\"), \": Office Assistant Secretary of Defense/Network and Information Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Offensive Anti-Surface Weapon\"\n }, \"OASuW\"), \": Offensive Anti-Surface Weapon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Capability\"\n }, \"OC\"), \": Operational Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Original Classification Authority\"\n }, \"OCA\"), \": Original Classification Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Occupational Specialty Code\"\n }, \"OCC\"), \": Occupational Specialty Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Capability Development Document\"\n }, \"OCDD\"), \": Operational Capability Development Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Concept of Employment\"\n }, \"OCE\"), \": Operational Concept of Employment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Collateral Responsibility OR Operational Capability Requirement\"\n }, \"OCR\"), \": Office of Collateral Responsibility OR Operational Capability Requirement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"GPS Next Generation Operational Control System\"\n }, \"OCX\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" Next Generation Operational Control System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Effectiveness OR Operational Environment\"\n }, \"OE\"), \": Operational Effectiveness OR Operational Environment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Original Equipment Manufacturer\"\n }, \"OEM\"), \": Original Equipment Manufacturer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency Evaluation Report\"\n }, \"OER\"), \": Operational Test Agency Evaluation Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Flight Program\"\n }, \"OFP\"), \": Operational Flight Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Flight Software\"\n }, \"OFS\"), \": Operational Flight Software\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Overarching Integrated Product Team\"\n }, \"OIPT\"), \": Overarching Integrated Product Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \": Operating Location\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Management and Budget\"\n }, \"OMB\"), \": Office of Management and Budget\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Outer Mold Line\"\n }, \"OML\"), \": Outer Mold Line\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Mission Summary OR Operational Mode Summary\"\n }, \"OMS\"), \": Operational Mission Summary OR Operational Mode Summary\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Need Date\"\n }, \"OND\"), \": Operational Need Date\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Overhead Persistent Infrared\"\n }, \"OPIR\"), \": Overhead Persistent Infrared\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Plan\"\n }, \"OPLAN\"), \": Operations Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Order\"\n }, \"OPORD\"), \": Operations Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Primary Responsibility\"\n }, \"OPR\"), \": Office of Primary Responsibility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Security\"\n }, \"OPSEC\"), \": Operations Security\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Tempo\"\n }, \"OPTEMPO\"), \": Operational Tempo\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test and Evaluation Force\"\n }, \"OPTEVFOR\"), \": Operational Test and Evaluation Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Requirements Document\"\n }, \"ORD\"), \": Operational Requirements Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Risk Management\"\n }, \"ORM\"), \": Operational Risk Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Suitability\"\n }, \"OS\"), \": Operational Suitability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \": Office of the Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Occupational Safety and Health Administration\"\n }, \"OSHA\"), \": Occupational Safety and Health Administration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Safety, Suitability, and Effectiveness\"\n }, \"OSS&E\"), \": Operational Safety\\nSuitability\\nand Effectiveness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \": Operational Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E: Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \": Operational Test Agency OR Other Transactions Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Over-the-Air Re-key\"\n }, \"OTAR\"), \": Over-the-Air Re-key\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Over Target Baseline\"\n }, \"OTB\"), \": Over Target Baseline\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Army Operational Test Command\"\n }, \"OTC\"), \": United States Army Operational Test Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open Technology Development\"\n }, \"OTD\"), \": Open Technology Development\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Training Infrastructure\"\n }, \"OTI\"), \": Operational Training Infrastructure\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Information Files\"\n }, \"OTIF\"), \": Operational Test Information Files\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Organization\"\n }, \"OTO\"), \": Operational Test Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \": Operational Test Readiness Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Over Target Schedule\"\n }, \"OTS\"), \": Over Target Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility\"\n }, \"OU\"), \": Operational Utility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Assessment\"\n }, \"OUA\"), \": Operational Utility Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \": Operational Utility Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Under Secretary of Defense\"\n }, \"OUSD\"), \": Office of the Under Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational View (or Viewpoint)\"\n }, \"OV\"), \": Operational View (or Viewpoint)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Overseas Workload Program\"\n }, \"OWLP\"), \": Overseas Workload Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Production and Deployment (phase)\"\n }, \"P&D\"), \": Production and Deployment (phase)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Pre-Planned Product Improvement\"\n }, \"P3I\"), \": Pre-Planned Product Improvement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Partnering Arrangement OR Preparing Activity OR Preparing Authority OR Program Authorization ORPublic Affairs\"\n }, \"PA\"), \": Partnering Arrangement OR Preparing Activity OR Preparing Authority OR Program Authorization ORPublic Affairs\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Phased Adaptive Approach\"\n }, \"PAA\"), \": Phased Adaptive Approach\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Action Directive\"\n }, \"PAD\"), \": Program Action Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Pamphlet OR Performance Attributes Matrix\"\n }, \"PAM\"), \": Pamphlet OR Performance Attributes Matrix\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Presidential Aircraft Recapitalization OR Proposal Analysis Report\"\n }, \"PAR\"), \": Presidential Aircraft Recapitalization OR Proposal Analysis Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Personnel Accounting Symbol\"\n }, \"PAS\"), \": Personnel Accounting Symbol\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Production Acceptance Test and Evaluation\"\n }, \"PAT&E\"), \": Production Acceptance Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Acquisition Unit Cost\"\n }, \"PAUC\"), \": Program Acquisition Unit Cost\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"President’s Budget\"\n }, \"PB\"), \": President\\u2019s Budget\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Based Acquisition OR Performance Based Agreement\"\n }, \"PBA\"), \": Performance Based Acquisition OR Performance Based Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Portable Biological Containment Module\"\n }, \"PBCM\"), \": Portable Biological Containment Module\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Based Logistics\"\n }, \"PBL\"), \": Performance Based Logistics\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program/Budget Review\"\n }, \"PBR\"), \": Program/Budget Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Center\"\n }, \"PC\"), \": Product Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Control Chief\"\n }, \"PCC\"), \": Program Control Chief\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \": Procuring Contracting Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Director\"\n }, \"PD\"), \": Program Director\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Data Acquisition\"\n }, \"PDAQ\"), \": Product Data Acquisition\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Decision Memorandum OR Programmed Depot Maintenance\"\n }, \"PDM\"), \": Program Decision Memorandum OR Programmed Depot Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Preliminary Design Review\"\n }, \"PDR\"), \": Preliminary Design Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Element\"\n }, \"PE\"), \": Program Element\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Element Monitor\"\n }, \"PEM\"), \": Program Element Monitor\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \": Program Executive Office / Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Personnel Electrostatic Discharge\"\n }, \"PESD\"), \": Personnel Electrostatic Discharge\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Programmatic Environment, Safety, and Occupational Health Evaluation\"\n }, \"PESHE\"), \": Programmatic Environment\\nSafety\\nand Occupational Health Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Group\"\n }, \"PG\"), \": Product Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procedures, Guidance, and Information\"\n }, \"PGI\"), \": Procedures\\nGuidance\\nand Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Guidance Letter\"\n }, \"PGL\"), \": Program Guidance Letter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Precision Guided Munitions OR Product Group Manager\"\n }, \"PGM\"), \": Precision Guided Munitions OR Product Group Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Packaging, Handling, Storage, and Transportation\"\n }, \"PHS&T\"), \": Packaging\\nHandling\\nStorage\\nand Transportation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Privacy Impact Assessment\"\n }, \"PIA\"), \": Privacy Impact Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Introduction Document\"\n }, \"PID\"), \": Program Introduction Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Personally Identifiable Information\"\n }, \"PII\"), \": Personally Identifiable Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Post-Implementation Review\"\n }, \"PIR\"), \": Post-Implementation Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Persistent Intelligence, Surveillance, and Reconnaissance\"\n }, \"PISR\"), \": Persistent Intelligence\\nSurveillance\\nand Reconnaissance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Platform Information Technology\"\n }, \"PIT\"), \": Platform Information Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Public Law\"\n }, \"PL\"), \": Public Law\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Position Location Information\"\n }, \"PLI\"), \": Position Location Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Lifecycle Management System\"\n }, \"PLMS\"), \": Product Lifecycle Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Position Location Recorder\"\n }, \"PLR\"), \": Position Location Recorder\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \": Program Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multi-Functional Team\"\n }, \"MFT\"), \": Program Management or Multi-Functional Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Management Agreement\"\n }, \"PMA\"), \": Program Management Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Measurement Baseline\"\n }, \"PMB\"), \": Performance Measurement Baseline\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Partially Mission Capable\"\n }, \"PMC\"), \": Partially Mission Capable\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Preventive Maintenance Checks and Services\"\n }, \"PMCS\"), \": Preventive Maintenance Checks and Services\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Management Directive\"\n }, \"PMD\"), \": Program Management Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Management Listing\"\n }, \"PML\"), \": Program Management Listing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Management Office\"\n }, \"PMO\"), \": Program Management Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Management Resource Tools\"\n }, \"PMRT\"), \": Program Management Resource Tools\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager‘s Tool\"\n }, \"PMT\"), \": Program Manager\\u2018s Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Presidential and National Voice Conferencing\"\n }, \"PNVC\"), \": Presidential and National Voice Conferencing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Office OR Project Officer\"\n }, \"PO\"), \": Program Office OR Project Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Plan of Action & Milestones\"\n }, \"POA&M\"), \": Plan of Action & Milestones\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \": Point of Contact\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Office Estimates\"\n }, \"POE\"), \": Program Office Estimates\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \": Program Objective Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Maintenance\"\n }, \"POMx\"), \": Point of Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Probability of Program Success\"\n }, \"PoPS\"), \": Probability of Program Success\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program of Record\"\n }, \"PoR\"), \": Program of Record\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Pre-Operational Support\"\n }, \"POS\"), \": Pre-Operational Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Partial Operational Utility\"\n }, \"POU\"), \": Partial Operational Utility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Planning, Programming, Budgeting, and Execution\"\n }, \"PPBE\"), \": Planning\\nProgramming\\nBudgeting\\nand Execution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Programming Plan\"\n }, \"P-PLAN\"), \": Programming Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Programming Plans\"\n }, \"PPLANS\"), \": Programming Plans\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Protection Plan OR Public-Private Partnership\"\n }, \"PPP\"), \": Program Protection Plan OR Public-Private Partnership\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Pre-Production Qualification Test\"\n }, \"PPQT\"), \": Pre-Production Qualification Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Post-Publication Review\"\n }, \"PPR\"), \": Post-Publication Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Production Qualification Test\"\n }, \"PQT\"), \": Production Qualification Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Risk Assessment\"\n }, \"PRA\"), \": Performance Risk Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Portable Rugged Objected\"\n }, \"PRO\"), \": Portable Rugged Objected\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Production Readiness Review\"\n }, \"PRR\"), \": Production Readiness Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Support Business Case Analysis\"\n }, \"PS-BCA\"), \": Product Support Business Case Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Physical Security Equipment Action Group\"\n }, \"PSEAG\"), \": Physical Security Equipment Action Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Support Integrator\"\n }, \"PSI\"), \": Product Support Integrator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Propulsion Systems Integrity Program\"\n }, \"PSIP\"), \": Propulsion Systems Integrity Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Support Manager\"\n }, \"PSM\"), \": Product Support Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Support Management Plan\"\n }, \"PSMP\"), \": Product Support Management Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Publication Stock Number\"\n }, \"PSN\"), \": Publication Stock Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Support Provider\"\n }, \"PSP\"), \": Product Support Provider\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Preliminary Specification\"\n }, \"PSpec\"), \": Preliminary Specification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Support Review\"\n }, \"PSR\"), \": Program Support Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Protected Tactical Enterprise Services\"\n }, \"PTES\"), \": Protected Tactical Enterprise Services\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Participating Test Organization OR Preliminary Technical Order\"\n }, \"PTO\"), \": Participating Test Organization OR Preliminary Technical Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Protected Tactical SATCOM\"\n }, \"PTS\"), \": Protected Tactical \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Satellite Communications\"\n }, \"SATCOM\"), \"\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Precision Tracking Space System\"\n }, \"PTSS\"), \": Precision Tracking Space System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Project Viewpoint\"\n }, \"PV\"), \": Project Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Pilot Vehicle Interface\"\n }, \"PVI\"), \": Pilot Vehicle Interface\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Work Statement\"\n }, \"PWS\"), \": Performance Work Statement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quadrennial Defense Review\"\n }, \"QDR\"), \": Quadrennial Defense Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quality of Service\"\n }, \"QoS\"), \": Quality of Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Qualification Operational Test and Evaluation\"\n }, \"QOT&E\"), \": Qualification Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quick Reaction Capability\"\n }, \"QRC\"), \": Quick Reaction Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quick Reaction Fund\"\n }, \"QRF\"), \": Quick Reaction Fund\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quick Reference Guide\"\n }, \"QRG\"), \": Quick Reference Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quick Reaction Instrumentation Package\"\n }, \"QRIP\"), \": Quick Reaction Instrumentation Package\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Qualification Test and Evaluation\"\n }, \"QT&E\"), \": Qualification Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Research and Development\"\n }, \"R&D\"), \": Research and Development\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability and Maintainability\"\n }, \"R&M\"), \": Reliability and Maintainability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Test\"\n }, \"R/T\"), \": Request for Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rapid Acquisition Authority OR Required Assets Available\"\n }, \"RAA\"), \": Rapid Acquisition Authority OR Required Assets Available\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radio Detection and Ranging\"\n }, \"RADAR\"), \": Radio Detection and Ranging\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Recorded Aircraft Information\"\n }, \"RAI\"), \": Recorded Aircraft Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \": Risk Assessment Level of Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability, Availability, and Maintainability\"\n }, \"RAM\"), \": Reliability\\nAvailability\\nand Maintainability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability, Availability, and Maintainability\"\n }, \"RAM\"), \"&C: Reliability\\nAvailability\\nMaintainability\\nand Cost\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability, Availability, Maintainability for Pods and Integrated Systems\"\n }, \"RAMPOD\"), \": Reliability\\nAvailability\\nMaintainability for Pods and Integrated Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability, Availability, Maintainability, and Supportability\"\n }, \"RAMS\"), \": Reliability\\nAvailability\\nMaintainability\\nand Supportability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rapid Analysis Processing Instrumentation Deployment System\"\n }, \"RAPIDS\"), \": Rapid Analysis Processing Instrumentation Deployment System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Recommended Changes\"\n }, \"RC\"), \": Recommended Changes\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Regulatory Contracting Approval\"\n }, \"RCA\"), \": Regulatory Contracting Approval\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability Centered Maintenance\"\n }, \"RCM\"), \": Reliability Centered Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Report Control Number\"\n }, \"RCN\"), \": Report Control Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Correlation Table\"\n }, \"RCT\"), \": Requirements Correlation Table\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Restricted Data\"\n }, \"RD\"), \": Restricted Data\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability Development/Growth Test\"\n }, \"RDGT\"), \": Reliability Development/Growth Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radiological Detection System OR Records Disposition Schedule\"\n }, \"RDS\"), \": Radiological Detection System OR Records Disposition Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Research, Development, Test and Evaluation\"\n }, \"RDT&E\"), \": Research\\nDevelopment\\nTest and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability and Maintainability Information System\"\n }, \"REMIS\"), \": Reliability and Maintainability Information System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Resource Enhancement Program\"\n }, \"REP\"), \": Resource Enhancement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radio Frequency\"\n }, \"RF\"), \": Radio Frequency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radio Frequency Identification\"\n }, \"RFID\"), \": Radio Frequency Identification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \": Request for Proposal\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability Growth Curve\"\n }, \"RGC\"), \": Reliability Growth Curve\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Identification: Integration & -Ilities\"\n }, \"RI3\"), \": Risk Identification: Integration & -Ilities\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Remote Reconfigurable Intelligent Instrumentation to Control, Collect, Simulate and Stimulate\"\n }, \"RICS2\"), \": Remote Reconfigurable Intelligent Instrumentation to Control\\nCollect\\nSimulate and Stimulate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radioisotope Identification Detector\"\n }, \"RIID\"), \": Radioisotope Identification Detector\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rotary Launcher Assembly\"\n }, \"RLA\"), \": Rotary Launcher Assembly\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \": Reference Manual OR Risk Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \"&A: Reliability\\nMaintainability and Availability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Management Certification Training\"\n }, \"RMCT\"), \": Requirements Management Certification Training\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Management Division\"\n }, \"RMD\"), \": Requirements Management Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Management Framework\"\n }, \"RMF\"), \": Risk Management Framework\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radar Modernization Program OR Risk Management Plan\"\n }, \"RMP\"), \": Radar Modernization Program OR Risk Management Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rough Order of Magnitude\"\n }, \"ROM\"), \": Rough Order of Magnitude\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Remotely Piloted Aircraft\"\n }, \"RPA\"), \": Remotely Piloted Aircraft\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Real Property Installed Equipment\"\n }, \"RPIE\"), \": Real Property Installed Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"RQ-4B Block 30 Multi-Spectral Intelligence\"\n }, \"RQ-4B Bk 30 MSI\"), \": RQ-4B Block 30 Multi-Spectral Intelligence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rifleman Radio\"\n }, \"RR\"), \": Rifleman Radio\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \": Requirements Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rapid Reaction Fund\"\n }, \"RRF\"), \": Rapid Reaction Fund\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rapid Response Process\"\n }, \"RRP\"), \": Rapid Response Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radiated Susceptibility\"\n }, \"RS\"), \": Radiated Susceptibility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radar Signal Emulator\"\n }, \"RSE\"), \": Radar Signal Emulator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Strategy Review\"\n }, \"RSR\"), \": Requirements Strategy Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Real Time Kill Notification\"\n }, \"RTKN\"), \": Real Time Kill Notification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radio Telephone Operator OR Ready for Transition to Operations ORResponsible Test Organization (now obsolete) OR Range Training Officer\"\n }, \"RTO\"), \": Radio Telephone Operator OR Ready for Transition to Operations ORResponsible Test Organization (now obsolete) OR Range Training Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reduction of Total Ownership Cost\"\n }, \"R-TOC\"), \": Reduction of Total Ownership Cost\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Readiness to Test\"\n }, \"RTT\"), \": Readiness to Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Science and Technology\"\n }, \"S&T\"), \": Science and Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Based Infrared Sys (SBIRS) Survivable and Endurable Evolution\"\n }, \"S2E2\"), \": Space Based Infrared Sys (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Based Infrared System\"\n }, \"SBIRS\"), \") Survivable and Endurable Evolution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assistance OR Situational Awareness OR System Administrator\"\n }, \"SA\"), \": Security Assistance OR Situational Awareness OR System Administrator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Selective Availability Anti-Spoofing Module\"\n }, \"SAASM\"), \": Selective Availability Anti-Spoofing Module\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Service Acquisition Executive\"\n }, \"SAE\"), \": Service Acquisition Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \": Secretary of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/AQ: Assistant Secretary of the Air Force (Acquisition)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/AQX: Deputy Assistant Secretary for Acquisition Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Information Officer\"\n }, \"CIO\"), \" A6: Chief of Warfighting Integration and Chief Information Officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Information Officer\"\n }, \"CIO\"), \")\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Financial Management OR Frequency Modulation OR Functional Manager\"\n }, \"FM\"), \": Assistant Secretary of the Air Force (Financial Management)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fully Mission Capable\"\n }, \"FMC\"), \": Deputy Assistant Secretary (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition System\"\n }, \"DAS\"), \") of the Air Force for Cost and Economics\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/GC: General Counsel of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/GCQ: Deputy General Counsel (Acquisition)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/IE: Assistant Secretary of the Air Force (Installations\\nEnvironment\\nand Logistics\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/IG: Inspector General of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/LL: Assistant Secretary of the Air Force (Legislative Affairs)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/US: Under Secretary of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/XC: Secretary of the Air Force Directorate (Warfighting Integration and Chief Information Officer)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Support Agreement Manager\"\n }, \"SAM\"), \": Support Agreement Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Single Acquisition Management Plan\"\n }, \"SAMP\"), \": Single Acquisition Management Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assistance Organizations\"\n }, \"SAO\"), \": Security Assistance Organizations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \": Security Assessment Plan OR Security Assistance Program OR Special Access Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Access Program Control Office\"\n }, \"SAPCO\"), \": Special Access Program Control Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Report OR Special Access Required OR Synthetic Aperture Radar OR System Assessment Report\"\n }, \"SAR\"), \": Security Assessment Report OR Special Access Required OR Synthetic Aperture Radar OR System Assessment Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Site Activation Task Force\"\n }, \"SATAF\"), \": Site Activation Task Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Satellite Communications\"\n }, \"SATCOM\"), \": Satellite Communications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assistance Technical Order Program\"\n }, \"SATOP\"), \": Security Assistance Technical Order Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Small Business\"\n }, \"SB\"), \": Small Business\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Small Business Innovation Research\"\n }, \"SBIR\"), \": Small Business Innovation Research\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Based Infrared System\"\n }, \"SBIRS\"), \": Space Based Infrared System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Based Infrared System\"\n }, \"SBIRS\"), \" F/O: Space Based Infrared System Follow-on\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Smart Bomb Rack Assembly\"\n }, \"SBRA\"), \": Smart Bomb Rack Assembly\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Based Space Surveillance Follow-On\"\n }, \"SBSS F/O\"), \": Space Based Space Surveillance Follow-On\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Capabilities Document\"\n }, \"SCD\"), \": System Capabilities Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \": Security Classification Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sensitive Compartmented Information\"\n }, \"SCI\"), \": Sensitive Compartmented Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Supply Chain Manager\"\n }, \"SCM\"), \": Supply Chain Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Contracting Official\"\n }, \"SCO\"), \": Senior Contracting Official\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Service Cost Position\"\n }, \"SCP\"), \": Service Cost Position\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Supply Chain Risk Management\"\n }, \"SCRM\"), \": Supply Chain Risk Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Strike Common Weapon Data Link\"\n }, \"SCWDL\"), \": Strike Common Weapon Data Link\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standardization Document\"\n }, \"SD\"), \": Standardization Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Small Diameter Bomb\"\n }, \"SDB\"), \": Small Diameter Bomb\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Development and Demonstration\"\n }, \"SDD\"), \": System Development and Demonstration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Services Designated Official\"\n }, \"SDO\"), \": Services Designated Official\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Design Review\"\n }, \"SDR\"), \": System Design Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \": Safety OR Support Equipment OR Systems Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automatic Test System\"\n }, \"ATS\"), \": Support Equipment/Automatic Test System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Suppression of Enemy Air Defenses\"\n }, \"SEAD\"), \": Suppression of Enemy Air Defenses\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Engineering Assessment Model\"\n }, \"SEAM\"), \": Systems Engineering Assessment Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SECAF\"), \": Secretary of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of Defense\"\n }, \"SECDEF\"), \": Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Software Engineering Institute\"\n }, \"SEI\"), \": Software Engineering Institute\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Spectrum Efficient National Surveillance Radar System\"\n }, \"SENSR\"), \": Spectrum Efficient National Surveillance Radar System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Evaluation Plan OR Systems Engineering Plan\"\n }, \"SEP\"), \": System Evaluation Plan OR Systems Engineering Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Support Equipment Recommendation Data\"\n }, \"SERD\"), \": Support Equipment Recommendation Data\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Executive Service\"\n }, \"SES\"), \": Senior Executive Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Selected Essential Item Stockage for Availability Methodology\"\n }, \"SESAME\"), \": Selected Essential Item Stockage for Availability Methodology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Forces OR Standard Form\"\n }, \"SF\"), \": Security Forces OR Standard Form\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Small Form Fit\"\n }, \"SFF\"), \": Small Form Fit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Functional Review\"\n }, \"SFR\"), \": System Functional Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Information Assurance Official\"\n }, \"SIAO\"), \": Senior Information Assurance Official\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Signals Intelligence\"\n }, \"SIGINT\"), \": Signals Intelligence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Interest Item\"\n }, \"SII\"), \": Special Interest Item\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Serialized Item Management\"\n }, \"SIM\"), \": Serialized Item Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Simulation and Analysis Facility\"\n }, \"SIMAF\"), \": Simulation and Analysis Facility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Simulator Certification\"\n }, \"SIMCERT\"), \": Simulator Certification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Simulator Validation\"\n }, \"SIMVAL\"), \": Simulator Validation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Intelligence Officer\"\n }, \"SIO\"), \": Senior Intelligence Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Single Integrated Operational Plan-Extremely Sensitive Information\"\n }, \"SIOP-ESI\"), \": Single Integrated Operational Plan-Extremely Sensitive Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Identification Profile OR System Information Profile\"\n }, \"SIP\"), \": System Identification Profile OR System Information Profile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Service Intelligence Production Centers\"\n }, \"SIPC\"), \": Service Intelligence Production Centers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secret Internet Protocol Router Network\"\n }, \"SIPRNET\"), \": Secret Internet Protocol Router Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security, Interoperability, Supportability, Sustainability, and Usability\"\n }, \"SISSU\"), \": Security\\nInteroperability\\nSupportability\\nSustainability\\nand Usability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Situational Report\"\n }, \"SITREP\"), \": Situational Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Service Level Agreements\"\n }, \"SLA\"), \": Service Level Agreements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standoff Land Attack Missile Expanded Response\"\n }, \"SLAM-ER\"), \": Standoff Land Attack Missile Expanded Response\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Service Life Extension Program\"\n }, \"SLEP\"), \": Service Life Extension Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sub-Line Item Number\"\n }, \"SLIN\"), \": Sub-Line Item Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Manager OR Service Manager OR Single Manager\"\n }, \"SM\"), \": Security Manager OR Service Manager OR Single Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Science, Mathematics, And Research For Transformation OR System Metrics and Reporting Tool\"\n }, \"SMART\"), \": Science\\nMathematics\\nAnd Research For Transformation OR System Metrics and Reporting Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space and Missile Systems Center\"\n }, \"SMC\"), \": Space and Missile Systems Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Single Manager for Conventional Ammunition\"\n }, \"SMCA\"), \": Single Manager for Conventional Ammunition\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \": Subject Matter Expert\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Soldier-Machine Interface\"\n }, \"SMI\"), \": Soldier-Machine Interface\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Maturity Matrix\"\n }, \"SMM\"), \": System Maturity Matrix\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standardized Operations Center Remotely Piloted Aircraft\"\n }, \"SOC RPA\"), \": Standardized Operations Center Remotely Piloted Aircraft\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Statement of Capabilities\"\n }, \"SOC\"), \": Statement of Capabilities\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Operations Command\"\n }, \"SOCOM\"), \": Special Operations Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Operations Forces\"\n }, \"SOF\"), \": Special Operations Forces\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Statement of Intent\"\n }, \"SOI\"), \": Statement of Intent\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Statement of Objectives\"\n }, \"SOO\"), \": Statement of Objectives\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Operations-Peculiar\"\n }, \"SO-P\"), \": Special Operations-Peculiar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source of Repair\"\n }, \"SOR\"), \": Source of Repair\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source of Repair Assignment\"\n }, \"SORA\"), \": Source of Repair Assignment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source of Repair Assignment Process\"\n }, \"SORAP\"), \": Source of Repair Assignment Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System of Record Notice\"\n }, \"SORN\"), \": System of Record Notice\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Speed of Service OR System of Systems\"\n }, \"SoS\"), \": Speed of Service OR System of Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sufficiency of Operational Test Review OR Sufficiency of Test Report\"\n }, \"SOTR\"), \": Sufficiency of Operational Test Review OR Sufficiency of Test Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Operations Wing OR Statement of Work\"\n }, \"SOW\"), \": Special Operations Wing OR Statement of Work\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Plan OR Special Publication\"\n }, \"SP\"), \": Security Plan OR Special Publication\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Single Point Adjustment\"\n }, \"SPA\"), \": Single Point Adjustment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Director\"\n }, \"SPD\"), \": System Program Director\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Procurement Executive\"\n }, \"SPE\"), \": Senior Procurement Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Strategic Planning Guidance\"\n }, \"SPG\"), \": Strategic Planning Guidance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Manager\"\n }, \"SPM\"), \": System Program Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sustainment Program Master List\"\n }, \"SPML\"), \": Sustainment Program Master List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \": System Program Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Operations Command\"\n }, \"SpOC\"), \": Space Operations Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Planning Team\"\n }, \"SPT\"), \": Systems Planning Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Structured Query Language\"\n }, \"SQL\"), \": Structured Query Language\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Schedule Risk Assessment\"\n }, \"SRA\"), \": Schedule Risk Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety Review Board\"\n }, \"SRB\"), \": Safety Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Software or Systems Requirements Document\"\n }, \"SRD\"), \": Software or Systems Requirements Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Requirements Review OR Systems Readiness Review\"\n }, \"SRR\"), \": System Requirements Review OR Systems Readiness Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Soldier Radio Waveform\"\n }, \"SRW\"), \": Soldier Radio Waveform\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source Selection Authority\"\n }, \"SSA\"), \": Source Selection Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Security Authorization Agreement\"\n }, \"SSAA\"), \": Systems Security Authorization Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Situational Awareness-Environmental Monitoring\"\n }, \"SSAEM\"), \": Space Situational Awareness-Environmental Monitoring\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source Selection Decision\"\n }, \"SSD\"), \": Source Selection Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source Selection Decision Document\"\n }, \"SSDD\"), \": Source Selection Decision Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Security Engineering\"\n }, \"SSE\"), \": Systems Security Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source Selection Evaluation Team\"\n }, \"SSET\"), \": Source Selection Evaluation Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Sustainment Manager\"\n }, \"SSM\"), \": System Sustainment Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Social Security Number\"\n }, \"SSN\"), \": Social Security Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standard Surveillance Operating Manual\"\n }, \"SSOM\"), \": Standard Surveillance Operating Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Strategic Source of Repair\"\n }, \"SSOR\"), \": Strategic Source of Repair\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source Selection Plan OR System Support Package\"\n }, \"SSP\"), \": Source Selection Plan OR System Support Package\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Staff Summary Sheet\"\n }, \"SSS\"), \": Staff Summary Sheet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Security Working Group\"\n }, \"SSWG\"), \": Systems Security Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Threat Analysis OR System Threat Assessment\"\n }, \"STA\"), \": System Threat Analysis OR System Threat Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Threat Assessment Report\"\n }, \"STAR\"), \": System Threat Assessment Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Training and Readiness Command\"\n }, \"STARCOM\"), \": Space Training and Readiness Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Scientific Test and Analysis Techniques\"\n }, \"STAT\"), \": Scientific Test and Analysis Techniques\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standards Viewpoint\"\n }, \"StdV\"), \": Standards Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standard for Exchange of Product\"\n }, \"STEP\"), \": Standard for Exchange of Product\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Technical Implementation Guide\"\n }, \"STIG\"), \": Security Technical Implementation Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Scientific and Technical Information\"\n }, \"STINFO\"), \": Scientific and Technical Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Test Program OR System Training Plan\"\n }, \"STP\"), \": Space Test Program OR System Training Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sea Test Range\"\n }, \"STR\"), \": Sea Test Range\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Strategy-To-Task\"\n }, \"STT\"), \": Strategy-To-Task\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Small Business Technology Transfer\"\n }, \"STTR\"), \": Small Business Technology Transfer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \": System Under Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System View\"\n }, \"SV\"), \": System View\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Survivability, Vulnerability, and Assessment Directorate\"\n }, \"SVAD\"), \": Survivability\\nVulnerability\\nand Assessment Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Services Viewpoint\"\n }, \"SvcV\"), \": Services Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Verification Review\"\n }, \"SVR\"), \": System Verification Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Software Assurance\"\n }, \"SwA\"), \": Software Assurance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Command\"\n }, \"SYSCOM\"), \": Systems Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Integrated Test Team\"\n }, \"T&E ITT\"), \": Test and Evaluation Integrated Test Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \": Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \": Technical Advisor OR Test Area\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Airworthiness Authority\"\n }, \"TAA\"), \": Technical Airworthiness Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Checkout\"\n }, \"TACO\"), \": Test and Checkout\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Air Control Party\"\n }, \"TACP\"), \": Tactical Air Control Party\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Air Control Party\"\n }, \"TACP\"), \"-M: Tactical Air Control Party-Modernization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Automated Security System\"\n }, \"TASS\"), \": Tactical Automated Security System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"To Be Determined\"\n }, \"TBD\"), \": To Be Determined\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"TRADOC Capabilities Manager-Tactical Radios\"\n }, \"TCM-TR\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Training and Doctrine Command (US Army)\"\n }, \"TRADOC\"), \" Capabilities Manager-Tactical Radios\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessment\"\n }, \"TCRA\"), \": test capability readiness assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessments\"\n }, \"TCRAs\"), \": test capability readiness assessments\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Total Contract Training\"\n }, \"TCT\"), \": Total Contract Training\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Time Compliance Technical Order\"\n }, \"TCTO\"), \": Time Compliance Technical Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \": Test Director OR Technical Director OR Technology Development OR Technology Director\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"&E: Tactics Development and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \": Test Design Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Data Package\"\n }, \"TDP\"), \": Technical Data Package\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Requirement\"\n }, \"TDR\"), \": Test Design Requirement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Development Strategy\"\n }, \"TDS\"), \": Technology Development Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Data Scoring Board\"\n }, \"TDSB\"), \": Test Data Scoring Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Temporary Duty\"\n }, \"TDY\"), \": Temporary Duty\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \": Technical Editor OR Test Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Text Element Identifiers\"\n }, \"TEI\"), \": Text Element Identifiers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \": Test and Evaluation Master Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Transient Electromagnetic Pulse Surveillance Technology\"\n }, \"TEMPEST\"), \": Transient Electromagnetic Pulse Surveillance Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Executive Officers\"\n }, \"TEO\"), \": Technology Executive Officers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Strategy\"\n }, \"TES\"), \": Test and Evaluation Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Total Force Integration\"\n }, \"TFI\"), \": Total Force Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Investment Planning and Programming\"\n }, \"TIPP\"), \": Test Investment Planning and Programming\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Integrated Product Team\"\n }, \"TIPT\"), \": Test Integrated Product Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Incident Report\"\n }, \"TIR\"), \": Test Incident Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Information Sheet\"\n }, \"TIS\"), \": Test Information Sheet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tailored Information Support Plan\"\n }, \"TISP\"), \": Tailored Information Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tail Kit Assembly\"\n }, \"TKA\"), \": Tail Kit Assembly\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Target Location, Designation, and Hand-Off System\"\n }, \"TLDHS\"), \": Target Location\\nDesignation\\nand Hand-Off System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Target Location Error\"\n }, \"TLE\"), \": Target Location Error\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Manual OR Telemetry OR Test Manager\"\n }, \"TM\"), \": Technical Manual OR Telemetry OR Test Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Manual Contract Requirement\"\n }, \"TMCR\"), \": Technical Manual Contract Requirement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Measurement Diagnostic Equipment\"\n }, \"TMDE\"), \": Test Measurement Diagnostic Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Theater Medical Information Program-Joint\"\n }, \"TMIPJ\"), \": Theater Medical Information Program-Joint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Triple Missile Launcher Adapter\"\n }, \"TMLA\"), \": Triple Missile Launcher Adapter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Maturation & Risk Reduction (phase)\"\n }, \"TMRR\"), \": Technology Maturation & Risk Reduction (phase)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Manual Specifications and Standards\"\n }, \"TMSS\"), \": Technical Manual Specifications and Standards\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Task Management Tool\"\n }, \"TMT\"), \": Task Management Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Total Not Mission Capable-Maintenance\"\n }, \"TNMCM\"), \": Total Not Mission Capable-Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Total Not Mission Capable-Supply\"\n }, \"TNMCS\"), \": Total Not Mission Capable-Supply\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \": Tasking Order OR Technical Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Total Obligation Authority\"\n }, \"TOA\"), \": Total Obligation Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Order Advisory Council\"\n }, \"TOAC\"), \": Technical Order Advisory Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"\n }, \"TOC\"), \": Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Order Distribution Office\"\n }, \"TODO\"), \": Technical Order Distribution Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Order Management Agency\"\n }, \"TOMA\"), \": Technical Order Management Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Program Case File\"\n }, \"TPCF\"), \": Test Program Case File\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \": Technical Performance Measure OR Test Program Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Protection Plan\"\n }, \"TPP\"), \": Technology Protection Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Program Set\"\n }, \"TPS\"), \": Test Program Set\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Training Planning Team\"\n }, \"TPT\"), \": Training Planning Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Plan Working Group\"\n }, \"TPWG\"), \": Test Plan Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Review\"\n }, \"TR\"), \": Technical Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Readiness Assessment\"\n }, \"TRA\"), \": Technology Readiness Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Training and Doctrine Command (US Army)\"\n }, \"TRADOC\"), \": Training and Doctrine Command (US Army)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Review Board\"\n }, \"TRB\"), \": Technical Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Requirements Document\"\n }, \"TRD\"), \": Technical Requirements Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Readiness Level\"\n }, \"TRL\"), \": Technology Readiness Level\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \": Technology Reference Model OR Test Resource Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Management Center\"\n }, \"TRMC\"), \": Test Resource Management Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \": Test Resource Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \": Test Readiness Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Squadron OR Top Secret\"\n }, \"TS\"), \": Test Squadron OR Top Secret\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Trusted Systems & Networks\"\n }, \"TSN\"), \": Trusted Systems & Networks\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Support Plan OR Transfer Support Plan OR Transition Support Plan\"\n }, \"TSP\"), \": Test Support Plan OR Transfer Support Plan OR Transition Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Squadron OR Top Secret\"\n }, \"TS\"), \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Precision Guided Munitions OR Product Group Manager\"\n }, \"PGM\"), \": Training System Product Group Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Time / Space / Position Information\"\n }, \"TSPI\"), \": Time / Space / Position Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Training System Requirements Analysis\"\n }, \"TSRA\"), \": Training System Requirements Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Threat Systems Working Group\"\n }, \"TSWG\"), \": Threat Systems Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"The Technology Cooperation Program\"\n }, \"TTCP\"), \": The Technology Cooperation Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactics, Techniques, and Procedures OR Technology Transition Plan\"\n }, \"TTP\"), \": Tactics\\nTechniques\\nand Procedures OR Technology Transition Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical View\"\n }, \"TV\"), \": Technical View\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Wing\"\n }, \"TW\"), \": Test Wing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Universal Armament\"\n }, \"UAI\"), \": Universal Armament\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unmanned Aerial Systems\"\n }, \"UAS\"), \": Unmanned Aerial Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unmanned Aerial Vehicle\"\n }, \"UAV\"), \": Unmanned Aerial Vehicle\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unified Capabilities\"\n }, \"UC\"), \": Unified Capabilities\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Undefinitized Contract Action\"\n }, \"UCA\"), \": Undefinitized Contract Action\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unified Combatant Commander\"\n }, \"UCC\"), \": Unified Combatant Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ultra-High Frequency\"\n }, \"UHF\"), \": Ultra-High Frequency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unique Identification number\"\n }, \"UID\"), \": Unique Identification number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unfavorable Information File\"\n }, \"UIF\"), \": Unfavorable Information File\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unique Item Identifier\"\n }, \"UII\"), \": Unique Item Identifier\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Uniform Integrated Protection Ensemble\"\n }, \"UIPE\"), \": Uniform Integrated Protection Ensemble\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Universal Joint Task List\"\n }, \"UJTL\"), \": Universal Joint Task List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Underwater Locator Beacon\"\n }, \"ULB\"), \": Underwater Locator Beacon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unliquidated Obligation\"\n }, \"ULO\"), \": Unliquidated Obligation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Urgent Operational Need\"\n }, \"UON\"), \": Urgent Operational Need\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"US Operational Test Team\"\n }, \"UOTT\"), \": US Operational Test Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unified Platform\"\n }, \"UP\"), \": Unified Platform\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"User Representative Agency\"\n }, \"URA\"), \": User Representative Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Uniform Resource Locator\"\n }, \"URL\"), \": Uniform Resource Locator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unit Reference Number\"\n }, \"URN\"), \": Unit Reference Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \": United States Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force Warfare Center\"\n }, \"USAFWC\"), \": United States Air Force Warfare Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Universal Serial Bus\"\n }, \"USB\"), \": Universal Serial Bus\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Code\"\n }, \"USC\"), \": United States Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \": Undersecretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Under Secretary of the Air Force\"\n }, \"USecAF\"), \": Under Secretary of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Marine Corps\"\n }, \"USMC\"), \": United States Marine Corps\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Space Force\"\n }, \"USSF\"), \": United States Space Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"U.S. Special Operations Command\"\n }, \"USSOCOM\"), \": U.S. Special Operations Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Coordinated Universal Time\"\n }, \"UTC\"), \": Coordinated Universal Time\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Utah Test and Training Range\"\n }, \"UTTR\"), \": Utah Test and Training Range\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \": Verification and Validation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Chairman of the Joint Chiefs of Staff\"\n }, \"VCJCS\"), \": Vice Chairman of the Joint Chiefs of Staff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Chief of Staff of the United States Air Force\"\n }, \"VCSAF\"), \": Vice Chief of Staff of the United States Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Chief of Space Operations\"\n }, \"VCSO\"), \": Vice Chief of Space Operations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Value Engineering\"\n }, \"VE\"), \": Value Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Value Engineering Change Proposal\"\n }, \"VECP\"), \": Value Engineering Change Proposal\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Value Engineering Proposal\"\n }, \"VEP\"), \": Value Engineering Proposal\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Very High Frequency\"\n }, \"VHF\"), \": Very High Frequency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Documentation\"\n }, \"VIDOC\"), \": Visual Information Documentation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Manager\"\n }, \"VIM\"), \": Visual Information Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Meteorological Conditions\"\n }, \"VMC\"), \": Visual Meteorological Conditions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vulnerable to Move List\"\n }, \"VML\"), \": Vulnerable to Move List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vulnerability Management Process\"\n }, \"VMP\"), \": Vulnerability Management Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Validated Online Lifecycle Threat\"\n }, \"VOLT\"), \": Validated Online Lifecycle Threat\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Virtual Prime Vendor\"\n }, \"VPV\"), \": Virtual Prime Vendor\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification Status Page\"\n }, \"VSP\"), \": Verification Status Page\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Virtual System Threat Assessment Report\"\n }, \"VSTAR\"), \": Virtual System Threat Assessment Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Video Teleconference\"\n }, \"VTC\"), \": Video Teleconference\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \": Verification\\nValidation and Accreditation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Wide Area Surveillance\"\n }, \"WAS\"), \": Wide Area Surveillance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Wide Area Workflow\"\n }, \"WAWF\"), \": Wide Area Workflow\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Work Breakdown Schedule\"\n }, \"WBS\"), \": Work Breakdown Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Working Capital Fund\"\n }, \"WCF\"), \": Working Capital Fund\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Working\\x1ELevel Integrated Product Team\"\n }, \"WIPT\"), \": Working\\x1ELevel Integrated Product Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Watch Item Tracking\"\n }, \"WIT\"), \": Watch Item Tracking\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Warfighting Mission Area\"\n }, \"WMA\"), \": Warfighting Mission Area\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"weapons of mass destruction\"\n }, \"WMD\"), \": weapons of mass destruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Warfighter Rapid Acquisition Process\"\n }, \"WRAP\"), \": Warfighter Rapid Acquisition Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapons Storage and Security System Service Life Extension Program\"\n }, \"WS3 SLEP\"), \": Weapons Storage and Security System Service Life Extension Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapon System Evaluation Program\"\n }, \"WSEP\"), \": Weapon System Evaluation Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapon System Enterprise Reviews\"\n }, \"WSER\"), \": Weapon System Enterprise Reviews\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weather Satellite Follow-on Electro-Optical /Infra-Red\"\n }, \"WSF-EO/IR\"), \": Weather Satellite Follow-on Electro-Optical /Infra-Red\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weather Satellite Follow-on Microwave\"\n }, \"WSF-M\"), \": Weather Satellite Follow-on Microwave\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapon System Integration OR Weapon System Integrity\"\n }, \"WSI\"), \": Weapon System Integration OR Weapon System Integrity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapon System Integrity Guide\"\n }, \"WSIG\"), \": Weapon System Integrity Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapon System Integrity Program\"\n }, \"WSIP\"), \": Weapon System Integrity Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"White Sands Missile Range\"\n }, \"WSMR\"), \": White Sands Missile Range\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapons System Support Program\"\n }, \"WSSP\"), \": Weapons System Support Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weather\"\n }, \"WX\"), \": Weather\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Extended Data Rate\"\n }, \"XDR\"), \": Extended Data Rate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Year to Date\"\n }, \"YTD\"), \": Year to Date\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"acronyms.md"},"frontmatter":{"metaTitle":"Acronyms","metaDescription":"Acronyms"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"3c246e82-b17b-5afa-aacd-40f5e182c186"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"componentChunkName":"component---src-templates-docs-js","path":"/acronyms","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"3c246e82-b17b-5afa-aacd-40f5e182c186","title":"Acronyms","slug":"/acronyms"},"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\": \"Acronyms\",\n \"metaTitle\": \"Acronyms\",\n \"metaDescription\": \"Acronyms\"\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, \"If you're just searching for the meaning of an ancroym, here's the place.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"2-Letter\"\n }, \"2Ltr\"), \": 2-Letter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block\"\n }, \"Blk\"), \": Block\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \": Detachment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standardization and Evaluation\"\n }, \"Stan/Eval\"), \": Standardization and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Three Dimensional Expeditionary Long Range Radar\"\n }, \"3DELRR\"), \": Three Dimensional Expeditionary Long Range Radar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Third Party Source\"\n }, \"3PS\"), \": Third Party Source\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advisory and Assistance Services\"\n }, \"AAS\"), \": Advisory and Assistance Services\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force and Army Anti-Jam Modem\"\n }, \"A3M\"), \": Air Force and Army Anti-Jam Modem\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \": Adversarial Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Aircraft Availability Improvement Program\"\n }, \"AAIP\"), \": Aircraft Availability Improvement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"After-Action Review / Report\"\n }, \"AAR\"), \": After-Action Review / Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Anti-Radiation Guided Missile\"\n }, \"AARGM\"), \": Advanced Anti-Radiation Guided Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air-to-air Range Infrastructure\"\n }, \"AARI\"), \": Air-to-air Range Infrastructure\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Airborne Strategic Deterrence\"\n }, \"ABSD\"), \": Airborne Strategic Deterrence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Alternating Current\"\n }, \"AC\"), \": Alternating Current\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Category\"\n }, \"ACAT\"), \": Acquisition Category\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Combat Command\"\n }, \"ACC\"), \": Air Combat Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Alternative Compensatory Control Measure\"\n }, \"ACCM\"), \": Alternative Compensatory Control Measure\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Center of Excellence\"\n }, \"ACE\"), \": Acquisition Center of Excellence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automated Civil Engineer System\"\n }, \"ACES\"), \": Automated Civil Engineer System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force C4I Program Assessment Tool\"\n }, \"ACPAT\"), \": Air Force \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Communications, Computers, and Intelligence\"\n }, \"C4I\"), \" Program Assessment Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automated Computer Program Identification Number System\"\n }, \"ACPINS\"), \": Automated Computer Program Identification Number System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Chief Process Office\"\n }, \"ACPO\"), \": Acquisition Chief Process Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Concept Technology Demonstration\"\n }, \"ACTD\"), \": Advanced Concept Technology Demonstration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Actual Cost Work Performed\"\n }, \"ACWP\"), \": Actual Cost Work Performed\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Decision Memorandum\"\n }, \"ADM\"), \": Acquisition Decision Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Distributed Simulation\"\n }, \"ADS\"), \": Advanced Distributed Simulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Army Evaluation Center\"\n }, \"AEC\"), \": United States Army Evaluation Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advance Engineering Change Order\"\n }, \"AECO\"), \": Advance Engineering Change Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Entry Control System OR AFOTEC Electronic Coordination System\"\n }, \"AECS\"), \": Advanced Entry Control System OR \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Electronic Coordination System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air and Space Expeditionary Force\"\n }, \"AEF\"), \": Air and Space Expeditionary Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Extremely High Frequency\"\n }, \"AEHF\"), \": Advanced Extremely High Frequency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Accrued Expenditures Paid\"\n }, \"AEP\"), \": Accrued Expenditures Paid\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advance Engineering Supplemental Order\"\n }, \"AESO\"), \": Advance Engineering Supplemental Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Education and Training Command\"\n }, \"AETC\"), \": Air Education and Training Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Evaluation Task Force\"\n }, \"AETF\"), \": Army Evaluation Task Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Accrued Expenditures Unpaid\"\n }, \"AEU\"), \": Accrued Expenditures Unpaid\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Global Cyberspace Integration Center\"\n }, \"AF GCIC\"), \": Air Force Global Cyberspace Integration Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Management and Oversight of Acquisition Services Process\"\n }, \"AFMOASP\"), \": Air Force Management and Oversight of Acquisition Services Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \": (US) Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A10: Assistant Chief of Staff for Strategic Deterrence and Nuclear Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A2: Deputy Chief of Staff\\nIntelligence\\nSurveillance and Reconnaissance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A3/5: Deputy Chief of Staff\\nOperations\\nPlans\\nand Requirements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A4/7: Deputy Chief of Staff\\nLogistics\\nInstallations\\nand Mission Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A5/8: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"\\nStrategic Plans and Programs\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A5R: Air Force Requirements Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A6: Chief of Warfighting Integration and Chief Information Officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Information Officer\"\n }, \"CIO\"), \")\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/A8: Headquarters\\nAir Force Strategic Plans and Programs\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \": Chief of Staff\\nUnited States Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Commander OR Capability Viewpoint\"\n }, \"CV\"), \": Vice Chief of Staff\\nUnited States Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \": Air Force Chief of Safety\"), mdx(\"p\", null, \"\", 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\"), \": Headquarters Air Force Test and Evaluation Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Acquisition Executive\"\n }, \"AFAE\"), \": Air Force Acquisition Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Agency for Modeling and Simulation\"\n }, \"AFAMS\"), \": Air Force Agency for Modeling and Simulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Base\"\n }, \"AFB\"), \": Air Force Base\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Command & Control Integration Center\"\n }, \"AFC2IC\"), \": Air Force Command & Control Integration Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Command and Control and Intelligence, Surveillance, and Reconnaissance Center (disestablished)\"\n }, \"AFC2ISRC\"), \": Air Force Command and Control and Intelligence\\nSurveillance\\nand Reconnaissance Center (disestablished)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Communications Agency\"\n }, \"AFCA\"), \": Air Force Communications Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Cost Analysis Agency\"\n }, \"AFCAA\"), \": Air Force Cost Analysis Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Certification and Accreditation Program\"\n }, \"AFCAP\"), \": Air Force Certification and Accreditation Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Capabilities Document\"\n }, \"AFCD\"), \": Air Force Capabilities Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Civil Engineer Center\"\n }, \"AFCEC\"), \": Air Force Civil Engineer Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Civil Engineer Support Agency\"\n }, \"AFCESA\"), \": Air Force Civil Engineer Support Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Doctrine Document\"\n }, \"AFDD\"), \": Air Force Doctrine Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Departmental Publishing Office\"\n }, \"AFDPO\"), \": Air Force Departmental Publishing Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Economic Analysis OR Electronic Attack OR Evolutionary Acquisition OR Executing Authority\"\n }, \"EA\"), \": Air Force Enterprise Architecture\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Element of Expense\"\n }, \"AFEE\"), \": Air Force Element of Expense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Electronic Warfare Simulator\"\n }, \"AFEWES\"), \": Air Force Electronic Warfare Simulator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Federal Acquisition Regulation Supplement\"\n }, \"AFFARS\"), \": Air Force Federal Acquisition Regulation Supplement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Frequency Management Agency\"\n }, \"AFFMA\"), \": Air Force Frequency Management Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Gatekeeper\"\n }, \"AFGK\"), \": Air Force Gatekeeper\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Global Logistics Support Center\"\n }, \"AFGLSC\"), \": Air Force Global Logistics Support Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Global Strike Command\"\n }, \"AFGSC\"), \": Air Force Global Strike Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \": Air Force Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Integrated Collaborative Environment\"\n }, \"AFICE\"), \": Air Force Integrated Collaborative Environment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Information Operations Center\"\n }, \"AFIOC\"), \": Air Force Information Operations Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Integrated Personnel and Pay System\"\n }, \"AFIPPS\"), \": Air Force Integrated Personnel and Pay System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Institute of Technology\"\n }, \"AFIT\"), \": Air Force Institute of Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Information Warfare Center (disestablished)\"\n }, \"AFIWC\"), \": Air Force Information Warfare Center (disestablished)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Joint Test Program Office\"\n }, \"AFJO\"), \": Air Force Joint Test Program Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Knowledge Now\"\n }, \"AFKN\"), \": Air Force Knowledge Now\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Lessons Learned Program\"\n }, \"AFL2P\"), \": Air Force Lessons Learned Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Life Cycle Management Center\"\n }, \"AFLCMC\"), \": Air Force Life Cycle Management Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Lesson Issue Resolution Program\"\n }, \"AFLIRP\"), \": Air Force Lesson Issue Resolution Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \": Air Force Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Material Command\"\n }, \"AFMC\"), \": Air Force Material Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Mission Directive\"\n }, \"AFMD\"), \": Air Force Mission Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Metrology and Calibration\"\n }, \"AFMETCAL\"), \": Air Force Metrology and Calibration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Modeling and Simulation Resource Repository\"\n }, \"AFMSRR\"), \": Air Force Modeling and Simulation Resource Repository\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Network\"\n }, \"AFNET\"), \": Air Force Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Network Integration Center\"\n }, \"AFNIC\"), \": Air Force Network Integration Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Nuclear Security Administration\"\n }, \"NNSA\"), \": Air Force-National Nuclear Security Administration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Nuclear Weapons Center\"\n }, \"AFNWC\"), \": Air Force Nuclear Weapons Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Occupational and Environmental Safety, Fire Protection, and Health OR Air Force Office of Safety and Health\"\n }, \"AFOSH\"), \": Air Force Occupational and Environmental Safety\\nFire Protection\\nand Health OR Air Force Office of Safety and Health\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Office of Special Investigations\"\n }, \"AFOSI\"), \": Air Force Office of Special Investigations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \": Air Force Operational Test and Evaluation Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-1: Manpower and Personnel Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-1T: Training Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-1W: Manpower and Personnel (Operations) Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-2/9: Intelligence\\nAnalyses\\nand Assessments Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-2N: Intelligence Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3: Operations Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3C: Cyber Strategic Evaluation Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3E: Operations Mission Support Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3F: Test Operations Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3I: Cyberspace Test Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3O: Test Design Operations Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3Z: Special Access Programs Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-4/7: Installations and Mission Support Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-4F: Logistics and Facilities Management Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-5/8: Plans and Programs Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-5R: Test Infrastructure Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-6: Communications and Information Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-6O: Cyber Operations Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-6X: Plans and Resources Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-6Z: Special Access Programs Information Technology Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-7K: Contracting Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-7R: Financial Resources Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-8P: Programming Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-8R: Long Range Investments Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-8X: Strategic Plans and Policy Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-9A: Analysis and Assessments Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-9I: Analysis Foundation and Integration Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-9X: Methods and Tools Division\"), 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\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \": Technical Advisor\"), 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\": \"Commander OR Critical Component\"\n }, \"CC\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/CCE: Executive Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/CCJ: Graphics\"), 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\": \"Command Control Points\"\n }, \"CCP\"), \": Protocol\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/CCS: Secretary\"), 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\": \"Commander’s Action Group Office Symbol\"\n }, \"CCX\"), \": Commander\\u2019s Action Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/CEM: Chief Enlisted Manager\"), 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\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \": Command Staff\"), 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\": \"Vice Commander OR Capability Viewpoint\"\n }, \"CV\"), \": Vice Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/DS: Director of Staff\"), 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\": \"Executive Director\"\n }, \"ED\"), \": Executive Director\"), 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\": \"HQ AFOTEC History Office\"\n }, \"HO\"), \": History Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/IGI: Inspector General (Inspections)\"), 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\": \"Information Protection OR Initial Point OR Intellectual Property OR Internet Protocol\"\n }, \"IP\"), \": Information Protection\"), 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\": \"HQ AFOTEC Legal Counsel\"\n }, \"LC\"), \": Legal Council\"), 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\": \"Partnering Arrangement OR Preparing Activity OR Preparing Authority OR Program Authorization ORPublic Affairs\"\n }, \"PA\"), \": Public Affairs\"), 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\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \": Safety\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Instruction\"\n }, \"AFOTECI\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Pamphlet\"\n }, \"AFOTECPAM\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Pamphlet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Tactics, Techniques, and Procedures\"\n }, \"AFOTTP\"), \": Air Force Operational Tactics\\nTechniques\\nand Procedures\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Pamphlet\"\n }, \"AFPAM\"), \": Air Force Pamphlet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Policy Directive\"\n }, \"AFPD\"), \": Air Force Policy Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Program Executive Officer/Combat and Mission Support\"\n }, \"AFPEO/CM\"), \": Air Force Program Executive Officer/Combat and Mission Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Review Board\"\n }, \"AFRB\"), \": Air Force Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Reserve Command\"\n }, \"AFRC\"), \": Air Force Reserve Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Information Management System Records Disposition Schedule\"\n }, \"AFRIMS RDS\"), \": Air Force Information Management System Records Disposition Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Records Information Management System\"\n }, \"AFRIMS\"), \": Air Force Records Information Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Research Laboratory\"\n }, \"AFRL\"), \": Air Force Research Laboratory\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Requirements Oversight Council\"\n }, \"AFROC\"), \": Air Force Requirements Oversight Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Requirements for Operational Capabilities Council\"\n }, \"AFROCC\"), \": Air Force Requirements for Operational Capabilities Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Requirements Oversight Council Memorandum\"\n }, \"AFROCM\"), \": Air Force Requirements Oversight Council Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Requirements Review Group\"\n }, \"AFRRG\"), \": Air Force Requirements Review Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Specialty Code\"\n }, \"AFSC\"), \": Air Force Specialty Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force SEEK EAGLE Office\"\n }, \"AFSEO\"), \": Air Force SEEK EAGLE Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Security Forces Center\"\n }, \"AFSFC\"), \": Air Force Security Forces Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force System Interoperability Testing\"\n }, \"AFSIT\"), \": Air Force System Interoperability Testing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Special Operations Command\"\n }, \"AFSOC\"), \": Air Force Special Operations Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Space Command\"\n }, \"AFSPC\"), \": Air Force Space Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Systems Security Instruction\"\n }, \"AFSSI\"), \": Air Force Systems Security Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Test Center\"\n }, \"AFTC\"), \": Air Force Test Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Above Ground Level\"\n }, \"AGL\"), \": Above Ground Level\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Ground Missile\"\n }, \"AGM\"), \": Air Ground Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Active Guard and Reserve\"\n }, \"AGR\"), \": Active Guard and Reserve\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \": Air Intercept Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \"-120 Adv \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AIM-120C Advanced Electronic Protection Improvement Program\"\n }, \"EPIP\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \"-120C Advanced Electronic Protection Improvement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \" 120D \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Identification Profile OR System Information Profile\"\n }, \"SIP\"), \"-3: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \"-120D System Improvement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Aircraft Information Program\"\n }, \"AIP\"), \": Aircraft Information Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Information Repository\"\n }, \"AIR\"), \": Acquisition Information Repository\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automated Information Systems\"\n }, \"AIS\"), \": Automated Information Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Airborne Intelligence, Surveillance, and Reconnaissance\"\n }, \"AISR\"), \": Airborne Intelligence\\nSurveillance\\nand Reconnaissance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automatic Identification Technology\"\n }, \"AIT\"), \": Automatic Identification Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Logistics Center\"\n }, \"ALC\"), \": Air Logistics Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Launched Cruise Missile\"\n }, \"ALCM\"), \": Air Launched Cruise Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Airborne Launch Control System Replacement\"\n }, \"ALCS-R\"), \": Airborne Launch Control System Replacement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Administrative and Logistics Delay\"\n }, \"ALDT\"), \": Administrative and Logistics Delay\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Autonomic Logistics Information System (F-35)\"\n }, \"ALIS\"), \": Autonomic Logistics Information System (F-35)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Aerospace Maintenance and Regeneration Group\"\n }, \"AMARG\"), \": Aerospace Maintenance and Regeneration Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Mission Applications Suite\"\n }, \"AMAS\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Mission Applications Suite\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Mobility Command\"\n }, \"AMC\"), \": Air Mobility Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Alternate Mission Equipment\"\n }, \"AME\"), \": Alternate Mission Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Master List\"\n }, \"AML\"), \": Acquisition Master List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"C-130 Avionics Modernization Program\"\n }, \"AMP\"), \": C-130 Avionics Modernization Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Materiel Systems Analysis Activity\"\n }, \"AMSAA\"), \": Army Materiel Systems Analysis Activity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Navy/Portable Radio Communication\"\n }, \"AN/PRC\"), \": Army Navy/Portable Radio Communication\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air National Guard\"\n }, \"ANG\"), \": Air National Guard\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \": Area of Operations or Authorizing Official or Action Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Availability\"\n }, \"Ao\"), \": Operational Availability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \": Analysis of Alternatives\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Operations Center Weapon System\"\n }, \"AOC WS\"), \": Air Operations Center Weapon System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Assessment of Operational Test Readiness\"\n }, \"AOTR\"), \": Assessment of Operational Test Readiness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Additional Performance Attribute\"\n }, \"APA\"), \": Additional Performance Attribute\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Process Architecture Team\"\n }, \"APAT\"), \": Acquisition Process Architecture Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Program Baseline\"\n }, \"APB\"), \": Acquisition Program Baseline\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Professional Development Program\"\n }, \"APDP\"), \": Acquisition Professional Development Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Precision Kill Weapon System\"\n }, \"APKWS\"), \": Advanced Precision Kill Weapon System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Process Model\"\n }, \"APM\"), \": Acquisition Process Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Program Master List\"\n }, \"APML\"), \": Acquisition Program Master List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Annual Planning and Programming Guidance\"\n }, \"APPG\"), \": Annual Planning and Programming Guidance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Accountable Property Systems of Record\"\n }, \"APSR\"), \": Accountable Property Systems of Record\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Pilot Training\"\n }, \"APT\"), \": Advanced Pilot Training\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Average Unit Procurement Cost\"\n }, \"APUC\"), \": Average Unit Procurement Cost\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis and Reporting Toolset OR Army Regulation\"\n }, \"AR\"), \": Analysis and Reporting Toolset OR Army Regulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Radiation Missile\"\n }, \"ARM\"), \": Anti-Radiation Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air-Launched Rapid Response Weapon\"\n }, \"ARRW\"), \": Air-Launched Rapid Response Weapon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \": Adaptive-Relevant Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Radar Threat System\"\n }, \"ARTS\"), \": Advanced Radar Threat System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition and Sustainment Tool Kit\"\n }, \"AS Tool Kit\"), \": Acquisition and Sustainment Tool Kit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Strategy\"\n }, \"AS\"), \": Acquisition Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Situational Awareness Countermeasures System\"\n }, \"ASACMS\"), \": Advanced Situational Awareness Countermeasures System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Application Software Assurance Center of Excellence\"\n }, \"ASACoE\"), \": Application Software Assurance Center of Excellence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Assistant Secretary of the Air Force\"\n }, \"ASAF\"), \": Assistant Secretary of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Strategy Development OR Agile Software Development OR Assist Sec of Defense\"\n }, \"ASD\"), \": Acquisition Strategy Development OR Agile Software Development OR Assist Sec of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Assistant Secretary of Defense (Network and Information Integration\"\n }, \"ASDNII\"), \": Assistant Secretary of Defense (Network and Information Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Airborne Signals Intelligence Payload OR Aircraft Structural Integrity Program\"\n }, \"ASIP\"), \": Airborne Signals Intelligence Payload OR Aircraft Structural Integrity Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Strategy Panel\"\n }, \"ASP\"), \": Acquisition Strategy Panel\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition and Sustainment Reviews OR Alternative Systems Review\"\n }, \"ASR\"), \": Acquisition and Sustainment Reviews OR Alternative Systems Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Sustainment Tool Kit\"\n }, \"ASTK\"), \": Acquisition Sustainment Tool Kit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Surface Warfare\"\n }, \"ASuW\"), \": Anti-Surface Warfare\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \": Anti-Tamper\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L: Acquisition\\nTechnology\\nand Logistics\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automated Time Attendance and Production System\"\n }, \"ATAPPS\"), \": Automated Time Attendance and Production System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Traffic Control and Landing Systems\"\n }, \"ATCALS\"), \": Air Traffic Control and Landing Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Technology Demonstration (or Development)\"\n }, \"ATD\"), \": Advanced Technology Demonstration (or Development)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automatic Test Equipment\"\n }, \"ATE\"), \": Automatic Test Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Test and Evaluation Command\"\n }, \"ATEC\"), \": Army Test and Evaluation Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Tasking Order OR Authority to Operate\"\n }, \"ATO\"), \": Air Tasking Order OR Authority to Operate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automated Technical Orders System\"\n }, \"ATOS\"), \": Automated Technical Orders System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Test Program Application\"\n }, \"ATPA\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Program Application\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Targeting Pod-Sensor Enhancement\"\n }, \"ATP-SE\"), \": Advanced Targeting Pod-Sensor Enhancement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automatic Test System\"\n }, \"ATS\"), \": Automatic Test System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analyst Training and Technical Information Center\"\n }, \"ATTIC\"), \": Analyst Training and Technical Information Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Universal Task List\"\n }, \"AUTL\"), \": Army Universal Task List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"All Viewpoint\"\n }, \"AV\"), \": All Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Aviation Integrity Program\"\n }, \"AVIP\"), \": Aviation Integrity Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Aviation Petroleum, Oil, and Lubricants\"\n }, \"AVPOL\"), \": Aviation Petroleum\\nOil\\nand Lubricants\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Airborne Warning and Control System\"\n }, \"AWACS\"), \": Airborne Warning and Control System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Warfare Battle Shaping\"\n }, \"AWBS\"), \": Air Warfare Battle Shaping\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Advanced Weapons Integration Program\"\n }, \"AWIP\"), \": Advanced Weapons Integration Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defensive Management System\"\n }, \"B-2 DMS\"), \": Defensive Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Extremely High Frequency Satellite Communications\"\n }, \"B-2 EHF SATCOM\"), \": Extremely High Frequency Satellite Communications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"B-52 Commercial Engine Replacement Program\"\n }, \"B-52 CERP\"), \": B-52 Commercial Engine Replacement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"B-52 Radar Modernization Program\"\n }, \"B-52 RMP\"), \": B-52 Radar Modernization Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"B61 Life Extension Program\"\n }, \"B61 LEP\"), \": B61 Life Extension Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Buy American Act\"\n }, \"BAA\"), \": Buy American Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Bullet Background Paper\"\n }, \"BBP\"), \": Bullet Background Paper\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Business Case\"\n }, \"BC\"), \": Business Case\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Business Case Analysis\"\n }, \"BCA\"), \": Business Case Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Business Capability Lifecycle\"\n }, \"BCL\"), \": Business Capability Lifecycle\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Baseline Comparison System\"\n }, \"BCS\"), \": Baseline Comparison System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Baseline Comparison System\"\n }, \"BCS\"), \"-F: Battle Control System-Fixed\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Big Data Analytics; Bomb Damage Assessment\"\n }, \"BDA\"), \": Big Data Analytics; Bomb Damage Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Battle Damage Repair Spares Kit\"\n }, \"BDRSK\"), \": Battle Damage Repair Spares Kit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Business Enterprise Architecture\"\n }, \"BEA\"), \": Business Enterprise Architecture\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Budget Estimate Submission\"\n }, \"BES\"), \": Budget Estimate Submission\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Blue Force Tracking\"\n }, \"BFT\"), \": Blue Force Tracking\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Base and Installation Security System\"\n }, \"BISS\"), \": Base and Installation Security System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Beyond-Line-of-Sight Command and Control\"\n }, \"BLOS C2\"), \": Beyond-Line-of-Sight Command and Control\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Beyond Line of Sight\"\n }, \"BLOS\"), \": Beyond Line of Sight\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Bomb, Live Unit\"\n }, \"BLU\"), \": Bomb\\nLive Unit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Battle Management Command and Control Communications\"\n }, \"BMC2\"), \": Battle Management Command and Control Communications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ballistic Missile Defense\"\n }, \"BMD\"), \": Ballistic Missile Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ballistic Missile Defense System\"\n }, \"BMDS\"), \": Ballistic Missile Defense System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Base Operating Support\"\n }, \"BOS\"), \": Base Operating Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Budget Program Activity Code\"\n }, \"BPAC\"), \": Budget Program Activity Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Bomb Release Units\"\n }, \"BRU\"), \": Bomb Release Units\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \": Block Update\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Certification and Accreditation\"\n }, \"C&A\"), \": Certification and Accreditation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities and Limitations\"\n }, \"C&L\"), \": Capabilities and Limitations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities and Limitations Report\"\n }, \"C&LR\"), \": Capabilities and Limitations Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command and Control\"\n }, \"C2\"), \": Command and Control\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command and Control Air Operations Suite\"\n }, \"C2AOS\"), \": Command and Control Air Operations Suite\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Battle Management, and Communications\"\n }, \"C2BMC\"), \": Command\\nControl\\nBattle Management\\nand Communications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Continuous Capability Development and Delivery\"\n }, \"C2D2\"), \": Continuous Capability Development and Delivery\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command and Control Information Services\"\n }, \"C2IS\"), \": Command and Control Information Services\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Communications, and Computers\"\n }, \"C4\"), \": Command\\nControl\\nCommunications\\nand Computers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Communications, Computers, and Intelligence\"\n }, \"C4I\"), \": Command\\nControl\\nCommunications\\nComputers\\nand Intelligence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Communication, Computers, and Intelligence Support Plan\"\n }, \"C4ISP\"), \": Command\\nControl\\nCommunication\\nComputers\\nand Intelligence Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cmd, Control, Comm, Computers, Intel, Surveillance, and Reconnaissance\"\n }, \"C4ISR\"), \": Cmd\\nControl\\nComm\\nComputers\\nIntel\\nSurveillance\\nand Reconnaissance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \": Command Technical Advisor OR Contract Award OR Criticality Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Access Card \"\n }, \"CAC\"), \": Common Access Card \"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Computer-Aided Design (or Drafting)\"\n }, \"CAD\"), \": Computer-Aided Design (or Drafting)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Acquisition Executive\"\n }, \"CAE\"), \": Component Acquisition Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Comprehensive Air Force Technical Order Plan\"\n }, \"CAFTOP\"), \": Comprehensive Air Force Technical Order Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group\"\n }, \"CAG\"), \": Commander\\u2019s Action Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commercial and Government Entity\"\n }, \"CAGE\"), \": Commercial and Government Entity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cost Analysis Improvement Group\"\n }, \"CAIG\"), \": Cost Analysis Improvement Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Analytical Laboratory System\"\n }, \"CALS\"), \": Common Analytical Laboratory System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Centralized Asset Management\"\n }, \"CAM\"), \": Centralized Asset Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Coalition Air Operations Center\"\n }, \"CAOC\"), \": Coalition Air Operations Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Acquired Property OR Critical Acquisition Position\"\n }, \"CAP\"), \": Contractor Acquired Property OR Critical Acquisition Position\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Controlled Access Program Coordinating Office\"\n }, \"CAPCO\"), \": Controlled Access Program Coordinating Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cost Assessment and Program Evaluation\"\n }, \"CAPE\"), \": Cost Assessment and Program Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"F-16 Combat Avionics Programmed Extension Suite\"\n }, \"CAPES\"), \": F-16 Combat Avionics Programmed Extension Suite\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cost Analysis Requirements Description\"\n }, \"CARD\"), \": Cost Analysis Requirements Description\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Close Air Support System\"\n }, \"CASS\"), \": Close Air Support System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Category\"\n }, \"CAT\"), \": Category\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities-Based Assessment\"\n }, \"CBA\"), \": Capabilities-Based Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chemical and Biological Defense Program\"\n }, \"CBDP\"), \": Chemical and Biological Defense Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Condition-Based Maintenance Plus\"\n }, \"CBM\"), \": Condition-Based Maintenance Plus\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability-Based Planning\"\n }, \"CBP\"), \": Capability-Based Planning\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chemical, Biological, and Radiological\"\n }, \"CBR\"), \": Chemical\\nBiological\\nand Radiological\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities-Based Requirements Document\"\n }, \"CBRD\"), \": Capabilities-Based Requirements Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chemical, Biological, Radiological and Nuclear\"\n }, \"CBRN\"), \": Chemical\\nBiological\\nRadiological and Nuclear\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \": Commander OR Critical Component\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Clinger-Cohen Act OR Component Cost Analysis\"\n }, \"CCA\"), \": Clinger-Cohen Act OR Component Cost Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Comprehensive Cost and Requirement System\"\n }, \"CCaR\"), \": Comprehensive Cost and Requirement System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Core Compliance Area\"\n }, \"CCCA\"), \": Common Core Compliance Area\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Capability Document\"\n }, \"CCD\"), \": Combat Capability Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combatant Commander\"\n }, \"CCDR\"), \": Combatant Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capstone Concept for Joint Operations\"\n }, \"CCJO\"), \": Capstone Concept for Joint Operations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combatant Command\"\n }, \"CCMD\"), \": Combatant Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Control Points\"\n }, \"CCP\"), \": Command Control Points\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Corrosion Control Program Executive\"\n }, \"CCPE\"), \": Corrosion Control Program Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Call Completion Rate\"\n }, \"CCR\"), \": Call Completion Rate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Counter-Concealment Sensing\"\n }, \"C-CS\"), \": Counter-Concealment Sensing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Collaboration Teams\"\n }, \"CCT\"), \": Capability Collaboration Teams\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept Characterization and Technical Description\"\n }, \"CCTD\"), \": Concept Characterization and Technical Description\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Action Group Office Symbol\"\n }, \"CCX\"), \": Commander\\u2019s Action Group Office Symbol\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Director (or Directorate) OR Deputy Commander\"\n }, \"CD\"), \": Capability Director (or Directorate) OR Deputy Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Current Design Activity\"\n }, \"CDA\"), \": Current Design Activity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \": Capability Development Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Definition Package\"\n }, \"CDP\"), \": Capability Definition Package\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Design Review\"\n }, \"CDR\"), \": Critical Design Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contract Data Requirements List\"\n }, \"CDRL\"), \": Contract Data Requirements List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cross Domain Solution\"\n }, \"CDS\"), \": Cross Domain Solution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Developmental Tester\"\n }, \"CDT\"), \": Chief Developmental Tester\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Civil Engineer OR Conducted Emissions\"\n }, \"CE\"), \": Civil Engineer OR Conducted Emissions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \": Circular Error Probability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Certification\"\n }, \"CERT\"), \": Certification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Core Function Lead\"\n }, \"CFL\"), \": Core Function Lead\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Core Function Lead Integrator\"\n }, \"CFLI\"), \": Core Function Lead Integrator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Core Function Master Plan\"\n }, \"CFMP\"), \": Core Function Master Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Financial Officer\"\n }, \"CFO\"), \": Chief Financial Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities Focused Planning\"\n }, \"CFP\"), \": Capabilities Focused Planning\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Code of Federal Regulations\"\n }, \"CFR\"), \": Code of Federal Regulations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contract Funds Status Report\"\n }, \"CFSR\"), \": Contract Funds Status Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Gap Assessment\"\n }, \"CGA\"), \": Capability Gap Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common GPS Module\"\n }, \"CGM\"), \": Common \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" Module\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Configuration Item OR Counterintelligence\"\n }, \"CI\"), \": Configuration Item OR Counterintelligence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Competition in Contracting Act\"\n }, \"CICA\"), \": Competition in Contracting Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contamination Indicator Decontamination Assurance System\"\n }, \"CIDAS\"), \": Contamination Indicator Decontamination Assurance System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Counter-Improvised Explosive Device\"\n }, \"CIED\"), \": Counter-Improvised Explosive Device\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander’s Inspection Management Board\"\n }, \"CIMB\"), \": Commander\\u2019s Inspection Management Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Information Officer\"\n }, \"CIO\"), \": Chief Information Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Intelligence Parameter\"\n }, \"CIP\"), \": Critical Intelligence Parameter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cyberspace Infrastructure Planning System\"\n }, \"CIPS\"), \": Cyberspace Infrastructure Planning System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capital Investment Report\"\n }, \"CIR\"), \": Capital Investment Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Counterintelligence Support Plan\"\n }, \"CISP\"), \": Counterintelligence Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Center of Industrial and Technical Excellence\"\n }, \"CITE\"), \": Center of Industrial and Technical Excellence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman, Joint Chiefs of Staff\"\n }, \"CJCS\"), \": Chairman\\nJoint Chiefs of Staff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman, Joint Chief of Staff Instruction\"\n }, \"CJCSI\"), \": Chairman\\nJoint Chief of Staff Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman, Joint Chiefs of Staff Manual\"\n }, \"CJCSM\"), \": Chairman\\nJoint Chiefs of Staff Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"COBRA JUDY Replacement\"\n }, \"CJR\"), \": COBRA JUDY Replacement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Coalition Joint Task Force\"\n }, \"CJTF\"), \": Coalition Joint Task Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"China Lake OR Civilian Leader OR Continuous Learning\"\n }, \"CL\"), \": China Lake OR Civilian Leader OR Continuous Learning\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contract Line Item Number\"\n }, \"CLIN\"), \": Contract Line Item Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Logistics Support\"\n }, \"CLS\"), \": Contractor Logistics Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Configuration Management OR Consequence Management OR Constellation Management OR Corrective Maintenance\"\n }, \"CM\"), \": Configuration Management OR Consequence Management OR Constellation Management OR Corrective Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Munitions BIT Reprogramming Equipment\"\n }, \"CMBRE\"), \": Common Munitions BIT Reprogramming Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"C-5 Core Mission Computer and Weather Radar Program\"\n }, \"CMC\"), \": C-5 Core Mission Computer and Weather Radar Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability-Mission Lattice\"\n }, \"CML\"), \": Capability-Mission Lattice\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Maturity Model Integration\"\n }, \"CMMI\"), \": Capability Maturity Model Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Configuration Management Plan\"\n }, \"CMP\"), \": Configuration Management Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Collaboration and Measurements Requirements Summary\"\n }, \"CMRS\"), \": Collaboration and Measurements Requirements Summary\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Computer Network Attack\"\n }, \"CNA\"), \": Computer Network Attack\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Change Notice Engineering Order\"\n }, \"CNEO\"), \": Change Notice Engineering Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Committee on National Security Systems (CNSS) Instruction\"\n }, \"CNSSI\"), \": Committee on National Security Systems (CNSS) Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Nuclear Weapons Design Information\"\n }, \"CNWDI\"), \": Critical Nuclear Weapons Design Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer\"\n }, \"CO\"), \": Contracting Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Course of Action\"\n }, \"COA\"), \": Course of Action\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Certificate of Compliance\"\n }, \"CoC\"), \": Certificate of Compliance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combatant Command\"\n }, \"COCOM\"), \": Combatant Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"COD\"), \": Capability Development Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \": Critical Operational Issue\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Community On-Line Intelligence System for End Users and Managers\"\n }, \"COLISEUM\"), \": Community On-Line Intelligence System for End Users and Managers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander Air Force Forces\"\n }, \"COMAFFOR\"), \": Commander Air Force Forces\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Naval Command Operational Test and Evaluation Force\"\n }, \"COMOPTEVFOR\"), \": Naval Command Operational Test and Evaluation Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Communications Security\"\n }, \"COMSEC\"), \": Communications Security\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Certificate of Networthiness\"\n }, \"CoN\"), \": Certificate of Networthiness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"B-52 Combat Network Communications Technology\"\n }, \"CONECT\"), \": B-52 Combat Network Communications Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Employment\"\n }, \"CONEMP\"), \": Concept of Employment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \": Concept of Operations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Continuity of Operations Plan\"\n }, \"COOP\"), \": Continuity of Operations Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Operating Picture\"\n }, \"COP\"), \": Common Operating Picture\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Community of Practice\"\n }, \"CoP\"), \": Community of Practice\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer’s Representative\"\n }, \"COR\"), \": Contracting Officer\\u2019s Representative\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issues and Criteria\"\n }, \"CORE\"), \": Critical Operational Issues and Criteria\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander, Operational Test Force (OPTEVFOR)\"\n }, \"COTF\"), \": Commander\\nOperational Test Force (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test and Evaluation Force\"\n }, \"OPTEVFOR\"), \")\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commercial Off-the-Shelf\"\n }, \"COTS\"), \": Commercial Off-the-Shelf\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Operational Test Team\"\n }, \"COTT\"), \": Combined Operational Test Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman’s Program Assessment\"\n }, \"CPA\"), \": Chairman\\u2019s Program Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cost-Plus Award Fee\"\n }, \"CPAF\"), \": Cost-Plus Award Fee\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Performance Assessment Reporting System\"\n }, \"CPARS\"), \": Contractor Performance Assessment Reporting System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Corrosion Prevention and Control Plan\"\n }, \"CPCP\"), \": Corrosion Prevention and Control Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Production Document\"\n }, \"CPD\"), \": Capability Production Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Crash Position Indicator OR Critical Program Information\"\n }, \"CPI\"), \": Crash Position Indicator OR Critical Program Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cost Plus Incentive Fee\"\n }, \"CPIF\"), \": Cost Plus Incentive Fee\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Portfolio Manager\"\n }, \"CPM\"), \": Capability Portfolio Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman’s Program Recommendation\"\n }, \"CPR\"), \": Chairman\\u2019s Program Recommendation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Change Request\"\n }, \"CR\"), \": Change Request\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hexavalent Chromium\"\n }, \"CR6\"), \": Hexavalent Chromium\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Continuing Resolution Authority OR Cost Risk Assessment OR Chairman’s Risk Assessment\"\n }, \"CRA\"), \": Continuing Resolution Authority OR Cost Risk Assessment OR Chairman\\u2019s Risk Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities Requirements Document \"\n }, \"CRD\"), \": Capabilities Requirements Document \"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Research and Development Agreement\"\n }, \"CRDA\"), \": Cooperative Research and Development Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Rescue Helicopter\"\n }, \"CRH\"), \": Combat Rescue Helicopter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Range Integrated Instrumentation System\"\n }, \"CRIIS\"), \": Common Range Integrated Instrumentation System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cross Industry Standard Process for Data Mining\"\n }, \"CRISP\"), \": Cross Industry Standard Process for Data Mining\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Component Resolution Matrix OR Crew Resource Management\"\n }, \"CRM\"), \": Component Resolution Matrix OR Crew Resource Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capabilities Review and Risk Assessment\"\n }, \"CRRA\"), \": Capabilities Review and Risk Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman’s Readiness System\"\n }, \"CRS\"), \": Chairman\\u2019s Readiness System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \": Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \": Combat Support Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff of the Air Force\"\n }, \"CSAF\"), \": Chief of Staff of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Consolidated Sustainment Activity Group\"\n }, \"CSAG\"), \": Consolidated Sustainment Activity Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue\"\n }, \"CSAR\"), \": Combat Search and Rescue\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue Locator\"\n }, \"CSARL\"), \": Combat Search and Rescue Locator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Configuration Steering Board\"\n }, \"CSB\"), \": Configuration Steering Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Computer Software Configuration Items\"\n }, \"CSCI\"), \": Computer Software Configuration Items\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Center for Systems Engineering OR Common Support Equipment\"\n }, \"CSE\"), \": Center for Systems Engineering OR Common Support Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Support Helicopter\"\n }, \"CSH\"), \": Common Support Helicopter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Safety Item\"\n }, \"CSI\"), \": Critical Safety Item\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commodity Strategy Official\"\n }, \"CSO\"), \": Commodity Strategy Official\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical System Resources\"\n }, \"CSR\"), \": Critical System Resources\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contract Sustainment Support\"\n }, \"CSS\"), \": Contract Sustainment Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Counter-small Unmanned Aerial Systems\"\n }, \"C-sUAS\"), \": Counter-small Unmanned Aerial Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Supported Weapon System\"\n }, \"CSWS\"), \": Contractor Supported Weapon System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \": Contractor Testing OR Critical Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Threat Assessments OR Center Test Authority\"\n }, \"CTA\"), \": Capability Threat Assessments OR Center Test Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Technology Element\"\n }, \"CTE\"), \": Critical Technology Element\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Central Test & Evaluation Investment Program\"\n }, \"CTEIP\"), \": Central Test & Evaluation Investment Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combined Task Force\"\n }, \"CTF\"), \": Combined Task Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Technical Information Code\"\n }, \"CTIC\"), \": Contractor Technical Information Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Transition Memorandum\"\n }, \"CTM\"), \": Capability Transition Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Certificate to Operate\"\n }, \"CtO\"), \": Certificate to Operate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Centralized Technical Order Management\"\n }, \"CTOM\"), \": Centralized Technical Order Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Technical Parameter\"\n }, \"CTP\"), \": Critical Technical Parameter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Transition Review\"\n }, \"CTR\"), \": Capability Transition Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Controlled Unclassified Information\"\n }, \"CUI\"), \": Controlled Unclassified Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Controlled Unclassified Military Information\"\n }, \"CUMI\"), \": Controlled Unclassified Military Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Commander OR Capability Viewpoint\"\n }, \"CV\"), \": Vice Commander OR Capability Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Information Protection/SAP Security (office symbol)\"\n }, \"CVI\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Information Protection/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \" Security (office symbol)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Common Vertical Lift Support Platform\"\n }, \"CVLSP\"), \": Common Vertical Lift Support Platform\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \": Cooperative Vulnerability and Penetration Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Carrier Air Wing\"\n }, \"CVW\"), \": Carrier Air Wing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Continuous Wave Illuminator\"\n }, \"CWI\"), \": Continuous Wave Illuminator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Calendar Year\"\n }, \"CY\"), \": Calendar Year\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Determination and Findings\"\n }, \"D&F\"), \": Determination and Findings\"), mdx(\"p\", null, \"D\\nARA: Director\\nAcquisition Resources\\nand Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director, Cost Assessment, and Program Evaluation\"\n }, \"D/CAPE\"), \": Director\\nCost Assessment\\nand Program Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Development/Qualification Test and Evaluation\"\n }, \"D/QT&E\"), \": Development/Qualification Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of the Army\"\n }, \"DA\"), \": Department of the Army\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Designated Approval Authority\"\n }, \"DAA\"), \": Designated Approval Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Board\"\n }, \"DAB\"), \": Defense Acquisition Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Designated Acquisition Commander\"\n }, \"DAC\"), \": Designated Acquisition Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director, Acquisition Career Management\"\n }, \"DACM\"), \": Director\\nAcquisition Career Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Executive\"\n }, \"DAE\"), \": Defense Acquisition Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Executive Summary\"\n }, \"DAES\"), \": Defense Acquisition Executive Summary\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of the Air Force\"\n }, \"DAF\"), \": Department of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Guidebook\"\n }, \"DAG\"), \": Defense Acquisition Guidebook\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Management Information Retrieval\"\n }, \"DAMIR\"), \": Defense Acquisition Management Information Retrieval\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Designated Acquisition Officials\"\n }, \"DAO\"), \": Designated Acquisition Officials\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deep Space Advanced Radar Concept\"\n }, \"DARC\"), \": Deep Space Advanced Radar Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Advanced Research Projects Agency\"\n }, \"DARPA\"), \": Defense Advanced Research Projects Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data, Acquisition, Recording, and Telemetry OR Deficiency Analysis Ranking Technique\"\n }, \"DART\"), \": Data\\nAcquisition\\nRecording\\nand Telemetry OR Deficiency Analysis Ranking Technique\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition System\"\n }, \"DAS\"), \": Defense Acquisition System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Assistant Secretary of Defense\"\n }, \"DASD\"), \": Deputy Assistant Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Denial of Authorization to Operate\"\n }, \"DATO\"), \": Denial of Authorization to Operate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition University\"\n }, \"DAU\"), \": Defense Acquisition University\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Workforce Improvement Act\"\n }, \"DAWIA\"), \": Defense Acquisition Workforce Improvement Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Business Council\"\n }, \"DBC\"), \": Defense Business Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Business Systems\"\n }, \"DBS\"), \": Defense Business Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Business Systems Management Committee\"\n }, \"DBSMC\"), \": Defense Business Systems Management Committee\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Derivative Classifier OR Direct Current\"\n }, \"DC\"), \": Derivative Classifier OR Direct Current\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Contract Audit Agency\"\n }, \"DCAA\"), \": Defense Contract Audit Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Cost Assessment and Program Evaluation\"\n }, \"DCAPE\"), \": Director of Cost Assessment and Program Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deliberate and Crisis Action Planning and Execution Segments\"\n }, \"DCAPES\"), \": Deliberate and Crisis Action Planning and Execution Segments\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Distributed Common Ground System\"\n }, \"DCGS\"), \": Distributed Common Ground System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Central Intelligence Directive\"\n }, \"DCID\"), \": Director of Central Intelligence Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Contract Management Agency\"\n }, \"DCMA\"), \": Defense Contract Management Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Civilian Personnel Data System\"\n }, \"DCPDS\"), \": Defense Civilian Personnel Data System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"DOTMLPF-P Change Recommendation\"\n }, \"DCR\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Doctrine, Organization, Training, materiel, Leadership Policy and Education, Personnel, Facilities, and Policy\"\n }, \"DOTMLPF-P\"), \" Change Recommendation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Chief of Staff\"\n }, \"DCS\"), \": Deputy Chief of Staff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Director of National Intelligence for Management\"\n }, \"DDNI/M\"), \": Deputy Director of National Intelligence for Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Director for Requirements OR Dismount Detection Radar\"\n }, \"DDR\"), \": Deputy Director for Requirements OR Dismount Detection Radar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director, Developmental Test and Evaluation\"\n }, \"DDT&E\"), \": Director\\nDevelopmental Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Destruction of Enemy Air Defenses\"\n }, \"DEAD\"), \": Destruction of Enemy Air Defenses\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Enterprise Accounting and Management System\"\n }, \"DEAMS\"), \": Defense Enterprise Accounting and Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Evaluation Framework\"\n }, \"DEF\"), \": Developmental Evaluation Framework\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Secretary of Defense\"\n }, \"DepSecDef\"), \": Deputy Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \": Detachment Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Directed Energy Weapons\"\n }, \"DEW\"), \": Directed Energy Weapons\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Directed Energy Weapons Certification Board\"\n }, \"DEWCB\"), \": Directed Energy Weapons Certification Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Federal Acquisition Regulation Supplement\"\n }, \"DFARS\"), \": Defense Federal Acquisition Regulation Supplement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Dual Frequency Civil Navigation\"\n }, \"DFCN\"), \": Dual Frequency Civil Navigation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Decontamination Family of Systems\"\n }, \"DFoS\"), \": Decontamination Family of Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Healthcare Management Systems Modernization\"\n }, \"DHMSM\"), \": Defense Healthcare Management Systems Modernization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Intelligence Agency\"\n }, \"DIA\"), \": Defense Intelligence Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"DoD Information Assurance Certification and Accreditation Process\"\n }, \"DIACAP\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Information Assurance Certification and Accreditation Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Item Description\"\n }, \"DID\"), \": Data Item Description\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"DIACAP Implementation Plan\"\n }, \"DIP\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"DoD Information Assurance Certification and Accreditation Process\"\n }, \"DIACAP\"), \" Implementation Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Information Systems Agency\"\n }, \"DISA\"), \": Defense Information Systems Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Information Technology Standards Registry\"\n }, \"DISR\"), \": Department of Defense Information Technology Standards Registry\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Information Technology Security Certification and Accreditation Program\"\n }, \"DITSCAP\"), \": Department of Defense Information Technology Security Certification and Accreditation Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data and Information Viewpoint\"\n }, \"DIV\"), \": Data and Information Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Logistics Agency\"\n }, \"DLA\"), \": Defense Logistics Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot-Level Repairable\"\n }, \"DLR\"), \": Depot-Level Repairable\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Mining\"\n }, \"DM\"), \": Data Mining\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Management and Analysis Plan\"\n }, \"DMAP\"), \": Data Management and Analysis Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot Maintenance Activation Working Group\"\n }, \"DMAWG\"), \": Depot Maintenance Activation Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Microelectronics Activity\"\n }, \"DMEA\"), \": Defense Microelectronics Activity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot Maintenance Interservice\"\n }, \"DMI\"), \": Depot Maintenance Interservice\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Medical Information Exchange Joint Legacy Viewer\"\n }, \"DMIX JLV\"), \": Defense Medical Information Exchange Joint Legacy Viewer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defensive Management System OR Diminishing Manufacturing Sources\"\n }, \"DMS\"), \": Defensive Management System OR Diminishing Manufacturing Sources\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Diminishing Manufacturing Sources Material Shortages\"\n }, \"DMSMS\"), \": Diminishing Manufacturing Sources Material Shortages\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Domestic Non-Availability Determination\"\n }, \"DNAD\"), \": Domestic Non-Availability Determination\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of National Intelligence\"\n }, \"DNI\"), \": Director of National Intelligence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \": Department of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Activity Code\"\n }, \"DODAAC\"), \": Department of Defense Activity Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Directive\"\n }, \"DODD\"), \": Department of Defense Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Instruction\"\n }, \"DODI\"), \": Department of Defense Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Information Network\"\n }, \"DODIN\"), \": Department of Defense Information Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Intelligence Production Program\"\n }, \"DODIPP\"), \": Department of Defense Intelligence Production Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Index of Specifications and Standards\"\n }, \"DODISS\"), \": Department of Defense Index of Specifications and Standards\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Manual\"\n }, \"DODM\"), \": Department of Defense Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \": Department of Energy OR Design of Experiments\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of the Navy\"\n }, \"DoN\"), \": Department of the Navy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \": Director of Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Doctrine, Organization, Training, materiel, Leadership Policy and Education, Personnel, Facilities, and Policy\"\n }, \"DOTMLPF-P\"), \": Doctrine\\nOrganization\\nTraining\\nmateriel\\nLeadership Policy and Education\\nPersonnel\\nFacilities\\nand Policy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Development Planning\"\n }, \"DP\"), \": Development Planning\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Procurement and Acquisition Policy\"\n }, \"DPAP\"), \": Director of Procurement and Acquisition Policy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Priorities and Allocation System\"\n }, \"DPAS\"), \": Defense Priorities and Allocation System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot Purchased Equipment Maintenance\"\n }, \"DPEM\"), \": Depot Purchased Equipment Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Planning Guidance\"\n }, \"DPG\"), \": Defense Planning Guidance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Processing Ground Station\"\n }, \"DPGS\"), \": Data Processing Ground Station\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Planning and Programming Guidance\"\n }, \"DPPG\"), \": Defense Planning and Programming Guidance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Dismounted Reconnaissance Sets, Kits, and Outfits\"\n }, \"DR SKO\"), \": Dismounted Reconnaissance Sets\\nKits\\nand Outfits\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deficiency Report\"\n }, \"DR\"), \": Deficiency Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"\n }, \"DRAGON\"), \": E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deficiency Review Board\"\n }, \"DRB\"), \": Deficiency Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Research Engineering Network\"\n }, \"DREN\"), \": Defense Research Engineering Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Referential Integrity\"\n }, \"DRI\"), \": Data Referential Integrity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Referential Integrity\"\n }, \"DRI\"), \"&R: Deficiency Reporting\\nInvestigation and Resolution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"DRAGON Requirements Memorandum\"\n }, \"DRM\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"\n }, \"DRAGON\"), \" Requirements Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Reutilization Marketing Office\"\n }, \"DRMO\"), \": Defense Reutilization Marketing Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Design Readiness Review\"\n }, \"DRR\"), \": Design Readiness Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Direct Reporting Unit\"\n }, \"DRU\"), \": Direct Reporting Unit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Designated Science and Technology Information\"\n }, \"DS&TI\"), \": Designated Science and Technology Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Direct Sales Agreement\"\n }, \"DSA\"), \": Direct Sales Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Decision Support Question\"\n }, \"DSC\"), \": Decision Support Question\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Security Cooperation Agency\"\n }, \"DSCA\"), \": Defense Security Cooperation Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Development System Manager OR Digital System Model\"\n }, \"DSM\"), \": Development System Manager OR Digital System Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot Source of Repair\"\n }, \"DSOR\"), \": Depot Source of Repair\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Depot Source of Repair\"\n }, \"DSOR\"), \"-EM: Depot Source of Repair-Electronic Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \": Developmental Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E: Developmental Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Data Type Definition\"\n }, \"DTD\"), \": Data Type Definition\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Technical Information Center\"\n }, \"DTIC\"), \": Defense Technical Information Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Directive-Type Memorandum\"\n }, \"DTM\"), \": Directive-Type Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detailed Test Plan\"\n }, \"DTP\"), \": Detailed Test Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deputy Under Secretary of Defense\"\n }, \"DUSD\"), \": Deputy Under Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \": Effectiveness and Suitability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"\n }, \"E-3 DRAGON\"), \": E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Environmental Effects\"\n }, \"E3\"), \": Electromagnetic Environmental Effects\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Economic Analysis OR Electronic Attack OR Evolutionary Acquisition OR Executing Authority\"\n }, \"EA\"), \": Economic Analysis OR Electronic Attack OR Evolutionary Acquisition OR Executing Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Estimate at Completion\"\n }, \"EAC\"), \": Estimate at Completion\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Estimated Completion Date\"\n }, \"ECD\"), \": Estimated Completion Date\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Countermeasures\"\n }, \"ECM\"), \": Electronic Countermeasures\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enclave Control Node\"\n }, \"ECN\"), \": Enclave Control Node\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Expeditionary Combat Support System\"\n }, \"ECSS\"), \": Expeditionary Combat Support System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Director\"\n }, \"ED\"), \": Executive Director\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engineering Data Guidance Conference\"\n }, \"EDGC\"), \": Engineering Data Guidance Conference\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engineering Data Manager (or Management) OR Engineering Development Model\"\n }, \"EDM\"), \": Engineering Data Manager (or Management) OR Engineering Development Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engineering Data Service Center\"\n }, \"EDSC\"), \": Engineering Data Service Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enterprise Engineering Center\"\n }, \"EEC\"), \": Enterprise Engineering Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Element of Expense Investment Code\"\n }, \"EEIC\"), \": Element of Expense Investment Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Essential Function Failure\"\n }, \"EFF\"), \": Essential Function Failure\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Extremely High Frequency\"\n }, \"EHF\"), \": Extremely High Frequency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment Impact Analysis Process\"\n }, \"EIAP\"), \": Environment Impact Analysis Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enterprise Information Environment Mission Area\"\n }, \"EIEMA\"), \": Enterprise Information Environment Mission Area\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Influence Strategy\"\n }, \"EIS\"), \": Early Influence Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Influence Team\"\n }, \"EIT\"), \": Early Influence Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enterprise Information Technology Data Repository\"\n }, \"EITDR\"), \": Enterprise Information Technology Data Repository\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Key Management System\"\n }, \"EKMS\"), \": Electronic Key Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Elevated Level of Assurance\"\n }, \"ELA\"), \": Elevated Level of Assurance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Emergency Locator Transmitter\"\n }, \"ELT\"), \": Emergency Locator Transmitter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Expectation Management Agreement\"\n }, \"EMA\"), \": Expectation Management Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Compatibility\"\n }, \"EMC\"), \": Electromagnetic Compatibility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Compatibility\"\n }, \"EMC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Interference\"\n }, \"EMI\"), \": Electromagnetic Compatibility/Electromagnetic Interference\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engineering and Manufacturing Development\"\n }, \"EMD\"), \": Engineering and Manufacturing Development\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Interference\"\n }, \"EMI\"), \": Electromagnetic Interference\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Pulse\"\n }, \"EMP\"), \": Electromagnetic Pulse\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Emission Security\"\n }, \"EMSEC\"), \": Emission Security\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Vulnerability\"\n }, \"EMV\"), \": Electromagnetic Vulnerability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engine Structural Integrity Program\"\n }, \"ENSIP\"), \": Engine Structural Integrity Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electro-Optical OR Executive Order OR Engineering Order\"\n }, \"EO\"), \": Electro-Optical OR Executive Order OR Engineering Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \": Early Operational Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Explosive Ordnance Disposal\"\n }, \"EOD\"), \": Explosive Ordnance Disposal\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Protection\"\n }, \"EP\"), \": Electronic Protection\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"F-15 Eagle Passive and Active Warning and Survivability System\"\n }, \"EPAWSS\"), \": F-15 Eagle Passive and Active Warning and Survivability System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Proving Ground\"\n }, \"EPG\"), \": Electronic Proving Ground\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AIM-120C Advanced Electronic Protection Improvement Program\"\n }, \"EPIP\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Intercept Missile\"\n }, \"AIM\"), \"-120C Advanced Electronic Protection Improvement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enhanced Polar System\"\n }, \"EPS\"), \": Enhanced Polar System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetically Enhanced Physical Vapor Deposition (gun tube coating\"\n }, \"EPVD\"), \": Electromagnetically Enhanced Physical Vapor Deposition (gun tube coating\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Remote Fill\"\n }, \"ERF\"), \": Electronic Remote Fill\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environmental Resources Manager\"\n }, \"ERM\"), \": Environmental Resources Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \": Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \": Environment\\nSafety\\nand Occupational Health\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Council\"\n }, \"ESOHC\"), \": Environment\\nSafety\\nand Occupational Health Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \": Environment\\nSafety\\nand Occupational Health Certification Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \": Environment\\nSafety\\nand Occupational Health Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Emergency and Special Program\"\n }, \"ESP\"), \": Emergency and Special Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness, Suitability, and Survivability OR Evolved Strategic Satellite Communications\"\n }, \"ESS\"), \": Effectiveness\\nSuitability\\nand Survivability OR Evolved Strategic Satellite Communications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Systems Wing OR Evaluation Summary Worksheet\"\n }, \"ESW\"), \": Electronic Systems Wing OR Evaluation Summary Worksheet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enhanced Technical Information Management System\"\n }, \"ETIMS\"), \": Enhanced Technical Information Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Technical Manual\"\n }, \"ETM\"), \": Electronic Technical Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executing Test Organization\"\n }, \"ETO\"), \": Executing Test Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Engineering Units\"\n }, \"EU\"), \": Engineering Units\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"End Use Certificate\"\n }, \"EUC\"), \": End Use Certificate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \": Evaluation View\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Earned Value Management\"\n }, \"EVM\"), \": Earned Value Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Earned Value Management\"\n }, \"EVM\"), \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Change Request\"\n }, \"CR\"), \": Earned Value Management-Central Repository\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Earned Value Management System\"\n }, \"EVMS\"), \": Earned Value Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Warfare\"\n }, \"EW\"), \": Electronic Warfare\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Warfare Infrastructure Improvement Program\"\n }, \"EWIIP\"), \": Electronic Warfare Infrastructure Improvement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electronic Warfare Integrated Reprogramming\"\n }, \"EWIR\"), \": Electronic Warfare Integrated Reprogramming\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Executive Weapons System Review\"\n }, \"EWSR\"), \": Executive Weapons System Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"F-15 Eagle Passive and Active Warning and Survivability System\"\n }, \"F-15 EPAWSS\"), \": F-15 Eagle Passive and Active Warning and Survivability System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"F-15 Infrared Search and Track System\"\n }, \"F-15 IRST\"), \": F-15 Infrared Search and Track System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Form, Fit, Function, or Interface\"\n }, \"F3I\"), \": Form\\nFit\\nFunction\\nor Interface\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Aviation Administration OR Functional Area Analysis\"\n }, \"FAA\"), \": Federal Aviation Administration OR Functional Area Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Family of Advanced Beyond Line Of Sight Terminals\"\n }, \"FAB-T\"), \": Family of Advanced Beyond Line Of Sight Terminals\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Forward Air Controller-Airborne\"\n }, \"FAC-A\"), \": Forward Air Controller-Airborne\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Acquisition Regulation\"\n }, \"FAR\"), \": Federal Acquisition Regulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Area Records Manager\"\n }, \"FARM\"), \": Functional Area Records Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"First Article Test\"\n }, \"FAT\"), \": First Article Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Configuration Audit\"\n }, \"FCA\"), \": Functional Configuration Audit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Capabilities Board\"\n }, \"FCB\"), \": Functional Capabilities Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Flagship Capability Concepts\"\n }, \"FCC\"), \": Flagship Capability Concepts\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Foreign Comparative Test\"\n }, \"FCT\"), \": Foreign Comparative Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fielding Decision\"\n }, \"FD\"), \": Fielding Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fielding Decision\"\n }, \"FD\"), \"/SC: Failure Definition/Scoring Criteria\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Final Evaluation and Decision Brief\"\n }, \"FDB\"), \": Final Evaluation and Decision Brief\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Deployment Decision\"\n }, \"FDD\"), \": Full Deployment Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Deployment Decision Review\"\n }, \"FDDR\"), \": Full Deployment Decision Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Force Development Evaluation\"\n }, \"FDE\"), \": Force Development Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fee Determining Official\"\n }, \"FDO\"), \": Fee Determining Official\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Final (or Formal) Design Review\"\n }, \"FDR\"), \": Final (or Formal) Design Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Force Element Terminal\"\n }, \"FET\"), \": Force Element Terminal\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Firm Fixed Price\"\n }, \"FFP\"), \": Firm Fixed Price\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federally Funded Research and Development Centers\"\n }, \"FFRDC\"), \": Federally Funded Research and Development Centers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Friendly Force Tracking\"\n }, \"FFT\"), \": Friendly Force Tracking\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Flying Hours\"\n }, \"FH\"), \": Flying Hours\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Financial Improvement and Audit Readiness\"\n }, \"FIAR\"), \": Financial Improvement and Audit Readiness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Information Processing\"\n }, \"FIP\"), \": Federal Information Processing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Information System Controls Audit Manual\"\n }, \"FISCAM\"), \": Federal Information System Controls Audit Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Information Security Management Act of 2002\"\n }, \"FISMA\"), \": Federal Information Security Management Act of 2002\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Financial Management OR Frequency Modulation OR Functional Manager\"\n }, \"FM\"), \": Financial Management OR Frequency Modulation OR Functional Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fully Mission Capable\"\n }, \"FMC\"), \": Fully Mission Capable\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Failure Mode, Effects, and Criticality Analysis\"\n }, \"FMECA\"), \": Failure Mode\\nEffects\\nand Criticality Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Flight Manual Manager\"\n }, \"FMM\"), \": Flight Manual Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Flight Manuals Program OR Foreign Materiel Program\"\n }, \"FMP\"), \": Flight Manuals Program OR Foreign Materiel Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Financial Management Regulation\"\n }, \"FMR\"), \": Financial Management Regulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Financial Management Regulation System\"\n }, \"FMRS\"), \": Financial Management Regulation System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Foreign Military Sales\"\n }, \"FMS\"), \": Foreign Military Sales\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fuze Module Unit-139\"\n }, \"FMU-139 D/B\"), \": Fuze Module Unit-139\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Needs Analysis\"\n }, \"FNA\"), \": Functional Needs Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Field Operating Agency\"\n }, \"FOA\"), \": Field Operating Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Forward Operating Base\"\n }, \"FOB\"), \": Forward Operating Base\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Operational Capability\"\n }, \"FOC\"), \": Full Operational Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Freedom of Information Act\"\n }, \"FOIA\"), \": Freedom of Information Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Modernization\"\n }, \"FoM\"), \": Follow-on Modernization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Future Operationally Resilient Ground Evolution\"\n }, \"FORGE\"), \": Future Operationally Resilient Ground Evolution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Family of Systems\"\n }, \"FoS\"), \": Family of Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \": Follow-on Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Operational Utility\"\n }, \"FOU\"), \": Full Operational Utility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"For Official Use Only\"\n }, \"FOUO\"), \": For Official Use Only\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Field of View\"\n }, \"FOV\"), \": Field of View\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fixed-Price with Award Fee\"\n }, \"FPAF\"), \": Fixed-Price with Award Fee\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Production Decision\"\n }, \"FPD\"), \": Follow-on Production Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Procurement data System-Next Generation\"\n }, \"FPDS-NG\"), \": Federal Procurement data System-Next Generation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fixed-Price Incentive\"\n }, \"FPIF\"), \": Fixed-Price Incentive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Final Pricing Report OR Final Proposal Revision\"\n }, \"FPR\"), \": Final Pricing Report OR Final Proposal Revision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Forward Price Rate Agreements\"\n }, \"FPRA\"), \": Forward Price Rate Agreements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Formal Qualification Review\"\n }, \"FQR\"), \": Formal Qualification Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Formerly Restricted Data\"\n }, \"FRD\"), \": Formerly Restricted Data\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full-Rate Production\"\n }, \"FRP\"), \": Full-Rate Production\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full-Rate Production\"\n }, \"FRP\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fielding Decision\"\n }, \"FD\"), \": Full-Rate Production or Full Deployment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Rate Production Decision Review\"\n }, \"FRPDR\"), \": Full Rate Production Decision Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Requirements Review Board\"\n }, \"FRRB\"), \": Functional Requirements Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Functional Solution Analysis\"\n }, \"FSA\"), \": Functional Solution Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Federal Supply Classification\"\n }, \"FSC\"), \": Federal Supply Classification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Field Service Representative\"\n }, \"FSR\"), \": Field Service Representative\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Time Equivalent\"\n }, \"FTE\"), \": Full Time Equivalent\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Field Training Exercise\"\n }, \"FTX\"), \": Field Training Exercise\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fiscal Year\"\n }, \"FY\"), \": Fiscal Year\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Future Years Defense Program\"\n }, \"FYDP\"), \": Future Years Defense Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General and Administrative (Expense)\"\n }, \"G&A\"), \": General and Administrative (Expense)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Accountability Office\"\n }, \"GAO\"), \": Government Accountability Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Analysis Tool\"\n }, \"GAT\"), \": Government Analysis Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Broadcast Service\"\n }, \"GBS\"), \": Global Broadcast Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ground Based Strategic Deterrent\"\n }, \"GBSD\"), \": Ground Based Strategic Deterrent\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Guided Bomb Unit\"\n }, \"GBU\"), \": Guided Bomb Unit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Cyberspace Integration Center\"\n }, \"GCIC\"), \": Global Cyberspace Integration Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ground Control Stations\"\n }, \"GCS\"), \": Ground Control Stations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Combat Support System – Air Force\"\n }, \"GCSS-AF\"), \": Global Combat Support System \\u2013 Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Development Test\"\n }, \"GDT\"), \": Government Development Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Guidance for the Employment of the Force\"\n }, \"GEF\"), \": Guidance for the Employment of the Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Geosynchronous Earth Orbit\"\n }, \"GEO\"), \": Geosynchronous Earth Orbit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Furnished Equipment\"\n }, \"GFE\"), \": Government Furnished Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Furnished Information\"\n }, \"GFI\"), \": Government Furnished Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Force Management\"\n }, \"GFM\"), \": Global Force Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Furnished Property\"\n }, \"GFP\"), \": Government Furnished Property\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Hawk Ground Segment Modernization Program\"\n }, \"GH GSMP\"), \": Global Hawk Ground Segment Modernization Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Industry Data Exchange Program\"\n }, \"GIDEP\"), \": Government Industry Data Exchange Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Information Grid\"\n }, \"GIG\"), \": Global Information Grid\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Logistics Support Center\"\n }, \"GLSC\"), \": Global Logistics Support Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ground Movement Terrain Radar\"\n }, \"GMT\"), \": Ground Movement Terrain Radar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ground Moving Target Indicator\"\n }, \"GMTI\"), \": Ground Moving Target Indicator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Officer\"\n }, \"GO\"), \": General Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Officer\"\n }, \"GO\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Executive Service\"\n }, \"SES\"), \": General Officer/Senior Executive Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Owned Contractor Operated\"\n }, \"GOCO\"), \": Government Owned Contractor Operated\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Officer Steering Group\"\n }, \"GOSG\"), \": General Officer Steering Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Off-the-Shelf\"\n }, \"GOTS\"), \": Government Off-the-Shelf\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"GPS Pulse-per-Second Adapter\"\n }, \"GPA\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" Pulse-per-Second Adapter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purchase Card\"\n }, \"GPC\"), \": Government Purchase Card\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Purpose Decontaminant Program\"\n }, \"GPD\"), \": General Purpose Decontaminant Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purpose License Rights\"\n }, \"GPLR\"), \": Government Purpose License Rights\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Purpose Rights\"\n }, \"GPR\"), \": Government Purpose Rights\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System III Contingency Operations\"\n }, \"GPS III COps\"), \": Global Positioning System III Contingency Operations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System M-Code Early Use\"\n }, \"GPS MCEU\"), \": Global Positioning System M-Code Early Use\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military GPS User Equipment\"\n }, \"GPS MGUE\"), \": Military \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" User Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"GPS Next Generation Operational Control System\"\n }, \"GPS OCX\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" Next Generation Operational Control System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \": Global Positioning System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Schedule\"\n }, \"GS\"), \": General Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Government Services Administration\"\n }, \"GSA\"), \": Government Services Administration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ground Segment Modernization Program\"\n }, \"GSMP\"), \": Ground Segment Modernization Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Information Grid Technical Guidance Federation\"\n }, \"GTG-F\"), \": Global Information Grid Technical Guidance Federation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Theater Security Cooperative Management Information System\"\n }, \"G-TSCMIS\"), \": Global Theater Security Cooperative Management Information System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Guided Test Vehicle\"\n }, \"GTV\"), \": Guided Test Vehicle\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters Air Force\"\n }, \"HAF\"), \": Headquarters Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters Air Force Mission Directive\"\n }, \"HAFMD\"), \": Headquarters Air Force Mission Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardness Assurance, Maintenance, and Surveillance\"\n }, \"HAMS\"), \": Hardness Assurance\\nMaintenance\\nand Surveillance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(AGM-84-Fixed Wing; RGM-Surface Ships; UGM-Submarine Launched)\"\n }, \"HARPOON\"), \": (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Ground Missile\"\n }, \"AGM\"), \"-84-Fixed Wing; RGM-Surface Ships; UGM-Submarine Launched)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Head of Contracting Activity (or Agency)\"\n }, \"HCA\"), \": Head of Contracting Activity (or Agency)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Human-Computer Interactions\"\n }, \"HCI\"), \": Human-Computer Interactions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Human Capital Strategic Plan\"\n }, \"HCSP\"), \": Human Capital Strategic Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hypersonic Conventional Strike Weapon\"\n }, \"HCSW\"), \": Hypersonic Conventional Strike Weapon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hierarchical Data Format\"\n }, \"HDF\"), \": Hierarchical Data Format\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"High-Altitude Electromagnetic Pulse\"\n }, \"HEMP\"), \": High-Altitude Electromagnetic Pulse\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hazards of Electromagnetic Radiation to Volatile Material\"\n }, \"HERF\"), \": Hazards of Electromagnetic Radiation to Volatile Material\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hazards of Electromagnetic Radiation to Ordinance\"\n }, \"HERO\"), \": Hazards of Electromagnetic Radiation to Ordinance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hazards of Electromagnetic Radiation to Personnel\"\n }, \"HERP\"), \": Hazards of Electromagnetic Radiation to Personnel\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Human Factors Engineering\"\n }, \"HFE\"), \": Human Factors Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware in the Loop\"\n }, \"HITL\"), \": Hardware in the Loop\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardness Maintenance / Hardness Surveillance\"\n }, \"HM/HS\"), \": Hardness Maintenance / Hardness Surveillance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Handheld, Manpack, and Small Form Fit\"\n }, \"HMS\"), \": Handheld\\nManpack\\nand Small Form Fit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"HQ AFOTEC History Office\"\n }, \"HO\"), \": \", 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\"), \" History Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters Operating Instruction\"\n }, \"HOI\"), \": Headquarters Operating Instruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"High Performance Team\"\n }, \"HPT\"), \": High Performance Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \": Headquarters\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Human Systems Integration\"\n }, \"HSI\"), \": Human Systems Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"High Speed Network\"\n }, \"HSN\"), \": High Speed Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \": Health and Safety Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hard Target Munitions\"\n }, \"HTM\"), \": Hard Target Munitions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hard Target Void Sensing Fuze\"\n }, \"HTVSF\"), \": Hard Target Void Sensing Fuze\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware Assurance\"\n }, \"HwA\"), \": Hardware Assurance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Assurance (replaced by “cybersecurity”)\"\n }, \"IA\"), \": Information Assurance (replaced by \\u201Ccybersecurity\\u201D)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"International Armaments Cooperation\"\n }, \"IAC\"), \": International Armaments Cooperation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Air Defense\"\n }, \"IAD\"), \": Integrated Air Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Air Defense System\"\n }, \"IADS\"), \": Integrated Air Defense System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Aircrew Ensemble\"\n }, \"IAE\"), \": Integrated Aircrew Ensemble\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Air and Missile Defense\"\n }, \"IAMD\"), \": Integrated Air and Missile Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interim Authorization to Operate\"\n }, \"IATO\"), \": Interim Authorization to Operate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interim Authority to Test or Authorization to Test\"\n }, \"IATT\"), \": Interim Authority to Test or Authorization to Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Assurance Vulnerability Alert\"\n }, \"IAVA\"), \": Information Assurance Vulnerability Alert\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \": In Accordance With\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Involvement Briefing\"\n }, \"IB\"), \": Involvement Briefing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Individual Body Armor\"\n }, \"IBA\"), \": Individual Body Armor\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Involvement Bullet Background Paper\"\n }, \"IBBP\"), \": Involvement Bullet Background Paper\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Infantry Brigade Combat Team\"\n }, \"IBCT\"), \": Infantry Brigade Combat Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Base Defense Command and Control\"\n }, \"IBDC2\"), \": Integrated Base Defense Command and Control\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Base Defense Security System\"\n }, \"IBDSS\"), \": Integrated Base Defense Security System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Baseline Review\"\n }, \"IBR\"), \": Integrated Baseline Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Broadcast Service\"\n }, \"IBS\"), \": Integrated Broadcast Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Community\"\n }, \"IC\"), \": Intelligence Community\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Individual Combat Aircrew Display System\"\n }, \"ICADS\"), \": Individual Combat Aircrew Display System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intercontinental Ballistic Missile\"\n }, \"ICBM\"), \": Intercontinental Ballistic Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Community Capability Requirements\"\n }, \"ICCR\"), \": Intelligence Community Capability Requirements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \": Initial Capabilities Document OR Interface Control Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"initial Capability Development Document\"\n }, \"iCDD\"), \": initial Capability Development Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Independent Cost Estimate\"\n }, \"ICE\"), \": Independent Cost Estimate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Certification Evaluation Plan\"\n }, \"ICEP\"), \": Information Certification Evaluation Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interim Contractor Support\"\n }, \"ICM\"), \": Interim Contractor Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Inventory Control Point\"\n }, \"ICP\"), \": Inventory Control Point\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interim Contract Support\"\n }, \"ICS\"), \": Interim Contract Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Concept Team\"\n }, \"ICT\"), \": Integrated Concept Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Identification\"\n }, \"ID\"), \": Identification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Identification\"\n }, \"ID\"), \"/IQ: Indefinite Delivery/Indefinite Quantity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Data Environment\"\n }, \"IDE\"), \": Integrated Data Environment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Indentured Data List\"\n }, \"IDL\"), \": Indentured Data List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Data Requirements List\"\n }, \"IDRL\"), \": Integrated Data Requirements List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Evaluation Briefing\"\n }, \"IEB\"), \": Initial Evaluation Briefing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Improvised Explosive Device\"\n }, \"IED\"), \": Improvised Explosive Device\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Electronic Health Records\"\n }, \"iEHR\"), \": Integrated Electronic Health Records\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Exchange Requirements\"\n }, \"IER\"), \": Information Exchange Requirements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interactive Electronic Technical Manual\"\n }, \"IETM\"), \": Interactive Electronic Technical Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Functional Capability\"\n }, \"IFC\"), \": Integrated Functional Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intraflight Datalink\"\n }, \"IFDL\"), \": Intraflight Datalink\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence in Force Modernization\"\n }, \"IFM\"), \": Intelligence in Force Modernization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In-Flight Targeting Update\"\n }, \"IFTU\"), \": In-Flight Targeting Update\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Inherently Governmental Function\"\n }, \"IGF\"), \": Inherently Governmental Function\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Integrated Test Design\"\n }, \"IITD\"), \": Initial Integrated Test Design\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \": Involvement Letter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Life Cycle Management\"\n }, \"ILCM\"), \": Integrated Life Cycle Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Instrument Landing System OR Integrated Logistics Support\"\n }, \"ILS\"), \": Instrument Landing System OR Integrated Logistics Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Logistics Support Plan\"\n }, \"ILSP\"), \": Integrated Logistics Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Insensitive Munitions\"\n }, \"IM\"), \": Insensitive Munitions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Instrument Meteorological Conditions\"\n }, \"IMC\"), \": Instrument Meteorological Conditions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Mission Data\"\n }, \"IMD\"), \": Intelligence Mission Data\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Maintenance Data System\"\n }, \"IMDS\"), \": Integrated Maintenance Data System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"International Military Education and Training\"\n }, \"IMET\"), \": International Military Education and Training\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Master Plan\"\n }, \"IMP\"), \": Integrated Master Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Master Schedule\"\n }, \"IMS\"), \": Integrated Master Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Management Tool\"\n }, \"IMT\"), \": Information Management Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Master Test Plan\"\n }, \"IMTP\"), \": Integrated Master Test Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Increment\"\n }, \"INC\"), \": Increment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Inertial Navigation System\"\n }, \"INS\"), \": Inertial Navigation System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Operations\"\n }, \"IO\"), \": Information Operations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Capability\"\n }, \"IOC\"), \": Initial Operational Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \": Initial Operational Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E: Initial Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Protection OR Initial Point OR Intellectual Property OR Internet Protocol\"\n }, \"IP\"), \": Information Protection OR Initial Point OR Intellectual Property OR Internet Protocol\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Independent Program Assessment\"\n }, \"IPA\"), \": Independent Program Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Independent Program Assessment Team\"\n }, \"IPAT\"), \": Independent Program Assessment Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Priority List\"\n }, \"IPL\"), \": Integrated Priority List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Independent Program Management Report\"\n }, \"IPMR\"), \": Independent Program Management Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In-Process Review\"\n }, \"IPR\"), \": In-Process Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Program Summary OR Intellectual Property Strategy\"\n }, \"IPS\"), \": Integrated Program Summary OR Intellectual Property Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Provisioning Performance Specifications\"\n }, \"IPSS\"), \": Initial Provisioning Performance Specifications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Product Team\"\n }, \"IPT\"), \": Integrated Product Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Infrared\"\n }, \"IR\"), \": Infrared\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Independent Research and Development\"\n }, \"IRAD\"), \": Independent Research and Development\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Resources Board OR Investment Review Board\"\n }, \"IRB\"), \": Intelligence Resources Board OR Investment Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Infrared Countermeasures\"\n }, \"IRCM\"), \": Infrared Countermeasures\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information and Resource Support System\"\n }, \"IRSS\"), \": Information and Resource Support System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Infrared Search and Track System\"\n }, \"IRST\"), \": Infrared Search and Track System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System Capability Development Document\"\n }, \"IS CDD\"), \": Information System Capability Development Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System Initial Capabilities Document\"\n }, \"IS ICD\"), \": Information System Initial Capabilities Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \": Information System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"International Standardization Agreement\"\n }, \"ISA\"), \": International Standardization Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Systems Audit and Control Association\"\n }, \"ISACA\"), \": Information Systems Audit and Control Association\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"International Standards Organization\"\n }, \"ISO\"), \": International Standards Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Security Oversight Office\"\n }, \"ISOO\"), \": Information Security Oversight Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Support Plan\"\n }, \"ISP\"), \": Information Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Strategic Planning and Analysis Network\"\n }, \"ISPAN\"), \": Integrated Strategic Planning and Analysis Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence, Surveillance, and Reconnaissance OR Interim Summary Report\"\n }, \"ISR\"), \": Intelligence\\nSurveillance\\nand Reconnaissance OR Interim Summary Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System Security Manager\"\n }, \"ISSM\"), \": Information System Security Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Support Working Group\"\n }, \"ISWG\"), \": Intelligence Support Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology Lean\"\n }, \"IT Lean\"), \": Information Technology Lean\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \": Information Technology OR Integrated Testing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E: Integrated Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Space OR National Security Strategy OR National Security System\"\n }, \"NSS\"), \": Information Technology/National Security System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Interface Test Adapter\"\n }, \"ITA\"), \": Interface Test Adapter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology Acquisition Board\"\n }, \"ITAB\"), \": Information Technology Acquisition Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Concept\"\n }, \"ITC\"), \": Integrated Test Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \": Initial Test Design\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Threat Environment Assessment\"\n }, \"ITEA\"), \": Initial Threat Environment Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Tasking Order\"\n }, \"ITO\"), \": Initial Tasking Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Plan\"\n }, \"ITP\"), \": Integrated Test Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \": Integrated Test Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Item Unique Identification\"\n }, \"IUID\"), \": Item Unique Identification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Internal Use Software\"\n }, \"IUS\"), \": Internal Use Software\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Warfare\"\n }, \"IW\"), \": Information Warfare\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Internal Weapons Bay Upgrade\"\n }, \"IWBU\"), \": Internal Weapons Bay Upgrade\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Weapons System Management\"\n }, \"IWSM\"), \": Integrated Weapons System Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Justification and Approval\"\n }, \"J&A\"), \": Justification and Approval\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Staff J-8, Deputy Director for Requirements\"\n }, \"J-8/DDR\"), \": Joint Staff J-8\\nDeputy Director for Requirements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Staff J-8, Special Access Program Coordinator\"\n }, \"J-8/SAPCOORD\"), \": Joint Staff J-8\\nSpecial Access Program Coordinator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Air Force Army Navy\"\n }, \"JAFAN\"), \": Joint Air Force Army Navy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Air-to-Ground Missile\"\n }, \"JAGM\"), \": Joint Air-to-Ground Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Aerial Layered Network\"\n }, \"JALN\"), \": Joint Aerial Layered Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Aircraft Survivability Program\"\n }, \"JASP\"), \": Joint Aircraft Survivability Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Air-to-Surface Standoff Missile\"\n }, \"JASSM\"), \": Joint Air-to-Surface Standoff Missile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Avionics Workstation\"\n }, \"JAWS\"), \": Joint Avionics Workstation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \": Joint Biological Agent Decontamination System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Tactical Detection System\"\n }, \"JBTDS\"), \": Joint Biological Tactical Detection System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capability Area\"\n }, \"JCA\"), \": Joint Capability Area\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Improvised Explosive Device Defeat Capability Approval and Acquisition Management Process\"\n }, \"JCAAMP\"), \": Joint Improvised Explosive Device Defeat Capability Approval and Acquisition Management Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Computer-Aided Acquisition and Logistic Support\"\n }, \"JCALS\"), \": Joint Computer-Aided Acquisition and Logistic Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Board\"\n }, \"JCB\"), \": Joint Capabilities Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Cyber Command and Control\"\n }, \"JCC2\"), \": Joint Cyber Command and Control\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Combat Capability Assessment\"\n }, \"JCCA\"), \": Joint Combat Capability Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Document\"\n }, \"JCD\"), \": Joint Capabilities Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capabilities Integration and Development System\"\n }, \"JCIDS\"), \": Joint Capabilities Integration and Development System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint C4I Program Assessment Tool-Empowered\"\n }, \"JCPATE\"), \": Joint \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command, Control, Communications, Computers, and Intelligence\"\n }, \"C4I\"), \" Program Assessment Tool-Empowered\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Counter Radio-Controlled Improvised Explosive Device Electronic Warfare\"\n }, \"JCREW\"), \": Joint Counter Radio-Controlled Improvised Explosive Device Electronic Warfare\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Chiefs of Staff\"\n }, \"JCS\"), \": Joint Chiefs of Staff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capability Technology Demonstration\"\n }, \"JCTD\"), \": Joint Capability Technology Demonstration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Direct Attack Munition\"\n }, \"JDAM\"), \": Joint Direct Attack Munition\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Depot Maintenance Activities Group\"\n }, \"JDMAG\"), \": Joint Depot Maintenance Activities Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Deficiency Reporting System\"\n }, \"JDRS\"), \": Joint Deficiency Reporting System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Engineering Data Management Information and Combat System\"\n }, \"JEDMICS\"), \": Joint Engineering Data Management Information and Combat System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Effects Model\"\n }, \"JEM\"), \": Joint Effects Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Enterprise Network Manager\"\n }, \"JENM\"), \": Joint Enterprise Network Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Emergent Operational Need\"\n }, \"JEON\"), \": Joint Emergent Operational Need\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Functional Concept\"\n }, \"JFC\"), \": Joint Functional Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Functional Component Commander\"\n }, \"JFCC\"), \": Joint Functional Component Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Integrating Concept\"\n }, \"JIC\"), \": Joint Integrating Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interface Control Officer\"\n }, \"JICO\"), \": Joint Interface Control Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Intelligence Estimate\"\n }, \"JIE\"), \": Joint Intelligence Estimate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Improvised Explosive Device Defeat Fund\"\n }, \"JIEDDF\"), \": Joint Improvised Explosive Device Defeat Fund\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Improvised Explosive Device Defeat Organization\"\n }, \"JIEDDO\"), \": Joint Improvised Explosive Device Defeat Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interoperability Test Command\"\n }, \"JITC\"), \": Joint Interoperability Test Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Logistics Estimate\"\n }, \"JLE\"), \": Joint Logistics Estimate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Lessons Learned Program\"\n }, \"JLLP\"), \": Joint Lessons Learned Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Light Tactical Vehicle\"\n }, \"JLTV\"), \": Joint Light Tactical Vehicle\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Mission Computer\"\n }, \"JMC\"), \": Joint Mission Computer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Mission Environment Test Capability\"\n }, \"JMETC\"), \": Joint Mission Environment Test Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Miniature Munitions\"\n }, \"JMM\"), \": Joint Miniature Munitions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Space Operations Center (JSpOC) Mission System\"\n }, \"JMS\"), \": Joint Space Operations Center (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Space Operations Center\"\n }, \"JSpOC\"), \") Mission System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Mission Thread\"\n }, \"JMT\"), \": Joint Mission Thread\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Operating Concept\"\n }, \"JOC\"), \": Joint Operating Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Operational Medicine Information Systems\"\n }, \"JOMIS\"), \": Joint Operational Medicine Information Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Operations Concept\"\n }, \"JOpsC\"), \": Joint Operations Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"JSF Operational Test Team\"\n }, \"JOTT\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strike Fighter\"\n }, \"JSF\"), \" Operational Test Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \": Joint Publication\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Precision Approach and Landing System\"\n }, \"JPALS\"), \": Joint Precision Approach and Landing System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Potential Designator\"\n }, \"JPD\"), \": Joint Potential Designator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Personnel Estimate\"\n }, \"JPE\"), \": Joint Personnel Estimate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Planning Guidance\"\n }, \"JPG\"), \": Joint Planning Guidance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strike fighter Program Office\"\n }, \"JPO\"), \": Joint Strike fighter Program Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Rapid Acquisition Cell\"\n }, \"JRAC\"), \": Joint Rapid Acquisition Cell\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Reliability and Maintainability Evaluation Team\"\n }, \"JRMET\"), \": Joint Reliability and Maintainability Evaluation Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Requirements Office\"\n }, \"JRO\"), \": Joint Requirements Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Requirements Oversight Council\"\n }, \"JROC\"), \": Joint Requirements Oversight Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Requirements Oversight Council Memorandum\"\n }, \"JROCM\"), \": Joint Requirements Oversight Council Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Staff\"\n }, \"JS\"), \": Joint Staff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strategic Assessment\"\n }, \"JSA\"), \": Joint Strategic Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Service Aircrew Mask-Fixed Wing\"\n }, \"JSAM-FW\"), \": Joint Service Aircrew Mask-Fixed Wing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Service Aircrew Mask-Strategic Aircraft\"\n }, \"JSAM-SA\"), \": Joint Service Aircrew Mask-Strategic Aircraft\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Service Aircrew Mask-Tactical Aircraft\"\n }, \"JSAM-TA\"), \": Joint Service Aircrew Mask-Tactical Aircraft\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Staffing Designator\"\n }, \"JSD\"), \": Joint Staffing Designator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Simulation Environment\"\n }, \"JSE\"), \": Joint Simulation Environment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Sensitive Equipment Wipes (Decontamination Family of Systems)\"\n }, \"JSEW\"), \": Joint Sensitive Equipment Wipes (Decontamination Family of Systems)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strike Fighter\"\n }, \"JSF\"), \": Joint Strike Fighter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Special Access Program (SAP) Implementation Guide\"\n }, \"JSIG\"), \": Joint Special Access Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \") Implementation Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Stand-Off Weapon\"\n }, \"JSOW\"), \": Joint Stand-Off Weapon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Space Operations Center\"\n }, \"JSpOC\"), \": Joint Space Operations Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strategic Planning System\"\n }, \"JSPS\"), \": Joint Strategic Planning System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Strategy Review\"\n }, \"JSR\"), \": Joint Strategy Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interface Control Officer (JICO) Support System\"\n }, \"JSS\"), \": Joint Interface Control Officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interface Control Officer\"\n }, \"JICO\"), \") Support System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint System Threat Assessment Report\"\n }, \"JSTAR\"), \": Joint System Threat Assessment Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Surveillance Target Attack Radar System Recapitalization\"\n }, \"JSTARS RECAP\"), \": Joint Surveillance Target Attack Radar System Recapitalization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Test and Evaluation\"\n }, \"JT&E\"), \": Joint Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Terminal Attack Controller\"\n }, \"JTAC\"), \": Joint Terminal Attack Controller\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Tactical Radio\"\n }, \"JTR\"), \": Joint Tactical Radio\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Tactical Radio System\"\n }, \"JTRS\"), \": Joint Tactical Radio System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Tactical Radio System\"\n }, \"JTRS\"), \"-AMF: Joint Tactical Radio System-Airborne Maritime Fixed\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Urgent Operational Need\"\n }, \"JUON\"), \": Joint Urgent Operational Need\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint United States Forces Korea Portal and Integrated Threat Recognition\"\n }, \"JUPITR\"), \": Joint United States Forces Korea Portal and Integrated Threat Recognition\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Warning & Reporting Network\"\n }, \"JWARN\"), \": Joint Warning & Reporting Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Worldwide Intelligence Communications System\"\n }, \"JWICS\"), \": Joint Worldwide Intelligence Communications System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Decision Point\"\n }, \"KDP\"), \": Key Decision Point\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Interface Profile\"\n }, \"KIP\"), \": Key Interface Profile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Leadership Position\"\n }, \"KLP\"), \": Key Leadership Position\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Knowledge Management/Decision Support\"\n }, \"KM/DS\"), \": Knowledge Management/Decision Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Knowledge Now\"\n }, \"KN\"), \": Knowledge Now\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \": Key Performance Parameter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key System Attribute\"\n }, \"KSA\"), \": Key System Attribute\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lessons Learned\"\n }, \"L2\"), \": Lessons Learned\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics Assessment\"\n }, \"LA\"), \": Logistics Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lot Acceptance Test\"\n }, \"LAT\"), \": Lot Acceptance Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Long Band\"\n }, \"L-band\"), \": Long Band\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"HQ AFOTEC Legal Counsel\"\n }, \"LC\"), \": \", 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\"), \" Legal Counsel\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lower Confidence Bound\"\n }, \"LCB\"), \": Lower Confidence Bound\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Cost\"\n }, \"LCC\"), \": Life Cycle Cost\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Cost Estimate\"\n }, \"LCCE\"), \": Life Cycle Cost Estimate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Management Center\"\n }, \"LCMC\"), \": Life Cycle Management Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Management Plan\"\n }, \"LCMP\"), \": Life Cycle Management Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Risk Management\"\n }, \"LCRM\"), \": Life Cycle Risk Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Launch and Checkout System\"\n }, \"LCS\"), \": Launch and Checkout System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Sustainment Plan\"\n }, \"LCSP\"), \": Life Cycle Sustainment Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Limited Deployment OR Logistics Demonstration\"\n }, \"LD\"), \": Limited Deployment OR Logistics Demonstration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"LAN Data Collector\"\n }, \"LDC\"), \": LAN Data Collector\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lead Developmental Test Organization\"\n }, \"LDTO\"), \": Lead Developmental Test Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Light Emitting Diode\"\n }, \"LED\"), \": Light Emitting Diode\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Low Earth Orbit\"\n }, \"LEO\"), \": Low Earth Orbit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Extension Program\"\n }, \"LEP\"), \": Life Extension Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Limited Fielding Decision\"\n }, \"LFD\"), \": Limited Fielding Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live Fire Test and Evaluation\"\n }, \"LFT&E\"), \": Live Fire Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics Health Assessments\"\n }, \"LHA\"), \": Logistics Health Assessments\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Laser Joint Direct Attack Munition (GBU-56)\"\n }, \"LJDAM\"), \": Laser Joint Direct Attack Munition (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Guided Bomb Unit\"\n }, \"GBU\"), \"-56)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lockheed Martin\"\n }, \"LM\"), \": Lockheed Martin\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics MANPRINT Demonstration\"\n }, \"LMD\"), \": Logistics \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower and Personnel Integration\"\n }, \"MANPRINT\"), \" Demonstration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Mission Data Plan\"\n }, \"LMDP\"), \": Life Cycle Mission Data Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Late Network Entry\"\n }, \"LNE\"), \": Late Network Entry\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Liaison Officers\"\n }, \"LNO\"), \": Liaison Officers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Letter of Offer and Acceptance\"\n }, \"LOA\"), \": Letter of Offer and Acceptance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Level of Repair Analysis\"\n }, \"LORA\"), \": Level of Repair Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Line of Sight\"\n }, \"LOS\"), \": Line of Sight\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Limited Rights\"\n }, \"LR\"), \": Limited Rights\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Long Range Discrimination Radar\"\n }, \"LRDR\"), \": Long Range Discrimination Radar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Low Rate Initial Production\"\n }, \"LRIP\"), \": Low Rate Initial Production\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Long Range Standoff\"\n }, \"LRSO\"), \": Long Range Standoff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics Response Time\"\n }, \"LRT\"), \": Logistics Response Time\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Line-Replaceable Unit\"\n }, \"LRU\"), \": Line-Replaceable Unit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics Support Concept\"\n }, \"LSC\"), \": Logistics Support Concept\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lead Systems Engineer\"\n }, \"LSE\"), \": Lead Systems Engineer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Large Scale Integration OR Lead Systems Integrator\"\n }, \"LSI\"), \": Large Scale Integration OR Lead Systems Integrator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Last Test Event\"\n }, \"LTE\"), \": Last Test Event\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Logistics Test Working Group\"\n }, \"LTWG\"), \": Logistics Test Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Limited User Test\"\n }, \"LUT\"), \": Limited User Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \": Live\\nVirtual\\nand Constructive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \": Modeling and Simulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer\"\n }, \"CO\"), \": Modeling and Simulation Coordination Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Master Air Attack Plan\"\n }, \"MAAP\"), \": Master Air Attack Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Master Air Attack Planning Toolkit\"\n }, \"MAAPTK\"), \": Master Air Attack Planning Toolkit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Assurance Category\"\n }, \"MAC\"), \": Mission Assurance Category\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modular Air Crew Helmet\"\n }, \"MACH\"), \": Modular Air Crew Helmet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multifunction Advanced Data Link\"\n }, \"MADL\"), \": Multifunction Advanced Data Link\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mobility Air Forces-Dynamic Retasking Capability\"\n }, \"MAF-DRC\"), \": Mobility Air Forces-Dynamic Retasking Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mobility Air Force Automated Flight Planning Service\"\n }, \"MAFPS\"), \": Mobility Air Force Automated Flight Planning Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Automated Information System\"\n }, \"MAIS\"), \": Major Automated Information System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \": Major Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Miniature Air Launched Decoy-Jammer\"\n }, \"MALD-J\"), \": Miniature Air Launched Decoy-Jammer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Man Portable Air Defense System\"\n }, \"MANPAD\"), \": Man Portable Air Defense System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower and Personnel Integration\"\n }, \"MANPRINT\"), \": Manpower and Personnel Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modular Analysis and Test Support System\"\n }, \"MAnTSS\"), \": Modular Analysis and Test Support System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Monthly Acquisition Report\"\n }, \"MAR\"), \": Monthly Acquisition Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Maverick\"\n }, \"MAV\"), \": Maverick\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiband Inter/Intra Team Radio\"\n }, \"MBITR\"), \": Multiband Inter/Intra Team Radio\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Based Test Design\"\n }, \"MBTD\"), \": Mission Based Test Design\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Capable\"\n }, \"MC\"), \": Mission Capable\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Critical Functions\"\n }, \"MCF\"), \": Mission Critical Functions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Marine Corps Operational Test and Evaluation Activity\"\n }, \"MCOTEA\"), \": Marine Corps Operational Test and Evaluation Activity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Message Completion Rate\"\n }, \"MCR\"), \": Message Completion Rate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Directive\"\n }, \"MD\"), \": Mission Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone Decision Authority OR Missile Defense Agency\"\n }, \"MDA\"), \": Milestone Decision Authority OR Missile Defense Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Defense Acquisition Program\"\n }, \"MDAP\"), \": Major Defense Acquisition Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Maintenance Data Documentation OR Material Development Decision\"\n }, \"MDD\"), \": Maintenance Data Documentation OR Material Development Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Data File\"\n }, \"MDF\"), \": Mission Data File\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Design Series\"\n }, \"MDS\"), \": Mission Design Series\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mean Down Time\"\n }, \"MDT\"), \": Mean Down Time\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Maintenance Engineering/Sustaining Engineering\"\n }, \"ME/SE\"), \": Maintenance Engineering/Sustaining Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mechanical Subsystems Integrity Plan\"\n }, \"MECSIP\"), \": Mechanical Subsystems Integrity Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Engineering Data Asset Locator System\"\n }, \"MEDALS\"), \": Military Engineering Data Asset Locator System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Essential Functions List\"\n }, \"MEFL\"), \": Mission Essential Functions List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Medium Earth Orbit\"\n }, \"MEO\"), \": Medium Earth Orbit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower Estimate Report\"\n }, \"MER\"), \": Manpower Estimate Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Minimum Essential Subsystems List\"\n }, \"MESL\"), \": Minimum Essential Subsystems List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Equipment Valuation\"\n }, \"MEV\"), \": Military Equipment Valuation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Flight Operations Quality Assurance\"\n }, \"MFOQA\"), \": Military Flight Operations Quality Assurance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Force Program OR Materiel Fielding Plan\"\n }, \"MFP\"), \": Major Force Program OR Materiel Fielding Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum for Record\"\n }, \"MFR\"), \": Memorandum for Record\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multi-Functional Team\"\n }, \"MFT\"), \": Multi-Functional Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Grid Referencing System\"\n }, \"MGRS\"), \": Military Grid Referencing System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military GPS User Equipment Hand Held\"\n }, \"MGUE Inc 2 HH\"), \": Military \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" User Equipment Hand Held\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military GPS User Equipment\"\n }, \"MGUE\"), \": Military \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" User Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modular Handgun System\"\n }, \"MHS\"), \": Modular Handgun System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Megahertz\"\n }, \"MHz\"), \": Megahertz\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Detail (Specification)\"\n }, \"MIL-DTL\"), \":Military Detail (Specification)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Handbook\"\n }, \"MIL-HDBK\"), \":Military Handbook\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Performance (Specification)\"\n }, \"MIL-PRF\"), \":Military Performance (Specification)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Standard\"\n }, \"MIL-STD\"), \":Military Standard\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Materiel Improvement Program OR Military Intelligence Program\"\n }, \"MIP\"), \": Materiel Improvement Program OR Military Intelligence Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Interdepartmental Purchase Request\"\n }, \"MIPR\"), \": Military Interdepartmental Purchase Request\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Material Improvement Program Review Board\"\n }, \"MIPRB\"), \": Material Improvement Program Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiple Levels of Security\"\n }, \"MLS\"), \": Multiple Levels of Security\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions, Missiles, and Target\"\n }, \"MMT\"), \": Munitions\\nMissiles\\nand Target\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Needs Statement\"\n }, \"MNS\"), \": Mission Needs Statement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \": Memorandum of Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Management and Oversight of Acquisition Services Process\"\n }, \"MOASP\"), \": Management and Oversight of Acquisition Services Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \": Measure of Effectiveness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \": Measures of Effectiveness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \": Measure of Performance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Oriented Protective Posture\"\n }, \"MOPP\"), \": Mission Oriented Protective Posture\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \": Mission-Oriented Response Variables\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \": Measure of Suitability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modular Open Systems Approach\"\n }, \"MOSA\"), \": Modular Open Systems Approach\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \": Multiservice Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Understanding\"\n }, \"MOU\"), \": Memorandum of Understanding\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Profile\"\n }, \"MP\"), \": Mission Profile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manpower Authorization\"\n }, \"MPA\"), \": Manpower Authorization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Planning Element\"\n }, \"MPE\"), \": Mission Planning Element\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multipart GPS Pulse-per-Second Adapter\"\n }, \"MPGPA\"), \": Multipart \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" Pulse-per-Second Adapter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Master Program Schedule OR Mission Planning System\"\n }, \"MPS\"), \": Master Program Schedule OR Mission Planning System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Methods and Procedures Technical Order\"\n }, \"MPTO\"), \": Methods and Procedures Technical Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manufacturing Readiness Assessment\"\n }, \"MRA\"), \": Manufacturing Readiness Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Requirements Board\"\n }, \"MRB\"), \": Mission Requirements Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Man-Portable Radiological Detection System\"\n }, \"MRDS\"), \": Man-Portable Radiological Detection System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Manufacturing Readiness Level\"\n }, \"MRL\"), \": Manufacturing Readiness Level\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Depot Maintenance, Repair, and Overhaul Initiative\"\n }, \"MROi\"), \": Air Force Depot Maintenance\\nRepair\\nand Overhaul Initiative\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions Requirements Process\"\n }, \"MRP\"), \": Munitions Requirements Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Materiel Release Review\"\n }, \"MRR\"), \": Materiel Release Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Maintenance Requirement Review Board\"\n }, \"MRRB\"), \": Maintenance Requirement Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mobility Readiness Spares Package\"\n }, \"MRSP\"), \": Mobility Readiness Spares Package\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Range and Test Facility Base\"\n }, \"MRTFB\"), \": Major Range and Test Facility Base\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \": Milestone\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Materiel Solution Analysis\"\n }, \"MSA\"), \": Materiel Solution Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation Information Analysis Center\"\n }, \"MSIAC\"), \": Modeling and Simulation Information Analysis Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mean Sea Level\"\n }, \"MSL\"), \": Mean Sea Level\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation Support Plan\"\n }, \"MSSP\"), \": Modeling and Simulation Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mean Time Between Essential Function Failures\"\n }, \"MTBEFF\"), \": Mean Time Between Essential Function Failures\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mean Time To Repair\"\n }, \"MTTR\"), \": Mean Time To Repair\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Military Utility Assessment\"\n }, \"MUA\"), \": Military Utility Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mobile User Objective System\"\n }, \"MUOS\"), \": Mobile User Objective System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \": Measures Workshop\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Airborne Operations Center\"\n }, \"NAOC\"), \": National Airborne Operations Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Air and Space Intelligence Center\"\n }, \"NASIC\"), \": National Air and Space Intelligence Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"North Atlantic Treaty Organization\"\n }, \"NATO\"), \": North Atlantic Treaty Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Navigation Plan Tactical Pilotage Charts\"\n }, \"NAVPLAN TPC\"), \": Navigation Plan Tactical Pilotage Charts\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear, Biological and Chemical\"\n }, \"NBC\"), \": Nuclear\\nBiological and Chemical\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear Command and Control-Extremely Sensitive Information\"\n }, \"NC2-ESI\"), \": Nuclear Command and Control-Extremely Sensitive Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear Command, Control, Communications\"\n }, \"NC3\"), \": Nuclear Command\\nControl\\nCommunications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network-Centric Operations and Warfare\"\n }, \"NCOW\"), \": Network-Centric Operations and Warfare\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network-Centric Operations and Warfare\"\n }, \"NCOW\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \": Net-Centric Operations and Warfare Reference Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Defense Authorization Act\"\n }, \"NDAA\"), \": National Defense Authorization Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network Design Facility\"\n }, \"NDF\"), \": Network Design Facility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Developmental Item\"\n }, \"NDI\"), \": Non-Developmental Item\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Defense Strategy\"\n }, \"NDS\"), \": National Defense Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Environmental Policy Act\"\n }, \"NEPA\"), \": National Environmental Policy Act\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"New Equipment Training\"\n }, \"NET\"), \": New Equipment Training\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network Risk Assessment\"\n }, \"NetRA\"), \": Network Risk Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network Enabled Weapon\"\n }, \"NEW\"), \": Network Enabled Weapon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Next Generation Geosynchronous Earth Orbit (GEO)\"\n }, \"NGG\"), \": Next Generation Geosynchronous Earth Orbit (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Geosynchronous Earth Orbit\"\n }, \"GEO\"), \")\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Next Generation Polar\"\n }, \"NGP\"), \": Next Generation Polar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Geospatial-Intelligence Agency\"\n }, \"NGA\"), \": National Geospatial-Intelligence Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Guard Bureau\"\n }, \"NGB\"), \": National Guard Bureau\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Next Generation Chemical Detector\"\n }, \"NGCD\"), \": Next Generation Chemical Detector\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Next Generation Diagnostic System\"\n }, \"NGDS\"), \": Next Generation Diagnostic System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Guard and Reserve Equipment Account\"\n }, \"NGREA\"), \": National Guard and Reserve Equipment Account\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Government Standard (commercial)\"\n }, \"NGS\"), \": Non-Government Standard (commercial)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Interest Determination\"\n }, \"NID\"), \": National Interest Determination\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Intelligence Program\"\n }, \"NIP\"), \": National Intelligence Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \": Non-Secure Internet Protocol Router Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Industrial Security Program Operating Manual\"\n }, \"NISPOM\"), \": National Industrial Security Program Operating Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Institute of Standards and Technology\"\n }, \"NIST\"), \": National Institute of Standards and Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Kinetic Counter Electronics\"\n }, \"NKCE\"), \": Non-Kinetic Counter Electronics\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"No or Not Later Than\"\n }, \"NLT\"), \": No or Not Later Than\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network Management\"\n }, \"NM\"), \": Network Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Not Mission Capable\"\n }, \"NMC\"), \": Not Mission Capable\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Military Strategy\"\n }, \"NMS\"), \": National Military Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nonnuclear Munitions Safety Board\"\n }, \"NNMSB\"), \": Nonnuclear Munitions Safety Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Nuclear Security Administration\"\n }, \"NNSA\"), \": National Nuclear Security Administration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"No Operational Utility\"\n }, \"NOU\"), \": No Operational Utility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear Planning and Execution System Modernization\"\n }, \"NPES\"), \": Nuclear Planning and Execution System Modernization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Net-Ready Key Performance Parameter\"\n }, \"NR KPP\"), \": Net-Ready Key Performance Parameter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Recurring Engineering\"\n }, \"NRE\"), \": Non-Recurring Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Reconnaissance Office\"\n }, \"NRO\"), \": National Reconnaissance Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Agency\"\n }, \"NSA\"), \": National Security Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Near Strike Lightning\"\n }, \"NSL\"), \": Near Strike Lightning\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Stock Number\"\n }, \"NSN\"), \": National Stock Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Personnel System\"\n }, \"NSPS\"), \": National Security Personnel System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Space OR National Security Strategy OR National Security System\"\n }, \"NSS\"), \": National Security Space OR National Security Strategy OR National Security System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \": Nevada Test and Training Range\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear Weapons Council\"\n }, \"NWC\"), \": Nuclear Weapons Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nuclear Weapons Related Materiel\"\n }, \"NWRM\"), \": Nuclear Weapons Related Materiel\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operation and Maintenance\"\n }, \"O&M\"), \": Operation and Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operation and Support\"\n }, \"O&S\"), \": Operation and Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \": Operational Assessment OR Operational Availability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Advisory Group (USN/USMC)\"\n }, \"OAG\"), \": Operational Advisory Group (USN/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Marine Corps\"\n }, \"USMC\"), \")\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \": Open-Air Range\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating at Risk List\"\n }, \"OARL\"), \": Operating at Risk List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Aerospace Studies\"\n }, \"OAS\"), \": Office of Aerospace Studies\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office Assistant Secretary of Defense/Network and Information Integration\"\n }, \"OASD/NII\"), \": Office Assistant Secretary of Defense/Network and Information Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Offensive Anti-Surface Weapon\"\n }, \"OASuW\"), \": Offensive Anti-Surface Weapon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Capability\"\n }, \"OC\"), \": Operational Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Original Classification Authority\"\n }, \"OCA\"), \": Original Classification Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Occupational Specialty Code\"\n }, \"OCC\"), \": Occupational Specialty Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Capability Development Document\"\n }, \"OCDD\"), \": Operational Capability Development Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Concept of Employment\"\n }, \"OCE\"), \": Operational Concept of Employment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Collateral Responsibility OR Operational Capability Requirement\"\n }, \"OCR\"), \": Office of Collateral Responsibility OR Operational Capability Requirement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"GPS Next Generation Operational Control System\"\n }, \"OCX\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Global Positioning System\"\n }, \"GPS\"), \" Next Generation Operational Control System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Effectiveness OR Operational Environment\"\n }, \"OE\"), \": Operational Effectiveness OR Operational Environment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Original Equipment Manufacturer\"\n }, \"OEM\"), \": Original Equipment Manufacturer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency Evaluation Report\"\n }, \"OER\"), \": Operational Test Agency Evaluation Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Flight Program\"\n }, \"OFP\"), \": Operational Flight Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Flight Software\"\n }, \"OFS\"), \": Operational Flight Software\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Overarching Integrated Product Team\"\n }, \"OIPT\"), \": Overarching Integrated Product Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \": Operating Location\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Management and Budget\"\n }, \"OMB\"), \": Office of Management and Budget\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Outer Mold Line\"\n }, \"OML\"), \": Outer Mold Line\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Mission Summary OR Operational Mode Summary\"\n }, \"OMS\"), \": Operational Mission Summary OR Operational Mode Summary\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Need Date\"\n }, \"OND\"), \": Operational Need Date\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Overhead Persistent Infrared\"\n }, \"OPIR\"), \": Overhead Persistent Infrared\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Plan\"\n }, \"OPLAN\"), \": Operations Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Order\"\n }, \"OPORD\"), \": Operations Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Primary Responsibility\"\n }, \"OPR\"), \": Office of Primary Responsibility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Security\"\n }, \"OPSEC\"), \": Operations Security\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Tempo\"\n }, \"OPTEMPO\"), \": Operational Tempo\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test and Evaluation Force\"\n }, \"OPTEVFOR\"), \": Operational Test and Evaluation Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Requirements Document\"\n }, \"ORD\"), \": Operational Requirements Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Risk Management\"\n }, \"ORM\"), \": Operational Risk Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Suitability\"\n }, \"OS\"), \": Operational Suitability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \": Office of the Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Occupational Safety and Health Administration\"\n }, \"OSHA\"), \": Occupational Safety and Health Administration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Safety, Suitability, and Effectiveness\"\n }, \"OSS&E\"), \": Operational Safety\\nSuitability\\nand Effectiveness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \": Operational Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E: Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \": Operational Test Agency OR Other Transactions Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Over-the-Air Re-key\"\n }, \"OTAR\"), \": Over-the-Air Re-key\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Over Target Baseline\"\n }, \"OTB\"), \": Over Target Baseline\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Army Operational Test Command\"\n }, \"OTC\"), \": United States Army Operational Test Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open Technology Development\"\n }, \"OTD\"), \": Open Technology Development\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Training Infrastructure\"\n }, \"OTI\"), \": Operational Training Infrastructure\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Information Files\"\n }, \"OTIF\"), \": Operational Test Information Files\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Organization\"\n }, \"OTO\"), \": Operational Test Organization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Readiness Review\"\n }, \"OTRR\"), \": Operational Test Readiness Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Over Target Schedule\"\n }, \"OTS\"), \": Over Target Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility\"\n }, \"OU\"), \": Operational Utility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Assessment\"\n }, \"OUA\"), \": Operational Utility Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \": Operational Utility Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Under Secretary of Defense\"\n }, \"OUSD\"), \": Office of the Under Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational View (or Viewpoint)\"\n }, \"OV\"), \": Operational View (or Viewpoint)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Overseas Workload Program\"\n }, \"OWLP\"), \": Overseas Workload Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Production and Deployment (phase)\"\n }, \"P&D\"), \": Production and Deployment (phase)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Pre-Planned Product Improvement\"\n }, \"P3I\"), \": Pre-Planned Product Improvement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Partnering Arrangement OR Preparing Activity OR Preparing Authority OR Program Authorization ORPublic Affairs\"\n }, \"PA\"), \": Partnering Arrangement OR Preparing Activity OR Preparing Authority OR Program Authorization ORPublic Affairs\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Phased Adaptive Approach\"\n }, \"PAA\"), \": Phased Adaptive Approach\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Action Directive\"\n }, \"PAD\"), \": Program Action Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Pamphlet OR Performance Attributes Matrix\"\n }, \"PAM\"), \": Pamphlet OR Performance Attributes Matrix\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Presidential Aircraft Recapitalization OR Proposal Analysis Report\"\n }, \"PAR\"), \": Presidential Aircraft Recapitalization OR Proposal Analysis Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Personnel Accounting Symbol\"\n }, \"PAS\"), \": Personnel Accounting Symbol\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Production Acceptance Test and Evaluation\"\n }, \"PAT&E\"), \": Production Acceptance Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Acquisition Unit Cost\"\n }, \"PAUC\"), \": Program Acquisition Unit Cost\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"President’s Budget\"\n }, \"PB\"), \": President\\u2019s Budget\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Based Acquisition OR Performance Based Agreement\"\n }, \"PBA\"), \": Performance Based Acquisition OR Performance Based Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Portable Biological Containment Module\"\n }, \"PBCM\"), \": Portable Biological Containment Module\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Based Logistics\"\n }, \"PBL\"), \": Performance Based Logistics\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program/Budget Review\"\n }, \"PBR\"), \": Program/Budget Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Center\"\n }, \"PC\"), \": Product Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Control Chief\"\n }, \"PCC\"), \": Program Control Chief\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procuring Contracting Officer\"\n }, \"PCO\"), \": Procuring Contracting Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Director\"\n }, \"PD\"), \": Program Director\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Data Acquisition\"\n }, \"PDAQ\"), \": Product Data Acquisition\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Decision Memorandum OR Programmed Depot Maintenance\"\n }, \"PDM\"), \": Program Decision Memorandum OR Programmed Depot Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Preliminary Design Review\"\n }, \"PDR\"), \": Preliminary Design Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Element\"\n }, \"PE\"), \": Program Element\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Element Monitor\"\n }, \"PEM\"), \": Program Element Monitor\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \": Program Executive Office / Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Personnel Electrostatic Discharge\"\n }, \"PESD\"), \": Personnel Electrostatic Discharge\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Programmatic Environment, Safety, and Occupational Health Evaluation\"\n }, \"PESHE\"), \": Programmatic Environment\\nSafety\\nand Occupational Health Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Group\"\n }, \"PG\"), \": Product Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Procedures, Guidance, and Information\"\n }, \"PGI\"), \": Procedures\\nGuidance\\nand Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Guidance Letter\"\n }, \"PGL\"), \": Program Guidance Letter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Precision Guided Munitions OR Product Group Manager\"\n }, \"PGM\"), \": Precision Guided Munitions OR Product Group Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Packaging, Handling, Storage, and Transportation\"\n }, \"PHS&T\"), \": Packaging\\nHandling\\nStorage\\nand Transportation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Privacy Impact Assessment\"\n }, \"PIA\"), \": Privacy Impact Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Introduction Document\"\n }, \"PID\"), \": Program Introduction Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Personally Identifiable Information\"\n }, \"PII\"), \": Personally Identifiable Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Post-Implementation Review\"\n }, \"PIR\"), \": Post-Implementation Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Persistent Intelligence, Surveillance, and Reconnaissance\"\n }, \"PISR\"), \": Persistent Intelligence\\nSurveillance\\nand Reconnaissance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Platform Information Technology\"\n }, \"PIT\"), \": Platform Information Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Public Law\"\n }, \"PL\"), \": Public Law\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Position Location Information\"\n }, \"PLI\"), \": Position Location Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Lifecycle Management System\"\n }, \"PLMS\"), \": Product Lifecycle Management System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Position Location Recorder\"\n }, \"PLR\"), \": Position Location Recorder\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \": Program Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multi-Functional Team\"\n }, \"MFT\"), \": Program Management or Multi-Functional Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Management Agreement\"\n }, \"PMA\"), \": Program Management Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Measurement Baseline\"\n }, \"PMB\"), \": Performance Measurement Baseline\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Partially Mission Capable\"\n }, \"PMC\"), \": Partially Mission Capable\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Preventive Maintenance Checks and Services\"\n }, \"PMCS\"), \": Preventive Maintenance Checks and Services\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Management Directive\"\n }, \"PMD\"), \": Program Management Directive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Management Listing\"\n }, \"PML\"), \": Program Management Listing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Management Office\"\n }, \"PMO\"), \": Program Management Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Management Resource Tools\"\n }, \"PMRT\"), \": Program Management Resource Tools\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager‘s Tool\"\n }, \"PMT\"), \": Program Manager\\u2018s Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Presidential and National Voice Conferencing\"\n }, \"PNVC\"), \": Presidential and National Voice Conferencing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Office OR Project Officer\"\n }, \"PO\"), \": Program Office OR Project Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Plan of Action & Milestones\"\n }, \"POA&M\"), \": Plan of Action & Milestones\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \": Point of Contact\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Office Estimates\"\n }, \"POE\"), \": Program Office Estimates\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \": Program Objective Memorandum\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Maintenance\"\n }, \"POMx\"), \": Point of Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Probability of Program Success\"\n }, \"PoPS\"), \": Probability of Program Success\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program of Record\"\n }, \"PoR\"), \": Program of Record\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Pre-Operational Support\"\n }, \"POS\"), \": Pre-Operational Support\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Partial Operational Utility\"\n }, \"POU\"), \": Partial Operational Utility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Planning, Programming, Budgeting, and Execution\"\n }, \"PPBE\"), \": Planning\\nProgramming\\nBudgeting\\nand Execution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Programming Plan\"\n }, \"P-PLAN\"), \": Programming Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Programming Plans\"\n }, \"PPLANS\"), \": Programming Plans\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Protection Plan OR Public-Private Partnership\"\n }, \"PPP\"), \": Program Protection Plan OR Public-Private Partnership\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Pre-Production Qualification Test\"\n }, \"PPQT\"), \": Pre-Production Qualification Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Post-Publication Review\"\n }, \"PPR\"), \": Post-Publication Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Production Qualification Test\"\n }, \"PQT\"), \": Production Qualification Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Risk Assessment\"\n }, \"PRA\"), \": Performance Risk Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Portable Rugged Objected\"\n }, \"PRO\"), \": Portable Rugged Objected\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Production Readiness Review\"\n }, \"PRR\"), \": Production Readiness Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Support Business Case Analysis\"\n }, \"PS-BCA\"), \": Product Support Business Case Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Physical Security Equipment Action Group\"\n }, \"PSEAG\"), \": Physical Security Equipment Action Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Support Integrator\"\n }, \"PSI\"), \": Product Support Integrator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Propulsion Systems Integrity Program\"\n }, \"PSIP\"), \": Propulsion Systems Integrity Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Support Manager\"\n }, \"PSM\"), \": Product Support Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Support Management Plan\"\n }, \"PSMP\"), \": Product Support Management Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Publication Stock Number\"\n }, \"PSN\"), \": Publication Stock Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Product Support Provider\"\n }, \"PSP\"), \": Product Support Provider\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Preliminary Specification\"\n }, \"PSpec\"), \": Preliminary Specification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Support Review\"\n }, \"PSR\"), \": Program Support Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Protected Tactical Enterprise Services\"\n }, \"PTES\"), \": Protected Tactical Enterprise Services\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Participating Test Organization OR Preliminary Technical Order\"\n }, \"PTO\"), \": Participating Test Organization OR Preliminary Technical Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Protected Tactical SATCOM\"\n }, \"PTS\"), \": Protected Tactical \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Satellite Communications\"\n }, \"SATCOM\"), \"\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Precision Tracking Space System\"\n }, \"PTSS\"), \": Precision Tracking Space System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Project Viewpoint\"\n }, \"PV\"), \": Project Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Pilot Vehicle Interface\"\n }, \"PVI\"), \": Pilot Vehicle Interface\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Performance Work Statement\"\n }, \"PWS\"), \": Performance Work Statement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quadrennial Defense Review\"\n }, \"QDR\"), \": Quadrennial Defense Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quality of Service\"\n }, \"QoS\"), \": Quality of Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Qualification Operational Test and Evaluation\"\n }, \"QOT&E\"), \": Qualification Operational Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quick Reaction Capability\"\n }, \"QRC\"), \": Quick Reaction Capability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quick Reaction Fund\"\n }, \"QRF\"), \": Quick Reaction Fund\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quick Reference Guide\"\n }, \"QRG\"), \": Quick Reference Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Quick Reaction Instrumentation Package\"\n }, \"QRIP\"), \": Quick Reaction Instrumentation Package\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Qualification Test and Evaluation\"\n }, \"QT&E\"), \": Qualification Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Research and Development\"\n }, \"R&D\"), \": Research and Development\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability and Maintainability\"\n }, \"R&M\"), \": Reliability and Maintainability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Test\"\n }, \"R/T\"), \": Request for Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rapid Acquisition Authority OR Required Assets Available\"\n }, \"RAA\"), \": Rapid Acquisition Authority OR Required Assets Available\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radio Detection and Ranging\"\n }, \"RADAR\"), \": Radio Detection and Ranging\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Recorded Aircraft Information\"\n }, \"RAI\"), \": Recorded Aircraft Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \": Risk Assessment Level of Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability, Availability, and Maintainability\"\n }, \"RAM\"), \": Reliability\\nAvailability\\nand Maintainability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability, Availability, and Maintainability\"\n }, \"RAM\"), \"&C: Reliability\\nAvailability\\nMaintainability\\nand Cost\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability, Availability, Maintainability for Pods and Integrated Systems\"\n }, \"RAMPOD\"), \": Reliability\\nAvailability\\nMaintainability for Pods and Integrated Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability, Availability, Maintainability, and Supportability\"\n }, \"RAMS\"), \": Reliability\\nAvailability\\nMaintainability\\nand Supportability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rapid Analysis Processing Instrumentation Deployment System\"\n }, \"RAPIDS\"), \": Rapid Analysis Processing Instrumentation Deployment System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Recommended Changes\"\n }, \"RC\"), \": Recommended Changes\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Regulatory Contracting Approval\"\n }, \"RCA\"), \": Regulatory Contracting Approval\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability Centered Maintenance\"\n }, \"RCM\"), \": Reliability Centered Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Report Control Number\"\n }, \"RCN\"), \": Report Control Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Correlation Table\"\n }, \"RCT\"), \": Requirements Correlation Table\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Restricted Data\"\n }, \"RD\"), \": Restricted Data\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability Development/Growth Test\"\n }, \"RDGT\"), \": Reliability Development/Growth Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radiological Detection System OR Records Disposition Schedule\"\n }, \"RDS\"), \": Radiological Detection System OR Records Disposition Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Research, Development, Test and Evaluation\"\n }, \"RDT&E\"), \": Research\\nDevelopment\\nTest and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability and Maintainability Information System\"\n }, \"REMIS\"), \": Reliability and Maintainability Information System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Resource Enhancement Program\"\n }, \"REP\"), \": Resource Enhancement Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radio Frequency\"\n }, \"RF\"), \": Radio Frequency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radio Frequency Identification\"\n }, \"RFID\"), \": Radio Frequency Identification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \": Request for Proposal\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability Growth Curve\"\n }, \"RGC\"), \": Reliability Growth Curve\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Identification: Integration & -Ilities\"\n }, \"RI3\"), \": Risk Identification: Integration & -Ilities\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Remote Reconfigurable Intelligent Instrumentation to Control, Collect, Simulate and Stimulate\"\n }, \"RICS2\"), \": Remote Reconfigurable Intelligent Instrumentation to Control\\nCollect\\nSimulate and Stimulate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radioisotope Identification Detector\"\n }, \"RIID\"), \": Radioisotope Identification Detector\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rotary Launcher Assembly\"\n }, \"RLA\"), \": Rotary Launcher Assembly\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \": Reference Manual OR Risk Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reference Manual OR Risk Management\"\n }, \"RM\"), \"&A: Reliability\\nMaintainability and Availability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Management Certification Training\"\n }, \"RMCT\"), \": Requirements Management Certification Training\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Management Division\"\n }, \"RMD\"), \": Requirements Management Division\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Management Framework\"\n }, \"RMF\"), \": Risk Management Framework\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radar Modernization Program OR Risk Management Plan\"\n }, \"RMP\"), \": Radar Modernization Program OR Risk Management Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rough Order of Magnitude\"\n }, \"ROM\"), \": Rough Order of Magnitude\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Remotely Piloted Aircraft\"\n }, \"RPA\"), \": Remotely Piloted Aircraft\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Real Property Installed Equipment\"\n }, \"RPIE\"), \": Real Property Installed Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"RQ-4B Block 30 Multi-Spectral Intelligence\"\n }, \"RQ-4B Bk 30 MSI\"), \": RQ-4B Block 30 Multi-Spectral Intelligence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rifleman Radio\"\n }, \"RR\"), \": Rifleman Radio\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \": Requirements Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rapid Reaction Fund\"\n }, \"RRF\"), \": Rapid Reaction Fund\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Rapid Response Process\"\n }, \"RRP\"), \": Rapid Response Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radiated Susceptibility\"\n }, \"RS\"), \": Radiated Susceptibility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radar Signal Emulator\"\n }, \"RSE\"), \": Radar Signal Emulator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Strategy Review\"\n }, \"RSR\"), \": Requirements Strategy Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Real Time Kill Notification\"\n }, \"RTKN\"), \": Real Time Kill Notification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Radio Telephone Operator OR Ready for Transition to Operations ORResponsible Test Organization (now obsolete) OR Range Training Officer\"\n }, \"RTO\"), \": Radio Telephone Operator OR Ready for Transition to Operations ORResponsible Test Organization (now obsolete) OR Range Training Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reduction of Total Ownership Cost\"\n }, \"R-TOC\"), \": Reduction of Total Ownership Cost\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Readiness to Test\"\n }, \"RTT\"), \": Readiness to Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Science and Technology\"\n }, \"S&T\"), \": Science and Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Based Infrared Sys (SBIRS) Survivable and Endurable Evolution\"\n }, \"S2E2\"), \": Space Based Infrared Sys (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Based Infrared System\"\n }, \"SBIRS\"), \") Survivable and Endurable Evolution\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assistance OR Situational Awareness OR System Administrator\"\n }, \"SA\"), \": Security Assistance OR Situational Awareness OR System Administrator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Selective Availability Anti-Spoofing Module\"\n }, \"SAASM\"), \": Selective Availability Anti-Spoofing Module\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Service Acquisition Executive\"\n }, \"SAE\"), \": Service Acquisition Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \": Secretary of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/AQ: Assistant Secretary of the Air Force (Acquisition)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/AQX: Deputy Assistant Secretary for Acquisition Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Information Officer\"\n }, \"CIO\"), \" A6: Chief of Warfighting Integration and Chief Information Officer (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief Information Officer\"\n }, \"CIO\"), \")\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Financial Management OR Frequency Modulation OR Functional Manager\"\n }, \"FM\"), \": Assistant Secretary of the Air Force (Financial Management)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fully Mission Capable\"\n }, \"FMC\"), \": Deputy Assistant Secretary (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition System\"\n }, \"DAS\"), \") of the Air Force for Cost and Economics\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/GC: General Counsel of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/GCQ: Deputy General Counsel (Acquisition)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/IE: Assistant Secretary of the Air Force (Installations\\nEnvironment\\nand Logistics\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/IG: Inspector General of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/LL: Assistant Secretary of the Air Force (Legislative Affairs)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/US: Under Secretary of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/XC: Secretary of the Air Force Directorate (Warfighting Integration and Chief Information Officer)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Support Agreement Manager\"\n }, \"SAM\"), \": Support Agreement Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Single Acquisition Management Plan\"\n }, \"SAMP\"), \": Single Acquisition Management Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assistance Organizations\"\n }, \"SAO\"), \": Security Assistance Organizations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \": Security Assessment Plan OR Security Assistance Program OR Special Access Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Access Program Control Office\"\n }, \"SAPCO\"), \": Special Access Program Control Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Report OR Special Access Required OR Synthetic Aperture Radar OR System Assessment Report\"\n }, \"SAR\"), \": Security Assessment Report OR Special Access Required OR Synthetic Aperture Radar OR System Assessment Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Site Activation Task Force\"\n }, \"SATAF\"), \": Site Activation Task Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Satellite Communications\"\n }, \"SATCOM\"), \": Satellite Communications\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assistance Technical Order Program\"\n }, \"SATOP\"), \": Security Assistance Technical Order Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Small Business\"\n }, \"SB\"), \": Small Business\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Small Business Innovation Research\"\n }, \"SBIR\"), \": Small Business Innovation Research\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Based Infrared System\"\n }, \"SBIRS\"), \": Space Based Infrared System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Based Infrared System\"\n }, \"SBIRS\"), \" F/O: Space Based Infrared System Follow-on\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Smart Bomb Rack Assembly\"\n }, \"SBRA\"), \": Smart Bomb Rack Assembly\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Based Space Surveillance Follow-On\"\n }, \"SBSS F/O\"), \": Space Based Space Surveillance Follow-On\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Capabilities Document\"\n }, \"SCD\"), \": System Capabilities Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \": Security Classification Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sensitive Compartmented Information\"\n }, \"SCI\"), \": Sensitive Compartmented Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Supply Chain Manager\"\n }, \"SCM\"), \": Supply Chain Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Contracting Official\"\n }, \"SCO\"), \": Senior Contracting Official\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Service Cost Position\"\n }, \"SCP\"), \": Service Cost Position\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Supply Chain Risk Management\"\n }, \"SCRM\"), \": Supply Chain Risk Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Strike Common Weapon Data Link\"\n }, \"SCWDL\"), \": Strike Common Weapon Data Link\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standardization Document\"\n }, \"SD\"), \": Standardization Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Small Diameter Bomb\"\n }, \"SDB\"), \": Small Diameter Bomb\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Development and Demonstration\"\n }, \"SDD\"), \": System Development and Demonstration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Services Designated Official\"\n }, \"SDO\"), \": Services Designated Official\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Design Review\"\n }, \"SDR\"), \": System Design Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \": Safety OR Support Equipment OR Systems Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Automatic Test System\"\n }, \"ATS\"), \": Support Equipment/Automatic Test System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Suppression of Enemy Air Defenses\"\n }, \"SEAD\"), \": Suppression of Enemy Air Defenses\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Engineering Assessment Model\"\n }, \"SEAM\"), \": Systems Engineering Assessment Model\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SECAF\"), \": Secretary of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of Defense\"\n }, \"SECDEF\"), \": Secretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Software Engineering Institute\"\n }, \"SEI\"), \": Software Engineering Institute\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Spectrum Efficient National Surveillance Radar System\"\n }, \"SENSR\"), \": Spectrum Efficient National Surveillance Radar System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Evaluation Plan OR Systems Engineering Plan\"\n }, \"SEP\"), \": System Evaluation Plan OR Systems Engineering Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Support Equipment Recommendation Data\"\n }, \"SERD\"), \": Support Equipment Recommendation Data\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Executive Service\"\n }, \"SES\"), \": Senior Executive Service\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Selected Essential Item Stockage for Availability Methodology\"\n }, \"SESAME\"), \": Selected Essential Item Stockage for Availability Methodology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Forces OR Standard Form\"\n }, \"SF\"), \": Security Forces OR Standard Form\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Small Form Fit\"\n }, \"SFF\"), \": Small Form Fit\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Functional Review\"\n }, \"SFR\"), \": System Functional Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Information Assurance Official\"\n }, \"SIAO\"), \": Senior Information Assurance Official\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Signals Intelligence\"\n }, \"SIGINT\"), \": Signals Intelligence\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Interest Item\"\n }, \"SII\"), \": Special Interest Item\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Serialized Item Management\"\n }, \"SIM\"), \": Serialized Item Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Simulation and Analysis Facility\"\n }, \"SIMAF\"), \": Simulation and Analysis Facility\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Simulator Certification\"\n }, \"SIMCERT\"), \": Simulator Certification\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Simulator Validation\"\n }, \"SIMVAL\"), \": Simulator Validation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Intelligence Officer\"\n }, \"SIO\"), \": Senior Intelligence Officer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Single Integrated Operational Plan-Extremely Sensitive Information\"\n }, \"SIOP-ESI\"), \": Single Integrated Operational Plan-Extremely Sensitive Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Identification Profile OR System Information Profile\"\n }, \"SIP\"), \": System Identification Profile OR System Information Profile\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Service Intelligence Production Centers\"\n }, \"SIPC\"), \": Service Intelligence Production Centers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secret Internet Protocol Router Network\"\n }, \"SIPRNET\"), \": Secret Internet Protocol Router Network\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security, Interoperability, Supportability, Sustainability, and Usability\"\n }, \"SISSU\"), \": Security\\nInteroperability\\nSupportability\\nSustainability\\nand Usability\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Situational Report\"\n }, \"SITREP\"), \": Situational Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Service Level Agreements\"\n }, \"SLA\"), \": Service Level Agreements\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standoff Land Attack Missile Expanded Response\"\n }, \"SLAM-ER\"), \": Standoff Land Attack Missile Expanded Response\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Service Life Extension Program\"\n }, \"SLEP\"), \": Service Life Extension Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sub-Line Item Number\"\n }, \"SLIN\"), \": Sub-Line Item Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Manager OR Service Manager OR Single Manager\"\n }, \"SM\"), \": Security Manager OR Service Manager OR Single Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Science, Mathematics, And Research For Transformation OR System Metrics and Reporting Tool\"\n }, \"SMART\"), \": Science\\nMathematics\\nAnd Research For Transformation OR System Metrics and Reporting Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space and Missile Systems Center\"\n }, \"SMC\"), \": Space and Missile Systems Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Single Manager for Conventional Ammunition\"\n }, \"SMCA\"), \": Single Manager for Conventional Ammunition\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \": Subject Matter Expert\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Soldier-Machine Interface\"\n }, \"SMI\"), \": Soldier-Machine Interface\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Maturity Matrix\"\n }, \"SMM\"), \": System Maturity Matrix\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standardized Operations Center Remotely Piloted Aircraft\"\n }, \"SOC RPA\"), \": Standardized Operations Center Remotely Piloted Aircraft\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Statement of Capabilities\"\n }, \"SOC\"), \": Statement of Capabilities\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Operations Command\"\n }, \"SOCOM\"), \": Special Operations Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Operations Forces\"\n }, \"SOF\"), \": Special Operations Forces\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Statement of Intent\"\n }, \"SOI\"), \": Statement of Intent\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Statement of Objectives\"\n }, \"SOO\"), \": Statement of Objectives\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Operations-Peculiar\"\n }, \"SO-P\"), \": Special Operations-Peculiar\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source of Repair\"\n }, \"SOR\"), \": Source of Repair\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source of Repair Assignment\"\n }, \"SORA\"), \": Source of Repair Assignment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source of Repair Assignment Process\"\n }, \"SORAP\"), \": Source of Repair Assignment Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System of Record Notice\"\n }, \"SORN\"), \": System of Record Notice\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Speed of Service OR System of Systems\"\n }, \"SoS\"), \": Speed of Service OR System of Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sufficiency of Operational Test Review OR Sufficiency of Test Report\"\n }, \"SOTR\"), \": Sufficiency of Operational Test Review OR Sufficiency of Test Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Special Operations Wing OR Statement of Work\"\n }, \"SOW\"), \": Special Operations Wing OR Statement of Work\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Plan OR Special Publication\"\n }, \"SP\"), \": Security Plan OR Special Publication\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Single Point Adjustment\"\n }, \"SPA\"), \": Single Point Adjustment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Director\"\n }, \"SPD\"), \": System Program Director\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Procurement Executive\"\n }, \"SPE\"), \": Senior Procurement Executive\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Strategic Planning Guidance\"\n }, \"SPG\"), \": Strategic Planning Guidance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Manager\"\n }, \"SPM\"), \": System Program Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sustainment Program Master List\"\n }, \"SPML\"), \": Sustainment Program Master List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \": System Program Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Operations Command\"\n }, \"SpOC\"), \": Space Operations Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Planning Team\"\n }, \"SPT\"), \": Systems Planning Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Structured Query Language\"\n }, \"SQL\"), \": Structured Query Language\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Schedule Risk Assessment\"\n }, \"SRA\"), \": Schedule Risk Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety Review Board\"\n }, \"SRB\"), \": Safety Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Software or Systems Requirements Document\"\n }, \"SRD\"), \": Software or Systems Requirements Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Requirements Review OR Systems Readiness Review\"\n }, \"SRR\"), \": System Requirements Review OR Systems Readiness Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Soldier Radio Waveform\"\n }, \"SRW\"), \": Soldier Radio Waveform\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source Selection Authority\"\n }, \"SSA\"), \": Source Selection Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Security Authorization Agreement\"\n }, \"SSAA\"), \": Systems Security Authorization Agreement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Situational Awareness-Environmental Monitoring\"\n }, \"SSAEM\"), \": Space Situational Awareness-Environmental Monitoring\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source Selection Decision\"\n }, \"SSD\"), \": Source Selection Decision\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source Selection Decision Document\"\n }, \"SSDD\"), \": Source Selection Decision Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Security Engineering\"\n }, \"SSE\"), \": Systems Security Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source Selection Evaluation Team\"\n }, \"SSET\"), \": Source Selection Evaluation Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Sustainment Manager\"\n }, \"SSM\"), \": System Sustainment Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Social Security Number\"\n }, \"SSN\"), \": Social Security Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standard Surveillance Operating Manual\"\n }, \"SSOM\"), \": Standard Surveillance Operating Manual\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Strategic Source of Repair\"\n }, \"SSOR\"), \": Strategic Source of Repair\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Source Selection Plan OR System Support Package\"\n }, \"SSP\"), \": Source Selection Plan OR System Support Package\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Staff Summary Sheet\"\n }, \"SSS\"), \": Staff Summary Sheet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Security Working Group\"\n }, \"SSWG\"), \": Systems Security Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Threat Analysis OR System Threat Assessment\"\n }, \"STA\"), \": System Threat Analysis OR System Threat Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Threat Assessment Report\"\n }, \"STAR\"), \": System Threat Assessment Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Training and Readiness Command\"\n }, \"STARCOM\"), \": Space Training and Readiness Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Scientific Test and Analysis Techniques\"\n }, \"STAT\"), \": Scientific Test and Analysis Techniques\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standards Viewpoint\"\n }, \"StdV\"), \": Standards Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Standard for Exchange of Product\"\n }, \"STEP\"), \": Standard for Exchange of Product\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Technical Implementation Guide\"\n }, \"STIG\"), \": Security Technical Implementation Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Scientific and Technical Information\"\n }, \"STINFO\"), \": Scientific and Technical Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Space Test Program OR System Training Plan\"\n }, \"STP\"), \": Space Test Program OR System Training Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sea Test Range\"\n }, \"STR\"), \": Sea Test Range\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Strategy-To-Task\"\n }, \"STT\"), \": Strategy-To-Task\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Small Business Technology Transfer\"\n }, \"STTR\"), \": Small Business Technology Transfer\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \": System Under Test\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System View\"\n }, \"SV\"), \": System View\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Survivability, Vulnerability, and Assessment Directorate\"\n }, \"SVAD\"), \": Survivability\\nVulnerability\\nand Assessment Directorate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Services Viewpoint\"\n }, \"SvcV\"), \": Services Viewpoint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Verification Review\"\n }, \"SVR\"), \": System Verification Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Software Assurance\"\n }, \"SwA\"), \": Software Assurance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Systems Command\"\n }, \"SYSCOM\"), \": Systems Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Integrated Test Team\"\n }, \"T&E ITT\"), \": Test and Evaluation Integrated Test Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \": Test and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \": Technical Advisor OR Test Area\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Airworthiness Authority\"\n }, \"TAA\"), \": Technical Airworthiness Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Checkout\"\n }, \"TACO\"), \": Test and Checkout\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Air Control Party\"\n }, \"TACP\"), \": Tactical Air Control Party\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Air Control Party\"\n }, \"TACP\"), \"-M: Tactical Air Control Party-Modernization\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Automated Security System\"\n }, \"TASS\"), \": Tactical Automated Security System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"To Be Determined\"\n }, \"TBD\"), \": To Be Determined\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"TRADOC Capabilities Manager-Tactical Radios\"\n }, \"TCM-TR\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Training and Doctrine Command (US Army)\"\n }, \"TRADOC\"), \" Capabilities Manager-Tactical Radios\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessment\"\n }, \"TCRA\"), \": test capability readiness assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessments\"\n }, \"TCRAs\"), \": test capability readiness assessments\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Total Contract Training\"\n }, \"TCT\"), \": Total Contract Training\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Time Compliance Technical Order\"\n }, \"TCTO\"), \": Time Compliance Technical Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \": Test Director OR Technical Director OR Technology Development OR Technology Director\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"&E: Tactics Development and Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \": Test Design Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Data Package\"\n }, \"TDP\"), \": Technical Data Package\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Requirement\"\n }, \"TDR\"), \": Test Design Requirement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Development Strategy\"\n }, \"TDS\"), \": Technology Development Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Data Scoring Board\"\n }, \"TDSB\"), \": Test Data Scoring Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Temporary Duty\"\n }, \"TDY\"), \": Temporary Duty\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \": Technical Editor OR Test Evaluation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Text Element Identifiers\"\n }, \"TEI\"), \": Text Element Identifiers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \": Test and Evaluation Master Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Transient Electromagnetic Pulse Surveillance Technology\"\n }, \"TEMPEST\"), \": Transient Electromagnetic Pulse Surveillance Technology\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Executive Officers\"\n }, \"TEO\"), \": Technology Executive Officers\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Strategy\"\n }, \"TES\"), \": Test and Evaluation Strategy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Total Force Integration\"\n }, \"TFI\"), \": Total Force Integration\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Investment Planning and Programming\"\n }, \"TIPP\"), \": Test Investment Planning and Programming\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Integrated Product Team\"\n }, \"TIPT\"), \": Test Integrated Product Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Incident Report\"\n }, \"TIR\"), \": Test Incident Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Information Sheet\"\n }, \"TIS\"), \": Test Information Sheet\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tailored Information Support Plan\"\n }, \"TISP\"), \": Tailored Information Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tail Kit Assembly\"\n }, \"TKA\"), \": Tail Kit Assembly\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Target Location, Designation, and Hand-Off System\"\n }, \"TLDHS\"), \": Target Location\\nDesignation\\nand Hand-Off System\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Target Location Error\"\n }, \"TLE\"), \": Target Location Error\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Manual OR Telemetry OR Test Manager\"\n }, \"TM\"), \": Technical Manual OR Telemetry OR Test Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Manual Contract Requirement\"\n }, \"TMCR\"), \": Technical Manual Contract Requirement\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Measurement Diagnostic Equipment\"\n }, \"TMDE\"), \": Test Measurement Diagnostic Equipment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Theater Medical Information Program-Joint\"\n }, \"TMIPJ\"), \": Theater Medical Information Program-Joint\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Triple Missile Launcher Adapter\"\n }, \"TMLA\"), \": Triple Missile Launcher Adapter\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Maturation & Risk Reduction (phase)\"\n }, \"TMRR\"), \": Technology Maturation & Risk Reduction (phase)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Manual Specifications and Standards\"\n }, \"TMSS\"), \": Technical Manual Specifications and Standards\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Task Management Tool\"\n }, \"TMT\"), \": Task Management Tool\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Total Not Mission Capable-Maintenance\"\n }, \"TNMCM\"), \": Total Not Mission Capable-Maintenance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Total Not Mission Capable-Supply\"\n }, \"TNMCS\"), \": Total Not Mission Capable-Supply\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \": Tasking Order OR Technical Order\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Total Obligation Authority\"\n }, \"TOA\"), \": Total Obligation Authority\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Order Advisory Council\"\n }, \"TOAC\"), \": Technical Order Advisory Council\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"\n }, \"TOC\"), \": Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Order Distribution Office\"\n }, \"TODO\"), \": Technical Order Distribution Office\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Order Management Agency\"\n }, \"TOMA\"), \": Technical Order Management Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Program Case File\"\n }, \"TPCF\"), \": Test Program Case File\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Performance Measure OR Test Program Management\"\n }, \"TPM\"), \": Technical Performance Measure OR Test Program Management\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Protection Plan\"\n }, \"TPP\"), \": Technology Protection Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Program Set\"\n }, \"TPS\"), \": Test Program Set\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Training Planning Team\"\n }, \"TPT\"), \": Training Planning Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Plan Working Group\"\n }, \"TPWG\"), \": Test Plan Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Review\"\n }, \"TR\"), \": Technical Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Readiness Assessment\"\n }, \"TRA\"), \": Technology Readiness Assessment\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Training and Doctrine Command (US Army)\"\n }, \"TRADOC\"), \": Training and Doctrine Command (US Army)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Review Board\"\n }, \"TRB\"), \": Technical Review Board\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Requirements Document\"\n }, \"TRD\"), \": Technical Requirements Document\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Readiness Level\"\n }, \"TRL\"), \": Technology Readiness Level\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \": Technology Reference Model OR Test Resource Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Management Center\"\n }, \"TRMC\"), \": Test Resource Management Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \": Test Resource Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \": Test Readiness Review\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Squadron OR Top Secret\"\n }, \"TS\"), \": Test Squadron OR Top Secret\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Trusted Systems & Networks\"\n }, \"TSN\"), \": Trusted Systems & Networks\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Support Plan OR Transfer Support Plan OR Transition Support Plan\"\n }, \"TSP\"), \": Test Support Plan OR Transfer Support Plan OR Transition Support Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Squadron OR Top Secret\"\n }, \"TS\"), \"-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Precision Guided Munitions OR Product Group Manager\"\n }, \"PGM\"), \": Training System Product Group Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Time / Space / Position Information\"\n }, \"TSPI\"), \": Time / Space / Position Information\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Training System Requirements Analysis\"\n }, \"TSRA\"), \": Training System Requirements Analysis\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Threat Systems Working Group\"\n }, \"TSWG\"), \": Threat Systems Working Group\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"The Technology Cooperation Program\"\n }, \"TTCP\"), \": The Technology Cooperation Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactics, Techniques, and Procedures OR Technology Transition Plan\"\n }, \"TTP\"), \": Tactics\\nTechniques\\nand Procedures OR Technology Transition Plan\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical View\"\n }, \"TV\"), \": Technical View\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Wing\"\n }, \"TW\"), \": Test Wing\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Universal Armament\"\n }, \"UAI\"), \": Universal Armament\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unmanned Aerial Systems\"\n }, \"UAS\"), \": Unmanned Aerial Systems\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unmanned Aerial Vehicle\"\n }, \"UAV\"), \": Unmanned Aerial Vehicle\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unified Capabilities\"\n }, \"UC\"), \": Unified Capabilities\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Undefinitized Contract Action\"\n }, \"UCA\"), \": Undefinitized Contract Action\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unified Combatant Commander\"\n }, \"UCC\"), \": Unified Combatant Commander\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Ultra-High Frequency\"\n }, \"UHF\"), \": Ultra-High Frequency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unique Identification number\"\n }, \"UID\"), \": Unique Identification number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unfavorable Information File\"\n }, \"UIF\"), \": Unfavorable Information File\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unique Item Identifier\"\n }, \"UII\"), \": Unique Item Identifier\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Uniform Integrated Protection Ensemble\"\n }, \"UIPE\"), \": Uniform Integrated Protection Ensemble\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Universal Joint Task List\"\n }, \"UJTL\"), \": Universal Joint Task List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Underwater Locator Beacon\"\n }, \"ULB\"), \": Underwater Locator Beacon\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unliquidated Obligation\"\n }, \"ULO\"), \": Unliquidated Obligation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Urgent Operational Need\"\n }, \"UON\"), \": Urgent Operational Need\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"US Operational Test Team\"\n }, \"UOTT\"), \": US Operational Test Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unified Platform\"\n }, \"UP\"), \": Unified Platform\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"User Representative Agency\"\n }, \"URA\"), \": User Representative Agency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Uniform Resource Locator\"\n }, \"URL\"), \": Uniform Resource Locator\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Unit Reference Number\"\n }, \"URN\"), \": Unit Reference Number\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \": United States Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force Warfare Center\"\n }, \"USAFWC\"), \": United States Air Force Warfare Center\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Universal Serial Bus\"\n }, \"USB\"), \": Universal Serial Bus\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Code\"\n }, \"USC\"), \": United States Code\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \": Undersecretary of Defense\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Under Secretary of the Air Force\"\n }, \"USecAF\"), \": Under Secretary of the Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Marine Corps\"\n }, \"USMC\"), \": United States Marine Corps\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Space Force\"\n }, \"USSF\"), \": United States Space Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"U.S. Special Operations Command\"\n }, \"USSOCOM\"), \": U.S. Special Operations Command\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Coordinated Universal Time\"\n }, \"UTC\"), \": Coordinated Universal Time\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Utah Test and Training Range\"\n }, \"UTTR\"), \": Utah Test and Training Range\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \": Verification and Validation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Chairman of the Joint Chiefs of Staff\"\n }, \"VCJCS\"), \": Vice Chairman of the Joint Chiefs of Staff\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Chief of Staff of the United States Air Force\"\n }, \"VCSAF\"), \": Vice Chief of Staff of the United States Air Force\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vice Chief of Space Operations\"\n }, \"VCSO\"), \": Vice Chief of Space Operations\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Value Engineering\"\n }, \"VE\"), \": Value Engineering\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Value Engineering Change Proposal\"\n }, \"VECP\"), \": Value Engineering Change Proposal\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Value Engineering Proposal\"\n }, \"VEP\"), \": Value Engineering Proposal\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Very High Frequency\"\n }, \"VHF\"), \": Very High Frequency\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Documentation\"\n }, \"VIDOC\"), \": Visual Information Documentation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Information Manager\"\n }, \"VIM\"), \": Visual Information Manager\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Visual Meteorological Conditions\"\n }, \"VMC\"), \": Visual Meteorological Conditions\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vulnerable to Move List\"\n }, \"VML\"), \": Vulnerable to Move List\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Vulnerability Management Process\"\n }, \"VMP\"), \": Vulnerability Management Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Validated Online Lifecycle Threat\"\n }, \"VOLT\"), \": Validated Online Lifecycle Threat\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Virtual Prime Vendor\"\n }, \"VPV\"), \": Virtual Prime Vendor\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification Status Page\"\n }, \"VSP\"), \": Verification Status Page\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Virtual System Threat Assessment Report\"\n }, \"VSTAR\"), \": Virtual System Threat Assessment Report\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Video Teleconference\"\n }, \"VTC\"), \": Video Teleconference\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \": Verification\\nValidation and Accreditation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Wide Area Surveillance\"\n }, \"WAS\"), \": Wide Area Surveillance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Wide Area Workflow\"\n }, \"WAWF\"), \": Wide Area Workflow\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Work Breakdown Schedule\"\n }, \"WBS\"), \": Work Breakdown Schedule\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Working Capital Fund\"\n }, \"WCF\"), \": Working Capital Fund\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Working\\x1ELevel Integrated Product Team\"\n }, \"WIPT\"), \": Working\\x1ELevel Integrated Product Team\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Watch Item Tracking\"\n }, \"WIT\"), \": Watch Item Tracking\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Warfighting Mission Area\"\n }, \"WMA\"), \": Warfighting Mission Area\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"weapons of mass destruction\"\n }, \"WMD\"), \": weapons of mass destruction\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Warfighter Rapid Acquisition Process\"\n }, \"WRAP\"), \": Warfighter Rapid Acquisition Process\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapons Storage and Security System Service Life Extension Program\"\n }, \"WS3 SLEP\"), \": Weapons Storage and Security System Service Life Extension Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapon System Evaluation Program\"\n }, \"WSEP\"), \": Weapon System Evaluation Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapon System Enterprise Reviews\"\n }, \"WSER\"), \": Weapon System Enterprise Reviews\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weather Satellite Follow-on Electro-Optical /Infra-Red\"\n }, \"WSF-EO/IR\"), \": Weather Satellite Follow-on Electro-Optical /Infra-Red\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weather Satellite Follow-on Microwave\"\n }, \"WSF-M\"), \": Weather Satellite Follow-on Microwave\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapon System Integration OR Weapon System Integrity\"\n }, \"WSI\"), \": Weapon System Integration OR Weapon System Integrity\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapon System Integrity Guide\"\n }, \"WSIG\"), \": Weapon System Integrity Guide\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapon System Integrity Program\"\n }, \"WSIP\"), \": Weapon System Integrity Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"White Sands Missile Range\"\n }, \"WSMR\"), \": White Sands Missile Range\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weapons System Support Program\"\n }, \"WSSP\"), \": Weapons System Support Program\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Weather\"\n }, \"WX\"), \": Weather\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Extended Data Rate\"\n }, \"XDR\"), \": Extended Data Rate\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Year to Date\"\n }, \"YTD\"), \": Year to Date\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"acronyms.md"},"frontmatter":{"metaTitle":"Acronyms","metaDescription":"Acronyms"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"3c246e82-b17b-5afa-aacd-40f5e182c186"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/1-2-OVERVIEW/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/1-2-OVERVIEW/page-data.json new file mode 100644 index 00000000..c7db133d --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/1-2-OVERVIEW/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/1-2-OVERVIEW","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ca790f90-c311-5139-ae34-e49884cbd5aa","title":"OVERVIEW","slug":"/analyst_test_design_guide/1-2-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\": \"OVERVIEW\",\n \"metaTitle\": \"OVERVIEW\",\n \"metaDescription\": \"OVERVIEW\"\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(\"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\": \"742px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/9bb00d4f6f07179b37c87073f951944c/24ee3/image1.jpg\",\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\": \"71.42857142857143%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/jpeg;base64,/9j/2wBDABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVGC8aGi9jQjhCY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2P/wgARCAAOABQDASIAAhEBAxEB/8QAGAAAAgMAAAAAAAAAAAAAAAAAAAECAwX/xAAUAQEAAAAAAAAAAAAAAAAAAAAA/9oADAMBAAIQAxAAAAHcFEtEH//EABkQAAIDAQAAAAAAAAAAAAAAAAABAhARMf/aAAgBAQABBQKkJmkef//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQMBAT8BP//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQIBAT8BP//EABUQAQEAAAAAAAAAAAAAAAAAABAB/9oACAEBAAY/Amv/xAAbEAACAwADAAAAAAAAAAAAAAAAEQEhMRBBYf/aAAgBAQABPyG3NHWGBk+BVnB//9oADAMBAAIAAwAAABCwz//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQMBAT8QP//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQIBAT8QP//EABsQAQEAAwEBAQAAAAAAAAAAAAERACExQWFx/9oACAEBAAE/ED1NV/cVto83hexH7gQXrLVsCW4hs4qhOZ//2Q==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image1\",\n \"title\": \"image1\",\n \"src\": \"/static/9bb00d4f6f07179b37c87073f951944c/24ee3/image1.jpg\",\n \"srcSet\": [\"/static/9bb00d4f6f07179b37c87073f951944c/8356d/image1.jpg 259w\", \"/static/9bb00d4f6f07179b37c87073f951944c/bc760/image1.jpg 518w\", \"/static/9bb00d4f6f07179b37c87073f951944c/24ee3/image1.jpg 742w\"],\n \"sizes\": \"(max-width: 742px) 100vw, 742px\",\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, \"This guide is an overview of test design, with a strong focus on the\\ntypes of designs that are most often used in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \". It is intended to\\nserve as a reference for both new and senior analysts and assumes\\nfamiliarity with the \", 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 Guide. It is meant to be consulted\\nseveral times during the life of a test program. The guide begins by\\npresenting an overview of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s Initial Test Design Framework. The\\nbulk of this guide presents the types of test designs typically used at\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", their strengths and weaknesses, and their measures of merit. The\\nremainder of the guide discusses common situations encountered in test\\ndesign along with suggested remedies, as well as best practices and\\npitfalls.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is charged with evaluating the operational effectiveness,\\nsuitability, and mission capability of a system under test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"). That\\nevaluation must be technically credible; i.e., the results must be\\naccurate and sufficient to support and defend the conclusions the test\\nteam reports.\"), mdx(\"p\", null, \"Operational sufficiency and technical adequacy are the foundation for\\ntechnical credibility. Operational sufficiency addresses the breadth of\\noperations and conditions, test execution, and whether the test was\\nconducted in an operationally realistic and representative environment.\\nThe focus of this guide is on the second critical area: technical\\nadequacy. A test is technically adequate if analysis of the test data\\nprovides the user/warfighter with sufficient information to make\\nfielding and employment decisions. This guide provides information to\\ncreate a statistically rigorous test design that will lead to a\\ntechnically adequate test.\"), mdx(\"p\", null, \"Creating statistically rigorous test designs takes careful planning. All\\ntests are designed; some are designed well and some are designed poorly.\\nThe principles and concepts of design of experiments (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \") provide\\ntime-tested statistical tools and methods for maximizing the information\\nobtained from a test. Using this test design guide, a test analyst can\\nmake design choices based on a sound understanding of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" principles. As\\na result, the analyst will be able to collect and analyze the\\nappropriate data leading to an objective and defensible report.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" process to execute an operationally sufficient and\\ntechnically adequate test is grounded in the seven-step design of\\nexperiments process (Montgomery, 2013). Table 1 lists the seven steps on\\nthe left and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s coinciding steps and events on the right.\"), mdx(\"p\", null, \"Table 1. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Processes\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"DOE Process Step\"), mdx(\"th\", null, \"AFOTEC Process\"), mdx(\"th\", null, \"AFOTEC Event\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"1. Recognize and state the problem\"), mdx(\"td\", null, mdx(\"p\", null, \"Understand missions and battlespace through the development of the EV-1, requirements/EV-2, COIs/operations/OCs, and ESC\"), mdx(\"p\", null, \"Determine the purpose/goal of test\")), mdx(\"td\", null, \"ITD Meeting\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"2. Select the response variable\"), mdx(\"td\", null, \"Define mission oriented response variables (MORV)\"), mdx(\"td\", null, \"ITD Meeting\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"Develop Measures\"), mdx(\"td\", null, \"Measures Workshop\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"3. Choose the factors, levels and range\"), mdx(\"td\", null, mdx(\"p\", null, \"Develop factors and levels\"), mdx(\"p\", null, \"Apply factor management\")), mdx(\"td\", null, \"ITD Meeting\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"4. Choose the experimental design\"), mdx(\"td\", null, mdx(\"p\", null, \"Choose and evaluate the design based on the goal of the test, factors and levels, and factor management\"), mdx(\"p\", null, \"Develop scenarios and test events\")), mdx(\"td\", null, \"Post ITD Meeting\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"Develop Scenario-measures-test event linkage\"), mdx(\"td\", null, \"Test Concept Brief Preparation\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"5. Perform the experiment\"), mdx(\"td\", null, \"Execute the test\"), mdx(\"td\", null, \"Test Execution\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"6. Analyze the data\"), mdx(\"td\", null, \"Analyze the data\"), mdx(\"td\", null, \"Post Execution\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"7. Draw conclusions and make recommendations\"), mdx(\"td\", null, \"Report\"), mdx(\"td\", null, \"Reporting\")))), mdx(\"p\", null, \"This guide briefly discusses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" process steps 1 through 3 framed within\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test planning process, but focuses on step 4: the process of\\nselecting an appropriate test design.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/1-2-OVERVIEW.md"},"frontmatter":{"metaTitle":"OVERVIEW","metaDescription":"OVERVIEW"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"ca790f90-c311-5139-ae34-e49884cbd5aa"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS/page-data.json new file mode 100644 index 00000000..0bfa1dc8 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"d8c6cef0-7eaf-5fdc-b6c6-1cfa5b2dc28f","title":"ELEMENTS OF THE TEST PLANNING PROCESS","slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS"},"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\": \"ELEMENTS OF THE TEST PLANNING PROCESS\",\n \"metaTitle\": \"ELEMENTS OF THE TEST PLANNING PROCESS\",\n \"metaDescription\": \"ELEMENTS OF THE TEST PLANNING PROCESS\"\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, \"Critical Operational Issues and Operations\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" process begins with a thorough understanding of the missions\\nthat the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is expected to enable or support; the \", 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 Guide\\nprovides an overview of this process. Once the mission is defined, the\\ncore team identifies the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" and subordinate operations. Operations are the distinct activities or\\nprocesses that occur within a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" and are the focus of test design. Each\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" will have at least one operation.\"), mdx(\"h1\", null, \"Response Variables\"), mdx(\"p\", null, \"Each operation under a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" shall have at least one Mission Oriented\\nResponse Variable (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \"). A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" is an indicator that a system under\\ntest can successfully accomplish its mission in the operational\\nenvironment. MORVs are the dependent variables that guide the initial\\ntest design (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \") process. Ideally, a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" should be \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"quantitative\")), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn1\"\n }, \"1\"), \" . If a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" is \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"qualitative\")), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn2\"\n }, \"2\"), \" an analyst should develop one or more\\ncontinuous response variables (measures) to complement it. While a\\nqualitative \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" may be a satisfactory indicator of mission success, it\\nmight also require considerably more testing and resources than a\\nquantitative \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \". In statistical terms, for a given test size, the\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"population parameter\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn3\"\n }, \"3\"), \"\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"estimates\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn4\"\n }, \"4\"), \" for a continuous\\nresponse have less variability than estimates for the population\\nparameter for a binary response. Therefore tests using binary MORVs must\\nhave a significantly larger \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"sample\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn5\"\n }, \"5\"), \" size than tests using continuous MORVs; i.e., more runs\\nare required to achieve equivalent statistical quality and precision of\\nthe parameter estimates. Thus qualitative MORVs should be used with\\ncaution.\"), mdx(\"p\", null, \"Ideally, a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" should be written as a measure (see the \", 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 Guide\"), \"\\nfor further guidance on writing measures). However, it is not necessary\\nthat a measure threshold be identified for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \". If a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" becomes a\\nmeasure during the measures workshop, the appropriate detail is then\\nadded.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#critical-operational-issues-and-operations","title":"Critical Operational Issues and Operations"},{"url":"#response-variables","title":"Response Variables"}]},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS.md"},"frontmatter":{"metaTitle":"ELEMENTS OF THE TEST PLANNING PROCESS","metaDescription":"ELEMENTS OF THE TEST PLANNING PROCESS"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"d8c6cef0-7eaf-5fdc-b6c6-1cfa5b2dc28f"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization/page-data.json new file mode 100644 index 00000000..9fa2e330 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"5625bf25-bbea-5c4f-b4f1-eb65cdd7b1dc","title":"Factors, Levels, and Prioritization","slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization"},"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\": \"Factors, Levels, and Prioritization\",\n \"metaTitle\": \"Factors, Levels, and Prioritization\",\n \"metaDescription\": \"Factors, Levels, and Prioritization\"\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 key event in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" process is the initial test design (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \")\\nmeeting. The following organizations send representatives to this\\nweek-long event: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" headquarters; the detachment conducting the\\noperational test; Director, Operational Test and Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \"); the\\nInstitute for Defense Analysis (IDA); the program office (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Office OR Project Officer\"\n }, \"PO\"), \"); the\\ndevelopmental test organization; and subject matter experts from the\\nuser community.\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" has several phases. In the first phase the COIs, operations, and\\nMORVs are refined and vetted. In the second phase the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" participants\\ndevelop a list of \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"factors\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn6\"\n }, \"6\"), \" and\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"levels\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn7\"\n }, \"7\"), \" (F&L) that apply to each\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" under an operation. Factors are the independent variables that\\ndefine the battlespace---with a range of values called levels---that may\\naffect a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" when the factor's level is changed.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Operational Test & Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) Guide has several\\nexamples of desirable factor characteristics that should be considered\\nduring the test design process. There are attributes of the factors\\n(quantitative data type, qualitative data type, number of levels, etc.)\\nwhich will significantly affect the size and quality of the test design.\\nThese attributes should be considered by the analyst as they facilitate\\nthe F&L discussion during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" process.\"), mdx(\"p\", null, \"In addition to the characteristics and examples in the \", 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\\nGuide, the facilitator should consider the following:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"It is a best practice to use quantitative factors with numeric\\nvalues for levels (e.g., Altitude: 10,000 ft and 30,000 ft) instead\\nof categorical factor levels (e.g., Altitude: Low and High).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Factor levels must be mutually exclusive, meaning that two levels of\\nthe same factor describe conditions that cannot simultaneously\\noccur.\"))), mdx(\"p\", null, \"In phase three, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" participants determine two things: the magnitude\\nof a factor's impact on each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \", and the likelihood of each factor\\nlevel occurring in the operational environment. Based on the combination\\nof a factor's impact and the likelihood of occurrence for each of its\\nlevels, the test team chooses one of four methods for incorporating that\\nfactor in the test design.\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Vary\"), \" -- The factor is deliberately manipulated during the test\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Fix\"), \" -- The factor level is held constant during the test\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Log\"), \" -- During a test run, the level of this factor is recorded\\nas an observation\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Demo\"), \" -- The level will be incorporated into a test run that is\\nexecuted and analyzed separately from the design incorporating the\\nvaried factors\"))), mdx(\"p\", null, \"Choosing one of the four methods for each factor is referred to as\\nfactor management. Figure 1 gives general guidance on which of the four\\nmanagement methods to select for a factor level given a combination of\\nthe factor's magnitude of impact and the likelihood of encountering the\\nfactor level.\"), mdx(\"p\", null, \"Figure 1. Factor Management Guidance\"), 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\": \"610px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/b76f614222db541cc6f859ec0a16434d/5aae9/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\": \"64.09266409266408%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAIAAAAmMtkJAAAACXBIWXMAAAsTAAALEwEAmpwYAAACAUlEQVQoz3VSy5KbMBDk/7/EB/vg8s2HJJc4yVY5tXZILeAneiCeEg9hQIB32yapnDKlQzNoZnq6ZWVSRlGUpglnLIkTIUQUxYxxEQSU0iRJ3/8flue5nPO6rvNc+Vcf53Q6S6l6Y5pb07ad6QxOh2i7tm2bBucGMI6jdfA8IcIgCDDqcr4AnE+nOI5rXcssy9LkevU541EIdmkcJ1I+0krlwzBYmH6/38dxaLsOGKnxGeCfxDGY/Nrb2+32crkqpVD2/rh8R5HruqB9QLYsS0ap63pFUehag9XLj5fPn74QyiDHdvtzs9m8vu4YY8fj0bbtNMtms5kVcIHivu9DIb59/Y79JzGECIqyBNBVRQjpTT/0fRSFjuNgZ+RXq5UVhVgYSwvXcd/eHKxdVZUxBl2KogRQUmJtY9C/55x5ngeATReLhUV8Am8gLCMEl7JMal2jcZ7nqASoa43uEx1oBvEmvFwurbLEpAoKMULt/W+ZyfYZuAf/UJ8rRQmFU8AB52B3uzUQ7TE5TaG7RCdMxoSH0MMAVqEIq0ojX5Ul58FkCtSBVXDkz2RcnT6o7/uE4srkltZ6yqOYIP90sdYaTv0rBiX0wzeKd7u9kso8A1oAowtogxFEQjLBc01TrAAW8/ncwttomgY/4PPhcGz/Bgyf8ijGEwRAEio2z8Cw9Xr9AQnz0qI7lHiNAAAAAElFTkSuQmCC')\",\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/b76f614222db541cc6f859ec0a16434d/5aae9/image3.png\",\n \"srcSet\": [\"/static/b76f614222db541cc6f859ec0a16434d/a2ead/image3.png 259w\", \"/static/b76f614222db541cc6f859ec0a16434d/6b9fd/image3.png 518w\", \"/static/b76f614222db541cc6f859ec0a16434d/5aae9/image3.png 610w\"],\n \"sizes\": \"(max-width: 610px) 100vw, 610px\",\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 test team should keep in mind that the factor level likelihood\\nshould be determined in the context of the system conducting its\\nmission, not the likelihood the level occurs in general. For example, a\\nfactor level related to a nuclear weapon system may be very unlikely in\\npeacetime, but may be very likely in the context of a nuclear weapon\\nemployment. The latter is the likelihood that should be documented.\"), mdx(\"p\", null, \"It is important to remember that even if a factor's levels occur in\\nunequal proportions in the operational environment, the frequency that\\nthe levels occur in the test design may not coincide with those\\nproportions. Factor levels that occur disproportionally frequently (or\\ninfrequently) in the test design could create an unrepresentative sample\\nof the system's overall performance across a typical set of operational\\nconditions. Consequently, the test design could cause an overly\\npessimistic or optimistic assessment of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"Test Design Workbook\"), mdx(\"p\", null, \"The major product from an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" that summarizes the test planning elements\\nand F&Ls is the Test Design Workbook (TDW). Figure 2 shows the F&L tab\\nfor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1 from the TDW for the X-100 Block Upgrade 1.1 (X-100 is a\\nfictitious program). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Does X-100 1.1 support Airland operations\"), \"\\n, is shown at the top. This \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" had three operations: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff &\\nDeparture, Enroute,\"), \" and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Arrival\"), \" . Operation 1, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff & Departure\"), \"\\n, is shown underneath \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" for Operation 1 is \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Delta Time\\nbetween Planned and Actual Take-Off Time\"), \" .\"), mdx(\"p\", null, \"The test team developed a list of 23 factors for Operation 1 at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \".\\nHowever, only two will be strategically controlled (varied) during the\\noperational test. The other factors will either have their levels\\ndemonstrated (demo), fixed during the test \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"runs\")), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn8\"\n }, \"8\"), \", or logged. Typically factors will\\nbe logged because the levels cannot be controlled. However, for some\\nfactors that are controllable but judged to be inconsequential, the\\nanalyst may choose to log the levels in case the factors are actually\\nsignificant.\"), mdx(\"p\", null, \"Four of 23 factors are shown: two factors to be varied and two factors\\nthat cannot be controlled (which will be logged.) In the columns under\\nprioritization, the test team noted the magnitude of impact of the\\nfactor, and the likelihood of encountering each factor level.\"), mdx(\"p\", null, \"Figure 2. F&L Tab of TDW\"), mdx(\"p\", null, \"Accurately selecting and prioritizing factors, levels, and their impact\\non the system's MORVs is extremely important to ensure the test design\\nselected will achieve the test goal.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization.md"},"frontmatter":{"metaTitle":"Factors, Levels, and Prioritization","metaDescription":"Factors, Levels, and Prioritization"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"5625bf25-bbea-5c4f-b4f1-eb65cdd7b1dc"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST/page-data.json new file mode 100644 index 00000000..e98bd99d --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"da882a58-4a7d-565d-a7a6-253ea2a465bc","title":"GOALS AND TYPES OF TEST","slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-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\": \"GOALS AND TYPES OF TEST\",\n \"metaTitle\": \"GOALS AND TYPES OF TEST\",\n \"metaDescription\": \"GOALS AND TYPES 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, \"Before selecting the test design, the goal of the test must be\\nestablished. The goal not only determines how the test is designed and\\nexecuted but how it is reported as well. Within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", there are\\ngenerally three goals of a test:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"characterize system performance\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"compare system performance to a requirement or to another system\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"identify problems with the system\"))), mdx(\"p\", null, \"A test program may include up to all three test design goals. Generally,\\neach goal will have its own collection of test events based on one of\\nthe design types outlined later in this guide. The above list states the\\ncommon goals in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" testing, but it is not all-inclusive. If a test\\nteam has a different goal for their operational test, they should\\nprovide an explanation including the unique nature of the desired test\\ngoal and how it affects the design, execution, and reporting of the\\ntest.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST.md"},"frontmatter":{"metaTitle":"GOALS AND TYPES OF TEST","metaDescription":"GOALS AND TYPES 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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"da882a58-4a7d-565d-a7a6-253ea2a465bc"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/1-6-Characterize/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/1-6-Characterize/page-data.json new file mode 100644 index 00000000..ec72cbf0 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/1-6-Characterize/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/1-6-Characterize","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"08eb12d3-efdf-5e56-b1c4-ee5e1fc50ffa","title":"Characterize","slug":"/analyst_test_design_guide/1-6-Characterize"},"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\": \"Characterize\",\n \"metaTitle\": \"Characterize\",\n \"metaDescription\": \"Characterize\"\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, \"When characterizing a system, the test goal is to analyze the system's\\nmeasures across the operational conditions (battlespace) defined by the\\nfactors and levels. In addition, the test team quantifies the\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"effect\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn9\"\n }, \"9\"), \" that changing factor\\nlevels (and combinations of factor levels) have on the measures. To\\naccomplish this test teams use test designs that allow the estimation of\\nthe factors' \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"main effects\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn10\"\n }, \"10\"), \"\\nand the factor \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"interactions\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn11\"\n }, \"11\"), \"\\n.\"), mdx(\"p\", null, \"Designs used to characterize the system vary the levels of multiple\\nfactors simultaneously with the intent of testing and reporting the\\nperformance of a system under different operational conditions. They\\nalso enable an analyst to determine which factors are most influential\\non system performance. The data produced by these designs can be used in\\nfuture testing and for the development of operational Tactics,\\nTechniques and Procedures.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/1-6-Characterize.md"},"frontmatter":{"metaTitle":"Characterize","metaDescription":"Characterize"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"08eb12d3-efdf-5e56-b1c4-ee5e1fc50ffa"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/1-7-Compare/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/1-7-Compare/page-data.json new file mode 100644 index 00000000..d87aa093 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/1-7-Compare/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/1-7-Compare","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"59cb7c94-c251-54bd-8d0d-8c6318b59a34","title":"Compare","slug":"/analyst_test_design_guide/1-7-Compare"},"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\": \"Compare\",\n \"metaTitle\": \"Compare\",\n \"metaDescription\": \"Compare\"\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, \"When the goal of a test is to compare, the test team gathers data on a\\nsystem and compares it to data from another system, to a requirement\\nthreshold, or to some other criterion. System comparisons do not provide\\ninformation about the system's performance across the battlespace.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/1-7-Compare.md"},"frontmatter":{"metaTitle":"Compare","metaDescription":"Compare"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"59cb7c94-c251-54bd-8d0d-8c6318b59a34"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/1-8-Problem-Identification/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/1-8-Problem-Identification/page-data.json new file mode 100644 index 00000000..c90809fa --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/1-8-Problem-Identification/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/1-8-Problem-Identification","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"fd6a22db-b3c1-53d2-928a-6081c9011a35","title":"Problem Identification","slug":"/analyst_test_design_guide/1-8-Problem-Identification"},"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\": \"Problem Identification\",\n \"metaTitle\": \"Problem Identification\",\n \"metaDescription\": \"Problem Identification\"\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, \"When one of the test goals is problem-identification, the test team\\nattempts to determine whether a \\\"success\\\" or \\\"failure\\\" occurs at one or\\nmore factor level combinations that define the battlespace. One approach\\nis to use combinatorial designs; these designs efficiently combine\\nfactor levels so that problems caused by specific factor level\\ncombinations can be identified with less resources than designs used for\\nsystem characterization. However, combinatorial designs do not generally\\nprovide data that can be analyzed with statistical modeling (system\\ncharacterization.)\"), mdx(\"p\", null, \"Another approach is to demonstrate (demo) strategically chosen (and\\nusually infrequently occurring) factor level combinations. The data from\\nthese demo runs are analyzed separately from the data associated with\\ntest runs used to characterize the system performance. The analysis\\nessentially determines if a failure occurred during the demo.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/1-8-Problem-Identification.md"},"frontmatter":{"metaTitle":"Problem Identification","metaDescription":"Problem Identification"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"fd6a22db-b3c1-53d2-928a-6081c9011a35"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS/page-data.json new file mode 100644 index 00000000..f3ab0ae8 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"6b30bd69-87f7-52d8-88fe-6020781beeeb","title":"TYPES OF TEST DESIGNS","slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS"},"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\": \"TYPES OF TEST DESIGNS\",\n \"metaTitle\": \"TYPES OF TEST DESIGNS\",\n \"metaDescription\": \"TYPES OF TEST DESIGNS\"\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, \"Choosing the most appropriate test design is a combination of science\\nand art. The choice requires expertise on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", the operational\\nmission it supports, and \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#_The_Three_Principles\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" principles\"), \" . Each\\nof the designs in this section has strengths and weaknesses depending on\\nthe test goal and the nature of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test program may use a combination of the designs presented in\\nthis section. It is typical to use a separate test design for each\\noperation under a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \", as factors and levels are often different between\\noperations. Some MORVs may even require a separate test design.\"), mdx(\"p\", null, \"Test designs have associated quality indicators; within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" these\\nindicators are referred to as measures of merit. Measures of merit\\nprovide a basis for comparison when choosing between multiple designs.\\nAlso, measures of merit are used as evidence that a test design meets\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" standards for technical adequacy. The Test Design Measures of Merit section of this guide presents a\\nmore detailed explanation of the measures most often used at \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS.md"},"frontmatter":{"metaTitle":"TYPES OF TEST DESIGNS","metaDescription":"TYPES OF TEST DESIGNS"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"6b30bd69-87f7-52d8-88fe-6020781beeeb"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/2-1-Factorials/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/2-1-Factorials/page-data.json new file mode 100644 index 00000000..274938d7 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/2-1-Factorials/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/2-1-Factorials","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"b894b6d4-2aa0-5588-a0d2-e6d822d58d35","title":"Factorials","slug":"/analyst_test_design_guide/2-1-Factorials"},"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\": \"Factorials\",\n \"metaTitle\": \"Factorials\",\n \"metaDescription\": \"Factorials\"\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 \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"factorial design\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn12\"\n }, \"12\"), \" is a list\\nof test runs in which multiple factors are varied simultaneously from\\nrun to run. This list of runs is called a test event matrix (TEM). The\\nspecial structure of the factor level combinations in the TEM enables\\nthe tester to estimate the main factor effects and interactions between\\nfactors. The following sections discuss two types of factorial designs:\\nfull factorials and fractional factorials.\"), mdx(\"p\", null, \"Full Factorial\"), mdx(\"p\", null, \"A full factorial is a test design that includes every possible\\ncombination of the levels across all factors. Full factorial designs\\nhave the following desirable properties:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Every factor level occurs equally often in the test matrix. For\\nexample, if a factor has 4 levels and there are 16 test runs, each\\nfactor level will occur in 4 runs. This property is related to\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"balance\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn13\"\n }, \"13\"), \" \", mdx(\"strong\", {\n parentName: \"p\"\n }, \",\"), \" and it\\nensures that factor levels do not have a disproportionate influence\\non the analytical results.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The design includes every possible factor level combination in the\\nTEM. This ensures that system performance can be analyzed over the\\nentire battlespace and we can identify factor level combinations\\nthat lead to exceptionally negative or positive performance.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The effects (main effects and all interactions) are completely\\nuncorrelated in the TEM. This means the estimation of each effect is\\nnot biased (influenced) by other main effects and interactions.\"))), mdx(\"p\", null, \"Full factorials are \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"orthogonal\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn14\"\n }, \"14\"), \" , balanced, and easy to construct with or without\\nsoftware. Since every possible factor level combination must be present\\nin a full factorial, these designs are not applicable to test scenarios\\nwith \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"disallowed combinations\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn15\"\n }, \"15\"), \"\\nof factors.\"), mdx(\"p\", null, \"Use the following process to construct a full factorial design in JMP\\n13. The example shown in figure 3 a/b is for the X-100 Block Upgrade 1.1\\nprogram.\"), mdx(\"p\", null, \"Creating Full Factorial Designs in JMP 13:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"From the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" menu, select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Classical\"), \" , then select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Full\\nFactorial Design\"), \" (figure 3a)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Specify the Factors and levels. In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Factors\"), \" section, add the\\ncontinuous and categorical factors using the drop down menu. Specify\\nthe number of levels for each factor. The factors and levels can be\\ngiven appropriate names. Figure 3b shows the input for the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \"\\n1 example.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Continue\"), \" when all of the factors and levels have been\\nentered.\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 3a. Creating a Full Factorial in JMP Figure 3b. Enter the Factors and Levels\"), mdx(\"p\", {\n parentName: \"li\"\n }, 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/736c001347f918ce522b12f0a64d5cd6/9b29b/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\": \"31.27413127413127%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAGCAIAAABM9SnKAAAACXBIWXMAAAsTAAALEwEAmpwYAAABAklEQVQY022Q3W6EIBCFTbyoD+D7v027m1QTe+HNJtvGuv4ioAiDgEhnTdqrfjmZkAlzmEM0zzPn3BoDegMAY1w7MsYlX9QiNwH2dvvK8+L+WdWPrutJP1LGl5GJalgja91+4pwNIRjnJso5Y2534WSibCKEMYpSUq6rwKoA/OEjc6K1xmettUpvVd20TYNndMThrm2/q6rve0ImhFKKN1cJbvdR+OU4jmcNAban3V9/aNr2UWMSQgiaknHUoEDrHYc/ToqiyLIsz/P3LH99u1wvV+yUZem9HwjFqJgTNS+rkLCsivJl9z56+Y8kSeI4TtNUCOEP3MXqUxLwX1EWK+74A/+SNkC1sjEVAAAAAElFTkSuQmCC')\",\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/736c001347f918ce522b12f0a64d5cd6/e3189/image5.png\",\n \"srcSet\": [\"/static/736c001347f918ce522b12f0a64d5cd6/a2ead/image5.png 259w\", \"/static/736c001347f918ce522b12f0a64d5cd6/6b9fd/image5.png 518w\", \"/static/736c001347f918ce522b12f0a64d5cd6/e3189/image5.png 1035w\", \"/static/736c001347f918ce522b12f0a64d5cd6/44d59/image5.png 1553w\", \"/static/736c001347f918ce522b12f0a64d5cd6/a6d66/image5.png 2070w\", \"/static/736c001347f918ce522b12f0a64d5cd6/9b29b/image5.png 3840w\"],\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(\"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/d7a5bd76098167c73c567e83925db85f/9b29b/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\": \"31.27413127413127%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAGCAIAAABM9SnKAAAACXBIWXMAAAsTAAALEwEAmpwYAAAA/ElEQVQY01WQ606EMBSESUiUB1jf/23QGFgDP1B/qCwspetKW9oCpRfqgc16+TJJm7ZzZtJA6xlkrWVcEsompaxb5lkbWLyvqvr15flY1wgh0hFKSdeRQRml3aRd4L0H57IslEvc4kFK/wfCGCEwk/V9P2z0QjjnLrcBOJVSep4/O1KWB3gEg+DQGgPJqK7Lt3eMcdu2VVU1TUNpv0Z5Dwp+QqCnNsb/54RPX+cz5xwaSSkgWcrhNznP8zRNkyS5f3iM4/hpv883siwriuLjUDeo5QIs4ziqcVLwNdZezbdXbjYu+yiKwjDc3e2OCHM5ESY6xmkvySqxtV75BmnlOHLX13cnAAAAAElFTkSuQmCC')\",\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/d7a5bd76098167c73c567e83925db85f/e3189/image6.png\",\n \"srcSet\": [\"/static/d7a5bd76098167c73c567e83925db85f/a2ead/image6.png 259w\", \"/static/d7a5bd76098167c73c567e83925db85f/6b9fd/image6.png 518w\", \"/static/d7a5bd76098167c73c567e83925db85f/e3189/image6.png 1035w\", \"/static/d7a5bd76098167c73c567e83925db85f/44d59/image6.png 1553w\", \"/static/d7a5bd76098167c73c567e83925db85f/a6d66/image6.png 2070w\", \"/static/d7a5bd76098167c73c567e83925db85f/9b29b/image6.png 3840w\"],\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Specify your \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Run Order\"), \" ; JMP can output your design runs in\\nrandom order, or sorted from left to right (or right to left) by\\nfactor level. The number of runs is the product of the number of\\nlevels for each factor---in this example the number of runs is\\n3x4x4x3=144.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Choose the number of \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"center points\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn16\"\n }, \"16\"), \" (only applicable when using continuous factors).\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Choose the number of \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"replicates\"), \" . The number of replicates is\\nthe number of times you want the original full factorial design\\nrepeated. Thus 1 replicate implies 2 copies of the full factorial.\\nNote that when reporting the number of replicates in a test design\\nworksheet (TDW), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" convention is to state the number of\\nreplicates as the number of copies; thus, on a TDW, 2 replicates\\nimplies 2 copies.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Table\"), \" (figure 4a)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"JMP outputs a new design table (figure 4b)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 4a. Output Options Figure 4b. The Design Table\\n\", 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/b8c4f14d283db950ec571c959cf4cc5d/07a9c/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\": \"79.15057915057915%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAQCAIAAACZeshMAAAACXBIWXMAAAsTAAALEwEAmpwYAAACfklEQVQozz1S7W6bQBDk/V+lsvOjbZQmTVq5smSlaStVcezajh2Dgfu+44ADYzAdIMnqBFrdzs3O7Hqb/WG32x9CKqQWUjEuCYJTpTVhSuisLE+uqFxx7L+Vtak2VulEm9SbL9fzp81mG25fwpjpKGSr9Wa92/kh2QZi9UKDiB9iGRIZRDKiOohoELKISMIS73G5CPxASSE5L5wTnEZhuHveEhJTSpJEK62M0ZxzpOv1uj4hqrquXZ57QkmtdVWd8j6E4EgFF2VZCMab5ty2LUrzLHcuJ4Q1TQM0vkppryiPVXUsyzJN06IoKKWcsTAMrbVKSRSdz+eqqjSEWuv7wQCu6wbteMWxOh5fwc45RqkUgkSx7QNYVAOcJBYFjPMBjACTt1mt/P2+l0SdAzMRnJOYpFmKctAOYNthU0pZn576U3nL+9n8aUHiGFLBjCcEmAmDRMYYLBzaHsBKKaQDM/r1nh/nu5d9kiTGGIDjOBJSBEGgjaYxgU/ntgOn6ARtw8I3cMds0rz7d9edZgLNSsQxybJMSdX08abZRlH8rrkDu6ILGAZ7OjCJpETbxKY2y/N3zZhUlr1q7pE9GKMaAlR4JY4iLgTWBkKiMMLkMWcUY1RoDVd9+sYslR6mAsNQGpNYCHArdKOVwnoMhhmT4HW8OBgG5s6wp8VSY97GgCfLct/3sZeBf4BB8LxwxQCWSiXWSgm32wrgU43l8g5B2PZRFq5tmzQx1mhrzKk6WoPSpm3PTV25LC1dmlmFZW1P5RmnrrzPd7PryQPO1fef15Nfn25n48vJ6HIyvpqOv0wvbmYXN/fj24fR14fR3Z/Rt78XPxbj6b8P09XH3/v/wgZ9qIOM22EAAAAASUVORK5CYII=')\",\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/b8c4f14d283db950ec571c959cf4cc5d/e3189/image7.png\",\n \"srcSet\": [\"/static/b8c4f14d283db950ec571c959cf4cc5d/a2ead/image7.png 259w\", \"/static/b8c4f14d283db950ec571c959cf4cc5d/6b9fd/image7.png 518w\", \"/static/b8c4f14d283db950ec571c959cf4cc5d/e3189/image7.png 1035w\", \"/static/b8c4f14d283db950ec571c959cf4cc5d/07a9c/image7.png 1440w\"],\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(\"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\": \"922px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/c3f4e9bc392c4923653c3f1d08768083/6da96/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\": \"38.61003861003861%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAICAIAAAB2/0i6AAAACXBIWXMAAAsTAAALEwEAmpwYAAABQ0lEQVQY0zWQW3eCMBCE+f8/y2OLD55K0HK1XgJBwAeUSyGg0k+0e/IwSWZ2Z9Z4PB73/wKP4/jCt9vtd6owDB3HcR23KC5d17VtN04F2WjbFiJsrXVZlk3T9FoPwwDNsixb2Ov1BrAwF6uVRaPN5psDM45j49M0T2l6Pp8RuI4zn3/UdU2voe9ns5kt1kyQ8iiEQLnf75fLpWkuttutbdtGnmVpmtKmuBRhGPAkpey0xpFSCiM0SpIky/On1fudFgwD82h84UaIKIrQiAmQncB93x8Oh6qq4KlExbFiHwR0XUdG8VvseR4ertcr98D3gyBgJhFYQSQjIvCePSvHP03DIFAqeYsZeJnWiMD3fVJlaQZmbbvdT1mVE09BfYkZhou3GEusTk8h+ajrBiWYtKck4YtrHMFXBGGG57nHo2QRBPwDe0640ge6IlgAAAAASUVORK5CYII=')\",\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/c3f4e9bc392c4923653c3f1d08768083/6da96/image8.png\",\n \"srcSet\": [\"/static/c3f4e9bc392c4923653c3f1d08768083/a2ead/image8.png 259w\", \"/static/c3f4e9bc392c4923653c3f1d08768083/6b9fd/image8.png 518w\", \"/static/c3f4e9bc392c4923653c3f1d08768083/6da96/image8.png 922w\"],\n \"sizes\": \"(max-width: 922px) 100vw, 922px\",\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 main weakness of a full factorial design is that the run size grows\\nrapidly with the addition of factors. The number of runs in a full\\nfactorial design is equal to the product of the number of levels of each\\nfactor in the design. In the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1.1 example, if we added just one\\nadditional 2\\u2011level factor, the number of runs in the design would double\\nfrom 3x4x4x3=144 runs to 288 runs! Because the number of runs increases\\nso rapidly, a full factorial design is infeasible for many test programs\\nunless there are only a small number of varied factors.\"), mdx(\"p\", null, \"Rather than reducing the number of varied factors in order to enable the\\nuse of a full factorial design, we recommend using one of the other\\ndesign types that are discussed in the subsequent sections. This\\nrecommendation is rooted in the concept that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" tests should also be\\noperationally sufficient as well as technically adequate. A test is\\noperationally sufficient if it provides both the decision maker and the\\nwarfighter with results drawn from test events executed across a\\nsufficiently broad set of operational conditions.\"), mdx(\"h1\", null, \"Fractional Factorial\"), mdx(\"p\", null, \"A fractional factorial design is a strategically selected fraction\\n(typically \\xBD or \\xBC) of the runs in a full factorial design. These designs\\nhave many of the same advantageous characteristics of a full factorial.\\nDepending on the degree of fractionation, fractional factorials can\\nyield the same information about main effects and two-factor\\ninteractions (2FI) with fewer test runs. They are easy to construct,\\northogonal, balanced, and are an economical alternative to full\\nfactorials.\"), mdx(\"p\", null, \"As an example, suppose the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1.1 program chose to vary four\\ntwo-level factors, as shown in figure 5.\"), mdx(\"p\", null, \"Figure 5. Sample of F&Ls for X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1.1\"), 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\": \"759px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/4242e0d9b98f022be2d75fa3f00e49e9/ef3e1/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\": \"61.38996138996139%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAIAAADtbgqsAAAACXBIWXMAAAsTAAALEwEAmpwYAAAB4klEQVQoz22SyZKbMBCGef+XmkNySOYw4y32MCB2JCyE0AICbMD58aQqh0TV1aWlv17lfeY8pywvGK241J3UVirbtEa2RtseIpVpWmu6YZjubrz1wwTBvXWj93Yiu/1utw99QgOSB1EB8f3wsD/8fHt9fT9GSfHjkPsxL1ibM1lUbYkNlRmtvff9MSIRIVGSpLQou67P0uzX+SPPy/P54vsBIXEcJ2maBSHhXBjTWdtDG2O9SxxGQVjX9TAM1ppxHGhZxlHinJNSPh4PfuVaGW307bnu9/u6rrgXQng5rRil2MFUKQWGUoqw4zjWvJ7nuRFNi7qNmba18csyA2as8g7fvx1P59PxRAjRWg+Dg68sK2BICwpT2TR9777gr9jwCLiqAL+8XD4+SQhyc4/IZYnE6W2aKlohSVE3jZB4uj1h3PyF80oareEVMY21ru/TLEOdy7LUQqA8wesOg/kn7Q0OAvSQo2AcoJ3rsw2uAV+fLnjFEdz8F94dzoDRnkZKtK13PYkiNGNdVkwI1sgCU2mVgs345Od5Qb8ZYx5mqdt2XebOGq3a2zRcGdNKbcPgW3y8KtkOzi2AIMvyeC50wrskPKtUWVvoBP+mUgU3TPa06WjzR29HgU1XCgtdCJs+jX8DSIWbThpOeakAAAAASUVORK5CYII=')\",\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/4242e0d9b98f022be2d75fa3f00e49e9/ef3e1/image9.png\",\n \"srcSet\": [\"/static/4242e0d9b98f022be2d75fa3f00e49e9/a2ead/image9.png 259w\", \"/static/4242e0d9b98f022be2d75fa3f00e49e9/6b9fd/image9.png 518w\", \"/static/4242e0d9b98f022be2d75fa3f00e49e9/ef3e1/image9.png 759w\"],\n \"sizes\": \"(max-width: 759px) 100vw, 759px\",\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 full factorial test design matrix would look like the design in\\nfigure 6a. However, if test resources were not available to execute 16\\ntest runs, a fractional factorial design could be used to execute the\\ntest in 8 runs---a \\xBD fraction of the original full factorial. The test\\ndesign matrix would look like the design in figure 6b. It is important\\nto note that this example is only intended to illustrate the concept of\\na fractional factorial; practically speaking the design in figure 6b\\nshould not be used at \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" since main effects are confounded with 2FI.\\nHow to choose appropriate fractional factorials is covered in the next\\nsection.\"), mdx(\"p\", null, \" Figure 6a. Full Factorial Figure 6b. Fractional Factorial\"), mdx(\"hr\", null), 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\": \"783px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/6a7ccd5f9cb79b6878e82a0de2ca92a2/e51a6/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\": \"70.27027027027026%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAAByUlEQVQoz5WRa5OaMBSG+f9/q5cvO9NqcdWFyGWFhERCAiHhJtoXtU63X9oyZ04OyfvkXOIF7yKj/JgXlIlKN9pY1SxWG9e0Hby+/dpuhLl+MeN6yIztvdU2Wq19fxOFcUGSnMRZlLDgLdxsXlfbzevbIYzZtz3LmC5KQ7mmvKaFzgp9pNLzN7swCIMgjA4xy6lWKjpEhBBK6Xa33QdBntOQRGmahiER4qSUNsZoXdd1462DHQmIMa21tmka62wSx4xxKKC7Xq8nUVaVWo6sned5GEZsIrhcLl7KKM0yVamu66AAkyaplFVrWsFP0MmyQh7s931/Pp/7fgCGALxXLpc2pm3hUQpEKNvZrm1bJARcilIpnNTOOQAf4PWXr77/6v/w0RUUYNAtkkAqSwm4vrWH/WEYwKBsYA94//kTOcSYmFKPxqZput8NPz+/83xn7tgDDkgqyxJ5kA0pAI/jeId/1z39B9gOyDSik8e0b/Dz+C8wHphzXkopOEfl/we/vHznXGAMlawwXuf+CZ5ui7fbh3gitGiwaN05e54mDBnDglvsFlx++UcwL97bpTJhOinqmKlDrmJWp9wcRfuHvQvz9BCQvIqZ/glXYxhUMaUomAAAAABJRU5ErkJggg==')\",\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/6a7ccd5f9cb79b6878e82a0de2ca92a2/e51a6/image10.png\",\n \"srcSet\": [\"/static/6a7ccd5f9cb79b6878e82a0de2ca92a2/a2ead/image10.png 259w\", \"/static/6a7ccd5f9cb79b6878e82a0de2ca92a2/6b9fd/image10.png 518w\", \"/static/6a7ccd5f9cb79b6878e82a0de2ca92a2/e51a6/image10.png 783w\"],\n \"sizes\": \"(max-width: 783px) 100vw, 783px\",\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(\"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\": \"783px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/b7239545c2738fdce12b8c23bb33cd97/e51a6/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\": \"70.27027027027026%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAABqUlEQVQoz5WR23KbMBCG9f6PldtMJ4baxpiDwEgCMQEkdAADhi6QNlM3F41m59euZj/2AAqykjB+owXJOc3L91q2ppO6E62RykIgFJg13WD70farKtvDozI9OnjxwXHdI74ENz+I4iQ/+9hxjsfT+XT1/Sj1Y/rjTDNWMy5oIXYFy1iFfp4uwRWyrkEQMsKkkN7ZgxBjHEbhLcu0Mq3SQrZtq8R6KSlbuYYtcnwvvIZKaWstxMYaSgijjBLa9/1jO/M8P+vj0Q8jSgvGCKnrpuu69eNKpUnKWMForrUehmHnp2n6S6epuw+oEpCvtDFASinBxzGG5pMk9X2fUrqVmp7hrTh6e3k5uK7juFmWrZW1Yvlas+CcEFK9V3uf/8JwUJkXUBDa3ssaY8Zx3GZ7LMvyJfYJq24Yh/swjjAz8ADvcz7lfQ23FpbaA/mx7W/BQRiXnFdVBdo0zffg19c3zsv7fairGia39r/g/RV5lwB+0TxNCi4hOmumaVyWeVkXNm9rm/84nzqvj8hLqyQXSSFx3kS0wbm8cZWV+rd9+LfN2TXlbcRqnItfYb4a5biQp1sAAAAASUVORK5CYII=')\",\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/b7239545c2738fdce12b8c23bb33cd97/e51a6/image11.png\",\n \"srcSet\": [\"/static/b7239545c2738fdce12b8c23bb33cd97/a2ead/image11.png 259w\", \"/static/b7239545c2738fdce12b8c23bb33cd97/6b9fd/image11.png 518w\", \"/static/b7239545c2738fdce12b8c23bb33cd97/e51a6/image11.png 783w\"],\n \"sizes\": \"(max-width: 783px) 100vw, 783px\",\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, \"Observe that columns are balanced in both the full factorial and\\nfractional factorial figures; i.e., each factor level occurs the same\\nnumber of times. Also, for the runs involving a specific level of one\\nfactor, the other factors' levels are also balanced. For example, in the\\nfirst four runs of figure 6b where the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"departure type\"), \" factor is set to\\nthe \", mdx(\"em\", {\n parentName: \"p\"\n }, \"instrument\"), \" level, there are 2 occurrences of each of the other\\nfactor levels: 2xDay, 2xNight, 2xLocal, 2xNon-local, 2xOff, and 2xOn.\\nRecall that this means the fractional factorial is an orthogonal design.\"), mdx(\"p\", null, \"Fractional factorials have the \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"projection\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn17\"\n }, \"17\"), \" property; if a factor in the design is determined to be\\ninsignificant and its associated design column removed, the degree of\\nfractionation is reduced. In figure 6b, if \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Autopilot\"), \" was not an\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"active effect\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn18\"\n }, \"18\"), \" (significant\\nfactor), the resulting design is no longer a \\xBD fraction, but a full\\nfactorial in the three remaining factors. If the fractional factorial\\nwas a \\xBC fraction, removing one insignificant factor creates a \\xBD\\nfraction.\"), mdx(\"p\", null, \"The strategy of using only a fraction of the runs in a full factorial is\\nbased on the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Sparsity\\u2011of\\u2011Effects\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn19\"\n }, \"19\"), \" principle. The principle implies that the effect of the\\nhigher order (3-factor or greater) interactions are likely negligible.\\nAlthough there is strong evidence that this principle applies in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \", it\\nis not always true and therefore should be assumed with caution. It is\\nwise to verify this assumption by discussing the issue with system\\nexperts.\"), mdx(\"p\", null, \"Although fractional factorial designs save resources and have many of\\nthe same properties as full factorials (balance, orthogonality), these\\ndesigns have less information than full factorials and may not allow the\\nindependent estimation of the main effects and 2FI if the fractionated\\ndesign is too small. The next section discusses how fractional\\nfactorials are classified based on the degree to which independent\\nfactor estimation is impeded.\"), mdx(\"p\", null, \"Resolution, Aliasing, and Confounding\"), mdx(\"p\", null, \"A central issue in experimental design is minimizing the degree to which\\nfactors are \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"correlated\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn20\"\n }, \"20\"), \" with\\neach other while adhering to the test resource constraints. To\\nillustrate the problem with correlated factors, figure 7a shows three\\npossible designs for two varied factors in the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1.1 test.\\nSuppose the average response for runs 1-4 was higher than the average\\nfor runs 5\\u20118.\"), mdx(\"p\", null, \" Figure 7a. Perfect Aliasing Figure 7b. Partial Aliasing Figure 7c. Orthogonality\\n\", 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\": \"541px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/3cf25b6ba90988c4159f47efcff14704/9d576/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\": \"61.003861003861005%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAIAAADtbgqsAAAACXBIWXMAAAsTAAALEwEAmpwYAAACBElEQVQoz1WR626jMBCFef+n2RdYaXf/VEmzuXCHADY2xsY2NFxMuARYN22l7dHRaDTWZ8+MDRtVhHGIGSIM50VGZZZz+dbe51WNj35adXKfnp7X7j41aqjqdhzHPawNN4IgiaMwDIIkTtI4itIUA4gIYSkiGULx9RrFUQxiCFECYJpmXoQl5/vkZhzs+K/tW6Z5vOAIVRfTtfwkBNR2wcGMdrvj6+v55bA7eo7pAT9BQUx/nvIgyn68QMNxfP1a4AeObYdBiFEmGeuVqoS4XC6eHwhZphBiRNIUlWV5f1c/D90Rvhn78/l8PFumnT1FSFbfbp2GqzKJQar7x8SxbM45yUnTtMuyjNO8rQ8zV4ZzOLiO57leeI2E4FKKpmmUUpwXGSY0Z7wQGOG27XR9GKZlWefHum2rTXvD/vP7YlmuY59OZ9O0qqr6gAtGQQw0xnKmk3ma9Yanaf4Gn08WAKB6So+EMf6AGSsgTFWnSlklUVKWeglcqfu6bvNj+YQdNySEDMPQ972OjLFPuCiSBOghpSij8CqE0Eed6r/Bu/0xDK+6Ib1EDec5/YCFlDSnSvW3W53CNCM5xqht1TfYD2NG2TiNGtZTCS7quu67Tv/Wuq56Qr3e7UuPx/Je0Rdsm0PvBiqaQja5aOjTpLhhWulIijcmW20qWvafCW8SIgvKf7niH/fnjvr7gUTyAAAAAElFTkSuQmCC')\",\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/3cf25b6ba90988c4159f47efcff14704/9d576/image12.png\",\n \"srcSet\": [\"/static/3cf25b6ba90988c4159f47efcff14704/a2ead/image12.png 259w\", \"/static/3cf25b6ba90988c4159f47efcff14704/6b9fd/image12.png 518w\", \"/static/3cf25b6ba90988c4159f47efcff14704/9d576/image12.png 541w\"],\n \"sizes\": \"(max-width: 541px) 100vw, 541px\",\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(\"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\": \"541px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/31b1d981bd212ab2873cca6496991226/9d576/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\": \"61.003861003861005%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAIAAADtbgqsAAAACXBIWXMAAAsTAAALEwEAmpwYAAAB/0lEQVQoz1WS25LiIBCG8/5Psy+wVbt7M6VjaTRHI4QAIRAgMYmSkxqXceZi5q+/KKD6o7sBxyc1EzKjAuecFmXOdV5Ifb4Mt8VM935e7GSYX74t12HuzFi3l2ma1lnrhCBDEEJwAgDBFEMAMKYoI4wJTFhOCDydAAQQwSwjKcowziNAtZTrtHE2Ptx4cRQFSVqecL33Qi9OE8T9EG0OYLXavr+7b5vVNgoOEYpTcoT89644gvzXW+YEfmyzxfHR9/zkmFCSayF6Y2ql9vt9FB+VrnCWUcIwJlVVDR/qb+N1m52dteu6W9c7+PlLjOVt01wtXFcpRNjWT1ng+VIqVrCuuzwej2m+PZf7oTBOsNmEQRSFUXICSkmtVdd1xhgpy5wyXgiLEUzatmuaZhymZXne7svzufi8d/x/f/eeFwb+buceDl5d159wKTiCiBIquAAJqOuzPbfvhxf8+ILdnYcQql+yLVFKP2EhyizD5mq0tvWnNq0NGPrxBxyECWNsHMe+7+0ohPiCyzJNkW1SKw0AbJr2Ax5+wqv1NklO0zzbS7RwUfBPWGnNC25M3zadLV5XlZTSmJ9lxwm0XU3zZGH7b5RUbdv216t9rWVZHg9rG/q0jNX9/vjYeS0CPjik7ErdFarjL7Oyoby2IyvPQl+subqIb2ayS5kuufwTqv8se4803fB5bgAAAABJRU5ErkJggg==')\",\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/31b1d981bd212ab2873cca6496991226/9d576/image13.png\",\n \"srcSet\": [\"/static/31b1d981bd212ab2873cca6496991226/a2ead/image13.png 259w\", \"/static/31b1d981bd212ab2873cca6496991226/6b9fd/image13.png 518w\", \"/static/31b1d981bd212ab2873cca6496991226/9d576/image13.png 541w\"],\n \"sizes\": \"(max-width: 541px) 100vw, 541px\",\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(\"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/e59896aaf75cc8fb3ce0e8e66381cfcf/7bf07/image14.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\": \"39.768339768339764%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAICAIAAAB2/0i6AAAACXBIWXMAAAsTAAALEwEAmpwYAAAA5UlEQVQY05WOa2vCMBSG+///lfswhMFARWfTi01zbS5m7dJVbNIY6xAGY24PL/kQzvOek7xlxXqXAgAYpUoqRFiNOOGKyw92j+hocw1pWiq6mr1XxMQkoGIQon0KEMJU6BSpDOuStyVrITUwzlGDm47pTyy6Ah9BJRevh6cVft7y5DyOjTquNrsS1gdEX7bZcrNflwQrI4UUQkqpT8MphDBNU3zj/OhcmEniT28tRkhrZZTOU1DkuVbSWht+wnnvnP+S/dx3w3vf9/0wDOe5/7F8O2aaCX8gLoj+N/nOw5bf5H9tvgAfvMsYBa00bQAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image14\",\n \"title\": \"image14\",\n \"src\": \"/static/e59896aaf75cc8fb3ce0e8e66381cfcf/e3189/image14.png\",\n \"srcSet\": [\"/static/e59896aaf75cc8fb3ce0e8e66381cfcf/a2ead/image14.png 259w\", \"/static/e59896aaf75cc8fb3ce0e8e66381cfcf/6b9fd/image14.png 518w\", \"/static/e59896aaf75cc8fb3ce0e8e66381cfcf/e3189/image14.png 1035w\", \"/static/e59896aaf75cc8fb3ce0e8e66381cfcf/7bf07/image14.png 1128w\"],\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 problem with the first design in figure 7a is that every time the\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" factor is set at the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Instrument\"), \" level, the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff\\nProcedure\"), \" factor is set at the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Normal\"), \" level. Also, every time the\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" factor is set at the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Tactical\"), \" level, the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff\\nProcedure\"), \" factor is set at the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Adjusted Max Effort\"), \" level. Since both\\nfactors' levels were changed at the same time, it cannot be determined\\nif the higher response in runs 5-8 was due to changing the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure\\nType\"), \" factor, or due to changing the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" factor---or\\nperhaps the increase was due to changing both factors.\"), mdx(\"p\", null, \"This ambiguity is because \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" are\\nperfectly correlated; i.e., a level of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" is always\\nmatched with the same level of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" . In the terminology\\nof \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \", these factors are perfectly \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"aliased\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn21\"\n }, \"21\"), \". It is also equivalent to say that \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" and\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" are \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"confounded\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn22\"\n }, \"22\"), \".\"), mdx(\"p\", null, \"The second design in figure 7b is also not ideal. Although the factors\\nare no longer perfectly aliased (perfectly correlated), they are still\\ncorrelated, i.e. when \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" is set to the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Instrument\"), \" level,\\nit is more common that \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" is set to the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Normal\"), \" level.\\nIn this scenario, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" are partially\\naliased; which means the estimate of the effect of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" on\\nthe response will be influenced by the effect of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" .\"), mdx(\"p\", null, \"The ideal case is the third design shown in figure 7c. When \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure\\nType\"), \" is set to the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Instrument\"), \" level, the two levels of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff\\nProcedure\"), \" appear equally often (2x each)---likewise for the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Tactical\"), \"\\nlevel. Thus the two factors are uncorrelated and therefore this design\\nis orthogonal. The effect of changing the level of the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \"\\nfactor from \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Instrument\"), \" to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Tactical\"), \" can be independently determined\\nbecause the effect of changing from the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Normal\"), \" level of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff\\nProcedure\"), \" to the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Adjusted Max Effort\"), \" level will average out over each\\nlevel of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" .\"), mdx(\"p\", null, \"Aliasing and confounding are sometimes used interchangeably, but\\nconfounding conventionally refers to perfect aliasing. Any time a test\\ndesign is not a full factorial, there are some effects--- main effects\\nor interactions of some degree---that are aliased/confounded. Fractional\\nfactorials do not have any partially aliased effects; the effects are\\neither orthogonal or completely confounded.\"), mdx(\"p\", null, \"Note that the use of full and fractional factorials assumes that the\\nlevels of factors can be chosen independently; i.e., If level 1 for\\nfactor A is chosen, that does not constrain what level is chosen for\\nfactor B. Occasionally the levels of two factor cannot be independently\\nchosen, perhaps due to some physical constraint---in other words these\\nfactors are naturally correlated. For example, if one factor is user\\nweight and a second factor is user height (each with two levels, low and\\nhigh), it may be difficult to find military users who are relatively\\nshort and relatively heavy; likewise it may be hard to find military\\nusers who are relatively tall and relatively light. In this situation it\\nmay not be possible to have separate factors for weight and height since\\nall of the possible level combinations cannot be effectively covered in\\nthe test.\"), mdx(\"p\", null, \"The \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"resolution\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn23\"\n }, \"23\"), \" of fractional\\nfactorial designs gives information about the type of effects that are\\nconfounded; the convention is to use roman numerals to signify the\\nresolution. Table 2 shows which types of effects are confounded at the\\nthree common design resolutions. The size of a design increases as the\\nresolution increases. Thus test teams may not have enough resources to\\nuse the ideal resolution V design.\"), mdx(\"p\", null, \"Table 2. Design Resolution\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Resolution\"), mdx(\"th\", null, \"Aliasing of Effects\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"III\"), mdx(\"td\", null, mdx(\"p\", null, \"Some/all main effects are aliased with 2FI\"), mdx(\"p\", null, \"Some/all 2FI are aliased with other 2FI\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"IV\"), mdx(\"td\", null, mdx(\"p\", null, \"All main effects are orthogonal to 2FI\"), mdx(\"p\", null, \"Some/all 2FI are aliased with other 2FI\"))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"V\"), mdx(\"td\", null, mdx(\"p\", null, \"All main effects are orthogonal to 2FI\"), mdx(\"p\", null, \"All 2FI are orthogonal to other 2FI\"))))), mdx(\"p\", null, \"Since main effects are confounded with 2-factor interactions in\\nResolution III designs, these designs are not recommended for use at\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \". Resolution III fractional factorials are typically used as\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"screening designs\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn24\"\n }, \"24\"), \" . They are\\nintended for experiments where the intent is to determine the active\\nmain effects before subsequent testing is conducted to de-alias and\\nestimate the active 2FI. Since \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not typically conduct\\nfollow-on testing, resolution III designs do not provide enough\\ninformation during a test event and are not suitable for operational\\ntest. If it is not feasible to use a larger resolution IV design, then\\nan optimal design (discussed later in this section) is a better design\\nchoice.\"), mdx(\"p\", null, \"Resolution IV designs are an appropriate choice when resource\\nconstraints are a significant concern and a larger resolution V design\\ncannot be executed. Main effects can be accurately estimated because\\nthey are uncorrelated with any 2FI. However 2FI are correlated with\\nother 2FI. Since it is often the case that multiple 2FI are active,\\nthese designs do may not facilitate an adequate characterization of the\\nsystem in the battlespace.\"), mdx(\"p\", null, \"Resolution V designs are the most popular choice. If the\\nSparsity-of-Effects principle is valid, three-factor interactions or\\nhigher are likely negligible, so main effects and 2FI are most likely\\nthe only important effects required to characterize a system. Since both\\nmain effects and 2FI are orthogonal to other main effects and 2FI in\\nresolution V designs, these are more efficient designs (require fewer\\nresources) for characterizing a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" than full factorials.\"), mdx(\"p\", null, \"Any test design higher than resolution V is likely a waste of test\\nresources and any design less than resolution V represents an increased\\nrisk of not discovering or accurately estimating all of the active\\neffects. The goal within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is to minimize or eliminate the\\naliasing/confounding for the main effects and all 2FI. When this is not\\npossible, a balance must be struck between what can be estimated and the\\ntest resources available.\"), mdx(\"h1\", null, \"Creating Fractional Factorial Designs in JMP 13:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, \"From the main JMP menu, choose \", mdx(\"strong\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" then \", mdx(\"strong\", {\n parentName: \"li\"\n }, \"Classical\"), \" , then\\n\", mdx(\"strong\", {\n parentName: \"li\"\n }, \"Screening Design\"))), mdx(\"p\", null, \"Figure 8. Creating Fractional Factorials in JMP 13\"), 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\": \"655px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/03c441e177f31c652c8325a6ca306b07/ae6b7/image15.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\": \"73.35907335907336%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAACMUlEQVQoz3VT23KjMAzl/z9o28feZqfbbUkCDQm5B7ABG2NzN0ma9ABtpjM7e6wxsi3Z0pEwdoRHPCUhD8JOCSjLKl3Uh6JuIWVzGOSq1+0pK5ui1kzVhvM+fXt9fXl+fnx4eLftAPA9b7/3PR+z5+HTyWazwS4JAqVkmgqVCiaU4czmN79u7u/vZ7MZLMIwJJTSMAwCEkVRCkMhkiRJe0DhGIlIOO+c937wcHf3+PhkvpmTyWQ+m5uj0cufl/FojLuklCIRZVmK/g4o2GGMVVUp88qQWZ4phSuxW9f18XjMsmyxWPB+B0HEcQxH0gcCJUJohCJ0LnOjavTlcjmfz5cfOPe4/AfDgSpqI+YJISTP8/obVVU1TXNdYMISARdFUX7jeDhIOLur1e3tLTKcTqfj0Qiz4zimaYI/27Jc1/V9f7/b7kIZiiLPMpV10E2jysZglFp/X5er1Xa7hZ01sWDJ4phzbo+t+dxFzmBo65GAxohkCEHrBtU2Yufd+f20XG1CGmmtLctau2ukBOZs2wZhSqmiyC1UwpygRkPNvpwFpdF+J9IUDh+nEx5UMoN++jgRStJUSgXWJXhhjKfdusOXc8QTNAbKgGzwCJhDXrK3gVdfXqH6Kg5cDmhb3eW82e7Qngt3gR5cusvNeo2E8QJHK3EuRKcolYHw9htat1/OhIZob1CCi0HGUCd9HdC1Hqqlf+DQ6i7sgOWJrEOe43cahMTqX7mehizb0dQjbLFnn2nkOknYX2D3AAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image15\",\n \"title\": \"image15\",\n \"src\": \"/static/03c441e177f31c652c8325a6ca306b07/ae6b7/image15.png\",\n \"srcSet\": [\"/static/03c441e177f31c652c8325a6ca306b07/a2ead/image15.png 259w\", \"/static/03c441e177f31c652c8325a6ca306b07/6b9fd/image15.png 518w\", \"/static/03c441e177f31c652c8325a6ca306b07/ae6b7/image15.png 655w\"],\n \"sizes\": \"(max-width: 655px) 100vw, 655px\",\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(\"ol\", {\n \"start\": 2\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Factors\"), \" section, add the continuous and categorical\\nfactors using the drop down menu. Specify the number of levels for\\neach factor. The factors and levels can be given appropriate names.\\nFigures 9a/b shows the input for the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1 example.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Continue\"), \" .\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Select \\\" \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Choose from a list of fractional factorial designs\"), \" \\\"\\n(figure 9b).\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 9a. Enter Factors and Levels Figure 9b. Request a List of Fractional Factorials\\n\", 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\": \"655px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/2073f8693efdea58b6cd75481ee0526d/ae6b7/image16.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\": \"73.35907335907336%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAACH0lEQVQoz3VTaXOiQBDl//+gTT7GJLWVdSMqRBA8QGA4ZjiGe9Co+4DEsmorj67xTU/30P0aJZuwkKUkYF7QE8+neS3K5lg2Haxqj6PdeNN95lVbNoLyRtI+VrP39+nb28vz84eqeoDrOIeD67hYHQc/ve33e3iJ53GepWnC04QmXNL09cOvh8lkous6IoIgIL7vB4HnkTAMUwQmSRzH6QAQhidOYsb65IPrPT89vby8yjN5uVyu9bU8n0//TBfzBe7KsiyJk6qqkuEOEHgopXVdZUUtZXmRc44r4W2a5nQ65XlumiYbPCgiiiIkkqEQkBClER+ls6yQ6lZcr9fL5XK9w2XA9QeMB7xspIjFhJCiKJpv1HXdtu1t069tU9XVPU7HY4ZkY7t9fHxEh6vVajGfY9U0TZZl6KcqimEYruvato2+8juItuVVK1HfV/6+b7Zby7IQpywV27JpFDHG1IWyXhvoGQrhKAxClIHXlmUpRItpS5H2of1+3ewsnHVCKIqyM3ZoCcqpqgrBOOdlWeDShbzEjMaZfSUngR85hyTNzufz5/kTU8x5jmRsoQXisgHglLLb9is5pHH/SbjufrfHMNBPP9skQdwo3ohRwtu260Tfs0v8+Wy21nXbsjabjWmYuqYbhomCIXL3DSHEHe++kkkQ6poGMe/GM0xngPgBx070ZXtRwbLapwWJ8tHwvxoIB/nfAprbfuoQah7oP5bBOnl4fWcHAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image16\",\n \"title\": \"image16\",\n \"src\": \"/static/2073f8693efdea58b6cd75481ee0526d/ae6b7/image16.png\",\n \"srcSet\": [\"/static/2073f8693efdea58b6cd75481ee0526d/a2ead/image16.png 259w\", \"/static/2073f8693efdea58b6cd75481ee0526d/6b9fd/image16.png 518w\", \"/static/2073f8693efdea58b6cd75481ee0526d/ae6b7/image16.png 655w\"],\n \"sizes\": \"(max-width: 655px) 100vw, 655px\",\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(\"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\": \"635px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/d02c8e7cabe428a1138af0c40f689fcf/1ddef/image17.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\": \"98.45559845559846%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAIAAAAC64paAAAACXBIWXMAAAsTAAALEwEAmpwYAAACzUlEQVQ4y51T2W7aQBT1//9Gn1vlJVUSKYtUEkIJxuwEY/A29izebWzAJvTYVqRGTfvQw/HMnZl7585dkDYWdVxuO8y0HdN2CeUiiNK8iNJdnOUJuCvSfA+hXe72R5xiB5SW86UiD/q9XvfxcfDyQgixTNPCZxq1gEnXbcvStxsIxlbnjPme11JStc3Ft69XV9fKcKiqKxgTx3Edt5mdIAjiOA6BKIqTBKPv+1hh34MxFf5Lv9/pPA4G8nA4nE6nI0XpPnX7P/vjycTFRa4Lg8D3cZ0QIooiXMoYgyAFcYqJ83o3z/PT6VRV1VpdW5adpinnnLo0CEKYwcb3fPgkto0lXiElWXH+L8CN5AUx5yxNs+PxeGiw3+8P74BcFEU7Zlm2awABS5xKukW+X172nnuz2UxRlMlkslgsZFlG8DP8plMd2OoIGI9vgZcnSQJ7CbmYyPJKVaFj2zbUNW1jWRalTFtrylCxbBs5Q+RAkqRwi1zAf+3Zt8zFw+1KQyG3h8Nxo2mz6RwhICrTMMajiSc8+IH9U+fJMMy2SMhubRwyxlcL7gV4BgwcQtALZVlCpq4D7ThO8FRGKUoA/+2zUfza2CTuc7c7GAxQG849ykRNytvroeo3gHabtvwdWEqEsjHaQlFMXQ85DbibhV7sUQQshIcI8yJH1hHk/g9ITPjoY4/R8UZ86TgXsn+5OHxfFKpmLJeL1esrTtHGSNInxsIPUVe0lc3Ch6H+Y2R051QVpWkSTVPXwEpFqf7i2Qtwa1lVSRhsX+ecmOdTeX4r8e9BhkBikyisc9t2y0fPAVp6h9okcYI4HeI2rVehzoapG4YB95ZpFXnxiWdX+KPReK1tcIomTbMdHIAQEvRD3RL1mO3ydv93SnEUyr0nXVPPb9VbuT9Xh3PZsPoXoQlKNxNxO2V3U34/E3cN7xvefeT9Ox9m4npMrxVyMyS/AC0+SbMBU5uPAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image17\",\n \"title\": \"image17\",\n \"src\": \"/static/d02c8e7cabe428a1138af0c40f689fcf/1ddef/image17.png\",\n \"srcSet\": [\"/static/d02c8e7cabe428a1138af0c40f689fcf/a2ead/image17.png 259w\", \"/static/d02c8e7cabe428a1138af0c40f689fcf/6b9fd/image17.png 518w\", \"/static/d02c8e7cabe428a1138af0c40f689fcf/1ddef/image17.png 635w\"],\n \"sizes\": \"(max-width: 635px) 100vw, 635px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 10a shows the fractional factorial design list provided in\\nJMP 13. Notice that JMP states the resolution of each design\\n(although they do not use roman numerals.) You can choose a standard\\nfractional factorial or you can choose a fractional factorial with\\nblocks (Blocks are discussed in the section of this guide titled, \\\"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#_The_Three_Principles\"\n }, \"The Three Principles of \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" \\\" Note that\\nthe full factorial is also available as an option, since there are\\nno resolution V designs smaller than the full factorial.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Select a design and click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Continue\"), \" .\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"JMP presents menu options to evaluate and modify your design (figure\\n10b). The \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Aliasing of Effects\"), \" output shows which effects are\\naliased (confounded) with which other effects. Figure 11a shows that\\nin the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1.1 example, the \\xBD fractional factorial\\n(resolution IV) has 3 pairs of 2FI that are aliased.\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 10a. Fractional Factorial Options Figure 10b. Additional Diagnostics and Options\\n\", 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\": \"635px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/0c6cc5215fa13f5dc272700ed3861239/1ddef/image18.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\": \"100%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAIAAAAC64paAAAACXBIWXMAAAsTAAALEwEAmpwYAAACm0lEQVQ4y5VTiW7aQBD1//9MG9KmAYLaKBzGmMtctgLYxrd31zeYK22fcZOmUpOqT6PJZPGbmZ23w60sajrE9pjlkEtAaZhuD+d0d8zyY7aHnWBpfiwNP0VZnuwOME5WHmcTaTQYCDzfF0XTMDa6ZmzgtI2umxtEumWa2nqt6zpOGZIHQWFhwKm68alydXPzRej1ZFm2bdtxHNfz3AsYY2EYwrMgiKIIfymlQRAg8AnhPBYL3e79t3tRFIfDoTSWhoNBl+d7gjAej8H3Pb+oEgSuU+RCCiSmjMVxzLE4w/8oRgmN4+R4gaIomqrhHGTbslDWcz3TMOkFuJjv+0jHhenu+9PTj//H+XzmaJTiImmWoeDhcHjtS+z3+9LvXqE84SyP1qrVdruzWMiSJE2nM1lWxuPRbDZbzBfz2VwvoGGQ4SukaZrnORdE6Xw0mi9kVVUNw5hNp8vHJfTBzBFghBDPcQoJPM8DJ8sy+O12W1QOfKp8rSvL9Xq5RjJN0ybjCbrCrZBCkiYYZJIkkLrTapumBYkxM5zgGy5gIVHmrkfBBIESYmzMkuy6jr7ZJEmMPlF5tVqhOCTAnH+RHcI67dag3++LfUEQ+E5H6AroLb9gv88xnue4QP6Mom1I1Wo+XH38UK/VKpVKo9HAPUEu5/k+uGS7F8Ve9fa2Vr3t8HycJOfT6aXOP8i2z+7qtbt6/fP1Nd/hMU70+dJhqep75ObDQ0/Awx4YhgkhMEztAmyUixXxvLca4YI4c7BJtkN87AmhtNgbaK6uVTwOxFiGNyv7LJpIBVbLleO6cRRjWmgVL/R8PpV78iaZBHGr2YRS+BQoP81/y1PaHzgWj/8Az6l2pJtEt5hNEtuPbf/iSRn8xRw/US2mmb5ukZ9N2kwVHSoyIQAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image18\",\n \"title\": \"image18\",\n \"src\": \"/static/0c6cc5215fa13f5dc272700ed3861239/1ddef/image18.png\",\n \"srcSet\": [\"/static/0c6cc5215fa13f5dc272700ed3861239/a2ead/image18.png 259w\", \"/static/0c6cc5215fa13f5dc272700ed3861239/6b9fd/image18.png 518w\", \"/static/0c6cc5215fa13f5dc272700ed3861239/1ddef/image18.png 635w\"],\n \"sizes\": \"(max-width: 635px) 100vw, 635px\",\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(\"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\": \"727px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/468ec28867ae5e20c3d14443bb57cace/c54b3/image19.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\": \"97.2972972972973%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAATCAIAAAAf7rriAAAACXBIWXMAAAsTAAALEwEAmpwYAAACfklEQVQ4y31TyXLiMBDl/78ll0kOGSi45DSQGZaAV2zAu2VbtiwvyEDIPGNSyaTCvGp3yVI/9are1o2imPph5HqBH5KQJFleZDlPGWe8hGSMZww7RbVvanGAlPWel1VZi56iaKNBfzgYPD09mYZBSOi5ruc6rnMV29rZluVYVhRFSRxD54w1QmRZ2nOCcDQcgrlcLhVFUZUWkiSb5obzguMrLpoXeQ4WY3leVtXxeAzDsEcZ9z0fppZtR3FMKZVlea2vCSGe5yGNlFLHdpI4ARzbThJaVeXhcGjJrKzP59fz+fz2jsPx0DTN6XSCBTx0+vNvXddXckSzIPBzzvcX4EB8Anag608ADZtXshOQ0Wg0nc4UWZ7NZkj4ZbFYXYA1SmXbdpZl/B3d7VdyEhJ1PtN1w7lgtZTiOEaR1rquqXqaUqS62WxQi6qqsP8v2bbd1Yvrh2IvyrJcr42qqpG5YRiWZYGD5k3/TE3TJBfgig9ySCJdlmGH2u6snaZpCLIsCkoTLNAaaDjsygF0VXgnx2n/8fHh/sfd3d3D/T16jjgRQpcheouvEeJLFT9aNRmPJ5PJYvGiqhoCM00DQeLM970Q40pp5+0bcl7tpZWkqqqu6/JSch0P4zlfTCVpuVjMUTUEIkRzw3NRmVo7lF22GA8cF2XBctbOI5qUc3ErbBd9Hg77/Z+DwSAIgm5ULiatEe6C3X/I0eTXGIMBz2nWYrvdYjRIRHDcPqCmuUmOU2bvdrD2PJ+QKKUZdvEMiqIteNfVr2SxRzxB26qEPo/HuqqiJe30IFQhLvPftNKIb+X1dMLT7tkBff4931geL0XKSgjNim5xS5KsiBIWRPQvrKQXxuQ643gAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image19\",\n \"title\": \"image19\",\n \"src\": \"/static/468ec28867ae5e20c3d14443bb57cace/c54b3/image19.png\",\n \"srcSet\": [\"/static/468ec28867ae5e20c3d14443bb57cace/a2ead/image19.png 259w\", \"/static/468ec28867ae5e20c3d14443bb57cace/6b9fd/image19.png 518w\", \"/static/468ec28867ae5e20c3d14443bb57cace/c54b3/image19.png 727w\"],\n \"sizes\": \"(max-width: 727px) 100vw, 727px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Specify your \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Run Order\"), \" ; JMP provides options to sort (or\\nrandomize) the run order and add replicates to your design.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Table\"), \" to create the fractional factorial design\\n(figure 11b)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 11a. Aliasing of Effects Figure 11b. Fractional Factorial Design\\n\", 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\": \"596px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/bcbd0572a407898baa816abc8db8beed/699b7/image20.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\": \"76.83397683397683%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAACaElEQVQoz22T23KbMBCGefq+Qy+T9iHSu84007h1YgdzsAGJgzibgwRIgMHYXSCTq+4s4h+Nfn2LVkg6cjFGp5Nlmbbj+nGchmEcJxkhQRhGrkM84gURzKQw4wUpcoKqFpdWbHApvemOZhjy+8m0c8s9GzgwnMhEvhsUlok19biVX3f6UT5hx09klG/11ItonLKnXSDtdwddOyoHRT2oloWI4zYNz9OzAcUg7Lje+Zxvt2/7vZznxVHXXAiPONbpxxuWNGRiExVFIYSom7osy67rGKO2bcMyznmSJA3nfd+3bWdjh9KqnJ9sR2rJcG1kIY+Qum4ulwtlrO26PMs91/NJME230A8rVt/v976/BCTkDTDE2Akt6aUTQpZpGoYJ8HwJIIP2fT/LcjAnScq5WM1xmAB/NatxLym/nt9l5SArqqqCgTEGFYLZtCxWzsAgCIVoZ3PXu7YneMuqpmvYTEZ/N7ZLTvoRYwxYMMPHg/A8UrEGPFEQM1qB6LoedFPzquZD2yhxJ8nbveM4cRQBcBwGMEPZQswndL1eoey+H8ZxFuM4QeU9HMxwhb0OUSu5QVrkWVVVlNJiCSDDIY/XD8P8nm4wrlvcbvfVLIdC2r3uoEK6BHQly7KuB7IYwTfHbfGsYpoWOXySFc2AuwelQFLKwLySh4WzMj/F9TqPlwuYbzP5XdagGcMwzE2mLC8K6LNoWwAuq6dPAcB1o2GcgKwA2fPjsqRctNDMqqqLgvKaw5HC74GRDVcKY8deEiE7WC5MlrO2oi/GWXrYpN//pI8vyZrfNh/5+BL/Nx9+x19/ksdn78sT+QeRuTQhLcqZJQAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image20\",\n \"title\": \"image20\",\n \"src\": \"/static/bcbd0572a407898baa816abc8db8beed/699b7/image20.png\",\n \"srcSet\": [\"/static/bcbd0572a407898baa816abc8db8beed/a2ead/image20.png 259w\", \"/static/bcbd0572a407898baa816abc8db8beed/6b9fd/image20.png 518w\", \"/static/bcbd0572a407898baa816abc8db8beed/699b7/image20.png 596w\"],\n \"sizes\": \"(max-width: 596px) 100vw, 596px\",\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(\"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/9e30f49b10958e17ea91a1e36ecec01a/1c1a4/image21.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\": \"52.89575289575289%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAIAAADwazoUAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAwklEQVQoz+WNyw6CMBRE+//f486tG02Mb02wFIKg5f1qC4V7iyQujHGjbp2cxWzODFmd6OLEmM9dnvo8jqOY8zBJsiwXaS7fUHmhskKVVTNC1gdrcaCz5W7vXs/ezXZ8yi6XIHKCnAXlKxX10v05PNrhdG5PZpTUde05zGUsjSIpJZihx6ED06HpzRuIGrAUMilEJTVp29ayrO1me71xIcTwQXBc6WEsBAGaplFKaa0B4CMZsXvIw/d5Pv8gm1GGf5XvE6KBEtFPgBsAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image21\",\n \"title\": \"image21\",\n \"src\": \"/static/9e30f49b10958e17ea91a1e36ecec01a/e3189/image21.png\",\n \"srcSet\": [\"/static/9e30f49b10958e17ea91a1e36ecec01a/a2ead/image21.png 259w\", \"/static/9e30f49b10958e17ea91a1e36ecec01a/6b9fd/image21.png 518w\", \"/static/9e30f49b10958e17ea91a1e36ecec01a/e3189/image21.png 1035w\", \"/static/9e30f49b10958e17ea91a1e36ecec01a/1c1a4/image21.png 1046w\"],\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, \"JMP can only create fractional factorials if every factor is restricted\\nto two levels. There are methodologies for fractionating designs\\ninvolving factors with more than two levels, but that topic is beyond\\nthe scope of this design guide. When it is not applicable to use\\nfractional factorials with 2-level factors, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" analysts typically\\nuse JMP to create an optimal design; these designs are discussed in a\\nsubsequent part of this section. The National Institute of Standards and\\nTechnology has a comprehensive list of 2-level fractional factorial\\ndesigns here:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri3347.htm\"\n }, \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri3347.htm\")), mdx(\"p\", null, \"For more information on fractional factorials and design resolution see\\nChapter 8 of Montgomery, D. C. (2013). Design and Analysis of\\nExperiments, 8th Edition. Hoboken, NJ: John Wiley & Sons, Inc.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#fractional-factorial","title":"Fractional Factorial"},{"url":"#creating-fractional-factorial-designs-in-jmp-13","title":"Creating Fractional Factorial Designs in JMP 13:"}]},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/2-1-Factorials.md"},"frontmatter":{"metaTitle":"Factorials","metaDescription":"Factorials"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"b894b6d4-2aa0-5588-a0d2-e6d822d58d35"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)/page-data.json new file mode 100644 index 00000000..1a56bbff --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"0978d9fc-18f8-5671-82ff-985c108f6d92","title":"Optimal Designs (Computer Generated Designs)","slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)"},"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\": \"Optimal Designs (Computer Generated Designs)\",\n \"metaTitle\": \"Optimal Designs (Computer Generated Designs)\",\n \"metaDescription\": \"Optimal Designs (Computer Generated Designs)\"\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 \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Optimal design\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn25\"\n }, \"25\"), \",\\nsometimes referred to as computer generated design (CGD), is a test\\ndesign whose levels are combined in a way that optimizes a specified\\nstatistical criterion that is a function of the design matrix. Unlike\\nfactorial designs, which are constructed using a standard method that\\nguarantees balance and orthogonality, optimal designs are constructed by\\na computer implementing an algorithm. Design construction algorithms\\ncombine factor levels into test runs with the goal of optimizing some\\ndesign quality criterion. The optimization incorporates constraints such\\nas run size or disallowed combinations of factors.\"), mdx(\"p\", null, \"Optimal design construction algorithms may not always find the \\\"best\\\"\\ndesign. One reason is that the algorithm may not be allowed to run long\\nenough to find the optimal combination of factor levels. Another reason\\nis that there may be multiple designs which have the same optimal value\\nof the chosen criterion. The generated design may be optimal for the\\nspecified criterion, but another design (with the same optimal value)\\nmay be superior in terms of a different un-evaluated criterion. As a\\nconsequence, optimal designs must be evaluated for quality by a\\nknowledgeable test analyst. The test team should also modify the default\\nsettings of the construction algorithm---as an example, the algorithm\\nrun time---if a generated design has flaws.\"), mdx(\"p\", null, \"An optimal design is constructed based on a model specified by the\\nanalyst. The analyst may include in the model any number of main\\neffects, two-factor interactions, or higher-order terms if necessary;\\nthree-factor interactions and higher are not generally included at\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" based on the Sparsity\\u2011of\\u2011Effects principle.\"), mdx(\"p\", null, \"The optimality criterion chosen to create the design depends on the test\\ngoal. The following are optimal designs that can be created with JMP\\nsoftware.\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"D-optimal\"), \" designs - Used when an analyst places a priority on\\naccurate effect estimates. This is because D-optimal designs\\nminimize the joint variance of the parameters in the statistical\\nmodel. For example, when using continuous factors, these designs\\nminimize the joint variance of the \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"linear regression\")), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn26\"\n }, \"26\"), \" coefficients \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\widehat{\\\\mathbf{\\\\beta}}\"), \" . When model\\nparameter estimates have low variance, we can expect the estimates\\nto be close to the true value (assuming we are using unbiased\\nestimates.) D-optimal designs are used most often in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" as they are\\nideal for characterizing a system.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"I-optimal\"), \" designs - Used when an analyst prioritizes accurate\\npredictions from a statistical model. These designs minimize the\\naverage prediction variance of statistical models. Unlike D-optimal\\ndesigns which have test points located at the extremes of the design\\nspace, some test points in I-optimal designs may be spread\\nthroughout the design space (when continuous factors are used.)\\nThese points improve a model's predictive capability across the\\nwhole design space.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Alias-optimal\"), \" designs - Used when an analyst prioritizes\\nminimizing bias in the parameter estimates from un-modeled factors.\\nThese designs minimize the aliasing (correlation) between the\\nspecified model effects and other terms not included in the model.\\nThis optimality criterion is typically used when a design is\\nconstructed to estimate main effects only, but the analyst wants to\\ninsure against 2FI which may be active (but are not included in the\\nmodel).\"))), mdx(\"h1\", null, \"Creating a D-Optimal design in JMP 13:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"From the main JMP menu, choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Design\"), \"\\n(figure 12a)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Add the response variables\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. One response variable is included by default. Change the\\nresponse name by clicking on \\\"Y\\\"\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. For additional responses, use the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add Response\"), \" drop down\\nmenu in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Responses\"), \" box. You can choose whether the\\nresponse should be maximized, match a target value, minimized,\\nor none of these\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Add the factors\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Factors\"), \" box, use the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add Factor\"), \" drop down menu to\\nadd the appropriate type of factor. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" typically uses\\ncategorical factors, although continuous factors are ideal; the\\nnumber of levels must be specified for \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Categorical\"), \" and\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Discrete Numeric\"), \" factors\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. For adding multiple factors of the same type and number of\\nlevels, input the appropriate number in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add N Factors\"), \"\\nbox\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"c. If you have created a JMP table of your factors and levels, you\\ncan populate them in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Factors\"), \" box by clicking on the red\\ntriangle to the left of \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Design\"), \" and choosing \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Load\\nFactors\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Specify Factors\"), \" box, click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Continue\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Linear constraints on continuous factors, or disallowed combinations\\nof categorical factors can be added in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Define Factor\\nConstraints\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Only the main effects are loaded by default in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Model\"), \" box\\n(figure 12b). To add more model terms click on the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Interactions\"), \"\\ndrop down menu and choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"2nd\"), \" (this will load all 2-factor\\ninteractions -- if you want higher order interactions, choose those\\nas well)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 12a. Creating a D-optimal Design Figure 12b. Adding 2-way Interactions to Model\\n\", 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\": \"967px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/7e0b49f45ef727a59ed85505bec1b927/aa08e/image22.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\": \"105.01930501930504%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACwElEQVQ4y5VTV2/bMBjk//9P7UsatHlogcRNYlt7cGhwSdR27J7kBEjRgfb0gSBof+OOR5JQIZXSxjjX9fi6fhzHYYtxnMbpLcbp7XC0Td+6oXEjuX8OD0EqRJlRjihrZRqnmxZh1nDX1boOJ7W2CS2/H/nDsdgdBQkTdv/weHtz8+XzZ86YlLJYIcqyLFByXUQhCmN0Y00tVRBn2kjbDbSoSFLoKKMfP3x4ft5TSvFvUGg2uK5zzvU92IAOlt42TSk1E8K1IDmQKOVpRgPfD8MQbaMoyrO8rio0jKNIKcUY20YRnHEpFWjxUoVxGuecRE/H/d7PsoxRviwLchhlrm211mEQ1nWdJkme557n+X4gilUT51opS+xJWaokY993O9/3D/tDkqT9MEDWYbhKu4k+T+s6jRhdmmaahnkCp47Uuq2UDvzAO3qhH9AsxylGmDdM6yW9FsIePNFZcLGcXi6XC8lZsT/6375+fXre7z3/6AcxEEVBEPieh0EMhNYaFbfkHsk0p9ivyRkrwigNPf/+ENzu411IoXOSJI+PT8ix1qItdAaXa2epbVkUp9NpWU4kFzJMKc3zqqqUrJGJkkYbxvnlHaYVI+4nyaEoXS0AwWrdwFav5Te8vLyg8DTPpzdAgqtgrh8F9wTLlDIwAYFZ0pzdfrq5u7uDSa4M0X/8BZCu6yerooJnsAz6EV4ZOBo0kijO0gx2QD7keX9V75JHo2IkK6lBg4jaUlFsNq4w83id73d47axjwVLOORxKBOwmyseHB7iy7xyob3c8Lb/EaZkxDRcU0maUpWlOEl4fwnT3dITJa+1Kaf8UojI5q+BOiH8+n/H+SaXalApeylKanJeVstK0v41KN/h1npfr5eHqiWl61+FzeHXz6pvz5d+wPklpW61027bnt7TzX+On5NpaPFprDJxw+R/AbT8AmqmbaRVQbiQAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image22\",\n \"title\": \"image22\",\n \"src\": \"/static/7e0b49f45ef727a59ed85505bec1b927/aa08e/image22.png\",\n \"srcSet\": [\"/static/7e0b49f45ef727a59ed85505bec1b927/a2ead/image22.png 259w\", \"/static/7e0b49f45ef727a59ed85505bec1b927/6b9fd/image22.png 518w\", \"/static/7e0b49f45ef727a59ed85505bec1b927/aa08e/image22.png 967w\"],\n \"sizes\": \"(max-width: 967px) 100vw, 967px\",\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(\"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\": \"715px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/273996145c2c87c428e91aca96ff76ca/d0c0e/image23.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\": \"106.94980694980696%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACkklEQVQ4y4VUiXKbMBTk/38pjjvTSZtmctmujTkM4kaAQBKHDXYSd4HYTTKdeg2axxOLVvuerNhOGMXUDyLien4Yp1leCMkKzgpRcJlzyXLOZZnlQ0bIZteWdSOruqy3iqpq06uryWTycH9PKU0ojeMojvoLj/1DFCYJjU4ZIQTnvL85V4gXXE+uFovfQ0KUJ1R1XVfveM8MgThBSqlA6rfpdLlarddrA9ANQhzMMcbyPC8GbLfbpmmqssLY9GHTti1GJSuErmn6Wvdcr2s73/fns0Vd1Z7nZRnD1GazkbK0LMs0jCRJPddVV2oQhPioUsgqCkMsc3h5OR6P0GoY5r478CLv9p1pmL4fsJwRQoIgIDaBQKwVhmGapr3s58dHXdfxbVVVN+YGe4Oq3W53HgEoR7jf75GB4DFQUsbnz8/L5co0TW2twdWRDF77gd91XXvCOVZE1UC2oemu61qmZVt2QpPD4TC+tB+AYHvCWUtPJq4/vZ5inzAGG3PwI84A17bt3ifThHkoEmqDKoxWv5MTVsxnM03TYEzgB2EYQDl6YzGbPz08wSQoojHFgmPBPpGzXBDLBhMzxwFvb28YUbkgjM4ZiH99fUUbofiIz2QOh+OI4sPYKiZGMvSjmMcTxiRqm2XZ6EhPTlmxXqmO61kby3V8wQVWwHuosE2ckTYCMcRj83/ddvzw5vv329tftk3gx1hS9DUUwqHdZ3x12wtjkH/e/Li7u0MzBr1rAeSB+bG2/4Qi620pSykkL/i4GpYdF2kvAQdDpjivlOaMfVF1mZzmHIZZlo0Cogmqqr6otu/Z4VZoxmZPjzgSTV3j76Cqq6Ed2/9f/Ssd2jPIlqqhGYQVVS4axquLV5JLmvGUiT9apJF/32ubNAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image23\",\n \"title\": \"image23\",\n \"src\": \"/static/273996145c2c87c428e91aca96ff76ca/d0c0e/image23.png\",\n \"srcSet\": [\"/static/273996145c2c87c428e91aca96ff76ca/a2ead/image23.png 259w\", \"/static/273996145c2c87c428e91aca96ff76ca/6b9fd/image23.png 518w\", \"/static/273996145c2c87c428e91aca96ff76ca/d0c0e/image23.png 715w\"],\n \"sizes\": \"(max-width: 715px) 100vw, 715px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Input the number of runs. Select either the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Minimum\"), \" (determined\\nby the model terms you entered in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Model\"), \" box), \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Default,\"), \"\\nor enter the number of runs you want in \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"User Specified\"), \" (figure\\n13a)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click on the red triangle to the left of \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Design\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. Choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Optimality Criterion\"), \" , then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make D-Optimal Design\"), \"\\n(figure 13b)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Number of Starts\"), \" ; enter an appropriate number and\\nchoose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"c. Choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Design Search Time;\"), \" enter an appropriate number and\\nchoose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Design\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 13a. Specify the Number of Runs Figure 13b. Specify the Optimality Criterion\\n\", 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\": \"955px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/8bd727dcf8a29a60d23457c3d7fe1815/a0b80/image24.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\": \"106.56370656370657%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAAC10lEQVQ4y5VT2W7bSBDk//+SsS8L5MEGEq+9XtE6KIrkcE7OzeElyU5R3n0IHCySQmNESl091dWtrCKs09ZY50MMsY99SsP4b4zjME63WF/7NCBSSkoHZXpE9pQft4eypbSqSU2o6oxxwTj/cdr/ztAnF3ptfVnzvBDPe7ktVbY71vlm+/fT08P9AyGkU4pSyjlXSgrB5XpwHNZa72ynddVQ57p+GLV1WUEUajPGiqKIsZ+mydwQb+iBlHDgCR/eB6oMEwJNQkW23ZWMC5DLskRyGgbnHLoAikNhjG3qWog1oalqpY02VnSWSn9iOtt8e6obKgV/zV+7rpvGEReCD5113dhbIXRxPB6rqhKqg7vwTCsqZJcREDtTN2TzuuVShTRC85T6ZZ6WCUYnlFsxjfM8wzaohf7zkuZpzpiyQtuyJi+bbcNESMORqi//HP78K/+6r15aTbVHIdDneerTiJtb0i7L+f39PdsXVdsyzthuu0NDMwxz/vn18PD4/PDtuWgYX9fAQCpuhiV4k0LOy7KSi4qQllHaomeMCg6h4WK/hz3jMKQYUQ4uhhCWZSVr42DNsizTNGanVp7q9rDbM8rgkvf+crmQhiilUPvt7Q3nMAxSysv5HNNwIpQx+CSRkAntG0LzPD+WpeACvSEbXSEbD+fz+Xq9QjBGgJtjGpUoeXvCGmKumTTxWJ7+uLu7v79vmsZYNGggcjX4R8CwmKbgGsmqlFb/MiI0Rg8GPAMgBkw0O33CjTx623B6EkJBTkaVw3jrqmKMYwVxH75F6vgpAKxvsDUjBQbkvMuo1ELIbb4xWqc+rgtwhpfz57hgM8ZRKm6Mpky2TGaHmu2K+uvjy6nhykTReanDTwM/Net/P7xdr5gIRoCbLUbVcsWEJkx2NmgXfxrKooT72C0A8jIbIBYIWAkI+xjsr2AlmxCxGPDp4ytw/z9+IGsfvMPEI5bh/XcA8ndfypqWpqVWbwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image24\",\n \"title\": \"image24\",\n \"src\": \"/static/8bd727dcf8a29a60d23457c3d7fe1815/a0b80/image24.png\",\n \"srcSet\": [\"/static/8bd727dcf8a29a60d23457c3d7fe1815/a2ead/image24.png 259w\", \"/static/8bd727dcf8a29a60d23457c3d7fe1815/6b9fd/image24.png 518w\", \"/static/8bd727dcf8a29a60d23457c3d7fe1815/a0b80/image24.png 955w\"],\n \"sizes\": \"(max-width: 955px) 100vw, 955px\",\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(\"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\": \"847px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/6edde8a38fdbdaa87feced0f8a3244ef/b2cef/image25.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\": \"120.84942084942085%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAYCAIAAAB1KUohAAAACXBIWXMAAAsTAAALEwEAmpwYAAACwUlEQVQ4y51U2Y7rRBD1P/NBfAFC4hF4GSGQAF1lrjMzTiaO433rxb243baT2Pc4UYYAV0KhVSpVV+vUqc121ttot/Pfd1EYxe9htj0kRRKXec4pKXAIO6S0rFgjtTa91N1gzXy0RgvGhfPsbl/etp9Wm7fNzvX2T+7upz/cX9b+54Q8b4K3bbjysq2fQuKM1IR/+2vzzQ/mu9/zLE4cd+0RQtI0iaOoEWKfZJ4fQicljdMiy4o4Sg5hUpaUEJql8W878f1n9Zp18zw53t73d77Wbdd1Wqk0jl/XbhgEgjN4pmmKDjHnDWO8ronneZwRLWir5TTNjm6HcRxwtNZSyjRN16673wcLgLJhGLM0V0rXNZiZ523SgqQ151LPACtthx5nAbdtyxhLksxaK4Q8Hs/jeCzyUgoFWkr54RAWNc0XsDqfp7+BcRilcZyY1lDKGi7AnKcFDK3aphHBfl/U7OtgMCM5hAcVBRPlAJdFpVQrhUTDdu/vRUVywjG56d9p13WF/qFIYJI4tbYvy6rrbHiIkjTzfb8kLKsxY3UDD3fMlIRh1GoUz1Hw8XiqyhpgZEEX5l1R0b+YuewsZtJZtBr4qq6iKJZSodtt2yFtgFttEAstDPZBXpKsWpiXmr1Pz95mg2HneX6dFgLhoTMWqYAcV4QwBhPo4TFdb/uxH46n09nZPD29vL4dgqBpQLWsCpBXmef5w4YgT8jVOJ0Wj/Pzn9GPLunHozEtmAFGSDzc9Idxvtr3rw4RvTDjJSX9n+A7/wWstR0He+22UsoYgw7j7aY/jBPsO/+iHantMqjbhj3G/I/1fAwslb1g/xe4NePlkxwxp4drzrMaExZC4GN8GPy8esFvCLRlWQL8WNqr1QtW8nw+NZwrJa3tJuzWZZOgp/P8cV3sm/+qnThrCFOE65IISEUlEx2ENube+Or1C7lwT/Fk3Td0AAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image25\",\n \"title\": \"image25\",\n \"src\": \"/static/6edde8a38fdbdaa87feced0f8a3244ef/b2cef/image25.png\",\n \"srcSet\": [\"/static/6edde8a38fdbdaa87feced0f8a3244ef/a2ead/image25.png 259w\", \"/static/6edde8a38fdbdaa87feced0f8a3244ef/6b9fd/image25.png 518w\", \"/static/6edde8a38fdbdaa87feced0f8a3244ef/b2cef/image25.png 847w\"],\n \"sizes\": \"(max-width: 847px) 100vw, 847px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"At the bottom of the new window, set \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Run Order\"), \" to \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Sort Left to\\nRight\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Table\"), \" . Notice that unlike when using a \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Full\\nFactorial\"), \" or \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Screening\"), \" design, there is no \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Pattern\"), \" column\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"To assess the designs balance, JMP has graphically see the results\\n(balance) of the design:\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. From the JMP main menu, click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Analyze\"), \" then\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Distribution\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Under \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Select Columns\"), \" , select all the factors except \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Y\"), \"\\n(the response variable) and click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Y, Columns\"), \" to add all\\nthe factors to that box\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"c. Click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"d. The bar charts can be used to determine if each factor has\\nbalanced levels, and whether the other factors' levels are\\nbalanced over a factor level.\"))), mdx(\"p\", null, \"Creating optimal designs requires a sound understanding of design\\nprinciples. Analysts can create an optimal design to meet the\\nrequirements of almost any test situation, but should review the test\\ndesign to ensure the following:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"There is no excessive aliasing/confounding between main effects and\\ntwo-factor interactions; A good rule of thumb is to have\\ncorrelations below 0.5 as much as possible and not exceed 0.7.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"There are enough degrees of freedom (dof) for error estimation; a\\ngood rule of thumb is to have at least 5 dof to estimate error.\"))), mdx(\"p\", null, \"The aliasing structure in an optimal design can be very complex, which\\nresults in biased effect estimates. The D-optimality criterion is most\\nfrequently used at \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", as it minimizes the bias in the effect\\nestimates that results from correlation between the specified model\\neffects. When JMP is used to construct an optimal design, the design\\ndiagnostics which can be used to evaluate the correlation structure are\\nprovided under the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Design Evaluation\"), \" header.\"), mdx(\"p\", null, \"An analyst should create several optimal designs and compare them using\\nthe Test Design Measures of Merit. The\\nalgorithm that generates the optimal design may not always produce the\\n\\\"best\\\" design. Optimal designs are usually created based on a single\\noptimization criterion. In contrast, full and fractional factorials are\\noptimal over several optimality criteria; when fitting a model with main\\neffects and two-factor interactions, factorials are D-optimal,\\nI-optimal, and Alias-optimal. If the number of runs in a test is a power\\nof two and all factors have two levels, then the optimal design is a\\nfull or fractional factorial.\"), mdx(\"p\", null, \"Unfortunately, it is possible an optimal design algorithm may not\\nproduce a factorial when appropriate. As mentioned earlier in this\\nsection, this may be due to insufficient run time for the algorithm or\\nanother design has an equivalent value of the specified optimality\\ncriterion. Consequently, it is wise to verify that the software used to\\ngenerate an optimal design actually produces a factorial design when\\napplicable.\"), mdx(\"p\", null, \"The number of runs in the test design can have a significant impact on\\nthe quality of a design produced by a construction algorithm. Suppose\\nyou have a design with two three-level factors and one four-level\\nfactor. If you require a design with fewer runs than the full factorial\\nwith 36 runs, you should choose a design size that is evenly divisible\\nby the number of levels in as many factors as possible. By doing this,\\nyou make it more likely the factor levels are balanced. For example, if\\nthe chosen design size is 26 it is impossible to balance both the\\nthree-level and four-level factors. However, if the design size is 24,\\nthen the design could be balanced; each level of the three-level factors\\ncould be in eight runs, and each level of the four-level factor could be\\nin six runs.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#creating-a-d-optimal-design-in-jmp-13","title":"Creating a D-Optimal design in JMP 13:"}]},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs).md"},"frontmatter":{"metaTitle":"Optimal Designs (Computer Generated Designs)","metaDescription":"Optimal Designs (Computer Generated Designs)"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"0978d9fc-18f8-5671-82ff-985c108f6d92"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/2-3-Augmented-Designs/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/2-3-Augmented-Designs/page-data.json new file mode 100644 index 00000000..047d5e6c --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/2-3-Augmented-Designs/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/2-3-Augmented-Designs","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"590cee2e-f906-5ffd-bfcd-8982d4a76413","title":"Augmented Designs","slug":"/analyst_test_design_guide/2-3-Augmented-Designs"},"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\": \"Augmented Designs\",\n \"metaTitle\": \"Augmented Designs\",\n \"metaDescription\": \"Augmented Designs\"\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, \"When a test plan changes during execution, the uncompleted portion of\\nthe design should be updated ( \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"augmented\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn27\"\n }, \"27\"), \" ) with new runs; optimal designs in particular may not be\\nrobust to lost or altered test runs. Designs can be created and\\naugmented quickly with software, but logistical constraints may make it\\ndifficult to adjust test events in real time. The following describes\\nhow to augment designs in JMP 13. Note that JMP assumes that data is\\nentered in the response column.\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Augmenting a design in JMP 13:\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Open the existing design table in JMP\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"From the main JMP menu, choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augment Design\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Drag the response to the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Y, Response\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Drag the factors to the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"X, Factor\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Action\"), \" box, click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 14a. Augmenting a Design in JMP Figure 14b. Enter the Response and Factors\\n\", 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\": \"463px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/940c09bed5bbe5fa17ab5754394474af/71ce0/image26.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\": \"71.04247104247105%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAACNklEQVQoz41RS2/TQBD2X0L8AyQOSNw4ceTCb0JICCFQLkiVChcurQREpa2SqEkTO/EjfmQfXtuJ3/Zu7HoZp1SqeEh8Ho2/ndnZnW9WMb3Q8fDaRbaHbRdTFiEaNlLythO9yTsvK9HypkuLOsnLvBJAFMPZEIIpxQFjBAPQBvURINSHH2I+gMIGSonPGCY4isI0TZtmr0xVXV/pqrbUDTPJ8rwo06xIs3S73QG2B0RRFIQBANJFnkO8LCsh9opu2I69xs46JJuGF3JfyqaGuzRNW2qablpr26WYUEI9b5OmWRzvTMPYIJTEseJjMh3P3w6DwWVydM3fXFTHCw7djkaji/Pz6Vw1HMrrqoSvqrMsY4zNZrPhcGjbtpIE7NvX+aMP8vG77sl7+eCVfDbY51nWdd3NzY0QoicH3i+5ABW6bkwmE0KIEvv0+8n4xSf5/GP3dCAfvpYvj1sYnmVBwzZy3S1Gvfw4TpKkLMsY+j7MAYjCokQ10NKvV0zMiVCpsMIahns9m06uZuZkrH4+UnVzuVgs5ipGOIyiH2dnpyenpmUpQVKAoj0vG162By+qAm5o27aTsvCJcfJFXzsb10viFNqGyU9GIyjuNcd53exFzQW/Z1BcwXw4z+M49BwWwMNmoB9iIMHQV6AZIaTsMngx/htgE5TfnlBDuq6B3Z7Y+7oHkL8Xc/EL/F7udinuIkCUbVLCwXX1p1X/Nri398rY2mreTnX/yzQvvlzRK4uNVHdmhT8BhDX6dqk7Ql4AAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image26\",\n \"title\": \"image26\",\n \"src\": \"/static/940c09bed5bbe5fa17ab5754394474af/71ce0/image26.png\",\n \"srcSet\": [\"/static/940c09bed5bbe5fa17ab5754394474af/a2ead/image26.png 259w\", \"/static/940c09bed5bbe5fa17ab5754394474af/71ce0/image26.png 463w\"],\n \"sizes\": \"(max-width: 463px) 100vw, 463px\",\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(\"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\": \"484px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/afca27eb6f2f06f2145c833626d5c997/ff42b/image27.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\": \"69.4980694980695%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAACNUlEQVQoz2VSXbOaMBTk//+atm+3L/bq9NaCV+z4rUASgoGQEBQQFK12xXamne6cObPJZE9O9sRaU8mFIpGkPOGxZjspVO7RiPDEY2InTRirXWqa6706/yyby6FupSnK01UfjhYVmRCShIKwKGCRD5ZmIlHxI2upc6mM1Huzr0xeZXmJ0KZAVuZgQTDsv374+Kk/6AOfX16CgGTGKKVTpVIA+RlpKrullA+CsJLs4NjDXq9HGSvKQmstpUySROyE6oBlHMecc2RwIcRzE7Dy6hSFoWPbvh8wFkJ8BKpqNpvO5guxi5umIYH/PnKNMevl0nHeI87LDlZWHHFLLGLOOCUMfd1ut/v9jr58L1CpBofM5DnIYrEghKIv3cEyZcPCYDKehGFUVsdbB5zzfW/4zeYsAt/xkIUcxB2PZ7PF4XCAMssyS+3LLV1tN15VHS9tW9c1+mzqGsdxc57vr9cruoA9bXvBgyEzf2DxRI1s++3r22g0Gg6Hju0M+q+93hd37B7r+nQ6odz5fAbpatbVX7DSvHgfjQb9gW1/dxwHja1Xq/l8wRhr2xaC01PXEdTAJnpBxtJK9P6HC0xmwHQ6cd3lYhmGIZ70GKrWsEemv4eMgBcTdxIQgnK4uWSUYE4QEEKCINhuNpgqDMk7kx/OZJnuLELCsfVqjV/wEDORMkYpZZgB8jPAUa4LIPA8Hx+rLKuiKOFrdWxAUNiaE7WlckP+C/pP+FyTnaHCrKmabqO1xz2mfgEqE/NNb+cH1QAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image27\",\n \"title\": \"image27\",\n \"src\": \"/static/afca27eb6f2f06f2145c833626d5c997/ff42b/image27.png\",\n \"srcSet\": [\"/static/afca27eb6f2f06f2145c833626d5c997/a2ead/image27.png 259w\", \"/static/afca27eb6f2f06f2145c833626d5c997/ff42b/image27.png 484w\"],\n \"sizes\": \"(max-width: 484px) 100vw, 484px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"If the existing design has already been executed, it is a best\\npractice to check the box next to \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\\"Group new runs into separate\\nblock\\\"\"), \" (See the blocking discussion.)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Linear constraints on continuous factors, or disallowed combinations\\nof categorical factors can be added in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Define Factor\\nConstraints\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"To replicate the existing design, choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Replicate\"), \" in the\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augmentation Choices\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"To add center points to the existing design, choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add\\nCenterpoints\"), \" in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augmentation Choices\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Otherwise choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augment\"), \" in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augmentation Choices\"), \" box\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. Only the main effects are loaded by default in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Model\"), \"\\nbox. To add more model terms click on the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Interactions\"), \" drop\\ndown menu and choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"2nd\"), \" (this will load all 2-factor\\ninteractions); If you want higher order interactions, choose\\nthose as well)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Under the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Design Generation\"), \" header, enter the total number\\nof runs in the design \", mdx(\"em\", {\n parentName: \"p\"\n }, \"AFTER\"), \" augmentation; e.g., given a\\ndesign with 20 completed runs, if you want to augment it with 10\\nadditional runs then enter 30 runs.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click the red triangle next to \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augment Design\"), \" , select\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Optimality Criterion\"), \" and select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make D-Optimal Design\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Design\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 15a. Select an Augmentation Choice Figure 15b. Define the Model and Enter \", \"#\", \" of Runs\\n\", 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/4675fc77b3966076342674a27a0c4448/5bd27/image28.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\": \"71.81467181467181%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAAB80lEQVQoz3WS646bMBSEef83y4+qWe02NxJIbLANvnMxYJK0A1EqVeqOBjCg75zDmOSck/zKmFCMy/x6vRZlXsiCKaUbZbpK2pIrIZSoFWOyLHkpNGEGLrhJzueUEGqMYSVjjBtrUQnmoiqYuFGW4RBS1FrbxvjWuA7GulIu0Ub3qzjn1tghDN41zjqUyvLbr88vTFNDomJryXpVJURVyyTGOAxD27Z1VXvnx3EEaa2VUtKSUUJCH5SUGM05W62iBI9JrXQCEt0Al0Upa1nXErDRljN+JfQH9HO7OxyVUsCEEM457z0g59skzvM0TStcaKTUtLCzHrUJLbNLtj1mKeW1EKdTiokwWghhHIam7RJGCOqhmDam67oQhiWArvO+qaQqKC1o0XU9Giipfq/C+xD6BT5sP5gQ6Bzj/Hg87vf76/x8Pts+bDab7fajfAvTojPO0zT6pkv6sKxWOD7eepUI4wTgcrmc0/Nut8dGvmAIg3h0xgWPmqb5C9/fGsYJEWLsJbz8hsDHtxYYnV9jfAcj3/SUIrY8u2qt/wMjve9gZJlfMs5YnuX4N/CB/8DYIe+x/2ae4/P5gIHDWCD642F/PBzw54LH2GDjNMFzjMs3E8raNiht+4CCMzyMEZ7irF37ub/kRBRcw6UwMKssjFvK1R/AWg5tAJ2c/AAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image28\",\n \"title\": \"image28\",\n \"src\": \"/static/4675fc77b3966076342674a27a0c4448/e3189/image28.png\",\n \"srcSet\": [\"/static/4675fc77b3966076342674a27a0c4448/a2ead/image28.png 259w\", \"/static/4675fc77b3966076342674a27a0c4448/6b9fd/image28.png 518w\", \"/static/4675fc77b3966076342674a27a0c4448/e3189/image28.png 1035w\", \"/static/4675fc77b3966076342674a27a0c4448/5bd27/image28.png 1432w\"],\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(\"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\": \"540px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/0e56354a48d688a9dbe9a0f2de1eab14/07484/image29.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\": \"123.93822393822393%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAZCAIAAAC+dZmEAAAACXBIWXMAAAsTAAALEwEAmpwYAAABcklEQVQ4y52U2XaDMAxE8//fyk7ZytZb3xyTkEBo9cAZyxpJY8vc1nUdx7FtW77fwYZhOAKPNs/zDfKyLF/BCOq6Ls/zIVhVVSQFlGWJH0BMXdeUYQn+JWNGA8gHQafpAX3fU8AecbpsmuYNGW90SqaOQDIBGxlEM3gvkqXcybjSNPXMaAmFYzBUsQQgHjBNEzFw8Kj/P20/Vf5ItqzSzsgE0Y9OOQC6NYt3HmvcdCVJQgTAe7YCpVgC0CyAQGpva9Ps3sV73tqGxt6un0j2VKP4PVnv0YShGQ/Zz+45yzIW8GGCH2eb6KIoHHJn2ydw10xW4nCRj0RsL8GIYGkRATHqp6P399wFs8M/D4lHSO7Ppx3bdrZ9vTBfZ9t/xn62CWUw9DokfbD4Mzg7MNv2Ynw6V4ckjrGzyTeSL70q0et4XiKz5mfAOUFDkj8G9pgWhIE5BfUTo37CNs2+EhOxEf9NSiURAb5N+3oakiPzeo52fwCK2bl1mKBICwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image29\",\n \"title\": \"image29\",\n \"src\": \"/static/0e56354a48d688a9dbe9a0f2de1eab14/07484/image29.png\",\n \"srcSet\": [\"/static/0e56354a48d688a9dbe9a0f2de1eab14/a2ead/image29.png 259w\", \"/static/0e56354a48d688a9dbe9a0f2de1eab14/6b9fd/image29.png 518w\", \"/static/0e56354a48d688a9dbe9a0f2de1eab14/07484/image29.png 540w\"],\n \"sizes\": \"(max-width: 540px) 100vw, 540px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Table\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"To graphically see the results (balance) of the design:\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. From the JMP main menu, click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Analyze\"), \" then\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Distribution\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Under \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Select Columns\"), \" , select all the factors except \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Y\"), \"\\n(the response variable) and click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Y, Columns\"), \" to add all\\nthe factors to that box\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"c. Click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"d. The bar charts can be used to determine if each factor has\\nbalanced levels, and whether the other factors' levels are\\nbalanced over a factor level.\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/2-3-Augmented-Designs.md"},"frontmatter":{"metaTitle":"Augmented Designs","metaDescription":"Augmented Designs"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"590cee2e-f906-5ffd-bfcd-8982d4a76413"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments/page-data.json new file mode 100644 index 00000000..126a0b27 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"eb103b61-f99e-5d4e-8b78-3029900d80ee","title":"Designs for Computer Experiments","slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments"},"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\": \"Designs for Computer Experiments\",\n \"metaTitle\": \"Designs for Computer Experiments\",\n \"metaDescription\": \"Designs for Computer Experiments\"\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, \"Data for some test programs are obtained from simulation models, many of\\nwhich are \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"deterministic\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn28\"\n }, \"28\"), \".\\nThis means that the simulation output does not change if the inputs are\\nheld constant. In other words, a single observation obtained from a\\ngiven combination of factor levels (test point) provides all of the\\ninformation available about that test point.\"), mdx(\"p\", null, \"When obtaining data from deterministic simulations (or software systems\\nwhich have deterministic outputs) using a factorial design may not be\\nthe best experimental design strategy. An efficient design strategy for\\ndeterministic systems uses the following two principles:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Designs should not replicate test design runs; one run provides\\ncomplete information about the response variable at that test point\\nbecause there is no variance in the response.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Designs should allow for the fitting of complex models by providing\\ninformation about the response variable at all areas of the design\\nregion.\"))), mdx(\"p\", null, \"The next section discusses some alternative designs that follow the\\nabove principles.\"), mdx(\"h1\", null, \"Space-Filling Designs\"), mdx(\"p\", null, \"Space-filling designs are constructed so that they spread design points\\nevenly throughout a design region. These designs are used when the test\\nfactors are continuous. The following are general construction methods:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Disperse the design points as uniformly as possible in the design\\nregion using distance measures.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Obtain design points using sampling methods in the design region\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Utilize a hybrid distance measure/sampling approach\"))), mdx(\"p\", null, \"Common construction algorithms for these designs include Uniform\\nsampling, Sphere Packing, and Latin Hypercube sampling.\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Uniform space-filling designs -- Design points are randomly selected\\nfrom a uniform \", mdx(\"em\", {\n parentName: \"p\"\n }, \"distribution\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn29\"\n }, \"29\"), \"\\ndefined over the range of a factor. They are simple to construct and\\naugment (just add more randomly selected points to the space.)\\nHowever these designs tend to leave gaps in the design coverage when\\nthe points are unevenly distributed---particularly when the number\\nof test points is small relative to the size of the design space.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Sphere packing space-filling designs -- Algorithms pack circles,\\nspheres or hyper spheres of equal radii into the design space and\\nuse the center of each as the design point. Sphere packing designs\\ngive even coverage across the design space but are difficult to\\naugment because the spheres have already been optimally \\\"packed\\\"\\ninto the design space and any new points would upset the\\ndistribution of existing points.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Latin Hypercube Designs -- Each continuous factor is divided into n\\nevenly spaced intervals, creating a grid of hypercubes (in the\\ntwo-dimensional case this is a square grid with n2 squares.) The\\ndesign points are chosen so that each of the n subintervals are\\nchosen exactly once in each dimension. The worst case scenario, if\\nthis process is done completely at random, is that all of the design\\npoints fall along the diagonal of the hypercube (figure 16a). To\\navoid this, the algorithm is usually modified to create designs more\\nlike figure 16b.\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 16a. Worst Case Space Filling Design Figure 16b. Desirable Space Filling Design\\n\", 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\": \"515px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/fc172cea01f35f33f53eb89cdc129b64/fbdcb/image30.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\": \"128.95752895752898%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAaCAIAAAA44esqAAAACXBIWXMAAAsTAAALEwEAmpwYAAABgUlEQVQ4y53UiXKCQBAEUP7/Wz3wxIiYPLeplRBTHlOlDj3bc7TDNsMwHA6H6/U6vGkojc/pdNrv977P5/Nmszkej33fQ3a7HQcOPBdTBsjpuo7ffBdDqM7lcuF8FVMBv0bR5OIo+YTs6LGYOu+R67mI8pgstlqtTKKUDo2nDn7GqzP3xaYgUW6VHf2w8gdtKx5wJFdJ0vOMXFOnYaGR7Ge73RoAhCarcAhADi0cuBSTGqhn4G1mYT8kwQERz2MIbdtyVFgul6diU1CZRif6qc280vZdsIgB4oSQdO+p7ZkDCllvUVEjBsmxCt4FM0beB1kfzgzsis1nnk313syvLImMaPnD0vYv8tMlcTrrPX8xpkvC/7skFBGagbclkQMUDj490rkYUCm9rNfr3CRTcBRs1rYY8ieCIaeCxl5akni5ELNn2bm0kzvgWkzGiJfb4ibYYrEgiQcB4xmGA+FHIS9Gom0xjjNj5Vw0aSx6ZBPrVsqS/0902s44839WV/2h/QB0bvIDmb6WSAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image30\",\n \"title\": \"image30\",\n \"src\": \"/static/fc172cea01f35f33f53eb89cdc129b64/fbdcb/image30.png\",\n \"srcSet\": [\"/static/fc172cea01f35f33f53eb89cdc129b64/a2ead/image30.png 259w\", \"/static/fc172cea01f35f33f53eb89cdc129b64/fbdcb/image30.png 515w\"],\n \"sizes\": \"(max-width: 515px) 100vw, 515px\",\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(\"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/3f475d88968f9957501fccf228114009/e3829/image31.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\": \"40.92664092664093%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAICAIAAAB2/0i6AAAACXBIWXMAAAsTAAALEwEAmpwYAAAA20lEQVQY052Ny07DMBBF8/9fxIZ1JSQkJCiJ6tqJHU9je5wmTZPi4DjgKqJQNjyuzmLmao4mSQl7TDcZYQBQ21rAjpeqKKudbio8Vqb7hsJjBHQH6pCsKVDGc8YI2Vq0YJpSH6TpAHtpPoEzg6jaDcc1VTer7e29SNzoh9MpS7MIIo7j+PZThhcXQohDMs/nhRSCFFzV7QOVq2d6l+VP0nKz1xqtbdE23vuL7KcwRy3K0xQubeyUQcpyUUqs913fO+e8nyLL9ZLXj/VK/mW+fA5XcuzmJf+Q//T5HTwPyxNHDTtqAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image31\",\n \"title\": \"image31\",\n \"src\": \"/static/3f475d88968f9957501fccf228114009/e3189/image31.png\",\n \"srcSet\": [\"/static/3f475d88968f9957501fccf228114009/a2ead/image31.png 259w\", \"/static/3f475d88968f9957501fccf228114009/6b9fd/image31.png 518w\", \"/static/3f475d88968f9957501fccf228114009/e3189/image31.png 1035w\", \"/static/3f475d88968f9957501fccf228114009/e3829/image31.png 1077w\"],\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, \"You can create Space Filling Designs in JMP 13 by going to the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \"\\nmenu and selecting the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Special Purpose\"), \" option, then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Space Filling\\nDesign\"), \" (figure 17a). JMP 13 provides 7 design construction methods\\n(figure 17b).\"), mdx(\"p\", null, \" Figure 17a. Opening the Space Filling Design Platform Figure 17b. Space Filling Design Methods in JMP 13\\n\", 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\": \"635px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/6dcb712bfae8f7365fd595c4a833d9e1/1ddef/image32.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\": \"116.21621621621622%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAXCAIAAACEf/j0AAAACXBIWXMAAAsTAAALEwEAmpwYAAAC2klEQVQ4y51UaXeaQBTl//+Y9vRT+l3RxmgEMYIQ2YZtgGHftFFzgVPb9KTrPTjnOczl3bcNZzmR61HXpzbxLeK5QeTTuKzbrKzzqimqtqjbvKyxUzZtVtSw4ySv2mPZdJwsq8Jqtbj/Muf5+/lckXeu4xAbsIbVxmqaxmBahq7blmlbVsIYi2POcrxPHz/c3X1erVZ7RdE0zR3gOA7WJEmyPM+yLE3T/GYUOfZjkMOkEAVhOpkuH5brtSDvdhtRnM9mi8VCkiQPcL3BTUwIiaIINMe2QxriQxzLq6Io8Bpr23Xn8/lyvVimCbdVXYMThmGWZzBoQOEXZN/3e0Ugp0VzvV6u/46XlxfIzgmxwjAqyxLO67quql4LAM9A+R7aARxlGc/zO1keFT5rz4Q4MBAe8ov80QHBgJsNzV3XcTStVMO7Xs6jmMD3Td1suyNspAlHRxVRhA+GMMacQ93xePyfmC+XCzT3noMo2YiCLMuKoqiq+rSVDMO4RfUb9OQ4Kx+Xy620RXkOh4Ou6yhb0zR/ZPbkvO5cQlbL1VaSttutKIiaqgU+PZ1Ot0O/AudHCXo5SYbyM5YmKSqGfHR/AY54VJFlTVVNw4RyaMYuZI8FB5q3wP532fCMcdk9IVOSIivoSsu0MDe2hQamLGanr4jgdPM2puMHsmVtxM3ifiGsBSTMNAyoMHUD3Y++QOXRP6jqO2QvTPTDAeQZP8OKlhrdYpDTNBtnEAaK1w38n8gMYziZTPkpP5lMMIYYvcAPQMZHXNfzPY/YxCFOWVXQ/4bs0ljaiNC8fHiYz+frx/Ve2aPgpCfjMkEpCKIwdMPBdRVQ1OJNqTR1j/KucRWs+1bTDzo4UT8aURyz/seSwV+f6pvndiCzIc+YKhwO0fj9aOa4aMaIcRFk+It4ETHS1jYNDOg/no6c4aWuz/wwC5MqZGUQ53hoXFBW9Ou3BwfGJ4hyEqRuEHtB8gq+8fdAn1CFsgAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image32\",\n \"title\": \"image32\",\n \"src\": \"/static/6dcb712bfae8f7365fd595c4a833d9e1/1ddef/image32.png\",\n \"srcSet\": [\"/static/6dcb712bfae8f7365fd595c4a833d9e1/a2ead/image32.png 259w\", \"/static/6dcb712bfae8f7365fd595c4a833d9e1/6b9fd/image32.png 518w\", \"/static/6dcb712bfae8f7365fd595c4a833d9e1/1ddef/image32.png 635w\"],\n \"sizes\": \"(max-width: 635px) 100vw, 635px\",\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(\"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\": \"930px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/cdd0a56ba4b0448053d961858403f19e/416ee/image33.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\": \"73.74517374517376%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAzUlEQVQoz+2Ou26DMBRA/f8/1KlThk6dGFKSGBKFh+/DxuZRcCBQJ+palKhSpx6dybrn+ooohSTDfZrloKdl8eM8XufLtKaf5s/h0vVevLynm4N9jcq3uCyyszEmzwsFytrKWfujztXOiUQmWhvWuiyV3G8BIPpI4p2EG7iiUiCkPBBRWBZmiXVd11Vlg+uEn5m1iOMdE92uLQpEDK/2Ab7j8/GkjWmahogR6bnYe7/c6fs+9M/Fw6/i4T/+u7jruvFO27YKkDUTPyQSfQHfeUuH6DcRigAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image33\",\n \"title\": \"image33\",\n \"src\": \"/static/cdd0a56ba4b0448053d961858403f19e/416ee/image33.png\",\n \"srcSet\": [\"/static/cdd0a56ba4b0448053d961858403f19e/a2ead/image33.png 259w\", \"/static/cdd0a56ba4b0448053d961858403f19e/6b9fd/image33.png 518w\", \"/static/cdd0a56ba4b0448053d961858403f19e/416ee/image33.png 930w\"],\n \"sizes\": \"(max-width: 930px) 100vw, 930px\",\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, \"For specific questions that are not addressed here or in the JMP help\\nfiles, feel free to contact the Intelligence, Analysis and Assessments\\nDirectorate (A-2/9).\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#space-filling-designs","title":"Space-Filling Designs"}]},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/2-4-Designs-for-Computer-Experiments.md"},"frontmatter":{"metaTitle":"Designs for Computer Experiments","metaDescription":"Designs for Computer Experiments"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"eb103b61-f99e-5d4e-8b78-3029900d80ee"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems/page-data.json new file mode 100644 index 00000000..1370ca71 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"d54c464b-b7f6-587c-9881-fe9ed999ba1e","title":"Test Designs for Comparing Systems","slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems"},"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 Designs for Comparing Systems\",\n \"metaTitle\": \"Test Designs for Comparing Systems\",\n \"metaDescription\": \"Test Designs for Comparing Systems\"\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, \"Comparison tests are conducted to test the hypothesis that a system\\nmeets a specified threshold, to compare system performance under two or\\nmore different conditions, or to compare the performance of two or more\\nsystems. When designing a comparison test, there are two important\\nissues to address:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"When data is grouped by the systems being compared, or the different\\noperational conditions for which performance is compared, it is a\\nbest practice to have an equal number of test points in each group.\\nThis will facilitate a more effective comparison of the group means.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The number of test points in each group gives appropriate power to\\ndetect the delta (difference between the group means) of interest.\"))), mdx(\"p\", null, \"For more information please contact the Test Design and Analyses\\nDivision of A-2/9.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems.md"},"frontmatter":{"metaTitle":"Test Designs for Comparing Systems","metaDescription":"Test Designs for Comparing Systems"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"d54c464b-b7f6-587c-9881-fe9ed999ba1e"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification/page-data.json new file mode 100644 index 00000000..ccd4fb4e --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"5d07caec-0a70-5366-bc5e-6ff84ef69a0b","title":"Test Designs for Problem Identification","slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification"},"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 Designs for Problem Identification\",\n \"metaTitle\": \"Test Designs for Problem Identification\",\n \"metaDescription\": \"Test Designs for Problem Identification\"\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, \"Test designs for problem identification are constructed using different\\ndesign principles than those used for system characterization. The\\ndesigns, called combinatorial designs or covering arrays, are used when\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is assumed to have a deterministic response variable; i.e.,\\nreplicating the design points is not necessary. They are typically not\\nsuitable for characterization of system performance in the battlespace,\\nbut they generally require fewer runs than designs used for performance\\ncharacterization. These designs are a useful tool for designing test\\nruns for \\\"demo'd\\\" factor levels; i.e., for test runs representing rare\\noperational conditions. Consequently, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test may involve designs\\nfor both characterization and problem identification.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification.md"},"frontmatter":{"metaTitle":"Test Designs for Problem Identification","metaDescription":"Test Designs for Problem Identification"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"5d07caec-0a70-5366-bc5e-6ff84ef69a0b"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays/page-data.json new file mode 100644 index 00000000..d3e52b4c --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"032abcf7-25d6-5133-aeb2-974046a98b67","title":"Combinatorial Designs (Covering Arrays)","slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays"},"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\": \"Combinatorial Designs (Covering Arrays)\",\n \"metaTitle\": \"Combinatorial Designs (Covering Arrays)\",\n \"metaDescription\": \"Combinatorial Designs (Covering Arrays)\"\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, \"Combinatorial Designs or Covering Arrays (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \"), terms sometimes used\\ninterchangeably, employ the science of systematically selecting\\ncombinations of factors and levels to provide the best chance of\\nidentifying problems. They are constructed to efficiently evaluate a\\nsystem at all possible level combinations for subsets of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" factors,\\nwhere \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" is usually small relative to the total number of factors. Note\\nthat a combination of levels for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" factors is called a \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"t\"), \" -tuple\"), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn30\"\n }, \"30\"), \". Combinatorial designs are often\\nused in testing software intensive systems with a deterministic binomial\\nresponse variable (a pass/fail response which will not change no matter\\nhow many times the design point is replicated.) However, these designs\\ncan also be applied to testing other types of systems where problem\\nidentification is the primary goal.\"), mdx(\"p\", null, \"Combinatorial designs have advantages and disadvantages. The drawback of\\ncombinatorial designs is that they do not allow for the effect of a\\nfactor to be estimated nor do they allow for statistical modeling; they\\nare rarely balanced or orthogonal. The advantage of these designs is\\nthat they can be used with a large number of factors---even if they have\\nmany levels---as the size of the design can be controlled.\"), mdx(\"p\", null, \"Design size is determined by adjusting construction parameters called\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"strength\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn31\"\n }, \"31\"), \" and \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"coverage\"), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn32\"\n }, \"32\"), \". Combinatorial designs have\\nstrength \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" if every possible \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" -tuple of factor levels appears at\\nleast once in the design. The notion of combinatorial design coverage is\\nused to quantify what percentage of the possible factor level \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \"\\n-tuples occur in the design. Intuitively, 100% coverage at strength \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \"\\nmeans that all possible \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" \\u2011tuples appear in the design at least once.\\nA test team may choose a design with less than 100% coverage at strength\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" , rather than 100% coverage at strength \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t-1\"), \" . The benefit is that\\neven though the design only partially covers the possible \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" -tuple\\ncombinations, the probability of finding a fault caused by a t-way\\ninteraction of factors is higher than when using the smaller design of\\nstrength \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\\u20111\"), \" (with 100% coverage); therefore the overall effectiveness\\nof the design at finding faults is higher.\"), mdx(\"p\", null, \"A combinatorial design can be constructed for any combination of\\ncategorical factors and levels (continuous factors must be converted to\\ncategorical). Disallowed combinations of levels can be removed from the\\ndesigns, but this may increase the size of the design for a given\\nstrength and coverage. Industry has embraced combinatorial designs for\\nsoftware testing as an efficient method of finding software problems\\nwhen the possible input (factor) space is large (Kacker, Kuhn, &\\nLawrence, 2013). During an operational test for a software intensive\\nsystem, a combinatorial design may be an option to evaluate\\ndeterministic measures. However, data for any \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"stochastic\"), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn33\"\n }, \"33\"), \" measures (those having random\\nvariation) should be collected using other types of designs.\"), mdx(\"p\", null, \"The National Institute of Standards and Technology has a free tool for\\ncreating Covering Arrays and Combinatorial Designs: Automated\\nCombinatorial Testing System (ACTS). The tool takes the factor and level\\ninputs from a test design, and provides the minimal factor covering\\narray at the desired strength and coverage. The tool is located at:\"), mdx(\"p\", null, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://csrc.nist.gov/groups/SNS/acts/documents/comparison-report.html\"\n }, \"http://csrc.nist.gov/groups/SNS/acts/documents/comparison-report.html\"), \"\\n.\"), mdx(\"p\", null, \"JMP does not have a platform for constructing combinatorial designs.\"), mdx(\"h1\", null, \"Creating a Combinatorial Design in ACTS:\"), mdx(\"p\", null, \"Note: when entering factor or level names, do not use commas, spaces, or\\nspecial characters.\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"System\"), \" , then select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"New\"), \" (figure 18a)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Enter the name of the system in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"System Name\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Enter a factor (ACTS refers to factors as parameters)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. Type the factor name in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Parameter Name\"), \" box\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Enter the nature of the levels and the level names\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \"i. If the factor is a Boolean type (true/false, yes/no,\\n > pass/fail)\\n\\n 1. Select **Boolean** in the **Parameter Type** drop down\\n > menu\\n\\n 2. The factor levels are automatically named **true** and\\n > **false**\\n\\nii. If the factor is categorical\\n\\n 1. Select **Enum** in the **Parameter Type** drop down menu\\n\\n 2. Type the level name in the **Simple Value** box\\n\\n 3. Click **Add**\\n\\n 4. Repeat steps 2-3 for all factor levels\\n\\niii. If the factor is continuous\\n\\n 1. Select **Number** in the **Parameter Type** drop down\\n > menu\\n\\n 2. Type the level value as an integer in the **Simple\\n > Value** box\\n\\n 3. Click **Add**\\n\\n 4. Repeat steps 2-3 for all factor levels\\n\\niv. If the factor is categorical or continuous and the levels\\n > are labeled by consecutive integers\\n\\n 1. Select **Range** in the **Parameter Type** drop down\\n > menu\\n\\n 2. Type the first integer value in the left **Range Value**\\n > box\\n\\n 3. Type the last integer value in the right **Range Value**\\n > box\\n\\n 4. Click **Add**\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"c. Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add to Table\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Repeat Step 3 for all factors\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 18a. Creating a Combinatorial Design Figure 18b. Enter the Factors and Levels\\n\", 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\": \"831px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/73a2e2d3905b9e6606f75789e2e67fb1/5b4a1/image34.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\": \"74.5173745173745%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAABw0lEQVQoz41S2W7bMBD0//9ZH+o2bWzE1mWZssRreUm+ZMnuiErTFgGaDAaLBbXD4Wp3wRpdc1lzZdtjOJ6Pl/6Np+vtehsvtxHJuR/mE7C79MNwW5Z+IZQmrXnTHKqKN9xPcGAIXkmZZSljexRopZwzRFNChs6tWxZ6IRWlSbIrSyFlBT0XbdvGK3xVHb59X23T8nm1zXZVLfTzevNztWGNMlp9zfVCSJ2mSZblUkgi45yfaa0lIiTehzla64x1yBE7ZyYxnLM0K4od9IxV0IcA7w5VEOMK9w5/xGhZCCHRCdqRaFOZiNn5AzGX6sfT02q9ZllOUk6u0fpTzlJTkeecczwYVFqjnqbfSrP/f8VkX0q+3gkXur7vz5fL9XpF+FzPZNK8WL8keOzj8bjf748IPP1jsTYWTQbvTsfT4y/gLI7KzTOfZXNune/8bzG+wKHrunEch2EYI3wIOoIi5hHMOc6C1a/iOHlf1/Vmu2WMTXdbi61A0XbCBisopURZnudYhyRJVXNYFrTAUoW4U9HeIiAP3gvO2X5PcQYVY4g+loAYwutuN9pp49S/1NaXVZ0WpdAGzEvGFb19FTTd/iXTvwDzS0AaoR8T0gAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image34\",\n \"title\": \"image34\",\n \"src\": \"/static/73a2e2d3905b9e6606f75789e2e67fb1/5b4a1/image34.png\",\n \"srcSet\": [\"/static/73a2e2d3905b9e6606f75789e2e67fb1/a2ead/image34.png 259w\", \"/static/73a2e2d3905b9e6606f75789e2e67fb1/6b9fd/image34.png 518w\", \"/static/73a2e2d3905b9e6606f75789e2e67fb1/5b4a1/image34.png 831w\"],\n \"sizes\": \"(max-width: 831px) 100vw, 831px\",\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(\"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\": \"932px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/739a4c96f070296771b2f576d4a1d13e/f6f78/image35.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\": \"73.74517374517376%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAzUlEQVQoz+2Ty07DMBBF/f9f0x9gj0CiC0pJ2hJc6jgz9liOo7Z+pKKMsidql0hcHW9GczSba9F2sG/xZdN+KJPHa758l4k8znGK5XhOwmq5XMvFs3x4M9UegnddB5zQ9yH8yhACI0A3r++bVS1bcAf1pbVe1Z9VvUNARDMDAIpjwLpZP1awhRNYNwzB+97zmw0fJ3LiHHMPT1rJUkayFHh8Q3iNiESMydtGqUMuxdLdcrxOSSnRv/xH5Hy3zBWdfgJaS1xnco6rcgtozA8scUq3uvd32AAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image35\",\n \"title\": \"image35\",\n \"src\": \"/static/739a4c96f070296771b2f576d4a1d13e/f6f78/image35.png\",\n \"srcSet\": [\"/static/739a4c96f070296771b2f576d4a1d13e/a2ead/image35.png 259w\", \"/static/739a4c96f070296771b2f576d4a1d13e/6b9fd/image35.png 518w\", \"/static/739a4c96f070296771b2f576d4a1d13e/f6f78/image35.png 932w\"],\n \"sizes\": \"(max-width: 932px) 100vw, 932px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add System\"), \" when all factors are entered (figure 18b)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Create the combinatorial design by opening the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operations\"), \" menu\\nand clicking \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Build\"), \" (figure 19a)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \" a. Specify the algorithm in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Algorithm\"), \" box (the recommended\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > one is **IPOG** )\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" b. In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Strength\"), \" box, indicate the strength of the\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > combinatorial array (1-6)\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" c. In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mode\"), \" box\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" i. Select **Scratch** to create a new combinatorial array\\n\\n ii. Select **Extend** to extend an existing array\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" d. In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Constraint Handling\"), \" box, select how the algorithm\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > incorporates disallowed combinations of levels; the default\\n > method is recommended\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" e. Check the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Show Progress\"), \" box if you want to see the\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > algorithm's progress\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" f. Check the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Ignore Constraints\"), \" box if you have entered\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > constraints but want to compare the design with constraints to\\n > a design without constraints\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" g. Uncheck the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Randomize DontCare Values\"), \" box unless you have\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > constraints\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" h. Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Build\"), \" (figure 19b)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 19a. Build the Combinatorial Design Figure 19b. Select the Design Options\\n\", 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\": \"506px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/6173875a132326703cdc682678095ee1/29f4e/image36.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\": \"52.89575289575289%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAIAAADwazoUAAAACXBIWXMAAAsTAAALEwEAmpwYAAABe0lEQVQoz41RYY+jIBD1//+zbXo1tsn2BBRwRQsKIqDd3dxe7tWmt/1wH+6FyMxk3szjmTWdEUqLVsf3X+nj63/O8vk7XD+HKWaNEIxSZ+31uuKsS1pSRJBiXJcFhRTDdV1QR+UdPbeWGMIcw5xVjB4OOSGkLMn59VzXopESqeq6ilWUsq7rkAohVavO558loX3fe++dmzLn7DgOwGWDGYZxHC8Xba0zxmitIWowBsVpmvr+1nOPgSzMs1JKNs00ebWh24C7bZXWxlr7tkFKiTiE4B8A2QvZcCEwSXDBGJMPcM4xBXsEREtZVRU2g4POJzLHSBdjPJ1OLy87xqp6AyUEZGtB5hILuKhrDh46/5JnUpLDj1wbA2N2u11RFPkh3+/3x+Op215ZliWlFOOqbSy+0zeZ0KI44j14J7RBJDZAKMSOo3XOwYj+G5e72zfy7H1KaV1XJDAjbYDJeZ5jJ6UEKpBCanjCgzz7u+/+CTCpbdv7/4PnSP2/8AdbrFgvP3/73AAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image36\",\n \"title\": \"image36\",\n \"src\": \"/static/6173875a132326703cdc682678095ee1/29f4e/image36.png\",\n \"srcSet\": [\"/static/6173875a132326703cdc682678095ee1/a2ead/image36.png 259w\", \"/static/6173875a132326703cdc682678095ee1/29f4e/image36.png 506w\"],\n \"sizes\": \"(max-width: 506px) 100vw, 506px\",\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(\"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\": \"936px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/ba4a50bffb2e4d73ba89147e9ccaab3c/6d2da/image37.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\": \"73.74517374517376%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAABnElEQVQoz32SbU+DMBDH+f6fQxMTv4FvTdxm1GzoBovIcEChLQ/lYdO1tPUKiU6H++cg7XG/u6M9K8FkG6H3EH3wjkvNOyWkPnTqjO0+heD8el5Y/tv7fOXNXzbRdovTJEnSMIoYK+uqqhgbtZKxQ1tfPWDLXbu3T+sXP1257qu7et2E2xhTQlCaZv+I0KwqsotpbKFkfWOj+0i7AZlNp7b97Pt+lhdxmtS1KX8qKP/RVJczZH3WXug9ik5Tgu8mk8Vi4TgOQkmIUB83orJk+5r1cEs2/ppzSSm1bXu5XIZhGMex43mE0lH+B9ZaK/MonBUPToBI3jbNwJTf6g9psL+wQZWCmCzLq6re7/e7XmYxrNt21zRgkPcU1lIq8ELnEDkkG/xaCM25eXcdGFzvCDxUDoJggCXsOxiIgxJCfUtDnv9huKS2bc2Wc0NKOVASFlJC0BmYYYzhF02HEDomIcTJafe5wUswLmkGp9JAA40RzMnxGwRhxWjb5sNvwbDnRwLPr8o4TRFCMLGYkLw4UVke7/LeYHgbll/M4i8GP0eJtxdNawAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image37\",\n \"title\": \"image37\",\n \"src\": \"/static/ba4a50bffb2e4d73ba89147e9ccaab3c/6d2da/image37.png\",\n \"srcSet\": [\"/static/ba4a50bffb2e4d73ba89147e9ccaab3c/a2ead/image37.png 259w\", \"/static/ba4a50bffb2e4d73ba89147e9ccaab3c/6b9fd/image37.png 518w\", \"/static/ba4a50bffb2e4d73ba89147e9ccaab3c/6d2da/image37.png 936w\"],\n \"sizes\": \"(max-width: 936px) 100vw, 936px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Check the design statistics (figure 20)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. Click on the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Statistics\"), \" tab\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Graph\"), \" to see a graph of the coverage ratio vs. the\\nnumber of test runs.\"))), mdx(\"p\", null, \"Figure 20. Checking the Combinatorial Design Statistics\"), 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/6a21335eacb86fe51cfa004efcbab56b/71e8d/image38.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\": \"25.86872586872587%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAFCAIAAADKYVtkAAAACXBIWXMAAAsTAAALEwEAmpwYAAABPElEQVQY0wExAc7+AFh0mDlchi1SgEBijERljkJkjDhchi9UgTBUgT9hi0FjjDVZhE5ulFh1mUdmjklokFp2mztdh0Zmj114mgCit9OWoq2hpqWkqqyhp6meo6eiqKmkqKqorK6boaSora+2u7ueo6Wqrq+ssbGkqam/xMOxtrWyuLnN0dEAvM/ltbm6x8O20c7Dyca7xMC2xsO429fL0s3Dv7uy0MzC39zPxMG2x8W6y8i9wr+139zQ1NDF0c7D7evgALjL4q+0t8C+s8rHv8C+tcG/t727s9jWzNDOxbu4scXDu8zKwMLAuMLAuMbEu768tN3c0tHPxtHQxufm3QC4y+Kwtbi/vLHDwbi7ubHGw7m7ubHJx77Ny8K+vLTBwLe+vLO9u7PFw7rKyL6/vbTb2c7U0sjc29Dn5dwyysuYJFRLWwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image38\",\n \"title\": \"image38\",\n \"src\": \"/static/6a21335eacb86fe51cfa004efcbab56b/e3189/image38.png\",\n \"srcSet\": [\"/static/6a21335eacb86fe51cfa004efcbab56b/a2ead/image38.png 259w\", \"/static/6a21335eacb86fe51cfa004efcbab56b/6b9fd/image38.png 518w\", \"/static/6a21335eacb86fe51cfa004efcbab56b/e3189/image38.png 1035w\", \"/static/6a21335eacb86fe51cfa004efcbab56b/71e8d/image38.png 1304w\"],\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, \"Example of a Combinatorial Design\"), mdx(\"p\", null, \"Suppose \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is testing an enterprise software system. There is a\\npass/fail deterministic response variable that indicates whether the\\noperator was able to successfully use the system under a specified\\ncondition defined by a combination of factor levels. There are six\\nthree-level categorical factors, so a full factorial requires \", \"[ 3 ^6^\\n=\\u2004729 ]\", \"{.math .inline} runs. The test team cannot afford that many runs,\\nso they use ACTS to investigate how a combinatorial design can reduce\\nthe size of the test. Table 3 shows the number of runs required for a\\ndesign of strength \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" , for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t = 1\"), \" to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"6\"), \" .\"), mdx(\"p\", null, \"Table 3. Number of Runs Required for Strength t\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Strength\"), mdx(\"th\", null, \"Number of Runs\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"1\"), mdx(\"td\", null, \"3\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"2\"), mdx(\"td\", null, \"15\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"3\"), mdx(\"td\", null, \"48\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"4\"), mdx(\"td\", null, \"140\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"5\"), mdx(\"td\", null, \"318\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"6\"), mdx(\"td\", null, \"729\")))), mdx(\"p\", null, \"Suppose the test team has resources for a test with 100 runs. Then if\\nthe test team wants 100% coverage of the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" -tuples, they should use\\nthe combinatorial design of strength 3 with 48 runs. However, since they\\nhave the budget to conduct a test twice that size, the test team\\nconsiders using a subset of the strength 4 design and accepting partial\\ncoverage of the 1215 possible 4\\u2011tuples. Checking the graph of the\\ncoverage ratio vs. the number of test runs (figure 20), the test team\\nlearns that using 100 runs from the strength four design will give\\napproximately 90% coverage of the 4-tuples; this is a very good design\\noption. For more information on combinatorial designs contact the Test\\nDesign and Analyses Division of A-2/9.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#creating-a-combinatorial-design-in-acts","title":"Creating a Combinatorial Design in ACTS:"},{"url":"#example-of-a-combinatorial-design","title":"Example of a Combinatorial Design"}]},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays.md"},"frontmatter":{"metaTitle":"Combinatorial Designs (Covering Arrays)","metaDescription":"Combinatorial Designs (Covering Arrays)"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"032abcf7-25d6-5133-aeb2-974046a98b67"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/2-8-Demonstrations/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/2-8-Demonstrations/page-data.json new file mode 100644 index 00000000..4be6ab3d --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/2-8-Demonstrations/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/2-8-Demonstrations","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"d6fd29b0-b42d-506b-9b83-60511dc04161","title":"Demonstrations","slug":"/analyst_test_design_guide/2-8-Demonstrations"},"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\": \"Demonstrations\",\n \"metaTitle\": \"Demonstrations\",\n \"metaDescription\": \"Demonstrations\"\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, \"Demonstrations are the simplest of the problem identification test\\ndesigns. They are usually single events demonstrating that a system can\\nsuccessfully operate under a particular condition of interest (a single\\nfactor level or specific combination of levels). Demonstrations should\\nonly be used to supplement more statistically rigorous test designs, not\\nused as the primary test design. The test team should methodically\\nselect the factor levels for the demonstration test points using prior\\nknowledge from SMEs.\"), mdx(\"p\", null, \"It is unlikely that any meaningful inferential conclusions can be drawn\\nfrom demonstrations alone, as the principles of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" are rarely applied\\nto these runs. There is usually little to no replication of the factor\\nlevel being evaluated, so it is difficult to characterize the average\\nperformance of the response at the demo'd factor level. Also, for the\\nfactors that are not of interest in a demo run, there is a tendency for\\ntheir levels to be randomly selected during execution. Also, if there\\nare several factors with levels marked for demonstration, these levels\\nmay be combined into a single demo run. These practices add significant\\nambiguity concerning the attribution of system performance to the demo'd\\nfactor's level. If there are several demo runs in a test, it is a best\\npractice to fix the levels of the factors that are not of interest. This\\nallows the impact of the demo levels to be more easily determined in the\\nanalysis.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/2-8-Demonstrations.md"},"frontmatter":{"metaTitle":"Demonstrations","metaDescription":"Demonstrations"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"d6fd29b0-b42d-506b-9b83-60511dc04161"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/2-9-Cases/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/2-9-Cases/page-data.json new file mode 100644 index 00000000..aec2d460 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/2-9-Cases/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/2-9-Cases","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"d07cf22a-9ebb-55d2-98de-3b90410fb48a","title":"Cases","slug":"/analyst_test_design_guide/2-9-Cases"},"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\": \"Cases\",\n \"metaTitle\": \"Cases\",\n \"metaDescription\": \"Cases\"\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, \"Cases are like demonstrations but have several specific combinations of\\nfactors and levels that are intended to be examined together. Types of\\ncase designs include examining the worst or best case configuration of\\nthe factors and levels. The belief is that if a problem exists, it will\\nexhibit itself when the system is operated under the worst possible or\\nbest possible scenario. Sometimes a case design is executed for a\\nspecial-interest item or even political reasons. As with single\\ndemonstrations, it is unlikely the data recorded from these events can\\nbe statistically analyzed.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/2-9-Cases.md"},"frontmatter":{"metaTitle":"Cases","metaDescription":"Cases"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"d07cf22a-9ebb-55d2-98de-3b90410fb48a"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/3-1-Observational-Studies/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/3-1-Observational-Studies/page-data.json new file mode 100644 index 00000000..b921a1cf --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/3-1-Observational-Studies/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/3-1-Observational-Studies","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"85ff243f-1ca2-592b-86f1-a271813a3033","title":"Observational Studies","slug":"/analyst_test_design_guide/3-1-Observational-Studies"},"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\": \"Observational Studies\",\n \"metaTitle\": \"Observational Studies\",\n \"metaDescription\": \"Observational Studies\"\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 pure observational study is a rigorous investigation of treatments and\\nthe effects they cause, but differs from a designed experiment (or test)\\nin that the investigator cannot control the assignment of factor levels\\n(treatments) to the items under test. Consequently, the analysis of the\\ntreatment effects must consider any possible bias due to confounded\\nfactors. When using statistics to draw inferences about a population, it\\nis commonly said, \\\"Correlation does not equal causation.\\\" This is\\nespecially important to remember when using an observational study to\\ndraw conclusions about the performance of a system. Since the test team\\ndoes not change factor level settings and then directly observe a\\nresponse, it is more difficult to attribute the change in a measure\\n(response variable) to the change of a particular factor's level. This\\ndifficulty is caused by the increased likelihood that nuisance factors\\nare strongly correlated with test factors in an observational study,\\nwhich prevents clear attribution of cause and effect between factors and\\nthe measures.\"), mdx(\"p\", null, \"During some \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" tests, it is impossible to control the test\\nconditions. However, there are combinations of factors and levels that\\nthe test team wants to see at some point during the test event. It is a\\nbest practice to create a test event matrix (TEM) for observational\\nstudies which includes all of the factor/level combinations that the\\ntest team desires to see. Then the goal of test planning is to maximize\\nthe probability that each level combination is observed a sufficient\\nnumber of times.\"), mdx(\"p\", null, \"For example, figure 21 shows a portion of the TEM for the notional New\\nAir Force Electronic Pay System (NAFEPS). NAFEPS will replace the Air\\nForce's legacy human resource (HR) software system. Factors in the test\\ninclude the HR business process, the user role executing the process\\n(e.g., HR specialist), the affected member's total force component\\n(e.g., Air Force Reserve), the affected member's classification (e.g.,\\nofficer), and the organization level at which the business process is\\nexecuted (e.g., base level).\"), mdx(\"p\", null, \"Figure 21. TEM for the New Air Force Electronic Pay System (NAFEPS)\"), 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\": \"585px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image39.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\": \"107.33590733590734%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACh0lEQVQ4y41UiXKiQBDl/79mN653zLEaYyWagBEMAZEZGBAEuUcE1G20UknlWPOqq6th5jE9r7thZthAmEgz9YkXRXmOdROThaoZ4IlpI90E001bIxY82o63XAWW4/t+wKkuo8xRo/bn6uqKF4SpIIRhGEVhHEfgD/ERxyAMAqD5nu8noT/VXAYTs1GvctwYtsKCe4DjuCuAu3Id9w2Os/K8kuyVZAHIZLG8vrwcDAbD4bB/0394eBQEgeM4WZbBQ8yyj0+Tp9EBGGNKKaSxoYlo+MwqiGeSrCK83e6KvMjzfLvdFkUBHmIIDq58f1za7Xbg9vu9skwYxwtenp9F8UXDGizvf4Bdyd3PHcq4fqjIM6BPeUGWFV0jeVb8lOyFCcgCWJgLgG0vAz/c/hdwJ/hCmTZUb9DvgxiQOdwty7LNZpMesP4GlK6LLJWsiEHErPz+1ev1CCGGYUAl4kOVwcO+9CvA6222mdkxY7veRaddotVutVqQdpIkUPMgCCA4QY7WG55jm41Gq9W8vLiAOvM8PxoOLcvO8+zLw9/IQZJOxlyjXut2u+ftdrVSqdZqlcqZ+CJB5U6Qw2QNDdWo1yHr8vxmk+U4lmVVhEC8E+SIpv3+TbVardcbve5fCEA8hPB3zA8np6P7u855p3Pehjvf3g4kSYIeBtlPCwZpL21L10k5Ra4LIkOdYfJAMLqmp8g01TXMjyd+EELTZ+U05Bghlh3DAKWvDfMe9F2pUkKwwE9Nw1g6jrVYeCvPti34NVCaHPvtgwF2RaYsY+htCrS5gtQ5wkhXFBWpWhjFMPHQZklCP1sIIiexaIbMreiMZGcou6XNXv3sNf5kd5JzPSH3U1J5MP8BGK6DK+VV5VoAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image39\",\n \"title\": \"image39\",\n \"src\": \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image39.png\",\n \"srcSet\": [\"/static/dce8b102f6f990edb7f2f403dd356157/a2ead/image39.png 259w\", \"/static/dce8b102f6f990edb7f2f403dd356157/6b9fd/image39.png 518w\", \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image39.png 585w\"],\n \"sizes\": \"(max-width: 585px) 100vw, 585px\",\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, \"During \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \", the system will be live and capable of altering real-world\\ndatabases. Without the \\\"sandbox\\\" environment of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \", the test team is\\nunable to direct users to process fictitious paperwork, such as\\nrecording disciplinary actions or retirements. Consequently, the test\\nteam can only observe users executing various HR business processes\\nduring the course of their normal duty.\"), mdx(\"p\", null, \"The TEM aids the test team in determining where and when to observe the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" in order to maximize the probability of observing the factor level\\ncombinations of interest. For example, the test team could choose to\\nsend a team to the Air Reserve Personnel Center (ARPC) at Buckley Air\\nForce Base, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer\"\n }, \"CO\"), \" to observe ARPC HR specialists processing retirement\\npaperwork. For business practices that peak in frequency at various\\ntimes of the year, the test teams will time the site visits accordingly.\"), mdx(\"p\", null, \"Another important question the test team must answer is how long to\\nobserve the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" in order to see all of the factor level combinations of\\ninterest. Some factor level combinations may be relatively rare, such as\\ndesign point 1. \\\"Record Disciplinary Actions\\\" against Regular Air Force\\ncadets. Fortunately there are some simple formulas that can be used for\\nplanning the duration of observational studies.\"), mdx(\"p\", null, \"If the factor level combinations of interest occur at a predictable rate\\nduring some period of time, but completely at random during the time\\nperiod, then the test event can be modeled as a Poisson Process. Poisson\\nprocesses are used to model situations like the arrivals of customers to\\na store, or the number of car accidents in a certain area. The important\\nassumptions are:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The events occur at a certain rate but completely at random within\\nan interval (e.g., on average, 5 customers arrive at a store per\\nhour; but when they arrive within the hour is completely random)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The number of events in some interval of length t is independent of\\nand identically distributed as the number of events in another\\n(disjoint) interval of length t (e.g., the average number of\\ncustomers arriving to the store between 0900 and 1000 is the same\\naverage number arriving between 1100 and 1200)\"))), mdx(\"p\", null, \"In the context of observational studies, the arrivals of interest are\\nthe rare factor level combinations. It suffices to focus on the\\nprobabilities of the rare factor level combinations, as the\\nprobabilities of observing the more common events will be greater and\\ntherefore are not limiting factors.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 1: Calculating the Time to Observe One Rare Event with\\nSpecified Probability.\"), \" Suppose we want to know the test time \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" that\\ngives a probability of 80% (p = 0.8) that the test team will observe a\\nrare factor level combination.\"), mdx(\"p\", null, \"The first step is to estimate the rate \", \"[ \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\u03BB\"), \" ]\", \"{.math .inline} of the\\naverage number of events per time period. Suppose a rare factor level\\ncombination occurs randomly 1 time every 3 working days (on average)\\nwhile a system is operating. Assuming an 8 hour work day, this is 1\\nevent every 24 working hours, implying \", \"[ \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\u03BB\"), \" ]\", \"{.math .inline} =\\xA00.042\\nevents per hour.\"), mdx(\"p\", null, \" \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\frac{\\\\mathbf{1}\\\\ \\\\mathbf{\\\\text{event}}}{\\\\mathbf{24}\\\\ \\\\mathbf{\\\\text{hours}}}\\\\overset{\\\\Rightarrow}{\\\\ }\\\\mathbf{\\\\lambda} = \\\\mathbf{0}.\\\\mathbf{042}\\\\ \\\\mathbf{\\\\text{events}}/\\\\mathbf{\\\\text{hour}}\"), \" \"), mdx(\"p\", null, \"Step 2 is to convert 80% into the decimal p = 0.8 and use the following\\nformula to calculate the test\\xA0time\\xA0t.\"), mdx(\"p\", null, \" \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\mathbf{t} = \\\\frac{- \\\\mathbf{\\\\ln}\\\\left( \\\\mathbf{1} - \\\\mathbf{p} \\\\right)}{\\\\mathbf{\\\\lambda}}\"), \" \"), mdx(\"p\", null, \" \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\mathbf{t} = \\\\frac{- \\\\mathbf{\\\\ln}\\\\left( \\\\mathbf{1} - \\\\mathbf{0}.\\\\mathbf{8} \\\\right)}{\\\\mathbf{0}.\\\\mathbf{042}} = \\\\mathbf{38}.\\\\mathbf{3}\\\\ \\\\mathbf{\\\\text{hours}}\"), \" \"), mdx(\"p\", null, \"The analysis shows that 38.3 test hours are required to have an 80%\\nchance of observing a factor level combination that occurs randomly 1\\ntime every 24 hours (on average.)\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 2: Calculating the Time to Observe \", mdx(\"em\", {\n parentName: \"strong\"\n }, \"k\"), \" Rare Events with\\nSpecified Probability.\"), \" Suppose we want to know the test time \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" that\\ngives us an 80% probability (p = 0.8) chance of observing k = 3\\noccurrences of a rare factor level combination that occurs randomly 1\\ntime every 3 working days (on average). We already calculated that \", \"[\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\u03BB\"), \" ]\", \"{.math .inline} =\\xA00.042 events per hour. In this example a more\\ncomplicated formula is required:\"), mdx(\"p\", null, \" \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\mathbf{1} - \\\\mathbf{p} = \\\\sum\\\\_{\\\\mathbf{n} = \\\\mathbf{0}}^{\\\\mathbf{k} - \\\\mathbf{1}}{\\\\frac{\\\\mathbf{1}}{\\\\mathbf{n}!}\\\\mathbf{e}^{- \\\\mathbf{\\\\lambda}\\\\mathbf{t}}\\\\left( \\\\mathbf{\\\\lambda}\\\\mathbf{t} \\\\right)^{\\\\mathbf{n}}}\"), \" \"), mdx(\"p\", null, \"Plugging in the values we know (p = 0.8, k = 3, \", \"[ \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\u03BB\"), \" ]\", \"{.math .inline}\\n=\\xA00.042) we have\"), mdx(\"p\", null, \" \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\mathbf{0}.\\\\mathbf{20} = \\\\mathbf{e}^{- \\\\mathbf{0}.\\\\mathbf{042}\\\\mathbf{t}} + \\\\mathbf{e}^{- \\\\mathbf{0}.\\\\mathbf{042}\\\\mathbf{t}}\\\\left( \\\\mathbf{0}.\\\\mathbf{042}\\\\mathbf{t} \\\\right) + \\\\frac{\\\\mathbf{1}}{\\\\mathbf{2}}\\\\mathbf{e}^{- \\\\mathbf{0}.\\\\mathbf{042}\\\\mathbf{t}}\\\\left( \\\\mathbf{0}.\\\\mathbf{042}\\\\mathbf{t} \\\\right)^{\\\\mathbf{2}}\"), \" \"), mdx(\"p\", null, \"A simple way to solve this equation for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" is to use Excel's solver\\nfunction to find the value for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" that minimizes the difference between\\nthe equation's right hand side and the left hand side (0.2 in this\\nexample.) The solver reports that \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" =\\xA071.3 hours. This means we must\\nobserve the system 71.3 hours in order to have an 80% chance of seeing 3\\noccurrences of a rare factor level combination that occurs 1 time every\\n3 working days (on average.)\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 3: Calculating the Probability of Observing a Rare Event with\\nSpecified Time.\"), \" Suppose the resource constraints have imposed a limit\\nof 4 working days (32 hours) for the observational study. Given a fixed\\ntest time \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" = 32 hours, we want to determine the probability of\\nobserving a rare factor level combination that occurs randomly 1 time\\nevery 3 working days. In other words, if \", \"[ \", mdx(\"em\", {\n parentName: \"p\"\n }, \"T\"), \" ~1~ ]\", \"{.math .inline} is\\nthe time of the first occurrence of the rare event, then we want the\\nprobability that \", \"[ \", mdx(\"em\", {\n parentName: \"p\"\n }, \"T\"), \" ~1~ ]\", \"{.math .inline} is less than \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" : P \", \"[ ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"T\"), \"\\n~1~ \\\\< \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" ) ]\", \"{.math .inline} . Recall that \", \"[ \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\u03BB\"), \" ]\", \"{.math .inline}\\n=\\xA00.042 events per hour. The formula to use is:\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"**P** ( **T** **1** **<** **t** ) **=** **1** **\\u2212** **e** **\\u2212** (\\u03BBt) \\n\\n**P** ( **T** **1** **<** **32** ) **=** **1** **\\u2212** **e** **\\u2212** **(** **0.042** **)** **(** **32** **)** **=** **0.74** \\n\")), mdx(\"p\", null, \"Therefore we have a 74% chance of seeing the rare event during the 32\\nhour test.\"), mdx(\"p\", null, \"In summary, the three formulas in Examples 1-3 provide probability\\nassessments that can be used to plan the duration of observational\\nstudies, as well as characterize the risk of not observing important\\nfactor level combinations.\"), mdx(\"p\", null, \"An observational study should only be used when it is impossible to\\ncontrol the factor levels. They must have sufficient documentation to\\nprove the test team will gather the appropriate data to answer all of\\nthe desired questions. While an observational study is not the ideal\\ntest scenario, with proper planning these tests can provide data to\\ncharacterize the performance of the system. For more information on the\\nuse of an observational study for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test program, and the theory\\nbehind the use of Poisson Process modeling, please contact the Test\\nDesign and Analyses Division of A-2/9.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/3-1-Observational-Studies.md"},"frontmatter":{"metaTitle":"Observational Studies","metaDescription":"Observational Studies"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"85ff243f-1ca2-592b-86f1-a271813a3033"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT/page-data.json new file mode 100644 index 00000000..91c0402a --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"8d58b0f8-22c1-5f3e-9590-75dcbe997d30","title":"TEST DESIGN MEASURES OF MERIT","slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT"},"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 DESIGN MEASURES OF MERIT\",\n \"metaTitle\": \"TEST DESIGN MEASURES OF MERIT\",\n \"metaDescription\": \"TEST DESIGN MEASURES OF MERIT\"\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, \"All test designs have associated measures of merit, or quality\\nindicators, which should be considered when deciding on a test design.\\nTest design measures of merit include power, optimality efficiency,\\ncorrelation, prediction variance, resolution, strength, and coverage.\\nThe most commonly encountered and generally applicable test design\\nmeasures of merit are presented in this section. Note that some measures\\nof merit which pertain to specific design types (like strength and\\ncoverage for combinatorial designs) are discussed in the sections of\\nthis guide corresponding to the relevant designs.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT.md"},"frontmatter":{"metaTitle":"TEST DESIGN MEASURES OF MERIT","metaDescription":"TEST DESIGN MEASURES OF MERIT"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"8d58b0f8-22c1-5f3e-9590-75dcbe997d30"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/3-3-Power/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/3-3-Power/page-data.json new file mode 100644 index 00000000..75fd04dd --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/3-3-Power/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/3-3-Power","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"bcda7632-6140-50ac-af5f-56f7d6608c69","title":"Power","slug":"/analyst_test_design_guide/3-3-Power"},"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\": \"Power\",\n \"metaTitle\": \"Power\",\n \"metaDescription\": \"Power\"\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, \"In a hypothesis test, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"power\"), \" is a measure of the probability the null\\nhypothesis will be correctly rejected when it is false. In the context\\nof statistical modeling, the null hypothesis is that a factor is not\\nactive (has no effect on the response); therefore in that context power\\nrefers to the probability the test data will correctly identify a factor\\nas active. Power is a function of the test design, significance level,\\nsignal (e.g., difference in the response between factor levels), and\\nnoise (natural variation in the measure for a given test run.)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" calculates power over a range of signal to noise ratios (SNR) at\\na significance level of \", \"[ \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u03B1\"), \" =\\u20040.2 ]\", \"{.math .inline} . SNR refers to the\\nratio of the minimum desired detectable difference, delta (\\u03B4), and the\\nstandard deviation of the response values at a given design point, sigma\\n(\\u03C3). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" typically evaluates power for 0\\xA0\\\\<\\xA0\\u03B4/\\u03C3\\xA0\\\\<\\xA0 3.5; the range of\\ninterest for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" is usually between 1\\xA0\\\\<\\xA0\\u03B4/\\u03C3\\xA0\\\\<\\xA02. Rather\\nthan using a SNR, power can also be calculated by using SMEs,\\nrequirements documents, and previous system data (from a legacy system\\nor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \") to identify appropriate values for \\u03B4 and \\u03C3.\"), mdx(\"p\", null, \"A rule of thumb is to employ designs with a minimum power of 80% for\\neffects of interest. Power analysis for a designed experiment requires\\nthe following information:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The test design matrix metadata (which includes the number of\\nfactors, levels for each factor, and sample size)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The proposed statistical model\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The significant level (\\u03B1)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The desired detectable change in the response (\\u03B4)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The standard deviation of the response value at a given design point\\n(\\u03C3); the assumption for power analysis is that \\u03C3 is the same at all\\ndesign points.\"))), mdx(\"p\", null, \"List items 4 and 5 can be combined into a SNR value.\"), mdx(\"p\", null, \"Power calculations for binary response variables are different than\\nthose for continuous response variables. More information on calculating\\npower for binomial response variables can be found here:\"), mdx(\"p\", null, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdf\"\n }, \"http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdf\"), \"\\n. (Ortiz, 2014)\"), mdx(\"p\", null, \"For guidance on creating power curves or power calculations in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nrefer to the November 2014 guide, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Power Analysis Tutorial for\\nExperimental Design Software,\"), \" which can be found on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nSharePoint in the Analyst and Engineer Community. Contact the Test\\nDesign and Analyses Division of A-2/9 for assistance creating or\\ninterpreting power curves.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/3-3-Power.md"},"frontmatter":{"metaTitle":"Power","metaDescription":"Power"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"bcda7632-6140-50ac-af5f-56f7d6608c69"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/3-4-Optimality-Efficiency/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/3-4-Optimality-Efficiency/page-data.json new file mode 100644 index 00000000..2e24fefe --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/3-4-Optimality-Efficiency/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/3-4-Optimality-Efficiency","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"41fc26e9-5c67-5d70-aa66-bef1c3fab0e0","title":"Optimality (Efficiency)","slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency"},"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\": \"Optimality (Efficiency)\",\n \"metaTitle\": \"Optimality (Efficiency)\",\n \"metaDescription\": \"Optimality (Efficiency)\"\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 important measure of merit for optimal designs is the optimality\\nefficiency. The optimality relates to the criteria used to determine the\\n\\\"best\\\" design during execution of the design construction algorithm. JMP\\ncalculates efficiencies for the D \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn34\"\n }, \"34\"), \", G \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn35\"\n }, \"35\"), \" and A \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn36\"\n }, \"36\"), \" optimality criteria, which were discussed in the Optimal Designs section of this guide. The efficiencies are\\nthe ratio of the optimality criterion value of the evaluated design to\\nthe optimal value of an ideal (perhaps unobtainable) design of the same\\ndimensions. When JMP constructs a computer generated design, it reports\\nthe D, G, and A efficiencies under the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Design Diagnostics\"), \" header under\\n\\\" \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Design Evaluation\"), \" \\\" (figure 22).\"), mdx(\"p\", null, \"Figure 22. Optimality Efficiencies under Design Diagnostics\"), 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\": \"585px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image40.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\": \"107.33590733590734%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACh0lEQVQ4y41UiXKiQBDl/79mN653zLEaYyWagBEMAZEZGBAEuUcE1G20UknlWPOqq6th5jE9r7thZthAmEgz9YkXRXmOdROThaoZ4IlpI90E001bIxY82o63XAWW4/t+wKkuo8xRo/bn6uqKF4SpIIRhGEVhHEfgD/ERxyAMAqD5nu8noT/VXAYTs1GvctwYtsKCe4DjuCuAu3Id9w2Os/K8kuyVZAHIZLG8vrwcDAbD4bB/0394eBQEgeM4WZbBQ8yyj0+Tp9EBGGNKKaSxoYlo+MwqiGeSrCK83e6KvMjzfLvdFkUBHmIIDq58f1za7Xbg9vu9skwYxwtenp9F8UXDGizvf4Bdyd3PHcq4fqjIM6BPeUGWFV0jeVb8lOyFCcgCWJgLgG0vAz/c/hdwJ/hCmTZUb9DvgxiQOdwty7LNZpMesP4GlK6LLJWsiEHErPz+1ev1CCGGYUAl4kOVwcO+9CvA6222mdkxY7veRaddotVutVqQdpIkUPMgCCA4QY7WG55jm41Gq9W8vLiAOvM8PxoOLcvO8+zLw9/IQZJOxlyjXut2u+ftdrVSqdZqlcqZ+CJB5U6Qw2QNDdWo1yHr8vxmk+U4lmVVhEC8E+SIpv3+TbVardcbve5fCEA8hPB3zA8np6P7u855p3Pehjvf3g4kSYIeBtlPCwZpL21L10k5Ra4LIkOdYfJAMLqmp8g01TXMjyd+EELTZ+U05Bghlh3DAKWvDfMe9F2pUkKwwE9Nw1g6jrVYeCvPti34NVCaHPvtgwF2RaYsY+htCrS5gtQ5wkhXFBWpWhjFMPHQZklCP1sIIiexaIbMreiMZGcou6XNXv3sNf5kd5JzPSH3U1J5MP8BGK6DK+VV5VoAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image40\",\n \"title\": \"image40\",\n \"src\": \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image40.png\",\n \"srcSet\": [\"/static/dce8b102f6f990edb7f2f403dd356157/a2ead/image40.png 259w\", \"/static/dce8b102f6f990edb7f2f403dd356157/6b9fd/image40.png 518w\", \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image40.png 585w\"],\n \"sizes\": \"(max-width: 585px) 100vw, 585px\",\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 efficiency values will range from 0-100% with 100% being the best.\\nFor more information, please consult the JMP documentation or contact\\nthe Test Design and Analyses Division of A-2/9. \"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/3-4-Optimality-Efficiency.md"},"frontmatter":{"metaTitle":"Optimality (Efficiency)","metaDescription":"Optimality (Efficiency)"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"41fc26e9-5c67-5d70-aa66-bef1c3fab0e0"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/3-5-Correlation-Multicollinearity/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/3-5-Correlation-Multicollinearity/page-data.json new file mode 100644 index 00000000..fa840636 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/3-5-Correlation-Multicollinearity/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"9bc35eee-946d-5b36-a59f-48a4e6fa5358","title":"Correlation (Multicollinearity)","slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity"},"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\": \"Correlation (Multicollinearity)\",\n \"metaTitle\": \"Correlation (Multicollinearity)\",\n \"metaDescription\": \"Correlation (Multicollinearity)\"\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, \"Correlation between two factors is a statistical measure that indicates\\nthe extent to which the levels of those factors vary together. A\\npositive correlation indicates that factors increase or decrease in\\nparallel; a negative correlation indicates that one factor increases as\\nthe other decreases.\"), mdx(\"p\", null, \"It is undesirable to have correlated factors in a test design. First,\\nwhen two active factors are perfectly correlated, it is not possible to\\nquantify the independent effect of each factor on the response. Second,\\ncorrelated factors increase the variance of the estimates of the\\nstatistical model parameters and the estimates of the mean response\\nvalue.\"), mdx(\"p\", null, \"Bias due to multicollinearity can be unintentionally introduced when\\ninfluential and controllable factors that are not of interest\\noperationally are allowed to vary randomly during the test event. This\\nsituation may occur when the test team decides to exclude medium impact\\nfactors from the list of varied factors in order to prevent the design\\nfrom becoming too large, or to prevent the test from having low power.\\nIt is poor practice to label these excluded factors as \\\"logged\\\" factors,\\nas the chances of biased data becomes far more likely. Instead, include\\nthese factors in an \\\"off-line\\\" test design (that will be used for test\\nexecution) if you think post-test analysis might possibly involve them.\\nThese factors can be omitted from the reported design for the purposes\\nof calculating measures of merit like power.\"), mdx(\"p\", null, \"A correlation matrix shows the linear relationship between any pair of\\nfactors. If any of the values in the correlation matrix is above 0.5,\\nthe design should be adjusted if possible to reduce the correlation. JMP\\nwill produce a \\\"Color Map on Correlations\\\" in the \\\"Design Diagnostics\\\"\\ntab. Figure 23 shows two \\\"Color Map on Correlations\\\" plots from JMP.\"), mdx(\"p\", null, \"Figure 23. Examples of Color Maps\"), 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\": \"425px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image41.jpg\",\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\": \"118.53281853281852%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/jpeg;base64,/9j/2wBDABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVGC8aGi9jQjhCY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2P/wgARCAAYABQDASIAAhEBAxEB/8QAGAABAQEBAQAAAAAAAAAAAAAAAAUBAwT/xAAXAQADAQAAAAAAAAAAAAAAAAABAwQC/9oADAMBAAIQAxAAAAGvkXHi+4Emd5S3FoRM/8QAHhAAAQQBBQAAAAAAAAAAAAAAAwABAhEzBBAhIjL/2gAIAQEAAQUC6WztsSNmuKDjLxPytPg//8QAGBEAAwEBAAAAAAAAAAAAAAAAAAEREFH/2gAIAQMBAT8BfcsY1HD/xAAZEQADAQEBAAAAAAAAAAAAAAAAARECQQP/2gAIAQIBAT8BXlzo1DCuRuun/8QAHRAAAgEEAwAAAAAAAAAAAAAAAAECECExcRFhsf/aAAgBAQAGPwLKLNUnssLnJLZ34RP/xAAfEAEAAgAGAwAAAAAAAAAAAAABABEhMUFRYZEQcaH/2gAIAQEAAT8hWy+8lP4mCVmRKhriGDy2wXiY0BunrlN63x4w6Z//2gAMAwEAAgADAAAAEF8AfP/EABkRAAMAAwAAAAAAAAAAAAAAAAABERAxQf/aAAgBAwEBPxBoo1hMFhOH/8QAGREBAQEAAwAAAAAAAAAAAAAAAQARMUHw/9oACAECAQE/EBeU0JAW+yRF3f/EAB0QAQACAgMBAQAAAAAAAAAAAAEAESExQVFhkfD/2gAIAQEAAT8QMBW8iSMVRPgyize3M39I/ZS4mQmh2e+bhbSOHc22CPY2RpX3+bhCACpfcs//2Q==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image41\",\n \"title\": \"image41\",\n \"src\": \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image41.jpg\",\n \"srcSet\": [\"/static/70c09ba0146ea8fcde79f75b00b8fde7/8356d/image41.jpg 259w\", \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image41.jpg 425w\"],\n \"sizes\": \"(max-width: 425px) 100vw, 425px\",\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(\"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\": \"425px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image42.jpg\",\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\": \"118.53281853281852%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/jpeg;base64,/9j/2wBDABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVGC8aGi9jQjhCY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2P/wgARCAAYABQDASIAAhEBAxEB/8QAGAABAQEBAQAAAAAAAAAAAAAAAAUBAwT/xAAXAQADAQAAAAAAAAAAAAAAAAABAwQC/9oADAMBAAIQAxAAAAGvkXHi+4Emd5S3FoRM/8QAHhAAAQQBBQAAAAAAAAAAAAAAAwABAhEzBBAhIjL/2gAIAQEAAQUC6WztsSNmuKDjLxPytPg//8QAGBEAAwEBAAAAAAAAAAAAAAAAAAEREFH/2gAIAQMBAT8BfcsY1HD/xAAZEQADAQEBAAAAAAAAAAAAAAAAARECQQP/2gAIAQIBAT8BXlzo1DCuRuun/8QAHRAAAgEEAwAAAAAAAAAAAAAAAAECECExcRFhsf/aAAgBAQAGPwLKLNUnssLnJLZ34RP/xAAfEAEAAgAGAwAAAAAAAAAAAAABABEhMUFRYZEQcaH/2gAIAQEAAT8hWy+8lP4mCVmRKhriGDy2wXiY0BunrlN63x4w6Z//2gAMAwEAAgADAAAAEF8AfP/EABkRAAMAAwAAAAAAAAAAAAAAAAABERAxQf/aAAgBAwEBPxBoo1hMFhOH/8QAGREBAQEAAwAAAAAAAAAAAAAAAQARMUHw/9oACAECAQE/EBeU0JAW+yRF3f/EAB0QAQACAgMBAQAAAAAAAAAAAAEAESExQVFhkfD/2gAIAQEAAT8QMBW8iSMVRPgyize3M39I/ZS4mQmh2e+bhbSOHc22CPY2RpX3+bhCACpfcs//2Q==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image42\",\n \"title\": \"image42\",\n \"src\": \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image42.jpg\",\n \"srcSet\": [\"/static/70c09ba0146ea8fcde79f75b00b8fde7/8356d/image42.jpg 259w\", \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image42.jpg 425w\"],\n \"sizes\": \"(max-width: 425px) 100vw, 425px\",\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 horizontal labels across the top are the main effects and the\\n2-factor interactions. The labels on the vertical axis are not shown but\\nare the same as the horizontal axis. The scale on the right indicates\\nthe amount of pair-wise correlation. Royal blue indicates no correlation\\nand red indicates perfect correlation. The plot on the left is the\\noptimal, and depicts no correlation between any of the factors or their\\n2-factor interactions (the red diagonal is the correlation of each\\nfactor with itself and therefore shows red for perfect correlation.)\"), mdx(\"p\", null, \"The color map on the right shows a plot with some partial correlation\\nbetween the main effects and one or more 2-factor interactions, as\\nindicated by the grey color. The upper left 4x4 portion of the map (in\\nthe black square) shows us that no main effect is correlated with any\\nother main effect. If a completely blue map (apart from the diagonal)\\ncannot be achieved, attempt to make the correlation between main effects\\nas small as possible. \"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/3-5-Correlation-Multicollinearity.md"},"frontmatter":{"metaTitle":"Correlation (Multicollinearity)","metaDescription":"Correlation (Multicollinearity)"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"9bc35eee-946d-5b36-a59f-48a4e6fa5358"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/3-6-Prediction-Variance/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/3-6-Prediction-Variance/page-data.json new file mode 100644 index 00000000..0e803bfc --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/3-6-Prediction-Variance/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/3-6-Prediction-Variance","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"76017247-2e43-5d20-b382-529ccefe4a12","title":"Prediction Variance","slug":"/analyst_test_design_guide/3-6-Prediction-Variance"},"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\": \"Prediction Variance\",\n \"metaTitle\": \"Prediction Variance\",\n \"metaDescription\": \"Prediction Variance\"\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, \"Prediction variance is a test design measure of merit which provides\\ninformation regarding the variability in the estimate of the response\\nvariable at a particular point in the design space. It essentially\\nquantifies how precise the model is in estimating the true average\\nresponse. If the prediction variance is large, the true average response\\nvalue may be quite different from the model's estimate.\"), mdx(\"p\", null, \"Prediction variance is a function of both natural system variation ( \", \"[\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u03C3\"), \" ^2^ ) ]\", \"{.math .inline} and the structure of the experimental design.\\nRelative prediction variance considers only the experimental design's\\ninfluence on the prediction variance (independent of natural system\\nvariation). Although we do not usually create predictive statistical\\nmodels at \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", this metric can still be useful because the predictive\\nvariance is indicative of the design quality.\"), mdx(\"p\", null, \"JMP provides graphical tools that are useful for assessing the\\nprediction variance of a test design. They are the \\\" \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Prediction\\nVariance Profiler\"), \" \\\" (2D and 3D) and the \\\" \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Fraction of the Design\\nSpace\"), \" \\\" (FDS) plot.\"), mdx(\"p\", null, \"Figure 24. Example of JMP\\\\'s 2D Prediction Variance Profiler\"), 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\": \"501px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/c98d5250b1fb3e6f9f7d182add9ecc15/55811/image43.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,iVBORw0KGgoAAAANSUhEUgAAABQAAAAKCAYAAAC0VX7mAAAACXBIWXMAAA7DAAAOwwHHb6hkAAABTUlEQVQoz21SCXKDMAzk/59MSUNCpk0awId8YFUrbJIemhGypdW1puNSGLKuK4cQOMW4aUqqRMQR/nqHRonDr/fwxCO/W3mTeZrVwas0qE0gABbR35JzVltgKx7YjsYPZikWKXCQTq0gpkgCzihYk5tQqNhttd2PnC5TUOfj8WDyxEVWsPPMzhgtlCTZL0atFWuXhck6iVs9A6tW1DvHXaturWEjoIzuwk+u05HzbKZJKSHvJbbxjDN49NZWP20clpdHgdxuNx0dD3G/37Wwd1uCleQF04g1skE7w2JDXVmJlaKt8HUcmVAwJ76cz9zi8tWmDQvFfYUVRWP49gmb1ZcWHjM4En2N/Ssp4zW4Ap8ctqQYZdW3I5fPrx9+J4SPx5Ou9fpLXft3jtOyY/8UDIH4NAw8DBclvYlZZj4c3pSz/TeRbfq+58t4VUog374sEE46rUhmAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image43\",\n \"title\": \"image43\",\n \"src\": \"/static/c98d5250b1fb3e6f9f7d182add9ecc15/55811/image43.png\",\n \"srcSet\": [\"/static/c98d5250b1fb3e6f9f7d182add9ecc15/a2ead/image43.png 259w\", \"/static/c98d5250b1fb3e6f9f7d182add9ecc15/55811/image43.png 501w\"],\n \"sizes\": \"(max-width: 501px) 100vw, 501px\",\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 prediction variance profiler (figure 24) in JMP plots the relative\\nvariance of prediction as a function of each factor level. These plots\\ncan be used to identify combination of factor levels with high\\nprediction variance. It is ideal for the prediction variance to be small\\nthroughout the design region. Generally, the prediction variance drops\\nas the sample size increases.\"), mdx(\"p\", null, \"A fraction of the design space (FDS) plot (figure 25) may be created in\\nJMP to show what proportion of the design space has prediction variance\\nat or below a given level.\"), mdx(\"p\", null, \"Figure 25. Fraction of Design Space Plot\"), 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/b410856306118d0933a88a9dbc9445b6/8b46b/image44.jpg\",\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\": \"73.35907335907336%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/jpeg;base64,/9j/2wBDABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVGC8aGi9jQjhCY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2P/wgARCAAPABQDASIAAhEBAxEB/8QAFgABAQEAAAAAAAAAAAAAAAAAAAEF/8QAFAEBAAAAAAAAAAAAAAAAAAAAAP/aAAwDAQACEAMQAAAB3aAH/8QAFRABAQAAAAAAAAAAAAAAAAAAASD/2gAIAQEAAQUCK//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQMBAT8BP//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQIBAT8BP//EABQQAQAAAAAAAAAAAAAAAAAAACD/2gAIAQEABj8CX//EABkQAQADAQEAAAAAAAAAAAAAAAEAESEQMf/aAAgBAQABPyHSyuAiy98mz//aAAwDAQACAAMAAAAQQM//xAAUEQEAAAAAAAAAAAAAAAAAAAAQ/9oACAEDAQE/ED//xAAUEQEAAAAAAAAAAAAAAAAAAAAQ/9oACAECAQE/ED//xAAbEAADAQEAAwAAAAAAAAAAAAAAARExIVFxof/aAAgBAQABPxBLPMJr0iTcIAlHnRPxr2Ss+n//2Q==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image44\",\n \"title\": \"image44\",\n \"src\": \"/static/b410856306118d0933a88a9dbc9445b6/af659/image44.jpg\",\n \"srcSet\": [\"/static/b410856306118d0933a88a9dbc9445b6/8356d/image44.jpg 259w\", \"/static/b410856306118d0933a88a9dbc9445b6/bc760/image44.jpg 518w\", \"/static/b410856306118d0933a88a9dbc9445b6/af659/image44.jpg 1035w\", \"/static/b410856306118d0933a88a9dbc9445b6/8b46b/image44.jpg 1330w\"],\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 figure shows that 50% of the design region has a relative prediction\\nvariance below 0.039. The \\\"flatness\\\" of the plot is an indication of the\\nprediction variance stability; i.e., the prediction variance does not\\nsignificantly increase in some portion of the design region. Comparing\\nthe FDS plot for two designs side-by-side is one way to compare two\\ndesigns; the preferred design is the one with lower prediction variance\\non average throughout the design space.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/3-6-Prediction-Variance.md"},"frontmatter":{"metaTitle":"Prediction Variance","metaDescription":"Prediction Variance"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"76017247-2e43-5d20-b382-529ccefe4a12"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit/page-data.json new file mode 100644 index 00000000..a3f5fabf --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"f6289bcd-a5c2-5568-affb-54e607ea7ab3","title":"Comparing Measures of Merit","slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit"},"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\": \"Comparing Measures of Merit\",\n \"metaTitle\": \"Comparing Measures of Merit\",\n \"metaDescription\": \"Comparing Measures of Merit\"\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, \"JMP has created the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Compare Designs\"), \" platform to provide a convenient\\nway to compare two or three designs.\"), mdx(\"p\", null, \"Comparing Designs in JMP\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"From the menu above one of the design tables, launch the platform by\\nselecting \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" , then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Design Diagnostics\"), \" , then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Compare\\nDesigns\"), \" (figure 26a).\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Compare Reference Design With\"), \" box, select the\\nother designs to be compared (figure 26b).\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 26a. Comparing Designs in JMP Figure 26b. Choosing Designs to Compare\\n\", 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\": \"640px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/53bcebe7d11ca1ec4310fd2bf86936ac/6af66/image45.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\": \"67.56756756756756%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAAB/ElEQVQoz32SWY+bMBDH+f5fo+9VVamvfVlp092w2SXJFsqVcGNzmcMXgdAhJI16qKMfI8vM357DShBFYYwOXuSHcZTgnDRU9HXL6o41ABV1xxs6A4uqoUBO2r6XDzZRHMe1TMswLMt2jkfPMk3bNH3fzzDGaTp7hGCR5xlKkhQsSSpSn3v+aJdK4rt5Eqahh4IDBo8g5hpEKRNCcM7B4ywndSv72biQ0yBXh1r5vA4/PQUfV/6XffvVaLquK7Js+/a22byqqhqEUVmWeZH/cIPVyx7lREpJGZ/Fbq28o9HAo46Gl/i8jU8d5yTyzaeVZbmGbjRtO01THMee7+/3+6Io4GbGb+LpLK9MchxFx3iLUaC/RynuJeyMwzCAJgxDXderqoSb72IorKNs8QBUSAhx3YPruqZlYZxB2lVVQTlt2zI2d4FxcRVLKe4GvelPdRob62fDMLfarqoI5AkthEPlLfR/4g4l7kY9+lFZlKCEzGEEy51/ii+z4Ms8wOD4HKOj43ieDyOGEiilTdP8CvhNPAynxZaRghiS1DRtp2nb7a5umjmasX+L0fwgIC88dwv0cyiHCTXwQYc4p4wBy68FysV5kI8g7uqqq0lLql7yoRcz8uJ7eUH8DbRpGsXzsVZeD9XGnVGd4opdrG/cN2+s7fzhe6oa8YdvyU+KeAk+5cBw8QAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image45\",\n \"title\": \"image45\",\n \"src\": \"/static/53bcebe7d11ca1ec4310fd2bf86936ac/6af66/image45.png\",\n \"srcSet\": [\"/static/53bcebe7d11ca1ec4310fd2bf86936ac/a2ead/image45.png 259w\", \"/static/53bcebe7d11ca1ec4310fd2bf86936ac/6b9fd/image45.png 518w\", \"/static/53bcebe7d11ca1ec4310fd2bf86936ac/6af66/image45.png 640w\"],\n \"sizes\": \"(max-width: 640px) 100vw, 640px\",\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(\"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\": \"640px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/78f05b64bb96fe33d158c4505e324d22/6af66/image46.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\": \"67.56756756756756%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAACJ0lEQVQoz31S30/bMBDO//+4x2nStpe9TUWwCYk9rAhWNNq0FApJmzRt0vyy4zRJHcdnp03mjlFAmjh9Op/O33e+s62tgsAP0cINPD8MIkzyDQNZ0Kooq40Cg6LkG7aHCrINUyA5lVJc2Lk2ny+smW2almU7y6VrzWb2bOZ5XoIxjuO9R0gFhCQoimJlUZTlRSP4uYm1yJuTaBX7S7RysPJIcf6RGKsAgHOuPE5IXlAh98ZBNBKOf1vaySg51lGnH383RNeCkrE0Se7Ho7ub4Y3ej0O/LNZpSqbO6kqfIJILARWHpoaj3lS7T9opaU3SDuP2Dm0pBxa6nbPxu+76/Tn+ctt80BtjEQa+N5lM0jQVQuzFEo6uplrbQLsTezSw2/KyqihGy4eHRZgwLrlsKN8mJA183zCMLFu/EqvBSlY9egU1oboP33Ui13bnJl0jWa6LPKO0pJRW1eMtPInVDM+m0rLexP63s+uPP51PP8yT27wz3thuIIGLJ+pbYobCQU+/NBIzZHbajAOxCmPg1UvW/8QAqjzBOFraOHAzgniZt3VVlrT6+2BvifcHS+EH4aV+29PHw9FNFOMYIUIIvO5PiTu/TA0EqJoHKMso+9odnPWNpesFofowKEmSlxzGYVfD6cjV1LKVz6glQFXiYEXicCtFu63bZqeSteAHjmq23cGVnWq6kw7mr2Gnw0U+cLK+Tfp22rfItUUOuyp58RAPzPBzL/gDYqoAw9U+fDIAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image46\",\n \"title\": \"image46\",\n \"src\": \"/static/78f05b64bb96fe33d158c4505e324d22/6af66/image46.png\",\n \"srcSet\": [\"/static/78f05b64bb96fe33d158c4505e324d22/a2ead/image46.png 259w\", \"/static/78f05b64bb96fe33d158c4505e324d22/6b9fd/image46.png 518w\", \"/static/78f05b64bb96fe33d158c4505e324d22/6af66/image46.png 640w\"],\n \"sizes\": \"(max-width: 640px) 100vw, 640px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Matching Specification\"), \" Box, you can specify which columns\\nare equivalent (matched) in the two designs. Click the gray triangle\\nto reveal the Match button. Highlight a factor in each design and\\nclick \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Match\"), \" .\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\"), \" in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Action\"), \" box (figure 27a).\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Measures of Merit for all of the designs such as power (figure 27b),\\nprediction variance, FDS plots, and optimality efficiencies are\\nprovided in the output.\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 27a. Matching Columns of Multiple Designs Figure 27b. Comparing Power of Two Designs\\n\", 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\": \"534px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/90235aadeb4b6aaca7825a8b91ad266a/a07a7/image47.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\": \"108.1081081081081%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAWCAYAAADAQbwGAAAACXBIWXMAAA7DAAAOwwHHb6hkAAADKUlEQVQ4y4WU+U8TQRTH+//6g8Yj8TYe8cB4RCK/GC+qSESM/mC8wKAi7S69D4sIFltoaSlld9tt95r5+ma2RYQuTvLy9r2d+cz3vZ2d0MJCAfPzKqKRCMqrq+h0OjAMA61Wa7AZvjekb0PX9W3TyEKe51GgodlsotVuo2OaMP9nbRNdq03zNTDG0R+cc4T6QVox4JguaqsuKssuZVw4jgvX3W0ePK+D3Pc2pmc2YOh11GobWK9U4dD7EEHhMhuRaR1gQH0VqPzs74iBw4ONasbB8oyFTa2KyloV5VJZCpBAThNm3ukoRDmibxjmXjKBkyXsNjG6HUtCB40QZ1ILPr5oIXya4fFVhofnGJxNf7HoUR9ET9LbjgXLskViz4Yh12WwXANvx5t4epaA1xgenWfwGhy6w1Fd8CHraxxei2qh9q79tOB69vaH+Efh1pYOl5uYed0lhR5GhxjunWHgJkdjnePLpL8g8o42KPnPn8a7sLQAIPM4fRSTFG7hCYGeXGe4dYxBec2hjjM8oBZ8e8Xx6jbD7ASD+hkYG+qiW+8BGR/UQ2BK9tCTwOGTDPcPMDy76Pf05hHq60E/HjnFqSVd2M0AhQLIYeH9cw3hnkIBHCXIxBW/p3dPkT/M8ILa8fAKx+MLBNwMUMiYf7I+TBgYpYVhWnTnOH2YQwzPL5MnhcMnejFtcP9ST+H+QIaply08peMydoMU0fEJHyVFpC5Mikd68eR1X2H40j4ly3NlW1j6UUF8bhmZ+G/EIr+Qiq4gpRaRFnG0iPjsMtLzK0iSpWO/4VhOQA97ifrGOmJxBbl8mnwUc5GviCdU5L9nEFVmEUso8r3ICbNte3+guJISiSRSqTSKRVKSTNG1No9sJotIJApVUWUunc4gHk/8H+g4DsFSWFpakpMWFxdlnEwmkclkoCgKbZiQuWw2K+cHAvtJcbnWajX6fxlyuZyEFQoFxGIxqKq6DRP5QIWDkgKYz+clRIAFtK9OxPV6/e+FEVTyTqU7geVyWeZKpRL1tohGowFxyw+C7VG404uyhKL+0DTtnzIDFe4Mdk/qdExsafqedgTBxPgDxExk2xIaiz0AAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image47\",\n \"title\": \"image47\",\n \"src\": \"/static/90235aadeb4b6aaca7825a8b91ad266a/a07a7/image47.png\",\n \"srcSet\": [\"/static/90235aadeb4b6aaca7825a8b91ad266a/a2ead/image47.png 259w\", \"/static/90235aadeb4b6aaca7825a8b91ad266a/6b9fd/image47.png 518w\", \"/static/90235aadeb4b6aaca7825a8b91ad266a/a07a7/image47.png 534w\"],\n \"sizes\": \"(max-width: 534px) 100vw, 534px\",\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(\"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\": \"719px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/00cdf102bdd871862309b280e962ac41/073e9/image48.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\": \"107.33590733590734%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACqklEQVQ4y4VUa1fiMBDt//9D60ddVveoCFQQBdpC36RJ09ImbQGBvUlE2eM5u/eEMJ10HncyUysMEs6LPC8Y4zkvNpu6qsSmwq6EqhYQ6lrqRwiiaTohGrVkY608r//4cHt72+/3syxjjGaUZgpUI9NKpp61qriAlcTR1dWP+/t7SllZIvJfqKoKe1mW6qFUwiWsjJDr6+tn+3k6nb6+vnqu6/sBBxMNYyaEUBkLIaU0gtFYOA4CX9GSsm3bKIpse1xtKghJksZxRBkzBjzP03QNodJQkZENeJ5Op+PxiB0uxuOXrmk5zxEpieM1IaAaRzHc+b4fx3GaptAQQlTaT/0+cnZdbz6feZ6HMF3XIQvsTdPIRkGoOjfQmOSVXkoLxAZPA9u2Z7PZZDwJggApdRrG3mCr8fF3hgVPSGP+NvNXvud4KBiI7fd7nO00IGNvz+guYKVpcnNz4zgO+CAsiIVhGMUKQRhCs1ouIZubQ5GQ7Zcx2mo4GIxGtuu4IOyvFGBjj0YPD4/QOAsH7gxJw/bLGN7QQMjuZHA8mrIrFsvVpw7JHw4HREYLgMWHMQqGPjpbHRXF93e85wfhyg/wAL9QHrRHWKJP8Yohb6H9UDBzhm5YrtdRTKKE+GFSVqLd7rb7Q76RRVXjBdjgLlTZTWRC1piK4XCIqhCG2coxAIxSznJ4SQg4MRQwY3y33eorv+AM497P3q9e7/fd3fB5ItsOs1YLWcsmJrkbpI67XLirLC/O8S6uSqoml2Z6MsrQjQmha0JTNCVD+ILxkubIut5+s1YFC6NIj0ECN+bctAfy3OlOMnv3DWqqMImL+QLxMT26N7ef7fS5LtHqhR8i87FtTyeT2nx5qo2KqLr4X8vkYsUpfZkupm8uK2peCl6I/H8r49WaFvjw/AF9CJSX68LVqAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image48\",\n \"title\": \"image48\",\n \"src\": \"/static/00cdf102bdd871862309b280e962ac41/073e9/image48.png\",\n \"srcSet\": [\"/static/00cdf102bdd871862309b280e962ac41/a2ead/image48.png 259w\", \"/static/00cdf102bdd871862309b280e962ac41/6b9fd/image48.png 518w\", \"/static/00cdf102bdd871862309b280e962ac41/073e9/image48.png 719w\"],\n \"sizes\": \"(max-width: 719px) 100vw, 719px\",\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, \"For more information on the design comparison platform, see JMP's help\\ndocumentation or contact the Test Design and Analyses Division of A-2/9.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/3-7-Comparing-Measures-of-Merit.md"},"frontmatter":{"metaTitle":"Comparing Measures of Merit","metaDescription":"Comparing Measures of Merit"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"f6289bcd-a5c2-5568-affb-54e607ea7ab3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS/page-data.json new file mode 100644 index 00000000..67834663 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"66cf8415-3c18-5802-8c48-f765cc54e603","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS","slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS"},"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\": \"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS\",\n \"metaTitle\": \"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS\",\n \"metaDescription\": \"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS\"\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, \"For many \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" tests the response data has variability; i.e., if two\\ntest runs are conducted while holding the factor levels constant, we\\nwill likely measure two different response values. There are three basic\\nprinciples of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" that help us compensate for, quantify, and control\\nvariability in our response data: randomization, replication, and\\nblocking.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS.md"},"frontmatter":{"metaTitle":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS","metaDescription":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"66cf8415-3c18-5802-8c48-f765cc54e603"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/3-9-Randomization/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/3-9-Randomization/page-data.json new file mode 100644 index 00000000..94c4e920 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/3-9-Randomization/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/3-9-Randomization","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"87e5758d-702f-57e9-a090-8da7b2292d81","title":"Randomization","slug":"/analyst_test_design_guide/3-9-Randomization"},"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\": \"Randomization\",\n \"metaTitle\": \"Randomization\",\n \"metaDescription\": \"Randomization\"\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, \"Randomization is a principle of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" used to average out the effects of\\nunknown and uncontrollable nuisance factors. Randomization refers to\\nboth the random allocation of test material to a test run, and to the\\norder in which the test runs are executed. If possible, the order of\\ntest runs should be randomized to avoid biasing the factor effect\\nestimates with the effects of the unknown nuisance variables.\"), mdx(\"p\", null, \"For example, suppose we have one two-level factor of interest. Our test\\nis conducted over a morning and afternoon with 4 test runs in the\\nmorning and 4 test runs in the afternoon. Suppose the temperature in the\\nmorning is 15 degrees cooler than in the afternoon, and the response\\nvalue increases as the temperature increases. The test is not randomized\\nand factor level 1 is run in the morning and factor level 2 is run in\\nthe afternoon. The test data show that the response is higher for factor\\nlevel 2 than for factor level 1. Unfortunately the test team cannot be\\ncertain whether the increase in the response was due to changing from\\nfactor level 1 to factor level 2, or due to the increase in the ambient\\ntemperature from the morning to the afternoon.\"), mdx(\"p\", null, \"If the test was randomized, the runs in the morning would involve both\\nfactor level 1 and level 2 (and likewise for the afternoon.) Ideally the\\neffect of the ambient temperature will average out over each level of\\nthe factor, and we remove its influence on the estimate of the factor\\neffect.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/3-9-Randomization.md"},"frontmatter":{"metaTitle":"Randomization","metaDescription":"Randomization"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"87e5758d-702f-57e9-a090-8da7b2292d81"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/4-1-Replication/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/4-1-Replication/page-data.json new file mode 100644 index 00000000..a216760e --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/4-1-Replication/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/4-1-Replication","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ae8bfa57-a000-580a-8a6f-75af9be0e31a","title":"Replication","slug":"/analyst_test_design_guide/4-1-Replication"},"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\": \"Replication\",\n \"metaTitle\": \"Replication\",\n \"metaDescription\": \"Replication\"\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, \"Replication is an independent, repeated run of a factor level\\ncombination (as opposed to measuring the result of a single test run\\ntwice---this is a repeated measure.) Replicating factor level\\ncombinations is the best method for obtaining an estimate of run-to-run\\nvariability, which is often called experimental noise. An important\\nbenefit of factorial experimentation is that there is hidden replication\\nin the test design. This means that even if a factorial design for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"k\"), \"\\nfactors is unreplicated, if one factor is determined to be\\ninsignificant, the resulting design is a replicated design for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"k-1\"), \"\\nfactors.\"), mdx(\"p\", null, \"Since statistical analysis of test data using \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"ANOVA\")), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn37\"\n }, \"37\"), \" or linear regression involves\\nevaluating a ratio of an estimated factor effect to the experimental\\nnoise, replication is important to enabling accurate analysis. While\\nthere are methods to estimate experimental noise without replication,\\nthese methods produce estimates that are generally inferior to those\\nproduced by repeating factor level combinations.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/4-1-Replication.md"},"frontmatter":{"metaTitle":"Replication","metaDescription":"Replication"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"ae8bfa57-a000-580a-8a6f-75af9be0e31a"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/4-2-Blocking/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/4-2-Blocking/page-data.json new file mode 100644 index 00000000..4837460c --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/4-2-Blocking/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/4-2-Blocking","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"4a5de6d1-3465-5775-b3d3-430069a2297f","title":"Blocking","slug":"/analyst_test_design_guide/4-2-Blocking"},"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\": \"Blocking\",\n \"metaTitle\": \"Blocking\",\n \"metaDescription\": \"Blocking\"\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, \"Blocking is one of the fundamental principles of Design of Experiments\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \") that allows us to account for the variability in our response data\\ncaused by controllable nuisance factors---factors that are not of\\ninterest but can be controlled. In the absence of blocking, variability\\ncaused by nuisance variables is attributed to experimental noise and may\\nalso bias factor effect estimates; this inflates the experimental noise\\nestimate and makes it more difficult to determine if factors of interest\\nhave an effect on the response variable.\"), mdx(\"p\", null, \"During operational test, there is almost always a nuisance factor that\\nis a source of variability that could and should be controlled. Some\\ntypical operational test nuisance factors are the day of the test,\\nshifts of operators, pilots, tail numbers, terminal/position numbers,\\nand ranges. These factors can impact the response variable\\nsignificantly, sometimes even more than the factors of interest.\"), mdx(\"p\", null, \"Blocking is simply incorporating a nuisance factor into the test design\\nas a blocking factor. Just as with the factors of interest, the goal is\\nto make the blocking factor orthogonal to the other factors. If the\\nlevels of a blocking factor are time based, such as the day of the test\\nor a shift of operators, then the blocking factor creates a restriction\\non randomization. This is because the blocking factor level is held\\nconstant for some period of time.\"), mdx(\"p\", null, \"One way to add a blocking factor in JMP is through the Custom Design\\nMenu. Suppose we have a test with three 2-level categorical factors and\\none 3-level categorical factor. If an 18 run test was planned over three\\ndays, it may improve the analysis to block on the day of the test. Doing\\nso would account for the variability from nuisance factors that vary\\nday-to-day, such as precipitation, humidity, sunlight, and temperature.\\nFigure 28 shows the JMP Custom Design Menu. To add blocking factor for\\nTest Day, under the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Factors\"), \" box, select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add Factors\"), \" , then\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Blocking\"), \" , then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Other.\"), \" By selecting 6 runs per block, we can\\ndivide the 18 test runs among the three days such that all of the levels\\nof the factors of interest occur equally often on each day. Thus any\\ndifferences between each test day will average out across the levels of\\nthe factors of interest. Now the estimates of the factors of interest\\nwill be independent of any effect on the response caused by the test day\\nconditions. Also, the error estimate will be reduced, as the variability\\nassociated with each test day would have been included in the error\\nestimate if the test was unblocked.\"), mdx(\"p\", null, \"Figure 28. Adding Blocking Factors in JMP\"), 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\": \"783px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/dc9b37d8f0f865ce9b5f58a780a2d621/e51a6/image49.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\": \"74.5173745173745%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAACHVAAAh1QEEnLSdAAAC4ElEQVQ4y2NgwA6YgFgAiJWAWBKK5aB8GSCWBWIRBhIByFBxIFaDGqYAxFpQtioQCzOQCcShhslADZOGupiFVIO4oN4CeV0CyftyUMO5STGMEaoB5F0VqEEgQxShLgYZKkqOd5mhBkkSrcM6ZQqDsnkAg7y+M4OglCqSA+ERA3KJEJoEmOYWlGSwiqxnEFXQY1C3i2KwSpoEkXUt2wS34P///wzypn4MShYhIC4PNEZBNJOcaSBYjVlkG4O+TyGDX9spuL6ZQH1mkS0MDDFr/zPkz7nENPXmf6aFT/8z5c29yiRhFskQO/MJWKGSvgM7j5CkpISSHi/IMhAwDW8C09mzrzCu+f+fce6T/4xVGz4w2sZ3grw8TZydW1CUnY1VkYWZSZ5XTJEfGAyCQNsErZKnCnPxi4mys7LIAeVkgAYLWiZOEjGNaOKzTZ8tIKtpJSIkLKokJCwuLy6nKWadMpWPwTqxnze0cYuObVJvsENyT2hw8y5NNY9iZrOYLlG3uFq2yM5Dms7ZM33ccmf7BLXs17QPL2czi+kWtgirYfWs3ydpGNVlpx9c4+Jcvll18kWgDzQCGngW7ry5Z/bW6/9nbr76f9aWq1tBXnNOnywOoudtv7537vYb/6dvuvJ/xuaru0FiHjkzREH0rK3Xp03dePX/pPVXfk5ef/l0z/pbbAyG0d08T5+/2/nwyZv/9x+9/P/oyetNIMX+edPABj5++nbX42fvgHKvQHI7QGKR5XPFQPTTFx/m3n/8Gix39+GLy//+/+dgMIrp5br94PXha3de/L96+/n/G/de7gEp9s2dKgGigfwjN+69gsjdfXEIJBZeOgds2cNnH+YC5UF6/l+/8/w6UIyRwSSqU+za3efd1+8+33/l9tP9F288bmOQS+T0yposzCATx33p5uOe6/deHLhy68kBoFwXA08IV0jxLCEG9WSRw2fvTDh16f7D05fv3zly9vaO6KqFCgDykj7YgzhiwwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image49\",\n \"title\": \"image49\",\n \"src\": \"/static/dc9b37d8f0f865ce9b5f58a780a2d621/e51a6/image49.png\",\n \"srcSet\": [\"/static/dc9b37d8f0f865ce9b5f58a780a2d621/a2ead/image49.png 259w\", \"/static/dc9b37d8f0f865ce9b5f58a780a2d621/6b9fd/image49.png 518w\", \"/static/dc9b37d8f0f865ce9b5f58a780a2d621/e51a6/image49.png 783w\"],\n \"sizes\": \"(max-width: 783px) 100vw, 783px\",\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, \"Blocking can also be employed as a strategy to hedge against the\\nnegative impact on analysis resulting from lost test data. The levels of\\nthe factors of interest should be balanced across the levels of the\\nblocking factors; the consequence of this is that all blocks typically\\ncontain data for every factor level. In the above example with a three\\nday test, if one test day was lost due to weather or an equipment\\nmalfunction, the test runs from the other test days will still be\\nbalanced. Also, the factors of interest will likely be less correlated\\nthan they would be in a scenario where a random set of 6 test runs were\\nlost.\"), mdx(\"p\", null, \"JMP's help files have useful information on building blocking factors\\ninto a test design. The rule of thumb is: \\\"Block what you know,\\nrandomize the rest!\\\"\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/4-2-Blocking.md"},"frontmatter":{"metaTitle":"Blocking","metaDescription":"Blocking"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"4a5de6d1-3465-5775-b3d3-430069a2297f"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS/page-data.json new file mode 100644 index 00000000..23db47ec --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"47367be9-e1ff-5056-8797-97e1b83ea9ee","title":"TYPICAL SITUATIONS","slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS"},"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\": \"TYPICAL SITUATIONS\",\n \"metaTitle\": \"TYPICAL SITUATIONS\",\n \"metaDescription\": \"TYPICAL SITUATIONS\"\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 next section covers some typical situations that may be encountered\\nin \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" and some suggested remedies.\"), mdx(\"h1\", null, \"How do I Select a Design?\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Table of commonly encountered design scenarios and possible design matches.\"), mdx(\"th\", null, \"Full Factorial\"), mdx(\"th\", null, \"2\", mdx(\"sup\", null, \"k\"), \"Fractional Factorial\"), mdx(\"th\", null, \"Orthogonal Arrays\"), mdx(\"th\", null, \"Covering Array/Combinatorial Design\"), mdx(\"th\", null, \"Computer Generated Design (Optimal)\"), mdx(\"th\", null, \"Split/Strip Plot Designs\"), mdx(\"th\", null, \"Space Filling Designs\"), mdx(\"th\", null, \"Demonstration\"), mdx(\"th\", null, \"Cases\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Factor Considerations\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"All continuous factors\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\", mdx(\"sup\", null, \"31\")), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"All 2-level factors (mixed continuous and/or categorical)\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Mixed level factors (mixed continuous and/or categorical)\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X [38](#fn38)\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Disallowed combinations\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Modeling Considerations\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Quadratic terms\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X [39](#fn39)\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Two-factor interaction terms\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X [40](#fn40)\"), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Three-factor or higher interaction terms\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X [41](#fn41)\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Response Variable Considerations\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Random Variation\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Deterministic\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"X\", mdx(\"sup\", null, \"31\")), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\")))), mdx(\"p\", null, \"If all of the factors in your test have only 2-levels or are all\\ncontinuous, you can choose almost any design type. It is most desirable\\nto select a design with a run size that is a power of 2 (8, 16, 32,\\netc.) If resource constraints prevent this, choose a D-Optimal design.\"), mdx(\"p\", null, \"When a test involves categorical factors with more than 2 levels, it is\\nmost common to create a full factorial or D-Optimal design. Create\\nseveral design options and compare them using the test design measures\\nof merit presented in this guide.\"), mdx(\"p\", null, \"When a test involves a deterministic response, use a combinatorial\\ndesign to find factor level combinations that cause problems in the\\nsystem. If you plan to characterize the system, choose a space filling\\ndesign.\"), mdx(\"h1\", null, \"I Have Factors that Are Hard to Change\"), mdx(\"p\", null, \"It is the rare operational test scenario where the runs in the test\\nevent matrix can be executed in an entirely randomized order. It is\\ncommon that a group of runs involving a particular factor level must be\\nexecuted consecutively because of constraints imposed by the range, test\\nasset availability, or feasible tactics. It is these cases when the\\ndesign should be set up, run and analyzed using a split plot\\nconfiguration.\"), mdx(\"p\", null, \"Split Plot designs can be created from an existing design type\\n(typically a computer generated design) by identifying the\\nhard\\u2011to\\u2011change factors and easy\\u2011to\\u2011change factors. The hard\\u2011to\\u2011change\\nfactors are those that cannot be arbitrarily changed from run to run.\\nThese factors are arranged into groups of runs called Whole Plots. Whole\\nPlots contain equally sized (usually) sets of runs and the levels of the\\neasy\\u2011to\\u2011change factors are randomized. Figure 29 shows a Split Plot\\nconfiguration with one hard\\u2011to\\u2011change and two easy\\u2011to\\u2011change factors.\"), mdx(\"p\", null, \"Figure 29. Split Plot with One Hard to Change Factor\"), 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\": \"787px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/a16a713032e3ac076fcc215599ea9ec2/e619b/image50.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\": \"75.2895752895753%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAACHVAAAh1QEEnLSdAAADiUlEQVQ4y2NgwA/YgVgciKWBWAyIZYFYAog5GcgEzEAsCDVIC4qlGSgAbFAXKkENEoK6miID+aGGyUMNZMarQ9+3kEFUTpNBSsOCQUbLmkFcUY9BWsee4f///wzMbJwgzQJALMXAyMjFyMjEzsjEAjZQztCTQULZgEFS1YRBSt2cQVrTikHDKZGBQdstnUFQTIZBSs2MQVLNlEFMXgtosA2DY+5iBgl1S5grwV7l4BVkEJBQYnDKW8qgYhUCViuupA802BCsH2Qog1Fonai2W5qwQ1yTiFNCq4hFaIWInm+RkFXSJG7j8GYBfa9sEVPfLCl9lzhZ0+BKIYOgan7rpMm8hiF1/Eb+hSIOMfWiDnGNoqbBFcKGIfV8DEZBFUriqqaaQBcogCOAiVdZyyle0SZluoBlTLs4j5SWCjT8RPlk9ZUNfQuEbFKmSZiF1orxSKirQeWkgeqUjANLRRiMovukorNqRCqn7phTNXP/+rJJWzIlXUp5nNKniIk4VfKVdC83rpy2a13FtD2rc5oXAsPAlcUxdbICs0EmV0HHUuPK6btXVc/ctyK/fakFg1wYJ4O0a4XUrccfhC7efvnt3PXn/y/dfrWQgYGJLbJioSTQZo6bD9+7Xbj54v/Z68/+X7331gcUWaGl85SBciw3H75zv3Dr5f9zN57/v3bvjT9QjAlkoPSjN3+EHj//8PL+kzf/n778OAMYVZzRVQuBOUKc6+W7784Pn777f//xm/8v3n73AMVSeNl8ULpkf/n2q8ujZ+//P3jy9v/LN1+8QZYwmMX2Kpn5pMuVt0xxb5u63D2/utPCMKJd2j55grB+ZI9UeGatWl3PbJ/GCQs9/BNKtDWD24SBcjJawW0SMVlV6o19c73r+xZ4+ieWqmsHNUswaAc3SzVPXCTUt+LUrv5VZ660zN3rBbSJ1Tt/tgSDXjpv65wd6hNWnT7Zs/z0+Y75ex2AcowOqZPlzWN7QFmSpX/lqZW9K0/f7V9xIhbsZUnncklguPDfe/L+y60Hr/8DvRgLCqfkxmVSDAyqXC/e/tC/8+jdf5Dcw+ef/EByPnkzFdT8GwVA7LuP3z0EyT1+8akMxGdQ9K5VmLD0gPy1O8+fX7715P+ZKw+TGRgkeRLrlwIjxYX31sPXencfvX5/+8HLnzfuvfAEucI7d4a8TnCLyLSVhzluPXh17sbd50ALXxWAXAwAswhSRyi6SnQAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image50\",\n \"title\": \"image50\",\n \"src\": \"/static/a16a713032e3ac076fcc215599ea9ec2/e619b/image50.png\",\n \"srcSet\": [\"/static/a16a713032e3ac076fcc215599ea9ec2/a2ead/image50.png 259w\", \"/static/a16a713032e3ac076fcc215599ea9ec2/6b9fd/image50.png 518w\", \"/static/a16a713032e3ac076fcc215599ea9ec2/e619b/image50.png 787w\"],\n \"sizes\": \"(max-width: 787px) 100vw, 787px\",\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, \"If there are two hard\\u2011to\\u2011change factors (one will be specified as\\nvery\\u2011hard\\u2011to\\u2011change and the other hard\\u2011to\\u2011change) the\\nvery\\u2011hard\\u2011to\\u2011change factor will determine the whole plots and the\\nhard\\u2011to\\u2011change factor will be used to create sub plots within the whole\\nplots. The easy\\u2011to\\u2011change factors will be randomized within the subplots\\nas shown in figure 30.\"), mdx(\"p\", null, \"Figure 30. Split Plot with a Very Hard and Hard to Change Factor\"), 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\": \"715px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/cc63166e2a57e41214ea94f51e1e8e88/d0c0e/image51.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\": \"106.56370656370657%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACcElEQVQ4y41TaZeaMBTl//+ljtrOh7YfrNu4IEEQsrAIhFVFjzoXMm6dnrbXnHgJeY+b+140yxGe5zPurV3GhB8naZJmsUxBZJrHMmtIVnysZHm12+dllRVlXm61xWLZewE6v/r9APAbeIDwAsWEFwYB/sDxPpVSDUCzXfry8mUyeVML+RVFUZRlWbTI8jvSK7Is0yj3vvZ6s9kcMIClYdtrvIuiaLPZJEmCTdsWVVUh3fYKPGphJDmnuxZ1faCUjkeTsigZo9bKcl0XKaAIykGCdkZeZEdeLZJQmF8ul/P5jBlKDYMc6qOUyX6/F4Jjt23bSMo5B0G8SQjcCMNQc7k3Ggx0XScmgXLTJDgkwnZXKF7X9SPBDK6FsRwPh9PplBCiL3QhhArGxv01cn+FirxBS4tKcG7oS8dxVmSFcwZ+cDwe1dZDC5CbT4+5NNuh3W7HIMQ0TRxpjZ+9buFYlrVaraAItqFIsB0+weR7cBA1snFa7GCMwRUoRz9MRuNBf4AVKPI9Hx9U5XkKjppCpqfTWRmuAO46LuPi0gIrEH86nVCzOI7BP4JhWJHnl0+Afui4PaqMqC0qpxxpgtH66OD21eX2cRBiEMte/yYH4nH4m+eaw8TPH9+HwyHu1q37sEk18KPJ6thPbrtM9LodtPe311d9scAtapyGZs7hFhoLhsHEx5h7cJIWHJ3HOKUM1uEeoXXRJ1XZ3AN42/AHh5+CYRhvS5RIqQ4DafUn/DnY3yRv44lhmLi+cRRnrR+qNf85cCWTyXi0mM/RAqgZ5mPbkf8zNN32RzMyXa5dL6G+dL0Y5C+DeonFI4sGNgvfAZy9k49ApaxuAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image51\",\n \"title\": \"image51\",\n \"src\": \"/static/cc63166e2a57e41214ea94f51e1e8e88/d0c0e/image51.png\",\n \"srcSet\": [\"/static/cc63166e2a57e41214ea94f51e1e8e88/a2ead/image51.png 259w\", \"/static/cc63166e2a57e41214ea94f51e1e8e88/6b9fd/image51.png 518w\", \"/static/cc63166e2a57e41214ea94f51e1e8e88/d0c0e/image51.png 715w\"],\n \"sizes\": \"(max-width: 715px) 100vw, 715px\",\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 consequence of designing the test in this manner is that we can no\\nlonger use a common estimate of error to evaluate both the\\nhard\\u2011to\\u2011change and easy\\u2011to\\u2011change factors. There is more variability in\\nthe average response between the levels of the hard\\u2011to\\u2011change factors\\nthan between the easy\\u2011to\\u2011change factor levels. Hence the power for the\\nhard\\u2011to\\u2011change factors will be lower than for the easy\\u2011to\\u2011change\\nfactors. To improve the power of the hard\\u2011to\\u2011change factors, the test\\nshould include multiple whole plots for each hard\\u2011to\\u2011change factor\\nlevel. The resulting test will be larger than if a completely randomized\\ndesign was used.\"), mdx(\"p\", null, \"To construct a split plot design in JMP's custom designer, open the\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Designer\"), \" tab, and enter the desired factors as usual. Under\\nthe \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Changes\"), \" column for the factors, change \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Easy\"), \" to \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Hard\"), \" .\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Very Hard\"), \" is used if there are two hard-to-change factors and there\\nwill be subplots within the whole plots; the subplot factor will be\\nlabeled \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Hard\"), \" . Specify the desired model.\"), mdx(\"p\", null, \"Specify the number of runs in each whole plot. Under \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Design\\nGeneration\"), \" , enter the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Number of Whole Plots\"), \" , which will\\ndetermine the number of times the levels of the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Hard\"), \" factor (if\\nthere is only one hard-to-change factor) or \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Very Hard\"), \" factor is\\nreplicated. In figure 31 the very hard-to-change factor will have each\\nfactor level replicated 2 times; 4 whole plots divided by 2 levels\\nequals 2 whole plots for each level.\"), mdx(\"p\", null, \"Specify the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Number of Subplots\"), \" (if necessary because there are 2\\nhard-to-change factors). Each whole plot will have 2 subplots; 8\\nsubplots divided by 4 whole plots equals 2 subplots per whole plot.\\nEnsure that analysis is done in the table created by JMP, as several\\nimportant factor properties have been changed to enable a proper\\nanalysis.\"), mdx(\"p\", null, \"Figure 31. Creating a Split Plot Design in JMP\"), 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/096255ffb480f7df5de5e36fdb5d4c6b/5148a/image52.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\": \"25.482625482625483%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAFCAYAAABFA8wzAAAACXBIWXMAABcRAAAXEQHKJvM/AAAAnUlEQVQY002P2wrCMBBEV1H0wRvV1qIxaq1NRRAp6v9/mrNyhD4csjPZ7E7MzILYir2I4iym4oC+iAwv0l+JZa8v8L42Cjee1GsxEblI4oY2vJohI7yMEDlzbN673IgVtSfoxFWMxUAU4iOOYkifB3iT3of+HpQYOzFj653NiR5P9cCrOAvuG86X8YUIJ7Fga0L/B3jdogO6RDfo7gt8vgphhqAn3QAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image52\",\n \"title\": \"image52\",\n \"src\": \"/static/096255ffb480f7df5de5e36fdb5d4c6b/e3189/image52.png\",\n \"srcSet\": [\"/static/096255ffb480f7df5de5e36fdb5d4c6b/a2ead/image52.png 259w\", \"/static/096255ffb480f7df5de5e36fdb5d4c6b/6b9fd/image52.png 518w\", \"/static/096255ffb480f7df5de5e36fdb5d4c6b/e3189/image52.png 1035w\", \"/static/096255ffb480f7df5de5e36fdb5d4c6b/5148a/image52.png 1228w\"],\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, \"For more specific information on the construction and analysis of Split\\nPlot designs, check the JMP help files or contact the Test Design and\\nAnalyses Division of A-2/9.\"), mdx(\"h1\", null, \"Can I Combine Developmental Test and Operational Test Data?\"), mdx(\"p\", null, \"Developmental and Operational Test data can be combined if the\\ndevelopmental test is determined to be operationally representative.\\nDuring test planning, if the analyst thinks that combining developmental\\ntest (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \") data with operational test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \") data may be a possibility,\\nthere are some important considerations to discuss with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" team.\"), mdx(\"p\", null, \"To combine any data to be used for characterization, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" events\\nshould have factors that correspond to the factors for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" event. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" test articles must also be the \\\"same\\\" as the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" test articles. Any\\nvariability caused by small changes to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" may be addressed with an\\nadditional blocking variable. Another very important requirement is that\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" events must be \\\"operational\\\" in nature. Lab tests, chamber tests\\nor table top tests are not usually operational and so cannot be\\nconsidered for combined \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" data.\"), mdx(\"p\", null, \"During test planning and test design, discussion of the possibility of\\ncombining the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" data is essential to ensure that the future\\ncombination will be feasible. Ultimately, it may not be possible to\\ncombine the data because of the evolution of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", but proper\\nplanning will maintain the possibility. The same considerations can be\\napplied when planning the combination of data from Initial and Follow-on\\nTest & Evaluations.\"), mdx(\"p\", null, \"There are several advantages to combining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" data. First,\\ncombining data makes the \\\"Test-Analyze-Test\\\" strategy viable. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" test\\ndata can be used to determine the significant main effects so that later\\nin \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" the test event matrix can be more focused on the relevant factors\\nand their interactions. Second, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" test events are usually planned and\\nexecuted for the \\\"minimum\\\" data needed, so \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" data is an attractive way\\nto increase the sample size of the data for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" analysis. To obtain more\\ninformation on combining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" data, contact the Test Design and\\nAnalyses Division of A-2/9.\"), mdx(\"h1\", null, \"I Have Disallowed Combinations\"), mdx(\"p\", null, \"One of the reasons optimal designs have skyrocketed in popularity at\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is the ability to deal with disallowed combinations. A disallowed\\ncombination occurs when one level of a factor cannot occur\\nsimultaneously with a level of another factor. The JMP \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Design\"), \"\\nplatform allows you to specify disallowed combinations using a script or\\nfilter.\"), mdx(\"p\", null, \"Keep in mind that if the operation/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" in question has a large number\\nof disallowed combinations, you may need to make some modifications to\\nthe test design. One solution could be to add another operation to the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" in order to separate the factor list into two groups for separate\\ntest events. Perhaps the factor prioritization and management may need\\nto be reevaluated to determine if a factor can be removed from the test.\\nThe factors in question may not be independent enough to be separate\\nfactors, and combining the factors into a super factor could be the best\\napproach. For more information on these or other techniques to avoid or\\novercome disallowed combinations contact the Test Design and Analyses\\nDivision of A-2/9.\"), mdx(\"h1\", null, \"My Power Is Too Low\"), mdx(\"p\", null, \"You have created the test event matrix, created the power curves, and\\ndetermined that the power for either your main effects or two-factor\\ninteractions is not sufficient. A straight-forward solution is to\\nincrease the test size, but this is often not feasible due to resource\\nconstraints. Another common solution is to eliminate factors. This\\nsolution results in a less-thorough exploration of the battlespace and\\ncould result in undetected system problems. Fortunately, there are some\\nother options to consider:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Keep the same test plan and explain why this added risk is\\nacceptable for the test program.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Split a factor into two factors: As an example, splitting a 4 level\\nfactor into two 2 level factors will increase the estimation power\\nof a design without any additional runs. This can be an option for\\nmany factors that are amalgamations of multiple factors.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Reexamine the likelihood and magnitude of impact for the two-factor\\ninteractions; if some are not as important or less likely to exist,\\ninclude the important ones and remove the other interactions from\\nthe power analysis.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Report the power on the main effects only and explain why the added\\nrisk of not detecting two-factor interactions is acceptable for the\\ntest program.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Make sure the categorical factors really are categorical; if factors\\ncan be changed to continuous, the levels can be reduced to two (but\\nadd some center points). Fewer levels will increase the power for\\nthose factors.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ask someone outside the program for their thoughts. Creating test\\ndesigns only within the test team can lead to \\\"group think,\\\" and\\nexternal advice may provide another point of view and a solution.\"))), mdx(\"p\", null, \"Whatever the option chosen, it is important to document the rationale in\\nthe Test and Evaluation Master Plan to keep interested parties informed.\\nIn the end, if the power is too low and there are not any realistic\\noptions to increase the power, it is better to report the low power and\\nthe associated risk, than to eliminate factors which may be crucial to\\nthe warfighter's situational awareness. For guidance on creating power\\ncurves or power calculations in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", see the November 2014 guide,\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Power Analysis Tutorial for Experimental Design Software.\")), mdx(\"h1\", null, \"I Have Factor Levels that Depend on Other Factor Levels\"), mdx(\"p\", null, \"The traditional nested design occurs when the levels of one factor are\\nsimilar but not identical for the levels of another factor. These types\\nof designs are also called hierarchical designs (Montgomery, 2013). In\\noperational test they might resemble figure 32.\"), mdx(\"p\", null, \"Figure 32. Example of a Traditional Nested Design in Operational 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\": \"988px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/9fd1e3689a7b8e9ca89ba3e5685488c2/e4900/image53.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\": \"25.482625482625483%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAFCAYAAABFA8wzAAAACXBIWXMAACHVAAAh1QEEnLSdAAAAmUlEQVQY02XQawsBYRCG4SnlbJEcWyxCjpuUwidy+v+/yD16yhtPXbU77+zO7JqZrTHEDAO0ZC5TtNHAQn0xMuhgiTESFEwNXYzQRISq7r2xj4qak2Cop4gd9nr2k8i+KWlymKzqedR07clpwxUOWsAX+XvBb3yzOnoaXg7qk+DLYv0aO2KDVLaSqn7GDXe8cNH5CQ88dX51bx0jCp+5Sna4AAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image53\",\n \"title\": \"image53\",\n \"src\": \"/static/9fd1e3689a7b8e9ca89ba3e5685488c2/e4900/image53.png\",\n \"srcSet\": [\"/static/9fd1e3689a7b8e9ca89ba3e5685488c2/a2ead/image53.png 259w\", \"/static/9fd1e3689a7b8e9ca89ba3e5685488c2/6b9fd/image53.png 518w\", \"/static/9fd1e3689a7b8e9ca89ba3e5685488c2/e4900/image53.png 988w\"],\n \"sizes\": \"(max-width: 988px) 100vw, 988px\",\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, \"Each aircraft has four power ports which may be used during test, but\\nthe power port \\\"A\\\" on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Alternating Current\"\n }, \"AC\"), \"-130 is different than the power ports \\\"A\\\"\\non the A-10 and the F-15. The response variable can still be analyzed\\nunder both factors but the analysis model must be set up differently\\nthan a traditional ANOVA model; e.g., do not include an interaction term\\nbetween the parent and nested factor. In the design construction in JMP\\nchange the attribute of the nested factor to \\\"nested\\\". Include in the\\ntest design documentation that \\\"Power Port\\\" is nested within \\\"Aircraft\\\".\"), mdx(\"p\", null, \"Within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", there is a type of test design called a sub-design. As an\\nexample, a test with a sub-design might occur when examining terrain.\\nMaritime terrain has sea states, while desert and mountain terrain does\\nnot. See figure 33.\"), mdx(\"p\", null, \"Figure 33. Example of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Sub-Design\"), 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\": \"717px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image54.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\": \"75.2895752895753%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAACMUlEQVQoz3WT+3OaQBDH+f//i3bsdJofOmMmaczDNGkMaEwiwaCAXjhex+MEEQQBIelGGx8zzZdl5+Dus7e7BwxGiGPZTqcjSVIQBP6HJiv5nwtmGYxxs9nsCwKdUNd1d7F1rMmOKKW7jwwhpN3m+iBBeH4WHx8fBsOh53mWaRqGYRPbdZxNAIi3B8PdF/oenZRVVZaVbduiKM7nCZCweCCKLyqeRVEwnXqOoygKpBN+iIHEEEJhOHtbKU3isSItiyKOwiLPTR1rKkrnsecQm0Jdnq5po9EIqCiKGM91iWV1xeGv9tPFnXjKCcetXuO2d3R1d3TdbdzyZ+9v+Mb1PX90Ek78LM/nCWT2LuYFoevfl/Vm6+vhZa3erB02vx9fffnZqNXPv9Uvfpz8ATs4bZ2z/NnhuaygKJpNQWEIjjFNk+M4ttub+tSxzYnnvJtrF9miWuYlWJEtiwwqcoPZGBsxwJuaoWEaVju9Z1XToEloDBeCrMqyzAuovSiWy7woqqrSLMdyaJLMVxuvYJsQRZYl1QDG0A3oJ/QjSdO3Hb2+voI3HeoFs0WaBhuYUg8OdDDCozGCD0aWZeChGZ/A4SJNtjvDCCZGmoU1nRAba1jX9cUi+y/s+vuwoetPPM92+UWWrdf9E4xXtoEtl2KTzON4C1vE4tjWTfs+y6AveZ7DQe7Jn85oEE4DX1E11QA42sKrH4Q+9CVBRrJqKNhc+421BYXlJbb7eNPlDeLE0Rb+C552K79tIqVpAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image54\",\n \"title\": \"image54\",\n \"src\": \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image54.png\",\n \"srcSet\": [\"/static/cb39d329fcfcee19a87388fd0a5e782f/a2ead/image54.png 259w\", \"/static/cb39d329fcfcee19a87388fd0a5e782f/6b9fd/image54.png 518w\", \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image54.png 717w\"],\n \"sizes\": \"(max-width: 717px) 100vw, 717px\",\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, \"There are two primary ways to deal with a scenario such as this one; one\\napproach would require a computer generated design while the second\\nwould allow the choice of any other appropriate design type.\"), mdx(\"p\", null, \"The design could be constructed as an optimal design with specified\\ndisallowed combinations for the Sea State and Terrain factors. The\\noptimal design would then only contain runs where the Mountain/Desert\\nlevels were paired with the Sea State = 0 level. Figure 34 shows how the\\n\\\" \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Define Factor Constraints\"), \" \\\" box in the JMP \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Design\"), \" tool\\ncan be used to specify disallowed combinations using a script. In the\\nresulting design, only the Maritime factor will have a sea state other\\nthan 0.\"), mdx(\"p\", null, \"Figure 34. Computer Generated Design with Disallowed Combinations\"), 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\": \"717px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image55.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\": \"75.2895752895753%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAACMUlEQVQoz3WT+3OaQBDH+f//i3bsdJofOmMmaczDNGkMaEwiwaCAXjhex+MEEQQBIelGGx8zzZdl5+Dus7e7BwxGiGPZTqcjSVIQBP6HJiv5nwtmGYxxs9nsCwKdUNd1d7F1rMmOKKW7jwwhpN3m+iBBeH4WHx8fBsOh53mWaRqGYRPbdZxNAIi3B8PdF/oenZRVVZaVbduiKM7nCZCweCCKLyqeRVEwnXqOoygKpBN+iIHEEEJhOHtbKU3isSItiyKOwiLPTR1rKkrnsecQm0Jdnq5po9EIqCiKGM91iWV1xeGv9tPFnXjKCcetXuO2d3R1d3TdbdzyZ+9v+Mb1PX90Ek78LM/nCWT2LuYFoevfl/Vm6+vhZa3erB02vx9fffnZqNXPv9Uvfpz8ATs4bZ2z/NnhuaygKJpNQWEIjjFNk+M4ttub+tSxzYnnvJtrF9miWuYlWJEtiwwqcoPZGBsxwJuaoWEaVju9Z1XToEloDBeCrMqyzAuovSiWy7woqqrSLMdyaJLMVxuvYJsQRZYl1QDG0A3oJ/QjSdO3Hb2+voI3HeoFs0WaBhuYUg8OdDDCozGCD0aWZeChGZ/A4SJNtjvDCCZGmoU1nRAba1jX9cUi+y/s+vuwoetPPM92+UWWrdf9E4xXtoEtl2KTzON4C1vE4tjWTfs+y6AveZ7DQe7Jn85oEE4DX1E11QA42sKrH4Q+9CVBRrJqKNhc+421BYXlJbb7eNPlDeLE0Rb+C552K79tIqVpAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image55\",\n \"title\": \"image55\",\n \"src\": \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image55.png\",\n \"srcSet\": [\"/static/cb39d329fcfcee19a87388fd0a5e782f/a2ead/image55.png 259w\", \"/static/cb39d329fcfcee19a87388fd0a5e782f/6b9fd/image55.png 518w\", \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image55.png 717w\"],\n \"sizes\": \"(max-width: 717px) 100vw, 717px\",\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, \"Another way to address the scenario would be to create a \\\"super\\\" factor\\nof Terrain and Sea State. The factor would have a level for each of the\\nallowed combinations of Terrain and Sea State (7 total levels.) The\\nsuper factor has seven levels, so the test size will need to increase to\\nobtain the same effect power that the former five level Terrain factor\\nhad. Figure 35 shows the super factor, \\\"Terrain\\\" as described in this\\nexample.\"), mdx(\"p\", null, \"Figure 35. Super Factor to Address a Nested Factor Scenario\"), 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\": \"890px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/4e101b73addfad659838133f69035bf0/7f80b/image56.jpg\",\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.490347490347496%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/jpeg;base64,/9j/2wBDABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVGC8aGi9jQjhCY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2P/wgARCAAJABQDASIAAhEBAxEB/8QAGAAAAwEBAAAAAAAAAAAAAAAAAAIDAQX/xAAVAQEBAAAAAAAAAAAAAAAAAAAAAf/aAAwDAQACEAMQAAAB6zZZEKi//8QAGhAAAgIDAAAAAAAAAAAAAAAAAAECERAiMf/aAAgBAQABBQJWbFSF3H//xAAUEQEAAAAAAAAAAAAAAAAAAAAQ/9oACAEDAQE/AT//xAAUEQEAAAAAAAAAAAAAAAAAAAAQ/9oACAECAQE/AT//xAAZEAACAwEAAAAAAAAAAAAAAAAAQQEQETH/2gAIAQEABj8C5ghEX//EAB0QAAIBBAMAAAAAAAAAAAAAAAABIRARUWGBkbH/2gAIAQEAAT8hZoXIi2UtG3oewxT/2gAMAwEAAgADAAAAEKwv/8QAFREBAQAAAAAAAAAAAAAAAAAAEBH/2gAIAQMBAT8Qh//EABURAQEAAAAAAAAAAAAAAAAAAAEQ/9oACAECAQE/EFn/xAAcEAACAQUBAAAAAAAAAAAAAAABESEAEEFx0fH/2gAIAQEAAT8QSBJk4epmi0BYKJdr23bFje3/2Q==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image56\",\n \"title\": \"image56\",\n \"src\": \"/static/4e101b73addfad659838133f69035bf0/7f80b/image56.jpg\",\n \"srcSet\": [\"/static/4e101b73addfad659838133f69035bf0/8356d/image56.jpg 259w\", \"/static/4e101b73addfad659838133f69035bf0/bc760/image56.jpg 518w\", \"/static/4e101b73addfad659838133f69035bf0/7f80b/image56.jpg 890w\"],\n \"sizes\": \"(max-width: 890px) 100vw, 890px\",\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, \"For more information on nested factors, refer to the JMP help files or\\ncontact the Test Design and Analyses Division of A-2/9.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#how-do-i-select-a-design","title":"How do I Select a Design?"},{"url":"#i-have-factors-that-are-hard-to-change","title":"I Have Factors that Are Hard to Change"},{"url":"#can-i-combine-developmental-test-and-operational-test-data","title":"Can I Combine Developmental Test and Operational Test Data?"},{"url":"#i-have-disallowed-combinations","title":"I Have Disallowed Combinations"},{"url":"#my-power-is-too-low","title":"My Power Is Too Low"},{"url":"#i-have-factor-levels-that-depend-on-other-factor-levels","title":"I Have Factor Levels that Depend on Other Factor Levels"}]},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/4-3-TYPICAL-SITUATIONS.md"},"frontmatter":{"metaTitle":"TYPICAL SITUATIONS","metaDescription":"TYPICAL SITUATIONS"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"47367be9-e1ff-5056-8797-97e1b83ea9ee"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design/page-data.json new file mode 100644 index 00000000..b2810d75 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"a36fc389-5aa8-559b-a2e6-85701de974d3","title":"Best Practices and Pitfalls in Test Design","slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design"},"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\": \"Best Practices and Pitfalls in Test Design\",\n \"metaTitle\": \"Best Practices and Pitfalls in Test Design\",\n \"metaDescription\": \"Best Practices and Pitfalls in Test Design\"\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, \"Best Practices\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"When possible, make factors continuous.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"If you use a continuous factor and you suspect a nonlinear\\nrelationship between the factor and the response, use three levels\\nfor the factor. Most textbooks advocate using two levels and\\nincluding center points in the design, but this assumes a sequential\\ntest-analyze-test approach.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Use continuous MORVs when possible. Continuous MORVs offer several\\nadvantages to binary MORVs. First, for the same size test, power\\nwill be higher using a continuous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \". Second, more information is\\ncontained in continuous data; a continuous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" can be turned into a\\nbinary \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \", but the reverse is not true. If a binary/discrete \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \"\\nis used, consider developing other continuous MORVs for power\\ncalculations.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Your first design option should be a full factorial. Consider other\\noptions only if the full factorial is infeasible or inefficient\\n(i.e., many more runs than required to estimate a main effect and\\ntwo-factor interaction model).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Create two or three test designs that meet your needs and use the\\nmeasures of merit to compare them.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Control the nuisance variability you know about with blocking;\\naverage out the unknown nuisance variability with randomization.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ask for help, advice or sanity checks. Even the most experienced\\nanalyst may not have thought of the best way to do something.\"))), mdx(\"h1\", null, \"Pitfalls:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Be cautious with disallowed combinations. If you have a lot, you may\\nrequire additional operations under a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Don't limit your design because you believe you won't be able to\\ntest it. Things change all the time and the capability may exist by\\nthe time you go to test or may be developed just for your test.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Just because you generate a design in JMP's Custom Designer, doesn't\\nmean it is the optimal design! Run the design generation algorithm\\nseveral times and check multiple measures of merit.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Don't just turn the crank on JMP or the Test Design Suite. It is\\nyour job to understand the output and what methods are used to\\ngenerate the results.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Never change a design point without re-evaluating the design's\\ncapability to estimate the main effects and two-factor interactions.\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#best-practices","title":"Best Practices"},{"url":"#pitfalls","title":"Pitfalls:"}]},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design.md"},"frontmatter":{"metaTitle":"Best Practices and Pitfalls in Test Design","metaDescription":"Best Practices and Pitfalls in Test Design"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"a36fc389-5aa8-559b-a2e6-85701de974d3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/4-5-Appendices/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/4-5-Appendices/page-data.json new file mode 100644 index 00000000..3e4d1f06 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/4-5-Appendices/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/4-5-Appendices","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"0472c615-4c7b-564f-a42a-8c39998f4f5a","title":"Appendices","slug":"/analyst_test_design_guide/4-5-Appendices"},"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\": \"Appendices\",\n \"metaTitle\": \"Appendices\",\n \"metaDescription\": \"Appendices\"\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(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Glossary\"), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Active Effect\"), mdx(\"td\", null, \"A term used to describe a main effect (factor) or interaction that causes a statistically significant difference in the response variable when the factor levels are changed.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Aliasing\"), mdx(\"td\", null, \"A condition where the effect estimate of one factor includes the influence of one or more other effects (main effect or higher-order interactions).\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"ANalysis Of VAriance (ANOVA)\"), mdx(\"td\", null, \"A mathematical process for evaluating the variation in data between groups and within groups in order to determine whether there is a differences between the group means. This procedure can be used to compare multiple systems, or determine if there are differences in the mean response between levels of a factor.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Augmentation\"), mdx(\"td\", null, \"The process of strategically adding new runs to an existing test design after some data has been collected.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Balance\"), mdx(\"td\", null, \"A column in a test design matrix is balanced if every factor level occurs an equal number of times. A test design is balanced if every possible factor level combination occurs an equal number of times.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Blocking\"), mdx(\"td\", null, \"Blocking is one of the fundamental principles of Design of Experiments (DOE) that allows us to account for the variability in our response data caused by nuisance factors\\u2014factors that are not of interest but can be controlled. Blocking factors become part of a test event matrix.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Center Points\"), mdx(\"td\", null, \"A test run where every continuous factor is set to the value halfway between its minimum and maximum factor levels.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Confounding\"), mdx(\"td\", null, \"Synonymous with aliasing: a condition where the effect estimate of one factor includes the influence of one or more other effects (main effect or higher-order interactions).\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Correlation\"), mdx(\"td\", null, \"A statistical measure on a scale from -1 to 1 that indicates how close two variables are to having a linear relationship with each other. Two factors are perfectly correlated when the value of one factor\\u2019s level can be precisely determined by knowing the value of the other factor\\u2019s level.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Coverage\"), mdx(\"td\", null, \"Describes the percentage of possible factor level combinations (after removing the disallowed combinations from the complete combination space) that a combinatorial design includes at a given strength.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Deterministic\"), mdx(\"td\", null, \"A deterministic system or model will always produce the same output from a given starting condition (level settings of the independent variables.)\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Disallowed Combination\"), mdx(\"td\", null, \"A combination of the levels of two or more factors that cannot be feasibly executed together in a test run.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Distribution\"), mdx(\"td\", null, \"A listing or function showing all the possible values of a data set and how often they occur.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Effect\"), mdx(\"td\", null, \"The average change in a response variable produced by changing the level of a factor.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Estimation\"), mdx(\"td\", null, \"An attempt to gain insight about an unknown population parameter based on information obtained from sample data. At AFOTEC we typically estimate means and variances of measures, factor effects, and proportions of failures.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Factor\"), mdx(\"td\", null, \"An independent variable which may affect the performance of a system when its levels are changed\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Factorial\"), mdx(\"td\", null, \"A test plan consisting of two or more factors, each with discrete possible values (or levels). A full factorial is a design whose experimental units (runs) take on all possible combinations of these levels. A design which includes a strategically selected subset of the possible combinations is called a fractional factorial.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Interaction\"), mdx(\"td\", null, \"A situation where the effect of one factor on a response depends on the level of another factor.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Level\"), mdx(\"td\", null, \"A specific setting of a factor during a test or experiment.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Main Effect\"), mdx(\"td\", null, \"The effect of a factor (independent variable) on a measure (dependent variable) averaging across the levels of the other factors.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Optimal Designs\"), mdx(\"td\", null, \"A test design whose levels are combined in a way that optimizes some statistical design quality criterion that is a function of the design matrix.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Orthogonality\"), mdx(\"td\", null, \"A test design is orthogonal if each factor can be evaluated independently of all the other factors. This is possible if, for the test runs involving any level of any factor, the levels of the other factors are present in equal amounts. When an orthogonal test design has two-level factors coded -1 and +1, the inner (dot) product of any two columns is 0.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Population Parameter\"), mdx(\"td\", null, \"A quantity or statistical measure that for a given population is fixed, such as a mean or a variance. The parameter is used in some general distribution or frequency function (e.g., a Normal Distribution) to make it descriptive of that population.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Prior Distribution\"), mdx(\"td\", null, \"The probability distribution that expresses beliefs about an unknown quantity before testing takes place. Within AFOTEC this distribution could be based on the performance of a similar system, the performance of a previous version of a system, or SME knowledge.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Posterior Distribution\"), mdx(\"td\", null, \"The conditional probability distribution that describes an unknown quantity after test or experimental data is taken into account.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Projection\"), mdx(\"td\", null, \"A property of factorial designs where the degree of replication doubles when a design column is removed (such as when a factor is determined to be insignificant). With fractional factorial designs the degree of fractionation is reduced.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Qualitative\"), mdx(\"td\", null, \"A term used to describe data that is descriptive or subjective; the values are ordinal or nominal in nature; e.g., red, blue and green.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Quantitative\"), mdx(\"td\", null, \"A term used to describe data that is measured on a numeric or quantitative scale; interval and ratio scales are quantitative. The data may be discrete or continuous.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Randomization\"), mdx(\"td\", null, \"A principle of DOE used to average out the effects of unknown and uncontrollable nuisance factors.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Regression\"), mdx(\"td\", null, \"A statistical process to model the change in the mean value of a continuous dependent variable (e.g., measure) as the values of one or more continuous independent variables change.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Replication\"), mdx(\"td\", null, \"Replication is an independent, repeated run of a factor level combination (as opposed to measuring the result of a single test run twice\\u2014this is a repeated measure.) In JMP, requesting one replicate will create a design with two of each design point.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Resolution\"), mdx(\"td\", null, \"An indication of the ability to independently estimate main effects and interactions in a fractional factorial design.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Run\"), mdx(\"td\", null, \"One combination of factor levels used for collecting data on one or more measures; a test design point.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Sample\"), mdx(\"td\", null, \"A set of data collected from a population. In operational test, it is usually impossible to test the entire population of a new system, so a sample is tested.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Screening Designs\"), mdx(\"td\", null, \"Designs that focus on the identification of active main effects. The goal is to reduce an initially large list of potential factors to only those that are influential on the response variable. Using screening designs decreases the size of subsequent tests conducted to estimate two-factor interactions or higher-order effects.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Sparsity-of-Effects Principle\"), mdx(\"td\", null, \"The principle that a system is usually dominated by main effects and low-order interactions. Thus it is very likely that main effects (single factor) and two-factor interactions are the only significant effects when analyzing data from a test; higher-order interactions such as three-factor interactions are very rare.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Stochastic\"), mdx(\"td\", null, \"Randomly determined; Any process or system that has a random probability distribution or pattern which may be analyzed statistically, but not predicted perfectly.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Strength\"), mdx(\"td\", null, \"An integer between 2 and the total number of factors in the test design. For combinatorial designs, strength t means that for every possible subset of t factors, every possible t-tuple of level combinations is present in the design at least one time.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"t-tuple\"), mdx(\"td\", null, mdx(\"p\", null, \"A combination of the levels of t factors selected from a design. Suppose there is a design with four two-level factors with levels coded as +1 and -1.\"), mdx(\"p\", null, \"There are four possible 2-tuples, e.g. (+1,-1).\"), mdx(\"p\", null, \"There are eight possible 3-tuples, e.g. (+1,-1,+1).\"), mdx(\"p\", null, \"There are sixteen possible 4-tuples, e.g. (+1,-1,+1,+1).\"))))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/4-5-Appendices.md"},"frontmatter":{"metaTitle":"Appendices","metaDescription":"Appendices"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"0472c615-4c7b-564f-a42a-8c39998f4f5a"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/4-6-Test-Design-Guidance/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/4-6-Test-Design-Guidance/page-data.json new file mode 100644 index 00000000..acc29766 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/4-6-Test-Design-Guidance/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/4-6-Test-Design-Guidance","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"d43e23c7-1096-5004-a618-870e643aa2c9","title":"Test Design Guidance","slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance"},"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 Design Guidance\",\n \"metaTitle\": \"Test Design Guidance\",\n \"metaDescription\": \"Test Design Guidance\"\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 following documents have more information and guidance from the\\nDepartment of Defense and the Air Force on the use of Design of\\nExperiments in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. They are all accessible on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint or\\nin the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Analyst and Engineer Community.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \" between the service Operational Test Agencies (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Test and Evaluation Command\"\n }, \"ATEC\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test and Evaluation Force\"\n }, \"OPTEVFOR\"), \",\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", JTIC and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \"), 20 Feb 09, Using Design of Experiments for\\nOperational Test and Evaluation\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo, 19 Oct 10, Guidance on the use of Design of\\nExperiments (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \") in Operational Test and Evaluation\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo, 23 Jul 13, Best Practices for Assessing the\\nStatistical Adequacy of Experimental Designs Used in Operational\\nTest and Evaluation\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\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 Guide,\\\" Apr 20\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Institute for Defense Analyses paper, Nov 14, Power Analysis\\nTutorial for Experimental Design Software\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Operational Test Information File, 17 Feb 15, Statistical\\nPower for Test Designs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Instruction\"\n }, \"DODI\"), \" 5000.02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Operation of the Defense Acquisition System\"), \" , 7 Jan\\n15\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/4-6-Test-Design-Guidance.md"},"frontmatter":{"metaTitle":"Test Design Guidance","metaDescription":"Test Design Guidance"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"d43e23c7-1096-5004-a618-870e643aa2c9"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/4-7-Technical-References-and-Citations/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/4-7-Technical-References-and-Citations/page-data.json new file mode 100644 index 00000000..0e6e8496 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/4-7-Technical-References-and-Citations/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"173ab635-292a-51d0-8e60-e4605daf685d","title":"Technical References and Citations","slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations"},"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\": \"Technical References and Citations\",\n \"metaTitle\": \"Technical References and Citations\",\n \"metaDescription\": \"Technical References and Citations\"\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(\"em\", {\n parentName: \"p\"\n }, \"Best Practices for Assessing the Statistical\\nAdequacy of Experimental Designs Used in Operational Test and\\nEvaluation.\"), \" Washington, D.C.: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \".Freeman, L. J., Johnson, T. H., &\\nSimpson, J. R. (2014). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Power Analysis Tutorial for Experimental Design\\nSoftware.\"), \" Alexandria, Virginia: INSTITUTE FOR DEFENSE ANALYSES.Hartman,\\nM. (2014, August 19). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Design Comparison and Slection Method Best\\nPractice.\"), \" Retrieved March 3, 2015, from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Institute of Technology\"\n }, \"AFIT\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Scientific Test and Analysis Techniques\"\n }, \"STAT\"), \" COE:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.afit.edu/docs/Test%20Design%20Comparison%20and%20Selection-Best%20Practice.pdfKacker\"\n }, \"http://www.afit.edu/docs/Test%20Design%20Comparison%20and%20Selection-Best%20Practice.pdfKacker\"), \",\"), mdx(\"p\", null, \"R. N., Kuhn, R. D., & Lawrence, J. F. (2013). Combinatorial testing for\\nsoftware: An adaptation of design of experiments. \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Measurement, 46\"), \" (9),\\n3745-3752.Kruschke, J. K. (2012, May 31). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Bayesian Estimation\\nsupercedes the t test.\"), \" Retrieved March 17, 2015, from Indiana\\nUniversity, Bloomington:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.indiana.edu/%5C~kruschke/BEST/BEST.pdfKuhn\"\n }, \"http://www.indiana.edu/\\\\~kruschke/BEST/BEST.pdfKuhn\"), \", K. L. (2010).\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Practical Combinatorial Testing.\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Institute of Standards and Technology\"\n }, \"NIST\"), \", U.S. Department of\\nCommerce.Montgomery, D. C. (2009). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Design and Analysis of Experiments,\\n7th Edition.\"), \" New York: Wiley and Sons.Myers, M. A.-C. (2009). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Response\\nSurface Methodology.\"), \" Hoboken, NJ: John Wiley & Sons, Inc.NIST1. (n.d.).\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Engineering Statistics Handbook\"), \" . Retrieved from\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://math.nist.gov/coveringarrays/coveringarray.htmlNIST2\"\n }, \"http://math.nist.gov/coveringarrays/coveringarray.htmlNIST2\"), \". (n.d.).\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Engineering Statistics Handbook\"), \" . Retrieved from What are John\\\\'s 3/4\\nfractional factorial designs?:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.itl.nist.gov/div898/handbook/pri/section5/pri57.htmNIST3\"\n }, \"http://www.itl.nist.gov/div898/handbook/pri/section5/pri57.htmNIST3\"), \".\\n(n.d.). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Plackett-Burman Designs\"), \" . Retrieved from Engineering\\nStatistics Handbook:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri335.htmNIST4\"\n }, \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri335.htmNIST4\"), \".\\n(n.d.). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Central Composite Designs (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Combat Capability Document\"\n }, \"CCD\"), \")\"), \" . Retrieved from Engineering\\nStatistics Handbook:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri3361.htmOrtiz\"\n }, \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri3361.htmOrtiz\"), \",\\nF. (2014). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Dealing with Categorical Data Types in a Designed Experiment\\nPart II: Sizing a Designed Experiment when Using a Binary Response.\"), \"\\nRetrieved March 3, 2015, from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Institute of Technology\"\n }, \"AFIT\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Scientific Test and Analysis Techniques\"\n }, \"STAT\"), \" COE:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdfRosenbaum\"\n }, \"http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdfRosenbaum\"), \",\\nP. R. (2002). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Observational Studies Second Edition.\"), \" New York:\\nSpringer-Verlag Inc. .Winkler, R. L. (2003). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"An Introduction to\\nBayesian Inference and Decision, 2nd Edition.\"), \" Gainsville, FL:\\nProbabalistic Publishing (\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.decisions-books.com\"\n }, \"www.decisions-books.com\"), \").\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/4-7-Technical-References-and-Citations.md"},"frontmatter":{"metaTitle":"Technical References and Citations","metaDescription":"Technical References and Citations"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"173ab635-292a-51d0-8e60-e4605daf685d"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/4-8-Footnotes/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/4-8-Footnotes/page-data.json new file mode 100644 index 00000000..184f7c44 --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/4-8-Footnotes/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide/4-8-Footnotes","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"e74a1fdf-acbe-5cc8-9916-1b61fe6a138b","title":"Footnotes","slug":"/analyst_test_design_guide/4-8-Footnotes"},"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\": \"Footnotes\",\n \"metaTitle\": \"Footnotes\",\n \"metaDescription\": \"Footnotes\"\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, \"fn1\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Quantitative -- A term used to describe data that is measured on a\\nnumeric or quantitative scale; interval and ratio scales are\\nquantitative. The data may be discrete or continuous. \")), mdx(\"h1\", null, \"fn2\"), mdx(\"ol\", {\n \"start\": 2\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Qualitative -- A term used to describe data that is descriptive or\\nsubjective; the values are ordinal or nominal in nature; e.g., red,\\nblue and green. \")), mdx(\"h1\", null, \"fn3\"), mdx(\"ol\", {\n \"start\": 3\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Population parameter -- A quantity or statistical measure that for a\\ngiven population is fixed, such as a mean or a variance. The\\nparameter is used in some general distribution or frequency function\\n(e.g., a Normal Distribution) to make it descriptive of that\\npopulation. \")), mdx(\"h1\", null, \"fn4\"), mdx(\"ol\", {\n \"start\": 4\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Estimation -- An attempt to gain insight about an unknown population\\nparameter based on information obtained from sample data. At \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nwe typically estimate means and variances of measures, factor\\neffects, and proportions of failures. \")), mdx(\"h1\", null, \"fn5\"), mdx(\"ol\", {\n \"start\": 5\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Sample -- A set of data collected from a population. \")), mdx(\"h1\", null, \"fn6\"), mdx(\"ol\", {\n \"start\": 6\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Factor -- An independent variable which may affect the performance\\nof a system when its levels are changed. \")), mdx(\"h1\", null, \"fn7\"), mdx(\"ol\", {\n \"start\": 7\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Level -- A specific setting of a factor during a test or experiment. \")), mdx(\"h1\", null, \"fn8\"), mdx(\"ol\", {\n \"start\": 8\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Run -- One combination of factor levels used for collecting data on\\none or more measures; a test design point.\")), mdx(\"h1\", null, \"fn9\"), mdx(\"ol\", {\n \"start\": 9\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Effect - The average change in a response variable produced by\\nchanging the level of a factor. \")), mdx(\"h1\", null, \"fn10\"), mdx(\"ol\", {\n \"start\": 10\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Main Effect - The effect of a factor (independent variable) on a\\nmeasure (dependent variable) averaging across the levels of the\\nother factors. \")), mdx(\"h1\", null, \"fn11\"), mdx(\"ol\", {\n \"start\": 11\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Interaction -- A situation where the effect of one factor on a\\nresponse depends on the level of another factor. \")), mdx(\"h1\", null, \"fn12\"), mdx(\"ol\", {\n \"start\": 12\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Factorial Design -- A test plan consisting of two or more factors,\\neach with discrete possible values (or levels). A full factorial is\\na design whose experimental units (runs) take on all possible\\ncombinations of these levels. A design which includes a\\nstrategically selected subset of the possible combinations is called\\na fractional factorial. \")), mdx(\"h1\", null, \"fn13\"), mdx(\"ol\", {\n \"start\": 13\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Balance -- A column in a test design matrix is balanced if every\\nfactor level occurs an equal number of times. A test design is\\nbalanced if every possible factor level combination occurs an equal\\nnumber of times. \")), mdx(\"h1\", null, \"fn14\"), mdx(\"ol\", {\n \"start\": 14\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Orthogonal - A test design is orthogonal if each factor can be\\nevaluated independently of all the other factors. This is possible\\nif, for the test runs involving any level of any factor, the levels\\nof the other factors are present in equal amounts. When an\\northogonal test design has two-level factors coded -1 and +1, the\\ninner (dot) product of any two columns is 0.\")), mdx(\"h1\", null, \"fn15\"), mdx(\"ol\", {\n \"start\": 15\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Disallowed Combinations - A combination of the levels of two or more\\nfactors that cannot be feasibly executed together in a test run. \")), mdx(\"h1\", null, \"fn16\"), mdx(\"ol\", {\n \"start\": 16\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Center Point -- A test run where every continuous factor is set to\\nthe value halfway between its minimum and maximum factor levels. \")), mdx(\"h1\", null, \"fn17\"), mdx(\"ol\", {\n \"start\": 17\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Projection -- A property of factorial designs where the degree of\\nreplication doubles when a design column is removed (such as when a\\nfactor is determined to be insignificant). With fractional factorial\\ndesigns the degree of fractionation is reduced. \")), mdx(\"h1\", null, \"fn18\"), mdx(\"ol\", {\n \"start\": 18\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Active Effect -- A term used to describe a main effect (factor) or\\ninteraction that causes a statistically significant difference in\\nthe response variable when the factor levels are changed. \")), mdx(\"h1\", null, \"fn19\"), mdx(\"ol\", {\n \"start\": 19\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Sparsity-of-Effects Principle -- The principle that a system is\\nusually dominated by main effects and low-order interactions. Thus\\nit is very likely that main effects (single factor) and two-factor\\ninteractions are the only significant effects when analyzing data\\nfrom a test; higher-order interactions such as three-factor\\ninteractions are very rare. \")), mdx(\"h1\", null, \"fn20\"), mdx(\"ol\", {\n \"start\": 20\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Correlation -- A statistical measure on a scale from -1 to 1 that\\nindicates how close two variables are to having a linear\\nrelationship with each other. Two factors are perfectly correlated\\nwhen the value of one factor's level can be precisely determined by\\nknowing the value of the other factor's level. \")), mdx(\"h1\", null, \"fn21\"), mdx(\"ol\", {\n \"start\": 21\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Aliasing - A condition where the effect estimate of one factor\\nincludes the influence of one or more other effects (main effect or\\nhigher-order interactions). \")), mdx(\"h1\", null, \"fn22\"), mdx(\"ol\", {\n \"start\": 22\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Confounding -- Synonymous with aliasing: a condition where the\\neffect estimate of one factor includes the influence of one or more\\nother effects (main effect or higher-order interactions). \")), mdx(\"h1\", null, \"fn23\"), mdx(\"ol\", {\n \"start\": 23\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Resolution -- An indication of the ability to independently estimate\\nmain effects and interactions in a fractional factorial design. \")), mdx(\"h1\", null, \"fn24\"), mdx(\"ol\", {\n \"start\": 24\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Screening design -- Designs that focus on the identification of\\nactive main effects. The goal is to reduce an initially large list\\nof potential factors to only those that are influential on the\\nresponse variable. Using screening designs decreases the size of\\nsubsequent test designs used to estimate two factor interactions or\\nhigher-order effects.\")), mdx(\"h1\", null, \"fn25\"), mdx(\"ol\", {\n \"start\": 25\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Optimal Designs -- A test design whose levels are combined in a way\\nthat optimizes some statistical design quality criterion that is a\\nfunction of the design matrix.\")), mdx(\"h1\", null, \"fn26\"), mdx(\"ol\", {\n \"start\": 26\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Linear Regression -- A statistical process to model the change in\\nthe mean value of a continuous dependent variable (e.g., measure) as\\nthe values of one or more continuous independent variables change. \")), mdx(\"h1\", null, \"fn27\"), mdx(\"ol\", {\n \"start\": 27\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Augmentation -- The process of strategically adding new runs to an\\nexisting test design after some data has been collected. \")), mdx(\"h1\", null, \"fn28\"), mdx(\"ol\", {\n \"start\": 28\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Deterministic -- A deterministic system or model will always produce\\nthe same output from a given starting condition (level settings of\\nthe independent variables.) \")), mdx(\"h1\", null, \"fn29\"), mdx(\"ol\", {\n \"start\": 29\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Distribution -- A table or function showing all the possible values\\nof a data set and how often they occur. \")), mdx(\"h1\", null, \"fn30\"), mdx(\"ol\", {\n \"start\": 30\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"em\", {\n parentName: \"li\"\n }, \"t\"), \" -tuples - A combination of the levels of t factors selected from\\na design. Suppose there is a design with four two-level factors with\\nlevels coded as +1 and -1. There are four possible 2-tuples, e.g.\\n(+1,-1). There are eight possible 3-tuples, e.g. (+1,-1,+1). There\\nare sixteen possible 4-tuples, e.g. (+1,-1,+1,+1). \")), mdx(\"h1\", null, \"fn31\"), mdx(\"ol\", {\n \"start\": 31\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Strength - An integer between 2 and the total number of factors in\\nthe test design. For combinatorial designs, strength \", mdx(\"em\", {\n parentName: \"li\"\n }, \"t\"), \" means that\\nfor every possible subset of t factors, every possible \", mdx(\"em\", {\n parentName: \"li\"\n }, \"t\"), \" -tuple of\\nlevel combinations is present in the design at least one time. \")), mdx(\"h1\", null, \"fn32\"), mdx(\"ol\", {\n \"start\": 32\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Coverage - Describes the percentage of possible factor level\\ncombinations (after removing the disallowed combinations from the\\ncomplete combination space) that a combinatorial design includes at\\na given strength.\")), mdx(\"h1\", null, \"fn33\"), mdx(\"ol\", {\n \"start\": 33\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Stochastic - Randomly determined; any process or system that has a\\nrandom probability distribution or pattern which may be analyzed\\nstatistically, but not predicted perfectly.\")), mdx(\"h1\", null, \"fn34\"), mdx(\"ol\", {\n \"start\": 34\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"D-Efficiency is calculated as follows: \", mdx(\"span\", {\n parentName: \"li\",\n \"className\": \"inlineMath\"\n }, \"= 100 \\\\times \\\\left( \\\\frac{\\\\left| X^{'}X \\\\right|^{\\\\frac{1}{p}}}{N} \\\\right)\"), \" where p is the number of columns in X matrix and N\\nis the number of runs. \")), mdx(\"h1\", null, \"fn35\"), mdx(\"ol\", {\n \"start\": 35\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"G-Efficiency is calculated as follows: \", mdx(\"span\", {\n parentName: \"li\",\n \"className\": \"inlineMath\"\n }, \"= 100 \\\\times \\\\left( \\\\frac{\\\\sqrt{\\\\frac{p}{N}}}{\\\\sigma\\\\_{M}} \\\\right)\"), \" where p is the number of columns in X matrix, N is the\\nnumber of runs and \", \"[ \", mdx(\"em\", {\n parentName: \"li\"\n }, \"\\u03C3\"), \" ~\", mdx(\"em\", {\n parentName: \"li\"\n }, \"M\"), \"~ ]\", \"{.math .inline} is the maximum\\nstandard error for prediction across the space. The X matrix is the\\nde-correlated X matrix. \")), mdx(\"h1\", null, \"fn36\"), mdx(\"ol\", {\n \"start\": 36\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"A-Efficiency is calculated as follows: \", mdx(\"span\", {\n parentName: \"li\",\n \"className\": \"inlineMath\"\n }, \"= 100 \\\\times \\\\left( \\\\frac{p}{\\\\text{trace}\\\\left( N \\\\times \\\\left( X^{'}X \\\\right)^{- 1} \\\\right)} \\\\right)\"), \" where p is the\\nnumber of columns in X matrix and N is the number of runs. The X\\nmatrix is the de-correlated X matrix. \")), mdx(\"h1\", null, \"fn37\"), mdx(\"ol\", {\n \"start\": 37\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"ANOVA -- A mathematical process for evaluating the variation in data\\nbetween groups and within groups in order to determine whether there\\nis a differences between the group means. This procedure can be used\\nto compare multiple systems, or determine if there are differences\\nin the mean response between levels of a factor. \")), mdx(\"h1\", null, \"fn38\"), mdx(\"ol\", {\n \"start\": 38\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"An orthogonal array may not exist for the required number of factors\\nand levels \", mdx(\"a\", {\n parentName: \"li\",\n \"href\": \"#fnref38\"\n }, \"\\u21A9\\uFE0E\"))), mdx(\"h1\", null, \"fn39\"), mdx(\"ol\", {\n \"start\": 39\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"All factors must be continuous \")), mdx(\"h1\", null, \"fn40\"), mdx(\"ol\", {\n \"start\": 40\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Strength 4 and higher \")), mdx(\"h1\", null, \"fn41\"), mdx(\"ol\", {\n \"start\": 41\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Resolution VI or higher is required to analyze 3 factor interactions \")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#fn1","title":"fn1"},{"url":"#fn2","title":"fn2"},{"url":"#fn3","title":"fn3"},{"url":"#fn4","title":"fn4"},{"url":"#fn5","title":"fn5"},{"url":"#fn6","title":"fn6"},{"url":"#fn7","title":"fn7"},{"url":"#fn8","title":"fn8"},{"url":"#fn9","title":"fn9"},{"url":"#fn10","title":"fn10"},{"url":"#fn11","title":"fn11"},{"url":"#fn12","title":"fn12"},{"url":"#fn13","title":"fn13"},{"url":"#fn14","title":"fn14"},{"url":"#fn15","title":"fn15"},{"url":"#fn16","title":"fn16"},{"url":"#fn17","title":"fn17"},{"url":"#fn18","title":"fn18"},{"url":"#fn19","title":"fn19"},{"url":"#fn20","title":"fn20"},{"url":"#fn21","title":"fn21"},{"url":"#fn22","title":"fn22"},{"url":"#fn23","title":"fn23"},{"url":"#fn24","title":"fn24"},{"url":"#fn25","title":"fn25"},{"url":"#fn26","title":"fn26"},{"url":"#fn27","title":"fn27"},{"url":"#fn28","title":"fn28"},{"url":"#fn29","title":"fn29"},{"url":"#fn30","title":"fn30"},{"url":"#fn31","title":"fn31"},{"url":"#fn32","title":"fn32"},{"url":"#fn33","title":"fn33"},{"url":"#fn34","title":"fn34"},{"url":"#fn35","title":"fn35"},{"url":"#fn36","title":"fn36"},{"url":"#fn37","title":"fn37"},{"url":"#fn38","title":"fn38"},{"url":"#fn39","title":"fn39"},{"url":"#fn40","title":"fn40"},{"url":"#fn41","title":"fn41"}]},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide/4-8-Footnotes.md"},"frontmatter":{"metaTitle":"Footnotes","metaDescription":"Footnotes"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"e74a1fdf-acbe-5cc8-9916-1b61fe6a138b"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/analyst_test_design_guide/page-data.json b/sites/oteguide/page-data/analyst_test_design_guide/page-data.json new file mode 100644 index 00000000..3913562b --- /dev/null +++ b/sites/oteguide/page-data/analyst_test_design_guide/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/analyst_test_design_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"47ae1d72-7a43-5acc-85ba-b03c16a60c62","title":"Analyst Test Design Guide","slug":"/analyst_test_design_guide"},"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\": \"Analyst Test Design Guide\",\n \"metaTitle\": \"Analyst Test Design Guide\",\n \"metaDescription\": \"Analyst Test Design Guide\"\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, \"Last Updated/Reviewed: 08 December 2020\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"analyst_test_design_guide.md"},"frontmatter":{"metaTitle":"Analyst Test Design Guide","metaDescription":"Analyst Test Design Guide"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"47ae1d72-7a43-5acc-85ba-b03c16a60c62"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/app-data.json b/sites/oteguide/page-data/app-data.json index 3fe9f0c1..768ec3b9 100644 --- a/sites/oteguide/page-data/app-data.json +++ b/sites/oteguide/page-data/app-data.json @@ -1 +1 @@ -{"webpackCompilationHash":"203325c7032a25328279"} +{"webpackCompilationHash":"1fd7664b02fcbfd3792f"} diff --git a/sites/oteguide/page-data/editing_reports_guide/1-2-PURPOSE/page-data.json b/sites/oteguide/page-data/editing_reports_guide/1-2-PURPOSE/page-data.json new file mode 100644 index 00000000..d10a2485 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/1-2-PURPOSE/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/1-2-PURPOSE","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"57d4e997-1650-5f30-9ab2-cd3aeee6fa4d","title":"PURPOSE","slug":"/editing_reports_guide/1-2-PURPOSE"},"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\": \"PURPOSE\",\n \"metaTitle\": \"PURPOSE\",\n \"metaDescription\": \"PURPOSE\"\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 guide was developed for technical editors, but will help all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\npersonnel write and edit final test plans and reports that meet our goal\\nof providing relevant, credible, and timely feedback to the acquisition\\ncommunity and Air Force leaders.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"*Note\"), \" : This editing guide applies to final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test plans and\\nreports. It is not designed to take the place of, nor conflict with,\\nwriting guidance for other products, such as OPRs/EPRs, memos, or\\nother \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test products. Please adhere to the writing guidelines,\\nauthorities, and templates that apply to the specific product you are\\nproducing.*\")), mdx(\"p\", null, \"This guide follows the grammar and punctuation rules from the following\\nauthorities: Air Force Handbook (AFH) 33-337, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Tongue and Quill\"), \" , 27\\nMay 15 (Incorporating Change 1, 19 Nov 15), and the Air University\\nPress, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Air University Style and Author Guide\"), \" (Maxwell \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Base\"\n }, \"AFB\"), \" AL, 2005),\\nunless otherwise indicated. While you should explore and review\\nreference materials you feel are helpful in developing your editing\\nskills, the rules outlined herein take precedence over other\\nwriting/editing guidance.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/1-2-PURPOSE.md"},"frontmatter":{"metaTitle":"PURPOSE","metaDescription":"PURPOSE"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"57d4e997-1650-5f30-9ab2-cd3aeee6fa4d"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices/page-data.json b/sites/oteguide/page-data/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices/page-data.json new file mode 100644 index 00000000..af8c7881 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"cafe718b-5844-575a-8440-5cf9151e1023","title":"Executive Summary, Body, and Appendices","slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices"},"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\": \"Executive Summary, Body, and Appendices\",\n \"metaTitle\": \"Executive Summary, Body, and Appendices\",\n \"metaDescription\": \"Executive Summary, Body, and Appendices\"\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, \"Edit the executive summary, the body, and the appendices as separate\\ndocuments. The appendices will be created first because they contain the\\ntechnical information and details of the assessment or evaluation. In\\nthe appendices, symbols, equations, and technical terms are appropriate,\\njust as they are in tables. The body is a synopsis of the information\\ncontained in the appendices. It is written as a formal document in which\\nsymbols, abbreviations, and technical terms are spelled out and is\\nintended for a wider audience.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Executive Summary\"), \" . While the executive summary is usually written\\nlast, it is the most crucial part of the document because it is intended\\nfor and read by the wider acquisition community. If written as intended,\\nthe executive summary will capture the critical components of the\\nassessment or evaluation in a brief but thorough summary.\"), mdx(\"p\", null, \"The executive summary is written from the Commander's perspective, as\\nthough he or she is personally addressing the audience. It describes the\\nsystem under test, type of test, decision maker, and decision supported,\\nand summarizes the system's effectiveness, suitability, mission\\ncapability, critical deficiencies, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s recommendations (in\\norder of their significance) to correct those deficiencies. It is\\nwritten as a formal document in which symbols, abbreviations, and\\ntechnical terms are spelled out, and although it is acceptable to use\\nacronyms in the executive summary, writers should limit their use to\\npromote a smoother read.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices.md"},"frontmatter":{"metaTitle":"Executive Summary, Body, and Appendices","metaDescription":"Executive Summary, Body, and Appendices"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"cafe718b-5844-575a-8440-5cf9151e1023"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/1-4-Consistency-is-Key/page-data.json b/sites/oteguide/page-data/editing_reports_guide/1-4-Consistency-is-Key/page-data.json new file mode 100644 index 00000000..3aaf6b1e --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/1-4-Consistency-is-Key/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/1-4-Consistency-is-Key","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"d9ec6252-6ecb-58a7-a8e9-0b05d974c8f1","title":"Consistency is Key","slug":"/editing_reports_guide/1-4-Consistency-is-Key"},"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\": \"Consistency is Key\",\n \"metaTitle\": \"Consistency is Key\",\n \"metaDescription\": \"Consistency is Key\"\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, \"In regards to subjective writing preferences, ensure the author applies\\nthem consistently, i.e., benchmark, bench mark, and bench-mark should\\nnot appear in the same document. When such variations occur, choose the\\nmost frequently used or best option and change other instances to match.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/1-4-Consistency-is-Key.md"},"frontmatter":{"metaTitle":"Consistency is Key","metaDescription":"Consistency is Key"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"d9ec6252-6ecb-58a7-a8e9-0b05d974c8f1"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/1-5-One-Voice/page-data.json b/sites/oteguide/page-data/editing_reports_guide/1-5-One-Voice/page-data.json new file mode 100644 index 00000000..dfb395a7 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/1-5-One-Voice/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/1-5-One-Voice","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"4453c062-c8ae-5be2-9c5c-6b12e2c4943d","title":"One Voice","slug":"/editing_reports_guide/1-5-One-Voice"},"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\": \"One Voice\",\n \"metaTitle\": \"One Voice\",\n \"metaDescription\": \"One Voice\"\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, \"Several different test team members collaborate on writing each plan or\\nreport. Edit the mechanics of each part of the document separately, but\\nit is important to read the plan or report as a whole document to\\nconfirm that it reads as \\\"one voice\\\" rather than as a conglomeration of\\ndifferent sections by different authors.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/1-5-One-Voice.md"},"frontmatter":{"metaTitle":"One Voice","metaDescription":"One Voice"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"4453c062-c8ae-5be2-9c5c-6b12e2c4943d"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/1-6-Templates/page-data.json b/sites/oteguide/page-data/editing_reports_guide/1-6-Templates/page-data.json new file mode 100644 index 00000000..57838fda --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/1-6-Templates/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/1-6-Templates","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"f008de09-0204-5e3d-997e-cc2cb421c397","title":"Templates","slug":"/editing_reports_guide/1-6-Templates"},"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\": \"Templates\",\n \"metaTitle\": \"Templates\",\n \"metaDescription\": \"Templates\"\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, \"Templates for each type of test plan and report are posted on\\nSharePoint. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" encourages the use of templates because they are a\\ngood guide to ensure the test team includes all necessary planning and\\nreporting elements. Test teams may find it necessary to deviate from the\\ntemplates and include different information or exclude information not\\npertinent to their program. They should feel free to innovate as needed\\nas long as they meet the ultimate goal of creating a comprehensive\\ndocument that meets \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s planning and reporting obligations.\\nTemplates include blue instructional text to assist the test team in\\npopulating various sections, but if writers have questions not covered\\nin the instructional text, have them contact A-3 for additional\\nguidance.\"), mdx(\"p\", null, \"The templates are dynamic and change as guidance and reporting\\nrequirements change. A-3 attempts to make template changes in real time,\\nbut this is not always possible. If you are unsure whether a template\\nreflects the latest changes, contact the A-3 technical editor.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/1-6-Templates.md"},"frontmatter":{"metaTitle":"Templates","metaDescription":"Templates"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"f008de09-0204-5e3d-997e-cc2cb421c397"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/1-7-Microsoft-Word-Options/page-data.json b/sites/oteguide/page-data/editing_reports_guide/1-7-Microsoft-Word-Options/page-data.json new file mode 100644 index 00000000..5eb4602c --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/1-7-Microsoft-Word-Options/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/1-7-Microsoft-Word-Options","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ff724255-d555-55a7-8126-dfd8544a43fd","title":"Microsoft Word Options","slug":"/editing_reports_guide/1-7-Microsoft-Word-Options"},"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\": \"Microsoft Word Options\",\n \"metaTitle\": \"Microsoft Word Options\",\n \"metaDescription\": \"Microsoft Word Options\"\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, \"Set the following \\\"options\\\" to ensure Microsoft Word works in harmony\\nwith our templates. Setting these options from the start will solve a\\nlot of formatting problems before they begin.\"), mdx(\"h1\", null, \"Display:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"All formatting marks\")), mdx(\"h1\", null, \"Proofing:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"AutoCorrect: remove ALL checks\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"AutoFormat: remove all checks except for \\\"smart quotes\\\" ( \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Note\"), \" :\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not use superscript for ordinals; superscript is only\\nused for fractional factorial notations in factor tables)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"AutoFormat As You Type: remove all checks except for \\\"smart quotes\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Spelling and Grammar Settings:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Grammar and style options: Require (comma: always);\\n(punctuation: inside); (spaces:\\xA01)\")))), mdx(\"h1\", null, \"Advanced:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Enable Click and Type\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Default Paragraph Style: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Body\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Insert pictures \\\"in line with text\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Cut, copy, and paste\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Show Paste Options button when content is pasted\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Use smart cut and paste (Word 2002-2010)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Pasting between documents when style definitions conflict---Use\\nDestination Styles (Default)\")))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Show Bookmarks\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Field Shading--always\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Style area pane width in Draft and Outline views--2\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Compatibility should be Word 2010 \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"(DO NOT check any of the layout\\noptions)\")))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#display","title":"Display:"},{"url":"#proofing","title":"Proofing:"},{"url":"#advanced","title":"Advanced:"}]},"parent":{"__typename":"File","relativePath":"editing_reports_guide/1-7-Microsoft-Word-Options.md"},"frontmatter":{"metaTitle":"Microsoft Word Options","metaDescription":"Microsoft Word Options"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"ff724255-d555-55a7-8126-dfd8544a43fd"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/1-8-Focus-Areas/page-data.json b/sites/oteguide/page-data/editing_reports_guide/1-8-Focus-Areas/page-data.json new file mode 100644 index 00000000..fbbd4df5 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/1-8-Focus-Areas/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/1-8-Focus-Areas","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"a6376d6f-ba21-5fab-9b0f-c0ac2e1ee2a1","title":"Focus Areas","slug":"/editing_reports_guide/1-8-Focus-Areas"},"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\": \"Focus Areas\",\n \"metaTitle\": \"Focus Areas\",\n \"metaDescription\": \"Focus Areas\"\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, \"Enforce the following standards to ensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" produces uniform\\ndocuments. These areas are not listed in order of importance, but are an\\noverall view of the editing process.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/1-8-Focus-Areas.md"},"frontmatter":{"metaTitle":"Focus Areas","metaDescription":"Focus Areas"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"a6376d6f-ba21-5fab-9b0f-c0ac2e1ee2a1"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/1-9-Styles/page-data.json b/sites/oteguide/page-data/editing_reports_guide/1-9-Styles/page-data.json new file mode 100644 index 00000000..5cd735c6 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/1-9-Styles/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/1-9-Styles","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"81d924bf-3a38-5a25-bf87-6b9abe3b7cfe","title":"Styles","slug":"/editing_reports_guide/1-9-Styles"},"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\": \"Styles\",\n \"metaTitle\": \"Styles\",\n \"metaDescription\": \"Styles\"\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\"), \" templates are designed with unique Microsoft Word styles that\\nwork in tandem with the page numbering and the table of contents. That\\nis why it is critical to ensure the styles are not removed or corrupted\\nduring the writing process. Unless a writer deliberately changes or\\ncorrupts a style by deleting a heading or subheading, the templates are\\nuser-friendly and low maintenance. The body style is designed to be\\n\\\"justified\\\" and to have the optimal amount of white space to make it\\neasy to read and distinguish between paragraphs. \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses one space\\nafter end-of-sentence punctuation because that prevents excessive\\nspreading between letters and words when using justified alignment\"), \" .\"), mdx(\"p\", null, \"Problems can arise when writers copy and paste information from other\\nsources into the template document, which can introduce styles from that\\nsource. In those cases, you will have to clear the styles and reapply\\nthe appropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles. Teach writers to use the \\\"use destination\\nstyles\\\" option on the pasting clipboard to eliminate this problem.\"), mdx(\"p\", null, \"To confirm the styles are correct and uncorrupted, open the document in\\nDraft view. Reapply appropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles where necessary. Modify\\ncorrupted styles if it is something simple to correct such as left align\\nversus justified, tab spacing, font size, etc. If more than one style is\\ncorrupt or you cannot modify them easily, use the following steps to\\nimport styles from a document in which \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles are sound and\\nuncorrupted (i.e., plan or report template):\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click on the third icon in bottom left corner of \\\"Styles\\\" pane\\ncalled \\\"Manage Styles.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \\\"Import/Export\\\" on bottom left corner of the Edit tab.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"On the right side pane of the \\\"Organizer\\\" window that opens, close\\nthe \\\"In Normal\\\" file and open a document with all the uncorrupted\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles by clicking \\\"open file.\\\" Locate and open that file.\\nAll the styles from that document will populate the right side pane.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Copy all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles you wish to replace from the right side to\\nthe \\\"to Document 1\\\" left side. (Note: if you have set your \\\"Normal\\\"\\ntemplate to contain \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles \", \"[\", \"recommended\", \"]\", \", just copy the\\nnecessary styles from there to the \\\"to Document 1\\\" left side and\\nomit the step of closing the \\\"Normal\\\" file and finding a file with\\nuncorrupted \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles.)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \\\"yes\\\" or \\\"yes to all\\\" when prompted as to whether you want to\\noverwrite the existing styles in the document.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Close the \\\"Normal\\\" file or the file you copied styles from on the\\nright side pane.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Close out of the \\\"Organizer\\\" window.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The corrected styles will appear in your style pane.\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/1-9-Styles.md"},"frontmatter":{"metaTitle":"Styles","metaDescription":"Styles"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"81d924bf-3a38-5a25-bf87-6b9abe3b7cfe"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/2-1-Acronyms/page-data.json b/sites/oteguide/page-data/editing_reports_guide/2-1-Acronyms/page-data.json new file mode 100644 index 00000000..f7177f51 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/2-1-Acronyms/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/2-1-Acronyms","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"c60b2963-561e-51ec-9819-064d93fc5276","title":"Acronyms","slug":"/editing_reports_guide/2-1-Acronyms"},"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\": \"Acronyms\",\n \"metaTitle\": \"Acronyms\",\n \"metaDescription\": \"Acronyms\"\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, \"Define an acronym the first time it appears in each section (i.e.,\\nexecutive summary, body, appendices \", \"[\", \"as a whole, not each appendix as a\\nseparate section\", \"]\", \"), then use the acronym thereafter. Edit these three\\ndistinct parts of the plan or report as separate documents.\"), mdx(\"p\", null, \"Add all acronyms in the document to the acronym table in the designated\\nappendix. If an acronym is only used one or two times, delete it from\\nthe document and the acronym table and spell it out.\"), mdx(\"p\", null, \"Define acronyms in tables and figures in the acronym table, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"not within\\nthe table or figure\"), \" ; the only exception is a measure table that\\ndisplays a \\\"mean\\\" as the metric. To help readers make the connection to\\na standard term (i.e., \\\"mean time between failures\\\"), add the standard\\nacronym in parenthesis following the measure title, then define it below\\n\\\"\", \"*\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or supports \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or \\\\^ Identified Standard\\\" if applicable (or in a\\nmerged row at the bottom of the table as shown in the following\\nexample). Then, add the acronym to the acronym table.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"(FOUO)\"), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operational Capability: Reliability\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Measure\"), mdx(\"td\", null, \"Metric\"), mdx(\"td\", null, \"Threshold\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOS 3.8: Time Between Failures (MTBF)\"), mdx(\"td\", null, \"Mean\"), mdx(\"td\", null, \">= 8,736 hours\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MTBF\\u2013mean time between failures\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, \"Some acronyms are more easily recognized than the words they represent\\n(e.g., NASA, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"North Atlantic Treaty Organization\"\n }, \"NATO\"), \"). In those cases, do not remove the acronym from the\\ndocument, nor from the acronym table even if it is used only once. This\\nis a judgment call so consult your test team's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \", \", 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\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \" if in\\ndoubt as to whether you should remove a particular acronym.\"), mdx(\"p\", null, \"Acronyms use the same vowel/consonant rules as regular words (i.e., use\\n\\\"a\\\" before a consonant; use \\\"an\\\" before a vowel), except that with\\nacronyms the beginning \\\"sound\\\" rather than the beginning \\\"letter\\\" is\\nwhat determines the article you will use. If the beginning sound is a\\nvowel sound, you will use \\\"an.\\\" If it is a consonant sound, use \\\"a.\\\"\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \" report (beginning sound--long o vowel sound)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"a NASA rocket (beginning sound--consonant n)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \" (beginning sound--short e vowel sound)\"))), mdx(\"p\", null, \"Follow regular capitalization rules when defining acronyms and\\ncapitalize only those words that are proper nouns. The only exception to\\nthis rule is the acronym table, which should use the following \\\"title\\ncase\\\" capitalization rules for uniformity:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capitalize the principal words, including prepositions and\\nconjunctions of four or more letters.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capitalize an article---the, a, an---or words of fewer than four\\nletters if it is the first or last word in a title.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Performing the acronym scrub is the most time-intensive part of the\\nedit, but it must be done, and is ultimately the technical editor's\\nresponsibility. Do not cheat!\")), mdx(\"p\", null, \"Perform a spell check, but before you begin, go into Microsoft Word\\noptions/Proofing and uncheck the Custom Dictionary \\\"Custom Dic\\\" button;\\nselect \\\"English (United States)\\\" as your language.\"), mdx(\"p\", null, \"Make sure each acronym spell-check catches was defined in the acronym\\ntable. If not, add it and define it. Begin with the first acronym in the\\ntable and perform the following:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Highlight the acronym\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Copy it (ctrl c)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Open find (ctrl f)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Paste (ctrl v)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Go to top of doc (ctrl home)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Enter \\\"find next\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Make sure the acronym is defined the first time it shows up in the\\nbody and appendices, and that the definition is the same as what is\\nin the acronym table\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Repeat this process for each acronym\"))), mdx(\"p\", null, \"In addition to this, remove acronyms from the table that were not used\\nin the plan or report. The acronyms provided in the templates will not\\nnecessarily pertain to the document you are editing.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/2-1-Acronyms.md"},"frontmatter":{"metaTitle":"Acronyms","metaDescription":"Acronyms"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"c60b2963-561e-51ec-9819-064d93fc5276"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/2-2-Commas/page-data.json b/sites/oteguide/page-data/editing_reports_guide/2-2-Commas/page-data.json new file mode 100644 index 00000000..74a88d17 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/2-2-Commas/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/2-2-Commas","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"94e3d3a5-0886-58a5-9e69-8ead96a1a5af","title":"Commas","slug":"/editing_reports_guide/2-2-Commas"},"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\": \"Commas\",\n \"metaTitle\": \"Commas\",\n \"metaDescription\": \"Commas\"\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, \"Technical writing requires the use of the \\\"serial\\\" comma (sometimes\\ncalled the oxford comma), which is the comma used immediately preceding\\na coordinating conjunction (usually, and, or, or sometimes nor), or the\\nfinal item in a series of three or more items. This is important because\\nthe meaning of a sentence can change when commas are omitted or used\\nincorrectly.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/2-2-Commas.md"},"frontmatter":{"metaTitle":"Commas","metaDescription":"Commas"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"94e3d3a5-0886-58a5-9e69-8ead96a1a5af"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/2-3-Next-Page-and-Page-Breaks/page-data.json b/sites/oteguide/page-data/editing_reports_guide/2-3-Next-Page-and-Page-Breaks/page-data.json new file mode 100644 index 00000000..d1e75eb4 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/2-3-Next-Page-and-Page-Breaks/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"7c3b255c-b08b-593b-a456-403022d6849e","title":"Next Page and Page Breaks","slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks"},"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\": \"Next Page and Page Breaks\",\n \"metaTitle\": \"Next Page and Page Breaks\",\n \"metaDescription\": \"Next Page and Page Breaks\"\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, \"Use \\\"next page\\\" breaks when you separate a page to change its\\norientation from portrait to landscape, or when you create a blank page\\nor a new appendix. Use regular \\\"page\\\" breaks versus \\\"next page\\\" breaks\\nbetween new sections in the body and between measures in appendix B. The\\nfrugal use of \\\"next page\\\" breaks prevents the problem of a document\\ncontaining too many sections, which inhibits printing a customized range\\nof pages within a document.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"NEVER\"), \" use \\\"continuous\\\" page breaks in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" documents. \\\"Continuous\\\"\\npage breaks are hard to remove. If you try to delete them, you will\\nbegin a domino affect of formatting difficulties. Use the following\\nmethod to remove \\\"continuous\\\" page breaks successfully:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Place cursor at beginning of document\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Scroll to end of document while holding mouse button down to select\\neverything (do not use Ctrl A) (this can take a while on a long\\ndocument, but there is no short cut so be patient)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Hold down shift button and do a left click on mouse\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Go to Page Layout/Page Setup\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"On layout pick \\\"New Page\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"And \\\"selected sections\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Push OK button\"))), mdx(\"p\", null, \"You should have all \\\"next page\\\" page breaks in place of the \\\"continuous\\\"\\npage breaks when you complete this process.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/2-3-Next-Page-and-Page-Breaks.md"},"frontmatter":{"metaTitle":"Next Page and Page Breaks","metaDescription":"Next Page and Page Breaks"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"7c3b255c-b08b-593b-a456-403022d6849e"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/2-4-Headers-and-Footers/page-data.json b/sites/oteguide/page-data/editing_reports_guide/2-4-Headers-and-Footers/page-data.json new file mode 100644 index 00000000..a84fa268 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/2-4-Headers-and-Footers/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/2-4-Headers-and-Footers","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"2a519469-c31d-5a88-9737-f1f511eb644e","title":"Headers and Footers","slug":"/editing_reports_guide/2-4-Headers-and-Footers"},"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\": \"Headers and Footers\",\n \"metaTitle\": \"Headers and Footers\",\n \"metaDescription\": \"Headers and Footers\"\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(\"em\", {\n parentName: \"p\"\n }, \"Headers.\"), \" All headers on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" plans and reports should be connected\\n(\\\"linked to previous\\\") with the exception of the SF298 (only applicable\\nto reports). This enables consistent classification markings on every\\npage.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Footers.\"), \" All footers on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" plans and reports should be connected,\\nwith the exception of the cover page (which is not numbered) and the\\nSF298 (only applicable to reports). This enables consistent\\nclassification markings on every page.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Header/Footer on SF298.\"), \" Keep information on the Standard Form (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Forces OR Standard Form\"\n }, \"SF\"), \") 298\\nat the unclassified level whenever possible. It will usually have a\\ndifferent classification marking or none at all. However, even when its\\nclassification is the same as that of the plan or report, do not connect\\nthe header or footer because the form also requires different margins\\nand header/footer settings and does not have page numbers (technically,\\nit is not part of the report and should not be included in the number of\\npages in a report).\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/2-4-Headers-and-Footers.md"},"frontmatter":{"metaTitle":"Headers and Footers","metaDescription":"Headers and Footers"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"2a519469-c31d-5a88-9737-f1f511eb644e"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/2-5-Page-Numbering/page-data.json b/sites/oteguide/page-data/editing_reports_guide/2-5-Page-Numbering/page-data.json new file mode 100644 index 00000000..55b5beb3 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/2-5-Page-Numbering/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/2-5-Page-Numbering","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"036c1d3a-3054-5159-b105-29a6cd996dad","title":"Page Numbering","slug":"/editing_reports_guide/2-5-Page-Numbering"},"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\": \"Page Numbering\",\n \"metaTitle\": \"Page Numbering\",\n \"metaDescription\": \"Page Numbering\"\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 templates were designed with automatic page numbering that populates\\nthe table of contents automatically. However, when you add a \\\"next page\\\"\\nbreak, you may have to click into the footer and go to \\\"format page\\nnumbers.\\\" Click the radial button and choose \\\"continue from previous\\nsection\\\" so that the page numbering will continue instead of restarting\\nat page 1.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/2-5-Page-Numbering.md"},"frontmatter":{"metaTitle":"Page Numbering","metaDescription":"Page Numbering"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"036c1d3a-3054-5159-b105-29a6cd996dad"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/2-6-Blank-Pages/page-data.json b/sites/oteguide/page-data/editing_reports_guide/2-6-Blank-Pages/page-data.json new file mode 100644 index 00000000..276addba --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/2-6-Blank-Pages/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/2-6-Blank-Pages","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"2e52de83-c70a-52b5-abcf-aa7a7162f98f","title":"Blank Pages","slug":"/editing_reports_guide/2-6-Blank-Pages"},"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\": \"Blank Pages\",\n \"metaTitle\": \"Blank Pages\",\n \"metaDescription\": \"Blank Pages\"\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, \"Insert or remove a blank page (i.e., Page intentionally blank) as\\nnecessary so that the following pages are always right facing (which\\nwill present on the left side of the screen in the 2-page layout view):\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Executive Summary\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Table of Contents\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"First page of the body of the report, which begins with\\n\\\"Introduction\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"First page of Appendix A\"))), mdx(\"p\", null, \"The SF298 Report Documentation Page (applicable for reports only) should\\nalways be left facing, (which will appear on the right side of the\\nscreen in the 2-page layout view) to ensure the form stays on the front\\nand back of the same page.\"), mdx(\"p\", null, \"A blank page should continue the page numbering of the section it\\nfollows (A-12 is followed by the blank page A-13). The section that\\nfollows the blank page will begin with page number one (B-1).\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/2-6-Blank-Pages.md"},"frontmatter":{"metaTitle":"Blank Pages","metaDescription":"Blank Pages"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"2e52de83-c70a-52b5-abcf-aa7a7162f98f"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/2-7-Capitalization/page-data.json b/sites/oteguide/page-data/editing_reports_guide/2-7-Capitalization/page-data.json new file mode 100644 index 00000000..9466d54f --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/2-7-Capitalization/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/2-7-Capitalization","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"bae53965-d790-52e2-a005-a23a7349ef2a","title":"Capitalization","slug":"/editing_reports_guide/2-7-Capitalization"},"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\": \"Capitalization\",\n \"metaTitle\": \"Capitalization\",\n \"metaDescription\": \"Capitalization\"\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, \"Use capitalization appropriately. Writers have a tendency to capitalize\\nnonspecific titles of documents and things, even acronym definitions.\"), mdx(\"p\", null, \"Capitalize:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The title of a document when used in conjunction with the program's\\nproper name:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\\\"initial operational test and evaluation\\\" becomes \\\"RQ-4 Initial\\nOperational Test and Evaluation\\\"\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The production decision when used in conjunction with the decision\\nmaker's proper title:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\\\"full-rate production decision\\\" becomes the \\\"Under Secretary of\\nDefense for Acquisition, Technology and Logistics' (\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \"\", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L\", \"]\", \")\\nFull-Rate Production decision\\\"\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Cross-references (table or figure) when used at the beginning of a\\nsentence, but not in the middle of a sentence:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\\"Table (Figure) 1 contains the details.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\\"\", \".\", \"..as shown in table (figure) X.\\\"\"))))), mdx(\"p\", null, \"Frame COIs as questions. Write them as a sentence punctuated with a\\nquestion mark ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Example\"), \" : \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1: Does the KC-46 support refueling?).\\nWrite \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" and MOSs in title case ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Example\"), \" : \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.8: Percent of\\nReports and Queries Generated Successfully).\"), mdx(\"p\", null, \"The acronym list is considered a table. Use title case capitalization\\nfor style continuity. In all other parts of the document, follow regular\\ncapitalization rules for words acronyms represent. Joint Publication\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \") 1-02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Department of Defense Dictionary of Military and Associated\\nTerms\"), \" , 12\\xA0Apr 01 (amended through Apr 10), Appendix A, contains a\\ncomprehensive list of abbreviations and acronyms. Refer to this\\npublication for clarification on when to, or not to, capitalize words.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/2-7-Capitalization.md"},"frontmatter":{"metaTitle":"Capitalization","metaDescription":"Capitalization"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"bae53965-d790-52e2-a005-a23a7349ef2a"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases/page-data.json b/sites/oteguide/page-data/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases/page-data.json new file mode 100644 index 00000000..ff2751da --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"0f2baa05-1c4c-567f-a885-143e59c0f1e1","title":"Citing Air Force (or Other Military) Bases","slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases"},"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\": \"Citing Air Force (or Other Military) Bases\",\n \"metaTitle\": \"Citing Air Force (or Other Military) Bases\",\n \"metaDescription\": \"Citing Air Force (or Other Military) Bases\"\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, \"Verify military bases are cited properly. The first time a base is\\nmentioned, spell out the name, type of base, and state or country (ex:\\nEdwards Air Force Base, California; Ramstein Air Base, Germany; Royal\\nAir Force Lakenheath, England). Thereafter, use the name of the base\\nonly, or the name in conjunction with the type of base (ex: Edwards or\\nEdwards \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Base\"\n }, \"AFB\"), \"; Ramstein or Ramstein AB; Lakenheath or RAF Lakenheath). In\\ntables and figures, use only the abbreviated form.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases.md"},"frontmatter":{"metaTitle":"Citing Air Force (or Other Military) Bases","metaDescription":"Citing Air Force (or Other Military) Bases"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"0f2baa05-1c4c-567f-a885-143e59c0f1e1"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/2-9-Vertical-Lists/page-data.json b/sites/oteguide/page-data/editing_reports_guide/2-9-Vertical-Lists/page-data.json new file mode 100644 index 00000000..8b4bcca6 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/2-9-Vertical-Lists/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/2-9-Vertical-Lists","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"21386905-adbd-5772-8699-c92ab8c80e59","title":"Vertical Lists","slug":"/editing_reports_guide/2-9-Vertical-Lists"},"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\": \"Vertical Lists\",\n \"metaTitle\": \"Vertical Lists\",\n \"metaDescription\": \"Vertical Lists\"\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, \"Validate proper punctuation, capitalization, and structure of vertical\\n(bulleted) lists, depending on how the information was structured.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example 1:\")), mdx(\"p\", null, \"The test team will assess the following capabilities:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Data conversion\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Upgrade integration\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Operability\"))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example 2:\")), mdx(\"p\", null, \"The test team will assess the\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"multiple data conversions necessary to transition from the legacy\\nsystem to the upgraded system;\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"integration of the upgrade at every location (all six Air Force\\nbases); and\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"operability at Peterson Air Force Base, Colorado; Kirtland Air Force\\nBase, New Mexico; and Wright-Patterson Air Force Base, Ohio.\"))), mdx(\"p\", null, \"The type of vertical list used will depend on the complexity and length\\nof the ideas presented. Example 1 is good for a simple list. Example 2\\nis a good choice for a complex sentence that contains various types of\\npunctuation and could be confusing when expressed in one very long,\\nlinear sentence.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/2-9-Vertical-Lists.md"},"frontmatter":{"metaTitle":"Vertical Lists","metaDescription":"Vertical Lists"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"21386905-adbd-5772-8699-c92ab8c80e59"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/3-1-Numbering-Tables-and-Figures/page-data.json b/sites/oteguide/page-data/editing_reports_guide/3-1-Numbering-Tables-and-Figures/page-data.json new file mode 100644 index 00000000..80799f3e --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/3-1-Numbering-Tables-and-Figures/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"d4d7f84b-3be0-5ca2-b671-5ef0222bd90f","title":"Numbering Tables and Figures","slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures"},"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\": \"Numbering Tables and Figures\",\n \"metaTitle\": \"Numbering Tables and Figures\",\n \"metaDescription\": \"Numbering Tables and Figures\"\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, \"Number tables and figures sequentially and cross-reference them in the\\npreceding text. In the body, number tables and figures consecutively\\nthroughout (Use Navigation Pane on View Tab). Then, restart the table\\nand figure numbering in each appendix, adding the appendix letter as a\\nprefix. For example, \\\"Table A-5\\\" would be the fifth table in \\\"Appendix\\nA.\\\"\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/3-1-Numbering-Tables-and-Figures.md"},"frontmatter":{"metaTitle":"Numbering Tables and Figures","metaDescription":"Numbering Tables and Figures"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"d4d7f84b-3be0-5ca2-b671-5ef0222bd90f"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/3-2-Tables/page-data.json b/sites/oteguide/page-data/editing_reports_guide/3-2-Tables/page-data.json new file mode 100644 index 00000000..0c30269a --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/3-2-Tables/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/3-2-Tables","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"6df1e491-b6e2-52e2-8391-1dd3c085628e","title":"Tables","slug":"/editing_reports_guide/3-2-Tables"},"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\": \"Tables\",\n \"metaTitle\": \"Tables\",\n \"metaDescription\": \"Tables\"\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 most important aspect of editing tables is to ensure the contents\\nreflect the information in the accompanying text accurately. Check each\\nof the following standards:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Apply \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Table Header + Rating and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Table Text styles\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Verify table properties: preferred width: 100%; default cell\\nmargins: top/bottom: 0\\\", left/right: 0.08\\\"; borders: 1 pt\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Align cells left/center\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Add classification by inserting a merged row above the header\\nrow\", \"-\", \"-apply the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Caption + Class style to classification\\nportion marking\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure classification and header rows repeat by highlighting\\nclassification and header rows and selecting \\\"repeat header rows\\\" in\\n\\\"Layout\\\" tab\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure tables break across the next page when necessary; avoid\\nexcess white space whenever possible, particularly in classified\\ndocuments\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Make sure ratings in tables match ratings in accompanying narrative\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure changes made to COIs, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", and MOSs are rolled into all the\\ntables (especially the evaluation summary chart or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \") in which\\nthey appear, and into affected narratives\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure ratings are uniform in color and size (copy and paste from\\ntemplate ratings)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Confirm tables use percent sign, dollar sign, numbers, and other\\nsymbols\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Do not define acronyms within the table except when it includes a\\nstandard mean term in parenthesis (i.e., MTBF)\", \"-\", \"-add the acronym and\\nits definition below \\\"\", \"*\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or supports \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or \\\\^ Identified\\nStandard\\\" if applicable (or in a merged row at the bottom of the\\ntable)\", \"-\", \"-add the acronym to the acronym table\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Align numbers on decimal (use decimal tab on ruler).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Add footnotes to the bottom of table in an inserted/merged row or\\nshift/enter below \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or Identified Standard, if applicable.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Eliminate repetitive symbols or labels (e.g., \", \"$\", \", %, hrs) by adding\\nthem to the table header and deleting them from text cells, when\\nappropriate\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capitalize cross-references at the beginning of a sentence: \\\"Table 1\\ncontains the details.\\\" Do not capitalize them in the middle of a\\nsentence: \\\"\", \".\", \"..as shown in table X.\\\"\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/3-2-Tables.md"},"frontmatter":{"metaTitle":"Tables","metaDescription":"Tables"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"6df1e491-b6e2-52e2-8391-1dd3c085628e"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/3-3-Figures/page-data.json b/sites/oteguide/page-data/editing_reports_guide/3-3-Figures/page-data.json new file mode 100644 index 00000000..75b626b4 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/3-3-Figures/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/3-3-Figures","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"938fef95-e567-520e-9e16-6fb52d1bfe22","title":"Figures","slug":"/editing_reports_guide/3-3-Figures"},"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\": \"Figures\",\n \"metaTitle\": \"Figures\",\n \"metaDescription\": \"Figures\"\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, \"Ensure contents of a figure reflects the information in the accompanying\\ntext accurately. Check each of the following standards:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Apply \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Caption + Class style to caption and classification\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Apply 1-pt black border\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Do not copy/paste a figure from another document, but save it as a\\n\\\".png\\\" or \\\".jpg\\\" file and insert it as a picture. Alternatively, use\\nthe \\\"snip and sketch\\\" tool to save any image\", \"-\", \"-the image will remain\\nsharp and clear because it is a scan of the image rather than a\\nconversion. Before \\\"capturing\\\" your image, unselect the \\\"show all\\nformatting marks\\\" so that you will not capture the marks with the\\npicture.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Do not duplicate figures in the body and appendices. The body is a\\nconcise presentation of the most important facts taken from the\\nappendices. Appendices contain the comprehensive details and are the\\nbetter choice for detailed figures describing a system or test.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Eliminate text boxes, symbols, figures, etc., inserted on top of\\nfigures by following the procedures above for converting pasted\\npictures to a .png or .jpg file. Reinsert them as a picture with all\\nadd-ons captured as part of the picture.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure all acronyms used in figures were added to and defined in the\\nacronym table.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capitalize cross-references at the beginning of a sentence: \\\"Figure\\n1 contains the details.\\\" Do not capitalize them in the middle of a\\nsentence: \\\"\", \".\", \"..as shown in figure X.\\\"\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/3-3-Figures.md"},"frontmatter":{"metaTitle":"Figures","metaDescription":"Figures"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"938fef95-e567-520e-9e16-6fb52d1bfe22"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/3-4-Passive-Voice/page-data.json b/sites/oteguide/page-data/editing_reports_guide/3-4-Passive-Voice/page-data.json new file mode 100644 index 00000000..36911e01 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/3-4-Passive-Voice/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/3-4-Passive-Voice","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ae732afd-ed92-5f80-a203-da16893f827d","title":"Passive Voice","slug":"/editing_reports_guide/3-4-Passive-Voice"},"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\": \"Passive Voice\",\n \"metaTitle\": \"Passive Voice\",\n \"metaDescription\": \"Passive Voice\"\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, \"Change passive voice to active voice, when appropriate. You can\\nrecognize a sentence with passive voice because a form of the verb to be\\n(is, are, was, were, be, being, or been) is followed by a past\\nparticiple verb (a verb ending in ed, en, or t). A sentence written in\\npassive voice always contains both.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Verb\"), mdx(\"th\", null, \"Passive Sentence\"), mdx(\"th\", null, \"Active Sentence\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"is\"), mdx(\"td\", null, \"Adequate planning\", mdx(\"strong\", null, \"\\xA0is\\xA0\"), \"requir\", mdx(\"strong\", null, \"ed\\xA0\"), \"for successful OT&E.\"), mdx(\"td\", null, \"Successful OT&E requires adequate planning.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"are\"), mdx(\"td\", null, \"Details\", mdx(\"strong\", null, \"\\xA0are\\xA0\"), \"contain\", mdx(\"strong\", null, \"ed\\xA0\"), \"in appendix D.\"), mdx(\"td\", null, \"Appendix D contains details.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"was\"), mdx(\"td\", null, \"The course\", mdx(\"strong\", null, \"\\xA0was\\xA0\"), \"taugh\", mdx(\"strong\", null, \"t\\xA0\"), \"by the instructor.\"), mdx(\"td\", null, \"The instructor taught the course.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"were\"), mdx(\"td\", null, \"The results\", mdx(\"strong\", null, \"\\xA0were\\xA0\"), \"writt\", mdx(\"strong\", null, \"en\\xA0\"), \"in active voice.\"), mdx(\"td\", null, \"They wrote the results in active voice ,\", mdx(\"em\", null, \"or if subject is known,\"), \"The test team wrote the results in active voice.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"be\"), mdx(\"td\", null, \"Annual maintenance\", mdx(\"strong\", null, \"\\xA0will be\\xA0\"), \"perform\", mdx(\"strong\", null, \"ed\\xA0\"), \"on the system.\"), mdx(\"td\", null, \"Maintainers will perform annual maintenance on the system\", mdx(\"em\", null, \"or\"), \"Maintainers will perform maintenance on the system annually.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"being\"), mdx(\"td\", null, \"Part A\", mdx(\"strong\", null, \"\\xA0was being\\xA0\"), \"substitut\", mdx(\"strong\", null, \"ed\\xA0\"), \"for part B as a workaround.\"), mdx(\"td\", null, \"The workaround substituted part A for part B.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"been\"), mdx(\"td\", null, \"The data\", mdx(\"strong\", null, \"\\xA0was\\xA0\"), \"giv\", mdx(\"strong\", null, \"en\\xA0\"), \"to the analyst.\"), mdx(\"td\", null, \"The analyst received the data,\", mdx(\"em\", null, \"or if subject is known,\"), \"The test director gave the analyst the data.\")))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/3-4-Passive-Voice.md"},"frontmatter":{"metaTitle":"Passive Voice","metaDescription":"Passive Voice"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"ae732afd-ed92-5f80-a203-da16893f827d"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/3-5-Copyrights-and-Trademarks/page-data.json b/sites/oteguide/page-data/editing_reports_guide/3-5-Copyrights-and-Trademarks/page-data.json new file mode 100644 index 00000000..0390f7ed --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/3-5-Copyrights-and-Trademarks/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"510a3983-9f4a-5b8a-99e0-db6ad3e425dd","title":"Copyrights and Trademarks","slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks"},"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\": \"Copyrights and Trademarks\",\n \"metaTitle\": \"Copyrights and Trademarks\",\n \"metaDescription\": \"Copyrights and Trademarks\"\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, \"In accordance with the following authorities, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is not required to\\nuse the designated markings for copyrights and trademarks in our\\ndocuments because we are not a commercial entity and we do not\\ndistribute our documents publically. We are, however, required to use\\nthe proper spelling and capitalization for these trademarks (e.g.,\\nMicrosoft PowerPoint, Microsoft Word).\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Copyeditor's Handbook\"), \" states:\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"\\\"There is no need to include such designations as ^\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Manual OR Telemetry OR Test Manager\"\n }, \"TM\"), \"^ (trademark),\\n^\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Manager OR Service Manager OR Single Manager\"\n }, \"SM\"), \"^ (service mark), \\xAE\\xA0(registered trademark), or \\xA9 (copyright) in\\nrunning text. Indeed, it is preferable not to use these symbols\\nbecause they may interfere with the line spacing of the final\\ndocument.\\\"\"), mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"-\", \"-Einsohn, Amy. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"The Copyeditor's Handbook\"), \" , 2d ed. University of\\nCalifornia Press: Berkeley. 2006.\")), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Gregg Manual Reference Manual\"), \" states:\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"\\\"If you refer to other organizations' trademarks in material of a\\ncommercial nature that will be publically distributed, use a raised\\nsymbol after each trademark. In all other documents, the symbols are\\nnot necessary, but do use the proper spelling and capitalization for\\nthese trademarks.\\\"\"), mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"-\", \"- \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Gregg Manual Reference Manual\"), \" , 10th ed., McGraw-Hill: New York.\\n2005. p 114.\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/3-5-Copyrights-and-Trademarks.md"},"frontmatter":{"metaTitle":"Copyrights and Trademarks","metaDescription":"Copyrights and Trademarks"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"510a3983-9f4a-5b8a-99e0-db6ad3e425dd"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/3-6-Wordiness/page-data.json b/sites/oteguide/page-data/editing_reports_guide/3-6-Wordiness/page-data.json new file mode 100644 index 00000000..0a56caae --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/3-6-Wordiness/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/3-6-Wordiness","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"d68ea301-60aa-5fe0-ac20-eb0959f53051","title":"Wordiness","slug":"/editing_reports_guide/3-6-Wordiness"},"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\": \"Wordiness\",\n \"metaTitle\": \"Wordiness\",\n \"metaDescription\": \"Wordiness\"\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, \"Remove extra words that add nothing to the meaning of the sentence, as\\nshown in the following examples:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Capability\"\n }, \"IOC\"), \" plus 10-year \", mdx(\"em\", {\n parentName: \"p\"\n }, \"period\"), \" ---\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Capability\"\n }, \"IOC\"), \" plus 10 years\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Over a 5-year \", mdx(\"em\", {\n parentName: \"p\"\n }, \"time\"), \" period---Over a 5-year period \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"or\"), \" Over 5\\nyears\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Program was \", mdx(\"em\", {\n parentName: \"p\"\n }, \"first\"), \" launched---Program was launched\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"In order\"), \" to avoid confusion---To avoid confusion\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/3-6-Wordiness.md"},"frontmatter":{"metaTitle":"Wordiness","metaDescription":"Wordiness"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"d68ea301-60aa-5fe0-ac20-eb0959f53051"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes/page-data.json b/sites/oteguide/page-data/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes/page-data.json new file mode 100644 index 00000000..6449ed69 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"2a6f917f-5d78-5199-9a0f-e36a6fd0f8f2","title":"Hyphens, En Dashes, and Em Dashes","slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes"},"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\": \"Hyphens, En Dashes, and Em Dashes\",\n \"metaTitle\": \"Hyphens, En Dashes, and Em Dashes\",\n \"metaDescription\": \"Hyphens, En Dashes, and Em Dashes\"\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, \"Hyphens, en dashes, and em dashes all have their proper place in\\ntechnical writing, and should not be used interchangeably. Hyphens and\\nen dashes are the \\\"mechanics\\\" of punctuation and have clear-cut rules\\nfor their use. The em dash, on the other hand, is a stylistic choice\\nthat the writer chooses over other forms of punctuation to make a\\ndistinct point.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Hyphens:\"), \" Hyphens are used to connect and to separate textual\\nelements.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"It was a 2-year program.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Wright-Patterson Air Force Base, Ohio; Northrop-Grumman Corporation\"))), mdx(\"p\", null, \"As connectors, hyphens join the parts of compound modifiers.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The well-known author gave an interview.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The equipment emitted a high-frequency signal.\"))), mdx(\"p\", null, \"Hyphens separate numbers that are not inclusive (i.e., not within a\\nrange).\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"My phone number is 500-111-2222.\")), mdx(\"p\", null, \"The trend is moving toward using the hyphen less frequently.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Email versus e-mail\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Multifunctional versus multi-functional\"))), mdx(\"p\", null, \"Retain the hyphen if its absence makes a word or its meaning unclear.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Re-cover versus recover (to reapply a covering versus to come back\\nfrom; different meaning)\")), mdx(\"p\", null, \"Retain the hyphen when the prefix ends with the same letter with which\\nthe word begins.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Re-emerge versus reemerge; re-evaluate versus reevaluate (double-e\\ncan be confusing)\")), mdx(\"p\", null, \"Some program titles contain the hyphenated \\\"multi-\\\" as part of a program\\nor system title. In those cases, leave the hyphen in place.\"), mdx(\"p\", null, \"When one element of a compound modifier ends in \\\"ing\\\" or \\\"ed,\\\" use a\\nhyphen.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Fast-burning fuel; self-contained module\")), mdx(\"p\", null, \"When two or more related compounds have a common basic element, retain\\nthe hyphen with all parts.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"10- to 20-page report; long- and short-term memory\")), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"En Dashes:\"), \" En dashes connect numbers within a range (including\\nnumber ranges in tables) or take the place of the word \\\"to.\\\"\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The years 1995--1996 were interesting ones for most government\\nworkers.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The Las Vegas--Albuquerque flight departs in 1 hour.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The test team assessed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" 2.3--2.6.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Em Dashes:\"), \" \\\"Em dashes involve a choice writers and editors make when\\nother options might be commas, a colon, or a set of parentheses. The em\\ndash can be used singly or in pairs. Its most common purpose is to set\\noff an amplifying or explanatory element of the sentence. It is also\\nused to indicate a sudden break in thought or an interruption in\\ndialogue.\\\" ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Chicago Manual of Style, 16th Edition\"), \" , pages 333--336)\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"The weapon failed the test---the trigger jammed.\")), mdx(\"p\", null, \"Em dashes are also used to set off explanatory elements that already\\ncontain internal punctuation (i.e., commas).\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Boeing's system offers improvements---better navigation, streamlined\\nmaintenance, and greater reliability---that no other vendor can\\npromise.\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes.md"},"frontmatter":{"metaTitle":"Hyphens, En Dashes, and Em Dashes","metaDescription":"Hyphens, En Dashes, and Em Dashes"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"2a6f917f-5d78-5199-9a0f-e36a6fd0f8f2"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/3-8-Apostrophes/page-data.json b/sites/oteguide/page-data/editing_reports_guide/3-8-Apostrophes/page-data.json new file mode 100644 index 00000000..32ea5511 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/3-8-Apostrophes/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/3-8-Apostrophes","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"f3f9a75b-2de7-5791-8307-c5ac71391155","title":"Apostrophes","slug":"/editing_reports_guide/3-8-Apostrophes"},"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\": \"Apostrophes\",\n \"metaTitle\": \"Apostrophes\",\n \"metaDescription\": \"Apostrophes\"\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, \"Use apostrophes to show singular possessives (belonging to a single\\nentity) or plural possessives (belonging to one or more entities). Do\\nnot use apostrophes for a plural expression that is not used in the\\npossessive form.\"), mdx(\"p\", null, \"The word \\\"its\\\" means belonging to it and is never expressed as a\\npossessive. \\\"It's\\\" is a contraction that means \\\"it is\\\" or \\\"it has.\\\" If\\nyou cannot replace the word it's with it is or it has, do not use an\\napostrophe. The following table contains examples of when to, or not to\\nuse an apostrophe.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Apostrophe Not Required\"), mdx(\"th\", null, \"Apostrophe Required\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"The test teams\\u2019 wrote the report. (plural)\"), mdx(\"td\", null, \"AFOTEC published the test teams\\u2019 report. (plural possessive)\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"In the 1970s, Journey was a popular rock band. (plural)\"), mdx(\"td\", null, \"Journey was a popular 1970\\u2019s rock band. (possessive)\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Several MC-130s are parked on the flightline. (plural)\"), mdx(\"td\", null, \"Examine the MC-130\\u2019s payload. (possessive)\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"They examined its contents. (belonging to it, not a contraction)\"), mdx(\"td\", null, \"It\\u2019s a windy day. (contraction for it is)\")))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/3-8-Apostrophes.md"},"frontmatter":{"metaTitle":"Apostrophes","metaDescription":"Apostrophes"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"f3f9a75b-2de7-5791-8307-c5ac71391155"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/3-9-Choppy-Sentences/page-data.json b/sites/oteguide/page-data/editing_reports_guide/3-9-Choppy-Sentences/page-data.json new file mode 100644 index 00000000..a86140fd --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/3-9-Choppy-Sentences/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/3-9-Choppy-Sentences","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"50434fbc-f6f0-573c-b3f0-1b31759dd30f","title":"Choppy Sentences","slug":"/editing_reports_guide/3-9-Choppy-Sentences"},"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\": \"Choppy Sentences\",\n \"metaTitle\": \"Choppy Sentences\",\n \"metaDescription\": \"Choppy Sentences\"\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, \"Rewrite choppy sentences into ones that flow better by adding\\npunctuation and conjunctions, when appropriate. However, be careful not\\nto change the meaning or context when doing so.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Original\"), \" : The test team wrote the report. The report informed the 14\\nNovember 2014 full-rate production decision.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Edit\"), \" : The test team wrote the report, which informed the 14 November\\n2014 full-rate production decision.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/3-9-Choppy-Sentences.md"},"frontmatter":{"metaTitle":"Choppy Sentences","metaDescription":"Choppy Sentences"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"50434fbc-f6f0-573c-b3f0-1b31759dd30f"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/4-1-Numbers/page-data.json b/sites/oteguide/page-data/editing_reports_guide/4-1-Numbers/page-data.json new file mode 100644 index 00000000..70dea648 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/4-1-Numbers/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/4-1-Numbers","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"40ab4911-7e03-5201-97fb-97f999ad8bb5","title":"Numbers","slug":"/editing_reports_guide/4-1-Numbers"},"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\": \"Numbers\",\n \"metaTitle\": \"Numbers\",\n \"metaDescription\": \"Numbers\"\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, \"Express numbers referring to time, measurements, or money as figures\\n(e.g., 8 hours, 2 feet, 5 dollars). Use ordinal numbers when spelling\\nout a unit's name. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not use superscript for ordinals.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : 21st Space Wing (21 SW); subsequent use: 21 SW\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : 21st Space Wing (SW); 21st SW; 21 ^st^ SW; 21 ^st^\\nSpace Wing\"))), mdx(\"p\", null, \"Do not use an \\\"n\\\" or \\\"r\\\" for second and third ordinals\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : 43d Test Squadron; 302d Airlift Wing\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : 43rd Test Squadron; 302nd Airlift Wing\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/4-1-Numbers.md"},"frontmatter":{"metaTitle":"Numbers","metaDescription":"Numbers"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"40ab4911-7e03-5201-97fb-97f999ad8bb5"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/4-2-Dates/page-data.json b/sites/oteguide/page-data/editing_reports_guide/4-2-Dates/page-data.json new file mode 100644 index 00000000..67699e09 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/4-2-Dates/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/4-2-Dates","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"a7946a7d-04e8-5b68-83b3-ff48e9507f63","title":"Dates","slug":"/editing_reports_guide/4-2-Dates"},"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\": \"Dates\",\n \"metaTitle\": \"Dates\",\n \"metaDescription\": \"Dates\"\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, \"Write dates differently depending on the context in which you use them.\\nIn general, use the complete date format (full day, month and four-digit\\nyear). However, abbreviate dates in tables, figures, and document or\\npublication references. Do not mix complete and abbreviated date\\nformats.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : 20 Jul 04 or 20 July 2004\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : 20 Jul 2004 or 20 July 04\"))), mdx(\"p\", null, \"When the terms fiscal or calendar year are spelled out, the four-digit\\nyear should be used.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : fiscal year 2001; calendar year 2001\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : fiscal year 01; calendar year 01\"))), mdx(\"p\", null, \"When they are abbreviated, the year should also be abbreviated without a\\nspace between the term and the year.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : FY01; CY01\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fiscal Year\"\n }, \"FY\"), \" 01; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Calendar Year\"\n }, \"CY\"), \" 01\"))), mdx(\"p\", null, \"Use the words \\\"to\\\" or \\\"through\\\" instead of an en dash when dates are\\npreceded by words \\\"between\\\" or \\\"from.\\\"\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : from 15 through 30 July; between 15 to 30 July and 1 to\\n5 August; 15--30 July; 15--30 July and 1--5 August\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : from 15--30 July; between 15--30 July and 1--5 August\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"The only exceptions are tables and figures; always abbreviate dates\\nand use an en dash.\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/4-2-Dates.md"},"frontmatter":{"metaTitle":"Dates","metaDescription":"Dates"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"a7946a7d-04e8-5b68-83b3-ff48e9507f63"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/4-3-Abbreviations/page-data.json b/sites/oteguide/page-data/editing_reports_guide/4-3-Abbreviations/page-data.json new file mode 100644 index 00000000..9e01a509 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/4-3-Abbreviations/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/4-3-Abbreviations","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"b5d4b0d2-47eb-566e-802d-6fb2124b5e6e","title":"Abbreviations","slug":"/editing_reports_guide/4-3-Abbreviations"},"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\": \"Abbreviations\",\n \"metaTitle\": \"Abbreviations\",\n \"metaDescription\": \"Abbreviations\"\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, \"Common units of measure (e.g., ft, in, sec, nm) or common symbols (e.g.,\\npercent, degrees) are abbreviations, not acronyms. Spell them out or\\ndefine them the first time you use them. Do not add them to the acronym\\ntable.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/4-3-Abbreviations.md"},"frontmatter":{"metaTitle":"Abbreviations","metaDescription":"Abbreviations"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"b5d4b0d2-47eb-566e-802d-6fb2124b5e6e"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/4-4-Terms/page-data.json b/sites/oteguide/page-data/editing_reports_guide/4-4-Terms/page-data.json new file mode 100644 index 00000000..241bddc8 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/4-4-Terms/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/4-4-Terms","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"479feec5-3f51-5f83-a775-d0f432e1f7c2","title":"Terms","slug":"/editing_reports_guide/4-4-Terms"},"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\": \"Terms\",\n \"metaTitle\": \"Terms\",\n \"metaDescription\": \"Terms\"\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, \"Do not use terms \\\"i.e.,\\\" and \\\"e.g.,\\\" in conjunction with \\\"etc.\\\" and,\\nmost importantly, do not use them interchangeably. Always follow \\\"i.e.,\\\"\\nand \\\"e.g.,\\\" with a comma.\"), mdx(\"p\", null, \"The term \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\\"e.g.,\\\"\"), \" means \\\"for example.\\\" It is \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"not a finite list\"), \" ;\\nthere are more possibilities than the ones stated.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"They brought fruit (e.g., apples, oranges, bananas)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"They brought fruit (apples, oranges, bananas, etc.)\"))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"They brought fruit (e.g., apples, oranges, bananas, etc.)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"They brought fruit (e.g., the apples were crunchy)\"))), mdx(\"p\", null, \"The term \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\\"i.e.\\\"\"), \" means \\\"in other words\\\" and is used to add extra\\ninformation that clarifies. \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"It is finite; it is the only possibility\"), \"\\nthat could be listed.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The hurricane affected two of the Hawaiian islands (i.e., Oahu and\\nKauai) with winds over 130 mph.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Several personnel (i.e., active-duty and civilian) were promoted at\\nthe ceremony.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"He corrected the problem (i.e., tightened down the screw) and the\\nrattling stopped.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Four of the tech giants (i.e., Google, Amazon, Facebook, Apple)\\nhired promising new employees at the job fair.\"))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Several tech giants (i.e., Google, Facebook) hired promising new\\nemployees.\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/4-4-Terms.md"},"frontmatter":{"metaTitle":"Terms","metaDescription":"Terms"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"479feec5-3f51-5f83-a775-d0f432e1f7c2"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/4-5-Symbols-and-Units-of-Measure/page-data.json b/sites/oteguide/page-data/editing_reports_guide/4-5-Symbols-and-Units-of-Measure/page-data.json new file mode 100644 index 00000000..913e547c --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/4-5-Symbols-and-Units-of-Measure/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"e3086b00-3c65-5b0d-85c5-4557bd8ba509","title":"Symbols and Units of Measure","slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure"},"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\": \"Symbols and Units of Measure\",\n \"metaTitle\": \"Symbols and Units of Measure\",\n \"metaDescription\": \"Symbols and Units of Measure\"\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, \"Use symbols and abbreviated units of measure in appendices, figures, and\\ntables, but spell them out in the executive summary and body of the\\ndocument.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Executive Summary and Body\"), \" : percent, greater than, nautical mile\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Appendix, Figure, or Table\"), \" : %, \", \">\", \", nm\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/4-5-Symbols-and-Units-of-Measure.md"},"frontmatter":{"metaTitle":"Symbols and Units of Measure","metaDescription":"Symbols and Units of Measure"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"e3086b00-3c65-5b0d-85c5-4557bd8ba509"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/4-6-Verb-Tenses/page-data.json b/sites/oteguide/page-data/editing_reports_guide/4-6-Verb-Tenses/page-data.json new file mode 100644 index 00000000..baec89db --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/4-6-Verb-Tenses/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/4-6-Verb-Tenses","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"3a6d093d-2e79-534d-ba5f-fb56af4a29e8","title":"Verb Tenses","slug":"/editing_reports_guide/4-6-Verb-Tenses"},"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\": \"Verb Tenses\",\n \"metaTitle\": \"Verb Tenses\",\n \"metaDescription\": \"Verb Tenses\"\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, \"Be consistent in the use of verb tenses throughout the plan or report. A\\nplan describes how \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will execute a test and is written in future\\ntense. A report contains results, ratings, and operational impacts and\\nis written in past tense.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Plan\"), mdx(\"th\", null, \"Report\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Describes how AFOTEC will execute the test\"), mdx(\"td\", null, \"Contains results and ratings of the system under test, and the operational impact of those results and ratings\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Will happen, future tense\"), mdx(\"td\", null, \"Has happened, past tense\")))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/4-6-Verb-Tenses.md"},"frontmatter":{"metaTitle":"Verb Tenses","metaDescription":"Verb Tenses"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"3a6d093d-2e79-534d-ba5f-fb56af4a29e8"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/4-7-Embedded-Files/page-data.json b/sites/oteguide/page-data/editing_reports_guide/4-7-Embedded-Files/page-data.json new file mode 100644 index 00000000..ce9cccd1 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/4-7-Embedded-Files/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/4-7-Embedded-Files","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"3d8a3123-9059-51e3-b846-05c767974b8b","title":"Embedded Files","slug":"/editing_reports_guide/4-7-Embedded-Files"},"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\": \"Embedded Files\",\n \"metaTitle\": \"Embedded Files\",\n \"metaDescription\": \"Embedded Files\"\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, \"If the test teams follow the templates, you should not discover an\\nembedded file or link (PowerPoint, Excel spreadsheet, etc.) in the\\ndocument, because embedding documents into our plans or reports is not\\npermitted. However, if you discover such a file or link (i.e., a test\\nplan or report from another entity) within the document, you will have\\nto open and save it as a separate file, then forward it along with the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" document so it can be included as an attachment to the completed\\n.pdf file that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" publishes and distributes.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/4-7-Embedded-Files.md"},"frontmatter":{"metaTitle":"Embedded Files","metaDescription":"Embedded Files"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"3d8a3123-9059-51e3-b846-05c767974b8b"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/4-8-Converting-Pictures/page-data.json b/sites/oteguide/page-data/editing_reports_guide/4-8-Converting-Pictures/page-data.json new file mode 100644 index 00000000..32d3bc35 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/4-8-Converting-Pictures/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/4-8-Converting-Pictures","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"1e8cb746-0830-5b71-b058-5483eb643b3e","title":"Converting Pictures","slug":"/editing_reports_guide/4-8-Converting-Pictures"},"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\": \"Converting Pictures\",\n \"metaTitle\": \"Converting Pictures\",\n \"metaDescription\": \"Converting Pictures\"\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, \"Do not copy/paste a picture from another document; instead, save it as a\\n\\\".png\\\" or \\\".jpg\\\" file and insert it as a picture. Alternatively, use the\\n\\\"snip and sketch\\\" tool to save any image, table, text, equation, or\\nwhatever you want to capture from a page and change into a picture.\\nBefore \\\"capturing\\\" your image, unselect the \\\"show all formatting marks\\\"\\nso that you will not capture the marks with the picture. The \\\"snip and\\nsketch\\\" tool avoids the conversion process that makes pictures appear\\ngrainy.\"), mdx(\"p\", null, \"You can also transfer a pasted picture to PowerPoint (directions below)\\nto change it into a \\\".png\\\" or \\\".jpg\\\" file, then delete the original\\nimage and reinsert the picture you created.\"), mdx(\"p\", null, \"Procedures for converting a pasted picture into a .jpg or .png using\\nPowerPoint:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capture picture and all text blocks or other objects placed within\\nit or on top of it, and copy the group of images (Ctrl C)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Paste into PowerPoint (Ctrl V), the select all (Ctrl A) or \\\"group\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Right click, save as a picture (.png or .jpg)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Delete embedded object from document\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In its place, position cursor and insert picture from where you\\nsaved it\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Center picture, then add a 1-pt black border (some flow charts or\\nsimilar figures may be disrupted by a border and, therefore, are\\nexempt)\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/4-8-Converting-Pictures.md"},"frontmatter":{"metaTitle":"Converting Pictures","metaDescription":"Converting Pictures"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"1e8cb746-0830-5b71-b058-5483eb643b3e"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/4-9-References-and-Documentation/page-data.json b/sites/oteguide/page-data/editing_reports_guide/4-9-References-and-Documentation/page-data.json new file mode 100644 index 00000000..3983dff8 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/4-9-References-and-Documentation/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/4-9-References-and-Documentation","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"c814beeb-0792-59b6-813f-ae8025e0d9d4","title":"References and Documentation","slug":"/editing_reports_guide/4-9-References-and-Documentation"},"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\": \"References and Documentation\",\n \"metaTitle\": \"References and Documentation\",\n \"metaDescription\": \"References and Documentation\"\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, \"Cite references (documentation) correctly. A good authority is the Air\\nUniversity Press, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Air University Style and Author Guide\"), \" (Maxwell \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Base\"\n }, \"AFB\"), \"\\nAL, 2005), Part 1, Appendix B, Bibliographic Entries. You can access\\nthis publication on the Internet. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Suggestion\"), \" : print out or save the\\nappendix and have it available for reference when you are editing. In\\ngeneral, official publications with unlimited distribution (e.g., AFIs,\\ndirectives) are italicized:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 99-103, \", mdx(\"em\", {\n parentName: \"li\"\n }, \"Capabilities Based Test and Evaluation\"), \" , 16 Oct 13\")), mdx(\"p\", null, \"Reports and other publications with limited distribution (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nreports, threat documents) are enclosed in quotation marks:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Executive Order (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electro-Optical OR Executive Order OR Engineering Order\"\n }, \"EO\"), \") 13526, \\\"Classified National Security\\nInformation,\\\" 29 Dec 09\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\\"Defense Enterprise Accounting and Management System (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Enterprise Accounting and Management System\"\n }, \"DEAMS\"), \")\\n(Increment 1 Release 3) Initial Operational Test and Evaluation\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E) Plan,\\\" 4 Aug 14\"))), mdx(\"p\", null, \"Memos and standard forms (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Forces OR Standard Form\"\n }, \"SF\"), \") are cited without italics or quotes. For\\nmemos, state the entity who wrote the memo, the date, and the subject:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo, 1 Aug 14, Procedures for Operational Test and Evaluation\\nof Cybersecurity in Acquisition Programs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"SF298, Report Documentation Page\"))), mdx(\"p\", null, \"The table below contains examples of the correct way to cite different\\ntypes of reference documents. Use the long citation the first time the\\ndocument is referenced and the short version for subsequent citings.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Type\"), mdx(\"th\", null, \"First Use\"), mdx(\"th\", null, \"Subsequent Use\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"United States Code\"), mdx(\"td\", null, mdx(\"em\", null, \"Title 10, United States Code\"), \", Section\\xA02366\"), mdx(\"td\", null, \"10\\xA0USC\\xA0\\xA72366\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Executive Order\"), mdx(\"td\", null, \"EO\\xA013526, \\u201CClassified National Security Information,\\u201D 29\\xA0Dec\\xA009\"), mdx(\"td\", null, \"EO\\xA013526\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"DoD Directive\"), mdx(\"td\", null, \"DoDD\\xA08500.01,\", mdx(\"em\", null, \"Cybersecurity\"), \", 7 Mar 14\"), mdx(\"td\", null, \"DoDD\\xA08500.01\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"DoD Regulation\"), mdx(\"td\", null, \"DoD\\xA05400.7-R,\", mdx(\"em\", null, \"DoD Freedom of Information Act (FOIA) Program\"), \", Sep\\xA098\"), mdx(\"td\", null, \"DoD\\xA05400.7-R\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Chairman of the Joint Chiefs of Staff Instruction\"), mdx(\"td\", null, \"CJCSI\\xA06212.01E,\", mdx(\"em\", null, \"Interoperability and Supportability of Information Technology and National Security Systems,\"), \"15\\xA0Dec 08\"), mdx(\"td\", null, \"CJCSI\\xA06212.01E\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Air Force Handbook\"), mdx(\"td\", null, \"Air Force Handbook 33\\u2011337,\", mdx(\"em\", null, \"The Tongue and Quill\"), \", 27\\xA0May\\xA015 (Incorporating Change 1, 19 Nov 15)\"), mdx(\"td\", null, mdx(\"em\", null, \"Tongue and Quill\"), \"or AFH\\xA033\\u2011337\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Air Force Instruction\"), mdx(\"td\", null, \"AFI\\xA099\\u2011103,\", mdx(\"em\", null, \"Capabilities Based Test and Evaluation,\"), \"16\\xA0Oct\\xA013\"), mdx(\"td\", null, \"AFI\\xA099\\u2011103\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"AFOTEC Instruction\"), mdx(\"td\", null, \"AFOTECI\\xA099\\u2011101,\", mdx(\"em\", null, \"Conduct of Operational Test and Evaluation,\"), \"1\\xA0May\\xA007\"), mdx(\"td\", null, \"AFOTECI\\xA099\\u2011101\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"AFOTEC Manual\"), mdx(\"td\", null, \"AFOTECMAN\\xA099-101,\", mdx(\"em\", null, \"Operational Test Processes and Procedures\"), \", 11\\xA0Oct\\xA012\"), mdx(\"td\", null, \"AFOTECMAN\\xA099\\u2011101\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Military Standard\"), mdx(\"td\", null, \"MIL-STD-130N,\", mdx(\"em\", null, \"Identification Marking of U.S. Military Property,\"), \"16\\xA0Nov\\xA012 (with change 1)\"), mdx(\"td\", null, \"MIL\\u2011STD\\u2011130N\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Technical Order\"), mdx(\"td\", null, \"TO\\xA000\\u201135D\\u201154,\", mdx(\"em\", null, \"USAF Deficiency Reporting, Investigation, and Resolution,\"), \"1 Nov 11\"), mdx(\"td\", null, \"TO\\xA000\\u201135D\\u201154\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Concept of Operations\"), mdx(\"td\", null, \"\\u201CCombat Survivor Evader Locator (CSEL) Concept of Operations,\\u201D 4\\xA0Jul\\xA005\"), mdx(\"td\", null, \"CSEL\\xA0CONOPS\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"System Threat Assessment Report\"), mdx(\"td\", null, \"NASIC-1574-0210-03, \\u201CAutomated Information Systems Threat Environment Description,\\u201D Dec\\xA002\"), mdx(\"td\", null, \"AI\\xA0STAR\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Published AFOTEC document\"), mdx(\"td\", null, \"\\u201CDefense Enterprise Accounting and Management System (DEAMS) (Increment 1 Release 3) Initial Operational Test and Evaluation (IOT&E) Plan,\\u201D 4 Aug 14\"), mdx(\"td\", null, \"DEAMS IOT&E Plan or the IOT&E plan\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Official Memorandum\"), mdx(\"td\", null, \"DOT&E Memo, 1 Aug 14, Procedures for Operational Test and Evaluation of Cybersecurity in Acquisition Programs\"), mdx(\"td\", null, \"DOT&E Memo on Policy for OT&E of Cybersecurity\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Standard Form\"), mdx(\"td\", null, \"Standard Form 298, Report Documentation Page\"), mdx(\"td\", null, \"SF\\xA0298\")))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/4-9-References-and-Documentation.md"},"frontmatter":{"metaTitle":"References and Documentation","metaDescription":"References and Documentation"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"c814beeb-0792-59b6-813f-ae8025e0d9d4"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/5-1-Patches/page-data.json b/sites/oteguide/page-data/editing_reports_guide/5-1-Patches/page-data.json new file mode 100644 index 00000000..99a37067 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/5-1-Patches/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/5-1-Patches","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"af6684a0-95fe-5183-ac6d-9fe4baca91b1","title":"Patches","slug":"/editing_reports_guide/5-1-Patches"},"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\": \"Patches\",\n \"metaTitle\": \"Patches\",\n \"metaDescription\": \"Patches\"\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, \"Verify \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \" patches on multiservice operational test and evaluation\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \") plan or report cover pages are correct. Patches should be in\\nsame order of precedence as the signature page (Ref: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 36-2203),\\nwhich is army, marine corps, navy, air force, coast guard. However, when\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is the lead \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \", our patch and our Commander's signature will go\\nfirst, followed by the other services in the correct order of\\nprecedence.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/5-1-Patches.md"},"frontmatter":{"metaTitle":"Patches","metaDescription":"Patches"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"af6684a0-95fe-5183-ac6d-9fe4baca91b1"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/5-2-Classification-Markings/page-data.json b/sites/oteguide/page-data/editing_reports_guide/5-2-Classification-Markings/page-data.json new file mode 100644 index 00000000..8b7681df --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/5-2-Classification-Markings/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/5-2-Classification-Markings","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"c70f9491-bb5c-5d67-a39a-bdaea5ddd8c7","title":"Classification Markings","slug":"/editing_reports_guide/5-2-Classification-Markings"},"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\": \"Classification Markings\",\n \"metaTitle\": \"Classification Markings\",\n \"metaDescription\": \"Classification Markings\"\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, \"Ensure writers follow the guidance in DoDM 5200.01, V2, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Community\"\n }, \"IC\"), \" 4, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \"\\nInformation Security Program: Marking Information, 28 Jul 20\"), \" , and DoDI\\n5200.48, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Controlled Unclassified Information\"), \" , 6 Mar 20 when they\\napply required classification markings to classified documents. Perform\\nthe following actions:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Verify the correct distribution statement and derivative,\\ndeclassification, and destruction information were included on cover\\npage.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure the Controlled Unclassified Information (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Controlled Unclassified Information\"\n }, \"CUI\"), \") designation\\nblock is included on the lower right-hand side of the cover page, if\\nneeded\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure every page was marked with the highest overall classification\\nof the document.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Make sure every portion was marked with the applicable portion\\nmarking.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure portion marks were carried over (\\\"carry-over marks\\\") when a\\nparagraph broke and continued onto the following page; insert a\\nmanual line break (shift/enter) at end of the last sentence on the\\npage, then copy the carry-over mark (that applies to the broken\\nparagraph) onto the top of next page. This method helps locate\\ncarry-over marks to place them in the correct spot at the top of the\\npage when they shift to another part of the page due to additions\\nand/or deletions of information during rewrites/editing.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Find carry-over marks that might have moved to the middle of a page\\nor paragraph by using (ctrl F, special--manual line break). Move\\neach shifted carry-over mark by deleting the carry-over mark and its\\ncorresponding manual line break, and reapplying them to the top of\\nthe page where they belong.\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/5-2-Classification-Markings.md"},"frontmatter":{"metaTitle":"Classification Markings","metaDescription":"Classification Markings"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"c70f9491-bb5c-5d67-a39a-bdaea5ddd8c7"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/5-3-Distribution-List/page-data.json b/sites/oteguide/page-data/editing_reports_guide/5-3-Distribution-List/page-data.json new file mode 100644 index 00000000..cb96952e --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/5-3-Distribution-List/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/5-3-Distribution-List","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"45a75db1-2b55-5a34-9d4b-94eeb2390f65","title":"Distribution List","slug":"/editing_reports_guide/5-3-Distribution-List"},"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\": \"Distribution List\",\n \"metaTitle\": \"Distribution List\",\n \"metaDescription\": \"Distribution List\"\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 test team must compile a distribution list that contains members of\\nthe acquisition and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" community with an interest in their particular\\nprogram's test plan or report. Those contacts are usually listed in\\ntheir program's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" charter and/or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \". The template includes permanent\\nmembers who receive each document (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \", \", 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\"), \") and\\nsuggests other personnel the team should consider adding (in blue\\ninstructional text). The test team should also add whatever additional\\npersonnel they deem appropriate. The distribution list must contain\\npersonal email addresses, not workflows, for purposes of accountability.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/5-3-Distribution-List.md"},"frontmatter":{"metaTitle":"Distribution List","metaDescription":"Distribution List"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"45a75db1-2b55-5a34-9d4b-94eeb2390f65"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/5-4-SF298-Report-Documentation-Page/page-data.json b/sites/oteguide/page-data/editing_reports_guide/5-4-SF298-Report-Documentation-Page/page-data.json new file mode 100644 index 00000000..5f516843 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/5-4-SF298-Report-Documentation-Page/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"acecd159-40cd-5b8f-9a98-a31bf8908119","title":"SF298 Report Documentation Page","slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page"},"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\": \"SF298 Report Documentation Page\",\n \"metaTitle\": \"SF298 Report Documentation Page\",\n \"metaDescription\": \"SF298 Report Documentation Page\"\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\"), \" reports (not plans) must include an SF298 attached to the end of\\nthe document. Defense Technical Information Center (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Technical Information Center\"\n }, \"DTIC\"), \") uses this form\\nto archive official reports, as required. The SF298 should be maintained\\nat the unclassified level, if possible, so avoid details that would make\\nit classified. If not possible, ensure it is marked appropriately in the\\nheader and footer and wherever classification information is required.\"), mdx(\"p\", null, \"Ensure the test team completes the form, because it is often neglected\\nin the writing process. Complete the blocks with the following\\ninformation:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 1--Must match date on cover page; use format described (i.e.,\\n12082014, not 12\\xA0Aug\\xA014)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 2--Type of report\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 3--Dates covered are from beginning of testing period to date\\nof report; use format described (i.e., 09032014--12082014, not 9 Mar\\n14 - 12 Aug 14)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 4--Full title from cover page; should match exactly\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Blocks 5a--5f--Leave blank\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 6--Complete address of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachment that produced the\\nreport\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 7--\", 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\"), \" address (i.e., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", 1251 Wyoming Blvd \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \",\\nKirtland \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Base\"\n }, \"AFB\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network Management\"\n }, \"NM\"), \" 87117)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Blocks 8--11--Leave blank\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 12--Distribution statement must match cover page\\nexactly---copy and paste from cover page, then reapply \\\"SF298 text\\\"\\nstyle\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 13--If there is a classified annex or other supplemental\\ndocument for the report, add that information in this block---i.e.,\\nThis report is associated with \\\"Annex 1 to the Joint Air-to-Surface\\nStandoff Missile-Extended Range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Air-to-Surface Standoff Missile\"\n }, \"JASSM\"), \"\\u2011ER) Initial Operational Test\\nand Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E) Report,\\\" 8 Jan 13 (classified).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 14--Add a synopsis of the report---i.e., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" conducted an\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \" to assess \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Air-to-Surface Standoff Missile\"\n }, \"JASSM\"), \"\\u2011ER's progress toward operational effectiveness\\nand suitability in supporting the long-range, standoff precision\\nstrike mission. Additionally, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assessed the program's\\nreadiness for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. This \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \" report will inform the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \"(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L)'s\\n7\\xA0Dec\\xA010, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" C decision.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 15--Add the search engine terms a person would likely use on\\nthe Internet to find our report; this information will be added to\\nthe document properties in the published pdf\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 16--Verify that the security classifications for the following\\nare stated accurately:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"a\", \".\", \" Report--classification of report\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"b\", \".\", \" Abstract--classification of abstract (should be\\nunclassified, if possible)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"c\", \".\", \" This Page--classification of the SF298 front page (should be\\nunclassified, if possible)\")))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 17--Limitation of Abstract\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Unclassified abstract---should read UU (for unclassified,\\nunlimited distribution)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Secret abstract---should read S or same as report (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Report OR Special Access Required OR Synthetic Aperture Radar OR System Assessment Report\"\n }, \"SAR\"), \"); when it\\nis not possible to keep the abstract at the unclassified level\")))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 18--Enter total number of pages, minus the SF298 because it\\ndoes not count as part of the report\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 19a--Enter \", 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\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 19b--Enter \", 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\"), \" phone number: (505) 846-2484\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/5-4-SF298-Report-Documentation-Page.md"},"frontmatter":{"metaTitle":"SF298 Report Documentation Page","metaDescription":"SF298 Report Documentation Page"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"acecd159-40cd-5b8f-9a98-a31bf8908119"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/5-5-Spell-Check/page-data.json b/sites/oteguide/page-data/editing_reports_guide/5-5-Spell-Check/page-data.json new file mode 100644 index 00000000..1501a6a9 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/5-5-Spell-Check/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/5-5-Spell-Check","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"8aca0236-1b3f-5c4f-8411-3e0c64f97978","title":"Spell Check","slug":"/editing_reports_guide/5-5-Spell-Check"},"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\": \"Spell Check\",\n \"metaTitle\": \"Spell Check\",\n \"metaDescription\": \"Spell Check\"\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, \"ALWAYS run a final spell check before the final save at the end of the\\nediting process. It might seem obvious, but this step is often\\noverlooked.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/5-5-Spell-Check.md"},"frontmatter":{"metaTitle":"Spell Check","metaDescription":"Spell Check"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"8aca0236-1b3f-5c4f-8411-3e0c64f97978"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/5-6-Configuration-Control/page-data.json b/sites/oteguide/page-data/editing_reports_guide/5-6-Configuration-Control/page-data.json new file mode 100644 index 00000000..d9a7835a --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/5-6-Configuration-Control/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/5-6-Configuration-Control","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"f3ae0203-f03a-5d3e-a249-99a8211de5b4","title":"Configuration Control","slug":"/editing_reports_guide/5-6-Configuration-Control"},"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\": \"Configuration Control\",\n \"metaTitle\": \"Configuration Control\",\n \"metaDescription\": \"Configuration Control\"\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 hardest part of a technical editor's job is maintaining\\nconfiguration control. It is critical you maintain a constant line of\\ncommunication with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test team members to ensure their final edited\\nversion is the ONLY version to which changes are being made.\"), mdx(\"p\", null, \"After the 2-letter adjudication process, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" turns the document over\\nto \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \", via \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Collaborative Action Platform (ACAP), for command\\nsection coordination. At this point, configuration control of the\\ndocument converts from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" technical editor to the A-3 technical\\neditor. Detachment personnel should cease working on the document, and\\npass any additional changes they wish to make to their A-3 point of\\ncontact. If the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" continues to work on the document they submitted,\\nwhich is no longer the valid version, that work will likely have to be\\nreaccomplished or, worst case, will be omitted inadvertently. The\\ndocument will be reviewed by members of the command staff (including the\\nCommander, Executive Director, Vice Commander, and Technical Advisor)\\nwho will make comments and changes. The A-3 technical editor will\\nincorporate those changes into the configuration control version.\"), mdx(\"p\", null, \"Good communication is key to successful configuration control. Never\\nassume you have the correct version of a document unless the person with\\nwhom the control resides confirms that it is the latest version.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/5-6-Configuration-Control.md"},"frontmatter":{"metaTitle":"Configuration Control","metaDescription":"Configuration Control"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"f3ae0203-f03a-5d3e-a249-99a8211de5b4"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/5-7-Table-of-Contents/page-data.json b/sites/oteguide/page-data/editing_reports_guide/5-7-Table-of-Contents/page-data.json new file mode 100644 index 00000000..cc739fc6 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/5-7-Table-of-Contents/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/5-7-Table-of-Contents","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ff3a3b4b-5960-516a-823d-49a2354ae9d2","title":"Table of Contents","slug":"/editing_reports_guide/5-7-Table-of-Contents"},"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\": \"Table of Contents\",\n \"metaTitle\": \"Table of Contents\",\n \"metaDescription\": \"Table of Contents\"\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, \"Do not attempt to hand-jam changes to the table of contents (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"\n }, \"TOC\"), \"). It is\\ndesigned to work in tandem with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles---which is why it is\\nimportant to ensure the correct styles are applied---and will update\\nautomatically. To update the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"\n }, \"TOC\"), \", go to the References tab, select\\nUpdate Table, then select Update Entire Table.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/5-7-Table-of-Contents.md"},"frontmatter":{"metaTitle":"Table of Contents","metaDescription":"Table of Contents"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"ff3a3b4b-5960-516a-823d-49a2354ae9d2"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/5-8-Standardization-Checklist/page-data.json b/sites/oteguide/page-data/editing_reports_guide/5-8-Standardization-Checklist/page-data.json new file mode 100644 index 00000000..3c338cb3 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/5-8-Standardization-Checklist/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide/5-8-Standardization-Checklist","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"4deacdca-4d61-56bf-a7a0-4609de8cc7dd","title":"Standardization Checklist ","slug":"/editing_reports_guide/5-8-Standardization-Checklist"},"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\": \"Standardization Checklist \",\n \"metaTitle\": \"Standardization Checklist \",\n \"metaDescription\": \"Standardization Checklist \"\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 following checklist can be a handy guide when editing an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" plan\\nor report. Print it out to ensure you perform a thorough check of all\\nareas of emphasis.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC STANDARDIZATION CHECKLIST\"), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Were AFOTEC styles applied?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you perform an acronym scrub?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you replace \\u201Ccontinuous\\u201D page breaks with \\u201Cnext page\\u201D breaks?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you ensure the serial comma was used consistently throughout the document?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you verify headers and footers were standardized and contained correct classification, if necessary?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you check page numbering to ensure there were no disconnects?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Were blank pages added or deleted, as required?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you correct capitalization errors?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you verify military and Air Force Bases were cited correctly?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you examine vertical lists for correct structure and punctuation?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you confirm tables and figures were in sequential order?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you verify each table and figure followed AFOTEC standards?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you eliminate inappropriate passive voice?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you rewrite wordy and choppy sentences?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you ensure hyphens, en dashes, and em dashes were used correctly?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you correct apostrophes that were applied incorrectly?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you confirm number rules were followed?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Were dates written correctly, according to the context in which they were used?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you ensure only acceptable abbreviations were used?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you verify whether the terms i.e., e.g., and etc. were used correctly?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you ensure symbols and units of measure were spelled out in the executive summary and body?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you correct errors in verb tenses?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you eliminate embedded files?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you convert copy/pasted pictures into .jpg or .png files and reinsert them?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you verify documentation was cited correctly throughout the document?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you verify whether classification markings, portion markings, and carry-over marks were applied correctly?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you verify that the distribution list was compiled IAW template guidance, and includes all pertinent addressees?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you check the SF298 to ensure it was accurate and complete?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you perform a final spell check?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you update the table of contents?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"MAINTAIN CONFIGURATION CONTROL!\\xA0\"), \"Do not password protect documents in 2-letter and CS coordination. Do not continue to work the version of the document you have at the detachment while it is in 2-letter or CS coordination. Instead, contact your A-3 POC about changes that need to be incorporated.\"), mdx(\"td\", null)))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide/5-8-Standardization-Checklist.md"},"frontmatter":{"metaTitle":"Standardization Checklist ","metaDescription":"Standardization Checklist "}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"4deacdca-4d61-56bf-a7a0-4609de8cc7dd"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/editing_reports_guide/page-data.json b/sites/oteguide/page-data/editing_reports_guide/page-data.json new file mode 100644 index 00000000..cd502363 --- /dev/null +++ b/sites/oteguide/page-data/editing_reports_guide/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/editing_reports_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"d88d5eea-bb8c-5d50-906f-448e5ec86a1d","title":"Editing Guide","slug":"/editing_reports_guide"},"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\": \"Editing Guide\",\n \"metaTitle\": \"Editing Guide\",\n \"metaDescription\": \"Editing Guide\"\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(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\\"I cannot think of anybody who doesn't need an editor, even though\\nsome people claim they don't.\\\" \", \"~\", \" Toni Morrison\")), mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\\"Clever words are not as good as straight talk.\\\" \", \"~\", \" Chinese proverb\")), mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\\"Like stones, words are laborious and unforgiving, and the fitting of\\nthem together, like the fitting of stones, demands great patience and\\nstrength of purpose and particular skill.\\\" \", \"~\", \" Edmund Morrison\"))), mdx(\"p\", null, \"Last Updated/Reviewed: 08 December 2020\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-3\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"editing_reports_guide.md"},"frontmatter":{"metaTitle":"Editing Guide","metaDescription":"Editing Guide"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"d88d5eea-bb8c-5d50-906f-448e5ec86a1d"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/evaluation_and_reporting_guide/2-INTRODUCTION/page-data.json b/sites/oteguide/page-data/evaluation_and_reporting_guide/2-INTRODUCTION/page-data.json new file mode 100644 index 00000000..ba5d632f --- /dev/null +++ b/sites/oteguide/page-data/evaluation_and_reporting_guide/2-INTRODUCTION/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/evaluation_and_reporting_guide/2-INTRODUCTION","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"317e4c0d-8067-5de2-878a-fbe501ebeac3","title":"INTRODUCTION","slug":"/evaluation_and_reporting_guide/2-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\": \"INTRODUCTION\",\n \"metaDescription\": \"INTRODUCTION\"\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(\"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/15c01df8a9fa6f626567e43efe3eaffe/bd9eb/image2.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\": \"66.02316602316603%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAAD2klEQVQ4yyVSe0ybVRQ/Cm2ZLRXK+xl0CmSBbcaxbCYY/vGdJRoS56JIIkamCSGZSafGxzRRY2JiDGyEOZfojGN/kIGU50YfK6Xtvra0tP3ebb/2o3Qt26DFf5a2HG/lJufee849Off8zu8HHCvf4hhZkKQYTdMcEw5H6EwmE9re3jaTwMtut4ubnp4SDIZZ/p/pacEXDAhhihL85O4NBgWREwRRFFhJCscDgcAYuFxe2eMOoiyn0ONZR0naxJ2dNKbTO0n7quvtOxYfBgIMOhwe9K6tIyuI6LM7kZq/hT6GRj+3jrYVJy4tWtBits5BKpUUk8kkprbuZwMBMZdMPsju7mZwa2tLXlhwvD87yz2y2Xy55WVLzm535yiXN7dsdmTvWL1Zk2MlO2GfyM5MLj8au/g3TlyfmQeO42QCFUOhDaQoD/J8BBmGR5/Pv2UyUf2CwBCfQQILBZEn7yKyrB1d1CTa7RT6faRrliHGotPpNsLDhw+skUgkvrERj8hyMppIpCRZljfi8YRvfHzmiNu99s7S4u2PRn+9fmFs5MbXf1yd0s/N3xicmx35cGraOmAy3/1gack2YDbaz165bHgLGFqcX111CFarJWixrDBWq5UmRLChUNhz+vTFCoPhPiAikKUhVk1MUfARvynEFMTK9v30fl7AL0gU5ce1NT/6/TQGgzQKgkDIiWX1+t/r6+r41hMnJ2sqyzobNNDYfqjj0/LWtnO6np5rGpWqvRWg5thjr5qe+K3zzbZrz77WCIIY5cyWVTIzNhcKxfIrK1RuZmaeFOcyev14Y7Hiy+7XO1JK7dGy6obPD3edONxNmuqF/r526O2taPrqi9rnb35cBd/Vlh4a1BxshcTmPT4ixJDjxHw0eo8QEN6jaYGQJP07NDTeWIChI9BKn2qtKe1pJtXKNGptG4GKcOqUql5/XtEBcKYINLoigLNq4GSWv00bMcxv5BcWjYXO9sgnKMdiu9//8GeV/vw6VNQqSlTwRpMK3nuuBF6oAujRKpU/qgE+KQforypXf0bm+0sJwFgJiHKYt3EURsRo3mS2kflF9jZTKZQ3NzPWxb+0ALb6isqfKwFOFkipg8dHDxDIZUrlVXJWHCTNH4fiyyXD2hebwtU6NYHM8bJkIVCjefvqXQxyoT3J6UbZ7U6POF06rfrSS690MQcUzU/WlfcdOVYgcmj4Jzg3DNDd3dwwONDSaTijgkstLUdHq2qfgUQiwvsDRvR6mTzRHK4HuT3a7sA4TaevGI26gjaIHqCl72l19XB1175E3gWR1UBfHzRf+BaO/5+jhGKyF/0HzoBsKifzEJsAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image2\",\n \"title\": \"image2\",\n \"src\": \"/static/15c01df8a9fa6f626567e43efe3eaffe/e3189/image2.png\",\n \"srcSet\": [\"/static/15c01df8a9fa6f626567e43efe3eaffe/a2ead/image2.png 259w\", \"/static/15c01df8a9fa6f626567e43efe3eaffe/6b9fd/image2.png 518w\", \"/static/15c01df8a9fa6f626567e43efe3eaffe/e3189/image2.png 1035w\", \"/static/15c01df8a9fa6f626567e43efe3eaffe/bd9eb/image2.png 1442w\"],\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, \"This guide focuses on the analysis, evaluation, and reporting 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\"), \"&E activities. It covers the products and processes you must follow to\\ncomplete this final phase of test execution successfully. Submit\\nsuggested changes to: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".A3.Workflow\\\\@us.af.mil.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"evaluation_and_reporting_guide/2-INTRODUCTION.md"},"frontmatter":{"metaTitle":"INTRODUCTION","metaDescription":"INTRODUCTION"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"317e4c0d-8067-5de2-878a-fbe501ebeac3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE/page-data.json b/sites/oteguide/page-data/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE/page-data.json new file mode 100644 index 00000000..d3a936cd --- /dev/null +++ b/sites/oteguide/page-data/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"5cbdc691-9a66-5f3e-948b-aa90cd88b1af","title":"TEST ACTIVITY SEQUENCE","slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE"},"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 ACTIVITY SEQUENCE\",\n \"metaTitle\": \"TEST ACTIVITY SEQUENCE\",\n \"metaDescription\": \"TEST ACTIVITY SEQUENCE\"\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, \"During a test activity, you will carry out a sequence of five steps: \"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"determine what to test\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"design a test plan\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"execute the test and collect data\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"analyze and evaluate test results\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"report conclusions (Figure 1). \")), mdx(\"p\", null, \"The success of this activity depends largely on\\nthe robustness of the earlier steps to ensure an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" effort that is\\noperationally sufficient and technically adequate. This guide focuses on\\nthe analysis and evaluation of results and how to report test\\nconclusions.\"), mdx(\"p\", null, \"Figure 1. Test Activity 5-Step Sequence\"), 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/caf341903034649f50378463567c3773/248b0/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\": \"18.91891891891892%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAECAYAAACOXx+WAAAACXBIWXMAABcRAAAXEQHKJvM/AAABRUlEQVQY0w2LW0vCcBxA95n6AD2G98/gwF7rYfbaQwn7V5vOoTA1oqQyw6SyNK81yZbD3U2dc5axKLp8hl97OBw4cDA/o1ABRiGDrIZ8CQn5GRkFWRWFUjoKMBJa2aqjpQiLljdrtC+p0Z64RHvdx5uQKU9Cpv1J1e3qTohV0yFmsIqddC0q3xmTuZqKzoUFOuanKFdVUNZl323UhUjGLwcsWzWy6aaVSdUnmXhF55jbIZdqmNxuWcrQ1zpHV4zD7ZKyjolDG7TZB9zxfTDsTzCdPzDmX/CsmdASR1DmVRD0GRiWA8r4FTTzDYYzB6bvP2A5v9Dtq/AgyNAWVGiI4xHGS5NIT7PDpRqP39yLeP9lgXfEEd7TbVybf+NF3gjHDiprVKG9QRc7xN5pM0oeVaPpqyfi7HFKsKUuQRdarvloLF8P/gOgBdlcGChcdwAAAABJRU5ErkJggg==')\",\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/caf341903034649f50378463567c3773/e3189/image3.png\",\n \"srcSet\": [\"/static/caf341903034649f50378463567c3773/a2ead/image3.png 259w\", \"/static/caf341903034649f50378463567c3773/6b9fd/image3.png 518w\", \"/static/caf341903034649f50378463567c3773/e3189/image3.png 1035w\", \"/static/caf341903034649f50378463567c3773/248b0/image3.png 1316w\"],\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":{},"parent":{"__typename":"File","relativePath":"evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE.md"},"frontmatter":{"metaTitle":"TEST ACTIVITY SEQUENCE","metaDescription":"TEST ACTIVITY SEQUENCE"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"5cbdc691-9a66-5f3e-948b-aa90cd88b1af"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING/page-data.json b/sites/oteguide/page-data/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING/page-data.json new file mode 100644 index 00000000..8714c969 --- /dev/null +++ b/sites/oteguide/page-data/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"fcc75d8d-ffdd-522b-8c59-9cb674123119","title":"ANALYSIS, EVALUATION, AND REPORTING","slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING"},"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\": \"ANALYSIS, EVALUATION, AND REPORTING\",\n \"metaTitle\": \"ANALYSIS, EVALUATION, AND REPORTING\",\n \"metaDescription\": \"ANALYSIS, EVALUATION, AND REPORTING\"\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\"), \" produces a test report that provides results of its analysis and\\nevaluation of operational test data. Time constraints are a constant and\\ncompounding factor because \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E reports often inform a milestone or\\nfielding decision with a hard need-date. Test teams must analyze data,\\nevaluate impacts to the mission, draw conclusions, and draft and\\ncoordinate a test report as expeditiously as possible so the findings\\nare relevant and timely.\"), mdx(\"h1\", null, \"Analysis\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Analysis\"), \" is the detailed examination and application of disciplined\\ntechniques (e.g., mathematics, statistics) to understand or determine\\nessential features of complex problems. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" employs an\\noperations-based approach to analyzing system performance. Sound\\nanalysis produces technical adequacy and credibility. Test teams\\ntypically rely on measures of performance (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \") and measures of\\nsuitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \") to analyze \", mdx(\"em\", {\n parentName: \"p\"\n }, \"system\"), \" performance. Measures of\\neffectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \") are used to analyze \", mdx(\"em\", {\n parentName: \"p\"\n }, \"operational\"), \" performance. They\\nmay compare performance at the measures level against a criteria or\\nidentified standard threshold to determine whether there are shortfalls.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" operational evaluations are not based on findings attributed to\\noperational unit or operator performance shortfalls.\")), mdx(\"p\", null, \"Analysis provides the foundation or basis for evaluation. While we\\nseparate analysis and evaluation into different steps, there is no\\ndistinct \\\"line\\\" between them.\"), mdx(\"h1\", null, \"Evaluation\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Evaluation\"), \" is intended to be the judgment of a system's operational\\neffectiveness and suitability when exposed to representative threats\\nwhile being operated and maintained in a realistic operational\\nenvironment by typical operators and maintainers. Evaluations require\\noperational experience to apply judgment and place system performance in\\nthe context of intended operations.\"), mdx(\"p\", null, \"Operational evaluation determines the impact or significance of \", 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\"), \"\\nshortfalls by considering operational effects defined by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \".\\nSimilarly, the operational evaluation of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are in the context of the\\noperations defined by the critical operational issues (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"). After\\nevaluating COIs and measures, the test team has a basis for evaluating\\n(determining) a system's operational effectiveness and suitability.\"), mdx(\"h1\", null, \"Reporting\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Reporting\"), \" is dependent on numerous factors: the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activity, the\\ngoal of the activity, time constraints, and the status of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E (is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nongoing or complete). However, regardless of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activity or\\ndriving need, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will produce credible reports that are accurate,\\nbalanced, and timely.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Accurate\"), \": The test team analyzes and evaluates test data\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"meticulously to ensure the report's narrative and ratings are\\nconsistent and conclusions are defendable.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Balanced\"), \": The report's narrative highlights both system\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"capabilities and system limitations ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"what the system did well\\nand what it did not do so well\"), \" ) to enable mission effects.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Timely\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" delivers the report to decision makers to\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"allow them time to review and understand results prior to a\\ndecision date.\")))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#reporting","title":"Reporting"}]},"parent":{"__typename":"File","relativePath":"evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING.md"},"frontmatter":{"metaTitle":"ANALYSIS, EVALUATION, AND REPORTING","metaDescription":"ANALYSIS, EVALUATION, AND REPORTING"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"fcc75d8d-ffdd-522b-8c59-9cb674123119"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION/page-data.json b/sites/oteguide/page-data/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION/page-data.json new file mode 100644 index 00000000..024c5f28 --- /dev/null +++ b/sites/oteguide/page-data/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"f3bbd157-9ee2-5964-b348-97cfd54506b3","title":"STRUCTURE OF AN EVALUATION","slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION"},"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\": \"STRUCTURE OF AN EVALUATION\",\n \"metaTitle\": \"STRUCTURE OF AN EVALUATION\",\n \"metaDescription\": \"STRUCTURE OF AN EVALUATION\"\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\"), \" structures a test program to facilitate an evaluation of the\\noperational effectiveness and suitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \") of a system under test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"); therefore, all activities leading to analysis, evaluation, and\\nreporting support a determination of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \". Figure 2 illustrates how\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" structures an evaluation of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"Figure 2. Structure of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Evaluation\"), 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\": \"687px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/b39f3d34c537aa7abc9c5d3db3e3423e/aec65/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\": \"122.77992277992279%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAZCAYAAAAxFw7TAAAACXBIWXMAABcRAAAXEQHKJvM/AAAGk0lEQVQ4y2VV7U+b1xW/Wtt1UrdmkzKtc/JhXzZpmrR9XKutX7b/oNpWaQlpUrG0K8GggUloaBMwMhFRSXgxFBwbMOYlDjbB4Hcbv2HwKzZ+we9gg0ObB6K2qdSoXD/37Dzemg+bpZ/Oufc+Pvfc+zu/c0ksFjsJBoOQzWbZo0ePYH9/H/b29qCQz0OmVIIkIrW7C/FcDmLZLAQTCQhHo5BMRCCVCkMiEYStLT9Eo+tgNBqAuN3ubw0GA7NarbzdbudNJhO/5nLxuXSaD3AcP+Tz8bcePuRlS0t8j1bL37ZYeCOulwom3mjq543G27xO18s/eHCTV6tHeJLAHbe3twEzhUgkAkK2wVAIkvE4PETbee8edCHaBodA3N8PLZ98AnM6HUTCWpicug6Dg20gk30AAwNiGBm5Vc/w0Ov1HrlcLs7pdHI2m40zm83cysoKN6/VcpMaDaecnuakfSNPRsbGj4bkcm5CoeDGx+WcXH6H6+rqfdLf38fdutXLSaU9HGlsbBRdunRJdPHiRdGFCxdE58+fFzU0NIjOoW1+7z1Rx5Vm0c1rrT8//7eWX/zxjabf9XW3v3bu7++caWpq/Nnrv//nb95884NftbaKX7t8uQX/946InDlzhpw9e5acOnWK/O/vZcSvf0DIGz8l5Cfktzj6+FVCel/54Ut/IOT7vhfJ966dJuSX5PSLhJx+6WXy4x9hjFwuR/DeSLlcJgDwf/jmvxD8KgNhn1cF/ztbfAaECms8kGxpn5BQKKTAgKp4PK46ODioo1gsqgqFgiqXy6uS2aIqkSmqkrmyKpEt3QvFc2r1wvrC2npiLpbO4TijCsbSKn8opjJbrCqyvr4OFosFHA4HCIxjIKhgLe5X9mCnUAZl6Bu4bdyD3gcJkOl3QKZLQvf9+POxYPuWMjDk+QI0eiuQVCr1LBAI1Px+P0WmKfoUr4EWiwWayeapdTNNl11RqrdvUq15g47P2qliwUGn9Wt0ftVD1UtO9O10xuChc1odJaiKEzwmVCoVJiikhMp4+vQpVKtVYQ6q+2V4+uUTKOaL4LC5IRYNg83iAo/LDX6fB9wuJzjtVlwzw/37C/UMTzKZDMooxfDIDIucYYYMr4K51pzMabewcMDPvG4v0y8amMtpq9tVwwozG5eZ4aGeLS1qmf7BApuammQEM3l2eHjIY5YUUROAeq6lksma071RM2wd1WY9xdqsO1+b85RqSmuuNrYcr02sxmqT9h0cpxDpmsqRrw2NT9YINgXAewOfzwcbGxsgkCTIz+vxwuTMMgzb9uHGzCZ0KhzQpfLATU0ArirW4eqnduia8qE0XXAd5/uW89A7MAZkbGysbXR0tEMul0uGh4clg4ODkoGBgTpGR0ckUqlU0ivrk0h7ZR09Uml7Z+fHH/717asftbV/9OH1ruvtHVc7O9olHZLW1lZJW1ubhNy9e5fcuXOnDplMRjAAuXHjBunp6SbDw3fJ+01icuVf1xCd5P1mCdbzn1/4S8M/0P7phea2ZtLwbhM5d+kyeevtc+TdRpzf2dkhyWSSYGETZLeOI44jjx8/Jp9Xq+T4oEy++GyfpKPJ5+pxWAPPfactRIqotp1UhgQCQSK0ryvIbAu2LzGWjXh3d1eMLIsz2aw4k06LU/E4IiaOBMItFqP72vZWpDkcjrQEg+Fmg8HV4XD4Wrxev1iA2WwRE4EQLGjweDyAkqt3a6H+ymiLAlA1BRz7gklUThFS2LkTyW3s8AkstTh4vRuosCgiAjabBQgy+8xoNNaw/1GdTkfX1tZoaXeXFrNZmvjqK7pardKVUomu7FWo7bNDajw4pMl8lB4fOVFJelqpmBBGenzsoGbzAhWawwm2f0Aw1DRDCTI8LstioYePj9kc+lOhEJtPbrP7Oym2tFdh27kQO/nWhyLQsHB4kkWjavb11y62uqphJJ/Pnwhyw6bA0AckCZAkSOKzsL4VA2s4DMaNTVDqrDBrsoN6xQr6ZQOYTVpYWtKARjMJJtM8OJ1amJlRgsDwCcpO6DQMmcYXbAtfsChg5hDY3IQNLHiv213Xr9vpRbsGOgy+uuoAg8GGAXUwN7cAs7MLMDGh+I+W0+n084DfBdvEYD5UjRvJstntcHTEIVllyBfyUCwVkcA8HB5W8Ts/qFRKDDwDcvkIkOXl5RME6PV6tri4CFqtFubn53HHWVCr1TA1NQVKpRKmp9WgUChgfHwcM5kAVBeMjX2Kr94Q9ONrKKC7uxv+DboTg4Q7xsCdAAAAAElFTkSuQmCC')\",\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/b39f3d34c537aa7abc9c5d3db3e3423e/aec65/image4.png\",\n \"srcSet\": [\"/static/b39f3d34c537aa7abc9c5d3db3e3423e/a2ead/image4.png 259w\", \"/static/b39f3d34c537aa7abc9c5d3db3e3423e/6b9fd/image4.png 518w\", \"/static/b39f3d34c537aa7abc9c5d3db3e3423e/aec65/image4.png 687w\"],\n \"sizes\": \"(max-width: 687px) 100vw, 687px\",\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 test team composes COIs that ask whether a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can accomplish its\\ncritical mission elements or operational objectives. Then, they develop\\na variety of measures within each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" to evaluate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s mission\\neffects, capabilities, functions, properties, or structure. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"\\nevaluate performance-driven mission effects and MOPs/MOSs capture system\\ncapabilities and attributes.\"), mdx(\"h1\", null, \"Evaluation Structure\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E evaluation structure is a subset of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E construct. The\\nstructure uses the following elements to report results of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s\\nevaluation.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\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\"), \" ).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\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).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Critical Operational Issues\"), \" . A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" addresses a critical mission\\nelement or operational objective examined during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to determine\\nthe system's overall capability to support mission accomplishment\\n(often referred to as operations-based COIs).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\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(\"strong\", {\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(\"strong\", {\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(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Effectiveness\"), \". \\\"Are measures designed to\\ncorrespond to accomplishment of mission objectives and achievement\\nof desired results? They quantify the results to be obtained by a\\nsystem and may be expressed as probabilities that the system will\\nperform as required. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may be further decomposed into measures of\\nperformance and measures of suitability.\\\" ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition\\nGuidebook\"), \" ). \\\"A criterion used to assess changes in system\\nbehavior, capability, or operational environment that is tied to\\nmeasuring the attainment of an end state, achievement of an\\nobjective, or creation of an effect.\\\" (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \"\\xA01-02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Dictionary of\\nMilitary and Associated Terms\"), \" , \", mdx(\"em\", {\n parentName: \"p\"\n }, \"As Amended Through 15 Feb 16\"), \" ).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Performance\"), \". Measure of a system's performance\\nexpressed as speed, payload, range, time-on-station, frequency, or\\nother distinctly quantifiable performance features. Several MOPs\\nand/or MOSs may be related to the achievement of a particular \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \". (\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition Guidebook\"), \" )\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Suitability\"), \". Measure of an item's ability to be\\nsupported in its intended operational environment. MOSs typically\\nrelate to readiness or operational availability and, hence,\\nreliability, maintainability, and the item's support structure.\\nSeveral MOSs and/or MOPs may be related to the achievement of a\\nparticular measure of effectiveness or multiple measures of\\neffectiveness. ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition Guidebook\"), \" )\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data/Data Element\"), \". Data is any measurement or information\\nused to determine the value of a measure. Data may be quantitative\\nor qualitative, subjective or objective.\"))), mdx(\"p\", null, \"The evaluation summary chart (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \") is a concise presentation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nevaluation structure. It summarizes the mission statement, COIs, and\\nmeasures using colored indicators to rate each element. Figure 3 is a\\nrepresentative \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \".\"), mdx(\"p\", null, \"Figure 3. Example Evaluation Summary Chart\"), 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/1b4ce8b1d68a710375991db28f1461ba/b79a5/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\": \"66.40926640926641%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAADa0lEQVQ4y01TW0yTZxh+/79/qZS2trSF/gMqYLE6TKgXM1tiiNvlbrZdbInxyjthC/MYNGYoNKR4AKGiWbKYuMxM4+bGIRKo9IQwf4RysAJtKatQGFSk9AQoXnx+LyuJF0+e73/f733ew/f+AABGkQgMlIvMZtjV0SE7RAhAeXmFmNpAJuNYnQ5E9MiwLDDIaKcxjFYLnFhM7f/bmGKOw3tQjGIIjoNCnv8iD+BIkYg5qOcY+IjeU1NfFhXjqZ+nZ2RqBw3FDvwGjuFZ2PJlomAOhTJ9Ac/5O5WyUlaeVQqc3GQ6oDL9eCLzEwD2YwCuQCQS00AuT63J0Fy8yO7PzAQTjaE+2Nes13+GgphNT7ErQyLRUlYT2jMCK0D+/hj6FdLaWuDVakZWXQ18WRkof6oBg1YB8t1nCnnIA6m7sHg3BpVhBoVSlU1Zcqr22qf3nk5ZbL3Pbj7qGbplC8y2PLDfrqI+MZ3xXsqK6rOwJy8HsquqYK9Oxqr05/NLwSRV/lFQVIqC+ygKdPn6XKzml07Xtx2eILEHX5OBhXUiLL4lPZORtbYhv885E/cNzK9ND4TfTP6zsBG2+ZYfYCJ8IzovCTIKlmDLWj5fhy91/ffu79o8YdI9ufKudzq56Qytk/bR/8Z+cwUsf48sXW8fX2lsH1u+1uldtf7qDJwFTYUKCs+pQH2a4qQKBfdgldkajR4rvNP58Bvb6CARQr7N8cjs5vPlMOkPjM33DDscnjmv2xvxu8cXp9wvXgVcwsyIYBvp83vCEz5vZNr3fCngQ0EjtmwwaHE9oKf7h6OzL80kunKFJOKNJJVsJAvzFvJvyEKi0WYSj1tJLNZCEokbJBK5SkIzNclY1JJMxi8nE7GGJGrgoEuMxlwZVtjVVXU4GKzvX11tdqRSrc6NjZvOcLjBFZw2OxKJFvva2g17KmXt3Vi3uuYWWv986H5c6fA+qxRCk1tAQUN6bXZKpRkKyjgHjoJND5lJL6w4bUNwmNx62/L50NRfZGKuiwSWHm9h+5WN6cXmsrK2RCXbgWmWfiAoqawol6Ng/5MTX9KWSSzaQN69bSKbb5rI9q+nZximKL3kuXftw6fv94233nWONbU99TQNC+aWEaGmcXTw0s9C34Wv6J0MCnlt3dclwuCFihcTdcf9/vrjPor3TFd2XpKBTy4AAAAASUVORK5CYII=')\",\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/1b4ce8b1d68a710375991db28f1461ba/e3189/image5.png\",\n \"srcSet\": [\"/static/1b4ce8b1d68a710375991db28f1461ba/a2ead/image5.png 259w\", \"/static/1b4ce8b1d68a710375991db28f1461ba/6b9fd/image5.png 518w\", \"/static/1b4ce8b1d68a710375991db28f1461ba/e3189/image5.png 1035w\", \"/static/1b4ce8b1d68a710375991db28f1461ba/b79a5/image5.png 1372w\"],\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, mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \" : Operational capabilities (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Capability\"\n }, \"OC\"), \") are depicted for context, but are\\nNOT rated or assigned colored indicators.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#evaluation-structure","title":"Evaluation Structure"}]},"parent":{"__typename":"File","relativePath":"evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION.md"},"frontmatter":{"metaTitle":"STRUCTURE OF AN EVALUATION","metaDescription":"STRUCTURE OF AN EVALUATION"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"f3bbd157-9ee2-5964-b348-97cfd54506b3"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/evaluation_and_reporting_guide/page-data.json b/sites/oteguide/page-data/evaluation_and_reporting_guide/page-data.json new file mode 100644 index 00000000..1c3ff754 --- /dev/null +++ b/sites/oteguide/page-data/evaluation_and_reporting_guide/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/evaluation_and_reporting_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"02656e14-526d-59e4-8901-f02635b64338","title":"Evaluation and Reporting Guide","slug":"/evaluation_and_reporting_guide"},"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\": \"Evaluation and Reporting Guide\",\n \"metaTitle\": \"Evaluation and Reporting Guide\",\n \"metaDescription\": \"Evaluation and Reporting Guide\"\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\": \"Office of Primary Responsibility\"\n }, \"OPR\"), \" is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Collateral Responsibility OR Operational Capability Requirement\"\n }, \"OCR\"), \" is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-2/9\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"evaluation_and_reporting_guide.md"},"frontmatter":{"metaTitle":"Evaluation and Reporting Guide","metaDescription":"Evaluation and Reporting Guide"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"02656e14-526d-59e4-8901-f02635b64338"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/fn_guides/OTE_construct_development_guide/page-data.json b/sites/oteguide/page-data/fn_guides/OTE_construct_development_guide/page-data.json deleted file mode 100644 index cf88c596..00000000 --- a/sites/oteguide/page-data/fn_guides/OTE_construct_development_guide/page-data.json +++ /dev/null @@ -1 +0,0 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides/OTE_construct_development_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"6133484f-bd7c-5686-9d20-576e0aa03f74","title":"OT&E Test Construct Development Guide","slug":"/fn_guides/OTE_construct_development_guide"},"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 Construct Development Guide\",\n \"metaTitle\": \"OT&E Test Construct Development Guide\",\n \"metaDescription\": \"OT&E Test Construct Development Guide\"\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, \"11 February 2021\"), mdx(\"span\", {\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/d1cb86a64fbd92e448b7cbc0614256b0/45662/image2.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\": \"64.86486486486486%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAADpElEQVQ4y2VSb2gbZRz+tas4xCFCoeyDMoYgq2IV+0FhOsF/c+KHiYwiggiK84PgYMo+jVpGECluFeYmbszixnCVujFTR2vNTLM0ySW5yyWX3OVy/3LJXXJ3SS6Xu6RJm72+KXNf/PDwvC937/O+z/P8wHE7qCBXUZQSkFKyUMNuoWPTl/YBwEMzc9dfiaVEg2QUK5GWDAwzkZbNOGYiJeqyam4VpNLn7U4XbKe9Y//BjwD0ai2aYZVYJJlPYI6r5Upo9oeF3QghkNXKrjgtmlRWQaygobxUQZygI7agoVxBu6sbNpKK+pXBvxhDCzdWAe5t8IPggf/Wx32/wmpE2l5HSSFAZYvbYmLRxDCQpJpIKVuobntI1UwWYHT48AfHgUzzABXTedNquAdDcX7KdjpvadXGawj1RwY3BNYZiCR5XzjBIQwrRLD2AESqYGfzakOv1l21bJTmzl8Zm796ExZvrg6B02qjJka5Uke24+EMHXT0xLknAV56BGsOLfgjRylG5rH1eCItkmKxSqqaRWqVerJq2phryb+C8eeCYQrWIqlhkIvatKLqMwSV/0aUyzOSUjp57Ov5x/YeOLF3YDlEcG/jMrq4BDdBi24yI3mpnOIVy5bXsF2nYjRQgmKn4hQLiRS3YxA8eJ67nVfFqIOq1Z/Hh0rrSd5kOGXlK9/lSWw3TFCFeIzkiTsESwSjWYLMSAR+XbiEM0wxhc/sVhda7a3hgdCDDFfcefjTuTFvoz+SYvjHA6HkO8uB2Ks3lm5Pwu53d+KRyiczMkqzqoNLaWHbrZJea7e8zqbX6SLs8Ld7hY78r+XNzR7QGRZ6W2ifbroTZt19MRSl35j78drTwXX6CEHmprC194Pr5KFT354dG93zwq7BWdfbgN5mH6DR9H7G8zSfyqkLVcv5pdZwzn1/8Y8nsJVYghYK6ZwiSIr25+XfQy8XyyYlFSsUZi5J8z+dvnjr0f5d9HG705ttuR1ft9d/Hbz2BjJrze3BNawmajotNHt+cbxq2adwq2cZTj3D8sqXZy74nxJk3RenhdOcoF3Agp+ksvKHZs1BvKQjQakOJqQC/uXQMyuB9Qn/8toE5meXlv8Z/2L60mjVqC9GyfxKji+x+MI+K+hLhuWgYISJ0FnpNsOK3w0iohl+XJTV97Js4dDVa9fHIBShIBqnIRhOYk7DWjgBWPB+tsFIeg8eYDbDFXH42p3JA0cedjro/ncsDJJSBo6XwH/rb/gXpYD4s61ku5YAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image2\",\n \"title\": \"image2\",\n \"src\": \"/static/d1cb86a64fbd92e448b7cbc0614256b0/e3189/image2.png\",\n \"srcSet\": [\"/static/d1cb86a64fbd92e448b7cbc0614256b0/a2ead/image2.png 259w\", \"/static/d1cb86a64fbd92e448b7cbc0614256b0/6b9fd/image2.png 518w\", \"/static/d1cb86a64fbd92e448b7cbc0614256b0/e3189/image2.png 1035w\", \"/static/d1cb86a64fbd92e448b7cbc0614256b0/45662/image2.png 1410w\"],\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, \"Last Updated: 26 February 2021\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Primary Responsibility\"\n }, \"OPR\"), \" is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-3 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Collateral Responsibility OR Operational Capability Requirement\"\n }, \"OCR\"), \" is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9\"), mdx(\"h1\", null, \"INTRODUCTION\"), mdx(\"p\", null, \"This document contains information pertaining to the first two steps of\\nfive major steps that define the overarching \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E test activity.\\nAlthough the five major steps of a generic test activity can be applied\\nto various level of test (e.g., testing system functions, components,\\nsub-systems, and capabilities), this guide focuses on developing the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct to capture mission effects and the subsequent,\\noverarching test activity.\"), mdx(\"p\", null, \"The first step is \\u201Cdefining the what;\\u201D in the context of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct, this is commonly described as battlespace development. It\\nanswers the following questions: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"What\"), \" are the operations under test;\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"what\"), \" is the intended use of the system(s) in the operation; \", mdx(\"em\", {\n parentName: \"p\"\n }, \"what\"), \" are\\nthe operational conditions they will be employed/supported under\\n(operations and conditions); and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"what\"), \" do you need to measure to\\ndetermine combat capability or mission effects. Battlespace development\\nprovides a strong operations-based foundation to build upon during test\\ndesign and when executing and reporting operational test.\"), mdx(\"p\", null, \"This guide also addresses the second of the five major steps, test\\ndesign. Test design determines the goals of the test and how to achieve\\nthem. This includes considerations of creating an operationally\\nrealistic environment, executing representative scenarios, and the means\\nto collect the resulting data.\"), mdx(\"p\", null, \"When answering these questions with discipline, the output is a strong\\nfoundation for operationally sufficient and technically adequate\\noperational test and evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E).\"), mdx(\"p\", null, \"Submit suggested changes to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Direct Reporting Unit\"\n }, \"DRU\"), \" A-3E Workflow at\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:AFOTEC.A3E.Workflow@us.af.mil\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".A3E.Workflow@us.af.mil\")), mdx(\"h1\", null, \"The Operational Test and Evaluation Construct\"), 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 one another:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Effectiveness:\\xA0\\xA0\"), \"Measure of the *overall capability\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"to accomplish a mission\", mdx(\"em\", {\n parentName: \"p\"\n }, \" when used by representative personnel in\\nthe environment planned or expected for operational employment of\\nthe system considering organization, doctrine, supportability,\\nsurvivability, vulnerability and threat. (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\xA099\\u2011103,\\n\"), \"Capability\\u2011Based Test and Evaluation*, 6\\xA0Apr\\xA017)\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Suitability:\"), \"\\xA0\\xA0The *degree to which a system can be\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"placed satisfactorily in field use\", mdx(\"em\", {\n parentName: \"p\"\n }, \" with consideration given to\\navailability, compatibility, transportability, interoperability,\\nreliability, wartime usage rates, maintainability, safety, human\\nfactors, manpower supportability, logistics supportability,\\nnatural environmental effects and impacts, documentation and\\ntraining requirements. (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 99-103, \"), \"Capabilities-Based Test and\\nEvaluation*, 6\\xA0Apr\\xA017)\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission Statement:\"), \" Mission statements are written at a high,\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"overarching level consistent with the mission the system is\\nintended to support or enable.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Critical Operational Issues (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"):\"), \" A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" addresses a *critical\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"mission element or operational objective* examined during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to\\ndetermine the system\\u2019s 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(\"strong\", {\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.\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"Operations describe \", mdx(\"em\", {\n parentName: \"p\"\n }, \"the actions, activities, or phases of a\\nmission\"), \" needed to accomplish the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". With two or more\\noperations, the overarching operational objective is the same;\\nhowever, the steps and/or conditions to achieve the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" are\\ndifferent between operations.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission Effects:\"), \" Mission effects are \", mdx(\"em\", {\n parentName: \"p\"\n }, \"outcomes or results\"), \" of\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"conducting an operation.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Capabilities:\"), \" OCs provide operational context for\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"system capabilities or attributes of high interest or importance\"), \"\\nwithin an operation. It may be useful to distinguish between\\nsystem capabilities (i.e., the potential to perform some action)\\nand system attributes (i.e., the functions, properties, structure)\\nof a system. Operational capabilities provide the means to conduct\\nan operation and achieve effects.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational (User) Requirements:\"), \" A *system capability,\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"attribute, or characteristic required to accomplish approved\\ncapability needs*. Operational requirements (including\\nsuitability) are typically performance attributes, but they may\\nalso be derived from cost and schedule (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-601). Typically\\nreferred to as \\u201Crequirements.\\u201D\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Conditions:\"), \" Operational conditions are identified\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or operation and depict the operational battlespace.\\nAn operational condition is defined by \", mdx(\"em\", {\n parentName: \"p\"\n }, \"a set of factors, each set\\nat a given level\"), \". A factor is a variable of the environment that\\nmay affect task performance. A level is a set value within the\\nrange of values a factor can hold.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures:\"), \" Measures are designed to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"convey information\"), \" about a\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"system\\u2019s effect, capabilities, functions, properties, or structure\\nbeing addressed.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data/Data Element:\"), \" Data is *any measurement or information used\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"to determine 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(\"strong\", {\n parentName: \"p\"\n }, \"Test Design:\"), \" The test design is a \", mdx(\"em\", {\n parentName: \"p\"\n }, \"set of test events\"), \" for each\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"operation and battlespace condition, including \", mdx(\"em\", {\n parentName: \"p\"\n }, \"the rationale for\\nselecting the test events\"), \".\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Event:\"), \" A test event is a *single execution of an operation\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"or sequence/set of operations* under specified conditions for the\\noperations.\")))), mdx(\"p\", null, \"This guide provides methods to develop these elements of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct for the overarching goal of determining effectiveness and\\nsuitability.\"), mdx(\"h1\", null, \"Operational Sufficiency and Technical Adequacy\"), mdx(\"p\", null, \"Operational sufficiency and technical adequacy are two basic \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntenets leading to an adequate and credible test.\"), mdx(\"p\", null, \"Operational Sufficiency addresses the breadth of the operations and\\nconditions addressed while employing new or modified capabilities within\\nthe context of representative employment and support concepts. An\\noperational test and evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) is considered operationally\\nsufficient if it provides the decision maker and the warfighter with\\nresults from test events executed across sufficient operations and\\nconditions to identify the capabilities and limitations associated with\\nemployment and support, and enables an effectiveness and suitability\\ndetermination.\"), mdx(\"p\", null, \"Ensuring operational sufficiency requires a thorough understanding and\\nidentification of the operational employment and support environment and\\nconditions, to include operational threats. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" core teams address\\noperational sufficiency while designing test events to ensure\\ncapabilities and concepts are adequately addressed within the\\noperational evaluation. Core teams are one tool to address operational\\nsufficiency by using operational perspective, experience, and judgment\\nto ensure test events are evaluated within the context of envisioned\\noperations and support. This allows \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" to characterize systems\\u2019\\ncapabilities and mission effects.\"), mdx(\"p\", null, \"Technical Adequacy addresses the relevance of the technical information\\nproduced by the test in relation to the purpose of the test (i.e., test\\nevents address operationally relevant questions). This includes test\\ndesign, test measures, relevant threat environments, data collection\\nmethods, scoring, analysis, modeling and simulation, and test capability\\naccreditation. A test is technically adequate if the test data\\nevaluation provides the acquisition decision maker information to inform\\nthe relevant decision.\"), mdx(\"h1\", null, \"Operational Test and Evaluation Test Activity Cycles\"), mdx(\"p\", null, \"A general test activity is the sequence of determining what to test, how\\nto test, executing the test and collecting data, analyzing the results,\\nand reporting the conclusions (see figure 1). The success of this\\nactivity depends largely on an initial understanding of the battlespace,\\nthe capabilities under test, and how the capabilities fit within the\\nbattlespace. All subsequent activities build on a test team\\u2019s basic\\nunderstanding of the expected capabilities under test, in what\\noperational conditions the capabilities will be employed and supported,\\nand what needs to be measured. This is called \\u201CDefining the What.\\u201D Using\\nmore operational terminology, this effort is commonly referred to as\\nbattlespace development and should be the first step for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct test activity.\"), mdx(\"p\", null, \"Figure 1. Steps in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct Test Activity\"), mdx(\"undefined\", null, mdx(\"span\", {\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/0af8f41b7293a3dced7f85fd09684cbb/6c2de/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\": \"21.235521235521233%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAECAYAAACOXx+WAAAACXBIWXMAABcRAAAXEQHKJvM/AAABLElEQVQY0z3MyU7CQAAG4D6SRE2fwnj1oIA+hicfQhMRCCV4MCbGQ1VcgNGiLGMXusyUmVIpSylxARu5jyMHD9/h/5P/F1InHSmZNblO6c92Ri+l82YplTOL6bwt7Rzr0ubBhbSxfyrt8rxXQFI6Z/1L8S1XTGaMwtYhvBTaJMQ3dRXLoEUUg1IUxlTvTahGQ1f1Jrgb/WASxhjiAeKcNgocPJw57vh7CQ2+HDv4tHnnQu+9IihOnz00LQYgYopOGBrFzOhNGXSHrMVZwznDoznTvYipZLzs+QF77njsSeuyhvXG+UsajWKh/EoSR+fyav6qJmbliihrRKz7U7HR/1iHwSwBdH+l3ERr5mB+1o0W9UeN1O4aFqhCF9w3bXCtaOD2xQQqjYA7WVR/Afny8o7kNCZ6AAAAAElFTkSuQmCC')\",\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/0af8f41b7293a3dced7f85fd09684cbb/e3189/image3.png\",\n \"srcSet\": [\"/static/0af8f41b7293a3dced7f85fd09684cbb/a2ead/image3.png 259w\", \"/static/0af8f41b7293a3dced7f85fd09684cbb/6b9fd/image3.png 518w\", \"/static/0af8f41b7293a3dced7f85fd09684cbb/e3189/image3.png 1035w\", \"/static/0af8f41b7293a3dced7f85fd09684cbb/6c2de/image3.png 1334w\"],\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 \"), \"Developing\\na battlespace is the first of five major steps in the AFOTEC OT&E\\nConstruct and is accomplished in conjunction with Test Design (discussed\\nin this guide with more detail in the Analyst Test Design Guide). This\\nstep frames the OT&E by answering four fundamental questions. *What* are\\nthe capabilities under test; *what* is the intended use of the\\ncapabilities; in *what* operational conditions will the capabilities be\\nemployed/supported (operations and conditions); and *what* do you need\\nto measure to determine combat capability?\"), mdx(\"p\", null, \"Test teams have latitude in how they develop the battlespace. However,\\nthis guide presents a long-standing and proven approach test teams\\nshould consider before proceeding with test design. It is systematic and\\ncan quickly take test teams from limited operational understanding to\\ncredible \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Constructs. This \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" default approach to battlespace\\ndevelopment will provide a sound foundation for the second step, Test\\nDesign. Figure 2 generalizes this approach. Although depicted as a\\nsequence of steps, the process is iterative and adaptive.\"), mdx(\"p\", null, \"Figure 2. Battlespace Development Within the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct\"), mdx(\"span\", {\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/3712e01ffbfebd9b130c15c6a7fd1b5c/73a2e/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\": \"64.09266409266408%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAADuElEQVQ4y1VSXWgcVRQ+6Z8SbW2rQvSlDyKWlkgVRU01UEQo+JCWIhGlWixoqaASFAvWx/RBxb9YKk0aW1FDINqqSWx22WQ3mf2Z2d2ZnZmdmd3Z2d3Zndn//9ndye4mcr0TqeDDxznn3nO+c+53LrTN7o+ikun9tcrlvaxSzJYqxvU/HCMAcN+pj756ct7FeFcoMe4KSJElNx91+IQojvllUgha5wQtXEQIwQc3JnfufvcVADWXv06xscafjqDuIHgtpeXLpD98zEoCGN3ucIv0KhlFJBNHAS6JvLSyBStmwikkyOkVK/flq5fuuvvcyV0Azxzux5V9sP/k/odhYJvlkzgBJ21bWGHBvhaevu3iUIBP/i3IGSQpWcRJ2pZNpEsok6ukJ6dv7dtwV+ChsdP94AyJj1Kx2HPTv7uO++X408sMf8ROB+7FxLA4zwMRiJ51eASEUcdoLnsxPILBCGpdUPSGli8Zv9y2DVpTvnNtYgd0uhv23sYmypcaqNpoo7a5jmYWXa9aGgLcs+fTidkRJxlWbUSIt7tZkWRlkZfVsBTXGCmWDsaSGcnmpIaXfAFAlc0+0LLFc7lC+QYvqVNYvyt6tnDNvuI/BDD8gNXV6YkcCkf1CiulTSGqNwVZb0Xj2VauWGu3zY7RbK2jsJR4T88UQU5o2y2t4N8FwE7LTv08v5eT0j53QE5EFJ344vtbQ0uu0M01UmRWSZFcdvOUbZWl3H6JiqtZN4ZIc/InGiZMZ4pbhBbRrtNjkwOW3+l0H3R62Dfn7eRrToI+hRvtwBt1hMQUCke1biJd7KlaqafnKptGy0TrnS7K5ssea5m4/n8T9t3xWUGx7O5IsjoQSZYOkLT04oKNGCJI7gQbjo1ygjJKs5ETDqf38dnfFh+59Pnl+3ubCBpNE6DWaJ+tG+YV/CWuFsrGN3WjPTG34D5cKNVnY8lcDmumFEo1//Ts8gvZQs2eL9aEYrkhxtXczaeOj+3BjV9qmd2Pjeb6BXO9dxRMs+NoGG38QXWk6iXUbLaRzRkcEWXtbZpXpihG/hqLPj7+7dwgJyYvYu0maD4+haf+0L7KjlTrLYQbY+RRuVIvAOELHfTT4WEnERzyBfijVJB7/sz7X+7LFaqXOUn1BViFqdabPbyoX/EL2j5alvwhhYgl9J+eOPZWfyqdHdT0/BvJlP76mpt8DAIhCXgxBh6KA4aPAstH4LPvZv7T9sL4D3srNYNJaCWkZ4vVmbnFg3fuDjx7HhKqDlomD5gQfBQN/wA4Gt/Lr1Q70gAAAABJRU5ErkJggg==')\",\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/3712e01ffbfebd9b130c15c6a7fd1b5c/e3189/image4.png\",\n \"srcSet\": [\"/static/3712e01ffbfebd9b130c15c6a7fd1b5c/a2ead/image4.png 259w\", \"/static/3712e01ffbfebd9b130c15c6a7fd1b5c/6b9fd/image4.png 518w\", \"/static/3712e01ffbfebd9b130c15c6a7fd1b5c/e3189/image4.png 1035w\", \"/static/3712e01ffbfebd9b130c15c6a7fd1b5c/73a2e/image4.png 1439w\"],\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, \"Battlespace development provides the foundation for operationally\\nsufficient and technically adequate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E by ensuring operations-based\\ntest designs. It supports the later application of scientific methods of\\ntesting needed to design and analyze tests across the operational\\nbattlespace to ensure credibility. A key element of the scientific\\nmethod of operational test is mission thread analysis, which includes\\nidentifying the operational conditions and considering test constraints,\\nthereby leading to a set of high-return test events. These events will\\nlead to a defensible basis for resource estimations (test articles,\\npersonnel, etc.) early in an acquisition and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E lifecycle. It also\\naids the development of test execution methodologies (field test,\\nmodeling and simulation, hybrid), identifying test capability\\nrequirements and shortfalls, and refining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities and schedule\\n(Integrated Test & Evaluation).\"), mdx(\"h1\", null, \"Using a Core Team Approach.\"), mdx(\"p\", null, \"The core team is an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-led working group established to support\\nprogram test activities. Examples include battlespace development, test\\ndesign, measures workshops, and technical reviews. The core team is\\ncomposed of all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" stakeholders (Test Team, Detachment and\\nHeadquarters staff). The core team is led by the responsible test\\ndirector (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"). It includes any \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachment subject matter\\nexpertise (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \") the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" believes is needed (e.g., logistics and cyber\\nSMEs). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A3 typically facilitates the process. An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ndirectorate\\u2019s core team member\\u2019s general responsibilities include\\nensuring their directorate\\u2019s intent and expertise is considered as early\\nas possible. It also aids the staff awareness and support during later\\nactivities and staffing actions. External stakeholders are also invited\\nto support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct development. Key external representatives come\\nfrom operational users, program offices, development test, and other\\nOTAs (for Multi-service \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" action officers (or support\\ncontractors, typically the Institute for Defense Analyses (IDA)) should\\nalso be invited if the program is on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" oversight list. External\\ninvolvement during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct development is significant in\\nterms of early buy-in on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\u2019s foundational planning effort, and it\\nbuilds relationships at the earliest possible opportunity. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct can be developed without externals, and with some rapid test\\nactivities it may be required to keep a program moving quickly. However,\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Constructs are typically better if external stakeholder\\ninterests/inputs are considered. Figure 3 reflects a typical \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \"\\ncomposition and potential external stakeholders.\"), mdx(\"p\", null, \"Figure 3. Core Team Composition\"), mdx(\"span\", {\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/baccd1277005f889d1667dc7557661fa/0d6fe/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\": \"67.95366795366795%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAYAAAAvxDzwAAAACXBIWXMAABcSAAAXEgFnn9JSAAAEE0lEQVQ4yy1UyU/bVxh8KX9ED73mVKmHRuqlV3qIcomiKFEpRCJELGE3a5ogxQWDnZA0jgNq1BBScM1iG0jCauMFb9iAsY1XvLLWYJCJsc3mn/2mP9R+0tye5s1o5vsIYYfPl+Xdvl1PuFwpuXWr5GphYUP9/fuPxtvbRYGODlGayxXmeLyeUw6nM1xU1PS5uLilpaCg6tvHjyXk3r1fiVA4lXf9+i+kuPgJIVKp/6vW1gGWqPrqw4cCSW3ti7Pq6udobBRieloDtVoPpXIBer0Jvb0SlJd3obJSgIqKrkxZGW+8sLDpu+bmQWK3n1y5caOUkFevNKS6uqegv3/2dHZWj48f51mSRWZwUMFMTxtzLCE1may0p2eCCgTS3IcPCkYu1zNymR7v+2bB549mGxreVgwPu0gkkr5CRKKZn4eHzdBoXLDbPRmTaZVarS6q0dhgMLjp9PQKdDoX3O4NHCfSlOaySBwnaWQrStc84Uw4/A8rwAOhcKZmdNRKyOTkZsLp3ILZbGMMBhtMJge9xNKSA0ajF1NTm9jfTyGVTiEQ3kF0L4at7V1qYT/VmVYROzjIgh2fL0o7O4d+IOu+fSwvOxin0w+X84D6fGFYV5xwODyw2cLY3U1evkcsdoAlqxserx8n6SRCG1EsmN1UbXRjLxbPUpqFdsG8ShSqTcyrQnRWGaRK9R6UqggU8yHMKYOwWKI4OkoiGNmB07uBYHgLqVQSmUwG8S/H0Fm8WLT66fn5OVjk9vf3QPrEIQyPbdPR8W06PLYBiew/9EvC0BnOcBRPQ2eyQm92wOZws+pSyDLMpSoodGvQLnrol0QSDMPQSCQCYjFfIBQ8ZNwuLzzuAHWueal/PYAlyxHUqjQCgRRrOIOd3X1WZRhe/wZOT0+wshZmLXupxuTGemg3xzAXGBwcCRCpzLerUESg1a5n1GofVCo/1WgD1GjcYi3vYX5+B8FgHKHIJuyudfgDYRweHlJvYIvG43HW/lnu7OyUzs1Z2O52/USePh3Jn5hYvgyGJbBeKJUrVKGwUq12kU15mcrlRioSaTE2ZoFt1U9jsUNssykbFm1sveyMybRGBwbmweW++00gGCfs2nwmzc3C/I6OgVh7uxhDQ2pMTi4y/yP3+vU4lUhUVCrTUZlsIScUyrN8vpjpfi5Be/sA2treoaXl9ycCwRqJRkFIX58ur63tLblz58HXpaXcXrF4LDE6OgGxWAaZ7BO6u//C6qqdLf0K2zUXnj17j9LSDtTU8GltLU9RX//ox6amPnJwAFJVVXG5y8vscfg77+bNB6Su7g25di3/m7t3q8qKihokhYUcd0lJa4LPf8O8fPnHiUj0Z4TD4c4UF3PaKivrvq+r+0TKy5sIjzeSx+FUkPr6RvIvHykvyUyNP9cAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"C:\\\\Users\\\\James.Thomas\\\\Desktop\\\\ITD Brief\\\\CT Picture.png\",\n \"title\": \"C:\\\\Users\\\\James.Thomas\\\\Desktop\\\\ITD Brief\\\\CT Picture.png\",\n \"src\": \"/static/baccd1277005f889d1667dc7557661fa/e3189/image5.png\",\n \"srcSet\": [\"/static/baccd1277005f889d1667dc7557661fa/a2ead/image5.png 259w\", \"/static/baccd1277005f889d1667dc7557661fa/6b9fd/image5.png 518w\", \"/static/baccd1277005f889d1667dc7557661fa/e3189/image5.png 1035w\", \"/static/baccd1277005f889d1667dc7557661fa/0d6fe/image5.png 1115w\"],\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 typical roles and responsibilities for core team members and\\nexternal stakeholders are addressed in table 1.\"), mdx(\"p\", null, \"Table 1. Core team and External participant Roles and Responsibilities\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, mdx(\"strong\", null, \"Core Team\")), mdx(\"th\", null, mdx(\"strong\", null, \"External Participants\"), \".\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Detachment TD:\"), mdx(\"p\", null, \"- Serves as the overall lead for all core/test team activities from program involvement through OT closeout\"), mdx(\"p\", null, \"- Produces well-written documents and well-prepared briefings\"), mdx(\"p\", null, \"- Serves as primary briefer for the program\"), mdx(\"p\", null, \"Note: Det/CC has operational control of the testing process from TO through OT closeout\"), mdx(\"p\", null, \"Battlespace development facilitator:\"), mdx(\"p\", null, \"- Facilitates the battlespace development and assists TD with developing the test design\"), mdx(\"p\", null, \"- Documents the OT&E Construct\"), mdx(\"p\", null, \"- Co-facilitates test events, methodologies, and scenarios\"), mdx(\"p\", null, \"A-2/9 Staff:\"), mdx(\"p\", null, \"- Co-facilitates test events, methodologies, and scenarios\"), mdx(\"p\", null, \"- Assesses program\\u2019s intelligence sensitivity\"), mdx(\"p\", null, \"- Provides assistance with development of realistic threat scenarios\"), mdx(\"p\", null, \"- Provides specialized support to team in the effectiveness analysis, suitability analysis, modeling and simulation expertise, test design expertise, weather, intelligence, and human factors\"), mdx(\"p\", null, \"A-5/8 Staff: Provides policy guidance, test capability, and range identification\"), mdx(\"p\", null, \"SE Staff: Provides environmental, safety, and health guidance\")), mdx(\"td\", null, mdx(\"p\", null, \"- Warfighters bring operational currency, background information and clarity when addressing operational requirements and concepts of operations\"), mdx(\"p\", null, \"- Program office participants bring program information (schedules, technical risk areas, funding, etc.) Gain insight into OT expectations; know potential impact to contract awards with OT flavor\"), mdx(\"p\", null, \"- Lead Developmental test organization (LDTO)/CTA participants bring developmental test (DT) information, gain insight into OT expectations, identify operationally representative OT events that DT can fulfill, know potential impact on capability requirements clarification start provide insight into integrated test challenges\"), mdx(\"p\", null, \"- Other agencies provide insight into test capabilities, expectations, plans, limitations\"), mdx(\"p\", null, \"-- Director, Operational Test and Evaluation (DOT&E) fulfills an oversight function\"), mdx(\"p\", null, \"-- Other OTAs address their Service equities for MOT&Es\"), mdx(\"p\", null, \"--- Army Test and Evaluation Center (ATEC)\"), mdx(\"p\", null, \"--- Operational Test and Evaluation Force (OPTEVFOR)\"), mdx(\"p\", null, \"--- Marine Corps Operational Test and Evaluation Agency (MCOTEA)\"))))), mdx(\"h1\", null, \"Construct Development Meetings\"), mdx(\"p\", null, \"Battlespace development typically occurs in a formal meeting(s)\\nenvironment. It is closely tied to the test design and is often\\naccomplished during the same meeting(s). In most cases, an A3 test\\ndesign manager (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \") will accomplish pre-work with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" prior to the\\nformal battlespace development meeting. The pre-work, coupled with A3\\nfacilitation, allows the meeting to be executed quickly and efficiently.\\nSuccessful battlespace development typically takes a couple of days\\nallowing a transition into the test design activity during the same\\nformal meeting. Optimally, one battlespace development/test design\\nmeeting is required with follow-on activities for measures development\\n(measures workshop) and execution planning activities.\"), mdx(\"h1\", null, \"Battlespace Development\"), mdx(\"p\", null, \"The Battlespace development steps are captured in the subsequent\\nparagraphs.\"), mdx(\"h2\", null, \"Researching the Capability or System Being Acquired\"), mdx(\"p\", null, \"Core team members and external stakeholders should strive for maximum\\nunderstanding of the capability being acquired, the mission(s) it\\nsupports, and how it will be employed and supported before the formal\\nmeeting. To prepare for the battlespace development/test design meeting,\\nresearch capability-based requirements (e.g., draft \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \") and any\\navailable system information from various sources (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Software or Systems Requirements Document\"\n }, \"SRD\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Requirements Document\"\n }, \"TRD\"), \").\\nOther documents critical to operational understanding are \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", TTPs\\nand threat documentation. This research results in knowledge of where\\nand how the system fits into the envisioned battlespace and the intended\\noperational capabilities. Gaining this knowledge can be inherently\\ndifficult early in a program\\u2019s acquisition cycle with only a draft \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \"\\nand a limited, or no written \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \". The operational significance of the\\nrequired capabilities and their impact on the battlespace need to be\\nunderstood sufficiently in order to properly scope the overall\\noperational evaluation.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \" should strive to understand:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The mission the system is designed to support\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Operational objectives required to accomplish the mission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The critical elements of the mission the system supports\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Information/data cyber dependencies which enable the mission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Bounds of the \\u201Csystem\\u201D acquisition and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" processes (i.e., \\u201Cto\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"what extent are other systems impacted, beyond the system being\\nacquired, within the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" processes?\\u201D)\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Threat environment (kinetic and non-kinetic) in which the system is\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"expected to operate\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Limitations and issues that are resolved to support the acquisition\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" processes (technical as well as operational)\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Program documentation:\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"System \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capability requirements documents\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Program acquisition strategy (DoDI 5000.02 model being employed -\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"hardware- or software-centric; additional documents may be used,\\nas required)\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" battlespace development process\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test design process\"))), mdx(\"undefined\", null, mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"858px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/64a5740f114bce09bca2bf11f9a2d76e/42d54/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\": \"55.5984555984556%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAYAAAB/Ca1DAAAACXBIWXMAABcRAAAXEQHKJvM/AAADLUlEQVQoz32Sy08TURTGr5IYRQQU8IEmqBsXrtwQF/4L/gFujMREwbhjoyZGSA1aHpUpAWkLfak4QFvoY2baUvoY6IMBWvoeSi0gta/plJZCiiGm3jZx6+K7597N757zfQdwudxGg8EwiGHYp5mZGZ5areapVKohgiD4eoPhXT0ANcgue02Vz5DEcc77dZteF3gp92TI454Iut3z+8k1vMRGZtg0v1wuA8Dj8a6TJMmYTKYCBO5DYEWs2Ww+spFk8OHt67XDicPLs7n0guYwuyKJBO0Cv9sh3gw4xr1rjql4bEl3xHq/Z1KDVWDl+J+G3BHwwb976Vs61avMZweFdIiLrFL9os1wP8/l7Ifvj6oCy5clkh1V4MDAwHkcxzt1Ot0L2FmXVqutqBOO/BLD8ccAgFO8GFPpUAE7MagPGFwU2iDG3CuE7EeYwI4LOk2RsaFMurcKRBDkhtVqLWk0mj9w5BMIPZmbm/sNPylbbbadR/funh/+dXBlNpexqAuZdWk0vCKOBClhwEOJQl4KTe66tIdscCqT+lQFdnd31wiFwja5XH5TKpW2VSSRSKp1dHy81fK7DDjb2UZVIduvOWRGYWd8Me0bqQjeR+QxGsFLORHKpDr/hQIsFguAIQCYNlhcXAQwILC8vAycpgUQI821X6iNW8r0L66WTY4YSgXkC4SMrjsRbTHLx48LwzAswXSOeVYF9vX1XYAr8wb69sZoNPZW1gW+EXgfwQnirfx9T4PEv3VHwSQ3NPupbVUmviWn/dEJD7U1n4yltGziAMunGDQRF1eBKIq222y26pooFIoi9LCoVCqL0NcT6GG4/Qw4O5QuNSvzzLz+pLj4bS9qGHaSRoFv3Ti2saqfz6cx43GenE4m+pTfNa1Ar9e3icXim9DHFplM1gxrE5/Pr+dwOA2venrr1QkWvD8qN8njO1Zh0BMURwI+aTTkn9z0+2XRUHgi5A1LI4G9qfhPkQrFroJAIHCapulzLpfrot1uvwRrI0VRdR6Pp87t89XZTQstmN15H/V5X39eXuoSrK50jDnsTwWU66nA5XwudDq6Jp1LT2Qh+kHL1WnwF2foUxQh3RHmAAAAAElFTkSuQmCC')\",\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/64a5740f114bce09bca2bf11f9a2d76e/42d54/image6.png\",\n \"srcSet\": [\"/static/64a5740f114bce09bca2bf11f9a2d76e/a2ead/image6.png 259w\", \"/static/64a5740f114bce09bca2bf11f9a2d76e/6b9fd/image6.png 518w\", \"/static/64a5740f114bce09bca2bf11f9a2d76e/42d54/image6.png 858w\"],\n \"sizes\": \"(max-width: 858px) 100vw, 858px\",\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 \"), \"To\\nfacilitate common understanding a series of briefings are typically\\nprovided at the start of a battlespace development /test design meeting.\\nThe briefings cover the Acquisition, CONOPS, capability requirements and\\nthreats. Generally, the program office, warfighting user, and\\nintelligence representatives provide the briefings. Once the team\\nunderstands the battlespace and how the SUT will support the operation\\nin that battlespace, the team can examine how the required capabilities\\nmap to the operational activities. The AFOTEC approach to ensure the\\ncore team understands the capability and system being acquired is to\\nbuild battlespace depiction in the form of an Evaluation View (EV).\"), mdx(\"h2\", null, \"Battlespace Depiction\"), mdx(\"span\", {\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/fa6e66c528a61855f6c7099891e53bcb/e4ab3/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\": \"86.48648648648648%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAARCAYAAADdRIy+AAAACXBIWXMAAC4jAAAuIwF4pT92AAAEEklEQVQ4yz1T+0/bVhTOX7afp/0wadqj0tSqUjdpZVXLtlJ1pRrQSusK1abB6PqgK6CNtpTSqUCFgNCBNsYr4ZEXIWDnQRLbcYzzcBzHcc6345D1Wp+/4+N7zzn3O/d6qtVqw7JrNJ4I0OPULg0zRlo86vJRgEbELRLzMn0TW6K2/UVqC83T1/t/0ZnwLC0oAoEf26mTaZrkqds21RsOvgssoi08j4vhBcY8LjG3My649vYsoqqEz/fncTo6jU/Dr3Bu/zXeDUxgRjmEOxqMWq0Gj80BDaMMJZUhNZkhLS1RQVIpcxCnHH9TxSI4oLpl0qgg0I1wgjpX/dSzE6PvoyKlzSJxLOIXVS2LPByVmingMDvM9VY+p8WuWWN3FUuigc7lPDqno7juTePejoGsWsTyUbkZEQ2bK+SAjQZhOKjRT/48+n059DP/vKk08eOGCxl6oYg1xULXioxubwxdSwk8ihSxkSnhj50skvkSIkoJTQ0rpolJ/yE988XxdD2GJ2sxjG8eYnIrjtlYHnOCDsuqIqJZGNkrY2gjiZGAihmueHw3i6hcQETS8SwgnWjI3YGWTVNRycAq6TjOHiEtxKDLGZjHOZRUmQUyMCc10OGr4itvAu3LCvqiDvLHOpy6zQqyPA5v+X8NLXbpLFverKFYJ1TYZ/CfEvsKDDdpauUN9t4swD/1EisTT7H2fAzKwR6MitmU2nK7XOPOSGoe0cFuynedQXHgCor9l1Ee6EB58CrMXzpQuP0F5K1/gbsdcK6+D7P3POiHc0D3KRixANw+y9kMDMOAR5FlknMqqtt/U3FqGAXvCxQWJqDPTzRt7c8hZMb6kd0PQ+cqxK11ZHovIX+/B+XRXtj3roH+mYJRb0A8PISnUqmQJEko2Q61Dsnb4X6rj29BE6KwhBCk327BOggAV96Dc+M0rJtn4Xz5DrSHPcjqJeiadtIUHjAKBdJzOZSPj2GVy6iaVejP7yL9ZBClcgWaIiM5NQZp4BqKSQGycAAtIUJOCFB5nV2vg2OdaOhWc1ytkmpZyJZKiKsqEnkNIk8WkyIiyRRSmSz8cRET8zMYX13FgiBigysyG/R2R3bz6nGX646D34MBuh8I4MHODh7u7mIoGMTDUAgPgiH86vNB5cVrhTLuRGK4s7qBvnUfHglJZDhx3axgU1Gwy5V6rFaFYA1hs2pNOCeotcDHyOakg6kd3E74cTO6gr64Dz3xDfi1DMiy8Soex54b0L0p7uTz26/pg+AUPg4wgtP4iPkU84ehaXyyOcnXKo3r4go6hGW0Rxbw7eEyPovOwasIzeQS36QSn1WPxdrVWMyZZIQmUiG8SDKYJ1Nhxon9Mh5EWs+jI7aEC/uLuLjnxWW2z4Zn4c3FW0eiAY6F/wBE8KpheY1VdAAAAABJRU5ErkJggg==')\",\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/fa6e66c528a61855f6c7099891e53bcb/e3189/image7.png\",\n \"srcSet\": [\"/static/fa6e66c528a61855f6c7099891e53bcb/a2ead/image7.png 259w\", \"/static/fa6e66c528a61855f6c7099891e53bcb/6b9fd/image7.png 518w\", \"/static/fa6e66c528a61855f6c7099891e53bcb/e3189/image7.png 1035w\", \"/static/fa6e66c528a61855f6c7099891e53bcb/44d59/image7.png 1553w\", \"/static/fa6e66c528a61855f6c7099891e53bcb/a6d66/image7.png 2070w\", \"/static/fa6e66c528a61855f6c7099891e53bcb/e4ab3/image7.png 2883w\"],\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, \"When\\ndeveloping the battlespace depiction, the core team should consider the\\ntype of capability being acquired, what actions the capability enables,\\nwhat objective(s) the capability supports, and the objective\\u2019s\\ndependencies on other systems. For example, if accomplishment of an\\noperational objective depends on numerous other systems and operational\\nfactors, it may be difficult to provide a credible answer about the\\nsystem\\u2019s contribution to the objective; in this case the scope or level\\nof test could be too high (e.g., operational level of conflict, table 4)\\nversus a more credible tactical level of conflict. These considerations\\nwill help guide the level of detail for the nodes in the evaluation view\\nand define the scope of the test.\"), mdx(\"h3\", null, \"The Evaluation View\"), mdx(\"p\", null, \"The evaluation view (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \") (Figure 5) is one method used to aid\\noperational understanding; it is a facilitation tool to get the core\\nteam and external participants to a point of common battlespace\\nunderstanding before jumping into operational test design. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"\\nillustrates three important \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" fundamentals: where in the operation the\\nsystem will likely influence operational outcome; where and when\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"-relevant data will likely be generated; and where the operational\\nenvironment could affect the system\\u2019s capability.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" is \", mdx(\"em\", {\n parentName: \"p\"\n }, \"not\"), \" intended to be a literal depiction. The core team should\\nunderstand that the battlespace depiction is not perfect, but that it\\nmeets the needs of process facilitation. The core team will need to have\\na degree of understanding and latitude as they progress through the\\nprocess because they will have to reach a consensus on the level of\\ndetail they deem sufficient to proceed to the next step.\"), mdx(\"p\", null, \"There are other methods to gain operational understanding, but using the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" has proven successful over several hundred test efforts and is\\ntypically the tool of choice to facilitate the majority of battlespace\\ndevelopment efforts. It has advantages over various other tools such as\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Architecture Framework (DODAF) views. Although DODAF views are\\nuseful for different levels of planning, they are oftentimes not\\navailable for the early \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" planning efforts. The DODAF system views\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System View\"\n }, \"SV\"), \") and technical views (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical View\"\n }, \"TV\"), \") are very specific in purpose and do not\\nprovide an overall picture of the battlespace. A DODAF operational view\\n1 (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational View (or Viewpoint)\"\n }, \"OV\"), \"-1) is often useful; however, it normally only addresses the\\npointy-edge of the operation and does not typically address logistics to\\nan acceptable level of detail. When an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" is complete, and done\\nproperly, it should reflect a tailored battlespace depiction that shows:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Major battlespace phases\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Elements of the operation (primary nodes)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Mission statement\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Critical operational issues (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \") and subordinate operations\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capability requirements mapping\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Information sources/references\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Inherently addresses both effectiveness and suitability elements\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provides equal consideration to logistics-centric operations\"))), mdx(\"h3\", null, \"The Evaluation View 1\"), mdx(\"span\", {\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/c5ad4772ebefa2bbe29a9a2f738fa756/412e0/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\": \"83.01158301158301%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAARCAYAAADdRIy+AAAACXBIWXMAAC4jAAAuIwF4pT92AAAEDUlEQVQ4y21US28bVRQeEAKExAZRYMsGsegPQMAGCcSCDUJIbKCbCoREQUKlUUWBIugChWcjirooLAKoEKFAlCbkQdIkSpo4duw4rvMyjieJ7bFn7JnxvO48z8exUySQekZXdx73fvN95zvnSnEcJ4Zp0kp5mxZKRVr8e5PmdgqktDTyhSDXdcl2HYIf0bvpMfokN0MIY34XkWVF5Hkm+b7B6wQ/JyTFUUS252KmtovRw02MV7cwIuehOia6QXx1o+U7eDn1K05lRxAFBNdOod0+jmLxXqRSd6NUegSa9hWkMAwpCAJ4gv/qBOR6CQ9QkvSQKOGrO8usoi89T5+t3yBbBBQGVepY/dRsvkO12lvUbp8lw7jODOOYHMfF7NY+XSs0MZKt4OfFceS3pxCIGsKoRxB5xcI3GRtX1nR0RIzbRcRrewyjyO+pi8QMKHwAnnUnNvJ3wHEklvU8EmGh1DAxkFHwfbaORqsJQ3+FZUosV0I2K6HZfAG23TgCDEOvq48sOwvDfAYbhWO88H6UK4/CtN8D4gDXKwb6FlUMpBX4fgDhjULXP0BdOc1g5xhsGEK4kKKoC3gr/xycOxB1Xwh+cIHg6NPQ+gE+navgN55j3uDHtzb8J4Ig7DIEJ/UC8vljtLN9F1ZX70Fl7wnUqssYSqu4kqogVyzB6Ri9TQd2hNOzhzi77KHUug0gJ5J0fRoNtY8a6uuo1t+EpvezdBnLaS6jqXnIuyWQcOBtZqCsLmC3vI+y8hea2hdQ6hdY8ucseZwl22CXuThZWXU2S/LIPKoTK6hem0O7rkH88DHUN56GNvYjjJ0NqGdeRLP/FIJ2E457EvuyhPSqhPWcBEV5EpYldxnGJLwOOuo0qfJ3qJcvQq38BOErsItrqA1+CW1qCK7w0Sis4eDqJbg3JhA4ESLOo4gUhGj17rteMEOQpi3AtB6knTKXQUZidyW0OmdgzM1CPf8q5IH3obOzemYO2vkTaH37IRx1C3bnNXh7j8PdfQyu8RwMK/1vHXJFJjrFfhZJuMJjjy0MewYrjoec2sLXhQ2M7B/ADGPozMRPVHTazyIsP4yw9BDc5nHonXn0OsVyHGTkQ1quNJCSVSyU9tGxHXaxhYtrLNtghwWjdFxMVmRc3tnCXkOD7xXQNi6hbV2GI2R2Gd0cRnxa+PA8j1wGdl2HO8RBl3VCBFsILhmLGS7gZOp3jO3mwL0O1bgKryEhKfC4KcHU7mPJxSNAjzctKXs0zSfObL2EycNttD3nfzX29vqfeGppEDmjftS3ic0nziCEcQ6e8RF3zgT8wD+S3Gq3Mbm9Tn9srmF0K4vhm6uQG3V4fGiYtgXftHBiZRgvLf0CSzdgOzbXnculAzaTM2GDlfHMSv4BV4m1gWnAPDQAAAAASUVORK5CYII=')\",\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/c5ad4772ebefa2bbe29a9a2f738fa756/e3189/image8.png\",\n \"srcSet\": [\"/static/c5ad4772ebefa2bbe29a9a2f738fa756/a2ead/image8.png 259w\", \"/static/c5ad4772ebefa2bbe29a9a2f738fa756/6b9fd/image8.png 518w\", \"/static/c5ad4772ebefa2bbe29a9a2f738fa756/e3189/image8.png 1035w\", \"/static/c5ad4772ebefa2bbe29a9a2f738fa756/44d59/image8.png 1553w\", \"/static/c5ad4772ebefa2bbe29a9a2f738fa756/a6d66/image8.png 2070w\", \"/static/c5ad4772ebefa2bbe29a9a2f738fa756/412e0/image8.png 2990w\"],\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, \"Building\\nan \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" can look challenging on the surface, but it is initially framed by\\nan A-3 Test Design Manager (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \") skilled in their development. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \"\\nworks hand-in-hand with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" in all pre-work activities and the\\ninitial framing occurs prior to any formal meetings. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-1 forms a\\nsystem-of-systems depiction of the Joint and/or Air Force doctrinal\\nmission area that the new/modified capability is intended to support. It\\nis developed using the broad knowledge gained from early involvement,\\nstudying Joint and Air Force doctrine and researching all available\\nprogram documentation (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \", system \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \", \", 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\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \"\\nstrategy, Air Force & Joint \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" & Doctrine, associated DODAF\\narchitectures). The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" consists of typical operational nodes linked\\ntogether using a \\u201Cnecessary conditions\\u201D methodology. Primary nodes are\\nsignificant elements of the operation. Major phases are logical\\ngroupings of primary nodes and are used to add clarity and understanding\\nto differing phases of the operation. Major phases of the operation\\nusually become apparent after the primary nodes are linked and are\\nfurther differentiated using different colors to associate the primary\\nnodes with their respective major phase.\"), mdx(\"h3\", null, \"The Evaluation View 2\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-2s are a near-seamless evolution of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-1s and differ in three primary\\nareas. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-2 has capability requirements, critical operational issues\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \") and subordinate operations mapped into the battlespace.\"), mdx(\"h3\", null, \"Capability Requirements Mapping\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" 2 (Figure 6) builds on the operational environment depicted on\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-1. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-2 is developed by mapping operational capability\\nrequirements into the depiction where the operational performance data\\nwould likely be generated during a typical operations. Operational\\ncapability requirements are found in a variety of documents (e.g., draft\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"). Operational capability requirements usually\\ncontain key characteristics (attributes) with appropriate parameters and\\nmetrics. However, they may be described with only the characteristic\\n(e.g., \\u201Cthe system must possess high reliability\\u201D). Other times there\\nmay not be any documented capability requirements and in these cases\\nthere will be greater reliance on current operational expertise to\\ndefine the material solution (system under test). This is the most\\nextreme case for defining the battlespace and system under test and\\nwould require documenting capability documentation shortfalls. While\\nmapping requirements, keep in mind that teams often identify\\nrequirements shortfalls that should be mapped as derived capabilities.\"), mdx(\"p\", null, \"Derived capabilities are usually the result of some inferences in the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \", or could result from an interpretation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" and\\ncapabilities relationship and understanding that certain performance\\ncharacteristics must exist for a system to meet its overall mission\\nneed. Derived capabilities do not have associated criteria or\\nreferences, but generally influence the overall effectiveness and/or\\nsuitability determinations (The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" must validate capabilities derived\\nduring the core team process with the user).\"), mdx(\"p\", null, \"To help teams readily identify cybersecurity interest areas. The nodes\\nwith cyber dependencies will be identified by a blue border and will\\nhave applicable requirements and verbiage detailing the cyber dependency\\nmapped into it. The purpose of this step is to generate discussion and\\nidentify area for further investigation into possible test implications\\nconcerning Cybersecurity.\"), mdx(\"p\", null, \"During \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \", the test team should monitor/assist with cybersecurity\\ntest events, pursuing test events using standard scenarios based on real\\nprocedures, real operators, and production-representative equipment. If\\nviable, the team should plan accordingly and reflect the plan in the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" and other test-planning documentation. The team must incorporate\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Production Document\"\n }, \"CPD\"), \" and system \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" as testing evolves.\"), mdx(\"h3\", null, \"Mission Statement\"), mdx(\"p\", null, \"Mission statements are written at a high, overarching level consistent\\nwith the mission the system is intended to support. For example, \\u201CCombat\\nSearch and Rescue Locator (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue Locator\"\n }, \"CSARL\"), \") supports the combat search and rescue\\nmission.\\u201D The team should ask, \\u201CWhat mission is the system intended to\\nexecute or support?\\u201D or \\u201CWhy are the capabilities being acquired?\\u201D\\nMission statements should be consistent with wording from published\\ndocuments like 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\"), \", \", 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\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", doctrine, etc. The\\nmission statement should also trace to the capability gaps identified in\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \". The Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \" develop a recommended mission\\nstatement in the pre-work and present it to the team during the meeting.\"), mdx(\"h3\", null, \"Critical Operational Issues\"), mdx(\"p\", null, \"A critical operational issues (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \") is an operational question. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ndefines a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" as a critical mission element or operational objective\\nthat is examined during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to determine the system\\u2019s overall\\ncapability to support mission accomplishment as determined by\\neffectiveness and suitability. Put simply, COIs are operations, and\\nshould clearly speak to the warfighter. When answered, the operational\\nimpact is clear. For COIs, the team should ask, \\u201CWhat are the critical\\nelements of the mission?\\u201D or \\u201CWhat warfighter goals, major operations,\\nor activities are intended to be accomplished?\\u201D\"), mdx(\"p\", null, \"A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" may be composed of more than one type of operation and may\\ndescribe the operation in a set of activities or phases of a mission\\nneeded to accomplish the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". An example is the KC-46 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \", \\u201CCan KC-46\\nprovide refueling?\\u201D There are at least two distinct activities or\\noperations within this \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \": air-to-air refueling and forward area\\nrefueling point (FARP), which is forward ground refueling. Although the\\noverarching goal is the same (to provide refueling), the activities and\\nthe conditions to do this are different. Identifying operations allows\\nfor designing test around the unique operations and associated\\noperational conditions. The major phases identified on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" should\\nprovide a logical \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" structure. The COIs and any breakout of\\nsubordinate operations are documented on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \" near logically group\\noperational nodes.\"), mdx(\"p\", null, \"COIs are operations, not functions, system characteristics, or enable\\ncharacteristics. Figure 7 illustrates some basic \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" tenants.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 7. \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Tenets\")), mdx(\"span\", {\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/9d82dda1880573be3bd02ea6f57a4533/e3829/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\": \"47.10424710424711%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAJCAYAAAAywQxIAAAACXBIWXMAABcRAAAXEQHKJvM/AAACMUlEQVQoz13Sy08TURQH4NMqA5RoiSRYfEQpKlGoAj4ixWd04cYFDakLw19BXJi4wGDSjdGNLEgKpZJ0rExrO6jQMtZO23n1kRZQN1SjiZhKYogmsPFxPbe5TYxNvtzJzM3vnnNPAQA45EDdqAf1oZOoCx2n6jiuF9f26YR+UEopWkh8/mFeSqzHMrm7XzfyTk2LVaLRwCfDyJRxH5jRYTSATqNT6CxbafAFepjJBHZcrcQzBLBJuLbXExY4ACZCqiyozu0mUAvsYBXSqg6hY+goe0eDrXTjpctXIJvNehQ9IyVfiW7V0CYURZ6UFuVhVU1H4vH4bbpvOwuhrZ5D/awqWqWNHsbVNzR7FzWI5pfhvs/v9D8ZH3rsDXT4Q4IrGPa6Zvx8dyQyORwI+C7WAu3sHjtZlRS9t9372u30e/2z4qqDX/l87c7Kl71dNwm8SC7Ab70ErhsEFPUB8PxPUFWj2nIDu/ye/4ZCD7HtamnZT1uOKnlhPpkmUn55dkMkEEoXRsKp3Hgox3d+W7vXWiqFR8vlVLVljt0ZDTrzTzit0rbTam3DtXlGzg/OpbSXC4YuFD+KzmAi7feJsaRYlK8TMuWIxadlWQ4maOA2NoB+1iYNO4Gc6AjaY7E0Nr1b/wElQ4FiKXhL14W5N0tT52fDS2DovKwoT9cKhYe9lUoOaj866SbUiHawZwubLoV/DQJvCznz5tZ7+PPrOxCyhYhZEDx9Xu/o1UzmUevY2AD8BeKh4qdGpySTAAAAAElFTkSuQmCC')\",\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/9d82dda1880573be3bd02ea6f57a4533/e3189/image9.png\",\n \"srcSet\": [\"/static/9d82dda1880573be3bd02ea6f57a4533/a2ead/image9.png 259w\", \"/static/9d82dda1880573be3bd02ea6f57a4533/6b9fd/image9.png 518w\", \"/static/9d82dda1880573be3bd02ea6f57a4533/e3189/image9.png 1035w\", \"/static/9d82dda1880573be3bd02ea6f57a4533/e3829/image9.png 1077w\"],\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, \"As with all things, there are exceptions. Given the emphasis on\\ncybersecurity, teams have the option to address cybersecurity as a\\nseparate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". This is typically done because teams believe there are\\ntest reporting advantages. For some systems, a cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" may be helpful\\nfor reporting cyber effects to warfighters and acquisition community\\nseparate from system performance in an uncontested cyber environment.\\nReporting this way highlights cyber during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E by more narrowly\\nfocusing on what needs to be corrected, why, and the impact if not\\ncorrected from a cyber perspective. In these cases, a separate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" to\\ncapture cybersecurity concerns, may be warranted. Considerations that\\ncould justify a separate cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" are characteristics of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" (e.g.,\\ncommon architecture across all COIs, a software/network focus, and\\npotential catastrophic node), characteristics of the operating\\nenvironment (e.g., significant documented cyber threats or reliance on\\nout of boundary systems or connections), or when cyber effects are not\\nfully captured in traditional ops-based COIs. Test teams can choose from\\nthree \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E constructs (integrated, stand-alone, and hybrid) to capture\\nand report cyber impacts in a manner that ensures stakeholders\\nunderstands performance and mission impacts in a cyber-contested\\nenvironment. Cyber considerations do not mandate a cyber-centric \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \";\\nhowever, core teams have flexibility should they desire a different\\ncyber reporting approach.\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"integrated approach\"), \" (commonly referred to as \", mdx(\"em\", {\n parentName: \"p\"\n }, \"traditional\"), \" or\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Ops-based\"), \") would only have a cyber-centric \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" if there was a defined\\ncyber operation introduced by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Cyber elements (operational\\nconditions, threats, test measures, etc.) are addressed within the\\ncontext of the missions or operations-based COIs (wherever cyber can\\naffect operational outcome). Using the integrated approach, any notable\\nissues identified that extend beyond the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" (e.g., do not affect the\\ndegree of mission accomplishment of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" or the ability to place in\\nfield use) may be addressed in a separate annex to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report, if\\nwarranted.\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"stand-alone approach\"), \" addresses all of the operations-based COIs in\\nan uncontested cyber environment; the stand-alone, cyber-centric \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\naddresses the operations in a cyber-contested environment. This approach\\nallows the baselining of uncontested performance, as compared to\\ncontested performance of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". The Stand-alone Cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" essentially\\nembeds and executes the operations documented in the traditional COIs in\\na cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" that has a contested environment. All cyber contested\\nelements (e.g., operational conditions, threats, test measures, and test\\nevents) are addressed within the cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". Additional cyber-specific\\nmeasures address the system\\u2019s cyber operational capabilities.\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"hybrid approach\"), \" applies elements of both the integrated and\\nstand-alone approaches, addressing cyber both within the\\noperations-based COIs and a separate cyber-centric \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". Cyber elements\\n(e.g., operational conditions, threats, test measures, and test events)\\nare addressed within the context of the missions or operations-based\\nCOIs, the cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is functionally focused (e.g., cybersecurity\\noperational capabilities) and also addresses effects not seen within the\\nmissions or operations-based COIs (i.e., indirect effects, 2nd/3rd order\\neffects). This may also be used to expand cyber reporting beyond the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", if warranted.\"), mdx(\"h3\", null, \"Operations\"), mdx(\"p\", null, \"Based on different activities or different operational conditions within\\na \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \", multiple subordinate operations may be identified under a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". An\\nexample \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" for the KC-46 was, \\u201CCan KC-46 provide refueling?\\u201D There are\\nat least two distinct activities or operations within this \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \":\\nair-to-air refueling and forward area refueling point (FARP). Although\\nthe overarching goal is the same (to provide refueling), the activities\\nand the conditions to achieve this are different. Another example could\\nbe sustainment operations that has a subordinate maintenance operation,\\ndeployed operation, and training operation. Again the need for breaking\\ndown various operations become obvious when identifying the various\\nconditions associated with the different operations.\"), mdx(\"h2\", null, \"Operational Employment and Support Conditions\"), mdx(\"h3\", null, \"Measures of Effectiveness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" (very similar to the previous Mission-Oriented Response Variables\\nor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \") are developed for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or for each operation. An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" is a\\nmeasure of a system\\u2019s (or operation\\u2019s) degree of mission success and\\nwill be commensurate with the level of test. It is a dependent variable\\nwhich gauges the achievement of a desired effect (aka measure of\\neffect). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" also guide the development of factors and levels by\\nassessing factors\\u2019 expected impact on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \".\"), mdx(\"p\", null, \"Ideally, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" should be continuous, but could also be binary\\u2014was the\\neffect achieved or not. While a categorical or binary \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" may be a\\nstrong indicator of mission success, it might also drive considerably\\nmore testing and resource requirements than a continuous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" would\\nrequire to achieve the same statistical significance.\"), mdx(\"p\", null, \"Examples of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" for a notional Combat Search and Rescue system\\u2019s\\noperation of Recover Personnel might be:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Binary: \\u201CPercentage of Rescue Attempts that are Successful\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Continuous: \\u201CProportion of Survivors Rescued\\u201D\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Note the measure of effectiveness reflects the outcome or effect of\\nan operation.\"))), mdx(\"h3\", null, \"Operational Conditions (Factors and Levels)\"), mdx(\"p\", null, \"Operational conditions define the system\\u2019s operations and support\\nenvironment. After \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" have been developed, operational conditions that\\npotentially have a significant influence on outcome of the operations\\nare identified. Operational conditions are identified for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or\\noperation within a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" and depict the operational battlespace identified\\nto support development of test events and scenarios. An operational\\ncondition is defined by a set of factors, each set at a given level. A\\nfactor is a variable of the environment that affects task performance. A\\nlevel is a set value within the range of values that a factor can hold.\\nIt is important to understand the factors influencing task performance\\nin order to initially capture representative operational conditions in\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct. The terminology (conditions, factors, and levels) is\\nderived from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chairman, Joint Chiefs of Staff Manual\"\n }, \"CJCSM\"), \"\\xA03500.04D.\"), mdx(\"p\", null, \"The set of factors and levels forms the relevant set of operational\\nconditions. These conditions are contained in the test design\\nworksheets. As an example, the Mode of Travel, Battery Type, Terrain,\\nTime of Day, and Threat are all factors (Table 3) potentially\\ninfluencing the outcome of the operation as defined by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \":\\nPercentage of Rescue Attempts that are Successful. No Vehicle,\\nRechargeable, Flat, Night, and High are one level for each factor,\\nrespectively. A single condition for the survivor/evader navigation \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\ncan be described by a specific combination of factors and levels. For\\nexample, one possible combination or single condition can be described\\nas mode is no vehicle, battery is non-rechargeable, terrain is\\nmountainous, time of day is night and the threat is high. Another\\noperational condition can be described as the terrain is flat, time of\\nday is daytime, and the threat is low. Cyber threats have the potential\\nto impact most systems. The cyber factors in table 2 are generally\\nsufficient for test designs; however, other cyber focused factors may be\\nappropriate depending on the COIs and/or subordinate operations.\"), mdx(\"p\", null, \"Table 2. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 2, Survivor/Evader Navigation\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Conditions\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Factors\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Levels\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mode of Travel\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Battery Type\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Terrain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountainous\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Time of Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Disruptive Cyber threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Yes\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non Disruptive Cyber threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Yes\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"h3\", null, \"Identify Factors and Levels.\"), mdx(\"p\", null, \"Factors and levels are identified through a number of methods. If\\nstudies (such as an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \") have been conducted, they could provide insight\\non potential factors. If requirements have been mapped on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \", they\\ncould provide specific factors of interest (e.g., for \\u201Cthe system shall\\noperate day and night\\u201D the factor would be time of day). The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contractor Testing OR Critical Technology\"\n }, \"CT\"), \",\\ncomposed of the users, developers, operators, analysts, etc., brings a\\ngreat deal of knowledge and expertise to the task of brainstorming ideas\\non factors.\"), mdx(\"p\", null, \"To identify factors, the team reviews each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" and asks the question,\\n\\u201CWhat factors potentially influence the outcome of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or operation\\ncaptured by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"?\\u201D Some of these factors may be an explicit part of\\nthe environment in which the system will be employed (e.g., altitude,\\nweather, network load.) Other factors may not seem as directly related\\nto the employment environment, such as manning level, technical orders,\\nskill level. Yet, others may appear as inherent system factors that will\\nlikely be \\u201Cas-is\\u201D when the system is employed. Examples of this include\\nmemory size, number of display screens, and seat positions, we identify\\nthese as a \\u201CGiven\\u201D level within the design. While this list is not\\nexhaustive set of factors, it is important to document all of the\\nfactors identified for future reference. For \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" purposes, attempt to\\nfocus on the sets that will have a potential effect on the outcome of\\nthe operation and are likely to vary the operational environment or the\\nuser/operator.\"), mdx(\"p\", null, \"After the core team documents the factors, appropriate levels will be\\nadded to each factor. When identifying the levels, it is desirable to\\ncapture the range of possible levels. The decision on exactly which\\nlevels to test will be made later during test design. At this point, it\\nmay be recognized that several of the factors, particularly the inherent\\nsystem factors, may be given for operational test. In the example, the\\nfactors are software version and training. It is not necessary to\\nidentify levels for those factors (although, the developer may wish to\\ndo so). Table 3 expands on the navigation \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" example discussed in table\\n3.\"), mdx(\"p\", null, \"The last two factors highlight the point of documenting all identified\\nfactors. In the illustrated example, these particular factors were\\npreviously recognized as going to be \\u201Cgiven\\u201D or \\u201Cas-is\\u201D when the system\\nis delivered. Therefore, they are not prioritized since there is no\\npossibility for them to change. The software version factor is important\\nto document since it is part of the operation and is measured and\\nreported. The last two factors (software version/training) is at a set\\nvalue for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E.\"), mdx(\"p\", null, \"Table 3. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 2, Survivor/Evader Navigation\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Conditions\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Factors\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Levels\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mode of Travel\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Battery Type\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Terrain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountainous\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Time of Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Disruptive Cyber threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Yes\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-Disruptive Cyber threat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Yes\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Software Version\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Given\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Training\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Given\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"h3\", null, \"Prioritizing Factors\"), mdx(\"p\", null, \"The table of factors may include factors in the operational environment\\nwhich may not influence the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", but are used to describe an operational\\nenvironment. As a result, a prioritization process is used to rank\\nfactors based on their impact against each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\u2019s operations by\\nconsidering their effect on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \". This is a subjective determination\\nmade by the Core Team and is intended to identify those operational\\nconditions that have the most impact to mission success and are\\ntherefore more important from a test design perspective. This is a\\ntwo-step process for each factor and is accomplished during the\\nBattlespace Development meeting, using operator/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" input. The\\nprioritization process begins with determining the likelihood or\\nfrequency of encountering each level of each factor in the operational\\nenvironments and continues by determining the estimated magnitude of\\nimpact varying the levels of a factor has on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \".\"), mdx(\"p\", null, \"The first step determines the likelihood of encountering the particular\\nlevels for each factor. This is based on the potential to encounter a\\nparticular factor/level in the operational environment (e.g., the\\nprobability of recovery from mountains is high, but the probability of\\nrecovery from Flat is low). This may be done with specific probabilities\\nor percentages or with qualitative statements (e.g., likely, frequently,\\nseldom). The combinations of the factors, levels, and the likelihood of\\nencountering each level describes the possible battlespace conditions\\nthe system under test could operate within when conducting the\\nactivities depicted by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or Operation.\"), mdx(\"p\", null, \"The second step estimates the magnitude of impact and assigns a \\u201Chigh,\\u201D\\n\\u201Cmedium,\\u201D \\u201Clow,\\u201D or \\u201Cnone\\u201D rating for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" for each factor. The\\nimpact is assigned after considering the potential size of the change in\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" when the factor is varied between its levels, leading to a\\nsignificant change in the outcome of the operation with consideration of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \". Table 4 shows the prioritized factors highlighted in grey.\"), mdx(\"p\", null, \"Table 4. Factor Prioritization\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"COI 1: Can CSARL enable survivor/evader navigation to a rendezvous location?\"), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operation 1: Rescue Survivor\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"MOE 1: Timeliness of Rescue;\"), mdx(\"p\", null, \"MOE 2 Accuracy of Pick-up Point\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Factor\")), mdx(\"td\", null, mdx(\"strong\", null, \"Levels\")), mdx(\"td\", null, mdx(\"strong\", null, \"Prioritization\")), mdx(\"td\", null, mdx(\"strong\", null, \"Factor Mgmt\")), mdx(\"td\", null, mdx(\"strong\", null, \"Why factor is operationally important; Why level is selected\")), mdx(\"td\", null, mdx(\"strong\", null, \"Notes\")), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, mdx(\"strong\", null, \"Likelihood of Encountering\")), mdx(\"td\", null, mdx(\"strong\", null, \"Magnitude of Impact\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 1\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 2\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Mode of Travel\"), mdx(\"td\", null, mdx(\"p\", null, \"Vehicle\"), mdx(\"p\", null, \"No Vehicle\")), mdx(\"td\", null, mdx(\"p\", null, \"Frequent\"), mdx(\"p\", null, \"Seldom\")), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null), mdx(\"td\", null, \"Affects the survivor\\u2019s ability to move from the area.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Battery Type\"), mdx(\"td\", null, mdx(\"p\", null, \"Rechargeable\"), mdx(\"p\", null, \"Non Rechargeable\")), mdx(\"td\", null, mdx(\"p\", null, \"Frequent\"), mdx(\"p\", null, \"Seldom\")), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null), mdx(\"td\", null, \"Ability of the survivor/evader to have communications.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Terrain\"), mdx(\"td\", null, mdx(\"p\", null, \"Flat\"), mdx(\"p\", null, \"Mountainous\"), mdx(\"p\", null, \"Littoral\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null), mdx(\"td\", null, \"Difference in the terrain could affect the survivors\\u2019 ability to move or platform recovery.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Time of Day\"), mdx(\"td\", null, mdx(\"p\", null, \"Day\"), mdx(\"p\", null, \"Night\"), mdx(\"p\", null, \"Transition\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null), mdx(\"td\", null, \"Night time could affect the ability to see the survivor/evader.\"), mdx(\"td\", null, \"The CT should document notes for each F&L set.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"High\"), mdx(\"p\", null, \"Low\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null), mdx(\"td\", null, \"This would affect the platforms ability to reach location.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Disruptive Cyber Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"Yes\"), mdx(\"p\", null, \"No\")), mdx(\"td\", null, \"Common\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null), mdx(\"td\", null, \"Will have to look at mission planer vulnerabilities.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Non Disruptive Cyber Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"Yes\"), mdx(\"p\", null, \"No\")), mdx(\"td\", null, \"Common\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null), mdx(\"td\", null, \"Look at possible mission effects.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Software Version\"), mdx(\"td\", null, \"Given\"), mdx(\"td\", null, \"Givens not prioritized\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"Complete instructions on how to plan and operate system, also affects maintenance.\"), mdx(\"td\", null, \"Latest version.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Training\"), mdx(\"td\", null, \"Given\"), mdx(\"td\", null, \"Givens not prioritized\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"Platform dependent, survival or equipment related capabilities.\"), mdx(\"td\", null, \"Both survivor and recovery team have training.\")))), mdx(\"p\", null, \"The last two factors highlight the point of documenting all identified\\nfactors. In this example, these particular factors are seen as \\u201Cgiven\\u201D\\nupon system delivery. Therefore, they are not prioritized because there\\nis no possibility they will change. The technical data factor is\\nimportant to document because it is part of the operation and will be\\nmeasured and reported. The last factor will be at a set value for the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. The team has determined this factor is unlikely to have an impact;\\nnonetheless, it is documented as part of the set of factors. The last\\ntwo factors and the factor \\u201Cthreat\\u201D are not removed from the list\\u2014they\\nare still needed to ensure the test environment is operationally\\nrepresentative. Consideration should be given to them for resource\\nplanning and test execution.\"), mdx(\"h2\", null, \"Operational Capabilities (\", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Operational Capability\"\n }, \"OC\"), \")\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Capability\"\n }, \"OC\"), \" is a system attribute or grouping of attributes users or SMEs\\nidentified as having value or that are crucial to the system to satisfy\\nthe capability gap within the context of the operations defined by the\\nCOIs. They provide operational context for attributes of high interest\\nor importance within the operation. OCs are identified by reviewing the\\nsystem\\u2019s requirements documents and by SMEs identifying system\\ncapability attributes that can significantly influence achieving the\\nCOIs.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"Cybersecurity and cyber resiliency are high-interest attributes and\\nare assessed/evaluated as applicable across all operations.\")), mdx(\"p\", null, \"The OCs are not part of the rating structure or evaluation at the end of\\ntest, but serve instead to highlight possible trends/patterns of\\noperational impact along a particular capability. For instance, if in\\nthe final evaluation, multiple measures fail across the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Capability\"\n }, \"OC\"), \"\\n\\u201CInteroperability\\u201D, then this potential capability impact is highlighted\\nto leadership and decision makers. OCs are captured as a short phrase or\\ntopic. Although the identification of OCs is a facilitated effort by the\\nA3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \", table 5 shows which areas to examine when developing OCs.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 5. Operational Capability Areas\")), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"th\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Capability\"\n }, \"OC\"), \"\")), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"th\"\n }, \"Area to Examine\")))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Performance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What are the measures of desired effects (e.g., timeliness)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What operational performance attributes are listed (e.g., precision, responsiveness)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What operational performance attributes are associated with the key performance parameters (\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \") and key system attributes (\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Key System Attribute\"\n }, \"KSA\"), \") (e.g., accuracy)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What attributes are high risk (e.g., lethality; cybersecurity, dependent on new technology)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"System Support\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What support attributes are listed (e.g., reliability, maintainability, availability, compatibility)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What are the support\\u2011related attributes associated with the KPPs and KSAs (e.g., cybersecurity)?\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"What attributes are high risk (e.g., reliability; dependent on new manufacturing techniques)?\")))), mdx(\"p\", null, \"On the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \", OCs allow some logical grouping of the operational\\ncapabilities or capability requirements (e.g., from an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \"). The\\nrelationship between operations (defined by the COIs), operational\\ncapabilities and capability requirements are clearly depicted.\"), mdx(\"h1\", null, \"Evaluation Summary Chart\"), mdx(\"p\", null, \"The team presents the program\\u2019s \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct in an Evaluation Summary\\nChart (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \"). The chart will vary slightly depending on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" approach\\n(see tables 6-8). The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" identifies the various elements of an\\noperational test and the relationship of the individual elements to each\\nother. The initial elements of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct are the Mission\\nStatement (optional), COIs, Mission Effects (as \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"), OCs, and\\nOperational Requirements; these form the first version of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \"\\nlabeled an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \"-1. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \"-1 is intended to be a concise presentation\\ntool for summarizing the focus and scope of the test and relationship of\\nCOIs and operational capabilities. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" presents the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" as part of an\\nInitial Test Design (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \") Briefing.\"), mdx(\"p\", null, \"Table 6. Evaluation Summary Chart-1 (Integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Approach)\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, mdx(\"strong\", null, \"Mission Statement: The CSARL supports the combat search and rescue mission.\")), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, mdx(\"strong\", null, \"Critical Operational Issues\")), mdx(\"p\", null, mdx(\"strong\", null, \"\\u2192\"))), mdx(\"td\", null, mdx(\"strong\", null, \"COI 1: Can CSARL enable rescue team navigation to a survivor/evader\\u2019s location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 3: Does CSARL support worldwide search and rescue operations?\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, mdx(\"strong\", null, \"Mission Effects \\u2192\")), mdx(\"p\", null, mdx(\"strong\", null, \"Operational\")), mdx(\"p\", null, mdx(\"strong\", null, \"Capabilities \\u2193\"))), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 1.1, 1.2\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 2.1, 2.2, 2.3\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 3.1, 3.2, 3.3\"))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Accuracy\"), mdx(\"td\", null, \"4.3, 7.4\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Situational Awareness\"), mdx(\"td\", null, \"4.1, 4.2\"), mdx(\"td\", null, \"4.1, 4.2, 4.9\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Timeliness\"), mdx(\"td\", null, \"4.4, 4.5\"), mdx(\"td\", null, \"4.4, 4.5, 4.6\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Mission Planning\"), mdx(\"td\", null, \"4.9\\u20134.12\"), mdx(\"td\", null, \"4.10\\u20134.13\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Cyber Resiliency/ Survivability\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Interoperability\"), mdx(\"td\", null, \"4.29\"), mdx(\"td\", null, \"4.30\\u20134.32\"), mdx(\"td\", null, \"4.33\\u20134.35\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Reliability\"), mdx(\"td\", null, \"4.25\"), mdx(\"td\", null, \"4.25\"), mdx(\"td\", null, \"4.26\\u20134.28\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Compatibility\"), mdx(\"td\", null, \"4.22, 4.24\"), mdx(\"td\", null, \"4.22, 4.23\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Availability\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"4.39\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Maintainability\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"4.40\\u20134.43\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Ground Equipment\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"4.44\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*KPP or supports KPP\"), mdx(\"td\", null, \"Effectiveness Centric\"), mdx(\"td\", null, \"Suitability Centric\"), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 7. Evaluation Summary Chart-1 (Hybrid \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Approach)\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, mdx(\"strong\", null, \"Mission Statement: The CSARL supports the combat search and rescue mission.\")), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Critical Operational Issues \\u2192\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 1: Can CSARL enable rescue team navigation to a survivor/evader\\u2019s location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 3: Does CSARL support worldwide search and rescue operations?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 4: Does CSARL Cyber Ops enable support Mission Assurance?\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, mdx(\"strong\", null, \"Mission Effects \\u2192\")), mdx(\"p\", null, mdx(\"strong\", null, \"Operational\")), mdx(\"p\", null, mdx(\"strong\", null, \"Capabilities \\u2193\"))), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 1.1, 1.2\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 2.1, 2.2, 2.3\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 3.1, 3.2, 3.3\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 4.1, 4.2, 4.3\"))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Accuracy\"), mdx(\"td\", null, \"4.3, 7.4\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"...\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Cyber Resiliency/ Survivability\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"....\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*KPP or supports KPP\"), mdx(\"td\", null, \"Effectiveness Centric\"), mdx(\"td\", null, \"Suitability Centric\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 8. Evaluation Summary Chart-1 (Stand-Alone \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Approach)\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, mdx(\"strong\", null, \"Mission Statement: The CSARL supports the combat search and rescue mission.\")), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Critical Operational Issues \\u2192\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 1: Can CSARL enable rescue team navigation to a survivor/evader\\u2019s location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 2: Can CSARL enable survivor/ evader navigation to a rendezvous location?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 3: Does CSARL support worldwide search and rescue operations?\")), mdx(\"td\", null, mdx(\"strong\", null, \"COI 4: Can CSARL operate in a cyber contested environment?\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, mdx(\"strong\", null, \"Mission Effects \\u2192\")), mdx(\"p\", null, mdx(\"strong\", null, \"Operational\")), mdx(\"p\", null, mdx(\"strong\", null, \"Capabilities \\u2193\"))), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 1.1, 1.2\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 2.1, 2.2, 2.3\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 3.1, 3.2, 3.3\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 4.1, 4.2, 4.3\"))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Accuracy\"), mdx(\"td\", null, \"4.3, 7.4\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, mdx(\"p\", null, \"4.1-4.13, 7.4.\"), mdx(\"p\", null, mdx(\"em\", null, \"Note: Will require later development of COI 1, COI 2, and COI 3 composite MOP/MOS\")))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Situational Awareness\"), mdx(\"td\", null, \"4.1, 4.2\"), mdx(\"td\", null, \"4.1, 4.2, 4.9\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Timeliness\"), mdx(\"td\", null, \"4.4, 4.5\"), mdx(\"td\", null, \"4.4, 4.5, 4.6\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Mission Planning\"), mdx(\"td\", null, \"4.9\\u20134.12\"), mdx(\"td\", null, \"4.10\\u20134.13\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Cyber Resiliency/ Survivability\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\"), mdx(\"td\", null, \"*4.21\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Interoperability\"), mdx(\"td\", null, \"4.29\"), mdx(\"td\", null, \"4.30\\u20134.32\"), mdx(\"td\", null, \"4.33\\u20134.35\"), mdx(\"td\", null, mdx(\"p\", null, \"4.29-4.44\"), mdx(\"p\", null, mdx(\"em\", null, \"Note: Will address in later COI 1, COI 2, and COI 3 composite MOP/MOS\")))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Reliability\"), mdx(\"td\", null, \"4.25\"), mdx(\"td\", null, \"4.25\"), mdx(\"td\", null, \"4.26\\u20134.28\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"...\"), mdx(\"td\", null, \"...\"), mdx(\"td\", null, \"...\"), mdx(\"td\", null, \"...\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*KPP or supports KPP\"), mdx(\"td\", null, \"Effectiveness Centric\"), mdx(\"td\", null, \"Suitability Centric\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"h2\", null, \"Mission Statement in an Evaluation Summary Chart\"), mdx(\"p\", null, \"The mission statement (optional) is copied and pasted into the\\nEvaluation Summary Chart.\"), mdx(\"h2\", null, \"Critical Operational Issues in an Evaluation Summary Chart\"), mdx(\"p\", null, \"COIs are copied and pasted into the Evaluation Summary Chart.\"), mdx(\"h2\", null, \"Mission Effects in an Evaluation Summary Chart\"), mdx(\"p\", null, \"Mission effects, captured as \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" for the COIs, are listed on the\\nEvaluation Summary Chart\"), mdx(\"h2\", null, \"Operational Capability Requirements in an Evaluation Summary Chart\"), mdx(\"p\", null, \"Operational capability requirements paragraph references from 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\"\n }, \"IS\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \"/\", 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\"), \" are copied into the first version of the Evaluation\\nSummary Chart (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \"-1) based on their relationship to the COIs on the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \"-2. This provides a clear understanding of how the COIs and\\noperational capability requirements relate to the operational and\\nsupport\\u2011related performance attributes of the system and provide the\\ncapability required by the warfighter. They are intended as high\\u2011level\\nplaceholders for operational test measures (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"/MOPs/MOSs) to be\\ndeveloped later during the measures workshop and refined during test\\nconcept development.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"Note: Operations and conditions (factors and levels) are not depicted\\non an Evaluation Summary Chart. However, they are part of the overall\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct and are typically provided in the test design and test\\nconcept briefings.\")), mdx(\"h1\", null, \"Test Design\"), mdx(\"p\", null, \"Test design is the second step in a test activity (see figure 8). For\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct test activity, the focus is on the test design for\\nevaluating achievement of the mission effects. The test design addresses\\nthe following areas.\"), mdx(\"h2\", null, \"Test Design Goals\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", the level of test and the kind of answer required, determine\\nthe test design goals for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"/operation and each may have multiple\\ngoals and therefore designs. In general, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses three types of test\\ndesign goals: characterize, compare, and problem identification.\"), mdx(\"h2\", null, \"Types of Test Design\"), mdx(\"p\", null, \"Choosing the most appropriate test design(s) requires expertise on the\\nsystem and the operational application it supports. An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\nprogram will likely have combinations of the designs presented here.\\nEach \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" or operation has its own test design and may have more than one\\ndesign. The result of a test design is a set of design points and the\\nrationale for choosing them. The following are typical types of design.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Demonstrations.\\xA0\\xA0\"), \"Demonstration test designs are used to\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"demonstrate whether something is possible or not.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Space\\u2011Filling Designs.\\xA0\\xA0\"), \"Space\\u2011filling designs use a variety of\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"techniques and criteria to select design points to provide\\ncoverage across the possible set of conditions.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Combinatorial Designs.\"), \" A combinatorial design employs the\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"science of systematically selecting combinations of factors and\\nlevels to provide the best chance of identifying problems. This is\\nmost often used in testing software intensive systems.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Case Designs.\\xA0\\xA0\"), \"Case designs are used to demonstrate the\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"capabilities of a system and operation under a specified set of\\nconditions. Several cases may be created using multiple methods.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Worst Case/Best Case Design.\\xA0\\xA0\"), \"One method may be \\u201Cworst case,\\u201D\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"where the conditions chosen are those perceived to be the most\\nstressing.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Special Cases Design.\\xA0\\xA0\"), \"Some special cases may be of particular\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"interest to someone (e.g., the user, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \", Congress). The\\nunderlying reason for the special case should be documented,\\nbecause experience has shown the underlying goal is to prove it\\neither works or it does not work under some specific condition of\\ninterest.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Profiles Case Design.\\xA0\\xA0\"), \"Select cases based on the\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"expected frequency of encountering the particular conditions\\nduring planned operations (e.g., from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"). The rationale\\n(besides operationally realistic) is that this would be the\\nfastest way to reveal the most operationally\\u2011relevant problems.\")))), mdx(\"p\", null, \"**\", mdx(\"br\", {\n parentName: \"p\"\n }), \"\\n\", \"**\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 8. Test Design Within the \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct\")), mdx(\"span\", {\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/3c52401eb66650bf114cbd98cbac9881/45662/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\": \"64.86486486486486%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAADsklEQVQ4y2VSW2gcVRg+hailGEUohD4oVQRpKkYwIILUglJrig+KlOKLLypFEY1Q8iYxtGkoa5oKNVVba7VG2mKMYGJITDbZ28zuzt5md247Mzu33Zmdnb3N7Oxusrkczwbtiw8f3zmcc77z/9//AcdtQ0E2YTgpQiVfhrV6Aw6P3jwCADgwdmXueCSVKyUopRxLSyUEK5aWLQJxNJUzZM3aFqT8J9s7EJCCs0+VsgAYZiWcYZUIHs/GEBNaoRjwfHPvEIQQyFqxlyBzVpJWICvqMCsVIScakBV0yAj6rlGqQ0kxZrp3EQ5oMv8I+HeDCgIP/Lc+N34H/I1Le+twQvQmaXVPLKeW9iBpFlQKZVipuzBvVBj09sGfZmbnQnhUAoZlv16tN09icfGM29p8Qzdrr0G409P9YQ2jkSA/jsWzEItlyyGCqwcRoimhTme1ml6sNHWzqpwaOnn0gudaeH7JbwOn0YLlqgNziglLZRt56MCzI9PPAPDyo0hz38xc8CwS5INRjljHmQQnFhJqwUogobhp1VOmZROXPJPHL341vb64EiwBWTVGc0phDIsxE5ygjklK/ovhL289/uSxkac6Gy5YCVKnvCF6czVEuatByvVidNMXZptpVm2iAhqomN1fZu58PDH53crKGr4BFK0I6raz55emW0DVqy/EM1Iei/MWxSnLI+O3B1GroUiCJ1D7UX+EifrCdJRICdG8bmGoUmZ51T98YWLyh0Aw5O8KPZRh1f1vfXilz3Y7PSmKf8IbiL+55I28+sfC2iA49PZ+FKlsIiPDNKs5aCiNLgrFastttrda7U1kV+E3ZE/v559+1Pu/KW9tdQCZYUFnGx4xLHfAqrovBXDyxNS3d5/1YeTpSII5E0tx7/pCiaHzl672HTz8Yi9628OyHMjnCwDU7OaPKE+3Uox2zyw7P1dqzvTXN/58GrUTiZGikGYUUVL0v27/HjiGhpGU1GISMRcn+e8v31h8bGcXvt9sdzx2o3VxY3PrBGi2NqBVsfeC252y7TSg59psv1mun4+lc1cpTptieeXc1PX5o6JsjBOkeJkT9etI8IMULb9nVRzISwYUUUpQQopgfinw3LIXG0AZGkD8/MLSev9nozcPmqXqbDiRXWb4PIs+3GFFY6FUdqAPp3CSltYoNjfZtYik+P6crL1Ds8LQr3fn+kAAT4IwQQJfKI44DfyhGECC97314enDhlllM5wKFU0PDr5y+mGnDe+fI2EgKQXA8RKYX1wF/wDyIfaJxTCoJQAAAABJRU5ErkJggg==')\",\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/3c52401eb66650bf114cbd98cbac9881/e3189/image10.png\",\n \"srcSet\": [\"/static/3c52401eb66650bf114cbd98cbac9881/a2ead/image10.png 259w\", \"/static/3c52401eb66650bf114cbd98cbac9881/6b9fd/image10.png 518w\", \"/static/3c52401eb66650bf114cbd98cbac9881/e3189/image10.png 1035w\", \"/static/3c52401eb66650bf114cbd98cbac9881/45662/image10.png 1410w\"],\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(\"h2\", null, \"Factor Management.\"), mdx(\"p\", null, \"Within the test design, for each operation, operational factors are\\nmanaged at specified levels. How they are managed will depend on the\\ntest design goal, the likelihood of encountering levels, and the\\nmagnitude of operational impacts when a levels are changed. Table 9\\nillustrates the factor management logic.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Vary factor.\"), \" If a factor management is \\u201CVary,\\u201D that factor\\u2019s\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"levels will be changed in accordance with the test design by the\\ntest team.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Fixed factor.\"), \" \\u201CFixed\\u201D factors will be set and will not change\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"throughout the test.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Log (Record) Factor.\"), \" Those factors labeled \\u201CLog\\u201D are not\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"actively managed, but the setting of that factor will be recorded\\nduring the execution of test events for possible use during\\npost-test data analysis.\")))), mdx(\"p\", null, \"Table 9. Factor Management Logic\"), mdx(\"span\", {\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/068278f9f8136483e8e782c16d2689d4/289dd/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\": \"58.301158301158296%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAABcRAAAXEQHKJvM/AAABk0lEQVQoz4VSPU/CUBRtC6190JZ+QC1SPwEFE1E0DIYEJkkIA4mLixuOht1fQEJYSBhIiCTGxcUYjYOr/8z76ql5YZAmJ33v9tzTc897krT+0QhVQomwTdglhIR91A4I6XUiKsEB0SBsEgqEIqFCOIJYiLoFrvmfYBFNFbiw0cQFAuw3UOPCW6KgvCKoEHIEH0Q+ZhYiZUSQg3MXPAdrsqNqeVmWz2l5QkhBkIHI/67j77HDHfBsfAvAVePQPcIF4QxjMDRk4IwhywRqLtYG+FnUVKlevzxsNq9avd4NP8EkRmRYJ9EkCXnl4dqBoxRGD6L9aPR4N5+/f0ynL0Pe5Hm+TuOnQNQgrkHYQWOIEeOTLfwZabe71U7nutvv35Z/M5H3MFYCQpbgkMFhARxNcB1EnMnkebBcfr2Ry3vuyrLsNDk0hbF1YXQPzXmcson84qvkSKXSsd9otE5rtUZ0Soqi2MjGhICPt44YXOwtOEzCrRPdjvH4abhYfH7PZq8PvIkcGuQwzsZEoyFcm8xKjQlc9gPldyrI+L2lyQAAAABJRU5ErkJggg==')\",\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/068278f9f8136483e8e782c16d2689d4/e3189/image11.png\",\n \"srcSet\": [\"/static/068278f9f8136483e8e782c16d2689d4/a2ead/image11.png 259w\", \"/static/068278f9f8136483e8e782c16d2689d4/6b9fd/image11.png 518w\", \"/static/068278f9f8136483e8e782c16d2689d4/e3189/image11.png 1035w\", \"/static/068278f9f8136483e8e782c16d2689d4/289dd/image11.png 1409w\"],\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, \"Table 10 reflects the typical factor management resulting from the\\nfactor prioritization discussed earlier in the guide.\"), mdx(\"p\", null, \"**\", mdx(\"br\", {\n parentName: \"p\"\n }), \"\\n\", \"**\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 10. Factor Management\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"COI 1: Can CSARL enable survivor/evader navigation to a rendezvous location?\"), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operation 1: Rescue Survivor\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOE 1: Timeliness of Rescue; MOE 2 Accuracy of Pick-up Point\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Factor\")), mdx(\"td\", null, mdx(\"strong\", null, \"Levels\")), mdx(\"td\", null, mdx(\"strong\", null, \"Prioritization\")), mdx(\"td\", null, mdx(\"strong\", null, \"Factor Mgmt\")), mdx(\"td\", null, mdx(\"strong\", null, \"Why factor is operationally important; Why level is selected\")), mdx(\"td\", null, mdx(\"strong\", null, \"Notes\")), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, mdx(\"strong\", null, \"Likelihood of Encountering\")), mdx(\"td\", null, mdx(\"strong\", null, \"Magnitude of Impact\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 1\")), mdx(\"td\", null, mdx(\"strong\", null, \"MOE 2\")), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Mode of Travel\"), mdx(\"td\", null, mdx(\"p\", null, \"Vehicle\"), mdx(\"p\", null, \"No Vehicle\")), mdx(\"td\", null, mdx(\"p\", null, \"Frequent\"), mdx(\"p\", null, \"Seldom\")), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"Vary Vary\"), mdx(\"td\", null, \"Affects the survivor\\u2019s ability to move from the area.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Battery Type\"), mdx(\"td\", null, mdx(\"p\", null, \"Rechargeable\"), mdx(\"p\", null, \"Non Rechargeable\")), mdx(\"td\", null, mdx(\"p\", null, \"Frequent\"), mdx(\"p\", null, \"Seldom\")), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"Vary Vary\"), mdx(\"td\", null, \"Ability of the survivor/evader to have communications.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Terrain\"), mdx(\"td\", null, mdx(\"p\", null, \"Flat\"), mdx(\"p\", null, \"Mountainous\"), mdx(\"p\", null, \"Littoral\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, mdx(\"p\", null, \"Vary Vary\"), mdx(\"p\", null, \"Demo\")), mdx(\"td\", null, \"Difference in the terrain could affect the survivors\\u2019 ability to move or platform recovery.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Time of Day\"), mdx(\"td\", null, mdx(\"p\", null, \"Day\"), mdx(\"p\", null, \"Night\"), mdx(\"p\", null, \"Transition\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"Vary Vary Demo\"), mdx(\"td\", null, \"Night time could affect the ability to see the survivor/evader.\"), mdx(\"td\", null, \"The CT should document notes for each F&L set.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"High\"), mdx(\"p\", null, \"Low\")), mdx(\"td\", null, \"Balanced\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"Vary Vary\"), mdx(\"td\", null, \"This would affect the platforms ability to reach location.\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Disruptive Cyber Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"Yes\"), mdx(\"p\", null, \"No\")), mdx(\"td\", null, \"Common\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, mdx(\"p\", null, \"Fix\"), mdx(\"p\", null, \"Demo\")), mdx(\"td\", null, \"Will have to look at mission planer vulnerabilities.\"), mdx(\"td\", null, \"Fix at Yes.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Non Disruptive Cyber Threat\"), mdx(\"td\", null, mdx(\"p\", null, \"Yes\"), mdx(\"p\", null, \"No\")), mdx(\"td\", null, \"Common\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, mdx(\"p\", null, \"Fix\"), mdx(\"p\", null, \"Demo\")), mdx(\"td\", null, \"Look at possible mission effects.\"), mdx(\"td\", null, \"Fix at Yes.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Software Version\"), mdx(\"td\", null, \"Given\"), mdx(\"td\", null, \"Givens not prioritized\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"Log\"), mdx(\"td\", null, \"Complete instructions on how to plan and operate system, also affects maintenance.\"), mdx(\"td\", null, \"Latest version.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Training\"), mdx(\"td\", null, \"Given\"), mdx(\"td\", null, \"Givens not prioritized\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"Log\"), mdx(\"td\", null, \"Platform dependent, survival or equipment related capabilities.\"), mdx(\"td\", null, \"Both survivor and recovery team have training.\")))), mdx(\"h2\", null, \"Unconstrained and Constrained events\"), mdx(\"p\", null, \"In prioritizing the factors and determining factor management, the\\nentire set of possible test conditions has been filtered into a smaller,\\nmore manageable and executable set of test conditions. The process\\ncontinues by introducing constraints and picking an appropriate test\\ndesign or set of test designs. Test design requires a discussion on\\nfactor constraints. The core team will examine all of the possible\\ncombinations of factor levels and specify which are infeasible due to\\noperational or physical constraints.\"), mdx(\"h2\", null, \"Statistical Measures of Merit\"), mdx(\"p\", null, \"All test designs have associated measures of merit, or quality\\nindicators, and most are grounded in scientific statistical\\nmethodologies. The measures of merit should be considered when deciding\\non a test design. Regardless of chosen design type, there is a related\\nmeasure of merit which should be a consideration addressed in the test\\nplan documentation. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Design Guide has more information on\\nstatistical measures of merit and their applicability to different\\ndesign types.\"), mdx(\"h2\", null, \"Test Events\"), mdx(\"p\", null, \"Any single design results in a set of test events. A single test event\\nis defined as a single execution of a test to collect data with the\\noperational factors set at a single, given level (i.e., a single\\ncondition or design point). Table 11 continues the survivor/evader\\nnavigation example introduced earlier. In this example, the team has\\ndecided the type of answer they wanted to provide was to characterize\\nthe system\\u2019s behavior. Consequently, a characterize design matches well\\nwith the desired type of answer. Other factors are fixed.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 11. Example \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Test Events to Recover Isolated Personnel\")), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Test Event\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Mode of Travel\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Battery Type\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Terrain\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Time of Day\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Threat\"))), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Characterize\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\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 }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), 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 }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), 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 }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), 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 }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"6\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"7\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"8\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"9\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"10\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"11\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"12\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mountain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Problem \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Identification\"\n }, \"ID\"), \"\")), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"13\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Littoral\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Day\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"14\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"No Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Non-rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Flat\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Transition\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"15\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Vehicle\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rechargeable\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Night\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"If multiple test designs are created, such as a characterize design\\nsupplemented with a case design, the total number of test events\\nincreases. Similarly, the total number of test events increases in\\naccordance with test events that are replicated.\"), mdx(\"h2\", null, \"Test Design Validations\"), mdx(\"p\", null, \"Testing evolves continuously and it is expected that test designs will\\nchange. Most of the design evolution is managed by the test teams during\\nthe normal testing ops. However, a test design validation is a more\\nformal effort that generally occurs at the request of a Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"\\nand is usually employed when the test design is significantly outdated,\\nwhen there have been major changes in the scope of an acquisition, or\\nwhen earlier test design documentation is not sufficient/available. The\\nscope of a design validation depends on the test team needs. It could\\nrequire all of the step leading to a test design or only specific pieces\\nof the test design to be readdressed. When making a design validation\\nscope determination, keep in mind that most of the steps build on one\\nanother. Formal test design validations should be requested by the\\nDetachment through the A\\u20113 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \".\"), mdx(\"h1\", null, \"Measures Development\"), mdx(\"p\", null, \"This section discusses the process for refining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", developing\\nmeasures of performance (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \"), and measures of suitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \"), and\\nidentifying the associated data elements. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are identified during the\\nearlier battlespace development effort and refined during a measures\\nworkshop (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \"). See the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Measures Guide for additional details. In\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", measures are developed using a top-down and bottom-up approach.\\nThe top down approach is most useful for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" development and the\\nbottom-up approach is effective when developing MOPs and MOSs. Figure 9\\nillustrates where measures fit in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E construct.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 9. Measure development in the \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct\")), mdx(\"span\", {\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/884fffcade99ca845f2e3cc372cc89d9/45662/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\": \"64.86486486486486%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAADq0lEQVQ4y2VSa2gcVRj9kkYsYrFCIYgPRARpFKM0goJowVet+qMgJYgggooVhIr1R/0hIUgoGKwRWoNGa5EYNRKiddOaNOa1u5nNzuy8dnZnH7Pz2p3Z2ZnNzs7u7Gbzut4NtX/8cTj3MnPPvd85B7x6E2UVC0UYCal5B1XcGvpo4NJhALhtcGT66BqbK9GC6lC8XMKwKV6xScxRNmcqur2dlfMfNpotcL3GvqePvQ1gWuVIXFTXiFiawkzqhWJw+OLkXQghUPTiAZLL2UxCRaJkoLRcRCnJRGLWQMmssWuWXCRr5nj7X4yOyT/mAW5s8IPglv/WZ4Z+hXlC3ltHaGmBSWh7YjnNxighWbeRWnDQuusj3bBFgEOdJ948AzSfASja3ktOpX4sSGb6Xa/5smFVnkdoq6t9w+JqAohYZihMpRCGE4yKbhtRNusm0nrFtNbreqGUHxkd7748cQWmrsx3gFdroCpGobiOXM/HHnrog7OjDwEcvQNrdkwGiPdpQcng0UmKz9E5zaJ1w6ELxXLMsl3awHx9iXx8OczACsF2gqIZA6puDkaZ9DlJKQzKav6zU5+O3Xv3kx8/0B45RKZficXlFsXl6jFerjOC4vOi5ufNsl+p1r1iqYIoRuwnGREoNrWvbTz4fn3Pr7zpQDJrHpkPCfmZBdaO0Om5s+d+7rse5MNLRIJcjiSjcytc9OoCHV1cFaJaoRTGZ0RWyJ5yay2oNbY720K3Cilt/4n3Rrp3EOqK0sn7/l5Ye+3Pa6Hnfpma64ODr+6fW4mnl4gkwq/1OFGrJdL5Gk69YZe9rebGJlI08/cbgXb9L+VWawMiFA/bu+iwVfZ7nYr/VCjCvTh8YeKRxTB7EifZz8azb0RI/vjXF3/oPnjPEwfaZ+v+Bmxu7QBUqv6PuE+X2aQ+aTneT+WK983I9389iOuwRnFSlk+qkqwaV8enQ8/oBZvJqUVGK9gpik1/98W3M3fu7KJ3Gs3N4Vq9OdTa3HkB/MYGssvVveKWnCqqejU0PDrVYznu5zjVC0JK/0rMqJ+cHws8LCnmEMlJ51OSMRbjMu+yCeUtPDbKyCaSVKvdkCIEZoOPzi2s9gZmV3oxPzYzu9RzeuDSIau0PtUOJZnJi/jCHVEyZ0qOh5YJgeAS8qIg5r5sW8QJmZ6cor+eELPHJ36b7oYgwUCE5GA5HMPMw0qYAix409tlgr8fF1iMpzSk6kao79mTt3tNdPM7FgZZLUAqI0Pg2j/wL0UM9nHBBaToAAAAAElFTkSuQmCC')\",\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/884fffcade99ca845f2e3cc372cc89d9/e3189/image12.png\",\n \"srcSet\": [\"/static/884fffcade99ca845f2e3cc372cc89d9/a2ead/image12.png 259w\", \"/static/884fffcade99ca845f2e3cc372cc89d9/6b9fd/image12.png 518w\", \"/static/884fffcade99ca845f2e3cc372cc89d9/e3189/image12.png 1035w\", \"/static/884fffcade99ca845f2e3cc372cc89d9/45662/image12.png 1410w\"],\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, \"Measures of performance 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\"), \") are initially\\ndeveloped in a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" facilitated by A\\u20112/9 with A\\u20113 and Detachment\\nparticipation. The optimal time for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" after the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct is approved and a draft \", 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\"), \", or an equivalent document,\\n(e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Form 1067, A\\u2011spec) is available as the source document for\\ncapability requirements. Measures development can also be triggered by\\nimmediate need.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"Measures are expected for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" B/C TEMPs, test concept\\nbriefings, and all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assessment and test plans. For \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \" TEMPs\\nthat are too early for a Measures Workshop, an initial measure set\\nwill be developed by A-2/9 (working with the detachment and the Test\\nTeam as input to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \".\")), mdx(\"p\", null, \"Measures of effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \") are the measures related to the\\ncapability to accomplish an operation. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" directly determine the\\ndegree of the desired effect achieved for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \".\"), mdx(\"p\", null, \"Measures may also be associated with the operational capabilities that\\ncontribute to a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" being satisfied. Measures of Performance (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \") are\\nthe measures related to the system\\u2019s capabilities, features, functions,\\nand properties enabling the effects to be achieved. Measures of\\nsuitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \") are the measures related to the degree to which a\\nsystem can be placed satisfactorily into field use. Additional\\ninformation on MOPs and MOSs can be found in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\xA063\\u2011101/20\\u2011101\", \"_\", \"AFGM\\n2016-01, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Life Cycle Management\"), \", 9\\xA0May\\xA017; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\xA099\\u2011103, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Capabilities\\nBased Test and Evaluation\"), \", 6\\xA0Apr\\xA017; and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Pamphlet\"\n }, \"AFOTECPAM\"), \"\\xA099\\u2011104, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nOperational Suitability Test and Evaluation Guide\"), \", 24 Sep 13, etc.).\\nTest teams should consult the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Measures Guide, their Detachment\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \", and A\\u20112/9 for current best practices on the development of measures.\\nProposed exceptions to these best practices should be discussed with\\nA\\u20112/9 before developing measures. Generally, the desired outcome of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \"\\nis a complete set of measures for the test activity with defined scopes\\nfor each measure.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" are meetings facilitated by A-2/9 and A-3. Major stakeholders in\\nthe acquisition program are invited: the user community, the program\\noffice (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Office OR Project Officer\"\n }, \"PO\"), \"), \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \", system developers, and developmental testers. All\\nparticipants apply their subject matter expertise toward the goal of\\ndeveloping a measure set and test designs. Generally, the Detachment,\\nA\\u20112/9 and A\\u20113 do \\u201Chomework\\u201D prior to the workshop. A\\u20112/9, with inputs\\nfrom the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" or technical advisor, develops draft measures in\\npreparation for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" meeting. The purpose of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" preparation before\\nholding the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" meeting is to save time and level of effort.\"), mdx(\"h1\", null, \"Test Execution Planning\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" core team members will usually meet informally to continue\\nbuilding upon the information compiled during the Battlespace\\nDevelopment, initial test design, and measures development. This is\\nreferred to as execution planning (see figure 10). The purpose of these\\nfollow-on meetings is to finalize the test construct such as refining\\ntest design worksheets, identifying test methodologies, creating test\\nscenarios, and identifying resources.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 10. Test execution Planning in the \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct\")), mdx(\"span\", {\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/3ff8742e484549c66f3022e8c4ce41e9/45662/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\": \"67.56756756756756%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAYAAAAvxDzwAAAACXBIWXMAABcRAAAXEQHKJvM/AAAD9klEQVQ4y01Ta4hUZRh+XUf8YQtFEYoU3aAflUWWFmkhRau0Bom74iZtWllpUCFSsKkRBmtQQoSZJN1cNXdbXXWN2WWdy87szM7MnrmcuZ2ZPdc595lz5nJmxnXX5es7g1QHXt7ng4/ne973eQ5Y9TlEZkU0Q3JILVZRuWKJDzy3936Atvb+H692hBOsEc8IxViKLxJJ7t/C97U8q87xBW0IIQS42jq3vwsgKsUYQdLxqUiWpGgxIyn6lXUd++9yeachnmJXhhOMHkvzKJ2XEMUoKDMrt7BdvFRCimbSO/Z83t774SE4Pzy2BG6zA/5W/IdXgStILbFxgJidno7RLYJZTkNYVaszgt6aSNXLyOWLrnH7oxCOZduAEYrPiIr57OBoaLOiV9dRjPy4zW6TnbscACLJfjtDsrciCaYYjtNmKEabsRRn5hjF1EqVYrlaXwhH050FSQdZLbXBwq1FVK01kaxX0NzNBWTVm9q9a3ofvGftp3dj3uW/D3k/8oezlDuQjLgDKSKeZgm8GiLPSATNyRFWUCl/iHybF3XA1QaKVhoQZX0gRfEXMB4UJbUf4JE7ATasqDcaMBmitiayAsJG1HBvxNN8I5UTGwXZaFStZq1mNRE1K5xSNANzGUv/v8M77J7OCa/jEZORBJukOeX0/r5T67FCT5CgfNPR3KR3Ou3zBlM29hVk3YPHnMnRwonbPC1Tltm1ufe7VQDtQGa5F8e90f7RichRbyC+9+DRX1fjBwysEMergPDuWsbYphhlC1mNG0jWjNrxEwMrt791AMdGLQMrlmyFyzjRAIZXYcxDwE9//A3n/hq3H3T4Q8kt2MkeIkH1SLK6S5SUXRwv9pDpfHeMpLZNBohXbIU0J7UIu3AMdji95Pu8ZPRIivGy0x19givo5IQ/SeHIzMqqMXj2oudRnENnOi8GKVoJkRn+ChbhsJVgX9ffmJt/tVxtrIZavYkIkkW+cA7xYgnVrHr5k8MnHyMz3JfXffFjnmDyWDiaPbSv7/SGwEy2PziT+SYSzx93T8UP/jbo2qSXqlYCr8L+00TFWARR0o4wnHQkm+cPFyTta5oV3js/MvkUdjA7FckJyZyomRWLJEjmQEEx2Ql/SgzFGEXRyuFQNPfwzfmFd1TdPKsVzQuCqH4B1VoDZM3EAdegUmuCpBShIPBL/xy+9tAbvX33OV2RN3mxiFyBDGJ4BZ0ZHHvt0qjrY+eEX73qnBwfueYewudLuF8fvnj5AzArdYekmg6uUHSUTMuBY+BAi/MwMuqC738ehs++Ogl8QX6JSOT2Jcj0pjPDHhj45YflW7Z2Pd3R2fV8d8+ejV07d7+wrbt3Y1f3zif/AXmSHjeEvrexAAAAAElFTkSuQmCC')\",\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/3ff8742e484549c66f3022e8c4ce41e9/e3189/image13.png\",\n \"srcSet\": [\"/static/3ff8742e484549c66f3022e8c4ce41e9/a2ead/image13.png 259w\", \"/static/3ff8742e484549c66f3022e8c4ce41e9/6b9fd/image13.png 518w\", \"/static/3ff8742e484549c66f3022e8c4ce41e9/e3189/image13.png 1035w\", \"/static/3ff8742e484549c66f3022e8c4ce41e9/45662/image13.png 1410w\"],\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(\"h2\", null, \"Test Methodology\"), mdx(\"p\", null, \"Test events may be executed through a variety of methods. Replicating a\\nrealistic mission or mission segment should be used whenever feasible.\\nReplicating a realistic mission does not have to focus on the engagement\\nor battle outcome level (full engagement level of testing can be cost\\nprohibitive), but should provide the means to evaluate the operational\\neffectiveness and suitability of the system or subsystem in\\noperationally realistic conditions. Additionally, it should provide a\\nmeans to determine overall mission capability. Testers create controlled\\ntest scenarios to reflect the conditions that best evaluate the system.\\nField testing is a good, initial choice for operational testing as it\\nprovides the most operationally realistic environment. However, field\\ntesting is not always feasible to capture all test events. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" provides\\nanother venue for executing test events (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"United States Code\"\n }, \"USC\"), \", Title 10\"), \" imposes\\nconstraints on the use of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" during operational testing) and may\\ninclude distributed test applications using live, virtual and\\nconstructive (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \") simulation assets. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" requirements should be\\ndetermined early in order to become part of the system development\\ncontract. Other test methods include studies and analysis, exercises and\\ntraining opportunities. The test methodologies may be a combination of\\nthese methods during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". For example, early in a program,\\nyou might use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to help identify important operational factors to\\ninclude in an Early Operational Assessment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \") or Operational\\nAssessment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \"). Execution of test events during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \" is followed\\nby some analysis highlighting that some factors may not be important\\n(and possibly identify new factors). The revised set of operational\\nfactors is then used in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E.\"), mdx(\"p\", null, \"If test capability requirements (to include modeling and simulation) are\\nidentified during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct development, accreditation activities\\nare required. Identification of test capability requirements will result\\nin the development of an accreditation memo. The memo identifies the\\ntest capability requirements, accreditation documentation requirements\\nand format, timelines, the accreditation authority and other pertinent\\ninformation. The memo is increasingly important because it initiates\\ndevelopment of the accreditation plans and begins tracking \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" resource\\nexpenditures including manpower and dollars.\"), mdx(\"h2\", null, \"Test Scenarios\"), mdx(\"p\", null, \"Test scenarios capture the end\\u2011to\\u2011end flow and reintroduce the factors\\nidentified during the battlespace development and test design. During\\nthose earlier steps the operational factors were used to identify\\ncondition based test events. These events must be translated into\\nrepresentative operational test scenarios (figure 11). Test events\\nshould be executed in in the most representative scenarios possible.\\nThis allows the best evaluation of a system by replicating a realistic\\nmission or mission segment. Test scenarios should allow all key factors\\nidentified in the condition-based test event to be exercised.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 11. Test Events and Scenario Linkage\")), mdx(\"span\", {\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/7816b04b8896b481dd69bc60ce7b5cae/c1b63/image14.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\": \"31.27413127413127%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAGCAYAAADDl76dAAAACXBIWXMAABcRAAAXEQHKJvM/AAABlklEQVQY0zWRz0sCQRTHpwihe5fAS5oEgf9Mhy4dpJPHTl2Ejh6joFQCO4TgPZUuogdDjUz8RSvtqgcV8UfmllE7u7Pz+q7QwJf3mHnzfZ95w7LZ7Em9Xr9otVqXUtJKhiEuLVNeWJaMCCFPiZbrRMQ0TVubzWas0+l4e73ewXA4PO/3+8nBYJBHfhUOhzdYtVolVVWpVqvRYqET5ybBlCwhESXZtlRhtu73+1g8HmeZTGabc/6ORYAgRVGo2+2SEMLJo6zdbj/N53OJyBXl1VTVNxMXTHgZMEOh/RIIHG36fHsuh3I0Gt0iEkCMQqEgisWiyOfzHFsSYN+sUqmsujQaDVouv0n//KJfwwQZrQgty26GQmeuYDD4b3ht4xAAJghls9kU4/GYAEXpdPqelcvl4+l0OptMpl+o03FJBz0kPyAOykfnyQwrGo2wXC7nwdweIMI8MaaFYz7GKO6chiyRSDAkO5DXMCzPzw9HFF58iAd7u5Bb056dGlYqldbwIas8Fovtp1Kpw2QyeeN2u7d0XXd6sj/dNXcDy+eY5QAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image14\",\n \"title\": \"image14\",\n \"src\": \"/static/7816b04b8896b481dd69bc60ce7b5cae/e3189/image14.png\",\n \"srcSet\": [\"/static/7816b04b8896b481dd69bc60ce7b5cae/a2ead/image14.png 259w\", \"/static/7816b04b8896b481dd69bc60ce7b5cae/6b9fd/image14.png 518w\", \"/static/7816b04b8896b481dd69bc60ce7b5cae/e3189/image14.png 1035w\", \"/static/7816b04b8896b481dd69bc60ce7b5cae/c1b63/image14.png 1200w\"],\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, \"Test scenarios may include test events supporting multiple measures or\\nCOIs. Thus, one scenario may satisfy the completion of multiple test\\nevents simultaneously (Figure X). Evaluating a system by replicating a\\nrealistic mission or mission segment should be used whenever feasible.\\nMission replication should provide the means to evaluate the operational\\neffectiveness and suitability of the system or subsystem in\\noperationally realistic conditions. Realistic threats, including cyber\\nthreats, should be drawn from the latest intelligence sources for the\\nemploying commands. Core teams create controlled test scenarios that\\nreflect the operationally realistic conditions to best evaluate the\\nsystem. Defense business systems testing will include theft/fraud test\\nscenarios.\"), mdx(\"p\", null, \"The intent is to identify test scenarios that allow for an end\\u2011to\\u2011end\\nflow from one \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" to the next, as well as for concurrent COIs. Within\\nthe test scenarios, factors are set to the appropriate levels called for\\nby each test design. It is important to realize that the levels may be\\ndifferent or vary from scenario to scenario. For example, an F\\u201116\\nconducting a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue\"\n }, \"CSAR\"), \" scenario is unlikely to fly at high altitudes; thus,\\nthe level for altitude is set to low and another scenario (such as a\\nstrike scenario) is used to capture altitude at its high level. Another\\napproach would be to select a set of test scenarios that allow all the\\ntest events (described by the factors and levels) to be executed within\\nthe scenarios. Selecting test scenarios appropriately allows for\\nefficient use of test resources, as well as presenting an operationally\\nrealistic test environment. Proper scenario selection also helps avoid\\ntesting in independent segments (e.g., COIs) when there are actually\\ninteractions between these segments. However, not all test events are\\nlikely to be executable as part of one overall scenario or set of\\nscenarios. Expect some test events to require separate, specific\\nportions of a scenario to establish the necessary operational\\nconditions. A consequence of identifying end\\u2011to\\u2011end flow and interaction\\nbetween COIs is that test events are overlapping and occurring\\nsimultaneously. For example, the same F\\u201116 sortie that captures two\\ntargeting test events (one in mountainous terrain, the other in flat\\nterrain) also captures a mission\\u2011planning test event and a weapons\\nload\\u2011time test event. These events all take place within the context of\\na \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue\"\n }, \"CSAR\"), \" scenario where the particular operational factors are set to\\nlevels consistent with a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Search and Rescue\"\n }, \"CSAR\"), \" scenario. Figure 12 reflects this concept\\nof end-to-end threads across COIs\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Figure 12. End-to-end threads across COIs\")), mdx(\"span\", {\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/99815a5456ca70df67c2d114b4552b48/29c1d/image15.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\": \"31.27413127413127%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAGCAYAAADDl76dAAAACXBIWXMAABcRAAAXEQHKJvM/AAAB00lEQVQY02OYuG8Tw/plK/hu3bxZd//evbWvXr5c8OLlS5X///8zLLl8jiln7lYmEBuGZ9w/y5h3Yitjy9r9EPGfXxk+P3/N0HXzBAPDfzkGBue7K4QW7jm+f/Pha/+3n7z+//rLZ3+fPnrkVPf8GEPlod0Mfv0bQAYJA7EoELP23j3JkH1yK0PbhkMgce7//36Ifn/+VrDw2kEGvhdrGRjSru20O3XkRNfpk2cPXLtw5fj+Z3dSV908F73vzuWApWdPuh25fn/6tcev7j148+bzjVdP5yy5fMJqw9VznrvOXp146trdl5fv3v926/GD/unnDnM/vHuPn8H0wnKdNacvxV64/+LEnWdvH116/fTziptno4U/r+SaumNPwMbdZ/5v2nP+/+lrd75f/foyguvgZP7SvZvVeubtnNM7d8+aGWsO1Na/2CPMsKWBBRQEDP8X/GdYsHHv5nXbT/zfsOvE/6uPHq5jEGFg6N6/niErKFRy9pSJ8fNmTMmqKsi3AWmwW9XPMO3/L3B4AgEjiO7avwZoEANErGTVdIY9K5cor1g4y29yd5sfUBHvoq5ehhWXjzGBdMAiAwSK+9uZE/+/YSi5fhhkEBwvunKYkaEZohYAcogmu/WFLxAAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image15\",\n \"title\": \"image15\",\n \"src\": \"/static/99815a5456ca70df67c2d114b4552b48/e3189/image15.png\",\n \"srcSet\": [\"/static/99815a5456ca70df67c2d114b4552b48/a2ead/image15.png 259w\", \"/static/99815a5456ca70df67c2d114b4552b48/6b9fd/image15.png 518w\", \"/static/99815a5456ca70df67c2d114b4552b48/e3189/image15.png 1035w\", \"/static/99815a5456ca70df67c2d114b4552b48/29c1d/image15.png 1375w\"],\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, \"Test scenarios also allow the re\\u2011introduction of the operational factors\\nthat were set aside earlier. These are the operational factors likely to\\nexist in the operational environment, but at a given level or minimally\\nrelated to the system. These are included in the test scenarios to\\nensure operationally realistic conditions.\"), mdx(\"h2\", null, \"Test Capability Needs and Shortfalls\"), mdx(\"p\", null, \"Execution of operationally relevant \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E will normally require test\\ncapabilities. This section only discusses test capabilities and\\naccreditation to the extent needed for an initial test design. For more\\ndetails see the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Capabilities Guide and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nAccreditation Guide. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not own or operate test ranges,\\nfacilities, or assets and must identify test capability resource\\nrequirements as early as possible to ensure they are available, and\\ntechnically and operationally sufficient, for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E purposes. The\\nbattlespace development and test design processes defined the test scope\\nand methodologies and is the foundation for identifying test capability\\nrequirements. Table 10 shows typical test capability requirements.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 10. Typical Test Capabilities\")), mdx(\"table\", null, mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Test articles\")), mdx(\"li\", null, mdx(\"p\", null, \"Test sites\")), mdx(\"li\", null, mdx(\"p\", null, \"Test instrumentation\")), mdx(\"li\", null, mdx(\"p\", null, \"Test support equipment\")), mdx(\"li\", null, mdx(\"p\", null, \"Threat representation\")))), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Test targets and expendables\")), mdx(\"li\", null, mdx(\"p\", null, \"Operational force test support\")), mdx(\"li\", null, mdx(\"p\", null, \"Models, simulations, and test beds\")), mdx(\"li\", null, mdx(\"p\", null, \"Joint operational test environment\")), mdx(\"li\", null, mdx(\"p\", null, \"Special requirements\"))))))), mdx(\"p\", null, \"Requirements that cannot be met by existing test infrastructure and\\ncapabilities must be identified to A-5R. Gaps/shortfalls associated with\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \" should be addressed through A-8Z. Test capability requirements are\\naddressed in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Resource Plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \") and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses a\\nTime-Phased Investment Planning Document process to advocate for test\\ncapability development. For test capabilities that may require foreign\\nthreat capability, contact \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2N to request and advocate for\\nforeign assets through the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" foreign materiel program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Flight Manuals Program OR Foreign Materiel Program\"\n }, \"FMP\"), \") process.\\nThis process acquires and exploits foreign systems for testing, training\\nand intelligence purposes and may satisfy a threat test capability need.\"), mdx(\"h3\", null, \"Time-Phased Investment Document\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" T-PhID (formerly Test Capability Roadmap) serves as the\\ncornerstone of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\u2019s test capability investment strategy. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" must\\ncommunicate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" requirements 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\"), \" investment forums. Test\\ncapability development must be funded in appropriate investment\\nportfolios to ensure the needed capabilities will be in place, verified,\\nand validated in time to support the test. A-5R continuously gathers \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nrequirements (test capability gaps/shortfalls) through:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Individual program test capability readiness assessments (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessments\"\n }, \"TCRAs\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"SharePoint interface used for spontaneous/asynchronous\\nidentification of requirements by test teams\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"An annual requirements call closely aligned with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \"\"))), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"Test capability requirements priorities are approved by \", 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\"), \"\\nannually, in time to support \", 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\"), \" investment planning processes.\\nSome of the test capability investment forums are listed below.\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Investment Planning and Programming (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Investment Planning and Programming\"\n }, \"TIPP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Central Test and Evaluation Investment Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Central Test & Evaluation Investment Program\"\n }, \"CTEIP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Resource Enhancement Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Resource Enhancement Program\"\n }, \"REP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Threat Systems Working Group (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Threat Systems Working Group\"\n }, \"TSWG\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Joint Aircraft Survivability Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Aircraft Survivability Program\"\n }, \"JASP\"), \")\"))), mdx(\"p\", null, \"A-5R coordinates communication of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test capability requirements to\\nthese investment forums, coordinates review of development proposals to\\nidentify those that may satisfy \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" needs, and monitors program\\ndevelopment ensuring fulfillment of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" needs including completion of\\ncapability verification and validation. There are numerous range\\ncapability requirements that must be addressed as early as possible.\"), mdx(\"h3\", null, \"Determining Range Requirements\"), mdx(\"p\", null, \"In building a mission scenario and determining range requirements, the\\ntester needs to know, for example, the type of target, the number of\\naircraft attacking a target and weapons employed. The tester also needs\\nto consider the range\\u2019s ability to accommodate the operational test\\nwithout environmental impact. The system \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" should contain\\ninformation such as specific tactics and techniques to be employed\\nagainst certain targets and threat systems. Ensure that range personnel\\nhave a full understanding of the specific \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives. The core team\\nshould consult with A\\u20118Z (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operating Location\"\n }, \"OL\"), \"\\u2011NN post-tasking order) for testing\\nconsiderations at \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \" and A\\u20115R for any other test range or facilities.\"), mdx(\"h3\", null, \"Range Requirement Identification\"), mdx(\"p\", null, \"Carefully thought\\u2011out mission scenarios provide the test team with\\npreliminary test range resource requirements (e.g., threat simulators\\nand instrumentation packages). Early identification of these\\nrequirements is extremely important for advanced range scheduling, test\\nresource plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \") development, and incorporation of new range\\nrequirements into the various range improvement programs and other\\ninvestment forums (need at least 1 year lead time). In support of the\\ncore team, A\\u20115R (A\\u20118Z for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Nevada Test and Training Range\"\n }, \"NTTR\"), \") provides information on current and\\nlegacy \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" databases that archive data on existing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" test assets\\nand is the Air Force\\u2019s focal point for integrating new \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" range\\nrequirements into the range improvements program. All potential test\\nsites should be considered before the final selection is made.\"), mdx(\"h3\", null, \"Range Selection Considerations\"), mdx(\"p\", null, \"The Test Team may have to give special consideration to test range\\nselection and use. Usually, flight test programs require scheduling of\\nand coordinating with test ranges for some or all test sorties. Test\\nteams need to ensure range availability at the time of their scheduled\\ntest. All major ranges and centers are subject to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" uniform\\nfunding policy and require formal documentation of the test and the\\nsupport needed. The range, in turn, provides a statement of their\\ncapability to support the test. The range process can take 6 months or\\nmore. Although documentation requirements vary among the ranges and\\ncenters, most require the development of a Program Introduction Document\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Introduction Document\"\n }, \"PID\"), \"). When selecting a range, ensure the availability of applicable\\nrange data is considered. To determine specific range initiation\\nrequirements, consult the Universal Documentation System Handbook\\n501\\u201108, available from Secretariat, Range Commanders Council,\\nTEDT\\u2011WS\\u2011RCC, White Sands Missile Range, New Mexico 88002\\u20115110.\"), mdx(\"h3\", null, \"National Cyber Range Considerations\"), mdx(\"p\", null, \"The National Cyber Range (NCR) provides test teams with a capability to\\naccomplish system training and perform disruptive and non-disruptive\\ncyber-attacks on a complete or sub-component of a system under test at\\nmultiple classification levels. The NCR\\u2019s system reset capabilities make\\nit possible for cyber attackers to completely disable or even\\ncatastrophically damage a system without the risk of negatively\\nimpacting operational users or causing unrecoverable damage to the test\\nenvironment. This environment also provides a means for cyber offensive\\nand defensive training as well as basic user training before or during\\ntest execution (to include cybersecurity assessments). As the NCR is a\\ncontained range, connections with outside systems may need to be\\nemulated. Having said that, events can occur exclusively at NCR, or in\\nconjunction with other Joint Mission Environment Test Capability or\\nJoint Information Operations Range nodes. However, programs using unique\\nsystems (i.e., components that won\\u2019t be used by any other programs in\\nthe future) may incur a cost of purchasing the necessary hardware and/or\\nsoftware. Test Directors interested in learning more about the NCR or\\nseeing if the NCR can support their program can contact the NCR directly\\nat \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:osd.pentagon.ousd-atl.mbx.trmc-ncr@mail.mil\"\n }, \"osd.pentagon.ousd-atl.mbx.trmc-ncr@mail.mil\"), \".\"), mdx(\"h3\", null, \"Test Targets\"), mdx(\"p\", null, \"Test targets, when applicable, should be realistic; they should be\\noperationally representative and challenging. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should coordinate\\nwith the applicable \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \" to develop the target list. Through A\\u20112N,\\ncoordinate with the appropriate intelligence agency on the design of\\nselected targets, existing and newly developed. A\\u20115R maintains current\\nlists of available aerial test targets in the inventory and is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \"\\nfor obtaining target allocations. A\\u20115R also maintains contacts for other\\ntarget types such as surface targets. Funding for target\\u2011related\\nexpenditures must be included in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \".\"), mdx(\"h3\", null, \"Range Safety Considerations\"), mdx(\"p\", null, \"Ranges and test centers are sensitive to safety considerations and may\\nrequire special test procedures, hardware, or software to reduce the\\nrisk of a mishap during the test. Ranges and test centers frequently\\nrequire safety review boards before start of testing. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should\\nallow sufficient time to support these safety reviews. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" can assist in\\nresolving range safety issues or support in safety reviews. When\\nidentifying required test resources and range requirements, test teams\\nshould ensure weather warnings and advisories are considered in support\\nrequirements (contact A\\u20112/9 for assistance).\"), mdx(\"h3\", null, \"Range Instrumentation Considerations\"), mdx(\"p\", null, \"Instrumentation varies widely among ranges. Therefore, the test team\\nshould carefully select a range to ensure instrumentation is available\\nto provide the required information and to allow the most realistic\\nrepresentation of the operational environment.\"), mdx(\"h3\", null, \"Range Data Processing Considerations\"), mdx(\"p\", null, \"Data processing capabilities and times are considered when the test\\nschedule is prepared. The range equipment user\\u2019s guide, facilities\\nhandbook, or the test support contact may be consulted for typical\\nprocessing times. TDs must also consider the method by which test data\\nis transmitted for analysis (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secret Internet Protocol Router Network\"\n }, \"SIPRNET\"), \", courier, etc.).\"), mdx(\"h3\", null, \"Test Article Instrumentation\"), mdx(\"p\", null, \"Identify the test article instrumentation requirements early to ensure\\nthat instrumentation is sufficient to support test events. There is a\\nfine balance between not compromising the production\\u2011representative test\\narticle and obtaining telemetry from an instrumentation package. Test\\narticle instrumentation should be compatible with the range or test\\nfacility telemetry and data collection systems, with sufficient accuracy\\nand sample rates to enable verification of system performance. If the\\ntest article needs to transmit instrumentation data, the instrumentation\\npackage needs to be compatible with the MIL\\u2011STD\\u20111553 multiplex data bus.\"), mdx(\"h3\", null, \"Program Introduction Document Release Authority\"), mdx(\"p\", null, \"PIDs are executing direction approved in TRPs for obtaining test range\\nsupport. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/CCs are authorized to release PIDs to range agencies.\\nCopies of all PIDs are sent to 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\"), \", A\\u20113 and A\\u20115/8 when\\nreleased to range support agencies by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \". Issues identified\\nduring subsequent \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Introduction Document\"\n }, \"PID\"), \" coordination with the supporting range are\\nhighlighted during the Detachment Commander Monthly Program Update.\"), mdx(\"h2\", null, \"The Use of Modeling and Simulation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" includes, but is not limited to, digital \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \", hardware\\u2011in\\u2011the\\u2011loop\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware in the Loop\"\n }, \"HITL\"), \") virtual simulations and test drivers such as data injectors and\\nstimulators. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" also includes physical models of targets, threat\\nrepresentations and combinations of simulations. Testers (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live Fire Test and Evaluation\"\n }, \"LFT&E\"), \",\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) should collaborate early with the program manager\\u2019s (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \") \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nproponent on planned uses of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" for the purpose of identifying \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nrequirements, necessary verification and validation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \") activities,\\nand for securing program office \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" funding (as applicable) \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Instruction\"\n }, \"DODI\"), \"\\xA05000.02 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\xA063\\u2011101/20\\u2011101, 9\\xA0May\\xA017.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses digital \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" for two primary purposes: prediction of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\nperformance and extension of field test results. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware in the Loop\"\n }, \"HITL\"), \"\\nvirtual simulations (and facilities) and test drivers to test system\\nperformance under conditions that cannot be reproduced on an open\\u2011air\\nrange or on actual operational equipment. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct, test\\nconcept and test plan should identify and explicitly describe the use of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to include the use of distributed capabilities for executing\\noperational test events.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" can play a helpful role in optimizing limited open\\u2011air range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \")\\nor ground test facility test time. In addition, testers can examine\\nvarious configurations of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Resulting information\\nprovides insight to maximize return from limited range time and to\\ninvestigate areas of principle interest to the warfighter.\"), mdx(\"p\", null, \"With an adequate representation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", the test team can use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nassets to predict \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance and optimize field test events by\\nestimating \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance boundaries. The optimization enables\\ntailoring of field testing to address those areas that merit further\\nevaluation or are of special interest to the user.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" can fill in gaps associated with field testing in cases where it\\nwould be too expensive or impossible due to lack of capability to\\nconduct an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \"\\u2011only evaluation. The test team would first use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to\\nrehearse and construct valid \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" events and ensure a common baseline.\\nThen once the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is appropriately accredited, the test team can use it\\nto run events beyond the scope of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" events.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"As an example, consider testing an air\\u2011to\\u2011air missile system, where\\nthe primary target of interest is a foreign fighter. Since it would be\\nimpractical or impossible to fire the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" missile at an actual foreign\\naircraft, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" events may consist of firing the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" missile at a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \"\\nfighter configured as a surrogate foreign aircraft. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" would then\\nrepeat the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \" drone aircraft firings and \\u201Cextend\\u201D the results to the\\nforeign aircraft of interest by executing the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" with a\\nrepresentation of the foreign aircraft signature and other parameters\\nof interest, provided by an external organization (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Air and Space Intelligence Center\"\n }, \"NASIC\"), \", MSIC, etc.).\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" could then provide the user information regarding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\nperformance versus real threats.\")), mdx(\"p\", null, \"Other reasons for using \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" are safety concerns, environmental concerns\\n(hazmat), treaty limitations, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Security\"\n }, \"OPSEC\"), \" concerns, or support concept\\nlimitations.\"), mdx(\"p\", null, \"Whenever the test team intends to use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" results to capture information\\nin an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Final Report, they need to ensure proper \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" accreditation.\\nTest teams are encouraged to contact A\\u20112/9 early in the life of a\\nprogram, primarily after the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct is completed, for assistance\\nin determining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" applicability and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" requirements. A\\u20112/9 and A-5/8\\nmaintains information on various \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" applications,\\nincluding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\u2011specific \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" guidance.\"), mdx(\"h2\", null, \"Test Capability Accreditation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" often uses test capabilities to create a pseudo-employment or\\ncombat environment in which to conduct the operational testing. These\\ntest capabilities may include \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the employment environment as well\\nas \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Accreditation Guide provides actionable\\ninformation for Test Directors, analysts, engineers, and program\\nmanagers on how best to plan, execute, and report accreditation of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nsystems. The accreditation process involves:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Developing an executable plan, assessment, and report with focus on\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"documenting the results of the accreditation assessment\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Documenting the recommendations in support of the accreditation\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"decision, and\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Documenting lessons learned during accreditation\"))), mdx(\"p\", null, \"Accreditation is applicable when a test capability is used directly or\\nindirectly to provide information that appears in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Final Report.\\nIf a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" intends to draw weapon system capability conclusions (i.e., rate\\nmeasures) based upon the use of a test capability, accreditation is\\nrequired. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" accreditation policy exists to ensure standardization\\nacross test teams and a consistent level of rigor in determining\\nadequacy of test capabilities. Accreditation activities should not\\nexcessively burden test teams or lead to inordinate expense. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nstaff lead for Accreditation is A-2/9. Refer questions about\\nVerification, Validation, and Accreditation to\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"\n }, \"UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"), \".\"), mdx(\"p\", null, \"Test capabilities used solely for test\\u2011planning purposes and assessments\\n(such as observations, EOAs) do not require a formal accreditation,\\nalthough the analyst should exercise a similar process to ensure that\\nthe test capability is adequate and to identify risks involved and how\\nthey may affect the overall test. Any informal accreditation\\ninvestigation procedures (peer review, analyst investigations, etc.)\\nshould be documented to ensure continuity when program personnel change.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\u2019s mission is to Deliver Combat Capability through Operational\\nTest. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" often uses test capabilities to create a pseudo-employment\\nor combat environment in which to conduct the operational testing. These\\ntest capabilities may include \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the employment environment as well\\nas \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". The test capabilities used in a given test do not\\nalways represent the employment environment with 100% accuracy. There\\nare usually some differences in fidelity between the actual combat\\nsystems and test representations. Given these differences, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is\\ncareful in drawing conclusions about \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" capabilities and ensures that\\nthe representation of the employment environment is adequate to draw\\ncredible conclusions. Inherently, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assumes some degree of risk\\nwhen using test capabilities to represent an employment environment or\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" to determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" capabilities. The purpose of accreditation is to\\ncharacterize that risk and ensure the risk is acceptable.\"), mdx(\"p\", null, \"See the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Accreditation Guide accreditation details.\"), mdx(\"h2\", null, \"Test Constraints and Limitations\"), mdx(\"p\", null, \"Limitations may be identified at any point in a program, however the\\nearlier a potential limitation is identified, the more likely it can be\\nresolved without impacting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E credibility. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and core team\\nincluding A-5R and/or A\\u20118Z are encouraged to identify limitations as\\nearly as possible. The documentation provides justification for\\ncontinued improvement and modernization of test capabilities that\\nultimately lead to more useful and relevant \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" reports and better\\nsystems delivered to the warfighter. A limitation is something that\\nwould influence being able to accomplish a credible operational\\nevaluation.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Limitation:\"), \" A limitation affects the ability to evaluate certain\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"aspects of a weapon system or to re\\u2011create certain aspects of the\\noperational environment. Limitations can be due to differences in\\nthe scenario (operational versus test), test capabilities such as\\nthreat simulation, range restrictions (safety, physical airspace),\\nspecific test measurement constraints, numbers of test articles,\\nor the threat lay down (types and numbers). Limitations, once\\nidentified, are carried throughout all phases of the test program\\nunless the underlying factors are no longer applicable. A system\\nthat is not production representative for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E may be\\nidentified as a limitation.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mitigation:\"), \" Each limitation requires the team to plan a\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"mitigation to reduce the risk to the evaluation of the system.\\nMitigation is intended to reduce the impact of the limitation to\\nthe point where the evaluation is still credible. There are\\ntypically few, if any, limitations in conducting credible EOAs and\\nOAs. However, when there are limitations, mitigation may be\\ndifferent for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \", or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is one method used to\\nmitigate a limitation. Teams should actively pursue mitigation of\\na limitation in order to have an adequate test.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Impact\"), \" (of a limitation after mitigation): The impact should\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"describe the extent to which the limitation will (for a plan) or\\ndid (for a report) affect the quality, completeness and/or\\nconfidence of our evaluation of the system under test\\u2019s\\neffectiveness, suitability and mission capability. The intent is\\nto acknowledge limitations and inform the decision\\u2011maker and\\nwarfighter of the extent to which the limitations will or did\\naffect our ability to report weapon system performance. The impact\\nshould clearly state what characteristics or attributes of the\\nevaluation are affected.\")))), mdx(\"p\", null, \"Table 12 provides some example limitations, mitigations, and impacts.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 12. Examples of Limitations\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Limitation\"), mdx(\"th\", null, \"Mitigation\"), mdx(\"th\", null, \"Impact\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Limited UAS System Availability\"), mdx(\"td\", null, mdx(\"p\", null, \"Coordination with operational unit to share assets between the field training unit and IOT&E test\"), mdx(\"p\", null, \"Leverage combat missions\")), mdx(\"td\", null, mdx(\"p\", null, \"Inability to fully evaluate all measures\"), mdx(\"p\", null, \"Cybersecurity not evaluated\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Limited Flight Hours for Reliability, Maintainability and Availability Evaluation\"), mdx(\"td\", null, \"Use reliability availability logistics operations model\"), mdx(\"td\", null, \"Reported values may not reflect actual values in operational use\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Limited capability of Red Team to test weapon system via data link while in flight\"), mdx(\"td\", null, \"Coordinated with AFTC to emulate mission parameters in anechoic chamber to allow Red Team cyber attacks\"), mdx(\"td\", null, mdx(\"p\", null, \"Cyber-exploitation effects not fully evaluated\"), mdx(\"p\", null, \"Inability to fully evaluate all measures\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Lack of Threat Systems at Test Facilities\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"Inability to report system effectiveness versus some threats\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"No integration of Lynx Radar Capability in Mobile Ground Control Station\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"Unable to evaluate Lynx synthetic aperture radar\")))), mdx(\"h2\", null, \"Basis of Estimate for Test Resources\"), mdx(\"p\", null, \"Together, the set of test events, test methodologies and test scenarios\\nform the basis of estimate. They describe why you are testing, what you\\nare going to do and how you are going to do it. Underlying the basis of\\nestimate is a set of assumptions that are validated to the extent\\npossible and documented. For the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct, particular focus is\\nplaced on the high cost (which includes high level of effort) and\\nlong\\u2011lead items. Typical examples of such items are threats,\\ninstrumentation and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" efforts. Some of these items have been\\nidentified throughout the preceding steps. In forming the basis of\\nestimate, these previously identified items are consolidated and test\\ndesigns are reviewed to identify new items. Collectively, there may be\\noverlap between the resources required for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". These should be\\nidentified and a consolidated list of resources should be provided (with\\ntraceability and rationale).\"), mdx(\"p\", null, \"Table 13 contains the basis of estimate contents.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table 13. Contents of Basis of Estimate\")), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Content Area\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Content Expectations\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"COIs\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"The COIs define the operations that need to be exercised during \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E and provide 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.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Test Events\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"For the particular test design(s) underlying the test events, a review of the factors and levels provide insight into the resources to establish the conditions. Man\\u2011made 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\\u2011lead 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 parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Test Methodology\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"How a set of test events are executed also provides the rationale or basis for resources. Field\\u2011testing may incur range costs, or possibly even the development of new range capabilities. \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" incurs both costs and potentially long\\u2011lead development. Reviewing the test methodologies provides insight on what might be needed to execute the test events.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Test Scenarios\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"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\\u2011is factors, need to be measured and resources identified in order to collect and analyze data when executing the test scenario.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Assumptions\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Although assumptions may not directly drive resources, they provide indicators of potential risks and disconnects with other organizations.\")))), mdx(\"h2\", null, \"Initial Resource Estimates\"), mdx(\"p\", null, \"The core team uses the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct basis of estimate to refine\\ninitial resource estimates documented in the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \". The Detachment\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" updates 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\\neach resource category of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \" to determine which line items need\\ncosting and which ones need to be paid for by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \". Table 14 contains\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E support costs breakdown.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Table14. Operational \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" Support Costs\")), mdx(\"table\", null, mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"AFOTEC Pays\"), mdx(\"td\", null, \"AFOTEC Does Not Pay\")), mdx(\"tr\", {\n className: \"even\"\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 & penetration assessment/ adversarial assessment)\")))), 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\")), 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(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Identifying Resources\"), \". To move from the basis of estimate to a\\ncompleted test resource plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \") takes a significant amount of effort.\\nThis is an iterative process, and teams will generally refine the\\ninitially planned events/activities based on resource availability,\\nrealism, cost, etc., which are focused on arriving at the best\\ncost-benefit solution.\"), mdx(\"p\", null, \"The actual costing of resources, developing agreements, and many other\\ndetailed steps required to source and cost are not captured here. These\\nspecifics depend on acquisition and test approaches (joint, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" lead,\\nresource types, participants, funding strategies, time-to-test start,\\ninfrastructure developmental needs, etc.), and teams rely on the\\nHeadquarters and Detachment resource managers to support each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct effort.\"), mdx(\"h1\", null, \"Documenting the Operational Test and Evaluation Construct\"), mdx(\"p\", null, \"Documentation cannot be overstated. Too many programs efforts have been\\nlost and needed to be re-accomplished because they were not properly\\ndocumented or in some cases, not documented at all. Each of the process\\nsteps above have a recommended documentation approach. Why documentation\\nimportant?\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The only constant with acquisition programs and the people who work\\nthem, is change. Personnel come and go, and programs evolve. When\\nnew people start a program, questions about how and why the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nlooks the way it does.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Leadership often ask why \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E is doing various activities\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" often has questions about the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E approach\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Integrating testing is best served by robust \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E documentation\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provides the foundational products and narrative for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nplan inputs\"))), mdx(\"p\", null, \"Following the test design development, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Design Manager\"\n }, \"TDM\"), \" provides the test design\\nproducts to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \". Using these products, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" then begins developing\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing with support from his core team for presentation to 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\"), \" on the date specified in the tasking order. This briefing will\\nbe developed and coordinated electronically for 2\\u2011letter approval. The\\nbriefing is an internal\\u2011only \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" product (i.e. it is not presented to\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \"). The purpose of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing is to convey to 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\"), \",\\nwith a high degree of confidence, the complete beginning\\u2011to\\u2011end scope of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities, resources, and costs with rationale. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing\\nindicates the specific acquisition events that the planned \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities\\nsupport. The Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" presents the acquisition information in a\\nbriefing to 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\"), \" for approval. Tailor the level of detail in\\neach area within the briefing to fit the specific program circumstances.\\nIf a particular subject area in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing template does not apply\\nto a program, do not include that subject area in the briefing.\\nSignificant issues should be resolved with appropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" directorates\\nbefore the formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing must include all\\nsupporting information by using embedded documents, as described in the\\nbriefing template. Following completion of the briefing, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nConstruct is updated as required by the Detachment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" to reflect the\\ndecisions made. The detailed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" Briefing template is found on the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct supports early integration and promotes the\\ncombining, where appropriate, of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events to satisfy both \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives. Remember that throughout \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E planning and execution, the\\nindividual \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" objectives should not be compromised. Early\\nintegration of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" planning provides the foundation for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" A\\n(and beyond) Test and Evaluation Master Plan development and supports\\nidentification \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" requirements needed for RFPs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" is an\\nopportunity to document integration with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" community and reduce\\ndedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events when they have been accomplished satisfactorily in\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E. These events are only removed from dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" when \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nrequirements have been met.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#the-operational-test-and-evaluation-construct","title":"The Operational Test and Evaluation Construct"},{"url":"#operational-sufficiency-and-technical-adequacy","title":"Operational Sufficiency and Technical Adequacy"},{"url":"#operational-test-and-evaluation-test-activity-cycles","title":"Operational Test and Evaluation Test Activity Cycles"},{"url":"#using-a-core-team-approach","title":"Using a Core Team Approach."},{"url":"#construct-development-meetings","title":"Construct Development Meetings"},{"url":"#battlespace-development","title":"Battlespace Development","items":[{"url":"#researching-the-capability-or-system-being-acquired","title":"Researching the Capability or System Being Acquired"},{"url":"#battlespace-depiction","title":"Battlespace Depiction","items":[{"url":"#the-evaluation-view","title":"The Evaluation View"},{"url":"#the-evaluation-view-1","title":"The Evaluation View 1"},{"url":"#the-evaluation-view-2","title":"The Evaluation View 2"},{"url":"#capability-requirements-mapping","title":"Capability Requirements Mapping"},{"url":"#mission-statement","title":"Mission Statement"},{"url":"#critical-operational-issues","title":"Critical Operational Issues"},{"url":"#operations","title":"Operations"}]},{"url":"#operational-employment-and-support-conditions","title":"Operational Employment and Support Conditions","items":[{"url":"#measures-of-effectiveness","title":"Measures of Effectiveness"},{"url":"#operational-conditions-factors-and-levels","title":"Operational Conditions (Factors and Levels)"},{"url":"#identify-factors-and-levels","title":"Identify Factors and Levels."},{"url":"#prioritizing-factors","title":"Prioritizing Factors"}]},{"url":"#operational-capabilities-oc","title":"Operational Capabilities (OC)"}]},{"url":"#evaluation-summary-chart","title":"Evaluation Summary Chart","items":[{"url":"#mission-statement-in-an-evaluation-summary-chart","title":"Mission Statement in an Evaluation Summary Chart"},{"url":"#critical-operational-issues-in-an-evaluation-summary-chart","title":"Critical Operational Issues in an Evaluation Summary Chart"},{"url":"#mission-effects-in-an-evaluation-summary-chart","title":"Mission Effects in an Evaluation Summary Chart"},{"url":"#operational-capability-requirements-in-an-evaluation-summary-chart","title":"Operational Capability Requirements in an Evaluation Summary Chart"}]},{"url":"#test-design","title":"Test Design","items":[{"url":"#test-design-goals","title":"Test Design Goals"},{"url":"#types-of-test-design","title":"Types of Test Design"},{"url":"#factor-management","title":"Factor Management."},{"url":"#unconstrained-and-constrained-events","title":"Unconstrained and Constrained events"},{"url":"#statistical-measures-of-merit","title":"Statistical Measures of Merit"},{"url":"#test-events","title":"Test Events"},{"url":"#test-design-validations","title":"Test Design Validations"}]},{"url":"#measures-development","title":"Measures Development"},{"url":"#test-execution-planning","title":"Test Execution Planning","items":[{"url":"#test-methodology","title":"Test Methodology"},{"url":"#test-scenarios","title":"Test Scenarios"},{"url":"#test-capability-needs-and-shortfalls","title":"Test Capability Needs and Shortfalls","items":[{"url":"#time-phased-investment-document","title":"Time-Phased Investment Document"},{"url":"#determining-range-requirements","title":"Determining Range Requirements"},{"url":"#range-requirement-identification","title":"Range Requirement Identification"},{"url":"#range-selection-considerations","title":"Range Selection Considerations"},{"url":"#national-cyber-range-considerations","title":"National Cyber Range Considerations"},{"url":"#test-targets","title":"Test Targets"},{"url":"#range-safety-considerations","title":"Range Safety Considerations"},{"url":"#range-instrumentation-considerations","title":"Range Instrumentation Considerations"},{"url":"#range-data-processing-considerations","title":"Range Data Processing Considerations"},{"url":"#test-article-instrumentation","title":"Test Article Instrumentation"},{"url":"#program-introduction-document-release-authority","title":"Program Introduction Document Release Authority"}]},{"url":"#the-use-of-modeling-and-simulation","title":"The Use of Modeling and Simulation"},{"url":"#test-capability-accreditation","title":"Test Capability Accreditation"},{"url":"#test-constraints-and-limitations","title":"Test Constraints and Limitations"},{"url":"#basis-of-estimate-for-test-resources","title":"Basis of Estimate for Test Resources"},{"url":"#initial-resource-estimates","title":"Initial Resource Estimates"}]},{"url":"#documenting-the-operational-test-and-evaluation-construct","title":"Documenting the Operational Test and Evaluation Construct"}]},"parent":{"__typename":"File","relativePath":"fn_guides/OTE_construct_development_guide.md"},"frontmatter":{"metaTitle":"OT&E Test Construct Development Guide","metaDescription":"OT&E Test Construct Development Guide"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"6133484f-bd7c-5686-9d20-576e0aa03f74"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/fn_guides/accreditation_guide/page-data.json b/sites/oteguide/page-data/fn_guides/accreditation_guide/page-data.json deleted file mode 100644 index 2b690d5c..00000000 --- a/sites/oteguide/page-data/fn_guides/accreditation_guide/page-data.json +++ /dev/null @@ -1 +0,0 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides/accreditation_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"60d0d63d-0770-5cac-8cf2-b116c38568ac","title":"Accreditation Guide","slug":"/fn_guides/accreditation_guide"},"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\": \"Accreditation Guide\",\n \"metaTitle\": \"Accreditation Guide\",\n \"metaDescription\": \"Accreditation Guide\"\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, \"08 December 2020\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9\"), mdx(\"h1\", null, \"INTRODUCTION\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Accreditation Guide provides actionable information for test\\ndirectors (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"), analysts, engineers, and program managers on how best to\\nplan, execute, and report accreditation of modeling and simulation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \")\\nsystems. The accreditation process involves:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Developing an executable plan, assessment, and report with focus on\\ndocumenting the results of the accreditation assessment\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Documenting the recommendations in support of the accreditation\\ndecision, and\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Documenting lessons learned during accreditation\"))), mdx(\"p\", null, \"Accreditation is applicable when a test capability is used directly or\\nindirectly to provide information that appears in an operational test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \") final report. If a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" intends\\nto draw weapon system capability conclusions (i.e., rate measures) based\\nupon the use of a test capability, accreditation is required. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\naccreditation policy exists to ensure standardization across test teams\\nand a consistent level of rigor in determining adequacy of test\\ncapabilities. Accreditation activities should not excessively burden\\ntest teams or lead to inordinate expense. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" staff lead for\\nAccreditation is A-2/9. Email questions about verification, validation,\\nand accreditation to A-2/9 workflow at:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"\n }, \"UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"), \" .\"), mdx(\"h1\", null, \"Test Capability Accreditation\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s mission is to deliver combat capability through operational\\ntest. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" often uses test capabilities to create a pseudo-employment\\nor combat environment in which to conduct the operational testing. These\\ntest capabilities may include \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the employment environment as well\\nas \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" of the system under test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"). The test capabilities used in a\\ngiven test do not always represent the employment environment with 100%\\naccuracy. There are usually some differences in fidelity between the\\nactual combat systems and test representations. Given these differences,\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is careful in drawing conclusions about \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" capabilities and\\nensures that the representation of the employment environment is\\nadequate to draw credible conclusions. Inherently, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assumes some\\ndegree of risk when using test capabilities to represent an employment\\nenvironment or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" to determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" capabilities. The purpose of\\naccreditation is to characterize that risk and ensure the risk is\\nacceptable.\"), mdx(\"h1\", null, \"The Use of Modeling and Simulation\"), 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\": \"Operational Test\"\n }, \"OT\"), \"&E Guide,\\\" 11th ed. states that whenever \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is used to\\ncapture information in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Final Report, proper \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" accreditation is\\nrequired. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" includes, but is not limited to, digital \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \",\\nhardware-in-the-loop (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware in the Loop\"\n }, \"HITL\"), \") virtual simulations and test drivers such as\\ndata injectors and stimulators. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" also includes physical models of\\ntargets, threat representations and combinations of simulations. Test\\nplanners (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live Fire Test and Evaluation\"\n }, \"LFT&E\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) should collaborate early with the program\\nmanager's (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \") \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" proponent on planned uses of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" for the purpose of\\nidentifying \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" requirements, necessary verification and validation\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \") activities, and for securing program office \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" funding (as\\napplicable) \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" DoDI\\xA05000.02 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 63-101/20-101, 9 May 17.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses digital \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" for three primary purposes: test planning,\\nprediction of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance, and extension of field test results.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Hardware in the Loop\"\n }, \"HITL\"), \" virtual simulations (and facilities) and test drivers\\nto test system performance under conditions that cannot be reproduced on\\nan open\\u2011air range or on actual operational equipment. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \", test\\nconcept and test plan should identify and explicitly describe the use of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" to include the use of distributed capabilities for executing\\noperational test events.\"), mdx(\"h1\", null, \"Verification, Validation and Accreditation Definitions\"), mdx(\"p\", null, \"Definitions are based on DoDI 5000.61, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" Verification, Validation\\n& Accreditation (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \")\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Verification. The process of determining that a test capability\\naccurately represents the developer's conceptual description and\\nspecifications. Verification addresses whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" works as\\nplanned. Verification is typically accomplished by the model\\ndeveloper (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \", system contractor or facility/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" owner).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Validation. The process of determining the degree to which a test\\ncapability provides an accurate representation of the real world\\nfrom the perspective of the intended uses of the test capability.\\nValidation addresses whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" represents reality. Validation\\nis typically accomplished by the model developer (Program Office\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Office OR Project Officer\"\n }, \"PO\"), \"), system contractor or facility/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" owner).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Accreditation. The official certification that a test capability is\\nacceptable for use with a specific application. Accreditation\\naddresses whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is acceptable for a specific use.\\nAccreditation is accomplished by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".\"))), mdx(\"p\", null, \"The accreditation requirement applies to I/Q/F/MOT&Es and Operational\\nUtility Evaluations (UOUEs). Typical test capabilities requiring\\naccreditation may include open air range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Open-Air Range\"\n }, \"OAR\"), \") assets, ground test\\nfacilities, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \", foreign materiel acquisition, test drivers, threat\\nsimulators, targets, blue weapons used as threat surrogates and kill\\nremoval systems.\"), mdx(\"h1\", null, \"Acquisition Implications of Verification, Validation and Accreditation\"), mdx(\"p\", null, \"With the inception of agile acquisition, sprints, and rapid testing, it\\nis likely that there will be a unique acquisition approach for each\\nsystem under test. The \", 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 Guide states: \\\"There is no single\\nacquisition approach for a given type of system. The approach is\\ninfluenced by the urgency of need, the technology development\\nrequirements, the amount of money allocated to the program, or any of a\\nvariety of other influences.\\\"\"), mdx(\"h1\", null, \"Accreditation Concepts\"), mdx(\"p\", null, \"Test teams should plan to accomplish the accreditation and publish the\\naccreditation report prior to test readiness review (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will\\nbe able to begin the test execution phase with confidence that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nis credible. It may not always be possible to complete the accreditation\\nreport prior to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \" but that should be the goal.\"), mdx(\"p\", null, \"Accreditation is about characterizing risk. Specifically, it is about\\nensuring that the risk of using a model and/or simulation to determine\\nand report \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" effectiveness/suitability in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final report is\\nacceptable. Keeping this fundamental principle in mind will help keep\\naccreditation efforts on track. Test teams are encouraged to focus the\\naccreditation effort and documentation describing the risks. The\\naccreditation authority will ultimately decide whether or not to accept\\nthe risks.\"), mdx(\"h1\", null, \"Risk Matrix: Example\"), mdx(\"p\", null, \"The following excerpt is from the Accreditation Report for the Radar\\nSimulation Suite (RSS) used in the Cobra Judy Replacement Multi-Service\\nOperational Test and Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \"), 12 Mar 14.\"), mdx(\"p\", null, \"The test team assessed the impacts to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" and the probability of\\noccurrence using the Air Force operational risk management general\\nassessment practices and definitions presented in Table 5-9, in\\naccordance with the 'Risk Management Guide for DOD Acquisition,' 6th\\nedition, Aug 06.\"), mdx(\"p\", null, \"For each identified risk, the test team has provided a narrative\\ndiscussion and identified major issues. The test team provided an\\noverall risk assessment for the use of RSS in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \".\\\" Table 5-9 defines the\\nseverity of each risk ratings (low, low/medium, medium, medium/high, and\\nhigh). Table 5-10 identifies the assigned risk assessment by the test\\nteam: Figure 5-5 shows the risk management rating scale (RMRS) with\\ngreen (low), yellow (medium) and red (high) ratings. \\\"After rating each\\nprimary risk, the test team populated the RMRS with the associated risk\\nnumber\\\". \\\"Risk 1 was identified as L/M impact and M/H probability of\\noccurrence.\"), mdx(\"p\", null, \"Table 5-9. Risk Severity Definitions\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Impact to OT\"), mdx(\"th\", null, \"Definition\"), mdx(\"th\", null, \"Probability of Occurrence\"), mdx(\"th\", null, \"Definition\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"L\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"L\"), mdx(\"td\", null, \"Unlikely\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"L/M\"), mdx(\"td\", null, \"Negligible\"), mdx(\"td\", null, \"L/M\"), mdx(\"td\", null, \"Seldom\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"Moderate\"), mdx(\"td\", null, \"M\"), mdx(\"td\", null, \"Occasional\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"M/H\"), mdx(\"td\", null, \"Critical\"), mdx(\"td\", null, \"M/H\"), mdx(\"td\", null, \"Likely\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"Catastrophic\"), mdx(\"td\", null, \"H\"), mdx(\"td\", null, \"Frequent\")))), mdx(\"p\", null, \"Figure 5-5. Risk Management Rating Scale\"), 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\": \"705px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/0a7706806fc964c1e3039be52acc7070/d2cbc/image2.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.204633204633204%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAHCAYAAAAIy204AAAACXBIWXMAABcRAAAXEQHKJvM/AAAB+klEQVQozy2SX0hTYRjGn52zYY10i50txoKtbbnpOfvXJgqthCQpMJMksYvuDIMIjC6iCCTIVtSNQTdB7KKbugq6LtyFXYXkxS5Sjw5S0bmtuXX2p6P59g68+PHj+3h5no/v+3DUjDYA4sBlofPRjBh5nBKVh09FJZWC8pJ59Q7ysA1XLgHXbwCDI8DQlBk9sxLkFzaEnh2B8hwIvQa6bwG9OG5FBBDsahZP9Apor4qqVkAtv4NakV3Qoa3Porkdg164iOZWHxrbQK0MaCX2FlMyQtsVUMsJKKPdZgjwCY+9yUrT6V8OSq879t/nJGrWQfSP2QPpDRzohIN9AjXKIO0BF98FNdkVhQ1eMzvAX4hWY5ADbac+RWZOz8XJl0lQ15cYTS546X7WQxM/fPRxxUr1KqhQESj/20AlLinqoCoXFL+D/qRB9Q+gjbcgmOwmFweawp/le/H5aD7xLbocy0RU/9f4qj+TWHPP9ajJ+dDSzcXO5dGFoDqx6FvaLAgrlSLWdovIlTSoGmGVyW1q+AnBLIgcaLSct0iOcYdHuiZ5XJNOZ/i2zeXsNcedsbaz6LcHcOakjIC9DwNu7+CQoftcEsnhq5Cnp+C8MwL3aD+6xi7Az1nogAArW2Jathy6gznBhA38evwVFCZoZPNelPG27v5wtkV7a/4/D8HL4EHCE0QAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image2\",\n \"title\": \"image2\",\n \"src\": \"/static/0a7706806fc964c1e3039be52acc7070/d2cbc/image2.png\",\n \"srcSet\": [\"/static/0a7706806fc964c1e3039be52acc7070/a2ead/image2.png 259w\", \"/static/0a7706806fc964c1e3039be52acc7070/6b9fd/image2.png 518w\", \"/static/0a7706806fc964c1e3039be52acc7070/d2cbc/image2.png 705w\"],\n \"sizes\": \"(max-width: 705px) 100vw, 705px\",\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, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" should strive to publish the accreditation plan early in the test\\nprogram lifecycle (shortly after measures are defined). The\\naccreditation plan establishes acceptance criteria, to which the\\nvalidation plans and reports should respond. Publishing the\\naccreditation plan early ensures AFOTECs opportunity to influence the\\nscope and nature of subsequent \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" activities and products, and to enter\\ndiscussions early with the developer of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" capability. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \"\\nexpects the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" to include details on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" approach, or a reference\\nto such details \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" memo, 14 Mar 16.\"), mdx(\"p\", null, \"Known baseline. To the extent possible, the accreditation acceptance\\ncriteria should be based upon comparing model output to a known\\nbaseline. For example, for a threat, the known baseline may be the\\nIntelligence community assessment of threat behavior. For a target drone\\naircraft the known baseline may be measured signature data of a foreign\\naircraft. Strive to establish quantitative criteria whenever possible.\"), mdx(\"h1\", null, \"Previous Accreditation\"), mdx(\"p\", null, \"There may be an opportunity to use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" that has been accredited in the\\npast, either by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" or by another organization. For example, if\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" or another organization has used the intended \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" for similar\\npurposes, it may be possible to focus the accreditation effort on \\\"delta\\naccreditation.\\\" In this case, the accreditation team will need to\\narticulate how the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" has changed, if at all, since last accredited. In\\naddition, the team must illustrate how use of the previously accredited\\nmodel compares to the proposed use.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not make blanket or class accreditations. However, if \\\"delta\\naccreditation\\\" is feasible or the upcoming test, a new accreditation\\nreport is not required. Depending on the intended use of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \", the\\naccreditation effort may consist of a comprehensive new report or a\\none-page memo for record. When beginning any accreditation effort, it is\\nbest to examine what has been done in order to avoid potential\\nduplication of effort or unnecessary documentation and staffing. Consult\\nwith \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" A-2/9 to help decide the best route to take. Table 2 describes\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" offices that have a role in the Accreditation process as well\\nas the correlation (if any) to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" roles as outlined in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 16-1001,\\nand associated responsibilities.\"), mdx(\"p\", null, \"Table 2. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" Roles and Documentation Responsibilities\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Office\"), mdx(\"th\", null, \"AFI Role Correlation\"), mdx(\"th\", null, \"Responsibilities\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"AFOTEC (typically the TD)\"), mdx(\"td\", null, \"Requiring Agency\"), mdx(\"td\", null, \"Establish the need for M&S for use in a particular program\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"AFOTEC Technical Advisor (CA)*\"), mdx(\"td\", null, \"Accreditation Authority\"), mdx(\"td\", null, \"Approves AFOTEC accreditation plans and reports\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Det Technical Advisor (TA)\"), mdx(\"td\", null, \"Accreditation Agent\"), mdx(\"td\", null, \"Review and sign accreditation plans and reports prior to submission to CA\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Det Commander*\"), mdx(\"td\", null, \"Accreditation Authority\"), mdx(\"td\", null, \"Approves and signs accreditation plans/reports originating from his/her Detachment\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Det TD\"), mdx(\"td\", null, \"Accreditation Agent\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Reviews/signs accreditation plans/reports documenting adequacy of test capabilities to support OT&E\")), mdx(\"li\", null, mdx(\"p\", null, \"Briefs M&S developer on Accreditation Plan and ensures V&V plans/reports meet Accreditation requirements identified in Accreditation Plan\")), mdx(\"li\", null, mdx(\"p\", null, \"Briefs the accreditation approach to A\\u20112/9 during the TR\")), mdx(\"li\", null, mdx(\"p\", null, \"Ensures that all test capabilities are accredited\")), mdx(\"li\", null, mdx(\"p\", null, \"Sends signed copies of accreditation plans and reports to A\\u20113 and HO for records management and archiving\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Det Analyst\"), mdx(\"td\", null, \"Accreditation Agent\"), mdx(\"td\", null, \"Authors, signs and executes accreditation plans and authors accreditation reports for all test capabilities\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operations Directorate (A\\u20113)\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Reviews accreditation plans/reports documenting adequacy of test capabilities to support OT&E\")), mdx(\"li\", null, mdx(\"p\", null, \"Validates test capability requirements\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Intelligence, Analyses and Assessments Directorate (A\\u20112/9)\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Assists the TD with the accreditation process as directed in the program tasking order\")), mdx(\"li\", null, mdx(\"p\", null, \"Advises on VV&A policy and process\")), mdx(\"li\", null, mdx(\"p\", null, \"Post final accreditation plans/reports to AFOTEC\\u2011SharePoint site.\")), mdx(\"li\", null, mdx(\"p\", null, \"Records the decision on whether accreditation is required or not in a memo for the Det/TD post ITD\")), mdx(\"li\", null, mdx(\"p\", null, \"Reviews accreditation plans/reports for technical adequacy and advises CA accordingly\")), mdx(\"li\", null, mdx(\"p\", null, \"Staffs plans/reports through HQ via SSS; tracks comments and revisions, obtains CA signature\")), mdx(\"li\", null, mdx(\"p\", null, \"Monitors AF and DoD VV&A policy and communicates policy changes within AFOTEC\"))))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Special Projects Division for NTTR (A\\u20118Z)\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Assists the TD as directed in the program tasking order\")), mdx(\"li\", null, mdx(\"p\", null, \"Maintains cognizance of accreditation activities associated with NTTR assets\")), mdx(\"li\", null, mdx(\"p\", null, \"Advises test team on the likelihood of successful accreditation for specific test capabilities\")), mdx(\"li\", null, mdx(\"p\", null, \"Maintains library of accreditation plans/reports associated with NTTR\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"A-5R\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"Monitors test capability through participation in AF and DoD investment processes ensuring V&V plans support accreditation, are fully funded, and are included in the project management plans\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"HO\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Receives copies of accreditation plans/reports from the TD\")), mdx(\"li\", null, mdx(\"p\", null, \"Maintains library of all AFOTEC accreditation plans/reports\")), mdx(\"li\", null, mdx(\"p\", null, \"Maintains a library of verification and validation reports for facilities AFOTEC commonly uses\"))))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"V&V Manager\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"N/A\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"V&V Agent\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"N/A\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"PM/Developer\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"N/A\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*For the F-35 program and BMDS, the AFOTEC Commander (as a member of the F-35 Executive Committee) serves as the accreditation authority\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, \"Verification and validation are the responsibility of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\ndeveloper/owner. Figure 1 illustrates an overview of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" process,\\nincluding the roles/responsibilities associated with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \". The bold\\nvertical line indicates the distinction between the capability owner\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" manager & \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" agent) \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \") and the capability user (Accreditation\\nAgent & Accreditation Authority).\"), mdx(\"p\", null, \"Figure 1. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" 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\": \"1035px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/12f6c67135c455d9270eed34e455ee4c/b9024/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\": \"58.687258687258684%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAYAAABiDJ37AAAACXBIWXMAACHVAAAh1QEEnLSdAAAC70lEQVQoz0WTTW8bVRSGza9gw5oVEgsqUNQVEisE/wFSiUioZAESlaBNKK2qdoUqUASFNsFNgkqhjYOJkiZOHNsNSVyPP8dj7PlyJuOx59NNEKzg4Y7TqItX956jc885997nJGxnwMD16A/ckZxY/XjvjeQ8W3vCl9nceh7rusIXcOjE8keKzyZczyMMAoJnOh6GRGFEWY3YafqUtZCKFuG4EflcFt8PGA4jdKPL1Suf8uXUBFenzzN96WNMwxAJRcWTZD6u51PXHErtHk2jP7I1a0Dxzx414d/c2iIMA1EwEF0OaDYkVnMFvkhuMJ3MsNs8IBFfwfd9joY+skjy4V2F8VmFG+mO6Dbg60c6k4ttzs3K3P51nadRiGm7mD2faHjMstRnPKkxsaAznzdJeKILz4+IomPaVsDUQ40bKwazORM/8FgoyFxcanE5pTO3lKXvhULivdw+fx+F5OUB799p8dFChxXpkITd66HqXSLtLkfKZYLmddS9axS2l1F2b+HKF9nY+Ry/doXVB19h2RZNpYrZ7VBSs9jyN3RrM9j1mxyouyQ0w6b6ZJ3/pDGonCUqvcmje6/QLi0S5cdwC6/zT/EN3NQLJOfO44d/0ajXMLoOVvUS/z45A8238FdfQtn7joTR7VEpbqAtv4qZPkPt/svM/zBGtfGY0oN3aKTeRk6/y87iWZIPv6V7YAipGJaDmnkPa+U1rNUx9u68SEfOiA51g0q1TkVRSOX2uZUu0JD2kSoya9k/SOckZtZa4p2HbGY2kaQilUpZdFmnXJXYEfbt37dptGSB0xEJ0zQp1xSmUl3Oid+a/EnDC4csFS0m7+l8cl/ng2RLoGTzuJDHDZ9yKJj0BKvfZy0m5nXGf1TZb7sjKka/bDsuc9s6N9c0ZtY1jMMBqf0uF35uce03lc9+abGr2GSyeSznZIpCwW0ccz2tCnUEpz2BVPAc7HhaYh5jwE/t0ZgJxUXjBPlcbgT2aczpMHj+iR2f/x/Aai7Zqmjx/AAAAABJRU5ErkJggg==')\",\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/12f6c67135c455d9270eed34e455ee4c/e3189/image3.png\",\n \"srcSet\": [\"/static/12f6c67135c455d9270eed34e455ee4c/a2ead/image3.png 259w\", \"/static/12f6c67135c455d9270eed34e455ee4c/6b9fd/image3.png 518w\", \"/static/12f6c67135c455d9270eed34e455ee4c/e3189/image3.png 1035w\", \"/static/12f6c67135c455d9270eed34e455ee4c/b9024/image3.png 1203w\"],\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, \"Accreditation Process\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" will email unclassified accreditation plans/reports to the A-2/9\\nworkflow address: \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"\n }, \"UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"), \" . If the\\nplan/report is classified, contact the A-2/9 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" or workflow for\\ninstructions. The A-2/9 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will place accreditation plans/reports into\\n2-ltr coordination for 5 days and adjudicate all comments. Upon\\ncompletion, the A-2/9 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" will place accreditation plans/reports into \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \"\\ncoordination for review and signature by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \". The \\\"\", 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 Guide\\\"\\nshows \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s accreditation process (Figure 2 below). Accreditation\\nactivities begin during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct development with\\nidentification of test capability requirements, followed by development\\nof an accreditation memo.\"), mdx(\"p\", null, \"Figure 2. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Accreditation Process\"), 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/36b9575e92d08f0fe1b26f2d1ff7bef4/d5b59/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\": \"54.440154440154444%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAYAAAB/Ca1DAAAACXBIWXMAACHVAAAh1QEEnLSdAAADhklEQVQozwF7A4T8AGt/jxN3jqAYdoyeF01hbw1viJsShJ6zF2h+jw4AAAAAWm59GlhndCR1dXbPfXt85IB9fNR+e3zafXx+435+f+prbnJdAAAAAADL/wBihqcAAFWHteBbj8D2W5DB+kR3prdTh7fhW428+1CFt+M/c6SXVoe08liKuPZkmMn8Vo3A5nV3fFtce5idW468/1+OufNgkb39WIy8zigrMgn//wAAAF2Lr+hfh6T/Y5Gz/2uYt9lhjKv0WIGf/1+Lrv9llLfdXIyx+FN/o/5Tha7/VpHF9nB9hmZZg6mdRX2w/z5xofpFfrP/T4/K+QBX2wuRaVMAAFqMtvNah6z/XI20/2CPs+Bhkrn9YZG4/2SUuv9mk7TiZJGz/2CJpv9plLP/caHD/5SppH+Ao7S0ZpKx/2ONrP9khqH/ZYGc9KxpPk3DYB0tAEh+r6ZEe660RXuvtz5xoI9OisGsT43Ht0uHwLRAdqmHQnipnT5xoaJBdaShSH2tokdtjhZZhalNVI/Apo+Mi7nDfkr/t4FU/L9+S//KcDLRAFaVhgD///8B//+xAwB/ngBOn5oA/4QAAv+ZIwQAAP8APYKNAAJwogAtn94Aad3/ANv//wDJ//8A7cfDALZWC0u+YB//uWAk/rl+Tv/IgEvWADpfInxMbjfeUHE54EVrLLkwVRlhUnY72lV6POJRdzjONlsihVl8Q81bf0XNYIRL1lNzP5hcfEmzc5Rj4YOXauXAlGD80JZm9NqSWf/VdzXBAF+CS9Nqilj/X4NK/2mPUv9qjFfbZYhR/2aIUv9wlVr/cJFc+nWYYP93mGP/eZtm/3ycafd3l2T4bpBZ/22SVv+Nm3xNu492GpxJFCSHQRQRAGqMVsJ2lGX/YYBP+miJVPpukFvRZolS9l5/S/1hhUz8YYZK61V4P/hGZjL7TXMz/VB7NOo9XybmOl4j/0NsJ/UTPQAgeX5LAONPDwCfSxYAAEdvK8tAZij/PWIi/0ZxKf9BaiXKQGcl/j1jJP9Hcir/RnEq8URsKf9IcSz/TXkw/0t2L/NGbSzyUn40/1SBNf88WCcrI1gaAHNkLgOsXyoBAEZsLKtDZyrjR20t2k54MtpDZyusR20t00hvLtpKci/aRGorxE13MctPezLPUHwy0UdtLb9JcS63UHwyy0pzLsIvSR0fNFEhADdWIwEAAAAA7O+2KeUEI+AAAAAASUVORK5CYII=')\",\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/36b9575e92d08f0fe1b26f2d1ff7bef4/e3189/image4.png\",\n \"srcSet\": [\"/static/36b9575e92d08f0fe1b26f2d1ff7bef4/a2ead/image4.png 259w\", \"/static/36b9575e92d08f0fe1b26f2d1ff7bef4/6b9fd/image4.png 518w\", \"/static/36b9575e92d08f0fe1b26f2d1ff7bef4/e3189/image4.png 1035w\", \"/static/36b9575e92d08f0fe1b26f2d1ff7bef4/d5b59/image4.png 1370w\"],\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 memo from the Director, A\\u20112/9 to the detachment commander identifies\\nthe test capability requirements, accreditation documentation\\nrequirements, initial timelines, and relevant \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" documents available.\\nUpon receipt of this memo, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" (and designated test team members/with\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" assistance) begins tracking \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" resource expenditures including\\nmanpower and dollars.\"), mdx(\"p\", null, \"During each Test Concept Technical Review, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" will discuss the test\\ncapabilities to be used and how the accreditation will be accomplished\\nbased on the guidelines for use of the capability. A\\u20112/9 advises whether\\naccreditation is required or not. Throughout test planning, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"\\nshould inform A\\u20112/9 on the accreditation approach during scheduled\\ntechnical reviews, including proposed level of effort, completion dates\\nand accreditation resource requirements. The information enables A\\u20112/9\\nto ensure technical adequacy on the overall accreditation approach and\\nprevent unnecessary expenditure of resources. As the program progresses,\\nthe test team should identify planned use of test capabilities and the\\nassociated accreditation approach in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" and test concept briefings.\"), mdx(\"p\", null, \"The next step is an accreditation concept discussion, typically\\nconducted via \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Video Teleconference\"\n }, \"VTC\"), \". This discussion is between the test team and A-2/9.\\nThe purpose is to initiate dialogue and agree on assumptions and the\\noverall accreditation approach before initiating development of the\\naccreditation plan. The topics shown in Figure 5-8 help frame this\\ndialogue. After internal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" discussion it is a good idea to discuss\\nthe accreditation concept with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" action officer, if \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" is\\ninvolved, to ensure there are no disconnects between \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \"\\nwith respect to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \".\"), mdx(\"p\", null, \"Following completion of the accreditation concept discussion the test\\nteam initiates development of the accreditation plan(s). Many test\\ncapabilities have existing validation and/or accreditation reports that\\nmay be useful for current and future \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" efforts. A\\u20118Z, A\\u20112/9 and the\\nHistory Office (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"HQ AFOTEC History Office\"\n }, \"HO\"), \") may have copies of previous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" documents. The\\naccreditation plan establishes the benchmark for all remaining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \"\\nactivities. Per \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \"\\xA016-1001, \\\"Acceptability criteria are the most\\nimportant content of the accreditation plan and should be presented as\\nminimum criteria for accreditation.\\\" The team should place priority on\\ndeveloping meaningful accreditation acceptance criteria. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" submits\\nthe plan to A-2/9, who reviews and coordinates the plan and submits the\\nplan to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \" for approval.\"), mdx(\"p\", null, \"Once the plan is approved, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" distributes the plan to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" capability\\nowners so they can prepare \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" plans/reports that will produce data to\\nallow \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" to determine whether or not the acceptance criteria have\\nbeen met. Following receipt of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" reports, the test team executes\\nthe accreditation plan. This step primarily involves comparing the\\nresults of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" to the acceptance criteria.\"), mdx(\"h1\", null, \"Test Capability Accreditation Concept\"), mdx(\"p\", null, \"Discussion Topics\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Describe system under test and its \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Include threats, targets and/or situations likely to require \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Describe what must be simulated and why (much simulate moving\\nvehicle targets; insufficient quantity at test ranges, etc.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Explain why you selected a particular test capability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identify measures that require test capability to rate\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Describe the risks of using a specific test capability in terms of\\nthe effect on rating specific measures of effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"),\\nmeasures of performance (MOPs), and measures of suitability (MOSs).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What is the likelihood of drawing an incorrect conclusion on\\neffectiveness/suitability?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Explain how you will convince yourself the capability is acceptable\\nfor use in a specific test\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identify accreditation criteria\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Typically involves comparison of test capability performance to some\\nknown or expected values\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Explain your accreditation timing\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" information is available or missing?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What are the risks of accrediting before the start of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E versus\\nafter?\"))), mdx(\"p\", null, \"Based upon review of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" reports, the test team produces an\\naccreditation report. The accreditation report summarizes the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" report\\nfindings and concludes with a recommendation to either: accredit,\\naccredit with limitations, or do not accredit the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \". The typical\\noutcome will be accredit\", \"-\", \"-accredit with limitations will be by\\nexception. The accreditation report should include a summary statement\\nthat the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" is accredited for a specific \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to address specific\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"/MOPs/MOSs. The test team submits the accreditation report to A-2/9\\nfor review and coordination and then A-2/9 submits the report to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \" for\\napproval.\"), mdx(\"p\", null, \"From a timing standpoint the team should strive to publish the\\naccreditation report prior to test readiness review (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \"). This ensures\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" leadership is aware of all risks associated with using \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" prior\\nto the use of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \". Sometimes it is not possible to publish the\\naccreditation report prior to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \". In this case the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" should include\\ninformation in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \" briefing characterizing the risk associated with\\nusing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" and any mitigating factors, and include information regarding\\nwhen the accreditation report will be published.\"), mdx(\"p\", null, \"Next, the test team will use \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" as planned (e.g. execute the test),\\nconsider lessons learned associated with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" process, and document\\nthose lessons learned in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E final report.\"), mdx(\"p\", null, \"Finally, A-2/9 reviews the lessons learned and considers adjustments to\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" process as needed. A-2/9 ensures the accreditation\\nplans/reports are archived and submits any necessary metadata to the\\nappropriate agency.\"), mdx(\"h1\", null, \"Accreditation Plan and Report Format\"), mdx(\"p\", null, \"A sample format for accreditation plans and reports is located on the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint.\"), mdx(\"p\", null, \"The format is based upon MIL\\u2011STD\\u20113022, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Standard Practice\\nDocumentation of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" for Models and Simulations. Accreditation\\ndocumentation need not be voluminous, but should provide sufficient\\ninformation to enable the accreditation authority to make the\\naccreditation decision. The selected format (determined collaboratively\\nby the test team and A-2/9) will depend on past use of the test\\ncapability, the number of measures impacted, resources needed for\\naccreditation, the test schedule and other factors. If the plan or\\nreport is distributed outside of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", it needs to be properly marked\\nalong with the appropriate distribution statement.\"), mdx(\"h1\", null, \"Accreditation References and Resources\"), mdx(\"p\", null, \"The following are organizations that the accreditation team can\\nreference for assistance in gathering pertinent accreditation\\ninformation.\"), mdx(\"h1\", null, \"Air Force Agency for Modeling and Simulation\"), mdx(\"p\", null, \"The Air Force Agency for Modeling and Simulation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Agency for Modeling and Simulation\"\n }, \"AFAMS\"), \") (\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.afams.af.mil\"\n }, \"http://www.afams.af.mil\"), \" ) is a field operating agency of the Deputy\\nChief of Staff for Operations, Plans and Requirements, Headquarters U.S.\\nAir Force. The Agency is located in Orlando\\\\'s Central Florida Research\\nPark, with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \", Joint, service, contractor, and educational\\norganizations focused on modeling and simulation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Agency for Modeling and Simulation\"\n }, \"AFAMS\"), \"\\\\' mission\\nis to provide seamless integration of cross-functional Live Virtual\\nConstructive-Operational Training environments that allow warfighters to\\nmaximize performance and decision making. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Agency for Modeling and Simulation\"\n }, \"AFAMS\"), \" works closely with\\nCombatant Commands, Major Commands, the Air Force Reserve Command, the\\nAir National Guard, the Air Force Headquarters, Direct Reporting Units,\\nand Field Operating Agencies to provide the necessary development and\\nimplementation standards for common access and interoperability within\\nthe Live, Virtual and Constructive (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Live, Virtual, and Constructive\"\n }, \"LVC\"), \") Training domains for efficient\\nand secure global operations.\"), mdx(\"h1\", null, \"Modeling and Simulation Coordination Office\"), mdx(\"p\", null, \"The Department of Defense (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \") Modeling and Simulation Coordination\\nOffice (M&\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Contracting Official\"\n }, \"SCO\"), \") ( \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.msco.mil)\"\n }, \"http://www.msco.mil)\"), \" is the focal point for\\ncoordinating all matters regarding modeling and simulation across the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" for the Undersecretary of Defense (Acquisition, Technology and\\nLogistics) \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.acq.osd.mil/\"\n }, \"(\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \"(\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L))\"), \" . M&\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Contracting Official\"\n }, \"SCO\"), \" recommends\\npolicies, plans, and programs to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \"(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L) that supports the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nStrategic Vision and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" priorities. Among other documents, MSCO\\nmaintains the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" Recommended Practices Guide.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" provides the M&\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Contracting Official\"\n }, \"SCO\"), \" a descriptive summary and metadata for all\\naccredited models or simulations that can potentially be reused by other\\nprograms.\"), mdx(\"p\", null, \"On 18 March 2020, M&\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Senior Contracting Official\"\n }, \"SCO\"), \" released a new \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" Guidebook. The guidebook is a\\ncompendium of short articles that capture key concepts in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" realm.\\nAccording to their website, the intent of the guidebook is to \\\"provide\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" practitioners an information resource to leverage existing\\nknowledge, past experience, and available tools.\\\"\"), mdx(\"p\", null, \"Organizations supported by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" need visibility into the tools, data and\\nservices that meet their requirements. The DOD \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" steering committee\\nhas established a web based search capability to provide a card catalog\\nlevel of detail about \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" tools, data and services. The catalog is\\noperated by the DMSC. Register to view this catalog here:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:MSCatalogHelpDesk@mscatalog.msco.mil\"\n }, \"MSCatalogHelpDesk@mscatalog.msco.mil\")), mdx(\"h1\", null, \"Best Practices\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"It is OK to conclude that the test capability is inadequate or to\\nrecommend that the test capability not be accredited for use;\\ninclude justification and documentation. Establish acceptance\\ncriteria in terms of comparison to known baseline. Can recommend\\nAccredit, accredit w/ limitations, don't accredit\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Computer-based constructive models must be approved for use on Air\\nForce networks; start early\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure that a clear link exists between test capability use and test\\nlimitations\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Convince the Accreditation Authority the level of risk is\\nacceptable. Answer the question: \\\"To what extent is this\\nrepresentation adequate for purposes of a given test?\\\"\"))), mdx(\"h1\", null, \"Summary\"), mdx(\"p\", null, \"Models and simulations will not be 100% accurate and there is risk\\nassociated with drawing inferences about the models and their\\napplicability to actual systems. There is potential to draw incorrect\\nconclusions about \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance based on use of a particular test\\ncapability. Remember AFOTECs credibility is at stake with every report.\\nEnsuring due diligence will result in a robust and valid accreditation\\nprocess. Inherently, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assumes some degree of risk when using test\\ncapabilities to represent an employment environment to determine \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\ncapabilities. The purpose of accreditation is to assess and document\\nthat risk.\"), mdx(\"p\", null, \"Remember that acceptability criteria are the most important concepts of\\nAccreditation. Make sure to consider the following: How confident are\\nyou that the proposed test capability is acceptable for use during the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"? List the pros and cons. What acceptability criteria did you\\nestablish? What research/analysis did you perform? How did you reach\\nyour conclusions? The accreditation plan and report configuration is at\\nthe discretion of the test team. It is acceptable to have one plan and\\nmultiple reports, or multiple plans and multiple reports. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nSharePoint site contains current accreditation information and\\ntemplates, including the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" Recommended Practices Guide.\"), mdx(\"h1\", null, \"References and Resources\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Accreditation Statement.\"), \" \\\"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" accredits \", \"[\", \"model\", \"]\", \" for use\\nin \", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\", \"]\", \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to address the following\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \":\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"_\", \"\\\"\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example \\\"Delta Accreditation\\\" Memo\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://www.msco.mil/DocumentLibrary/MSReferences/PolicyGuidance/DMSRA_Ver1_0_Dist_A.pdf\"\n }, \"Defense Modeling and Simulation Reference Architecture, Version\\n1.0\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/513401p.pdf\"\n }, \"DoDD 5134.01, Under Secretary of Defense for Acquisition,\\nTechnology, and Logistics (\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \"(\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L), April 1,\\n2008\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/500059p.pdf\"\n }, \"DoDD 5000.59, \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Modeling and Simulation (\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \") Management, August\\n8,\\n2007\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/832002p.pdf\"\n }, \"DoDD 8320.02, Data Sharing in a Net-Centric Department of Defense,\\nApril 23,\\n2007\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500061p.pdf\"\n }, \"DoDI 5000.61, \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Modeling and Simulation (\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \") Verification,\\nValidation, and Accreditation (\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \"), December 9,\\n2009\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/500070_2012_ch1.pdf\"\n }, \"DoDI 5000.70, Management of \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Modeling and Simulation Activities,\\nMay 10 2012. Incorporating Change 1, Effective March 19,\\n2014\"), \"\\n\", 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\": \"24px\"\n }\n }, \"\\n \", mdx(\"span\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-background-image\",\n \"style\": {\n \"paddingBottom\": \"75%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAAsTAAALEwEAmpwYAAADR0lEQVQ4y3WTX0hTcRTHj3eig0KiInoNCqJeeuihB3uzZ+mtx6CHwP7Qc+B/rNTACMweSlfqLi4bY043XJSxtUbWnFvmNJuklf3Z3Fz+abu799s5txUR9IMv53fO75zP73B+9xLxGh4ernA4HMRyer1e+P3+wvj4OP4Vx+F2uw2Px4Pp6WkNwL5sNku5XE4R+2cJ0Gaz0cDAgHNtbY3zUMB/VjQaxfLysh6PxxEOh7c4dJhFmUxGMWHzAnQ4Kmz375vAdCplAnVdx98qapoJjEQiBgNlm0/MziIQCDwNBIMUCgYrhUVvBNjfX6F2dVG/qjpXs1kTaPzTmV6ysdevMTI2ZoQnJ7VgKASuGRq6cYPUvr6KN7+BxC03Fgqk2myu9KdPwI8fmr65CaNQgL6xAX193RTYz7NNffyIzMqKlpyZgaO319WWz5sMk/WONUtUN8ehhKJszW/fjrc7dhhzlZVIcOxtVZX4mN+2DbPil5djkf3FXbuM5O7dSFitW1IrDGHRFNHBCAciiqK/ZPuls9NY41f81t2NaYa/O3kSq3Y7Mg4Hluvq8EouPnoUqbt3kXU6jQ8XL2KSSJ+yWCAsChDtZyFosWgTRMbW0hI+2+3GxsIC3jc1YeH8eXN2i42NKObzSJw6heixYzB4JRsaEDtxwnhKpAUUBcIiH9EBFnwM9LDNxWLIvXgBLZ1G7PRpzJw7B51BI3yWevQIS7dv4zl3WORZZicm8PzIEYwy0FdWBmHRQ6ay8NBiKarc4aZ0yIXPamuhymxaW399fxcuoPj9OyJnz2KiupqfXcfj48fhqqoyhomKJkM6tBEdusfOgKLkenkWK3LrmTMGx9HHmrx0Cet8SS6ZRLy9HYNWK/w1NViNRg2uAefp/UQ5YQiL7hDt7CGa6+aWuzl4lROuse1kXWfJ/kpJV0vxjpLP57rUSK0whEU3+aU79uzZy4ctPTU18Sf19Qg3Nxef8cBFIX6YUHPzL/HejPMDhVtaio8vX4bUSK0whCVASxQov1VbS6rfr5Z+4v/+y3+tgiRJjdQKQ1jUxdDB1lar5+tXGhocdI263fCNjmpe/hbHRkbgFfHexxL7x+ccyX1gt7vG0mmyt7VZhfUTcnT0J9JSq5oAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"https://www.msco.mil/images/pdf.png\",\n \"title\": \"https://www.msco.mil/images/pdf.png\",\n \"src\": \"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png\",\n \"srcSet\": [\"/static/254e90e86c285a1c9074bbb89b4d3ca1/8f029/image6.png 24w\"],\n \"sizes\": \"(max-width: 24px) 100vw, 24px\",\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 \"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://www.msco.mil/MSReferences/MSResourceDiscovery.aspx\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" Community of Interest Discovery Metadata Specification\\n(MSC-\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Defensive Management System OR Diminishing Manufacturing Sources\"\n }, \"DMS\"), \")\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Documents from Recommended Practices Guide\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/UserLegacy/user-leg-pr.pdf\"\n }, \"User's Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of Legacy\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/VVAgentLegacy/vv-leg-pr.pdf\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" Agent\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of Legacy\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/AccAgentLegacy/aa-leg-pr.pdf\"\n }, \"Accreditation Agent\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of Legacy\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/UserNew/user-new-pr.pdf\"\n }, \"User\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/DeveloperNew/dev-new-pr.pdf\"\n }, \"Developer\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/ManagerNew/pm-new-pr.pdf\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \"\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/VVAgentNew/vv-new-pr.pdf\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" Agent\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Role/AccAgentNew/aa-new-pr.pdf\"\n }, \"Accreditation Agent\\\\'s Role in the \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \" of New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Conceptual/conceptual-pr.pdf\"\n }, \"Conceptual Model Development and\\nValidation\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/DataVV-New/DataVV-new-pr.pdf\"\n }, \"Data \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" for New\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/DataVV-Leg/DataVV-Leg.pdf\"\n }, \"Data \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" for Legacy\\nSimulations\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Fidelity/fidelity-pr.pdf\"\n }, \"Fidelity\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/HBR-Validation/hbr-validation-pr.pdf\"\n }, \"Human Behavior Representation\\nValidation\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Paradigm/dev-paradigm-pr.pdf\"\n }, \"Paradigms for \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \"\\nDevelopment\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Requirements/Requirements-pr.pdf\"\n }, \"Requirements\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Risk/Risk-pr.pdf\"\n }, \"Risk and Its Impact on\\n\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \"\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/SME/sme-pr.pdf\"\n }, \"Subject Matter Experts and\\n\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \"\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/Validation/Validation-pr.pdf\"\n }, \"Validation\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/environment/environment-pr.pdf\"\n }, \"Foundations for \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" of the Natural Environment in a\\nSimulation\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Special_Topics/measures/measures-pr.pdf\"\n }, \"Measures\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Ref_Docs/HBR/beh-ref-pr.pdf\"\n }, \"Human Behavior Representation (HBR) Literature\\nReview\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Ref_Docs/Datadefs/Datadefs-pr.pdf\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" Data Concepts and\\nTerms\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://vva.msco.mil/Ref_Docs/Val_Lawref/Val-LawRef-pr.pdf\"\n }, \"A Practitioner\\\\'s Perspective on Simulation\\nValidation\")))), mdx(\"h1\", null, \"Governance\"), mdx(\"p\", null, \"DoDI\\xA05000.02, 7 Jan 15: \\\"Every distinct use of a model or simulation in\\nsupport of an operational evaluation will be accredited by an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \", and,\\nfor programs under \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Oversight, its use for the operational\\nevaluation will be approved by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \".\\\"\"), mdx(\"p\", null, \"DoDI 5000.61, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Modeling and Simulation (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \") Verification,\\nValidation, and Accreditation (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \")\"), \" , 9 Dec 09, para 4.a-b: \\\"Models,\\nsimulations, and associated data used to support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" processes,\\nproducts, and decisions shall undergo verification and validation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \")\\nthroughout their lifecycles. Models, simulations, and associated data\\nused to support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" processes, products, and decisions shall be\\naccredited for an intended use.\\\"\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 16-1001, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Verification, Validation and Accreditation (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Verification, Validation and Accreditation\"\n }, \"VV&A\"), \")\"), \" , 29\\nApr 2020, para 2.3: \\\\\\\"Air Force \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" applications will be accredited for\\ntheir intended purpose when supporting major \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" decision-making\\norganizations or processes, joint training, and joint exercises. All\\nexecuted \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" activities will support the model acceptance and\\naccreditation requirements defined by the accreditation authority.\\\\\\\"\"), mdx(\"h1\", null, \"Points of Contact\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"The \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" staff lead for Accreditation is A-2/9. Refer questions\\nabout Verification, Validation, and Accreditation to\\n\", mdx(\"a\", {\n parentName: \"li\",\n \"href\": \"mailto:UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"\n }, \"UDG_AFOTEC.A2A9_AFOTECA2A9@us.af.mil\"), \" .\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#test-capability-accreditation","title":"Test Capability Accreditation"},{"url":"#the-use-of-modeling-and-simulation","title":"The Use of Modeling and Simulation"},{"url":"#verification-validation-and-accreditation-definitions","title":"Verification, Validation and Accreditation Definitions"},{"url":"#acquisition-implications-of-verification-validation-and-accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"},{"url":"#accreditation-concepts","title":"Accreditation Concepts"},{"url":"#risk-matrix-example","title":"Risk Matrix: Example"},{"url":"#previous-accreditation","title":"Previous Accreditation"},{"url":"#accreditation-process","title":"Accreditation Process"},{"url":"#test-capability-accreditation-concept","title":"Test Capability Accreditation Concept"},{"url":"#accreditation-plan-and-report-format","title":"Accreditation Plan and Report Format"},{"url":"#accreditation-references-and-resources","title":"Accreditation References and Resources"},{"url":"#air-force-agency-for-modeling-and-simulation","title":"Air Force Agency for Modeling and Simulation"},{"url":"#modeling-and-simulation-coordination-office","title":"Modeling and Simulation Coordination Office"},{"url":"#best-practices","title":"Best Practices"},{"url":"#summary","title":"Summary"},{"url":"#references-and-resources","title":"References and Resources"},{"url":"#governance","title":"Governance"},{"url":"#points-of-contact","title":"Points of Contact"}]},"parent":{"__typename":"File","relativePath":"fn_guides/accreditation_guide.md"},"frontmatter":{"metaTitle":"Accreditation Guide","metaDescription":"Accreditation Guide"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"60d0d63d-0770-5cac-8cf2-b116c38568ac"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/fn_guides/analyst_test_design_guide/page-data.json b/sites/oteguide/page-data/fn_guides/analyst_test_design_guide/page-data.json deleted file mode 100644 index 728d8ba3..00000000 --- a/sites/oteguide/page-data/fn_guides/analyst_test_design_guide/page-data.json +++ /dev/null @@ -1 +0,0 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides/analyst_test_design_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"c74500cd-1ebf-56c9-942f-23d8e3775c83","title":"Analyst Test Design Guide","slug":"/fn_guides/analyst_test_design_guide"},"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\": \"Analyst Test Design Guide\",\n \"metaTitle\": \"Analyst Test Design Guide\",\n \"metaDescription\": \"Analyst Test Design Guide\"\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, \"Last Updated/Reviewed: 08 December 2020\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9\"), 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\": \"742px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/9bb00d4f6f07179b37c87073f951944c/24ee3/image1.jpg\",\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\": \"71.42857142857143%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/jpeg;base64,/9j/2wBDABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVGC8aGi9jQjhCY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2P/wgARCAAOABQDASIAAhEBAxEB/8QAGAAAAgMAAAAAAAAAAAAAAAAAAAECAwX/xAAUAQEAAAAAAAAAAAAAAAAAAAAA/9oADAMBAAIQAxAAAAHcFEtEH//EABkQAAIDAQAAAAAAAAAAAAAAAAABAhARMf/aAAgBAQABBQKkJmkef//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQMBAT8BP//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQIBAT8BP//EABUQAQEAAAAAAAAAAAAAAAAAABAB/9oACAEBAAY/Amv/xAAbEAACAwADAAAAAAAAAAAAAAAAEQEhMRBBYf/aAAgBAQABPyG3NHWGBk+BVnB//9oADAMBAAIAAwAAABCwz//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQMBAT8QP//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQIBAT8QP//EABsQAQEAAwEBAQAAAAAAAAAAAAERACExQWFx/9oACAEBAAE/ED1NV/cVto83hexH7gQXrLVsCW4hs4qhOZ//2Q==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image1\",\n \"title\": \"image1\",\n \"src\": \"/static/9bb00d4f6f07179b37c87073f951944c/24ee3/image1.jpg\",\n \"srcSet\": [\"/static/9bb00d4f6f07179b37c87073f951944c/8356d/image1.jpg 259w\", \"/static/9bb00d4f6f07179b37c87073f951944c/bc760/image1.jpg 518w\", \"/static/9bb00d4f6f07179b37c87073f951944c/24ee3/image1.jpg 742w\"],\n \"sizes\": \"(max-width: 742px) 100vw, 742px\",\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, \"OVERVIEW\"), mdx(\"p\", null, \"This guide is an overview of test design, with a strong focus on the\\ntypes of designs that are most often used in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \". It is intended to\\nserve as a reference for both new and senior analysts and assumes\\nfamiliarity with the \", 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 Guide. It is meant to be consulted\\nseveral times during the life of a test program. The guide begins by\\npresenting an overview of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s Initial Test Design Framework. The\\nbulk of this guide presents the types of test designs typically used at\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", their strengths and weaknesses, and their measures of merit. The\\nremainder of the guide discusses common situations encountered in test\\ndesign along with suggested remedies, as well as best practices and\\npitfalls.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is charged with evaluating the operational effectiveness,\\nsuitability, and mission capability of a system under test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"). That\\nevaluation must be technically credible; i.e., the results must be\\naccurate and sufficient to support and defend the conclusions the test\\nteam reports.\"), mdx(\"p\", null, \"Operational sufficiency and technical adequacy are the foundation for\\ntechnical credibility. Operational sufficiency addresses the breadth of\\noperations and conditions, test execution, and whether the test was\\nconducted in an operationally realistic and representative environment.\\nThe focus of this guide is on the second critical area: technical\\nadequacy. A test is technically adequate if analysis of the test data\\nprovides the user/warfighter with sufficient information to make\\nfielding and employment decisions. This guide provides information to\\ncreate a statistically rigorous test design that will lead to a\\ntechnically adequate test.\"), mdx(\"p\", null, \"Creating statistically rigorous test designs takes careful planning. All\\ntests are designed; some are designed well and some are designed poorly.\\nThe principles and concepts of design of experiments (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \") provide\\ntime-tested statistical tools and methods for maximizing the information\\nobtained from a test. Using this test design guide, a test analyst can\\nmake design choices based on a sound understanding of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" principles. As\\na result, the analyst will be able to collect and analyze the\\nappropriate data leading to an objective and defensible report.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" process to execute an operationally sufficient and\\ntechnically adequate test is grounded in the seven-step design of\\nexperiments process (Montgomery, 2013). Table 1 lists the seven steps on\\nthe left and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s coinciding steps and events on the right.\"), mdx(\"p\", null, \"Table 1. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Processes\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"DOE Process Step\"), mdx(\"th\", null, \"AFOTEC Process\"), mdx(\"th\", null, \"AFOTEC Event\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"1. Recognize and state the problem\"), mdx(\"td\", null, mdx(\"p\", null, \"Understand missions and battlespace through the development of the EV-1, requirements/EV-2, COIs/operations/OCs, and ESC\"), mdx(\"p\", null, \"Determine the purpose/goal of test\")), mdx(\"td\", null, \"ITD Meeting\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"2. Select the response variable\"), mdx(\"td\", null, \"Define mission oriented response variables (MORV)\"), mdx(\"td\", null, \"ITD Meeting\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"Develop Measures\"), mdx(\"td\", null, \"Measures Workshop\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"3. Choose the factors, levels and range\"), mdx(\"td\", null, mdx(\"p\", null, \"Develop factors and levels\"), mdx(\"p\", null, \"Apply factor management\")), mdx(\"td\", null, \"ITD Meeting\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"4. Choose the experimental design\"), mdx(\"td\", null, mdx(\"p\", null, \"Choose and evaluate the design based on the goal of the test, factors and levels, and factor management\"), mdx(\"p\", null, \"Develop scenarios and test events\")), mdx(\"td\", null, \"Post ITD Meeting\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"Develop Scenario-measures-test event linkage\"), mdx(\"td\", null, \"Test Concept Brief Preparation\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"5. Perform the experiment\"), mdx(\"td\", null, \"Execute the test\"), mdx(\"td\", null, \"Test Execution\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"6. Analyze the data\"), mdx(\"td\", null, \"Analyze the data\"), mdx(\"td\", null, \"Post Execution\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"7. Draw conclusions and make recommendations\"), mdx(\"td\", null, \"Report\"), mdx(\"td\", null, \"Reporting\")))), mdx(\"p\", null, \"This guide briefly discusses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" process steps 1 through 3 framed within\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test planning process, but focuses on step 4: the process of\\nselecting an appropriate test design.\"), mdx(\"h1\", null, \"ELEMENTS OF THE TEST PLANNING PROCESS\"), mdx(\"h2\", null, \"Critical Operational Issues and Operations\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" process begins with a thorough understanding of the missions\\nthat the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is expected to enable or support; the \", 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 Guide\\nprovides an overview of this process. Once the mission is defined, the\\ncore team identifies the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" and subordinate operations. Operations are the distinct activities or\\nprocesses that occur within a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" and are the focus of test design. Each\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" will have at least one operation.\"), mdx(\"h2\", null, \"Response Variables\"), mdx(\"p\", null, \"Each operation under a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" shall have at least one Mission Oriented\\nResponse Variable (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \"). A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" is an indicator that a system under\\ntest can successfully accomplish its mission in the operational\\nenvironment. MORVs are the dependent variables that guide the initial\\ntest design (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \") process. Ideally, a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" should be \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"quantitative\")), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn1\"\n }, \"1\"), \" . If a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" is \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"qualitative\")), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn2\"\n }, \"2\"), \" an analyst should develop one or more\\ncontinuous response variables (measures) to complement it. While a\\nqualitative \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" may be a satisfactory indicator of mission success, it\\nmight also require considerably more testing and resources than a\\nquantitative \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \". In statistical terms, for a given test size, the\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"population parameter\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn3\"\n }, \"3\"), \"\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"estimates\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn4\"\n }, \"4\"), \" for a continuous\\nresponse have less variability than estimates for the population\\nparameter for a binary response. Therefore tests using binary MORVs must\\nhave a significantly larger \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"sample\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn5\"\n }, \"5\"), \" size than tests using continuous MORVs; i.e., more runs\\nare required to achieve equivalent statistical quality and precision of\\nthe parameter estimates. Thus qualitative MORVs should be used with\\ncaution.\"), mdx(\"p\", null, \"Ideally, a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" should be written as a measure (see the \", 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 Guide\"), \"\\nfor further guidance on writing measures). However, it is not necessary\\nthat a measure threshold be identified for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \". If a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" becomes a\\nmeasure during the measures workshop, the appropriate detail is then\\nadded.\"), mdx(\"h1\", null, \"Factors, Levels, and Prioritization\"), mdx(\"p\", null, \"A key event in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" process is the initial test design (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \")\\nmeeting. The following organizations send representatives to this\\nweek-long event: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" headquarters; the detachment conducting the\\noperational test; Director, Operational Test and Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \"); the\\nInstitute for Defense Analysis (IDA); the program office (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Office OR Project Officer\"\n }, \"PO\"), \"); the\\ndevelopmental test organization; and subject matter experts from the\\nuser community.\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" has several phases. In the first phase the COIs, operations, and\\nMORVs are refined and vetted. In the second phase the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" participants\\ndevelop a list of \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"factors\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn6\"\n }, \"6\"), \" and\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"levels\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn7\"\n }, \"7\"), \" (F&L) that apply to each\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" under an operation. Factors are the independent variables that\\ndefine the battlespace---with a range of values called levels---that may\\naffect a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" when the factor's level is changed.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Operational Test & Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) Guide has several\\nexamples of desirable factor characteristics that should be considered\\nduring the test design process. There are attributes of the factors\\n(quantitative data type, qualitative data type, number of levels, etc.)\\nwhich will significantly affect the size and quality of the test design.\\nThese attributes should be considered by the analyst as they facilitate\\nthe F&L discussion during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" process.\"), mdx(\"p\", null, \"In addition to the characteristics and examples in the \", 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\\nGuide, the facilitator should consider the following:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"It is a best practice to use quantitative factors with numeric\\nvalues for levels (e.g., Altitude: 10,000 ft and 30,000 ft) instead\\nof categorical factor levels (e.g., Altitude: Low and High).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Factor levels must be mutually exclusive, meaning that two levels of\\nthe same factor describe conditions that cannot simultaneously\\noccur.\"))), mdx(\"p\", null, \"In phase three, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" participants determine two things: the magnitude\\nof a factor's impact on each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \", and the likelihood of each factor\\nlevel occurring in the operational environment. Based on the combination\\nof a factor's impact and the likelihood of occurrence for each of its\\nlevels, the test team chooses one of four methods for incorporating that\\nfactor in the test design.\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Vary\"), \" -- The factor is deliberately manipulated during the test\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Fix\"), \" -- The factor level is held constant during the test\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Log\"), \" -- During a test run, the level of this factor is recorded\\nas an observation\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Demo\"), \" -- The level will be incorporated into a test run that is\\nexecuted and analyzed separately from the design incorporating the\\nvaried factors\"))), mdx(\"p\", null, \"Choosing one of the four methods for each factor is referred to as\\nfactor management. Figure 1 gives general guidance on which of the four\\nmanagement methods to select for a factor level given a combination of\\nthe factor's magnitude of impact and the likelihood of encountering the\\nfactor level.\"), mdx(\"p\", null, \"Figure 1. Factor Management Guidance\"), 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\": \"610px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/b76f614222db541cc6f859ec0a16434d/5aae9/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\": \"64.09266409266408%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAIAAAAmMtkJAAAACXBIWXMAAAsTAAALEwEAmpwYAAACAUlEQVQoz3VSy5KbMBDk/7/EB/vg8s2HJJc4yVY5tXZILeAneiCeEg9hQIB32yapnDKlQzNoZnq6ZWVSRlGUpglnLIkTIUQUxYxxEQSU0iRJ3/8flue5nPO6rvNc+Vcf53Q6S6l6Y5pb07ad6QxOh2i7tm2bBucGMI6jdfA8IcIgCDDqcr4AnE+nOI5rXcssy9LkevU541EIdmkcJ1I+0krlwzBYmH6/38dxaLsOGKnxGeCfxDGY/Nrb2+32crkqpVD2/rh8R5HruqB9QLYsS0ap63pFUehag9XLj5fPn74QyiDHdvtzs9m8vu4YY8fj0bbtNMtms5kVcIHivu9DIb59/Y79JzGECIqyBNBVRQjpTT/0fRSFjuNgZ+RXq5UVhVgYSwvXcd/eHKxdVZUxBl2KogRQUmJtY9C/55x5ngeATReLhUV8Am8gLCMEl7JMal2jcZ7nqASoa43uEx1oBvEmvFwurbLEpAoKMULt/W+ZyfYZuAf/UJ8rRQmFU8AB52B3uzUQ7TE5TaG7RCdMxoSH0MMAVqEIq0ojX5Ul58FkCtSBVXDkz2RcnT6o7/uE4srkltZ6yqOYIP90sdYaTv0rBiX0wzeKd7u9kso8A1oAowtogxFEQjLBc01TrAAW8/ncwttomgY/4PPhcGz/Bgyf8ijGEwRAEio2z8Cw9Xr9AQnz0qI7lHiNAAAAAElFTkSuQmCC')\",\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/b76f614222db541cc6f859ec0a16434d/5aae9/image3.png\",\n \"srcSet\": [\"/static/b76f614222db541cc6f859ec0a16434d/a2ead/image3.png 259w\", \"/static/b76f614222db541cc6f859ec0a16434d/6b9fd/image3.png 518w\", \"/static/b76f614222db541cc6f859ec0a16434d/5aae9/image3.png 610w\"],\n \"sizes\": \"(max-width: 610px) 100vw, 610px\",\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 test team should keep in mind that the factor level likelihood\\nshould be determined in the context of the system conducting its\\nmission, not the likelihood the level occurs in general. For example, a\\nfactor level related to a nuclear weapon system may be very unlikely in\\npeacetime, but may be very likely in the context of a nuclear weapon\\nemployment. The latter is the likelihood that should be documented.\"), mdx(\"p\", null, \"It is important to remember that even if a factor's levels occur in\\nunequal proportions in the operational environment, the frequency that\\nthe levels occur in the test design may not coincide with those\\nproportions. Factor levels that occur disproportionally frequently (or\\ninfrequently) in the test design could create an unrepresentative sample\\nof the system's overall performance across a typical set of operational\\nconditions. Consequently, the test design could cause an overly\\npessimistic or optimistic assessment of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"Test Design Workbook\"), mdx(\"p\", null, \"The major product from an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" that summarizes the test planning elements\\nand F&Ls is the Test Design Workbook (TDW). Figure 2 shows the F&L tab\\nfor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1 from the TDW for the X-100 Block Upgrade 1.1 (X-100 is a\\nfictitious program). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Does X-100 1.1 support Airland operations\"), \"\\n, is shown at the top. This \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" had three operations: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff &\\nDeparture, Enroute,\"), \" and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Arrival\"), \" . Operation 1, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff & Departure\"), \"\\n, is shown underneath \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" for Operation 1 is \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Delta Time\\nbetween Planned and Actual Take-Off Time\"), \" .\"), mdx(\"p\", null, \"The test team developed a list of 23 factors for Operation 1 at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \".\\nHowever, only two will be strategically controlled (varied) during the\\noperational test. The other factors will either have their levels\\ndemonstrated (demo), fixed during the test \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"runs\")), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn8\"\n }, \"8\"), \", or logged. Typically factors will\\nbe logged because the levels cannot be controlled. However, for some\\nfactors that are controllable but judged to be inconsequential, the\\nanalyst may choose to log the levels in case the factors are actually\\nsignificant.\"), mdx(\"p\", null, \"Four of 23 factors are shown: two factors to be varied and two factors\\nthat cannot be controlled (which will be logged.) In the columns under\\nprioritization, the test team noted the magnitude of impact of the\\nfactor, and the likelihood of encountering each factor level.\"), mdx(\"p\", null, \"Figure 2. F&L Tab of TDW\"), mdx(\"p\", null, \"Accurately selecting and prioritizing factors, levels, and their impact\\non the system's MORVs is extremely important to ensure the test design\\nselected will achieve the test goal.\"), mdx(\"h1\", null, \"GOALS AND TYPES OF TEST\"), mdx(\"p\", null, \"Before selecting the test design, the goal of the test must be\\nestablished. The goal not only determines how the test is designed and\\nexecuted but how it is reported as well. Within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", there are\\ngenerally three goals of a test:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"characterize system performance\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"compare system performance to a requirement or to another system\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"identify problems with the system\"))), mdx(\"p\", null, \"A test program may include up to all three test design goals. Generally,\\neach goal will have its own collection of test events based on one of\\nthe design types outlined later in this guide. The above list states the\\ncommon goals in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" testing, but it is not all-inclusive. If a test\\nteam has a different goal for their operational test, they should\\nprovide an explanation including the unique nature of the desired test\\ngoal and how it affects the design, execution, and reporting of the\\ntest.\"), mdx(\"h1\", null, \"Characterize\"), mdx(\"p\", null, \"When characterizing a system, the test goal is to analyze the system's\\nmeasures across the operational conditions (battlespace) defined by the\\nfactors and levels. In addition, the test team quantifies the\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"effect\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn9\"\n }, \"9\"), \" that changing factor\\nlevels (and combinations of factor levels) have on the measures. To\\naccomplish this test teams use test designs that allow the estimation of\\nthe factors' \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"main effects\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn10\"\n }, \"10\"), \"\\nand the factor \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"interactions\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn11\"\n }, \"11\"), \"\\n.\"), mdx(\"p\", null, \"Designs used to characterize the system vary the levels of multiple\\nfactors simultaneously with the intent of testing and reporting the\\nperformance of a system under different operational conditions. They\\nalso enable an analyst to determine which factors are most influential\\non system performance. The data produced by these designs can be used in\\nfuture testing and for the development of operational Tactics,\\nTechniques and Procedures.\"), mdx(\"h1\", null, \"Compare\"), mdx(\"p\", null, \"When the goal of a test is to compare, the test team gathers data on a\\nsystem and compares it to data from another system, to a requirement\\nthreshold, or to some other criterion. System comparisons do not provide\\ninformation about the system's performance across the battlespace.\"), mdx(\"h1\", null, \"Problem Identification\"), mdx(\"p\", null, \"When one of the test goals is problem-identification, the test team\\nattempts to determine whether a \\\"success\\\" or \\\"failure\\\" occurs at one or\\nmore factor level combinations that define the battlespace. One approach\\nis to use combinatorial designs; these designs efficiently combine\\nfactor levels so that problems caused by specific factor level\\ncombinations can be identified with less resources than designs used for\\nsystem characterization. However, combinatorial designs do not generally\\nprovide data that can be analyzed with statistical modeling (system\\ncharacterization.)\"), mdx(\"p\", null, \"Another approach is to demonstrate (demo) strategically chosen (and\\nusually infrequently occurring) factor level combinations. The data from\\nthese demo runs are analyzed separately from the data associated with\\ntest runs used to characterize the system performance. The analysis\\nessentially determines if a failure occurred during the demo.\"), mdx(\"h1\", null, \"TYPES OF TEST DESIGNS\"), mdx(\"p\", null, \"Choosing the most appropriate test design is a combination of science\\nand art. The choice requires expertise on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", the operational\\nmission it supports, and \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#_The_Three_Principles\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" principles\"), \" . Each\\nof the designs in this section has strengths and weaknesses depending on\\nthe test goal and the nature of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test program may use a combination of the designs presented in\\nthis section. It is typical to use a separate test design for each\\noperation under a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \", as factors and levels are often different between\\noperations. Some MORVs may even require a separate test design.\"), mdx(\"p\", null, \"Test designs have associated quality indicators; within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" these\\nindicators are referred to as measures of merit. Measures of merit\\nprovide a basis for comparison when choosing between multiple designs.\\nAlso, measures of merit are used as evidence that a test design meets\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" standards for technical adequacy. The Test Design Measures of Merit section of this guide presents a\\nmore detailed explanation of the measures most often used at \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".\"), mdx(\"h1\", null, \"Factorials\"), mdx(\"p\", null, \"A \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"factorial design\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn12\"\n }, \"12\"), \" is a list\\nof test runs in which multiple factors are varied simultaneously from\\nrun to run. This list of runs is called a test event matrix (TEM). The\\nspecial structure of the factor level combinations in the TEM enables\\nthe tester to estimate the main factor effects and interactions between\\nfactors. The following sections discuss two types of factorial designs:\\nfull factorials and fractional factorials.\"), mdx(\"p\", null, \"Full Factorial\"), mdx(\"p\", null, \"A full factorial is a test design that includes every possible\\ncombination of the levels across all factors. Full factorial designs\\nhave the following desirable properties:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Every factor level occurs equally often in the test matrix. For\\nexample, if a factor has 4 levels and there are 16 test runs, each\\nfactor level will occur in 4 runs. This property is related to\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"balance\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn13\"\n }, \"13\"), \" \", mdx(\"strong\", {\n parentName: \"p\"\n }, \",\"), \" and it\\nensures that factor levels do not have a disproportionate influence\\non the analytical results.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The design includes every possible factor level combination in the\\nTEM. This ensures that system performance can be analyzed over the\\nentire battlespace and we can identify factor level combinations\\nthat lead to exceptionally negative or positive performance.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The effects (main effects and all interactions) are completely\\nuncorrelated in the TEM. This means the estimation of each effect is\\nnot biased (influenced) by other main effects and interactions.\"))), mdx(\"p\", null, \"Full factorials are \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"orthogonal\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn14\"\n }, \"14\"), \" , balanced, and easy to construct with or without\\nsoftware. Since every possible factor level combination must be present\\nin a full factorial, these designs are not applicable to test scenarios\\nwith \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"disallowed combinations\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn15\"\n }, \"15\"), \"\\nof factors.\"), mdx(\"p\", null, \"Use the following process to construct a full factorial design in JMP\\n13. The example shown in figure 3 a/b is for the X-100 Block Upgrade 1.1\\nprogram.\"), mdx(\"p\", null, \"Creating Full Factorial Designs in JMP 13:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"From the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" menu, select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Classical\"), \" , then select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Full\\nFactorial Design\"), \" (figure 3a)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Specify the Factors and levels. In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Factors\"), \" section, add the\\ncontinuous and categorical factors using the drop down menu. Specify\\nthe number of levels for each factor. The factors and levels can be\\ngiven appropriate names. Figure 3b shows the input for the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \"\\n1 example.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Continue\"), \" when all of the factors and levels have been\\nentered.\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 3a. Creating a Full Factorial in JMP Figure 3b. Enter the Factors and Levels\"), mdx(\"p\", {\n parentName: \"li\"\n }, 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/736c001347f918ce522b12f0a64d5cd6/9b29b/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\": \"31.27413127413127%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAGCAIAAABM9SnKAAAACXBIWXMAAAsTAAALEwEAmpwYAAABAklEQVQY022Q3W6EIBCFTbyoD+D7v027m1QTe+HNJtvGuv4ioAiDgEhnTdqrfjmZkAlzmEM0zzPn3BoDegMAY1w7MsYlX9QiNwH2dvvK8+L+WdWPrutJP1LGl5GJalgja91+4pwNIRjnJso5Y2534WSibCKEMYpSUq6rwKoA/OEjc6K1xmettUpvVd20TYNndMThrm2/q6rve0ImhFKKN1cJbvdR+OU4jmcNAban3V9/aNr2UWMSQgiaknHUoEDrHYc/ToqiyLIsz/P3LH99u1wvV+yUZem9HwjFqJgTNS+rkLCsivJl9z56+Y8kSeI4TtNUCOEP3MXqUxLwX1EWK+74A/+SNkC1sjEVAAAAAElFTkSuQmCC')\",\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/736c001347f918ce522b12f0a64d5cd6/e3189/image5.png\",\n \"srcSet\": [\"/static/736c001347f918ce522b12f0a64d5cd6/a2ead/image5.png 259w\", \"/static/736c001347f918ce522b12f0a64d5cd6/6b9fd/image5.png 518w\", \"/static/736c001347f918ce522b12f0a64d5cd6/e3189/image5.png 1035w\", \"/static/736c001347f918ce522b12f0a64d5cd6/44d59/image5.png 1553w\", \"/static/736c001347f918ce522b12f0a64d5cd6/a6d66/image5.png 2070w\", \"/static/736c001347f918ce522b12f0a64d5cd6/9b29b/image5.png 3840w\"],\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(\"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/d7a5bd76098167c73c567e83925db85f/9b29b/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\": \"31.27413127413127%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAGCAIAAABM9SnKAAAACXBIWXMAAAsTAAALEwEAmpwYAAAA/ElEQVQY01WQ606EMBSESUiUB1jf/23QGFgDP1B/qCwspetKW9oCpRfqgc16+TJJm7ZzZtJA6xlkrWVcEsompaxb5lkbWLyvqvr15flY1wgh0hFKSdeRQRml3aRd4L0H57IslEvc4kFK/wfCGCEwk/V9P2z0QjjnLrcBOJVSep4/O1KWB3gEg+DQGgPJqK7Lt3eMcdu2VVU1TUNpv0Z5Dwp+QqCnNsb/54RPX+cz5xwaSSkgWcrhNznP8zRNkyS5f3iM4/hpv883siwriuLjUDeo5QIs4ziqcVLwNdZezbdXbjYu+yiKwjDc3e2OCHM5ESY6xmkvySqxtV75BmnlOHLX13cnAAAAAElFTkSuQmCC')\",\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/d7a5bd76098167c73c567e83925db85f/e3189/image6.png\",\n \"srcSet\": [\"/static/d7a5bd76098167c73c567e83925db85f/a2ead/image6.png 259w\", \"/static/d7a5bd76098167c73c567e83925db85f/6b9fd/image6.png 518w\", \"/static/d7a5bd76098167c73c567e83925db85f/e3189/image6.png 1035w\", \"/static/d7a5bd76098167c73c567e83925db85f/44d59/image6.png 1553w\", \"/static/d7a5bd76098167c73c567e83925db85f/a6d66/image6.png 2070w\", \"/static/d7a5bd76098167c73c567e83925db85f/9b29b/image6.png 3840w\"],\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Specify your \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Run Order\"), \" ; JMP can output your design runs in\\nrandom order, or sorted from left to right (or right to left) by\\nfactor level. The number of runs is the product of the number of\\nlevels for each factor---in this example the number of runs is\\n3x4x4x3=144.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Choose the number of \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"center points\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn16\"\n }, \"16\"), \" (only applicable when using continuous factors).\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Choose the number of \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"replicates\"), \" . The number of replicates is\\nthe number of times you want the original full factorial design\\nrepeated. Thus 1 replicate implies 2 copies of the full factorial.\\nNote that when reporting the number of replicates in a test design\\nworksheet (TDW), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" convention is to state the number of\\nreplicates as the number of copies; thus, on a TDW, 2 replicates\\nimplies 2 copies.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Table\"), \" (figure 4a)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"JMP outputs a new design table (figure 4b)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 4a. Output Options Figure 4b. The Design Table\\n\", 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/b8c4f14d283db950ec571c959cf4cc5d/07a9c/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\": \"79.15057915057915%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAQCAIAAACZeshMAAAACXBIWXMAAAsTAAALEwEAmpwYAAACfklEQVQozz1S7W6bQBDk/V+lsvOjbZQmTVq5smSlaStVcezajh2Dgfu+44ADYzAdIMnqBFrdzs3O7Hqb/WG32x9CKqQWUjEuCYJTpTVhSuisLE+uqFxx7L+Vtak2VulEm9SbL9fzp81mG25fwpjpKGSr9Wa92/kh2QZi9UKDiB9iGRIZRDKiOohoELKISMIS73G5CPxASSE5L5wTnEZhuHveEhJTSpJEK62M0ZxzpOv1uj4hqrquXZ57QkmtdVWd8j6E4EgFF2VZCMab5ty2LUrzLHcuJ4Q1TQM0vkppryiPVXUsyzJN06IoKKWcsTAMrbVKSRSdz+eqqjSEWuv7wQCu6wbteMWxOh5fwc45RqkUgkSx7QNYVAOcJBYFjPMBjACTt1mt/P2+l0SdAzMRnJOYpFmKctAOYNthU0pZn576U3nL+9n8aUHiGFLBjCcEmAmDRMYYLBzaHsBKKaQDM/r1nh/nu5d9kiTGGIDjOBJSBEGgjaYxgU/ntgOn6ARtw8I3cMds0rz7d9edZgLNSsQxybJMSdX08abZRlH8rrkDu6ILGAZ7OjCJpETbxKY2y/N3zZhUlr1q7pE9GKMaAlR4JY4iLgTWBkKiMMLkMWcUY1RoDVd9+sYslR6mAsNQGpNYCHArdKOVwnoMhhmT4HW8OBgG5s6wp8VSY97GgCfLct/3sZeBf4BB8LxwxQCWSiXWSgm32wrgU43l8g5B2PZRFq5tmzQx1mhrzKk6WoPSpm3PTV25LC1dmlmFZW1P5RmnrrzPd7PryQPO1fef15Nfn25n48vJ6HIyvpqOv0wvbmYXN/fj24fR14fR3Z/Rt78XPxbj6b8P09XH3/v/wgZ9qIOM22EAAAAASUVORK5CYII=')\",\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/b8c4f14d283db950ec571c959cf4cc5d/e3189/image7.png\",\n \"srcSet\": [\"/static/b8c4f14d283db950ec571c959cf4cc5d/a2ead/image7.png 259w\", \"/static/b8c4f14d283db950ec571c959cf4cc5d/6b9fd/image7.png 518w\", \"/static/b8c4f14d283db950ec571c959cf4cc5d/e3189/image7.png 1035w\", \"/static/b8c4f14d283db950ec571c959cf4cc5d/07a9c/image7.png 1440w\"],\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(\"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\": \"922px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/c3f4e9bc392c4923653c3f1d08768083/6da96/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\": \"38.61003861003861%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAICAIAAAB2/0i6AAAACXBIWXMAAAsTAAALEwEAmpwYAAABQ0lEQVQY0zWQW3eCMBCE+f8/y2OLD55K0HK1XgJBwAeUSyGg0k+0e/IwSWZ2Z9Z4PB73/wKP4/jCt9vtd6owDB3HcR23KC5d17VtN04F2WjbFiJsrXVZlk3T9FoPwwDNsixb2Ov1BrAwF6uVRaPN5psDM45j49M0T2l6Pp8RuI4zn3/UdU2voe9ns5kt1kyQ8iiEQLnf75fLpWkuttutbdtGnmVpmtKmuBRhGPAkpey0xpFSCiM0SpIky/On1fudFgwD82h84UaIKIrQiAmQncB93x8Oh6qq4KlExbFiHwR0XUdG8VvseR4ertcr98D3gyBgJhFYQSQjIvCePSvHP03DIFAqeYsZeJnWiMD3fVJlaQZmbbvdT1mVE09BfYkZhou3GEusTk8h+ajrBiWYtKck4YtrHMFXBGGG57nHo2QRBPwDe0640ge6IlgAAAAASUVORK5CYII=')\",\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/c3f4e9bc392c4923653c3f1d08768083/6da96/image8.png\",\n \"srcSet\": [\"/static/c3f4e9bc392c4923653c3f1d08768083/a2ead/image8.png 259w\", \"/static/c3f4e9bc392c4923653c3f1d08768083/6b9fd/image8.png 518w\", \"/static/c3f4e9bc392c4923653c3f1d08768083/6da96/image8.png 922w\"],\n \"sizes\": \"(max-width: 922px) 100vw, 922px\",\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 main weakness of a full factorial design is that the run size grows\\nrapidly with the addition of factors. The number of runs in a full\\nfactorial design is equal to the product of the number of levels of each\\nfactor in the design. In the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1.1 example, if we added just one\\nadditional 2\\u2011level factor, the number of runs in the design would double\\nfrom 3x4x4x3=144 runs to 288 runs! Because the number of runs increases\\nso rapidly, a full factorial design is infeasible for many test programs\\nunless there are only a small number of varied factors.\"), mdx(\"p\", null, \"Rather than reducing the number of varied factors in order to enable the\\nuse of a full factorial design, we recommend using one of the other\\ndesign types that are discussed in the subsequent sections. This\\nrecommendation is rooted in the concept that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" tests should also be\\noperationally sufficient as well as technically adequate. A test is\\noperationally sufficient if it provides both the decision maker and the\\nwarfighter with results drawn from test events executed across a\\nsufficiently broad set of operational conditions.\"), mdx(\"h2\", null, \"Fractional Factorial\"), mdx(\"p\", null, \"A fractional factorial design is a strategically selected fraction\\n(typically \\xBD or \\xBC) of the runs in a full factorial design. These designs\\nhave many of the same advantageous characteristics of a full factorial.\\nDepending on the degree of fractionation, fractional factorials can\\nyield the same information about main effects and two-factor\\ninteractions (2FI) with fewer test runs. They are easy to construct,\\northogonal, balanced, and are an economical alternative to full\\nfactorials.\"), mdx(\"p\", null, \"As an example, suppose the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1.1 program chose to vary four\\ntwo-level factors, as shown in figure 5.\"), mdx(\"p\", null, \"Figure 5. Sample of F&Ls for X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1.1\"), 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\": \"759px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/4242e0d9b98f022be2d75fa3f00e49e9/ef3e1/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\": \"61.38996138996139%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAIAAADtbgqsAAAACXBIWXMAAAsTAAALEwEAmpwYAAAB4klEQVQoz22SyZKbMBCGef+XmkNySOYw4y32MCB2JCyE0AICbMD58aQqh0TV1aWlv17lfeY8pywvGK241J3UVirbtEa2RtseIpVpWmu6YZjubrz1wwTBvXWj93Yiu/1utw99QgOSB1EB8f3wsD/8fHt9fT9GSfHjkPsxL1ibM1lUbYkNlRmtvff9MSIRIVGSpLQou67P0uzX+SPPy/P54vsBIXEcJ2maBSHhXBjTWdtDG2O9SxxGQVjX9TAM1ppxHGhZxlHinJNSPh4PfuVaGW307bnu9/u6rrgXQng5rRil2MFUKQWGUoqw4zjWvJ7nuRFNi7qNmba18csyA2as8g7fvx1P59PxRAjRWg+Dg68sK2BICwpT2TR9777gr9jwCLiqAL+8XD4+SQhyc4/IZYnE6W2aKlohSVE3jZB4uj1h3PyF80oareEVMY21ru/TLEOdy7LUQqA8wesOg/kn7Q0OAvSQo2AcoJ3rsw2uAV+fLnjFEdz8F94dzoDRnkZKtK13PYkiNGNdVkwI1sgCU2mVgs345Od5Qb8ZYx5mqdt2XebOGq3a2zRcGdNKbcPgW3y8KtkOzi2AIMvyeC50wrskPKtUWVvoBP+mUgU3TPa06WjzR29HgU1XCgtdCJs+jX8DSIWbThpOeakAAAAASUVORK5CYII=')\",\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/4242e0d9b98f022be2d75fa3f00e49e9/ef3e1/image9.png\",\n \"srcSet\": [\"/static/4242e0d9b98f022be2d75fa3f00e49e9/a2ead/image9.png 259w\", \"/static/4242e0d9b98f022be2d75fa3f00e49e9/6b9fd/image9.png 518w\", \"/static/4242e0d9b98f022be2d75fa3f00e49e9/ef3e1/image9.png 759w\"],\n \"sizes\": \"(max-width: 759px) 100vw, 759px\",\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 full factorial test design matrix would look like the design in\\nfigure 6a. However, if test resources were not available to execute 16\\ntest runs, a fractional factorial design could be used to execute the\\ntest in 8 runs---a \\xBD fraction of the original full factorial. The test\\ndesign matrix would look like the design in figure 6b. It is important\\nto note that this example is only intended to illustrate the concept of\\na fractional factorial; practically speaking the design in figure 6b\\nshould not be used at \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" since main effects are confounded with 2FI.\\nHow to choose appropriate fractional factorials is covered in the next\\nsection.\"), mdx(\"p\", null, \" Figure 6a. Full Factorial Figure 6b. Fractional Factorial\"), mdx(\"hr\", null), 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\": \"783px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/6a7ccd5f9cb79b6878e82a0de2ca92a2/e51a6/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\": \"70.27027027027026%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAAByUlEQVQoz5WRa5OaMBSG+f9/q5cvO9NqcdWFyGWFhERCAiHhJtoXtU63X9oyZ04OyfvkXOIF7yKj/JgXlIlKN9pY1SxWG9e0Hby+/dpuhLl+MeN6yIztvdU2Wq19fxOFcUGSnMRZlLDgLdxsXlfbzevbIYzZtz3LmC5KQ7mmvKaFzgp9pNLzN7swCIMgjA4xy6lWKjpEhBBK6Xa33QdBntOQRGmahiER4qSUNsZoXdd1462DHQmIMa21tmka62wSx4xxKKC7Xq8nUVaVWo6sned5GEZsIrhcLl7KKM0yVamu66AAkyaplFVrWsFP0MmyQh7s931/Pp/7fgCGALxXLpc2pm3hUQpEKNvZrm1bJARcilIpnNTOOQAf4PWXr77/6v/w0RUUYNAtkkAqSwm4vrWH/WEYwKBsYA94//kTOcSYmFKPxqZput8NPz+/83xn7tgDDkgqyxJ5kA0pAI/jeId/1z39B9gOyDSik8e0b/Dz+C8wHphzXkopOEfl/we/vHznXGAMlawwXuf+CZ5ui7fbh3gitGiwaN05e54mDBnDglvsFlx++UcwL97bpTJhOinqmKlDrmJWp9wcRfuHvQvz9BCQvIqZ/glXYxhUMaUomAAAAABJRU5ErkJggg==')\",\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/6a7ccd5f9cb79b6878e82a0de2ca92a2/e51a6/image10.png\",\n \"srcSet\": [\"/static/6a7ccd5f9cb79b6878e82a0de2ca92a2/a2ead/image10.png 259w\", \"/static/6a7ccd5f9cb79b6878e82a0de2ca92a2/6b9fd/image10.png 518w\", \"/static/6a7ccd5f9cb79b6878e82a0de2ca92a2/e51a6/image10.png 783w\"],\n \"sizes\": \"(max-width: 783px) 100vw, 783px\",\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(\"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\": \"783px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/b7239545c2738fdce12b8c23bb33cd97/e51a6/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\": \"70.27027027027026%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAABqUlEQVQoz5WR23KbMBCG9f6PldtMJ4baxpiDwEgCMQEkdAADhi6QNlM3F41m59euZj/2AAqykjB+owXJOc3L91q2ppO6E62RykIgFJg13WD70farKtvDozI9OnjxwXHdI74ENz+I4iQ/+9hxjsfT+XT1/Sj1Y/rjTDNWMy5oIXYFy1iFfp4uwRWyrkEQMsKkkN7ZgxBjHEbhLcu0Mq3SQrZtq8R6KSlbuYYtcnwvvIZKaWstxMYaSgijjBLa9/1jO/M8P+vj0Q8jSgvGCKnrpuu69eNKpUnKWMForrUehmHnp2n6S6epuw+oEpCvtDFASinBxzGG5pMk9X2fUrqVmp7hrTh6e3k5uK7juFmWrZW1Yvlas+CcEFK9V3uf/8JwUJkXUBDa3ssaY8Zx3GZ7LMvyJfYJq24Yh/swjjAz8ADvcz7lfQ23FpbaA/mx7W/BQRiXnFdVBdo0zffg19c3zsv7fairGia39r/g/RV5lwB+0TxNCi4hOmumaVyWeVkXNm9rm/84nzqvj8hLqyQXSSFx3kS0wbm8cZWV+rd9+LfN2TXlbcRqnItfYb4a5biQp1sAAAAASUVORK5CYII=')\",\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/b7239545c2738fdce12b8c23bb33cd97/e51a6/image11.png\",\n \"srcSet\": [\"/static/b7239545c2738fdce12b8c23bb33cd97/a2ead/image11.png 259w\", \"/static/b7239545c2738fdce12b8c23bb33cd97/6b9fd/image11.png 518w\", \"/static/b7239545c2738fdce12b8c23bb33cd97/e51a6/image11.png 783w\"],\n \"sizes\": \"(max-width: 783px) 100vw, 783px\",\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, \"Observe that columns are balanced in both the full factorial and\\nfractional factorial figures; i.e., each factor level occurs the same\\nnumber of times. Also, for the runs involving a specific level of one\\nfactor, the other factors' levels are also balanced. For example, in the\\nfirst four runs of figure 6b where the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"departure type\"), \" factor is set to\\nthe \", mdx(\"em\", {\n parentName: \"p\"\n }, \"instrument\"), \" level, there are 2 occurrences of each of the other\\nfactor levels: 2xDay, 2xNight, 2xLocal, 2xNon-local, 2xOff, and 2xOn.\\nRecall that this means the fractional factorial is an orthogonal design.\"), mdx(\"p\", null, \"Fractional factorials have the \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"projection\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn17\"\n }, \"17\"), \" property; if a factor in the design is determined to be\\ninsignificant and its associated design column removed, the degree of\\nfractionation is reduced. In figure 6b, if \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Autopilot\"), \" was not an\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"active effect\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn18\"\n }, \"18\"), \" (significant\\nfactor), the resulting design is no longer a \\xBD fraction, but a full\\nfactorial in the three remaining factors. If the fractional factorial\\nwas a \\xBC fraction, removing one insignificant factor creates a \\xBD\\nfraction.\"), mdx(\"p\", null, \"The strategy of using only a fraction of the runs in a full factorial is\\nbased on the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Sparsity\\u2011of\\u2011Effects\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn19\"\n }, \"19\"), \" principle. The principle implies that the effect of the\\nhigher order (3-factor or greater) interactions are likely negligible.\\nAlthough there is strong evidence that this principle applies in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \", it\\nis not always true and therefore should be assumed with caution. It is\\nwise to verify this assumption by discussing the issue with system\\nexperts.\"), mdx(\"p\", null, \"Although fractional factorial designs save resources and have many of\\nthe same properties as full factorials (balance, orthogonality), these\\ndesigns have less information than full factorials and may not allow the\\nindependent estimation of the main effects and 2FI if the fractionated\\ndesign is too small. The next section discusses how fractional\\nfactorials are classified based on the degree to which independent\\nfactor estimation is impeded.\"), mdx(\"p\", null, \"Resolution, Aliasing, and Confounding\"), mdx(\"p\", null, \"A central issue in experimental design is minimizing the degree to which\\nfactors are \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"correlated\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn20\"\n }, \"20\"), \" with\\neach other while adhering to the test resource constraints. To\\nillustrate the problem with correlated factors, figure 7a shows three\\npossible designs for two varied factors in the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1.1 test.\\nSuppose the average response for runs 1-4 was higher than the average\\nfor runs 5\\u20118.\"), mdx(\"p\", null, \" Figure 7a. Perfect Aliasing Figure 7b. Partial Aliasing Figure 7c. Orthogonality\\n\", 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\": \"541px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/3cf25b6ba90988c4159f47efcff14704/9d576/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\": \"61.003861003861005%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAIAAADtbgqsAAAACXBIWXMAAAsTAAALEwEAmpwYAAACBElEQVQoz1WR626jMBCFef+n2RdYaXf/VEmzuXCHADY2xsY2NFxMuARYN22l7dHRaDTWZ8+MDRtVhHGIGSIM50VGZZZz+dbe51WNj35adXKfnp7X7j41aqjqdhzHPawNN4IgiaMwDIIkTtI4itIUA4gIYSkiGULx9RrFUQxiCFECYJpmXoQl5/vkZhzs+K/tW6Z5vOAIVRfTtfwkBNR2wcGMdrvj6+v55bA7eo7pAT9BQUx/nvIgyn68QMNxfP1a4AeObYdBiFEmGeuVqoS4XC6eHwhZphBiRNIUlWV5f1c/D90Rvhn78/l8PFumnT1FSFbfbp2GqzKJQar7x8SxbM45yUnTtMuyjNO8rQ8zV4ZzOLiO57leeI2E4FKKpmmUUpwXGSY0Z7wQGOG27XR9GKZlWefHum2rTXvD/vP7YlmuY59OZ9O0qqr6gAtGQQw0xnKmk3ma9Yanaf4Gn08WAKB6So+EMf6AGSsgTFWnSlklUVKWeglcqfu6bvNj+YQdNySEDMPQ972OjLFPuCiSBOghpSij8CqE0Eed6r/Bu/0xDK+6Ib1EDec5/YCFlDSnSvW3W53CNCM5xqht1TfYD2NG2TiNGtZTCS7quu67Tv/Wuq56Qr3e7UuPx/Je0Rdsm0PvBiqaQja5aOjTpLhhWulIijcmW20qWvafCW8SIgvKf7niH/fnjvr7gUTyAAAAAElFTkSuQmCC')\",\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/3cf25b6ba90988c4159f47efcff14704/9d576/image12.png\",\n \"srcSet\": [\"/static/3cf25b6ba90988c4159f47efcff14704/a2ead/image12.png 259w\", \"/static/3cf25b6ba90988c4159f47efcff14704/6b9fd/image12.png 518w\", \"/static/3cf25b6ba90988c4159f47efcff14704/9d576/image12.png 541w\"],\n \"sizes\": \"(max-width: 541px) 100vw, 541px\",\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(\"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\": \"541px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/31b1d981bd212ab2873cca6496991226/9d576/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\": \"61.003861003861005%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAIAAADtbgqsAAAACXBIWXMAAAsTAAALEwEAmpwYAAAB/0lEQVQoz1WS25LiIBCG8/5Psy+wVbt7M6VjaTRHI4QAIRAgMYmSkxqXceZi5q+/KKD6o7sBxyc1EzKjAuecFmXOdV5Ifb4Mt8VM935e7GSYX74t12HuzFi3l2ma1lnrhCBDEEJwAgDBFEMAMKYoI4wJTFhOCDydAAQQwSwjKcowziNAtZTrtHE2Ptx4cRQFSVqecL33Qi9OE8T9EG0OYLXavr+7b5vVNgoOEYpTcoT89644gvzXW+YEfmyzxfHR9/zkmFCSayF6Y2ql9vt9FB+VrnCWUcIwJlVVDR/qb+N1m52dteu6W9c7+PlLjOVt01wtXFcpRNjWT1ng+VIqVrCuuzwej2m+PZf7oTBOsNmEQRSFUXICSkmtVdd1xhgpy5wyXgiLEUzatmuaZhymZXne7svzufi8d/x/f/eeFwb+buceDl5d159wKTiCiBIquAAJqOuzPbfvhxf8+ILdnYcQql+yLVFKP2EhyizD5mq0tvWnNq0NGPrxBxyECWNsHMe+7+0ohPiCyzJNkW1SKw0AbJr2Ax5+wqv1NklO0zzbS7RwUfBPWGnNC25M3zadLV5XlZTSmJ9lxwm0XU3zZGH7b5RUbdv216t9rWVZHg9rG/q0jNX9/vjYeS0CPjik7ErdFarjL7Oyoby2IyvPQl+subqIb2ayS5kuufwTqv8se4803fB5bgAAAABJRU5ErkJggg==')\",\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/31b1d981bd212ab2873cca6496991226/9d576/image13.png\",\n \"srcSet\": [\"/static/31b1d981bd212ab2873cca6496991226/a2ead/image13.png 259w\", \"/static/31b1d981bd212ab2873cca6496991226/6b9fd/image13.png 518w\", \"/static/31b1d981bd212ab2873cca6496991226/9d576/image13.png 541w\"],\n \"sizes\": \"(max-width: 541px) 100vw, 541px\",\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(\"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/e59896aaf75cc8fb3ce0e8e66381cfcf/7bf07/image14.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\": \"39.768339768339764%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAICAIAAAB2/0i6AAAACXBIWXMAAAsTAAALEwEAmpwYAAAA5UlEQVQY05WOa2vCMBSG+///lfswhMFARWfTi01zbS5m7dJVbNIY6xAGY24PL/kQzvOek7xlxXqXAgAYpUoqRFiNOOGKyw92j+hocw1pWiq6mr1XxMQkoGIQon0KEMJU6BSpDOuStyVrITUwzlGDm47pTyy6Ah9BJRevh6cVft7y5DyOjTquNrsS1gdEX7bZcrNflwQrI4UUQkqpT8MphDBNU3zj/OhcmEniT28tRkhrZZTOU1DkuVbSWht+wnnvnP+S/dx3w3vf9/0wDOe5/7F8O2aaCX8gLoj+N/nOw5bf5H9tvgAfvMsYBa00bQAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image14\",\n \"title\": \"image14\",\n \"src\": \"/static/e59896aaf75cc8fb3ce0e8e66381cfcf/e3189/image14.png\",\n \"srcSet\": [\"/static/e59896aaf75cc8fb3ce0e8e66381cfcf/a2ead/image14.png 259w\", \"/static/e59896aaf75cc8fb3ce0e8e66381cfcf/6b9fd/image14.png 518w\", \"/static/e59896aaf75cc8fb3ce0e8e66381cfcf/e3189/image14.png 1035w\", \"/static/e59896aaf75cc8fb3ce0e8e66381cfcf/7bf07/image14.png 1128w\"],\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 problem with the first design in figure 7a is that every time the\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" factor is set at the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Instrument\"), \" level, the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff\\nProcedure\"), \" factor is set at the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Normal\"), \" level. Also, every time the\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" factor is set at the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Tactical\"), \" level, the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff\\nProcedure\"), \" factor is set at the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Adjusted Max Effort\"), \" level. Since both\\nfactors' levels were changed at the same time, it cannot be determined\\nif the higher response in runs 5-8 was due to changing the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure\\nType\"), \" factor, or due to changing the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" factor---or\\nperhaps the increase was due to changing both factors.\"), mdx(\"p\", null, \"This ambiguity is because \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" are\\nperfectly correlated; i.e., a level of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" is always\\nmatched with the same level of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" . In the terminology\\nof \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \", these factors are perfectly \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"aliased\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn21\"\n }, \"21\"), \". It is also equivalent to say that \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" and\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" are \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"confounded\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn22\"\n }, \"22\"), \".\"), mdx(\"p\", null, \"The second design in figure 7b is also not ideal. Although the factors\\nare no longer perfectly aliased (perfectly correlated), they are still\\ncorrelated, i.e. when \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" is set to the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Instrument\"), \" level,\\nit is more common that \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" is set to the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Normal\"), \" level.\\nIn this scenario, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" are partially\\naliased; which means the estimate of the effect of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" on\\nthe response will be influenced by the effect of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff Procedure\"), \" .\"), mdx(\"p\", null, \"The ideal case is the third design shown in figure 7c. When \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure\\nType\"), \" is set to the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Instrument\"), \" level, the two levels of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff\\nProcedure\"), \" appear equally often (2x each)---likewise for the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Tactical\"), \"\\nlevel. Thus the two factors are uncorrelated and therefore this design\\nis orthogonal. The effect of changing the level of the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \"\\nfactor from \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Instrument\"), \" to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Tactical\"), \" can be independently determined\\nbecause the effect of changing from the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Normal\"), \" level of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Takeoff\\nProcedure\"), \" to the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Adjusted Max Effort\"), \" level will average out over each\\nlevel of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Departure Type\"), \" .\"), mdx(\"p\", null, \"Aliasing and confounding are sometimes used interchangeably, but\\nconfounding conventionally refers to perfect aliasing. Any time a test\\ndesign is not a full factorial, there are some effects--- main effects\\nor interactions of some degree---that are aliased/confounded. Fractional\\nfactorials do not have any partially aliased effects; the effects are\\neither orthogonal or completely confounded.\"), mdx(\"p\", null, \"Note that the use of full and fractional factorials assumes that the\\nlevels of factors can be chosen independently; i.e., If level 1 for\\nfactor A is chosen, that does not constrain what level is chosen for\\nfactor B. Occasionally the levels of two factor cannot be independently\\nchosen, perhaps due to some physical constraint---in other words these\\nfactors are naturally correlated. For example, if one factor is user\\nweight and a second factor is user height (each with two levels, low and\\nhigh), it may be difficult to find military users who are relatively\\nshort and relatively heavy; likewise it may be hard to find military\\nusers who are relatively tall and relatively light. In this situation it\\nmay not be possible to have separate factors for weight and height since\\nall of the possible level combinations cannot be effectively covered in\\nthe test.\"), mdx(\"p\", null, \"The \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"resolution\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn23\"\n }, \"23\"), \" of fractional\\nfactorial designs gives information about the type of effects that are\\nconfounded; the convention is to use roman numerals to signify the\\nresolution. Table 2 shows which types of effects are confounded at the\\nthree common design resolutions. The size of a design increases as the\\nresolution increases. Thus test teams may not have enough resources to\\nuse the ideal resolution V design.\"), mdx(\"p\", null, \"Table 2. Design Resolution\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Resolution\"), mdx(\"th\", null, \"Aliasing of Effects\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"III\"), mdx(\"td\", null, mdx(\"p\", null, \"Some/all main effects are aliased with 2FI\"), mdx(\"p\", null, \"Some/all 2FI are aliased with other 2FI\"))), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"IV\"), mdx(\"td\", null, mdx(\"p\", null, \"All main effects are orthogonal to 2FI\"), mdx(\"p\", null, \"Some/all 2FI are aliased with other 2FI\"))), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"V\"), mdx(\"td\", null, mdx(\"p\", null, \"All main effects are orthogonal to 2FI\"), mdx(\"p\", null, \"All 2FI are orthogonal to other 2FI\"))))), mdx(\"p\", null, \"Since main effects are confounded with 2-factor interactions in\\nResolution III designs, these designs are not recommended for use at\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \". Resolution III fractional factorials are typically used as\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"screening designs\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn24\"\n }, \"24\"), \" . They are\\nintended for experiments where the intent is to determine the active\\nmain effects before subsequent testing is conducted to de-alias and\\nestimate the active 2FI. Since \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not typically conduct\\nfollow-on testing, resolution III designs do not provide enough\\ninformation during a test event and are not suitable for operational\\ntest. If it is not feasible to use a larger resolution IV design, then\\nan optimal design (discussed later in this section) is a better design\\nchoice.\"), mdx(\"p\", null, \"Resolution IV designs are an appropriate choice when resource\\nconstraints are a significant concern and a larger resolution V design\\ncannot be executed. Main effects can be accurately estimated because\\nthey are uncorrelated with any 2FI. However 2FI are correlated with\\nother 2FI. Since it is often the case that multiple 2FI are active,\\nthese designs do may not facilitate an adequate characterization of the\\nsystem in the battlespace.\"), mdx(\"p\", null, \"Resolution V designs are the most popular choice. If the\\nSparsity-of-Effects principle is valid, three-factor interactions or\\nhigher are likely negligible, so main effects and 2FI are most likely\\nthe only important effects required to characterize a system. Since both\\nmain effects and 2FI are orthogonal to other main effects and 2FI in\\nresolution V designs, these are more efficient designs (require fewer\\nresources) for characterizing a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" than full factorials.\"), mdx(\"p\", null, \"Any test design higher than resolution V is likely a waste of test\\nresources and any design less than resolution V represents an increased\\nrisk of not discovering or accurately estimating all of the active\\neffects. The goal within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is to minimize or eliminate the\\naliasing/confounding for the main effects and all 2FI. When this is not\\npossible, a balance must be struck between what can be estimated and the\\ntest resources available.\"), mdx(\"h2\", null, \"Creating Fractional Factorial Designs in JMP 13:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, \"From the main JMP menu, choose \", mdx(\"strong\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" then \", mdx(\"strong\", {\n parentName: \"li\"\n }, \"Classical\"), \" , then\\n\", mdx(\"strong\", {\n parentName: \"li\"\n }, \"Screening Design\"))), mdx(\"p\", null, \"Figure 8. Creating Fractional Factorials in JMP 13\"), 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\": \"655px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/03c441e177f31c652c8325a6ca306b07/ae6b7/image15.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\": \"73.35907335907336%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAACMUlEQVQoz3VT23KjMAzl/z9o28feZqfbbUkCDQm5B7ABG2NzN0ma9ABtpjM7e6wxsi3Z0pEwdoRHPCUhD8JOCSjLKl3Uh6JuIWVzGOSq1+0pK5ui1kzVhvM+fXt9fXl+fnx4eLftAPA9b7/3PR+z5+HTyWazwS4JAqVkmgqVCiaU4czmN79u7u/vZ7MZLMIwJJTSMAwCEkVRCkMhkiRJe0DhGIlIOO+c937wcHf3+PhkvpmTyWQ+m5uj0cufl/FojLuklCIRZVmK/g4o2GGMVVUp88qQWZ4phSuxW9f18XjMsmyxWPB+B0HEcQxH0gcCJUJohCJ0LnOjavTlcjmfz5cfOPe4/AfDgSpqI+YJISTP8/obVVU1TXNdYMISARdFUX7jeDhIOLur1e3tLTKcTqfj0Qiz4zimaYI/27Jc1/V9f7/b7kIZiiLPMpV10E2jysZglFp/X5er1Xa7hZ01sWDJ4phzbo+t+dxFzmBo65GAxohkCEHrBtU2Yufd+f20XG1CGmmtLctau2ukBOZs2wZhSqmiyC1UwpygRkPNvpwFpdF+J9IUDh+nEx5UMoN++jgRStJUSgXWJXhhjKfdusOXc8QTNAbKgGzwCJhDXrK3gVdfXqH6Kg5cDmhb3eW82e7Qngt3gR5cusvNeo2E8QJHK3EuRKcolYHw9htat1/OhIZob1CCi0HGUCd9HdC1Hqqlf+DQ6i7sgOWJrEOe43cahMTqX7mehizb0dQjbLFnn2nkOknYX2D3AAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image15\",\n \"title\": \"image15\",\n \"src\": \"/static/03c441e177f31c652c8325a6ca306b07/ae6b7/image15.png\",\n \"srcSet\": [\"/static/03c441e177f31c652c8325a6ca306b07/a2ead/image15.png 259w\", \"/static/03c441e177f31c652c8325a6ca306b07/6b9fd/image15.png 518w\", \"/static/03c441e177f31c652c8325a6ca306b07/ae6b7/image15.png 655w\"],\n \"sizes\": \"(max-width: 655px) 100vw, 655px\",\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(\"ol\", {\n \"start\": 2\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Factors\"), \" section, add the continuous and categorical\\nfactors using the drop down menu. Specify the number of levels for\\neach factor. The factors and levels can be given appropriate names.\\nFigures 9a/b shows the input for the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1 example.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Continue\"), \" .\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Select \\\" \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Choose from a list of fractional factorial designs\"), \" \\\"\\n(figure 9b).\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 9a. Enter Factors and Levels Figure 9b. Request a List of Fractional Factorials\\n\", 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\": \"655px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/2073f8693efdea58b6cd75481ee0526d/ae6b7/image16.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\": \"73.35907335907336%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAACH0lEQVQoz3VTaXOiQBDl//+gTT7GJLWVdSMqRBA8QGA4ZjiGe9Co+4DEsmorj67xTU/30P0aJZuwkKUkYF7QE8+neS3K5lg2Haxqj6PdeNN95lVbNoLyRtI+VrP39+nb28vz84eqeoDrOIeD67hYHQc/ve33e3iJ53GepWnC04QmXNL09cOvh8lkous6IoIgIL7vB4HnkTAMUwQmSRzH6QAQhidOYsb65IPrPT89vby8yjN5uVyu9bU8n0//TBfzBe7KsiyJk6qqkuEOEHgopXVdZUUtZXmRc44r4W2a5nQ65XlumiYbPCgiiiIkkqEQkBClER+ls6yQ6lZcr9fL5XK9w2XA9QeMB7xspIjFhJCiKJpv1HXdtu1t069tU9XVPU7HY4ZkY7t9fHxEh6vVajGfY9U0TZZl6KcqimEYruvato2+8juItuVVK1HfV/6+b7Zby7IQpywV27JpFDHG1IWyXhvoGQrhKAxClIHXlmUpRItpS5H2of1+3ewsnHVCKIqyM3ZoCcqpqgrBOOdlWeDShbzEjMaZfSUngR85hyTNzufz5/kTU8x5jmRsoQXisgHglLLb9is5pHH/SbjufrfHMNBPP9skQdwo3ohRwtu260Tfs0v8+Wy21nXbsjabjWmYuqYbhomCIXL3DSHEHe++kkkQ6poGMe/GM0xngPgBx070ZXtRwbLapwWJ8tHwvxoIB/nfAprbfuoQah7oP5bBOnl4fWcHAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image16\",\n \"title\": \"image16\",\n \"src\": \"/static/2073f8693efdea58b6cd75481ee0526d/ae6b7/image16.png\",\n \"srcSet\": [\"/static/2073f8693efdea58b6cd75481ee0526d/a2ead/image16.png 259w\", \"/static/2073f8693efdea58b6cd75481ee0526d/6b9fd/image16.png 518w\", \"/static/2073f8693efdea58b6cd75481ee0526d/ae6b7/image16.png 655w\"],\n \"sizes\": \"(max-width: 655px) 100vw, 655px\",\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(\"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\": \"635px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/d02c8e7cabe428a1138af0c40f689fcf/1ddef/image17.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\": \"98.45559845559846%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAIAAAAC64paAAAACXBIWXMAAAsTAAALEwEAmpwYAAACzUlEQVQ4y51T2W7aQBT1//9Gn1vlJVUSKYtUEkIJxuwEY/A29izebWzAJvTYVqRGTfvQw/HMnZl7585dkDYWdVxuO8y0HdN2CeUiiNK8iNJdnOUJuCvSfA+hXe72R5xiB5SW86UiD/q9XvfxcfDyQgixTNPCZxq1gEnXbcvStxsIxlbnjPme11JStc3Ft69XV9fKcKiqKxgTx3Edt5mdIAjiOA6BKIqTBKPv+1hh34MxFf5Lv9/pPA4G8nA4nE6nI0XpPnX7P/vjycTFRa4Lg8D3cZ0QIooiXMoYgyAFcYqJ83o3z/PT6VRV1VpdW5adpinnnLo0CEKYwcb3fPgkto0lXiElWXH+L8CN5AUx5yxNs+PxeGiw3+8P74BcFEU7Zlm2awABS5xKukW+X172nnuz2UxRlMlkslgsZFlG8DP8plMd2OoIGI9vgZcnSQJ7CbmYyPJKVaFj2zbUNW1jWRalTFtrylCxbBs5Q+RAkqRwi1zAf+3Zt8zFw+1KQyG3h8Nxo2mz6RwhICrTMMajiSc8+IH9U+fJMMy2SMhubRwyxlcL7gV4BgwcQtALZVlCpq4D7ThO8FRGKUoA/+2zUfza2CTuc7c7GAxQG849ykRNytvroeo3gHabtvwdWEqEsjHaQlFMXQ85DbibhV7sUQQshIcI8yJH1hHk/g9ITPjoY4/R8UZ86TgXsn+5OHxfFKpmLJeL1esrTtHGSNInxsIPUVe0lc3Ch6H+Y2R051QVpWkSTVPXwEpFqf7i2Qtwa1lVSRhsX+ecmOdTeX4r8e9BhkBikyisc9t2y0fPAVp6h9okcYI4HeI2rVehzoapG4YB95ZpFXnxiWdX+KPReK1tcIomTbMdHIAQEvRD3RL1mO3ydv93SnEUyr0nXVPPb9VbuT9Xh3PZsPoXoQlKNxNxO2V3U34/E3cN7xvefeT9Ox9m4npMrxVyMyS/AC0+SbMBU5uPAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image17\",\n \"title\": \"image17\",\n \"src\": \"/static/d02c8e7cabe428a1138af0c40f689fcf/1ddef/image17.png\",\n \"srcSet\": [\"/static/d02c8e7cabe428a1138af0c40f689fcf/a2ead/image17.png 259w\", \"/static/d02c8e7cabe428a1138af0c40f689fcf/6b9fd/image17.png 518w\", \"/static/d02c8e7cabe428a1138af0c40f689fcf/1ddef/image17.png 635w\"],\n \"sizes\": \"(max-width: 635px) 100vw, 635px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 10a shows the fractional factorial design list provided in\\nJMP 13. Notice that JMP states the resolution of each design\\n(although they do not use roman numerals.) You can choose a standard\\nfractional factorial or you can choose a fractional factorial with\\nblocks (Blocks are discussed in the section of this guide titled, \\\"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#_The_Three_Principles\"\n }, \"The Three Principles of \", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" \\\" Note that\\nthe full factorial is also available as an option, since there are\\nno resolution V designs smaller than the full factorial.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Select a design and click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Continue\"), \" .\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"JMP presents menu options to evaluate and modify your design (figure\\n10b). The \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Aliasing of Effects\"), \" output shows which effects are\\naliased (confounded) with which other effects. Figure 11a shows that\\nin the X-100 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Block Update\"\n }, \"BU\"), \" 1.1 example, the \\xBD fractional factorial\\n(resolution IV) has 3 pairs of 2FI that are aliased.\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 10a. Fractional Factorial Options Figure 10b. Additional Diagnostics and Options\\n\", 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\": \"635px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/0c6cc5215fa13f5dc272700ed3861239/1ddef/image18.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\": \"100%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAIAAAAC64paAAAACXBIWXMAAAsTAAALEwEAmpwYAAACm0lEQVQ4y5VTiW7aQBD1//9MG9KmAYLaKBzGmMtctgLYxrd31zeYK22fcZOmUpOqT6PJZPGbmZ23w60sajrE9pjlkEtAaZhuD+d0d8zyY7aHnWBpfiwNP0VZnuwOME5WHmcTaTQYCDzfF0XTMDa6ZmzgtI2umxtEumWa2nqt6zpOGZIHQWFhwKm68alydXPzRej1ZFm2bdtxHNfz3AsYY2EYwrMgiKIIfymlQRAg8AnhPBYL3e79t3tRFIfDoTSWhoNBl+d7gjAej8H3Pb+oEgSuU+RCCiSmjMVxzLE4w/8oRgmN4+R4gaIomqrhHGTbslDWcz3TMOkFuJjv+0jHhenu+9PTj//H+XzmaJTiImmWoeDhcHjtS+z3+9LvXqE84SyP1qrVdruzWMiSJE2nM1lWxuPRbDZbzBfz2VwvoGGQ4SukaZrnORdE6Xw0mi9kVVUNw5hNp8vHJfTBzBFghBDPcQoJPM8DJ8sy+O12W1QOfKp8rSvL9Xq5RjJN0ybjCbrCrZBCkiYYZJIkkLrTapumBYkxM5zgGy5gIVHmrkfBBIESYmzMkuy6jr7ZJEmMPlF5tVqhOCTAnH+RHcI67dag3++LfUEQ+E5H6AroLb9gv88xnue4QP6Mom1I1Wo+XH38UK/VKpVKo9HAPUEu5/k+uGS7F8Ve9fa2Vr3t8HycJOfT6aXOP8i2z+7qtbt6/fP1Nd/hMU70+dJhqep75ObDQ0/Awx4YhgkhMEztAmyUixXxvLca4YI4c7BJtkN87AmhtNgbaK6uVTwOxFiGNyv7LJpIBVbLleO6cRRjWmgVL/R8PpV78iaZBHGr2YRS+BQoP81/y1PaHzgWj/8Az6l2pJtEt5hNEtuPbf/iSRn8xRw/US2mmb5ukZ9N2kwVHSoyIQAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image18\",\n \"title\": \"image18\",\n \"src\": \"/static/0c6cc5215fa13f5dc272700ed3861239/1ddef/image18.png\",\n \"srcSet\": [\"/static/0c6cc5215fa13f5dc272700ed3861239/a2ead/image18.png 259w\", \"/static/0c6cc5215fa13f5dc272700ed3861239/6b9fd/image18.png 518w\", \"/static/0c6cc5215fa13f5dc272700ed3861239/1ddef/image18.png 635w\"],\n \"sizes\": \"(max-width: 635px) 100vw, 635px\",\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(\"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\": \"727px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/468ec28867ae5e20c3d14443bb57cace/c54b3/image19.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\": \"97.2972972972973%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAATCAIAAAAf7rriAAAACXBIWXMAAAsTAAALEwEAmpwYAAACfklEQVQ4y31TyXLiMBDl/78ll0kOGSi45DSQGZaAV2zAu2VbtiwvyEDIPGNSyaTCvGp3yVI/9are1o2imPph5HqBH5KQJFleZDlPGWe8hGSMZww7RbVvanGAlPWel1VZi56iaKNBfzgYPD09mYZBSOi5ruc6rnMV29rZluVYVhRFSRxD54w1QmRZ2nOCcDQcgrlcLhVFUZUWkiSb5obzguMrLpoXeQ4WY3leVtXxeAzDsEcZ9z0fppZtR3FMKZVlea2vCSGe5yGNlFLHdpI4ARzbThJaVeXhcGjJrKzP59fz+fz2jsPx0DTN6XSCBTx0+vNvXddXckSzIPBzzvcX4EB8Anag608ADZtXshOQ0Wg0nc4UWZ7NZkj4ZbFYXYA1SmXbdpZl/B3d7VdyEhJ1PtN1w7lgtZTiOEaR1rquqXqaUqS62WxQi6qqsP8v2bbd1Yvrh2IvyrJcr42qqpG5YRiWZYGD5k3/TE3TJBfgig9ySCJdlmGH2u6snaZpCLIsCkoTLNAaaDjsygF0VXgnx2n/8fHh/sfd3d3D/T16jjgRQpcheouvEeJLFT9aNRmPJ5PJYvGiqhoCM00DQeLM970Q40pp5+0bcl7tpZWkqqqu6/JSch0P4zlfTCVpuVjMUTUEIkRzw3NRmVo7lF22GA8cF2XBctbOI5qUc3ErbBd9Hg77/Z+DwSAIgm5ULiatEe6C3X/I0eTXGIMBz2nWYrvdYjRIRHDcPqCmuUmOU2bvdrD2PJ+QKKUZdvEMiqIteNfVr2SxRzxB26qEPo/HuqqiJe30IFQhLvPftNKIb+X1dMLT7tkBff4931geL0XKSgjNim5xS5KsiBIWRPQvrKQXxuQ643gAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image19\",\n \"title\": \"image19\",\n \"src\": \"/static/468ec28867ae5e20c3d14443bb57cace/c54b3/image19.png\",\n \"srcSet\": [\"/static/468ec28867ae5e20c3d14443bb57cace/a2ead/image19.png 259w\", \"/static/468ec28867ae5e20c3d14443bb57cace/6b9fd/image19.png 518w\", \"/static/468ec28867ae5e20c3d14443bb57cace/c54b3/image19.png 727w\"],\n \"sizes\": \"(max-width: 727px) 100vw, 727px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Specify your \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Run Order\"), \" ; JMP provides options to sort (or\\nrandomize) the run order and add replicates to your design.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Table\"), \" to create the fractional factorial design\\n(figure 11b)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 11a. Aliasing of Effects Figure 11b. Fractional Factorial Design\\n\", 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\": \"596px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/bcbd0572a407898baa816abc8db8beed/699b7/image20.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\": \"76.83397683397683%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAACaElEQVQoz22T23KbMBCGefq+Qy+T9iHSu84007h1YgdzsAGJgzibgwRIgMHYXSCTq+4s4h+Nfn2LVkg6cjFGp5Nlmbbj+nGchmEcJxkhQRhGrkM84gURzKQw4wUpcoKqFpdWbHApvemOZhjy+8m0c8s9GzgwnMhEvhsUlok19biVX3f6UT5hx09klG/11ItonLKnXSDtdwddOyoHRT2oloWI4zYNz9OzAcUg7Lje+Zxvt2/7vZznxVHXXAiPONbpxxuWNGRiExVFIYSom7osy67rGKO2bcMyznmSJA3nfd+3bWdjh9KqnJ9sR2rJcG1kIY+Qum4ulwtlrO26PMs91/NJME230A8rVt/v976/BCTkDTDE2Akt6aUTQpZpGoYJ8HwJIIP2fT/LcjAnScq5WM1xmAB/NatxLym/nt9l5SArqqqCgTEGFYLZtCxWzsAgCIVoZ3PXu7YneMuqpmvYTEZ/N7ZLTvoRYwxYMMPHg/A8UrEGPFEQM1qB6LoedFPzquZD2yhxJ8nbveM4cRQBcBwGMEPZQswndL1eoey+H8ZxFuM4QeU9HMxwhb0OUSu5QVrkWVVVlNJiCSDDIY/XD8P8nm4wrlvcbvfVLIdC2r3uoEK6BHQly7KuB7IYwTfHbfGsYpoWOXySFc2AuwelQFLKwLySh4WzMj/F9TqPlwuYbzP5XdagGcMwzE2mLC8K6LNoWwAuq6dPAcB1o2GcgKwA2fPjsqRctNDMqqqLgvKaw5HC74GRDVcKY8deEiE7WC5MlrO2oi/GWXrYpN//pI8vyZrfNh/5+BL/Nx9+x19/ksdn78sT+QeRuTQhLcqZJQAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image20\",\n \"title\": \"image20\",\n \"src\": \"/static/bcbd0572a407898baa816abc8db8beed/699b7/image20.png\",\n \"srcSet\": [\"/static/bcbd0572a407898baa816abc8db8beed/a2ead/image20.png 259w\", \"/static/bcbd0572a407898baa816abc8db8beed/6b9fd/image20.png 518w\", \"/static/bcbd0572a407898baa816abc8db8beed/699b7/image20.png 596w\"],\n \"sizes\": \"(max-width: 596px) 100vw, 596px\",\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(\"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/9e30f49b10958e17ea91a1e36ecec01a/1c1a4/image21.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\": \"52.89575289575289%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAIAAADwazoUAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAwklEQVQoz+WNyw6CMBRE+//f486tG02Mb02wFIKg5f1qC4V7iyQujHGjbp2cxWzODFmd6OLEmM9dnvo8jqOY8zBJsiwXaS7fUHmhskKVVTNC1gdrcaCz5W7vXs/ezXZ8yi6XIHKCnAXlKxX10v05PNrhdG5PZpTUde05zGUsjSIpJZihx6ED06HpzRuIGrAUMilEJTVp29ayrO1me71xIcTwQXBc6WEsBAGaplFKaa0B4CMZsXvIw/d5Pv8gm1GGf5XvE6KBEtFPgBsAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image21\",\n \"title\": \"image21\",\n \"src\": \"/static/9e30f49b10958e17ea91a1e36ecec01a/e3189/image21.png\",\n \"srcSet\": [\"/static/9e30f49b10958e17ea91a1e36ecec01a/a2ead/image21.png 259w\", \"/static/9e30f49b10958e17ea91a1e36ecec01a/6b9fd/image21.png 518w\", \"/static/9e30f49b10958e17ea91a1e36ecec01a/e3189/image21.png 1035w\", \"/static/9e30f49b10958e17ea91a1e36ecec01a/1c1a4/image21.png 1046w\"],\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, \"JMP can only create fractional factorials if every factor is restricted\\nto two levels. There are methodologies for fractionating designs\\ninvolving factors with more than two levels, but that topic is beyond\\nthe scope of this design guide. When it is not applicable to use\\nfractional factorials with 2-level factors, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" analysts typically\\nuse JMP to create an optimal design; these designs are discussed in a\\nsubsequent part of this section. The National Institute of Standards and\\nTechnology has a comprehensive list of 2-level fractional factorial\\ndesigns here:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri3347.htm\"\n }, \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri3347.htm\")), mdx(\"p\", null, \"For more information on fractional factorials and design resolution see\\nChapter 8 of Montgomery, D. C. (2013). Design and Analysis of\\nExperiments, 8th Edition. Hoboken, NJ: John Wiley & Sons, Inc.\"), mdx(\"h1\", null, \"Optimal Designs (Computer Generated Designs)\"), mdx(\"p\", null, \"An \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Optimal design\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn25\"\n }, \"25\"), \",\\nsometimes referred to as computer generated design (CGD), is a test\\ndesign whose levels are combined in a way that optimizes a specified\\nstatistical criterion that is a function of the design matrix. Unlike\\nfactorial designs, which are constructed using a standard method that\\nguarantees balance and orthogonality, optimal designs are constructed by\\na computer implementing an algorithm. Design construction algorithms\\ncombine factor levels into test runs with the goal of optimizing some\\ndesign quality criterion. The optimization incorporates constraints such\\nas run size or disallowed combinations of factors.\"), mdx(\"p\", null, \"Optimal design construction algorithms may not always find the \\\"best\\\"\\ndesign. One reason is that the algorithm may not be allowed to run long\\nenough to find the optimal combination of factor levels. Another reason\\nis that there may be multiple designs which have the same optimal value\\nof the chosen criterion. The generated design may be optimal for the\\nspecified criterion, but another design (with the same optimal value)\\nmay be superior in terms of a different un-evaluated criterion. As a\\nconsequence, optimal designs must be evaluated for quality by a\\nknowledgeable test analyst. The test team should also modify the default\\nsettings of the construction algorithm---as an example, the algorithm\\nrun time---if a generated design has flaws.\"), mdx(\"p\", null, \"An optimal design is constructed based on a model specified by the\\nanalyst. The analyst may include in the model any number of main\\neffects, two-factor interactions, or higher-order terms if necessary;\\nthree-factor interactions and higher are not generally included at\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" based on the Sparsity\\u2011of\\u2011Effects principle.\"), mdx(\"p\", null, \"The optimality criterion chosen to create the design depends on the test\\ngoal. The following are optimal designs that can be created with JMP\\nsoftware.\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"D-optimal\"), \" designs - Used when an analyst places a priority on\\naccurate effect estimates. This is because D-optimal designs\\nminimize the joint variance of the parameters in the statistical\\nmodel. For example, when using continuous factors, these designs\\nminimize the joint variance of the \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"linear regression\")), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn26\"\n }, \"26\"), \" coefficients \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\widehat{\\\\mathbf{\\\\beta}}\"), \" . When model\\nparameter estimates have low variance, we can expect the estimates\\nto be close to the true value (assuming we are using unbiased\\nestimates.) D-optimal designs are used most often in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" as they are\\nideal for characterizing a system.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"I-optimal\"), \" designs - Used when an analyst prioritizes accurate\\npredictions from a statistical model. These designs minimize the\\naverage prediction variance of statistical models. Unlike D-optimal\\ndesigns which have test points located at the extremes of the design\\nspace, some test points in I-optimal designs may be spread\\nthroughout the design space (when continuous factors are used.)\\nThese points improve a model's predictive capability across the\\nwhole design space.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Alias-optimal\"), \" designs - Used when an analyst prioritizes\\nminimizing bias in the parameter estimates from un-modeled factors.\\nThese designs minimize the aliasing (correlation) between the\\nspecified model effects and other terms not included in the model.\\nThis optimality criterion is typically used when a design is\\nconstructed to estimate main effects only, but the analyst wants to\\ninsure against 2FI which may be active (but are not included in the\\nmodel).\"))), mdx(\"h2\", null, \"Creating a D-Optimal design in JMP 13:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"From the main JMP menu, choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Design\"), \"\\n(figure 12a)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Add the response variables\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. One response variable is included by default. Change the\\nresponse name by clicking on \\\"Y\\\"\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. For additional responses, use the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add Response\"), \" drop down\\nmenu in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Responses\"), \" box. You can choose whether the\\nresponse should be maximized, match a target value, minimized,\\nor none of these\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Add the factors\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Factors\"), \" box, use the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add Factor\"), \" drop down menu to\\nadd the appropriate type of factor. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" typically uses\\ncategorical factors, although continuous factors are ideal; the\\nnumber of levels must be specified for \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Categorical\"), \" and\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Discrete Numeric\"), \" factors\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. For adding multiple factors of the same type and number of\\nlevels, input the appropriate number in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add N Factors\"), \"\\nbox\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"c. If you have created a JMP table of your factors and levels, you\\ncan populate them in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Factors\"), \" box by clicking on the red\\ntriangle to the left of \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Design\"), \" and choosing \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Load\\nFactors\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Specify Factors\"), \" box, click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Continue\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Linear constraints on continuous factors, or disallowed combinations\\nof categorical factors can be added in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Define Factor\\nConstraints\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Only the main effects are loaded by default in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Model\"), \" box\\n(figure 12b). To add more model terms click on the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Interactions\"), \"\\ndrop down menu and choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"2nd\"), \" (this will load all 2-factor\\ninteractions -- if you want higher order interactions, choose those\\nas well)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 12a. Creating a D-optimal Design Figure 12b. Adding 2-way Interactions to Model\\n\", 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\": \"967px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/7e0b49f45ef727a59ed85505bec1b927/aa08e/image22.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\": \"105.01930501930504%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACwElEQVQ4y5VTV2/bMBjk//9P7UsatHlogcRNYlt7cGhwSdR27J7kBEjRgfb0gSBof+OOR5JQIZXSxjjX9fi6fhzHYYtxnMbpLcbp7XC0Td+6oXEjuX8OD0EqRJlRjihrZRqnmxZh1nDX1boOJ7W2CS2/H/nDsdgdBQkTdv/weHtz8+XzZ86YlLJYIcqyLFByXUQhCmN0Y00tVRBn2kjbDbSoSFLoKKMfP3x4ft5TSvFvUGg2uK5zzvU92IAOlt42TSk1E8K1IDmQKOVpRgPfD8MQbaMoyrO8rio0jKNIKcUY20YRnHEpFWjxUoVxGuecRE/H/d7PsoxRviwLchhlrm211mEQ1nWdJkme557n+X4gilUT51opS+xJWaokY993O9/3D/tDkqT9MEDWYbhKu4k+T+s6jRhdmmaahnkCp47Uuq2UDvzAO3qhH9AsxylGmDdM6yW9FsIePNFZcLGcXi6XC8lZsT/6375+fXre7z3/6AcxEEVBEPieh0EMhNYaFbfkHsk0p9ivyRkrwigNPf/+ENzu411IoXOSJI+PT8ix1qItdAaXa2epbVkUp9NpWU4kFzJMKc3zqqqUrJGJkkYbxvnlHaYVI+4nyaEoXS0AwWrdwFav5Te8vLyg8DTPpzdAgqtgrh8F9wTLlDIwAYFZ0pzdfrq5u7uDSa4M0X/8BZCu6yerooJnsAz6EV4ZOBo0kijO0gx2QD7keX9V75JHo2IkK6lBg4jaUlFsNq4w83id73d47axjwVLOORxKBOwmyseHB7iy7xyob3c8Lb/EaZkxDRcU0maUpWlOEl4fwnT3dITJa+1Kaf8UojI5q+BOiH8+n/H+SaXalApeylKanJeVstK0v41KN/h1npfr5eHqiWl61+FzeHXz6pvz5d+wPklpW61027bnt7TzX+On5NpaPFprDJxw+R/AbT8AmqmbaRVQbiQAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image22\",\n \"title\": \"image22\",\n \"src\": \"/static/7e0b49f45ef727a59ed85505bec1b927/aa08e/image22.png\",\n \"srcSet\": [\"/static/7e0b49f45ef727a59ed85505bec1b927/a2ead/image22.png 259w\", \"/static/7e0b49f45ef727a59ed85505bec1b927/6b9fd/image22.png 518w\", \"/static/7e0b49f45ef727a59ed85505bec1b927/aa08e/image22.png 967w\"],\n \"sizes\": \"(max-width: 967px) 100vw, 967px\",\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(\"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\": \"715px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/273996145c2c87c428e91aca96ff76ca/d0c0e/image23.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\": \"106.94980694980696%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACkklEQVQ4y4VUiXKbMBTk/38pjjvTSZtmctmujTkM4kaAQBKHDXYSd4HYTTKdeg2axxOLVvuerNhOGMXUDyLien4Yp1leCMkKzgpRcJlzyXLOZZnlQ0bIZteWdSOruqy3iqpq06uryWTycH9PKU0ojeMojvoLj/1DFCYJjU4ZIQTnvL85V4gXXE+uFovfQ0KUJ1R1XVfveM8MgThBSqlA6rfpdLlarddrA9ANQhzMMcbyPC8GbLfbpmmqssLY9GHTti1GJSuErmn6Wvdcr2s73/fns0Vd1Z7nZRnD1GazkbK0LMs0jCRJPddVV2oQhPioUsgqCkMsc3h5OR6P0GoY5r478CLv9p1pmL4fsJwRQoIgIDaBQKwVhmGapr3s58dHXdfxbVVVN+YGe4Oq3W53HgEoR7jf75GB4DFQUsbnz8/L5co0TW2twdWRDF77gd91XXvCOVZE1UC2oemu61qmZVt2QpPD4TC+tB+AYHvCWUtPJq4/vZ5inzAGG3PwI84A17bt3ifThHkoEmqDKoxWv5MTVsxnM03TYEzgB2EYQDl6YzGbPz08wSQoojHFgmPBPpGzXBDLBhMzxwFvb28YUbkgjM4ZiH99fUUbofiIz2QOh+OI4sPYKiZGMvSjmMcTxiRqm2XZ6EhPTlmxXqmO61kby3V8wQVWwHuosE2ckTYCMcRj83/ddvzw5vv329tftk3gx1hS9DUUwqHdZ3x12wtjkH/e/Li7u0MzBr1rAeSB+bG2/4Qi620pSykkL/i4GpYdF2kvAQdDpjivlOaMfVF1mZzmHIZZlo0Cogmqqr6otu/Z4VZoxmZPjzgSTV3j76Cqq6Ed2/9f/Ssd2jPIlqqhGYQVVS4axquLV5JLmvGUiT9apJF/32ubNAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image23\",\n \"title\": \"image23\",\n \"src\": \"/static/273996145c2c87c428e91aca96ff76ca/d0c0e/image23.png\",\n \"srcSet\": [\"/static/273996145c2c87c428e91aca96ff76ca/a2ead/image23.png 259w\", \"/static/273996145c2c87c428e91aca96ff76ca/6b9fd/image23.png 518w\", \"/static/273996145c2c87c428e91aca96ff76ca/d0c0e/image23.png 715w\"],\n \"sizes\": \"(max-width: 715px) 100vw, 715px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Input the number of runs. Select either the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Minimum\"), \" (determined\\nby the model terms you entered in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Model\"), \" box), \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Default,\"), \"\\nor enter the number of runs you want in \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"User Specified\"), \" (figure\\n13a)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click on the red triangle to the left of \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Design\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. Choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Optimality Criterion\"), \" , then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make D-Optimal Design\"), \"\\n(figure 13b)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Number of Starts\"), \" ; enter an appropriate number and\\nchoose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"c. Choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Design Search Time;\"), \" enter an appropriate number and\\nchoose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Design\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 13a. Specify the Number of Runs Figure 13b. Specify the Optimality Criterion\\n\", 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\": \"955px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/8bd727dcf8a29a60d23457c3d7fe1815/a0b80/image24.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\": \"106.56370656370657%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAAC10lEQVQ4y5VT2W7bSBDk//+SsS8L5MEGEq+9XtE6KIrkcE7OzeElyU5R3n0IHCySQmNESl091dWtrCKs09ZY50MMsY99SsP4b4zjME63WF/7NCBSSkoHZXpE9pQft4eypbSqSU2o6oxxwTj/cdr/ztAnF3ptfVnzvBDPe7ktVbY71vlm+/fT08P9AyGkU4pSyjlXSgrB5XpwHNZa72ynddVQ57p+GLV1WUEUajPGiqKIsZ+mydwQb+iBlHDgCR/eB6oMEwJNQkW23ZWMC5DLskRyGgbnHLoAikNhjG3qWog1oalqpY02VnSWSn9iOtt8e6obKgV/zV+7rpvGEReCD5113dhbIXRxPB6rqhKqg7vwTCsqZJcREDtTN2TzuuVShTRC85T6ZZ6WCUYnlFsxjfM8wzaohf7zkuZpzpiyQtuyJi+bbcNESMORqi//HP78K/+6r15aTbVHIdDneerTiJtb0i7L+f39PdsXVdsyzthuu0NDMwxz/vn18PD4/PDtuWgYX9fAQCpuhiV4k0LOy7KSi4qQllHaomeMCg6h4WK/hz3jMKQYUQ4uhhCWZSVr42DNsizTNGanVp7q9rDbM8rgkvf+crmQhiilUPvt7Q3nMAxSysv5HNNwIpQx+CSRkAntG0LzPD+WpeACvSEbXSEbD+fz+Xq9QjBGgJtjGpUoeXvCGmKumTTxWJ7+uLu7v79vmsZYNGggcjX4R8CwmKbgGsmqlFb/MiI0Rg8GPAMgBkw0O33CjTx623B6EkJBTkaVw3jrqmKMYwVxH75F6vgpAKxvsDUjBQbkvMuo1ELIbb4xWqc+rgtwhpfz57hgM8ZRKm6Mpky2TGaHmu2K+uvjy6nhykTReanDTwM/Net/P7xdr5gIRoCbLUbVcsWEJkx2NmgXfxrKooT72C0A8jIbIBYIWAkI+xjsr2AlmxCxGPDp4ytw/z9+IGsfvMPEI5bh/XcA8ndfypqWpqVWbwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image24\",\n \"title\": \"image24\",\n \"src\": \"/static/8bd727dcf8a29a60d23457c3d7fe1815/a0b80/image24.png\",\n \"srcSet\": [\"/static/8bd727dcf8a29a60d23457c3d7fe1815/a2ead/image24.png 259w\", \"/static/8bd727dcf8a29a60d23457c3d7fe1815/6b9fd/image24.png 518w\", \"/static/8bd727dcf8a29a60d23457c3d7fe1815/a0b80/image24.png 955w\"],\n \"sizes\": \"(max-width: 955px) 100vw, 955px\",\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(\"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\": \"847px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/6edde8a38fdbdaa87feced0f8a3244ef/b2cef/image25.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\": \"120.84942084942085%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAYCAIAAAB1KUohAAAACXBIWXMAAAsTAAALEwEAmpwYAAACwUlEQVQ4y51U2Y7rRBD1P/NBfAFC4hF4GSGQAF1lrjMzTiaO433rxb243baT2Pc4UYYAV0KhVSpVV+vUqc121ttot/Pfd1EYxe9htj0kRRKXec4pKXAIO6S0rFgjtTa91N1gzXy0RgvGhfPsbl/etp9Wm7fNzvX2T+7upz/cX9b+54Q8b4K3bbjysq2fQuKM1IR/+2vzzQ/mu9/zLE4cd+0RQtI0iaOoEWKfZJ4fQicljdMiy4o4Sg5hUpaUEJql8W878f1n9Zp18zw53t73d77Wbdd1Wqk0jl/XbhgEgjN4pmmKDjHnDWO8ronneZwRLWir5TTNjm6HcRxwtNZSyjRN16673wcLgLJhGLM0V0rXNZiZ523SgqQ151LPACtthx5nAbdtyxhLksxaK4Q8Hs/jeCzyUgoFWkr54RAWNc0XsDqfp7+BcRilcZyY1lDKGi7AnKcFDK3aphHBfl/U7OtgMCM5hAcVBRPlAJdFpVQrhUTDdu/vRUVywjG56d9p13WF/qFIYJI4tbYvy6rrbHiIkjTzfb8kLKsxY3UDD3fMlIRh1GoUz1Hw8XiqyhpgZEEX5l1R0b+YuewsZtJZtBr4qq6iKJZSodtt2yFtgFttEAstDPZBXpKsWpiXmr1Pz95mg2HneX6dFgLhoTMWqYAcV4QwBhPo4TFdb/uxH46n09nZPD29vL4dgqBpQLWsCpBXmef5w4YgT8jVOJ0Wj/Pzn9GPLunHozEtmAFGSDzc9Idxvtr3rw4RvTDjJSX9n+A7/wWstR0He+22UsoYgw7j7aY/jBPsO/+iHantMqjbhj3G/I/1fAwslb1g/xe4NePlkxwxp4drzrMaExZC4GN8GPy8esFvCLRlWQL8WNqr1QtW8nw+NZwrJa3tJuzWZZOgp/P8cV3sm/+qnThrCFOE65IISEUlEx2ENube+Or1C7lwT/Fk3Td0AAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image25\",\n \"title\": \"image25\",\n \"src\": \"/static/6edde8a38fdbdaa87feced0f8a3244ef/b2cef/image25.png\",\n \"srcSet\": [\"/static/6edde8a38fdbdaa87feced0f8a3244ef/a2ead/image25.png 259w\", \"/static/6edde8a38fdbdaa87feced0f8a3244ef/6b9fd/image25.png 518w\", \"/static/6edde8a38fdbdaa87feced0f8a3244ef/b2cef/image25.png 847w\"],\n \"sizes\": \"(max-width: 847px) 100vw, 847px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"At the bottom of the new window, set \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Run Order\"), \" to \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Sort Left to\\nRight\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Table\"), \" . Notice that unlike when using a \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Full\\nFactorial\"), \" or \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Screening\"), \" design, there is no \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Pattern\"), \" column\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"To assess the designs balance, JMP has graphically see the results\\n(balance) of the design:\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. From the JMP main menu, click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Analyze\"), \" then\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Distribution\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Under \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Select Columns\"), \" , select all the factors except \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Y\"), \"\\n(the response variable) and click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Y, Columns\"), \" to add all\\nthe factors to that box\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"c. Click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"d. The bar charts can be used to determine if each factor has\\nbalanced levels, and whether the other factors' levels are\\nbalanced over a factor level.\"))), mdx(\"p\", null, \"Creating optimal designs requires a sound understanding of design\\nprinciples. Analysts can create an optimal design to meet the\\nrequirements of almost any test situation, but should review the test\\ndesign to ensure the following:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"There is no excessive aliasing/confounding between main effects and\\ntwo-factor interactions; A good rule of thumb is to have\\ncorrelations below 0.5 as much as possible and not exceed 0.7.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"There are enough degrees of freedom (dof) for error estimation; a\\ngood rule of thumb is to have at least 5 dof to estimate error.\"))), mdx(\"p\", null, \"The aliasing structure in an optimal design can be very complex, which\\nresults in biased effect estimates. The D-optimality criterion is most\\nfrequently used at \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", as it minimizes the bias in the effect\\nestimates that results from correlation between the specified model\\neffects. When JMP is used to construct an optimal design, the design\\ndiagnostics which can be used to evaluate the correlation structure are\\nprovided under the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Design Evaluation\"), \" header.\"), mdx(\"p\", null, \"An analyst should create several optimal designs and compare them using\\nthe Test Design Measures of Merit. The\\nalgorithm that generates the optimal design may not always produce the\\n\\\"best\\\" design. Optimal designs are usually created based on a single\\noptimization criterion. In contrast, full and fractional factorials are\\noptimal over several optimality criteria; when fitting a model with main\\neffects and two-factor interactions, factorials are D-optimal,\\nI-optimal, and Alias-optimal. If the number of runs in a test is a power\\nof two and all factors have two levels, then the optimal design is a\\nfull or fractional factorial.\"), mdx(\"p\", null, \"Unfortunately, it is possible an optimal design algorithm may not\\nproduce a factorial when appropriate. As mentioned earlier in this\\nsection, this may be due to insufficient run time for the algorithm or\\nanother design has an equivalent value of the specified optimality\\ncriterion. Consequently, it is wise to verify that the software used to\\ngenerate an optimal design actually produces a factorial design when\\napplicable.\"), mdx(\"p\", null, \"The number of runs in the test design can have a significant impact on\\nthe quality of a design produced by a construction algorithm. Suppose\\nyou have a design with two three-level factors and one four-level\\nfactor. If you require a design with fewer runs than the full factorial\\nwith 36 runs, you should choose a design size that is evenly divisible\\nby the number of levels in as many factors as possible. By doing this,\\nyou make it more likely the factor levels are balanced. For example, if\\nthe chosen design size is 26 it is impossible to balance both the\\nthree-level and four-level factors. However, if the design size is 24,\\nthen the design could be balanced; each level of the three-level factors\\ncould be in eight runs, and each level of the four-level factor could be\\nin six runs.\"), mdx(\"h1\", null, \"Augmented Designs\"), mdx(\"p\", null, \"When a test plan changes during execution, the uncompleted portion of\\nthe design should be updated ( \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"augmented\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn27\"\n }, \"27\"), \" ) with new runs; optimal designs in particular may not be\\nrobust to lost or altered test runs. Designs can be created and\\naugmented quickly with software, but logistical constraints may make it\\ndifficult to adjust test events in real time. The following describes\\nhow to augment designs in JMP 13. Note that JMP assumes that data is\\nentered in the response column.\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Augmenting a design in JMP 13:\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Open the existing design table in JMP\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"From the main JMP menu, choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augment Design\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Drag the response to the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Y, Response\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Drag the factors to the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"X, Factor\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Action\"), \" box, click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 14a. Augmenting a Design in JMP Figure 14b. Enter the Response and Factors\\n\", 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\": \"463px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/940c09bed5bbe5fa17ab5754394474af/71ce0/image26.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\": \"71.04247104247105%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAACNklEQVQoz41RS2/TQBD2X0L8AyQOSNw4ceTCb0JICCFQLkiVChcurQREpa2SqEkTO/EjfmQfXtuJ3/Zu7HoZp1SqeEh8Ho2/ndnZnW9WMb3Q8fDaRbaHbRdTFiEaNlLythO9yTsvK9HypkuLOsnLvBJAFMPZEIIpxQFjBAPQBvURINSHH2I+gMIGSonPGCY4isI0TZtmr0xVXV/pqrbUDTPJ8rwo06xIs3S73QG2B0RRFIQBANJFnkO8LCsh9opu2I69xs46JJuGF3JfyqaGuzRNW2qablpr26WYUEI9b5OmWRzvTMPYIJTEseJjMh3P3w6DwWVydM3fXFTHCw7djkaji/Pz6Vw1HMrrqoSvqrMsY4zNZrPhcGjbtpIE7NvX+aMP8vG77sl7+eCVfDbY51nWdd3NzY0QoicH3i+5ABW6bkwmE0KIEvv0+8n4xSf5/GP3dCAfvpYvj1sYnmVBwzZy3S1Gvfw4TpKkLMsY+j7MAYjCokQ10NKvV0zMiVCpsMIahns9m06uZuZkrH4+UnVzuVgs5ipGOIyiH2dnpyenpmUpQVKAoj0vG162By+qAm5o27aTsvCJcfJFXzsb10viFNqGyU9GIyjuNcd53exFzQW/Z1BcwXw4z+M49BwWwMNmoB9iIMHQV6AZIaTsMngx/htgE5TfnlBDuq6B3Z7Y+7oHkL8Xc/EL/F7udinuIkCUbVLCwXX1p1X/Nri398rY2mreTnX/yzQvvlzRK4uNVHdmhT8BhDX6dqk7Ql4AAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image26\",\n \"title\": \"image26\",\n \"src\": \"/static/940c09bed5bbe5fa17ab5754394474af/71ce0/image26.png\",\n \"srcSet\": [\"/static/940c09bed5bbe5fa17ab5754394474af/a2ead/image26.png 259w\", \"/static/940c09bed5bbe5fa17ab5754394474af/71ce0/image26.png 463w\"],\n \"sizes\": \"(max-width: 463px) 100vw, 463px\",\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(\"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\": \"484px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/afca27eb6f2f06f2145c833626d5c997/ff42b/image27.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\": \"69.4980694980695%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAACNUlEQVQoz2VSXbOaMBTk//+atm+3L/bq9NaCV+z4rUASgoGQEBQQFK12xXamne6cObPJZE9O9sRaU8mFIpGkPOGxZjspVO7RiPDEY2InTRirXWqa6706/yyby6FupSnK01UfjhYVmRCShIKwKGCRD5ZmIlHxI2upc6mM1Huzr0xeZXmJ0KZAVuZgQTDsv374+Kk/6AOfX16CgGTGKKVTpVIA+RlpKrullA+CsJLs4NjDXq9HGSvKQmstpUySROyE6oBlHMecc2RwIcRzE7Dy6hSFoWPbvh8wFkJ8BKpqNpvO5guxi5umIYH/PnKNMevl0nHeI87LDlZWHHFLLGLOOCUMfd1ut/v9jr58L1CpBofM5DnIYrEghKIv3cEyZcPCYDKehGFUVsdbB5zzfW/4zeYsAt/xkIUcxB2PZ7PF4XCAMssyS+3LLV1tN15VHS9tW9c1+mzqGsdxc57vr9cruoA9bXvBgyEzf2DxRI1s++3r22g0Gg6Hju0M+q+93hd37B7r+nQ6odz5fAbpatbVX7DSvHgfjQb9gW1/dxwHja1Xq/l8wRhr2xaC01PXEdTAJnpBxtJK9P6HC0xmwHQ6cd3lYhmGIZ70GKrWsEemv4eMgBcTdxIQgnK4uWSUYE4QEEKCINhuNpgqDMk7kx/OZJnuLELCsfVqjV/wEDORMkYpZZgB8jPAUa4LIPA8Hx+rLKuiKOFrdWxAUNiaE7WlckP+C/pP+FyTnaHCrKmabqO1xz2mfgEqE/NNb+cH1QAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image27\",\n \"title\": \"image27\",\n \"src\": \"/static/afca27eb6f2f06f2145c833626d5c997/ff42b/image27.png\",\n \"srcSet\": [\"/static/afca27eb6f2f06f2145c833626d5c997/a2ead/image27.png 259w\", \"/static/afca27eb6f2f06f2145c833626d5c997/ff42b/image27.png 484w\"],\n \"sizes\": \"(max-width: 484px) 100vw, 484px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"If the existing design has already been executed, it is a best\\npractice to check the box next to \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\\"Group new runs into separate\\nblock\\\"\"), \" (See the blocking discussion.)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Linear constraints on continuous factors, or disallowed combinations\\nof categorical factors can be added in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Define Factor\\nConstraints\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"To replicate the existing design, choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Replicate\"), \" in the\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augmentation Choices\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"To add center points to the existing design, choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add\\nCenterpoints\"), \" in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augmentation Choices\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Otherwise choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augment\"), \" in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augmentation Choices\"), \" box\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. Only the main effects are loaded by default in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Model\"), \"\\nbox. To add more model terms click on the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Interactions\"), \" drop\\ndown menu and choose \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"2nd\"), \" (this will load all 2-factor\\ninteractions); If you want higher order interactions, choose\\nthose as well)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Under the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Design Generation\"), \" header, enter the total number\\nof runs in the design \", mdx(\"em\", {\n parentName: \"p\"\n }, \"AFTER\"), \" augmentation; e.g., given a\\ndesign with 20 completed runs, if you want to augment it with 10\\nadditional runs then enter 30 runs.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click the red triangle next to \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Augment Design\"), \" , select\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Optimality Criterion\"), \" and select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make D-Optimal Design\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Design\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 15a. Select an Augmentation Choice Figure 15b. Define the Model and Enter \", \"#\", \" of Runs\\n\", 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/4675fc77b3966076342674a27a0c4448/5bd27/image28.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\": \"71.81467181467181%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAAB80lEQVQoz3WS646bMBSEef83y4+qWe02NxJIbLANvnMxYJK0A1EqVeqOBjCg75zDmOSck/zKmFCMy/x6vRZlXsiCKaUbZbpK2pIrIZSoFWOyLHkpNGEGLrhJzueUEGqMYSVjjBtrUQnmoiqYuFGW4RBS1FrbxvjWuA7GulIu0Ub3qzjn1tghDN41zjqUyvLbr88vTFNDomJryXpVJURVyyTGOAxD27Z1VXvnx3EEaa2VUtKSUUJCH5SUGM05W62iBI9JrXQCEt0Al0Upa1nXErDRljN+JfQH9HO7OxyVUsCEEM457z0g59skzvM0TStcaKTUtLCzHrUJLbNLtj1mKeW1EKdTiokwWghhHIam7RJGCOqhmDam67oQhiWArvO+qaQqKC1o0XU9Giipfq/C+xD6BT5sP5gQ6Bzj/Hg87vf76/x8Pts+bDab7fajfAvTojPO0zT6pkv6sKxWOD7eepUI4wTgcrmc0/Nut8dGvmAIg3h0xgWPmqb5C9/fGsYJEWLsJbz8hsDHtxYYnV9jfAcj3/SUIrY8u2qt/wMjve9gZJlfMs5YnuX4N/CB/8DYIe+x/2ae4/P5gIHDWCD642F/PBzw54LH2GDjNMFzjMs3E8raNiht+4CCMzyMEZ7irF37ub/kRBRcw6UwMKssjFvK1R/AWg5tAJ2c/AAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image28\",\n \"title\": \"image28\",\n \"src\": \"/static/4675fc77b3966076342674a27a0c4448/e3189/image28.png\",\n \"srcSet\": [\"/static/4675fc77b3966076342674a27a0c4448/a2ead/image28.png 259w\", \"/static/4675fc77b3966076342674a27a0c4448/6b9fd/image28.png 518w\", \"/static/4675fc77b3966076342674a27a0c4448/e3189/image28.png 1035w\", \"/static/4675fc77b3966076342674a27a0c4448/5bd27/image28.png 1432w\"],\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(\"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\": \"540px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/0e56354a48d688a9dbe9a0f2de1eab14/07484/image29.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\": \"123.93822393822393%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAZCAIAAAC+dZmEAAAACXBIWXMAAAsTAAALEwEAmpwYAAABcklEQVQ4y52U2XaDMAxE8//fyk7ZytZb3xyTkEBo9cAZyxpJY8vc1nUdx7FtW77fwYZhOAKPNs/zDfKyLF/BCOq6Ls/zIVhVVSQFlGWJH0BMXdeUYQn+JWNGA8gHQafpAX3fU8AecbpsmuYNGW90SqaOQDIBGxlEM3gvkqXcybjSNPXMaAmFYzBUsQQgHjBNEzFw8Kj/P20/Vf5ItqzSzsgE0Y9OOQC6NYt3HmvcdCVJQgTAe7YCpVgC0CyAQGpva9Ps3sV73tqGxt6un0j2VKP4PVnv0YShGQ/Zz+45yzIW8GGCH2eb6KIoHHJn2ydw10xW4nCRj0RsL8GIYGkRATHqp6P399wFs8M/D4lHSO7Ppx3bdrZ9vTBfZ9t/xn62CWUw9DokfbD4Mzg7MNv2Ynw6V4ckjrGzyTeSL70q0et4XiKz5mfAOUFDkj8G9pgWhIE5BfUTo37CNs2+EhOxEf9NSiURAb5N+3oakiPzeo52fwCK2bl1mKBICwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image29\",\n \"title\": \"image29\",\n \"src\": \"/static/0e56354a48d688a9dbe9a0f2de1eab14/07484/image29.png\",\n \"srcSet\": [\"/static/0e56354a48d688a9dbe9a0f2de1eab14/a2ead/image29.png 259w\", \"/static/0e56354a48d688a9dbe9a0f2de1eab14/6b9fd/image29.png 518w\", \"/static/0e56354a48d688a9dbe9a0f2de1eab14/07484/image29.png 540w\"],\n \"sizes\": \"(max-width: 540px) 100vw, 540px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Make Table\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"To graphically see the results (balance) of the design:\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. From the JMP main menu, click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Analyze\"), \" then\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Distribution\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Under \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Select Columns\"), \" , select all the factors except \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Y\"), \"\\n(the response variable) and click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Y, Columns\"), \" to add all\\nthe factors to that box\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"c. Click on \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"d. The bar charts can be used to determine if each factor has\\nbalanced levels, and whether the other factors' levels are\\nbalanced over a factor level.\"))), mdx(\"h1\", null, \"Designs for Computer Experiments\"), mdx(\"p\", null, \"Data for some test programs are obtained from simulation models, many of\\nwhich are \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"deterministic\")), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn28\"\n }, \"28\"), \".\\nThis means that the simulation output does not change if the inputs are\\nheld constant. In other words, a single observation obtained from a\\ngiven combination of factor levels (test point) provides all of the\\ninformation available about that test point.\"), mdx(\"p\", null, \"When obtaining data from deterministic simulations (or software systems\\nwhich have deterministic outputs) using a factorial design may not be\\nthe best experimental design strategy. An efficient design strategy for\\ndeterministic systems uses the following two principles:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Designs should not replicate test design runs; one run provides\\ncomplete information about the response variable at that test point\\nbecause there is no variance in the response.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Designs should allow for the fitting of complex models by providing\\ninformation about the response variable at all areas of the design\\nregion.\"))), mdx(\"p\", null, \"The next section discusses some alternative designs that follow the\\nabove principles.\"), mdx(\"h2\", null, \"Space-Filling Designs\"), mdx(\"p\", null, \"Space-filling designs are constructed so that they spread design points\\nevenly throughout a design region. These designs are used when the test\\nfactors are continuous. The following are general construction methods:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Disperse the design points as uniformly as possible in the design\\nregion using distance measures.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Obtain design points using sampling methods in the design region\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Utilize a hybrid distance measure/sampling approach\"))), mdx(\"p\", null, \"Common construction algorithms for these designs include Uniform\\nsampling, Sphere Packing, and Latin Hypercube sampling.\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Uniform space-filling designs -- Design points are randomly selected\\nfrom a uniform \", mdx(\"em\", {\n parentName: \"p\"\n }, \"distribution\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn29\"\n }, \"29\"), \"\\ndefined over the range of a factor. They are simple to construct and\\naugment (just add more randomly selected points to the space.)\\nHowever these designs tend to leave gaps in the design coverage when\\nthe points are unevenly distributed---particularly when the number\\nof test points is small relative to the size of the design space.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Sphere packing space-filling designs -- Algorithms pack circles,\\nspheres or hyper spheres of equal radii into the design space and\\nuse the center of each as the design point. Sphere packing designs\\ngive even coverage across the design space but are difficult to\\naugment because the spheres have already been optimally \\\"packed\\\"\\ninto the design space and any new points would upset the\\ndistribution of existing points.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Latin Hypercube Designs -- Each continuous factor is divided into n\\nevenly spaced intervals, creating a grid of hypercubes (in the\\ntwo-dimensional case this is a square grid with n2 squares.) The\\ndesign points are chosen so that each of the n subintervals are\\nchosen exactly once in each dimension. The worst case scenario, if\\nthis process is done completely at random, is that all of the design\\npoints fall along the diagonal of the hypercube (figure 16a). To\\navoid this, the algorithm is usually modified to create designs more\\nlike figure 16b.\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 16a. Worst Case Space Filling Design Figure 16b. Desirable Space Filling Design\\n\", 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\": \"515px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/fc172cea01f35f33f53eb89cdc129b64/fbdcb/image30.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\": \"128.95752895752898%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAaCAIAAAA44esqAAAACXBIWXMAAAsTAAALEwEAmpwYAAABgUlEQVQ4y53UiXKCQBAEUP7/Wz3wxIiYPLeplRBTHlOlDj3bc7TDNsMwHA6H6/U6vGkojc/pdNrv977P5/Nmszkej33fQ3a7HQcOPBdTBsjpuo7ffBdDqM7lcuF8FVMBv0bR5OIo+YTs6LGYOu+R67mI8pgstlqtTKKUDo2nDn7GqzP3xaYgUW6VHf2w8gdtKx5wJFdJ0vOMXFOnYaGR7Ge73RoAhCarcAhADi0cuBSTGqhn4G1mYT8kwQERz2MIbdtyVFgul6diU1CZRif6qc280vZdsIgB4oSQdO+p7ZkDCllvUVEjBsmxCt4FM0beB1kfzgzsis1nnk313syvLImMaPnD0vYv8tMlcTrrPX8xpkvC/7skFBGagbclkQMUDj490rkYUCm9rNfr3CRTcBRs1rYY8ieCIaeCxl5akni5ELNn2bm0kzvgWkzGiJfb4ibYYrEgiQcB4xmGA+FHIS9Gom0xjjNj5Vw0aSx6ZBPrVsqS/0902s44839WV/2h/QB0bvIDmb6WSAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image30\",\n \"title\": \"image30\",\n \"src\": \"/static/fc172cea01f35f33f53eb89cdc129b64/fbdcb/image30.png\",\n \"srcSet\": [\"/static/fc172cea01f35f33f53eb89cdc129b64/a2ead/image30.png 259w\", \"/static/fc172cea01f35f33f53eb89cdc129b64/fbdcb/image30.png 515w\"],\n \"sizes\": \"(max-width: 515px) 100vw, 515px\",\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(\"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/3f475d88968f9957501fccf228114009/e3829/image31.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\": \"40.92664092664093%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAICAIAAAB2/0i6AAAACXBIWXMAAAsTAAALEwEAmpwYAAAA20lEQVQY052Ny07DMBBF8/9fxIZ1JSQkJCiJ6tqJHU9je5wmTZPi4DjgKqJQNjyuzmLmao4mSQl7TDcZYQBQ21rAjpeqKKudbio8Vqb7hsJjBHQH6pCsKVDGc8YI2Vq0YJpSH6TpAHtpPoEzg6jaDcc1VTer7e29SNzoh9MpS7MIIo7j+PZThhcXQohDMs/nhRSCFFzV7QOVq2d6l+VP0nKz1xqtbdE23vuL7KcwRy3K0xQubeyUQcpyUUqs913fO+e8nyLL9ZLXj/VK/mW+fA5XcuzmJf+Q//T5HTwPyxNHDTtqAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image31\",\n \"title\": \"image31\",\n \"src\": \"/static/3f475d88968f9957501fccf228114009/e3189/image31.png\",\n \"srcSet\": [\"/static/3f475d88968f9957501fccf228114009/a2ead/image31.png 259w\", \"/static/3f475d88968f9957501fccf228114009/6b9fd/image31.png 518w\", \"/static/3f475d88968f9957501fccf228114009/e3189/image31.png 1035w\", \"/static/3f475d88968f9957501fccf228114009/e3829/image31.png 1077w\"],\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, \"You can create Space Filling Designs in JMP 13 by going to the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \"\\nmenu and selecting the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Special Purpose\"), \" option, then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Space Filling\\nDesign\"), \" (figure 17a). JMP 13 provides 7 design construction methods\\n(figure 17b).\"), mdx(\"p\", null, \" Figure 17a. Opening the Space Filling Design Platform Figure 17b. Space Filling Design Methods in JMP 13\\n\", 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\": \"635px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/6dcb712bfae8f7365fd595c4a833d9e1/1ddef/image32.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\": \"116.21621621621622%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAXCAIAAACEf/j0AAAACXBIWXMAAAsTAAALEwEAmpwYAAAC2klEQVQ4y51UaXeaQBTl//+Y9vRT+l3RxmgEMYIQ2YZtgGHftFFzgVPb9KTrPTjnOczl3bcNZzmR61HXpzbxLeK5QeTTuKzbrKzzqimqtqjbvKyxUzZtVtSw4ySv2mPZdJwsq8Jqtbj/Muf5+/lckXeu4xAbsIbVxmqaxmBahq7blmlbVsIYi2POcrxPHz/c3X1erVZ7RdE0zR3gOA7WJEmyPM+yLE3T/GYUOfZjkMOkEAVhOpkuH5brtSDvdhtRnM9mi8VCkiQPcL3BTUwIiaIINMe2QxriQxzLq6Io8Bpr23Xn8/lyvVimCbdVXYMThmGWZzBoQOEXZN/3e0Ugp0VzvV6u/46XlxfIzgmxwjAqyxLO67quql4LAM9A+R7aARxlGc/zO1keFT5rz4Q4MBAe8ov80QHBgJsNzV3XcTStVMO7Xs6jmMD3Td1suyNspAlHRxVRhA+GMMacQ93xePyfmC+XCzT3noMo2YiCLMuKoqiq+rSVDMO4RfUb9OQ4Kx+Xy620RXkOh4Ou6yhb0zR/ZPbkvO5cQlbL1VaSttutKIiaqgU+PZ1Ot0O/AudHCXo5SYbyM5YmKSqGfHR/AY54VJFlTVVNw4RyaMYuZI8FB5q3wP532fCMcdk9IVOSIivoSsu0MDe2hQamLGanr4jgdPM2puMHsmVtxM3ifiGsBSTMNAyoMHUD3Y++QOXRP6jqO2QvTPTDAeQZP8OKlhrdYpDTNBtnEAaK1w38n8gMYziZTPkpP5lMMIYYvcAPQMZHXNfzPY/YxCFOWVXQ/4bs0ljaiNC8fHiYz+frx/Ve2aPgpCfjMkEpCKIwdMPBdRVQ1OJNqTR1j/KucRWs+1bTDzo4UT8aURyz/seSwV+f6pvndiCzIc+YKhwO0fj9aOa4aMaIcRFk+It4ETHS1jYNDOg/no6c4aWuz/wwC5MqZGUQ53hoXFBW9Ou3BwfGJ4hyEqRuEHtB8gq+8fdAn1CFsgAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image32\",\n \"title\": \"image32\",\n \"src\": \"/static/6dcb712bfae8f7365fd595c4a833d9e1/1ddef/image32.png\",\n \"srcSet\": [\"/static/6dcb712bfae8f7365fd595c4a833d9e1/a2ead/image32.png 259w\", \"/static/6dcb712bfae8f7365fd595c4a833d9e1/6b9fd/image32.png 518w\", \"/static/6dcb712bfae8f7365fd595c4a833d9e1/1ddef/image32.png 635w\"],\n \"sizes\": \"(max-width: 635px) 100vw, 635px\",\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(\"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\": \"930px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/cdd0a56ba4b0448053d961858403f19e/416ee/image33.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\": \"73.74517374517376%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAzUlEQVQoz+2Ou26DMBRA/f8/1KlThk6dGFKSGBKFh+/DxuZRcCBQJ+palKhSpx6dybrn+ooohSTDfZrloKdl8eM8XufLtKaf5s/h0vVevLynm4N9jcq3uCyyszEmzwsFytrKWfujztXOiUQmWhvWuiyV3G8BIPpI4p2EG7iiUiCkPBBRWBZmiXVd11Vlg+uEn5m1iOMdE92uLQpEDK/2Ab7j8/GkjWmahogR6bnYe7/c6fs+9M/Fw6/i4T/+u7jruvFO27YKkDUTPyQSfQHfeUuH6DcRigAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image33\",\n \"title\": \"image33\",\n \"src\": \"/static/cdd0a56ba4b0448053d961858403f19e/416ee/image33.png\",\n \"srcSet\": [\"/static/cdd0a56ba4b0448053d961858403f19e/a2ead/image33.png 259w\", \"/static/cdd0a56ba4b0448053d961858403f19e/6b9fd/image33.png 518w\", \"/static/cdd0a56ba4b0448053d961858403f19e/416ee/image33.png 930w\"],\n \"sizes\": \"(max-width: 930px) 100vw, 930px\",\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, \"For specific questions that are not addressed here or in the JMP help\\nfiles, feel free to contact the Intelligence, Analysis and Assessments\\nDirectorate (A-2/9).\"), mdx(\"h1\", null, \"Test Designs for Comparing Systems\"), mdx(\"p\", null, \"Comparison tests are conducted to test the hypothesis that a system\\nmeets a specified threshold, to compare system performance under two or\\nmore different conditions, or to compare the performance of two or more\\nsystems. When designing a comparison test, there are two important\\nissues to address:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"When data is grouped by the systems being compared, or the different\\noperational conditions for which performance is compared, it is a\\nbest practice to have an equal number of test points in each group.\\nThis will facilitate a more effective comparison of the group means.\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The number of test points in each group gives appropriate power to\\ndetect the delta (difference between the group means) of interest.\"))), mdx(\"p\", null, \"For more information please contact the Test Design and Analyses\\nDivision of A-2/9.\"), mdx(\"h1\", null, \"Test Designs for Problem Identification\"), mdx(\"p\", null, \"Test designs for problem identification are constructed using different\\ndesign principles than those used for system characterization. The\\ndesigns, called combinatorial designs or covering arrays, are used when\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is assumed to have a deterministic response variable; i.e.,\\nreplicating the design points is not necessary. They are typically not\\nsuitable for characterization of system performance in the battlespace,\\nbut they generally require fewer runs than designs used for performance\\ncharacterization. These designs are a useful tool for designing test\\nruns for \\\"demo'd\\\" factor levels; i.e., for test runs representing rare\\noperational conditions. Consequently, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test may involve designs\\nfor both characterization and problem identification.\"), mdx(\"h1\", null, \"Combinatorial Designs (Covering Arrays)\"), mdx(\"p\", null, \"Combinatorial Designs or Covering Arrays (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command Technical Advisor OR Contract Award OR Criticality Analysis\"\n }, \"CA\"), \"), terms sometimes used\\ninterchangeably, employ the science of systematically selecting\\ncombinations of factors and levels to provide the best chance of\\nidentifying problems. They are constructed to efficiently evaluate a\\nsystem at all possible level combinations for subsets of \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" factors,\\nwhere \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" is usually small relative to the total number of factors. Note\\nthat a combination of levels for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" factors is called a \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"t\"), \" -tuple\"), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn30\"\n }, \"30\"), \". Combinatorial designs are often\\nused in testing software intensive systems with a deterministic binomial\\nresponse variable (a pass/fail response which will not change no matter\\nhow many times the design point is replicated.) However, these designs\\ncan also be applied to testing other types of systems where problem\\nidentification is the primary goal.\"), mdx(\"p\", null, \"Combinatorial designs have advantages and disadvantages. The drawback of\\ncombinatorial designs is that they do not allow for the effect of a\\nfactor to be estimated nor do they allow for statistical modeling; they\\nare rarely balanced or orthogonal. The advantage of these designs is\\nthat they can be used with a large number of factors---even if they have\\nmany levels---as the size of the design can be controlled.\"), mdx(\"p\", null, \"Design size is determined by adjusting construction parameters called\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"strength\"), \" \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn31\"\n }, \"31\"), \" and \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"coverage\"), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn32\"\n }, \"32\"), \". Combinatorial designs have\\nstrength \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" if every possible \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" -tuple of factor levels appears at\\nleast once in the design. The notion of combinatorial design coverage is\\nused to quantify what percentage of the possible factor level \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \"\\n-tuples occur in the design. Intuitively, 100% coverage at strength \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \"\\nmeans that all possible \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" \\u2011tuples appear in the design at least once.\\nA test team may choose a design with less than 100% coverage at strength\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" , rather than 100% coverage at strength \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t-1\"), \" . The benefit is that\\neven though the design only partially covers the possible \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" -tuple\\ncombinations, the probability of finding a fault caused by a t-way\\ninteraction of factors is higher than when using the smaller design of\\nstrength \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\\u20111\"), \" (with 100% coverage); therefore the overall effectiveness\\nof the design at finding faults is higher.\"), mdx(\"p\", null, \"A combinatorial design can be constructed for any combination of\\ncategorical factors and levels (continuous factors must be converted to\\ncategorical). Disallowed combinations of levels can be removed from the\\ndesigns, but this may increase the size of the design for a given\\nstrength and coverage. Industry has embraced combinatorial designs for\\nsoftware testing as an efficient method of finding software problems\\nwhen the possible input (factor) space is large (Kacker, Kuhn, &\\nLawrence, 2013). During an operational test for a software intensive\\nsystem, a combinatorial design may be an option to evaluate\\ndeterministic measures. However, data for any \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"stochastic\"), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn33\"\n }, \"33\"), \" measures (those having random\\nvariation) should be collected using other types of designs.\"), mdx(\"p\", null, \"The National Institute of Standards and Technology has a free tool for\\ncreating Covering Arrays and Combinatorial Designs: Automated\\nCombinatorial Testing System (ACTS). The tool takes the factor and level\\ninputs from a test design, and provides the minimal factor covering\\narray at the desired strength and coverage. The tool is located at:\"), mdx(\"p\", null, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://csrc.nist.gov/groups/SNS/acts/documents/comparison-report.html\"\n }, \"http://csrc.nist.gov/groups/SNS/acts/documents/comparison-report.html\"), \"\\n.\"), mdx(\"p\", null, \"JMP does not have a platform for constructing combinatorial designs.\"), mdx(\"h2\", null, \"Creating a Combinatorial Design in ACTS:\"), mdx(\"p\", null, \"Note: when entering factor or level names, do not use commas, spaces, or\\nspecial characters.\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"System\"), \" , then select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"New\"), \" (figure 18a)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Enter the name of the system in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"System Name\"), \" box\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Enter a factor (ACTS refers to factors as parameters)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. Type the factor name in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Parameter Name\"), \" box\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Enter the nature of the levels and the level names\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \"i. If the factor is a Boolean type (true/false, yes/no,\\n > pass/fail)\\n\\n 1. Select **Boolean** in the **Parameter Type** drop down\\n > menu\\n\\n 2. The factor levels are automatically named **true** and\\n > **false**\\n\\nii. If the factor is categorical\\n\\n 1. Select **Enum** in the **Parameter Type** drop down menu\\n\\n 2. Type the level name in the **Simple Value** box\\n\\n 3. Click **Add**\\n\\n 4. Repeat steps 2-3 for all factor levels\\n\\niii. If the factor is continuous\\n\\n 1. Select **Number** in the **Parameter Type** drop down\\n > menu\\n\\n 2. Type the level value as an integer in the **Simple\\n > Value** box\\n\\n 3. Click **Add**\\n\\n 4. Repeat steps 2-3 for all factor levels\\n\\niv. If the factor is categorical or continuous and the levels\\n > are labeled by consecutive integers\\n\\n 1. Select **Range** in the **Parameter Type** drop down\\n > menu\\n\\n 2. Type the first integer value in the left **Range Value**\\n > box\\n\\n 3. Type the last integer value in the right **Range Value**\\n > box\\n\\n 4. Click **Add**\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \"c. Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add to Table\"))), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Repeat Step 3 for all factors\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 18a. Creating a Combinatorial Design Figure 18b. Enter the Factors and Levels\\n\", 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\": \"831px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/73a2e2d3905b9e6606f75789e2e67fb1/5b4a1/image34.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\": \"74.5173745173745%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAABw0lEQVQoz41S2W7bMBD0//9ZH+o2bWzE1mWZssRreUm+ZMnuiErTFgGaDAaLBbXD4Wp3wRpdc1lzZdtjOJ6Pl/6Np+vtehsvtxHJuR/mE7C79MNwW5Z+IZQmrXnTHKqKN9xPcGAIXkmZZSljexRopZwzRFNChs6tWxZ6IRWlSbIrSyFlBT0XbdvGK3xVHb59X23T8nm1zXZVLfTzevNztWGNMlp9zfVCSJ2mSZblUkgi45yfaa0lIiTehzla64x1yBE7ZyYxnLM0K4od9IxV0IcA7w5VEOMK9w5/xGhZCCHRCdqRaFOZiNn5AzGX6sfT02q9ZllOUk6u0fpTzlJTkeecczwYVFqjnqbfSrP/f8VkX0q+3gkXur7vz5fL9XpF+FzPZNK8WL8keOzj8bjf748IPP1jsTYWTQbvTsfT4y/gLI7KzTOfZXNune/8bzG+wKHrunEch2EYI3wIOoIi5hHMOc6C1a/iOHlf1/Vmu2WMTXdbi61A0XbCBisopURZnudYhyRJVXNYFrTAUoW4U9HeIiAP3gvO2X5PcQYVY4g+loAYwutuN9pp49S/1NaXVZ0WpdAGzEvGFb19FTTd/iXTvwDzS0AaoR8T0gAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image34\",\n \"title\": \"image34\",\n \"src\": \"/static/73a2e2d3905b9e6606f75789e2e67fb1/5b4a1/image34.png\",\n \"srcSet\": [\"/static/73a2e2d3905b9e6606f75789e2e67fb1/a2ead/image34.png 259w\", \"/static/73a2e2d3905b9e6606f75789e2e67fb1/6b9fd/image34.png 518w\", \"/static/73a2e2d3905b9e6606f75789e2e67fb1/5b4a1/image34.png 831w\"],\n \"sizes\": \"(max-width: 831px) 100vw, 831px\",\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(\"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\": \"932px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/739a4c96f070296771b2f576d4a1d13e/f6f78/image35.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\": \"73.74517374517376%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAzUlEQVQoz+2Ty07DMBBF/f9f0x9gj0CiC0pJ2hJc6jgz9liOo7Z+pKKMsidql0hcHW9GczSba9F2sG/xZdN+KJPHa758l4k8znGK5XhOwmq5XMvFs3x4M9UegnddB5zQ9yH8yhACI0A3r++bVS1bcAf1pbVe1Z9VvUNARDMDAIpjwLpZP1awhRNYNwzB+97zmw0fJ3LiHHMPT1rJUkayFHh8Q3iNiESMydtGqUMuxdLdcrxOSSnRv/xH5Hy3zBWdfgJaS1xnco6rcgtozA8scUq3uvd32AAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image35\",\n \"title\": \"image35\",\n \"src\": \"/static/739a4c96f070296771b2f576d4a1d13e/f6f78/image35.png\",\n \"srcSet\": [\"/static/739a4c96f070296771b2f576d4a1d13e/a2ead/image35.png 259w\", \"/static/739a4c96f070296771b2f576d4a1d13e/6b9fd/image35.png 518w\", \"/static/739a4c96f070296771b2f576d4a1d13e/f6f78/image35.png 932w\"],\n \"sizes\": \"(max-width: 932px) 100vw, 932px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add System\"), \" when all factors are entered (figure 18b)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Create the combinatorial design by opening the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operations\"), \" menu\\nand clicking \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Build\"), \" (figure 19a)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \" a. Specify the algorithm in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Algorithm\"), \" box (the recommended\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > one is **IPOG** )\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" b. In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Strength\"), \" box, indicate the strength of the\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > combinatorial array (1-6)\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" c. In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mode\"), \" box\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" i. Select **Scratch** to create a new combinatorial array\\n\\n ii. Select **Extend** to extend an existing array\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" d. In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Constraint Handling\"), \" box, select how the algorithm\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > incorporates disallowed combinations of levels; the default\\n > method is recommended\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" e. Check the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Show Progress\"), \" box if you want to see the\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > algorithm's progress\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" f. Check the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Ignore Constraints\"), \" box if you have entered\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > constraints but want to compare the design with constraints to\\n > a design without constraints\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" g. Uncheck the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Randomize DontCare Values\"), \" box unless you have\"), mdx(\"pre\", {\n parentName: \"li\"\n }, mdx(\"code\", {\n parentName: \"pre\"\n }, \" > constraints\\n\")), mdx(\"p\", {\n parentName: \"li\"\n }, \" h. Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Build\"), \" (figure 19b)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 19a. Build the Combinatorial Design Figure 19b. Select the Design Options\\n\", 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\": \"506px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/6173875a132326703cdc682678095ee1/29f4e/image36.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\": \"52.89575289575289%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAIAAADwazoUAAAACXBIWXMAAAsTAAALEwEAmpwYAAABe0lEQVQoz41RYY+jIBD1//+zbXo1tsn2BBRwRQsKIqDd3dxe7tWmt/1wH+6FyMxk3szjmTWdEUqLVsf3X+nj63/O8vk7XD+HKWaNEIxSZ+31uuKsS1pSRJBiXJcFhRTDdV1QR+UdPbeWGMIcw5xVjB4OOSGkLMn59VzXopESqeq6ilWUsq7rkAohVavO558loX3fe++dmzLn7DgOwGWDGYZxHC8Xba0zxmitIWowBsVpmvr+1nOPgSzMs1JKNs00ebWh24C7bZXWxlr7tkFKiTiE4B8A2QvZcCEwSXDBGJMPcM4xBXsEREtZVRU2g4POJzLHSBdjPJ1OLy87xqp6AyUEZGtB5hILuKhrDh46/5JnUpLDj1wbA2N2u11RFPkh3+/3x+Op215ZliWlFOOqbSy+0zeZ0KI44j14J7RBJDZAKMSOo3XOwYj+G5e72zfy7H1KaV1XJDAjbYDJeZ5jJ6UEKpBCanjCgzz7u+/+CTCpbdv7/4PnSP2/8AdbrFgvP3/73AAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image36\",\n \"title\": \"image36\",\n \"src\": \"/static/6173875a132326703cdc682678095ee1/29f4e/image36.png\",\n \"srcSet\": [\"/static/6173875a132326703cdc682678095ee1/a2ead/image36.png 259w\", \"/static/6173875a132326703cdc682678095ee1/29f4e/image36.png 506w\"],\n \"sizes\": \"(max-width: 506px) 100vw, 506px\",\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(\"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\": \"936px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/ba4a50bffb2e4d73ba89147e9ccaab3c/6d2da/image37.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\": \"73.74517374517376%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAABnElEQVQoz32SbU+DMBDH+f6fQxMTv4FvTdxm1GzoBovIcEChLQ/lYdO1tPUKiU6H++cg7XG/u6M9K8FkG6H3EH3wjkvNOyWkPnTqjO0+heD8el5Y/tv7fOXNXzbRdovTJEnSMIoYK+uqqhgbtZKxQ1tfPWDLXbu3T+sXP1257qu7et2E2xhTQlCaZv+I0KwqsotpbKFkfWOj+0i7AZlNp7b97Pt+lhdxmtS1KX8qKP/RVJczZH3WXug9ik5Tgu8mk8Vi4TgOQkmIUB83orJk+5r1cEs2/ppzSSm1bXu5XIZhGMex43mE0lH+B9ZaK/MonBUPToBI3jbNwJTf6g9psL+wQZWCmCzLq6re7/e7XmYxrNt21zRgkPcU1lIq8ELnEDkkG/xaCM25eXcdGFzvCDxUDoJggCXsOxiIgxJCfUtDnv9huKS2bc2Wc0NKOVASFlJC0BmYYYzhF02HEDomIcTJafe5wUswLmkGp9JAA40RzMnxGwRhxWjb5sNvwbDnRwLPr8o4TRFCMLGYkLw4UVke7/LeYHgbll/M4i8GP0eJtxdNawAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image37\",\n \"title\": \"image37\",\n \"src\": \"/static/ba4a50bffb2e4d73ba89147e9ccaab3c/6d2da/image37.png\",\n \"srcSet\": [\"/static/ba4a50bffb2e4d73ba89147e9ccaab3c/a2ead/image37.png 259w\", \"/static/ba4a50bffb2e4d73ba89147e9ccaab3c/6b9fd/image37.png 518w\", \"/static/ba4a50bffb2e4d73ba89147e9ccaab3c/6d2da/image37.png 936w\"],\n \"sizes\": \"(max-width: 936px) 100vw, 936px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Check the design statistics (figure 20)\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"a. Click on the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Statistics\"), \" tab\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"b. Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Graph\"), \" to see a graph of the coverage ratio vs. the\\nnumber of test runs.\"))), mdx(\"p\", null, \"Figure 20. Checking the Combinatorial Design Statistics\"), 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/6a21335eacb86fe51cfa004efcbab56b/71e8d/image38.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\": \"25.86872586872587%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAFCAIAAADKYVtkAAAACXBIWXMAAAsTAAALEwEAmpwYAAABPElEQVQY0wExAc7+AFh0mDlchi1SgEBijERljkJkjDhchi9UgTBUgT9hi0FjjDVZhE5ulFh1mUdmjklokFp2mztdh0Zmj114mgCit9OWoq2hpqWkqqyhp6meo6eiqKmkqKqorK6boaSora+2u7ueo6Wqrq+ssbGkqam/xMOxtrWyuLnN0dEAvM/ltbm6x8O20c7Dyca7xMC2xsO429fL0s3Dv7uy0MzC39zPxMG2x8W6y8i9wr+139zQ1NDF0c7D7evgALjL4q+0t8C+s8rHv8C+tcG/t727s9jWzNDOxbu4scXDu8zKwMLAuMLAuMbEu768tN3c0tHPxtHQxufm3QC4y+Kwtbi/vLHDwbi7ubHGw7m7ubHJx77Ny8K+vLTBwLe+vLO9u7PFw7rKyL6/vbTb2c7U0sjc29Dn5dwyysuYJFRLWwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image38\",\n \"title\": \"image38\",\n \"src\": \"/static/6a21335eacb86fe51cfa004efcbab56b/e3189/image38.png\",\n \"srcSet\": [\"/static/6a21335eacb86fe51cfa004efcbab56b/a2ead/image38.png 259w\", \"/static/6a21335eacb86fe51cfa004efcbab56b/6b9fd/image38.png 518w\", \"/static/6a21335eacb86fe51cfa004efcbab56b/e3189/image38.png 1035w\", \"/static/6a21335eacb86fe51cfa004efcbab56b/71e8d/image38.png 1304w\"],\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(\"h2\", null, \"Example of a Combinatorial Design\"), mdx(\"p\", null, \"Suppose \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is testing an enterprise software system. There is a\\npass/fail deterministic response variable that indicates whether the\\noperator was able to successfully use the system under a specified\\ncondition defined by a combination of factor levels. There are six\\nthree-level categorical factors, so a full factorial requires \", \"[ 3 ^6^\\n=\\u2004729 ]\", \"{.math .inline} runs. The test team cannot afford that many runs,\\nso they use ACTS to investigate how a combinatorial design can reduce\\nthe size of the test. Table 3 shows the number of runs required for a\\ndesign of strength \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" , for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t = 1\"), \" to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"6\"), \" .\"), mdx(\"p\", null, \"Table 3. Number of Runs Required for Strength t\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Strength\"), mdx(\"th\", null, \"Number of Runs\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"1\"), mdx(\"td\", null, \"3\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"2\"), mdx(\"td\", null, \"15\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"3\"), mdx(\"td\", null, \"48\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"4\"), mdx(\"td\", null, \"140\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"5\"), mdx(\"td\", null, \"318\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"6\"), mdx(\"td\", null, \"729\")))), mdx(\"p\", null, \"Suppose the test team has resources for a test with 100 runs. Then if\\nthe test team wants 100% coverage of the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" -tuples, they should use\\nthe combinatorial design of strength 3 with 48 runs. However, since they\\nhave the budget to conduct a test twice that size, the test team\\nconsiders using a subset of the strength 4 design and accepting partial\\ncoverage of the 1215 possible 4\\u2011tuples. Checking the graph of the\\ncoverage ratio vs. the number of test runs (figure 20), the test team\\nlearns that using 100 runs from the strength four design will give\\napproximately 90% coverage of the 4-tuples; this is a very good design\\noption. For more information on combinatorial designs contact the Test\\nDesign and Analyses Division of A-2/9.\"), mdx(\"h1\", null, \"Demonstrations\"), mdx(\"p\", null, \"Demonstrations are the simplest of the problem identification test\\ndesigns. They are usually single events demonstrating that a system can\\nsuccessfully operate under a particular condition of interest (a single\\nfactor level or specific combination of levels). Demonstrations should\\nonly be used to supplement more statistically rigorous test designs, not\\nused as the primary test design. The test team should methodically\\nselect the factor levels for the demonstration test points using prior\\nknowledge from SMEs.\"), mdx(\"p\", null, \"It is unlikely that any meaningful inferential conclusions can be drawn\\nfrom demonstrations alone, as the principles of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" are rarely applied\\nto these runs. There is usually little to no replication of the factor\\nlevel being evaluated, so it is difficult to characterize the average\\nperformance of the response at the demo'd factor level. Also, for the\\nfactors that are not of interest in a demo run, there is a tendency for\\ntheir levels to be randomly selected during execution. Also, if there\\nare several factors with levels marked for demonstration, these levels\\nmay be combined into a single demo run. These practices add significant\\nambiguity concerning the attribution of system performance to the demo'd\\nfactor's level. If there are several demo runs in a test, it is a best\\npractice to fix the levels of the factors that are not of interest. This\\nallows the impact of the demo levels to be more easily determined in the\\nanalysis.\"), mdx(\"h1\", null, \"Cases\"), mdx(\"p\", null, \"Cases are like demonstrations but have several specific combinations of\\nfactors and levels that are intended to be examined together. Types of\\ncase designs include examining the worst or best case configuration of\\nthe factors and levels. The belief is that if a problem exists, it will\\nexhibit itself when the system is operated under the worst possible or\\nbest possible scenario. Sometimes a case design is executed for a\\nspecial-interest item or even political reasons. As with single\\ndemonstrations, it is unlikely the data recorded from these events can\\nbe statistically analyzed.\"), mdx(\"h1\", null, \"Observational Studies\"), mdx(\"p\", null, \"A pure observational study is a rigorous investigation of treatments and\\nthe effects they cause, but differs from a designed experiment (or test)\\nin that the investigator cannot control the assignment of factor levels\\n(treatments) to the items under test. Consequently, the analysis of the\\ntreatment effects must consider any possible bias due to confounded\\nfactors. When using statistics to draw inferences about a population, it\\nis commonly said, \\\"Correlation does not equal causation.\\\" This is\\nespecially important to remember when using an observational study to\\ndraw conclusions about the performance of a system. Since the test team\\ndoes not change factor level settings and then directly observe a\\nresponse, it is more difficult to attribute the change in a measure\\n(response variable) to the change of a particular factor's level. This\\ndifficulty is caused by the increased likelihood that nuisance factors\\nare strongly correlated with test factors in an observational study,\\nwhich prevents clear attribution of cause and effect between factors and\\nthe measures.\"), mdx(\"p\", null, \"During some \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" tests, it is impossible to control the test\\nconditions. However, there are combinations of factors and levels that\\nthe test team wants to see at some point during the test event. It is a\\nbest practice to create a test event matrix (TEM) for observational\\nstudies which includes all of the factor/level combinations that the\\ntest team desires to see. Then the goal of test planning is to maximize\\nthe probability that each level combination is observed a sufficient\\nnumber of times.\"), mdx(\"p\", null, \"For example, figure 21 shows a portion of the TEM for the notional New\\nAir Force Electronic Pay System (NAFEPS). NAFEPS will replace the Air\\nForce's legacy human resource (HR) software system. Factors in the test\\ninclude the HR business process, the user role executing the process\\n(e.g., HR specialist), the affected member's total force component\\n(e.g., Air Force Reserve), the affected member's classification (e.g.,\\nofficer), and the organization level at which the business process is\\nexecuted (e.g., base level).\"), mdx(\"p\", null, \"Figure 21. TEM for the New Air Force Electronic Pay System (NAFEPS)\"), 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\": \"585px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image39.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\": \"107.33590733590734%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACh0lEQVQ4y41UiXKiQBDl/79mN653zLEaYyWagBEMAZEZGBAEuUcE1G20UknlWPOqq6th5jE9r7thZthAmEgz9YkXRXmOdROThaoZ4IlpI90E001bIxY82o63XAWW4/t+wKkuo8xRo/bn6uqKF4SpIIRhGEVhHEfgD/ERxyAMAqD5nu8noT/VXAYTs1GvctwYtsKCe4DjuCuAu3Id9w2Os/K8kuyVZAHIZLG8vrwcDAbD4bB/0394eBQEgeM4WZbBQ8yyj0+Tp9EBGGNKKaSxoYlo+MwqiGeSrCK83e6KvMjzfLvdFkUBHmIIDq58f1za7Xbg9vu9skwYxwtenp9F8UXDGizvf4Bdyd3PHcq4fqjIM6BPeUGWFV0jeVb8lOyFCcgCWJgLgG0vAz/c/hdwJ/hCmTZUb9DvgxiQOdwty7LNZpMesP4GlK6LLJWsiEHErPz+1ev1CCGGYUAl4kOVwcO+9CvA6222mdkxY7veRaddotVutVqQdpIkUPMgCCA4QY7WG55jm41Gq9W8vLiAOvM8PxoOLcvO8+zLw9/IQZJOxlyjXut2u+ftdrVSqdZqlcqZ+CJB5U6Qw2QNDdWo1yHr8vxmk+U4lmVVhEC8E+SIpv3+TbVardcbve5fCEA8hPB3zA8np6P7u855p3Pehjvf3g4kSYIeBtlPCwZpL21L10k5Ra4LIkOdYfJAMLqmp8g01TXMjyd+EELTZ+U05Bghlh3DAKWvDfMe9F2pUkKwwE9Nw1g6jrVYeCvPti34NVCaHPvtgwF2RaYsY+htCrS5gtQ5wkhXFBWpWhjFMPHQZklCP1sIIiexaIbMreiMZGcou6XNXv3sNf5kd5JzPSH3U1J5MP8BGK6DK+VV5VoAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image39\",\n \"title\": \"image39\",\n \"src\": \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image39.png\",\n \"srcSet\": [\"/static/dce8b102f6f990edb7f2f403dd356157/a2ead/image39.png 259w\", \"/static/dce8b102f6f990edb7f2f403dd356157/6b9fd/image39.png 518w\", \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image39.png 585w\"],\n \"sizes\": \"(max-width: 585px) 100vw, 585px\",\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, \"During \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \", the system will be live and capable of altering real-world\\ndatabases. Without the \\\"sandbox\\\" environment of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \", the test team is\\nunable to direct users to process fictitious paperwork, such as\\nrecording disciplinary actions or retirements. Consequently, the test\\nteam can only observe users executing various HR business processes\\nduring the course of their normal duty.\"), mdx(\"p\", null, \"The TEM aids the test team in determining where and when to observe the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" in order to maximize the probability of observing the factor level\\ncombinations of interest. For example, the test team could choose to\\nsend a team to the Air Reserve Personnel Center (ARPC) at Buckley Air\\nForce Base, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Contracting Officer\"\n }, \"CO\"), \" to observe ARPC HR specialists processing retirement\\npaperwork. For business practices that peak in frequency at various\\ntimes of the year, the test teams will time the site visits accordingly.\"), mdx(\"p\", null, \"Another important question the test team must answer is how long to\\nobserve the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" in order to see all of the factor level combinations of\\ninterest. Some factor level combinations may be relatively rare, such as\\ndesign point 1. \\\"Record Disciplinary Actions\\\" against Regular Air Force\\ncadets. Fortunately there are some simple formulas that can be used for\\nplanning the duration of observational studies.\"), mdx(\"p\", null, \"If the factor level combinations of interest occur at a predictable rate\\nduring some period of time, but completely at random during the time\\nperiod, then the test event can be modeled as a Poisson Process. Poisson\\nprocesses are used to model situations like the arrivals of customers to\\na store, or the number of car accidents in a certain area. The important\\nassumptions are:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The events occur at a certain rate but completely at random within\\nan interval (e.g., on average, 5 customers arrive at a store per\\nhour; but when they arrive within the hour is completely random)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The number of events in some interval of length t is independent of\\nand identically distributed as the number of events in another\\n(disjoint) interval of length t (e.g., the average number of\\ncustomers arriving to the store between 0900 and 1000 is the same\\naverage number arriving between 1100 and 1200)\"))), mdx(\"p\", null, \"In the context of observational studies, the arrivals of interest are\\nthe rare factor level combinations. It suffices to focus on the\\nprobabilities of the rare factor level combinations, as the\\nprobabilities of observing the more common events will be greater and\\ntherefore are not limiting factors.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 1: Calculating the Time to Observe One Rare Event with\\nSpecified Probability.\"), \" Suppose we want to know the test time \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" that\\ngives a probability of 80% (p = 0.8) that the test team will observe a\\nrare factor level combination.\"), mdx(\"p\", null, \"The first step is to estimate the rate \", \"[ \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\u03BB\"), \" ]\", \"{.math .inline} of the\\naverage number of events per time period. Suppose a rare factor level\\ncombination occurs randomly 1 time every 3 working days (on average)\\nwhile a system is operating. Assuming an 8 hour work day, this is 1\\nevent every 24 working hours, implying \", \"[ \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\u03BB\"), \" ]\", \"{.math .inline} =\\xA00.042\\nevents per hour.\"), mdx(\"p\", null, \" \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\frac{\\\\mathbf{1}\\\\ \\\\mathbf{\\\\text{event}}}{\\\\mathbf{24}\\\\ \\\\mathbf{\\\\text{hours}}}\\\\overset{\\\\Rightarrow}{\\\\ }\\\\mathbf{\\\\lambda} = \\\\mathbf{0}.\\\\mathbf{042}\\\\ \\\\mathbf{\\\\text{events}}/\\\\mathbf{\\\\text{hour}}\"), \" \"), mdx(\"p\", null, \"Step 2 is to convert 80% into the decimal p = 0.8 and use the following\\nformula to calculate the test\\xA0time\\xA0t.\"), mdx(\"p\", null, \" \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\mathbf{t} = \\\\frac{- \\\\mathbf{\\\\ln}\\\\left( \\\\mathbf{1} - \\\\mathbf{p} \\\\right)}{\\\\mathbf{\\\\lambda}}\"), \" \"), mdx(\"p\", null, \" \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\mathbf{t} = \\\\frac{- \\\\mathbf{\\\\ln}\\\\left( \\\\mathbf{1} - \\\\mathbf{0}.\\\\mathbf{8} \\\\right)}{\\\\mathbf{0}.\\\\mathbf{042}} = \\\\mathbf{38}.\\\\mathbf{3}\\\\ \\\\mathbf{\\\\text{hours}}\"), \" \"), mdx(\"p\", null, \"The analysis shows that 38.3 test hours are required to have an 80%\\nchance of observing a factor level combination that occurs randomly 1\\ntime every 24 hours (on average.)\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 2: Calculating the Time to Observe \", mdx(\"em\", {\n parentName: \"strong\"\n }, \"k\"), \" Rare Events with\\nSpecified Probability.\"), \" Suppose we want to know the test time \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" that\\ngives us an 80% probability (p = 0.8) chance of observing k = 3\\noccurrences of a rare factor level combination that occurs randomly 1\\ntime every 3 working days (on average). We already calculated that \", \"[\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\u03BB\"), \" ]\", \"{.math .inline} =\\xA00.042 events per hour. In this example a more\\ncomplicated formula is required:\"), mdx(\"p\", null, \" \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\mathbf{1} - \\\\mathbf{p} = \\\\sum\\\\_{\\\\mathbf{n} = \\\\mathbf{0}}^{\\\\mathbf{k} - \\\\mathbf{1}}{\\\\frac{\\\\mathbf{1}}{\\\\mathbf{n}!}\\\\mathbf{e}^{- \\\\mathbf{\\\\lambda}\\\\mathbf{t}}\\\\left( \\\\mathbf{\\\\lambda}\\\\mathbf{t} \\\\right)^{\\\\mathbf{n}}}\"), \" \"), mdx(\"p\", null, \"Plugging in the values we know (p = 0.8, k = 3, \", \"[ \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\u03BB\"), \" ]\", \"{.math .inline}\\n=\\xA00.042) we have\"), mdx(\"p\", null, \" \", mdx(\"span\", {\n parentName: \"p\",\n \"className\": \"inlineMath\"\n }, \"\\\\mathbf{0}.\\\\mathbf{20} = \\\\mathbf{e}^{- \\\\mathbf{0}.\\\\mathbf{042}\\\\mathbf{t}} + \\\\mathbf{e}^{- \\\\mathbf{0}.\\\\mathbf{042}\\\\mathbf{t}}\\\\left( \\\\mathbf{0}.\\\\mathbf{042}\\\\mathbf{t} \\\\right) + \\\\frac{\\\\mathbf{1}}{\\\\mathbf{2}}\\\\mathbf{e}^{- \\\\mathbf{0}.\\\\mathbf{042}\\\\mathbf{t}}\\\\left( \\\\mathbf{0}.\\\\mathbf{042}\\\\mathbf{t} \\\\right)^{\\\\mathbf{2}}\"), \" \"), mdx(\"p\", null, \"A simple way to solve this equation for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" is to use Excel's solver\\nfunction to find the value for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" that minimizes the difference between\\nthe equation's right hand side and the left hand side (0.2 in this\\nexample.) The solver reports that \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" =\\xA071.3 hours. This means we must\\nobserve the system 71.3 hours in order to have an 80% chance of seeing 3\\noccurrences of a rare factor level combination that occurs 1 time every\\n3 working days (on average.)\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 3: Calculating the Probability of Observing a Rare Event with\\nSpecified Time.\"), \" Suppose the resource constraints have imposed a limit\\nof 4 working days (32 hours) for the observational study. Given a fixed\\ntest time \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" = 32 hours, we want to determine the probability of\\nobserving a rare factor level combination that occurs randomly 1 time\\nevery 3 working days. In other words, if \", \"[ \", mdx(\"em\", {\n parentName: \"p\"\n }, \"T\"), \" ~1~ ]\", \"{.math .inline} is\\nthe time of the first occurrence of the rare event, then we want the\\nprobability that \", \"[ \", mdx(\"em\", {\n parentName: \"p\"\n }, \"T\"), \" ~1~ ]\", \"{.math .inline} is less than \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" : P \", \"[ ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"T\"), \"\\n~1~ \\\\< \", mdx(\"em\", {\n parentName: \"p\"\n }, \"t\"), \" ) ]\", \"{.math .inline} . Recall that \", \"[ \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\u03BB\"), \" ]\", \"{.math .inline}\\n=\\xA00.042 events per hour. The formula to use is:\"), mdx(\"pre\", null, mdx(\"code\", {\n parentName: \"pre\"\n }, \"**P** ( **T** **1** **<** **t** ) **=** **1** **\\u2212** **e** **\\u2212** (\\u03BBt) \\n\\n**P** ( **T** **1** **<** **32** ) **=** **1** **\\u2212** **e** **\\u2212** **(** **0.042** **)** **(** **32** **)** **=** **0.74** \\n\")), mdx(\"p\", null, \"Therefore we have a 74% chance of seeing the rare event during the 32\\nhour test.\"), mdx(\"p\", null, \"In summary, the three formulas in Examples 1-3 provide probability\\nassessments that can be used to plan the duration of observational\\nstudies, as well as characterize the risk of not observing important\\nfactor level combinations.\"), mdx(\"p\", null, \"An observational study should only be used when it is impossible to\\ncontrol the factor levels. They must have sufficient documentation to\\nprove the test team will gather the appropriate data to answer all of\\nthe desired questions. While an observational study is not the ideal\\ntest scenario, with proper planning these tests can provide data to\\ncharacterize the performance of the system. For more information on the\\nuse of an observational study for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test program, and the theory\\nbehind the use of Poisson Process modeling, please contact the Test\\nDesign and Analyses Division of A-2/9.\"), mdx(\"h1\", null, \"TEST DESIGN MEASURES OF MERIT\"), mdx(\"p\", null, \"All test designs have associated measures of merit, or quality\\nindicators, which should be considered when deciding on a test design.\\nTest design measures of merit include power, optimality efficiency,\\ncorrelation, prediction variance, resolution, strength, and coverage.\\nThe most commonly encountered and generally applicable test design\\nmeasures of merit are presented in this section. Note that some measures\\nof merit which pertain to specific design types (like strength and\\ncoverage for combinatorial designs) are discussed in the sections of\\nthis guide corresponding to the relevant designs.\"), mdx(\"h1\", null, \"Power\"), mdx(\"p\", null, \"In a hypothesis test, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"power\"), \" is a measure of the probability the null\\nhypothesis will be correctly rejected when it is false. In the context\\nof statistical modeling, the null hypothesis is that a factor is not\\nactive (has no effect on the response); therefore in that context power\\nrefers to the probability the test data will correctly identify a factor\\nas active. Power is a function of the test design, significance level,\\nsignal (e.g., difference in the response between factor levels), and\\nnoise (natural variation in the measure for a given test run.)\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" calculates power over a range of signal to noise ratios (SNR) at\\na significance level of \", \"[ \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u03B1\"), \" =\\u20040.2 ]\", \"{.math .inline} . SNR refers to the\\nratio of the minimum desired detectable difference, delta (\\u03B4), and the\\nstandard deviation of the response values at a given design point, sigma\\n(\\u03C3). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" typically evaluates power for 0\\xA0\\\\<\\xA0\\u03B4/\\u03C3\\xA0\\\\<\\xA0 3.5; the range of\\ninterest for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" is usually between 1\\xA0\\\\<\\xA0\\u03B4/\\u03C3\\xA0\\\\<\\xA02. Rather\\nthan using a SNR, power can also be calculated by using SMEs,\\nrequirements documents, and previous system data (from a legacy system\\nor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \") to identify appropriate values for \\u03B4 and \\u03C3.\"), mdx(\"p\", null, \"A rule of thumb is to employ designs with a minimum power of 80% for\\neffects of interest. Power analysis for a designed experiment requires\\nthe following information:\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The test design matrix metadata (which includes the number of\\nfactors, levels for each factor, and sample size)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The proposed statistical model\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The significant level (\\u03B1)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The desired detectable change in the response (\\u03B4)\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The standard deviation of the response value at a given design point\\n(\\u03C3); the assumption for power analysis is that \\u03C3 is the same at all\\ndesign points.\"))), mdx(\"p\", null, \"List items 4 and 5 can be combined into a SNR value.\"), mdx(\"p\", null, \"Power calculations for binary response variables are different than\\nthose for continuous response variables. More information on calculating\\npower for binomial response variables can be found here:\"), mdx(\"p\", null, mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdf\"\n }, \"http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdf\"), \"\\n. (Ortiz, 2014)\"), mdx(\"p\", null, \"For guidance on creating power curves or power calculations in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nrefer to the November 2014 guide, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Power Analysis Tutorial for\\nExperimental Design Software,\"), \" which can be found on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nSharePoint in the Analyst and Engineer Community. Contact the Test\\nDesign and Analyses Division of A-2/9 for assistance creating or\\ninterpreting power curves.\"), mdx(\"h1\", null, \"Optimality (Efficiency)\"), mdx(\"p\", null, \"An important measure of merit for optimal designs is the optimality\\nefficiency. The optimality relates to the criteria used to determine the\\n\\\"best\\\" design during execution of the design construction algorithm. JMP\\ncalculates efficiencies for the D \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn34\"\n }, \"34\"), \", G \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn35\"\n }, \"35\"), \" and A \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn36\"\n }, \"36\"), \" optimality criteria, which were discussed in the Optimal Designs section of this guide. The efficiencies are\\nthe ratio of the optimality criterion value of the evaluated design to\\nthe optimal value of an ideal (perhaps unobtainable) design of the same\\ndimensions. When JMP constructs a computer generated design, it reports\\nthe D, G, and A efficiencies under the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Design Diagnostics\"), \" header under\\n\\\" \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Design Evaluation\"), \" \\\" (figure 22).\"), mdx(\"p\", null, \"Figure 22. Optimality Efficiencies under Design Diagnostics\"), 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\": \"585px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image40.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\": \"107.33590733590734%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACh0lEQVQ4y41UiXKiQBDl/79mN653zLEaYyWagBEMAZEZGBAEuUcE1G20UknlWPOqq6th5jE9r7thZthAmEgz9YkXRXmOdROThaoZ4IlpI90E001bIxY82o63XAWW4/t+wKkuo8xRo/bn6uqKF4SpIIRhGEVhHEfgD/ERxyAMAqD5nu8noT/VXAYTs1GvctwYtsKCe4DjuCuAu3Id9w2Os/K8kuyVZAHIZLG8vrwcDAbD4bB/0394eBQEgeM4WZbBQ8yyj0+Tp9EBGGNKKaSxoYlo+MwqiGeSrCK83e6KvMjzfLvdFkUBHmIIDq58f1za7Xbg9vu9skwYxwtenp9F8UXDGizvf4Bdyd3PHcq4fqjIM6BPeUGWFV0jeVb8lOyFCcgCWJgLgG0vAz/c/hdwJ/hCmTZUb9DvgxiQOdwty7LNZpMesP4GlK6LLJWsiEHErPz+1ev1CCGGYUAl4kOVwcO+9CvA6222mdkxY7veRaddotVutVqQdpIkUPMgCCA4QY7WG55jm41Gq9W8vLiAOvM8PxoOLcvO8+zLw9/IQZJOxlyjXut2u+ftdrVSqdZqlcqZ+CJB5U6Qw2QNDdWo1yHr8vxmk+U4lmVVhEC8E+SIpv3+TbVardcbve5fCEA8hPB3zA8np6P7u855p3Pehjvf3g4kSYIeBtlPCwZpL21L10k5Ra4LIkOdYfJAMLqmp8g01TXMjyd+EELTZ+U05Bghlh3DAKWvDfMe9F2pUkKwwE9Nw1g6jrVYeCvPti34NVCaHPvtgwF2RaYsY+htCrS5gtQ5wkhXFBWpWhjFMPHQZklCP1sIIiexaIbMreiMZGcou6XNXv3sNf5kd5JzPSH3U1J5MP8BGK6DK+VV5VoAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image40\",\n \"title\": \"image40\",\n \"src\": \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image40.png\",\n \"srcSet\": [\"/static/dce8b102f6f990edb7f2f403dd356157/a2ead/image40.png 259w\", \"/static/dce8b102f6f990edb7f2f403dd356157/6b9fd/image40.png 518w\", \"/static/dce8b102f6f990edb7f2f403dd356157/78a22/image40.png 585w\"],\n \"sizes\": \"(max-width: 585px) 100vw, 585px\",\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 efficiency values will range from 0-100% with 100% being the best.\\nFor more information, please consult the JMP documentation or contact\\nthe Test Design and Analyses Division of A-2/9. \"), mdx(\"h1\", null, \"Correlation (Multicollinearity)\"), mdx(\"p\", null, \"Correlation between two factors is a statistical measure that indicates\\nthe extent to which the levels of those factors vary together. A\\npositive correlation indicates that factors increase or decrease in\\nparallel; a negative correlation indicates that one factor increases as\\nthe other decreases.\"), mdx(\"p\", null, \"It is undesirable to have correlated factors in a test design. First,\\nwhen two active factors are perfectly correlated, it is not possible to\\nquantify the independent effect of each factor on the response. Second,\\ncorrelated factors increase the variance of the estimates of the\\nstatistical model parameters and the estimates of the mean response\\nvalue.\"), mdx(\"p\", null, \"Bias due to multicollinearity can be unintentionally introduced when\\ninfluential and controllable factors that are not of interest\\noperationally are allowed to vary randomly during the test event. This\\nsituation may occur when the test team decides to exclude medium impact\\nfactors from the list of varied factors in order to prevent the design\\nfrom becoming too large, or to prevent the test from having low power.\\nIt is poor practice to label these excluded factors as \\\"logged\\\" factors,\\nas the chances of biased data becomes far more likely. Instead, include\\nthese factors in an \\\"off-line\\\" test design (that will be used for test\\nexecution) if you think post-test analysis might possibly involve them.\\nThese factors can be omitted from the reported design for the purposes\\nof calculating measures of merit like power.\"), mdx(\"p\", null, \"A correlation matrix shows the linear relationship between any pair of\\nfactors. If any of the values in the correlation matrix is above 0.5,\\nthe design should be adjusted if possible to reduce the correlation. JMP\\nwill produce a \\\"Color Map on Correlations\\\" in the \\\"Design Diagnostics\\\"\\ntab. Figure 23 shows two \\\"Color Map on Correlations\\\" plots from JMP.\"), mdx(\"p\", null, \"Figure 23. Examples of Color Maps\"), 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\": \"425px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image41.jpg\",\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\": \"118.53281853281852%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/jpeg;base64,/9j/2wBDABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVGC8aGi9jQjhCY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2P/wgARCAAYABQDASIAAhEBAxEB/8QAGAABAQEBAQAAAAAAAAAAAAAAAAUBAwT/xAAXAQADAQAAAAAAAAAAAAAAAAABAwQC/9oADAMBAAIQAxAAAAGvkXHi+4Emd5S3FoRM/8QAHhAAAQQBBQAAAAAAAAAAAAAAAwABAhEzBBAhIjL/2gAIAQEAAQUC6WztsSNmuKDjLxPytPg//8QAGBEAAwEBAAAAAAAAAAAAAAAAAAEREFH/2gAIAQMBAT8BfcsY1HD/xAAZEQADAQEBAAAAAAAAAAAAAAAAARECQQP/2gAIAQIBAT8BXlzo1DCuRuun/8QAHRAAAgEEAwAAAAAAAAAAAAAAAAECECExcRFhsf/aAAgBAQAGPwLKLNUnssLnJLZ34RP/xAAfEAEAAgAGAwAAAAAAAAAAAAABABEhMUFRYZEQcaH/2gAIAQEAAT8hWy+8lP4mCVmRKhriGDy2wXiY0BunrlN63x4w6Z//2gAMAwEAAgADAAAAEF8AfP/EABkRAAMAAwAAAAAAAAAAAAAAAAABERAxQf/aAAgBAwEBPxBoo1hMFhOH/8QAGREBAQEAAwAAAAAAAAAAAAAAAQARMUHw/9oACAECAQE/EBeU0JAW+yRF3f/EAB0QAQACAgMBAQAAAAAAAAAAAAEAESExQVFhkfD/2gAIAQEAAT8QMBW8iSMVRPgyize3M39I/ZS4mQmh2e+bhbSOHc22CPY2RpX3+bhCACpfcs//2Q==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image41\",\n \"title\": \"image41\",\n \"src\": \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image41.jpg\",\n \"srcSet\": [\"/static/70c09ba0146ea8fcde79f75b00b8fde7/8356d/image41.jpg 259w\", \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image41.jpg 425w\"],\n \"sizes\": \"(max-width: 425px) 100vw, 425px\",\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(\"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\": \"425px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image42.jpg\",\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\": \"118.53281853281852%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/jpeg;base64,/9j/2wBDABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVGC8aGi9jQjhCY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2P/wgARCAAYABQDASIAAhEBAxEB/8QAGAABAQEBAQAAAAAAAAAAAAAAAAUBAwT/xAAXAQADAQAAAAAAAAAAAAAAAAABAwQC/9oADAMBAAIQAxAAAAGvkXHi+4Emd5S3FoRM/8QAHhAAAQQBBQAAAAAAAAAAAAAAAwABAhEzBBAhIjL/2gAIAQEAAQUC6WztsSNmuKDjLxPytPg//8QAGBEAAwEBAAAAAAAAAAAAAAAAAAEREFH/2gAIAQMBAT8BfcsY1HD/xAAZEQADAQEBAAAAAAAAAAAAAAAAARECQQP/2gAIAQIBAT8BXlzo1DCuRuun/8QAHRAAAgEEAwAAAAAAAAAAAAAAAAECECExcRFhsf/aAAgBAQAGPwLKLNUnssLnJLZ34RP/xAAfEAEAAgAGAwAAAAAAAAAAAAABABEhMUFRYZEQcaH/2gAIAQEAAT8hWy+8lP4mCVmRKhriGDy2wXiY0BunrlN63x4w6Z//2gAMAwEAAgADAAAAEF8AfP/EABkRAAMAAwAAAAAAAAAAAAAAAAABERAxQf/aAAgBAwEBPxBoo1hMFhOH/8QAGREBAQEAAwAAAAAAAAAAAAAAAQARMUHw/9oACAECAQE/EBeU0JAW+yRF3f/EAB0QAQACAgMBAQAAAAAAAAAAAAEAESExQVFhkfD/2gAIAQEAAT8QMBW8iSMVRPgyize3M39I/ZS4mQmh2e+bhbSOHc22CPY2RpX3+bhCACpfcs//2Q==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image42\",\n \"title\": \"image42\",\n \"src\": \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image42.jpg\",\n \"srcSet\": [\"/static/70c09ba0146ea8fcde79f75b00b8fde7/8356d/image42.jpg 259w\", \"/static/70c09ba0146ea8fcde79f75b00b8fde7/b9721/image42.jpg 425w\"],\n \"sizes\": \"(max-width: 425px) 100vw, 425px\",\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 horizontal labels across the top are the main effects and the\\n2-factor interactions. The labels on the vertical axis are not shown but\\nare the same as the horizontal axis. The scale on the right indicates\\nthe amount of pair-wise correlation. Royal blue indicates no correlation\\nand red indicates perfect correlation. The plot on the left is the\\noptimal, and depicts no correlation between any of the factors or their\\n2-factor interactions (the red diagonal is the correlation of each\\nfactor with itself and therefore shows red for perfect correlation.)\"), mdx(\"p\", null, \"The color map on the right shows a plot with some partial correlation\\nbetween the main effects and one or more 2-factor interactions, as\\nindicated by the grey color. The upper left 4x4 portion of the map (in\\nthe black square) shows us that no main effect is correlated with any\\nother main effect. If a completely blue map (apart from the diagonal)\\ncannot be achieved, attempt to make the correlation between main effects\\nas small as possible. \"), mdx(\"h1\", null, \"Prediction Variance\"), mdx(\"p\", null, \"Prediction variance is a test design measure of merit which provides\\ninformation regarding the variability in the estimate of the response\\nvariable at a particular point in the design space. It essentially\\nquantifies how precise the model is in estimating the true average\\nresponse. If the prediction variance is large, the true average response\\nvalue may be quite different from the model's estimate.\"), mdx(\"p\", null, \"Prediction variance is a function of both natural system variation ( \", \"[\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u03C3\"), \" ^2^ ) ]\", \"{.math .inline} and the structure of the experimental design.\\nRelative prediction variance considers only the experimental design's\\ninfluence on the prediction variance (independent of natural system\\nvariation). Although we do not usually create predictive statistical\\nmodels at \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", this metric can still be useful because the predictive\\nvariance is indicative of the design quality.\"), mdx(\"p\", null, \"JMP provides graphical tools that are useful for assessing the\\nprediction variance of a test design. They are the \\\" \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Prediction\\nVariance Profiler\"), \" \\\" (2D and 3D) and the \\\" \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Fraction of the Design\\nSpace\"), \" \\\" (FDS) plot.\"), mdx(\"p\", null, \"Figure 24. Example of JMP\\\\'s 2D Prediction Variance Profiler\"), 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\": \"501px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/c98d5250b1fb3e6f9f7d182add9ecc15/55811/image43.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,iVBORw0KGgoAAAANSUhEUgAAABQAAAAKCAYAAAC0VX7mAAAACXBIWXMAAA7DAAAOwwHHb6hkAAABTUlEQVQoz21SCXKDMAzk/59MSUNCpk0awId8YFUrbJIemhGypdW1puNSGLKuK4cQOMW4aUqqRMQR/nqHRonDr/fwxCO/W3mTeZrVwas0qE0gABbR35JzVltgKx7YjsYPZikWKXCQTq0gpkgCzihYk5tQqNhttd2PnC5TUOfj8WDyxEVWsPPMzhgtlCTZL0atFWuXhck6iVs9A6tW1DvHXaturWEjoIzuwk+u05HzbKZJKSHvJbbxjDN49NZWP20clpdHgdxuNx0dD3G/37Wwd1uCleQF04g1skE7w2JDXVmJlaKt8HUcmVAwJ76cz9zi8tWmDQvFfYUVRWP49gmb1ZcWHjM4En2N/Ssp4zW4Ap8ctqQYZdW3I5fPrx9+J4SPx5Ou9fpLXft3jtOyY/8UDIH4NAw8DBclvYlZZj4c3pSz/TeRbfq+58t4VUog374sEE46rUhmAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image43\",\n \"title\": \"image43\",\n \"src\": \"/static/c98d5250b1fb3e6f9f7d182add9ecc15/55811/image43.png\",\n \"srcSet\": [\"/static/c98d5250b1fb3e6f9f7d182add9ecc15/a2ead/image43.png 259w\", \"/static/c98d5250b1fb3e6f9f7d182add9ecc15/55811/image43.png 501w\"],\n \"sizes\": \"(max-width: 501px) 100vw, 501px\",\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 prediction variance profiler (figure 24) in JMP plots the relative\\nvariance of prediction as a function of each factor level. These plots\\ncan be used to identify combination of factor levels with high\\nprediction variance. It is ideal for the prediction variance to be small\\nthroughout the design region. Generally, the prediction variance drops\\nas the sample size increases.\"), mdx(\"p\", null, \"A fraction of the design space (FDS) plot (figure 25) may be created in\\nJMP to show what proportion of the design space has prediction variance\\nat or below a given level.\"), mdx(\"p\", null, \"Figure 25. Fraction of Design Space Plot\"), 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/b410856306118d0933a88a9dbc9445b6/8b46b/image44.jpg\",\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\": \"73.35907335907336%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/jpeg;base64,/9j/2wBDABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVGC8aGi9jQjhCY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2P/wgARCAAPABQDASIAAhEBAxEB/8QAFgABAQEAAAAAAAAAAAAAAAAAAAEF/8QAFAEBAAAAAAAAAAAAAAAAAAAAAP/aAAwDAQACEAMQAAAB3aAH/8QAFRABAQAAAAAAAAAAAAAAAAAAASD/2gAIAQEAAQUCK//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQMBAT8BP//EABQRAQAAAAAAAAAAAAAAAAAAABD/2gAIAQIBAT8BP//EABQQAQAAAAAAAAAAAAAAAAAAACD/2gAIAQEABj8CX//EABkQAQADAQEAAAAAAAAAAAAAAAEAESEQMf/aAAgBAQABPyHSyuAiy98mz//aAAwDAQACAAMAAAAQQM//xAAUEQEAAAAAAAAAAAAAAAAAAAAQ/9oACAEDAQE/ED//xAAUEQEAAAAAAAAAAAAAAAAAAAAQ/9oACAECAQE/ED//xAAbEAADAQEAAwAAAAAAAAAAAAAAARExIVFxof/aAAgBAQABPxBLPMJr0iTcIAlHnRPxr2Ss+n//2Q==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image44\",\n \"title\": \"image44\",\n \"src\": \"/static/b410856306118d0933a88a9dbc9445b6/af659/image44.jpg\",\n \"srcSet\": [\"/static/b410856306118d0933a88a9dbc9445b6/8356d/image44.jpg 259w\", \"/static/b410856306118d0933a88a9dbc9445b6/bc760/image44.jpg 518w\", \"/static/b410856306118d0933a88a9dbc9445b6/af659/image44.jpg 1035w\", \"/static/b410856306118d0933a88a9dbc9445b6/8b46b/image44.jpg 1330w\"],\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 figure shows that 50% of the design region has a relative prediction\\nvariance below 0.039. The \\\"flatness\\\" of the plot is an indication of the\\nprediction variance stability; i.e., the prediction variance does not\\nsignificantly increase in some portion of the design region. Comparing\\nthe FDS plot for two designs side-by-side is one way to compare two\\ndesigns; the preferred design is the one with lower prediction variance\\non average throughout the design space.\"), mdx(\"h1\", null, \"Comparing Measures of Merit\"), mdx(\"p\", null, \"JMP has created the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Compare Designs\"), \" platform to provide a convenient\\nway to compare two or three designs.\"), mdx(\"p\", null, \"Comparing Designs in JMP\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"From the menu above one of the design tables, launch the platform by\\nselecting \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \"\"), \" , then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Design Diagnostics\"), \" , then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Compare\\nDesigns\"), \" (figure 26a).\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Compare Reference Design With\"), \" box, select the\\nother designs to be compared (figure 26b).\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 26a. Comparing Designs in JMP Figure 26b. Choosing Designs to Compare\\n\", 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\": \"640px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/53bcebe7d11ca1ec4310fd2bf86936ac/6af66/image45.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\": \"67.56756756756756%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAAB/ElEQVQoz32SWY+bMBDH+f5fo+9VVamvfVlp092w2SXJFsqVcGNzmcMXgdAhJI16qKMfI8vM357DShBFYYwOXuSHcZTgnDRU9HXL6o41ABV1xxs6A4uqoUBO2r6XDzZRHMe1TMswLMt2jkfPMk3bNH3fzzDGaTp7hGCR5xlKkhQsSSpSn3v+aJdK4rt5Eqahh4IDBo8g5hpEKRNCcM7B4ywndSv72biQ0yBXh1r5vA4/PQUfV/6XffvVaLquK7Js+/a22byqqhqEUVmWeZH/cIPVyx7lREpJGZ/Fbq28o9HAo46Gl/i8jU8d5yTyzaeVZbmGbjRtO01THMee7+/3+6Io4GbGb+LpLK9MchxFx3iLUaC/RynuJeyMwzCAJgxDXderqoSb72IorKNs8QBUSAhx3YPruqZlYZxB2lVVQTlt2zI2d4FxcRVLKe4GvelPdRob62fDMLfarqoI5AkthEPlLfR/4g4l7kY9+lFZlKCEzGEEy51/ii+z4Ms8wOD4HKOj43ieDyOGEiilTdP8CvhNPAynxZaRghiS1DRtp2nb7a5umjmasX+L0fwgIC88dwv0cyiHCTXwQYc4p4wBy68FysV5kI8g7uqqq0lLql7yoRcz8uJ7eUH8DbRpGsXzsVZeD9XGnVGd4opdrG/cN2+s7fzhe6oa8YdvyU+KeAk+5cBw8QAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image45\",\n \"title\": \"image45\",\n \"src\": \"/static/53bcebe7d11ca1ec4310fd2bf86936ac/6af66/image45.png\",\n \"srcSet\": [\"/static/53bcebe7d11ca1ec4310fd2bf86936ac/a2ead/image45.png 259w\", \"/static/53bcebe7d11ca1ec4310fd2bf86936ac/6b9fd/image45.png 518w\", \"/static/53bcebe7d11ca1ec4310fd2bf86936ac/6af66/image45.png 640w\"],\n \"sizes\": \"(max-width: 640px) 100vw, 640px\",\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(\"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\": \"640px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/78f05b64bb96fe33d158c4505e324d22/6af66/image46.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\": \"67.56756756756756%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAIAAACgpqunAAAACXBIWXMAAAsTAAALEwEAmpwYAAACJ0lEQVQoz31S30/bMBDO//+4x2nStpe9TUWwCYk9rAhWNNq0FApJmzRt0vyy4zRJHcdnp03mjlFAmjh9Op/O33e+s62tgsAP0cINPD8MIkzyDQNZ0Kooq40Cg6LkG7aHCrINUyA5lVJc2Lk2ny+smW2almU7y6VrzWb2bOZ5XoIxjuO9R0gFhCQoimJlUZTlRSP4uYm1yJuTaBX7S7RysPJIcf6RGKsAgHOuPE5IXlAh98ZBNBKOf1vaySg51lGnH383RNeCkrE0Se7Ho7ub4Y3ej0O/LNZpSqbO6kqfIJILARWHpoaj3lS7T9opaU3SDuP2Dm0pBxa6nbPxu+76/Tn+ctt80BtjEQa+N5lM0jQVQuzFEo6uplrbQLsTezSw2/KyqihGy4eHRZgwLrlsKN8mJA183zCMLFu/EqvBSlY9egU1oboP33Ui13bnJl0jWa6LPKO0pJRW1eMtPInVDM+m0rLexP63s+uPP51PP8yT27wz3thuIIGLJ+pbYobCQU+/NBIzZHbajAOxCmPg1UvW/8QAqjzBOFraOHAzgniZt3VVlrT6+2BvifcHS+EH4aV+29PHw9FNFOMYIUIIvO5PiTu/TA0EqJoHKMso+9odnPWNpesFofowKEmSlxzGYVfD6cjV1LKVz6glQFXiYEXicCtFu63bZqeSteAHjmq23cGVnWq6kw7mr2Gnw0U+cLK+Tfp22rfItUUOuyp58RAPzPBzL/gDYqoAw9U+fDIAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image46\",\n \"title\": \"image46\",\n \"src\": \"/static/78f05b64bb96fe33d158c4505e324d22/6af66/image46.png\",\n \"srcSet\": [\"/static/78f05b64bb96fe33d158c4505e324d22/a2ead/image46.png 259w\", \"/static/78f05b64bb96fe33d158c4505e324d22/6b9fd/image46.png 518w\", \"/static/78f05b64bb96fe33d158c4505e324d22/6af66/image46.png 640w\"],\n \"sizes\": \"(max-width: 640px) 100vw, 640px\",\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(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Matching Specification\"), \" Box, you can specify which columns\\nare equivalent (matched) in the two designs. Click the gray triangle\\nto reveal the Match button. Highlight a factor in each design and\\nclick \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Match\"), \" .\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"OK\"), \" in the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Action\"), \" box (figure 27a).\")), mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Measures of Merit for all of the designs such as power (figure 27b),\\nprediction variance, FDS plots, and optimality efficiencies are\\nprovided in the output.\"), mdx(\"p\", {\n parentName: \"li\"\n }, \"Figure 27a. Matching Columns of Multiple Designs Figure 27b. Comparing Power of Two Designs\\n\", 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\": \"534px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/90235aadeb4b6aaca7825a8b91ad266a/a07a7/image47.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\": \"108.1081081081081%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAWCAYAAADAQbwGAAAACXBIWXMAAA7DAAAOwwHHb6hkAAADKUlEQVQ4y4WU+U8TQRTH+//6g8Yj8TYe8cB4RCK/GC+qSESM/mC8wKAi7S69D4sIFltoaSlld9tt95r5+ma2RYQuTvLy9r2d+cz3vZ2d0MJCAfPzKqKRCMqrq+h0OjAMA61Wa7AZvjekb0PX9W3TyEKe51GgodlsotVuo2OaMP9nbRNdq03zNTDG0R+cc4T6QVox4JguaqsuKssuZVw4jgvX3W0ePK+D3Pc2pmc2YOh11GobWK9U4dD7EEHhMhuRaR1gQH0VqPzs74iBw4ONasbB8oyFTa2KyloV5VJZCpBAThNm3ukoRDmibxjmXjKBkyXsNjG6HUtCB40QZ1ILPr5oIXya4fFVhofnGJxNf7HoUR9ET9LbjgXLskViz4Yh12WwXANvx5t4epaA1xgenWfwGhy6w1Fd8CHraxxei2qh9q79tOB69vaH+Efh1pYOl5uYed0lhR5GhxjunWHgJkdjnePLpL8g8o42KPnPn8a7sLQAIPM4fRSTFG7hCYGeXGe4dYxBec2hjjM8oBZ8e8Xx6jbD7ASD+hkYG+qiW+8BGR/UQ2BK9tCTwOGTDPcPMDy76Pf05hHq60E/HjnFqSVd2M0AhQLIYeH9cw3hnkIBHCXIxBW/p3dPkT/M8ILa8fAKx+MLBNwMUMiYf7I+TBgYpYVhWnTnOH2YQwzPL5MnhcMnejFtcP9ST+H+QIaply08peMydoMU0fEJHyVFpC5Mikd68eR1X2H40j4ly3NlW1j6UUF8bhmZ+G/EIr+Qiq4gpRaRFnG0iPjsMtLzK0iSpWO/4VhOQA97ifrGOmJxBbl8mnwUc5GviCdU5L9nEFVmEUso8r3ICbNte3+guJISiSRSqTSKRVKSTNG1No9sJotIJApVUWUunc4gHk/8H+g4DsFSWFpakpMWFxdlnEwmkclkoCgKbZiQuWw2K+cHAvtJcbnWajX6fxlyuZyEFQoFxGIxqKq6DRP5QIWDkgKYz+clRIAFtK9OxPV6/e+FEVTyTqU7geVyWeZKpRL1tohGowFxyw+C7VG404uyhKL+0DTtnzIDFe4Mdk/qdExsafqedgTBxPgDxExk2xIaiz0AAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image47\",\n \"title\": \"image47\",\n \"src\": \"/static/90235aadeb4b6aaca7825a8b91ad266a/a07a7/image47.png\",\n \"srcSet\": [\"/static/90235aadeb4b6aaca7825a8b91ad266a/a2ead/image47.png 259w\", \"/static/90235aadeb4b6aaca7825a8b91ad266a/6b9fd/image47.png 518w\", \"/static/90235aadeb4b6aaca7825a8b91ad266a/a07a7/image47.png 534w\"],\n \"sizes\": \"(max-width: 534px) 100vw, 534px\",\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(\"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\": \"719px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/00cdf102bdd871862309b280e962ac41/073e9/image48.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\": \"107.33590733590734%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACqklEQVQ4y4VUa1fiMBDt//9D60ddVveoCFQQBdpC36RJ09ImbQGBvUlE2eM5u/eEMJ10HncyUysMEs6LPC8Y4zkvNpu6qsSmwq6EqhYQ6lrqRwiiaTohGrVkY608r//4cHt72+/3syxjjGaUZgpUI9NKpp61qriAlcTR1dWP+/t7SllZIvJfqKoKe1mW6qFUwiWsjJDr6+tn+3k6nb6+vnqu6/sBBxMNYyaEUBkLIaU0gtFYOA4CX9GSsm3bKIpse1xtKghJksZxRBkzBjzP03QNodJQkZENeJ5Op+PxiB0uxuOXrmk5zxEpieM1IaAaRzHc+b4fx3GaptAQQlTaT/0+cnZdbz6feZ6HMF3XIQvsTdPIRkGoOjfQmOSVXkoLxAZPA9u2Z7PZZDwJggApdRrG3mCr8fF3hgVPSGP+NvNXvud4KBiI7fd7nO00IGNvz+guYKVpcnNz4zgO+CAsiIVhGMUKQRhCs1ouIZubQ5GQ7Zcx2mo4GIxGtuu4IOyvFGBjj0YPD4/QOAsH7gxJw/bLGN7QQMjuZHA8mrIrFsvVpw7JHw4HREYLgMWHMQqGPjpbHRXF93e85wfhyg/wAL9QHrRHWKJP8Yohb6H9UDBzhm5YrtdRTKKE+GFSVqLd7rb7Q76RRVXjBdjgLlTZTWRC1piK4XCIqhCG2coxAIxSznJ4SQg4MRQwY3y33eorv+AM497P3q9e7/fd3fB5ItsOs1YLWcsmJrkbpI67XLirLC/O8S6uSqoml2Z6MsrQjQmha0JTNCVD+ILxkubIut5+s1YFC6NIj0ECN+bctAfy3OlOMnv3DWqqMImL+QLxMT26N7ef7fS5LtHqhR8i87FtTyeT2nx5qo2KqLr4X8vkYsUpfZkupm8uK2peCl6I/H8r49WaFvjw/AF9CJSX68LVqAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image48\",\n \"title\": \"image48\",\n \"src\": \"/static/00cdf102bdd871862309b280e962ac41/073e9/image48.png\",\n \"srcSet\": [\"/static/00cdf102bdd871862309b280e962ac41/a2ead/image48.png 259w\", \"/static/00cdf102bdd871862309b280e962ac41/6b9fd/image48.png 518w\", \"/static/00cdf102bdd871862309b280e962ac41/073e9/image48.png 719w\"],\n \"sizes\": \"(max-width: 719px) 100vw, 719px\",\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, \"For more information on the design comparison platform, see JMP's help\\ndocumentation or contact the Test Design and Analyses Division of A-2/9.\"), mdx(\"h1\", null, \"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS\"), mdx(\"p\", null, \"For many \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" tests the response data has variability; i.e., if two\\ntest runs are conducted while holding the factor levels constant, we\\nwill likely measure two different response values. There are three basic\\nprinciples of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" that help us compensate for, quantify, and control\\nvariability in our response data: randomization, replication, and\\nblocking.\"), mdx(\"h1\", null, \"Randomization\"), mdx(\"p\", null, \"Randomization is a principle of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \" used to average out the effects of\\nunknown and uncontrollable nuisance factors. Randomization refers to\\nboth the random allocation of test material to a test run, and to the\\norder in which the test runs are executed. If possible, the order of\\ntest runs should be randomized to avoid biasing the factor effect\\nestimates with the effects of the unknown nuisance variables.\"), mdx(\"p\", null, \"For example, suppose we have one two-level factor of interest. Our test\\nis conducted over a morning and afternoon with 4 test runs in the\\nmorning and 4 test runs in the afternoon. Suppose the temperature in the\\nmorning is 15 degrees cooler than in the afternoon, and the response\\nvalue increases as the temperature increases. The test is not randomized\\nand factor level 1 is run in the morning and factor level 2 is run in\\nthe afternoon. The test data show that the response is higher for factor\\nlevel 2 than for factor level 1. Unfortunately the test team cannot be\\ncertain whether the increase in the response was due to changing from\\nfactor level 1 to factor level 2, or due to the increase in the ambient\\ntemperature from the morning to the afternoon.\"), mdx(\"p\", null, \"If the test was randomized, the runs in the morning would involve both\\nfactor level 1 and level 2 (and likewise for the afternoon.) Ideally the\\neffect of the ambient temperature will average out over each level of\\nthe factor, and we remove its influence on the estimate of the factor\\neffect.\"), mdx(\"h1\", null, \"Replication\"), mdx(\"p\", null, \"Replication is an independent, repeated run of a factor level\\ncombination (as opposed to measuring the result of a single test run\\ntwice---this is a repeated measure.) Replicating factor level\\ncombinations is the best method for obtaining an estimate of run-to-run\\nvariability, which is often called experimental noise. An important\\nbenefit of factorial experimentation is that there is hidden replication\\nin the test design. This means that even if a factorial design for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"k\"), \"\\nfactors is unreplicated, if one factor is determined to be\\ninsignificant, the resulting design is a replicated design for \", mdx(\"em\", {\n parentName: \"p\"\n }, \"k-1\"), \"\\nfactors.\"), mdx(\"p\", null, \"Since statistical analysis of test data using \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"ANOVA\")), \"\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"#fn37\"\n }, \"37\"), \" or linear regression involves\\nevaluating a ratio of an estimated factor effect to the experimental\\nnoise, replication is important to enabling accurate analysis. While\\nthere are methods to estimate experimental noise without replication,\\nthese methods produce estimates that are generally inferior to those\\nproduced by repeating factor level combinations.\"), mdx(\"h1\", null, \"Blocking\"), mdx(\"p\", null, \"Blocking is one of the fundamental principles of Design of Experiments\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \") that allows us to account for the variability in our response data\\ncaused by controllable nuisance factors---factors that are not of\\ninterest but can be controlled. In the absence of blocking, variability\\ncaused by nuisance variables is attributed to experimental noise and may\\nalso bias factor effect estimates; this inflates the experimental noise\\nestimate and makes it more difficult to determine if factors of interest\\nhave an effect on the response variable.\"), mdx(\"p\", null, \"During operational test, there is almost always a nuisance factor that\\nis a source of variability that could and should be controlled. Some\\ntypical operational test nuisance factors are the day of the test,\\nshifts of operators, pilots, tail numbers, terminal/position numbers,\\nand ranges. These factors can impact the response variable\\nsignificantly, sometimes even more than the factors of interest.\"), mdx(\"p\", null, \"Blocking is simply incorporating a nuisance factor into the test design\\nas a blocking factor. Just as with the factors of interest, the goal is\\nto make the blocking factor orthogonal to the other factors. If the\\nlevels of a blocking factor are time based, such as the day of the test\\nor a shift of operators, then the blocking factor creates a restriction\\non randomization. This is because the blocking factor level is held\\nconstant for some period of time.\"), mdx(\"p\", null, \"One way to add a blocking factor in JMP is through the Custom Design\\nMenu. Suppose we have a test with three 2-level categorical factors and\\none 3-level categorical factor. If an 18 run test was planned over three\\ndays, it may improve the analysis to block on the day of the test. Doing\\nso would account for the variability from nuisance factors that vary\\nday-to-day, such as precipitation, humidity, sunlight, and temperature.\\nFigure 28 shows the JMP Custom Design Menu. To add blocking factor for\\nTest Day, under the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Factors\"), \" box, select \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Add Factors\"), \" , then\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Blocking\"), \" , then \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Other.\"), \" By selecting 6 runs per block, we can\\ndivide the 18 test runs among the three days such that all of the levels\\nof the factors of interest occur equally often on each day. Thus any\\ndifferences between each test day will average out across the levels of\\nthe factors of interest. Now the estimates of the factors of interest\\nwill be independent of any effect on the response caused by the test day\\nconditions. Also, the error estimate will be reduced, as the variability\\nassociated with each test day would have been included in the error\\nestimate if the test was unblocked.\"), mdx(\"p\", null, \"Figure 28. Adding Blocking Factors in JMP\"), 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\": \"783px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/dc9b37d8f0f865ce9b5f58a780a2d621/e51a6/image49.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\": \"74.5173745173745%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAACHVAAAh1QEEnLSdAAAC4ElEQVQ4y2NgwA6YgFgAiJWAWBKK5aB8GSCWBWIRBhIByFBxIFaDGqYAxFpQtioQCzOQCcShhslADZOGupiFVIO4oN4CeV0CyftyUMO5STGMEaoB5F0VqEEgQxShLgYZKkqOd5mhBkkSrcM6ZQqDsnkAg7y+M4OglCqSA+ERA3KJEJoEmOYWlGSwiqxnEFXQY1C3i2KwSpoEkXUt2wS34P///wzypn4MShYhIC4PNEZBNJOcaSBYjVlkG4O+TyGDX9spuL6ZQH1mkS0MDDFr/zPkz7nENPXmf6aFT/8z5c29yiRhFskQO/MJWKGSvgM7j5CkpISSHi/IMhAwDW8C09mzrzCu+f+fce6T/4xVGz4w2sZ3grw8TZydW1CUnY1VkYWZSZ5XTJEfGAyCQNsErZKnCnPxi4mys7LIAeVkgAYLWiZOEjGNaOKzTZ8tIKtpJSIkLKokJCwuLy6nKWadMpWPwTqxnze0cYuObVJvsENyT2hw8y5NNY9iZrOYLlG3uFq2yM5Dms7ZM33ccmf7BLXs17QPL2czi+kWtgirYfWs3ydpGNVlpx9c4+Jcvll18kWgDzQCGngW7ry5Z/bW6/9nbr76f9aWq1tBXnNOnywOoudtv7537vYb/6dvuvJ/xuaru0FiHjkzREH0rK3Xp03dePX/pPVXfk5ef/l0z/pbbAyG0d08T5+/2/nwyZv/9x+9/P/oyetNIMX+edPABj5++nbX42fvgHKvQHI7QGKR5XPFQPTTFx/m3n/8Gix39+GLy//+/+dgMIrp5br94PXha3de/L96+/n/G/de7gEp9s2dKgGigfwjN+69gsjdfXEIJBZeOgds2cNnH+YC5UF6/l+/8/w6UIyRwSSqU+za3efd1+8+33/l9tP9F288bmOQS+T0yposzCATx33p5uOe6/deHLhy68kBoFwXA08IV0jxLCEG9WSRw2fvTDh16f7D05fv3zly9vaO6KqFCgDykj7YgzhiwwAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image49\",\n \"title\": \"image49\",\n \"src\": \"/static/dc9b37d8f0f865ce9b5f58a780a2d621/e51a6/image49.png\",\n \"srcSet\": [\"/static/dc9b37d8f0f865ce9b5f58a780a2d621/a2ead/image49.png 259w\", \"/static/dc9b37d8f0f865ce9b5f58a780a2d621/6b9fd/image49.png 518w\", \"/static/dc9b37d8f0f865ce9b5f58a780a2d621/e51a6/image49.png 783w\"],\n \"sizes\": \"(max-width: 783px) 100vw, 783px\",\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, \"Blocking can also be employed as a strategy to hedge against the\\nnegative impact on analysis resulting from lost test data. The levels of\\nthe factors of interest should be balanced across the levels of the\\nblocking factors; the consequence of this is that all blocks typically\\ncontain data for every factor level. In the above example with a three\\nday test, if one test day was lost due to weather or an equipment\\nmalfunction, the test runs from the other test days will still be\\nbalanced. Also, the factors of interest will likely be less correlated\\nthan they would be in a scenario where a random set of 6 test runs were\\nlost.\"), mdx(\"p\", null, \"JMP's help files have useful information on building blocking factors\\ninto a test design. The rule of thumb is: \\\"Block what you know,\\nrandomize the rest!\\\"\"), mdx(\"h1\", null, \"TYPICAL SITUATIONS\"), mdx(\"p\", null, \"The next section covers some typical situations that may be encountered\\nin \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" and some suggested remedies.\"), mdx(\"h2\", null, \"How do I Select a Design?\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Table of commonly encountered design scenarios and possible design matches.\"), mdx(\"th\", null, \"Full Factorial\"), mdx(\"th\", null, \"2\", mdx(\"sup\", null, \"k\"), \"Fractional Factorial\"), mdx(\"th\", null, \"Orthogonal Arrays\"), mdx(\"th\", null, \"Covering Array/Combinatorial Design\"), mdx(\"th\", null, \"Computer Generated Design (Optimal)\"), mdx(\"th\", null, \"Split/Strip Plot Designs\"), mdx(\"th\", null, \"Space Filling Designs\"), mdx(\"th\", null, \"Demonstration\"), mdx(\"th\", null, \"Cases\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Factor Considerations\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"All continuous factors\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\", mdx(\"sup\", null, \"31\")), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"All 2-level factors (mixed continuous and/or categorical)\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Mixed level factors (mixed continuous and/or categorical)\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X [38](#fn38)\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Disallowed combinations\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Modeling Considerations\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Quadratic terms\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X [39](#fn39)\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Two-factor interaction terms\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X [40](#fn40)\"), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Three-factor or higher interaction terms\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X [41](#fn41)\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Response Variable Considerations\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Random Variation\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Deterministic\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"X\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"X\", mdx(\"sup\", null, \"31\")), mdx(\"td\", null, \"X\"), mdx(\"td\", null, \"X\")))), mdx(\"p\", null, \"If all of the factors in your test have only 2-levels or are all\\ncontinuous, you can choose almost any design type. It is most desirable\\nto select a design with a run size that is a power of 2 (8, 16, 32,\\netc.) If resource constraints prevent this, choose a D-Optimal design.\"), mdx(\"p\", null, \"When a test involves categorical factors with more than 2 levels, it is\\nmost common to create a full factorial or D-Optimal design. Create\\nseveral design options and compare them using the test design measures\\nof merit presented in this guide.\"), mdx(\"p\", null, \"When a test involves a deterministic response, use a combinatorial\\ndesign to find factor level combinations that cause problems in the\\nsystem. If you plan to characterize the system, choose a space filling\\ndesign.\"), mdx(\"h2\", null, \"I Have Factors that Are Hard to Change\"), mdx(\"p\", null, \"It is the rare operational test scenario where the runs in the test\\nevent matrix can be executed in an entirely randomized order. It is\\ncommon that a group of runs involving a particular factor level must be\\nexecuted consecutively because of constraints imposed by the range, test\\nasset availability, or feasible tactics. It is these cases when the\\ndesign should be set up, run and analyzed using a split plot\\nconfiguration.\"), mdx(\"p\", null, \"Split Plot designs can be created from an existing design type\\n(typically a computer generated design) by identifying the\\nhard\\u2011to\\u2011change factors and easy\\u2011to\\u2011change factors. The hard\\u2011to\\u2011change\\nfactors are those that cannot be arbitrarily changed from run to run.\\nThese factors are arranged into groups of runs called Whole Plots. Whole\\nPlots contain equally sized (usually) sets of runs and the levels of the\\neasy\\u2011to\\u2011change factors are randomized. Figure 29 shows a Split Plot\\nconfiguration with one hard\\u2011to\\u2011change and two easy\\u2011to\\u2011change factors.\"), mdx(\"p\", null, \"Figure 29. Split Plot with One Hard to Change Factor\"), 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\": \"787px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/a16a713032e3ac076fcc215599ea9ec2/e619b/image50.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\": \"75.2895752895753%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAACHVAAAh1QEEnLSdAAADiUlEQVQ4y2NgwA/YgVgciKWBWAyIZYFYAog5GcgEzEAsCDVIC4qlGSgAbFAXKkENEoK6miID+aGGyUMNZMarQ9+3kEFUTpNBSsOCQUbLmkFcUY9BWsee4f///wzMbJwgzQJALMXAyMjFyMjEzsjEAjZQztCTQULZgEFS1YRBSt2cQVrTikHDKZGBQdstnUFQTIZBSs2MQVLNlEFMXgtosA2DY+5iBgl1S5grwV7l4BVkEJBQYnDKW8qgYhUCViuupA802BCsH2Qog1Fonai2W5qwQ1yTiFNCq4hFaIWInm+RkFXSJG7j8GYBfa9sEVPfLCl9lzhZ0+BKIYOgan7rpMm8hiF1/Eb+hSIOMfWiDnGNoqbBFcKGIfV8DEZBFUriqqaaQBcogCOAiVdZyyle0SZluoBlTLs4j5SWCjT8RPlk9ZUNfQuEbFKmSZiF1orxSKirQeWkgeqUjANLRRiMovukorNqRCqn7phTNXP/+rJJWzIlXUp5nNKniIk4VfKVdC83rpy2a13FtD2rc5oXAsPAlcUxdbICs0EmV0HHUuPK6btXVc/ctyK/fakFg1wYJ4O0a4XUrccfhC7efvnt3PXn/y/dfrWQgYGJLbJioSTQZo6bD9+7Xbj54v/Z68/+X7331gcUWaGl85SBciw3H75zv3Dr5f9zN57/v3bvjT9QjAlkoPSjN3+EHj//8PL+kzf/n778OAMYVZzRVQuBOUKc6+W7784Pn777f//xm/8v3n73AMVSeNl8ULpkf/n2q8ujZ+//P3jy9v/LN1+8QZYwmMX2Kpn5pMuVt0xxb5u63D2/utPCMKJd2j55grB+ZI9UeGatWl3PbJ/GCQs9/BNKtDWD24SBcjJawW0SMVlV6o19c73r+xZ4+ieWqmsHNUswaAc3SzVPXCTUt+LUrv5VZ660zN3rBbSJ1Tt/tgSDXjpv65wd6hNWnT7Zs/z0+Y75ex2AcowOqZPlzWN7QFmSpX/lqZW9K0/f7V9xIhbsZUnncklguPDfe/L+y60Hr/8DvRgLCqfkxmVSDAyqXC/e/tC/8+jdf5Dcw+ef/EByPnkzFdT8GwVA7LuP3z0EyT1+8akMxGdQ9K5VmLD0gPy1O8+fX7715P+ZKw+TGRgkeRLrlwIjxYX31sPXencfvX5/+8HLnzfuvfAEucI7d4a8TnCLyLSVhzluPXh17sbd50ALXxWAXAwAswhSRyi6SnQAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image50\",\n \"title\": \"image50\",\n \"src\": \"/static/a16a713032e3ac076fcc215599ea9ec2/e619b/image50.png\",\n \"srcSet\": [\"/static/a16a713032e3ac076fcc215599ea9ec2/a2ead/image50.png 259w\", \"/static/a16a713032e3ac076fcc215599ea9ec2/6b9fd/image50.png 518w\", \"/static/a16a713032e3ac076fcc215599ea9ec2/e619b/image50.png 787w\"],\n \"sizes\": \"(max-width: 787px) 100vw, 787px\",\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, \"If there are two hard\\u2011to\\u2011change factors (one will be specified as\\nvery\\u2011hard\\u2011to\\u2011change and the other hard\\u2011to\\u2011change) the\\nvery\\u2011hard\\u2011to\\u2011change factor will determine the whole plots and the\\nhard\\u2011to\\u2011change factor will be used to create sub plots within the whole\\nplots. The easy\\u2011to\\u2011change factors will be randomized within the subplots\\nas shown in figure 30.\"), mdx(\"p\", null, \"Figure 30. Split Plot with a Very Hard and Hard to Change Factor\"), 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\": \"715px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/cc63166e2a57e41214ea94f51e1e8e88/d0c0e/image51.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\": \"106.56370656370657%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAVCAIAAADJt1n/AAAACXBIWXMAAAsTAAALEwEAmpwYAAACcElEQVQ4y41TaZeaMBTl//+ljtrOh7YfrNu4IEEQsrAIhFVFjzoXMm6dnrbXnHgJeY+b+140yxGe5zPurV3GhB8naZJmsUxBZJrHMmtIVnysZHm12+dllRVlXm61xWLZewE6v/r9APAbeIDwAsWEFwYB/sDxPpVSDUCzXfry8mUyeVML+RVFUZRlWbTI8jvSK7Is0yj3vvZ6s9kcMIClYdtrvIuiaLPZJEmCTdsWVVUh3fYKPGphJDmnuxZ1faCUjkeTsigZo9bKcl0XKaAIykGCdkZeZEdeLZJQmF8ul/P5jBlKDYMc6qOUyX6/F4Jjt23bSMo5B0G8SQjcCMNQc7k3Ggx0XScmgXLTJDgkwnZXKF7X9SPBDK6FsRwPh9PplBCiL3QhhArGxv01cn+FirxBS4tKcG7oS8dxVmSFcwZ+cDwe1dZDC5CbT4+5NNuh3W7HIMQ0TRxpjZ+9buFYlrVaraAItqFIsB0+weR7cBA1snFa7GCMwRUoRz9MRuNBf4AVKPI9Hx9U5XkKjppCpqfTWRmuAO46LuPi0gIrEH86nVCzOI7BP4JhWJHnl0+Afui4PaqMqC0qpxxpgtH66OD21eX2cRBiEMte/yYH4nH4m+eaw8TPH9+HwyHu1q37sEk18KPJ6thPbrtM9LodtPe311d9scAtapyGZs7hFhoLhsHEx5h7cJIWHJ3HOKUM1uEeoXXRJ1XZ3AN42/AHh5+CYRhvS5RIqQ4DafUn/DnY3yRv44lhmLi+cRRnrR+qNf85cCWTyXi0mM/RAqgZ5mPbkf8zNN32RzMyXa5dL6G+dL0Y5C+DeonFI4sGNgvfAZy9k49ApaxuAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image51\",\n \"title\": \"image51\",\n \"src\": \"/static/cc63166e2a57e41214ea94f51e1e8e88/d0c0e/image51.png\",\n \"srcSet\": [\"/static/cc63166e2a57e41214ea94f51e1e8e88/a2ead/image51.png 259w\", \"/static/cc63166e2a57e41214ea94f51e1e8e88/6b9fd/image51.png 518w\", \"/static/cc63166e2a57e41214ea94f51e1e8e88/d0c0e/image51.png 715w\"],\n \"sizes\": \"(max-width: 715px) 100vw, 715px\",\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 consequence of designing the test in this manner is that we can no\\nlonger use a common estimate of error to evaluate both the\\nhard\\u2011to\\u2011change and easy\\u2011to\\u2011change factors. There is more variability in\\nthe average response between the levels of the hard\\u2011to\\u2011change factors\\nthan between the easy\\u2011to\\u2011change factor levels. Hence the power for the\\nhard\\u2011to\\u2011change factors will be lower than for the easy\\u2011to\\u2011change\\nfactors. To improve the power of the hard\\u2011to\\u2011change factors, the test\\nshould include multiple whole plots for each hard\\u2011to\\u2011change factor\\nlevel. The resulting test will be larger than if a completely randomized\\ndesign was used.\"), mdx(\"p\", null, \"To construct a split plot design in JMP's custom designer, open the\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Designer\"), \" tab, and enter the desired factors as usual. Under\\nthe \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Changes\"), \" column for the factors, change \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Easy\"), \" to \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Hard\"), \" .\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Very Hard\"), \" is used if there are two hard-to-change factors and there\\nwill be subplots within the whole plots; the subplot factor will be\\nlabeled \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Hard\"), \" . Specify the desired model.\"), mdx(\"p\", null, \"Specify the number of runs in each whole plot. Under \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Design\\nGeneration\"), \" , enter the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Number of Whole Plots\"), \" , which will\\ndetermine the number of times the levels of the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Hard\"), \" factor (if\\nthere is only one hard-to-change factor) or \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Very Hard\"), \" factor is\\nreplicated. In figure 31 the very hard-to-change factor will have each\\nfactor level replicated 2 times; 4 whole plots divided by 2 levels\\nequals 2 whole plots for each level.\"), mdx(\"p\", null, \"Specify the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Number of Subplots\"), \" (if necessary because there are 2\\nhard-to-change factors). Each whole plot will have 2 subplots; 8\\nsubplots divided by 4 whole plots equals 2 subplots per whole plot.\\nEnsure that analysis is done in the table created by JMP, as several\\nimportant factor properties have been changed to enable a proper\\nanalysis.\"), mdx(\"p\", null, \"Figure 31. Creating a Split Plot Design in JMP\"), 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/096255ffb480f7df5de5e36fdb5d4c6b/5148a/image52.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\": \"25.482625482625483%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAFCAYAAABFA8wzAAAACXBIWXMAABcRAAAXEQHKJvM/AAAAnUlEQVQY002P2wrCMBBEV1H0wRvV1qIxaq1NRRAp6v9/mrNyhD4csjPZ7E7MzILYir2I4iym4oC+iAwv0l+JZa8v8L42Cjee1GsxEblI4oY2vJohI7yMEDlzbN673IgVtSfoxFWMxUAU4iOOYkifB3iT3of+HpQYOzFj653NiR5P9cCrOAvuG86X8YUIJ7Fga0L/B3jdogO6RDfo7gt8vgphhqAn3QAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image52\",\n \"title\": \"image52\",\n \"src\": \"/static/096255ffb480f7df5de5e36fdb5d4c6b/e3189/image52.png\",\n \"srcSet\": [\"/static/096255ffb480f7df5de5e36fdb5d4c6b/a2ead/image52.png 259w\", \"/static/096255ffb480f7df5de5e36fdb5d4c6b/6b9fd/image52.png 518w\", \"/static/096255ffb480f7df5de5e36fdb5d4c6b/e3189/image52.png 1035w\", \"/static/096255ffb480f7df5de5e36fdb5d4c6b/5148a/image52.png 1228w\"],\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, \"For more specific information on the construction and analysis of Split\\nPlot designs, check the JMP help files or contact the Test Design and\\nAnalyses Division of A-2/9.\"), mdx(\"h2\", null, \"Can I Combine Developmental Test and Operational Test Data?\"), mdx(\"p\", null, \"Developmental and Operational Test data can be combined if the\\ndevelopmental test is determined to be operationally representative.\\nDuring test planning, if the analyst thinks that combining developmental\\ntest (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \") data with operational test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \") data may be a possibility,\\nthere are some important considerations to discuss with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" team.\"), mdx(\"p\", null, \"To combine any data to be used for characterization, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" events\\nshould have factors that correspond to the factors for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" event. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" test articles must also be the \\\"same\\\" as the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" test articles. Any\\nvariability caused by small changes to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" may be addressed with an\\nadditional blocking variable. Another very important requirement is that\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" events must be \\\"operational\\\" in nature. Lab tests, chamber tests\\nor table top tests are not usually operational and so cannot be\\nconsidered for combined \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" data.\"), mdx(\"p\", null, \"During test planning and test design, discussion of the possibility of\\ncombining the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" data is essential to ensure that the future\\ncombination will be feasible. Ultimately, it may not be possible to\\ncombine the data because of the evolution of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", but proper\\nplanning will maintain the possibility. The same considerations can be\\napplied when planning the combination of data from Initial and Follow-on\\nTest & Evaluations.\"), mdx(\"p\", null, \"There are several advantages to combining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" data. First,\\ncombining data makes the \\\"Test-Analyze-Test\\\" strategy viable. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" test\\ndata can be used to determine the significant main effects so that later\\nin \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" the test event matrix can be more focused on the relevant factors\\nand their interactions. Second, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" test events are usually planned and\\nexecuted for the \\\"minimum\\\" data needed, so \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" data is an attractive way\\nto increase the sample size of the data for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" analysis. To obtain more\\ninformation on combining \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" data, contact the Test Design and\\nAnalyses Division of A-2/9.\"), mdx(\"h2\", null, \"I Have Disallowed Combinations\"), mdx(\"p\", null, \"One of the reasons optimal designs have skyrocketed in popularity at\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is the ability to deal with disallowed combinations. A disallowed\\ncombination occurs when one level of a factor cannot occur\\nsimultaneously with a level of another factor. The JMP \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Design\"), \"\\nplatform allows you to specify disallowed combinations using a script or\\nfilter.\"), mdx(\"p\", null, \"Keep in mind that if the operation/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" in question has a large number\\nof disallowed combinations, you may need to make some modifications to\\nthe test design. One solution could be to add another operation to the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" in order to separate the factor list into two groups for separate\\ntest events. Perhaps the factor prioritization and management may need\\nto be reevaluated to determine if a factor can be removed from the test.\\nThe factors in question may not be independent enough to be separate\\nfactors, and combining the factors into a super factor could be the best\\napproach. For more information on these or other techniques to avoid or\\novercome disallowed combinations contact the Test Design and Analyses\\nDivision of A-2/9.\"), mdx(\"h2\", null, \"My Power Is Too Low\"), mdx(\"p\", null, \"You have created the test event matrix, created the power curves, and\\ndetermined that the power for either your main effects or two-factor\\ninteractions is not sufficient. A straight-forward solution is to\\nincrease the test size, but this is often not feasible due to resource\\nconstraints. Another common solution is to eliminate factors. This\\nsolution results in a less-thorough exploration of the battlespace and\\ncould result in undetected system problems. Fortunately, there are some\\nother options to consider:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Keep the same test plan and explain why this added risk is\\nacceptable for the test program.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Split a factor into two factors: As an example, splitting a 4 level\\nfactor into two 2 level factors will increase the estimation power\\nof a design without any additional runs. This can be an option for\\nmany factors that are amalgamations of multiple factors.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Reexamine the likelihood and magnitude of impact for the two-factor\\ninteractions; if some are not as important or less likely to exist,\\ninclude the important ones and remove the other interactions from\\nthe power analysis.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Report the power on the main effects only and explain why the added\\nrisk of not detecting two-factor interactions is acceptable for the\\ntest program.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Make sure the categorical factors really are categorical; if factors\\ncan be changed to continuous, the levels can be reduced to two (but\\nadd some center points). Fewer levels will increase the power for\\nthose factors.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ask someone outside the program for their thoughts. Creating test\\ndesigns only within the test team can lead to \\\"group think,\\\" and\\nexternal advice may provide another point of view and a solution.\"))), mdx(\"p\", null, \"Whatever the option chosen, it is important to document the rationale in\\nthe Test and Evaluation Master Plan to keep interested parties informed.\\nIn the end, if the power is too low and there are not any realistic\\noptions to increase the power, it is better to report the low power and\\nthe associated risk, than to eliminate factors which may be crucial to\\nthe warfighter's situational awareness. For guidance on creating power\\ncurves or power calculations in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", see the November 2014 guide,\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Power Analysis Tutorial for Experimental Design Software.\")), mdx(\"h2\", null, \"I Have Factor Levels that Depend on Other Factor Levels\"), mdx(\"p\", null, \"The traditional nested design occurs when the levels of one factor are\\nsimilar but not identical for the levels of another factor. These types\\nof designs are also called hierarchical designs (Montgomery, 2013). In\\noperational test they might resemble figure 32.\"), mdx(\"p\", null, \"Figure 32. Example of a Traditional Nested Design in Operational 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\": \"988px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/9fd1e3689a7b8e9ca89ba3e5685488c2/e4900/image53.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\": \"25.482625482625483%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAFCAYAAABFA8wzAAAACXBIWXMAACHVAAAh1QEEnLSdAAAAmUlEQVQY02XQawsBYRCG4SnlbJEcWyxCjpuUwidy+v+/yD16yhtPXbU77+zO7JqZrTHEDAO0ZC5TtNHAQn0xMuhgiTESFEwNXYzQRISq7r2xj4qak2Cop4gd9nr2k8i+KWlymKzqedR07clpwxUOWsAX+XvBb3yzOnoaXg7qk+DLYv0aO2KDVLaSqn7GDXe8cNH5CQ88dX51bx0jCp+5Sna4AAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image53\",\n \"title\": \"image53\",\n \"src\": \"/static/9fd1e3689a7b8e9ca89ba3e5685488c2/e4900/image53.png\",\n \"srcSet\": [\"/static/9fd1e3689a7b8e9ca89ba3e5685488c2/a2ead/image53.png 259w\", \"/static/9fd1e3689a7b8e9ca89ba3e5685488c2/6b9fd/image53.png 518w\", \"/static/9fd1e3689a7b8e9ca89ba3e5685488c2/e4900/image53.png 988w\"],\n \"sizes\": \"(max-width: 988px) 100vw, 988px\",\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, \"Each aircraft has four power ports which may be used during test, but\\nthe power port \\\"A\\\" on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Alternating Current\"\n }, \"AC\"), \"-130 is different than the power ports \\\"A\\\"\\non the A-10 and the F-15. The response variable can still be analyzed\\nunder both factors but the analysis model must be set up differently\\nthan a traditional ANOVA model; e.g., do not include an interaction term\\nbetween the parent and nested factor. In the design construction in JMP\\nchange the attribute of the nested factor to \\\"nested\\\". Include in the\\ntest design documentation that \\\"Power Port\\\" is nested within \\\"Aircraft\\\".\"), mdx(\"p\", null, \"Within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", there is a type of test design called a sub-design. As an\\nexample, a test with a sub-design might occur when examining terrain.\\nMaritime terrain has sea states, while desert and mountain terrain does\\nnot. See figure 33.\"), mdx(\"p\", null, \"Figure 33. Example of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Sub-Design\"), 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\": \"717px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image54.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\": \"75.2895752895753%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAACMUlEQVQoz3WT+3OaQBDH+f//i3bsdJofOmMmaczDNGkMaEwiwaCAXjhex+MEEQQBIelGGx8zzZdl5+Dus7e7BwxGiGPZTqcjSVIQBP6HJiv5nwtmGYxxs9nsCwKdUNd1d7F1rMmOKKW7jwwhpN3m+iBBeH4WHx8fBsOh53mWaRqGYRPbdZxNAIi3B8PdF/oenZRVVZaVbduiKM7nCZCweCCKLyqeRVEwnXqOoygKpBN+iIHEEEJhOHtbKU3isSItiyKOwiLPTR1rKkrnsecQm0Jdnq5po9EIqCiKGM91iWV1xeGv9tPFnXjKCcetXuO2d3R1d3TdbdzyZ+9v+Mb1PX90Ek78LM/nCWT2LuYFoevfl/Vm6+vhZa3erB02vx9fffnZqNXPv9Uvfpz8ATs4bZ2z/NnhuaygKJpNQWEIjjFNk+M4ttub+tSxzYnnvJtrF9miWuYlWJEtiwwqcoPZGBsxwJuaoWEaVju9Z1XToEloDBeCrMqyzAuovSiWy7woqqrSLMdyaJLMVxuvYJsQRZYl1QDG0A3oJ/QjSdO3Hb2+voI3HeoFs0WaBhuYUg8OdDDCozGCD0aWZeChGZ/A4SJNtjvDCCZGmoU1nRAba1jX9cUi+y/s+vuwoetPPM92+UWWrdf9E4xXtoEtl2KTzON4C1vE4tjWTfs+y6AveZ7DQe7Jn85oEE4DX1E11QA42sKrH4Q+9CVBRrJqKNhc+421BYXlJbb7eNPlDeLE0Rb+C552K79tIqVpAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image54\",\n \"title\": \"image54\",\n \"src\": \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image54.png\",\n \"srcSet\": [\"/static/cb39d329fcfcee19a87388fd0a5e782f/a2ead/image54.png 259w\", \"/static/cb39d329fcfcee19a87388fd0a5e782f/6b9fd/image54.png 518w\", \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image54.png 717w\"],\n \"sizes\": \"(max-width: 717px) 100vw, 717px\",\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, \"There are two primary ways to deal with a scenario such as this one; one\\napproach would require a computer generated design while the second\\nwould allow the choice of any other appropriate design type.\"), mdx(\"p\", null, \"The design could be constructed as an optimal design with specified\\ndisallowed combinations for the Sea State and Terrain factors. The\\noptimal design would then only contain runs where the Mountain/Desert\\nlevels were paired with the Sea State = 0 level. Figure 34 shows how the\\n\\\" \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Define Factor Constraints\"), \" \\\" box in the JMP \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Custom Design\"), \" tool\\ncan be used to specify disallowed combinations using a script. In the\\nresulting design, only the Maritime factor will have a sea state other\\nthan 0.\"), mdx(\"p\", null, \"Figure 34. Computer Generated Design with Disallowed Combinations\"), 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\": \"717px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image55.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\": \"75.2895752895753%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAIAAABr+ngCAAAACXBIWXMAAAsTAAALEwEAmpwYAAACMUlEQVQoz3WT+3OaQBDH+f//i3bsdJofOmMmaczDNGkMaEwiwaCAXjhex+MEEQQBIelGGx8zzZdl5+Dus7e7BwxGiGPZTqcjSVIQBP6HJiv5nwtmGYxxs9nsCwKdUNd1d7F1rMmOKKW7jwwhpN3m+iBBeH4WHx8fBsOh53mWaRqGYRPbdZxNAIi3B8PdF/oenZRVVZaVbduiKM7nCZCweCCKLyqeRVEwnXqOoygKpBN+iIHEEEJhOHtbKU3isSItiyKOwiLPTR1rKkrnsecQm0Jdnq5po9EIqCiKGM91iWV1xeGv9tPFnXjKCcetXuO2d3R1d3TdbdzyZ+9v+Mb1PX90Ek78LM/nCWT2LuYFoevfl/Vm6+vhZa3erB02vx9fffnZqNXPv9Uvfpz8ATs4bZ2z/NnhuaygKJpNQWEIjjFNk+M4ttub+tSxzYnnvJtrF9miWuYlWJEtiwwqcoPZGBsxwJuaoWEaVju9Z1XToEloDBeCrMqyzAuovSiWy7woqqrSLMdyaJLMVxuvYJsQRZYl1QDG0A3oJ/QjSdO3Hb2+voI3HeoFs0WaBhuYUg8OdDDCozGCD0aWZeChGZ/A4SJNtjvDCCZGmoU1nRAba1jX9cUi+y/s+vuwoetPPM92+UWWrdf9E4xXtoEtl2KTzON4C1vE4tjWTfs+y6AveZ7DQe7Jn85oEE4DX1E11QA42sKrH4Q+9CVBRrJqKNhc+421BYXlJbb7eNPlDeLE0Rb+C552K79tIqVpAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image55\",\n \"title\": \"image55\",\n \"src\": \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image55.png\",\n \"srcSet\": [\"/static/cb39d329fcfcee19a87388fd0a5e782f/a2ead/image55.png 259w\", \"/static/cb39d329fcfcee19a87388fd0a5e782f/6b9fd/image55.png 518w\", \"/static/cb39d329fcfcee19a87388fd0a5e782f/0ad97/image55.png 717w\"],\n \"sizes\": \"(max-width: 717px) 100vw, 717px\",\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, \"Another way to address the scenario would be to create a \\\"super\\\" factor\\nof Terrain and Sea State. The factor would have a level for each of the\\nallowed combinations of Terrain and Sea State (7 total levels.) The\\nsuper factor has seven levels, so the test size will need to increase to\\nobtain the same effect power that the former five level Terrain factor\\nhad. Figure 35 shows the super factor, \\\"Terrain\\\" as described in this\\nexample.\"), mdx(\"p\", null, \"Figure 35. Super Factor to Address a Nested Factor Scenario\"), 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\": \"890px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/4e101b73addfad659838133f69035bf0/7f80b/image56.jpg\",\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.490347490347496%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/jpeg;base64,/9j/2wBDABALDA4MChAODQ4SERATGCgaGBYWGDEjJR0oOjM9PDkzODdASFxOQERXRTc4UG1RV19iZ2hnPk1xeXBkeFxlZ2P/2wBDARESEhgVGC8aGi9jQjhCY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NjY2P/wgARCAAJABQDASIAAhEBAxEB/8QAGAAAAwEBAAAAAAAAAAAAAAAAAAIDAQX/xAAVAQEBAAAAAAAAAAAAAAAAAAAAAf/aAAwDAQACEAMQAAAB6zZZEKi//8QAGhAAAgIDAAAAAAAAAAAAAAAAAAECERAiMf/aAAgBAQABBQJWbFSF3H//xAAUEQEAAAAAAAAAAAAAAAAAAAAQ/9oACAEDAQE/AT//xAAUEQEAAAAAAAAAAAAAAAAAAAAQ/9oACAECAQE/AT//xAAZEAACAwEAAAAAAAAAAAAAAAAAQQEQETH/2gAIAQEABj8C5ghEX//EAB0QAAIBBAMAAAAAAAAAAAAAAAABIRARUWGBkbH/2gAIAQEAAT8hZoXIi2UtG3oewxT/2gAMAwEAAgADAAAAEKwv/8QAFREBAQAAAAAAAAAAAAAAAAAAEBH/2gAIAQMBAT8Qh//EABURAQEAAAAAAAAAAAAAAAAAAAEQ/9oACAECAQE/EFn/xAAcEAACAQUBAAAAAAAAAAAAAAABESEAEEFx0fH/2gAIAQEAAT8QSBJk4epmi0BYKJdr23bFje3/2Q==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image56\",\n \"title\": \"image56\",\n \"src\": \"/static/4e101b73addfad659838133f69035bf0/7f80b/image56.jpg\",\n \"srcSet\": [\"/static/4e101b73addfad659838133f69035bf0/8356d/image56.jpg 259w\", \"/static/4e101b73addfad659838133f69035bf0/bc760/image56.jpg 518w\", \"/static/4e101b73addfad659838133f69035bf0/7f80b/image56.jpg 890w\"],\n \"sizes\": \"(max-width: 890px) 100vw, 890px\",\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, \"For more information on nested factors, refer to the JMP help files or\\ncontact the Test Design and Analyses Division of A-2/9.\"), mdx(\"h1\", null, \"Best Practices/Pitfalls in Test Design\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"When possible, make factors continuous.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"If you use a continuous factor and you suspect a nonlinear\\nrelationship between the factor and the response, use three levels\\nfor the factor. Most textbooks advocate using two levels and\\nincluding center points in the design, but this assumes a sequential\\ntest-analyze-test approach.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Use continuous MORVs when possible. Continuous MORVs offer several\\nadvantages to binary MORVs. First, for the same size test, power\\nwill be higher using a continuous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \". Second, more information is\\ncontained in continuous data; a continuous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \" can be turned into a\\nbinary \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \", but the reverse is not true. If a binary/discrete \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission-Oriented Response Variables\"\n }, \"MORV\"), \"\\nis used, consider developing other continuous MORVs for power\\ncalculations.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Your first design option should be a full factorial. Consider other\\noptions only if the full factorial is infeasible or inefficient\\n(i.e., many more runs than required to estimate a main effect and\\ntwo-factor interaction model).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Create two or three test designs that meet your needs and use the\\nmeasures of merit to compare them.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Control the nuisance variability you know about with blocking;\\naverage out the unknown nuisance variability with randomization.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ask for help, advice or sanity checks. Even the most experienced\\nanalyst may not have thought of the best way to do something.\"))), mdx(\"h1\", null, \"Pitfalls:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Be cautious with disallowed combinations. If you have a lot, you may\\nrequire additional operations under a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Don't limit your design because you believe you won't be able to\\ntest it. Things change all the time and the capability may exist by\\nthe time you go to test or may be developed just for your test.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Just because you generate a design in JMP's Custom Designer, doesn't\\nmean it is the optimal design! Run the design generation algorithm\\nseveral times and check multiple measures of merit.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Don't just turn the crank on JMP or the Test Design Suite. It is\\nyour job to understand the output and what methods are used to\\ngenerate the results.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Never change a design point without re-evaluating the design's\\ncapability to estimate the main effects and two-factor interactions.\"))), mdx(\"h1\", null, \"Appendices\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Glossary\"), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Active Effect\"), mdx(\"td\", null, \"A term used to describe a main effect (factor) or interaction that causes a statistically significant difference in the response variable when the factor levels are changed.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Aliasing\"), mdx(\"td\", null, \"A condition where the effect estimate of one factor includes the influence of one or more other effects (main effect or higher-order interactions).\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"ANalysis Of VAriance (ANOVA)\"), mdx(\"td\", null, \"A mathematical process for evaluating the variation in data between groups and within groups in order to determine whether there is a differences between the group means. This procedure can be used to compare multiple systems, or determine if there are differences in the mean response between levels of a factor.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Augmentation\"), mdx(\"td\", null, \"The process of strategically adding new runs to an existing test design after some data has been collected.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Balance\"), mdx(\"td\", null, \"A column in a test design matrix is balanced if every factor level occurs an equal number of times. A test design is balanced if every possible factor level combination occurs an equal number of times.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Blocking\"), mdx(\"td\", null, \"Blocking is one of the fundamental principles of Design of Experiments (DOE) that allows us to account for the variability in our response data caused by nuisance factors\\u2014factors that are not of interest but can be controlled. Blocking factors become part of a test event matrix.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Center Points\"), mdx(\"td\", null, \"A test run where every continuous factor is set to the value halfway between its minimum and maximum factor levels.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Confounding\"), mdx(\"td\", null, \"Synonymous with aliasing: a condition where the effect estimate of one factor includes the influence of one or more other effects (main effect or higher-order interactions).\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Correlation\"), mdx(\"td\", null, \"A statistical measure on a scale from -1 to 1 that indicates how close two variables are to having a linear relationship with each other. Two factors are perfectly correlated when the value of one factor\\u2019s level can be precisely determined by knowing the value of the other factor\\u2019s level.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Coverage\"), mdx(\"td\", null, \"Describes the percentage of possible factor level combinations (after removing the disallowed combinations from the complete combination space) that a combinatorial design includes at a given strength.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Deterministic\"), mdx(\"td\", null, \"A deterministic system or model will always produce the same output from a given starting condition (level settings of the independent variables.)\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Disallowed Combination\"), mdx(\"td\", null, \"A combination of the levels of two or more factors that cannot be feasibly executed together in a test run.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Distribution\"), mdx(\"td\", null, \"A listing or function showing all the possible values of a data set and how often they occur.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Effect\"), mdx(\"td\", null, \"The average change in a response variable produced by changing the level of a factor.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Estimation\"), mdx(\"td\", null, \"An attempt to gain insight about an unknown population parameter based on information obtained from sample data. At AFOTEC we typically estimate means and variances of measures, factor effects, and proportions of failures.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Factor\"), mdx(\"td\", null, \"An independent variable which may affect the performance of a system when its levels are changed\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Factorial\"), mdx(\"td\", null, \"A test plan consisting of two or more factors, each with discrete possible values (or levels). A full factorial is a design whose experimental units (runs) take on all possible combinations of these levels. A design which includes a strategically selected subset of the possible combinations is called a fractional factorial.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Interaction\"), mdx(\"td\", null, \"A situation where the effect of one factor on a response depends on the level of another factor.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Level\"), mdx(\"td\", null, \"A specific setting of a factor during a test or experiment.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Main Effect\"), mdx(\"td\", null, \"The effect of a factor (independent variable) on a measure (dependent variable) averaging across the levels of the other factors.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Optimal Designs\"), mdx(\"td\", null, \"A test design whose levels are combined in a way that optimizes some statistical design quality criterion that is a function of the design matrix.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Orthogonality\"), mdx(\"td\", null, \"A test design is orthogonal if each factor can be evaluated independently of all the other factors. This is possible if, for the test runs involving any level of any factor, the levels of the other factors are present in equal amounts. When an orthogonal test design has two-level factors coded -1 and +1, the inner (dot) product of any two columns is 0.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Population Parameter\"), mdx(\"td\", null, \"A quantity or statistical measure that for a given population is fixed, such as a mean or a variance. The parameter is used in some general distribution or frequency function (e.g., a Normal Distribution) to make it descriptive of that population.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Prior Distribution\"), mdx(\"td\", null, \"The probability distribution that expresses beliefs about an unknown quantity before testing takes place. Within AFOTEC this distribution could be based on the performance of a similar system, the performance of a previous version of a system, or SME knowledge.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Posterior Distribution\"), mdx(\"td\", null, \"The conditional probability distribution that describes an unknown quantity after test or experimental data is taken into account.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Projection\"), mdx(\"td\", null, \"A property of factorial designs where the degree of replication doubles when a design column is removed (such as when a factor is determined to be insignificant). With fractional factorial designs the degree of fractionation is reduced.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Qualitative\"), mdx(\"td\", null, \"A term used to describe data that is descriptive or subjective; the values are ordinal or nominal in nature; e.g., red, blue and green.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Quantitative\"), mdx(\"td\", null, \"A term used to describe data that is measured on a numeric or quantitative scale; interval and ratio scales are quantitative. The data may be discrete or continuous.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Randomization\"), mdx(\"td\", null, \"A principle of DOE used to average out the effects of unknown and uncontrollable nuisance factors.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Regression\"), mdx(\"td\", null, \"A statistical process to model the change in the mean value of a continuous dependent variable (e.g., measure) as the values of one or more continuous independent variables change.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Replication\"), mdx(\"td\", null, \"Replication is an independent, repeated run of a factor level combination (as opposed to measuring the result of a single test run twice\\u2014this is a repeated measure.) In JMP, requesting one replicate will create a design with two of each design point.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Resolution\"), mdx(\"td\", null, \"An indication of the ability to independently estimate main effects and interactions in a fractional factorial design.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Run\"), mdx(\"td\", null, \"One combination of factor levels used for collecting data on one or more measures; a test design point.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Sample\"), mdx(\"td\", null, \"A set of data collected from a population. In operational test, it is usually impossible to test the entire population of a new system, so a sample is tested.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Screening Designs\"), mdx(\"td\", null, \"Designs that focus on the identification of active main effects. The goal is to reduce an initially large list of potential factors to only those that are influential on the response variable. Using screening designs decreases the size of subsequent tests conducted to estimate two-factor interactions or higher-order effects.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Sparsity-of-Effects Principle\"), mdx(\"td\", null, \"The principle that a system is usually dominated by main effects and low-order interactions. Thus it is very likely that main effects (single factor) and two-factor interactions are the only significant effects when analyzing data from a test; higher-order interactions such as three-factor interactions are very rare.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Stochastic\"), mdx(\"td\", null, \"Randomly determined; Any process or system that has a random probability distribution or pattern which may be analyzed statistically, but not predicted perfectly.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Strength\"), mdx(\"td\", null, \"An integer between 2 and the total number of factors in the test design. For combinatorial designs, strength t means that for every possible subset of t factors, every possible t-tuple of level combinations is present in the design at least one time.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"t-tuple\"), mdx(\"td\", null, mdx(\"p\", null, \"A combination of the levels of t factors selected from a design. Suppose there is a design with four two-level factors with levels coded as +1 and -1.\"), mdx(\"p\", null, \"There are four possible 2-tuples, e.g. (+1,-1).\"), mdx(\"p\", null, \"There are eight possible 3-tuples, e.g. (+1,-1,+1).\"), mdx(\"p\", null, \"There are sixteen possible 4-tuples, e.g. (+1,-1,+1,+1).\"))))), mdx(\"h1\", null, \"Test Design Guidance\"), mdx(\"p\", null, \"The following documents have more information and guidance from the\\nDepartment of Defense and the Air Force on the use of Design of\\nExperiments in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. They are all accessible on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint or\\nin the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Analyst and Engineer Community.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \" between the service Operational Test Agencies (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Army Test and Evaluation Command\"\n }, \"ATEC\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test and Evaluation Force\"\n }, \"OPTEVFOR\"), \",\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", JTIC and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \"), 20 Feb 09, Using Design of Experiments for\\nOperational Test and Evaluation\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo, 19 Oct 10, Guidance on the use of Design of\\nExperiments (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Energy OR Design of Experiments\"\n }, \"DOE\"), \") in Operational Test and Evaluation\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo, 23 Jul 13, Best Practices for Assessing the\\nStatistical Adequacy of Experimental Designs Used in Operational\\nTest and Evaluation\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\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 Guide,\\\" Apr 20\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Institute for Defense Analyses paper, Nov 14, Power Analysis\\nTutorial for Experimental Design Software\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Operational Test Information File, 17 Feb 15, Statistical\\nPower for Test Designs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense Instruction\"\n }, \"DODI\"), \" 5000.02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Operation of the Defense Acquisition System\"), \" , 7 Jan\\n15\"))), mdx(\"h1\", null, \"Technical References and Citations\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Best Practices for Assessing the Statistical\\nAdequacy of Experimental Designs Used in Operational Test and\\nEvaluation.\"), \" Washington, D.C.: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \".Freeman, L. J., Johnson, T. H., &\\nSimpson, J. R. (2014). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Power Analysis Tutorial for Experimental Design\\nSoftware.\"), \" Alexandria, Virginia: INSTITUTE FOR DEFENSE ANALYSES.Hartman,\\nM. (2014, August 19). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Design Comparison and Slection Method Best\\nPractice.\"), \" Retrieved March 3, 2015, from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Institute of Technology\"\n }, \"AFIT\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Scientific Test and Analysis Techniques\"\n }, \"STAT\"), \" COE:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.afit.edu/docs/Test%20Design%20Comparison%20and%20Selection-Best%20Practice.pdfKacker\"\n }, \"http://www.afit.edu/docs/Test%20Design%20Comparison%20and%20Selection-Best%20Practice.pdfKacker\"), \",\"), mdx(\"p\", null, \"R. N., Kuhn, R. D., & Lawrence, J. F. (2013). Combinatorial testing for\\nsoftware: An adaptation of design of experiments. \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Measurement, 46\"), \" (9),\\n3745-3752.Kruschke, J. K. (2012, May 31). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Bayesian Estimation\\nsupercedes the t test.\"), \" Retrieved March 17, 2015, from Indiana\\nUniversity, Bloomington:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.indiana.edu/%5C~kruschke/BEST/BEST.pdfKuhn\"\n }, \"http://www.indiana.edu/\\\\~kruschke/BEST/BEST.pdfKuhn\"), \", K. L. (2010).\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Practical Combinatorial Testing.\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Institute of Standards and Technology\"\n }, \"NIST\"), \", U.S. Department of\\nCommerce.Montgomery, D. C. (2009). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Design and Analysis of Experiments,\\n7th Edition.\"), \" New York: Wiley and Sons.Myers, M. A.-C. (2009). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Response\\nSurface Methodology.\"), \" Hoboken, NJ: John Wiley & Sons, Inc.NIST1. (n.d.).\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Engineering Statistics Handbook\"), \" . Retrieved from\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://math.nist.gov/coveringarrays/coveringarray.htmlNIST2\"\n }, \"http://math.nist.gov/coveringarrays/coveringarray.htmlNIST2\"), \". (n.d.).\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Engineering Statistics Handbook\"), \" . Retrieved from What are John\\\\'s 3/4\\nfractional factorial designs?:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.itl.nist.gov/div898/handbook/pri/section5/pri57.htmNIST3\"\n }, \"http://www.itl.nist.gov/div898/handbook/pri/section5/pri57.htmNIST3\"), \".\\n(n.d.). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Plackett-Burman Designs\"), \" . Retrieved from Engineering\\nStatistics Handbook:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri335.htmNIST4\"\n }, \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri335.htmNIST4\"), \".\\n(n.d.). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Central Composite Designs (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Combat Capability Document\"\n }, \"CCD\"), \")\"), \" . Retrieved from Engineering\\nStatistics Handbook:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri3361.htmOrtiz\"\n }, \"http://www.itl.nist.gov/div898/handbook/pri/section3/pri3361.htmOrtiz\"), \",\\nF. (2014). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Dealing with Categorical Data Types in a Designed Experiment\\nPart II: Sizing a Designed Experiment when Using a Binary Response.\"), \"\\nRetrieved March 3, 2015, from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Institute of Technology\"\n }, \"AFIT\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Scientific Test and Analysis Techniques\"\n }, \"STAT\"), \" COE:\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdfRosenbaum\"\n }, \"http://www.afit.edu/docs/6.%20Dealing%20with%20Categorical%20Data%20(Part%202%20of%203).pdfRosenbaum\"), \",\\nP. R. (2002). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Observational Studies Second Edition.\"), \" New York:\\nSpringer-Verlag Inc. .Winkler, R. L. (2003). \"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"An Introduction to\\nBayesian Inference and Decision, 2nd Edition.\"), \" Gainsville, FL:\\nProbabalistic Publishing (\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"http://www.decisions-books.com\"\n }, \"www.decisions-books.com\"), \").\"), mdx(\"h1\", null, \"Footnotes\"), mdx(\"h1\", null, \"fn1\"), mdx(\"ol\", null, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Quantitative -- A term used to describe data that is measured on a\\nnumeric or quantitative scale; interval and ratio scales are\\nquantitative. The data may be discrete or continuous. \")), mdx(\"h1\", null, \"fn2\"), mdx(\"ol\", {\n \"start\": 2\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Qualitative -- A term used to describe data that is descriptive or\\nsubjective; the values are ordinal or nominal in nature; e.g., red,\\nblue and green. \")), mdx(\"h1\", null, \"fn3\"), mdx(\"ol\", {\n \"start\": 3\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Population parameter -- A quantity or statistical measure that for a\\ngiven population is fixed, such as a mean or a variance. The\\nparameter is used in some general distribution or frequency function\\n(e.g., a Normal Distribution) to make it descriptive of that\\npopulation. \")), mdx(\"h1\", null, \"fn4\"), mdx(\"ol\", {\n \"start\": 4\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Estimation -- An attempt to gain insight about an unknown population\\nparameter based on information obtained from sample data. At \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nwe typically estimate means and variances of measures, factor\\neffects, and proportions of failures. \")), mdx(\"h1\", null, \"fn5\"), mdx(\"ol\", {\n \"start\": 5\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Sample -- A set of data collected from a population. \")), mdx(\"h1\", null, \"fn6\"), mdx(\"ol\", {\n \"start\": 6\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Factor -- An independent variable which may affect the performance\\nof a system when its levels are changed. \")), mdx(\"h1\", null, \"fn7\"), mdx(\"ol\", {\n \"start\": 7\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Level -- A specific setting of a factor during a test or experiment. \")), mdx(\"h1\", null, \"fn8\"), mdx(\"ol\", {\n \"start\": 8\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Run -- One combination of factor levels used for collecting data on\\none or more measures; a test design point.\")), mdx(\"h1\", null, \"fn9\"), mdx(\"ol\", {\n \"start\": 9\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Effect - The average change in a response variable produced by\\nchanging the level of a factor. \")), mdx(\"h1\", null, \"fn10\"), mdx(\"ol\", {\n \"start\": 10\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Main Effect - The effect of a factor (independent variable) on a\\nmeasure (dependent variable) averaging across the levels of the\\nother factors. \")), mdx(\"h1\", null, \"fn11\"), mdx(\"ol\", {\n \"start\": 11\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Interaction -- A situation where the effect of one factor on a\\nresponse depends on the level of another factor. \")), mdx(\"h1\", null, \"fn12\"), mdx(\"ol\", {\n \"start\": 12\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Factorial Design -- A test plan consisting of two or more factors,\\neach with discrete possible values (or levels). A full factorial is\\na design whose experimental units (runs) take on all possible\\ncombinations of these levels. A design which includes a\\nstrategically selected subset of the possible combinations is called\\na fractional factorial. \")), mdx(\"h1\", null, \"fn13\"), mdx(\"ol\", {\n \"start\": 13\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Balance -- A column in a test design matrix is balanced if every\\nfactor level occurs an equal number of times. A test design is\\nbalanced if every possible factor level combination occurs an equal\\nnumber of times. \")), mdx(\"h1\", null, \"fn14\"), mdx(\"ol\", {\n \"start\": 14\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Orthogonal - A test design is orthogonal if each factor can be\\nevaluated independently of all the other factors. This is possible\\nif, for the test runs involving any level of any factor, the levels\\nof the other factors are present in equal amounts. When an\\northogonal test design has two-level factors coded -1 and +1, the\\ninner (dot) product of any two columns is 0.\")), mdx(\"h1\", null, \"fn15\"), mdx(\"ol\", {\n \"start\": 15\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Disallowed Combinations - A combination of the levels of two or more\\nfactors that cannot be feasibly executed together in a test run. \")), mdx(\"h1\", null, \"fn16\"), mdx(\"ol\", {\n \"start\": 16\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Center Point -- A test run where every continuous factor is set to\\nthe value halfway between its minimum and maximum factor levels. \")), mdx(\"h1\", null, \"fn17\"), mdx(\"ol\", {\n \"start\": 17\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Projection -- A property of factorial designs where the degree of\\nreplication doubles when a design column is removed (such as when a\\nfactor is determined to be insignificant). With fractional factorial\\ndesigns the degree of fractionation is reduced. \")), mdx(\"h1\", null, \"fn18\"), mdx(\"ol\", {\n \"start\": 18\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Active Effect -- A term used to describe a main effect (factor) or\\ninteraction that causes a statistically significant difference in\\nthe response variable when the factor levels are changed. \")), mdx(\"h1\", null, \"fn19\"), mdx(\"ol\", {\n \"start\": 19\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Sparsity-of-Effects Principle -- The principle that a system is\\nusually dominated by main effects and low-order interactions. Thus\\nit is very likely that main effects (single factor) and two-factor\\ninteractions are the only significant effects when analyzing data\\nfrom a test; higher-order interactions such as three-factor\\ninteractions are very rare. \")), mdx(\"h1\", null, \"fn20\"), mdx(\"ol\", {\n \"start\": 20\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Correlation -- A statistical measure on a scale from -1 to 1 that\\nindicates how close two variables are to having a linear\\nrelationship with each other. Two factors are perfectly correlated\\nwhen the value of one factor's level can be precisely determined by\\nknowing the value of the other factor's level. \")), mdx(\"h1\", null, \"fn21\"), mdx(\"ol\", {\n \"start\": 21\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Aliasing - A condition where the effect estimate of one factor\\nincludes the influence of one or more other effects (main effect or\\nhigher-order interactions). \")), mdx(\"h1\", null, \"fn22\"), mdx(\"ol\", {\n \"start\": 22\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Confounding -- Synonymous with aliasing: a condition where the\\neffect estimate of one factor includes the influence of one or more\\nother effects (main effect or higher-order interactions). \")), mdx(\"h1\", null, \"fn23\"), mdx(\"ol\", {\n \"start\": 23\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Resolution -- An indication of the ability to independently estimate\\nmain effects and interactions in a fractional factorial design. \")), mdx(\"h1\", null, \"fn24\"), mdx(\"ol\", {\n \"start\": 24\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Screening design -- Designs that focus on the identification of\\nactive main effects. The goal is to reduce an initially large list\\nof potential factors to only those that are influential on the\\nresponse variable. Using screening designs decreases the size of\\nsubsequent test designs used to estimate two factor interactions or\\nhigher-order effects.\")), mdx(\"h1\", null, \"fn25\"), mdx(\"ol\", {\n \"start\": 25\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Optimal Designs -- A test design whose levels are combined in a way\\nthat optimizes some statistical design quality criterion that is a\\nfunction of the design matrix.\")), mdx(\"h1\", null, \"fn26\"), mdx(\"ol\", {\n \"start\": 26\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Linear Regression -- A statistical process to model the change in\\nthe mean value of a continuous dependent variable (e.g., measure) as\\nthe values of one or more continuous independent variables change. \")), mdx(\"h1\", null, \"fn27\"), mdx(\"ol\", {\n \"start\": 27\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Augmentation -- The process of strategically adding new runs to an\\nexisting test design after some data has been collected. \")), mdx(\"h1\", null, \"fn28\"), mdx(\"ol\", {\n \"start\": 28\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Deterministic -- A deterministic system or model will always produce\\nthe same output from a given starting condition (level settings of\\nthe independent variables.) \")), mdx(\"h1\", null, \"fn29\"), mdx(\"ol\", {\n \"start\": 29\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Distribution -- A table or function showing all the possible values\\nof a data set and how often they occur. \")), mdx(\"h1\", null, \"fn30\"), mdx(\"ol\", {\n \"start\": 30\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, mdx(\"em\", {\n parentName: \"li\"\n }, \"t\"), \" -tuples - A combination of the levels of t factors selected from\\na design. Suppose there is a design with four two-level factors with\\nlevels coded as +1 and -1. There are four possible 2-tuples, e.g.\\n(+1,-1). There are eight possible 3-tuples, e.g. (+1,-1,+1). There\\nare sixteen possible 4-tuples, e.g. (+1,-1,+1,+1). \")), mdx(\"h1\", null, \"fn31\"), mdx(\"ol\", {\n \"start\": 31\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Strength - An integer between 2 and the total number of factors in\\nthe test design. For combinatorial designs, strength \", mdx(\"em\", {\n parentName: \"li\"\n }, \"t\"), \" means that\\nfor every possible subset of t factors, every possible \", mdx(\"em\", {\n parentName: \"li\"\n }, \"t\"), \" -tuple of\\nlevel combinations is present in the design at least one time. \")), mdx(\"h1\", null, \"fn32\"), mdx(\"ol\", {\n \"start\": 32\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Coverage - Describes the percentage of possible factor level\\ncombinations (after removing the disallowed combinations from the\\ncomplete combination space) that a combinatorial design includes at\\na given strength.\")), mdx(\"h1\", null, \"fn33\"), mdx(\"ol\", {\n \"start\": 33\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Stochastic - Randomly determined; any process or system that has a\\nrandom probability distribution or pattern which may be analyzed\\nstatistically, but not predicted perfectly.\")), mdx(\"h1\", null, \"fn34\"), mdx(\"ol\", {\n \"start\": 34\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"D-Efficiency is calculated as follows: \", mdx(\"span\", {\n parentName: \"li\",\n \"className\": \"inlineMath\"\n }, \"= 100 \\\\times \\\\left( \\\\frac{\\\\left| X^{'}X \\\\right|^{\\\\frac{1}{p}}}{N} \\\\right)\"), \" where p is the number of columns in X matrix and N\\nis the number of runs. \")), mdx(\"h1\", null, \"fn35\"), mdx(\"ol\", {\n \"start\": 35\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"G-Efficiency is calculated as follows: \", mdx(\"span\", {\n parentName: \"li\",\n \"className\": \"inlineMath\"\n }, \"= 100 \\\\times \\\\left( \\\\frac{\\\\sqrt{\\\\frac{p}{N}}}{\\\\sigma\\\\_{M}} \\\\right)\"), \" where p is the number of columns in X matrix, N is the\\nnumber of runs and \", \"[ \", mdx(\"em\", {\n parentName: \"li\"\n }, \"\\u03C3\"), \" ~\", mdx(\"em\", {\n parentName: \"li\"\n }, \"M\"), \"~ ]\", \"{.math .inline} is the maximum\\nstandard error for prediction across the space. The X matrix is the\\nde-correlated X matrix. \")), mdx(\"h1\", null, \"fn36\"), mdx(\"ol\", {\n \"start\": 36\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"A-Efficiency is calculated as follows: \", mdx(\"span\", {\n parentName: \"li\",\n \"className\": \"inlineMath\"\n }, \"= 100 \\\\times \\\\left( \\\\frac{p}{\\\\text{trace}\\\\left( N \\\\times \\\\left( X^{'}X \\\\right)^{- 1} \\\\right)} \\\\right)\"), \" where p is the\\nnumber of columns in X matrix and N is the number of runs. The X\\nmatrix is the de-correlated X matrix. \")), mdx(\"h1\", null, \"fn37\"), mdx(\"ol\", {\n \"start\": 37\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"ANOVA -- A mathematical process for evaluating the variation in data\\nbetween groups and within groups in order to determine whether there\\nis a differences between the group means. This procedure can be used\\nto compare multiple systems, or determine if there are differences\\nin the mean response between levels of a factor. \")), mdx(\"h1\", null, \"fn38\"), mdx(\"ol\", {\n \"start\": 38\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"An orthogonal array may not exist for the required number of factors\\nand levels \", mdx(\"a\", {\n parentName: \"li\",\n \"href\": \"#fnref38\"\n }, \"\\u21A9\\uFE0E\"))), mdx(\"h1\", null, \"fn39\"), mdx(\"ol\", {\n \"start\": 39\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"All factors must be continuous \")), mdx(\"h1\", null, \"fn40\"), mdx(\"ol\", {\n \"start\": 40\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Strength 4 and higher \")), mdx(\"h1\", null, \"fn41\"), mdx(\"ol\", {\n \"start\": 41\n }, mdx(\"li\", {\n parentName: \"ol\"\n }, \"Resolution VI or higher is required to analyze 3 factor interactions \")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#overview","title":"OVERVIEW"},{"url":"#elements-of-the-test-planning-process","title":"ELEMENTS OF THE TEST PLANNING PROCESS","items":[{"url":"#critical-operational-issues-and-operations","title":"Critical Operational Issues and Operations"},{"url":"#response-variables","title":"Response Variables"}]},{"url":"#factors-levels-and-prioritization","title":"Factors, Levels, and Prioritization"},{"url":"#goals-and-types-of-test","title":"GOALS AND TYPES OF TEST"},{"url":"#characterize","title":"Characterize"},{"url":"#compare","title":"Compare"},{"url":"#problem-identification","title":"Problem Identification"},{"url":"#types-of-test-designs","title":"TYPES OF TEST DESIGNS"},{"url":"#factorials","title":"Factorials","items":[{"url":"#fractional-factorial","title":"Fractional Factorial"},{"url":"#creating-fractional-factorial-designs-in-jmp-13","title":"Creating Fractional Factorial Designs in JMP 13:"}]},{"url":"#optimal-designs-computer-generated-designs","title":"Optimal Designs (Computer Generated Designs)","items":[{"url":"#creating-a-d-optimal-design-in-jmp-13","title":"Creating a D-Optimal design in JMP 13:"}]},{"url":"#augmented-designs","title":"Augmented Designs"},{"url":"#designs-for-computer-experiments","title":"Designs for Computer Experiments","items":[{"url":"#space-filling-designs","title":"Space-Filling Designs"}]},{"url":"#test-designs-for-comparing-systems","title":"Test Designs for Comparing Systems"},{"url":"#test-designs-for-problem-identification","title":"Test Designs for Problem Identification"},{"url":"#combinatorial-designs-covering-arrays","title":"Combinatorial Designs (Covering Arrays)","items":[{"url":"#creating-a-combinatorial-design-in-acts","title":"Creating a Combinatorial Design in ACTS:"},{"url":"#example-of-a-combinatorial-design","title":"Example of a Combinatorial Design"}]},{"url":"#demonstrations","title":"Demonstrations"},{"url":"#cases","title":"Cases"},{"url":"#observational-studies","title":"Observational Studies"},{"url":"#test-design-measures-of-merit","title":"TEST DESIGN MEASURES OF MERIT"},{"url":"#power","title":"Power"},{"url":"#optimality-efficiency","title":"Optimality (Efficiency)"},{"url":"#correlation-multicollinearity","title":"Correlation (Multicollinearity)"},{"url":"#prediction-variance","title":"Prediction Variance"},{"url":"#comparing-measures-of-merit","title":"Comparing Measures of Merit"},{"url":"#the-three-principles-of-design-of-experiments","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"},{"url":"#randomization","title":"Randomization"},{"url":"#replication","title":"Replication"},{"url":"#blocking","title":"Blocking"},{"url":"#typical-situations","title":"TYPICAL SITUATIONS","items":[{"url":"#how-do-i-select-a-design","title":"How do I Select a Design?"},{"url":"#i-have-factors-that-are-hard-to-change","title":"I Have Factors that Are Hard to Change"},{"url":"#can-i-combine-developmental-test-and-operational-test-data","title":"Can I Combine Developmental Test and Operational Test Data?"},{"url":"#i-have-disallowed-combinations","title":"I Have Disallowed Combinations"},{"url":"#my-power-is-too-low","title":"My Power Is Too Low"},{"url":"#i-have-factor-levels-that-depend-on-other-factor-levels","title":"I Have Factor Levels that Depend on Other Factor Levels"}]},{"url":"#best-practicespitfalls-in-test-design","title":"Best Practices/Pitfalls in Test Design"},{"url":"#pitfalls","title":"Pitfalls:"},{"url":"#appendices","title":"Appendices"},{"url":"#test-design-guidance","title":"Test Design Guidance"},{"url":"#technical-references-and-citations","title":"Technical References and Citations"},{"url":"#footnotes","title":"Footnotes"},{"url":"#fn1","title":"fn1"},{"url":"#fn2","title":"fn2"},{"url":"#fn3","title":"fn3"},{"url":"#fn4","title":"fn4"},{"url":"#fn5","title":"fn5"},{"url":"#fn6","title":"fn6"},{"url":"#fn7","title":"fn7"},{"url":"#fn8","title":"fn8"},{"url":"#fn9","title":"fn9"},{"url":"#fn10","title":"fn10"},{"url":"#fn11","title":"fn11"},{"url":"#fn12","title":"fn12"},{"url":"#fn13","title":"fn13"},{"url":"#fn14","title":"fn14"},{"url":"#fn15","title":"fn15"},{"url":"#fn16","title":"fn16"},{"url":"#fn17","title":"fn17"},{"url":"#fn18","title":"fn18"},{"url":"#fn19","title":"fn19"},{"url":"#fn20","title":"fn20"},{"url":"#fn21","title":"fn21"},{"url":"#fn22","title":"fn22"},{"url":"#fn23","title":"fn23"},{"url":"#fn24","title":"fn24"},{"url":"#fn25","title":"fn25"},{"url":"#fn26","title":"fn26"},{"url":"#fn27","title":"fn27"},{"url":"#fn28","title":"fn28"},{"url":"#fn29","title":"fn29"},{"url":"#fn30","title":"fn30"},{"url":"#fn31","title":"fn31"},{"url":"#fn32","title":"fn32"},{"url":"#fn33","title":"fn33"},{"url":"#fn34","title":"fn34"},{"url":"#fn35","title":"fn35"},{"url":"#fn36","title":"fn36"},{"url":"#fn37","title":"fn37"},{"url":"#fn38","title":"fn38"},{"url":"#fn39","title":"fn39"},{"url":"#fn40","title":"fn40"},{"url":"#fn41","title":"fn41"}]},"parent":{"__typename":"File","relativePath":"fn_guides/analyst_test_design_guide.md"},"frontmatter":{"metaTitle":"Analyst Test Design Guide","metaDescription":"Analyst Test Design Guide"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"c74500cd-1ebf-56c9-942f-23d8e3775c83"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/fn_guides/editing_reports_guide/page-data.json b/sites/oteguide/page-data/fn_guides/editing_reports_guide/page-data.json deleted file mode 100644 index 9d0a8c56..00000000 --- a/sites/oteguide/page-data/fn_guides/editing_reports_guide/page-data.json +++ /dev/null @@ -1 +0,0 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides/editing_reports_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"f83c0915-7e80-5546-897f-dc21b54c3887","title":"Editing Guide","slug":"/fn_guides/editing_reports_guide"},"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\": \"Editing Guide\",\n \"metaTitle\": \"Editing Guide\",\n \"metaDescription\": \"Editing Guide\"\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(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\\"I cannot think of anybody who doesn't need an editor, even though\\nsome people claim they don't.\\\" \", \"~\", \" Toni Morrison\")), mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\\"Clever words are not as good as straight talk.\\\" \", \"~\", \" Chinese proverb\")), mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\\"Like stones, words are laborious and unforgiving, and the fitting of\\nthem together, like the fitting of stones, demands great patience and\\nstrength of purpose and particular skill.\\\" \", \"~\", \" Edmund Morrison\"))), mdx(\"p\", null, \"Last Updated/Reviewed: 08 December 2020\"), 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, \"PURPOSE\"), mdx(\"p\", null, \"This guide was developed for technical editors, but will help all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\npersonnel write and edit final test plans and reports that meet our goal\\nof providing relevant, credible, and timely feedback to the acquisition\\ncommunity and Air Force leaders.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"*Note\"), \" : This editing guide applies to final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test plans and\\nreports. It is not designed to take the place of, nor conflict with,\\nwriting guidance for other products, such as OPRs/EPRs, memos, or\\nother \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test products. Please adhere to the writing guidelines,\\nauthorities, and templates that apply to the specific product you are\\nproducing.*\")), mdx(\"p\", null, \"This guide follows the grammar and punctuation rules from the following\\nauthorities: Air Force Handbook (AFH) 33-337, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Tongue and Quill\"), \" , 27\\nMay 15 (Incorporating Change 1, 19 Nov 15), and the Air University\\nPress, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Air University Style and Author Guide\"), \" (Maxwell \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Base\"\n }, \"AFB\"), \" AL, 2005),\\nunless otherwise indicated. While you should explore and review\\nreference materials you feel are helpful in developing your editing\\nskills, the rules outlined herein take precedence over other\\nwriting/editing guidance.\"), mdx(\"h1\", null, \"Executive Summary, Body, and Appendices\"), mdx(\"p\", null, \"Edit the executive summary, the body, and the appendices as separate\\ndocuments. The appendices will be created first because they contain the\\ntechnical information and details of the assessment or evaluation. In\\nthe appendices, symbols, equations, and technical terms are appropriate,\\njust as they are in tables. The body is a synopsis of the information\\ncontained in the appendices. It is written as a formal document in which\\nsymbols, abbreviations, and technical terms are spelled out and is\\nintended for a wider audience.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Executive Summary\"), \" . While the executive summary is usually written\\nlast, it is the most crucial part of the document because it is intended\\nfor and read by the wider acquisition community. If written as intended,\\nthe executive summary will capture the critical components of the\\nassessment or evaluation in a brief but thorough summary.\"), mdx(\"p\", null, \"The executive summary is written from the Commander's perspective, as\\nthough he or she is personally addressing the audience. It describes the\\nsystem under test, type of test, decision maker, and decision supported,\\nand summarizes the system's effectiveness, suitability, mission\\ncapability, critical deficiencies, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s recommendations (in\\norder of their significance) to correct those deficiencies. It is\\nwritten as a formal document in which symbols, abbreviations, and\\ntechnical terms are spelled out, and although it is acceptable to use\\nacronyms in the executive summary, writers should limit their use to\\npromote a smoother read.\"), mdx(\"h1\", null, \"Consistency is Key\"), mdx(\"p\", null, \"In regards to subjective writing preferences, ensure the author applies\\nthem consistently, i.e., benchmark, bench mark, and bench-mark should\\nnot appear in the same document. When such variations occur, choose the\\nmost frequently used or best option and change other instances to match.\"), mdx(\"h1\", null, \"One Voice\"), mdx(\"p\", null, \"Several different test team members collaborate on writing each plan or\\nreport. Edit the mechanics of each part of the document separately, but\\nit is important to read the plan or report as a whole document to\\nconfirm that it reads as \\\"one voice\\\" rather than as a conglomeration of\\ndifferent sections by different authors.\"), mdx(\"h1\", null, \"Templates\"), mdx(\"p\", null, \"Templates for each type of test plan and report are posted on\\nSharePoint. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" encourages the use of templates because they are a\\ngood guide to ensure the test team includes all necessary planning and\\nreporting elements. Test teams may find it necessary to deviate from the\\ntemplates and include different information or exclude information not\\npertinent to their program. They should feel free to innovate as needed\\nas long as they meet the ultimate goal of creating a comprehensive\\ndocument that meets \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s planning and reporting obligations.\\nTemplates include blue instructional text to assist the test team in\\npopulating various sections, but if writers have questions not covered\\nin the instructional text, have them contact A-3 for additional\\nguidance.\"), mdx(\"p\", null, \"The templates are dynamic and change as guidance and reporting\\nrequirements change. A-3 attempts to make template changes in real time,\\nbut this is not always possible. If you are unsure whether a template\\nreflects the latest changes, contact the A-3 technical editor.\"), mdx(\"h1\", null, \"Microsoft Word Options\"), mdx(\"p\", null, \"Set the following \\\"options\\\" to ensure Microsoft Word works in harmony\\nwith our templates. Setting these options from the start will solve a\\nlot of formatting problems before they begin.\"), mdx(\"h2\", null, \"Display:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"All formatting marks\")), mdx(\"h2\", null, \"Proofing:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"AutoCorrect: remove ALL checks\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"AutoFormat: remove all checks except for \\\"smart quotes\\\" ( \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Note\"), \" :\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not use superscript for ordinals; superscript is only\\nused for fractional factorial notations in factor tables)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"AutoFormat As You Type: remove all checks except for \\\"smart quotes\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Spelling and Grammar Settings:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Grammar and style options: Require (comma: always);\\n(punctuation: inside); (spaces:\\xA01)\")))), mdx(\"h2\", null, \"Advanced:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Enable Click and Type\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Default Paragraph Style: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Body\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Insert pictures \\\"in line with text\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Cut, copy, and paste\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Show Paste Options button when content is pasted\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Use smart cut and paste (Word 2002-2010)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Pasting between documents when style definitions conflict---Use\\nDestination Styles (Default)\")))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Show Bookmarks\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Field Shading--always\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Style area pane width in Draft and Outline views--2\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Compatibility should be Word 2010 \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"(DO NOT check any of the layout\\noptions)\")))), mdx(\"h1\", null, \"Focus Areas\"), mdx(\"p\", null, \"Enforce the following standards to ensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" produces uniform\\ndocuments. These areas are not listed in order of importance, but are an\\noverall view of the editing process.\"), mdx(\"h1\", null, \"Styles\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" templates are designed with unique Microsoft Word styles that\\nwork in tandem with the page numbering and the table of contents. That\\nis why it is critical to ensure the styles are not removed or corrupted\\nduring the writing process. Unless a writer deliberately changes or\\ncorrupts a style by deleting a heading or subheading, the templates are\\nuser-friendly and low maintenance. The body style is designed to be\\n\\\"justified\\\" and to have the optimal amount of white space to make it\\neasy to read and distinguish between paragraphs. \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses one space\\nafter end-of-sentence punctuation because that prevents excessive\\nspreading between letters and words when using justified alignment\"), \" .\"), mdx(\"p\", null, \"Problems can arise when writers copy and paste information from other\\nsources into the template document, which can introduce styles from that\\nsource. In those cases, you will have to clear the styles and reapply\\nthe appropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles. Teach writers to use the \\\"use destination\\nstyles\\\" option on the pasting clipboard to eliminate this problem.\"), mdx(\"p\", null, \"To confirm the styles are correct and uncorrupted, open the document in\\nDraft view. Reapply appropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles where necessary. Modify\\ncorrupted styles if it is something simple to correct such as left align\\nversus justified, tab spacing, font size, etc. If more than one style is\\ncorrupt or you cannot modify them easily, use the following steps to\\nimport styles from a document in which \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles are sound and\\nuncorrupted (i.e., plan or report template):\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click on the third icon in bottom left corner of \\\"Styles\\\" pane\\ncalled \\\"Manage Styles.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \\\"Import/Export\\\" on bottom left corner of the Edit tab.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"On the right side pane of the \\\"Organizer\\\" window that opens, close\\nthe \\\"In Normal\\\" file and open a document with all the uncorrupted\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles by clicking \\\"open file.\\\" Locate and open that file.\\nAll the styles from that document will populate the right side pane.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Copy all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles you wish to replace from the right side to\\nthe \\\"to Document 1\\\" left side. (Note: if you have set your \\\"Normal\\\"\\ntemplate to contain \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles \", \"[\", \"recommended\", \"]\", \", just copy the\\nnecessary styles from there to the \\\"to Document 1\\\" left side and\\nomit the step of closing the \\\"Normal\\\" file and finding a file with\\nuncorrupted \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles.)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Click \\\"yes\\\" or \\\"yes to all\\\" when prompted as to whether you want to\\noverwrite the existing styles in the document.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Close the \\\"Normal\\\" file or the file you copied styles from on the\\nright side pane.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Close out of the \\\"Organizer\\\" window.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The corrected styles will appear in your style pane.\"))), mdx(\"h1\", null, \"Acronyms\"), mdx(\"p\", null, \"Define an acronym the first time it appears in each section (i.e.,\\nexecutive summary, body, appendices \", \"[\", \"as a whole, not each appendix as a\\nseparate section\", \"]\", \"), then use the acronym thereafter. Edit these three\\ndistinct parts of the plan or report as separate documents.\"), mdx(\"p\", null, \"Add all acronyms in the document to the acronym table in the designated\\nappendix. If an acronym is only used one or two times, delete it from\\nthe document and the acronym table and spell it out.\"), mdx(\"p\", null, \"Define acronyms in tables and figures in the acronym table, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"not within\\nthe table or figure\"), \" ; the only exception is a measure table that\\ndisplays a \\\"mean\\\" as the metric. To help readers make the connection to\\na standard term (i.e., \\\"mean time between failures\\\"), add the standard\\nacronym in parenthesis following the measure title, then define it below\\n\\\"\", \"*\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or supports \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or \\\\^ Identified Standard\\\" if applicable (or in a\\nmerged row at the bottom of the table as shown in the following\\nexample). Then, add the acronym to the acronym table.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"(FOUO)\"), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operational Capability: Reliability\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Measure\"), mdx(\"td\", null, \"Metric\"), mdx(\"td\", null, \"Threshold\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOS 3.8: Time Between Failures (MTBF)\"), mdx(\"td\", null, \"Mean\"), mdx(\"td\", null, \">= 8,736 hours\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MTBF\\u2013mean time between failures\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, \"Some acronyms are more easily recognized than the words they represent\\n(e.g., NASA, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"North Atlantic Treaty Organization\"\n }, \"NATO\"), \"). In those cases, do not remove the acronym from the\\ndocument, nor from the acronym table even if it is used only once. This\\nis a judgment call so consult your test team's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \", \", 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\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \" if in\\ndoubt as to whether you should remove a particular acronym.\"), mdx(\"p\", null, \"Acronyms use the same vowel/consonant rules as regular words (i.e., use\\n\\\"a\\\" before a consonant; use \\\"an\\\" before a vowel), except that with\\nacronyms the beginning \\\"sound\\\" rather than the beginning \\\"letter\\\" is\\nwhat determines the article you will use. If the beginning sound is a\\nvowel sound, you will use \\\"an.\\\" If it is a consonant sound, use \\\"a.\\\"\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \" report (beginning sound--long o vowel sound)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"a NASA rocket (beginning sound--consonant n)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \" (beginning sound--short e vowel sound)\"))), mdx(\"p\", null, \"Follow regular capitalization rules when defining acronyms and\\ncapitalize only those words that are proper nouns. The only exception to\\nthis rule is the acronym table, which should use the following \\\"title\\ncase\\\" capitalization rules for uniformity:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capitalize the principal words, including prepositions and\\nconjunctions of four or more letters.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capitalize an article---the, a, an---or words of fewer than four\\nletters if it is the first or last word in a title.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Performing the acronym scrub is the most time-intensive part of the\\nedit, but it must be done, and is ultimately the technical editor's\\nresponsibility. Do not cheat!\")), mdx(\"p\", null, \"Perform a spell check, but before you begin, go into Microsoft Word\\noptions/Proofing and uncheck the Custom Dictionary \\\"Custom Dic\\\" button;\\nselect \\\"English (United States)\\\" as your language.\"), mdx(\"p\", null, \"Make sure each acronym spell-check catches was defined in the acronym\\ntable. If not, add it and define it. Begin with the first acronym in the\\ntable and perform the following:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Highlight the acronym\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Copy it (ctrl c)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Open find (ctrl f)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Paste (ctrl v)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Go to top of doc (ctrl home)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Enter \\\"find next\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Make sure the acronym is defined the first time it shows up in the\\nbody and appendices, and that the definition is the same as what is\\nin the acronym table\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Repeat this process for each acronym\"))), mdx(\"p\", null, \"In addition to this, remove acronyms from the table that were not used\\nin the plan or report. The acronyms provided in the templates will not\\nnecessarily pertain to the document you are editing.\"), mdx(\"h1\", null, \"Commas\"), mdx(\"p\", null, \"Technical writing requires the use of the \\\"serial\\\" comma (sometimes\\ncalled the oxford comma), which is the comma used immediately preceding\\na coordinating conjunction (usually, and, or, or sometimes nor), or the\\nfinal item in a series of three or more items. This is important because\\nthe meaning of a sentence can change when commas are omitted or used\\nincorrectly.\"), mdx(\"h1\", null, \"\\\"Next Page\\\" and \\\"Page\\\" Breaks\"), mdx(\"p\", null, \"Use \\\"next page\\\" breaks when you separate a page to change its\\norientation from portrait to landscape, or when you create a blank page\\nor a new appendix. Use regular \\\"page\\\" breaks versus \\\"next page\\\" breaks\\nbetween new sections in the body and between measures in appendix B. The\\nfrugal use of \\\"next page\\\" breaks prevents the problem of a document\\ncontaining too many sections, which inhibits printing a customized range\\nof pages within a document.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"NEVER\"), \" use \\\"continuous\\\" page breaks in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" documents. \\\"Continuous\\\"\\npage breaks are hard to remove. If you try to delete them, you will\\nbegin a domino affect of formatting difficulties. Use the following\\nmethod to remove \\\"continuous\\\" page breaks successfully:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Place cursor at beginning of document\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Scroll to end of document while holding mouse button down to select\\neverything (do not use Ctrl A) (this can take a while on a long\\ndocument, but there is no short cut so be patient)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Hold down shift button and do a left click on mouse\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Go to Page Layout/Page Setup\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"On layout pick \\\"New Page\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"And \\\"selected sections\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Push OK button\"))), mdx(\"p\", null, \"You should have all \\\"next page\\\" page breaks in place of the \\\"continuous\\\"\\npage breaks when you complete this process.\"), mdx(\"h1\", null, \"Headers and Footers\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Headers.\"), \" All headers on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" plans and reports should be connected\\n(\\\"linked to previous\\\") with the exception of the SF298 (only applicable\\nto reports). This enables consistent classification markings on every\\npage.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Footers.\"), \" All footers on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" plans and reports should be connected,\\nwith the exception of the cover page (which is not numbered) and the\\nSF298 (only applicable to reports). This enables consistent\\nclassification markings on every page.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Header/Footer on SF298.\"), \" Keep information on the Standard Form (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Forces OR Standard Form\"\n }, \"SF\"), \") 298\\nat the unclassified level whenever possible. It will usually have a\\ndifferent classification marking or none at all. However, even when its\\nclassification is the same as that of the plan or report, do not connect\\nthe header or footer because the form also requires different margins\\nand header/footer settings and does not have page numbers (technically,\\nit is not part of the report and should not be included in the number of\\npages in a report).\"), mdx(\"h1\", null, \"Page Numbering\"), mdx(\"p\", null, \"The templates were designed with automatic page numbering that populates\\nthe table of contents automatically. However, when you add a \\\"next page\\\"\\nbreak, you may have to click into the footer and go to \\\"format page\\nnumbers.\\\" Click the radial button and choose \\\"continue from previous\\nsection\\\" so that the page numbering will continue instead of restarting\\nat page 1.\"), mdx(\"h1\", null, \"Blank Pages\"), mdx(\"p\", null, \"Insert or remove a blank page (i.e., Page intentionally blank) as\\nnecessary so that the following pages are always right facing (which\\nwill present on the left side of the screen in the 2-page layout view):\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Executive Summary\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Table of Contents\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"First page of the body of the report, which begins with\\n\\\"Introduction\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"First page of Appendix A\"))), mdx(\"p\", null, \"The SF298 Report Documentation Page (applicable for reports only) should\\nalways be left facing, (which will appear on the right side of the\\nscreen in the 2-page layout view) to ensure the form stays on the front\\nand back of the same page.\"), mdx(\"p\", null, \"A blank page should continue the page numbering of the section it\\nfollows (A-12 is followed by the blank page A-13). The section that\\nfollows the blank page will begin with page number one (B-1).\"), mdx(\"h1\", null, \"Capitalization\"), mdx(\"p\", null, \"Use capitalization appropriately. Writers have a tendency to capitalize\\nnonspecific titles of documents and things, even acronym definitions.\"), mdx(\"p\", null, \"Capitalize:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The title of a document when used in conjunction with the program's\\nproper name:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\\\"initial operational test and evaluation\\\" becomes \\\"RQ-4 Initial\\nOperational Test and Evaluation\\\"\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The production decision when used in conjunction with the decision\\nmaker's proper title:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\\\"full-rate production decision\\\" becomes the \\\"Under Secretary of\\nDefense for Acquisition, Technology and Logistics' (\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \"\", \"[\", \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L\", \"]\", \")\\nFull-Rate Production decision\\\"\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Cross-references (table or figure) when used at the beginning of a\\nsentence, but not in the middle of a sentence:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\\"Table (Figure) 1 contains the details.\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\\"\", \".\", \"..as shown in table (figure) X.\\\"\"))))), mdx(\"p\", null, \"Frame COIs as questions. Write them as a sentence punctuated with a\\nquestion mark ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Example\"), \" : \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1: Does the KC-46 support refueling?).\\nWrite \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" and MOSs in title case ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Example\"), \" : \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.8: Percent of\\nReports and Queries Generated Successfully).\"), mdx(\"p\", null, \"The acronym list is considered a table. Use title case capitalization\\nfor style continuity. In all other parts of the document, follow regular\\ncapitalization rules for words acronyms represent. Joint Publication\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \") 1-02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Department of Defense Dictionary of Military and Associated\\nTerms\"), \" , 12\\xA0Apr 01 (amended through Apr 10), Appendix A, contains a\\ncomprehensive list of abbreviations and acronyms. Refer to this\\npublication for clarification on when to, or not to, capitalize words.\"), mdx(\"h1\", null, \"Citing Air Force (or Other Military) Bases\"), mdx(\"p\", null, \"Verify military bases are cited properly. The first time a base is\\nmentioned, spell out the name, type of base, and state or country (ex:\\nEdwards Air Force Base, California; Ramstein Air Base, Germany; Royal\\nAir Force Lakenheath, England). Thereafter, use the name of the base\\nonly, or the name in conjunction with the type of base (ex: Edwards or\\nEdwards \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Base\"\n }, \"AFB\"), \"; Ramstein or Ramstein AB; Lakenheath or RAF Lakenheath). In\\ntables and figures, use only the abbreviated form.\"), mdx(\"h1\", null, \"Vertical Lists\"), mdx(\"p\", null, \"Validate proper punctuation, capitalization, and structure of vertical\\n(bulleted) lists, depending on how the information was structured.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example 1:\")), mdx(\"p\", null, \"The test team will assess the following capabilities:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Data conversion\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Upgrade integration\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Operability\"))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example 2:\")), mdx(\"p\", null, \"The test team will assess the\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"multiple data conversions necessary to transition from the legacy\\nsystem to the upgraded system;\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"integration of the upgrade at every location (all six Air Force\\nbases); and\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"operability at Peterson Air Force Base, Colorado; Kirtland Air Force\\nBase, New Mexico; and Wright-Patterson Air Force Base, Ohio.\"))), mdx(\"p\", null, \"The type of vertical list used will depend on the complexity and length\\nof the ideas presented. Example 1 is good for a simple list. Example 2\\nis a good choice for a complex sentence that contains various types of\\npunctuation and could be confusing when expressed in one very long,\\nlinear sentence.\"), mdx(\"h1\", null, \"Numbering Tables and Figures\"), mdx(\"p\", null, \"Number tables and figures sequentially and cross-reference them in the\\npreceding text. In the body, number tables and figures consecutively\\nthroughout (Use Navigation Pane on View Tab). Then, restart the table\\nand figure numbering in each appendix, adding the appendix letter as a\\nprefix. For example, \\\"Table A-5\\\" would be the fifth table in \\\"Appendix\\nA.\\\"\"), mdx(\"h1\", null, \"Tables\"), mdx(\"p\", null, \"The most important aspect of editing tables is to ensure the contents\\nreflect the information in the accompanying text accurately. Check each\\nof the following standards:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Apply \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Table Header + Rating and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Table Text styles\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Verify table properties: preferred width: 100%; default cell\\nmargins: top/bottom: 0\\\", left/right: 0.08\\\"; borders: 1 pt\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Align cells left/center\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Add classification by inserting a merged row above the header\\nrow\", \"-\", \"-apply the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Caption + Class style to classification\\nportion marking\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure classification and header rows repeat by highlighting\\nclassification and header rows and selecting \\\"repeat header rows\\\" in\\n\\\"Layout\\\" tab\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure tables break across the next page when necessary; avoid\\nexcess white space whenever possible, particularly in classified\\ndocuments\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Make sure ratings in tables match ratings in accompanying narrative\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure changes made to COIs, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", and MOSs are rolled into all the\\ntables (especially the evaluation summary chart or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \") in which\\nthey appear, and into affected narratives\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure ratings are uniform in color and size (copy and paste from\\ntemplate ratings)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Confirm tables use percent sign, dollar sign, numbers, and other\\nsymbols\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Do not define acronyms within the table except when it includes a\\nstandard mean term in parenthesis (i.e., MTBF)\", \"-\", \"-add the acronym and\\nits definition below \\\"\", \"*\", \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or supports \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or \\\\^ Identified\\nStandard\\\" if applicable (or in a merged row at the bottom of the\\ntable)\", \"-\", \"-add the acronym to the acronym table\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Align numbers on decimal (use decimal tab on ruler).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Add footnotes to the bottom of table in an inserted/merged row or\\nshift/enter below \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or Identified Standard, if applicable.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Eliminate repetitive symbols or labels (e.g., \", \"$\", \", %, hrs) by adding\\nthem to the table header and deleting them from text cells, when\\nappropriate\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capitalize cross-references at the beginning of a sentence: \\\"Table 1\\ncontains the details.\\\" Do not capitalize them in the middle of a\\nsentence: \\\"\", \".\", \"..as shown in table X.\\\"\"))), mdx(\"h1\", null, \"Figures\"), mdx(\"p\", null, \"Ensure contents of a figure reflects the information in the accompanying\\ntext accurately. Check each of the following standards:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Apply \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Caption + Class style to caption and classification\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Apply 1-pt black border\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Do not copy/paste a figure from another document, but save it as a\\n\\\".png\\\" or \\\".jpg\\\" file and insert it as a picture. Alternatively, use\\nthe \\\"snip and sketch\\\" tool to save any image\", \"-\", \"-the image will remain\\nsharp and clear because it is a scan of the image rather than a\\nconversion. Before \\\"capturing\\\" your image, unselect the \\\"show all\\nformatting marks\\\" so that you will not capture the marks with the\\npicture.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Do not duplicate figures in the body and appendices. The body is a\\nconcise presentation of the most important facts taken from the\\nappendices. Appendices contain the comprehensive details and are the\\nbetter choice for detailed figures describing a system or test.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Eliminate text boxes, symbols, figures, etc., inserted on top of\\nfigures by following the procedures above for converting pasted\\npictures to a .png or .jpg file. Reinsert them as a picture with all\\nadd-ons captured as part of the picture.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure all acronyms used in figures were added to and defined in the\\nacronym table.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capitalize cross-references at the beginning of a sentence: \\\"Figure\\n1 contains the details.\\\" Do not capitalize them in the middle of a\\nsentence: \\\"\", \".\", \"..as shown in figure X.\\\"\"))), mdx(\"h1\", null, \"Passive Voice\"), mdx(\"p\", null, \"Change passive voice to active voice, when appropriate. You can\\nrecognize a sentence with passive voice because a form of the verb to be\\n(is, are, was, were, be, being, or been) is followed by a past\\nparticiple verb (a verb ending in ed, en, or t). A sentence written in\\npassive voice always contains both.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Verb\"), mdx(\"th\", null, \"Passive Sentence\"), mdx(\"th\", null, \"Active Sentence\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"is\"), mdx(\"td\", null, \"Adequate planning\", mdx(\"strong\", null, \"\\xA0is\\xA0\"), \"requir\", mdx(\"strong\", null, \"ed\\xA0\"), \"for successful OT&E.\"), mdx(\"td\", null, \"Successful OT&E requires adequate planning.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"are\"), mdx(\"td\", null, \"Details\", mdx(\"strong\", null, \"\\xA0are\\xA0\"), \"contain\", mdx(\"strong\", null, \"ed\\xA0\"), \"in appendix D.\"), mdx(\"td\", null, \"Appendix D contains details.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"was\"), mdx(\"td\", null, \"The course\", mdx(\"strong\", null, \"\\xA0was\\xA0\"), \"taugh\", mdx(\"strong\", null, \"t\\xA0\"), \"by the instructor.\"), mdx(\"td\", null, \"The instructor taught the course.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"were\"), mdx(\"td\", null, \"The results\", mdx(\"strong\", null, \"\\xA0were\\xA0\"), \"writt\", mdx(\"strong\", null, \"en\\xA0\"), \"in active voice.\"), mdx(\"td\", null, \"They wrote the results in active voice ,\", mdx(\"em\", null, \"or if subject is known,\"), \"The test team wrote the results in active voice.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"be\"), mdx(\"td\", null, \"Annual maintenance\", mdx(\"strong\", null, \"\\xA0will be\\xA0\"), \"perform\", mdx(\"strong\", null, \"ed\\xA0\"), \"on the system.\"), mdx(\"td\", null, \"Maintainers will perform annual maintenance on the system\", mdx(\"em\", null, \"or\"), \"Maintainers will perform maintenance on the system annually.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"being\"), mdx(\"td\", null, \"Part A\", mdx(\"strong\", null, \"\\xA0was being\\xA0\"), \"substitut\", mdx(\"strong\", null, \"ed\\xA0\"), \"for part B as a workaround.\"), mdx(\"td\", null, \"The workaround substituted part A for part B.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"been\"), mdx(\"td\", null, \"The data\", mdx(\"strong\", null, \"\\xA0was\\xA0\"), \"giv\", mdx(\"strong\", null, \"en\\xA0\"), \"to the analyst.\"), mdx(\"td\", null, \"The analyst received the data,\", mdx(\"em\", null, \"or if subject is known,\"), \"The test director gave the analyst the data.\")))), mdx(\"h1\", null, \"Copyrights/Trademarks\"), mdx(\"p\", null, \"In accordance with the following authorities, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is not required to\\nuse the designated markings for copyrights and trademarks in our\\ndocuments because we are not a commercial entity and we do not\\ndistribute our documents publically. We are, however, required to use\\nthe proper spelling and capitalization for these trademarks (e.g.,\\nMicrosoft PowerPoint, Microsoft Word).\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Copyeditor's Handbook\"), \" states:\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"\\\"There is no need to include such designations as ^\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Manual OR Telemetry OR Test Manager\"\n }, \"TM\"), \"^ (trademark),\\n^\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Manager OR Service Manager OR Single Manager\"\n }, \"SM\"), \"^ (service mark), \\xAE\\xA0(registered trademark), or \\xA9 (copyright) in\\nrunning text. Indeed, it is preferable not to use these symbols\\nbecause they may interfere with the line spacing of the final\\ndocument.\\\"\"), mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"-\", \"-Einsohn, Amy. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"The Copyeditor's Handbook\"), \" , 2d ed. University of\\nCalifornia Press: Berkeley. 2006.\")), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Gregg Manual Reference Manual\"), \" states:\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"\\\"If you refer to other organizations' trademarks in material of a\\ncommercial nature that will be publically distributed, use a raised\\nsymbol after each trademark. In all other documents, the symbols are\\nnot necessary, but do use the proper spelling and capitalization for\\nthese trademarks.\\\"\"), mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"-\", \"- \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Gregg Manual Reference Manual\"), \" , 10th ed., McGraw-Hill: New York.\\n2005. p 114.\")), mdx(\"h1\", null, \"Wordiness\"), mdx(\"p\", null, \"Remove extra words that add nothing to the meaning of the sentence, as\\nshown in the following examples:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Capability\"\n }, \"IOC\"), \" plus 10-year \", mdx(\"em\", {\n parentName: \"p\"\n }, \"period\"), \" ---\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Capability\"\n }, \"IOC\"), \" plus 10 years\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Over a 5-year \", mdx(\"em\", {\n parentName: \"p\"\n }, \"time\"), \" period---Over a 5-year period \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"or\"), \" Over 5\\nyears\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Program was \", mdx(\"em\", {\n parentName: \"p\"\n }, \"first\"), \" launched---Program was launched\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"In order\"), \" to avoid confusion---To avoid confusion\"))), mdx(\"h1\", null, \"Hyphens, En Dashes, and Em Dashes\"), mdx(\"p\", null, \"Hyphens, en dashes, and em dashes all have their proper place in\\ntechnical writing, and should not be used interchangeably. Hyphens and\\nen dashes are the \\\"mechanics\\\" of punctuation and have clear-cut rules\\nfor their use. The em dash, on the other hand, is a stylistic choice\\nthat the writer chooses over other forms of punctuation to make a\\ndistinct point.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Hyphens:\"), \" Hyphens are used to connect and to separate textual\\nelements.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"It was a 2-year program.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Wright-Patterson Air Force Base, Ohio; Northrop-Grumman Corporation\"))), mdx(\"p\", null, \"As connectors, hyphens join the parts of compound modifiers.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The well-known author gave an interview.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The equipment emitted a high-frequency signal.\"))), mdx(\"p\", null, \"Hyphens separate numbers that are not inclusive (i.e., not within a\\nrange).\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"My phone number is 500-111-2222.\")), mdx(\"p\", null, \"The trend is moving toward using the hyphen less frequently.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Email versus e-mail\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Multifunctional versus multi-functional\"))), mdx(\"p\", null, \"Retain the hyphen if its absence makes a word or its meaning unclear.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Re-cover versus recover (to reapply a covering versus to come back\\nfrom; different meaning)\")), mdx(\"p\", null, \"Retain the hyphen when the prefix ends with the same letter with which\\nthe word begins.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Re-emerge versus reemerge; re-evaluate versus reevaluate (double-e\\ncan be confusing)\")), mdx(\"p\", null, \"Some program titles contain the hyphenated \\\"multi-\\\" as part of a program\\nor system title. In those cases, leave the hyphen in place.\"), mdx(\"p\", null, \"When one element of a compound modifier ends in \\\"ing\\\" or \\\"ed,\\\" use a\\nhyphen.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Fast-burning fuel; self-contained module\")), mdx(\"p\", null, \"When two or more related compounds have a common basic element, retain\\nthe hyphen with all parts.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"10- to 20-page report; long- and short-term memory\")), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"En Dashes:\"), \" En dashes connect numbers within a range (including\\nnumber ranges in tables) or take the place of the word \\\"to.\\\"\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The years 1995--1996 were interesting ones for most government\\nworkers.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The Las Vegas--Albuquerque flight departs in 1 hour.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The test team assessed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" 2.3--2.6.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Em Dashes:\"), \" \\\"Em dashes involve a choice writers and editors make when\\nother options might be commas, a colon, or a set of parentheses. The em\\ndash can be used singly or in pairs. Its most common purpose is to set\\noff an amplifying or explanatory element of the sentence. It is also\\nused to indicate a sudden break in thought or an interruption in\\ndialogue.\\\" ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Chicago Manual of Style, 16th Edition\"), \" , pages 333--336)\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"The weapon failed the test---the trigger jammed.\")), mdx(\"p\", null, \"Em dashes are also used to set off explanatory elements that already\\ncontain internal punctuation (i.e., commas).\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Boeing's system offers improvements---better navigation, streamlined\\nmaintenance, and greater reliability---that no other vendor can\\npromise.\")), mdx(\"h1\", null, \"Apostrophes\"), mdx(\"p\", null, \"Use apostrophes to show singular possessives (belonging to a single\\nentity) or plural possessives (belonging to one or more entities). Do\\nnot use apostrophes for a plural expression that is not used in the\\npossessive form.\"), mdx(\"p\", null, \"The word \\\"its\\\" means belonging to it and is never expressed as a\\npossessive. \\\"It's\\\" is a contraction that means \\\"it is\\\" or \\\"it has.\\\" If\\nyou cannot replace the word it's with it is or it has, do not use an\\napostrophe. The following table contains examples of when to, or not to\\nuse an apostrophe.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Apostrophe Not Required\"), mdx(\"th\", null, \"Apostrophe Required\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"The test teams\\u2019 wrote the report. (plural)\"), mdx(\"td\", null, \"AFOTEC published the test teams\\u2019 report. (plural possessive)\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"In the 1970s, Journey was a popular rock band. (plural)\"), mdx(\"td\", null, \"Journey was a popular 1970\\u2019s rock band. (possessive)\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Several MC-130s are parked on the flightline. (plural)\"), mdx(\"td\", null, \"Examine the MC-130\\u2019s payload. (possessive)\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"They examined its contents. (belonging to it, not a contraction)\"), mdx(\"td\", null, \"It\\u2019s a windy day. (contraction for it is)\")))), mdx(\"h1\", null, \"Choppy Sentences\"), mdx(\"p\", null, \"Rewrite choppy sentences into ones that flow better by adding\\npunctuation and conjunctions, when appropriate. However, be careful not\\nto change the meaning or context when doing so.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Original\"), \" : The test team wrote the report. The report informed the 14\\nNovember 2014 full-rate production decision.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Edit\"), \" : The test team wrote the report, which informed the 14 November\\n2014 full-rate production decision.\"), mdx(\"h1\", null, \"Numbers\"), mdx(\"p\", null, \"Express numbers referring to time, measurements, or money as figures\\n(e.g., 8 hours, 2 feet, 5 dollars). Use ordinal numbers when spelling\\nout a unit's name. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" does not use superscript for ordinals.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : 21st Space Wing (21 SW); subsequent use: 21 SW\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : 21st Space Wing (SW); 21st SW; 21 ^st^ SW; 21 ^st^\\nSpace Wing\"))), mdx(\"p\", null, \"Do not use an \\\"n\\\" or \\\"r\\\" for second and third ordinals\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : 43d Test Squadron; 302d Airlift Wing\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : 43rd Test Squadron; 302nd Airlift Wing\"))), mdx(\"h1\", null, \"Dates\"), mdx(\"p\", null, \"Write dates differently depending on the context in which you use them.\\nIn general, use the complete date format (full day, month and four-digit\\nyear). However, abbreviate dates in tables, figures, and document or\\npublication references. Do not mix complete and abbreviated date\\nformats.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : 20 Jul 04 or 20 July 2004\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : 20 Jul 2004 or 20 July 04\"))), mdx(\"p\", null, \"When the terms fiscal or calendar year are spelled out, the four-digit\\nyear should be used.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : fiscal year 2001; calendar year 2001\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : fiscal year 01; calendar year 01\"))), mdx(\"p\", null, \"When they are abbreviated, the year should also be abbreviated without a\\nspace between the term and the year.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Example:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : FY01; CY01\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Fiscal Year\"\n }, \"FY\"), \" 01; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Calendar Year\"\n }, \"CY\"), \" 01\"))), mdx(\"p\", null, \"Use the words \\\"to\\\" or \\\"through\\\" instead of an en dash when dates are\\npreceded by words \\\"between\\\" or \\\"from.\\\"\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct\"), \" : from 15 through 30 July; between 15 to 30 July and 1 to\\n5 August; 15--30 July; 15--30 July and 1--5 August\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect\"), \" : from 15--30 July; between 15--30 July and 1--5 August\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"The only exceptions are tables and figures; always abbreviate dates\\nand use an en dash.\")), mdx(\"h1\", null, \"Abbreviations\"), mdx(\"p\", null, \"Common units of measure (e.g., ft, in, sec, nm) or common symbols (e.g.,\\npercent, degrees) are abbreviations, not acronyms. Spell them out or\\ndefine them the first time you use them. Do not add them to the acronym\\ntable.\"), mdx(\"h1\", null, \"Terms\"), mdx(\"p\", null, \"Do not use terms \\\"i.e.,\\\" and \\\"e.g.,\\\" in conjunction with \\\"etc.\\\" and,\\nmost importantly, do not use them interchangeably. Always follow \\\"i.e.,\\\"\\nand \\\"e.g.,\\\" with a comma.\"), mdx(\"p\", null, \"The term \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\\"e.g.,\\\"\"), \" means \\\"for example.\\\" It is \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"not a finite list\"), \" ;\\nthere are more possibilities than the ones stated.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"They brought fruit (e.g., apples, oranges, bananas)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"They brought fruit (apples, oranges, bananas, etc.)\"))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"They brought fruit (e.g., apples, oranges, bananas, etc.)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"They brought fruit (e.g., the apples were crunchy)\"))), mdx(\"p\", null, \"The term \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"\\\"i.e.\\\"\"), \" means \\\"in other words\\\" and is used to add extra\\ninformation that clarifies. \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"It is finite; it is the only possibility\"), \"\\nthat could be listed.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Correct:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The hurricane affected two of the Hawaiian islands (i.e., Oahu and\\nKauai) with winds over 130 mph.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Several personnel (i.e., active-duty and civilian) were promoted at\\nthe ceremony.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"He corrected the problem (i.e., tightened down the screw) and the\\nrattling stopped.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Four of the tech giants (i.e., Google, Amazon, Facebook, Apple)\\nhired promising new employees at the job fair.\"))), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Incorrect:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Several tech giants (i.e., Google, Facebook) hired promising new\\nemployees.\")), mdx(\"h1\", null, \"Symbols and Units of Measure\"), mdx(\"p\", null, \"Use symbols and abbreviated units of measure in appendices, figures, and\\ntables, but spell them out in the executive summary and body of the\\ndocument.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Examples:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Executive Summary and Body\"), \" : percent, greater than, nautical mile\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"em\", {\n parentName: \"p\"\n }, \"Appendix, Figure, or Table\"), \" : %, \", \">\", \", nm\"))), mdx(\"h1\", null, \"Verb Tenses\"), mdx(\"p\", null, \"Be consistent in the use of verb tenses throughout the plan or report. A\\nplan describes how \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will execute a test and is written in future\\ntense. A report contains results, ratings, and operational impacts and\\nis written in past tense.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Plan\"), mdx(\"th\", null, \"Report\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Describes how AFOTEC will execute the test\"), mdx(\"td\", null, \"Contains results and ratings of the system under test, and the operational impact of those results and ratings\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Will happen, future tense\"), mdx(\"td\", null, \"Has happened, past tense\")))), mdx(\"h1\", null, \"Embedded Files\"), mdx(\"p\", null, \"If the test teams follow the templates, you should not discover an\\nembedded file or link (PowerPoint, Excel spreadsheet, etc.) in the\\ndocument, because embedding documents into our plans or reports is not\\npermitted. However, if you discover such a file or link (i.e., a test\\nplan or report from another entity) within the document, you will have\\nto open and save it as a separate file, then forward it along with the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" document so it can be included as an attachment to the completed\\n.pdf file that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" publishes and distributes.\"), mdx(\"h1\", null, \"Converting Pictures\"), mdx(\"p\", null, \"Do not copy/paste a picture from another document; instead, save it as a\\n\\\".png\\\" or \\\".jpg\\\" file and insert it as a picture. Alternatively, use the\\n\\\"snip and sketch\\\" tool to save any image, table, text, equation, or\\nwhatever you want to capture from a page and change into a picture.\\nBefore \\\"capturing\\\" your image, unselect the \\\"show all formatting marks\\\"\\nso that you will not capture the marks with the picture. The \\\"snip and\\nsketch\\\" tool avoids the conversion process that makes pictures appear\\ngrainy.\"), mdx(\"p\", null, \"You can also transfer a pasted picture to PowerPoint (directions below)\\nto change it into a \\\".png\\\" or \\\".jpg\\\" file, then delete the original\\nimage and reinsert the picture you created.\"), mdx(\"p\", null, \"Procedures for converting a pasted picture into a .jpg or .png using\\nPowerPoint:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Capture picture and all text blocks or other objects placed within\\nit or on top of it, and copy the group of images (Ctrl C)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Paste into PowerPoint (Ctrl V), the select all (Ctrl A) or \\\"group\\\"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Right click, save as a picture (.png or .jpg)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Delete embedded object from document\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In its place, position cursor and insert picture from where you\\nsaved it\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Center picture, then add a 1-pt black border (some flow charts or\\nsimilar figures may be disrupted by a border and, therefore, are\\nexempt)\"))), mdx(\"h1\", null, \"References/Documentation\"), mdx(\"p\", null, \"Cite references (documentation) correctly. A good authority is the Air\\nUniversity Press, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Air University Style and Author Guide\"), \" (Maxwell \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Base\"\n }, \"AFB\"), \"\\nAL, 2005), Part 1, Appendix B, Bibliographic Entries. You can access\\nthis publication on the Internet. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Suggestion\"), \" : print out or save the\\nappendix and have it available for reference when you are editing. In\\ngeneral, official publications with unlimited distribution (e.g., AFIs,\\ndirectives) are italicized:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 99-103, \", mdx(\"em\", {\n parentName: \"li\"\n }, \"Capabilities Based Test and Evaluation\"), \" , 16 Oct 13\")), mdx(\"p\", null, \"Reports and other publications with limited distribution (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nreports, threat documents) are enclosed in quotation marks:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Executive Order (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electro-Optical OR Executive Order OR Engineering Order\"\n }, \"EO\"), \") 13526, \\\"Classified National Security\\nInformation,\\\" 29 Dec 09\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\\"Defense Enterprise Accounting and Management System (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Enterprise Accounting and Management System\"\n }, \"DEAMS\"), \")\\n(Increment 1 Release 3) Initial Operational Test and Evaluation\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E) Plan,\\\" 4 Aug 14\"))), mdx(\"p\", null, \"Memos and standard forms (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Forces OR Standard Form\"\n }, \"SF\"), \") are cited without italics or quotes. For\\nmemos, state the entity who wrote the memo, the date, and the subject:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo, 1 Aug 14, Procedures for Operational Test and Evaluation\\nof Cybersecurity in Acquisition Programs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"SF298, Report Documentation Page\"))), mdx(\"p\", null, \"The table below contains examples of the correct way to cite different\\ntypes of reference documents. Use the long citation the first time the\\ndocument is referenced and the short version for subsequent citings.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Type\"), mdx(\"th\", null, \"First Use\"), mdx(\"th\", null, \"Subsequent Use\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"United States Code\"), mdx(\"td\", null, mdx(\"em\", null, \"Title 10, United States Code\"), \", Section\\xA02366\"), mdx(\"td\", null, \"10\\xA0USC\\xA0\\xA72366\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Executive Order\"), mdx(\"td\", null, \"EO\\xA013526, \\u201CClassified National Security Information,\\u201D 29\\xA0Dec\\xA009\"), mdx(\"td\", null, \"EO\\xA013526\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"DoD Directive\"), mdx(\"td\", null, \"DoDD\\xA08500.01,\", mdx(\"em\", null, \"Cybersecurity\"), \", 7 Mar 14\"), mdx(\"td\", null, \"DoDD\\xA08500.01\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"DoD Regulation\"), mdx(\"td\", null, \"DoD\\xA05400.7-R,\", mdx(\"em\", null, \"DoD Freedom of Information Act (FOIA) Program\"), \", Sep\\xA098\"), mdx(\"td\", null, \"DoD\\xA05400.7-R\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Chairman of the Joint Chiefs of Staff Instruction\"), mdx(\"td\", null, \"CJCSI\\xA06212.01E,\", mdx(\"em\", null, \"Interoperability and Supportability of Information Technology and National Security Systems,\"), \"15\\xA0Dec 08\"), mdx(\"td\", null, \"CJCSI\\xA06212.01E\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Air Force Handbook\"), mdx(\"td\", null, \"Air Force Handbook 33\\u2011337,\", mdx(\"em\", null, \"The Tongue and Quill\"), \", 27\\xA0May\\xA015 (Incorporating Change 1, 19 Nov 15)\"), mdx(\"td\", null, mdx(\"em\", null, \"Tongue and Quill\"), \"or AFH\\xA033\\u2011337\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Air Force Instruction\"), mdx(\"td\", null, \"AFI\\xA099\\u2011103,\", mdx(\"em\", null, \"Capabilities Based Test and Evaluation,\"), \"16\\xA0Oct\\xA013\"), mdx(\"td\", null, \"AFI\\xA099\\u2011103\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"AFOTEC Instruction\"), mdx(\"td\", null, \"AFOTECI\\xA099\\u2011101,\", mdx(\"em\", null, \"Conduct of Operational Test and Evaluation,\"), \"1\\xA0May\\xA007\"), mdx(\"td\", null, \"AFOTECI\\xA099\\u2011101\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"AFOTEC Manual\"), mdx(\"td\", null, \"AFOTECMAN\\xA099-101,\", mdx(\"em\", null, \"Operational Test Processes and Procedures\"), \", 11\\xA0Oct\\xA012\"), mdx(\"td\", null, \"AFOTECMAN\\xA099\\u2011101\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Military Standard\"), mdx(\"td\", null, \"MIL-STD-130N,\", mdx(\"em\", null, \"Identification Marking of U.S. Military Property,\"), \"16\\xA0Nov\\xA012 (with change 1)\"), mdx(\"td\", null, \"MIL\\u2011STD\\u2011130N\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Technical Order\"), mdx(\"td\", null, \"TO\\xA000\\u201135D\\u201154,\", mdx(\"em\", null, \"USAF Deficiency Reporting, Investigation, and Resolution,\"), \"1 Nov 11\"), mdx(\"td\", null, \"TO\\xA000\\u201135D\\u201154\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Concept of Operations\"), mdx(\"td\", null, \"\\u201CCombat Survivor Evader Locator (CSEL) Concept of Operations,\\u201D 4\\xA0Jul\\xA005\"), mdx(\"td\", null, \"CSEL\\xA0CONOPS\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"System Threat Assessment Report\"), mdx(\"td\", null, \"NASIC-1574-0210-03, \\u201CAutomated Information Systems Threat Environment Description,\\u201D Dec\\xA002\"), mdx(\"td\", null, \"AI\\xA0STAR\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Published AFOTEC document\"), mdx(\"td\", null, \"\\u201CDefense Enterprise Accounting and Management System (DEAMS) (Increment 1 Release 3) Initial Operational Test and Evaluation (IOT&E) Plan,\\u201D 4 Aug 14\"), mdx(\"td\", null, \"DEAMS IOT&E Plan or the IOT&E plan\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Official Memorandum\"), mdx(\"td\", null, \"DOT&E Memo, 1 Aug 14, Procedures for Operational Test and Evaluation of Cybersecurity in Acquisition Programs\"), mdx(\"td\", null, \"DOT&E Memo on Policy for OT&E of Cybersecurity\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Standard Form\"), mdx(\"td\", null, \"Standard Form 298, Report Documentation Page\"), mdx(\"td\", null, \"SF\\xA0298\")))), mdx(\"h1\", null, \"Patches\"), mdx(\"p\", null, \"Verify \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \" patches on multiservice operational test and evaluation\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \") plan or report cover pages are correct. Patches should be in\\nsame order of precedence as the signature page (Ref: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 36-2203),\\nwhich is army, marine corps, navy, air force, coast guard. However, when\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" is the lead \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \", our patch and our Commander's signature will go\\nfirst, followed by the other services in the correct order of\\nprecedence.\"), mdx(\"h1\", null, \"Classification Markings\"), mdx(\"p\", null, \"Ensure writers follow the guidance in DoDM 5200.01, V2, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence Community\"\n }, \"IC\"), \" 4, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \"\\nInformation Security Program: Marking Information, 28 Jul 20\"), \" , and DoDI\\n5200.48, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Controlled Unclassified Information\"), \" , 6 Mar 20 when they\\napply required classification markings to classified documents. Perform\\nthe following actions:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Verify the correct distribution statement and derivative,\\ndeclassification, and destruction information were included on cover\\npage.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure the Controlled Unclassified Information (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Controlled Unclassified Information\"\n }, \"CUI\"), \") designation\\nblock is included on the lower right-hand side of the cover page, if\\nneeded\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure every page was marked with the highest overall classification\\nof the document.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Make sure every portion was marked with the applicable portion\\nmarking.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Ensure portion marks were carried over (\\\"carry-over marks\\\") when a\\nparagraph broke and continued onto the following page; insert a\\nmanual line break (shift/enter) at end of the last sentence on the\\npage, then copy the carry-over mark (that applies to the broken\\nparagraph) onto the top of next page. This method helps locate\\ncarry-over marks to place them in the correct spot at the top of the\\npage when they shift to another part of the page due to additions\\nand/or deletions of information during rewrites/editing.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Find carry-over marks that might have moved to the middle of a page\\nor paragraph by using (ctrl F, special--manual line break). Move\\neach shifted carry-over mark by deleting the carry-over mark and its\\ncorresponding manual line break, and reapplying them to the top of\\nthe page where they belong.\"))), mdx(\"h1\", null, \"Distribution List\"), mdx(\"p\", null, \"The test team must compile a distribution list that contains members of\\nthe acquisition and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" community with an interest in their particular\\nprogram's test plan or report. Those contacts are usually listed in\\ntheir program's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Integrated Test Team\"\n }, \"ITT\"), \" charter and/or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \". The template includes permanent\\nmembers who receive each document (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \", \", 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\"), \") and\\nsuggests other personnel the team should consider adding (in blue\\ninstructional text). The test team should also add whatever additional\\npersonnel they deem appropriate. The distribution list must contain\\npersonal email addresses, not workflows, for purposes of accountability.\"), mdx(\"h1\", null, \"SF298 Report Documentation Page\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" reports (not plans) must include an SF298 attached to the end of\\nthe document. Defense Technical Information Center (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Technical Information Center\"\n }, \"DTIC\"), \") uses this form\\nto archive official reports, as required. The SF298 should be maintained\\nat the unclassified level, if possible, so avoid details that would make\\nit classified. If not possible, ensure it is marked appropriately in the\\nheader and footer and wherever classification information is required.\"), mdx(\"p\", null, \"Ensure the test team completes the form, because it is often neglected\\nin the writing process. Complete the blocks with the following\\ninformation:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 1--Must match date on cover page; use format described (i.e.,\\n12082014, not 12\\xA0Aug\\xA014)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 2--Type of report\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 3--Dates covered are from beginning of testing period to date\\nof report; use format described (i.e., 09032014--12082014, not 9 Mar\\n14 - 12 Aug 14)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 4--Full title from cover page; should match exactly\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Blocks 5a--5f--Leave blank\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 6--Complete address of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Detachment that produced the\\nreport\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 7--\", 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\"), \" address (i.e., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", 1251 Wyoming Blvd \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \",\\nKirtland \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Base\"\n }, \"AFB\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Network Management\"\n }, \"NM\"), \" 87117)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Blocks 8--11--Leave blank\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 12--Distribution statement must match cover page\\nexactly---copy and paste from cover page, then reapply \\\"SF298 text\\\"\\nstyle\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 13--If there is a classified annex or other supplemental\\ndocument for the report, add that information in this block---i.e.,\\nThis report is associated with \\\"Annex 1 to the Joint Air-to-Surface\\nStandoff Missile-Extended Range (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Air-to-Surface Standoff Missile\"\n }, \"JASSM\"), \"\\u2011ER) Initial Operational Test\\nand Evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E) Report,\\\" 8 Jan 13 (classified).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 14--Add a synopsis of the report---i.e., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" conducted an\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \" to assess \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Air-to-Surface Standoff Missile\"\n }, \"JASSM\"), \"\\u2011ER's progress toward operational effectiveness\\nand suitability in supporting the long-range, standoff precision\\nstrike mission. Additionally, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" assessed the program's\\nreadiness for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. This \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \" report will inform the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Undersecretary of Defense\"\n }, \"USD\"), \"(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Anti-Tamper\"\n }, \"AT\"), \"&L)'s\\n7\\xA0Dec\\xA010, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" C decision.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 15--Add the search engine terms a person would likely use on\\nthe Internet to find our report; this information will be added to\\nthe document properties in the published pdf\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 16--Verify that the security classifications for the following\\nare stated accurately:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"a\", \".\", \" Report--classification of report\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"b\", \".\", \" Abstract--classification of abstract (should be\\nunclassified, if possible)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"c\", \".\", \" This Page--classification of the SF298 front page (should be\\nunclassified, if possible)\")))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 17--Limitation of Abstract\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Unclassified abstract---should read UU (for unclassified,\\nunlimited distribution)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Secret abstract---should read S or same as report (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Report OR Special Access Required OR Synthetic Aperture Radar OR System Assessment Report\"\n }, \"SAR\"), \"); when it\\nis not possible to keep the abstract at the unclassified level\")))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 18--Enter total number of pages, minus the SF298 because it\\ndoes not count as part of the report\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 19a--Enter \", 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\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Block 19b--Enter \", 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\"), \" phone number: (505) 846-2484\"))), mdx(\"h1\", null, \"Spell Check\"), mdx(\"p\", null, \"ALWAYS run a final spell check before the final save at the end of the\\nediting process. It might seem obvious, but this step is often\\noverlooked.\"), mdx(\"h1\", null, \"Configuration Control\"), mdx(\"p\", null, \"The hardest part of a technical editor's job is maintaining\\nconfiguration control. It is critical you maintain a constant line of\\ncommunication with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test team members to ensure their final edited\\nversion is the ONLY version to which changes are being made.\"), mdx(\"p\", null, \"After the 2-letter adjudication process, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" turns the document over\\nto \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \", via \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Collaborative Action Platform (ACAP), for command\\nsection coordination. At this point, configuration control of the\\ndocument converts from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" technical editor to the A-3 technical\\neditor. Detachment personnel should cease working on the document, and\\npass any additional changes they wish to make to their A-3 point of\\ncontact. If the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" continues to work on the document they submitted,\\nwhich is no longer the valid version, that work will likely have to be\\nreaccomplished or, worst case, will be omitted inadvertently. The\\ndocument will be reviewed by members of the command staff (including the\\nCommander, Executive Director, Vice Commander, and Technical Advisor)\\nwho will make comments and changes. The A-3 technical editor will\\nincorporate those changes into the configuration control version.\"), mdx(\"p\", null, \"Good communication is key to successful configuration control. Never\\nassume you have the correct version of a document unless the person with\\nwhom the control resides confirms that it is the latest version.\"), mdx(\"h1\", null, \"Table of Contents\"), mdx(\"p\", null, \"Do not attempt to hand-jam changes to the table of contents (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"\n }, \"TOC\"), \"). It is\\ndesigned to work in tandem with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" styles---which is why it is\\nimportant to ensure the correct styles are applied---and will update\\nautomatically. To update the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"\n }, \"TOC\"), \", go to the References tab, select\\nUpdate Table, then select Update Entire Table.\"), mdx(\"h1\", null, \"Standardization Checklist\"), mdx(\"p\", null, \"The following checklist can be a handy guide when editing an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" plan\\nor report. Print it out to ensure you perform a thorough check of all\\nareas of emphasis.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC STANDARDIZATION CHECKLIST\"), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Were AFOTEC styles applied?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you perform an acronym scrub?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you replace \\u201Ccontinuous\\u201D page breaks with \\u201Cnext page\\u201D breaks?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you ensure the serial comma was used consistently throughout the document?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you verify headers and footers were standardized and contained correct classification, if necessary?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you check page numbering to ensure there were no disconnects?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Were blank pages added or deleted, as required?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you correct capitalization errors?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you verify military and Air Force Bases were cited correctly?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you examine vertical lists for correct structure and punctuation?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you confirm tables and figures were in sequential order?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you verify each table and figure followed AFOTEC standards?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you eliminate inappropriate passive voice?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you rewrite wordy and choppy sentences?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you ensure hyphens, en dashes, and em dashes were used correctly?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you correct apostrophes that were applied incorrectly?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you confirm number rules were followed?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Were dates written correctly, according to the context in which they were used?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you ensure only acceptable abbreviations were used?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you verify whether the terms i.e., e.g., and etc. were used correctly?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you ensure symbols and units of measure were spelled out in the executive summary and body?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you correct errors in verb tenses?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you eliminate embedded files?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you convert copy/pasted pictures into .jpg or .png files and reinsert them?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you verify documentation was cited correctly throughout the document?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you verify whether classification markings, portion markings, and carry-over marks were applied correctly?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you verify that the distribution list was compiled IAW template guidance, and includes all pertinent addressees?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you check the SF298 to ensure it was accurate and complete?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Did you perform a final spell check?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Did you update the table of contents?\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"MAINTAIN CONFIGURATION CONTROL!\\xA0\"), \"Do not password protect documents in 2-letter and CS coordination. Do not continue to work the version of the document you have at the detachment while it is in 2-letter or CS coordination. Instead, contact your A-3 POC about changes that need to be incorporated.\"), mdx(\"td\", null)))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#purpose","title":"PURPOSE"},{"url":"#executive-summary-body-and-appendices","title":"Executive Summary, Body, and Appendices"},{"url":"#consistency-is-key","title":"Consistency is Key"},{"url":"#one-voice","title":"One Voice"},{"url":"#templates","title":"Templates"},{"url":"#microsoft-word-options","title":"Microsoft Word Options","items":[{"url":"#display","title":"Display:"},{"url":"#proofing","title":"Proofing:"},{"url":"#advanced","title":"Advanced:"}]},{"url":"#focus-areas","title":"Focus Areas"},{"url":"#styles","title":"Styles"},{"url":"#acronyms","title":"Acronyms"},{"url":"#commas","title":"Commas"},{"url":"#next-page-and-page-breaks","title":"\"Next Page\" and \"Page\" Breaks"},{"url":"#headers-and-footers","title":"Headers and Footers"},{"url":"#page-numbering","title":"Page Numbering"},{"url":"#blank-pages","title":"Blank Pages"},{"url":"#capitalization","title":"Capitalization"},{"url":"#citing-air-force-or-other-military-bases","title":"Citing Air Force (or Other Military) Bases"},{"url":"#vertical-lists","title":"Vertical Lists"},{"url":"#numbering-tables-and-figures","title":"Numbering Tables and Figures"},{"url":"#tables","title":"Tables"},{"url":"#figures","title":"Figures"},{"url":"#passive-voice","title":"Passive Voice"},{"url":"#copyrightstrademarks","title":"Copyrights/Trademarks"},{"url":"#wordiness","title":"Wordiness"},{"url":"#hyphens-en-dashes-and-em-dashes","title":"Hyphens, En Dashes, and Em Dashes"},{"url":"#apostrophes","title":"Apostrophes"},{"url":"#choppy-sentences","title":"Choppy Sentences"},{"url":"#numbers","title":"Numbers"},{"url":"#dates","title":"Dates"},{"url":"#abbreviations","title":"Abbreviations"},{"url":"#terms","title":"Terms"},{"url":"#symbols-and-units-of-measure","title":"Symbols and Units of Measure"},{"url":"#verb-tenses","title":"Verb Tenses"},{"url":"#embedded-files","title":"Embedded Files"},{"url":"#converting-pictures","title":"Converting Pictures"},{"url":"#referencesdocumentation","title":"References/Documentation"},{"url":"#patches","title":"Patches"},{"url":"#classification-markings","title":"Classification Markings"},{"url":"#distribution-list","title":"Distribution List"},{"url":"#sf298-report-documentation-page","title":"SF298 Report Documentation Page"},{"url":"#spell-check","title":"Spell Check"},{"url":"#configuration-control","title":"Configuration Control"},{"url":"#table-of-contents","title":"Table of Contents"},{"url":"#standardization-checklist","title":"Standardization Checklist"}]},"parent":{"__typename":"File","relativePath":"fn_guides/editing_reports_guide.md"},"frontmatter":{"metaTitle":"Editing Guide","metaDescription":"Editing Guide"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"f83c0915-7e80-5546-897f-dc21b54c3887"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/fn_guides/evaluation_and_reporting_guide/page-data.json b/sites/oteguide/page-data/fn_guides/evaluation_and_reporting_guide/page-data.json deleted file mode 100644 index 04595be8..00000000 --- a/sites/oteguide/page-data/fn_guides/evaluation_and_reporting_guide/page-data.json +++ /dev/null @@ -1 +0,0 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides/evaluation_and_reporting_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"c1a3de9d-c097-5471-bd2c-8338370972f9","title":"Evaluation and Reporting Guide","slug":"/fn_guides/evaluation_and_reporting_guide"},"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\": \"Evaluation and Reporting Guide\",\n \"metaTitle\": \"Evaluation and Reporting Guide\",\n \"metaDescription\": \"Evaluation and Reporting Guide\"\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(\"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/15c01df8a9fa6f626567e43efe3eaffe/bd9eb/image2.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\": \"66.02316602316603%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAAD2klEQVQ4yyVSe0ybVRQ/Cm2ZLRXK+xl0CmSBbcaxbCYY/vGdJRoS56JIIkamCSGZSafGxzRRY2JiDGyEOZfojGN/kIGU50YfK6Xtvra0tP3ebb/2o3Qt26DFf5a2HG/lJufee849Off8zu8HHCvf4hhZkKQYTdMcEw5H6EwmE9re3jaTwMtut4ubnp4SDIZZ/p/pacEXDAhhihL85O4NBgWREwRRFFhJCscDgcAYuFxe2eMOoiyn0ONZR0naxJ2dNKbTO0n7quvtOxYfBgIMOhwe9K6tIyuI6LM7kZq/hT6GRj+3jrYVJy4tWtBits5BKpUUk8kkprbuZwMBMZdMPsju7mZwa2tLXlhwvD87yz2y2Xy55WVLzm535yiXN7dsdmTvWL1Zk2MlO2GfyM5MLj8au/g3TlyfmQeO42QCFUOhDaQoD/J8BBmGR5/Pv2UyUf2CwBCfQQILBZEn7yKyrB1d1CTa7RT6faRrliHGotPpNsLDhw+skUgkvrERj8hyMppIpCRZljfi8YRvfHzmiNu99s7S4u2PRn+9fmFs5MbXf1yd0s/N3xicmx35cGraOmAy3/1gack2YDbaz165bHgLGFqcX111CFarJWixrDBWq5UmRLChUNhz+vTFCoPhPiAikKUhVk1MUfARvynEFMTK9v30fl7AL0gU5ce1NT/6/TQGgzQKgkDIiWX1+t/r6+r41hMnJ2sqyzobNNDYfqjj0/LWtnO6np5rGpWqvRWg5thjr5qe+K3zzbZrz77WCIIY5cyWVTIzNhcKxfIrK1RuZmaeFOcyev14Y7Hiy+7XO1JK7dGy6obPD3edONxNmuqF/r526O2taPrqi9rnb35cBd/Vlh4a1BxshcTmPT4ixJDjxHw0eo8QEN6jaYGQJP07NDTeWIChI9BKn2qtKe1pJtXKNGptG4GKcOqUql5/XtEBcKYINLoigLNq4GSWv00bMcxv5BcWjYXO9sgnKMdiu9//8GeV/vw6VNQqSlTwRpMK3nuuBF6oAujRKpU/qgE+KQforypXf0bm+0sJwFgJiHKYt3EURsRo3mS2kflF9jZTKZQ3NzPWxb+0ALb6isqfKwFOFkipg8dHDxDIZUrlVXJWHCTNH4fiyyXD2hebwtU6NYHM8bJkIVCjefvqXQxyoT3J6UbZ7U6POF06rfrSS690MQcUzU/WlfcdOVYgcmj4Jzg3DNDd3dwwONDSaTijgkstLUdHq2qfgUQiwvsDRvR6mTzRHK4HuT3a7sA4TaevGI26gjaIHqCl72l19XB1175E3gWR1UBfHzRf+BaO/5+jhGKyF/0HzoBsKifzEJsAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image2\",\n \"title\": \"image2\",\n \"src\": \"/static/15c01df8a9fa6f626567e43efe3eaffe/e3189/image2.png\",\n \"srcSet\": [\"/static/15c01df8a9fa6f626567e43efe3eaffe/a2ead/image2.png 259w\", \"/static/15c01df8a9fa6f626567e43efe3eaffe/6b9fd/image2.png 518w\", \"/static/15c01df8a9fa6f626567e43efe3eaffe/e3189/image2.png 1035w\", \"/static/15c01df8a9fa6f626567e43efe3eaffe/bd9eb/image2.png 1442w\"],\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, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Primary Responsibility\"\n }, \"OPR\"), \" is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3 and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of Collateral Responsibility OR Operational Capability Requirement\"\n }, \"OCR\"), \" is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-2/9\"), mdx(\"h1\", null, \"INTRODUCTION\"), mdx(\"p\", null, \"This guide focuses on the analysis, evaluation, and reporting 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\"), \"&E activities. It covers the products and processes you must follow to\\ncomplete this final phase of test execution successfully. Submit\\nsuggested changes to: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".A3.Workflow\\\\@us.af.mil.\"), mdx(\"h1\", null, \"TEST ACTIVITY SEQUENCE\"), mdx(\"p\", null, \"During a test activity, you will carry out a sequence of five steps: \"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"determine what to test\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"design a test plan\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"execute the test and collect data\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"analyze and evaluate test results\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"report conclusions (Figure 1). \")), mdx(\"p\", null, \"The success of this activity depends largely on\\nthe robustness of the earlier steps to ensure an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" effort that is\\noperationally sufficient and technically adequate. This guide focuses on\\nthe analysis and evaluation of results and how to report test\\nconclusions.\"), mdx(\"p\", null, \"Figure 1. Test Activity 5-Step Sequence\"), 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/caf341903034649f50378463567c3773/248b0/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\": \"18.91891891891892%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAECAYAAACOXx+WAAAACXBIWXMAABcRAAAXEQHKJvM/AAABRUlEQVQY0w2LW0vCcBxA95n6AD2G98/gwF7rYfbaQwn7V5vOoTA1oqQyw6SyNK81yZbD3U2dc5axKLp8hl97OBw4cDA/o1ABRiGDrIZ8CQn5GRkFWRWFUjoKMBJa2aqjpQiLljdrtC+p0Z64RHvdx5uQKU9Cpv1J1e3qTohV0yFmsIqddC0q3xmTuZqKzoUFOuanKFdVUNZl323UhUjGLwcsWzWy6aaVSdUnmXhF55jbIZdqmNxuWcrQ1zpHV4zD7ZKyjolDG7TZB9zxfTDsTzCdPzDmX/CsmdASR1DmVRD0GRiWA8r4FTTzDYYzB6bvP2A5v9Dtq/AgyNAWVGiI4xHGS5NIT7PDpRqP39yLeP9lgXfEEd7TbVybf+NF3gjHDiprVKG9QRc7xN5pM0oeVaPpqyfi7HFKsKUuQRdarvloLF8P/gOgBdlcGChcdwAAAABJRU5ErkJggg==')\",\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/caf341903034649f50378463567c3773/e3189/image3.png\",\n \"srcSet\": [\"/static/caf341903034649f50378463567c3773/a2ead/image3.png 259w\", \"/static/caf341903034649f50378463567c3773/6b9fd/image3.png 518w\", \"/static/caf341903034649f50378463567c3773/e3189/image3.png 1035w\", \"/static/caf341903034649f50378463567c3773/248b0/image3.png 1316w\"],\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, \"ANALYSIS, EVALUATION, AND REPORTING\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" produces a test report that provides results of its analysis and\\nevaluation of operational test data. Time constraints are a constant and\\ncompounding factor because \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E reports often inform a milestone or\\nfielding decision with a hard need-date. Test teams must analyze data,\\nevaluate impacts to the mission, draw conclusions, and draft and\\ncoordinate a test report as expeditiously as possible so the findings\\nare relevant and timely.\"), mdx(\"h2\", null, \"Analysis\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Analysis\"), \" is the detailed examination and application of disciplined\\ntechniques (e.g., mathematics, statistics) to understand or determine\\nessential features of complex problems. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" employs an\\noperations-based approach to analyzing system performance. Sound\\nanalysis produces technical adequacy and credibility. Test teams\\ntypically rely on measures of performance (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \") and measures of\\nsuitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \") to analyze \", mdx(\"em\", {\n parentName: \"p\"\n }, \"system\"), \" performance. Measures of\\neffectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \") are used to analyze \", mdx(\"em\", {\n parentName: \"p\"\n }, \"operational\"), \" performance. They\\nmay compare performance at the measures level against a criteria or\\nidentified standard threshold to determine whether there are shortfalls.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" operational evaluations are not based on findings attributed to\\noperational unit or operator performance shortfalls.\")), mdx(\"p\", null, \"Analysis provides the foundation or basis for evaluation. While we\\nseparate analysis and evaluation into different steps, there is no\\ndistinct \\\"line\\\" between them.\"), mdx(\"h2\", null, \"Evaluation\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Evaluation\"), \" is intended to be the judgment of a system's operational\\neffectiveness and suitability when exposed to representative threats\\nwhile being operated and maintained in a realistic operational\\nenvironment by typical operators and maintainers. Evaluations require\\noperational experience to apply judgment and place system performance in\\nthe context of intended operations.\"), mdx(\"p\", null, \"Operational evaluation determines the impact or significance of \", 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\"), \"\\nshortfalls by considering operational effects defined by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \".\\nSimilarly, the operational evaluation of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are in the context of the\\noperations defined by the critical operational issues (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"). After\\nevaluating COIs and measures, the test team has a basis for evaluating\\n(determining) a system's operational effectiveness and suitability.\"), mdx(\"h2\", null, \"Reporting\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Reporting\"), \" is dependent on numerous factors: the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activity, the\\ngoal of the activity, time constraints, and the status of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E (is \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nongoing or complete). However, regardless of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activity or\\ndriving need, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" will produce credible reports that are accurate,\\nbalanced, and timely.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Accurate\"), \": The test team analyzes and evaluates test data\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"meticulously to ensure the report's narrative and ratings are\\nconsistent and conclusions are defendable.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Balanced\"), \": The report's narrative highlights both system\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"capabilities and system limitations ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"what the system did well\\nand what it did not do so well\"), \" ) to enable mission effects.\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Timely\"), \": \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" delivers the report to decision makers to\"), mdx(\"blockquote\", {\n parentName: \"li\"\n }, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"allow them time to review and understand results prior to a\\ndecision date.\")))), mdx(\"h1\", null, \"STRUCTURE OF AN EVALUATION\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" structures a test program to facilitate an evaluation of the\\noperational effectiveness and suitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \") of a system under test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"); therefore, all activities leading to analysis, evaluation, and\\nreporting support a determination of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \". Figure 2 illustrates how\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" structures an evaluation of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"Figure 2. Structure of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Evaluation\"), 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\": \"687px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/b39f3d34c537aa7abc9c5d3db3e3423e/aec65/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\": \"122.77992277992279%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAZCAYAAAAxFw7TAAAACXBIWXMAABcRAAAXEQHKJvM/AAAGk0lEQVQ4y2VV7U+b1xW/Wtt1UrdmkzKtc/JhXzZpmrR9XKutX7b/oNpWaQlpUrG0K8GggUloaBMwMhFRSXgxFBwbMOYlDjbB4Hcbv2HwKzZ+we9gg0ObB6K2qdSoXD/37Dzemg+bpZ/Oufc+Pvfc+zu/c0ksFjsJBoOQzWbZo0ePYH9/H/b29qCQz0OmVIIkIrW7C/FcDmLZLAQTCQhHo5BMRCCVCkMiEYStLT9Eo+tgNBqAuN3ubw0GA7NarbzdbudNJhO/5nLxuXSaD3AcP+Tz8bcePuRlS0t8j1bL37ZYeCOulwom3mjq543G27xO18s/eHCTV6tHeJLAHbe3twEzhUgkAkK2wVAIkvE4PETbee8edCHaBodA3N8PLZ98AnM6HUTCWpicug6Dg20gk30AAwNiGBm5Vc/w0Ov1HrlcLs7pdHI2m40zm83cysoKN6/VcpMaDaecnuakfSNPRsbGj4bkcm5CoeDGx+WcXH6H6+rqfdLf38fdutXLSaU9HGlsbBRdunRJdPHiRdGFCxdE58+fFzU0NIjOoW1+7z1Rx5Vm0c1rrT8//7eWX/zxjabf9XW3v3bu7++caWpq/Nnrv//nb95884NftbaKX7t8uQX/946InDlzhpw9e5acOnWK/O/vZcSvf0DIGz8l5Cfktzj6+FVCel/54Ut/IOT7vhfJ966dJuSX5PSLhJx+6WXy4x9hjFwuR/DeSLlcJgDwf/jmvxD8KgNhn1cF/ztbfAaECms8kGxpn5BQKKTAgKp4PK46ODioo1gsqgqFgiqXy6uS2aIqkSmqkrmyKpEt3QvFc2r1wvrC2npiLpbO4TijCsbSKn8opjJbrCqyvr4OFosFHA4HCIxjIKhgLe5X9mCnUAZl6Bu4bdyD3gcJkOl3QKZLQvf9+POxYPuWMjDk+QI0eiuQVCr1LBAI1Px+P0WmKfoUr4EWiwWayeapdTNNl11RqrdvUq15g47P2qliwUGn9Wt0ftVD1UtO9O10xuChc1odJaiKEzwmVCoVJiikhMp4+vQpVKtVYQ6q+2V4+uUTKOaL4LC5IRYNg83iAo/LDX6fB9wuJzjtVlwzw/37C/UMTzKZDMooxfDIDIucYYYMr4K51pzMabewcMDPvG4v0y8amMtpq9tVwwozG5eZ4aGeLS1qmf7BApuammQEM3l2eHjIY5YUUROAeq6lksma071RM2wd1WY9xdqsO1+b85RqSmuuNrYcr02sxmqT9h0cpxDpmsqRrw2NT9YINgXAewOfzwcbGxsgkCTIz+vxwuTMMgzb9uHGzCZ0KhzQpfLATU0ArirW4eqnduia8qE0XXAd5/uW89A7MAZkbGysbXR0tEMul0uGh4clg4ODkoGBgTpGR0ckUqlU0ivrk0h7ZR09Uml7Z+fHH/717asftbV/9OH1ruvtHVc7O9olHZLW1lZJW1ubhNy9e5fcuXOnDplMRjAAuXHjBunp6SbDw3fJ+01icuVf1xCd5P1mCdbzn1/4S8M/0P7phea2ZtLwbhM5d+kyeevtc+TdRpzf2dkhyWSSYGETZLeOI44jjx8/Jp9Xq+T4oEy++GyfpKPJ5+pxWAPPfactRIqotp1UhgQCQSK0ryvIbAu2LzGWjXh3d1eMLIsz2aw4k06LU/E4IiaOBMItFqP72vZWpDkcjrQEg+Fmg8HV4XD4Wrxev1iA2WwRE4EQLGjweDyAkqt3a6H+ymiLAlA1BRz7gklUThFS2LkTyW3s8AkstTh4vRuosCgiAjabBQgy+8xoNNaw/1GdTkfX1tZoaXeXFrNZmvjqK7pardKVUomu7FWo7bNDajw4pMl8lB4fOVFJelqpmBBGenzsoGbzAhWawwm2f0Aw1DRDCTI8LstioYePj9kc+lOhEJtPbrP7Oym2tFdh27kQO/nWhyLQsHB4kkWjavb11y62uqphJJ/Pnwhyw6bA0AckCZAkSOKzsL4VA2s4DMaNTVDqrDBrsoN6xQr6ZQOYTVpYWtKARjMJJtM8OJ1amJlRgsDwCcpO6DQMmcYXbAtfsChg5hDY3IQNLHiv213Xr9vpRbsGOgy+uuoAg8GGAXUwN7cAs7MLMDGh+I+W0+n084DfBdvEYD5UjRvJstntcHTEIVllyBfyUCwVkcA8HB5W8Ts/qFRKDDwDcvkIkOXl5RME6PV6tri4CFqtFubn53HHWVCr1TA1NQVKpRKmp9WgUChgfHwcM5kAVBeMjX2Kr94Q9ONrKKC7uxv+DboTg4Q7xsCdAAAAAElFTkSuQmCC')\",\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/b39f3d34c537aa7abc9c5d3db3e3423e/aec65/image4.png\",\n \"srcSet\": [\"/static/b39f3d34c537aa7abc9c5d3db3e3423e/a2ead/image4.png 259w\", \"/static/b39f3d34c537aa7abc9c5d3db3e3423e/6b9fd/image4.png 518w\", \"/static/b39f3d34c537aa7abc9c5d3db3e3423e/aec65/image4.png 687w\"],\n \"sizes\": \"(max-width: 687px) 100vw, 687px\",\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 test team composes COIs that ask whether a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can accomplish its\\ncritical mission elements or operational objectives. Then, they develop\\na variety of measures within each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" to evaluate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s mission\\neffects, capabilities, functions, properties, or structure. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"\\nevaluate performance-driven mission effects and MOPs/MOSs capture system\\ncapabilities and attributes.\"), mdx(\"h2\", null, \"\", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Evaluation Structure\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E evaluation structure is a subset of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E construct. The\\nstructure uses the following elements to report results of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s\\nevaluation.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\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\"), \" ).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\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).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Critical Operational Issues\"), \" . A \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" addresses a critical mission\\nelement or operational objective examined during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E to determine\\nthe system's overall capability to support mission accomplishment\\n(often referred to as operations-based COIs).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\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(\"strong\", {\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(\"strong\", {\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(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Effectiveness\"), \". \\\"Are measures designed to\\ncorrespond to accomplishment of mission objectives and achievement\\nof desired results? They quantify the results to be obtained by a\\nsystem and may be expressed as probabilities that the system will\\nperform as required. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may be further decomposed into measures of\\nperformance and measures of suitability.\\\" ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition\\nGuidebook\"), \" ). \\\"A criterion used to assess changes in system\\nbehavior, capability, or operational environment that is tied to\\nmeasuring the attainment of an end state, achievement of an\\nobjective, or creation of an effect.\\\" (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \"\\xA01-02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Dictionary of\\nMilitary and Associated Terms\"), \" , \", mdx(\"em\", {\n parentName: \"p\"\n }, \"As Amended Through 15 Feb 16\"), \" ).\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Performance\"), \". Measure of a system's performance\\nexpressed as speed, payload, range, time-on-station, frequency, or\\nother distinctly quantifiable performance features. Several MOPs\\nand/or MOSs may be related to the achievement of a particular \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \". (\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition Guidebook\"), \" )\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Suitability\"), \". Measure of an item's ability to be\\nsupported in its intended operational environment. MOSs typically\\nrelate to readiness or operational availability and, hence,\\nreliability, maintainability, and the item's support structure.\\nSeveral MOSs and/or MOPs may be related to the achievement of a\\nparticular measure of effectiveness or multiple measures of\\neffectiveness. ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition Guidebook\"), \" )\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data/Data Element\"), \". Data is any measurement or information\\nused to determine the value of a measure. Data may be quantitative\\nor qualitative, subjective or objective.\"))), mdx(\"p\", null, \"The evaluation summary chart (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \") is a concise presentation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nevaluation structure. It summarizes the mission statement, COIs, and\\nmeasures using colored indicators to rate each element. Figure 3 is a\\nrepresentative \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \".\"), mdx(\"p\", null, \"Figure 3. Example Evaluation Summary Chart\"), 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/1b4ce8b1d68a710375991db28f1461ba/b79a5/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\": \"66.40926640926641%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAADa0lEQVQ4y01TW0yTZxh+/79/qZS2trSF/gMqYLE6TKgXM1tiiNvlbrZdbInxyjthC/MYNGYoNKR4AKGiWbKYuMxM4+bGIRKo9IQwf4RysAJtKatQGFSk9AQoXnx+LyuJF0+e73/f733ew/f+AABGkQgMlIvMZtjV0SE7RAhAeXmFmNpAJuNYnQ5E9MiwLDDIaKcxjFYLnFhM7f/bmGKOw3tQjGIIjoNCnv8iD+BIkYg5qOcY+IjeU1NfFhXjqZ+nZ2RqBw3FDvwGjuFZ2PJlomAOhTJ9Ac/5O5WyUlaeVQqc3GQ6oDL9eCLzEwD2YwCuQCQS00AuT63J0Fy8yO7PzAQTjaE+2Nes13+GgphNT7ErQyLRUlYT2jMCK0D+/hj6FdLaWuDVakZWXQ18WRkof6oBg1YB8t1nCnnIA6m7sHg3BpVhBoVSlU1Zcqr22qf3nk5ZbL3Pbj7qGbplC8y2PLDfrqI+MZ3xXsqK6rOwJy8HsquqYK9Oxqr05/NLwSRV/lFQVIqC+ygKdPn6XKzml07Xtx2eILEHX5OBhXUiLL4lPZORtbYhv885E/cNzK9ND4TfTP6zsBG2+ZYfYCJ8IzovCTIKlmDLWj5fhy91/ffu79o8YdI9ufKudzq56Qytk/bR/8Z+cwUsf48sXW8fX2lsH1u+1uldtf7qDJwFTYUKCs+pQH2a4qQKBfdgldkajR4rvNP58Bvb6CARQr7N8cjs5vPlMOkPjM33DDscnjmv2xvxu8cXp9wvXgVcwsyIYBvp83vCEz5vZNr3fCngQ0EjtmwwaHE9oKf7h6OzL80kunKFJOKNJJVsJAvzFvJvyEKi0WYSj1tJLNZCEokbJBK5SkIzNclY1JJMxi8nE7GGJGrgoEuMxlwZVtjVVXU4GKzvX11tdqRSrc6NjZvOcLjBFZw2OxKJFvva2g17KmXt3Vi3uuYWWv986H5c6fA+qxRCk1tAQUN6bXZKpRkKyjgHjoJND5lJL6w4bUNwmNx62/L50NRfZGKuiwSWHm9h+5WN6cXmsrK2RCXbgWmWfiAoqawol6Ng/5MTX9KWSSzaQN69bSKbb5rI9q+nZximKL3kuXftw6fv94233nWONbU99TQNC+aWEaGmcXTw0s9C34Wv6J0MCnlt3dclwuCFihcTdcf9/vrjPor3TFd2XpKBTy4AAAAASUVORK5CYII=')\",\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/1b4ce8b1d68a710375991db28f1461ba/e3189/image5.png\",\n \"srcSet\": [\"/static/1b4ce8b1d68a710375991db28f1461ba/a2ead/image5.png 259w\", \"/static/1b4ce8b1d68a710375991db28f1461ba/6b9fd/image5.png 518w\", \"/static/1b4ce8b1d68a710375991db28f1461ba/e3189/image5.png 1035w\", \"/static/1b4ce8b1d68a710375991db28f1461ba/b79a5/image5.png 1372w\"],\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, mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \" : Operational capabilities (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Capability\"\n }, \"OC\"), \") are depicted for context, but are\\nNOT rated or assigned colored indicators.\"), mdx(\"h1\", null, \"RATING TENETS/PRINCIPLES\"), mdx(\"p\", null, \"The following discusses some basic tenets or principles as applied by\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".\"), mdx(\"h2\", null, \"Rating\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Rating\"), \" (a verb) is the process of analyzing, evaluating, and informing\\non \\\"something\\\"---for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", the \\\"something\\\" are the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \", COIs, and\\nMeasures elements of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct forming the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Evaluation\\nStructure. Typically, the results or conclusions are done with a\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"rating\"), \" (a noun)---a shorthand to communicate the conclusions from the\\nanalysis and evaluation.\"), mdx(\"h3\", null, \"Terminology\"), mdx(\"p\", null, \"The term rating is a general term. Based on various guidance (e.g.,\\nTitle 10), the particular levels of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Evaluation Structure use\\nspecific terminology:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"We \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Determine\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"We \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Answer\"), \" COIs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"We \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Rate\"), \" Measures\"))), mdx(\"p\", null, \"We use a rating to summarize the conclusions for each of these.\"), mdx(\"h3\", null, \"Report\"), mdx(\"p\", null, \"A report is the tool used to package and communicate results of test\\nevents. An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test report can come a wide variety of formats---an\\nemail, a memorandum, a briefing, or a lengthy structured document.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" provides standardized forms or templates test teams use, or\\ntailor, to create a report.\"), mdx(\"h2\", null, \"Ratings and Visual Indicators\"), mdx(\"p\", null, \"Within rating taxonomies, the definition corresponds to the visual\\nindicator (color code) differently depending on which level of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nevaluation structure it applies to. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" applies visual indicators to\\nratings at various levels to give readers a basic understanding of the\\nconclusion without having to read the complete narrative (Figure 4).\\nHowever, the words associated with the colors are different at each\\nlevel so test teams must familiarize themselves with the actual rating\\nand avoid phrases such as, \\\"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" was rated Yellow.\\\"\"), mdx(\"p\", null, \"Figure 4. Rating Definitions vs Visual Indicator\"), 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\": \"585px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/c63b7dbae6812abcf7b6b5d97ebbb864/78a22/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\": \"68.72586872586874%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAYAAAAvxDzwAAAACXBIWXMAABcRAAAXEQHKJvM/AAADEUlEQVQ4y22T/UtTURjHv/du09293LtNm3Nuhlo5rDRW+VKtMirL3takaBbV3VYUGkIliAlZRGTQC00pqhnBSloZgdAP/RJJhlZKPwTVejFT+wMiqh+C23Pmok268OE559znfHm+5zwHSH5GBCBOwRNFRD4hGSGDIab/n0uUiJw8R+TlBTSel8SGVMEkbIObWEKUGhIiQc4AHzJ5F+zaDkhcoEDi5NUmTagkmz+42MjLqym3kjCnCMr4TzUEm4egQw2gYplO4i7lXRRowBPmfDTrDfq9ZgkB7n+CQtJuzhTyDKowR0CtTqtDplotCOv2e41MLCdS11H+sGkCZ0qKEagG7i/jUqvhkoIGGhdTzKZYSIKFRgQLLNpNIonoCVXr6fbZtzq7m4tu1D+oenRUQfuiSlwuR8a5tXyavXTLU9HEB8jXbtjEzQkn8fi7WcMjw2WKouQB29Vww9E64sW13/u5fqUVbJOFyCWcJGalaE/ObTTPs2hC9jyxIZcE0NNzuy4ajW7rDJ91Mcv9TzZeGH6+9evTQe/Cj5/9iH/Ywf8VZGdWxAQoErKZxo4szb5iAXvswBJr772+U3fu9PhratZlJS9DOzjojb5+s10ZGti8bGLUj7FPfn7ajf4DWIENq04mbL59/7J6aGjAN/5l0tbYeCix5rKqwKpuWonCn4ddUK5UcErfeqSel5nZZBVa1CEr7RHqfWfnn+uI1l3punuA5hmMGdlWyS3o2C0Lr53Oq9+XLv/2GKiI08KoWsWnCmYRM018sACotx9rvuZrCF3ynWjr3kb5VnPGFoNzpsR6T6iVJB1F9Vub7eqPqsofTyjhIy2MTxOEgSKwBsFdF/Dm3YvqsfFX7sDO87RGVjAfvJqZpd41GBL9wybUS6WK3w8lFkscwXRBTlF+gS6CnpDXqsNeOgLZaeL2ObTw6BP9D04qLSszMfvXI5HI2OSkcrytrfZmJILeWIxPeykmLogsTYi9VZHOkbWOlcYO9lL0qNVSmob6OtPj8Qismq6uriPPBgbGWlpaFobDYXRHIvwfSPXrUYWr00wAAAAASUVORK5CYII=')\",\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/c63b7dbae6812abcf7b6b5d97ebbb864/78a22/image6.png\",\n \"srcSet\": [\"/static/c63b7dbae6812abcf7b6b5d97ebbb864/a2ead/image6.png 259w\", \"/static/c63b7dbae6812abcf7b6b5d97ebbb864/6b9fd/image6.png 518w\", \"/static/c63b7dbae6812abcf7b6b5d97ebbb864/78a22/image6.png 585w\"],\n \"sizes\": \"(max-width: 585px) 100vw, 585px\",\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(\"h2\", null, \"Rating Taxonomy\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses the rating taxonomy to indicate results from analyzing,\\nevaluating, and rating a test activity across levels of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nevaluation structure. It provides the traceability and rationale for\\nconclusions drawn at each level. Currently, there are three pre-defined\\nrating taxonomies that support established test activities (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \",\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Assessment\"\n }, \"OUA\"), \"). These taxonomies enable consistency when reporting\\ntest results. A brief summary of each follows.\"), mdx(\"h3\", null, \"\", mdx(\"abbr\", {\n parentName: \"h3\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E and \", mdx(\"abbr\", {\n parentName: \"h3\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \" Rating Taxonomy\"), mdx(\"p\", null, \"This taxonomy is used for programs acquired within one of the six\\nadaptive acquisition pathways (\\\"\", 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 Guide\\\" contains info on\\npathways). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&Es for these acquisitions inform development activities\\nand acquisition decisions. Effectiveness and suitability is determined\\nand reported.\"), mdx(\"h3\", null, \"\", mdx(\"abbr\", {\n parentName: \"h3\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \" and \", mdx(\"abbr\", {\n parentName: \"h3\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \" Rating Taxonomy\"), mdx(\"p\", null, \"This taxonomy is used for test activities where progress toward both\\neffectiveness and suitability and programmatic progress are being\\ndetermined and reported. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \"/OAs are broken into two areas.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Area 1. Used to rate system/capability progress and assesses\\nprogress toward operational capabilities (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \").\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Area 2. Used to rate programmatic progress and assess progress\\ntoward delivery of combat capability. The test team assesses major\\nimpacts affecting the progress toward \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \" certification of final\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activities by assessing three separate programmatic topics as\\norganized in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63\\u2011119. The three topics are test planning and\\ndocumentation, system design and performance, and test assets and\\nsupport.\"))), mdx(\"h3\", null, \"Operational Utility Assessment (\", mdx(\"abbr\", {\n parentName: \"h3\",\n \"title\": \"Operational Utility Assessment\"\n }, \"OUA\"), \") Rating Taxonomy\"), mdx(\"p\", null, \"This taxonomy is used for non-traditional programs (joint concept\\ntechnology demonstrations) when operational utility is being determined\\nand reported. OUAs provide the test team's judgment of a system's\\nmilitary utility when exposed to representative threats while being\\noperated and maintained in a realistic operational environment by\\ntypical operators and maintainers.\"), mdx(\"h1\", null, \"Ratings for Continuous and Cumulative Feedback\"), mdx(\"p\", null, \"The majority of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" programs require continuous feedback during\\nsystem development due to agile software development approaches with\\nrapid release and fielding cycles. However, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" provides some degree\\nof continuous feedback on all programs to inform development activities.\\nIn these cases, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" provides \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" impacts when practical, but rarely\\nprovides \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" ratings. Reporting results in a timely manner is\\ncritical and limits the amount of analysis and results \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" can\\nprovide beyond the \", 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\"), \" level. Furthermore, stakeholders may not need\\nfeedback beyond the \", 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\"), \" level at that time.\"), mdx(\"h1\", null, \"RATING MEASURES\"), mdx(\"p\", null, \"Rating measures consists of analyzing, evaluating, and informing\\nresults. In most cases, analysis should be concurrent with test\\nexecution. During execution, test teams should verify continuously that\\nthey are associating data with the correct measures or supporting\\nmeasures, and that analytical techniques and data management procedures\\nare working.\"), mdx(\"h2\", null, \"General Methods for Rating Measures\"), mdx(\"p\", null, \"The test team must synthesize ratings of individual \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" in order to\\nrate COIs. Accordingly, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may depend on rating MOPs and MOSs.\\nMeasures form a credible basis for rating COIs, effectiveness, and\\nsuitability. The two primary methods for analyzing and rating measures\\nare direct measurement and reasonable inference.\"), mdx(\"h3\", null, \"Direct Measurement\"), mdx(\"p\", null, \"Direct measurement is evidence observed during testing that supports the\\nconclusion that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" will be similarly successful when employed by\\nthe warfighter in an operational environment. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" document operational\\neffects that can be summarized as a proportion, percentage, or rate of\\nsuccess. In other words, if 80% of targets are destroyed, the overall\\ndetermination of operational impact (defined by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \") is likely\\npositive. In this case, we have direct evidence of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s (mission)\\neffectiveness. However, if the test is small and 4 out of 5 targets are\\ndestroyed, the test team should be more cautious when rating the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \".\\nFor example, 4 or more successes in 5 trials will occur 19% of time if\\nthe actual success rate is 50%. When the sample size is small, it is\\nimportant to use MOPs and MOSs as clues to determine how\\nunrepresentative (lucky or unlucky) the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" data might be.\"), mdx(\"h3\", null, \"Reasonable Inference\"), mdx(\"p\", null, \"Reasonable inference is evidence that supports the logical conclusion\\nthat the system will successfully (or unsuccessfully) achieve desired\\neffects and accomplish the mission in an operational environment.\\nReasonable inference depends on the degree to which the system satisfies\\nrequirements and performs necessary \", 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\"), \" operations/tasks. MOPs and\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" are often formally stated or derived from requirements documents,\\nand therefore have associated performance criteria that must be met by\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s developers. Test results for a \", 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\"), \" can be compared to the\\nperformance criteria, and the test team can infer that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" will or\\nwill not be successful (relative to \", mdx(\"em\", {\n parentName: \"p\"\n }, \"what\"), \" the \", 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\"), \" actually\\nmeasures) in the actual operational environment.\"), mdx(\"p\", null, \"One drawback of using \", 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\"), \" for an evaluation based on reasonable\\ninference is that requirement performance thresholds (criteria), the\\nguiding star for reasonable inference, may not accurately represent the\\nperformance required for desired effects. For example, a requirement may\\nstate that the average miss distance of a weapon (an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" measure) must\\nbe less than 30 meters. During the test, the average miss distance was\\n35 meters, but 80% of targets were destroyed, demonstrating the\\nrequirement was overly conservative. To overcome the uncertainty\\nconcerning the validity of the stated requirements, a well designed test\\nshould explicitly plan for the collection and evaluation of effects\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \").\"), mdx(\"h2\", null, \"Types of Measures\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses three types of measures---\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \". They are the\\ndata (sets) used to rate mission effects or operational impact, and are\\nevidence of the system's positive performance characteristics,\\ncapabilities, and deficiencies. MOPs and MOSs indicate specific\\nstrengths and weaknesses of a system, mitigate statistical issues\\nassociated with the typically small sample size of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" data, and support\\nor refute \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" conclusions. MOPs and MOSs are useful for quantifying \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\nperformance and, as they are often continuous data, can be used to\\ncreate analysis of variance or regression models of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance\\nacross variable battlespace conditions. In addition, MOPs and MOSs are\\noften used as evidence to validate Deficiency Reports (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deficiency Report\"\n }, \"DR\"), \") at a review\\nboard. A common analogy is that MOPs/MOSs provide a perspective on\\nindividual trees, but \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" provide a perspective on the forest.\"), mdx(\"h2\", null, \"Measures Worksheet\"), mdx(\"p\", null, \"The measures worksheet is used to document and organize details of a\\nmeasure. Measures worksheets contain significant detail about a measure\\nand how the data will be collected. For example, the scope section\\ndefines and qualifies the measurement attribute of interest.\\nUnderstanding the data in the header of a measures worksheet will be\\nsufficient for purposes of this guide, but a complete discussion of the\\ncontents of a measures worksheet can be found in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Measures\\nGuide.\"), mdx(\"p\", null, \"The header of the measures worksheet contains a concise summary of the\\nimportant information regarding a measure. It states the attribute of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" that the test team is measuring (operational capability), a\\nshort title (measure statement) describing what is being measured that\\nconveys information about the attribute, how it will be computed (the\\nmetric), and the basis for judging the metric (the threshold, if\\navailable). Table 1 is an example of a measures worksheet header within\\nan \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" report.\"), mdx(\"p\", null, \"Table 1. Standard Measures Worksheet Header\"), mdx(\"table\", null, \"\\n \", mdx(\"thead\", {\n parentName: \"table\"\n }, \"\\n \", mdx(\"tr\", {\n parentName: \"thead\",\n \"className\": \"header\"\n }, \"\\n \", mdx(\"th\", {\n parentName: \"tr\"\n }, \"\\n Operational Capability: Accuracy\\n \"), \"\\n \", mdx(\"th\", {\n parentName: \"tr\"\n }, \"\\n \"), \"\\n \", mdx(\"th\", {\n parentName: \"tr\"\n }, \"\\n \"), \"\\n \", mdx(\"th\", {\n parentName: \"tr\"\n }, \"\\n \"), \"\\n \", mdx(\"th\", {\n parentName: \"tr\"\n }, \"\\n \"), \"\\n \"), \"\\n \"), \"\\n \", mdx(\"tbody\", {\n parentName: \"table\"\n }, \"\\n \", mdx(\"tr\", {\n parentName: \"tbody\",\n \"className\": \"odd\"\n }, \"\\n \", mdx(\"td\", {\n parentName: \"tr\"\n }, \"\\n Measure\\n \"), \"\\n \", mdx(\"td\", {\n parentName: \"tr\"\n }, \"\\n Metric\\n \"), \"\\n \", mdx(\"td\", {\n parentName: \"tr\"\n }, \"\\n Threshold\\n \"), \"\\n \", mdx(\"td\", {\n parentName: \"tr\"\n }, \"\\n Results\\n \"), \"\\n \", mdx(\"td\", {\n parentName: \"tr\"\n }, \"\\n Rating\\n \"), \"\\n \"), \"\\n \", mdx(\"tr\", {\n parentName: \"tbody\",\n \"className\": \"even\"\n }, \"\\n \", mdx(\"td\", {\n parentName: \"tr\"\n }, \"\\n MOP 2.1: Miss Distance\\n \"), \"\\n \", mdx(\"td\", {\n parentName: \"tr\"\n }, \"\\n Mean\\n \"), \"\\n \", mdx(\"td\", {\n parentName: \"tr\"\n }, \"\\n \\u226420 meters\\n \"), \"\\n \", mdx(\"td\", {\n parentName: \"tr\"\n }, \"\\n 20.5 Meters\\n \"), \"\\n \", mdx(\"td\", {\n parentName: \"tr\"\n }, \"\\n \", mdx(\"span\", {\n parentName: \"td\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"48px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/e246abddf2a51a9e75b101fe3824e795/5ecaa/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\": \"112.5%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAXCAYAAAALHW+jAAAACXBIWXMAABcRAAAXEQHKJvM/AAADm0lEQVQ4y7VVS0hVURRdvuuvj1mWIkiZ4iAHRYKWJJWONAuzkCRoIEQoBIaB4QcrKBIxsHRQgwYpKH0ICgQrAoUKKRJrFEkSUoKJCqVlPt97p7XPOff6XtGwA5t7z757r7P25+wLcKWmAtXVQGYmsGEDfEoZnTy51lA2U7ZQEkS3dav5lpUFX2EhcPOmsdcrORm4fx84exYoKIAjOjEm8JFTp/Dg+nWM9fVhnrLQ1YWPNTV4mJKCY/YwlJfD6e4GZmeBTZuoKCkxYIcOwYmL0zZp3D8dGYHy+4mtImV5GertW6imJrykbZZEVVUFR1geP04NT8PevXBWr9ZgO27dwmQwqJ2XRfgeDAQQEpF3Vy/gZD3n8yE/LQ04eBBORgYRCBRlo0/hKZ8skyWyCwnDUAgh7rUIqOjIUvZ+sb19G19tjpGYSCwqdRFOnsTdxUUDRkflgogTQZVl7entXtuePo1+waC45JD7+LExXloyDj09CFVWQk1Pr+SvtxdKdJOTxkai4DM4NAQp0X6NVFcHFBXh0tSUdvJLWGL85o02Uky4BiOI3peVmT0Zhmw6/HNzUCxqBzvCtEh9PZ7aMANiJJUUp44OA/LuHRRbSMXEQP365QHq/FICsr94Ea/cVnLa2zFmjYLWSOdNdPn5UOvWGWD2m9c6NrdSKKm8unYNn2kTI4DRV6/iYzhguNPoqAErLY1g5ooHyHC/0C5Wh9zYiEHLKPAnQ2kTtoM6f/4vdhEhX76MUR1vaytw4ADaZ2ZMUayR2xZqfh4qPh6KefYAw8AkmuVv36AqKnDj0SN4a9/goHYIulV2Q//xA4r3WjU3RwB6jS5RDQ/rQ0vXrzdVjpKwz5zBExum32VggZW01PfvK4Vw9RR9Wxoa8Nw2NpCeDp9lue3ePSzYxPv/uBkRYPKN7PR9Zph++u4UgOxsYuXlmWnB9pCZVtLf7wEIaMDeX+lNd0AE3Hv87BkUB8Jh1gDnzsE5epSoLS2G6pUrcIqLNdPdbW14Pz4eMbZC4UwnJnSbTLD6RSdOALymjmC8eEHvjRsNoIicEh2tQWNzc1HHQgzfuYOFgQEoEabk54ULeL1nDxpos3YLZ3hnpwGTlZBgkyfVESUbHDTWORX61pADH9utZIpOWMliszsfPhg73qbIlZQE5OSs7PmP8U4OX6KrrYXDwapH1a5ddvT/a7HnIL8CDgI4jt5H8ekjgE/eY2OBVauMSLr++/oNZ3YRzGiFgDMAAAAASUVORK5CYII=')\",\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/e246abddf2a51a9e75b101fe3824e795/5ecaa/image7.png\",\n \"srcSet\": [\"/static/e246abddf2a51a9e75b101fe3824e795/5ecaa/image7.png 48w\"],\n \"sizes\": \"(max-width: 48px) 100vw, 48px\",\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 \"), \"\\n \"), \"\\n \"), mdx(\"br\", null), mdx(\"br\", null), mdx(\"br\", null), mdx(\"h2\", null, \"Rating Measures of Effectiveness\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" measure the degree to which the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can directly achieve desired\\noperational effects. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" communicate operational effects to\\nstakeholders (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \", warfighter) and how successful the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is at\\nconducting its mission. The operations and associated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are\\nconsidered anchors for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E construct and the evaluation structure.\\nWhen rating \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", the test team must consider the significance of the\\neffect demonstrated, through \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"direct measurement\"), \", as well as test\\nconditions, DRs, and application of operations experience and judgment.\\nThe test team night have to use \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"reasonable inference\"), \" to rate\\n\", 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\"), \" performance.\"), mdx(\"p\", null, \"Figure 5 depicts the rating logic for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \". \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may or may not have an\\nassociated criteria (or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Identification\"\n }, \"ID\"), \" standard). If there is a criteria/standard,\\ndetermine whether it was met or there was a capability shortfall. This\\nis a mechanical step and the outcome may not be operationally\\nsignificant, but external agencies (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \" and developer) are\\ninterested in knowing whether user criteria was satisfied. If there is\\nno associated criteria/standard, document the demonstrated effects\\nwithout comparing to a criteria/standard. If there were no shortfalls or\\nnegative effects, rate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" as \\\"No Shortfall\\\" or \\\"No Negative\\nEffect.\\\" If there was a capability shortfall or negative effect that did\\nnot impact mission accomplishment, rate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" as \\\"Shortfall, Not\\nSignificant\\\" or \\\"Negative Effects, Not Significant.\\\" If a shortfall or\\nnegative effect impacted mission accomplishment, rate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" as\\n\\\"Shortfall, Significant\\\" or \\\"Negative Effects, Significant.\\\"\"), mdx(\"p\", null, \"Figure 5. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" Rating Logic\"), 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/6b9833f68a1524a0b0cf7cfa443edbc8/c61d0/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\": \"76.06177606177606%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAABcRAAAXEQHKJvM/AAADO0lEQVQ4y4WUa0hUQRTHz927urv36r53bbe03LayxxqtSZJpC6UEhmARQWCQH6yMsuiJFUlB0oeIssKSkiAS60NlXyqooGJdY9tHD5A0bXtuUUku0fZi+o97C4WogR9z7sx/zpkzc+YSEQnABIzAoNh65XuWghfMAQUKmcq8aYQ+g5SmArkgB2SDCWAimKvAHS0GFaAYzFN6t6LljAVZ9J9mJrJZiKbJJJcZSFsIezwysBmUHf2zCaMxCqk1y5COyUOCdTp6pG7HruozhmMNa0at+91qwTHQCBrAA7AA7AJ7JBxZBgnmqSTYcCw16RjHGMNcJWj/rRvBsKORHAflfEIkQRYRQCTTNy0ZQjqLdF602c1p1dVW7GgmSdJhxUnj3xzuUQtCo4Zoi6awMJzmdBaNtVh8E+22KjupqYTUYpGKqnGzeS6VKt+s0dxTE+2AfpsWWapTu27lDveDDWAfDrtRXVd3XcUYI8YGQVw5X9kKcJ77kHIE3+hoicpk2g2bgU45dfFJrm9CWmt1ROsyc3ObpJQzljc0NFT/Jv56E+z5YsvyPNpb4ITd8OLli0eJRCICu4JrHY6FDiIPSqcYAYO8BE+iSLPHwJjkdObncNGrVx/qe3t7WSgcYsn3yXO57avOOs5WHxh8/uFc55VOFgrdZ2/ffuLByGzOmYG1PqIpyOJEqrgFweUUhEWO4uJHGi6KxZ5n+f1dpTdu3ip9+rjPTQdnc6H659cfyyPRaHN/f/9h6GZzrcfThlsvyRbInaVKlY1Eej1/SvMQwYL0c9RK2n+Q6LTWSmd0I8d4AJdrl2y1tmkztJWmzHQUpwFu+FxzcxZ5vWlcaABGYAYyY610sGlQJF2TntL36tvPxETGwqr16w9RTc1q2rp5G7W0ddCllTvJ75s7fM+USMj6QCDttt+/pCqZZH2RSOh7PB5nX758P8J3YjROm6y8Z68kecfh9Yg9PU9rA4HAxa67dy88fP9xf6xs8fZ3eVM6WMtRos+fjZpgkFY/ebLRE432nLp27erl7u7uqwMDsVrG7pAse/DTsE8lcrh1uiIbD9LX96w0EOiqCweDa3o/DS0d8JX7XjudK1jFIvoFDBc7ojuO1fkAAAAASUVORK5CYII=')\",\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/6b9833f68a1524a0b0cf7cfa443edbc8/e3189/image8.png\",\n \"srcSet\": [\"/static/6b9833f68a1524a0b0cf7cfa443edbc8/a2ead/image8.png 259w\", \"/static/6b9833f68a1524a0b0cf7cfa443edbc8/6b9fd/image8.png 518w\", \"/static/6b9833f68a1524a0b0cf7cfa443edbc8/e3189/image8.png 1035w\", \"/static/6b9833f68a1524a0b0cf7cfa443edbc8/c61d0/image8.png 1145w\"],\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 6 contains \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" ratings and visual indicators, and includes an\\n\\\"Inconclusive\\\" rating, which should be used only when analysis does not\\nallow a credible effects determination. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" Notable findings are\\naddressed later in this section.\"), mdx(\"p\", null, \"Figure 6. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" Ratings and Visual Indicators\"), 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\": \"853px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/67a8e7809655d9884d926e93f455b88a/66caf/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\": \"66.79536679536679%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAACHVAAAh1QEEnLSdAAACUUlEQVQ4y22Ty2sTURTGvySa1+TOTN5pqrVJtYmQEkurlFZRUXdCsahVSNO8FtEaqbqQgu50IXTTheDKVUVEXIlB2mJpRBAVuywKunHpxv+gfjdzQxLjHX5zz32c55zBxNot27HXNzG2WgMwB8NVgo5uBEoOzuPEsNbFJlLuGdlXBYy8yJ/KPM2ngYpuuEt9vCiJEb+S42oOkwN0oOkoSEe2TsfNEXx+B8HVxfP+J4tZDVdN3V0e4OGgVFQG95ODwlpLJ2lG5xVW5Ogx+GMb2PmEy9tbOAo8M+K+3AAv9vNCkCRFO0K5H1aOZJRDEsqhLoMfGho23oqpd+tiCFjxRT1zMaUYIPtUVFIpLKw9SZByVFhnRpfBP+YwfvtT+Z9aahK43xfDfEampVLNkpRiREcxyvkwyag9d0/K7+/VsLV0Y3JjqZYEztkToqzRs6yRi5cE8RCnVGbtnGotDclzh1XHQkfKX39hrbFzbfPj9+Nc6lFvlUUvHRJW8WW7wECl1T7/tFQFPsyiH5vttllfB+p1TNXfgDV86Y16cxH1dUPWhym7fbhC5etwYhQBPEQQDxDCCnb52KB19+G3xwJflvVHn5f1GaAh4p4c61Nk/YoJRiijjJiowoOa0rhAzirZ1dvYyYtwcIqQMAsS4mySAPErQh3E23u2pk5Ll8SaZz7U9uru2VHDmRu2YcK+xx52OBBXpOlsl/fyg8D8GHDpCFDIAtNeKxzTzlcnkP9kwkD5JOt1QqBsapjBeNNIa5wmC8xtwQfc9QBVRnibjs7gf+MvJz+Lywxv+NYAAAAASUVORK5CYII=')\",\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/67a8e7809655d9884d926e93f455b88a/66caf/image9.png\",\n \"srcSet\": [\"/static/67a8e7809655d9884d926e93f455b88a/a2ead/image9.png 259w\", \"/static/67a8e7809655d9884d926e93f455b88a/6b9fd/image9.png 518w\", \"/static/67a8e7809655d9884d926e93f455b88a/66caf/image9.png 853w\"],\n \"sizes\": \"(max-width: 853px) 100vw, 853px\",\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(\"h3\", null, \"Basis for \", mdx(\"abbr\", {\n parentName: \"h3\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" Evaluation\"), mdx(\"p\", null, \"Test teams use the following considerations when evaluating \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \":\"), mdx(\"h4\", null, \"Effect Criteria or Identified Standard\"), mdx(\"p\", null, \"When a threshold (criteria or identified standard) for an effect is\\nprovided, it should be the basis of a test team's evaluation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \".\\nTest team judgment is still important because some thresholds of\\nperformance are overly conservative while others underestimate the\\nrequired effectiveness.\"), mdx(\"p\", null, \"A significant challenge in evaluating an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" is that they may lack an\\nauthoritative threshold from which to base a rating of the measure data.\\nIn other words, if the success rate during a test was 75%, there is\\nseldom a requirement that states the minimum acceptable success rate is\\n80%. In addition, MAJCOMs are unaccustomed to providing an identified\\nstandard such as \\\"the success rate should be at least 80%.\\\" Test team\\njudgement and expertise is required to rate an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" without an\\nauthoritative threshold.\"), mdx(\"p\", null, \"If a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is conducting the same mission as a legacy system, then attempt\\nto derive \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" effect thresholds from the relevant operator community.\"), mdx(\"h4\", null, \"Feedback from Test Participants\"), mdx(\"p\", null, \"Test participant feedback on usability of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" should contribute\\nsignificantly to an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" rating. An operator is trained to perform system\\ntasks in order to achieve operational objectives; and if the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is\\nusable and effective at enabling them to perform system tasks, the test\\nparticipant feedback should be very positive and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" rating should\\nbe No Shortfall or Negative Effect (Green). If participants struggle to\\nuse the system to complete the test scenarios, the rating should be\\nShortfall or Negative Effect, NOT Significant (Yellow). If participants\\nare unable to complete the mission during testing, the rating should be\\nShortfall or Negative Effect, Significant (Red).\"), mdx(\"h4\", null, \"Problems/Deficiencies\"), mdx(\"p\", null, \"The number and significance of problems and deficiencies discovered\\nduring testing should contribute to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \"'s rating. Systems that\\naccomplish the mission but have problems that must be addressed by the\\ndeveloper are likely not worthy of a \\\"Green\\\" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" rating.\"), mdx(\"h4\", null, \"Required Workarounds\"), mdx(\"p\", null, \"Although \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" should be conducted per established employment and support\\nconcepts, TT&Ps and tech data workarounds are common. The significance\\nof workarounds to accomplish the mission should factor into the rating.\\nMission effects may not tell the whole story, because operators and\\nmaintainers are conditioned to accomplish the mission by overcoming\\nadversity, including system constraints. Workarounds can affect test\\nscenarios, performance results, safety, and skew operational effects\\nduring \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". Workarounds may also be reasonable as a short term fix during\\ncombat operations, but are unacceptable during ongoing peacetime\\noperations.\"), mdx(\"h4\", null, \"Statistical Confidence\"), mdx(\"p\", null, \"It takes a relatively large amount of test data to be statistically\\nconfident the point estimate of the proportion of successes and failures\\n(from the test of a system with variable performance) is close to the\\ntrue success rate that will be observed in the field. For example,\\nsuppose the \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"true\"), \" success rate of the system was 50% and the test\\nhas 5 test events.\"), mdx(\"p\", null, \"There is a 0.62 probability (0.31 + 0.31) that test results will be\\nwithin 10% of the true success rate of 50% (i.e., 2 or three successes).\\nFurthermore, it is impossible with a sample size of 5 to accurately\\nestimate a success rate of 50%; the closest possible outcomes are 2\\nsuccesses out of 5 (40%) or 3 successes out of 5 (60%). To have a 0.80\\nchance that the test results are within the range 40-60%, the test would\\nrequire 30 pass/fail events. If the sample of mission successes and\\nfailures is small, other sources of data become much more important in\\nthe evaluation of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \".\"), mdx(\"h4\", null, \"Reasonable Inference of \", mdx(\"abbr\", {\n parentName: \"h4\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" and \", mdx(\"abbr\", {\n parentName: \"h4\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" Impacts\"), mdx(\"p\", null, \"Test teams may use reasonable inference to develop an estimate of\\nresults for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" (i.e., the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" is not directly measurable) or may be\\nused to bolster results for an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" (i.e., small sample size). A variety\\nof techniques are available for this, such as rationale argument,\\nweighting schemes (discouraged), algorithms/formulas, models, and\\nsimulations. This is sometimes referred to as \\\"rolling up\\\" or\\naggregating to an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" or possibly a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". The preferred approach is to\\nuse direct measurement---aggregating can raise questions about the\\nvalidity of the conclusion.\"), mdx(\"h4\", null, \"Key Performance Parameters\"), mdx(\"p\", null, \"Key performance parameters (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \") are not a significant consideration\\nwhen rating \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \". While they highlight important characteristics of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\nperformance, the test team should place them into the context of the\\noperation to evaluate operational effect no differently than any other\\ncapability requirement. If a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" threshold appears contrary to\\noperational effects (or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" rating), the test team should recognize the\\ndifferences and document to communicate the rationale.\"), mdx(\"h4\", null, \"\", mdx(\"abbr\", {\n parentName: \"h4\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" Notable Findings\"), mdx(\"p\", null, \"The test team may document notable findings at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" level of the\\nevaluation for two potential situations. First, there was an additional\\nobservation made on one or more \", 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\"), \" that had an operational effect\\nmeasured by an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \". Second, an operational effect was recorded, but\\nthere was no corresponding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \". \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" notable findings are included along\\nwith the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" as part of the process of evaluating a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \".\"), mdx(\"h2\", null, \"Rating MOPs and MOSs\"), mdx(\"p\", null, \"Typically, test teams analyze MOPs and MOSs by summarizing the measure\\ndata (with an average, percentile, median, user rating, etc.) and then\\ncomparing that value to a threshold value (provided by the operational\\nuser as a criteria in capability requirements documents) or an\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"-formulated identified standard. Rating an \", 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\"), \" is a two-step\\nprocess (Figure 7).\"), mdx(\"p\", null, \"Figure 7. \", 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\"), \" Rating Logic\"), 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/bae1e4e348a78fabaf5658337ed25708/669eb/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\": \"56.37065637065637%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAYAAAB/Ca1DAAAACXBIWXMAABcRAAAXEQHKJvM/AAACdklEQVQoz4WSXWhSYRjHn3PUc46diU23mdv62Kix9cWGJRrF2KJBw5su3FUUjAxqQeEi6mpBIwi6ii4CW5Bd7KLILjLLCcI+2kIMFVxe5GCDTLSTM0fDj3p73qPRBsEO/M77nPc858///Z8HYOurHelFrIgJMSPHas91//2C3cYBIQTMgVGmxWVnSIkwCx8WFLjHmkxHeGwxVtHqcTVUa6YBgMBWgtD6eAhIkcBi4hOk02mIRGJyj0ZD74SvilBjTchd5CMibNJTsyKnf4CCPZ7Lncr7/RYUH0kuLQUkSXoXjy86sIe3WG6hpBrdGdHldTXAiArgHr66jZzZJNjEcMoeWhx+denEjif2ofXsj/HZ93NSKBSSlpdXrlD3VutFbdWWGtc7KDiGbsdxa6zGxiOrVfKRu6acsNd9ATLktxKfuRqswzEFPO9TADzCsx1FhzdYgKsQjX5h8D0Fvk9OwsxG0Rd9mE5iN5B1kMW/ZbNQKBTkmpASo9Wex65RdLerHuBmbZ9ApVyGX7Tf/eyfoNN5CMMfgPl5u+DxdIrY2J1Ofx3M5/M2rDvohwbDMGZ4SsuyZ/GPXFOFQikW9+tLxaK+TIgu89TNzQJsp3o7BUFxHFcukbAP+nw2ZybzMxCLRUgy+ZlIUn6CChqN7Qfp/CmVTDdGWedyxVrD4fDrmenpYCQe90YmnttW9nU8lB22tWkwh3Pg9Q4IqdSwGAzOdXk8L3v9fn9fNBrZQ4gfRLFfB7C/kWHMmOFpnmaby+WaK5VKC9bNa299whwO6t9TNygUdFChsQYdNA4RESVt0OkO0DlkqvN4Us5vdTUnZ0jrNd8bQEH4AxMIGKRDp8+1AAAAAElFTkSuQmCC')\",\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/bae1e4e348a78fabaf5658337ed25708/e3189/image10.png\",\n \"srcSet\": [\"/static/bae1e4e348a78fabaf5658337ed25708/a2ead/image10.png 259w\", \"/static/bae1e4e348a78fabaf5658337ed25708/6b9fd/image10.png 518w\", \"/static/bae1e4e348a78fabaf5658337ed25708/e3189/image10.png 1035w\", \"/static/bae1e4e348a78fabaf5658337ed25708/669eb/image10.png 1244w\"],\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, \"Step 1 is somewhat mechanical and documents that the system performance\\nmet or did not meet the threshold. The program office relies on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ndiscerning whether the benchmark for our rating is user-provided\\ncriteria or a standard developed by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" as a test planning standard\\n(the \\\"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Measures Guide\\\" contains more info on thresholds). For\\npurposes of this guide, criteria and identified standards are used\\nsynonymously as a threshold unless stated specifically.\"), mdx(\"p\", null, \"When \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance meets user-established criteria, the \", 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\"), \" rating\\nwill be \\\"Met Threshold.\\\" It is not operationally important whether or\\nnot a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" meets a threshold---\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s focus is performance-driven\\nmission effects. However, this information is provided because it is\\nimportant to external agencies such as the users and program offices.\\nWhen a measure does not meet criteria, the system is said to have a\\nshortfall. The test team must determine whether the shortfall is\\noperationally significant to the user community.\"), mdx(\"p\", null, \"Step 2 of the \", 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\"), \" rating logic addresses the operational\\nsignificance of performance shortfalls. Operational significance is the\\nconsequence or impact on an operation's outcome if a performance\\nthreshold is not met. A \", 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\"), \" can fail to meet a threshold, but not\\nhave a significant operational impact. Ultimately, the operational\\nimpact on an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" determines whether a shortfall is significant. A\\nshortfall having little to no impact on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" is rated \\\"Did Not Meet\\nCriteria, Not Significant.\\\" A shortfall that has mission effect is rated\\n\\\"Did not meet Criteria, Significant.\\\" Operational significance is the\\nprimary technique for rating the \", 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\"), \"; however, the test team should\\nconsider the operational significance of other factors, such as DRs, and\\napply operational experience/judgment to determine significance. The\\nfollowing paragraphs present additional considerations in determining\\noperational significance.\"), mdx(\"h3\", null, \"Test Conditions\"), mdx(\"p\", null, \"Performance measures may meet criteria under some conditions, but not\\nall, or a system may only be tested in a small set of conditions. In\\nthese cases, team judgement should be applied when\\ndetermining/projecting the operational significance. If the shortfall\\nonly appears under certain operational conditions (e.g., certain\\naltitudes, specific weather phenomena, cyber environment), the test team\\nuses available information such as \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" and OPLANS together with\\noperational experience/judgment to determine its impact. If mission\\neffects described by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" were significant and impacted the operation\\n(described by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \") substantially, the measure may be rated \\\"Did Not\\nMeet Criteria---Significant Shortfall.\\\" Conversely, if the system was\\ntested across a wide variety of conditions and the impact on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" was\\nnot substantial, even if it sometimes did not meet the threshold\\ncriteria, the variation may justify a Not Significant determination.\"), mdx(\"h3\", null, \"Deficiency Reports\"), mdx(\"p\", null, \"At times, DRs are associated with specific measures. These DRs may or\\nmay not align with performance outcomes and effects on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"/COIs.\\nWhen demonstrated effects of performance shortfalls differ from expected\\neffects documented in a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deficiency Report\"\n }, \"DR\"), \", the team must apply experience/judgement,\\nbut will likely rate the measure to be consistent with the \", 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\"), \"\\nrating. For more information on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deficiency Report\"\n }, \"DR\"), \" process, see \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tasking Order OR Technical Order\"\n }, \"TO\"), \" 00-35D-54 and the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Deficiency Reporting Tool on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" intranet Library.\"), mdx(\"h3\", null, \"Beyond the Point Estimate\"), mdx(\"p\", null, \"When analyzing a \", 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\"), \" that involves interval or ratio data (e.g.,\\ntime, temperature, distance), it is important to consider more than just\\nthe summarized value, known as a point estimate by statisticians, and\\nshould be identified as the metric in the measures worksheet. Point\\nestimates provide the best guess about some population parameter such as\\nthe overall performance average. However, the dispersion of data around\\nthe point estimate, or variability, also provides useful information to\\nthe test team and the warfighter. While variance or standard deviation\\nare metrics of choice for statisticians to summarize how data are\\ndispersed around an average, a more interpretable metric is the range of\\nthe data, i.e., the difference between the highest and lowest data\\nvalue. When the data are normally distributed (and therefore the average\\nis at the center of the distribution) one can estimate that roughly 99%\\nof the data will be within a range of plus or minus three standard\\ndeviations of the average. However, it is not easy to heuristically\\ntranslate a standard deviation into a range if the average is not near\\nthe center of the distribution. Hence the range is a more general and\\nstraightforward way of describing the degree of dispersion in the data.\\nUsing both the average and the range can facilitate a more thorough\\nassessment of the system. Suppose a system and its users take an average\\nof 10 minutes to accomplish a task and the range is 2 minutes. Then the\\nwarfighter can be told to expect the system to consistently require\\naround 10 minutes for task completion (9 to 11 minutes if the average is\\ncentered in the range.) However, suppose the average is 10 minutes and\\nthe range is 12 minutes. Furthermore, suppose the average is not\\ncentered in the range and the test data show the task takes between 8\\nand 20 minutes. Then the warfighter may need a warning about the\\nvariability in performance; it may be that waiting 10 extra minutes is\\nthe difference between life and death. Your evaluation of the measure\\nshould take the range of the data into account.\"), mdx(\"h3\", null, \"Operational Experience/Judgement\"), mdx(\"p\", null, \"The test team's experience/judgment is the cornerstone to credible \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\nanalysis, evaluation, and reporting. It will be the deciding factor when\\ndetermining operational significance throughout the rating levels. In\\nparticular, test teams leverage their operational experience/judgment\\nwhen they determine whether a shortfall is operationally significant.\\nTest team judgment should be informed by credible, and preferably,\\nverifiable information. Examples of different information types are\\noverall performance of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" during test scenarios, recorded feedback\\nand ratings provided by users during testing, modeling and simulation\\nresults, system \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", knowledge of legacy system performance (if\\napplicable), and DRs.\"), mdx(\"h3\", null, \"Key Performance Parameters\"), mdx(\"p\", null, \"KPPs are not significant considerations when rating MOPs/MOSs. While\\nthey highlight specific system performance, and meeting or not meeting a\\nthreshold criteria is of great interest to the user and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \", they are\\ntreated no differently than any other capability requirement. It is not\\nuncommon that a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" fails to meet a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" criteria, but there is little to\\nno operational impact. Test teams evaluate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \"-based operational effects\\nin the context of various operations and operational conditions, no\\ndifferently than other capability requirements. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" performance is\\ndocumented in \", 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\"), \" ratings, identified as KPPs, and rated based on\\nthe analysis of significance. If a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" threshold appears contrary to\\noperational effects (or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" rating), the test team should recognize and\\ndocument these differences and communicate the rationale.\"), mdx(\"h3\", null, \"Additional Observations\"), mdx(\"p\", null, \"Sometimes teams learn noteworthy information while evaluating a measure\\nthat was not previously considered during test planning (e.g., unplanned\\ndata collection, interviews, user comments or DRs), nor within the scope\\nof the measure. While additional observations may not affect the rating\\nof the measure, they are included in the narrative of the test report.\\nThe test team might identify a shortfall if they measure an aspect of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" not addressed by the criteria. For example, suppose a\\nrequirement states that a system must have an average assembly time of\\n20 minutes. The test team realizes that disassembly time is also\\noperationally relevant and not likely to be the same as the assembly\\ntime, so they create a separate measure without a threshold. They can\\ndetermine whether a shortfall exists by observing distinct steps of the\\ndisassembly process and the level of difficulty operators experience\\nwhile disassembling the system. In addition, when the test team talks to\\noperators during testing, they can include the average disassembly time\\nin context and determine if there are negative impacts to the mission.\\nFigure 8 shows \", 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\"), \" ratings and visual indicators, including the\\n\\\"Inconclusive\\\" rating, which should only be used when analysis does not\\nallow a credible performance determination.\"), mdx(\"p\", null, \"Figure 8. \", 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\"), \" Ratings and Visual Indicators\"), 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\": \"885px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/146a07273349dbc36954330a63b5388e/efc66/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\": \"90.34749034749035%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAASCAYAAABb0P4QAAAACXBIWXMAABcRAAAXEQHKJvM/AAAC5klEQVQ4y4WU20uTYRzHv++cc07bu3aweT6WZyuZh5l5KMpQDBTzwvDwOrWcTAnUiwrqNvIyEJIKg4SitIMShFk3jpjlTTcRdNFt/0Os77P3mW5T6IEPv+fwe77vd8/zewawhcNh5D0dSHIu9iiZs1ehpmuwYlQhIqqkmdSTFtJAsuRaNCeC3tr0UPbch4ylPmQFhhU1dT+JJJNKUkjKSRmxxwrFC2bpDk+sDA65H/aW5twYhGrRHEzIlhtdxExMJEnOWYjIOUpS4kXP6bo1q9NB1+OB/tzZcahpoxVc7CQl8ue2klPkJGkiZ+WcwBYneOf3Mp5tT+LlWnvj1puLrvW1Dizc7Y4mKCp80XMS7gyq3Jgwvy8YDgfII0PoW++P7S89wwv3riDHqlVLh8LBZVJHLpFG0iX7nfKShGPjnuDupAef/Kfxdqa6+vVMjW1zvpIHsLL3ReGoFvNxY73v23Md5/C+foTKn3rvz195RSMvClqQbxgUN9kmS6WD5Ep3XtIuHXsSxSKCfq8XH6j4HajcBawP2M9Gv1neprhFp7xJUY8F8tbdJCOxDvdKR5TN+1Bo+tXmx6bF5Q0UugI2KeSQUWw+dljtHaxDKfh5a2tn49361JOlVRRnBHKYUCPLpEr2a0n6fwVDoRCCwWBEVCBaGobSrIgUN12NsIg1Cml0qtGpxmPQ7PqaiMMmO27CjAYc2qyGbt7k9SIV4+dJm4qJesYzjLWMLSquNcTMNdow5bREX0dMsxhNsCgGmoMpnWNjM8IYhu74L+McKSE+Uk76SFhfNwLJKYwmksJRPhSYUw04UqrAkikTXJyTpJAkJ+DmWlE+Hz8LtbgAcLgV5iGyBofECVomfreKyUYV/oo6ftUAe8IP8JI5bvZf0JlqBW5bwZI/eGbwWfWnpHXJZ1Vsxy169yh0Kk5DfnyH+I4DYzx9XxHwleM85pgTBSNFWiXxyH+YmFKYIOMxiPEI6SGzZCxO7x/CJeOpeeAUJgAAAABJRU5ErkJggg==')\",\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/146a07273349dbc36954330a63b5388e/efc66/image11.png\",\n \"srcSet\": [\"/static/146a07273349dbc36954330a63b5388e/a2ead/image11.png 259w\", \"/static/146a07273349dbc36954330a63b5388e/6b9fd/image11.png 518w\", \"/static/146a07273349dbc36954330a63b5388e/efc66/image11.png 885w\"],\n \"sizes\": \"(max-width: 885px) 100vw, 885px\",\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, \"RATING CRITICAL OPERATIONAL ISSUES\"), mdx(\"p\", null, \"The measures, notably \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", form the basis for evaluating and rating a\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". Test team judgment is key to rating a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" and is based on test team\\nmembers' prior operational experience, military training, and\\nexperiences during test events. However, it is also informed by\\nbattlespace development, test design, measurement, analysis using formal\\nstatistics, measurement and evaluation logic, etc.\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" evaluation determines the impact effects had on operations defined\\nby COIs. After \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are rated individually, the evaluation shifts to\\ncollective effects (or operational impacts) on operations. Primarily,\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" ratings are based on evaluating \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" mapped to each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \", and\\njudgment of the test team. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" rating taxonomy has four tiers and\\neach tier addresses a different operational impact. In addition to\\neffects addressed in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", the test team should consider the impact of\\nnotable findings for each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \".\"), mdx(\"p\", null, \"Each \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" rating must be supported by a defensible narrative and an\\nassociated visual indicator. When there are no negative effects\\nresulting in operational impacts, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is rated \\\"No \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" Shortfalls.\\\"\\nWhen there are operational impacts, the three potential operational\\nratings are Minimal, Substantial, and Severe. Figure 9 depicts the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\nratings logic.\"), mdx(\"p\", null, \"Figure 9. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Rating Logic\"), 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/1eed82d67c46689b62a7e6728fc45a05/c56af/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\": \"53.28185328185329%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAYAAAB/Ca1DAAAACXBIWXMAABcRAAAXEQHKJvM/AAACd0lEQVQoz3WSXUhTcRjGn3M8Z21z5sdIUwuVFoprYOWKmBOEUBJietEHXahEehl0EXlnZXTRzSAICSqqVYMS1BDTlLBQ5zaaZ9O1zZhO09bWByQMWthO75nbhZl/+HE47zn/533eD2DzySByCAOhI1TpD8/ychBvMjFRbSW+lJfje30981mrhSiKSf49MqKAqCSOE0eJQ0QNUUEUdu7X8NFMBT7pDrQu63TGkIxHqKKC3U5QcpYHMLn0zAJKyOVuyZ1SSsTzvJqeTKTnHlzZexv9QPm3Oz3wl+xjtggaDEF2s/ZB4gUHzDMbhgHL40fSpZLf8V+jDp9/cDEcHhMTiaczqz/ZgYF+ds47l2EfnmeKn7SxqK39Co7ro2tiivPEiAJ4JQc6ISUPRNYlQeX6n0TD9LtZk9+71ETvtSOjAiYnJyC4BThefwQJAtXVwUaOs1KZzVT2beqlaSfNpRhQ5wMtKqi6eLW+jeINPGWSqskm5FKZTue8xuV6f8Ef8Hf4bCul6run6qDXr1yVyWw5G72r2gPcUqQGoQGuKcGWlqFAI0eWmfp5UhI7plBkSr1gBSFY5/F4+rwfvIMR34/q/IdnL8FojFLJz1ObcoV4SS5E6uESORpmTlCk/b492cupqTVVb+9qrtUazA0E1pRDQzOw2abg9ghwvVlAkaWV9qImwnJcL/1eRVwkeogjNBCqHA+k3qUnWRYKLUxPTMy+dTrnHNFouJ9ibHf3dZYccu7xRabI0pIecNd/uEHchN0+nlpe345YTCwcGzNddjg6TlNsVyx2LpkskUhgm7NVWLoQj4dhNgPLy+2UAGcEAYeDwVaaMLYs9l/uPBJ9SPPz9QAAAABJRU5ErkJggg==')\",\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/1eed82d67c46689b62a7e6728fc45a05/e3189/image12.png\",\n \"srcSet\": [\"/static/1eed82d67c46689b62a7e6728fc45a05/a2ead/image12.png 259w\", \"/static/1eed82d67c46689b62a7e6728fc45a05/6b9fd/image12.png 518w\", \"/static/1eed82d67c46689b62a7e6728fc45a05/e3189/image12.png 1035w\", \"/static/1eed82d67c46689b62a7e6728fc45a05/c56af/image12.png 1231w\"],\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, \"Use the following as a general guideline for rating COIs:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"No \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" Shortfalls, \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"No\"), \" impact. There were no negative \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \"\\neffects resulting in operational impact\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" Shortfalls, \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Minimal\"), \" impact. Use this rating if the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \"\\neffects indicate operational personnel will be able to accomplish\\nthe operation defined by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" with no significant impact.\\nGenerally, this means that all operational tasks can be accomplished\\nwithout any (or minimal) limitations and workarounds.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" Shortfalls, \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Substantial\"), \" impact. Use this rating if the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" effects indicate operational personnel will be able to\\naccomplish the operation with significant operational impact. This\\nmay mean the majority or all operational tasks can be accomplished,\\nbut with significant limitations or operational workarounds.\\nExamples of substantial impact would be: operations accomplished\\nwith a manageable reduction in accuracy; an acceptable increase in\\ntime, assets, and manpower; or minor changes to tactics/ training.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" Shortfalls, \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Severe\"), \" impact. Use this rating if \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" effects\\nindicate operational personnel will not be able to accomplish the\\noperation in the projected operational environment. This may mean\\nthe majority or all operational tasks cannot be accomplished, even\\nwith significant limitations or operational workarounds. Examples of\\nsevere impact would be: Unacceptable lethality or reliability;\\nunacceptable increase in time, assets, and manpower; or unacceptable\\ncybersecurity.\"))), mdx(\"p\", null, \"Figure 10 illustrates \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" ratings and visual indicators, including the\\n\\\"Inconclusive\\\" rating, which should only be used when analysis does not\\nallow a credible determination of operational impact at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" level.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Notable findings are addressed later in this section.\"), mdx(\"p\", null, \"Figure 10. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Ratings and Visual Indicators\"), 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/494a1319872ca8029c3f59b6fb1b72d2/62da8/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\": \"70.65637065637065%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAYAAAAvxDzwAAAACXBIWXMAABcRAAAXEQHKJvM/AAACNElEQVQ4y42UP2xSURTGv0eB8sqD93jlz3tAhYDVYmtEtCa0g4txVSeTasOj1BRKgoMmxsnRwRhX4+LoqhJjdNDBtIlaNVFrdDFp1MFEozUdTeh34TahKUQP+eVwL/d9fOecC5jOt1DI/biwP7tRBLymrlQLQcwdIHvJYbKPjJG8xCTYYkeM32pg7Fp9Ys/NczHA8Ri+uSAPqsQgfuKTWetaK3o/0V33G0jeWVhM3FuY8qBk6IMV4S5DJkhWOixKd2I/RzGlr8vvz9z40PRk11/ABK6rUW8pzEPC5TDRpStTOg7JzwLBLtFt8eabG0/feaurP8Ee3tUt/2yOh5JklKRkLydlP4XrtOzpQE/BjfQhfEkVTvxJ5saBqwFLcURZMSkWJ8KxLR0npGto/Ur+FTawFg4d/W14MsDtIQulER6KyIdj0ulB6TojvwB9e/j66xoevnxeevJ+5QiXQ3aglpKOklIQ/2K74Kt1NJtvi48ef0oBphpTa5Gu8jiECjoDKDOXmR1O7zJ8mETPWF0Glh6g/nEZ00BLjfvP7tYxnyQWSRNbw0m0+Pqv+HslgqVyqLKy6J8Cbmi2dyYbwBmbsNzZtMinKOYGFPmI0gcRXpyfgYtvhgGXrWkiwyBmZw+hTh6w2N4EGQV8ce5ZPeAvDSNQUVejHqcYdpfzwGel2/3xdpkFcskH1Hit5jm4KjcaOnCsd8nyvolrwT8FJxrCRTacd7xtfCs4r7a4Q067Ooi1vkNvE04PkbF54AlbAAAAAElFTkSuQmCC')\",\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/494a1319872ca8029c3f59b6fb1b72d2/e3189/image13.png\",\n \"srcSet\": [\"/static/494a1319872ca8029c3f59b6fb1b72d2/a2ead/image13.png 259w\", \"/static/494a1319872ca8029c3f59b6fb1b72d2/6b9fd/image13.png 518w\", \"/static/494a1319872ca8029c3f59b6fb1b72d2/e3189/image13.png 1035w\", \"/static/494a1319872ca8029c3f59b6fb1b72d2/62da8/image13.png 1262w\"],\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(\"h2\", null, \"Basis for \", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Evaluations\"), mdx(\"p\", null, \"The following paragraphs capture elements test teams must consider when\\ndetermining operational impact.\"), mdx(\"h3\", null, \"Preponderance of Measures Meeting Criteria\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are indicators of whether and how well a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" can be achieved. If\\nnumerous measures indicate success, the operation defined by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is\\nlikely to be achieved. However, avoid using a simple numeric that 4 out\\nof 5 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" have no significant effect on the operation to make a\\ndetermination. Take advantage of the operational experience and judgment\\nof the test team.\"), mdx(\"h3\", null, \"Prominent Measures\"), mdx(\"p\", null, \"There may be one or more measures that are have a greater influence and\\nimpact on a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". While these measures are usually identified prior to\\ntesting, particularly as a desired effect, test results sometimes reveal\\nthe unexpected importance of a particular measure. For example, even if\\na preponderance of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" reflect positive effects, a single prominent\\nmeasure (effect) could indicate a substantial/severe operational impact.\"), mdx(\"h3\", null, \"Operational Conditions\"), mdx(\"p\", null, \"It is not uncommon for a system to perform well under some conditions,\\nbut poorly under others. Test results combined with conditions provide\\nan indication of system robustness. A limitation or poor performance\\nunder certain conditions may justify a severe operational impact, but if\\nthe likelihood of employing/sustaining the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" under those certain\\nconditions is rare, it may warrant a rating of substantial, rather than\\nsevere, impact.\"), mdx(\"h4\", null, \"Cyber Effects\"), mdx(\"p\", null, \"Cyber threats are not more important than any other condition or threat,\\nbut are differentiated and highlighted for two reasons. First, and most\\nimportantly, cyber threats are always present and active during ongoing\\noperations, including during peacetime. Second, cyber receives a\\ndisproportionate level of external attention, which warrants special\\nemphasis and highlighting in test reports. Using cyber threat\\nconditions, test teams estimate cybersecurity protection, detection, and\\nrestoration risks at the \", 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\"), \" level, and confidentiality, integrity,\\nand availability effects at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" level. Then, they determine\\noperational impacts of cyber effects on the various operations defined\\nby COIs.\"), mdx(\"h3\", null, \"Interaction of Results\"), mdx(\"p\", null, \"Occasionally, prominent measures may have interdependencies that make it\\ndifficult to draw conclusions regarding a specific \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" (i.e., \\\"You can\\nplan a mission quickly, but it isn't complete,\\\" or \\\"You can create a\\ncomplete mission plan, but it takes an unacceptable amount of time.\\\").\\nSuch interactions must be understood and discussed to determine their\\nsignificance and operational impact.\"), mdx(\"h3\", null, \"Holistic Considerations\"), mdx(\"p\", null, \"Test teams must consider all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" under a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". In conjunction with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"\\nthat express desired effects, there may be \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" or notable findings that\\nexpress undesirable effects. Collectively, the operational impact of\\nthese effects will determine the consequent rating of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". In\\naddition, some MOPs/MOSs may have additional observations and DRs to\\nconsider when determining operational impact. For example, consider an\\noverly complex and timely maintenance action to remove and replace a\\ncomponent. This alone could result in negative operational effects, but\\nif the reliability of the component was well beyond the predicted\\nreliability, and the component would rarely need to be changed, this\\ncould mitigate the negative operational effects. The team would have to\\nconsider other factors in the aggregation, such as confidence in the\\nreliability predictions, criticality of the component, and operational\\ntempo.\"), mdx(\"h3\", null, \"\", mdx(\"abbr\", {\n parentName: \"h3\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Notable Findings\"), mdx(\"p\", null, \"Under rare circumstances, the team may identify a significant shortfall\\n(additional observation) and/or significant effect (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" notable finding)\\nthat was not addressed in the original \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E construct. If the shortfall\\nhas substantial/severe impact on the operational outcome, it is\\nidentified as a Notable Finding and considered when determining the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\nrating.\"), mdx(\"h1\", null, \"RATING OPERATIONAL EFFECTIVENESS AND SUITABILITY\"), mdx(\"p\", null, \"At the conclusion of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E (initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, qualification \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, follow-on\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E and multiservice \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E), an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" report documents the operational\\neffectiveness and operational suitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \") determination for the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". The definitions of effectiveness and suitability are fairly\\nspecific, but generally foreign to those without an acquisition and/or\\ntest background. Although the terms come across as acquisition jargon,\\nthe definitions are warfighter-centric and succinctly address the major\\noperational warfighting considerations. Figure 11 contains \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \"\\ndefinitions. Effectiveness is synonymous with mission accomplishment and\\nis defined by the mission statement and documented early in the planning\\nprocess. It subsumes all operations defined by COIs and factors in\\nemployment concepts and operational conditions. Suitability is defined\\nby support concepts, operational conditions, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" context.\"), mdx(\"p\", null, \"Figure 11. Effectiveness and Suitability Definitions\"), 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/8888bba70268037c536a218fe81ca688/29c1d/image14.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\": \"66.02316602316603%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAABcRAAAXEQHKJvM/AAACzUlEQVQ4y2WSy24SYRTHP9uVabSxsaVq02UTn0CjXUHosm/R53Djyo0v4MoXaLowMR2jaURgLjBcpgUKw3AZ6AwM0IECc6Of/29sm6okv5zrd8I5/yGmaX52nLkdBH7X83zDdT1jsVgY5+dVQxRFQ1EUQ5Ik+BmjUCgauZxsTKdj9M3BzPB95wK+NZ/Py8PhcJM0GtoXTWvTatUGV7RUGlNVvQqpVMZU067u8sxWqyY9O9NQayLXpOVyC7ZBDcMc2/blC6Lr3cNSaUAlyXJlue/ncgNflgd+Pm/42WwlhOcV5KqhFYQzX5LKsEXEpyzvpVIFDDR6lF4/J1jtWNMatNvt0na7TTudDtX1Dq3X67TVaiDXxL+t0kZDRazB1lFvoV4L87repM2mhk00dzKZbJFez/zguk52NpslcIckA37ScZyk7wf/gTujxwnrjuOid/4Llkf8tdPRnxLLst57nvfTdd1jz3M5DOcgEGdZfU4QeE6Ws5yiFDmeT3OpVJJT1Rq3WARhHwNvjmF/QNhDCLxOsPs3tiJbt9s1wZya5oxeXExorWZitR6E6ME3sKIJBjjLFDdjPax3inhGLy8d7/ra3iaDQf+o3e5RQVA8nucDns8CKUinhUAUs4EsF4NC4TRIpYTQCkI2SCTSQT5/GiSTYnBykoCQCnVd3xqNrC228lGpVKKiKHiZTAaDUhgiB7lcDg+SGMBjsBiSSCRghZB8PhfW0APFeQpBLNxxi/T7fQ4OFGxBrSZTK/R1Xb+LVVUNc7c9LGZ59iUwbNum0MEZjYbb7IYfoawCBCBhuMTsLSz+k7vhXnxTE/FVyOA7ZkXI/v7+0tra2jIh5C/Y7168RNZjj8nG3jPYjZCN+CZZefkQtQcrj54sRyKRpdXVVUIODg5INBolsVjsjts4Go2ReDxO3r55Td59qhD2+B9Qe4WePbK7u0t2dnbIb99DG0q0Z3TgAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image14\",\n \"title\": \"image14\",\n \"src\": \"/static/8888bba70268037c536a218fe81ca688/e3189/image14.png\",\n \"srcSet\": [\"/static/8888bba70268037c536a218fe81ca688/a2ead/image14.png 259w\", \"/static/8888bba70268037c536a218fe81ca688/6b9fd/image14.png 518w\", \"/static/8888bba70268037c536a218fe81ca688/e3189/image14.png 1035w\", \"/static/8888bba70268037c536a218fe81ca688/29c1d/image14.png 1375w\"],\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(\"h2\", null, \"Rating Effectiveness and Suitability\"), mdx(\"p\", null, \"By now, it should be clear that determining a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" begins at the\\nmeasures level and carries through to COIs. After the test team rates\\nCOIs individually, they determine the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" rating. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" rating is\\nbased on the collective operational (or aggregate) impact of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" ratings\\non mission accomplishment, and whether the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can be fielded and\\nsustained. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" rating taxonomy has four tiers and each tier\\naddresses a different operational impact. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" ratings (or\\ndetermination) should be supported by a defensible narrative and\\nassigned an associated visual indicator. Figure 12 depicts the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \"\\nrating logic. Use the following guidelines to rate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \":\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Fully Effective\")), \" . Applied if all aspects of the\\nmission can be accomplished in the intended operational environment\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Effective\")), \" . Applied if the all aspects of the mission\\ncan be accomplished, but with increased operational costs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Partially Effective\")), \" . Applied if only some aspects of\\nthe mission can be accomplished AND/OR the mission can only be\\naccomplished under some operational conditions\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Not Effective\")), \" . Applied is the mission cannot be\\nsatisfactorily accomplished\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Fully Suitable\")), \" . System can be fielded/sustained in\\nthe intended operational environment\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Suitable\")), \" . System can be fielded/sustained, but with\\nincreased operational costs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Partially Suitable\")), \" . Only some aspects of system\\nfielding/sustainment can be accomplished AND/OR fielding/sustainment\\ncan only be accomplished under some operational conditions\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Not Suitable\")), \" . Fielding/sustainment cannot be\\nsatisfactorily accomplished\"))), mdx(\"p\", null, \"Figure 12. Effectiveness and Suitability Rating Logic\"), 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/85d2923d3fca34d2087f79a66d925e25/2f6f6/image15.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\": \"69.11196911196912%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAYAAAAvxDzwAAAACXBIWXMAABcRAAAXEQHKJvM/AAADiklEQVQ4y0VTXWyTVRh+zne+33792q5d17/1Z+3649q1NRWYK9OMhRHkhmBc5kCJF4aIMTHETANcLFx4JcFookNjxJioMQiaLECCQpBxocXFbW03ooMpmeASHUo03n2+39dN34vznpz3fZ/zvM95DyqVJQA/wDT/xokTrzNYJglttHZheyJSOvPcUbzcp+OJFARDkjlHhWIPTE87xxsNHl6i8vNfMrvOfOckEI8v0rZJgCbq9SZWV+9CkDWJDttg8ERu4qUMW3uQoVgFRFWk0hDFYhMT0SqVyPXZEtUetvB0m0wgsMCBWYEA5bm5hpe8U5Q6wHjQAfgzQIX8QQXG+wwsDUEAFOVZBdjqA96VLSJkip8LA15BCKO//+Yuw/jxyZWV+oGrV6+ZzebCV0B7u8f9gc6YXoSAAbq8Bxg3gHIEeNtJBIOiiAHGtERK+pAuLPmvp3PHat3JMkZH/6TbTKVW+zY0Pz8/MDPzfdFSMZ46R4yGNWAPAY1RzqvErdvKpXDeC4SJfTISku6Tfin511K/bj62TcC9ezZlwRaV6J8+fd6WgiGhOrDdJeOZgAODhkDKMqTRAuzEhvn4FK1JLBU2w3y4YmNRFuvjXNyiaepmwwhQ9qRHRLFDx848gaYcGM5wBNwOPAIVY1STXoeT4BYuko9iNlvE3UIO4NxFmohZRVE2BYPBrnK5TC0ec9EjuzRUO3Xs6tWw1aLk8GCc3FMbDdnmFz6m1cBMNM5uxqKkRv4NeDym3e6tW8u4fHl6PZVLKoZ0GQdDKrY5WyjWxJzB/2YiJn1CPoKlfAm/9+aBvr4FymqGTfOfnkaj+cLKyi+7KcMZj93nYJuIaVc7CBjYRw/STgM/RWO2V1sfqbaoOCVSN556MtOznEq6MDj485DXu7x7be2np69c+fqPubn5T4Gc4XS+pgtiqIMp2AIWIdDjNB47CPAkgSfCsoxhzpV8jL9F56+o9XzxxdViIY3JSRMjI79t9MBag/qotc8CGU/THoLjYkuFvRBFL0KhIRXY7wauiab5EQqKLepD1g9CrWbi0KG/2KVLk8hme9DZGSb5DQvAg6rfl3nvwAje7JXYZ/ttTEVhUeufnzrl3XfjhjNw9nMfCmVDzHl9ml9TZRjGNxSfxZ07DRw5crTF0yWL9ix0t6UqXzz/OA5XFfbdmB2iVrutyb5wQRldXFTDt28r9KDu/57pX8Ql6YbsvEloAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image15\",\n \"title\": \"image15\",\n \"src\": \"/static/85d2923d3fca34d2087f79a66d925e25/e3189/image15.png\",\n \"srcSet\": [\"/static/85d2923d3fca34d2087f79a66d925e25/a2ead/image15.png 259w\", \"/static/85d2923d3fca34d2087f79a66d925e25/6b9fd/image15.png 518w\", \"/static/85d2923d3fca34d2087f79a66d925e25/e3189/image15.png 1035w\", \"/static/85d2923d3fca34d2087f79a66d925e25/2f6f6/image15.png 1377w\"],\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, \"Mission Capability Determination (Optional)\"), mdx(\"p\", null, \"An overall mission capability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Capable\"\n }, \"MC\"), \") rating may accompany the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" rating\\nin the final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Capable\"\n }, \"MC\"), \" determination is an optional rating for\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test teams that is intended to provide a determination of the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s overall capability to execute or support tasked missions. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Capable\"\n }, \"MC\"), \"\\nrating must consider operational costs (manpower, time, ease of use,\\nsupplies, workarounds and risks), limitations associated with aspects or\\nportions of the mission, and mission accomplishment across a variety of\\noperational conditions. Like the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" determination, it uses a four tier\\nrating scale (see Figure 13). The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Capable\"\n }, \"MC\"), \" determination merges \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \"\\nconclusions into a single rating. If the team applies the optional \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Capable\"\n }, \"MC\"), \"\\nrating, it is in addition to, not in lieu of, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" rating. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Mission Capable\"\n }, \"MC\"), \"\\ndetermination uses the same analysis and evaluation information used to\\nrate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" and the following definitions apply:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Fully Mission Capable\")), \" . Applied if all aspects of the\\nmission can be accomplished in the intended operational environment\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Mission Capable\")), \" . Applied if the all aspects of the\\nmission can be accomplished, but with increased operational costs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Partially Mission Capable\")), \" . Applied if only some\\naspects of the mission can be accomplished AND/OR the mission can\\nonly be accomplished under some operational conditions\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Rating: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Not Mission Capable\")), \" . Applied is the mission cannot be\\nsatisfactorily accomplished\"))), mdx(\"p\", null, \"Figure 13. Mission Capability Rating Logic\"), 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/f58c73453be1fe2eb373edf77fa2e353/5c98f/image16.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\": \"55.21235521235521%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAYAAAB/Ca1DAAAACXBIWXMAABcRAAAXEQHKJvM/AAACcUlEQVQoz6WSTUhUURTH//c+J0cckax0zPFrHLRGaCq/aIoCMU0XfVgY5MKwyI2YGKItRBgkDSYJijaZ0pfakEpOOBP6bBymdLLUTB2bMpWsjbtWbuR13uu1GGnXgd+7l/Pe/d9z/u8AocGIJCKNSCEyiGTCgP8InSqWTxSogtGhnzRvISQ6iJmtVUbRsg8QzLSPASLUdBjRQGQRFwiHkpVrCNKzW95arRK32d4yUXQL3d0iq6qSs6QFiXioAY6o9ziIQeInkUe0obBwDpIkYWDwheDs6OVSnpUjO1tCS4sfXq+IsbGAWsUvWVAAgto/wlBzt4hVDlRGAvc0XV2SIvjSNQTXg15IlgNAevpaTV2d77DH8+qazXaHetmh0+mO7mIsLJMxtgew7ARKqO2ceGA5HEjUM8bzBSE6FbixLTOj2PhsoL/Bdft+0VpqWh2MxtVCu33BtLQUKPV638fLZkVE5MYyFmnhPIo8NMcBHiq7iNpfotW4G9BaBEFPgtXhl8vvaqfm545NdT5NX9bHH4fJ9AOtrbNYWJhBILD298fQoRgTdYOkvbKffdBoGlVvNZGcn9ju8UDx+fzpm/BNvsN4x2N8NyTSfKR84+3ti2xlJch9Pj9qStsUX96I3kvB2c+1B5Gr3DA6Osk2N9exsbGudbsn7NPTi4f8/nm8Hv3AP30Jso+dT9jX2FgeMkCyUFLTKWZsPIOzj5pyznXaCuKay6BtOMn8/uvKe+V/OwrK+vvLDQ5HKZzOCspU/nui5QPm51d4Zl8VUnsqitN6Lpbtd1Yja+gqn5gAEhIk1Nc3Y3xcqB0eRvLICIcoqqOoxm/oY82cyG8D6wAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image16\",\n \"title\": \"image16\",\n \"src\": \"/static/f58c73453be1fe2eb373edf77fa2e353/e3189/image16.png\",\n \"srcSet\": [\"/static/f58c73453be1fe2eb373edf77fa2e353/a2ead/image16.png 259w\", \"/static/f58c73453be1fe2eb373edf77fa2e353/6b9fd/image16.png 518w\", \"/static/f58c73453be1fe2eb373edf77fa2e353/e3189/image16.png 1035w\", \"/static/f58c73453be1fe2eb373edf77fa2e353/5c98f/image16.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(\"h1\", null, \"TEST REPORTING\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s test report communicates results of our operational\\nassessment/evaluation and the impact of those results to the warfighter\\n(the \\\"so what\\\"). The test team reports test findings/results in various\\nformats and on different timelines depending on the test activity, test\\npurpose, and external needs. Depending on the nature of the program,\\nreports inform specified milestones, releases of capability to the\\nfield, progress or status to the program office, or feedback to\\ndevelopers and testers. Test reporting is the primary enabler for\\ncontinuous and cumulative feedback. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E reporting strategy should\\nbe tailored to the acquisition strategy and adapted during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, if\\nwarranted. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E reporting has evolved and taken on various formats. With\\nan increased emphasis on early and continuous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" feedback, reports are\\nsmaller, document less analysis, are generated more quickly, approved at\\nlower levels, and may not inform defined decisions. There are numerous\\ntypes of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E reports. Some have established content expectations with\\nexisting templates, while others are heavily tailored to specific\\nsituations. Some reports are written at the end of test, some\\nimmediately after test as quick interim summaries, and some reports are\\nprovided during test execution. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E reports can be generated to report\\nanything from problems or progress, up to a final determination of\\neffectiveness and suitability. Some reports also include briefings to\\ncommunicate results to various stakeholders.\"), mdx(\"blockquote\", null, mdx(\"p\", {\n parentName: \"blockquote\"\n }, \"Provide feedback in writing. In the past, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test teams provided\\ncontinuous relevant operational feedback during various\\nfunctions/forums, but delivered limited written feedback/information.\\nValuable information is easily forgotten, lost, or dismissed if not\\nprovided in writing.\")), mdx(\"p\", null, \"Although reporting choices are dependent on numerous factors, all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nreports should adhere to some fundamental \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E tenets. They should be\\naccurate, balanced, and timely, and they should be operationally\\nsufficient, technical adequate, and credible.\"), 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\\nthe conclusions are defendable.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Balanced\"), \": Balanced reports highlight system capabilities and\\nlimitations (strengths and weaknesses). This can be especially\\nchallenging when focusing on shortfalls.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Timely\"), \": Timely reporting is broken into two categories.\\nFirst, reports delivered to decision makers with time to review and\\nunderstand the results prior to decision dates. Second, reporting\\noperationally relevant information to stakeholders in time to affect\\ncapability development.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Sufficiency\"), \": The breadth of the operations\\naddressed while employing new or modified capabilities within the\\ncontext of representative employment and support concepts. The\\nevaluation is considered operationally sufficient if it provides the\\ndecision maker and the warfighter with results from test events\\nexecuted across sufficient operational conditions to identify the\\ncapabilities and limitations associated with employment as well as\\nto determine the effectiveness and suitability.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Technical Adequacy\"), \": Addresses the relevance of the technical\\ninformation produced by the test in relation to the purpose of the\\ntest (i.e., the operationally relevant questions being addressed by\\nthe test activity). A test is technically adequate if the test data\\nevaluation provides the acquisition decision maker with the\\ninformation to inform the appropriate decision.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Technical Credibility\"), \": Addresses the depth and accuracy of\\nthe technical information produced by the test. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" products must\\nbe credible and the Commander must have confidence in the conclusion\\nwhen reporting \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. The report addresses risk with an acceptable\\ndegree of certainty in test results. Acceptable certainty starts\\nwith sound, defendable processes from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" through \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E analysis and\\nreporting.\"))), mdx(\"p\", null, \"Test reporting is broken into two broad categories: continuous reporting\\nand final reporting.\"), mdx(\"h2\", null, \"Continuous Reporting\"), mdx(\"p\", null, \"Continuous and cumulative feedback ensures \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" provides timely\\nfeedback throughout the life of a program, to include early acquisition\\nstages. Test directors should continuously deliver timely, relevant\\nwritten information/findings to stakeholders (e.g., developers and\\nprogram offices) as soon as available. Test teams provide continuous\\nfeedback in small, tailorable reports (e.g., status reports, significant\\nevent reports, periodic reports, observation reports, and quick look\\nbriefs). TDs may also provide the more structured progress reports\\n(e.g., operational assessments) at specified milestones, depending on\\nthe acquisition strategy. Reporting deliverables may be cumulative,\\ncontaining all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" feedback captured prior to a particular milestone or\\ndecision point. Continuous feedback shifts the impression of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"\\n\\\"final exam\\\" to highlighting continuous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \", collaborative discovery, and\\ninformation exchange. Thus, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" better integrates and is a partner in\\nsystem development and delivering combat capability through timely\\nindependent feedback.\"), mdx(\"p\", null, \"Test directors should be acutely aware of their responsibility to keep\\ntheir leadership (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/CCs) apprised of test progress, status, and any\\npotential issues. Detachment commanders should ensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" senior\\nleadership is aware of any potential controversy that could surface\\nduring reporting. As staff \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \", A-3 provides feedback and recommended\\ncourses of action to Detachments and the Command Section during test\\nexecution and reporting. There are several recognized formats for\\nproviding continuous written feedback. Although continuous reporting\\nfundamentals are common across the various \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" programs, test teams\\nexercise significant latitude in reporting. Report titles vary from\\nDetachment to Detachment and contain subtle differences in internal\\nformat. Teams are not limited to currently recognized and helpful\\nreporting templates.\"), mdx(\"h3\", null, \"Operational Assessment Reports\"), mdx(\"p\", null, \"EOAs/OAs analyze and assess progress toward \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" and delivering combat\\ncapability. EOAs/OAs are most commonly used for Major Capability\\nAcquisitions (see DoDI 5000.02), but may be suited for some Middle Tier\\nAcquisitions (see DoDI 5000.80). Assessment areas are structured around\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63-119 templates that address acquisition, development, and\\ntesting. The \\\"\", 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 Guide\\\" and corresponding functional guides\\n(e.g., Test Execution Guide, Cybersecurity Guide) contain guidance on\\nEOAs/OAs. These assessment reports contain results for two distinct\\nareas. Area 1 assesses progress toward operational capabilities (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \").\\nArea 2 assesses progress towards delivery of combat capability in three\\nareas: test planning and documentation, system design and performance,\\nand test assets and support. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Operational Assessment\"\n }, \"EOA\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \" tools and report templates are\\navailable in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library. Approval authority is carried\\nout in accordance with (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \") the signature delegation memorandum on the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library.\"), mdx(\"h3\", null, \"Status Reports\"), mdx(\"p\", null, \"Status reports provide updates and important test findings during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E.\\nStatus reports are in the form of a letter, normally very short (no more\\nthan several pages) and are not intended to be a mini final report.\\nStatus reports may be periodic (monthly, quarterly, or as required),\\nassociated with specific (planned) test events, or in response to an\\nexternal organization's request for test status. Optimally, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E\\nplan documented the intent to produce a status report, and how often.\\nThe status report approval level is provided in the current \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nsignature delegation memorandum on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library. A status\\nreport template is provided as a starting point and is posted in the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library. Approval authority is carried out \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" the\\nsignature delegation memorandum on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library.\"), mdx(\"h3\", null, \"Periodic Reporting\"), mdx(\"p\", null, \"Periodic reporting allows frequent reporting on a pre-planned,\\ncontinuous interval. These reports are generally small and quick to\\nproduce given the content is limited. They are generally written in a\\nmemo format and the content and level of detail is tailored to the\\nprogram needs. Briefings are by exception. Currently, there is no\\nperiodic report template. Contact \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-3 for latest guidance and\\nexamples of periodic reports. Approval authority is carried out \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" the\\nsignature delegation memorandum on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library.\"), mdx(\"h3\", null, \"Observation Reports\"), mdx(\"p\", null, \"Observation reports provide \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E observations of key acquisition\\nactivities and test events, which do not have to be integrated.\\nObservation reports are usually associated with an observation plan, but\\nnot always. The report summarizes the scope of the observation, to\\ninclude the acquisition activities and developmental testing observed.\\nIt describes key activities observed (e.g., development laboratory\\ntesting, modeling and simulation events) and applied data collection\\nmethods (e.g., direct observation, questionnaires, interviews, and\\nresearch). It also provides notable observations (significant positive\\nand negative observations) of interest to decision makers and\\ndevelopers, and makes recommendations to address those observations.\\nObservation report briefings are provided by exception, if\\nrequested/directed. Observation reports communicate the status\\n(acquisition or performance), operational relevance, and results of\\nsignificant activities/events. See the observation report template on\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library. Approval authority is carried out \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" the\\nsignature delegation memorandum on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library.\"), mdx(\"h3\", null, \"Significant Event Reports\"), mdx(\"p\", null, \"Significant event reports briefly describe results of significant test\\nevents, as determined by 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\": \"Commander OR Critical Component\"\n }, \"CC\"), \", during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" activities. They\\nare usually not provided in pre-planned intervals. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" submits\\nthese reports via email to 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\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A-3 receives these\\nreports and submits them, as appropriate, to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \", \", 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\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Element Monitor\"\n }, \"PEM\"), \",\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Lead Developmental Test Organization\"\n }, \"LDTO\"), \", PTOs, operational \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \", and others, within 24 hours of any\\nsignificant test event, as described in the test plan.\"), mdx(\"h3\", null, \"Operational Test Situation Reports\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" SITREPs are used to keep leadership informed of test execution\\nprogress, test team status, and upcoming events. Typically, they are not\\nprovided for continuous reporting, but test teams should be aware of\\nthis type of report. Although uncommon, some teams have used a modified\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Situational Report\"\n }, \"SITREP\"), \" format as a method of providing continuous feedback for\\nexceptionally fast-paced development efforts. Usually, SITREPs are\\nsigned out by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", but it is important to elevate approval authority\\nwhen SITREPs provide cumulative results for later \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" buy-down or draw\\nconclusions that inform a fielding decision. See the \", 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 Guide,\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Execution Guide, and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Situational Report\"\n }, \"SITREP\"), \" templates (to include\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \") for more information.\"), mdx(\"h2\", null, \"Final Reporting\"), mdx(\"p\", null, \"The final report is the culmination of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E process and is often\\nconsidered the most important product \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" produces. The final report\\nprovides a determination of effectiveness and suitability for formal\\nacquisitions (and operational utility determinations for technology\\ndemonstrations\", \"-\", \"-see \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Assessment\"\n }, \"OUA\"), \" tool in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library). Final\\nreports include a briefing, which are general officer-level summaries of\\nthe test report. A final \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report is a cumulative document that\\ncontains operationally relevant feedback (periodic reporting) from all\\nprevious \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". It includes a determination of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"'s operational\\neffectiveness and suitability while it is operated and maintained in a\\nrealistic operational environment (including exposure to representative\\nthreats) by typical operators and maintainers. Evaluations require\\noperational experience to apply judgment and determine system\\nperformance and operational impact in the context of intended\\noperations. Various report templates are available in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nIntranet Library to aid teams when writing final reports (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \",\\nM/I/Q/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Assessment\"\n }, \"OUA\"), \"). Report templates are a guide to ensure important\\ncontent is included. The instructional text describes expectations for\\ncontent and format. Approval authority is carried out \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"In Accordance With\"\n }, \"IAW\"), \" the signature\\ndelegation memorandum on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library.\"), mdx(\"h3\", null, \"Effectiveness and Suitability Final Reporting\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" is determined and documented in one of the following final reports.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Operational utility evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \") report\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Initial operational test and evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E) report\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Qualification operational test and evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Qualification Operational Test and Evaluation\"\n }, \"QOT&E\"), \") report\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Follow-on operational test and evaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \") report\")), 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\"), \") report\"))), mdx(\"h4\", null, \"\", mdx(\"abbr\", {\n parentName: \"h4\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \" Final Reporting\"), mdx(\"p\", null, \"Although OUEs occur continuously during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E timeframe, they are\\nintended to provide an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" determination. They are conducted to\\ndemonstrate or validate new operational concepts or capabilities,\\nupgraded components, or expanded mission/capabilities of existing or\\nmodified systems. OUEs may support operational decisions (i.e., fielding\\na system with less than full capability, including but not limited to\\nintegrated testing of releases and increments of capabilities) or\\nacquisition-related decisions, whenever appropriate throughout the\\nsystem's lifecycle. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \" M/I/Q/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \" report and classified report\\nannex templates posted in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library contain more\\ninformation. Also see the \\\"\", 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 Guide,\\\" 11th ed. for staffing\\nguidelines.\"), mdx(\"h4\", null, \"\", mdx(\"abbr\", {\n parentName: \"h4\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E Final Reporting\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E is the final dedicated phase of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E, which precedes a full-rate\\nproduction (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full-Rate Production\"\n }, \"FRP\"), \") decision. It is the final evaluation that entails\\ndedicated operational testing of production representative test articles\\nand uses typical operational scenarios that are as realistic as\\npossible. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E is conducted by an operational test agency (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \")\\nindependent of the contractor, program management office, or developing\\nagency. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" commonly conducts \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&Es to inform the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full-Rate Production\"\n }, \"FRP\"), \"/initial\\noperational capability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Capability\"\n }, \"IOC\"), \")/full operational capability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Operational Capability\"\n }, \"FOC\"), \") and\\nfielding decisions. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E will likely include developmental (contractor\\nor government) test and integrated test results deemed operationally\\nrelevant. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \" M/I/Q/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \" report and classified report annex\\ntemplates posted on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library contain more\\ninformation. Also see the \\\"\", 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 Guide,\\\" 11th ed. for staffing\\nguidelines.\"), mdx(\"h4\", null, \"\", mdx(\"abbr\", {\n parentName: \"h4\",\n \"title\": \"Qualification Operational Test and Evaluation\"\n }, \"QOT&E\"), \" Final Reporting\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Qualification Operational Test and Evaluation\"\n }, \"QOT&E\"), \" is conducted by an operational test and evaluation agency (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \")\\nindependent of the contractor, program management office, or developing\\nagency. When programs lack \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Research, Development, Test and Evaluation\"\n }, \"RDT&E\"), \" funding (e.g., commercial\\noff-the-shelf, nondevelopmental items, and government furnished\\nequipment), \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" performs a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Qualification Operational Test and Evaluation\"\n }, \"QOT&E\"), \". QOT&Es are independent and\\ndedicated operational tests that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" conducts in as realistic an\\noperational environment as possible to evaluate a system's operational\\ncapability as determined by its effectiveness and suitability in its\\nintended operational environment. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Qualification Operational Test and Evaluation\"\n }, \"QOT&E\"), \" is the final dedicated phase of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E preceding a full-rate production (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full-Rate Production\"\n }, \"FRP\"), \") decision. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" can conduct\\nQOT&Es to inform the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full-Rate Production\"\n }, \"FRP\"), \"/initial operational capability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Capability\"\n }, \"IOC\"), \")/full\\noperational capability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full Operational Capability\"\n }, \"FOC\"), \") and fielding decisions. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \" M/I/Q/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \"\\nreport and classified report annex templates posted on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nIntranet Library contain more information. Also see the \\\"\", 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\\nGuide,\\\" 11th ed. for staffing guidelines.\"), mdx(\"h4\", null, \"\", mdx(\"abbr\", {\n parentName: \"h4\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \" Final Reporting\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \", a continuation of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Qualification Operational Test and Evaluation\"\n }, \"QOT&E\"), \", answers specific questions\\nabout unresolved COIs and test issues, verifies resolution of\\ndeficiencies determined to have substantial or severe impact on mission\\noperations, or completes areas not finished during the I/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Qualification Operational Test and Evaluation\"\n }, \"QOT&E\"), \".\\nRequirements for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \" are documented in an approved \", 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 report\\nprior to planning the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \". The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \" M/I/Q/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \" report and classified\\nreport annex templates posted on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library contain\\nmore information. Also see the \\\"\", 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 Guide,\\\" 11th ed. for\\nstaffing guidelines. In addition, DoDI 5000.02, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 99-103 contain\\ndetails on FOT&Es.\"), mdx(\"h4\", null, \"\", mdx(\"abbr\", {\n parentName: \"h4\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \" Final Reporting\"), mdx(\"p\", null, \"MOT&Es are essentially \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&Es involving more than one military Service. A\\nstanding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \", signed by the four Service OTAs and the Joint\\nInteroperability Test Command (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Interoperability Test Command\"\n }, \"JITC\"), \"), outlines roles, responsibilities\\nand event-driven deliverables for participating Service OTAs. Test team\\nmembers should review the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \" prior to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \" reporting activities. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Multiservice Operational Test and Evaluation\"\n }, \"MOT&E\"), \"\\nreport coordination is generally more challenging and takes longer. Per\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \", supporting OTAs will use the lead \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test Agency OR Other Transactions Authority\"\n }, \"OTA\"), \"'s processes and products\\nduring the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activities. However, even in a supporting role, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nTDs still have the responsibility to know, understand, and be able to\\npresent overall test results. The Multiservice \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Memorandum of Agreement\"\n }, \"MOA\"), \", the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \" M/I/Q/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Follow-on Operational Test and Evaluation\"\n }, \"FOT&E\"), \"\\nreport and classified report annex templates posted on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nIntranet Library contain more information. Also see the \\\"\", 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\\nGuide,\\\" 11th ed. for staffing guidelines.\"), mdx(\"h3\", null, \"Interim Summary Report\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence, Surveillance, and Reconnaissance OR Interim Summary Report\"\n }, \"ISR\"), \" is provided to the appropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" signature authority within\\n10 calendar days of completion of the final phase of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E (\", 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,\\netc.). An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Intelligence, Surveillance, and Reconnaissance OR Interim Summary Report\"\n }, \"ISR\"), \" is a time-sensitive alternative to a final report (with an\\nexpedited review cycle) used to meet a decision date that occurs before\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" can complete its final report. It is a short (15 pages maximum)\\nsummary that provides preliminary results of the test team's significant\\nfindings to credibly inform the decision maker about the system's\\neffectiveness and suitability. Distribution is limited to essential\\naddressees; however, expanded external circulation may be appropriate\\nfor programs with high interest or upon request or direction. ISRs are\\nstaffed following the product review procedures in the \\\"\", 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\\nGuide,\\\" 11th ed.\"), mdx(\"h3\", null, \"Operational Utility Assessment Final Reporting\"), mdx(\"p\", null, \"An operational utility assessments (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Assessment\"\n }, \"OUA\"), \") is a judgment of a system's\\nmilitary utility when exposed to representative threats while\\noperated/maintained in realistic operational environments by typical\\noperators/maintainers. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Assessment\"\n }, \"OUA\"), \" tool and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Assessment\"\n }, \"OUA\"), \" report template\\nposted to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library contain more information.\"), mdx(\"h1\", null, \"COORDINATION AND PUBLISHING\"), mdx(\"p\", null, \"With the ever evolving acquisition environment, reduced resources, and\\nexpanding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" roles, it is imperative that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" optimize its final\\nreport routing process, while maintaining both technical and\\nadministrative quality. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" leadership expects the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" technical\\nadvisor (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \") to ensure that each report is technically accurate and\\nsupportable and that it was reviewed by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"'s technical editor (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \")\\nprior to forwarding it to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" for coordination. Emphasis is placed on\\nusing final report templates to establish the foundation of the final\\nreport prior to test start. A strawman of the final report should be\\nready for review at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \" briefing. Remaining sections of the final\\nreport should be written as test events are completed to meet the\\ntimeline from last test event to submission of the final report for\\nstaffing and signature. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test director, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" are\\nresponsible for ensuring that all reports (e.g., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Situational Report\"\n }, \"SITREP\"), \", status, and\\nsignificant event) are ready for signature when they enter 2-letter\\nand/or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coordination. See the \", 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 Guide for coordination\\ndetails.\"), mdx(\"h2\", null, \"Controversial Information\"), mdx(\"p\", null, \"Potentially controversial information must be passed up the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" chain\\nof command before it is shared outside of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", and preferably before\\nofficial coordination begins. Delaying discussion of issues found early\\nin the evaluation and reporting phase can limit \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s options to\\nrespond to those issues.\"), mdx(\"h2\", null, \"Signature/Approval Levels\"), mdx(\"p\", null, \"The approval levels are documented in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" delegation memorandum\\nposted in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Intranet Library. See this site for current\\ndelegation guidance. All reports should have the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test director, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Advisor OR Test Area\"\n }, \"TA\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s signature.\"), mdx(\"h2\", null, \"Coordination Method\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Collaborative Action Platform (ACAP) system is the preferred\\ncoordination tool. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-3 (A-3Z for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Assessment Plan OR Security Assistance Program OR Special Access Program\"\n }, \"SAP\"), \") is the staff-lead for\\ncoordinating all test reports. However, in certain, time-sensitive\\ncases, email or other methods may be used. Discuss coordination methods\\nas soon as possible with A-3 if ACAP will not be used to coordinate. All\\nreports should be posted on the program's test management page.\"), mdx(\"h2\", null, \"History Office\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" will transmit a copy of all reports they distribute\\nto the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"HQ AFOTEC History Office\"\n }, \"HO\"), \".\"), mdx(\"h2\", null, \"Technical Editor Role\"), mdx(\"p\", null, \"The Detachment technical editor (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \") works with their leadership to\\nensure the final report complies with current \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" template, writing,\\nformatting, and style requirements. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" maintains configuration\\ncontrol of the draft final report and provides guidance to test teams.\\nAt a minimum, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" is involved in the following three stages of the\\nwriting process: provide the test team instruction and current template\\nguidance prior to writing; format and review the final report before or\\nafter \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \" coordination; perform a final edit prior to submission into\\n2-ltr coordination. Once the final report enters \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" coordination, the\\nA-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" maintains configuration control. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Assessment OR Operational Availability\"\n }, \"OA\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Assessment\"\n }, \"OUA\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Utility Evaluation\"\n }, \"OUE\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report\\ntemplates reside on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint.\"), mdx(\"h2\", null, \"Report Medium\"), mdx(\"p\", null, \"Reports are coordinated using ACAP, unless the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" obtains \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Chief of Staff OR Command Section OR Conducted Susceptibility OR Contractor Support OR Cybersecurity Strategy\"\n }, \"CS\"), \" approval\\nto use another method.\"), mdx(\"h2\", null, \"Report Timeline Exceptions\"), mdx(\"p\", null, \"Coordination could take longer on some programs (i.e., classified) or\\nrequire an expedited process due to shortened time between completion of\\ntesting (i.e., \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Last Test Event\"\n }, \"LTE\"), \") and the decision date. If the timelines outlined in\\nAttachment C need to be modified to meet requirements of a particular\\nreporting situation, contact A-3 early in the reporting process to\\ndevelop an agreeable alternative.\"), mdx(\"h2\", null, \"Final Report Publishing\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" is responsible for ensuring the distribution list documented in\\nthe final report contains accurate and up-to-date \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \" and SIPRNet\\naddresses for program-specific personnel (individuals, not workflow\\naddresses). Once 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\"), \" has signed the final product (keeping in\\nmind the timeline for staff coordination outlined in Attachment C), the\\nfollowing procedures are followed to publish the final report:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"If the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" wishes to include additional files (briefings,\\nvideos/photos, interviews, related reports, etc.) with the final\\nreport, the additional files will be included as supporting\\ndocumentation during ACAP 2-ltr coordination. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" ensures\\nthese additional files are in a format compatible with the final\\nreport file.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Following final review and approval/signature by 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\"), \", the\\nreport and all attachments, annexes, and appendices are considered\\nfinal; no further changes are authorized without 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\\napproval.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" converts the master report file into an electronic \\\".pdf\\\"\\nfile, including additional files as requested by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \".\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" transmits the file to individuals indicated on the\\ndocument's distribution list. If the file is classified, or if there\\nis a classified annex to the file, the A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" provides \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \"\\nnotification to the same individuals stating the file was\\ndistributed via SIPRNet.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Manager\"\n }, \"PM\"), \" posts these files to the program's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Non-Secure Internet Protocol Router Network\"\n }, \"NIPRNet\"), \" test\\nmanagement page (and SIPRNet, if applicable) and removes all\\nprevious versions.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The A-3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" transmits a copy of the file to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Technical Information Center\"\n }, \"DTIC\"), \" for processing.\"))), mdx(\"h2\", null, \"Report Briefings\"), mdx(\"p\", null, \"Report briefings should be in the approved format found on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nSharePoint. If the template formally changes after the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Readiness Review\"\n }, \"TRR\"), \" briefing, the\\nprevious template can be used unless \", 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\"), \" directs significant\\nchanges requiring use of a draft template. Additionally, the command\\nsection may require modified, new, or deleted information that requires\\nupdating slides in the existing template. Briefings to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \" and agencies\\noutside the Air Force are normally briefed 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\"), \" first. The user and\\nprogram office are normally represented. The briefing is reviewed and\\ncoordinated, as documented in Attachment C, and externals (program\\noffice, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Material Command\"\n }, \"AFMC\"), \", operating command, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters\"\n }, \"HQ\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \") are pre-briefed, as\\nappropriate.\"), mdx(\"p\", null, \"The report briefing is staffed with the written report as a package. An\\nelectronic copy of the briefing is maintained on the program's test\\nmanagement page. Detailed backup slides are not transmitted outside of\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \". 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 briefings required by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Office of the Secretary of Defense\"\n }, \"OSD\"), \" or other\\nexternal agencies before they are presented outside of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".\"), mdx(\"p\", null, \"The briefing trail begins with internal briefings that lead to 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\": \"Commander OR Critical Component\"\n }, \"CC\"), \"-approved and coordinated presentation. Consistent with 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 \\\"no surprises\\\" policy, the test team should encourage\\nparticipation in 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\"), \" presentation by personally inviting the\\nuser and developer communities. Prior to inviting any \\\"externals\\\" to the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \"'s briefing, the proposed attendees must be approved by the command\\nsection. Include proposed external invitees on the briefing request\\nform. Every attempt should be made to include the user and program\\noffice via video-teleconference or telephone conference. Attachment C\\ncontains the product review process for staffing the report briefing.\"), mdx(\"p\", null, \"There is a need for persistent communication and coordination with our\\nmission partners and our chain of command to achieve an uneventful final\\nreport briefing to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \".\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Flexibility and prior preparation are keys to a successful final\\nreport briefing. Know your audience and anticipate their concerns.\\nWork closely with your \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" action officer to know what they will\\nbrief to the Director and ask for feedback after the briefing.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Prior coordination is key to final preparations. After \", 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\"), \"\\napproves, ensure briefings are reviewed and coordinated with our\\nmission partners and our chain of command. We strive to achieve a\\nunified Air Force position with no surprises.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Coordinate responses to anticipated questions prior to the briefing.\\nYou should answer only questions pertaining to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E results or\\nobservations made during testing. It is imperative to have the right\\npeople (normally the user/program office) available to address\\nquestions outside of our lane.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Coordinate with the using \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Major Command\"\n }, \"MAJCOM\"), \", program office, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Secretary of the Air Force\"\n }, \"SAF\"), \"/AQ and others\\nto establish a clear understanding of each participant's\\nresponsibilities. Questions about \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" and operational impact\\nshould go to the user representative. Questions concerning funding,\\ncontinued development, or plans for correcting deficiencies should\\nbe answered by the program office.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Have contingency plans and additional briefings by the proper\\nattendee ready to address issues you know are important to your\\naudience or to facilitate discussions. For example, the program\\noffice may need to prepare a briefing describing their plan for\\ncorrecting deficiencies following \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. These special briefings\\nshould also be coordinated at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"General Officer\"\n }, \"GO\"), \" level well before the briefing.\\nThe additional briefs may not be needed, but you should have them\\navailable in case they are required.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Always stay in your lane. Do not answer rhetorical questions or\\noffer opinions unless specifically asked, and remember you are\\nspeaking for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander.\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#test-activity-sequence","title":"TEST ACTIVITY SEQUENCE"},{"url":"#analysis-evaluation-and-reporting","title":"ANALYSIS, EVALUATION, AND REPORTING","items":[{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#reporting","title":"Reporting"}]},{"url":"#structure-of-an-evaluation","title":"STRUCTURE OF AN EVALUATION","items":[{"url":"#ote-evaluation-structure","title":"OT&E Evaluation Structure"}]},{"url":"#rating-tenetsprinciples","title":"RATING TENETS/PRINCIPLES","items":[{"url":"#rating","title":"Rating","items":[{"url":"#terminology","title":"Terminology"},{"url":"#report","title":"Report"}]},{"url":"#ratings-and-visual-indicators","title":"Ratings and Visual Indicators"},{"url":"#rating-taxonomy","title":"Rating Taxonomy","items":[{"url":"#ote-and-oue-rating-taxonomy","title":"OT&E and OUE Rating Taxonomy"},{"url":"#eoa-and-oa-rating-taxonomy","title":"EOA and OA Rating Taxonomy"},{"url":"#operational-utility-assessment-oua-rating-taxonomy","title":"Operational Utility Assessment (OUA) Rating Taxonomy"}]}]},{"url":"#ratings-for-continuous-and-cumulative-feedback","title":"Ratings for Continuous and Cumulative Feedback"},{"url":"#rating-measures","title":"RATING MEASURES","items":[{"url":"#general-methods-for-rating-measures","title":"General Methods for Rating Measures","items":[{"url":"#direct-measurement","title":"Direct Measurement"},{"url":"#reasonable-inference","title":"Reasonable Inference"}]},{"url":"#types-of-measures","title":"Types of Measures"},{"url":"#measures-worksheet","title":"Measures Worksheet"},{"url":"#rating-measures-of-effectiveness","title":"Rating Measures of Effectiveness","items":[{"url":"#basis-for-moe-evaluation","title":"Basis for MOE Evaluation","items":[{"url":"#effect-criteria-or-identified-standard","title":"Effect Criteria or Identified Standard"},{"url":"#feedback-from-test-participants","title":"Feedback from Test Participants"},{"url":"#problemsdeficiencies","title":"Problems/Deficiencies"},{"url":"#required-workarounds","title":"Required Workarounds"},{"url":"#statistical-confidence","title":"Statistical Confidence"},{"url":"#reasonable-inference-of-mop-and-mos-impacts","title":"Reasonable Inference of MOP and MOS Impacts"},{"url":"#key-performance-parameters","title":"Key Performance Parameters"},{"url":"#moe-notable-findings","title":"MOE Notable Findings"}]}]},{"url":"#rating-mops-and-moss","title":"Rating MOPs and MOSs","items":[{"url":"#test-conditions","title":"Test Conditions"},{"url":"#deficiency-reports","title":"Deficiency Reports"},{"url":"#beyond-the-point-estimate","title":"Beyond the Point Estimate"},{"url":"#operational-experiencejudgement","title":"Operational Experience/Judgement"},{"url":"#key-performance-parameters-1","title":"Key Performance Parameters"},{"url":"#additional-observations","title":"Additional Observations"}]}]},{"url":"#rating-critical-operational-issues","title":"RATING CRITICAL OPERATIONAL ISSUES","items":[{"url":"#basis-for-coi-evaluations","title":"Basis for COI Evaluations","items":[{"url":"#preponderance-of-measures-meeting-criteria","title":"Preponderance of Measures Meeting Criteria"},{"url":"#prominent-measures","title":"Prominent Measures"},{"url":"#operational-conditions","title":"Operational Conditions","items":[{"url":"#cyber-effects","title":"Cyber Effects"}]},{"url":"#interaction-of-results","title":"Interaction of Results"},{"url":"#holistic-considerations","title":"Holistic Considerations"},{"url":"#coi-notable-findings","title":"COI Notable Findings"}]}]},{"url":"#rating-operational-effectiveness-and-suitability","title":"RATING OPERATIONAL EFFECTIVENESS AND SUITABILITY","items":[{"url":"#rating-effectiveness-and-suitability","title":"Rating Effectiveness and Suitability"}]},{"url":"#mission-capability-determination-optional","title":"Mission Capability Determination (Optional)"},{"url":"#test-reporting","title":"TEST REPORTING","items":[{"url":"#continuous-reporting","title":"Continuous Reporting","items":[{"url":"#operational-assessment-reports","title":"Operational Assessment Reports"},{"url":"#status-reports","title":"Status Reports"},{"url":"#periodic-reporting","title":"Periodic Reporting"},{"url":"#observation-reports","title":"Observation Reports"},{"url":"#significant-event-reports","title":"Significant Event Reports"},{"url":"#operational-test-situation-reports","title":"Operational Test Situation Reports"}]},{"url":"#final-reporting","title":"Final Reporting","items":[{"url":"#effectiveness-and-suitability-final-reporting","title":"Effectiveness and Suitability Final Reporting","items":[{"url":"#oue-final-reporting","title":"OUE Final Reporting"},{"url":"#iote-final-reporting","title":"IOT&E Final Reporting"},{"url":"#qote-final-reporting","title":"QOT&E Final Reporting"},{"url":"#fote-final-reporting","title":"FOT&E Final Reporting"},{"url":"#mote-final-reporting","title":"MOT&E Final Reporting"}]},{"url":"#interim-summary-report","title":"Interim Summary Report"},{"url":"#operational-utility-assessment-final-reporting","title":"Operational Utility Assessment Final Reporting"}]}]},{"url":"#coordination-and-publishing","title":"COORDINATION AND PUBLISHING","items":[{"url":"#controversial-information","title":"Controversial Information"},{"url":"#signatureapproval-levels","title":"Signature/Approval Levels"},{"url":"#coordination-method","title":"Coordination Method"},{"url":"#history-office","title":"History Office"},{"url":"#technical-editor-role","title":"Technical Editor Role"},{"url":"#report-medium","title":"Report Medium"},{"url":"#report-timeline-exceptions","title":"Report Timeline Exceptions"},{"url":"#final-report-publishing","title":"Final Report Publishing"},{"url":"#report-briefings","title":"Report Briefings"}]}]},"parent":{"__typename":"File","relativePath":"fn_guides/evaluation_and_reporting_guide.md"},"frontmatter":{"metaTitle":"Evaluation and Reporting Guide","metaDescription":"Evaluation and Reporting Guide"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"c1a3de9d-c097-5471-bd2c-8338370972f9"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/fn_guides/lessons_learned_guide/page-data.json b/sites/oteguide/page-data/fn_guides/lessons_learned_guide/page-data.json deleted file mode 100644 index 943d35f7..00000000 --- a/sites/oteguide/page-data/fn_guides/lessons_learned_guide/page-data.json +++ /dev/null @@ -1 +0,0 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides/lessons_learned_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"205149b6-7b93-5483-a0d5-fc1cf0a126f8","title":"Lessons Learned Guide","slug":"/fn_guides/lessons_learned_guide"},"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\": \"Lessons Learned Guide\",\n \"metaTitle\": \"Lessons Learned Guide\",\n \"metaDescription\": \"Lessons Learned Guide\"\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, \"Last Updated/Reviewed: 08 December 2020\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9\"), mdx(\"h1\", null, \"INTRODUCTION AND INTENT\"), mdx(\"p\", null, \"The goal of this guide is to provide an introduction to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nLessons Learned (LL) process, explain the importance of the LL effort,\\nand finally show where this process is tied to established policy and\\nguidance. This process is mandated by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-1302, but the\\nimplementation and usefulness of this effort is dependent on the\\nwillingness of the organization to consider and develop valuable inputs\\nto the program. The previous iteration of this process relied on a\\n\\\"push\\\" from Test Directors at the close-out of programs and would be\\npresented during the final briefing to the Commander. Lessons Learned\\ncan and should be produced at any point in a program lifecycle, but will\\nnow have a dedicated end of program event to discuss and collect\\nobservations. Lastly, Lessons Learned is just one aspect of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\ncommitment to continuous process improvement, and the increases in\\neffectiveness and efficiency that come of that active institutional\\nfeedback.\"), mdx(\"p\", null, \"It is the expectation that this guide will provide clarification of the\\nprocess that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses to collect, track, and disseminate and\\nimplement LL. This guide will serve as a reference for when and who to\\ncontact to submit identified lessons for evaluation and what to expect\\nafter submitting a proposed LL.\"), mdx(\"h1\", null, \"Vocabulary of Lessons Learned\"), mdx(\"p\", null, \"In the standard process of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \" LL identified in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-1302 (shown in\\nfigure 1), there are a series of steps all LL proceed through. These\\nsteps are collection, validation, dissemination, and resolution. This\\nstandard process is open to interpretation and implementation for each\\norganization, but the broad strokes will be described.\"), mdx(\"p\", null, \"Figure 1. Lessons Learned Process ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Diagram per \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-1302\"), \" )\"), 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\": \"554px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/b4cd47565392bce2eea73fe8ef510a4b/04abd/image2.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\": \"77.60617760617761%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAQCAIAAACZeshMAAAACXBIWXMAAAsTAAALEwEAmpwYAAADMklEQVQoz3VRWU8aURTmv7Rqmj60L9VU0zSNpu1PaNKkS7o+NY1L7JJYECVdcE0XXCJoothWAwUqgiIqsomizCioiGWYgZmBcURggGHtHacx8aE3X26+e7/z3XPPOQLDhszkUcx75CZIYYYVCzC3mzzy2dXhWReHBUhxAjmQAAHSCUaCBCLo+lXzRX+7T1vfpbohHr8mGq0TjdW1jVx9Lat5Jatu/XqlTV4rHK17p6jtmLgmVd3o0Tb06gDq4aBL8N3e/9M5MGb5Mr3ybX51SG8f1NlketvAnGvI6BzSOwa0VpnROWhwDM7YB/TOwYWN4WVYvrKlCBJBgZ9I0DRDMTk0yZbL5VKp/L9VOtHiR8ckfgjIMZMTIDg+4UXEFphhOXM8k223wJs4xRt0u+iwe69YKgA+ux+e9oVoKppiUlwkwwrKbLrXtXdnysJHR1OZ6hHDjB/jj+Jl+K7aBrICLlyCH6ut2VSS/xyXOUmR0pWtR1pHqVgs5lgymb6lXJrbDwO5kM102baf6xyFQr7MZj/avM3G9dPSOHMhlRDPr91XrQT8/v29XSjwB5i/u7a2N92hg4BkyfNE64A8mxEkKF70NM+5z5jpCPbJAj1QW6lYlIyE/WH8pnJpat0XDv6JhBBgfqpzhjGMJvGOZajJeNacoMge585DjYMvkkpnG8bNpgOcOxTyUrvv2W8nqAhY3tt8TYaz3wb8s/vgvsbBJBJ8w64rLSrIzzfpg3P3ntoep2nAO207oH7QsPJpw9DDozUkshjADrBwLsPkCnkveYgQZJzmhonSx/4YHSWJYp7F4okARcdIIncyVM7sPUp7ESKYZF2h6CEd519NpdMRkh81lx8jYgkmy0uhCOCZf3OObs2hmg7M0E3MfMiY+zKL/enFfsogRTUfSUMvqpNGDd2MqQfcpxb6GBBg7mXN3SysOU4XBPjPt2xnFdV5GWm76Gut8rZWQc2V7qbK9caKtcaK1Zfn1hrPwy1VUEslkPbfXCA6LiXaK3LTL+KZkgBb/R2ZFqJqSVjdiWskgSmxVynamRT5JtsBdibbtydE8LjQ/0NMaLgYVCXBVaKYVUmn8n8BERr8N8GUTTYAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image2\",\n \"title\": \"image2\",\n \"src\": \"/static/b4cd47565392bce2eea73fe8ef510a4b/04abd/image2.png\",\n \"srcSet\": [\"/static/b4cd47565392bce2eea73fe8ef510a4b/a2ead/image2.png 259w\", \"/static/b4cd47565392bce2eea73fe8ef510a4b/6b9fd/image2.png 518w\", \"/static/b4cd47565392bce2eea73fe8ef510a4b/04abd/image2.png 554w\"],\n \"sizes\": \"(max-width: 554px) 100vw, 554px\",\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, \"During the Collection phase of a LL, an \\\"Observation\\\" is created and\\nsubmitted to the LL Manager by a member of the organization. This\\nObservation is catalogued for tracking, then validated at the\\nappropriate level and with the appropriate process owners and experts.\\nIf the Observation is validated, it is assigned an action officer who\\ndetermines the necessary actions for implementation. The Observation\\nbecomes a \\\"Lesson Identified\\\", and is disseminated to the appropriate\\nmembers of the organization. Once the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \" has completed the\\nimplementation actions, and all relevant members are notified and\\ntrained on the changes, the Lesson Identified becomes a Lesson Learned\\n(Resolution).\"), mdx(\"h1\", null, \"Policy Guidance\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \" Lessons Learned policy is captured in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-1302, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Air Force\\nLessons Learned Program\"), \" .\"), mdx(\"h1\", null, \"PROCESS\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" LL process, illustrated in figure 2, adheres to the broad\\nstrokes defined by policy and implements them in a mixed pull\\n(interviews/surveys) and push process (SharePoint).\"), mdx(\"p\", null, \"Figure 2. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Lessons Learned Process\"), 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\": \"553px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/8173e07865edf8362ed55de244590c45/74cfa/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\": \"44.4015444015444%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAJCAIAAAC9o5sfAAAACXBIWXMAAAsTAAALEwEAmpwYAAACHUlEQVQozy2R7U9SARTG/Xf60NrIggB5NRBnri/WVroIrjFGW0CzGklLZi2sZEscqNzkLcx2Z7qZDNoYYmAyhUhi9obGagtbbXLv5b5fuihnz3l2dnZ+53w4bY3DYGgagWskgTUa7FGHYpgDFCUoiqtZloVRDKnjnNcQ7ADBGaY51kZStHshZ5teHZqI3fOl7MGtdK781fMsabuzYjEnbLe3HCPV9eQeZC9NGb/7b/wIWaphE/ar1IRxgro0GuVppwSAR3Rt+qRpYW6lkLtycaad5xWcnhXy30jEFShQdnWvm48Vh9v3x0R/H5wgvqUPYZw0uTNKy0uVOdhlDUmt0GQwngUGwko52Cmf16iSveey3vGSq3fTJti0i7cdsk/2U8TuRuvy4NOExOSXG72aoVcS6+vwUjZv0L6QS0GFLKJSLqvVOxHwj6+v8lAMu1V1TxfsEhPl9y0YGItJTQG1NaK2hDosEBQvFoy659IOUCkPnVXMKRSVxcjvmQs79898HJGUnYp/T0TkEYzhpN71jj8IioBJ2XW/0Lo8Hy3k9f2LMsnbbnWqR5NQde5BgS/jPRs3j2/b+Z8dwuoojyxnmjBBUndnswOP4vrHceNE5rJzNZoqFYdvrem0GQOQNgBruqs/Y0u7fuMH5/l9X38toIXBPqKSb8Jc1nEKxUhOzU/WuW00VUcJGCGRlhiSbFD1BomyOMLgCI3BLENz4H/7XnAM533YIwAAAABJRU5ErkJggg==')\",\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/8173e07865edf8362ed55de244590c45/74cfa/image3.png\",\n \"srcSet\": [\"/static/8173e07865edf8362ed55de244590c45/a2ead/image3.png 259w\", \"/static/8173e07865edf8362ed55de244590c45/6b9fd/image3.png 518w\", \"/static/8173e07865edf8362ed55de244590c45/74cfa/image3.png 553w\"],\n \"sizes\": \"(max-width: 553px) 100vw, 553px\",\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 stand-alone LL submissions form can be found on the LL\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://cs2.eis.af.mil/sites/10008/functional/lessons/SitePages/Home.aspx\"\n }, \"Sharepoint\"), \"\\nsite (example in Appendix A), along with contact information for the\\ncurrent LL manager. The submission of LL by team members can be\\nperformed at any time during a test program, and is encouraged while\\nmemory of an event is still fresh. This process has a number of\\nbenefits. For interviews it ensures that test directors, having\\ncompleted a test event and necessary reporting, are prepared and have\\nthe necessary bandwidth to thoughtfully consider any lessons or problems\\nthey encounter during the test program. Test team members are encouraged\\nto step back and give the organization its best opportunity to learn\\nfrom the challenges they encounter and solutions developed. Surveys\\noffer a focused opportunity to be directed by questions through the\\ndifferent aspects of their duties and highlight issues they've\\nencountered in each. Finally, self-reported observations offer out-of-\\nsequence opportunities for team members to identify issues and solutions\\nthey have uncovered during the normal accomplishment of their duties.\"), mdx(\"h1\", null, \"Milestone/Event Triggers\"), mdx(\"p\", null, \"The LL program has several specific triggers for the process. The first\\nis the submission of a final report and briefing on a program. This\\ntriggers the scheduling of an interview with the program test director,\\nand distribution of the interview worksheet (Appendix B). The second\\ntrigger is the departure of a test director from the organization.\\nEither by self-report or otherwise, the Lessons Learned manager\\nschedules an interview with the test director, as their timeline allows.\\nWhen a test director or team member schedules an interview, they are\\ngiven at least one weeks' notice to compile their thoughts, and then sit\\ndown for an interview with the Lessons Learned manager. During this\\nmeeting the LL manager explores and discusses the issues and novel\\nsolutions the test team member experienced during the test program.\\nThese notes and any specific observations captured are then crafted into\\nObservations for review. The third trigger is self-submission of\\nObservations through the internal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint site. Finally,\\nannual \\\"Drivers Surveys\\\" will be used to record the problems most\\nimpeding our member's accomplishment of their duties and can be used to\\ndraft observations to initiate the next phase.\"), mdx(\"h1\", null, \"Observations Review\"), mdx(\"p\", null, \"As interviews are accomplished, or observations are submitted, the LL\\nManager and division chief will sort through and initiate a disposition\\nof each observation. These observations will be reviewed with the\\nassistance of any pertinent experts or necessary process owners. If the\\nobservation is determined to be valid, the Observation becomes a Lesson\\nIdentified (LI), and proceeds to the next step. If the Observation is\\ndeemed invalid, the LL manager will craft a response to the submitter\\ndetailing why it was deemed invalid, and give the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" the chance to\\nfurther elaborate if they think the decision was reached with incomplete\\ninformation or understanding.\"), mdx(\"h1\", null, \"Dissemination\"), mdx(\"p\", null, \"Once a \\\"Lesson Identified\\\" is found by the LL team, it must be assigned\\nan action officer. This action officer is given the task of developing\\nthe actions necessary to incorporate the LI into the organization. These\\nactions are highly dependent on the individual LI, and will have to\\nadjust to the unique requirements of each LI.\"), mdx(\"p\", null, \"Once implementation actions are identified, the action officer will need\\nto regularly report on progress towards completion and keep the LL\\nmanager apprised of changes. The final goal of this process will be to\\nhave each of these LL incorporated into training, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E guide, or\\nOTIFs as appropriate; they will not exist within some stand-alone\\ndatabase of test advice.\"), mdx(\"h1\", null, \"Lessons Learned (Resolution)\"), mdx(\"p\", null, \"The final step is resolution, where the LI has reached a successful\\nimplementation and dissemination. The LI has improved how the\\norganization performs the mission, and the LI is changed to a LL. The\\nimplementation plan is closed and the LL is catalogued for reference.\"), mdx(\"h1\", null, \"CONCLUSION\"), mdx(\"p\", null, \"It is the place of every member of our organization to ensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ncontinues to learn and adapt. We must give our organization every\\nopportunity to respond to new challenges in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" acquisition\\nenvironment however they arise, be it policy, funding, or global\\nsituations. This process is one of the steps being taken to support our\\ncombined efforts to face and learn from the challenges of our mission,\\nand depends on our partners across the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" enterprise and their\\nwillingness to participate to support this endeavor.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Lessons Learned process is owned by A-2/9, and staffed by\\nmembers of A-9O. Any questions, comments, or suggestions for improvement\\ncan be directed to this office.\"), mdx(\"h1\", null, \"OBSERVATION SHEET\"), 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\": \"817px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/688af7e1bde67ae8e5b5f8c57a84b5f2/98314/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\": \"125.86872586872589%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAZCAIAAAC+dZmEAAAACXBIWXMAAAsTAAALEwEAmpwYAAACWUlEQVQ4y4WUaU/bQBCG+f+/p6pEqWhpVYkPlfoRkICExNd67b0v7+WO45SGOIHR49X4eD0z2tm5GA8sH1gIwXsPa4zx8Pnrxymli/GMWWuFEEop59zJD47F6/X67u5us9k8PT2B//z8/Pj4eH9/v1qtHh4ewCmK4qyYMYYxppQSQqYLrAfrZh93HeRyLIZKjDFcez5k4Uc2ZDaM8X91I5TNpYZXxGUX8nFk+P92s2k60jDTiqHVEevQKgCcBLeTr2Mjg/ULMSTcoL2VnSioK5lDKjbcNkQ2VL90qqS2EVH7tBRT3KK+w6hFJeqKui3r1vpkjBWMSCkx4VxZyDmkRWQqTQEBO171oqEQSta9YDZIn2UYpR/VtGbu0hCXYjuWaqw1kCuVS5kLETfMT9CJlx1r6sWwSJtr21Ix0zFFpYXajM9HaP827dklwmwxLzEv8JQ5YobbtISZdGKrqMulSLXaIVMlY8nDki0LwqVlzbHgvhIz4RwFD/KMOLwj+1C8C8t3vAr4m1xOi5nLlcyNyvuy/zE9kQk0M5ujmvO+SfQWkbIlRUsqTOuOVR1rel6gHlY1pBl51CR7sXJFL8sdFVE10dNKNdzCSkyc6XW0J7bK5kJCb8EmzUCTpVLEGdihmRd6aqu48TW3SLjpGAHTwXS9DnvORZ5HGtS1rjAUvCpRPZVKml6YOOowoXyGlgb4kPzyYIQ0ujhCzxsfb37dfv5y/fX7z8vrm6tvPz5dXt3+/gMBjU/Q8CeO5OH8VVJwRluE6qpqUYNxa4z+eHoeGkxcmLta63dG71/S2543NIPBlAAAAABJRU5ErkJggg==')\",\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/688af7e1bde67ae8e5b5f8c57a84b5f2/98314/image4.png\",\n \"srcSet\": [\"/static/688af7e1bde67ae8e5b5f8c57a84b5f2/a2ead/image4.png 259w\", \"/static/688af7e1bde67ae8e5b5f8c57a84b5f2/6b9fd/image4.png 518w\", \"/static/688af7e1bde67ae8e5b5f8c57a84b5f2/98314/image4.png 817w\"],\n \"sizes\": \"(max-width: 817px) 100vw, 817px\",\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, \"INTERVIEW SHEET\"), 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\": \"926px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/1882a4460923a55391e4af55449a1048/69476/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\": \"129.34362934362935%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAaCAIAAAA44esqAAAACXBIWXMAAAsTAAALEwEAmpwYAAACgklEQVQ4y61UaW+jMBDt//9bq90Pu5XabJKqnMHGNocPMDeE4B1I0pKs2kqrHT2NHxZv/DyDeKiqyhgzTdM5r+O0xN2mWcXDWnwX02k6HkfzcTyUZQkLnAA5YpFlWRjjkBDICCH/cHAcFwjsOa7bNM1c9E6steZC2La9ed7sdvv9br9bYrPZbLfblz3Ey9PTM6V0HMc3mxexlBKqR0nCpeBSxQkwHqdpnMw0FQJynufwcpblZ5vv4qapuWrSpE0CHSOdYs0RE78d+exlT04eMtBUZdm0Q9GYvDRn+UUMVQMchh6mTsR2hP4i5BHTRxz+RIfvXvj9tS3qth3a9jgMI0zg5mToOedczc605Ck0IOeZTESWCplKgcj223b3wyYvqQ4YjOFGrJR6tT0/iOqqxIS2Xet4hEYJ9CJKskwXhdaUimkczWqoF3FZFkKIKE5hEPPdoEYFa6nkvDkMw2dz1rpisUq5lqrisgAiVJnwHEjdjN1gun6a8xXnb+ci5tlp7482OlnBaJ1zcOEeMTegxsImVitxVgx+2CDWBKQJ6AJSA8eshXxYOGItEB+XLB3Lei3Wo4e7gPZnHEg3g3aIvT/OhM4Ex2NeXcTzKvRkY+MT4y7e3KtJd2X4jYPtRK3EchHfX+8DONik2X8T55ONLt7ccAVyxZXDO/bK9vKF6X7pdosXhHFP4iGMeiAAxLow6jCbgWAQrNM33c4q12MBTg8odg+MxVmue6lqoRqVt1xVYuYzuKyErPthWnU7nyw8+dR4s9sJvAH/CHCF+4Y5/9wwOPkVzSWdFc49c/6ChW7nXNQTTU0kbsA4bJ7uNgGUG11+9es9Ho9933/26/1E/GX8AWRouu9ZRXAbAAAAAElFTkSuQmCC')\",\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/1882a4460923a55391e4af55449a1048/69476/image5.png\",\n \"srcSet\": [\"/static/1882a4460923a55391e4af55449a1048/a2ead/image5.png 259w\", \"/static/1882a4460923a55391e4af55449a1048/6b9fd/image5.png 518w\", \"/static/1882a4460923a55391e4af55449a1048/69476/image5.png 926w\"],\n \"sizes\": \"(max-width: 926px) 100vw, 926px\",\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, 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\": \"922px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/854f02679aa6ba16edc99c0cc9bd8035/6da96/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\": \"129.7297297297297%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAaCAIAAAA44esqAAAACXBIWXMAAAsTAAALEwEAmpwYAAABkElEQVQ4y+1Ta0/rMAzd//+DiK3dmvdga5vXKLRZjd2uI4A2IdD9dq2j9NjNUezYWcFtSyn1fX9nw2r+xHhqra8b631EILfOt61D+HDCSDqP5xGuGHOxOaZ1NRS8L8VQilRw5EQml1BpqAyBGSgV2JCJnxrYCNgqKOUENUF+oFiA8UcOjc/FNWz4p605KTI9HrBmULtMfGjSTg1MY3oEIqpn+hKZXSJm3nD2p1xcnyrpuQ6V8kwFIsIxRRFaTcS/THth4k5Y8/zavWXi52vNS7Xba9n5inFNNR/aLxfGx1KOhSCUyzoTghwvYglrDkebp93SD+zH7gbwwJvixnZyH/RT1PsoTBDaoSuN13viXGGdL3hJLhKwya+faq7Thg9beRmJYpkN4jQw/VYmNk0IN7BT0H7p8yODQtC1fcccx2wRSB4qOORp24gTCvv6R9BHCC+Z+He2Wl7fuZ9syIy8lCaa7om7rrPWOuf8ZCHEEIKzLkZ8oT6GeE/8p7TRxsluuf/y5P/iy4Vj/39/8v1uvQM9M+DE8D5iFQAAAABJRU5ErkJggg==')\",\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/854f02679aa6ba16edc99c0cc9bd8035/6da96/image6.png\",\n \"srcSet\": [\"/static/854f02679aa6ba16edc99c0cc9bd8035/a2ead/image6.png 259w\", \"/static/854f02679aa6ba16edc99c0cc9bd8035/6b9fd/image6.png 518w\", \"/static/854f02679aa6ba16edc99c0cc9bd8035/6da96/image6.png 922w\"],\n \"sizes\": \"(max-width: 922px) 100vw, 922px\",\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":"#introduction-and-intent","title":"INTRODUCTION AND INTENT"},{"url":"#vocabulary-of-lessons-learned","title":"Vocabulary of Lessons Learned"},{"url":"#policy-guidance","title":"Policy Guidance"},{"url":"#process","title":"PROCESS"},{"url":"#milestoneevent-triggers","title":"Milestone/Event Triggers"},{"url":"#observations-review","title":"Observations Review"},{"url":"#dissemination","title":"Dissemination"},{"url":"#lessons-learned-resolution","title":"Lessons Learned (Resolution)"},{"url":"#conclusion","title":"CONCLUSION"},{"url":"#observation-sheet","title":"OBSERVATION SHEET"},{"url":"#interview-sheet","title":"INTERVIEW SHEET"}]},"parent":{"__typename":"File","relativePath":"fn_guides/lessons_learned_guide.md"},"frontmatter":{"metaTitle":"Lessons Learned Guide","metaDescription":"Lessons Learned Guide"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"205149b6-7b93-5483-a0d5-fc1cf0a126f8"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/fn_guides/measures_guide/page-data.json b/sites/oteguide/page-data/fn_guides/measures_guide/page-data.json deleted file mode 100644 index 5fcaad98..00000000 --- a/sites/oteguide/page-data/fn_guides/measures_guide/page-data.json +++ /dev/null @@ -1 +0,0 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides/measures_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"4de3df85-165d-5b6f-94c9-f1237b3cb3dd","title":"Measures Guide","slug":"/fn_guides/measures_guide"},"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\": \"Measures Guide\",\n \"metaTitle\": \"Measures Guide\",\n \"metaDescription\": \"Measures Guide\"\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, \"March 2021\"), mdx(\"p\", null, \"Last Updated/Reviewed: 25 March 2021\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9\"), mdx(\"h1\", null, \"INTRODUCTION\"), mdx(\"p\", null, \"Measurement is central to conducting operational test and evaluation\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E). This technical guide supplements the \\u201C\", 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 Guide\\u201D and\\nprovides \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" personnel the necessary background and specific\\ndirections on how to write and develop measures. The first section is a\\ngeneral overview of the fundamentals of measurement. Section 2 describes\\nhow \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" develops measures. Sections 3 provides details of measure\\ndocumentation. Appendix A provides examples of the types of continuous\\nand discrete measures. Appendix B provides checklists to ensure measures\\nare properly written. Appendix C discusses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\u2019s process for writing\\ncyber measures.\"), mdx(\"p\", null, \"Submit suggested changes to: \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:AFOTEC.A2A9.Workflow@us.af.mil\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".A2A9.Workflow@us.af.mil\")), mdx(\"h1\", null, \"SECTION 1 FUNDAMENTALS OF MEASUREMENT\"), mdx(\"h2\", null, \"Measures Overview\"), mdx(\"p\", null, \"Test measures are the basis of the evaluation of a system under test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"); they are the data used to assess effectiveness and suitability\\nand serve as evidence of system deficiencies. Operational effectiveness\\nand operational suitability are defined as follows:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Effectiveness\"), \" \\u2013 The overall degree of mission\\naccomplishment of a system when used by representative personnel in\\nthe environment planned or expected for operational employment\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Suitability\"), \" \\u2013 The degree to which a system can be\\nsatisfactorily placed into field use. Examples of issues evaluated\\nunder operational suitability:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Reliability, maintainability, availability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Compatibility and interoperability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Supportability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Transportability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Human factors\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Training requirements\"))))), mdx(\"p\", null, \"There are three general types of measures developed for Operational Test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"): Measures of effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \"), Measures of Performance (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \"),\\nand Measures of Suitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" provide direct evidence that a\\nuser can successfully employ the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" to accomplish a mission. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" can\\nbe used to evaluate the system as soon as it is feasible to test the\\nsystem in an operational environment.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"strong\", {\n parentName: \"li\"\n }, mdx(\"u\", null, \"Measure of Effectiveness (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \")\")), \" - Measures designed to\\nassess the degree to which the \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can accomplish mission objectives\\nand achieve desired mission effects. If appropriate, they may\\nquantify success as a proportion of successful test events, rate of\\nsuccess, or the probability that the system will achieve some\\nresult.\")), mdx(\"p\", null, \"MOPs and MOSs can be used to evaluate the system throughout development\\nand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. Capabilities and functions of a system are evaluated using\\nboth MOPs and MOSs. The supportability and sustainability of a system is\\nevaluated using MOSs.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"u\", null, \"Measures of Performance (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \")\")), \" - Measure a system\\u2019s\\ncapabilities. They may quantify performance such as speed, payload,\\nrange, time-on-station, frequency, rating or other distinctly\\nobservable and/or quantifiable performance features. They may also\\ndocument whether or not a system can successfully complete a task.\\nFinally, MOPs may document user ratings of system attributes.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"u\", null, \"Measures of Suitability (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \")\")), \" - Measure of the ability to\\nsupport the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" in its intended operational environment. MOSs\\ntypically relate to readiness or supportability and hence include\\nmeasures concerning reliability, availability, maintainability, the\\nquality of system documentation, the quality of training, and the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" logistics infrastructure.\"))), mdx(\"p\", null, \"All three types of measures (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \") are used by the test\\nteam to determine if a system can accomplish a mission, which is stated\\nas a Critical Operational Issue (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"). For example, the C-130J has two\\nprimary missions: conduct tactical airlift and conduct airdrop\\noperations. The following are two of the COIs from the C-130J test\\nprogram; note that the convention is to phrase COIs in the form of a\\nquestion.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1: Can the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" conduct tactical airlift\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 2: Can the C-130J conduct airdrop operations\"))), mdx(\"p\", null, \"When developing measures for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", it is useful to visualize the system\\nas having four layers that may require measurement and assessment:\\nMission Effects, System Capabilities, System Functions and Properties,\\nand System Structure. Figure 1-1 depicts these four levels in a pyramid\\nand provides definitions.\"), mdx(\"p\", null, \"Figure 1. The Pyramid: Evaluation Levels of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\"), mdx(\"span\", {\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/3a850abe9fde7feb04b16b5dcfbb9380/5819f/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\": \"54.440154440154444%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAIAAADwazoUAAAACXBIWXMAAAsTAAALEwEAmpwYAAACIUlEQVQoz2VQ30siYRSdfyrfArPeeivqwXoOIsjRxCwieqsgkIh6rAiKYFmEgnrJllwbdRylHcd1nB86zuiMo47OrqO5kzO7V2S3hT4Oh3vv9x3O/Q7y+8NRFK1SaZvmmyzriqLLcltVfwJEUZOkFkwAUBhGH/kofnjAw+F4q9WJx/mnJyaRKOJ4KZMRabrG8/VSqQlg2Xqj0XkX2/aQBcFIJns43idJwzQHg4EFPMLfZ/Y/Rv5X6roZDusnJ8zxMXV+rnHcAPxjMY4ghGiUTaVKGMZjGAdMkpXXV/NdbNtWPN69vNSOjtKHh8nT0+LNTVdReoLQkKQ2pKAoPwAQBLTNpgFLDcWWNdQnEvrenhIK1Q8OZEAopO7v166uNLiCbMCqUKgxjJrPK/BhaEWxhYwWbjR+7e7Wg0EpGCyurGBLS1/8fnpzUwgEFAzrGUYPlofYkslSKiW8vEjwC8h85GydnamBgLy+zqHoN6+X8vnyq6tpr5fc2Kju7Cg838lmxUJB5bg6Rcksq4JzuawNxXd3+sxMeXFRdLsrCwvV+fnvc3OU2y1BDcPZ2fL2ds2ybEnSwDOXq2azFeB2u4swTGd6OuN0piYniYkJwunEHY7PY2OfxsejLlfa5SKmpgiHI3F9XROE+u0tGYnQ9/dUJJLX9R5ycUEvL0f9/mefb4QYij56PI8o+jSarK09ezxft7aSLNvM5WQIjKYhM7Xff/sDFCQPUHG5M5AAAAAASUVORK5CYII=')\",\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/3a850abe9fde7feb04b16b5dcfbb9380/e3189/image7.png\",\n \"srcSet\": [\"/static/3a850abe9fde7feb04b16b5dcfbb9380/a2ead/image7.png 259w\", \"/static/3a850abe9fde7feb04b16b5dcfbb9380/6b9fd/image7.png 518w\", \"/static/3a850abe9fde7feb04b16b5dcfbb9380/e3189/image7.png 1035w\", \"/static/3a850abe9fde7feb04b16b5dcfbb9380/5819f/image7.png 1042w\"],\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, \"Measures can be used to evaluate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" at each level of the pyramid.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are used to evaluate mission effects, while MOPs and MOSs are\\ntypically used to evaluate system capabilities, system functions and\\nproperties, and system structure.\"), mdx(\"h2\", null, \"Qualities of a Good Measure Set\"), mdx(\"p\", null, \"The following are qualities of a good measures set:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Measures should be operationally relevant, necessary, and sufficient\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Measures should represent something quantifiable or observable, not\\na goal or objective\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The data satisfying a measure should be observable, or at least\\ninferable\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Measures should be clear and concise\"))), mdx(\"p\", null, \"Measures should be operationally relevant, necessary, and sufficient.\\nMeasures should only be included in a data set if they provide\\nsignificant support to one of three goals: delivering combat capability,\\ndiscovering system deficiencies, and evaluating the effectiveness and\\nsuitability of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Measures required by engineers during system\\ndevelopment may not be relevant to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" testers.\"), mdx(\"p\", null, \"Avoid the trap of writing too many measures. The resources required to\\ncollect data for measures varies, but at a minimum every measure\\nrequires the time and attention\\u2014limited resources\\u2014of a data collector.\\nTherefore, be discerning when searching requirement documents for\\npotential measures; requirements are written for system developers, not\\nnecessarily operational testers.\"), mdx(\"p\", null, \"Measures should represent something quantifiable or observable.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Poor measure: No friendly fighter losses\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Better measure: Number of friendly fighters destroyed or damaged\"))), mdx(\"p\", null, \"The goal for friendly fighter losses (zero) can be included in the\\nmeasure as a threshold used as the basis for an evaluation of acceptable\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance.\"), mdx(\"p\", null, \"The data satisfying a measure should be observable. Observable data can\\nbe either quantitative (numerical) or qualitative (descriptive). A\\nmeasurement can be objective (independently verifiable by 2 or more\\npeople) or subjective (an opinion or perception of an individual).\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Poor measure: Pilot\\u2019s opinion about the aircraft\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Better measure: Pilot\\u2019s rating (on a 5 point scale) of aircraft\\nmaneuverability\"))), mdx(\"p\", null, \"Measures should be clear and concise. Measures should be written in\\nlanguage that is understandable by someone with a limited knowledge of\\nthe system or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \".\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Poor measure: Status of enemy fighters\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Better measure: Percentage of enemy fighters destroyed or rendered\\ncombat ineffective\"))), mdx(\"p\", null, \"Measures sets can evolve as measures are added or deleted due to\\ninsights gained by the test team from test activities. The first measure\\nsets are developed relatively early in the continuum of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ninvolvement with system development. The test strategy should promote\\nregular updates, additions, and modifications to the measures sets\\nthroughout the test lifecycle. The next section discusses the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nprocess for measures development.\"), mdx(\"h1\", null, \"SECTION 2 MEASURES DEVELOPMENT\"), mdx(\"p\", null, \"This section discusses the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" process for developing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", MOPs, and\\nMOSs. From the perspective of the pyramid in figure 1, one can think of\\ndeveloping measures using a top-down or bottom-up approach. The top down\\napproach is most useful for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" development since it focuses on the\\nMission Effect, and the bottom up approach is effective when developing\\nMOPs and MOSs since it focuses on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"There are opportunities to bring stakeholders together through two\\nformal meetings, the Initial Test Design (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \") and the Measures Workshop\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \"), where measures are developed. These meetings are just one type of\\nvenue facilitated by the test team, A-2/9, and A\\u20113 to develop, refine,\\nand socialize measures. Major stakeholders in the acquisition program\\nare invited: the user community, the System Program Office (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \"), \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \",\\nsystem developers, and developmental testers. All participants apply\\ntheir subject matter expertise toward the goal of developing a measure\\nset and test designs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are developed at the Initial Test Design\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \") meeting, although they may be developed at a Measures Workshop\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \") if that occurs first. MOPs and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" are developed at a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \".\"), mdx(\"h2\", null, \"Developing \", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \"\"), mdx(\"p\", null, \"Developing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" using the top-down approach is typically done using a\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" document, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" Evaluation View (developed by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A3), mission\\ndocumentation and scenario development, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" inputs, empirical results\\nfrom test events, etc. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" describes the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" mission, how the\\nsystem will be employed, and what effects the user is trying to achieve.\\nThe Evaluation View (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \") describes the necessary conditions and\\nactivities that must be accomplished for the system to provide its\\ncapabilities, contribute to mission accomplishment, and ultimately\\nsupport national strategic objectives.\"), mdx(\"p\", null, \"Using an appropriate combination of the methods above, one can identify\\ndesired and undesired mission effects in the analysis of the system. For\\nexample, target damage from a bomb is a desired effect, while collateral\\ndamage is an undesired effect. It may be appropriate to also include an\\noperational context for the sake of scope or clarity.\"), mdx(\"p\", null, \"The definition of mission and mission effect are important in developing\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission\"), \": 1) The task, together with the purpose, that clearly\\nindicates the action to be taken and the reason therefore (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-0); 2)\\nIn common usage, especially when applied to lower military units, a duty\\nassigned to an individual or unit; a task (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-0); 3) The dispatching\\nof one or more aircraft to accomplish one particular task (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-0).\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission Effect\"), \": The result, outcome, or consequence of an action, at\\nits appropriate mission level, typically tactical, represents the\\nmission effect or outcome. Mission effects are considered within the\\ncontext of Concept of Operations / Operational Mode Summary / Mission\\nProfile/Employment (derived from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 1-02, Department of Defense\\nDictionary of Military and Associated Terms, As amended through 15 Feb\\n16). Mission effects may include desired and undesired effects.\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" may incorporate both the mission (action taken) and the effect;\\nfor some systems the effect and the action are one in the same.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" x.y: Recover personnel\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" x.y: Ingress area to reach pick-up point\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" x.y: Maintain aircraft to achieve required availability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" x.y: Defeat high value advisory targets\"))), mdx(\"p\", null, \"Once we have identified the actions and outcomes of interest for a\\nsystem it may be necessary to include additional components in order to\\ncommunicate metrics and evaluation criteria. These components will be\\nincluded within the measures worksheet but are not necessary to include\\nwithin measures summary tables.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"The components of an \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" may include the following (note some\\ncomponents are optional):\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The method of summarizing the observed sequence of successes and\\nfailures (e.g., proportion, rate, or probability)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A description of the mission effect (outcome) that will be defined\\nas a success; an optional standard of success can be explicitly\\nincluded\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"An optional operational context for the desired mission effect\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"An optional basis for evaluating the observed proportion of\\nsuccesses and failures\"))), mdx(\"p\", null, \"Figure 2 shows the basic structure of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \".\"), mdx(\"p\", null, \"Figure 2. Components of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \"\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"751px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/f1017db6f660a63c97b131a7227a0982/c483d/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\": \"85.71428571428571%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAARCAIAAABSJhvpAAAACXBIWXMAAAsTAAALEwEAmpwYAAADY0lEQVQ4y21TbUhTURg+2g8tKol+RCg1sKgffVFZFJEVqEWBZCYZEZXSh4V9EU2wli3yI6Ms0YygqEXltrZqms5tVtOZSUuzfbi0lptW5nS76253995zTudu6+NH73m5vJz3PPd5n/c9B2CMWRaWlYVWruRTUqBUyrMsIptI+AiGsBDRHF00VLS4b/FSx9KK7xUQQbIJSPbECRYANGECJg4ALijgSQLCf8AI57vzgRVMtk+eZJ8EeoFkRCKAnU4uOZk4XrQIL1yIZ83CM2bA/n4UwQsLYyttjbPFJToSs1xZmwc3J9gTZjpmeqAHdHQwiYkwNxfn5ODsbJyejmeLYEcHRzA8jzgkBC1jLcAGRA7RDvcOAp5un074nawTeDyhpCQ6NhZPm4anThXKnj8P+v1R2RHm76HhBNuU5c6UzMHMbFc2KWHJwBIe80QzvnePiokJEdkAwInxeG9h9yNde4jlvd5xr9dLM8Gy2tbM+iNx1ljQDUAPiP8Q3+RvEjSHu4pMJvrUqZ8nT9I9Ztj8uvv4ZVVn55vHxJTKF6+MZ2o13b1DJp/xaP8xsVP8jnoXaSQIa8O/DZF/EXe7Xc+fN+r1ep1O9+SJ+uuwO5r73X8e8ZFRCQZJbzjMER2cILLPbmtra7NYLGazWavVOhyOMAdLMEITYZQNhEeC/vJi7KVoc49VIZeHq1aqVKpPX1whhhFORm5MmC0KJph2ub1mf0t1frNZPXBZZigoV1gtHzQaTUNDg91u2yd9WKcw4q673pptVN12pqv+L7O2rley/nFFVsPFLc8kaxXlhY197m8IIpZlOSIGQWOv+9WlPeyVNYHarYHrG6mSBczLGgFM/QhI055W722pO9R644Dh6q7m0nQN7QlFrzcSJCHfICudE7yVyzw4zMj2BypWUxcWoJAfDFp+iFfIq/doZWKTrMhUmdMoTpEP28ZxBBh+AH6rwV8sCt7MCd7NYx4eCd7aSUlEnNcFfKM/JRsUNXl6mbi9vqTz2m5t6SZN0Mf9YSZBYMQ5VpzMnJ0buJYRqEqjxUm+qlQIWUFz64P359KU59PV0gy1dKOqUzkQpY3OQIhGm6qoC8sClal05Tpf+Sq6R/Vnzuit7uPt0/o7pw3vDZ/x/4xHaKxLPXrn4Nj9QrrPGEH9AtksAMPTtL1eAAAAAElFTkSuQmCC')\",\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/f1017db6f660a63c97b131a7227a0982/c483d/image8.png\",\n \"srcSet\": [\"/static/f1017db6f660a63c97b131a7227a0982/a2ead/image8.png 259w\", \"/static/f1017db6f660a63c97b131a7227a0982/6b9fd/image8.png 518w\", \"/static/f1017db6f660a63c97b131a7227a0982/c483d/image8.png 751w\"],\n \"sizes\": \"(max-width: 751px) 100vw, 751px\",\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, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 1: Desired Mission Effects.\"), \" Suppose the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" for a\\nsilo-based missile system stated the mission is to provide a safe,\\nsecure, responsive, on-time, and on-target nuclear deterrent force.\\nUsing a top-down approach to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" development, one \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" is required to\\nsupport an assessment that the system delivers a nuclear warhead to the\\nintended target. Another \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" is required to support an assessment that\\nthe system is responsive to launch commands. Other \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may be required,\\nbut two will suffice for this example.\"), mdx(\"p\", null, \"The following are possible \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", and the components of each measure are\\ncolor coded to be consistent with figure 2.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.1: Proportion of adversary high-value strategic targets\\ndefeated meets planning factor\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.2: Proportion of missiles that are launched in defensive\\nscenario meets \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Plan\"\n }, \"OPLAN\"), \" requirements\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 2: Undesired Mission Effects.\"), \" Tanker aircraft engage in a\\nvariety of missions, but the most common is air refueling of receiver\\naircraft. When receiver aircraft are properly refueled and consequently\\nin a return-to-mission status, a desired effect has been achieved. There\\nare circumstances, however, in which a tanker boom may cause damage to\\nreceiver aircraft during air refueling; and this damage may create a\\nrisk to mission accomplishment. The following \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" incorporates these\\nundesired effects into the measure.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" x.y: Proportion of boom-damaged, mission-compromised aircraft.\")), mdx(\"h2\", null, \"Developing MOPs and MOSs\"), mdx(\"p\", null, \"MOPs can be developed using a bottom-up or top-down approach. Using the\\nbottom-up approach, the test team reviews the available requirement\\ndocuments, identified standards, and acquisition documents (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Production Document\"\n }, \"CPD\"), \")\\nto determine what MOPs are required to evaluate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". These documents\\nmay also provide information about the expected level of reliability,\\navailability, maintainability, and other logistics aspects related to\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" employment and sustainment; these suitability issues are used to\\ndevelop MOSs. Using the top-down approach, the test team starts with the\\nMOPs and asks what performance characteristics are most relevant to\\nmission success.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"It is important for the test team to consider the following when\\ndeveloping measures:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What aspects of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance are important to enabling the\\noperation or mission?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What aspects of employment and sustainment are important to enabling\\nthe mission?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"How can the desired performance or aspect of suitability be\\nmeasured?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What is the best way to summarize performance (e.g., average,\\npercentile, etc.)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What degree of performance is required by the user?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Does the degree of performance required depend on certain\\nconditions?\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Common \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" attributes that MOPs typically measure (not all\\ninclusive):\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Accuracy\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Timeliness\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Completeness\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Workload\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Common \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" attributes that MOSs typically measure (not all\\ninclusive):\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Reliability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Availability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Maintainability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Usability\"))), mdx(\"p\", null, \"Systems may have other attributes that need to be evaluated such as\\nlethality, interoperability, trainability, etc. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \", and\\nthe requirements documents are used to determine the relevant system\\nattributes to evaluate with measures.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 3:\"), \" The Joint Biological Agent Decontamination System (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \")\\nis a capability designed to meet Air Mobility Command (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Mobility Command\"\n }, \"AMC\"), \") and United\\nStates Transportation Command (USTRANSCOM) needs for decontamination of\\naircraft against biological warfare agents (BWA) and other biological\\nagents of concern.\"), mdx(\"p\", null, \"MOPs need to be developed for the following \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \":\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"-2: Can \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \" be assembled and disassembled at deployed\\nlocations?\")), mdx(\"p\", null, \"There are 2 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \":\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1: Percentage of correctly assembled \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 2: Percentage of correctly disassembled \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \"\"))), mdx(\"p\", null, \"The user community at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" noted that the timeliness of\\nassembly/disassembly has operational impact. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" stated that the\\nassembly time should be less than 30 minutes. There was no requirement\\nfor disassembly. The user community noted that in the operational\\nenvironment, disassembly time was an important safety and security\\nissue. The following MOPs were created:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1: Assembly time\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2: Disassembly time\"))), mdx(\"p\", null, \"The user community also noted that it is important that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \" system\\nis reliable. The following \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" related to reliability was created:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" 1: Mean time to failure (MTTF)\")), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"-Operations-Measures-Data Hierarchy.\"), \" The resulting structure of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", MOSs and MOPs can be organized in several ways depending\\non the type of evaluation methods utilized. Figure 3 depicts some of\\npossibilities.\"), mdx(\"p\", null, \"Figure 3. Measure Hierarchies\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"578px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/00877f36d1251accb8ee1e7fe7d01628/508ef/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\": \"53.28185328185329%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAIAAADwazoUAAAACXBIWXMAAAsTAAALEwEAmpwYAAABKklEQVQoz5WSfWuDMBDG/f4faTA2+seKzEkbp1BE1w0aX5pq0kQTNdFdtZvQQrc+HOHJkd9dLsSqqopz3vf98COtNWNMKQUe0nMMs5lkRVHk+74xBvimaSAlpbRtO0mSEZ6LXstSo6ZN27bAUEr5KIxxShguJS5rWPOjwgV4Sev2DDejpk1d167rAgy+67TnofhzlzKpOiNUUynFpRRS1Upp08GlrDiOHccRQkyXBD4MQ4QQZGCWjzhaI5RmmApSHHNCccn3hGWEpZ1ure12GwTBb3Mw8ArATxko7b17X1lUVjmcvpx5uCmjDaH5euOgjXvg2cUT/gFrbZJ8t1g+va6Wpdif4OHfcG/6lODHxcPi5flwvKfzdI6KAoVvfrQq7u18LjKYU1x9mG/HOnq55lqlIAAAAABJRU5ErkJggg==')\",\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/00877f36d1251accb8ee1e7fe7d01628/508ef/image9.png\",\n \"srcSet\": [\"/static/00877f36d1251accb8ee1e7fe7d01628/a2ead/image9.png 259w\", \"/static/00877f36d1251accb8ee1e7fe7d01628/6b9fd/image9.png 518w\", \"/static/00877f36d1251accb8ee1e7fe7d01628/508ef/image9.png 578w\"],\n \"sizes\": \"(max-width: 578px) 100vw, 578px\",\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, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", MOPs, and MOSs are used synergistically to evaluate the\\neffectiveness and suitability of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" directly measure the degree\\nto which the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can achieve mission effects and successfully conduct\\noperations; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are the primary method of evaluating the question posed\\nby the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". Per the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Guidebook\"\n }, \"DAG\"), \", several MOPs and/or MOSs may be related to the\\nachievement of a particular mission effect. MOPs and MOSs are not\\nsubordinate to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", nor are they required to calculate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \".\\nHowever, MOPs and MOSs are an important part of determining the\\neffectiveness and suitability of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". MOPs and MOSs indicate specific\\nstrengths and weaknesses of a system, mitigate the statistical issues\\nassociated with the typically small sample size of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" data, and support\\nor refute the conclusions drawn from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" data. The next section\\ndiscusses the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" format for documenting the details of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", MOPs\\nand MOSs.\"), mdx(\"h1\", null, \"SECTION 3 MEASURE DOCUMENTATION\"), mdx(\"h2\", null, \"Measures Worksheet Overview\"), mdx(\"p\", null, \"The Measures Worksheet is a template used to document and organize the\\nfollowing details of a measure:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure:\"), \" A measure statement that describes what type of data is\\nbeing collected\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Metric(s):\"), \" The metric used to summarize the data (mean,\\npercentile, etc.)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Threshold (Optional):\"), \" The threshold of performance used to\\nevaluate the effectiveness of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Results:\"), \" The results attributed to observed and calculated data\\nprocured during test execution\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Rating (Optional):\"), \" The comparison of Results against the\\nThreshold, communicating any \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" shortfall\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Capability:\"), \" Attribute of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" being measured\\n(MOPs/MOSs only)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"References:\"), \" The source document that motivated the creation of\\nthe measure\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Scope:\"), \" The scope of the measure\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Methodology:\"), \" The test methodology used to generate the data\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Design:\"), \" The test design used to generate the data\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data and Analysis:\"), \" Data that may be required to compute the\\nmeasure, formulas required, and the intended method of analysis\"))), mdx(\"p\", null, \"Table 1 shows the measures worksheet template.\"), mdx(\"p\", null, \"Table 1. Measures Worksheet Template\"), mdx(\"table\", null, mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Operational Capability: State the OC (attribute)\"), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Measure\"), mdx(\"td\", null, \"Metric\"), mdx(\"td\", null, \"Threshold\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOE/P/S X.Y: State the Measure (In Title Case)\"), mdx(\"td\", null, \"State the specific metric\"), mdx(\"td\", null, \"Provide the value/units and any conditions/subsets specified\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"* KPP or Supports KPP (include as required)\"), mdx(\"p\", null, \"^ Identified Standard (include as required)\")), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", null, \"References:\"), \" Provide the requirement source (stated or derived). Specify the paragraph, section, line, etc.\"), mdx(\"p\", null, mdx(\"strong\", null, \"Scope:\"), \" Describe the measure and how it relates to the operation in terms of duration, procedures, start/end times, limitations, etc\\u2026 If the language in the measure or metric is not self-explanatory or is ambiguous, provide definition(s). For instance, define users, operators, successful or unsuccessful, and linkages to other measures. Concisely discuss operational relevance of the measure.\"), mdx(\"p\", null, mdx(\"strong\", null, \"Test Methodology:\"), \" Describe how the data used to support the measure is generated (modeling and simulation, open-air testing, analysis).\"), mdx(\"p\", null, mdx(\"strong\", null, \"Test Design:\"), \" Since tests are designed at the operation/COI level, this section will generally refer back to that level with the statement \\u201CUses the overarching operation/COI test design.\\u201D However, if unique factors and levels for this measure are identified in the Test Conditions section above, then a separate test design for the measure is required and should be summarized here.\"), mdx(\"p\", null, mdx(\"strong\", null, \"Data and Analysis:\"), \" Identify the minimum data required to compute the metric(s). Describe how the data will be collected, the sources of the data, and instrumentation required to collect the data. Provide an overview of the expected analysis method(s), equations, algorithms, and tools necessary for analysis.\"))))), mdx(\"h2\", null, \"Measures Worksheet Header\"), mdx(\"p\", null, \"The header of the measures worksheet contains a concise summary of the\\nmost important information regarding a measure. It states the attribute\\nof the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" the test team is interested in evaluating (operational\\ncapability), a short title (measure statement) describing what is being\\nmeasured that will convey information about the attribute, how it will\\nbe computed (the metric), and what will serve as the basis for judging\\nthe metric (the threshold). Table 2 is an example of the standard format\\nfor the measures worksheet header.\"), mdx(\"p\", null, \"Table 2. Standard Measures Worksheet Header\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226420 meters\")))), mdx(\"p\", null, \"The header can be expanded to accommodate more detailed requirements.\\nFor instance, a requirement may provide context, such as an operational\\ncondition, for a threshold of performance. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" convention is to\\ndenote these specific conditions with the \\u201C@\\u201D symbol trailing the\\nthreshold and preceding the condition. For example, if the miss distance\\nfor a particular munition is specified for a particular wind speed\\n(condition), the measure would be as shown in table 3.\"), mdx(\"p\", null, \"Table 3. Measures Worksheet Header with Conditions\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226420 meters @ 30 knots wind speed\")))), mdx(\"p\", null, \"Sometimes the threshold of the metric changes depending on which\\nsubcomponent or subset of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is being evaluated. In this case the\\nconvention is to add the word \\u201Cfor\\u201D after the threshold and specify the\\nrelevant subcomponent or subset. Consider the following requirements.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\u201CThe system shall send deliver priority 1 messages within 30\\nseconds\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\u201CThe system shall send deliver priority 2 messages within 5 minutes\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\u201CThe system shall send deliver priority 3 messages within 15\\nminutes\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\u201CThe system shall send deliver priority 4 messages within 1 hour\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\u201CThe system shall send deliver standard messages within 6 hours\\u201D\"))), mdx(\"p\", null, \"Table 4 shows these five requirements can be combined into one measure,\\nrather than five separate measures.\"), mdx(\"p\", null, \"Table 4. Measures Worksheet Header with Combined Conditions\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Time to Deliver Messages\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226430 seconds for Priority 1\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22645 minutes for Priority 2\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226415 minutes for Priority 3\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22641 hour for Priority 4\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22646 hours for Standard\")))), mdx(\"p\", null, \"This construct can be extended to create more complex measures that\\ninclude multiple metrics, thresholds, conditions, and subsets. Table 5\\nis an example of a multi metric/threshold measure.\"), mdx(\"p\", null, \"Table 5. Measures Worksheet Header with Multi Metric/Threshold\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Time to Deliver Messages\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"50th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22641 minute for Priority 1\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"80th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22648 minutes for all others\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22643 minutes @ Wartime for Priority 1\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"99th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226410 minutes for Priority 1\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226420 minutes for all others\")))), mdx(\"p\", null, \"Combining thresholds for different conditions and subsets of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" has\\nadvantages and disadvantages. One advantage is the reduction in\\ndocumentation. One disadvantage is that each measure is rated only once\\nin a report, even if it has multiple thresholds. Thus if there is a mix\\nof good and bad results within one measure, the good news, the bad news,\\nor both may be hidden behind the single summary rating.\"), mdx(\"p\", null, \"A measure is read aloud in a specific way to accurately convey its\\ncontents. The measure is read: \\u201CThe \", \"<\", \"metric\", \">\", \" of the\\n\", \"<\", \"measure\", \">\", \" is \", \"<\", \"threshold\", \">\", \".\\u201D For instance, the measure shown\\nin table 6 is read: \\u201CThe \", mdx(\"u\", null, \"mean\"), \" of the \", mdx(\"u\", null, \"miss distance\"), \" is\"), mdx(\"u\", null, \"less than or equal to 20 meters\"), \".\\u201D\", mdx(\"p\", null, \"Table 6. Reading a Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226420 meters\")))), mdx(\"h2\", null, \"Body of the Measures Worksheet\"), mdx(\"p\", null, \"The body of the measures worksheet contains five sections: References;\\nScope; Test Methodology; Test Design; Data and Analysis.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"References:\"), \" Provide the requirement source (stated or derived).\\nSpecify the paragraph, section, line, etc.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Scope:\"), \" Describe the measure and how it relates to the operation in\\nterms of duration, procedures, start/end times, limitations, etc. If the\\nlanguage in the measure or metric is not self-explanatory or is\\nambiguous, provide definitions. For instance, define users, operators,\\nsuccessful or unsuccessful, and linkages to other measures. Concisely\\ndiscuss operational relevance of the measure.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Methodology:\"), \" Describe how the data used to support the measure\\nis generated (modeling and simulation, open-air testing, analysis).\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Design:\"), \" Since tests are designed at the operation/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" level,\\nthis section will generally refer back to that level with the statement\\n\\u201CUses the overarching operation/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" test design.\\u201D However, if unique\\nfactors and levels for this measure are identified in the test\\nconditions section above, then a separate test design for the measure is\\nrequired and should be summarized here.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data and Analysis:\"), \" Identify the minimum data required to compute the\\nmetrics. Describe how the data will be collected, the sources of the\\ndata, and instrumentation required to collect the data. Provide an\\noverview of the expected analysis methods, equations, algorithms, and\\ntools necessary for analysis.\"), mdx(\"h2\", null, \"Formatting Measures\"), mdx(\"p\", null, \"The following are formatting conventions for the measures worksheet.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure Statement\"), \". Write measures statements in title case, i.e.,\\nuse capital letters for all principal words. Articles, conjunctions and\\nprepositions do not get capital letters unless they start the measure\\nstatement. All acronyms are spelled out in each measure, regardless if\\nthey have been used before in the document; this enables the measures\\nworksheet, and the header when separated from the full worksheet, to be\\ncomprehensible without other documentation. Table 7 shows a properly\\nformatted measure statement with acronyms.\"), mdx(\"p\", null, \"Table 7. Acronym Usage\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.4: Electro-Optical (\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Electro-Optical OR Executive Order OR Engineering Order\"\n }, \"EO\"), \") National Imagery Interpretation Rating Scale (NIIRS) Rating\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Minimum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u2265 NIIRS 6 @ 450 km\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Key Performance Parameter (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \")\"), \": If the measure is derived from a\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or supports a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \", the measure designator is preceded by an asterisk\\n(\", \"*\", \"). Additionally, a legend with the text \\u201C\", \"*\", \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or Supports \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \"\\u201D is\\nadded as another row at the bottom of the measure table, as shown in\\ntable 8.\"), mdx(\"p\", null, \"Table 8. Identifying a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \"\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Reliability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"*\", \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" 4.1: Time Between Failures\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226550 hours\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"*\", \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or Supports \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \"\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Identified Standards:\"), \" If a test team must develop a measure from a\\nrequirement that fails to provide a clear metric or threshold of\\nperformance, the test team can ask the user community for an appropriate\\nmetric or threshold; this value is known as an identified standard.\\nThere is a convention to highlighting and documenting identified\\nstandards on a measures worksheet. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" denotes an identified standard\\nby placing a carrot symbol (^) to the top left of the user-created\\nmetric or threshold. The source of the identified standard must be\\nexplained in the References section of the measures worksheet, which\\nshould start with the phrase \\u201CDerived from\\u2026\\u201D\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example:\"), \" The requirement states: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe miss distance shall be less\\nthan or equal to 15 meters.\\u201D\")), mdx(\"p\", null, \"While the measure statement (miss distance) and threshold (less than or\\nequal to 15 meters) are provided, the requirement does not explicitly\\nstate what the metric should be. The test team consults with the user\\nand determines the correct metric is circular error probable (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \").\\nSince this was not explicitly stated in the requirements document, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"\\nis an identified standard and must be annotated with a carrot symbol\\n(^\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"). Additionally a legend with the text \\u201C^ Identified Standard\\u201D is\\nadded as another row at the bottom of the measures worksheet header.\\nTable 9 shows how the additional information is incorporated.\"), mdx(\"p\", null, \"Table 9. Indicating an Identified Standard\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Operational Capability: Accuracy\"), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Measure\"), mdx(\"td\", null, \"Metric\"), mdx(\"td\", null, \"Threshold\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 2.1: Miss Distance\"), mdx(\"td\", null, \"^ CEP\"), mdx(\"td\", null, \"\\u2264 15 meters\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"* KPP or Supports KPP\", mdx(\"br\", null), \"^ Identified Standard\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"References:\"), \" Derived from weapon system subject matter expert (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \")\\njudgement based on operational experience on legacy systems and\\n\\u201CTechnical Requirements Document (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Requirements Document\"\n }, \"TRD\"), \"): Air Force (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \") Munition X 16 Dec\\n15, table 14, items 3.1.8 and 5.0.13-5.0.15\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Threshold:\"), \" If the measure is quantitative or ordinal, the threshold\\nmust be preceded by an equality or inequality mathematical symbol (=, \\u2264\\nor \\u2265).\"), mdx(\"h1\", null, \"APPENDIX A CATEGORIES OF MEASURES\"), mdx(\"p\", null, \"The primary goal of creating a well-written measure is to maximize the\\namount and quality of information obtained and to communicate the\\npurpose of a measure as effectively as possible. There are two different\\ncategories of measures used in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" testing: continuous, and discrete.\\nA number of measures from each category are typically included in a test\\nprogram. Together, these measures help form a basis for judgement about\\nthe system under test.\"), mdx(\"span\", {\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/ca059850c6d356ca47f16d936d93c9a1/e9140/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\": \"39.768339768339764%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAICAYAAAD5nd/tAAAACXBIWXMAABYlAAAWJQFJUiTwAAABkklEQVQoz22S7U/aUBTG+f+/78NMlm2JbsGhUXQ6Z6uUlzaW0RdIC9S2CkoWAoroF1ugP29LRJ17kif3nHuf+9yXc3IIJEmSMUOyII4eiaKIOI6Zz2fLeRZZnlGsJYs5/+5Nx9zKSGA4uqEd/sXoDNBaPWpWiGadU9GbqGYX1Q4oGz6608MVulT/jGefXLLM6ARXFE9NPhckvmxJbP3W0dpD8sc2G7LHpuIjGX3q3pj1XUVoZIolC+9ikBqsbppL/W4nU04bISXjgu97CgeVFrLusV9x+VSs87FQ4UO+xLfjJkdah/zPqtCVUaw+ihEynd6/PDkNJnepYYBi9tgrmeJkk33FYls2+HposbZdE1TJyw6Sfs7uSYPCkUbZvl4a3j+8/sMsxAuv+aW64lYOB1UX1R1y1h2xKTXFk7v8KAfIxhWNYCJMfXZOLA5rDv7l4E1x3hRlfDOhHQxouH1RkADNDtFbPuqfFrrtcdYMqZo+decSV+hG49v3RXnXNgKzOBKMMy5WbZMs52Zxtp7m/2ubJ8zRRpbI+S2LAAAAAElFTkSuQmCC')\",\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/ca059850c6d356ca47f16d936d93c9a1/e3189/image10.png\",\n \"srcSet\": [\"/static/ca059850c6d356ca47f16d936d93c9a1/a2ead/image10.png 259w\", \"/static/ca059850c6d356ca47f16d936d93c9a1/6b9fd/image10.png 518w\", \"/static/ca059850c6d356ca47f16d936d93c9a1/e3189/image10.png 1035w\", \"/static/ca059850c6d356ca47f16d936d93c9a1/e9140/image10.png 1226w\"],\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(\"h2\", null, \"Continuous Measures\"), mdx(\"p\", null, \"Quantitative measures with data collected objectively tend to be the\\nmost informative and easiest to substantiate because they enable broader\\nstatistical applications. This is because they often have the property\\nof being continuous, where the resulting measure and metric have an\\ninfinite number of possible values in a range. For example, suppose\\nthere is a requirement for the overall weight of the system under test\\nmust be between a specified range. The weight of the system is a\\ncontinuous measure because it can take on any value of weight, within\\nthe range zero to infinity.\"), mdx(\"p\", null, \"It is important to note that there are several advantages of having\\ncontinuous measures over discrete measures. Inferences can be made with\\nfewer continuous data points and valid analysis can be performed with\\nsmaller samples sizes. This smaller sample size typically translates\\ninto a shorter, less expensive test. When using discrete measures, a\\nmuch larger sample size (lengthier and costlier test) is required to\\nmake an equivalent inference. Additionally, continuous measures allow\\nfor more analysis options, which provide insight into the sources of\\nvariation.\"), mdx(\"p\", null, \"The remainder of this section expands on the common metrics associated\\nwith continuous measures and includes examples taken from previous\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test programs. This list of metrics is not meant to be exhaustive\\nbut intended to represent those that are commonly used in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntesting. If other metrics are warranted, consult with the Intelligence,\\nAnalyses and Assessments Directorate (A-2/9) to determine proper format\\nand usage.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mean.\"), \" A mean is a measure of the central tendency of a data set and\\nindicates, generally, where the data is clustered. In most cases, this\\nis the arithmetic mean, commonly known as the average. Using mean as a\\nmetric indicates a continuous, physical measure such as time, distance\\nor temperature. The measure is physical in the sense it can be measured\\nwith a stopwatch, ruler, thermometer or some other scaled instrument.\"), mdx(\"p\", null, \"Since the measure is physical and obtained by using a measuring device,\\nthe threshold must include the unit of measure (e.g. meters, degrees\\nFahrenheit, seconds, etc.). The three examples shown in tables A-1\\nthrough A-3 are mean measures with physical measures that are attainable\\nusing a measuring device. The metric in each case is \\u201Cmean\\u201D and the\\nthresholds all include an inequality (\\u2265 or \\u2264), followed by the threshold\\nand the unit of measure.\"), mdx(\"p\", null, \"Table A-1. Mean Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22645 meters\")))), mdx(\"p\", null, \"Table A-2. Mean Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Reliability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" 4.1: Time Between Failures\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226550 hours\")))), mdx(\"p\", null, \"Table A-3. Mean Measure 3\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Reliability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 4.1: Exhaust Temperature\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u2264395\", mdx(\"sup\", null, \"o\"), \" Fahrenheit\")))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Mean Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the threshold physical and continuous?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Keep in mind that the arithmetic mean can be sensitive to every value in the data set, including extremes. This effect is especially noticeable when the sample size is small.\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Percentile.\"), \" A percentile divides a ranked or ordered set of data\\ninto 100 equal groups. These groups can be specified (e.g., 95th, 90th,\\n50th, 1st Quartile) for comparison against the threshold. A percentile\\nindicates the value below which a given percentage of the population\\nfalls. A percentile is distinct from a percentage in that a percentile\\nexpresses a relational comparison to a population while a percentage\\ndescribes the relation of one part to the whole, expressed as a fraction\\nof 100. For instance, a student with a score of 80% on a 100 question\\ntest (80 out of 100 questions correct) may be in the 95th percentile if\\nthe student scored better than 95% of all the other students (a\\ncomparison).\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201C95% of messages must be sent\\nwithin 15 minutes\\u201D\"), \" This requirement is expressed as a percentile and\\nthe resulting measure is shown in table A-4. Since percentile measures\\nare continuous and obtained from a physical measure, the threshold must\\ninclude a unit of measure consistent with the measure itself.\"), mdx(\"p\", null, \"Table A-4. Percentile Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.4: Time to Send Message\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"95th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226415 minutes\")))), mdx(\"p\", null, \"When analyzing the results of a test in relation to a percentile\\nmeasure, it is important for the test team to carefully assess the data\\nto determine whether the percentile for the test results is appropriate\\nto make a determination about the population.\"), mdx(\"p\", null, \"In the example above, suppose the test team collects data and finds that\\n95% of the message send times are 17 minutes and below. The test team\\nhas options in determining the 95th percentile of the collected data.\\nThe easiest is to take the empirical data \\u201Cas is\\u201D and mark where the\\n95th percentile falls. The test team may also attempt to fit a\\ndistribution to the empirical data and, depending on the goodness of\\nfit, make a different determination of where the 95th percentile falls.\\nThese two methods will likely produce different results for the 95th\\npercentile and it is up to the test team\\u2019s judgment to determine the\\nmost appropriate analysis technique, taking into account the operational\\nsignificance of the result.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Percentile Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the threshold physical and continuous?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the metric include the percentile value (not just the word \\u201CPercentile\\u201D)\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a percentile applicable to the requirement or is there another metric more appropriate?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the team intend to report the percentile of the empirical data or of a fitted distribution?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sample size sufficient for a percentile to be meaningful?\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Minimum/Maximum.\"), \" Minimum/maximum measures set the threshold as a\\nhard limit for performance, where a single instance exceeding or falling\\nbelow the threshold indicates the measure\\u2019s criteria has not been met.\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe system must be able to\\naccommodate planning for a new mission within 16 hours\\u201D\"), \" A min/max\\nmeasure would take the form as outlined in table A-5, with the metric\\nset as \\u201CMaximum\\u201D and the threshold less than or equal to \\u201C16 hours\\u201D. A\\nsingle mission planning session that lasts more than 16 hours will\\nresult in the measure being rated as not met. Because min/max metrics\\nestablish a hard limit for performance, the test team should consider\\nthe operational significance prior to test, to determine if a min/max\\nmetric is warranted.\"), mdx(\"p\", null, \"Table A-5. Continuous Maximum Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.4: Time to Mission Plan\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226416 hours\")))), mdx(\"p\", null, \"Minimum/Maximum metrics can be applied to any continuous data type where\\na single event beyond the threshold is unacceptable (i.e. danger close\\nor collateral damage where the consequence is too severe to tolerate).\\nTable A-6 is a reasonable maximum metric, where if a single bomb is\\nfarther than 9 meters from the target the entire measure does not meet.\\nSince this measure is continuous, if there is a recorded event with a\\nmiss distance greater than 9 meters, the test team will have sufficient\\ndata to apply descriptive statistics techniques to characterize the\\noverall performance of all the events, the variability of those events,\\nand the comparative impact of the above-threshold event to state \\u201Cdoes\\nnot meet threshold.\\u201D\"), mdx(\"p\", null, \"Table A-6. Continuous Maximum Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22649 meters\")))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Continuous Minimum/Maximum Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265, \\u2264 or =?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sign appropriate for the metric (\\u201C\\u2264\\u201D for a Maximum, \\u201C\\u2265\\u201D for a Minimum, or an equals sign \\u201C=\\u201D in certain cases)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the metric spelled out completely (no \\u201CMin\\u201D or \\u201CMax\\u201D)?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a minimum/maximum metric operationally relevant?\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Error Probable.\"), \" There are multiple variations of the error probable\\nmetric including, but not limited to, circular, elliptical and\\nspherical. Each of these finds different levels of use in different\\ncommunities however, the most common is the circular error probable\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"). All of these principles apply to all variations of the error\\nprobable metric, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" is used here as an example.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" metric is used to measure the precision of a weapon system. It\\nis defined as the radius of a circle, centered at the mean, with the\\ncircle boundary expected to encompass some percentage (generally 50%,\\ndenoted \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \") of the population. As a probability distribution, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"\\ncan also describe a more inclusive boundary (such as 90%, denoted CE90),\\na threshold that should be made clear in the system requirements and in\\nthe resulting measure. If the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" is 20 meters for a particular\\nmunition, then we would expect 50% of them to land within 20 meters of\\nthe target.\"), mdx(\"p\", null, \"Since \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" corresponds to a physical measure, the threshold must include\\nthe units of measure. Additionally, the probability must be included in\\nthe metric. The example in table A-7 is for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" where 50% of the\\npopulation is expected to hit within 15 meters of the target.\"), mdx(\"p\", null, \"Table A-7. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.4: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226415 meters\")))), mdx(\"p\", null, \"While the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" is a widely used metric, there are underlying assumptions\\nabout the population that are often not met and the test team must\\ncarefully consider these when analyzing results. For instance, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"\\nis based on a circular bivariate normal distribution, but dropped\\nmunitions may not be normally distributed in this way. Consider an\\naircraft dropping a grouping of gravity bombs on a target from a single\\ndirection. As these bombs hit, they will likely tend to vary greater on\\nthe down range axis (the direction of travel) with a smaller\\nside-to-side variation on the axis perpendicular to the direction of\\ntravel. The result is a distribution where the circle is stretched along\\nthe range axis and contracted on the perpendicular axis, forming an\\nellipse instead. There are options for analysis in this case and the\\ntest team should contact the Intelligence, Analyses and Assessments\\nDirectorate (A-2/9) for assistance.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Error Probable Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the metric include the probability?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Are the underlying assumptions about the metric realistic for the operational scenario?\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Probability.\"), \" A probability is used to make a predictive inference\\nabout a population based on sample data. Probability measures can be\\ndiscrete or continuous, depending on the underlying measurements, and\\nwill have a threshold given as a decimal between 0 and 1. In test, there\\nare a variety of probabilities that are commonly used: Probability of\\noperational availability (A\", mdx(\"sub\", null, \"o\"), \"), Probability of materiel\\navailability (A\", mdx(\"sub\", null, \"m\"), \"), probability of kill (P\", mdx(\"sub\", null, \"k\"), \"),\\nProbability of Detect (P\", mdx(\"sub\", null, \"d\"), \"), etc. The predictive ability of a\\nprobability and its utility as a measure depend on many elements such as\\nthe size of the sample space, the number of factors and levels in a test\\ndesign that impact the measure, and the variability of the data.\"), mdx(\"p\", null, \"A probability measure has two formatting conditions. First, to clearly\\nexpress the probability as part of the measure statement, the phrase\\n\\u201CProbability of\\u201D is placed at the beginning of the measure statement.\\nSecond, since probability is the metric for the measure, the cells below\\nthe headers for \\u201CMetric\\u201D and \\u201CThreshold\\u201D are merged (while maintaining\\nthe header cells) and the threshold is entered with the appropriate\\ninequality (\\u2265, \\u2264) and a value between 0 and 1. The examples in tables\\nA-8 and A-9 are typical probability measures.\"), mdx(\"p\", null, \"Table A-8. Probability Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Availability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" 4.2: Probability of Operational Availability (A\", mdx(\"sub\", null, \"o\"), \")\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22650.90\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"Table A-9. Probability Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Lethality\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.5: Probability of Kill (PK)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22650.95\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Probability Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the threshold a value between 0 and 1?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the metric and threshold cells merged?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the measure name include the phrase \\u201CProbability of\\u201D?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the sample size sufficient to determine a probability with a reasonable confidence interval?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is a probability meaningful for the operational scenario?\"))))))), mdx(\"h2\", null, \"Discrete Measures\"), mdx(\"p\", null, \"Discrete measures are those where the measure and metric have a finite\\nnumber of possible values and can only take specific values in a range.\\nDiscrete measures are typically counted in whole numbers. For example,\\nsuppose a requirement states that the number of C-17s required to deploy\\nshall be two or less. This measure is discrete because the number of\\naircraft can only take on whole number values (i.e., you cannot have 2.5\\naircraft).\"), mdx(\"p\", null, \"Discrete measures with only two outcomes (e.g., yes/no,\\nsuccessful/unsuccessful, hit/miss) are sometimes referred to as \\u201Cbinary\\u201D\\nmeasures; however, discrete measures can have more than two bins as well\\n(e.g., easy/average/hard, high/medium/low).\"), mdx(\"p\", null, \"It is important to note that there are several advantages of having\\ncontinuous measures over discrete measures. Inferences can be made with\\nfewer continuous data points and valid analysis can be performed with\\nsmaller samples sizes. This smaller sample size typically translates\\ninto a shorter, less expensive test. When using discrete measures, a\\nmuch larger sample size (lengthier and costlier test) is required to\\nmake an equivalent inference. Additionally, continuous measures allow\\nfor more analysis options, which provide insight into the sources of\\nvariation.\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe system shall successfully hit\\nthe target 85% of the time. A successful hit is one where the munition\\nlands within 5 meters of the target center.\\u201D\"), \" We can construct two\\nmeasures from this requirement, one discrete and one continuous, shown\\nin tables A-10 and A-11, respectively.\"), mdx(\"p\", null, \"Table A-10. Discrete Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Weapon Releases that are on Target\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226585%\")))), mdx(\"p\", null, \"Table A-11. Continuous Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"85th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22645 meters\")))), mdx(\"p\", null, \"Both of these measures are valid for the requirement, but which one is\\nbetter? Assume we go to test and obtain the following results:\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Launch\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Miss Distance (Continuous)\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Weapon Release on Target? (Discrete)\"))), 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 }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), 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 }, \"0\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), 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 }, \"0\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), 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 }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"6\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"7\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"8\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"91\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Miss\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"9\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"10\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"11\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"12\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"13\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"14\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"0\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"15\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"16\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"135\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Miss\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"17\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"18\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"19\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"20\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")))), mdx(\"p\", null, \"If we look at the discrete data only and evaluate the measure, we see\\nthat 90% of the munitions were on target. This is greater than the\\nthreshold of 85% so the test team would rate this measure as having no\\nshortfalls as illustrated in table A-12.\"), mdx(\"p\", null, \"Table A-12. Evaluating the Discrete Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Results\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Weapon Releases that are on Target\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226585%\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"90%\")))), mdx(\"p\", null, \"If we use the continuous measure and analyze the miss distance, we see\\nthat the 85th percentile is 5 meters however, we also see that when the\\nsystem missed, it missed by 91 and 135 meters. By using a continuous\\nmeasure, this additional information about the variance is available to\\nthe test team allowing them to rate this measure more accurately,\\ndepending on the operational significance of the data.\"), mdx(\"p\", null, \"Table A-13. Evaluating the Continuous Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Results\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"85th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22645 meters\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5 meters\")))), mdx(\"p\", null, \"Therefore, as a general rule, if a measure is discrete, the test team\\nshould consider if there is any way to express the measure as\\ncontinuous. This will not be possible in all instances, but in some\\ncases the opportunity to create a continuous measure is obscured in an\\nimproperly or poorly written discrete measure or requirement.\"), mdx(\"p\", null, \"The remainder of this section expands on the common metrics associated\\nwith discrete measures and includes examples taken from previous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntest programs. This list of metrics is not meant to be exhaustive but\\nintended to represent those that have been commonly used in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntesting. If other metrics are warranted, consult with the Intelligence,\\nAnalyses and Assessments Directorate (A-2/9) to determine proper format\\nand usage.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Minimum/Maximum.\"), \" Minimum/Maximum measures can be either continuous\\nor discrete. Min/Max measures set the threshold as a hard limit for\\nperformance, where a single instance exceeding or falling below the\\nthreshold indicates the measure\\u2019s criteria has not been met.\"), mdx(\"p\", null, \"For discrete measures, the min/max metric can be problematic and the\\nanalysis of the results must consider the data as a whole. While the\\nsingle event that exceeds the threshold marks the measure as \\u201Cnot met,\\u201D\\nthe test team must consider the true operational impact of that\\nsingle-point failure.\"), mdx(\"p\", null, \"Discrete min/max measures are often the result of vague or poorly\\nwritten requirements with an unreasonably high expected level of success\\nnot typically seen in any system or process. In these cases, the test\\nteam should consult with the user to determine the validity of the\\nrequirement and highlight the consequences of single-point failures.\"), mdx(\"p\", null, \"For example, consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CMessage exchange will\\nnot interfere with other system components\\u201D\"), \" The test team may decide to\\ncount the number of interference events and set the threshold to zero.\\nThis results in the maximum measure shown in table A-14.\"), mdx(\"p\", null, \"Table A-14. Discrete Maximum Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Interoperability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.8: Number of Interface Exchange Requirements (\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Information Exchange Requirements\"\n }, \"IER\"), \") Not Met\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"= 0\")))), mdx(\"p\", null, \"A single instance of interference will result in the measure being rated\\nas \\u201Cnot met\", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201D\"), \" with the test team then having to make a determination of\\nwhether this is an operationally significant shortfall. While this is\\nthe assessment method as outlined in the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide\"), \", the test\\nteam should consider this question of \\u201Coperational significance\\u201D before\\nexecuting the test and, in conjunction with the user and SMEs, develop\\nan identified standard that defines what is actually required as a\\nthreshold. Although this may not result in a continuous measure, the\\ntest team will have defined operational significance before executing\\nthe test.\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CEleven active terminals will be\\navailable at each command station at all times\\u201D\"), \" In this case, the test\\nteam may decide to use a minimum metric, and construct the measure shown\\nin table A-15.\"), mdx(\"p\", null, \"Table A-15. Discrete Minimum Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accessibility\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.5: Number of Active Terminals in each Command Station\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Minimum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226511 Terminals\")))), mdx(\"p\", null, \"The question of operational significance comes into play here. Is it\\noperationally significant if one terminal is unavailable for 10 minutes\\nover a weeklong test? The test team should consult with the user and\\nSMEs to determine the answer to this question. If it is not\\noperationally significant, the team can coordinate with the user and\\nSMEs to determine a more operationally informative and meaningful\\nthreshold. A potential substitution for the above threshold is shown as\\nan identified standard in the measure shown in table A-16.\"), mdx(\"p\", null, \"Table A-16. More Operationally Meaningful Continuous Minimum Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accessibility\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.5: Time each Terminal is Active\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Minimum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ \\u226516 hours/day\")))), mdx(\"p\", null, \"In some cases the test team may want to create a measure that counts the\\nnumber of instances of an event. If the underlying population being\\ncounted cannot be reasonably known, or if the number of opportunities\\nthat may occur (and be counted) cannot be known, then a count measure\\nmay be in order. While it may seem natural to use \\u201CCount\\u201D as the metric,\\nin practice either \\u201CMinimum\\u201D or \\u201CMaximum\\u201D are used as the metric and the\\nphrase \\u201CNumber of\\u201D is placed as a lead in to the measure.\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CShall not induce runway\\nincursions\\u201D\"), \" In this case, the test team will have no way of knowing how\\nmany runway incursions there might be, so the best option is to simply\\ncount the number of runway incursions. The measure is shown in table\\nA-17. The metric is \\u201CMaximum\\u201D and the phrase \\u201CNumber of\\u201D leads the\\nmeasure. The Threshold (as implied in the requirement) is \\u201Czero.\\u201D\"), mdx(\"p\", null, \"Table A-17. Discrete Maximum Counting Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Vulnerability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.5: Number of Runway Incursions\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"=0\")))), mdx(\"p\", null, \"The reason for using \\u201CMaximum\\u201D or \\u201CMinimum\\u201D as the metric instead of\\n\\u201CCount\\u201D is so the boundary or limit is clearly identified in the\\nmeasure. \\u201CCount\\u201D by itself does not express to the reader the direction\\nof either a good or bad result.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Discrete Minimum/Maximum Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265, \\u2264 or =?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sign appropriate for the metric (\\u201C\\u2264\\u201D for a Maximum, \\u201C\\u2265\\u201D for a Minimum, or an equals sign \\u201C=\\u201D in certain cases)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the metric spelled out completely (no \\u201CMin\\u201D or \\u201CMax\\u201D)?\"))), mdx(\"p\", null, \"Planning for Analysis\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a minimum/maximum metric/threshold operationally relevant?\")), mdx(\"li\", null, mdx(\"p\", null, \"Can the measure be made continuous?\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Proportion.\"), \" A proportion is the relation of one part to the whole\\nwith respect to magnitude, quantity, or degree. For example, \\u201C2 out of\\n10 pie pieces have been eaten\\u201D is a proportion where the 2 eaten pieces\\nof pie are part of the 10 pieces of the whole pie. Proportions can be\\npresented in two ways to show the relationship between the part and the\\nwhole, in written form or as a fraction. For example, \\u201C3 out of 5 fuses\\ndetonated\\u201D is a proportion where 3 fuses detonated (the part) out of the\\n5 total fuses considered (the whole).\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In written form \\u2013 \\u201C3 out of 5 fuses detonated\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"As a fraction \\u2013 \\u201C3/5\\u201D\"))), mdx(\"p\", null, \"Similarly, the threshold must also be expressed as a proportion. In\\nwritten form, the preferred method of communicating the relationship\\nbetween the \\u201Cpart\\u201D and the \\u201Cwhole\\u201D is with the words \\u201Cout of\\u201D between\\nthem. For instance, in the fuse example, if the requirement is for 80%\\nof the fuses to detonate, then the threshold would be \\u201C\\u2265 4 out of 5\\u201D\\nAlternatively, this can be expressed using the mathematical symbol for\\ndivision\\u2014\\u201C\\u2265 4/5\\u201D\\u2014which in turn leads to a third expression if the\\ndivision is carried out of \\u201C\\u2265 0.8.\\u201D \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"However\"), \", this last notation\\nshould be avoided when reporting proportions, even if the requirement\\nthreshold is stated in decimal or percentage format, as a decimal or\\npercentage implies greater precision than might actually be available.\"), mdx(\"p\", null, \"Because a proportion is properly expressed by including both parts of\\nthe relationship represented, the grammar of the measure\\u2014both written\\nand spoken\\u2014is critical to ensure the correct information is\\ncommunicated.\"), mdx(\"p\", null, \"The general format for reading a proportion aloud is:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe proportion of the \", \"<\", \"denominator\", \">\", \" that are \", \"<\", \"numerator \", \">\", \"\\nis \", \"<\", \"threshold\", \">\", \"\\u201D\")), mdx(\"p\", null, \"Or, stated another way:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe proportion of the \", \"<\", \"the whole\", \">\", \" that are \", \"<\", \"the part \", \">\", \" is\\n\", \"<\", \"threshold\", \">\", \"\\u201D\")), mdx(\"p\", null, \"The following measure is read:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe proportion of the \", mdx(\"u\", null, \"Detected Targets\"), \" that are \", mdx(\"u\", null, \"Correctly\\nIdentified\"), \" is \", mdx(\"u\", null, \"9\"), \" out of \", mdx(\"u\", null, \"10\"), \"\\u201D\")), mdx(\"p\", null, \"Table A-18. Proportion Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Detected Targets that are Correctly Identified\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Proportion\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22659 out of 10\")))), mdx(\"p\", null, \"The measure statement must contain the \\u201Cwhole\\u201D followed by the \\u201Cpart\\u201D\\nwith the words \\u201Cthat are\\u201D between them to properly express the\\nrelationship.\"), mdx(\"p\", null, \"To emphasize why the grammar of a proportion measure is critical,\\nconsider the following other possibilities using the same requirement:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe system shall identify targets correctly 90% of the time.\\u201D\")), mdx(\"p\", null, \"Table A-19 shows the first improper measure where the requirement is\\ntaken quite literally. The measure \\u201CTargets Identified Correctly\\u201D does\\nnot convey what the \\u201Cpart\\u201D and \\u201Cwhole\\u201D are and how they are related. Is\\nthe \\u201Cwhole\\u201D all targets presented, whether detected or not? Only\\ndetected targets? Being able to answer these questions may require\\nconsultation with the user to clarify the requirement. Without answering\\nthese questions, the test team will not know what data to collect and\\nhow to evaluate the measure.\"), mdx(\"p\", null, \"Table A-19. Improper Proportion Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Targets Identified Correctly\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Proportion\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22659 out of 10\")))), mdx(\"p\", null, \"Table A-20 shows the second improper measure. While the measure now\\nexpresses a relationship, because of the addition of the words \\u201Cthat\\nare,\\u201D is the \\u201Cpart\\u201D and \\u201Cwhole\\u201D adequately conveyed as expressed in the\\noriginal requirement? In the taxonomy, \\u201CTargets\\u201D represents the \\u201Cwhole\\u201D\\nbut it is unclear which targets\\u2014all targets or only the targets the\\nsystem detected? Again, thoughtful consideration must be given to ensure\\nboth elements are clearly identified (as expressed in table A-21),\\nleaving no ambiguity for the reader of the report.\"), mdx(\"p\", null, \"Table A-20. Improper Proportion Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Targets that are Correctly Identified\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Proportion\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22659 out of 10\")))), mdx(\"p\", null, \"Table A-21. Correct Proportion Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Detected Targets that are Correctly Identified\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Proportion\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22659 out of 10\")))), mdx(\"p\", null, \"Why not use a percentage as stated in the requirement? \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Proportions\\nshould be used for small sample sizes\"), \" in lieu of a percentage. When\\nthe sample size is small, reporting a percentage may imply greater\\nprecision than actually exists; proportions paint a more accurate\\npicture of the data. For instance, going back to the fuse example,\\nstating \\u201C3 out of 5 fuses detonated\\u201D provides more insight than to say\\n\\u201C60% of the fuses detonated.\\u201D\"), mdx(\"p\", null, \"Consider the same requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe system shall identify targets\\ncorrectly 90% of the time.\\u201D\"), \" The percentage stated in the requirement\\nshould be expressed as a proportion (9 out of 10) if the test team\\nexpects the sample size of the test to be small (a common rule of thumb\\nis \", \"<\", \" \", \"~\", \"25 data points). If the test team expects the sample size to\\nbe large, then they should write the measure as a percentage (detailed\\nin the next section). Both measures in tables A-22 and A-23 are\\ntechnically correct for this requirement; however, the expected sample\\nsize will dictate which one to use.\"), mdx(\"p\", null, \"Table A-22. Proportion Measure for Small Sample Sizes\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Detected Targets that are Correctly Identified\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Proportion\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22659 out of 10\")))), mdx(\"p\", null, \"Table A-23. Equivalent Percentage Measure for Large Sample Sizes\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Detected Targets that are Correctly Identified\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226590%\")))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Proportion Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the measure clearly express a relationship between the \\u201Cwhole\\u201D and the \\u201Cpart\\u201D?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cwhole\\u201D listed first and the \\u201Cpart\\u201D listed second?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cthat are\\u201D used to convey the relationship?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are both parts of the relationship clearly and concisely expressed with no double meaning?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cout of\\u201D used to convey the relationship in the threshold?\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Alternatively a division symbol can be used (3/5)\"))))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Can the measure be made continuous?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the expected sample size support the decision to use a proportion metric?\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report proportion measure results in decimal form alone. If the requirement is given in a decimal or percentage, report the result as a proportion and annotate the decimal/percentage notation for comparison to the threshold of the requirement.\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report results in vague quantitative terms such as \\u201Ca majority of targets were correctly identified.\\u201D Always include the actual quantitative values.\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Percentage.\"), \" A percentage describes the relation of one part to the\\nwhole and is then expressed as a fraction of 100. Percentage should not\\nbe confused with percent, which strictly represents a part out of 100 as\\nthe name implies. For instance, if you have 40 apples, then 10% of the\\n40 apples is 4 apples. The 4 apples is the percentage of the 40 apples\\nrepresented by 10%. Since percent implies part of 100, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" convention\\nis not to use percent as a metric but to use percentage instead.\"), mdx(\"p\", null, \"A percentage is distinguished from a percentile in that while a\\npercentage describes a specific part/amount of the whole, a percentile\\ndescribes a relational comparison to a population. For instance, suppose\\na class of 100 students is given a test with 50 questions. If a student,\\nMary, gets 40 correct, then the percentage (the 40 correct answers) that\\nMary got correct is 80%. However, there is no information about how Mary\\ncompares to the rest of the class. If 90 of the 100 students got less\\nthan 80% of the questions correct, then Mary did better than 90% of the\\nwhole class and she is in the 90th percentile.\"), mdx(\"p\", null, \"A percentage is constructed in the same manner as a proportion and as\\nsuch, requires specific grammar. Because a percentage is properly\\nexpressed by including both parts of the relationship represented, the\\ngrammar of the percentage measure\\u2014both written and spoken\\u2014is critical to\\nensure the correct information is communicated.\"), mdx(\"p\", null, \"The general format for reading a percentage aloud is:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe percentage of the \", \"<\", \"the whole\", \">\", \" that are \", \"<\", \"the part \", \">\", \" is\\n\", \"<\", \"threshold\", \">\", \".\\u201D\")), mdx(\"p\", null, \"The measure must contain the \\u201Cwhole\\u201D followed by the \\u201Cpart\\u201D with the\\nwords \\u201Cthat are\\u201D between them to properly express the relationship.\\nSince a percentage is expressed as a fraction of 100, the threshold for\\na percentage measure will be specified by a percent.\"), mdx(\"p\", null, \"For example, consider the following system requirement:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe system shall execute \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Command and Control\"\n }, \"C2\"), \" commands successfully 95% of the time.\\u201D\")), mdx(\"p\", null, \"The whole is \\u201C\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command and Control\"\n }, \"C2\"), \" commands\\u201D and the part the team is interested in are\\nthose \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command and Control\"\n }, \"C2\"), \" commands that are \\u201Csuccessfully executed.\\u201D The words \\u201Cthat are\\u201D\\nare placed between the \\u201Cwhole\\u201D and the \\u201Cpart\\u201D as the measure and the\\nmetric is \\u201CPercentage\\u201D with a threshold of 95%. The complete example is\\nshown in table A-24.\"), mdx(\"p\", null, \"Table A-24. Percentage Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Payload Control\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 2.1:\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Command and Control\"\n }, \"C2\"), \" Commands that are Successfully Executed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226595%\")))), mdx(\"p\", null, \"In general, a percentage can just as easily be expressed as a\\nproportion, thus avoiding any confusion between percentage and percent.\\nThe percentage and proportion measures are very similar and the use of\\none or the other depends mainly on the sample size involved in the test.\\nIf the test team only has a small number of targets to input to the\\ntest, then the team should use a proportion measure to more accurately\\nreflect the scope of the measure. If the number of targets is larger,\\nthen a percentage may be in order.\"), mdx(\"p\", null, \"As with a proportion measure, it is important to avoid ambiguity in the\\npercentage measure. For instance, the following three examples, while\\nsimilar, are clearly measuring different outcomes. In the first example\\nin table A-25, it is unclear what is being measured; all commands that\\nare sent or only those that the system receives? The second and third\\nexamples in tables A-26 and A-27 are more defined and clearly measure\\ntwo different things.\"), mdx(\"p\", null, \"Table A-25. Ambiguous Percentage Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Payload Control\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.8: Commands that are Executed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226599%\")))), mdx(\"p\", null, \"Table A-26. Percentage Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Payload Control\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.8: Received Commands that are Executed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226599%\")))), mdx(\"p\", null, \"Table A-27. Percentage Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Payload Control\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.8: Sent Commands that are Executed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226599%\")))), mdx(\"p\", null, \"In some cases, what appears at first to be a percentage measure\\n(discrete) is likely a Percentile measure (continuous).\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe number of messages that are\\ndelivered within 5 minutes shall be greater than 95%\\u201D\"), \" A first attempt\\nto write a measure from this requirement may look like table A-28 or\\nA-29.\"), mdx(\"p\", null, \"Table A-28. Improper Percentage Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 2.6: Messages that are Delivered within 5 Minutes\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226595%\")))), mdx(\"p\", null, \"Table A-29. Improper Percentage Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 2.6: Messages that are Delivered\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226595% within 5 Minutes\")))), mdx(\"p\", null, \"In the first example, the time threshold has been appended to the\\nmeasure and in the second example, the time threshold is masquerading as\\na condition. In both examples, the measure is discrete. However, if the\\ntime threshold is isolated correctly, the metric is forced to change to\\na percentile, and the resulting measure as shown in table A-30 is\\ncontinuous and properly expresses the requirement.\"), mdx(\"p\", null, \"Table A-30. Correct Percentile Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.6: Time to Deliver Message\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"95th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22645 Minutes\")))), mdx(\"p\", null, \"In some cases, a poorly defined requirement can lead to a poorly written\\nmeasure. Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201C95% of the messages must\\nbe delivered successfully\\u201D\"), \" Again, the first attempt at writing a\\nmeasure may produce the following in table A-31.\"), mdx(\"p\", null, \"Table A-31. Ambiguous Percentage Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 2.6: Messages that are Successfully Delivered\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226595%\")))), mdx(\"p\", null, \"While this attempt seems reasonable for the information given, the\\nambiguity of \\u201Csuccessfully delivered\\u201D drives this discrete measure. As\\nthe test team develops this measure as written, the team naturally asks\\nwhat data is to be collected to answer this measure and it becomes clear\\nthe team must know what constitutes a successful message delivery (e.g.\\ntime, number of bits sent vs. received). This may require the test team\\nto develop an identified standard similar to the one shown in table A-30\\n(time threshold of within 5 minutes).\"), mdx(\"p\", null, \"One application of percentage measures is to estimate a probability.\\nOften times measures for reliability, availability, and maintainability\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability, Availability, and Maintainability\"\n }, \"RAM\"), \") metrics, such as operational availability. Are included in the\\ntest program. By definition, some of these metrics are probabilities\\n(i.e., operational availability: the probability that a system will be\\nready for operational use when required). While these are often stated\\nas probabilities in requirements documents, the execution period during\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E is rarely long enough to generate the amount of data required to\\nestimate a probability with a useful confidence interval. Due to this\\ncommon limitation, it is acceptable to use a percentage measure to\\nreport on the availability observed during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E period. Either way,\\nthe test team must report the sample size to give some context to the\\nresults (99% over 10 hours is much different than 95% over 500 hours).\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Percentage Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the measure clearly express a relationship between the \\u201Cwhole\\u201D and the \\u201Cpart\\u201D?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cwhole\\u201D listed first and the \\u201Cpart\\u201D listed second?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cthat are\\u201D used to convey the relationship?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are both parts of the relationship clearly and concisely expressed with no double meaning?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265 or \\u2264?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is there a continuous threshold hidden in the requirement that can used to convert the percentage measure into a continuous percentile measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Can a continuous identified standard be determined for the requirement?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the expected sample size support the decision to use a percentage metric?\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report results in vague quantitative terms such as \\u201Ca majority of targets were correctly identified\\u201D Always include the actual quantitative values.\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Ratings.\"), \" There are times when the test team will need to collect the\\nevaluation of a system directly from a user. Referred to as \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201Cuser\\nrating\\u201D\"), \" or \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201Cratings of\\u201D\"), \" measures, they are often used to provide data\\non the workload, usability, ergonomics, training, situational awareness\\nor some other attribute of the human interaction with the system under\\ntest. Ratings are used to provide insights into the system that cannot\\nbe determined through objectively collected, quantitative data alone.\\nThese types of measures should complement and support other objectively\\ncollectable, quantitative measures and not be used as a replacement.\"), mdx(\"p\", null, \"The format for rating measures has two unique elements, the measure\\ntitle and the evaluation criteria. First, the measure title is written\\nbeginning with the phrase \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201C\", \"<\", \"User\", \">\", \" Rating of\\u2026\\u201D\"), \" to clearly\\nidentify that the measure is based on the input of an individual or\\ngroup. The test team must clearly define who the user is and include\\nthis not only in the measure title, but also in the Scope section of the\\nmeasure worksheet. The format of the second part of the measure title\\nwill, in most cases, identify the attribute of the human system\\ninteraction the user is meant to rate. This attribute can be either an\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"internal\"), \" human quality or an \", mdx(\"em\", {\n parentName: \"p\"\n }, \"external\"), \" human aspect of the\\ninteraction with the system. Examples of internal human qualities are\\nsituational awareness or workload. Examples of external human aspects of\\nthe interaction with the system are readability, usability and\\naccessibility. If the attribute is for an external aspect, the measure\\nstatement should further identify what part of the system the human\\nattribute is connected with. The general format for the measure title\\ntakes one of the following formats, depending on the human attribute\\nbeing considered:\"), mdx(\"p\", null, \"\\u201C\", \"<\", \"User\", \">\", \" Rating of \", \"<\", \"internal attribute\", \">\", \"\\u201D\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"or\")), mdx(\"p\", null, \"\\u201C\", \"<\", \"User\", \">\", \" Rating of \", \"<\", \"external attribute\", \">\", \" of \", \"<\", \"part of\\nsystem\", \">\", \"\\u201D\"), mdx(\"p\", null, \"In some cases, the test team will be interested in the user rating of a\\nspecific topic area or process related to the system under test. For\\ninstance, the test team may want to evaluate the contractor provided\\ntraining, technical orders or the help desk associated with a particular\\nsoftware system. In this case, the measure will follow the following\\nformat:\"), mdx(\"p\", null, \"\\u201C\", \"<\", \"User\", \">\", \" Rating of \", \"<\", \"topic area/process\", \">\", \"\\u201D\"), mdx(\"p\", null, \"The second unique format element is how the metric and threshold are\\nidentified. Rating measures typically do not come directly from a system\\nrequirement so the test team will likely have to develop an identified\\nstandard for the evaluation criteria for the measure. This typically\\ntakes the form of a qualitative statement preceded by the carrot symbol\\n(^). Since there is no stated threshold, the cells below the headers for\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Metric\"), \" and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Threshold\"), \" are merged, while maintaining the header cells,\\nto accommodate the statement. Rating measures are evaluated in terms of\\nits effects, or if the operation or task was successfully accomplished.\\nIf feasible, the statement should be written to include the human\\nattribute that is being evaluated and the operation or task that is\\nachieved of facilitated. The general format for the evaluation criteria\\nis show below.\"), mdx(\"p\", null, \"\\u201C\", \"<\", \"Human system attribute\", \">\", \" \", \"<\", \"enables/facilitates\", \">\", \"\\n\", \"<\", \"operation/task accomplishment\", \">\", \"\\u201D\"), mdx(\"p\", null, \"Do not set arbitrary thresholds for rating measures (i.e. \", \">\", \"80% of\\nresponses must be positive). The test team should report their findings\\nwithout comparing to a numerical threshold. Figure A-1 demonstrates the\\ndifferent ways to construct a rating measure. The user groups,\\nattributes and topic areas/processes shown are examples and the lists\\nare not meant to be all inclusive. Test teams may come up with other\\nattributes, users, or topic areas/processes that are not shown.\\nSituational awareness is a special case of the internal attribute and\\ntherefore has its own format.\"), mdx(\"p\", null, \"Figure A-1. How to Construct a Rating Measure\"), mdx(\"span\", {\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/93d6e0e7234224240a45067b9ea22f05/081d5/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\": \"60.231660231660236%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAIAAADtbgqsAAAACXBIWXMAAAsTAAALEwEAmpwYAAABLUlEQVQoz42S126EQAxF+f/fQwIhmug1onfYzRFeERIlq/gBDfYttmeU5/c4jiOKItM0bdsOw3Capnv1cQt+leskMQwDnLIsl2WZ53kcx+ffofz4xyrPc8/zHMdBou/7exWtjzOqqlrXVQHKCcOu63DjC9P3/SzLmqYhjwRoYJSYSNM0XdeRbttWsSyrrmtU932fzoAJP01TCJCltG0bXwZBAgwHMgoaQDEhRSc0hjyKSCRJgjxkhHBTVZUSAJb6mtkwDHBFUTAeYggjR1IQOJOP4xgMNAwZjRZeZHojBZQUBRD4MOdwhiysOmM9gwa/nLknyIAgyzkIAprknl3XlXW8uyrZhPzLSmHSkWhdz+N3MgU6lDujBZwZm22xAgb51yO5nhqbl+XJI3tD/gR3/LGqyjKc4AAAAABJRU5ErkJggg==')\",\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/93d6e0e7234224240a45067b9ea22f05/e3189/image11.png\",\n \"srcSet\": [\"/static/93d6e0e7234224240a45067b9ea22f05/a2ead/image11.png 259w\", \"/static/93d6e0e7234224240a45067b9ea22f05/6b9fd/image11.png 518w\", \"/static/93d6e0e7234224240a45067b9ea22f05/e3189/image11.png 1035w\", \"/static/93d6e0e7234224240a45067b9ea22f05/081d5/image11.png 1264w\"],\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, \"For example, suppose an aircraft is undergoing an avionics suite upgrade\\nwith new processors, displays and controls. The test team wants to know\\nhow the aircrew\\u2019s situational awareness is impacted by the upgrade, but\\nhas no means to objectively collect quantitative data that adequately\\nmeasures the aircrew\\u2019s response to the changes. The test team can create\\na measure to collect the aircrew\\u2019s rating of how the changes to the\\navionics suite have impacted their ability to perform the mission. In\\ntable A-32, the measure follows the format discussed above for the\\ninternal human attribute of workload.\"), mdx(\"p\", null, \"Table A-32. Example of Internal Attribute Rating Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Usability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.4: Aircrew Rating of Workload\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Workload does not impair navigation\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"Additionally, the test team may want to know what the aircrew thinks of\\nthe new avionics suite multi-function display. Suppose the team is\\nspecifically interested in the impact of the crews ability to read the\\ndisplay in operational conditions. This measure could take the form in\\ntable A-33.\"), mdx(\"p\", null, \"Table A-33. Example of External Attribute Rating Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Usability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.5: Aircrew Rating of Legibility of the Multi-Function Display (MFD)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Legibility of MFD supports mission accomplishment\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"The data for ratings measures is typically collected using rating\\nscales, surveys, questionnaires, interviews, test team observations or\\nany combination of these. The methods used to create questionnaires and\\ncollect questionnaire data are extremely important for assuring the\\nusefulness of the data they produce. Test teams that plan to use these\\nmethods should consult the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Questionnaire Guide\"), \", available from\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint Library. In addition, test teams should work in\\nclose coordination with detachment human factors experts and A-2/9 to\\nensure the most effective use of questionnaires.\"), mdx(\"p\", null, \"Ratings measures are fraught with pitfalls and the test team must be\\ncautious when using them. There is a temptation to use a rating measure\\nas a \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201Ccatch-all\\u201D\"), \" to find problems or to \\u201C\", mdx(\"em\", {\n parentName: \"p\"\n }, \"cover all the bases\\u201D\"), \" not\\nexplicitly covered under another measure. Teams should only create\\nrating measures when there are attributes of the system that they\\ndetermined a need to evaluate and rate. Issues that arise during test\\nthat do not fit under a specific measure can be documented in the report\\nat the measure level as additional observations and at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" level as\\nnotable findings. There should rarely be a need to have a \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201Ccatch all\\u201D\"), \"\\nmeasure. There are also instances when teams may create a rating measure\\nfor something that can be answered by objectively collected quantitative\\ndata. Test teams should always strive to obtain objectively collected\\nquantitative data when feasible. Finally, there is the risk of writing a\\nrating measure so broadly that it becomes the overall rating of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\n(effectively removing the rating taxonomy for measures and COIs and\\nplacing it into a single measure). The following examples demonstrate\\nsome of the pitfalls that test teams must be aware of and consider when\\nwriting and utilizing rating measures.\"), mdx(\"p\", null, \"Table A-34. Example of Incorrect Rating Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.8:Operator Rating of Time Required to Input Coordinates\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Time required to input coordinates enables task accomplishment\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"The measure in table A-34 uses a rating to evaluate time, which can be\\ncollected objectively as quantitative data. Instead of the rating\\nmeasure, the test team should identify the appropriate metric (maximum,\\npercentile, etc.) for the measure and develop and identified standard\\nfor the time if no threshold is given in the requirements documentation.\\nTables A-35 and A-36 are two examples of measures that could be used in\\nplace of the incorrect measure shown in table A-34.\"), mdx(\"p\", null, \"Table A-35. Potential Replacement Measure for Figure 4-35\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.8: Time to Input Coordinates\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ \\u226470 seconds\")))), mdx(\"p\", null, \"Table A-36. Potential Replacement Measure for Figure 4-35\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.8: Time to Input Coordinates\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ 95th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ \\u226470 seconds\")))), mdx(\"p\", null, \"In table A-37, the measure is written at such a high level that it in\\nessence evaluates the system overall, bypassing the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" rating\\ntaxonomy where the test team rates all the measures and then the\\ncollective operational impact of those measure ratings at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" level.\\nWhile this is an extreme example, test teams must be wary of any measure\\nthat circumvents the intended rating taxonomy. If the measure speaks\\ndirectly to the overall system success, or to success at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" level,\\nit is likely that the measure is too broad.\"), mdx(\"p\", null, \"Table A-37. Example of Incorrect Rating Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.4:Aircrew Rating of Navigation System Upgrade\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Navigation system upgrade enables task accomplishment\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"Test teams also need to be cautious of creating rating measures that\\nsimply rollup other measures in the test program. Table A-38 is a set of\\nfour separate tables that show how the test team developed three\\nobjectively collectable quantitative measures to evaluate the timeliness\\nof a message delivery system. The fourth measure in the set is redundant\"), mdx(\"u\", null, \"and should be removed\"), \". MOPs 1.1\\u20131.2, MOE 1.3, and their outcomes form a sufficient basis for the evaluation of system timeliness with respect to message delivery. MOP 1.4 is not required and should not be included as a separate measure. Questionnaire data that would have been collected under MOP 1.4 can be included as data elements under any or all of the first three measures. In general, survey or questionnaire data can always be collected as a data element supporting an objective measure.\", mdx(\"p\", null, \"Table A-38. Set of Four Separate Measure Examples/Last Measure is\\nRedundant\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Sent Messages that are Correctly Received\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"90th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22642 minutes\")))), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.2: Message Drop Rate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ \\u22645 messages/hour\")))), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Messages that are Successfully Delivered\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226595%\")))), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.4:Terminal Operator Rating of Message Timeliness\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Message timeliness enables task accomplishment\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"These application errors in rating measures typically arise because of\\nthe test teams desire to catch all possible issues or problems that may\\noccur during test. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" measure model allows test teams to collect\\nand highlight issues without creating additional measures. For instance,\\nthe test team may add additional data elements to any measure to assist\\nin its rating and evaluation. For example, a survey or questionnaire may\\nbe added as a data element supporting an objectively collectable\\nquantitative measure. Further, the test report section for additional\\nobservations is designed to allow test teams to capture any items that\\nsurface during test that are not directly addressed by the measures.\"), mdx(\"p\", null, \"Evaluating rating measures is not a definitive process however, there\\nare some general principles that can be used. In addition to the main\\ndata source for a given rating measure, the test team in many cases will\\nalso record their observations of user\\u2019s reactions, comments or\\ninteractions. The test team should consider all of the data related to\\nthe measure and decide whether there is a convergence of responses\\n(positive or negative), which point to the measure as being met or not\\nmet.\"), mdx(\"p\", null, \"One special application of the ratings measure format is cyber measures.\\nAt the time of writing, cyber measures have typically taken the form of\\na rating, of either risk or capability level. While this has been the\\ncase historically, cyber measures do not have to be in the form of a\\nrating measure. It is up to the test team to determine the most\\nappropriate measure format in order to clearly convey the results of the\\noperational test. If the test team chooses to construct cyber measures\\nin the rating format, they should adhere to the generalized formats\\ndescribed in this section. Further discussion of cyber measures and\\nexamples can be found in Appendix C.\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Questionnaire Guide\"), \" provides a complete description of how\\nto analyze and report rating measures and should be consulted by the\\ntest team. In addition, the test team should contact A-2/9 with any\\nquestions or concerns on analyzing or reporting information.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Rating Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the measure written to evaluate some attribute of the human interaction with the system?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the correct format used for the specific attribute the measure is concerned with?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cuser\\u201D clearly defined in the measure title and/or Scope section of the worksheet?\")), mdx(\"li\", null, mdx(\"p\", null, \"The measure title should never start with \", mdx(\"em\", null, \"\\u201CTest Team Rating of\\u2026\\u201D\")), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Test team judgement is already accounted for in the AFOTEC rating taxonomy\")))), mdx(\"li\", null, mdx(\"p\", null, \"Are the Metric and Threshold cells merged, while maintaining the header cells?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the criteria statement formatted correctly?\")), mdx(\"li\", null, mdx(\"p\", null, \"Should the criteria statement be preceded with the identified standard symbol (^)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the measure follow one of the pitfalls described in the ratings measures Section?\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Measure should not be a \", mdx(\"em\", null, \"\\u201CCatch-all\\u201D\"), \" or used to \", mdx(\"em\", null, \"\\u201CCover all the bases\\u201D\"))), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not attempt to evaluate something that can be answered with objectively collected quantitative data\")), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not be so broad as to evaluate the entire system or COI\")), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not attempt to roll up other measures in the measure set\"))))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Are there any additional data elements that can be added to aid in the evaluation of the measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Plan to look for a convergence or harmony of responses when evaluating these types of measures.\"))))))), mdx(\"h2\", null, \"Composite Measures\"), mdx(\"p\", null, \"While a traditional measure evaluates a single attribute of a system, a\\ncomposite measure is a single evaluation of multiple attributes of a\\nsystem. In industry, these types of measures are called indexes,\\nratings, compound or complex measures. Some well-known examples include\\nthe Consumer Price Index, the Gross Happiness Index and the common\\nCredit Score. All of these measures take into account multiple\\nattributes and aggregate them into one score. The benefits of these\\ntypes of measures include:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A method to communicate a complex concept \\u2013 Composite measures allow\\nfor a single score or rating to be used to communicate the results\\nof complex relationships between multiple attributes of a system. It\\nis often easier to understand and interpret a single capability\\nrating rather than the individual ratings of multiple attributes\\nthat influence the capability.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A way to balance contributing factors \\u2013 Composite measures allow for\\nthe aggregation of multiple attributes. This combination reduces the\\npotential bias from highly variable attributes.\"))), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" defines a composite measure as: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"A measure describing a system\\ncapability that is influenced by multiple attributes whose results are\\naggregated into a single score or evaluation.\")), mdx(\"p\", null, \"This definition does not preclude the individual attributes from being\\nexamined separately and in relation to each other.\"), mdx(\"p\", null, \"An example of a composite measure is the US News Ranking of Best\\nColleges. This ranking scores the relative quality of college\\ninstitutions based on widely accepted indicators of excellence, shown in\\ntable A-39.\"), mdx(\"p\", null, \"Table A-39. US News Ranking of Best Colleges (Composite Measure Example)\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"span\", {\n parentName: \"th\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"176px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/d16f8a9984ee6f264c7746c87c873614/06437/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\": \"93.18181818181817%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAATCAIAAAAf7rriAAAACXBIWXMAAAsTAAALEwEAmpwYAAACt0lEQVQ4y6WUXVMSURjH92v0Gbrpou/QTBdNN13ZjKaTpc6Yk2MzQioqZdiYkChC61soILoLohIioK4KQbxsLgLx4mKwoBQy2CiMsmtnccYxQ6vpf3H2nN3n97yceZ6FTv5D0PkDwzA0TTNX6lL4j7rAQ2dvwUpRFIat2O0fNzZwm80GNuFwCMc9fr/P59v0egmKitOFQml400vU1tU2NDx53sJtbHwqFPZyOM2vuwUvX/Db2lo5XI5KpTwzvghHo2RHBw9g3d2CltYWs2lxdlb3pqdHrZ5cWV6aUquTycTx8XHpyORWhMvlvOrqauY089p5SqWCz++Eh+Dh4eFVDJPJZMDm6OioNBwlSZFIODg4ADClQqHValAUGRkdAeSSxTKNILup1KUXRhAEwBAUGR+XoyjqdDkXjEadTqfRanVzc9jamgfHGda4FLwT355FJz/oNPNaZAaZXF82rViMVmzJMKczL+gd1lWX3Xrxwgo0e5jHqUrpasVbQ1W/qQ5erhQvlgkN5WJTzdDao3dYlcTyQGx8KMWeqTyJzOFpdKhA0+AhW/BAd8S3BNiNDnMT6ns88fkB7GzXh+rV3iZks2LMXTbkAvtquQe6N3a9Qf4te3AKsz70eBS621/TuyhV2wZUNtmUbVTjgKftDscXtd4tn/mktxAihRVb918rH7vJmS4mfwLRxcgms5N3u3KLx6enkB8j8tz7iQw8Soqk8T5ZrE+6LZJsCyVg3ZHAhvvVnfWC3EGuWHOxfIaKH7hd2UwGeCLjVJCMBiIRb8C/4fcTgYDHS7i9RGArEk3tpkMhhiDoXO6XwQAuQPfkDw/3vqcTFBWLxUgSdA2rYDAYCYfjX2N76XTh995mKwD5F0cSfM7n89lsFrREIplMpVL7+/u5fJ6d1nOWV40kqIZNpMj81c/gX/UT/mLOxcXx+fAAAAAASUVORK5CYII=')\",\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/d16f8a9984ee6f264c7746c87c873614/06437/image12.png\",\n \"srcSet\": [\"/static/d16f8a9984ee6f264c7746c87c873614/06437/image12.png 176w\"],\n \"sizes\": \"(max-width: 176px) 100vw, 176px\",\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(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Attributes\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Graduation and Retention Rates\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Student Selectivity\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Undergraduate Academic Reputation\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Alumni Giving Rate\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Faculty Resources\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Graduation Rate Performance\")))), mdx(\"p\", null, \"Data is collected, directly from the universities, for each attribute. A\\nscore for each attribute is obtained and then a standard method is\\nemployed to aggregate the scores of all of the attributes. This yields a\\nsingle composite score for the university. This method allows readers to\\nget a sense of the relative quality of any institution.\"), mdx(\"p\", null, \"Within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", these type of measures are identified by the leading\\nverbiage \\u201CComposite Rating of\\u2026\\u201D and are used to evaluate and report on\\nsystem capabilities that are influenced by multiple attributes, but do\\nnot rise to the level of a critical operational issue (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \").\"), mdx(\"p\", null, \"Composite measures may be composed of any number of qualitative,\\nquantitative, continuous and/or discrete measurements. The\\ndistinguishing factor between a composite and traditional measure is\\nthat the measurements contained within the composite measure are looking\\nat multiple, different attributes of the system. It is critical that all\\nattribute measurements contributing to a composite measure are well\\ndefined. Additionally, the test team\\u2019s evaluation and aggregation\\nstrategy should be thoroughly documented in the measure worksheet and be\\ncredible and supportable.\"), mdx(\"p\", null, \"An example composite measure is shown in table A-40. This measure is\\nused to rate the air refueling of receiver aircraft by evaluating the\\nconfiguration, functionality, precision and effectiveness of several\\nsubsystems required to complete the air refueling task. Additionally,\\nthe measure considers the fatigue and workload of the operators while\\ncompleting the air refueling task. All of these attributes are\\nconsidered together when evaluating the measure.\"), mdx(\"p\", null, \"Table A-40. Composite Measure Example\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"(CUI)\"), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operational Capability: Refueling Flexibility\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Measure\"), mdx(\"td\", null, \"Metric\"), mdx(\"td\", null, \"Threshold\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 1.18: Composite Rating of KC-46A Air Refueling of Receiver Aircraft\"), mdx(\"td\", null, \"^ KC-46A AROS controls, displays and support systems enable air refueling of receiver aircraft with limited negative operational impacts\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*KPP or Supports KPP\", mdx(\"br\", null), \"^ Identified Standard\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Reference\"), \": Derived from \\u201CCapability Production Document for KC 135\\nReplacement Aircraft (KC X), Ver 4.4,\\u201D 19 Mar 15, para 6.2.2.1 and\\n6.2.3.1.435\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Scope\"), \": This measure evaluates air refueling from the air refueling\\noperator (ARO) perspective. The ARO employs the controls, displays, 3D\\nglasses, and support systems of the KC-46A air refueling operator\\nstation (AROS) to accomplish air refueling with receiver aircraft via a\\ncenterline boom, centerline drogue system (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cross Domain Solution\"\n }, \"CDS\"), \"), and wing air refueling\\npods (WARP). There is a significant design/functionality change in the\\nKC-46A vs. the KC-135 and KC-10, where the boom operator\\u2019s crew station\\nhas been moved to the front of the aircraft; and there is no longer a\\n\\u201Cdirect line of sight\\u201D through clear glass to the receiver aircraft and\\ncenterline boom during air refueling operations.\"), mdx(\"p\", null, \"Key measurement targets include:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Configuration and functionality of the AROS controls (e.g., fuel\\nmanagement system and scene selections),\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Camera-produced \\u201Cfield of view\\u201D and \\u201Cdepth of field\\u201D cues that are\\nprojected on the AROS visual/motion displays in day/night/low-light\\nmodes\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Precision control/stability of the centerline boom\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"ARO communication/coordination with receiver aircraft and KC-46A\\nflight crew\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Air refueling readout displays at the AROS\"))), mdx(\"p\", null, \"A secondary measurement target includes an ARO rating of subjective\\nfatigue/workload, principal drivers of workload, and operational\\nimpacts. Of special interest are any ARO reports of physical and/or\\nphysiological symptoms (e.g., eye strain, dizziness, headaches, and\\nnausea) that are due to the effects of using 3D glasses with the\\nvisual/motion display while in a fixed-position seat at the AROS, and\\nfacing the rear of the aircraft with forward aircraft motion. Finally,\\nidentification of any significant negative ARO operational transfer\\neffects from KC-135/KC-10 aircraft to the KC-46A.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Methodology\"), \": KC 46A aircrews will execute air refueling with a\\nplanned set of fighter, bomber, airlift, and reconnaissance receiver\\naircraft during planned test events, which occur during day, night, and\\ntransitional-light operations.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Design\"), \": Uses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1 Operations 1, 2, and 3 test design.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data and Analysis\"), \": Multiple data sets include ARO and test team\\nrecorded observations from data sheets, ARO evidence-based effectiveness\\nratings, ARO subjective fatigue/workload ratings, post-test interview\\ndata from AROs and onboard test team observers, and storable and\\nretrievable camera/video images and audio.\"), mdx(\"p\", null, \"Standardized observational data collection forms will include the\\nmeasurement targets specified in the Scope section. Prior to test\\nevents, approximately 10 AROs with experience representative of the\\noperational force will be briefed on the observational, workload, and\\nother measurement targets. They will conduct repeated observations\\nduring test events relative to the measurement targets. The onboard test\\nteam observer will sit in the instructor seat of the AROS and observe\\nreceiver refueling executed by the ARO. Crew Status Surveys will be\\nadministered to record subjective fatigue/workload ratings. If possible,\\nobservational data collection forms and workload ratings will be\\ncompleted in-flight at the conclusion of each air refueling test event;\\notherwise, they will be completed immediately after test events. ARO\\neffectiveness ratings of air refueling of receiver aircraft will be\\nformulated on the basis of the recorded observational evidence from test\\nevents (i.e., evidence-based ratings). The test team will conduct\\ndetailed, issues-based interviews and open-ended feedback sessions with\\nAROs and onboard observers in order to verify/clarify recorded data and\\ncollect additional information, including possible\\nphysical/physiological effects data. The test team will select relevant\\nstored video and audio data to support data analysis and resolution of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \".\"), mdx(\"p\", null, \"The test team will analyze data sets separately and relative to each\\nother to determine the extent of their convergence. The distributions of\\nARO evidence-based ratings and ARO workload ratings will be presented in\\nseparate tables. The range of scores, the modes of the distributions,\\nand other relevant distributional characteristics will be reported and\\ndiscussed in the text (e.g., outliers, distribution shape, etc.). A\\ncontent analysis of observational data will be performed, and the\\noutcomes will be discussed in a comprehensive, balanced (i.e., positive\\nand problematic findings), and factual narrative. Observational data\\nwill be analyzed across AROs, which is an index of replication and\\nverification of results. Cross-verification of observational outcomes\\nreported by AROs and onboard observers will be analyzed and discussed\\n(i.e., inter-observer agreement). Interview data will be analyzed, and\\nrelevant findings will be extracted and interwoven in the discussion.\\nThe identified standard will be met if ARO observations, onboard test\\nteam observations, reported operational impacts, ARO evidence-based\\nratings, ARO workload ratings, selected video and audio data, and\\ninterview data converge in the same, positive direction (i.e.,\\ntriangulation of data sets). If strict convergence is not met, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \"\\nwill be resolved according to the preponderance of the total evidence.\"), mdx(\"h1\", null, \"APPENDIX B MEASURE REVIEW QUICK REFERENCE\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Mean Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Keep in mind that the arithmetic mean can be sensitive to every value in the data set, including extremes. This effect is especially noticeable when the sample size is small.\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Error Probable Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the metric include the probability?\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Are the underlying assumptions about the metric realistic for the operational scenario?\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Percentile Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the metric include the percentile value (not just the word \\u201CPercentile\\u201D)\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a percentile applicable to the requirement or is there another metric more appropriate?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the team intend to report the percentile of the empirical data or of a fitted distribution?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sample size sufficient for a percentile to be meaningful?\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Probability Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the threshold a value between 0 and 1?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the metric and threshold cells merged?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the measure name include the phrase \\u201CProbability of\\u201D?\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the sample size sufficient to determine a probability with a reasonable confidence interval?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is a probability meaningful for the operational scenario?\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Continuous Minimum/Maximum Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265, \\u2264 or =?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sign appropriate for the metric (\\u201C\\u2264\\u201D for a Maximum, \\u201C\\u2265\\u201D for a Minimum, or an equals sign \\u201C=\\u201D in certain cases)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the metric spelled out completely (no \\u201CMin\\u201D or \\u201CMax\\u201D)?\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a minimum/maximum metric operationally relevant?\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Discrete Minimum/Maximum Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265, \\u2264 or =?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sign appropriate for the metric (\\u201C\\u2264\\u201D for a Maximum, \\u201C\\u2265\\u201D for a Minimum, or an equals sign \\u201C=\\u201D in certain cases)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the metric spelled out completely (no \\u201CMin\\u201D or \\u201CMax\\u201D)?\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a minimum/maximum metric/threshold operationally relevant?\")), mdx(\"li\", null, mdx(\"p\", null, \"Can the measure be made continuous?\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Proportion Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the measure clearly express a relationship between the \\u201Cwhole\\u201D and the \\u201Cpart\\u201D?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cwhole\\u201D listed first and the \\u201Cpart\\u201D listed second?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cthat are\\u201D used to convey the relationship?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are both parts of the relationship clearly and concisely expressed with no double meaning?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cout of\\u201D used to convey the relationship in the threshold?\"))), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Alternatively a division symbol can be used (3/5)\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Can the measure be made continuous?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the expected sample size support the decision to use a proportion metric?\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report proportion measure results in decimal form alone. If the requirement is given in a decimal or percentage, report the result as a proportion and annotate the decimal/percentage notation for comparison to the threshold of the requirement.\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report results in vague quantitative terms such as \\u201Ca majority of targets were correctly identified.\\u201D Always include the actual quantitative values.\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Percentage Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the measure clearly express a relationship between the \\u201Cwhole\\u201D and the \\u201Cpart\\u201D?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cwhole\\u201D listed first and the \\u201Cpart\\u201D listed second?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cthat are\\u201D used to convey the relationship?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are both parts of the relationship clearly and concisely expressed with no double meaning?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265 or \\u2264?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is there a continuous threshold hidden in the requirement that can used to convert the Percentage measure into a continuous Percentile measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Can a continuous identified standard be determined for the requirement?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the expected sample size support the decision to use a percentage metric?\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report results in vague quantitative terms such as \\u201Ca majority of targets were correctly identified.\\u201D Always include the actual quantitative values.\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Rating Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the measure written to evaluate some attribute of the human interaction with the system?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the correct format used for the specific attribute the measure is concerned with?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cuser\\u201D clearly defined in the measure title and/or Scope section of the worksheet?\")), mdx(\"li\", null, mdx(\"p\", null, \"The measure title should never start with \", mdx(\"em\", null, \"\\u201CTest Team Rating of\\u2026\\u201D\")))), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Test team judgement is already accounted for in the AFOTEC rating taxonomy\"))), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Are the Metric and Threshold cells merged, while maintaining the header cells?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the criteria statement formatted correctly?\")), mdx(\"li\", null, mdx(\"p\", null, \"Should the criteria statement be preceded with the identified standard symbol (^)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the measure follow one of the pitfalls described in the Ratings measures Section?\"))), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Measure should not be a \", mdx(\"em\", null, \"\\u201CCatch-all\\u201D\"), \" or used to \", mdx(\"em\", null, \"\\u201CCover all the bases\\u201D\"))), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not attempt to evaluate something that can be answered with objectively collected quantitative data\")), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not be so broad as to evaluate the entire system or COI\")), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not attempt to roll up other measures in the measure set\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Are there any additional data elements that can be added to aid in the evaluation of the measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Plan to look for a convergence or harmony of responses when evaluating these types of measures.\"))))))), mdx(\"h1\", null, \"APPENDIX C CYBER-RELATED MEASURES\"), mdx(\"p\", null, \"[1]\"), mdx(\"p\", null, \"Cybersecurity \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" is used to describe the activities that encompass all\\ncybersecurity test and evaluation activities, including vulnerability\\nassessments, security controls testing, penetration testing, adversarial\\ntesting, and cybersecurity testing related to a system\\u2019s operational\\nresilience and system cyber survivability capabilities within a mission\\ncontext.\", \"[2]\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" considers cyber survivability, resiliency and security critical\\nmission enabling capabilities of a system under test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"). So the\\nexpectation is that these capabilities will be fully integrated and\\ncomprehensively tested components of every test program. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9,\\nA-3I, and Detachment analysts will ensure that cyber-related measures\\nare developed for each program as necessary.\"), mdx(\"p\", null, \"Usage note: the focus of this appendix is on how to write a\\ncyber-related measure\\u2014refer to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Cyber Test Guide (CTG) for how\\nto rate and score cyber-related measures using operationally relevant\\ndata.\"), mdx(\"h2\", null, \"Measures Overview\"), mdx(\"p\", null, \"Test measures are the basis of the evaluation of a system under test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"). They drive the data needs, collection, and analysis used to\\nevaluate effectiveness and suitability and serve as evidence of\\ncapability performance and mission effects. There are three general\\ntypes of measures developed for Operational Test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"):\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures of Effectiveness (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \") -\"), \" Measures designed to assess\\nthe degree to which the system under test can accomplish mission\\nobjectives and achieve desired mission effects.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures of Performance (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \")\"), \" - Measure a system\\u2019s capabilities.\\nThey may quantify performance such as speed, payload, range,\\ntime-on-station, frequency, rating, or other distinctly observable\\nand/or quantifiable performance features. They may also document\\nwhether or not a system can successfully complete a task.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures of Suitability (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \")\"), \" - Measure of the ability to\\nsupport the system under test in its intended operational\\nenvironment. MOSs typically relate to readiness, supportability,\\nlogistics infrastructure and cost of ownership of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"))), mdx(\"h2\", null, \"Composite Measures\"), mdx(\"p\", null, \"Composite measures aggregate and summarize data from multiple\\nattributes. The multidimensional nature and complexity of cyber-related\\ntesting make adoption of composite measures very beneficial. A composite\\nmeasure facilitates evaluation of multiple attributes of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" by\\nconsolidating results into a single score.\"), mdx(\"p\", null, \"To prevent deceptively obtuse and irrelevant results, it is critical\\nthat all attribute measurements contributing to a composite measure be\\nwell defined. Additionally, the test team\\u2019s evaluation and aggregation\\nstrategy should be thoroughly documented in each of the composite\\nmeasure worksheets and be credible and supportable.\"), mdx(\"p\", null, \"Clarity, transparency, and accountability are required from all\\nstakeholders in composite cyber-related measures development and\\ndocumentation, as evidenced in the associated measures worksheets, to\\nbetter reduce distinct quality measures into a single summary indicator.\"), mdx(\"p\", null, \"See the main body of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Measures Guide for a complete\\ndescription and guidance on Composite Measures. See \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"-4 Stand Alone\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Construct \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" Example where they are used to aggregate effects of\\noperating within a cyber-contested environment for COIs 1, 2 and 3.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Cyber-Related Measures\"), \". Capabilities and functions of a system are\\nevaluated using both MOPs and MOSs. When developing cyber-related\\nmeasures for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", it is useful to visualize the system as having four\\nlayers that may require measurement and assessment: Mission Effects,\\nSystem Capabilities, System Functions and Properties, and System\\nStructure. Figure C-1 depicts these four levels in a pyramid and how\\nthey could relate to cyber-related measures.\"), mdx(\"p\", null, \"Figure C-1. The Pyramid\\u2014Evaluation Levels of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1026px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/f6c992d4a47d7bfd84862de0027c7346/eb3fa/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\": \"62.54826254826254%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAAA7DAAAOwwHHb6hkAAACkUlEQVQ4y5VTS0sbURjNP5K2ghvxNygiiGu3KoKiKyFLUTS7gA+QLty0YtFVsYLR+KqakIdJjIlJzCSZTMfJvB95nX73Rlu66MILZ+6938w9c853ZnygodstlEQLRdGBpHXQ6XRZGd1u993wea0uwikHO9+i+HL0iHCmi7riwLBcvHdwwg5dbh9tfD2TcXilIF6wUagqqNQVKC8G2u02XLcFx2lyeF5vresOLMt7hctrbPheueF4bTRJrWnZeNFMxBM57O+fQ5Y1XF8/4eQkg3D4EVdXedzcFDhisTKSSYHmZ9zfVzipr+f9r2yd3qbpLuIxAxcXKj1oQlFMNBoWV8OUMcX/tfy20DUNJUGErBoIn2vY2hKwuZnFzo6EfJ7UN5tcUSpVRSRS4oqi0RLi8TJXWK2qPcuu66LVaqLV7kA1LYg1D3t7OoLBBFZWQtjYyODw0IYgGETSI3x4qCGXq9OLJFqLyGZFqKrdI2TKJLkBSTXxQukGgyJWVyWsr4uEOgIBCcvLdezuyvyAabpcXaHw6w9pLichna7Ctr2eZd30YLo2Dg5UzM1VsLj4hOnpCCYnf2B29p72BapXKRyHemjg6CjFw2EhscAuL/N8z74AX02U0DB0JBImHRKwsFAmsgQhSWRZTE3FMDOTwPx8GUtLNWQyKj37zFUxu0wts8z6yELzNQyLUm3SQQGjo0VMTJQIFYyNZTAyEsH4OKsJvD48XITfL3LrrI93dyUK5pnmIrfP/jBO6Pen8enjGYaGzjE4GCZcoL9/H319nzEw8J3vWZ3d//AhRP0sE2EFx8dpnJ5mEQo9kGqhF0q9blLzo4TIP1hbuyH85PNbLRCIUPK32N5OolxWuNW3cGTZ4IS/AdMtiwnxpX7wAAAAAElFTkSuQmCC')\",\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/f6c992d4a47d7bfd84862de0027c7346/eb3fa/image13.png\",\n \"srcSet\": [\"/static/f6c992d4a47d7bfd84862de0027c7346/a2ead/image13.png 259w\", \"/static/f6c992d4a47d7bfd84862de0027c7346/6b9fd/image13.png 518w\", \"/static/f6c992d4a47d7bfd84862de0027c7346/eb3fa/image13.png 1026w\"],\n \"sizes\": \"(max-width: 1026px) 100vw, 1026px\",\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 Confidentiality, Integrity, and Availability (CIA) triad and the\\nPrevent, Mitigate, and Recover (PMR) constructs are useful in mapping\\ncyber to the four layers in the pyramid. The CIA triad can be thought of\\nas the desired effects akin to Mission Effects for a system that enables\\nor performs cyber defense operations, while the attributes associated\\nwith the PMR construct can be thought of as enabling the CIA effects and\\nakin to System Capabilities, System Functions and Properties, and System\\nStructure. Therefore, the CIA triad leads to cyber-related \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", since\\nthey look at achieving desired effects. The PMR attributes lead to\\ncyber-related MOPs/MOSs, since they address required system\\ncapabilities, functions, characteristics, and logistics. This guide\\nshould act as a guideline for measures evaluating cybersecurity, cyber\\nsurvivability and cyber resiliency of a system can take any of the three\\nmeasure forms (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \").\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Cyber related considerations for \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Design Constructs.\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntypically uses one of three different \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" design constructs for planning\\nand reporting cyber-related effects as part of the overall \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. The\\nappropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" design construct is typically determined/developed when\\nbuilding the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct. The choice of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct for cyber\\nhas an impact on the selection of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", MOPs, and MOSs and where they\\nare placed in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct. The three \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" constructs are designated\\nas Integrated, Stand-Alone, and Hybrid. Descriptions of the\\ncyber-related \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" design constructs follow with examples of evaluation\\nsummary charts (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \") for each.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Integrated\"), \" Construct.\"), \" For integrated constructs (commonly referred\\nto as traditional or Ops-based), the test team covers cyber effects\\nwithin the measures under each operational COIs.\"), mdx(\"p\", null, \"Cyber operational conditions, cyber threats, and cyber-related measures\\nare addressed within the context of each mission or operations-based \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\n(wherever cyber can affect operational outcome). Cyber-related MOPs/MOSs\\ncover all attributes associated with PMR and the ten CSAs (cyber\\nsurvivability attributes). This \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct also allows for\\ncyber-related \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \"\\u2019s addressing CIA to be outlined separately across the\\noperational COIs, if needed.\"), mdx(\"p\", null, \"Using the integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct, identified/ notable cyber-related\\nissues that extend beyond the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" (i.e., do not affect the degree of\\nmission accomplishment of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" or the ability to place in field use)\\nmay be addressed in an annex to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report, if warranted. Figure\\nC-2 shows an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" example for the Integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Construct.\"), mdx(\"p\", null, \"Figure C-2. Integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Construct \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" Example\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"768px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/e6a04a7d94d01652d98ca181f791f26e/e5715/image14.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\": \"69.11196911196912%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAYAAAAvxDzwAAAACXBIWXMAAA7DAAAOwwHHb6hkAAACg0lEQVQ4y22T2XaiQBCG8/i5mZmbvMbM3SQnycTsUQcBiWvYoZFFcQFEjQH/KTBxzNLnFF3dVf1RVV19ABqbzWYnWZbBcRzoug7DMMAYK3XLsmDbdrn3pg8GAyyWK2QbYE2fnM4fFJCPQ9M0iGITtVodsqyQyOB5HhzHlTCeF9DtdtHpdGAwH33FgGIOsHohYAFIkpii0CgyhtEwgGXq8F0HzDbgDhhMs4jKLGfPc6GqCsJwSL4+/DBC+1GCppt4zrAFei7D+ekv/K1VoMkiBOEOfLOGVleE1OJoj4drt8EMCboiQFcFGKqIZvsR3jiF4wawvRCrdb4FzmazslZxkiCdx6jUNfy8ZjjlQ/yuebhqUJpPU3D9Kbp6iBFBZJbACVLMohQvOfBMn7KGBXAymZRFXi4XWC3X4NsXqLaP0TabBKrirHoGniLjKapqu4GuxiFJ+0jTFp0ZvVZ+exe7CIvCh2GIxeIZo1EDcXSF+bxBtluq3zda/yDbEQbed1ofku2IAjkkqLTFbbKyS3YRFrfmeT45JlQbHccVASeXIu65Hs5v7nFSucLF3QOtOdKvcXZ9iz83d3CDoATmm70I4zhGQIbhcFjCTZuhJ6t4EPuoN58gqxbqkoV7QceTwnD5twexo0Hq0G2PZ3jr5R0wocuYTqelFLrrj+jPYwTjCJI6hOMzzBMdpmdgMrWhOmPk2ZrSnVMZFp+Bxabv+5SyhyiKoLMAYs9ER/NguBNISguKcU66gJbWLHtvsUhL39Vq9R741Uv5aviUmWGPoFghPbP3tn3Gwce3/CZ5/jqXzht6VjmkxxbVUH0F/vf9lPJXwH0pRtG443iJMFriJcuxf24f+A/hpxU9HA+24QAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image14\",\n \"title\": \"image14\",\n \"src\": \"/static/e6a04a7d94d01652d98ca181f791f26e/e5715/image14.png\",\n \"srcSet\": [\"/static/e6a04a7d94d01652d98ca181f791f26e/a2ead/image14.png 259w\", \"/static/e6a04a7d94d01652d98ca181f791f26e/6b9fd/image14.png 518w\", \"/static/e6a04a7d94d01652d98ca181f791f26e/e5715/image14.png 768w\"],\n \"sizes\": \"(max-width: 768px) 100vw, 768px\",\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, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Stand-Alone\"), \" Construct.\"), \" In the stand-alone \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct, a\\nseparate Cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" unifies and/or compartmentalizes the impacts to\\nmission and/or operations of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" when employed within a\\ncyber-contested environment. This \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct allows the baselining of\\nuncontested performance in a cyber benign environment, as compared to\\nperformance of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" in a cyber-contested environment. All\\ncyber-contested operational conditions, threats, measures, and test\\nevents are addressed within the separate cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". The separate cyber\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" captures all cyber survivability, cyber resiliency and\\ncybersecurity-related measures. These cyber-related measures cover all\\nattributes associated with CIA, PMR, and the ten CSAs.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Composite Measures\")), \" (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 4 in Figure C-3) are used to collect and\\naggregate the effects of a cyber-contested environment on measures from\\nthe operational COIs. There should be a composite measure for each of\\nthe operational COIs. Additional cyber-specific measures address the\\nsystem\\u2019s cyber operational capabilities.\"), mdx(\"p\", null, \"Figure C-3. Stand Alone \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Construct \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" Example\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"791px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/e6d5208c0a400e8b54ab8eb67b433df2/cc8d6/image15.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\": \"73.74517374517376%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAA7DAAAOwwHHb6hkAAAC3ElEQVQ4y5VU227TUBDs/38CT6hSxRtS4YGiQmkLIrSENHHusRPb8d0+ie/XxBn2nKRFvCBhabwr25nZ3TObM/zndTjFlpIwKeGxEHFe43A4CJzx2263w36/F3h+8S9w2rrZg0UZXNdFkjcnNSKs6xocTdMgz3MYhiFgWdZLbpqmwPMzHvM8w9LawmYpEVZodnvBeVZV1Us7nLjX66Hb7cJxHEynU5FzMlmW0el0BKFt2xhIEhbKEpYf4rE3wspiR8KiKMBJOVmSJFAUBcvlEr4fQNd1kUdRhPV6DVVVRRe8Tf7cMg1IiouxbMBhyZGQf8AYQ1GUYoZZmh7H0bbIsozEauwpj0msrhu0dBp+EEDTdGy3IQw/xXLtwgpOhIx5GDx9g9TvYDb9hdlcwlweYTofwFxP4JhT2MYEujqEoU8E5HkPyqIHedHHQjXQ6Q4p2qj3dChJHFNrGvIsge0GuLwb4qZv4bqrQTVduGQLy2PURUDtJtRBTNWtMB4NYTkuTC8kcRmmy9AIQmrF8zw0dQWHBnz5VcPnfoSrnx7e3qm46m7wocvoBxl9AyJtaZZrSIMBXJ9hEyZ/+fQspgr5KZZFBZ/Z+DE4x1T/goH8CQ/Se4y1GwHdvKYuvtNc78kBNArbQxQnmOsBwqxB1bR0Bu2xQlVdIQwjUidkE7R7neICvndOVV1g17wh0VdIswuU5WsE7AmeH4vDNL0tRpM5pPGMiOtjhdwePMakmKQNirIlqxQkUBJBTUQFWSqjvEFd7fDwa4h3H29xdfuI+74GWXchazaycneskDufe8v3fVRlTqtYieHntKNVxe1Tk0BMhAXZKydDqxjNFEyVNVnGw2qlIiUyMcOUfLfZbMhTW/IXg0JKmuljZXCBEb0bEdmYokMChTA5R03LwAVMJ8BiqSFKyz+rxyvj2NIc5ysbM4JKqxQEPcID0vSJqgyoukpsCi+CRwG+EAec/jSA32QEY/Fq396vAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image15\",\n \"title\": \"image15\",\n \"src\": \"/static/e6d5208c0a400e8b54ab8eb67b433df2/cc8d6/image15.png\",\n \"srcSet\": [\"/static/e6d5208c0a400e8b54ab8eb67b433df2/a2ead/image15.png 259w\", \"/static/e6d5208c0a400e8b54ab8eb67b433df2/6b9fd/image15.png 518w\", \"/static/e6d5208c0a400e8b54ab8eb67b433df2/cc8d6/image15.png 791w\"],\n \"sizes\": \"(max-width: 791px) 100vw, 791px\",\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, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Hybrid\"), \" Construct.\"), \" The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Hybrid\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct applies elements of\\nboth the Integrated and Stand-Alone \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" constructs. Similar to the\\nIntegrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct, cyber effects are addressed within the\\noperations-based COIs. Additionally, a separate cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is created to\\nallow the test team to focus on capturing non-disruptive and/or indirect\\ncyber effects or the underlying/common cyber aspects across the system.\"), mdx(\"p\", null, \"Cyber operational conditions, cyber threats, cyber-related measures, and\\ncyber test events are addressed within the context of the operational\\nCOIs. The separate cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is functionally focused (i.e., cyber\\nrelated operational capabilities) and also addresses effects not seen\\nwithin the missions or operational COIs (e.g., indirect effects, 2nd/3rd\\norder effects, exfiltration). The separate cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" may also be used to\\nexpand cyber reporting beyond the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", if warranted. Figure C-4 shows an\\nexample \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" for the Hybrid \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct.\"), mdx(\"p\", null, \"Figure C-4. Hybrid Construct \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" Example\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"844px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/b0e68fbd01d37d0cd3a38ba8367feb26/33e10/image16.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\": \"66.40926640926641%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAAA7DAAAOwwHHb6hkAAACX0lEQVQ4y41Ty3LaQBDk+3NJcssvpCqHVC44dqWMKQhgx4DBSAL0fj9YoTcgOXRGqhg7sQ+eqq2dlXZ6ert3W/gvjscj3hosyuB4G+T7h1NtK4wLeCxBtivrL82PJElgmiYcx4Ft2/8M13VhWxYsi9ZBDNNliLPdqUlL0myIoojsb5c66qJev48Fx0HXdQwGAwiCAE3TMBwOoShKAzj4NW+apvketheCxTlasu5AkSVaFLAdD2mawvf9pkkYsiZfLldgYQiP8hqsKApsNgymYYKxEFaQYiVSEz9Cyw4iKIYLSTVwddnG/G6EpTABz4+hG2vI0hyWvoBrCVDlGQyNg6nzEFdTyOKMyNzD32ywL39jd6jQejxmEkdQVRlpEmLGy/h8zqN9beNiKOOWs3C9cLFWPNqXEestPM9DtGUIAhdFnj1p+OhqFMUEqOKhOkKzRPTnZ+DMe3THHfTuehhLU4jGLapyhf2eQ5a6qCpitds14+Ty8ZmzorhGTAwYk0n0M2y3U9LpC5nxjth8oobvoWof4Acf4bgj0jSCS0zzvHgJWJtRu1jTlxQLX9tDdAYcvncn+HbewdVggvPuDdo/ergaTnHRHVHex+XPMQK2fR3QMAwwEtgg9xbCChrNM15Ff6JhtjIwmsngliKWko7ZYoXFUgK/VhHFyUvAPM9JaL+5Kq6/gaS70Bw6ki/BCxZQKZeMoLlzBe1NSaKyPDT5qxqWZUnGRKRljCjJoJg+AcbYbE24gQCOF3AzGiLYpsiLPRmzx+FwaOaqqp4A3/J+61fpsxiOz5Dkh9P+53WP+R8gAcwl2sfOGAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image16\",\n \"title\": \"image16\",\n \"src\": \"/static/b0e68fbd01d37d0cd3a38ba8367feb26/33e10/image16.png\",\n \"srcSet\": [\"/static/b0e68fbd01d37d0cd3a38ba8367feb26/a2ead/image16.png 259w\", \"/static/b0e68fbd01d37d0cd3a38ba8367feb26/6b9fd/image16.png 518w\", \"/static/b0e68fbd01d37d0cd3a38ba8367feb26/33e10/image16.png 844w\"],\n \"sizes\": \"(max-width: 844px) 100vw, 844px\",\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, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures Development.\"), \" Regardless of what \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct is selected,\\ntest teams must develop measures addressing cyber survivability, cyber\\nresiliency, and cybersecurity for their SUTs.\"), mdx(\"p\", null, \"The selection of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct (and development of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \") is\\naccomplished as part of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct. At the Measures Workshop\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are refined, and MOSs and MOPs are developed. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", Detachment\\ncyber analysts, the detachment test team, cyber test subject matter\\nexperts (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \") from A-3I, and analysts from A-2/9 collaborate on\\ndeveloping system-specific, mission-centric cyber-related measures.\"), mdx(\"p\", null, \"Developing quantitative and observable qualitative operationally\\nrelevant measures is a complex challenge that requires careful\\ncollaboration with all stakeholders. As teams develop measures to suit\\nspecific systems under test, the cyber teams develop cyber-related\\nmeasures that address and evaluate: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"effects, capabilities,\")), \"\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"attributes, and characteristics\")), \" that contribute to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\u2019s\\ndegree of cyber survivability, cyber resiliency and cybersecurity.\"), mdx(\"p\", null, \"Cyber survivability, resiliency and security can be represented with the\\nCIA triad of effects and the PMR associated attributes. A cyber-related\\nmeasure addressing CIA effects and/or PMR related attributes may be\\nincluded, or CIA effects and/or PMR related attributes may be aggregated\\ninto composite measures. Table C-1 contains definitions for CIA. Table\\nC-2 contains definitions for PMR and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"\\u2019s. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": if a separate cyber\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is employed the test team must still address PMR and CIA.\"), mdx(\"p\", null, \"Table C-1. CIA Defined\", \"[3]\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"CIA\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Confidentiality\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information.\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Integrity\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Guarding against improper information modification or destruction and ensuring information non-repudiation and authenticity.\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Data Integrity\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"The property that data has not been altered in an unauthorized manner. Data integrity covers data in storage, during processing, and while in transit.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"System Integrity\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"The quality that a system has when it performs its intended function in an unimpaired manner, free from unauthorized manipulation of the system, whether intentional or accidental.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Availability\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Ensuring timely and reliable access to and use of information.\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"Table C-2. System Survivability (SS) Key Performance Parameter (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \")\\nPillars\", \"[4]\", \" Defined and Mapped to their Cyber Survivability Attributes\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \")\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"SS \", mdx(\"abbr\", {\n parentName: \"th\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \"\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Description\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Cyber Survivability Attribute\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"PMR\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Prevent\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Design principles and operations that enable or provide protection of the systems mission functions from most likely cyber threats\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-01 \\u2013 Control Access\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-10 \\u2013 Actively Manage System Configurations to Counter Vulnerabilities at Tactically Relevant Speeds\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-02 \\u2013 Reduce System\\u2019s Cyber Detectability\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-03 \\u2013 Secure Transmissions and Communications\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-04 \\u2013 Protect System\\u2019s Information from Exploitation\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-05 \\u2013 Partition and Ensure Critical Functions at Mission Completion Performance Levels\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-06 \\u2013 Minimize and Harden Attack Surfaces\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mitigate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Design principles and operations that enable or provide detection and responding to cyber-attacks, enabling the system to survive, operate in a degraded environment, and complete the mission\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-07 \\u2013 Baseline & Monitor Systems and Detect Anomalies\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-08 \\u2013 Manage System Performance if Degraded by Cyber Events\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Recover\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Design principles and operations that enable or provide \", mdx(\"em\", {\n parentName: \"td\"\n }, mdx(\"u\", null, \"recovery\")), \" from cyber-attacks and prepare mission systems for the next fight\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-09 \\u2013 Recover System Capabilities\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"The goal of measures development is to produce operationally relevant\\nquantitative and qualitative measures. Each system is examined to\\ndetermine whether additional operationally relevant measures need to be\\napplied. Keep in mind that the structure and placement of cyber-related\\nmeasures will depend on choice of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct (Integrated,\\nStand-Alone, or Hybrid) made during the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E construct (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \")\\nmeeting.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Cyber-Related Measures Rating Options.\"), \" The Cyber-related Measures\\nAppendix is not intended to detail or specify how to rate cyber\\nmeasures. Refer to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Cyber Test Guide for guidance on how to\\nscore measures using operationally relevant data. The options presented\\nin the tables and figures that follow are provided to help cyber\\nanalysts look ahead to how measures are rated, while developing the\\nmeasures.\"), mdx(\"p\", null, \"One needs to establish an expected result for each operationally\\nrelevant measure. Rating of each measure will be based on the degree to\\nwhich test results meet expectations and requirements.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure Rating: Tier Set Option.\"), \" The following Cyber Tier Set Rating\\nScale is the first option provided to help influence cyber-related\\nmeasures development. Tables C-3 and C-4 show examples of tier sets,\\nthreshold levels, ratings and their descriptions for measures addressing\\ncyber survivability.\"), mdx(\"p\", null, \"Detachment cyber analysts have the autonomy to modify input for best\\npractice and with locally approved language that is defensible. Consider\\nthese to simply be a menu of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" approved tier sets and approaches.\"), mdx(\"p\", null, \"Table C-3. Ratings for Cyber-Related Measures for Cyber Survivability\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Tier Set\"), mdx(\"th\", null, \"Threshold Level\"), mdx(\"th\", null, \"Rating\"), mdx(\"th\", null, \"Rating Description\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Security\")), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Highly Effective\"), mdx(\"td\", null, \"Acts that bypass security policies, practices, or procedures are rapidly detected, cleaned and prevented from happening again. They do not degrade mission effects.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Effective\"), mdx(\"td\", null, \"Security breaches have minimal impact to System Capabilities, System Functions and Properties, but no degradation of Mission Effects.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Appears to be adequate\"), mdx(\"td\", null, \"Security breaches impact System Capabilities, System Functions and Properties, or System Structure, and minimally degrade Mission Effects.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Minimal with breaches\"), mdx(\"td\", null, \"Security breaches impact System Capabilities, System Functions and Properties, or System Structure, and significantly degrade Mission Effects.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"There are no security policies, practices, or procedures in place to prevent breaches. This leads to no mission accomplishment.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Proactive Protection\")), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Protected\"), mdx(\"td\", null, \"System-wide protection has proactive processes in identifying and mitigating disruptions. System is alert to new disruptions and puts corrective measures in place immediately.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Protection measures in place\"), mdx(\"td\", null, \"System has many protective measures in place. It is not totally proactive in its corrective action. However, it is able to identify problems and react appropriately and swiftly to ensure mission accomplishment.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Some system-wide protection available\"), mdx(\"td\", null, \"System has elementary protection measures. Primary mode of correction is reactionary to disruptions. Little time is available to be proactive. Although impacted, some system-wide protection remains.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Minimal, isolated protection\"), mdx(\"td\", null, \"No system-wide protection in place. Disruptions circumvent any protection measures attempted. Fixes turn out to be temporary in addressing symptoms and not causes.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"No protection\"), mdx(\"td\", null, \"System has little or no protection at all.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Vigilance\"), \" (Detection)\"), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Maintains awareness of new vulnerabilities\"), mdx(\"td\", null, \"System enables operators/defenders to maintain awareness of all known vulnerabilities, actively researches and identifies potentials for new vulnerabilities, and is able to project vulnerabilities that result from new technology development.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Able to react to new vulnerabilities\"), mdx(\"td\", null, \"System enables operators/defenders to address all known sources of disruption and/or vulnerabilities. The ability to address the surfacing of new sources of disruption and/or vulnerabilities is a reactive, but effective, process.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Able to mitigate most vulnerabilities\"), mdx(\"td\", null, \"System enables operators/defenders to identify existing vulnerabilities, mitigate most major vulnerabilities and react to disruptions. Although impacted, some awareness of attacks remains.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Not able to address new vulnerabilities\"), mdx(\"td\", null, \"System enables operators/defenders to have a basic understanding of vulnerabilities and has cursory awareness of them. Provides no ability to address new vulnerabilities ahead of disruptions.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"Unaware of vulnerabilities\"), mdx(\"td\", null, \"System\\u2019s design specification provides no consideration for detection of abnormal/malicious activity.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Mitigations\"), \" (Response)\"), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Successful in mitigating or avoiding all known attacks\"), mdx(\"td\", null, \"All known attacks did not affect operational availability of accurate data or lead to the unauthorized disclosure of data. System was able to tolerate and mitigate and continue operations as normal.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Successful in mitigating or avoiding most attacks\"), mdx(\"td\", null, \"Attacks are present, but do not affect successful completion of mission. Specific actions need to be taken; however, they are successful in mitigating any effects.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Some proactive measures in place\"), mdx(\"td\", null, \"Attacks are serious and cannot be ignored. More reactive than proactive measures are necessary. Many consequences of attacks are unexpected. Although impacted, some protective measures/capabilities remain.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Reactive measures taken\"), mdx(\"td\", null, \"Attacks are critical to the system operation and mission accomplishment. The reactive measures do not handle all of the attacks.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"No measures available\"), mdx(\"td\", null, \"Attacks are catastrophic and result in system shutdown.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Recovery\")), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Immediate Recovery\"), mdx(\"td\", null, \"The system is able to recover after attacks immediately such that there is no critical or non-critical mission impact.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Rapid Recovery\"), mdx(\"td\", null, \"There is observable downtime after an attack, but the system is able to recover before a critical mission impact occurs (non-critical mission impacts may occur).\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Timely Recovery\"), mdx(\"td\", null, \"There is minimal impact to critical mission after an attack due to downtime.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Can Recover Eventually\"), mdx(\"td\", null, \"Significant effort is required to recover after an attack resulting in severe mission impact.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"Unrecoverable\"), mdx(\"td\", null, \"The system is completely unrecoverable after an attack.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, mdx(\"strong\", null, \"Continuity of Operations\")), mdx(\"p\", null, \"(Transfer and Continue Ops)\")), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Maximum\"), mdx(\"td\", null, \"System successfully transfers full functionality. System remains highly capable of completing the mission.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Able to operate effectively\"), mdx(\"td\", null, \"System is able to transfer functionality required to meet most mission requirements. System may experience some minor problems, but effectively accomplishes the mission.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Meeting minimum requirements\"), mdx(\"td\", null, \"System is able to transfer only minimal functionality. System is struggling, but meets minimum mission requirements.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Failing\"), mdx(\"td\", null, \"Transfer is unable to meet most mission requirements. Delays and/or the lack of functionality are a distraction to the mission.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"Complete breakdown\"), mdx(\"td\", null, \"System is unable to transfer functionality, and is unable to continue operations.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Normal Operations\")), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Full capabilities online\"), mdx(\"td\", null, \"System is highly capable of completing the mission. System is running all subsystems, processes and applications with no problems. System-wide protection has proactive processes in identifying and mitigating disruptions. System confidence is high.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Maintains normal operations, reaches new equilibrium\"), mdx(\"td\", null, \"System experiences some minor problems but effectively accomplishes the mission. System is running normal operations; however, it is continuously adjusting for disruptions. System has many protective measures in place. System confidence is adequate.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Struggles to stay ahead of problems\"), mdx(\"td\", null, \"System is struggling to meet mission requirements. Subsystems, processes and applications are occasionally failing. System has elementary protection measures. System confidence is moderate illustrating concern over mission accomplishment and integrity of the system. Although impacted, minimum mission accomplishment continues.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Experiencing outages, delays and blackouts\"), mdx(\"td\", null, \"System cannot meet most mission requirements, is impacted by problems, and cannot keep up with mitigating actions. System is spending more time addressing disruptions than accomplishing the mission. No system-wide protection is in place. Low confidence that the system can be counted on to do the mission.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"System failure\"), mdx(\"td\", null, \"System cannot meet mission requirements. System crashes or is near to crashing under the weight of disruptions. System has little or no protection at all. No confidence that the system can be counted on to do the mission.\")))), mdx(\"p\", null, \"Table C-4. Ratings and Descriptions for PMR and Associated CSAs\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Tier Set\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold Level\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rating\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rating Description\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Prevent, Mitigate, Recover, and/or All-Encompassing\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"V\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Exceeds Capability Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Goes above and beyond the CSRC associated required capability standard to ensure the most secure cyber posture possible.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"IV\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Meets Capability Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Meets the CSRC associated required capability standard for effective cyber-security.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"II\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Approaches Capability Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"CSRC associated required capability standard is not met, however the system is close to achieving the standard.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"II\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Fails Capability Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"CSRC associated required capability standard is not close to being met and the system needs significant improvement in its cyber posture.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"I\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Entirely Fails Capability Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"System has no cybersecurity capability whatsoever and lacks even the most basic components to pass the CSRC associated required capability standard.\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure Rating: Tier Threshold to Mission Impact Heat Chart Option.\"), \"\\nThe following scale is the second menu option provided to help influence\\ncyber-related measures development. Here cyber-related impacts to the\\nmission correlate to tier thresholds and the mission of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" through\\nthe use of a heat chart. Tables C-5 and C-6 contain risk based scales to\\ninfluence cyber-related measures development.\"), mdx(\"p\", null, \"Table C-5. Tier Threshold to Mission Impact Comparison Heat Chart\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Tier Threshold\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"I\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"II\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"III\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"IV\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"V\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Impact\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Catastrophic\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Major\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Moderate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"1\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")))), mdx(\"p\", null, \"Table C-6. Mission Impact Descriptions\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Level\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Impact\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Description\"))), 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 }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Little to no mission degradation\")), 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 }, \"Moderate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Partial mission degradation\")), 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 }, \"Major\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Critical mission degradation\")), 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 }, \"Catastrophic\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Complete mission failure\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure Rating: Cyber Survivability Risk Category (CSRC) Heat Chart\\nOption.\"), \" In this option the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\u2019s assigned CSRC will drive selection of\\nthe required/expected metric and threshold for each cyber-related\\nmeasure. Definitions of the CSRCs and a description of the process used\\nto select the appropriate CSRC for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can be found in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Chiefs of Staff\"\n }, \"JCS\"), \" Cyber\\nSurvivability Endorsement Implementation Guide (CSEIG), Version 1.01. In\\ngeneral, The CSRC is determined from a combination of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\u2019s Mission\\nType (MT), Cyber Dependence Level (CDL), Adversary Threat Tier (ATT),\\nand Impact of System Compromise (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \"). Levels vary from 1 through 4.\\nTheir associated required capability standards are detailed in Table\\nC-7.\"), mdx(\"p\", null, \"Table C-7. Tiers and Descriptions of Associated Capability Standards\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Tier\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Description of Capability Standards (Tiers)\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"V\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Very High\"), \": Mitigations rely on best available countermeasures, to include custom \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" protections, commensurate against assumed threat capabilities.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"IV\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"High\"), \": Mitigations include Enhanced Assurance \\u2013 redundancy, TTPs, and strong \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commercial Off-the-Shelf\"\n }, \"COTS\"), \"/\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Government Off-the-Shelf\"\n }, \"GOTS\"), \" securely configured in layered architectures \\u2013 with \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" added technology, as needed.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"III\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Moderate\"), \": Mitigations include \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commercial Off-the-Shelf\"\n }, \"COTS\"), \"/\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Government Off-the-Shelf\"\n }, \"GOTS\"), \" cybersecurity products and technologies, with potential \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" technology additions, with best practices, strong \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" layered defenses, and selective use of \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" technology.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"II\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Low\"), \": Mitigations include \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commercial Off-the-Shelf\"\n }, \"COTS\"), \" with best practices if commercially hosted, or strong \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" layered defenses, possible use of \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" technology if \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" hosted\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"I\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Poor\"), \": Mitigations do not exists or are totally ineffective\")))), mdx(\"p\", null, \"Similar to the tier rating scale, a heat chart could also be used in\\nconjunction with the program\\u2019s assigned CSRC. After determination of the\\nassociated CSRC Level, a correlation to a low, medium, or high (e.g.,\\ngreen, yellow, red) reporting standard can easily be mapped against the\\ntier threshold (Table C-8).\"), mdx(\"p\", null, \"Table C-8. Tier Threshold to CSRC Comparison Heat Chart\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Tier Threshold\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"I (Poor)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"II (Low)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"III (Moderate)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"IV (High)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"V (Very High)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"CSRC Level\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"1\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Examples of Cyber-related Measures.\"), \" In general, it is up to the\\ndetachment and test team to determine the appropriate format for their\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\u2019s cyber-related \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" programs cybersecurity construct and associated\\nmeasures.\"), mdx(\"p\", null, \"What follows are two example cyber-related measures. This section is not\\nmeant to be an all-inclusive list of cyber-related measures. Nor is it\\nintended to be a checklist, or a cut-and-paste template. Rather, this\\nsection is intended to demonstrate acceptable cyber-related measures and\\nwhat should be included in a cyber-related measure worksheet. Test teams\\nare encouraged to develop and use variations of these cyber-related\\nmeasures (or new cyber-related measures) in order to best suit the needs\\nof their individual SUTs.\"), mdx(\"p\", null, \"The cyber-related measures in the Measures Summary (Tables C-9 and C-10)\\nand the Cyber-related Measure Worksheets (Tables C-11 thru C-14) are\\nexamples of how to evaluate the cyber risk to a system for the separate\\nCyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" in the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CStand Alone\\u201D\"), \" or \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CHybrid\\u201D\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Construct. They use a\\nkind of behaviorally anchored rating scale (i.e., tiers and heat charts)\\nto identify the levels of effectiveness and performance. These anchors\\ncan be tailored to a particular system or test program and ideally would\\nbe defined such that they are observable, measureable and independently\\nverifiable (i.e., via an inter-observer agreement).\"), mdx(\"p\", null, \"Table C-9. Example of a Separate Cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \", Tier Based\", mdx(\"br\", {\n parentName: \"p\"\n }), \"\\n\", \"Cyber-related Measures Summary Table\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Measure\"), mdx(\"th\", null, \"Tier Set\"), mdx(\"th\", null, \"Metric\"), mdx(\"th\", null, \"Threshold Level\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOE 4.1: Rating of NG DRAGON\\u2019s Confidentiality of Data and System Information \", mdx(\"strong\", null, \"(C)\")), mdx(\"td\", null, \"Confidentiality\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOE 4.2: Rating of NG DRAGON\\u2019s Integrity of Data and System (I)\"), mdx(\"td\", null, \"Integrity\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOE 4.3: Rating of NG DRAGON\\u2019s Availability of Data and System (A)\"), mdx(\"td\", null, \"Availability\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 1: Rating of NG Dragon\\u2019s Capabilities, Functions, Properties, and Structure Enabling Operational Users and Service Providers Management of Cybersecurity Risk to Systems, Assets, Data, and Capabilities\"), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 2: Rating of NG DRAGON\\u2019s Physical Security / Protection Against Physical Threats\"), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 3: Rating of NG DRAGON\\u2019s Detection of Abnormal/Malicious Activity\"), mdx(\"td\", null, \"Vigilance\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 4: Rating of NG DRAGON\\u2019s Response to Abnormal / Malicious Activity Without Degrading Capabilities (Incident Response)\"), mdx(\"td\", null, \"Mitigations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 5: Rating of NG DRAGON\\u2019s Restoring Sustained, Operationally Acceptable Capabilities after Abnormal/Malicious Activity (Mission Restoration)\"), mdx(\"td\", null, \"Recovery\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 6: Rating of NG DRAGON\\u2019s Capability to Recover Operationally Acceptable Data after Abnormal/Malicious Activity (Data Recovery)\"), mdx(\"td\", null, \"Recovery\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 7: Rating of NG DRAGON\\u2019s Transfer of Mission, Continuity of Operations after Abnormal/Malicious Activity\"), mdx(\"td\", null, \"COOP\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 8: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling Depot Maintenance Planning in a Contested Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOP 9: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling Depot Maintenance Scheduling in a Contested Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 10: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling Depot Maintenance Execution in a Disruptive Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOP 11: Rating of NG DRAGON Providing Enterprise Standardization and Visibility in a Disruptive Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOS 1: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling it to be Maintained (Maintainability) in a Disruptive Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOS 2: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling it to be Supported (Supportability) in a Disruptive Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOS 3: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling it to Operate Within The Operational Infrastructure in a Disruptive Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 12: Instances when NG DRAGON Does Not Process (Input/Output) Critical IERs\"), mdx(\"td\", null), mdx(\"td\", null, \"Maximum\"), mdx(\"td\", null, \"^ Zero\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 13: Non-Critical IER Exchanges that Process Successfully (Input/Output) on the First Try\"), mdx(\"td\", null), mdx(\"td\", null, \"Percentage\"), mdx(\"td\", null, \"^ \\u2265 90%\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOS 4: Rating of the Supply Chain Management (HW/SW) of NG DRAGON\"), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 14: Rating of the Configuration Control of NG DRAGON\"), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOS 5: Rating of Awareness Training for the Users of NG DRAGON\"), mdx(\"td\", null, \"Protection\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 15: Rating of the Security of NG DRAGON\\u2019s Architecture/Network\"), mdx(\"td\", null, \"Protection\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOP 16: Rating of the Software Security of NG DRAGON\"), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 17: Rating of the Boundary Protection (External Protection) of NG DRAGON\"), mdx(\"td\", null, \"Protection\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOP 18: Rating of the Access Management (Internal Protection) of NG DRAGON\"), mdx(\"td\", null, \"Protection\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 19: Rating of Situational Awareness (Indications and Warnings) of NG DRAGON\"), mdx(\"td\", null, \"Vigilance\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"* KPP or Supports KPP\", mdx(\"br\", null), \"^ AFOTEC Identified Standard (i.e., not specified in requirement documents)\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, \"Table C-10. Example - Cyber-related Measures and\", mdx(\"br\", {\n parentName: \"p\"\n }), \"\\n\", \"Cyber Survivability Tier Threshold Summary\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Measure\"), mdx(\"th\", null, \"Tier Set\"), mdx(\"th\", null, \"V\"), mdx(\"th\", null, \"IV\"), mdx(\"th\", null, \"III\"), mdx(\"th\", null, \"II\"), mdx(\"th\", null, \"I\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOE 4.1\"), mdx(\"td\", null, \"Confidentiality\"), mdx(\"td\", null, \"Very High\"), mdx(\"td\", null, \"High\"), mdx(\"td\", null, \"Moderate\"), mdx(\"td\", null, \"Low\"), mdx(\"td\", null, \"Poor\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOE 4.2\"), mdx(\"td\", null, \"Integrity\"), mdx(\"td\", null, \"Very High\"), mdx(\"td\", null, \"High\"), mdx(\"td\", null, \"Moderate\"), mdx(\"td\", null, \"Low\"), mdx(\"td\", null, \"Poor\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOE 4.3\"), mdx(\"td\", null, \"Availability\"), mdx(\"td\", null, \"Very High\"), mdx(\"td\", null, \"High\"), mdx(\"td\", null, \"Moderate\"), mdx(\"td\", null, \"Low\"), mdx(\"td\", null, \"Poor\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"*MOP 1\"), mdx(\"p\", null, \"*MOP 2\"), mdx(\"p\", null, \"MOS 4\"), mdx(\"p\", null, \"MOP 16\"), mdx(\"p\", null, \"MOP 18\")), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Highly Effective\"), mdx(\"td\", null, \"Effective\"), mdx(\"td\", null, \"Appears to be adequate\"), mdx(\"td\", null, \"Minimal with breaches\"), mdx(\"td\", null, \"None\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"MOS 5\"), mdx(\"p\", null, \"MOP 15\"), mdx(\"p\", null, \"MOP 17\"), mdx(\"p\", null, \"MOP 18\")), mdx(\"td\", null, \"Protection\"), mdx(\"td\", null, \"Protected\"), mdx(\"td\", null, \"Protection measures in place\"), mdx(\"td\", null, \"Some system-wide protection available\"), mdx(\"td\", null, \"Minimal, isolated protection\"), mdx(\"td\", null, \"No protection\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"*MOP 3\"), mdx(\"p\", null, \"MOP 19\")), mdx(\"td\", null, \"Vigilance\"), mdx(\"td\", null, \"Maintains awareness of new vulnerabilities\"), mdx(\"td\", null, \"Able to react to new vulnerabilities\"), mdx(\"td\", null, \"Able to mitigate most vulnerabilities\"), mdx(\"td\", null, \"Not able to address new vulnerabilities\"), mdx(\"td\", null, \"Unaware of vulnerabilities\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 4\"), mdx(\"td\", null, \"Mitigations\"), mdx(\"td\", null, \"Attacks have little or no effect on operations\"), mdx(\"td\", null, \"Successful in mitigating or avoiding most attacks\"), mdx(\"td\", null, \"Some proactive measures in place\"), mdx(\"td\", null, \"Reactive measures taken\"), mdx(\"td\", null, \"No measures available\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 7\"), mdx(\"td\", null, \"COOP\"), mdx(\"td\", null, \"Maximum\"), mdx(\"td\", null, \"Able to operate effectively\"), mdx(\"td\", null, \"Meeting minimum requirements\"), mdx(\"td\", null, \"Failing\"), mdx(\"td\", null, \"Complete breakdown\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"*MOP 5\"), mdx(\"p\", null, \"*MOP 6\")), mdx(\"td\", null, \"Recovery\"), mdx(\"td\", null, \"Immediate recovery\"), mdx(\"td\", null, \"Rapid recovery\"), mdx(\"td\", null, \"Timely recovery\"), mdx(\"td\", null, \"Can recover eventually\"), mdx(\"td\", null, \"Unrecoverable\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"MOP 8\"), mdx(\"p\", null, \"MOP 9\"), mdx(\"p\", null, \"MOP 10\"), mdx(\"p\", null, \"MOP 11\"), mdx(\"p\", null, \"MOS 1\"), mdx(\"p\", null, \"MOS 2\"), mdx(\"p\", null, \"MOS 3\")), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Full capabilities online\"), mdx(\"td\", null, \"Maintains normal operations, reaches new equilibrium\"), mdx(\"td\", null, \"Struggles to stay ahead of problems\"), mdx(\"td\", null, \"Experiencing outages, delays, and blackouts\"), mdx(\"td\", null, \"System failure\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*KPP or Supports KPP\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, \"Table C-11. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Tier Based Cyber-Related Measure Worksheet Example\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"(See the main body of this guide for template and content\\nrequirements)\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Operational Capability: Cybersecurity\"), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Measure\"), mdx(\"td\", null, \"Metric\"), mdx(\"td\", null, \"Threshold\"), mdx(\"td\", null, \"Results\"), mdx(\"td\", null, \"Rating\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOE 4.2: Rating of NG DRAGON\\u2019s Integrity of Data and Systems\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\"), mdx(\"td\", null, \"TBD\"), mdx(\"td\", null, \"TBD\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"* KPP or Supports KPP\", mdx(\"br\", null), \"^ Identified Standard\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"References\"), \": \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Provide the requirement source (stated or derived).\\nSpecify the paragraph, section, line, etc. \", mdx(\"u\", null, \"This is part of the\\nexample and references could be out of date.\"))), mdx(\"p\", null, \"Derived from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo, 3 Apr 18, Procedures for Operational Test and\\nEvaluation of Cybersecurity in Acquisition Programs; Department of\\nDefense (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \") 8510.01, Risk Management Framework (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Management Framework\"\n }, \"RMF\"), \") for Department of\\nDefense (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \") Information Technology (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"), 12 Mar 14; National Institute\\nof Standards and Technology (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Institute of Standards and Technology\"\n }, \"NIST\"), \") Special Publication (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Plan OR Special Publication\"\n }, \"SP\"), \") 800-53,\\nSecurity and Privacy Controls for Federal Information Systems and\\nOrganizations, Rev. 4, 30 Apr 13.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Scope\"), \": This cyber-related measure addresses the degree NG \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"\n }, \"DRAGON\"), \"\\u2019s\\nPMR capabilities, functions, and structure enable or provide data and\\nsystem integrity. Data integrity is the property that data has not been\\naltered in an unauthorized manner while in storage, during processing,\\nor while in transit. System integrity is the quality that a system has\\nwhen performing the intended function in an unimpaired manner, free from\\nunauthorized manipulation. This measure will also consider what \\u201Cimpact\\nadversary and unauthorized modification or destruction of system\\ninformation\\u201D has on \\u201Cfunctions to the mission\\u201D (\\u201C\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Center for Systems Engineering OR Common Support Equipment\"\n }, \"CSE\"), \" Implementation\\nGuide Version 1.01\\u201D, pg. 17). This measure evaluates the following\\nprotection metrics:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Account Management\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Least Privilege\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identification and Authentication\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Continuous Monitoring\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Device Identification and Authentication\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Authenticator Management\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Default Authenticators\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Physical Access Control\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Boundary Protection\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Secure Network Communications\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Update Management\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Malicious Code Prevention\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Methodology\"), \": The test team will coordinate with Blue & Red\\nTeams to conduct the Cooperative Vulnerability and Penetration\\nAssessment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \") and the Adversarial Assessment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \") respectively. The\\ntest team will review documentation, observe the system, and conduct the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \" during system use by operational users in a realistic\\noperational environment, as described in the overarching \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 4 test\\nmethodology. The test team will identify, verify, and attempt to exploit\\nvulnerabilities in the NG \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"\n }, \"DRAGON\"), \" system in accordance with identified\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" cybersecurity test requirements. They will leverage\\nvulnerabilities highlighted in prior risk assessments, system audit\\nreports, vulnerability and penetration team findings, and direct\\nobservation of the application of the cybersecurity controls. It is\\nassumed that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \" will disrupt and/or even deny operations, therefore\\neffectiveness and suitability test data must be collected prior to\\ncyber-attack. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \" and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \" are expected to last approximately 2\\nweeks each.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Design\"), \": Uses overarching \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 4 test design.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data and Analysis\"), \": The test team will compare system protection\\ninformation to requirements set forth in various laws, doctrine, and\\npolicies. For each instance where the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is unable to provide the\\nintegrity of data or the system, the test team will assess the\\ncorresponding mission impact using a simple scale (High, Medium, Low, or\\nequivalent), operational experience, and judgment to rate the measure\\nagainst the identified standard (Integrity tier sets). The mission\\nimpact scale will be related to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Management Framework\"\n }, \"RMF\"), \" categorization for integrity. In the\\nevent that exploitation of a vulnerability is precluded due to critical\\nmission requirements or safety concerns, the test team will estimate\\nmission impact based on technical expertise, operational experience, and\\nrelevant operational subject matter expert input.\"), mdx(\"p\", null, \"The test team will present cybersecurity control findings and aggregated\\nresults in the final report. Each control will be assigned a rating\\n(Met, Partially Met, Not Met, or Not Applicable) presented in table\\nformat. Cybersecurity findings will be detailed in the report narrative,\\nto include associated recommendations for risk mitigation, vulnerability\\nreduction, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactics, Techniques, and Procedures OR Technology Transition Plan\"\n }, \"TTP\"), \" modification. The number of users interviewed, the\\noverall trend of responses from interviews, and highlight comments and\\nobservations concerning the cybersecurity posture will also be included\\nin the report. The test team will log and bin the total number of\\nillicit attempts according to their category level. They will also log\\nthe total number of attempts, in conjunction with illicit attempts that\\nwere defended successfully. Manual and automated intrusion methods will\\nbe delineated and logged. The \\u201Ctime to achieve access\\u201D will be\\ncalculated via the delta between the initial attempt to access and when\\naccess is achieved. The \\u201Ctime to achieve elevated access\\u201D will be\\ncalculated via the delta between access and acquisition of an elevated\\nprivilege. The report will include a description of the exploitation\\nmethod and maneuver. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" analysis will categorize tool sophistication as\\neither Novice or Advanced. The overall integrity protection rating will\\nbe based on a combination of the number of instances and each instance\\u2019s\\nimpact to the mission.\"), mdx(\"p\", null, \"Table C-12. Example of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Risk Based Cyber-Related Measure\\nWorksheet\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Cybersecurity\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Results\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rating\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Risk to Joint OH Data (JOD) Communications in the AOR Due to Cyber Effects\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Low risk\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"To Be Determined\"\n }, \"TBD\"), \"\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"To Be Determined\"\n }, \"TBD\"), \"\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Identified Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"References\"), \": Provide the requirement source (stated or derived).\\nSpecify the paragraph, section, line, etc. \", mdx(\"u\", null, \"The following is part of\\nthe example and references could be out of date.\")), mdx(\"p\", null, \"Derived from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo. 3 Apr 18, Procedures for Operational Test and\\nEvaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) of Cybersecurity in Acquisition Programs; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo,\\n27 Jul 16, Cybersecurity Operational Test and Evaluation Priorities and\\nImprovements; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Cybersecurity \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" Guidebook, Version 2.0 Change 1, 10\\nFeb 2020; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Cyber Test Guide, XX Dec 2020\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Scope\"), \": This measure evaluates the risk to JOD\\u2019s ability to enable\\nsecure and survivable communications in a contested cyberspace\\nenvironment. The risk must be \\u201Clow\\u201D. The test team will determine the\\nrisk rating by evaluation the likelihood of an adversary exploiting\\nvulnerabilities and the resulting impact to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enhanced Polar System\"\n }, \"EPS\"), \"\\u2019 ability to enable\\nsecure and survivable communications in a contested cyberspace\\nenvironment.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Methodology\"), \": The test team mapped the mission of JOD to mission\\nessential functions and the components which support their operation.\\nThis nodal analysis will allow the test team to identify critical nodes\\nwithin JOD. Using this information the test team will commission the\\n346TS to conduct a cooperative vulnerability and penetration assessment\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \") before integrated test activities (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"). The test team will\\ncommission the 177 IAS, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Agency\"\n }, \"NSA\"), \" certified cyber red team, to conduct an\\nadversarial assessment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \") during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \".\"), mdx(\"p\", null, \"The test team will evaluate the risk of cyber-effects to JOD\\u2019s ability\\nto enable secure and survivable communications in a contested cyberspace\\nenvironment as follows:\"), mdx(\"p\", null, \"Table C-13. Example of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Risk Based Cyber-Related Measure\\nWorksheet\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Likelihood\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"1\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Near Certain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Impact\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Catastrophic\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High Risk\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Major\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Moderate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"1\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")))), mdx(\"p\", null, \"Table C-14\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Level\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Likelihood\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Description\"))), 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 }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Little to no capability for adversary to exploit\")), 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 }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High cost for adversary to exploit\")), 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 }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium cost for adversary to exploit\")), 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 }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low cost for adversary to exploit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Near Certain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Little to no cost for adversary to exploit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Level\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Impact\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Description\")), 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 }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Little to no mission degradation\")), 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 }, \"Moderate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Partial mission degradation\")), 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 }, \"Major\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Critical mission degradation\")), 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 }, \"Catastrophic\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Complete mission failure\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Design\"), \": Uses overarching \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" test design.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data and Analysis\"), \": Data will consist of results from the Mission\\nRisk Assessment Process for Cyber (MRAP-C), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \". During\\ntest execution, the test team will also collect performance data for all\\nmeasures within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \".\"), mdx(\"p\", null, \"The test team will record all data on test team logs and will store all\\nresults in the appropriately classified test team \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E database. Where\\nunable to collect quantitative data, the test team will collect end user\\nand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" qualitative data. The test team will collect data according to\\neach measure within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1. The test team will note periods of time when\\ncyber-effects were generated by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \" team. After test execution, the\\ntest team will evaluate the impacts of disruptive and non-disruptive\\ncyber-effects to each measure within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1. The test team will consult\\nwith \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2 to determine the likelihood of the demonstrated and\\nspeculated cyber-effects from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \". The test team will then provide a\\nrisk rating of each effect. Using each risk rating as input, the test\\nteam will then provide the overall risk rating to this measure.\"), mdx(\"p\", null, \"[1]\", \" Cyber test and evaluation is a rapidly evolving concept. Be sure to\\nreference the most current guidance as it may change more frequently\\nthan this \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Measures Guide.\"), mdx(\"p\", null, \"[2]\", \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Cybersecurity Test and Evaluation Guidebook, Version 2.0, Change\\n1, 10 Feb 20\"), mdx(\"p\", null, \"[3]\", \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Institute of Standards and Technology\"\n }, \"NIST\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Plan OR Special Publication\"\n }, \"SP\"), \" 800-12, \\u201CAn Introduction to Information Security,\\u201D Rev. 1,\\nJun 17\"), mdx(\"p\", null, \"[4]\", \" System Survivability Key Performance Parameter (SS \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \") Pillars are\\ndefined in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Chiefs of Staff\"\n }, \"JCS\"), \" Cyber Survivability Endorsement Implementation Guide,\\nVersion 1.01\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#section-1-fundamentals-of-measurement","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT","items":[{"url":"#measures-overview","title":"Measures Overview"},{"url":"#qualities-of-a-good-measure-set","title":"Qualities of a Good Measure Set"}]},{"url":"#section-2-measures-development","title":"SECTION 2 MEASURES DEVELOPMENT","items":[{"url":"#developing-moes","title":"Developing MOEs"},{"url":"#developing-mops-and-moss","title":"Developing MOPs and MOSs"}]},{"url":"#section-3-measure-documentation","title":"SECTION 3 MEASURE DOCUMENTATION","items":[{"url":"#measures-worksheet-overview","title":"Measures Worksheet Overview"},{"url":"#measures-worksheet-header","title":"Measures Worksheet Header"},{"url":"#body-of-the-measures-worksheet","title":"Body of the Measures Worksheet"},{"url":"#formatting-measures","title":"Formatting Measures"}]},{"url":"#appendix-a-categories-of-measures","title":"APPENDIX A CATEGORIES OF MEASURES","items":[{"url":"#continuous-measures","title":"Continuous Measures"},{"url":"#discrete-measures","title":"Discrete Measures"},{"url":"#composite-measures","title":"Composite Measures"}]},{"url":"#appendix-b-measure-review-quick-reference","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"},{"url":"#appendix-c-cyber-related-measures","title":"APPENDIX C CYBER-RELATED MEASURES","items":[{"url":"#measures-overview-1","title":"Measures Overview"},{"url":"#composite-measures-1","title":"Composite Measures"}]}]},"parent":{"__typename":"File","relativePath":"fn_guides/measures_guide.md"},"frontmatter":{"metaTitle":"Measures Guide","metaDescription":"Measures Guide"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"4de3df85-165d-5b6f-94c9-f1237b3cb3dd"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/fn_guides/page-data.json b/sites/oteguide/page-data/fn_guides/page-data.json index 27d50e44..3f272597 100644 --- a/sites/oteguide/page-data/fn_guides/page-data.json +++ b/sites/oteguide/page-data/fn_guides/page-data.json @@ -1 +1 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"e30a421f-fdbf-57cf-9340-9081dc8822ac","title":"Functional Guides","slug":"/fn_guides"},"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\": \"Functional Guides\",\n \"metaTitle\": \"Functional Guides\",\n \"metaDescription\": \"Functional Guides\"\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, \"Following is a list of functional guides and tools detailing the \\\"how\\\"\\nof conducting operational testing. The list is not all-inclusive and is\\ndynamic; Directorates and Detachments may have additional functional\\nguides and tools. Use these functional guides and tools in conjunction\\nwith this edition for comprehensive \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E guidance.\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Bolded items are here in the menu.\"))), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"em\", {\n parentName: \"td\"\n }, \"Italicized items don't exist yet.\"))), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Linked items are \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Controlled Unclassified Information\"\n }, \"CUI\"), \" and exist on our SharePoint site.\")))), mdx(\"br\", null), mdx(\"br\", null), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct Guide\"), \". Provides techniques for developing initial\\nportions of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct: mission statement, COIs, operations,\\nbattlespace conditions, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Accreditation Guide\"), \". Discusses processes that support accreditation, including the verification and validation required.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Analyst Test Design Guide\"), \". Focuses on particular techniques and methods for designing the test events based on goals of a test.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Editing Guide\"), \". How to do Technical Editing. Applicable for any report, and writing in general.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Evaluation and Reporting Guide.\"), \" Outlines methods for evaluating\\nparts of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct and various forms for how to communicate\\n(reporting) feedback and results of testing.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Lessons Learned Guide\"), \". Provides the process for capturing and incorporating lessons learned into \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures Guide\"), \". Details types of measures, how to develop them, and the grammar to use when writing measures.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Safety Risk Management Guide\"), \". Describes procedures for identifying and managing risks for test activities.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Strategy, Planning, and Programming Process (SP3) Guide\"), \". An overview of the process for both short and long term plans. The SP3 plans are constantly updated and revised.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Capabilities Guide\"), \". Outlines documenting and acquiring test capabilities, both immediate and long-lead, to support testing.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Execution Guide.\"), \" Details the real-time processes of executing\\ntest events.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"a\", {\n parentName: \"strong\",\n \"href\": \"https://usaf.dps.mil/:w:/r/sites/AFOTEC-PRIVATE/mainlibrary/oteguide/Shared%20Documents/Functional%20Guides/AFOTEC%20Cyber%20Support%20Package%20Guide.docx?d=wa256f83b0e4c475485e72f4a383f81a3&csf=1&web=1&e=C2RUBJ\"\n }, \"Cyber Support Package\\nGuide\"), \".\"), \" Discusses cyber participation and activities throughout the life of a program.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"a\", {\n parentName: \"strong\",\n \"href\": \"https://cs2.eis.af.mil/sites/10008/library/jobaidsguides/AFOTEC%20RALOT%20Guide%20Template.dotx?Web=1\"\n }, \"Risk Assessment and Level of Test (\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \")\\nGuide\")), \"\\nDetails when and how to conduct a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \" to guide the degree of expected\\nreporting.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"fn_guides.md"},"frontmatter":{"metaTitle":"Functional Guides","metaDescription":"Functional Guides"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"e30a421f-fdbf-57cf-9340-9081dc8822ac"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"e30a421f-fdbf-57cf-9340-9081dc8822ac","title":"Functional Guides","slug":"/fn_guides"},"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\": \"Functional Guides\",\n \"metaTitle\": \"Functional Guides\",\n \"metaDescription\": \"Functional Guides\"\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, \"Following is a list of functional guides and tools detailing the \\\"how\\\"\\nof conducting operational testing. The list is not all-inclusive and is\\ndynamic; Directorates and Detachments may have additional functional\\nguides and tools. Use these functional guides and tools in conjunction\\nwith this edition for comprehensive \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E guidance.\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Bolded items are here in the menu.\"))), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"em\", {\n parentName: \"td\"\n }, \"Italicized items don't exist yet.\"))), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Linked items are \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Controlled Unclassified Information\"\n }, \"CUI\"), \" and exist on our SharePoint site.\")))), mdx(\"br\", null), mdx(\"br\", null), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct Guide\"), \". Provides techniques for developing initial\\nportions of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct: mission statement, COIs, operations,\\nbattlespace conditions, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Accreditation Guide\"), \". Discusses processes that support accreditation, including the verification and validation required.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Analyst Test Design Guide\"), \". Focuses on particular techniques and methods for designing the test events based on goals of a test.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Editing Guide\"), \". How to do Technical Editing. Applicable for any report, and writing in general.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Evaluation and Reporting Guide.\"), \" Outlines methods for evaluating\\nparts of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct and various forms for how to communicate\\n(reporting) feedback and results of testing.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Lessons Learned Guide\"), \". Provides the process for capturing and incorporating lessons learned into \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures Guide\"), \". Details types of measures, how to develop them, and the grammar to use when writing measures.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Safety Risk Management Guide\"), \". Describes procedures for identifying and managing risks for test activities.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Strategy, Planning, and Programming Process (SP3) Guide\"), \". An overview of the process for both short and long term plans. The SP3 plans are constantly updated and revised.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Capabilities Guide\"), \". Outlines documenting and acquiring test capabilities, both immediate and long-lead, to support testing.\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Test Execution Guide.\"), \" Details the real-time processes of executing\\ntest events.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"a\", {\n parentName: \"strong\",\n \"href\": \"https://usaf.dps.mil/:w:/r/sites/AFOTEC-PRIVATE/mainlibrary/oteguide/Shared%20Documents/Functional%20Guides/AFOTEC%20Cyber%20Support%20Package%20Guide.docx?d=wa256f83b0e4c475485e72f4a383f81a3&csf=1&web=1&e=C2RUBJ\"\n }, \"Cyber Support Package\\nGuide\"), \".\"), \" Discusses cyber participation and activities throughout the life of a program.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"a\", {\n parentName: \"strong\",\n \"href\": \"https://cs2.eis.af.mil/sites/10008/library/jobaidsguides/AFOTEC%20RALOT%20Guide%20Template.dotx?Web=1\"\n }, \"Risk Assessment and Level of Test (\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \")\\nGuide\")), \"\\nDetails when and how to conduct a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Assessment Level of Test\"\n }, \"RALOT\"), \" to guide the degree of expected\\nreporting.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"fn_guides.md"},"frontmatter":{"metaTitle":"Functional Guides","metaDescription":"Functional Guides"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"e30a421f-fdbf-57cf-9340-9081dc8822ac"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/fn_guides/safety_risk_mgmt_guide/page-data.json b/sites/oteguide/page-data/fn_guides/safety_risk_mgmt_guide/page-data.json deleted file mode 100644 index cb1d2354..00000000 --- a/sites/oteguide/page-data/fn_guides/safety_risk_mgmt_guide/page-data.json +++ /dev/null @@ -1 +0,0 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides/safety_risk_mgmt_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"c5df5c25-1ef6-598e-aee3-434fc797a055","title":"Safety Risk Management Guide","slug":"/fn_guides/safety_risk_mgmt_guide"},"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\": \"Safety Risk Management Guide\",\n \"metaTitle\": \"Safety Risk Management Guide\",\n \"metaDescription\": \"Safety Risk Management Guide\"\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, \"Last Updated/Reviewed: 08 December 2020\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \"\"), mdx(\"h1\", null, \"ENVIRONMENT, SAFETY AND OCCUPATIONAL HEALTH\"), mdx(\"p\", null, \"The three basic principles of environment, safety, and occupational\\nhealth (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \") are to sustain readiness, leverage resources, and be a\\ngood neighbor. The test director (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \") is responsible for providing a\\nsafe and healthy workplace during test execution, enhancing mission\\naccomplishment, preserving resources and minimizing risks--on and off\\nthe installation or public lands. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Safety (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \") supports these\\nresponsibilities with subject matter experts (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \") assigned to the\\ncore/test teams. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" will assist the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and the team in\\nnavigating \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" statutory compliance, the database/tools, planning\\nprocess, health and safety plan development, Integrated Safety Review\\nBoards (ISRB), and ultimately the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" Certification Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \") (if\\nrequired) for each test activity.\"), mdx(\"h1\", null, \"Safety Database and Tools\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" uses a safety database as the starting point for every \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\nactivity and the ticket to a safe, compliant activity. It is comprised\\nof a collection of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" tools that includes standard work templates,\\nsystems safety analysis databases, \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"test team exposure identification\\ntools\"), \" , Integrated Safety Reviews, and the formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" certification\\nprocess, which ultimately results in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" certification for dedicated\\noperational test. The system aggregates data through the life of a\\nprogram, maintains individual records of each test activity, certifies\\nsafety and environmental planning, and supports the \\\"Readiness for\\nDedicated Operational Test\\\" decision. Upon receipt of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Tasking\\nOrder or notification of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" experiment participation, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" will initiate a new database entry for the core (or experimentation)\\nteam to capture known technology and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" factors and develop an initial\\ntechnology risk assessment. Then, as the test team develops each\\noperational test concept, \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"the safety office \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" will initiate an\\nactivity-specific integrated safety review for each test activity\"), \" .\\nThe process will be available to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and has the capability to branch\\nout to safety SMEs and other test experts as required to accomplish a\\nthorough analysis and develop the identified hazard list with\\nmitigations. Early initiation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" database is critical to allow\\nadequate time to request environmental analysis and scope test risks.\\nSince complex environmental analyses can take years to complete, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"\\nshould consult with the safety office \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" early in to determine whether\\na \\\"long pole\\\" may exist. The system connects the team and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" SMEs to\\ndevelop risk factors, assess installation environmental documentation,\\nand determine the test activity risk level. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" database facilitates all\\nof these phases and builds the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \".\"), mdx(\"h1\", null, \"Planning and Review Process\"), 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\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" assigns safety SMEs to advise and consult on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \"-related\\nmatters with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", Detachment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"), and Experimentation Office (EX)\\ntest team's designated safety point-of-contact (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \"), and attends\\nprogram/experiment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" meetings. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" leads the initial\\ntechnological safety review in pre-planning phases and guides the test\\nteams during site safety and environmental compliance planning for test\\nexecution. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" review composition is tailorable. Consider including\\nthe program office, sponsor, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test team safety \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \",\\nand others as needed. Safety-related concerns are normally identified\\nduring \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" planning, combined \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events, experimentation activities,\\nand at system safety working group meetings or system safety design\\nreview meetings. Identified hazards must be controlled or mitigated to\\nacceptable levels before start of test, which is the purpose of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \"\\ndatabase.\"), mdx(\"h1\", null, \"Health and Safety Plan\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" uses the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" database to build the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" interactively with the\\ntest team. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" covers environmental and occupational health and\\nsafety issues while documenting compliance with laws and regulations. It\\nis the key document evaluated by the ISRB, or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" for Dedicated\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"'s (or onsite responsible person's) daily\\npretest/deployment briefing guide. When used, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" assures statutory\\ncompliance and produces a solid foundation for test site risk management\\nconsiderations.\"), mdx(\"p\", null, \"Hazards are identified in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \", each with an initial risk level (low,\\nmedium, high, and extremely high) that is controlled or mitigated, as\\nwell as feasible to reduce the risk. Table 1 is an aid tailored from\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Pamphlet\"\n }, \"AFPAM\"), \" 90-803, \", 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,\"), \" used to\\nassess \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" risk levels for each type of hazard.\"), mdx(\"p\", null, \"Table 1. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" Mission Impact Matrix\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Mishap Risk Index\"), mdx(\"th\", null, \"AFOTEC Mission Impact\"), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Severity Probability\"), mdx(\"td\", null, \"I-Catastrophic\"), mdx(\"td\", null, \"II-Critical\"), mdx(\"td\", null, \"III-Moderate\"), mdx(\"td\", null, \"IV-Negligible\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"A \\u2013 Frequent\"), mdx(\"td\", null, \"Severe\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"B \\u2013 Likely\"), mdx(\"td\", null), mdx(\"td\", null, \"Substantial\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"C \\u2013 Occasional\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"Minimal\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"D \\u2013 Seldom\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"No impact\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"E \\u2013 Unlikely\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Risk Assessment Value (AFPAM90-803)\")), mdx(\"td\", null, mdx(\"strong\", null, \"Technology (Mil Std 882E)\")), mdx(\"td\", null, mdx(\"strong\", null, \"Impact to Test Activities\")), mdx(\"td\", null, mdx(\"strong\", null, \"ESOH Impact Acceptance Level\")), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Extremely High\"), mdx(\"td\", null, \"High\"), mdx(\"td\", null, \"Severe\"), mdx(\"td\", null, \"AFOTEC/CC\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"High\"), mdx(\"td\", null, \"Serious\"), mdx(\"td\", null, \"Substantial\"), mdx(\"td\", null, \"Det/EX/CC\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Medium\"), mdx(\"td\", null, \"Medium\"), mdx(\"td\", null, \"Minimal\"), mdx(\"td\", null, \"Det/EX/DO\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Low\"), mdx(\"td\", null, \"Low\"), mdx(\"td\", null, \"No\"), mdx(\"td\", null, \"Det/EX/TD\"), mdx(\"td\", null)))), mdx(\"p\", null, \"This is a subjective process and should not be confused with the\\ndeficiency report (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deficiency Report\"\n }, \"DR\"), \") or system safety processes. Residual risk is the\\nremaining mishap risk that exists after control measures are in place.\\nThe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" finally considers all residual risks to assess an overall risk\\nlevel for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" mission impact to test activities, which in turn\\ndetermines the risk acceptance authority. The appropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" mission\\nimpact risk acceptance decision authority for low risk---no \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" impact\\nto test activities is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/EX \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"; for medium risk---minimal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \"\\nimpact to test activities is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/EX DO; and for high\\nrisk---substantial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" impact to test activities is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" or EX\\nDirector. 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\"), \" is the risk acceptance authority for extremely\\nhigh risk---severe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" impact to test activities. The decision\\nauthority can accept the risk and proceed, or elevate (or consult other\\ngeneral officers prior to making a risk decision in the case of 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\"), \") the decision to the next higher authority. When an identified\\nhazard's control measures cannot be implemented, the risk level reverts\\nback to the initial (higher) risk, which in turn may require elevating\\nthe risk decision authority level before proceeding with the activity.\"), mdx(\"h1\", null, \"Integrated Safety Review Board\"), mdx(\"p\", null, \"The Integrated Safety Review Board (ISRB) assembles to consider all\\nknown \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" risk factors prior to all operational test activities with\\nthe exception of formal Dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. The ISRB reviews all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" data\\nand analysis known at the time. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" works with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" and\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/EX test team's safety \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" to prepare and coordinate the ISRB,\\nwhich the safety office chairs. The ISRB may be conducted in person, or\\nvia teleconference or video teleconference. The board structure is\\ntailorable to the programmatic or experiment situation. The ISRB focuses\\ntest team personnel exposure, and the early (preliminary) safety hazards\\nof the operational test activity. The board uses an Independent Safety\\nReview Exposure Identification Tool (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Influence Team\"\n }, \"EIT\"), \") to determine operational test\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" hazards likely to be present during those activities. Examples of\\nthese activities are: Contractor or Development Test Observations,\\nOperational Assessments (outside the purview of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63-119),\\nDemonstrations, Experiments or any other similar test activities.\"), mdx(\"h1\", null, \"Environment, Safety and Occupational Health Certification Board\"), mdx(\"p\", null, \"The Environment, Safety and Occupational Health Certification Board\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \") assembles to consider all outstanding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" risk factors, to\\nformalize the risk acceptance decision authority, and to certify the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" analyses in a certification memorandum for Dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" follows direction outlined in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63-119, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Certification of\\nSystem Readiness for Dedicated Operational Testing\"), \" , Atch 23,\\n\\\"Integrated Technical, Health, and Safety Reviews.\\\" The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" is\\naccomplished prior to dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" works with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test team's safety \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" to prepare and coordinate the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \", which the safety office chairs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" may be conducted in\\nperson, or via teleconference or video teleconference. The board\\nstructure is tailorable to the programmatic situation. For example, for\\nan \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \"-controversial program, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" could demand a formal meeting\\nwith multiple attendees; whereas, for a well-structured and\\nwell-documented program with significant but acknowledged risks, a\\nteleconference between the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", test team safety \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \",\\nDirector of Safety, and the risk acceptance authority could suffice. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" focuses on the safety of test, technology, and environment as\\nthey pertain to the scope of the test activities. The Board pays\\nparticular attention to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" as the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"'s primary \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" field source\\nfor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" hazards and mitigations, and emergency and mishap\\nnotifications. Additional sources include: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63-119, ITHSR,\\nAttachment 23, criteria; safety DRs; environmental considerations;\\ndeployment issues; system safety deficiencies related to the system\\nunder test; occupational health; infrastructure support requirements;\\nand others.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" gives the test activity an overall risk assessment based on\\nidentified hazards and mitigations applied. Then, the Board considers\\nthe potential impact of those risks on test activities. Table 2 outlines\\nthe different levels of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \"-related hazard risks and their impact to\\ntest activities, and establishes the appropriate risk decision\\nauthority.\"), mdx(\"p\", null, \"Table 2. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" Mission Impact Risk Levels and Acceptance\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"No Mission Impact:\"), mdx(\"br\", null), \"No ESOH hazards have been identified that impact test activities. Known hazards identified have been adequately controlled (mitigated) to acceptable levels. The potential ESOH-related capability impacts are negligible. The Test Director or higher is the risk decision authority to accept the hazard controls.\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Minimal Mission Impact:\"), mdx(\"br\", null), \"Some ESOH hazards have been identified with minimal impact on test activities. Known hazards have been adequately identified and controlled (mitigated) to an acceptable level. Some conditions will not be resolved prior to the test but sufficient mitigation measures are in place to reduce the operational objective limitations. The Detachment Director of Operations or higher is the appropriate level to accept the limitations.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Substantial Mission Impact:\"), mdx(\"br\", null), \"Some ESOH hazards have been identified with substantial impact on test activities. Known hazards have been adequately identified and the majority were resolved or mitigated. ESOH-related operational objective impacts were mitigated to acceptable levels. Some will not be resolved by test completion that may limit mission capability and may potentially influence affected test results. The Detachment Commander or higher is the appropriate level to accept and manage the limitations.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Severe Mission Impact:\"), mdx(\"br\", null), \"There are ESOH shortfalls identified with severe impact on test activities. The majority of known hazards have been identified and controlled (mitigated) to an acceptable level. However, some ESOH-related operational objectives have the potential to limit test capabilities and will not be resolved in time. If it is deemed necessary to proceed with the test considering these significant limitations, it may be appropriate that Senior (General Officer) level external involvement occur along with the AFOTEC Commander accepting responsibility to proceed with test execution.\")))), mdx(\"p\", null, \"The Director of Safety assigns the final risk in the form of a\\ncertification memorandum (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" Memo) and signs the memo. The\\nappropriate risk decision authority for the test activity will accept\\nthe risk and endorse the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" Memo. After risk acceptance, a copy of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" Memo will be forwarded as \\\"info\\\" to the next higher decision\\nauthority as level of risk dictates (i.e., \", 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\"), \" to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/DO to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" to\\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\"), \"). Coordination and approval of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" Memo will be\\naccomplished prior to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activities.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#environment-safety-and-occupational-health","title":"ENVIRONMENT, SAFETY AND OCCUPATIONAL HEALTH"},{"url":"#safety-database-and-tools","title":"Safety Database and Tools"},{"url":"#planning-and-review-process","title":"Planning and Review Process"},{"url":"#health-and-safety-plan","title":"Health and Safety Plan"},{"url":"#integrated-safety-review-board","title":"Integrated Safety Review Board"},{"url":"#environment-safety-and-occupational-health-certification-board","title":"Environment, Safety and Occupational Health Certification Board"}]},"parent":{"__typename":"File","relativePath":"fn_guides/safety_risk_mgmt_guide.md"},"frontmatter":{"metaTitle":"Safety Risk Management Guide","metaDescription":"Safety Risk Management Guide"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"c5df5c25-1ef6-598e-aee3-434fc797a055"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/fn_guides/strat_planning_programming_guide/page-data.json b/sites/oteguide/page-data/fn_guides/strat_planning_programming_guide/page-data.json deleted file mode 100644 index 941874c2..00000000 --- a/sites/oteguide/page-data/fn_guides/strat_planning_programming_guide/page-data.json +++ /dev/null @@ -1 +0,0 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides/strat_planning_programming_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"fc3e7111-5e81-55b8-ae6f-6c7a739bf515","title":"Strategy, Planning, and Programming Guide","slug":"/fn_guides/strat_planning_programming_guide"},"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\": \"Strategy, Planning, and Programming Guide\",\n \"metaTitle\": \"Strategy, Planning, and Programming Guide\",\n \"metaDescription\": \"Strategy, Planning, and Programming Guide\"\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, \"Last Updated/Reviewed: 28 October 2020\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-5/8\"), mdx(\"h1\", null, \"STRATEGY, PLANNING, AND PROGRAMMING PROCESS\"), mdx(\"p\", null, \"The Strategy, Planning, and Programming Process (SP3) is located on the\\nA-5/8 shared drive. References include a Guide and a Process Chart that\\nA-5/8 periodically updates.\"), mdx(\"p\", null, \"SP3 is the means by which \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" generates its short and long term\\nplans, assesses the risks to those plans, and identifies the actions\\nneeded to reduce risk and achieve the plans. The process is repeatable,\\ndefined, defendable and transparent, and provides timely \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nCommander engagement. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A5/8 is the responsible SP3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\norganization. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SP3 incorporates \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" guidance and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nCommander's guidance to produce three basic products: the annual Program\\nObjective Memorandum (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \") submission to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters Air Force\"\n }, \"HAF\"), \"; the annual Planning\\nChoices submission to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters Air Force\"\n }, \"HAF\"), \"; and a prioritized Time-Phased Investment\\nDocument (T\\u2011PhID) document for submission to the various \", 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\\nInfrastructure resource organizations.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \" provides resource allocation decisions in response to strategic\\nplanning and programming guidance. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \" is a major document in the\\nPlanning, Programming, Budgeting, and Execution (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Planning, Programming, Budgeting, and Execution\"\n }, \"PPBE\"), \") process, and is\\nthe basis for budget estimates. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \" is the principal programming\\ndocument that proposes how a Component will respond to the Defense\\nPlanning Guidance (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Planning Guidance\"\n }, \"DPG\"), \") and satisfy assigned functions over the Future\\nYears Defense Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Future Years Defense Program\"\n }, \"FYDP\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A5/8 submits the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nCommander-approved \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \" summarizing required manpower, resources, and\\nequipment associated with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" operational test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \") mission.\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"(\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" A-8P)\")), mdx(\"p\", null, \"The Planning Choices submission is similar to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \", and provides\\nfuture resource allocation decisions in response to strategic planning\\nand programming guidance for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Future Years Defense Program\"\n }, \"FYDP\"), \" beyond the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \". In general, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"\\nCorporate process uses Planning Choice decisions to inform \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \"\\nsubmissions. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \" submissions must support future \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" force structure and\\nposture designs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A5/8 submits the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander-approved\\nPlanning Choices summarizing manpower, resources, and equipment\\nassociated with the \", 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\"), \" mission. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"(\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" A-8P)\")), mdx(\"p\", null, \"The prioritized Time-Phased Investment Document (T-PhID) document is\\nprovided to various \", 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\\norganizations. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" owns almost no test assets, and must rely on other\\n\", 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 assist in developing, managing, and\\nsustaining solutions. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A5/8 submits the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander-approved,\\nprioritized T-PhID requirements document to appropriate resource\\norganizations. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"(POCs: A-5R and A-8Z)\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#strategy-planning-and-programming-process","title":"STRATEGY, PLANNING, AND PROGRAMMING PROCESS"}]},"parent":{"__typename":"File","relativePath":"fn_guides/strat_planning_programming_guide.md"},"frontmatter":{"metaTitle":"Strategy, Planning, and Programming Guide","metaDescription":"Strategy, Planning, and Programming Guide"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"fc3e7111-5e81-55b8-ae6f-6c7a739bf515"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/fn_guides/test_capability_guide/page-data.json b/sites/oteguide/page-data/fn_guides/test_capability_guide/page-data.json deleted file mode 100644 index 2a8518b5..00000000 --- a/sites/oteguide/page-data/fn_guides/test_capability_guide/page-data.json +++ /dev/null @@ -1 +0,0 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/fn_guides/test_capability_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"aec8f459-af89-5908-bf3b-102f6a4db590","title":"Test Capability Guide","slug":"/fn_guides/test_capability_guide"},"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 Capability Guide\",\n \"metaTitle\": \"Test Capability Guide\",\n \"metaDescription\": \"Test Capability Guide\"\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, \"31 July 2020\"), mdx(\"p\", null, \"Last Updated/Reviewed: 26 February 2021\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-5/8\"), mdx(\"h1\", null, \"PURPOSE\"), mdx(\"p\", null, \"Enable \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" and reduce risk by identifying, supporting, and advocating\\nfor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test capability requirements.\"), mdx(\"h2\", null, \"Definition\"), mdx(\"p\", null, \"The infrastructure or support system necessary to enable an operator to\\nexercise a system in a combat realistic environment to include threats\\nand targets for the purpose of conducting an operational test or\\nassessment and/or an integrated developmental/operational test.\"), mdx(\"h2\", null, \"Support Goals\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provide accurate reference data on test range and facilities\\ncapabilities.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provide research and analysis on existing test capabilities to\\nsupport operational test planning needs.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identify gaps in test capability that need to be filled to support\\nfuture operational test needs.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Prioritize, advocate, track, and report on solutions to test\\ncapability gaps.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provide feedback and support on weapons, munitions, and targets\\nplanning and allocation programming.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provide feedback on test resource plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \") requirements to ensure\\naccurate support levels are being planned for and reported.\"))), mdx(\"h1\", null, \"TEST RANGE AND FACILITY CAPABILITIES\"), mdx(\"p\", null, \"Provide reference information on the capabilities of test ranges and\\nfacilities to enable the planning and execution of operational tests and\\nassessments in combat realistic environments to include threats and\\ntargets.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Range and Facilities Database (Capabilities, POCs, etc)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Management Center\"\n }, \"TRMC\"), \" Database\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" List\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Range and Facilities Briefs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Range Commanders Council (RCC) Briefs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Program Introduction Documents (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Introduction Document\"\n }, \"PID\"), \")/Statement of Capability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Statement of Capabilities\"\n }, \"SOC\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"List of Training / Joint Exercises\"))), mdx(\"h1\", null, \"EXISTING TEST CAPABILITY IDENTIFICATION\"), mdx(\"p\", null, \"Provide support to test directors and the test team\\u2019s requests for test\\ncapability research and analysis, identifying existing test capabilities\\nto enable operational test planning and execution.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Capability Readiness Assessment\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Request a new \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessment\"\n }, \"TCRA\"), \" for your Test Program\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessment\"\n }, \"TCRA\"), \" Status Dashboard\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Completed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessment\"\n }, \"TCRA\"), \" Archive\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Nevada Test and Training Range Test Capabilities\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Contact A-8Z\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Capabilities Slide\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Briefing Template (Contact A-3)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Resource Plan support\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Mission Applications Suite\"\n }, \"AMAS\"), \" (SharePoint Link)\"))), mdx(\"h1\", null, \"TEST CAPABILITY GAP IDENTIFICATION\"), mdx(\"p\", null, \"Provide support to identify test capability gaps to support multiple\\noperational test programs. Leveraging Intelligence data, emerging\\ntechnologies research, and operator experience to document \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\ncapability current and future needs.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Threat Intelligence Research\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Validated Online Lifecycle Threat\"\n }, \"VOLT\"), \" & TTL (Contact A-2N)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Capability Gap Research\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Gap Database\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Team Input\"))), mdx(\"h1\", null, \"TEST CAPABILITY GAP SUPPORT AND REPORTING\"), mdx(\"p\", null, \"Provide support and advocate for projects which address \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\ncapability gaps. Supporting and tracking all applicable test capability\\ninvestment programs and the foreign material acquisition process.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Time-Phased Investment Document (T-PhID)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Monthly Report\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Capabilities Investment Programs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Central Test & Evaluation Investment Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Central Test & Evaluation Investment Program\"\n }, \"CTEIP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Joint Aircraft Survivability Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Aircraft Survivability Program\"\n }, \"JASP\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Resource Enhancement Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Resource Enhancement Program\"\n }, \"REP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Threat Systems Working Group (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Threat Systems Working Group\"\n }, \"TSWG\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Investment Planning and Programming (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Investment Planning and Programming\"\n }, \"TIPP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Foreign Material Acquisition (FMA)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Submission\"))), mdx(\"h1\", null, \"MUNITIONS MANAGEMENT\"), mdx(\"p\", null, \"Provide support to test directors and the test teams to properly\\nforecast ammunitions, munitions, and aerial targets necessary to plan\\nand execute operational tests and assessments.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions, Missiles, and Target\"\n }, \"MMT\"), \" Allocation Requests\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions, Missiles, and Target\"\n }, \"MMT\"), \" Support and Feedback on Test Resource Plans\"))), mdx(\"h1\", null, \"TEST RESOURCE PLAN REQUIREMENTS VERIFICATION AND FEEDBACK\"), mdx(\"p\", null, \"Provide support to test teams by soliciting, tracking, and reporting\\ntest resource needs and enabling program objective memorandum (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \")\\ninputs, the Resource Requirements Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \"), and data justification\\nfor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \" funding letters.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Resource Plan Support\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Mission Applications Suite\"\n }, \"AMAS\"), \" (Contact \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and/or A-8P)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Review Board\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \" Funding Letters\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Contractor Request Review Panel\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#purpose","title":"PURPOSE","items":[{"url":"#definition","title":"Definition"},{"url":"#support-goals","title":"Support Goals"}]},{"url":"#test-range-and-facility-capabilities","title":"TEST RANGE AND FACILITY CAPABILITIES"},{"url":"#existing-test-capability-identification","title":"EXISTING TEST CAPABILITY IDENTIFICATION"},{"url":"#test-capability-gap-identification","title":"TEST CAPABILITY GAP IDENTIFICATION"},{"url":"#test-capability-gap-support-and-reporting","title":"TEST CAPABILITY GAP SUPPORT AND REPORTING"},{"url":"#munitions-management","title":"MUNITIONS MANAGEMENT"},{"url":"#test-resource-plan-requirements-verification-and-feedback","title":"TEST RESOURCE PLAN REQUIREMENTS VERIFICATION AND FEEDBACK"}]},"parent":{"__typename":"File","relativePath":"fn_guides/test_capability_guide.md"},"frontmatter":{"metaTitle":"Test Capability Guide","metaDescription":"Test Capability Guide"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"aec8f459-af89-5908-bf3b-102f6a4db590"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/glossary/page-data.json b/sites/oteguide/page-data/glossary/page-data.json index 92e9acb4..f81de885 100644 --- a/sites/oteguide/page-data/glossary/page-data.json +++ b/sites/oteguide/page-data/glossary/page-data.json @@ -1 +1 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/glossary","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"bedf1131-0f55-53e9-918e-2b089446aa1b","title":"Glossary","slug":"/glossary"},"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\": \"Glossary\",\n \"metaTitle\": \"Appendix B\",\n \"metaDescription\": \"Glossary\"\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(\"strong\", {\n parentName: \"p\"\n }, \"Acquisition Decision Memorandum.\"), \" The milestone decision authority\\napproves the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Decision Memorandum\"\n }, \"ADM\"), \" and the program office releases it. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Decision Memorandum\"\n }, \"ADM\"), \" documents\\nthe decisions and exit criteria established for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" decision or\\nin-process reviews. It specifies what is done during the next\\nacquisition phase.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Analysis of Alternatives.\"), \" The user develops the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \", which is\\nconducted following a concept decision and validation of the initial\\ncapabilities 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\"), \". The focus of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" is to refine the concept documented in the validated \", 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\"), \".\\nThe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" assesses critical technologies associated with these concepts,\\nincluding technology maturity, technology risk and, if necessary,\\ntechnology maturation and demonstration needs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" to\\nunderstand critical areas that affect accomplishing an operational task.\\nOur participation in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" process allows us to play a key role in the\\nearly life of a program by gaining insight into its \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", mission\\ntasks, and model scenarios. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" can leverage information from\\nparticipating in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" mission effectiveness working group for early\\ninvolvement and early planning activities. A-3 developed a document\\nreview checklist to assist in reviewing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" documents.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Capability-Based Requirements Documents.\"), \" The user develops\\ncapability-based requirements documents. Typical requirements documents\\ninclude 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\"), \" and \", 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\"), \". Personnel involved in reviewing\\nICDs/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \" ICDs and CDDs/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \" CDDs can obtain additional training and\\ninformation regarding requirements development from the Defense\\nAcquisition University training website.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Concept of Operations.\"), \" The user produces the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", which documents\\nthe intended employment of forces and systems. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" is one of the\\ncornerstone documents used in planning \", 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. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" reviews it\\nto understand how the user plans to employ and support the system\\n(provides operational realism for the test), develop \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" scenarios, and\\ninject operational realism into \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Cybersecurity Strategy.\"), \" The program office writes the cybersecurity\\nstrategy, which provides documentation to \\\"ensure programs have an\\ninformation assurance strategy consistent with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" policies, standards\\nand architectures.\\\" The lead \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E organization is the office of\\ncollateral responsibility for the cybersecurity strategy. Prior to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" A,\\nthe cybersecurity strategy should identify the certification and\\naccreditation cybersecurity authorization process required by the\\nsystem. Ref: DoDI\\xA08510.01, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Risk Management Framework (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Risk Management Framework\"\n }, \"RMF\"), \") for \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \"\\nInformation Technology (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \")\"), \"; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Institute of Standards and Technology\"\n }, \"NIST\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Plan OR Special Publication\"\n }, \"SP\"), \" 800\\u201137, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Guide for Applying the\\nRisk Management Framework to Federal Information Systems\"), \", Rev. 1, Feb\\n10.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Information Support Plans.\"), \" The program office develops the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Support Plan\"\n }, \"ISP\"), \" for\\nall \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Category\"\n }, \"ACAT\"), \" and non-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Category\"\n }, \"ACAT\"), \" acquisitions and procurements. The plan describes\\nsystem dependencies and interface requirements in sufficient detail to\\nenable testing and verification of information technology (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \") and\\nNational Security System (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Space OR National Security Strategy OR National Security System\"\n }, \"NSS\"), \") interoperability and supportability\\nrequirements. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Support Plan\"\n }, \"ISP\"), \" also includes \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Space OR National Security Strategy OR National Security System\"\n }, \"NSS\"), \" interface descriptions,\\ninfrastructure and support requirements, standards profiles, measures of\\nperformance, and interoperability shortfalls.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"ISPs describe operational, system and technical architectures;\\nintelligence, spectrum, security, connectivity and interoperability\\nrequirements; communications and information manpower, training and\\nlogistics requirements; and shortfalls and solutions.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and Detachment cybersecurity analyst must track the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Support Plan\"\n }, \"ISP\"), \"'s\\ndevelopment because of the system-of-systems approach required by\\nthe plan. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Support Plan\"\n }, \"ISP\"), \" is an excellent source to gain knowledge of the\\nlarger picture for the system under test.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Joint Capability Technology Demonstration.\"), \" The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capability Technology Demonstration\"\n }, \"JCTD\"), \" process is an\\nadvanced technology development (pre-acquisition) process that provides\\na mechanism to rapidly field limited numbers of systems to meet urgent\\nmilitary needs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" becomes involved in a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capability Technology Demonstration\"\n }, \"JCTD\"), \" program \\\"by request\\\"\\nvia the normal involvement determination process, which is expedited and\\ntailored as necessary. If 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 involvement, we begin\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" and tailor it to accommodate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capability Technology Demonstration\"\n }, \"JCTD\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Life Cycle Sustainment Plan.\"), \" The program office develops the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Sustainment Plan\"\n }, \"LCSP\"), \".\\nIt integrates the acquisition and sustainment strategies and provides\\nall support requirements of a system, subsystem, or major end item. It\\nreferences the systems engineering plan, which is designed to ensure\\nsupportability considerations are implemented during the design,\\ndevelopment, production, and sustainment of a weapon system. An\\neffective product support strategy establishes the initial foundation\\nfor the collaboration of acquisition and sustainment planning concepts\\nand allows for the eventual transfer of program management\\nresponsibility from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \"'s portfolio to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Life Cycle Management Center\"\n }, \"AFLCMC\"), \"'s portfolio. External\\nstaffing of LCSPs is inconsistent; therefore, notify A-3 if an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Sustainment Plan\"\n }, \"LCSP\"), \" is\\nsent to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" for staffing to ensure we accomplish sufficient internal\\ncoordination.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Effectiveness.\"), \" Measures designed to correspond to\\naccomplishment of mission objectives and achievement of desired results.\\nThey quantify the results to be obtained by a system and may be\\nexpressed as probabilities that the system will perform as required.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may be further decomposed into measures of performance and measures\\nof suitability. (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition Guidebook\"), \"). A criterion used to\\nassess changes in system behavior, capability, or operational\\nenvironment tied to measuring attainment of an end state, achievement of\\nan objective, or creation of an effect. (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 1-02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Dictionary of\\nMilitary and Associated Terms\"), \", As Amended through 15\\xA0Feb\\xA016)\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Performance.\"), \" Measure of a system's performance expressed\\nas speed, payload, range, time-on-station, frequency, or other\\ndistinctly quantifiable performance features. Several MOPs and/or MOSs\\nmay be related to the achievement of a particular \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \". (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense\\nAcquisition Guidebook\"), \")\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Suitability.\"), \" Measure of an item's ability to be supported\\nin its intended operational environment. MOSs typically relate to\\nreadiness or operational availability and, hence, reliability,\\nmaintainability, and the item's support structure. Several MOSs and/or\\nMOPs may be related to the achievement of a particular \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense\\nAcquisition Guidebook\"), \")\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission.\"), \" 1) The task, together with the purpose, that clearly\\nindicates the action to be taken and the reason therefore (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-0); 2)\\nIn common usage, especially when applied to lower military units, a duty\\nassigned to an individual or unit; a task (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-0); 3) The dispatching\\none or more aircraft to accomplish one particular task (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-30).\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission Effect.\"), \" The result, outcome, or consequence of an action, at\\nits appropriate mission level, typically tactical, represents the\\nmission effect or outcome. Mission effects are considered within the\\ncontext of concept of operations/operational mode summary/mission\\nprofile/employment. (derived from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 1-02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Department of Defense\\nDictionary of Military and Associated Terms,\"), \" As Amended through 15 Feb\\n16)\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Modeling and Simulation Support Plan.\"), \" The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" support plan developed\\nby the program office, captures all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" requirements over the life cycle\\nof an acquisition program, including those for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". TDs must\\nensure the program office provides all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" plans and reports, and\\nensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" requirements are included as early as possible, as part of\\nthe program office's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" funding strategy.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Requests for Proposal.\"), \" RFPs are issued by program offices that are\\nin negotiated acquisitions to communicate government requirements to\\nprospective contractors and to solicit proposals. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" personnel\\nensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E language is provided to the program office for inclusion in\\nRFPs.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Security Classification Guide.\"), \" The program office develops the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \"\\nto provide security instructions for military and civilian personnel\\nworking on a system. It is available from the program office and all\\ntest team members should read and understand it to avoid security\\nviolations. Be aware that multiple SCGs may apply when dealing with\\ncyber vulnerabilities and exploitability of a system and its\\ninterconnected infrastructures. Cyber and information operations SCGs\\n(e.g., \\\"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \" Cybersecurity Security Classification/Declassification\\nGuide for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Weapon Systems,\\\" 17 Apr 17; DoDI O-3600.02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Information\\nOperation Security Classification Guidance\"), \", 28 Nov 05; and US Cyber\\nCommand Instruction 5200-03, 15 Jun 16) take precedence over\\nsystem-specific SCGs and may require classifying the cybersecurity test\\nreport at the Secret Collateral or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sensitive Compartmented Information\"\n }, \"SCI\"), \" level. In the absence of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \",\\nor if an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \" does not adequately cover capabilities, vulnerabilities,\\nweaknesses, and limitations, test team members should contact \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Information Protection/SAP Security (office symbol)\"\n }, \"CVI\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"System Capability.\"), \" A system capability is comprised of multiple,\\nintegrated system functions. It is the system's ability to complete a\\ntask or execute a course of action under specified conditions and level\\nof performance. Capabilities, when combined, create the desired mission\\neffect.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"System Functions/Properties.\"), \" Functions are specific, single actions\\n(enabled by the structure) for which a component/module/etc. is\\ndesigned. Properties are inherent, designed attributes or\\ncharacteristics of system.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"System Structure.\"), \" System structure includes system layouts or\\nconfigurations, controls and displays, embedded features, and underlying\\narchitectures that are relatively fixed and stable.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test and Evaluation Master Plan.\"), \" The program office develops the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" with input from the OTAs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" documents the overall structure\\nand objectives of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" program. It provides the framework for\\ngenerating detailed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" plans, and documents schedule and resource\\nimplications associated with the program, including comparison testing\\nor a suitable alternative. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" contains many of the agreements\\namong participants and specifies the levels of funding for the test. It\\nalso documents all integrated test activities, as well the criteria we\\nwill use to determine readiness for the final phase of operational\\ntesting. To support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" A, the program must have a signed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \"; to\\nsupport \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" B, the program must have a draft update for the development\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \" release decision point. Programs that enter the acquisition process\\nat a point other than pre-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" A will have a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" (draft or signed)\\ncommensurate with that entry milestone's requirements. The program\\noffice will provide further iterations/updates of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \", as required,\\nfor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" C and full-rate production (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full-Rate Production\"\n }, \"FRP\"), \")/fielding decisions. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" will\\napprove the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" for oversight programs. A-3 developed a document review\\nchecklist to assist with reviewing TEMPs, which is posted on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\nIntranet Library.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Threat Assessment Products.\"), \" Our test teams use validated threat\\nproducts and threat models that the National Air and Space Intelligence\\nCenter (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Air and Space Intelligence Center\"\n }, \"NASIC\"), \") and the Missiles and Space Intelligence Center produce\\ncontinuously as threats evolve.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"glossary.md"},"frontmatter":{"metaTitle":"Appendix B","metaDescription":"Glossary"}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"bedf1131-0f55-53e9-918e-2b089446aa1b"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"componentChunkName":"component---src-templates-docs-js","path":"/glossary","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"bedf1131-0f55-53e9-918e-2b089446aa1b","title":"Glossary","slug":"/glossary"},"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\": \"Glossary\",\n \"metaTitle\": \"Appendix B\",\n \"metaDescription\": \"Glossary\"\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(\"strong\", {\n parentName: \"p\"\n }, \"Acquisition Decision Memorandum.\"), \" The milestone decision authority\\napproves the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Decision Memorandum\"\n }, \"ADM\"), \" and the program office releases it. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Decision Memorandum\"\n }, \"ADM\"), \" documents\\nthe decisions and exit criteria established for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" decision or\\nin-process reviews. It specifies what is done during the next\\nacquisition phase.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Analysis of Alternatives.\"), \" The user develops the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \", which is\\nconducted following a concept decision and validation of the initial\\ncapabilities 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\"), \". The focus of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" is to refine the concept documented in the validated \", 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\"), \".\\nThe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" assesses critical technologies associated with these concepts,\\nincluding technology maturity, technology risk and, if necessary,\\ntechnology maturation and demonstration needs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" to\\nunderstand critical areas that affect accomplishing an operational task.\\nOur participation in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" process allows us to play a key role in the\\nearly life of a program by gaining insight into its \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", mission\\ntasks, and model scenarios. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" can leverage information from\\nparticipating in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" mission effectiveness working group for early\\ninvolvement and early planning activities. A-3 developed a document\\nreview checklist to assist in reviewing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Analysis of Alternatives\"\n }, \"AoA\"), \" documents.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Capability-Based Requirements Documents.\"), \" The user develops\\ncapability-based requirements documents. Typical requirements documents\\ninclude 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\"), \" and \", 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\"), \". Personnel involved in reviewing\\nICDs/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \" ICDs and CDDs/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information System\"\n }, \"IS\"), \" CDDs can obtain additional training and\\ninformation regarding requirements development from the Defense\\nAcquisition University training website.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Concept of Operations.\"), \" The user produces the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", which documents\\nthe intended employment of forces and systems. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" is one of the\\ncornerstone documents used in planning \", 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. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" reviews it\\nto understand how the user plans to employ and support the system\\n(provides operational realism for the test), develop \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" scenarios, and\\ninject operational realism into \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Cybersecurity Strategy.\"), \" The program office writes the cybersecurity\\nstrategy, which provides documentation to \\\"ensure programs have an\\ninformation assurance strategy consistent with \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" policies, standards\\nand architectures.\\\" The lead \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"&E organization is the office of\\ncollateral responsibility for the cybersecurity strategy. Prior to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" A,\\nthe cybersecurity strategy should identify the certification and\\naccreditation cybersecurity authorization process required by the\\nsystem. Ref: DoDI\\xA08510.01, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Risk Management Framework (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Risk Management Framework\"\n }, \"RMF\"), \") for \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \"\\nInformation Technology (\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \")\"), \"; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Institute of Standards and Technology\"\n }, \"NIST\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Plan OR Special Publication\"\n }, \"SP\"), \" 800\\u201137, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Guide for Applying the\\nRisk Management Framework to Federal Information Systems\"), \", Rev. 1, Feb\\n10.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Information Support Plans.\"), \" The program office develops the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Support Plan\"\n }, \"ISP\"), \" for\\nall \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Category\"\n }, \"ACAT\"), \" and non-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Acquisition Category\"\n }, \"ACAT\"), \" acquisitions and procurements. The plan describes\\nsystem dependencies and interface requirements in sufficient detail to\\nenable testing and verification of information technology (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \") and\\nNational Security System (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Space OR National Security Strategy OR National Security System\"\n }, \"NSS\"), \") interoperability and supportability\\nrequirements. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Support Plan\"\n }, \"ISP\"), \" also includes \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Space OR National Security Strategy OR National Security System\"\n }, \"NSS\"), \" interface descriptions,\\ninfrastructure and support requirements, standards profiles, measures of\\nperformance, and interoperability shortfalls.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"ISPs describe operational, system and technical architectures;\\nintelligence, spectrum, security, connectivity and interoperability\\nrequirements; communications and information manpower, training and\\nlogistics requirements; and shortfalls and solutions.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and Detachment cybersecurity analyst must track the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Support Plan\"\n }, \"ISP\"), \"'s\\ndevelopment because of the system-of-systems approach required by\\nthe plan. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Support Plan\"\n }, \"ISP\"), \" is an excellent source to gain knowledge of the\\nlarger picture for the system under test.\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Joint Capability Technology Demonstration.\"), \" The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capability Technology Demonstration\"\n }, \"JCTD\"), \" process is an\\nadvanced technology development (pre-acquisition) process that provides\\na mechanism to rapidly field limited numbers of systems to meet urgent\\nmilitary needs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" becomes involved in a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capability Technology Demonstration\"\n }, \"JCTD\"), \" program \\\"by request\\\"\\nvia the normal involvement determination process, which is expedited and\\ntailored as necessary. If 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 involvement, we begin\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \" and tailor it to accommodate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Capability Technology Demonstration\"\n }, \"JCTD\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Life Cycle Sustainment Plan.\"), \" The program office develops the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Sustainment Plan\"\n }, \"LCSP\"), \".\\nIt integrates the acquisition and sustainment strategies and provides\\nall support requirements of a system, subsystem, or major end item. It\\nreferences the systems engineering plan, which is designed to ensure\\nsupportability considerations are implemented during the design,\\ndevelopment, production, and sustainment of a weapon system. An\\neffective product support strategy establishes the initial foundation\\nfor the collaboration of acquisition and sustainment planning concepts\\nand allows for the eventual transfer of program management\\nresponsibility from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \"'s portfolio to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Life Cycle Management Center\"\n }, \"AFLCMC\"), \"'s portfolio. External\\nstaffing of LCSPs is inconsistent; therefore, notify A-3 if an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Life Cycle Sustainment Plan\"\n }, \"LCSP\"), \" is\\nsent to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" for staffing to ensure we accomplish sufficient internal\\ncoordination.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Effectiveness.\"), \" Measures designed to correspond to\\naccomplishment of mission objectives and achievement of desired results.\\nThey quantify the results to be obtained by a system and may be\\nexpressed as probabilities that the system will perform as required.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may be further decomposed into measures of performance and measures\\nof suitability. (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense Acquisition Guidebook\"), \"). A criterion used to\\nassess changes in system behavior, capability, or operational\\nenvironment tied to measuring attainment of an end state, achievement of\\nan objective, or creation of an effect. (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 1-02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Dictionary of\\nMilitary and Associated Terms\"), \", As Amended through 15\\xA0Feb\\xA016)\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Performance.\"), \" Measure of a system's performance expressed\\nas speed, payload, range, time-on-station, frequency, or other\\ndistinctly quantifiable performance features. Several MOPs and/or MOSs\\nmay be related to the achievement of a particular \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \". (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense\\nAcquisition Guidebook\"), \")\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure of Suitability.\"), \" Measure of an item's ability to be supported\\nin its intended operational environment. MOSs typically relate to\\nreadiness or operational availability and, hence, reliability,\\nmaintainability, and the item's support structure. Several MOSs and/or\\nMOPs may be related to the achievement of a particular \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" (\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Defense\\nAcquisition Guidebook\"), \")\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission.\"), \" 1) The task, together with the purpose, that clearly\\nindicates the action to be taken and the reason therefore (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-0); 2)\\nIn common usage, especially when applied to lower military units, a duty\\nassigned to an individual or unit; a task (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-0); 3) The dispatching\\none or more aircraft to accomplish one particular task (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-30).\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission Effect.\"), \" The result, outcome, or consequence of an action, at\\nits appropriate mission level, typically tactical, represents the\\nmission effect or outcome. Mission effects are considered within the\\ncontext of concept of operations/operational mode summary/mission\\nprofile/employment. (derived from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 1-02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Department of Defense\\nDictionary of Military and Associated Terms,\"), \" As Amended through 15 Feb\\n16)\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Modeling and Simulation Support Plan.\"), \" The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" support plan developed\\nby the program office, captures all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" requirements over the life cycle\\nof an acquisition program, including those for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \". TDs must\\nensure the program office provides all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Verification and Validation\"\n }, \"V&V\"), \" plans and reports, and\\nensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" requirements are included as early as possible, as part of\\nthe program office's \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Modeling and Simulation\"\n }, \"M&S\"), \" funding strategy.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Requests for Proposal.\"), \" RFPs are issued by program offices that are\\nin negotiated acquisitions to communicate government requirements to\\nprospective contractors and to solicit proposals. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" personnel\\nensure \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"&E language is provided to the program office for inclusion in\\nRFPs.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Security Classification Guide.\"), \" The program office develops the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \"\\nto provide security instructions for military and civilian personnel\\nworking on a system. It is available from the program office and all\\ntest team members should read and understand it to avoid security\\nviolations. Be aware that multiple SCGs may apply when dealing with\\ncyber vulnerabilities and exploitability of a system and its\\ninterconnected infrastructures. Cyber and information operations SCGs\\n(e.g., \\\"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \" Cybersecurity Security Classification/Declassification\\nGuide for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" Weapon Systems,\\\" 17 Apr 17; DoDI O-3600.02, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Information\\nOperation Security Classification Guidance\"), \", 28 Nov 05; and US Cyber\\nCommand Instruction 5200-03, 15 Jun 16) take precedence over\\nsystem-specific SCGs and may require classifying the cybersecurity test\\nreport at the Secret Collateral or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Sensitive Compartmented Information\"\n }, \"SCI\"), \" level. In the absence of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \",\\nor if an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Classification Guide\"\n }, \"SCG\"), \" does not adequately cover capabilities, vulnerabilities,\\nweaknesses, and limitations, test team members should contact \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Information Protection/SAP Security (office symbol)\"\n }, \"CVI\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"System Capability.\"), \" A system capability is comprised of multiple,\\nintegrated system functions. It is the system's ability to complete a\\ntask or execute a course of action under specified conditions and level\\nof performance. Capabilities, when combined, create the desired mission\\neffect.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"System Functions/Properties.\"), \" Functions are specific, single actions\\n(enabled by the structure) for which a component/module/etc. is\\ndesigned. Properties are inherent, designed attributes or\\ncharacteristics of system.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"System Structure.\"), \" System structure includes system layouts or\\nconfigurations, controls and displays, embedded features, and underlying\\narchitectures that are relatively fixed and stable.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test and Evaluation Master Plan.\"), \" The program office develops the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" with input from the OTAs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" documents the overall structure\\nand objectives of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" program. It provides the framework for\\ngenerating detailed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" plans, and documents schedule and resource\\nimplications associated with the program, including comparison testing\\nor a suitable alternative. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" contains many of the agreements\\namong participants and specifies the levels of funding for the test. It\\nalso documents all integrated test activities, as well the criteria we\\nwill use to determine readiness for the final phase of operational\\ntesting. To support \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" A, the program must have a signed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \"; to\\nsupport \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" B, the program must have a draft update for the development\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Request for Proposal\"\n }, \"RFP\"), \" release decision point. Programs that enter the acquisition process\\nat a point other than pre-\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" A will have a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" (draft or signed)\\ncommensurate with that entry milestone's requirements. The program\\noffice will provide further iterations/updates of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \", as required,\\nfor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Milestone\"\n }, \"MS\"), \" C and full-rate production (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Full-Rate Production\"\n }, \"FRP\"), \")/fielding decisions. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" will\\napprove the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation Master Plan\"\n }, \"TEMP\"), \" for oversight programs. A-3 developed a document review\\nchecklist to assist with reviewing TEMPs, which is posted on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\nIntranet Library.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Threat Assessment Products.\"), \" Our test teams use validated threat\\nproducts and threat models that the National Air and Space Intelligence\\nCenter (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Air and Space Intelligence Center\"\n }, \"NASIC\"), \") and the Missiles and Space Intelligence Center produce\\ncontinuously as threats evolve.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"glossary.md"},"frontmatter":{"metaTitle":"Appendix B","metaDescription":"Glossary"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"bedf1131-0f55-53e9-918e-2b089446aa1b"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/index/page-data.json b/sites/oteguide/page-data/index/page-data.json index 269b65c6..3363c877 100644 --- a/sites/oteguide/page-data/index/page-data.json +++ b/sites/oteguide/page-data/index/page-data.json @@ -1 +1 @@ -{"componentChunkName":"component---src-templates-docs-js","path":"/","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"f46490dd-6a74-5c5d-ab1a-5201afabdd21","title":"Operational Test & Evaluation Guide","slug":"/"},"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\": \"Operational Test & Evaluation Guide\"\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(\"em\", {\n parentName: \"p\"\n }, \"Chrome or Firefox recommended for best experience\")), mdx(\"p\", null, \"On mobile? \"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Click the 'hamburger' icon to access sections\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"save to your homescreen using the options in your browser of choice\")), mdx(\"h1\", null, \"About\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Team,\"), mdx(\"p\", null, \"Last Spring, we undertook an effort to evolve our \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E guidance to be less prescriptive, match what we were doing, and provide the tools to test teams to deliver combat capability. At the core of this effort was enabling the six principles of Adaptive, Relevant Testing. We have been on a journey to transform our core documentation, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide, into a mobile friendly app that makes use of the best the web has to offer.\"), mdx(\"p\", null, \"This site is still in beta, but is regularly updated with all the same data from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Sharepoint site. While we\\u2019re still experimenting with the format, if there\\u2019s an instance of informational discrepancy between sites, Sharepoint is the authoritative source.\"), mdx(\"p\", null, \"Current application features include:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mobile and desktop views\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Searchable across all documents with a scrollable table of contents that is always visible (desktop view)\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Pop-up definitions of acronyms (desktop view)\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Dark/Light reading experiences\")), mdx(\"p\", null, \"The new guide is a living and breathing document. Rather than performing an update every other year, the new guide will incorporate updates at any point. To keep the Guide up to date and meaningful, we need content from you. \"), mdx(\"p\", null, \"You can submit content through email submissions to the \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:Kirtland.AFOTEC.A5.Workflow@us.af.mil\"\n }, \"Guide Team\"), \" and \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:travis.smith.3@us.af.mil\"\n }, \"App Team\"), \", such as:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Information for specific guides related to your job duties to create living continuity constructs\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Tools and how-to methods for achieving certain aspects of your job\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Templates for reports and other deliverables, along with step-by-step instructions\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Contacts related to your job, to populate an always-current list\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Web Application features you\\u2019d like to see\")), mdx(\"p\", null, \"This is but one small part of transforming \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" for relevance in 2030. The new tools will allow \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\u2019s best ideas and most current information to move through the organization in an always current, dynamic fashion. \"), mdx(\"h1\", null, \"App Notes\"), mdx(\"p\", null, \"11 Mar 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Onboarded Lt Zink and MSgt Farr (in training) \"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Created a collapsible folder view on left \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"\n }, \"TOC\"), \"\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Link fixes\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Working on CMS\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Working on P1 pipeline\")), mdx(\"p\", null, \"4 Mar 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Onboarded Lt Peterson\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"P1 \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \"-4 setup\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Link updates\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mobile scroll up minor fix\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Color theme modification\")), mdx(\"p\", null, \"19 Feb 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"updated contact email\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"added mobile 'scroll up' button\")), mdx(\"p\", null, \"4 Feb 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Added 404 page\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Created internal links possibility for content pages\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"updated links to internal pages and docs on the SharePoint, minor fixes to content\")), mdx(\"p\", null, \"27 Jan 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"minor functional change to search (click away focus)\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"added links\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"added intro content\")), mdx(\"p\", null, \"20 Jan 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"modified search\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"added 6 Functional Guides (see bottom of the \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"\n }, \"TOC\"), \")\")), mdx(\"h1\", null, \"Credits\"), mdx(\"h2\", null, \"The \", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide Team is:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mr. Dan Telford\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mr. Russ Foos\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mr. Payton Akin\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mr. David Ray\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Col Kevin \\\"Maddog\\\" Madrigal\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Col Matthew \\\"Mags\\\" Magness\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"(others)\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"You, if you want to add content \", mdx(\"a\", {\n parentName: \"li\",\n \"href\": \"(mailto:Kirtland.AFOTEC.A5.Workflow@us.af.mil)\"\n }, \"(email the team)\"))), mdx(\"h2\", null, \"The App Team is:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Lt William Zink\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Lt Jacob Peterson\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Capt Andrew \\\"Auto\\\" Risse\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Maj Travis \\\"Agent\\\" Smith\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#about","title":"About"},{"url":"#app-notes","title":"App Notes"},{"url":"#credits","title":"Credits","items":[{"url":"#the-ote-guide-team-is","title":"The OT&E Guide Team is:"},{"url":"#the-app-team-is","title":"The App Team is:"}]}]},"parent":{"__typename":"File","relativePath":"index.mdx"},"frontmatter":{"metaTitle":null,"metaDescription":null}},"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}},"pageContext":{"id":"f46490dd-6a74-5c5d-ab1a-5201afabdd21"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file +{"componentChunkName":"component---src-templates-docs-js","path":"/","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"f46490dd-6a74-5c5d-ab1a-5201afabdd21","title":"Operational Test & Evaluation Guide","slug":"/"},"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\": \"Operational Test & Evaluation Guide\"\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(\"em\", {\n parentName: \"p\"\n }, \"Chrome or Firefox recommended for best experience\")), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"Most Guides have an expandable folder you can open to see contents. Or simply search for what you're after.\")), mdx(\"p\", null, \"On mobile? \"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Click the 'hamburger' icon to access sections\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"save to your homescreen using the options in your browser of choice\")), mdx(\"h1\", null, \"About\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Team,\"), mdx(\"p\", null, \"Last Spring, we undertook an effort to evolve our \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E guidance to be less prescriptive, match what we were doing, and provide the tools to test teams to deliver combat capability. At the core of this effort was enabling the six principles of Adaptive, Relevant Testing. We have been on a journey to transform our core documentation, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide, into a mobile friendly app that makes use of the best the web has to offer.\"), mdx(\"p\", null, \"This site is still in beta, but is regularly updated with all the same data from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Sharepoint site. While we\\u2019re still experimenting with the format, if there\\u2019s an instance of informational discrepancy between sites, Sharepoint is the authoritative source.\"), mdx(\"p\", null, \"Application features include:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mobile and desktop views\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Searchable across all documents with a scrollable table of contents that is always visible (desktop view)\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Pop-up definitions of acronyms (desktop view)\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Dark/Light reading experiences\")), mdx(\"p\", null, \"The new guide is a living and breathing document. Rather than performing an update every other year, the new guide will incorporate updates at any point. To keep the Guide up to date and meaningful, we need content from you. \"), mdx(\"p\", null, \"You can submit content through email to the \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:Kirtland.AFOTEC.A5.Workflow@us.af.mil\"\n }, \"Guide Team\"), \" and \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:travis.smith.3@us.af.mil\"\n }, \"App Team\"), \", such as:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Information for specific guides related to your job duties to create living continuity constructs\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Tools and how-to methods for achieving certain aspects of your job\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Templates for reports and other deliverables, along with step-by-step instructions\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Contacts related to your job, to populate an always-current list\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Web Application features you\\u2019d like to see\")), mdx(\"p\", null, \"This is but one small part of transforming \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" for relevance in 2030. The new tools will allow \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\u2019s best ideas and most current information to move through the organization in an always current, dynamic fashion. \"), mdx(\"h1\", null, \"App Notes\"), mdx(\"p\", null, \"8 Apr 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"decomposed many of the lengthier guides into sub-pages, to help with mobile viewing and quickly finding search results\")), mdx(\"p\", null, \"7 Apr 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"added several guide documents\", mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, \"updated utility that converts from Word Doc to Markdown\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, \"general improvements to links and descriptions\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"modified search \"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"added acronyms section\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \"-4 version in work: tests ~77% complete, CMS ~90% complete \")), mdx(\"p\", null, \"11 Mar 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Onboarded Lt Zink and MSgt Farr (in training) \"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Created a collapsible folder view on left \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"\n }, \"TOC\"), \"\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Link fixes\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Working on CMS\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Working on P1 pipeline\")), mdx(\"p\", null, \"4 Mar 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Onboarded Lt Peterson\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"P1 \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \"-4 setup\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Link updates\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mobile scroll up minor fix\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Color theme modification\")), mdx(\"p\", null, \"19 Feb 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"updated contact email\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"added mobile 'scroll up' button\")), mdx(\"p\", null, \"4 Feb 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Added 404 page\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Created internal links possibility for content pages\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"updated links to internal pages and docs on the SharePoint, minor fixes to content\")), mdx(\"p\", null, \"27 Jan 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"minor functional change to search (click away focus)\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"added links\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"added intro content\")), mdx(\"p\", null, \"20 Jan 2021\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"modified search\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"added 6 Functional Guides (see bottom of the \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Tactical Operation Center OR Total Ownership Cost OR Table of Contents\"\n }, \"TOC\"), \")\")), mdx(\"h1\", null, \"Credits\"), mdx(\"h2\", null, \"The \", mdx(\"abbr\", {\n parentName: \"h2\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide Team is:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mr. Dan Telford\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mr. Russ Foos\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mr. Payton Akin\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Mr. David Ray\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Col Kevin \\\"Maddog\\\" Madrigal\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Col Matthew \\\"Mags\\\" Magness\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"(others)\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"You, if you want to add content \", mdx(\"a\", {\n parentName: \"li\",\n \"href\": \"(mailto:Kirtland.AFOTEC.A5.Workflow@us.af.mil)\"\n }, \"(email the team)\"))), mdx(\"h2\", null, \"The App Team is:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"Lt William Zink\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Lt Jacob Peterson\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Capt Andrew \\\"Auto\\\" Risse\"), mdx(\"li\", {\n parentName: \"ul\"\n }, \"Maj Travis \\\"Agent\\\" Smith\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#about","title":"About"},{"url":"#app-notes","title":"App Notes"},{"url":"#credits","title":"Credits","items":[{"url":"#the-ote-guide-team-is","title":"The OT&E Guide Team is:"},{"url":"#the-app-team-is","title":"The App Team is:"}]}]},"parent":{"__typename":"File","relativePath":"index.mdx"},"frontmatter":{"metaTitle":null,"metaDescription":null}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"f46490dd-6a74-5c5d-ab1a-5201afabdd21"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT/page-data.json b/sites/oteguide/page-data/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT/page-data.json new file mode 100644 index 00000000..0bebf414 --- /dev/null +++ b/sites/oteguide/page-data/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"05e71cd2-f29e-5178-8f3a-7deba5460402","title":"INTRODUCTION AND INTENT","slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT"},"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 AND INTENT\",\n \"metaTitle\": \"INTRODUCTION AND INTENT\",\n \"metaDescription\": \"INTRODUCTION AND INTENT\"\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 goal of this guide is to provide an introduction to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nLessons Learned (LL) process, explain the importance of the LL effort,\\nand finally show where this process is tied to established policy and\\nguidance. This process is mandated by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-1302, but the\\nimplementation and usefulness of this effort is dependent on the\\nwillingness of the organization to consider and develop valuable inputs\\nto the program. The previous iteration of this process relied on a\\n\\\"push\\\" from Test Directors at the close-out of programs and would be\\npresented during the final briefing to the Commander. Lessons Learned\\ncan and should be produced at any point in a program lifecycle, but will\\nnow have a dedicated end of program event to discuss and collect\\nobservations. Lastly, Lessons Learned is just one aspect of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"'s\\ncommitment to continuous process improvement, and the increases in\\neffectiveness and efficiency that come of that active institutional\\nfeedback.\"), mdx(\"p\", null, \"It is the expectation that this guide will provide clarification of the\\nprocess that \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" uses to collect, track, and disseminate and\\nimplement LL. This guide will serve as a reference for when and who to\\ncontact to submit identified lessons for evaluation and what to expect\\nafter submitting a proposed LL.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT.md"},"frontmatter":{"metaTitle":"INTRODUCTION AND INTENT","metaDescription":"INTRODUCTION AND INTENT"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"05e71cd2-f29e-5178-8f3a-7deba5460402"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned/page-data.json b/sites/oteguide/page-data/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned/page-data.json new file mode 100644 index 00000000..5250731b --- /dev/null +++ b/sites/oteguide/page-data/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ac5a57d1-6494-541d-b3de-45667fb96cb8","title":"Vocabulary of Lessons Learned","slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned"},"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\": \"Vocabulary of Lessons Learned\",\n \"metaTitle\": \"Vocabulary of Lessons Learned\",\n \"metaDescription\": \"Vocabulary of Lessons Learned\"\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, \"In the standard process of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"United States Air Force\"\n }, \"USAF\"), \" LL identified in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-1302 (shown in\\nfigure 1), there are a series of steps all LL proceed through. These\\nsteps are collection, validation, dissemination, and resolution. This\\nstandard process is open to interpretation and implementation for each\\norganization, but the broad strokes will be described.\"), mdx(\"p\", null, \"Figure 1. Lessons Learned Process ( \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Diagram per \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-1302\"), \" )\"), 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\": \"554px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/b4cd47565392bce2eea73fe8ef510a4b/04abd/image2.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\": \"77.60617760617761%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAQCAIAAACZeshMAAAACXBIWXMAAAsTAAALEwEAmpwYAAADMklEQVQoz3VRWU8aURTmv7Rqmj60L9VU0zSNpu1PaNKkS7o+NY1L7JJYECVdcE0XXCJoothWAwUqgiIqsomizCioiGWYgZmBcURggGHtHacx8aE3X26+e7/z3XPPOQLDhszkUcx75CZIYYYVCzC3mzzy2dXhWReHBUhxAjmQAAHSCUaCBCLo+lXzRX+7T1vfpbohHr8mGq0TjdW1jVx9Lat5Jatu/XqlTV4rHK17p6jtmLgmVd3o0Tb06gDq4aBL8N3e/9M5MGb5Mr3ybX51SG8f1NlketvAnGvI6BzSOwa0VpnROWhwDM7YB/TOwYWN4WVYvrKlCBJBgZ9I0DRDMTk0yZbL5VKp/L9VOtHiR8ckfgjIMZMTIDg+4UXEFphhOXM8k223wJs4xRt0u+iwe69YKgA+ux+e9oVoKppiUlwkwwrKbLrXtXdnysJHR1OZ6hHDjB/jj+Jl+K7aBrICLlyCH6ut2VSS/xyXOUmR0pWtR1pHqVgs5lgymb6lXJrbDwO5kM102baf6xyFQr7MZj/avM3G9dPSOHMhlRDPr91XrQT8/v29XSjwB5i/u7a2N92hg4BkyfNE64A8mxEkKF70NM+5z5jpCPbJAj1QW6lYlIyE/WH8pnJpat0XDv6JhBBgfqpzhjGMJvGOZajJeNacoMge585DjYMvkkpnG8bNpgOcOxTyUrvv2W8nqAhY3tt8TYaz3wb8s/vgvsbBJBJ8w64rLSrIzzfpg3P3ntoep2nAO207oH7QsPJpw9DDozUkshjADrBwLsPkCnkveYgQZJzmhonSx/4YHSWJYp7F4okARcdIIncyVM7sPUp7ESKYZF2h6CEd519NpdMRkh81lx8jYgkmy0uhCOCZf3OObs2hmg7M0E3MfMiY+zKL/enFfsogRTUfSUMvqpNGDd2MqQfcpxb6GBBg7mXN3SysOU4XBPjPt2xnFdV5GWm76Gut8rZWQc2V7qbK9caKtcaK1Zfn1hrPwy1VUEslkPbfXCA6LiXaK3LTL+KZkgBb/R2ZFqJqSVjdiWskgSmxVynamRT5JtsBdibbtydE8LjQ/0NMaLgYVCXBVaKYVUmn8n8BERr8N8GUTTYAAAAASUVORK5CYII=')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image2\",\n \"title\": \"image2\",\n \"src\": \"/static/b4cd47565392bce2eea73fe8ef510a4b/04abd/image2.png\",\n \"srcSet\": [\"/static/b4cd47565392bce2eea73fe8ef510a4b/a2ead/image2.png 259w\", \"/static/b4cd47565392bce2eea73fe8ef510a4b/6b9fd/image2.png 518w\", \"/static/b4cd47565392bce2eea73fe8ef510a4b/04abd/image2.png 554w\"],\n \"sizes\": \"(max-width: 554px) 100vw, 554px\",\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, \"During the Collection phase of a LL, an \\\"Observation\\\" is created and\\nsubmitted to the LL Manager by a member of the organization. This\\nObservation is catalogued for tracking, then validated at the\\nappropriate level and with the appropriate process owners and experts.\\nIf the Observation is validated, it is assigned an action officer who\\ndetermines the necessary actions for implementation. The Observation\\nbecomes a \\\"Lesson Identified\\\", and is disseminated to the appropriate\\nmembers of the organization. Once the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Area of Operations or Authorizing Official or Action Officer\"\n }, \"AO\"), \" has completed the\\nimplementation actions, and all relevant members are notified and\\ntrained on the changes, the Lesson Identified becomes a Lesson Learned\\n(Resolution).\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned.md"},"frontmatter":{"metaTitle":"Vocabulary of Lessons Learned","metaDescription":"Vocabulary of Lessons Learned"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"ac5a57d1-6494-541d-b3de-45667fb96cb8"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/lessons_learned_guide/1-4-Policy-Guidance/page-data.json b/sites/oteguide/page-data/lessons_learned_guide/1-4-Policy-Guidance/page-data.json new file mode 100644 index 00000000..f856e88f --- /dev/null +++ b/sites/oteguide/page-data/lessons_learned_guide/1-4-Policy-Guidance/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/lessons_learned_guide/1-4-Policy-Guidance","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"eeac030f-9f41-51d0-a6bd-f557f6ad6181","title":"Policy Guidance","slug":"/lessons_learned_guide/1-4-Policy-Guidance"},"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\": \"Policy Guidance\",\n \"metaTitle\": \"Policy Guidance\",\n \"metaDescription\": \"Policy Guidance\"\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\": \"United States Air Force\"\n }, \"USAF\"), \" Lessons Learned policy is captured in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Instruction\"\n }, \"AFI\"), \" 10-1302, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Air Force\\nLessons Learned Program\"), \" .\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"lessons_learned_guide/1-4-Policy-Guidance.md"},"frontmatter":{"metaTitle":"Policy Guidance","metaDescription":"Policy Guidance"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"eeac030f-9f41-51d0-a6bd-f557f6ad6181"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/lessons_learned_guide/1-5-PROCESS/page-data.json b/sites/oteguide/page-data/lessons_learned_guide/1-5-PROCESS/page-data.json new file mode 100644 index 00000000..9107012e --- /dev/null +++ b/sites/oteguide/page-data/lessons_learned_guide/1-5-PROCESS/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/lessons_learned_guide/1-5-PROCESS","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"23fea79b-ea04-5e2e-a094-5e7e5c0681c4","title":"PROCESS","slug":"/lessons_learned_guide/1-5-PROCESS"},"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\": \"PROCESS\",\n \"metaTitle\": \"PROCESS\",\n \"metaDescription\": \"PROCESS\"\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\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" LL process, illustrated in figure 2, adheres to the broad\\nstrokes defined by policy and implements them in a mixed pull\\n(interviews/surveys) and push process (SharePoint).\"), mdx(\"p\", null, \"Figure 2. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Lessons Learned Process\"), 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\": \"553px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/8173e07865edf8362ed55de244590c45/74cfa/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\": \"44.4015444015444%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAJCAIAAAC9o5sfAAAACXBIWXMAAAsTAAALEwEAmpwYAAACHUlEQVQozy2R7U9SARTG/Xf60NrIggB5NRBnri/WVroIrjFGW0CzGklLZi2sZEscqNzkLcx2Z7qZDNoYYmAyhUhi9obGagtbbXLv5b5fuihnz3l2dnZ+53w4bY3DYGgagWskgTUa7FGHYpgDFCUoiqtZloVRDKnjnNcQ7ADBGaY51kZStHshZ5teHZqI3fOl7MGtdK781fMsabuzYjEnbLe3HCPV9eQeZC9NGb/7b/wIWaphE/ar1IRxgro0GuVppwSAR3Rt+qRpYW6lkLtycaad5xWcnhXy30jEFShQdnWvm48Vh9v3x0R/H5wgvqUPYZw0uTNKy0uVOdhlDUmt0GQwngUGwko52Cmf16iSveey3vGSq3fTJti0i7cdsk/2U8TuRuvy4NOExOSXG72aoVcS6+vwUjZv0L6QS0GFLKJSLqvVOxHwj6+v8lAMu1V1TxfsEhPl9y0YGItJTQG1NaK2hDosEBQvFoy659IOUCkPnVXMKRSVxcjvmQs79898HJGUnYp/T0TkEYzhpN71jj8IioBJ2XW/0Lo8Hy3k9f2LMsnbbnWqR5NQde5BgS/jPRs3j2/b+Z8dwuoojyxnmjBBUndnswOP4vrHceNE5rJzNZoqFYdvrem0GQOQNgBruqs/Y0u7fuMH5/l9X38toIXBPqKSb8Jc1nEKxUhOzU/WuW00VUcJGCGRlhiSbFD1BomyOMLgCI3BLENz4H/7XnAM533YIwAAAABJRU5ErkJggg==')\",\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/8173e07865edf8362ed55de244590c45/74cfa/image3.png\",\n \"srcSet\": [\"/static/8173e07865edf8362ed55de244590c45/a2ead/image3.png 259w\", \"/static/8173e07865edf8362ed55de244590c45/6b9fd/image3.png 518w\", \"/static/8173e07865edf8362ed55de244590c45/74cfa/image3.png 553w\"],\n \"sizes\": \"(max-width: 553px) 100vw, 553px\",\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 stand-alone LL submissions form can be found on the LL\\n\", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"https://cs2.eis.af.mil/sites/10008/functional/lessons/SitePages/Home.aspx\"\n }, \"Sharepoint\"), \"\\nsite (example in Appendix A), along with contact information for the\\ncurrent LL manager. The submission of LL by team members can be\\nperformed at any time during a test program, and is encouraged while\\nmemory of an event is still fresh. This process has a number of\\nbenefits. For interviews it ensures that test directors, having\\ncompleted a test event and necessary reporting, are prepared and have\\nthe necessary bandwidth to thoughtfully consider any lessons or problems\\nthey encounter during the test program. Test team members are encouraged\\nto step back and give the organization its best opportunity to learn\\nfrom the challenges they encounter and solutions developed. Surveys\\noffer a focused opportunity to be directed by questions through the\\ndifferent aspects of their duties and highlight issues they've\\nencountered in each. Finally, self-reported observations offer out-of-\\nsequence opportunities for team members to identify issues and solutions\\nthey have uncovered during the normal accomplishment of their duties.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"lessons_learned_guide/1-5-PROCESS.md"},"frontmatter":{"metaTitle":"PROCESS","metaDescription":"PROCESS"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"23fea79b-ea04-5e2e-a094-5e7e5c0681c4"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/lessons_learned_guide/page-data.json b/sites/oteguide/page-data/lessons_learned_guide/page-data.json new file mode 100644 index 00000000..d93534b6 --- /dev/null +++ b/sites/oteguide/page-data/lessons_learned_guide/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/lessons_learned_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"b97e367d-bac0-58f3-9b5e-92adeb60551c","title":"Lessons Learned Guide","slug":"/lessons_learned_guide"},"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\": \"Lessons Learned Guide\",\n \"metaTitle\": \"Lessons Learned Guide\",\n \"metaDescription\": \"Lessons Learned Guide\"\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, \"Last Updated/Reviewed: 08 December 2020\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"lessons_learned_guide.md"},"frontmatter":{"metaTitle":"Lessons Learned Guide","metaDescription":"Lessons Learned Guide"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"b97e367d-bac0-58f3-9b5e-92adeb60551c"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/measures_guide/2-INTRODUCTION/page-data.json b/sites/oteguide/page-data/measures_guide/2-INTRODUCTION/page-data.json new file mode 100644 index 00000000..9da1be7e --- /dev/null +++ b/sites/oteguide/page-data/measures_guide/2-INTRODUCTION/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/measures_guide/2-INTRODUCTION","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"f051865f-b0a9-5f60-a35d-4af3d3a1e9bb","title":"INTRODUCTION","slug":"/measures_guide/2-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\": \"INTRODUCTION\",\n \"metaDescription\": \"INTRODUCTION\"\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, \"Measurement is central to conducting operational test and evaluation\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E). This technical guide supplements the \\u201C\", 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 Guide\\u201D and\\nprovides \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" personnel the necessary background and specific\\ndirections on how to write and develop measures. The first section is a\\ngeneral overview of the fundamentals of measurement. Section 2 describes\\nhow \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" develops measures. Sections 3 provides details of measure\\ndocumentation. Appendix A provides examples of the types of continuous\\nand discrete measures. Appendix B provides checklists to ensure measures\\nare properly written. Appendix C discusses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\u2019s process for writing\\ncyber measures.\"), mdx(\"p\", null, \"Submit suggested changes to: \", mdx(\"a\", {\n parentName: \"p\",\n \"href\": \"mailto:AFOTEC.A2A9.Workflow@us.af.mil\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"a\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \".A2A9.Workflow@us.af.mil\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"measures_guide/2-INTRODUCTION.md"},"frontmatter":{"metaTitle":"INTRODUCTION","metaDescription":"INTRODUCTION"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"f051865f-b0a9-5f60-a35d-4af3d3a1e9bb"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT/page-data.json b/sites/oteguide/page-data/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT/page-data.json new file mode 100644 index 00000000..fecc9c7d --- /dev/null +++ b/sites/oteguide/page-data/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"08f41040-d4c7-542a-b313-76d3e075d7ac","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT","slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT"},"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\": \"SECTION 1 FUNDAMENTALS OF MEASUREMENT\",\n \"metaTitle\": \"SECTION 1 FUNDAMENTALS OF MEASUREMENT\",\n \"metaDescription\": \"SECTION 1 FUNDAMENTALS OF MEASUREMENT\"\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, \"Measures Overview\"), mdx(\"p\", null, \"Test measures are the basis of the evaluation of a system under test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"); they are the data used to assess effectiveness and suitability\\nand serve as evidence of system deficiencies. Operational effectiveness\\nand operational suitability are defined as follows:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Effectiveness\"), \" \\u2013 The overall degree of mission\\naccomplishment of a system when used by representative personnel in\\nthe environment planned or expected for operational employment\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Suitability\"), \" \\u2013 The degree to which a system can be\\nsatisfactorily placed into field use. Examples of issues evaluated\\nunder operational suitability:\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Reliability, maintainability, availability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Compatibility and interoperability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Supportability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Transportability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Human factors\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Training requirements\"))))), mdx(\"p\", null, \"There are three general types of measures developed for Operational Test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"): Measures of effectiveness (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \"), Measures of Performance (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \"),\\nand Measures of Suitability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" provide direct evidence that a\\nuser can successfully employ the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" to accomplish a mission. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" can\\nbe used to evaluate the system as soon as it is feasible to test the\\nsystem in an operational environment.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"strong\", {\n parentName: \"li\"\n }, mdx(\"u\", null, \"Measure of Effectiveness (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \")\")), \" - Measures designed to\\nassess the degree to which the \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can accomplish mission objectives\\nand achieve desired mission effects. If appropriate, they may\\nquantify success as a proportion of successful test events, rate of\\nsuccess, or the probability that the system will achieve some\\nresult.\")), mdx(\"p\", null, \"MOPs and MOSs can be used to evaluate the system throughout development\\nand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. Capabilities and functions of a system are evaluated using\\nboth MOPs and MOSs. The supportability and sustainability of a system is\\nevaluated using MOSs.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"u\", null, \"Measures of Performance (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \")\")), \" - Measure a system\\u2019s\\ncapabilities. They may quantify performance such as speed, payload,\\nrange, time-on-station, frequency, rating or other distinctly\\nobservable and/or quantifiable performance features. They may also\\ndocument whether or not a system can successfully complete a task.\\nFinally, MOPs may document user ratings of system attributes.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"u\", null, \"Measures of Suitability (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \")\")), \" - Measure of the ability to\\nsupport the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" in its intended operational environment. MOSs\\ntypically relate to readiness or supportability and hence include\\nmeasures concerning reliability, availability, maintainability, the\\nquality of system documentation, the quality of training, and the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" logistics infrastructure.\"))), mdx(\"p\", null, \"All three types of measures (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \") are used by the test\\nteam to determine if a system can accomplish a mission, which is stated\\nas a Critical Operational Issue (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"). For example, the C-130J has two\\nprimary missions: conduct tactical airlift and conduct airdrop\\noperations. The following are two of the COIs from the C-130J test\\nprogram; note that the convention is to phrase COIs in the form of a\\nquestion.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1: Can the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" conduct tactical airlift\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 2: Can the C-130J conduct airdrop operations\"))), mdx(\"p\", null, \"When developing measures for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", it is useful to visualize the system\\nas having four layers that may require measurement and assessment:\\nMission Effects, System Capabilities, System Functions and Properties,\\nand System Structure. Figure 1-1 depicts these four levels in a pyramid\\nand provides definitions.\"), mdx(\"p\", null, \"Figure 1. The Pyramid: Evaluation Levels of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\"), mdx(\"span\", {\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/3a850abe9fde7feb04b16b5dcfbb9380/5819f/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\": \"54.440154440154444%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAIAAADwazoUAAAACXBIWXMAAAsTAAALEwEAmpwYAAACIUlEQVQoz2VQ30siYRSdfyrfArPeeivqwXoOIsjRxCwieqsgkIh6rAiKYFmEgnrJllwbdRylHcd1nB86zuiMo47OrqO5kzO7V2S3hT4Oh3vv9x3O/Q7y+8NRFK1SaZvmmyzriqLLcltVfwJEUZOkFkwAUBhGH/kofnjAw+F4q9WJx/mnJyaRKOJ4KZMRabrG8/VSqQlg2Xqj0XkX2/aQBcFIJns43idJwzQHg4EFPMLfZ/Y/Rv5X6roZDusnJ8zxMXV+rnHcAPxjMY4ghGiUTaVKGMZjGAdMkpXXV/NdbNtWPN69vNSOjtKHh8nT0+LNTVdReoLQkKQ2pKAoPwAQBLTNpgFLDcWWNdQnEvrenhIK1Q8OZEAopO7v166uNLiCbMCqUKgxjJrPK/BhaEWxhYwWbjR+7e7Wg0EpGCyurGBLS1/8fnpzUwgEFAzrGUYPlofYkslSKiW8vEjwC8h85GydnamBgLy+zqHoN6+X8vnyq6tpr5fc2Kju7Cg838lmxUJB5bg6Rcksq4JzuawNxXd3+sxMeXFRdLsrCwvV+fnvc3OU2y1BDcPZ2fL2ds2ybEnSwDOXq2azFeB2u4swTGd6OuN0piYniYkJwunEHY7PY2OfxsejLlfa5SKmpgiHI3F9XROE+u0tGYnQ9/dUJJLX9R5ycUEvL0f9/mefb4QYij56PI8o+jSarK09ezxft7aSLNvM5WQIjKYhM7Xff/sDFCQPUHG5M5AAAAAASUVORK5CYII=')\",\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/3a850abe9fde7feb04b16b5dcfbb9380/e3189/image7.png\",\n \"srcSet\": [\"/static/3a850abe9fde7feb04b16b5dcfbb9380/a2ead/image7.png 259w\", \"/static/3a850abe9fde7feb04b16b5dcfbb9380/6b9fd/image7.png 518w\", \"/static/3a850abe9fde7feb04b16b5dcfbb9380/e3189/image7.png 1035w\", \"/static/3a850abe9fde7feb04b16b5dcfbb9380/5819f/image7.png 1042w\"],\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, \"Measures can be used to evaluate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" at each level of the pyramid.\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are used to evaluate mission effects, while MOPs and MOSs are\\ntypically used to evaluate system capabilities, system functions and\\nproperties, and system structure.\"), mdx(\"h1\", null, \"Qualities of a Good Measure Set\"), mdx(\"p\", null, \"The following are qualities of a good measures set:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Measures should be operationally relevant, necessary, and sufficient\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Measures should represent something quantifiable or observable, not\\na goal or objective\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The data satisfying a measure should be observable, or at least\\ninferable\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Measures should be clear and concise\"))), mdx(\"p\", null, \"Measures should be operationally relevant, necessary, and sufficient.\\nMeasures should only be included in a data set if they provide\\nsignificant support to one of three goals: delivering combat capability,\\ndiscovering system deficiencies, and evaluating the effectiveness and\\nsuitability of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". Measures required by engineers during system\\ndevelopment may not be relevant to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" testers.\"), mdx(\"p\", null, \"Avoid the trap of writing too many measures. The resources required to\\ncollect data for measures varies, but at a minimum every measure\\nrequires the time and attention\\u2014limited resources\\u2014of a data collector.\\nTherefore, be discerning when searching requirement documents for\\npotential measures; requirements are written for system developers, not\\nnecessarily operational testers.\"), mdx(\"p\", null, \"Measures should represent something quantifiable or observable.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Poor measure: No friendly fighter losses\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Better measure: Number of friendly fighters destroyed or damaged\"))), mdx(\"p\", null, \"The goal for friendly fighter losses (zero) can be included in the\\nmeasure as a threshold used as the basis for an evaluation of acceptable\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance.\"), mdx(\"p\", null, \"The data satisfying a measure should be observable. Observable data can\\nbe either quantitative (numerical) or qualitative (descriptive). A\\nmeasurement can be objective (independently verifiable by 2 or more\\npeople) or subjective (an opinion or perception of an individual).\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Poor measure: Pilot\\u2019s opinion about the aircraft\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Better measure: Pilot\\u2019s rating (on a 5 point scale) of aircraft\\nmaneuverability\"))), mdx(\"p\", null, \"Measures should be clear and concise. Measures should be written in\\nlanguage that is understandable by someone with a limited knowledge of\\nthe system or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \".\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Poor measure: Status of enemy fighters\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Better measure: Percentage of enemy fighters destroyed or rendered\\ncombat ineffective\"))), mdx(\"p\", null, \"Measures sets can evolve as measures are added or deleted due to\\ninsights gained by the test team from test activities. The first measure\\nsets are developed relatively early in the continuum of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ninvolvement with system development. The test strategy should promote\\nregular updates, additions, and modifications to the measures sets\\nthroughout the test lifecycle. The next section discusses the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nprocess for measures development.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#measures-overview","title":"Measures Overview"},{"url":"#qualities-of-a-good-measure-set","title":"Qualities of a Good Measure Set"}]},"parent":{"__typename":"File","relativePath":"measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT.md"},"frontmatter":{"metaTitle":"SECTION 1 FUNDAMENTALS OF MEASUREMENT","metaDescription":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"08f41040-d4c7-542a-b313-76d3e075d7ac"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT/page-data.json b/sites/oteguide/page-data/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT/page-data.json new file mode 100644 index 00000000..edcfa880 --- /dev/null +++ b/sites/oteguide/page-data/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"eddffb95-1616-5902-919b-7efa8e29efbe","title":"SECTION 2 MEASURES DEVELOPMENT","slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT"},"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\": \"SECTION 2 MEASURES DEVELOPMENT\",\n \"metaTitle\": \"SECTION 2 MEASURES DEVELOPMENT\",\n \"metaDescription\": \"SECTION 2 MEASURES DEVELOPMENT\"\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 discusses the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" process for developing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", MOPs, and\\nMOSs. From the perspective of the pyramid in figure 1, one can think of\\ndeveloping measures using a top-down or bottom-up approach. The top down\\napproach is most useful for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" development since it focuses on the\\nMission Effect, and the bottom up approach is effective when developing\\nMOPs and MOSs since it focuses on the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"), mdx(\"p\", null, \"There are opportunities to bring stakeholders together through two\\nformal meetings, the Initial Test Design (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \") and the Measures Workshop\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \"), where measures are developed. These meetings are just one type of\\nvenue facilitated by the test team, A-2/9, and A\\u20113 to develop, refine,\\nand socialize measures. Major stakeholders in the acquisition program\\nare invited: the user community, the System Program Office (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Program Office\"\n }, \"SPO\"), \"), \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \",\\nsystem developers, and developmental testers. All participants apply\\ntheir subject matter expertise toward the goal of developing a measure\\nset and test designs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are developed at the Initial Test Design\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \") meeting, although they may be developed at a Measures Workshop\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \") if that occurs first. MOPs and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" are developed at a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \".\"), mdx(\"h1\", null, \"Developing Measures of Effectiveness\"), mdx(\"p\", null, \"Developing \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" using the top-down approach is typically done using a\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" document, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" Evaluation View (developed by \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A3), mission\\ndocumentation and scenario development, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" inputs, empirical results\\nfrom test events, etc. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" describes the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" mission, how the\\nsystem will be employed, and what effects the user is trying to achieve.\\nThe Evaluation View (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \") describes the necessary conditions and\\nactivities that must be accomplished for the system to provide its\\ncapabilities, contribute to mission accomplishment, and ultimately\\nsupport national strategic objectives.\"), mdx(\"p\", null, \"Using an appropriate combination of the methods above, one can identify\\ndesired and undesired mission effects in the analysis of the system. For\\nexample, target damage from a bomb is a desired effect, while collateral\\ndamage is an undesired effect. It may be appropriate to also include an\\noperational context for the sake of scope or clarity.\"), mdx(\"p\", null, \"The definition of mission and mission effect are important in developing\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \".\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission\"), \": 1) The task, together with the purpose, that clearly\\nindicates the action to be taken and the reason therefore (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-0); 2)\\nIn common usage, especially when applied to lower military units, a duty\\nassigned to an individual or unit; a task (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-0); 3) The dispatching\\nof one or more aircraft to accomplish one particular task (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 3-0).\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mission Effect\"), \": The result, outcome, or consequence of an action, at\\nits appropriate mission level, typically tactical, represents the\\nmission effect or outcome. Mission effects are considered within the\\ncontext of Concept of Operations / Operational Mode Summary / Mission\\nProfile/Employment (derived from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Publication\"\n }, \"JP\"), \" 1-02, Department of Defense\\nDictionary of Military and Associated Terms, As amended through 15 Feb\\n16). Mission effects may include desired and undesired effects.\"), mdx(\"p\", null, \"An \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" may incorporate both the mission (action taken) and the effect;\\nfor some systems the effect and the action are one in the same.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" x.y: Recover personnel\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" x.y: Ingress area to reach pick-up point\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" x.y: Maintain aircraft to achieve required availability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" x.y: Defeat high value advisory targets\"))), mdx(\"p\", null, \"Once we have identified the actions and outcomes of interest for a\\nsystem it may be necessary to include additional components in order to\\ncommunicate metrics and evaluation criteria. These components will be\\nincluded within the measures worksheet but are not necessary to include\\nwithin measures summary tables.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"The components of an \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" may include the following (note some\\ncomponents are optional):\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"The method of summarizing the observed sequence of successes and\\nfailures (e.g., proportion, rate, or probability)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A description of the mission effect (outcome) that will be defined\\nas a success; an optional standard of success can be explicitly\\nincluded\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"An optional operational context for the desired mission effect\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"An optional basis for evaluating the observed proportion of\\nsuccesses and failures\"))), mdx(\"p\", null, \"Figure 2 shows the basic structure of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \".\"), mdx(\"p\", null, \"Figure 2. Components of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \"\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"751px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/f1017db6f660a63c97b131a7227a0982/c483d/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\": \"85.71428571428571%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAARCAIAAABSJhvpAAAACXBIWXMAAAsTAAALEwEAmpwYAAADY0lEQVQ4y21TbUhTURg+2g8tKol+RCg1sKgffVFZFJEVqEWBZCYZEZXSh4V9EU2wli3yI6Ms0YygqEXltrZqms5tVtOZSUuzfbi0lptW5nS76253995zTudu6+NH73m5vJz3PPd5n/c9B2CMWRaWlYVWruRTUqBUyrMsIptI+AiGsBDRHF00VLS4b/FSx9KK7xUQQbIJSPbECRYANGECJg4ALijgSQLCf8AI57vzgRVMtk+eZJ8EeoFkRCKAnU4uOZk4XrQIL1yIZ83CM2bA/n4UwQsLYyttjbPFJToSs1xZmwc3J9gTZjpmeqAHdHQwiYkwNxfn5ODsbJyejmeLYEcHRzA8jzgkBC1jLcAGRA7RDvcOAp5un074nawTeDyhpCQ6NhZPm4anThXKnj8P+v1R2RHm76HhBNuU5c6UzMHMbFc2KWHJwBIe80QzvnePiokJEdkAwInxeG9h9yNde4jlvd5xr9dLM8Gy2tbM+iNx1ljQDUAPiP8Q3+RvEjSHu4pMJvrUqZ8nT9I9Ztj8uvv4ZVVn55vHxJTKF6+MZ2o13b1DJp/xaP8xsVP8jnoXaSQIa8O/DZF/EXe7Xc+fN+r1ep1O9+SJ+uuwO5r73X8e8ZFRCQZJbzjMER2cILLPbmtra7NYLGazWavVOhyOMAdLMEITYZQNhEeC/vJi7KVoc49VIZeHq1aqVKpPX1whhhFORm5MmC0KJph2ub1mf0t1frNZPXBZZigoV1gtHzQaTUNDg91u2yd9WKcw4q673pptVN12pqv+L7O2rley/nFFVsPFLc8kaxXlhY197m8IIpZlOSIGQWOv+9WlPeyVNYHarYHrG6mSBczLGgFM/QhI055W722pO9R644Dh6q7m0nQN7QlFrzcSJCHfICudE7yVyzw4zMj2BypWUxcWoJAfDFp+iFfIq/doZWKTrMhUmdMoTpEP28ZxBBh+AH6rwV8sCt7MCd7NYx4eCd7aSUlEnNcFfKM/JRsUNXl6mbi9vqTz2m5t6SZN0Mf9YSZBYMQ5VpzMnJ0buJYRqEqjxUm+qlQIWUFz64P359KU59PV0gy1dKOqUzkQpY3OQIhGm6qoC8sClal05Tpf+Sq6R/Vnzuit7uPt0/o7pw3vDZ/x/4xHaKxLPXrn4Nj9QrrPGEH9AtksAMPTtL1eAAAAAElFTkSuQmCC')\",\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/f1017db6f660a63c97b131a7227a0982/c483d/image8.png\",\n \"srcSet\": [\"/static/f1017db6f660a63c97b131a7227a0982/a2ead/image8.png 259w\", \"/static/f1017db6f660a63c97b131a7227a0982/6b9fd/image8.png 518w\", \"/static/f1017db6f660a63c97b131a7227a0982/c483d/image8.png 751w\"],\n \"sizes\": \"(max-width: 751px) 100vw, 751px\",\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, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 1: Desired Mission Effects.\"), \" Suppose the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \" for a\\nsilo-based missile system stated the mission is to provide a safe,\\nsecure, responsive, on-time, and on-target nuclear deterrent force.\\nUsing a top-down approach to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" development, one \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" is required to\\nsupport an assessment that the system delivers a nuclear warhead to the\\nintended target. Another \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" is required to support an assessment that\\nthe system is responsive to launch commands. Other \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" may be required,\\nbut two will suffice for this example.\"), mdx(\"p\", null, \"The following are possible \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", and the components of each measure are\\ncolor coded to be consistent with figure 2.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.1: Proportion of adversary high-value strategic targets\\ndefeated meets planning factor\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.2: Proportion of missiles that are launched in defensive\\nscenario meets \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operations Plan\"\n }, \"OPLAN\"), \" requirements\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 2: Undesired Mission Effects.\"), \" Tanker aircraft engage in a\\nvariety of missions, but the most common is air refueling of receiver\\naircraft. When receiver aircraft are properly refueled and consequently\\nin a return-to-mission status, a desired effect has been achieved. There\\nare circumstances, however, in which a tanker boom may cause damage to\\nreceiver aircraft during air refueling; and this damage may create a\\nrisk to mission accomplishment. The following \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" incorporates these\\nundesired effects into the measure.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" x.y: Proportion of boom-damaged, mission-compromised aircraft.\")), mdx(\"h1\", null, \"Developing Measures of Performance and Measures of Suitability\"), mdx(\"p\", null, \"MOPs can be developed using a bottom-up or top-down approach. Using the\\nbottom-up approach, the test team reviews the available requirement\\ndocuments, identified standards, and acquisition documents (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Capabilities Document OR Interface Control Document\"\n }, \"ICD\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Production Document\"\n }, \"CPD\"), \")\\nto determine what MOPs are required to evaluate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". These documents\\nmay also provide information about the expected level of reliability,\\navailability, maintainability, and other logistics aspects related to\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" employment and sustainment; these suitability issues are used to\\ndevelop MOSs. Using the top-down approach, the test team starts with the\\nMOPs and asks what performance characteristics are most relevant to\\nmission success.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"It is important for the test team to consider the following when\\ndeveloping measures:\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What aspects of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" performance are important to enabling the\\noperation or mission?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What aspects of employment and sustainment are important to enabling\\nthe mission?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"How can the desired performance or aspect of suitability be\\nmeasured?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What is the best way to summarize performance (e.g., average,\\npercentile, etc.)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"What degree of performance is required by the user?\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Does the degree of performance required depend on certain\\nconditions?\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Common \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" attributes that MOPs typically measure (not all\\ninclusive):\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Accuracy\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Timeliness\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Completeness\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Workload\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Common \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" attributes that MOSs typically measure (not all\\ninclusive):\")), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Reliability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Availability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Maintainability\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Usability\"))), mdx(\"p\", null, \"Systems may have other attributes that need to be evaluated such as\\nlethality, interoperability, trainability, etc. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Concept of Operations\"\n }, \"CONOPS\"), \", the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Evaluation View\"\n }, \"EV\"), \", and\\nthe requirements documents are used to determine the relevant system\\nattributes to evaluate with measures.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example 3:\"), \" The Joint Biological Agent Decontamination System (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \")\\nis a capability designed to meet Air Mobility Command (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Mobility Command\"\n }, \"AMC\"), \") and United\\nStates Transportation Command (USTRANSCOM) needs for decontamination of\\naircraft against biological warfare agents (BWA) and other biological\\nagents of concern.\"), mdx(\"p\", null, \"MOPs need to be developed for the following \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \":\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"-2: Can \", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \" be assembled and disassembled at deployed\\nlocations?\")), mdx(\"p\", null, \"There are 2 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \":\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1: Percentage of correctly assembled \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 2: Percentage of correctly disassembled \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \"\"))), mdx(\"p\", null, \"The user community at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures Workshop\"\n }, \"MW\"), \" noted that the timeliness of\\nassembly/disassembly has operational impact. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Capability Development Document\"\n }, \"CDD\"), \" stated that the\\nassembly time should be less than 30 minutes. There was no requirement\\nfor disassembly. The user community noted that in the operational\\nenvironment, disassembly time was an important safety and security\\nissue. The following MOPs were created:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1: Assembly time\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2: Disassembly time\"))), mdx(\"p\", null, \"The user community also noted that it is important that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Biological Agent Decontamination System\"\n }, \"JBADS\"), \" system\\nis reliable. The following \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" related to reliability was created:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" 1: Mean time to failure (MTTF)\")), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"-Operations-Measures-Data Hierarchy.\"), \" The resulting structure of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", MOSs and MOPs can be organized in several ways depending\\non the type of evaluation methods utilized. Figure 3 depicts some of\\npossibilities.\"), mdx(\"p\", null, \"Figure 3. Measure Hierarchies\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"578px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/00877f36d1251accb8ee1e7fe7d01628/508ef/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\": \"53.28185328185329%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAALCAIAAADwazoUAAAACXBIWXMAAAsTAAALEwEAmpwYAAABKklEQVQoz5WSfWuDMBDG/f4faTA2+seKzEkbp1BE1w0aX5pq0kQTNdFdtZvQQrc+HOHJkd9dLsSqqopz3vf98COtNWNMKQUe0nMMs5lkRVHk+74xBvimaSAlpbRtO0mSEZ6LXstSo6ZN27bAUEr5KIxxShguJS5rWPOjwgV4Sev2DDejpk1d167rAgy+67TnofhzlzKpOiNUUynFpRRS1Upp08GlrDiOHccRQkyXBD4MQ4QQZGCWjzhaI5RmmApSHHNCccn3hGWEpZ1ure12GwTBb3Mw8ArATxko7b17X1lUVjmcvpx5uCmjDaH5euOgjXvg2cUT/gFrbZJ8t1g+va6Wpdif4OHfcG/6lODHxcPi5flwvKfzdI6KAoVvfrQq7u18LjKYU1x9mG/HOnq55lqlIAAAAABJRU5ErkJggg==')\",\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/00877f36d1251accb8ee1e7fe7d01628/508ef/image9.png\",\n \"srcSet\": [\"/static/00877f36d1251accb8ee1e7fe7d01628/a2ead/image9.png 259w\", \"/static/00877f36d1251accb8ee1e7fe7d01628/6b9fd/image9.png 518w\", \"/static/00877f36d1251accb8ee1e7fe7d01628/508ef/image9.png 578w\"],\n \"sizes\": \"(max-width: 578px) 100vw, 578px\",\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, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", MOPs, and MOSs are used synergistically to evaluate the\\neffectiveness and suitability of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" directly measure the degree\\nto which the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can achieve mission effects and successfully conduct\\noperations; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are the primary method of evaluating the question posed\\nby the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". Per the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Acquisition Guidebook\"\n }, \"DAG\"), \", several MOPs and/or MOSs may be related to the\\nachievement of a particular mission effect. MOPs and MOSs are not\\nsubordinate to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", nor are they required to calculate the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \".\\nHowever, MOPs and MOSs are an important part of determining the\\neffectiveness and suitability of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \". MOPs and MOSs indicate specific\\nstrengths and weaknesses of a system, mitigate the statistical issues\\nassociated with the typically small sample size of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" data, and support\\nor refute the conclusions drawn from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" data. The next section\\ndiscusses the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" format for documenting the details of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", MOPs\\nand MOSs.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#developing-measures-of-effectiveness","title":"Developing Measures of Effectiveness"},{"url":"#developing-measures-of-performance-and-measures-of-suitability","title":"Developing Measures of Performance and Measures of Suitability"}]},"parent":{"__typename":"File","relativePath":"measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT.md"},"frontmatter":{"metaTitle":"SECTION 2 MEASURES DEVELOPMENT","metaDescription":"SECTION 2 MEASURES DEVELOPMENT"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"eddffb95-1616-5902-919b-7efa8e29efbe"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION/page-data.json b/sites/oteguide/page-data/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION/page-data.json new file mode 100644 index 00000000..dbec650d --- /dev/null +++ b/sites/oteguide/page-data/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"90922035-a6f4-5f59-be33-5e1a4fe8c503","title":"SECTION 3 MEASURE DOCUMENTATION","slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION"},"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\": \"SECTION 3 MEASURE DOCUMENTATION\",\n \"metaTitle\": \"SECTION 3 MEASURE DOCUMENTATION\",\n \"metaDescription\": \"SECTION 3 MEASURE DOCUMENTATION\"\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, \"Measures Worksheet Overview\"), mdx(\"p\", null, \"The Measures Worksheet is a template used to document and organize the\\nfollowing details of a measure:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure:\"), \" A measure statement that describes what type of data is\\nbeing collected\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Metric(s):\"), \" The metric used to summarize the data (mean,\\npercentile, etc.)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Threshold (Optional):\"), \" The threshold of performance used to\\nevaluate the effectiveness of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Results:\"), \" The results attributed to observed and calculated data\\nprocured during test execution\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Rating (Optional):\"), \" The comparison of Results against the\\nThreshold, communicating any \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Effectiveness and Suitability\"\n }, \"E&S\"), \" shortfall\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Operational Capability:\"), \" Attribute of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" being measured\\n(MOPs/MOSs only)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"References:\"), \" The source document that motivated the creation of\\nthe measure\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Scope:\"), \" The scope of the measure\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Methodology:\"), \" The test methodology used to generate the data\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Design:\"), \" The test design used to generate the data\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data and Analysis:\"), \" Data that may be required to compute the\\nmeasure, formulas required, and the intended method of analysis\"))), mdx(\"p\", null, \"Table 1 shows the measures worksheet template.\"), mdx(\"p\", null, \"Table 1. Measures Worksheet Template\"), mdx(\"table\", null, mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Operational Capability: State the OC (attribute)\"), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Measure\"), mdx(\"td\", null, \"Metric\"), mdx(\"td\", null, \"Threshold\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOE/P/S X.Y: State the Measure (In Title Case)\"), mdx(\"td\", null, \"State the specific metric\"), mdx(\"td\", null, \"Provide the value/units and any conditions/subsets specified\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"* KPP or Supports KPP (include as required)\"), mdx(\"p\", null, \"^ Identified Standard (include as required)\")), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", null, \"References:\"), \" Provide the requirement source (stated or derived). Specify the paragraph, section, line, etc.\"), mdx(\"p\", null, mdx(\"strong\", null, \"Scope:\"), \" Describe the measure and how it relates to the operation in terms of duration, procedures, start/end times, limitations, etc\\u2026 If the language in the measure or metric is not self-explanatory or is ambiguous, provide definition(s). For instance, define users, operators, successful or unsuccessful, and linkages to other measures. Concisely discuss operational relevance of the measure.\"), mdx(\"p\", null, mdx(\"strong\", null, \"Test Methodology:\"), \" Describe how the data used to support the measure is generated (modeling and simulation, open-air testing, analysis).\"), mdx(\"p\", null, mdx(\"strong\", null, \"Test Design:\"), \" Since tests are designed at the operation/COI level, this section will generally refer back to that level with the statement \\u201CUses the overarching operation/COI test design.\\u201D However, if unique factors and levels for this measure are identified in the Test Conditions section above, then a separate test design for the measure is required and should be summarized here.\"), mdx(\"p\", null, mdx(\"strong\", null, \"Data and Analysis:\"), \" Identify the minimum data required to compute the metric(s). Describe how the data will be collected, the sources of the data, and instrumentation required to collect the data. Provide an overview of the expected analysis method(s), equations, algorithms, and tools necessary for analysis.\"))))), mdx(\"h1\", null, \"Measures Worksheet Header\"), mdx(\"p\", null, \"The header of the measures worksheet contains a concise summary of the\\nmost important information regarding a measure. It states the attribute\\nof the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" the test team is interested in evaluating (operational\\ncapability), a short title (measure statement) describing what is being\\nmeasured that will convey information about the attribute, how it will\\nbe computed (the metric), and what will serve as the basis for judging\\nthe metric (the threshold). Table 2 is an example of the standard format\\nfor the measures worksheet header.\"), mdx(\"p\", null, \"Table 2. Standard Measures Worksheet Header\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226420 meters\")))), mdx(\"p\", null, \"The header can be expanded to accommodate more detailed requirements.\\nFor instance, a requirement may provide context, such as an operational\\ncondition, for a threshold of performance. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" convention is to\\ndenote these specific conditions with the \\u201C@\\u201D symbol trailing the\\nthreshold and preceding the condition. For example, if the miss distance\\nfor a particular munition is specified for a particular wind speed\\n(condition), the measure would be as shown in table 3.\"), mdx(\"p\", null, \"Table 3. Measures Worksheet Header with Conditions\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226420 meters @ 30 knots wind speed\")))), mdx(\"p\", null, \"Sometimes the threshold of the metric changes depending on which\\nsubcomponent or subset of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is being evaluated. In this case the\\nconvention is to add the word \\u201Cfor\\u201D after the threshold and specify the\\nrelevant subcomponent or subset. Consider the following requirements.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\u201CThe system shall send deliver priority 1 messages within 30\\nseconds\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\u201CThe system shall send deliver priority 2 messages within 5 minutes\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\u201CThe system shall send deliver priority 3 messages within 15\\nminutes\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\u201CThe system shall send deliver priority 4 messages within 1 hour\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\\u201CThe system shall send deliver standard messages within 6 hours\\u201D\"))), mdx(\"p\", null, \"Table 4 shows these five requirements can be combined into one measure,\\nrather than five separate measures.\"), mdx(\"p\", null, \"Table 4. Measures Worksheet Header with Combined Conditions\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Time to Deliver Messages\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226430 seconds for Priority 1\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22645 minutes for Priority 2\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226415 minutes for Priority 3\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22641 hour for Priority 4\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22646 hours for Standard\")))), mdx(\"p\", null, \"This construct can be extended to create more complex measures that\\ninclude multiple metrics, thresholds, conditions, and subsets. Table 5\\nis an example of a multi metric/threshold measure.\"), mdx(\"p\", null, \"Table 5. Measures Worksheet Header with Multi Metric/Threshold\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Time to Deliver Messages\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"50th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22641 minute for Priority 1\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"80th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22648 minutes for all others\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22643 minutes @ Wartime for Priority 1\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"99th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226410 minutes for Priority 1\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226420 minutes for all others\")))), mdx(\"p\", null, \"Combining thresholds for different conditions and subsets of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" has\\nadvantages and disadvantages. One advantage is the reduction in\\ndocumentation. One disadvantage is that each measure is rated only once\\nin a report, even if it has multiple thresholds. Thus if there is a mix\\nof good and bad results within one measure, the good news, the bad news,\\nor both may be hidden behind the single summary rating.\"), mdx(\"p\", null, \"A measure is read aloud in a specific way to accurately convey its\\ncontents. The measure is read: \\u201CThe \", \"<\", \"metric\", \">\", \" of the\\n\", \"<\", \"measure\", \">\", \" is \", \"<\", \"threshold\", \">\", \".\\u201D For instance, the measure shown\\nin table 6 is read: \\u201CThe \", mdx(\"u\", null, \"mean\"), \" of the \", mdx(\"u\", null, \"miss distance\"), \" is\"), mdx(\"u\", null, \"less than or equal to 20 meters\"), \".\\u201D\", mdx(\"p\", null, \"Table 6. Reading a Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226420 meters\")))), mdx(\"h1\", null, \"Body of the Measures Worksheet\"), mdx(\"p\", null, \"The body of the measures worksheet contains five sections: References;\\nScope; Test Methodology; Test Design; Data and Analysis.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"References:\"), \" Provide the requirement source (stated or derived).\\nSpecify the paragraph, section, line, etc.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Scope:\"), \" Describe the measure and how it relates to the operation in\\nterms of duration, procedures, start/end times, limitations, etc. If the\\nlanguage in the measure or metric is not self-explanatory or is\\nambiguous, provide definitions. For instance, define users, operators,\\nsuccessful or unsuccessful, and linkages to other measures. Concisely\\ndiscuss operational relevance of the measure.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Methodology:\"), \" Describe how the data used to support the measure\\nis generated (modeling and simulation, open-air testing, analysis).\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Design:\"), \" Since tests are designed at the operation/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" level,\\nthis section will generally refer back to that level with the statement\\n\\u201CUses the overarching operation/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" test design.\\u201D However, if unique\\nfactors and levels for this measure are identified in the test\\nconditions section above, then a separate test design for the measure is\\nrequired and should be summarized here.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data and Analysis:\"), \" Identify the minimum data required to compute the\\nmetrics. Describe how the data will be collected, the sources of the\\ndata, and instrumentation required to collect the data. Provide an\\noverview of the expected analysis methods, equations, algorithms, and\\ntools necessary for analysis.\"), mdx(\"h1\", null, \"Formatting Measures\"), mdx(\"p\", null, \"The following are formatting conventions for the measures worksheet.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure Statement\"), \". Write measures statements in title case, i.e.,\\nuse capital letters for all principal words. Articles, conjunctions and\\nprepositions do not get capital letters unless they start the measure\\nstatement. All acronyms are spelled out in each measure, regardless if\\nthey have been used before in the document; this enables the measures\\nworksheet, and the header when separated from the full worksheet, to be\\ncomprehensible without other documentation. Table 7 shows a properly\\nformatted measure statement with acronyms.\"), mdx(\"p\", null, \"Table 7. Acronym Usage\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.4: Electro-Optical (\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Electro-Optical OR Executive Order OR Engineering Order\"\n }, \"EO\"), \") National Imagery Interpretation Rating Scale (NIIRS) Rating\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Minimum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u2265 NIIRS 6 @ 450 km\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Key Performance Parameter (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \")\"), \": If the measure is derived from a\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or supports a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \", the measure designator is preceded by an asterisk\\n(\", \"*\", \"). Additionally, a legend with the text \\u201C\", \"*\", \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or Supports \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \"\\u201D is\\nadded as another row at the bottom of the measure table, as shown in\\ntable 8.\"), mdx(\"p\", null, \"Table 8. Identifying a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \"\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Reliability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"*\", \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" 4.1: Time Between Failures\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226550 hours\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"*\", \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \" or Supports \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \"\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Identified Standards:\"), \" If a test team must develop a measure from a\\nrequirement that fails to provide a clear metric or threshold of\\nperformance, the test team can ask the user community for an appropriate\\nmetric or threshold; this value is known as an identified standard.\\nThere is a convention to highlighting and documenting identified\\nstandards on a measures worksheet. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" denotes an identified standard\\nby placing a carrot symbol (^) to the top left of the user-created\\nmetric or threshold. The source of the identified standard must be\\nexplained in the References section of the measures worksheet, which\\nshould start with the phrase \\u201CDerived from\\u2026\\u201D\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Example:\"), \" The requirement states: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe miss distance shall be less\\nthan or equal to 15 meters.\\u201D\")), mdx(\"p\", null, \"While the measure statement (miss distance) and threshold (less than or\\nequal to 15 meters) are provided, the requirement does not explicitly\\nstate what the metric should be. The test team consults with the user\\nand determines the correct metric is circular error probable (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \").\\nSince this was not explicitly stated in the requirements document, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"\\nis an identified standard and must be annotated with a carrot symbol\\n(^\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"). Additionally a legend with the text \\u201C^ Identified Standard\\u201D is\\nadded as another row at the bottom of the measures worksheet header.\\nTable 9 shows how the additional information is incorporated.\"), mdx(\"p\", null, \"Table 9. Indicating an Identified Standard\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Operational Capability: Accuracy\"), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Measure\"), mdx(\"td\", null, \"Metric\"), mdx(\"td\", null, \"Threshold\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 2.1: Miss Distance\"), mdx(\"td\", null, \"^ CEP\"), mdx(\"td\", null, \"\\u2264 15 meters\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"* KPP or Supports KPP\", mdx(\"br\", null), \"^ Identified Standard\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"References:\"), \" Derived from weapon system subject matter expert (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \")\\njudgement based on operational experience on legacy systems and\\n\\u201CTechnical Requirements Document (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technical Requirements Document\"\n }, \"TRD\"), \"): Air Force (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \") Munition X 16 Dec\\n15, table 14, items 3.1.8 and 5.0.13-5.0.15\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Threshold:\"), \" If the measure is quantitative or ordinal, the threshold\\nmust be preceded by an equality or inequality mathematical symbol (=, \\u2264\\nor \\u2265).\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#measures-worksheet-overview","title":"Measures Worksheet Overview"},{"url":"#measures-worksheet-header","title":"Measures Worksheet Header"},{"url":"#body-of-the-measures-worksheet","title":"Body of the Measures Worksheet"},{"url":"#formatting-measures","title":"Formatting Measures"}]},"parent":{"__typename":"File","relativePath":"measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION.md"},"frontmatter":{"metaTitle":"SECTION 3 MEASURE DOCUMENTATION","metaDescription":"SECTION 3 MEASURE DOCUMENTATION"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"90922035-a6f4-5f59-be33-5e1a4fe8c503"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES/page-data.json b/sites/oteguide/page-data/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES/page-data.json new file mode 100644 index 00000000..21061601 --- /dev/null +++ b/sites/oteguide/page-data/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"52fe8d68-e903-5bd3-aadb-8a66688074a5","title":"APPENDIX A CATEGORIES OF MEASURES","slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES"},"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\": \"APPENDIX A CATEGORIES OF MEASURES\",\n \"metaTitle\": \"APPENDIX A CATEGORIES OF MEASURES\",\n \"metaDescription\": \"APPENDIX A CATEGORIES OF MEASURES\"\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 primary goal of creating a well-written measure is to maximize the\\namount and quality of information obtained and to communicate the\\npurpose of a measure as effectively as possible. There are two different\\ncategories of measures used in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" testing: continuous, and discrete.\\nA number of measures from each category are typically included in a test\\nprogram. Together, these measures help form a basis for judgement about\\nthe system under test.\"), mdx(\"span\", {\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/ca059850c6d356ca47f16d936d93c9a1/e9140/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\": \"39.768339768339764%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAICAYAAAD5nd/tAAAACXBIWXMAABYlAAAWJQFJUiTwAAABkklEQVQoz22S7U/aUBTG+f+/78NMlm2JbsGhUXQ6Z6uUlzaW0RdIC9S2CkoWAoroF1ugP29LRJ17kif3nHuf+9yXc3IIJEmSMUOyII4eiaKIOI6Zz2fLeRZZnlGsJYs5/+5Nx9zKSGA4uqEd/sXoDNBaPWpWiGadU9GbqGYX1Q4oGz6608MVulT/jGefXLLM6ARXFE9NPhckvmxJbP3W0dpD8sc2G7LHpuIjGX3q3pj1XUVoZIolC+9ikBqsbppL/W4nU04bISXjgu97CgeVFrLusV9x+VSs87FQ4UO+xLfjJkdah/zPqtCVUaw+ihEynd6/PDkNJnepYYBi9tgrmeJkk33FYls2+HposbZdE1TJyw6Sfs7uSYPCkUbZvl4a3j+8/sMsxAuv+aW64lYOB1UX1R1y1h2xKTXFk7v8KAfIxhWNYCJMfXZOLA5rDv7l4E1x3hRlfDOhHQxouH1RkADNDtFbPuqfFrrtcdYMqZo+decSV+hG49v3RXnXNgKzOBKMMy5WbZMs52Zxtp7m/2ubJ8zRRpbI+S2LAAAAAElFTkSuQmCC')\",\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/ca059850c6d356ca47f16d936d93c9a1/e3189/image10.png\",\n \"srcSet\": [\"/static/ca059850c6d356ca47f16d936d93c9a1/a2ead/image10.png 259w\", \"/static/ca059850c6d356ca47f16d936d93c9a1/6b9fd/image10.png 518w\", \"/static/ca059850c6d356ca47f16d936d93c9a1/e3189/image10.png 1035w\", \"/static/ca059850c6d356ca47f16d936d93c9a1/e9140/image10.png 1226w\"],\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, \"Continuous Measures\"), mdx(\"p\", null, \"Quantitative measures with data collected objectively tend to be the\\nmost informative and easiest to substantiate because they enable broader\\nstatistical applications. This is because they often have the property\\nof being continuous, where the resulting measure and metric have an\\ninfinite number of possible values in a range. For example, suppose\\nthere is a requirement for the overall weight of the system under test\\nmust be between a specified range. The weight of the system is a\\ncontinuous measure because it can take on any value of weight, within\\nthe range zero to infinity.\"), mdx(\"p\", null, \"It is important to note that there are several advantages of having\\ncontinuous measures over discrete measures. Inferences can be made with\\nfewer continuous data points and valid analysis can be performed with\\nsmaller samples sizes. This smaller sample size typically translates\\ninto a shorter, less expensive test. When using discrete measures, a\\nmuch larger sample size (lengthier and costlier test) is required to\\nmake an equivalent inference. Additionally, continuous measures allow\\nfor more analysis options, which provide insight into the sources of\\nvariation.\"), mdx(\"p\", null, \"The remainder of this section expands on the common metrics associated\\nwith continuous measures and includes examples taken from previous\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test programs. This list of metrics is not meant to be exhaustive\\nbut intended to represent those that are commonly used in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntesting. If other metrics are warranted, consult with the Intelligence,\\nAnalyses and Assessments Directorate (A-2/9) to determine proper format\\nand usage.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Mean.\"), \" A mean is a measure of the central tendency of a data set and\\nindicates, generally, where the data is clustered. In most cases, this\\nis the arithmetic mean, commonly known as the average. Using mean as a\\nmetric indicates a continuous, physical measure such as time, distance\\nor temperature. The measure is physical in the sense it can be measured\\nwith a stopwatch, ruler, thermometer or some other scaled instrument.\"), mdx(\"p\", null, \"Since the measure is physical and obtained by using a measuring device,\\nthe threshold must include the unit of measure (e.g. meters, degrees\\nFahrenheit, seconds, etc.). The three examples shown in tables A-1\\nthrough A-3 are mean measures with physical measures that are attainable\\nusing a measuring device. The metric in each case is \\u201Cmean\\u201D and the\\nthresholds all include an inequality (\\u2265 or \\u2264), followed by the threshold\\nand the unit of measure.\"), mdx(\"p\", null, \"Table A-1. Mean Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22645 meters\")))), mdx(\"p\", null, \"Table A-2. Mean Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Reliability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" 4.1: Time Between Failures\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226550 hours\")))), mdx(\"p\", null, \"Table A-3. Mean Measure 3\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Reliability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 4.1: Exhaust Temperature\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mean\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u2264395\", mdx(\"sup\", null, \"o\"), \" Fahrenheit\")))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Mean Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the threshold physical and continuous?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Keep in mind that the arithmetic mean can be sensitive to every value in the data set, including extremes. This effect is especially noticeable when the sample size is small.\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Percentile.\"), \" A percentile divides a ranked or ordered set of data\\ninto 100 equal groups. These groups can be specified (e.g., 95th, 90th,\\n50th, 1st Quartile) for comparison against the threshold. A percentile\\nindicates the value below which a given percentage of the population\\nfalls. A percentile is distinct from a percentage in that a percentile\\nexpresses a relational comparison to a population while a percentage\\ndescribes the relation of one part to the whole, expressed as a fraction\\nof 100. For instance, a student with a score of 80% on a 100 question\\ntest (80 out of 100 questions correct) may be in the 95th percentile if\\nthe student scored better than 95% of all the other students (a\\ncomparison).\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201C95% of messages must be sent\\nwithin 15 minutes\\u201D\"), \" This requirement is expressed as a percentile and\\nthe resulting measure is shown in table A-4. Since percentile measures\\nare continuous and obtained from a physical measure, the threshold must\\ninclude a unit of measure consistent with the measure itself.\"), mdx(\"p\", null, \"Table A-4. Percentile Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.4: Time to Send Message\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"95th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226415 minutes\")))), mdx(\"p\", null, \"When analyzing the results of a test in relation to a percentile\\nmeasure, it is important for the test team to carefully assess the data\\nto determine whether the percentile for the test results is appropriate\\nto make a determination about the population.\"), mdx(\"p\", null, \"In the example above, suppose the test team collects data and finds that\\n95% of the message send times are 17 minutes and below. The test team\\nhas options in determining the 95th percentile of the collected data.\\nThe easiest is to take the empirical data \\u201Cas is\\u201D and mark where the\\n95th percentile falls. The test team may also attempt to fit a\\ndistribution to the empirical data and, depending on the goodness of\\nfit, make a different determination of where the 95th percentile falls.\\nThese two methods will likely produce different results for the 95th\\npercentile and it is up to the test team\\u2019s judgment to determine the\\nmost appropriate analysis technique, taking into account the operational\\nsignificance of the result.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Percentile Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the threshold physical and continuous?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the metric include the percentile value (not just the word \\u201CPercentile\\u201D)\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a percentile applicable to the requirement or is there another metric more appropriate?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the team intend to report the percentile of the empirical data or of a fitted distribution?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sample size sufficient for a percentile to be meaningful?\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Minimum/Maximum.\"), \" Minimum/maximum measures set the threshold as a\\nhard limit for performance, where a single instance exceeding or falling\\nbelow the threshold indicates the measure\\u2019s criteria has not been met.\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe system must be able to\\naccommodate planning for a new mission within 16 hours\\u201D\"), \" A min/max\\nmeasure would take the form as outlined in table A-5, with the metric\\nset as \\u201CMaximum\\u201D and the threshold less than or equal to \\u201C16 hours\\u201D. A\\nsingle mission planning session that lasts more than 16 hours will\\nresult in the measure being rated as not met. Because min/max metrics\\nestablish a hard limit for performance, the test team should consider\\nthe operational significance prior to test, to determine if a min/max\\nmetric is warranted.\"), mdx(\"p\", null, \"Table A-5. Continuous Maximum Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.4: Time to Mission Plan\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226416 hours\")))), mdx(\"p\", null, \"Minimum/Maximum metrics can be applied to any continuous data type where\\na single event beyond the threshold is unacceptable (i.e. danger close\\nor collateral damage where the consequence is too severe to tolerate).\\nTable A-6 is a reasonable maximum metric, where if a single bomb is\\nfarther than 9 meters from the target the entire measure does not meet.\\nSince this measure is continuous, if there is a recorded event with a\\nmiss distance greater than 9 meters, the test team will have sufficient\\ndata to apply descriptive statistics techniques to characterize the\\noverall performance of all the events, the variability of those events,\\nand the comparative impact of the above-threshold event to state \\u201Cdoes\\nnot meet threshold.\\u201D\"), mdx(\"p\", null, \"Table A-6. Continuous Maximum Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22649 meters\")))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Continuous Minimum/Maximum Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265, \\u2264 or =?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sign appropriate for the metric (\\u201C\\u2264\\u201D for a Maximum, \\u201C\\u2265\\u201D for a Minimum, or an equals sign \\u201C=\\u201D in certain cases)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the metric spelled out completely (no \\u201CMin\\u201D or \\u201CMax\\u201D)?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a minimum/maximum metric operationally relevant?\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Error Probable.\"), \" There are multiple variations of the error probable\\nmetric including, but not limited to, circular, elliptical and\\nspherical. Each of these finds different levels of use in different\\ncommunities however, the most common is the circular error probable\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"). All of these principles apply to all variations of the error\\nprobable metric, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" is used here as an example.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" metric is used to measure the precision of a weapon system. It\\nis defined as the radius of a circle, centered at the mean, with the\\ncircle boundary expected to encompass some percentage (generally 50%,\\ndenoted \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \") of the population. As a probability distribution, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"\\ncan also describe a more inclusive boundary (such as 90%, denoted CE90),\\na threshold that should be made clear in the system requirements and in\\nthe resulting measure. If the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" is 20 meters for a particular\\nmunition, then we would expect 50% of them to land within 20 meters of\\nthe target.\"), mdx(\"p\", null, \"Since \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" corresponds to a physical measure, the threshold must include\\nthe units of measure. Additionally, the probability must be included in\\nthe metric. The example in table A-7 is for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" where 50% of the\\npopulation is expected to hit within 15 meters of the target.\"), mdx(\"p\", null, \"Table A-7. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.4: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226415 meters\")))), mdx(\"p\", null, \"While the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \" is a widely used metric, there are underlying assumptions\\nabout the population that are often not met and the test team must\\ncarefully consider these when analyzing results. For instance, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Circular Error Probability\"\n }, \"CEP\"), \"\\nis based on a circular bivariate normal distribution, but dropped\\nmunitions may not be normally distributed in this way. Consider an\\naircraft dropping a grouping of gravity bombs on a target from a single\\ndirection. As these bombs hit, they will likely tend to vary greater on\\nthe down range axis (the direction of travel) with a smaller\\nside-to-side variation on the axis perpendicular to the direction of\\ntravel. The result is a distribution where the circle is stretched along\\nthe range axis and contracted on the perpendicular axis, forming an\\nellipse instead. There are options for analysis in this case and the\\ntest team should contact the Intelligence, Analyses and Assessments\\nDirectorate (A-2/9) for assistance.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Error Probable Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the metric include the probability?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Are the underlying assumptions about the metric realistic for the operational scenario?\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Probability.\"), \" A probability is used to make a predictive inference\\nabout a population based on sample data. Probability measures can be\\ndiscrete or continuous, depending on the underlying measurements, and\\nwill have a threshold given as a decimal between 0 and 1. In test, there\\nare a variety of probabilities that are commonly used: Probability of\\noperational availability (A\", mdx(\"sub\", null, \"o\"), \"), Probability of materiel\\navailability (A\", mdx(\"sub\", null, \"m\"), \"), probability of kill (P\", mdx(\"sub\", null, \"k\"), \"),\\nProbability of Detect (P\", mdx(\"sub\", null, \"d\"), \"), etc. The predictive ability of a\\nprobability and its utility as a measure depend on many elements such as\\nthe size of the sample space, the number of factors and levels in a test\\ndesign that impact the measure, and the variability of the data.\"), mdx(\"p\", null, \"A probability measure has two formatting conditions. First, to clearly\\nexpress the probability as part of the measure statement, the phrase\\n\\u201CProbability of\\u201D is placed at the beginning of the measure statement.\\nSecond, since probability is the metric for the measure, the cells below\\nthe headers for \\u201CMetric\\u201D and \\u201CThreshold\\u201D are merged (while maintaining\\nthe header cells) and the threshold is entered with the appropriate\\ninequality (\\u2265, \\u2264) and a value between 0 and 1. The examples in tables\\nA-8 and A-9 are typical probability measures.\"), mdx(\"p\", null, \"Table A-8. Probability Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Availability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \" 4.2: Probability of Operational Availability (A\", mdx(\"sub\", null, \"o\"), \")\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22650.90\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"Table A-9. Probability Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Lethality\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.5: Probability of Kill (PK)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22650.95\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Probability Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the threshold a value between 0 and 1?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the metric and threshold cells merged?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the measure name include the phrase \\u201CProbability of\\u201D?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the sample size sufficient to determine a probability with a reasonable confidence interval?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is a probability meaningful for the operational scenario?\"))))))), mdx(\"h1\", null, \"Discrete Measures\"), mdx(\"p\", null, \"Discrete measures are those where the measure and metric have a finite\\nnumber of possible values and can only take specific values in a range.\\nDiscrete measures are typically counted in whole numbers. For example,\\nsuppose a requirement states that the number of C-17s required to deploy\\nshall be two or less. This measure is discrete because the number of\\naircraft can only take on whole number values (i.e., you cannot have 2.5\\naircraft).\"), mdx(\"p\", null, \"Discrete measures with only two outcomes (e.g., yes/no,\\nsuccessful/unsuccessful, hit/miss) are sometimes referred to as \\u201Cbinary\\u201D\\nmeasures; however, discrete measures can have more than two bins as well\\n(e.g., easy/average/hard, high/medium/low).\"), mdx(\"p\", null, \"It is important to note that there are several advantages of having\\ncontinuous measures over discrete measures. Inferences can be made with\\nfewer continuous data points and valid analysis can be performed with\\nsmaller samples sizes. This smaller sample size typically translates\\ninto a shorter, less expensive test. When using discrete measures, a\\nmuch larger sample size (lengthier and costlier test) is required to\\nmake an equivalent inference. Additionally, continuous measures allow\\nfor more analysis options, which provide insight into the sources of\\nvariation.\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe system shall successfully hit\\nthe target 85% of the time. A successful hit is one where the munition\\nlands within 5 meters of the target center.\\u201D\"), \" We can construct two\\nmeasures from this requirement, one discrete and one continuous, shown\\nin tables A-10 and A-11, respectively.\"), mdx(\"p\", null, \"Table A-10. Discrete Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Weapon Releases that are on Target\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226585%\")))), mdx(\"p\", null, \"Table A-11. Continuous Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"85th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22645 meters\")))), mdx(\"p\", null, \"Both of these measures are valid for the requirement, but which one is\\nbetter? Assume we go to test and obtain the following results:\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Launch\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Miss Distance (Continuous)\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Weapon Release on Target? (Discrete)\"))), 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 }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), 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 }, \"0\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), 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 }, \"0\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), 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 }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"6\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"7\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"8\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"91\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Miss\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"9\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"10\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"11\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"12\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"13\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"14\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"0\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"15\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"16\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"135\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Miss\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"17\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"18\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"19\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"20\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Hit\")))), mdx(\"p\", null, \"If we look at the discrete data only and evaluate the measure, we see\\nthat 90% of the munitions were on target. This is greater than the\\nthreshold of 85% so the test team would rate this measure as having no\\nshortfalls as illustrated in table A-12.\"), mdx(\"p\", null, \"Table A-12. Evaluating the Discrete Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Results\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Weapon Releases that are on Target\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226585%\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"90%\")))), mdx(\"p\", null, \"If we use the continuous measure and analyze the miss distance, we see\\nthat the 85th percentile is 5 meters however, we also see that when the\\nsystem missed, it missed by 91 and 135 meters. By using a continuous\\nmeasure, this additional information about the variance is available to\\nthe test team allowing them to rate this measure more accurately,\\ndepending on the operational significance of the data.\"), mdx(\"p\", null, \"Table A-13. Evaluating the Continuous Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Results\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Miss Distance\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"85th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22645 meters\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5 meters\")))), mdx(\"p\", null, \"Therefore, as a general rule, if a measure is discrete, the test team\\nshould consider if there is any way to express the measure as\\ncontinuous. This will not be possible in all instances, but in some\\ncases the opportunity to create a continuous measure is obscured in an\\nimproperly or poorly written discrete measure or requirement.\"), mdx(\"p\", null, \"The remainder of this section expands on the common metrics associated\\nwith discrete measures and includes examples taken from previous \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntest programs. This list of metrics is not meant to be exhaustive but\\nintended to represent those that have been commonly used in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntesting. If other metrics are warranted, consult with the Intelligence,\\nAnalyses and Assessments Directorate (A-2/9) to determine proper format\\nand usage.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Minimum/Maximum.\"), \" Minimum/Maximum measures can be either continuous\\nor discrete. Min/Max measures set the threshold as a hard limit for\\nperformance, where a single instance exceeding or falling below the\\nthreshold indicates the measure\\u2019s criteria has not been met.\"), mdx(\"p\", null, \"For discrete measures, the min/max metric can be problematic and the\\nanalysis of the results must consider the data as a whole. While the\\nsingle event that exceeds the threshold marks the measure as \\u201Cnot met,\\u201D\\nthe test team must consider the true operational impact of that\\nsingle-point failure.\"), mdx(\"p\", null, \"Discrete min/max measures are often the result of vague or poorly\\nwritten requirements with an unreasonably high expected level of success\\nnot typically seen in any system or process. In these cases, the test\\nteam should consult with the user to determine the validity of the\\nrequirement and highlight the consequences of single-point failures.\"), mdx(\"p\", null, \"For example, consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CMessage exchange will\\nnot interfere with other system components\\u201D\"), \" The test team may decide to\\ncount the number of interference events and set the threshold to zero.\\nThis results in the maximum measure shown in table A-14.\"), mdx(\"p\", null, \"Table A-14. Discrete Maximum Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Interoperability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.8: Number of Interface Exchange Requirements (\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Information Exchange Requirements\"\n }, \"IER\"), \") Not Met\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"= 0\")))), mdx(\"p\", null, \"A single instance of interference will result in the measure being rated\\nas \\u201Cnot met\", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201D\"), \" with the test team then having to make a determination of\\nwhether this is an operationally significant shortfall. While this is\\nthe assessment method as outlined in the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Guide\"), \", the test\\nteam should consider this question of \\u201Coperational significance\\u201D before\\nexecuting the test and, in conjunction with the user and SMEs, develop\\nan identified standard that defines what is actually required as a\\nthreshold. Although this may not result in a continuous measure, the\\ntest team will have defined operational significance before executing\\nthe test.\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CEleven active terminals will be\\navailable at each command station at all times\\u201D\"), \" In this case, the test\\nteam may decide to use a minimum metric, and construct the measure shown\\nin table A-15.\"), mdx(\"p\", null, \"Table A-15. Discrete Minimum Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accessibility\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.5: Number of Active Terminals in each Command Station\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Minimum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226511 Terminals\")))), mdx(\"p\", null, \"The question of operational significance comes into play here. Is it\\noperationally significant if one terminal is unavailable for 10 minutes\\nover a weeklong test? The test team should consult with the user and\\nSMEs to determine the answer to this question. If it is not\\noperationally significant, the team can coordinate with the user and\\nSMEs to determine a more operationally informative and meaningful\\nthreshold. A potential substitution for the above threshold is shown as\\nan identified standard in the measure shown in table A-16.\"), mdx(\"p\", null, \"Table A-16. More Operationally Meaningful Continuous Minimum Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accessibility\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.5: Time each Terminal is Active\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Minimum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ \\u226516 hours/day\")))), mdx(\"p\", null, \"In some cases the test team may want to create a measure that counts the\\nnumber of instances of an event. If the underlying population being\\ncounted cannot be reasonably known, or if the number of opportunities\\nthat may occur (and be counted) cannot be known, then a count measure\\nmay be in order. While it may seem natural to use \\u201CCount\\u201D as the metric,\\nin practice either \\u201CMinimum\\u201D or \\u201CMaximum\\u201D are used as the metric and the\\nphrase \\u201CNumber of\\u201D is placed as a lead in to the measure.\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CShall not induce runway\\nincursions\\u201D\"), \" In this case, the test team will have no way of knowing how\\nmany runway incursions there might be, so the best option is to simply\\ncount the number of runway incursions. The measure is shown in table\\nA-17. The metric is \\u201CMaximum\\u201D and the phrase \\u201CNumber of\\u201D leads the\\nmeasure. The Threshold (as implied in the requirement) is \\u201Czero.\\u201D\"), mdx(\"p\", null, \"Table A-17. Discrete Maximum Counting Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Vulnerability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.5: Number of Runway Incursions\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"=0\")))), mdx(\"p\", null, \"The reason for using \\u201CMaximum\\u201D or \\u201CMinimum\\u201D as the metric instead of\\n\\u201CCount\\u201D is so the boundary or limit is clearly identified in the\\nmeasure. \\u201CCount\\u201D by itself does not express to the reader the direction\\nof either a good or bad result.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Discrete Minimum/Maximum Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265, \\u2264 or =?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sign appropriate for the metric (\\u201C\\u2264\\u201D for a Maximum, \\u201C\\u2265\\u201D for a Minimum, or an equals sign \\u201C=\\u201D in certain cases)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the metric spelled out completely (no \\u201CMin\\u201D or \\u201CMax\\u201D)?\"))), mdx(\"p\", null, \"Planning for Analysis\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a minimum/maximum metric/threshold operationally relevant?\")), mdx(\"li\", null, mdx(\"p\", null, \"Can the measure be made continuous?\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Proportion.\"), \" A proportion is the relation of one part to the whole\\nwith respect to magnitude, quantity, or degree. For example, \\u201C2 out of\\n10 pie pieces have been eaten\\u201D is a proportion where the 2 eaten pieces\\nof pie are part of the 10 pieces of the whole pie. Proportions can be\\npresented in two ways to show the relationship between the part and the\\nwhole, in written form or as a fraction. For example, \\u201C3 out of 5 fuses\\ndetonated\\u201D is a proportion where 3 fuses detonated (the part) out of the\\n5 total fuses considered (the whole).\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"In written form \\u2013 \\u201C3 out of 5 fuses detonated\\u201D\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"As a fraction \\u2013 \\u201C3/5\\u201D\"))), mdx(\"p\", null, \"Similarly, the threshold must also be expressed as a proportion. In\\nwritten form, the preferred method of communicating the relationship\\nbetween the \\u201Cpart\\u201D and the \\u201Cwhole\\u201D is with the words \\u201Cout of\\u201D between\\nthem. For instance, in the fuse example, if the requirement is for 80%\\nof the fuses to detonate, then the threshold would be \\u201C\\u2265 4 out of 5\\u201D\\nAlternatively, this can be expressed using the mathematical symbol for\\ndivision\\u2014\\u201C\\u2265 4/5\\u201D\\u2014which in turn leads to a third expression if the\\ndivision is carried out of \\u201C\\u2265 0.8.\\u201D \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"However\"), \", this last notation\\nshould be avoided when reporting proportions, even if the requirement\\nthreshold is stated in decimal or percentage format, as a decimal or\\npercentage implies greater precision than might actually be available.\"), mdx(\"p\", null, \"Because a proportion is properly expressed by including both parts of\\nthe relationship represented, the grammar of the measure\\u2014both written\\nand spoken\\u2014is critical to ensure the correct information is\\ncommunicated.\"), mdx(\"p\", null, \"The general format for reading a proportion aloud is:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe proportion of the \", \"<\", \"denominator\", \">\", \" that are \", \"<\", \"numerator \", \">\", \"\\nis \", \"<\", \"threshold\", \">\", \"\\u201D\")), mdx(\"p\", null, \"Or, stated another way:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe proportion of the \", \"<\", \"the whole\", \">\", \" that are \", \"<\", \"the part \", \">\", \" is\\n\", \"<\", \"threshold\", \">\", \"\\u201D\")), mdx(\"p\", null, \"The following measure is read:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe proportion of the \", mdx(\"u\", null, \"Detected Targets\"), \" that are \", mdx(\"u\", null, \"Correctly\\nIdentified\"), \" is \", mdx(\"u\", null, \"9\"), \" out of \", mdx(\"u\", null, \"10\"), \"\\u201D\")), mdx(\"p\", null, \"Table A-18. Proportion Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Detected Targets that are Correctly Identified\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Proportion\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22659 out of 10\")))), mdx(\"p\", null, \"The measure statement must contain the \\u201Cwhole\\u201D followed by the \\u201Cpart\\u201D\\nwith the words \\u201Cthat are\\u201D between them to properly express the\\nrelationship.\"), mdx(\"p\", null, \"To emphasize why the grammar of a proportion measure is critical,\\nconsider the following other possibilities using the same requirement:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe system shall identify targets correctly 90% of the time.\\u201D\")), mdx(\"p\", null, \"Table A-19 shows the first improper measure where the requirement is\\ntaken quite literally. The measure \\u201CTargets Identified Correctly\\u201D does\\nnot convey what the \\u201Cpart\\u201D and \\u201Cwhole\\u201D are and how they are related. Is\\nthe \\u201Cwhole\\u201D all targets presented, whether detected or not? Only\\ndetected targets? Being able to answer these questions may require\\nconsultation with the user to clarify the requirement. Without answering\\nthese questions, the test team will not know what data to collect and\\nhow to evaluate the measure.\"), mdx(\"p\", null, \"Table A-19. Improper Proportion Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Targets Identified Correctly\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Proportion\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22659 out of 10\")))), mdx(\"p\", null, \"Table A-20 shows the second improper measure. While the measure now\\nexpresses a relationship, because of the addition of the words \\u201Cthat\\nare,\\u201D is the \\u201Cpart\\u201D and \\u201Cwhole\\u201D adequately conveyed as expressed in the\\noriginal requirement? In the taxonomy, \\u201CTargets\\u201D represents the \\u201Cwhole\\u201D\\nbut it is unclear which targets\\u2014all targets or only the targets the\\nsystem detected? Again, thoughtful consideration must be given to ensure\\nboth elements are clearly identified (as expressed in table A-21),\\nleaving no ambiguity for the reader of the report.\"), mdx(\"p\", null, \"Table A-20. Improper Proportion Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Targets that are Correctly Identified\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Proportion\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22659 out of 10\")))), mdx(\"p\", null, \"Table A-21. Correct Proportion Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Detected Targets that are Correctly Identified\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Proportion\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22659 out of 10\")))), mdx(\"p\", null, \"Why not use a percentage as stated in the requirement? \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"Proportions\\nshould be used for small sample sizes\"), \" in lieu of a percentage. When\\nthe sample size is small, reporting a percentage may imply greater\\nprecision than actually exists; proportions paint a more accurate\\npicture of the data. For instance, going back to the fuse example,\\nstating \\u201C3 out of 5 fuses detonated\\u201D provides more insight than to say\\n\\u201C60% of the fuses detonated.\\u201D\"), mdx(\"p\", null, \"Consider the same requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe system shall identify targets\\ncorrectly 90% of the time.\\u201D\"), \" The percentage stated in the requirement\\nshould be expressed as a proportion (9 out of 10) if the test team\\nexpects the sample size of the test to be small (a common rule of thumb\\nis \", \"<\", \" \", \"~\", \"25 data points). If the test team expects the sample size to\\nbe large, then they should write the measure as a percentage (detailed\\nin the next section). Both measures in tables A-22 and A-23 are\\ntechnically correct for this requirement; however, the expected sample\\nsize will dictate which one to use.\"), mdx(\"p\", null, \"Table A-22. Proportion Measure for Small Sample Sizes\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Detected Targets that are Correctly Identified\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Proportion\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22659 out of 10\")))), mdx(\"p\", null, \"Table A-23. Equivalent Percentage Measure for Large Sample Sizes\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Geolocation Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Detected Targets that are Correctly Identified\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226590%\")))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Proportion Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the measure clearly express a relationship between the \\u201Cwhole\\u201D and the \\u201Cpart\\u201D?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cwhole\\u201D listed first and the \\u201Cpart\\u201D listed second?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cthat are\\u201D used to convey the relationship?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are both parts of the relationship clearly and concisely expressed with no double meaning?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cout of\\u201D used to convey the relationship in the threshold?\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Alternatively a division symbol can be used (3/5)\"))))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Can the measure be made continuous?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the expected sample size support the decision to use a proportion metric?\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report proportion measure results in decimal form alone. If the requirement is given in a decimal or percentage, report the result as a proportion and annotate the decimal/percentage notation for comparison to the threshold of the requirement.\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report results in vague quantitative terms such as \\u201Ca majority of targets were correctly identified.\\u201D Always include the actual quantitative values.\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Percentage.\"), \" A percentage describes the relation of one part to the\\nwhole and is then expressed as a fraction of 100. Percentage should not\\nbe confused with percent, which strictly represents a part out of 100 as\\nthe name implies. For instance, if you have 40 apples, then 10% of the\\n40 apples is 4 apples. The 4 apples is the percentage of the 40 apples\\nrepresented by 10%. Since percent implies part of 100, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" convention\\nis not to use percent as a metric but to use percentage instead.\"), mdx(\"p\", null, \"A percentage is distinguished from a percentile in that while a\\npercentage describes a specific part/amount of the whole, a percentile\\ndescribes a relational comparison to a population. For instance, suppose\\na class of 100 students is given a test with 50 questions. If a student,\\nMary, gets 40 correct, then the percentage (the 40 correct answers) that\\nMary got correct is 80%. However, there is no information about how Mary\\ncompares to the rest of the class. If 90 of the 100 students got less\\nthan 80% of the questions correct, then Mary did better than 90% of the\\nwhole class and she is in the 90th percentile.\"), mdx(\"p\", null, \"A percentage is constructed in the same manner as a proportion and as\\nsuch, requires specific grammar. Because a percentage is properly\\nexpressed by including both parts of the relationship represented, the\\ngrammar of the percentage measure\\u2014both written and spoken\\u2014is critical to\\nensure the correct information is communicated.\"), mdx(\"p\", null, \"The general format for reading a percentage aloud is:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe percentage of the \", \"<\", \"the whole\", \">\", \" that are \", \"<\", \"the part \", \">\", \" is\\n\", \"<\", \"threshold\", \">\", \".\\u201D\")), mdx(\"p\", null, \"The measure must contain the \\u201Cwhole\\u201D followed by the \\u201Cpart\\u201D with the\\nwords \\u201Cthat are\\u201D between them to properly express the relationship.\\nSince a percentage is expressed as a fraction of 100, the threshold for\\na percentage measure will be specified by a percent.\"), mdx(\"p\", null, \"For example, consider the following system requirement:\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe system shall execute \", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Command and Control\"\n }, \"C2\"), \" commands successfully 95% of the time.\\u201D\")), mdx(\"p\", null, \"The whole is \\u201C\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command and Control\"\n }, \"C2\"), \" commands\\u201D and the part the team is interested in are\\nthose \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Command and Control\"\n }, \"C2\"), \" commands that are \\u201Csuccessfully executed.\\u201D The words \\u201Cthat are\\u201D\\nare placed between the \\u201Cwhole\\u201D and the \\u201Cpart\\u201D as the measure and the\\nmetric is \\u201CPercentage\\u201D with a threshold of 95%. The complete example is\\nshown in table A-24.\"), mdx(\"p\", null, \"Table A-24. Percentage Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Payload Control\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 2.1:\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Command and Control\"\n }, \"C2\"), \" Commands that are Successfully Executed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226595%\")))), mdx(\"p\", null, \"In general, a percentage can just as easily be expressed as a\\nproportion, thus avoiding any confusion between percentage and percent.\\nThe percentage and proportion measures are very similar and the use of\\none or the other depends mainly on the sample size involved in the test.\\nIf the test team only has a small number of targets to input to the\\ntest, then the team should use a proportion measure to more accurately\\nreflect the scope of the measure. If the number of targets is larger,\\nthen a percentage may be in order.\"), mdx(\"p\", null, \"As with a proportion measure, it is important to avoid ambiguity in the\\npercentage measure. For instance, the following three examples, while\\nsimilar, are clearly measuring different outcomes. In the first example\\nin table A-25, it is unclear what is being measured; all commands that\\nare sent or only those that the system receives? The second and third\\nexamples in tables A-26 and A-27 are more defined and clearly measure\\ntwo different things.\"), mdx(\"p\", null, \"Table A-25. Ambiguous Percentage Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Payload Control\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.8: Commands that are Executed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226599%\")))), mdx(\"p\", null, \"Table A-26. Percentage Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Payload Control\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.8: Received Commands that are Executed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226599%\")))), mdx(\"p\", null, \"Table A-27. Percentage Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Payload Control\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.8: Sent Commands that are Executed\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226599%\")))), mdx(\"p\", null, \"In some cases, what appears at first to be a percentage measure\\n(discrete) is likely a Percentile measure (continuous).\"), mdx(\"p\", null, \"Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CThe number of messages that are\\ndelivered within 5 minutes shall be greater than 95%\\u201D\"), \" A first attempt\\nto write a measure from this requirement may look like table A-28 or\\nA-29.\"), mdx(\"p\", null, \"Table A-28. Improper Percentage Measure 1\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 2.6: Messages that are Delivered within 5 Minutes\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226595%\")))), mdx(\"p\", null, \"Table A-29. Improper Percentage Measure 2\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 2.6: Messages that are Delivered\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226595% within 5 Minutes\")))), mdx(\"p\", null, \"In the first example, the time threshold has been appended to the\\nmeasure and in the second example, the time threshold is masquerading as\\na condition. In both examples, the measure is discrete. However, if the\\ntime threshold is isolated correctly, the metric is forced to change to\\na percentile, and the resulting measure as shown in table A-30 is\\ncontinuous and properly expresses the requirement.\"), mdx(\"p\", null, \"Table A-30. Correct Percentile Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.6: Time to Deliver Message\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"95th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22645 Minutes\")))), mdx(\"p\", null, \"In some cases, a poorly defined requirement can lead to a poorly written\\nmeasure. Consider the following requirement: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201C95% of the messages must\\nbe delivered successfully\\u201D\"), \" Again, the first attempt at writing a\\nmeasure may produce the following in table A-31.\"), mdx(\"p\", null, \"Table A-31. Ambiguous Percentage Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 2.6: Messages that are Successfully Delivered\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226595%\")))), mdx(\"p\", null, \"While this attempt seems reasonable for the information given, the\\nambiguity of \\u201Csuccessfully delivered\\u201D drives this discrete measure. As\\nthe test team develops this measure as written, the team naturally asks\\nwhat data is to be collected to answer this measure and it becomes clear\\nthe team must know what constitutes a successful message delivery (e.g.\\ntime, number of bits sent vs. received). This may require the test team\\nto develop an identified standard similar to the one shown in table A-30\\n(time threshold of within 5 minutes).\"), mdx(\"p\", null, \"One application of percentage measures is to estimate a probability.\\nOften times measures for reliability, availability, and maintainability\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Reliability, Availability, and Maintainability\"\n }, \"RAM\"), \") metrics, such as operational availability. Are included in the\\ntest program. By definition, some of these metrics are probabilities\\n(i.e., operational availability: the probability that a system will be\\nready for operational use when required). While these are often stated\\nas probabilities in requirements documents, the execution period during\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E is rarely long enough to generate the amount of data required to\\nestimate a probability with a useful confidence interval. Due to this\\ncommon limitation, it is acceptable to use a percentage measure to\\nreport on the availability observed during the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E period. Either way,\\nthe test team must report the sample size to give some context to the\\nresults (99% over 10 hours is much different than 95% over 500 hours).\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Percentage Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the measure clearly express a relationship between the \\u201Cwhole\\u201D and the \\u201Cpart\\u201D?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cwhole\\u201D listed first and the \\u201Cpart\\u201D listed second?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cthat are\\u201D used to convey the relationship?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are both parts of the relationship clearly and concisely expressed with no double meaning?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265 or \\u2264?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is there a continuous threshold hidden in the requirement that can used to convert the percentage measure into a continuous percentile measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Can a continuous identified standard be determined for the requirement?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the expected sample size support the decision to use a percentage metric?\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report results in vague quantitative terms such as \\u201Ca majority of targets were correctly identified\\u201D Always include the actual quantitative values.\"))))))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Ratings.\"), \" There are times when the test team will need to collect the\\nevaluation of a system directly from a user. Referred to as \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201Cuser\\nrating\\u201D\"), \" or \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201Cratings of\\u201D\"), \" measures, they are often used to provide data\\non the workload, usability, ergonomics, training, situational awareness\\nor some other attribute of the human interaction with the system under\\ntest. Ratings are used to provide insights into the system that cannot\\nbe determined through objectively collected, quantitative data alone.\\nThese types of measures should complement and support other objectively\\ncollectable, quantitative measures and not be used as a replacement.\"), mdx(\"p\", null, \"The format for rating measures has two unique elements, the measure\\ntitle and the evaluation criteria. First, the measure title is written\\nbeginning with the phrase \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201C\", \"<\", \"User\", \">\", \" Rating of\\u2026\\u201D\"), \" to clearly\\nidentify that the measure is based on the input of an individual or\\ngroup. The test team must clearly define who the user is and include\\nthis not only in the measure title, but also in the Scope section of the\\nmeasure worksheet. The format of the second part of the measure title\\nwill, in most cases, identify the attribute of the human system\\ninteraction the user is meant to rate. This attribute can be either an\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"internal\"), \" human quality or an \", mdx(\"em\", {\n parentName: \"p\"\n }, \"external\"), \" human aspect of the\\ninteraction with the system. Examples of internal human qualities are\\nsituational awareness or workload. Examples of external human aspects of\\nthe interaction with the system are readability, usability and\\naccessibility. If the attribute is for an external aspect, the measure\\nstatement should further identify what part of the system the human\\nattribute is connected with. The general format for the measure title\\ntakes one of the following formats, depending on the human attribute\\nbeing considered:\"), mdx(\"p\", null, \"\\u201C\", \"<\", \"User\", \">\", \" Rating of \", \"<\", \"internal attribute\", \">\", \"\\u201D\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"or\")), mdx(\"p\", null, \"\\u201C\", \"<\", \"User\", \">\", \" Rating of \", \"<\", \"external attribute\", \">\", \" of \", \"<\", \"part of\\nsystem\", \">\", \"\\u201D\"), mdx(\"p\", null, \"In some cases, the test team will be interested in the user rating of a\\nspecific topic area or process related to the system under test. For\\ninstance, the test team may want to evaluate the contractor provided\\ntraining, technical orders or the help desk associated with a particular\\nsoftware system. In this case, the measure will follow the following\\nformat:\"), mdx(\"p\", null, \"\\u201C\", \"<\", \"User\", \">\", \" Rating of \", \"<\", \"topic area/process\", \">\", \"\\u201D\"), mdx(\"p\", null, \"The second unique format element is how the metric and threshold are\\nidentified. Rating measures typically do not come directly from a system\\nrequirement so the test team will likely have to develop an identified\\nstandard for the evaluation criteria for the measure. This typically\\ntakes the form of a qualitative statement preceded by the carrot symbol\\n(^). Since there is no stated threshold, the cells below the headers for\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"Metric\"), \" and \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Threshold\"), \" are merged, while maintaining the header cells,\\nto accommodate the statement. Rating measures are evaluated in terms of\\nits effects, or if the operation or task was successfully accomplished.\\nIf feasible, the statement should be written to include the human\\nattribute that is being evaluated and the operation or task that is\\nachieved of facilitated. The general format for the evaluation criteria\\nis show below.\"), mdx(\"p\", null, \"\\u201C\", \"<\", \"Human system attribute\", \">\", \" \", \"<\", \"enables/facilitates\", \">\", \"\\n\", \"<\", \"operation/task accomplishment\", \">\", \"\\u201D\"), mdx(\"p\", null, \"Do not set arbitrary thresholds for rating measures (i.e. \", \">\", \"80% of\\nresponses must be positive). The test team should report their findings\\nwithout comparing to a numerical threshold. Figure A-1 demonstrates the\\ndifferent ways to construct a rating measure. The user groups,\\nattributes and topic areas/processes shown are examples and the lists\\nare not meant to be all inclusive. Test teams may come up with other\\nattributes, users, or topic areas/processes that are not shown.\\nSituational awareness is a special case of the internal attribute and\\ntherefore has its own format.\"), mdx(\"p\", null, \"Figure A-1. How to Construct a Rating Measure\"), mdx(\"span\", {\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/93d6e0e7234224240a45067b9ea22f05/081d5/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\": \"60.231660231660236%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAMCAIAAADtbgqsAAAACXBIWXMAAAsTAAALEwEAmpwYAAABLUlEQVQoz42S126EQAxF+f/fQwIhmug1onfYzRFeERIlq/gBDfYttmeU5/c4jiOKItM0bdsOw3Capnv1cQt+leskMQwDnLIsl2WZ53kcx+ffofz4xyrPc8/zHMdBou/7exWtjzOqqlrXVQHKCcOu63DjC9P3/SzLmqYhjwRoYJSYSNM0XdeRbttWsSyrrmtU932fzoAJP01TCJCltG0bXwZBAgwHMgoaQDEhRSc0hjyKSCRJgjxkhHBTVZUSAJb6mtkwDHBFUTAeYggjR1IQOJOP4xgMNAwZjRZeZHojBZQUBRD4MOdwhiysOmM9gwa/nLknyIAgyzkIAprknl3XlXW8uyrZhPzLSmHSkWhdz+N3MgU6lDujBZwZm22xAgb51yO5nhqbl+XJI3tD/gR3/LGqyjKc4AAAAABJRU5ErkJggg==')\",\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/93d6e0e7234224240a45067b9ea22f05/e3189/image11.png\",\n \"srcSet\": [\"/static/93d6e0e7234224240a45067b9ea22f05/a2ead/image11.png 259w\", \"/static/93d6e0e7234224240a45067b9ea22f05/6b9fd/image11.png 518w\", \"/static/93d6e0e7234224240a45067b9ea22f05/e3189/image11.png 1035w\", \"/static/93d6e0e7234224240a45067b9ea22f05/081d5/image11.png 1264w\"],\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, \"For example, suppose an aircraft is undergoing an avionics suite upgrade\\nwith new processors, displays and controls. The test team wants to know\\nhow the aircrew\\u2019s situational awareness is impacted by the upgrade, but\\nhas no means to objectively collect quantitative data that adequately\\nmeasures the aircrew\\u2019s response to the changes. The test team can create\\na measure to collect the aircrew\\u2019s rating of how the changes to the\\navionics suite have impacted their ability to perform the mission. In\\ntable A-32, the measure follows the format discussed above for the\\ninternal human attribute of workload.\"), mdx(\"p\", null, \"Table A-32. Example of Internal Attribute Rating Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Usability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.4: Aircrew Rating of Workload\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Workload does not impair navigation\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"Additionally, the test team may want to know what the aircrew thinks of\\nthe new avionics suite multi-function display. Suppose the team is\\nspecifically interested in the impact of the crews ability to read the\\ndisplay in operational conditions. This measure could take the form in\\ntable A-33.\"), mdx(\"p\", null, \"Table A-33. Example of External Attribute Rating Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Usability\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.5: Aircrew Rating of Legibility of the Multi-Function Display (MFD)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Legibility of MFD supports mission accomplishment\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"The data for ratings measures is typically collected using rating\\nscales, surveys, questionnaires, interviews, test team observations or\\nany combination of these. The methods used to create questionnaires and\\ncollect questionnaire data are extremely important for assuring the\\nusefulness of the data they produce. Test teams that plan to use these\\nmethods should consult the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Questionnaire Guide\"), \", available from\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SharePoint Library. In addition, test teams should work in\\nclose coordination with detachment human factors experts and A-2/9 to\\nensure the most effective use of questionnaires.\"), mdx(\"p\", null, \"Ratings measures are fraught with pitfalls and the test team must be\\ncautious when using them. There is a temptation to use a rating measure\\nas a \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201Ccatch-all\\u201D\"), \" to find problems or to \\u201C\", mdx(\"em\", {\n parentName: \"p\"\n }, \"cover all the bases\\u201D\"), \" not\\nexplicitly covered under another measure. Teams should only create\\nrating measures when there are attributes of the system that they\\ndetermined a need to evaluate and rate. Issues that arise during test\\nthat do not fit under a specific measure can be documented in the report\\nat the measure level as additional observations and at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" level as\\nnotable findings. There should rarely be a need to have a \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201Ccatch all\\u201D\"), \"\\nmeasure. There are also instances when teams may create a rating measure\\nfor something that can be answered by objectively collected quantitative\\ndata. Test teams should always strive to obtain objectively collected\\nquantitative data when feasible. Finally, there is the risk of writing a\\nrating measure so broadly that it becomes the overall rating of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\n(effectively removing the rating taxonomy for measures and COIs and\\nplacing it into a single measure). The following examples demonstrate\\nsome of the pitfalls that test teams must be aware of and consider when\\nwriting and utilizing rating measures.\"), mdx(\"p\", null, \"Table A-34. Example of Incorrect Rating Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.8:Operator Rating of Time Required to Input Coordinates\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Time required to input coordinates enables task accomplishment\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"The measure in table A-34 uses a rating to evaluate time, which can be\\ncollected objectively as quantitative data. Instead of the rating\\nmeasure, the test team should identify the appropriate metric (maximum,\\npercentile, etc.) for the measure and develop and identified standard\\nfor the time if no threshold is given in the requirements documentation.\\nTables A-35 and A-36 are two examples of measures that could be used in\\nplace of the incorrect measure shown in table A-34.\"), mdx(\"p\", null, \"Table A-35. Potential Replacement Measure for Figure 4-35\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.8: Time to Input Coordinates\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ \\u226470 seconds\")))), mdx(\"p\", null, \"Table A-36. Potential Replacement Measure for Figure 4-35\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 2.8: Time to Input Coordinates\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ 95th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ \\u226470 seconds\")))), mdx(\"p\", null, \"In table A-37, the measure is written at such a high level that it in\\nessence evaluates the system overall, bypassing the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" rating\\ntaxonomy where the test team rates all the measures and then the\\ncollective operational impact of those measure ratings at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" level.\\nWhile this is an extreme example, test teams must be wary of any measure\\nthat circumvents the intended rating taxonomy. If the measure speaks\\ndirectly to the overall system success, or to success at the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" level,\\nit is likely that the measure is too broad.\"), mdx(\"p\", null, \"Table A-37. Example of Incorrect Rating Measure\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Accuracy\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.4:Aircrew Rating of Navigation System Upgrade\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Navigation system upgrade enables task accomplishment\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"Test teams also need to be cautious of creating rating measures that\\nsimply rollup other measures in the test program. Table A-38 is a set of\\nfour separate tables that show how the test team developed three\\nobjectively collectable quantitative measures to evaluate the timeliness\\nof a message delivery system. The fourth measure in the set is redundant\"), mdx(\"u\", null, \"and should be removed\"), \". MOPs 1.1\\u20131.2, MOE 1.3, and their outcomes form a sufficient basis for the evaluation of system timeliness with respect to message delivery. MOP 1.4 is not required and should not be included as a separate measure. Questionnaire data that would have been collected under MOP 1.4 can be included as data elements under any or all of the first three measures. In general, survey or questionnaire data can always be collected as a data element supporting an objective measure.\", mdx(\"p\", null, \"Table A-38. Set of Four Separate Measure Examples/Last Measure is\\nRedundant\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Sent Messages that are Correctly Received\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"90th Percentile\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u22642 minutes\")))), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.2: Message Drop Rate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Maximum\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ \\u22645 messages/hour\")))), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \" 1.3: Messages that are Successfully Delivered\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Percentage\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\\u226595%\")))), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Timeliness\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.4:Terminal Operator Rating of Message Timeliness\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Message timeliness enables task accomplishment\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"These application errors in rating measures typically arise because of\\nthe test teams desire to catch all possible issues or problems that may\\noccur during test. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" measure model allows test teams to collect\\nand highlight issues without creating additional measures. For instance,\\nthe test team may add additional data elements to any measure to assist\\nin its rating and evaluation. For example, a survey or questionnaire may\\nbe added as a data element supporting an objectively collectable\\nquantitative measure. Further, the test report section for additional\\nobservations is designed to allow test teams to capture any items that\\nsurface during test that are not directly addressed by the measures.\"), mdx(\"p\", null, \"Evaluating rating measures is not a definitive process however, there\\nare some general principles that can be used. In addition to the main\\ndata source for a given rating measure, the test team in many cases will\\nalso record their observations of user\\u2019s reactions, comments or\\ninteractions. The test team should consider all of the data related to\\nthe measure and decide whether there is a convergence of responses\\n(positive or negative), which point to the measure as being met or not\\nmet.\"), mdx(\"p\", null, \"One special application of the ratings measure format is cyber measures.\\nAt the time of writing, cyber measures have typically taken the form of\\na rating, of either risk or capability level. While this has been the\\ncase historically, cyber measures do not have to be in the form of a\\nrating measure. It is up to the test team to determine the most\\nappropriate measure format in order to clearly convey the results of the\\noperational test. If the test team chooses to construct cyber measures\\nin the rating format, they should adhere to the generalized formats\\ndescribed in this section. Further discussion of cyber measures and\\nexamples can be found in Appendix C.\"), mdx(\"p\", null, \"The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Questionnaire Guide\"), \" provides a complete description of how\\nto analyze and report rating measures and should be consulted by the\\ntest team. In addition, the test team should contact A-2/9 with any\\nquestions or concerns on analyzing or reporting information.\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Rating Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the measure written to evaluate some attribute of the human interaction with the system?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the correct format used for the specific attribute the measure is concerned with?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cuser\\u201D clearly defined in the measure title and/or Scope section of the worksheet?\")), mdx(\"li\", null, mdx(\"p\", null, \"The measure title should never start with \", mdx(\"em\", null, \"\\u201CTest Team Rating of\\u2026\\u201D\")), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Test team judgement is already accounted for in the AFOTEC rating taxonomy\")))), mdx(\"li\", null, mdx(\"p\", null, \"Are the Metric and Threshold cells merged, while maintaining the header cells?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the criteria statement formatted correctly?\")), mdx(\"li\", null, mdx(\"p\", null, \"Should the criteria statement be preceded with the identified standard symbol (^)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the measure follow one of the pitfalls described in the ratings measures Section?\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Measure should not be a \", mdx(\"em\", null, \"\\u201CCatch-all\\u201D\"), \" or used to \", mdx(\"em\", null, \"\\u201CCover all the bases\\u201D\"))), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not attempt to evaluate something that can be answered with objectively collected quantitative data\")), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not be so broad as to evaluate the entire system or COI\")), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not attempt to roll up other measures in the measure set\"))))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Are there any additional data elements that can be added to aid in the evaluation of the measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Plan to look for a convergence or harmony of responses when evaluating these types of measures.\"))))))), mdx(\"h1\", null, \"Composite Measures\"), mdx(\"p\", null, \"While a traditional measure evaluates a single attribute of a system, a\\ncomposite measure is a single evaluation of multiple attributes of a\\nsystem. In industry, these types of measures are called indexes,\\nratings, compound or complex measures. Some well-known examples include\\nthe Consumer Price Index, the Gross Happiness Index and the common\\nCredit Score. All of these measures take into account multiple\\nattributes and aggregate them into one score. The benefits of these\\ntypes of measures include:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A method to communicate a complex concept \\u2013 Composite measures allow\\nfor a single score or rating to be used to communicate the results\\nof complex relationships between multiple attributes of a system. It\\nis often easier to understand and interpret a single capability\\nrating rather than the individual ratings of multiple attributes\\nthat influence the capability.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"A way to balance contributing factors \\u2013 Composite measures allow for\\nthe aggregation of multiple attributes. This combination reduces the\\npotential bias from highly variable attributes.\"))), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" defines a composite measure as: \", mdx(\"em\", {\n parentName: \"p\"\n }, \"A measure describing a system\\ncapability that is influenced by multiple attributes whose results are\\naggregated into a single score or evaluation.\")), mdx(\"p\", null, \"This definition does not preclude the individual attributes from being\\nexamined separately and in relation to each other.\"), mdx(\"p\", null, \"An example of a composite measure is the US News Ranking of Best\\nColleges. This ranking scores the relative quality of college\\ninstitutions based on widely accepted indicators of excellence, shown in\\ntable A-39.\"), mdx(\"p\", null, \"Table A-39. US News Ranking of Best Colleges (Composite Measure Example)\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"span\", {\n parentName: \"th\",\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"176px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/d16f8a9984ee6f264c7746c87c873614/06437/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\": \"93.18181818181817%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAATCAIAAAAf7rriAAAACXBIWXMAAAsTAAALEwEAmpwYAAACt0lEQVQ4y6WUXVMSURjH92v0Gbrpou/QTBdNN13ZjKaTpc6Yk2MzQioqZdiYkChC61soILoLohIioK4KQbxsLgLx4mKwoBQy2CiMsmtnccYxQ6vpf3H2nN3n97yceZ6FTv5D0PkDwzA0TTNX6lL4j7rAQ2dvwUpRFIat2O0fNzZwm80GNuFwCMc9fr/P59v0egmKitOFQml400vU1tU2NDx53sJtbHwqFPZyOM2vuwUvX/Db2lo5XI5KpTwzvghHo2RHBw9g3d2CltYWs2lxdlb3pqdHrZ5cWV6aUquTycTx8XHpyORWhMvlvOrqauY089p5SqWCz++Eh+Dh4eFVDJPJZMDm6OioNBwlSZFIODg4ADClQqHValAUGRkdAeSSxTKNILup1KUXRhAEwBAUGR+XoyjqdDkXjEadTqfRanVzc9jamgfHGda4FLwT355FJz/oNPNaZAaZXF82rViMVmzJMKczL+gd1lWX3Xrxwgo0e5jHqUrpasVbQ1W/qQ5erhQvlgkN5WJTzdDao3dYlcTyQGx8KMWeqTyJzOFpdKhA0+AhW/BAd8S3BNiNDnMT6ns88fkB7GzXh+rV3iZks2LMXTbkAvtquQe6N3a9Qf4te3AKsz70eBS621/TuyhV2wZUNtmUbVTjgKftDscXtd4tn/mktxAihRVb918rH7vJmS4mfwLRxcgms5N3u3KLx6enkB8j8tz7iQw8Soqk8T5ZrE+6LZJsCyVg3ZHAhvvVnfWC3EGuWHOxfIaKH7hd2UwGeCLjVJCMBiIRb8C/4fcTgYDHS7i9RGArEk3tpkMhhiDoXO6XwQAuQPfkDw/3vqcTFBWLxUgSdA2rYDAYCYfjX2N76XTh995mKwD5F0cSfM7n89lsFrREIplMpVL7+/u5fJ6d1nOWV40kqIZNpMj81c/gX/UT/mLOxcXx+fAAAAAASUVORK5CYII=')\",\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/d16f8a9984ee6f264c7746c87c873614/06437/image12.png\",\n \"srcSet\": [\"/static/d16f8a9984ee6f264c7746c87c873614/06437/image12.png 176w\"],\n \"sizes\": \"(max-width: 176px) 100vw, 176px\",\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(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Attributes\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Graduation and Retention Rates\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Student Selectivity\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Undergraduate Academic Reputation\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Alumni Giving Rate\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Faculty Resources\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Graduation Rate Performance\")))), mdx(\"p\", null, \"Data is collected, directly from the universities, for each attribute. A\\nscore for each attribute is obtained and then a standard method is\\nemployed to aggregate the scores of all of the attributes. This yields a\\nsingle composite score for the university. This method allows readers to\\nget a sense of the relative quality of any institution.\"), mdx(\"p\", null, \"Within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \", these type of measures are identified by the leading\\nverbiage \\u201CComposite Rating of\\u2026\\u201D and are used to evaluate and report on\\nsystem capabilities that are influenced by multiple attributes, but do\\nnot rise to the level of a critical operational issue (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \").\"), mdx(\"p\", null, \"Composite measures may be composed of any number of qualitative,\\nquantitative, continuous and/or discrete measurements. The\\ndistinguishing factor between a composite and traditional measure is\\nthat the measurements contained within the composite measure are looking\\nat multiple, different attributes of the system. It is critical that all\\nattribute measurements contributing to a composite measure are well\\ndefined. Additionally, the test team\\u2019s evaluation and aggregation\\nstrategy should be thoroughly documented in the measure worksheet and be\\ncredible and supportable.\"), mdx(\"p\", null, \"An example composite measure is shown in table A-40. This measure is\\nused to rate the air refueling of receiver aircraft by evaluating the\\nconfiguration, functionality, precision and effectiveness of several\\nsubsystems required to complete the air refueling task. Additionally,\\nthe measure considers the fatigue and workload of the operators while\\ncompleting the air refueling task. All of these attributes are\\nconsidered together when evaluating the measure.\"), mdx(\"p\", null, \"Table A-40. Composite Measure Example\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"(CUI)\"), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Operational Capability: Refueling Flexibility\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Measure\"), mdx(\"td\", null, \"Metric\"), mdx(\"td\", null, \"Threshold\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 1.18: Composite Rating of KC-46A Air Refueling of Receiver Aircraft\"), mdx(\"td\", null, \"^ KC-46A AROS controls, displays and support systems enable air refueling of receiver aircraft with limited negative operational impacts\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*KPP or Supports KPP\", mdx(\"br\", null), \"^ Identified Standard\"), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Reference\"), \": Derived from \\u201CCapability Production Document for KC 135\\nReplacement Aircraft (KC X), Ver 4.4,\\u201D 19 Mar 15, para 6.2.2.1 and\\n6.2.3.1.435\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Scope\"), \": This measure evaluates air refueling from the air refueling\\noperator (ARO) perspective. The ARO employs the controls, displays, 3D\\nglasses, and support systems of the KC-46A air refueling operator\\nstation (AROS) to accomplish air refueling with receiver aircraft via a\\ncenterline boom, centerline drogue system (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cross Domain Solution\"\n }, \"CDS\"), \"), and wing air refueling\\npods (WARP). There is a significant design/functionality change in the\\nKC-46A vs. the KC-135 and KC-10, where the boom operator\\u2019s crew station\\nhas been moved to the front of the aircraft; and there is no longer a\\n\\u201Cdirect line of sight\\u201D through clear glass to the receiver aircraft and\\ncenterline boom during air refueling operations.\"), mdx(\"p\", null, \"Key measurement targets include:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Configuration and functionality of the AROS controls (e.g., fuel\\nmanagement system and scene selections),\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Camera-produced \\u201Cfield of view\\u201D and \\u201Cdepth of field\\u201D cues that are\\nprojected on the AROS visual/motion displays in day/night/low-light\\nmodes\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Precision control/stability of the centerline boom\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"ARO communication/coordination with receiver aircraft and KC-46A\\nflight crew\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Air refueling readout displays at the AROS\"))), mdx(\"p\", null, \"A secondary measurement target includes an ARO rating of subjective\\nfatigue/workload, principal drivers of workload, and operational\\nimpacts. Of special interest are any ARO reports of physical and/or\\nphysiological symptoms (e.g., eye strain, dizziness, headaches, and\\nnausea) that are due to the effects of using 3D glasses with the\\nvisual/motion display while in a fixed-position seat at the AROS, and\\nfacing the rear of the aircraft with forward aircraft motion. Finally,\\nidentification of any significant negative ARO operational transfer\\neffects from KC-135/KC-10 aircraft to the KC-46A.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Methodology\"), \": KC 46A aircrews will execute air refueling with a\\nplanned set of fighter, bomber, airlift, and reconnaissance receiver\\naircraft during planned test events, which occur during day, night, and\\ntransitional-light operations.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Design\"), \": Uses \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1 Operations 1, 2, and 3 test design.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data and Analysis\"), \": Multiple data sets include ARO and test team\\nrecorded observations from data sheets, ARO evidence-based effectiveness\\nratings, ARO subjective fatigue/workload ratings, post-test interview\\ndata from AROs and onboard test team observers, and storable and\\nretrievable camera/video images and audio.\"), mdx(\"p\", null, \"Standardized observational data collection forms will include the\\nmeasurement targets specified in the Scope section. Prior to test\\nevents, approximately 10 AROs with experience representative of the\\noperational force will be briefed on the observational, workload, and\\nother measurement targets. They will conduct repeated observations\\nduring test events relative to the measurement targets. The onboard test\\nteam observer will sit in the instructor seat of the AROS and observe\\nreceiver refueling executed by the ARO. Crew Status Surveys will be\\nadministered to record subjective fatigue/workload ratings. If possible,\\nobservational data collection forms and workload ratings will be\\ncompleted in-flight at the conclusion of each air refueling test event;\\notherwise, they will be completed immediately after test events. ARO\\neffectiveness ratings of air refueling of receiver aircraft will be\\nformulated on the basis of the recorded observational evidence from test\\nevents (i.e., evidence-based ratings). The test team will conduct\\ndetailed, issues-based interviews and open-ended feedback sessions with\\nAROs and onboard observers in order to verify/clarify recorded data and\\ncollect additional information, including possible\\nphysical/physiological effects data. The test team will select relevant\\nstored video and audio data to support data analysis and resolution of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \".\"), mdx(\"p\", null, \"The test team will analyze data sets separately and relative to each\\nother to determine the extent of their convergence. The distributions of\\nARO evidence-based ratings and ARO workload ratings will be presented in\\nseparate tables. The range of scores, the modes of the distributions,\\nand other relevant distributional characteristics will be reported and\\ndiscussed in the text (e.g., outliers, distribution shape, etc.). A\\ncontent analysis of observational data will be performed, and the\\noutcomes will be discussed in a comprehensive, balanced (i.e., positive\\nand problematic findings), and factual narrative. Observational data\\nwill be analyzed across AROs, which is an index of replication and\\nverification of results. Cross-verification of observational outcomes\\nreported by AROs and onboard observers will be analyzed and discussed\\n(i.e., inter-observer agreement). Interview data will be analyzed, and\\nrelevant findings will be extracted and interwoven in the discussion.\\nThe identified standard will be met if ARO observations, onboard test\\nteam observations, reported operational impacts, ARO evidence-based\\nratings, ARO workload ratings, selected video and audio data, and\\ninterview data converge in the same, positive direction (i.e.,\\ntriangulation of data sets). If strict convergence is not met, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \"\\nwill be resolved according to the preponderance of the total evidence.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#continuous-measures","title":"Continuous Measures"},{"url":"#discrete-measures","title":"Discrete Measures"},{"url":"#composite-measures","title":"Composite Measures"}]},"parent":{"__typename":"File","relativePath":"measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES.md"},"frontmatter":{"metaTitle":"APPENDIX A CATEGORIES OF MEASURES","metaDescription":"APPENDIX A CATEGORIES OF MEASURES"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"52fe8d68-e903-5bd3-aadb-8a66688074a5"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE/page-data.json b/sites/oteguide/page-data/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE/page-data.json new file mode 100644 index 00000000..8a343f3a --- /dev/null +++ b/sites/oteguide/page-data/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"cd2425fc-c774-5c61-8ecf-d8e4677f7006","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE","slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE"},"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\": \"APPENDIX B MEASURE REVIEW QUICK REFERENCE\",\n \"metaTitle\": \"APPENDIX B MEASURE REVIEW QUICK REFERENCE\",\n \"metaDescription\": \"APPENDIX B MEASURE REVIEW QUICK REFERENCE\"\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(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Mean Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Keep in mind that the arithmetic mean can be sensitive to every value in the data set, including extremes. This effect is especially noticeable when the sample size is small.\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Error Probable Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the metric include the probability?\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Are the underlying assumptions about the metric realistic for the operational scenario?\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Percentile Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include the units of measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the metric include the percentile value (not just the word \\u201CPercentile\\u201D)\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a percentile applicable to the requirement or is there another metric more appropriate?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the team intend to report the percentile of the empirical data or of a fitted distribution?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sample size sufficient for a percentile to be meaningful?\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Probability Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the threshold a value between 0 and 1?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality, either \\u2265 or \\u2264?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the metric and threshold cells merged?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the measure name include the phrase \\u201CProbability of\\u201D?\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the sample size sufficient to determine a probability with a reasonable confidence interval?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is a probability meaningful for the operational scenario?\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Continuous Minimum/Maximum Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265, \\u2264 or =?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sign appropriate for the metric (\\u201C\\u2264\\u201D for a Maximum, \\u201C\\u2265\\u201D for a Minimum, or an equals sign \\u201C=\\u201D in certain cases)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the metric spelled out completely (no \\u201CMin\\u201D or \\u201CMax\\u201D)?\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a minimum/maximum metric operationally relevant?\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Discrete Minimum/Maximum Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265, \\u2264 or =?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the sign appropriate for the metric (\\u201C\\u2264\\u201D for a Maximum, \\u201C\\u2265\\u201D for a Minimum, or an equals sign \\u201C=\\u201D in certain cases)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the metric spelled out completely (no \\u201CMin\\u201D or \\u201CMax\\u201D)?\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is a minimum/maximum metric/threshold operationally relevant?\")), mdx(\"li\", null, mdx(\"p\", null, \"Can the measure be made continuous?\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Proportion Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the measure clearly express a relationship between the \\u201Cwhole\\u201D and the \\u201Cpart\\u201D?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cwhole\\u201D listed first and the \\u201Cpart\\u201D listed second?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cthat are\\u201D used to convey the relationship?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are both parts of the relationship clearly and concisely expressed with no double meaning?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cout of\\u201D used to convey the relationship in the threshold?\"))), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Alternatively a division symbol can be used (3/5)\"))), mdx(\"p\", null, \"Example:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"???\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Can the measure be made continuous?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the expected sample size support the decision to use a proportion metric?\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report proportion measure results in decimal form alone. If the requirement is given in a decimal or percentage, report the result as a proportion and annotate the decimal/percentage notation for comparison to the threshold of the requirement.\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report results in vague quantitative terms such as \\u201Ca majority of targets were correctly identified.\\u201D Always include the actual quantitative values.\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Percentage Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Does the measure clearly express a relationship between the \\u201Cwhole\\u201D and the \\u201Cpart\\u201D?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cwhole\\u201D listed first and the \\u201Cpart\\u201D listed second?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are the words \\u201Cthat are\\u201D used to convey the relationship?\")), mdx(\"li\", null, mdx(\"p\", null, \"Are both parts of the relationship clearly and concisely expressed with no double meaning?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the threshold include an inequality or equal sign, either \\u2265 or \\u2264?\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is there a continuous threshold hidden in the requirement that can used to convert the Percentage measure into a continuous Percentile measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Can a continuous identified standard be determined for the requirement?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the expected sample size support the decision to use a percentage metric?\")), mdx(\"li\", null, mdx(\"p\", null, \"Do not report results in vague quantitative terms such as \\u201Ca majority of targets were correctly identified.\\u201D Always include the actual quantitative values.\"))))))), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"AFOTEC Keys to Rating Measures\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"Writing:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Is the measure written to evaluate some attribute of the human interaction with the system?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the correct format used for the specific attribute the measure is concerned with?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the \\u201Cuser\\u201D clearly defined in the measure title and/or Scope section of the worksheet?\")), mdx(\"li\", null, mdx(\"p\", null, \"The measure title should never start with \", mdx(\"em\", null, \"\\u201CTest Team Rating of\\u2026\\u201D\")))), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Test team judgement is already accounted for in the AFOTEC rating taxonomy\"))), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Are the Metric and Threshold cells merged, while maintaining the header cells?\")), mdx(\"li\", null, mdx(\"p\", null, \"Is the criteria statement formatted correctly?\")), mdx(\"li\", null, mdx(\"p\", null, \"Should the criteria statement be preceded with the identified standard symbol (^)?\")), mdx(\"li\", null, mdx(\"p\", null, \"Does the measure follow one of the pitfalls described in the Ratings measures Section?\"))), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Measure should not be a \", mdx(\"em\", null, \"\\u201CCatch-all\\u201D\"), \" or used to \", mdx(\"em\", null, \"\\u201CCover all the bases\\u201D\"))), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not attempt to evaluate something that can be answered with objectively collected quantitative data\")), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not be so broad as to evaluate the entire system or COI\")), mdx(\"li\", null, mdx(\"p\", null, \"Measure should not attempt to roll up other measures in the measure set\"))), mdx(\"p\", null, \"Planning for Analysis:\"), mdx(\"ul\", null, mdx(\"li\", null, mdx(\"p\", null, \"Are there any additional data elements that can be added to aid in the evaluation of the measure?\")), mdx(\"li\", null, mdx(\"p\", null, \"Plan to look for a convergence or harmony of responses when evaluating these types of measures.\"))))))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE.md"},"frontmatter":{"metaTitle":"APPENDIX B MEASURE REVIEW QUICK REFERENCE","metaDescription":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"cd2425fc-c774-5c61-8ecf-d8e4677f7006"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES/page-data.json b/sites/oteguide/page-data/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES/page-data.json new file mode 100644 index 00000000..d442b8f4 --- /dev/null +++ b/sites/oteguide/page-data/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"a7a397bc-d207-56b9-819e-804a37a205d4","title":"APPENDIX C CYBER-RELATED MEASURES ","slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES"},"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\": \"APPENDIX C CYBER-RELATED MEASURES \",\n \"metaTitle\": \"APPENDIX C CYBER-RELATED MEASURES \",\n \"metaDescription\": \"APPENDIX C CYBER-RELATED MEASURES \"\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, \"[1]\"), mdx(\"p\", null, \"Cybersecurity \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" is used to describe the activities that encompass all\\ncybersecurity test and evaluation activities, including vulnerability\\nassessments, security controls testing, penetration testing, adversarial\\ntesting, and cybersecurity testing related to a system\\u2019s operational\\nresilience and system cyber survivability capabilities within a mission\\ncontext.\", \"[2]\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" considers cyber survivability, resiliency and security critical\\nmission enabling capabilities of a system under test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"). So the\\nexpectation is that these capabilities will be fully integrated and\\ncomprehensively tested components of every test program. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9,\\nA-3I, and Detachment analysts will ensure that cyber-related measures\\nare developed for each program as necessary.\"), mdx(\"p\", null, \"Usage note: the focus of this appendix is on how to write a\\ncyber-related measure\\u2014refer to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Cyber Test Guide (CTG) for how\\nto rate and score cyber-related measures using operationally relevant\\ndata.\"), mdx(\"h1\", null, \"Measures Overview\"), mdx(\"p\", null, \"Test measures are the basis of the evaluation of a system under test\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"). They drive the data needs, collection, and analysis used to\\nevaluate effectiveness and suitability and serve as evidence of\\ncapability performance and mission effects. There are three general\\ntypes of measures developed for Operational Test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"):\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures of Effectiveness (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \") -\"), \" Measures designed to assess\\nthe degree to which the system under test can accomplish mission\\nobjectives and achieve desired mission effects.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures of Performance (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \")\"), \" - Measure a system\\u2019s capabilities.\\nThey may quantify performance such as speed, payload, range,\\ntime-on-station, frequency, rating, or other distinctly observable\\nand/or quantifiable performance features. They may also document\\nwhether or not a system can successfully complete a task.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures of Suitability (\", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \")\"), \" - Measure of the ability to\\nsupport the system under test in its intended operational\\nenvironment. MOSs typically relate to readiness, supportability,\\nlogistics infrastructure and cost of ownership of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \".\"))), mdx(\"h1\", null, \"Composite Measures\"), mdx(\"p\", null, \"Composite measures aggregate and summarize data from multiple\\nattributes. The multidimensional nature and complexity of cyber-related\\ntesting make adoption of composite measures very beneficial. A composite\\nmeasure facilitates evaluation of multiple attributes of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" by\\nconsolidating results into a single score.\"), mdx(\"p\", null, \"To prevent deceptively obtuse and irrelevant results, it is critical\\nthat all attribute measurements contributing to a composite measure be\\nwell defined. Additionally, the test team\\u2019s evaluation and aggregation\\nstrategy should be thoroughly documented in each of the composite\\nmeasure worksheets and be credible and supportable.\"), mdx(\"p\", null, \"Clarity, transparency, and accountability are required from all\\nstakeholders in composite cyber-related measures development and\\ndocumentation, as evidenced in the associated measures worksheets, to\\nbetter reduce distinct quality measures into a single summary indicator.\"), mdx(\"p\", null, \"See the main body of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Measures Guide for a complete\\ndescription and guidance on Composite Measures. See \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"-4 Stand Alone\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Construct \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" Example where they are used to aggregate effects of\\noperating within a cyber-contested environment for COIs 1, 2 and 3.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Cyber-Related Measures\"), \". Capabilities and functions of a system are\\nevaluated using both MOPs and MOSs. When developing cyber-related\\nmeasures for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", it is useful to visualize the system as having four\\nlayers that may require measurement and assessment: Mission Effects,\\nSystem Capabilities, System Functions and Properties, and System\\nStructure. Figure C-1 depicts these four levels in a pyramid and how\\nthey could relate to cyber-related measures.\"), mdx(\"p\", null, \"Figure C-1. The Pyramid\\u2014Evaluation Levels of a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"1026px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/f6c992d4a47d7bfd84862de0027c7346/eb3fa/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\": \"62.54826254826254%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAAA7DAAAOwwHHb6hkAAACkUlEQVQ4y5VTS0sbURjNP5K2ghvxNygiiGu3KoKiKyFLUTS7gA+QLty0YtFVsYLR+KqakIdJjIlJzCSZTMfJvB95nX73Rlu66MILZ+6938w9c853ZnygodstlEQLRdGBpHXQ6XRZGd1u993wea0uwikHO9+i+HL0iHCmi7riwLBcvHdwwg5dbh9tfD2TcXilIF6wUagqqNQVKC8G2u02XLcFx2lyeF5vresOLMt7hctrbPheueF4bTRJrWnZeNFMxBM57O+fQ5Y1XF8/4eQkg3D4EVdXedzcFDhisTKSSYHmZ9zfVzipr+f9r2yd3qbpLuIxAxcXKj1oQlFMNBoWV8OUMcX/tfy20DUNJUGErBoIn2vY2hKwuZnFzo6EfJ7UN5tcUSpVRSRS4oqi0RLi8TJXWK2qPcuu66LVaqLV7kA1LYg1D3t7OoLBBFZWQtjYyODw0IYgGETSI3x4qCGXq9OLJFqLyGZFqKrdI2TKJLkBSTXxQukGgyJWVyWsr4uEOgIBCcvLdezuyvyAabpcXaHw6w9pLichna7Ctr2eZd30YLo2Dg5UzM1VsLj4hOnpCCYnf2B29p72BapXKRyHemjg6CjFw2EhscAuL/N8z74AX02U0DB0JBImHRKwsFAmsgQhSWRZTE3FMDOTwPx8GUtLNWQyKj37zFUxu0wts8z6yELzNQyLUm3SQQGjo0VMTJQIFYyNZTAyEsH4OKsJvD48XITfL3LrrI93dyUK5pnmIrfP/jBO6Pen8enjGYaGzjE4GCZcoL9/H319nzEw8J3vWZ3d//AhRP0sE2EFx8dpnJ5mEQo9kGqhF0q9blLzo4TIP1hbuyH85PNbLRCIUPK32N5OolxWuNW3cGTZ4IS/AdMtiwnxpX7wAAAAAElFTkSuQmCC')\",\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/f6c992d4a47d7bfd84862de0027c7346/eb3fa/image13.png\",\n \"srcSet\": [\"/static/f6c992d4a47d7bfd84862de0027c7346/a2ead/image13.png 259w\", \"/static/f6c992d4a47d7bfd84862de0027c7346/6b9fd/image13.png 518w\", \"/static/f6c992d4a47d7bfd84862de0027c7346/eb3fa/image13.png 1026w\"],\n \"sizes\": \"(max-width: 1026px) 100vw, 1026px\",\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 Confidentiality, Integrity, and Availability (CIA) triad and the\\nPrevent, Mitigate, and Recover (PMR) constructs are useful in mapping\\ncyber to the four layers in the pyramid. The CIA triad can be thought of\\nas the desired effects akin to Mission Effects for a system that enables\\nor performs cyber defense operations, while the attributes associated\\nwith the PMR construct can be thought of as enabling the CIA effects and\\nakin to System Capabilities, System Functions and Properties, and System\\nStructure. Therefore, the CIA triad leads to cyber-related \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", since\\nthey look at achieving desired effects. The PMR attributes lead to\\ncyber-related MOPs/MOSs, since they address required system\\ncapabilities, functions, characteristics, and logistics. This guide\\nshould act as a guideline for measures evaluating cybersecurity, cyber\\nsurvivability and cyber resiliency of a system can take any of the three\\nmeasure forms (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Suitability OR Military Occupational Specialty\"\n }, \"MOS\"), \").\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Cyber related considerations for \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Design Constructs.\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\ntypically uses one of three different \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" design constructs for planning\\nand reporting cyber-related effects as part of the overall \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. The\\nappropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" design construct is typically determined/developed when\\nbuilding the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct. The choice of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct for cyber\\nhas an impact on the selection of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \", MOPs, and MOSs and where they\\nare placed in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct. The three \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" constructs are designated\\nas Integrated, Stand-Alone, and Hybrid. Descriptions of the\\ncyber-related \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" design constructs follow with examples of evaluation\\nsummary charts (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \") for each.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Integrated\"), \" Construct.\"), \" For integrated constructs (commonly referred\\nto as traditional or Ops-based), the test team covers cyber effects\\nwithin the measures under each operational COIs.\"), mdx(\"p\", null, \"Cyber operational conditions, cyber threats, and cyber-related measures\\nare addressed within the context of each mission or operations-based \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \"\\n(wherever cyber can affect operational outcome). Cyber-related MOPs/MOSs\\ncover all attributes associated with PMR and the ten CSAs (cyber\\nsurvivability attributes). This \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct also allows for\\ncyber-related \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measure of Effectiveness\"\n }, \"MOE\"), \"\\u2019s addressing CIA to be outlined separately across the\\noperational COIs, if needed.\"), mdx(\"p\", null, \"Using the integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct, identified/ notable cyber-related\\nissues that extend beyond the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" (i.e., do not affect the degree of\\nmission accomplishment of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" or the ability to place in field use)\\nmay be addressed in an annex to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E report, if warranted. Figure\\nC-2 shows an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" example for the Integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Construct.\"), mdx(\"p\", null, \"Figure C-2. Integrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Construct \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" Example\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"768px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/e6a04a7d94d01652d98ca181f791f26e/e5715/image14.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\": \"69.11196911196912%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAOCAYAAAAvxDzwAAAACXBIWXMAAA7DAAAOwwHHb6hkAAACg0lEQVQ4y22T2XaiQBCG8/i5mZmbvMbM3SQnycTsUQcBiWvYoZFFcQFEjQH/KTBxzNLnFF3dVf1RVV19ABqbzWYnWZbBcRzoug7DMMAYK3XLsmDbdrn3pg8GAyyWK2QbYE2fnM4fFJCPQ9M0iGITtVodsqyQyOB5HhzHlTCeF9DtdtHpdGAwH33FgGIOsHohYAFIkpii0CgyhtEwgGXq8F0HzDbgDhhMs4jKLGfPc6GqCsJwSL4+/DBC+1GCppt4zrAFei7D+ekv/K1VoMkiBOEOfLOGVleE1OJoj4drt8EMCboiQFcFGKqIZvsR3jiF4wawvRCrdb4FzmazslZxkiCdx6jUNfy8ZjjlQ/yuebhqUJpPU3D9Kbp6iBFBZJbACVLMohQvOfBMn7KGBXAymZRFXi4XWC3X4NsXqLaP0TabBKrirHoGniLjKapqu4GuxiFJ+0jTFp0ZvVZ+exe7CIvCh2GIxeIZo1EDcXSF+bxBtluq3zda/yDbEQbed1ofku2IAjkkqLTFbbKyS3YRFrfmeT45JlQbHccVASeXIu65Hs5v7nFSucLF3QOtOdKvcXZ9iz83d3CDoATmm70I4zhGQIbhcFjCTZuhJ6t4EPuoN58gqxbqkoV7QceTwnD5twexo0Hq0G2PZ3jr5R0wocuYTqelFLrrj+jPYwTjCJI6hOMzzBMdpmdgMrWhOmPk2ZrSnVMZFp+Bxabv+5SyhyiKoLMAYs9ER/NguBNISguKcU66gJbWLHtvsUhL39Vq9R741Uv5aviUmWGPoFghPbP3tn3Gwce3/CZ5/jqXzht6VjmkxxbVUH0F/vf9lPJXwH0pRtG443iJMFriJcuxf24f+A/hpxU9HA+24QAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image14\",\n \"title\": \"image14\",\n \"src\": \"/static/e6a04a7d94d01652d98ca181f791f26e/e5715/image14.png\",\n \"srcSet\": [\"/static/e6a04a7d94d01652d98ca181f791f26e/a2ead/image14.png 259w\", \"/static/e6a04a7d94d01652d98ca181f791f26e/6b9fd/image14.png 518w\", \"/static/e6a04a7d94d01652d98ca181f791f26e/e5715/image14.png 768w\"],\n \"sizes\": \"(max-width: 768px) 100vw, 768px\",\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, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Stand-Alone\"), \" Construct.\"), \" In the stand-alone \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct, a\\nseparate Cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" unifies and/or compartmentalizes the impacts to\\nmission and/or operations of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" when employed within a\\ncyber-contested environment. This \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct allows the baselining of\\nuncontested performance in a cyber benign environment, as compared to\\nperformance of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" in a cyber-contested environment. All\\ncyber-contested operational conditions, threats, measures, and test\\nevents are addressed within the separate cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \". The separate cyber\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" captures all cyber survivability, cyber resiliency and\\ncybersecurity-related measures. These cyber-related measures cover all\\nattributes associated with CIA, PMR, and the ten CSAs.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Composite Measures\")), \" (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 4 in Figure C-3) are used to collect and\\naggregate the effects of a cyber-contested environment on measures from\\nthe operational COIs. There should be a composite measure for each of\\nthe operational COIs. Additional cyber-specific measures address the\\nsystem\\u2019s cyber operational capabilities.\"), mdx(\"p\", null, \"Figure C-3. Stand Alone \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Construct \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" Example\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"791px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/e6d5208c0a400e8b54ab8eb67b433df2/cc8d6/image15.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\": \"73.74517374517376%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAPCAYAAADkmO9VAAAACXBIWXMAAA7DAAAOwwHHb6hkAAAC3ElEQVQ4y5VU227TUBDs/38CT6hSxRtS4YGiQmkLIrSENHHusRPb8d0+ie/XxBn2nKRFvCBhabwr25nZ3TObM/zndTjFlpIwKeGxEHFe43A4CJzx2263w36/F3h+8S9w2rrZg0UZXNdFkjcnNSKs6xocTdMgz3MYhiFgWdZLbpqmwPMzHvM8w9LawmYpEVZodnvBeVZV1Us7nLjX66Hb7cJxHEynU5FzMlmW0el0BKFt2xhIEhbKEpYf4rE3wspiR8KiKMBJOVmSJFAUBcvlEr4fQNd1kUdRhPV6DVVVRRe8Tf7cMg1IiouxbMBhyZGQf8AYQ1GUYoZZmh7H0bbIsozEauwpj0msrhu0dBp+EEDTdGy3IQw/xXLtwgpOhIx5GDx9g9TvYDb9hdlcwlweYTofwFxP4JhT2MYEujqEoU8E5HkPyqIHedHHQjXQ6Q4p2qj3dChJHFNrGvIsge0GuLwb4qZv4bqrQTVduGQLy2PURUDtJtRBTNWtMB4NYTkuTC8kcRmmy9AIQmrF8zw0dQWHBnz5VcPnfoSrnx7e3qm46m7wocvoBxl9AyJtaZZrSIMBXJ9hEyZ/+fQspgr5KZZFBZ/Z+DE4x1T/goH8CQ/Se4y1GwHdvKYuvtNc78kBNArbQxQnmOsBwqxB1bR0Bu2xQlVdIQwjUidkE7R7neICvndOVV1g17wh0VdIswuU5WsE7AmeH4vDNL0tRpM5pPGMiOtjhdwePMakmKQNirIlqxQkUBJBTUQFWSqjvEFd7fDwa4h3H29xdfuI+74GWXchazaycneskDufe8v3fVRlTqtYieHntKNVxe1Tk0BMhAXZKydDqxjNFEyVNVnGw2qlIiUyMcOUfLfZbMhTW/IXg0JKmuljZXCBEb0bEdmYokMChTA5R03LwAVMJ8BiqSFKyz+rxyvj2NIc5ysbM4JKqxQEPcID0vSJqgyoukpsCi+CRwG+EAec/jSA32QEY/Fq396vAAAAAElFTkSuQmCC')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image15\",\n \"title\": \"image15\",\n \"src\": \"/static/e6d5208c0a400e8b54ab8eb67b433df2/cc8d6/image15.png\",\n \"srcSet\": [\"/static/e6d5208c0a400e8b54ab8eb67b433df2/a2ead/image15.png 259w\", \"/static/e6d5208c0a400e8b54ab8eb67b433df2/6b9fd/image15.png 518w\", \"/static/e6d5208c0a400e8b54ab8eb67b433df2/cc8d6/image15.png 791w\"],\n \"sizes\": \"(max-width: 791px) 100vw, 791px\",\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, mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"Hybrid\"), \" Construct.\"), \" The \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Hybrid\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct applies elements of\\nboth the Integrated and Stand-Alone \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" constructs. Similar to the\\nIntegrated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct, cyber effects are addressed within the\\noperations-based COIs. Additionally, a separate cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is created to\\nallow the test team to focus on capturing non-disruptive and/or indirect\\ncyber effects or the underlying/common cyber aspects across the system.\"), mdx(\"p\", null, \"Cyber operational conditions, cyber threats, cyber-related measures, and\\ncyber test events are addressed within the context of the operational\\nCOIs. The separate cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is functionally focused (i.e., cyber\\nrelated operational capabilities) and also addresses effects not seen\\nwithin the missions or operational COIs (e.g., indirect effects, 2nd/3rd\\norder effects, exfiltration). The separate cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" may also be used to\\nexpand cyber reporting beyond the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \", if warranted. Figure C-4 shows an\\nexample \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" for the Hybrid \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct.\"), mdx(\"p\", null, \"Figure C-4. Hybrid Construct \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Electromagnetic Spectrum Certification OR Evaluation Summary Chart\"\n }, \"ESC\"), \" Example\"), mdx(\"span\", {\n \"className\": \"gatsby-resp-image-wrapper\",\n \"style\": {\n \"position\": \"relative\",\n \"display\": \"block\",\n \"marginLeft\": \"auto\",\n \"marginRight\": \"auto\",\n \"maxWidth\": \"844px\"\n }\n }, \"\\n \", mdx(\"a\", {\n parentName: \"span\",\n \"className\": \"gatsby-resp-image-link\",\n \"href\": \"/static/b0e68fbd01d37d0cd3a38ba8367feb26/33e10/image16.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\": \"66.40926640926641%\",\n \"position\": \"relative\",\n \"bottom\": \"0\",\n \"left\": \"0\",\n \"backgroundImage\": \"url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAANCAYAAACpUE5eAAAACXBIWXMAAA7DAAAOwwHHb6hkAAACX0lEQVQ4y41Ty3LaQBDk+3NJcssvpCqHVC44dqWMKQhgx4DBSAL0fj9YoTcgOXRGqhg7sQ+eqq2dlXZ6ert3W/gvjscj3hosyuB4G+T7h1NtK4wLeCxBtivrL82PJElgmiYcx4Ft2/8M13VhWxYsi9ZBDNNliLPdqUlL0myIoojsb5c66qJev48Fx0HXdQwGAwiCAE3TMBwOoShKAzj4NW+apvketheCxTlasu5AkSVaFLAdD2mawvf9pkkYsiZfLldgYQiP8hqsKApsNgymYYKxEFaQYiVSEz9Cyw4iKIYLSTVwddnG/G6EpTABz4+hG2vI0hyWvoBrCVDlGQyNg6nzEFdTyOKMyNzD32ywL39jd6jQejxmEkdQVRlpEmLGy/h8zqN9beNiKOOWs3C9cLFWPNqXEestPM9DtGUIAhdFnj1p+OhqFMUEqOKhOkKzRPTnZ+DMe3THHfTuehhLU4jGLapyhf2eQ5a6qCpitds14+Ty8ZmzorhGTAwYk0n0M2y3U9LpC5nxjth8oobvoWof4Acf4bgj0jSCS0zzvHgJWJtRu1jTlxQLX9tDdAYcvncn+HbewdVggvPuDdo/ergaTnHRHVHex+XPMQK2fR3QMAwwEtgg9xbCChrNM15Ff6JhtjIwmsngliKWko7ZYoXFUgK/VhHFyUvAPM9JaL+5Kq6/gaS70Bw6ki/BCxZQKZeMoLlzBe1NSaKyPDT5qxqWZUnGRKRljCjJoJg+AcbYbE24gQCOF3AzGiLYpsiLPRmzx+FwaOaqqp4A3/J+61fpsxiOz5Dkh9P+53WP+R8gAcwl2sfOGAAAAABJRU5ErkJggg==')\",\n \"backgroundSize\": \"cover\",\n \"display\": \"block\"\n }\n }), \"\\n \", mdx(\"img\", {\n parentName: \"a\",\n \"className\": \"gatsby-resp-image-image\",\n \"alt\": \"image16\",\n \"title\": \"image16\",\n \"src\": \"/static/b0e68fbd01d37d0cd3a38ba8367feb26/33e10/image16.png\",\n \"srcSet\": [\"/static/b0e68fbd01d37d0cd3a38ba8367feb26/a2ead/image16.png 259w\", \"/static/b0e68fbd01d37d0cd3a38ba8367feb26/6b9fd/image16.png 518w\", \"/static/b0e68fbd01d37d0cd3a38ba8367feb26/33e10/image16.png 844w\"],\n \"sizes\": \"(max-width: 844px) 100vw, 844px\",\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, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measures Development.\"), \" Regardless of what \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct is selected,\\ntest teams must develop measures addressing cyber survivability, cyber\\nresiliency, and cybersecurity for their SUTs.\"), mdx(\"p\", null, \"The selection of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct (and development of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \") is\\naccomplished as part of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E Construct. At the Measures Workshop\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Measures of Effectiveness\"\n }, \"MOEs\"), \" are refined, and MOSs and MOPs are developed. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", Detachment\\ncyber analysts, the detachment test team, cyber test subject matter\\nexperts (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \") from A-3I, and analysts from A-2/9 collaborate on\\ndeveloping system-specific, mission-centric cyber-related measures.\"), mdx(\"p\", null, \"Developing quantitative and observable qualitative operationally\\nrelevant measures is a complex challenge that requires careful\\ncollaboration with all stakeholders. As teams develop measures to suit\\nspecific systems under test, the cyber teams develop cyber-related\\nmeasures that address and evaluate: \", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"effects, capabilities,\")), \"\\n\", mdx(\"strong\", {\n parentName: \"p\"\n }, mdx(\"em\", {\n parentName: \"strong\"\n }, \"attributes, and characteristics\")), \" that contribute to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\u2019s\\ndegree of cyber survivability, cyber resiliency and cybersecurity.\"), mdx(\"p\", null, \"Cyber survivability, resiliency and security can be represented with the\\nCIA triad of effects and the PMR associated attributes. A cyber-related\\nmeasure addressing CIA effects and/or PMR related attributes may be\\nincluded, or CIA effects and/or PMR related attributes may be aggregated\\ninto composite measures. Table C-1 contains definitions for CIA. Table\\nC-2 contains definitions for PMR and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"\\u2019s. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Note\"), \": if a separate cyber\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" is employed the test team must still address PMR and CIA.\"), mdx(\"p\", null, \"Table C-1. CIA Defined\", \"[3]\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"CIA\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Confidentiality\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information.\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Integrity\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Guarding against improper information modification or destruction and ensuring information non-repudiation and authenticity.\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Data Integrity\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"The property that data has not been altered in an unauthorized manner. Data integrity covers data in storage, during processing, and while in transit.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"System Integrity\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"The quality that a system has when it performs its intended function in an unimpaired manner, free from unauthorized manipulation of the system, whether intentional or accidental.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Availability\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Ensuring timely and reliable access to and use of information.\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"Table C-2. System Survivability (SS) Key Performance Parameter (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \")\\nPillars\", \"[4]\", \" Defined and Mapped to their Cyber Survivability Attributes\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \")\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"SS \", mdx(\"abbr\", {\n parentName: \"th\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \"\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Description\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Cyber Survivability Attribute\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"PMR\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Prevent\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Design principles and operations that enable or provide protection of the systems mission functions from most likely cyber threats\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-01 \\u2013 Control Access\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-10 \\u2013 Actively Manage System Configurations to Counter Vulnerabilities at Tactically Relevant Speeds\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-02 \\u2013 Reduce System\\u2019s Cyber Detectability\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-03 \\u2013 Secure Transmissions and Communications\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-04 \\u2013 Protect System\\u2019s Information from Exploitation\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-05 \\u2013 Partition and Ensure Critical Functions at Mission Completion Performance Levels\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-06 \\u2013 Minimize and Harden Attack Surfaces\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Mitigate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Design principles and operations that enable or provide detection and responding to cyber-attacks, enabling the system to survive, operate in a degraded environment, and complete the mission\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-07 \\u2013 Baseline & Monitor Systems and Detect Anomalies\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-08 \\u2013 Manage System Performance if Degraded by Cyber Events\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Recover\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Design principles and operations that enable or provide \", mdx(\"em\", {\n parentName: \"td\"\n }, mdx(\"u\", null, \"recovery\")), \" from cyber-attacks and prepare mission systems for the next fight\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Combat Support Agency\"\n }, \"CSA\"), \"-09 \\u2013 Recover System Capabilities\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, \"The goal of measures development is to produce operationally relevant\\nquantitative and qualitative measures. Each system is examined to\\ndetermine whether additional operationally relevant measures need to be\\napplied. Keep in mind that the structure and placement of cyber-related\\nmeasures will depend on choice of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" construct (Integrated,\\nStand-Alone, or Hybrid) made during the initial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E construct (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Test Design\"\n }, \"ITD\"), \")\\nmeeting.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Cyber-Related Measures Rating Options.\"), \" The Cyber-related Measures\\nAppendix is not intended to detail or specify how to rate cyber\\nmeasures. Refer to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Cyber Test Guide for guidance on how to\\nscore measures using operationally relevant data. The options presented\\nin the tables and figures that follow are provided to help cyber\\nanalysts look ahead to how measures are rated, while developing the\\nmeasures.\"), mdx(\"p\", null, \"One needs to establish an expected result for each operationally\\nrelevant measure. Rating of each measure will be based on the degree to\\nwhich test results meet expectations and requirements.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure Rating: Tier Set Option.\"), \" The following Cyber Tier Set Rating\\nScale is the first option provided to help influence cyber-related\\nmeasures development. Tables C-3 and C-4 show examples of tier sets,\\nthreshold levels, ratings and their descriptions for measures addressing\\ncyber survivability.\"), mdx(\"p\", null, \"Detachment cyber analysts have the autonomy to modify input for best\\npractice and with locally approved language that is defensible. Consider\\nthese to simply be a menu of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" approved tier sets and approaches.\"), mdx(\"p\", null, \"Table C-3. Ratings for Cyber-Related Measures for Cyber Survivability\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Tier Set\"), mdx(\"th\", null, \"Threshold Level\"), mdx(\"th\", null, \"Rating\"), mdx(\"th\", null, \"Rating Description\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Security\")), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Highly Effective\"), mdx(\"td\", null, \"Acts that bypass security policies, practices, or procedures are rapidly detected, cleaned and prevented from happening again. They do not degrade mission effects.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Effective\"), mdx(\"td\", null, \"Security breaches have minimal impact to System Capabilities, System Functions and Properties, but no degradation of Mission Effects.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Appears to be adequate\"), mdx(\"td\", null, \"Security breaches impact System Capabilities, System Functions and Properties, or System Structure, and minimally degrade Mission Effects.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Minimal with breaches\"), mdx(\"td\", null, \"Security breaches impact System Capabilities, System Functions and Properties, or System Structure, and significantly degrade Mission Effects.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"None\"), mdx(\"td\", null, \"There are no security policies, practices, or procedures in place to prevent breaches. This leads to no mission accomplishment.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Proactive Protection\")), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Protected\"), mdx(\"td\", null, \"System-wide protection has proactive processes in identifying and mitigating disruptions. System is alert to new disruptions and puts corrective measures in place immediately.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Protection measures in place\"), mdx(\"td\", null, \"System has many protective measures in place. It is not totally proactive in its corrective action. However, it is able to identify problems and react appropriately and swiftly to ensure mission accomplishment.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Some system-wide protection available\"), mdx(\"td\", null, \"System has elementary protection measures. Primary mode of correction is reactionary to disruptions. Little time is available to be proactive. Although impacted, some system-wide protection remains.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Minimal, isolated protection\"), mdx(\"td\", null, \"No system-wide protection in place. Disruptions circumvent any protection measures attempted. Fixes turn out to be temporary in addressing symptoms and not causes.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"No protection\"), mdx(\"td\", null, \"System has little or no protection at all.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Vigilance\"), \" (Detection)\"), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Maintains awareness of new vulnerabilities\"), mdx(\"td\", null, \"System enables operators/defenders to maintain awareness of all known vulnerabilities, actively researches and identifies potentials for new vulnerabilities, and is able to project vulnerabilities that result from new technology development.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Able to react to new vulnerabilities\"), mdx(\"td\", null, \"System enables operators/defenders to address all known sources of disruption and/or vulnerabilities. The ability to address the surfacing of new sources of disruption and/or vulnerabilities is a reactive, but effective, process.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Able to mitigate most vulnerabilities\"), mdx(\"td\", null, \"System enables operators/defenders to identify existing vulnerabilities, mitigate most major vulnerabilities and react to disruptions. Although impacted, some awareness of attacks remains.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Not able to address new vulnerabilities\"), mdx(\"td\", null, \"System enables operators/defenders to have a basic understanding of vulnerabilities and has cursory awareness of them. Provides no ability to address new vulnerabilities ahead of disruptions.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"Unaware of vulnerabilities\"), mdx(\"td\", null, \"System\\u2019s design specification provides no consideration for detection of abnormal/malicious activity.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Mitigations\"), \" (Response)\"), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Successful in mitigating or avoiding all known attacks\"), mdx(\"td\", null, \"All known attacks did not affect operational availability of accurate data or lead to the unauthorized disclosure of data. System was able to tolerate and mitigate and continue operations as normal.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Successful in mitigating or avoiding most attacks\"), mdx(\"td\", null, \"Attacks are present, but do not affect successful completion of mission. Specific actions need to be taken; however, they are successful in mitigating any effects.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Some proactive measures in place\"), mdx(\"td\", null, \"Attacks are serious and cannot be ignored. More reactive than proactive measures are necessary. Many consequences of attacks are unexpected. Although impacted, some protective measures/capabilities remain.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Reactive measures taken\"), mdx(\"td\", null, \"Attacks are critical to the system operation and mission accomplishment. The reactive measures do not handle all of the attacks.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"No measures available\"), mdx(\"td\", null, \"Attacks are catastrophic and result in system shutdown.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Recovery\")), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Immediate Recovery\"), mdx(\"td\", null, \"The system is able to recover after attacks immediately such that there is no critical or non-critical mission impact.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Rapid Recovery\"), mdx(\"td\", null, \"There is observable downtime after an attack, but the system is able to recover before a critical mission impact occurs (non-critical mission impacts may occur).\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Timely Recovery\"), mdx(\"td\", null, \"There is minimal impact to critical mission after an attack due to downtime.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Can Recover Eventually\"), mdx(\"td\", null, \"Significant effort is required to recover after an attack resulting in severe mission impact.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"Unrecoverable\"), mdx(\"td\", null, \"The system is completely unrecoverable after an attack.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, mdx(\"strong\", null, \"Continuity of Operations\")), mdx(\"p\", null, \"(Transfer and Continue Ops)\")), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Maximum\"), mdx(\"td\", null, \"System successfully transfers full functionality. System remains highly capable of completing the mission.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Able to operate effectively\"), mdx(\"td\", null, \"System is able to transfer functionality required to meet most mission requirements. System may experience some minor problems, but effectively accomplishes the mission.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Meeting minimum requirements\"), mdx(\"td\", null, \"System is able to transfer only minimal functionality. System is struggling, but meets minimum mission requirements.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Failing\"), mdx(\"td\", null, \"Transfer is unable to meet most mission requirements. Delays and/or the lack of functionality are a distraction to the mission.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"Complete breakdown\"), mdx(\"td\", null, \"System is unable to transfer functionality, and is unable to continue operations.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Normal Operations\")), mdx(\"td\", null, \"V\"), mdx(\"td\", null, \"Full capabilities online\"), mdx(\"td\", null, \"System is highly capable of completing the mission. System is running all subsystems, processes and applications with no problems. System-wide protection has proactive processes in identifying and mitigating disruptions. System confidence is high.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"IV\"), mdx(\"td\", null, \"Maintains normal operations, reaches new equilibrium\"), mdx(\"td\", null, \"System experiences some minor problems but effectively accomplishes the mission. System is running normal operations; however, it is continuously adjusting for disruptions. System has many protective measures in place. System confidence is adequate.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"III\"), mdx(\"td\", null, \"Struggles to stay ahead of problems\"), mdx(\"td\", null, \"System is struggling to meet mission requirements. Subsystems, processes and applications are occasionally failing. System has elementary protection measures. System confidence is moderate illustrating concern over mission accomplishment and integrity of the system. Although impacted, minimum mission accomplishment continues.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"II\"), mdx(\"td\", null, \"Experiencing outages, delays and blackouts\"), mdx(\"td\", null, \"System cannot meet most mission requirements, is impacted by problems, and cannot keep up with mitigating actions. System is spending more time addressing disruptions than accomplishing the mission. No system-wide protection is in place. Low confidence that the system can be counted on to do the mission.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null), mdx(\"td\", null, \"I\"), mdx(\"td\", null, \"System failure\"), mdx(\"td\", null, \"System cannot meet mission requirements. System crashes or is near to crashing under the weight of disruptions. System has little or no protection at all. No confidence that the system can be counted on to do the mission.\")))), mdx(\"p\", null, \"Table C-4. Ratings and Descriptions for PMR and Associated CSAs\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Tier Set\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold Level\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rating\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rating Description\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Prevent, Mitigate, Recover, and/or All-Encompassing\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"V\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Exceeds Capability Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Goes above and beyond the CSRC associated required capability standard to ensure the most secure cyber posture possible.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"IV\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Meets Capability Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Meets the CSRC associated required capability standard for effective cyber-security.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"II\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Approaches Capability Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"CSRC associated required capability standard is not met, however the system is close to achieving the standard.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"II\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Fails Capability Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"CSRC associated required capability standard is not close to being met and the system needs significant improvement in its cyber posture.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"I\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Entirely Fails Capability Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"System has no cybersecurity capability whatsoever and lacks even the most basic components to pass the CSRC associated required capability standard.\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure Rating: Tier Threshold to Mission Impact Heat Chart Option.\"), \"\\nThe following scale is the second menu option provided to help influence\\ncyber-related measures development. Here cyber-related impacts to the\\nmission correlate to tier thresholds and the mission of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" through\\nthe use of a heat chart. Tables C-5 and C-6 contain risk based scales to\\ninfluence cyber-related measures development.\"), mdx(\"p\", null, \"Table C-5. Tier Threshold to Mission Impact Comparison Heat Chart\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Tier Threshold\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"I\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"II\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"III\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"IV\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"V\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Impact\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Catastrophic\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Major\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Moderate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"1\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")))), mdx(\"p\", null, \"Table C-6. Mission Impact Descriptions\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Level\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Impact\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Description\"))), 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 }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Little to no mission degradation\")), 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 }, \"Moderate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Partial mission degradation\")), 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 }, \"Major\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Critical mission degradation\")), 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 }, \"Catastrophic\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Complete mission failure\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Measure Rating: Cyber Survivability Risk Category (CSRC) Heat Chart\\nOption.\"), \" In this option the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\u2019s assigned CSRC will drive selection of\\nthe required/expected metric and threshold for each cyber-related\\nmeasure. Definitions of the CSRCs and a description of the process used\\nto select the appropriate CSRC for a \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" can be found in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Chiefs of Staff\"\n }, \"JCS\"), \" Cyber\\nSurvivability Endorsement Implementation Guide (CSEIG), Version 1.01. In\\ngeneral, The CSRC is determined from a combination of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\u2019s Mission\\nType (MT), Cyber Dependence Level (CDL), Adversary Threat Tier (ATT),\\nand Impact of System Compromise (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Involvement Letter\"\n }, \"IL\"), \"). Levels vary from 1 through 4.\\nTheir associated required capability standards are detailed in Table\\nC-7.\"), mdx(\"p\", null, \"Table C-7. Tiers and Descriptions of Associated Capability Standards\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Tier\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Description of Capability Standards (Tiers)\"))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"V\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Very High\"), \": Mitigations rely on best available countermeasures, to include custom \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" protections, commensurate against assumed threat capabilities.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"IV\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"High\"), \": Mitigations include Enhanced Assurance \\u2013 redundancy, TTPs, and strong \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commercial Off-the-Shelf\"\n }, \"COTS\"), \"/\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Government Off-the-Shelf\"\n }, \"GOTS\"), \" securely configured in layered architectures \\u2013 with \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" added technology, as needed.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"III\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Moderate\"), \": Mitigations include \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commercial Off-the-Shelf\"\n }, \"COTS\"), \"/\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Government Off-the-Shelf\"\n }, \"GOTS\"), \" cybersecurity products and technologies, with potential \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" technology additions, with best practices, strong \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" layered defenses, and selective use of \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" technology.\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"II\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Low\"), \": Mitigations include \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Commercial Off-the-Shelf\"\n }, \"COTS\"), \" with best practices if commercially hosted, or strong \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" layered defenses, possible use of \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" technology if \", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" hosted\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"I\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, mdx(\"strong\", {\n parentName: \"td\"\n }, \"Poor\"), \": Mitigations do not exists or are totally ineffective\")))), mdx(\"p\", null, \"Similar to the tier rating scale, a heat chart could also be used in\\nconjunction with the program\\u2019s assigned CSRC. After determination of the\\nassociated CSRC Level, a correlation to a low, medium, or high (e.g.,\\ngreen, yellow, red) reporting standard can easily be mapped against the\\ntier threshold (Table C-8).\"), mdx(\"p\", null, \"Table C-8. Tier Threshold to CSRC Comparison Heat Chart\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Tier Threshold\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"I (Poor)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"II (Low)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"III (Moderate)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"IV (High)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"V (Very High)\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"CSRC Level\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"1\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Examples of Cyber-related Measures.\"), \" In general, it is up to the\\ndetachment and test team to determine the appropriate format for their\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \"\\u2019s cyber-related \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" programs cybersecurity construct and associated\\nmeasures.\"), mdx(\"p\", null, \"What follows are two example cyber-related measures. This section is not\\nmeant to be an all-inclusive list of cyber-related measures. Nor is it\\nintended to be a checklist, or a cut-and-paste template. Rather, this\\nsection is intended to demonstrate acceptable cyber-related measures and\\nwhat should be included in a cyber-related measure worksheet. Test teams\\nare encouraged to develop and use variations of these cyber-related\\nmeasures (or new cyber-related measures) in order to best suit the needs\\nof their individual SUTs.\"), mdx(\"p\", null, \"The cyber-related measures in the Measures Summary (Tables C-9 and C-10)\\nand the Cyber-related Measure Worksheets (Tables C-11 thru C-14) are\\nexamples of how to evaluate the cyber risk to a system for the separate\\nCyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" in the \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CStand Alone\\u201D\"), \" or \", mdx(\"em\", {\n parentName: \"p\"\n }, \"\\u201CHybrid\\u201D\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" Construct. They use a\\nkind of behaviorally anchored rating scale (i.e., tiers and heat charts)\\nto identify the levels of effectiveness and performance. These anchors\\ncan be tailored to a particular system or test program and ideally would\\nbe defined such that they are observable, measureable and independently\\nverifiable (i.e., via an inter-observer agreement).\"), mdx(\"p\", null, \"Table C-9. Example of a Separate Cyber \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \", Tier Based\", mdx(\"br\", {\n parentName: \"p\"\n }), \"\\n\", \"Cyber-related Measures Summary Table\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Measure\"), mdx(\"th\", null, \"Tier Set\"), mdx(\"th\", null, \"Metric\"), mdx(\"th\", null, \"Threshold Level\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOE 4.1: Rating of NG DRAGON\\u2019s Confidentiality of Data and System Information \", mdx(\"strong\", null, \"(C)\")), mdx(\"td\", null, \"Confidentiality\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOE 4.2: Rating of NG DRAGON\\u2019s Integrity of Data and System (I)\"), mdx(\"td\", null, \"Integrity\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOE 4.3: Rating of NG DRAGON\\u2019s Availability of Data and System (A)\"), mdx(\"td\", null, \"Availability\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 1: Rating of NG Dragon\\u2019s Capabilities, Functions, Properties, and Structure Enabling Operational Users and Service Providers Management of Cybersecurity Risk to Systems, Assets, Data, and Capabilities\"), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 2: Rating of NG DRAGON\\u2019s Physical Security / Protection Against Physical Threats\"), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 3: Rating of NG DRAGON\\u2019s Detection of Abnormal/Malicious Activity\"), mdx(\"td\", null, \"Vigilance\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 4: Rating of NG DRAGON\\u2019s Response to Abnormal / Malicious Activity Without Degrading Capabilities (Incident Response)\"), mdx(\"td\", null, \"Mitigations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 5: Rating of NG DRAGON\\u2019s Restoring Sustained, Operationally Acceptable Capabilities after Abnormal/Malicious Activity (Mission Restoration)\"), mdx(\"td\", null, \"Recovery\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 6: Rating of NG DRAGON\\u2019s Capability to Recover Operationally Acceptable Data after Abnormal/Malicious Activity (Data Recovery)\"), mdx(\"td\", null, \"Recovery\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 7: Rating of NG DRAGON\\u2019s Transfer of Mission, Continuity of Operations after Abnormal/Malicious Activity\"), mdx(\"td\", null, \"COOP\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 8: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling Depot Maintenance Planning in a Contested Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOP 9: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling Depot Maintenance Scheduling in a Contested Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 10: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling Depot Maintenance Execution in a Disruptive Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOP 11: Rating of NG DRAGON Providing Enterprise Standardization and Visibility in a Disruptive Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOS 1: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling it to be Maintained (Maintainability) in a Disruptive Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOS 2: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling it to be Supported (Supportability) in a Disruptive Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOS 3: Rating of NG DRAGON\\u2019s Capabilities, Functions, Properties, and Structure Enabling it to Operate Within The Operational Infrastructure in a Disruptive Cyber Environment\"), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 12: Instances when NG DRAGON Does Not Process (Input/Output) Critical IERs\"), mdx(\"td\", null), mdx(\"td\", null, \"Maximum\"), mdx(\"td\", null, \"^ Zero\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 13: Non-Critical IER Exchanges that Process Successfully (Input/Output) on the First Try\"), mdx(\"td\", null), mdx(\"td\", null, \"Percentage\"), mdx(\"td\", null, \"^ \\u2265 90%\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOS 4: Rating of the Supply Chain Management (HW/SW) of NG DRAGON\"), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 14: Rating of the Configuration Control of NG DRAGON\"), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOS 5: Rating of Awareness Training for the Users of NG DRAGON\"), mdx(\"td\", null, \"Protection\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 15: Rating of the Security of NG DRAGON\\u2019s Architecture/Network\"), mdx(\"td\", null, \"Protection\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOP 16: Rating of the Software Security of NG DRAGON\"), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 17: Rating of the Boundary Protection (External Protection) of NG DRAGON\"), mdx(\"td\", null, \"Protection\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"MOP 18: Rating of the Access Management (Internal Protection) of NG DRAGON\"), mdx(\"td\", null, \"Protection\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"MOP 19: Rating of Situational Awareness (Indications and Warnings) of NG DRAGON\"), mdx(\"td\", null, \"Vigilance\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"* KPP or Supports KPP\", mdx(\"br\", null), \"^ AFOTEC Identified Standard (i.e., not specified in requirement documents)\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, \"Table C-10. Example - Cyber-related Measures and\", mdx(\"br\", {\n parentName: \"p\"\n }), \"\\n\", \"Cyber Survivability Tier Threshold Summary\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Measure\"), mdx(\"th\", null, \"Tier Set\"), mdx(\"th\", null, \"V\"), mdx(\"th\", null, \"IV\"), mdx(\"th\", null, \"III\"), mdx(\"th\", null, \"II\"), mdx(\"th\", null, \"I\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOE 4.1\"), mdx(\"td\", null, \"Confidentiality\"), mdx(\"td\", null, \"Very High\"), mdx(\"td\", null, \"High\"), mdx(\"td\", null, \"Moderate\"), mdx(\"td\", null, \"Low\"), mdx(\"td\", null, \"Poor\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOE 4.2\"), mdx(\"td\", null, \"Integrity\"), mdx(\"td\", null, \"Very High\"), mdx(\"td\", null, \"High\"), mdx(\"td\", null, \"Moderate\"), mdx(\"td\", null, \"Low\"), mdx(\"td\", null, \"Poor\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOE 4.3\"), mdx(\"td\", null, \"Availability\"), mdx(\"td\", null, \"Very High\"), mdx(\"td\", null, \"High\"), mdx(\"td\", null, \"Moderate\"), mdx(\"td\", null, \"Low\"), mdx(\"td\", null, \"Poor\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"*MOP 1\"), mdx(\"p\", null, \"*MOP 2\"), mdx(\"p\", null, \"MOS 4\"), mdx(\"p\", null, \"MOP 16\"), mdx(\"p\", null, \"MOP 18\")), mdx(\"td\", null, \"Security\"), mdx(\"td\", null, \"Highly Effective\"), mdx(\"td\", null, \"Effective\"), mdx(\"td\", null, \"Appears to be adequate\"), mdx(\"td\", null, \"Minimal with breaches\"), mdx(\"td\", null, \"None\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"MOS 5\"), mdx(\"p\", null, \"MOP 15\"), mdx(\"p\", null, \"MOP 17\"), mdx(\"p\", null, \"MOP 18\")), mdx(\"td\", null, \"Protection\"), mdx(\"td\", null, \"Protected\"), mdx(\"td\", null, \"Protection measures in place\"), mdx(\"td\", null, \"Some system-wide protection available\"), mdx(\"td\", null, \"Minimal, isolated protection\"), mdx(\"td\", null, \"No protection\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"*MOP 3\"), mdx(\"p\", null, \"MOP 19\")), mdx(\"td\", null, \"Vigilance\"), mdx(\"td\", null, \"Maintains awareness of new vulnerabilities\"), mdx(\"td\", null, \"Able to react to new vulnerabilities\"), mdx(\"td\", null, \"Able to mitigate most vulnerabilities\"), mdx(\"td\", null, \"Not able to address new vulnerabilities\"), mdx(\"td\", null, \"Unaware of vulnerabilities\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*MOP 4\"), mdx(\"td\", null, \"Mitigations\"), mdx(\"td\", null, \"Attacks have little or no effect on operations\"), mdx(\"td\", null, \"Successful in mitigating or avoiding most attacks\"), mdx(\"td\", null, \"Some proactive measures in place\"), mdx(\"td\", null, \"Reactive measures taken\"), mdx(\"td\", null, \"No measures available\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOP 7\"), mdx(\"td\", null, \"COOP\"), mdx(\"td\", null, \"Maximum\"), mdx(\"td\", null, \"Able to operate effectively\"), mdx(\"td\", null, \"Meeting minimum requirements\"), mdx(\"td\", null, \"Failing\"), mdx(\"td\", null, \"Complete breakdown\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"*MOP 5\"), mdx(\"p\", null, \"*MOP 6\")), mdx(\"td\", null, \"Recovery\"), mdx(\"td\", null, \"Immediate recovery\"), mdx(\"td\", null, \"Rapid recovery\"), mdx(\"td\", null, \"Timely recovery\"), mdx(\"td\", null, \"Can recover eventually\"), mdx(\"td\", null, \"Unrecoverable\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"p\", null, \"MOP 8\"), mdx(\"p\", null, \"MOP 9\"), mdx(\"p\", null, \"MOP 10\"), mdx(\"p\", null, \"MOP 11\"), mdx(\"p\", null, \"MOS 1\"), mdx(\"p\", null, \"MOS 2\"), mdx(\"p\", null, \"MOS 3\")), mdx(\"td\", null, \"Normal Operations\"), mdx(\"td\", null, \"Full capabilities online\"), mdx(\"td\", null, \"Maintains normal operations, reaches new equilibrium\"), mdx(\"td\", null, \"Struggles to stay ahead of problems\"), mdx(\"td\", null, \"Experiencing outages, delays, and blackouts\"), mdx(\"td\", null, \"System failure\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"*KPP or Supports KPP\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, \"Table C-11. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Tier Based Cyber-Related Measure Worksheet Example\"), mdx(\"p\", null, mdx(\"em\", {\n parentName: \"p\"\n }, \"(See the main body of this guide for template and content\\nrequirements)\")), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Operational Capability: Cybersecurity\"), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Measure\"), mdx(\"td\", null, \"Metric\"), mdx(\"td\", null, \"Threshold\"), mdx(\"td\", null, \"Results\"), mdx(\"td\", null, \"Rating\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"*MOE 4.2: Rating of NG DRAGON\\u2019s Integrity of Data and Systems\"), mdx(\"td\", null, \"Minimum\"), mdx(\"td\", null, \"^ \\u2265 Tier IV\"), mdx(\"td\", null, \"TBD\"), mdx(\"td\", null, \"TBD\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"* KPP or Supports KPP\", mdx(\"br\", null), \"^ Identified Standard\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"References\"), \": \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Provide the requirement source (stated or derived).\\nSpecify the paragraph, section, line, etc. \", mdx(\"u\", null, \"This is part of the\\nexample and references could be out of date.\"))), mdx(\"p\", null, \"Derived from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo, 3 Apr 18, Procedures for Operational Test and\\nEvaluation of Cybersecurity in Acquisition Programs; Department of\\nDefense (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \") 8510.01, Risk Management Framework (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Management Framework\"\n }, \"RMF\"), \") for Department of\\nDefense (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \") Information Technology (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"), 12 Mar 14; National Institute\\nof Standards and Technology (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Institute of Standards and Technology\"\n }, \"NIST\"), \") Special Publication (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Plan OR Special Publication\"\n }, \"SP\"), \") 800-53,\\nSecurity and Privacy Controls for Federal Information Systems and\\nOrganizations, Rev. 4, 30 Apr 13.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Scope\"), \": This cyber-related measure addresses the degree NG \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"\n }, \"DRAGON\"), \"\\u2019s\\nPMR capabilities, functions, and structure enable or provide data and\\nsystem integrity. Data integrity is the property that data has not been\\naltered in an unauthorized manner while in storage, during processing,\\nor while in transit. System integrity is the quality that a system has\\nwhen performing the intended function in an unimpaired manner, free from\\nunauthorized manipulation. This measure will also consider what \\u201Cimpact\\nadversary and unauthorized modification or destruction of system\\ninformation\\u201D has on \\u201Cfunctions to the mission\\u201D (\\u201C\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Center for Systems Engineering OR Common Support Equipment\"\n }, \"CSE\"), \" Implementation\\nGuide Version 1.01\\u201D, pg. 17). This measure evaluates the following\\nprotection metrics:\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Account Management\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Least Privilege\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identification and Authentication\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Continuous Monitoring\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Device Identification and Authentication\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Authenticator Management\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Default Authenticators\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Physical Access Control\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Boundary Protection\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Secure Network Communications\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Update Management\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Malicious Code Prevention\"))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Methodology\"), \": The test team will coordinate with Blue & Red\\nTeams to conduct the Cooperative Vulnerability and Penetration\\nAssessment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \") and the Adversarial Assessment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \") respectively. The\\ntest team will review documentation, observe the system, and conduct the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \" during system use by operational users in a realistic\\noperational environment, as described in the overarching \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 4 test\\nmethodology. The test team will identify, verify, and attempt to exploit\\nvulnerabilities in the NG \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"E-3 Diminishing manufacturing sources Replacement of Avionics for Global Operations and Navigation\"\n }, \"DRAGON\"), \" system in accordance with identified\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" cybersecurity test requirements. They will leverage\\nvulnerabilities highlighted in prior risk assessments, system audit\\nreports, vulnerability and penetration team findings, and direct\\nobservation of the application of the cybersecurity controls. It is\\nassumed that the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \" will disrupt and/or even deny operations, therefore\\neffectiveness and suitability test data must be collected prior to\\ncyber-attack. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \" and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \" are expected to last approximately 2\\nweeks each.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Design\"), \": Uses overarching \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 4 test design.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data and Analysis\"), \": The test team will compare system protection\\ninformation to requirements set forth in various laws, doctrine, and\\npolicies. For each instance where the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"System Under Test\"\n }, \"SUT\"), \" is unable to provide the\\nintegrity of data or the system, the test team will assess the\\ncorresponding mission impact using a simple scale (High, Medium, Low, or\\nequivalent), operational experience, and judgment to rate the measure\\nagainst the identified standard (Integrity tier sets). The mission\\nimpact scale will be related to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Risk Management Framework\"\n }, \"RMF\"), \" categorization for integrity. In the\\nevent that exploitation of a vulnerability is precluded due to critical\\nmission requirements or safety concerns, the test team will estimate\\nmission impact based on technical expertise, operational experience, and\\nrelevant operational subject matter expert input.\"), mdx(\"p\", null, \"The test team will present cybersecurity control findings and aggregated\\nresults in the final report. Each control will be assigned a rating\\n(Met, Partially Met, Not Met, or Not Applicable) presented in table\\nformat. Cybersecurity findings will be detailed in the report narrative,\\nto include associated recommendations for risk mitigation, vulnerability\\nreduction, and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Tactics, Techniques, and Procedures OR Technology Transition Plan\"\n }, \"TTP\"), \" modification. The number of users interviewed, the\\noverall trend of responses from interviews, and highlight comments and\\nobservations concerning the cybersecurity posture will also be included\\nin the report. The test team will log and bin the total number of\\nillicit attempts according to their category level. They will also log\\nthe total number of attempts, in conjunction with illicit attempts that\\nwere defended successfully. Manual and automated intrusion methods will\\nbe delineated and logged. The \\u201Ctime to achieve access\\u201D will be\\ncalculated via the delta between the initial attempt to access and when\\naccess is achieved. The \\u201Ctime to achieve elevated access\\u201D will be\\ncalculated via the delta between access and acquisition of an elevated\\nprivilege. The report will include a description of the exploitation\\nmethod and maneuver. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" analysis will categorize tool sophistication as\\neither Novice or Advanced. The overall integrity protection rating will\\nbe based on a combination of the number of instances and each instance\\u2019s\\nimpact to the mission.\"), mdx(\"p\", null, \"Table C-12. Example of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Risk Based Cyber-Related Measure\\nWorksheet\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Operational Capability: Cybersecurity\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Measure\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Metric\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Threshold\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Results\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Rating\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"Measure of Performance\"\n }, \"MOP\"), \" 1.1: Risk to Joint OH Data (JOD) Communications in the AOR Due to Cyber Effects\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Low risk\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"To Be Determined\"\n }, \"TBD\"), \"\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"\", mdx(\"abbr\", {\n parentName: \"td\",\n \"title\": \"To Be Determined\"\n }, \"TBD\"), \"\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"^ Identified Standard\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"References\"), \": Provide the requirement source (stated or derived).\\nSpecify the paragraph, section, line, etc. \", mdx(\"u\", null, \"The following is part of\\nthe example and references could be out of date.\")), mdx(\"p\", null, \"Derived from \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo. 3 Apr 18, Procedures for Operational Test and\\nEvaluation (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E) of Cybersecurity in Acquisition Programs; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Director of Operational Test and Evaluation\"\n }, \"DOT&E\"), \" Memo,\\n27 Jul 16, Cybersecurity Operational Test and Evaluation Priorities and\\nImprovements; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Cybersecurity \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test and Evaluation\"\n }, \"T&E\"), \" Guidebook, Version 2.0 Change 1, 10\\nFeb 2020; \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Cyber Test Guide, XX Dec 2020\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Scope\"), \": This measure evaluates the risk to JOD\\u2019s ability to enable\\nsecure and survivable communications in a contested cyberspace\\nenvironment. The risk must be \\u201Clow\\u201D. The test team will determine the\\nrisk rating by evaluation the likelihood of an adversary exploiting\\nvulnerabilities and the resulting impact to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Enhanced Polar System\"\n }, \"EPS\"), \"\\u2019 ability to enable\\nsecure and survivable communications in a contested cyberspace\\nenvironment.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Methodology\"), \": The test team mapped the mission of JOD to mission\\nessential functions and the components which support their operation.\\nThis nodal analysis will allow the test team to identify critical nodes\\nwithin JOD. Using this information the test team will commission the\\n346TS to conduct a cooperative vulnerability and penetration assessment\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \") before integrated test activities (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \"). The test team will\\ncommission the 177 IAS, an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Security Agency\"\n }, \"NSA\"), \" certified cyber red team, to conduct an\\nadversarial assessment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \") during \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Information Technology OR Integrated Testing\"\n }, \"IT\"), \" and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \".\"), mdx(\"p\", null, \"The test team will evaluate the risk of cyber-effects to JOD\\u2019s ability\\nto enable secure and survivable communications in a contested cyberspace\\nenvironment as follows:\"), mdx(\"p\", null, \"Table C-13. Example of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Risk Based Cyber-Related Measure\\nWorksheet\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Likelihood\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }))), mdx(\"tbody\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"1\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Near Certain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n })), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Impact\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"4\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Catastrophic\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High Risk\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"3\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Major\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"2\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Moderate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"1\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low\")))), mdx(\"p\", null, \"Table C-14\"), mdx(\"table\", null, mdx(\"thead\", {\n parentName: \"table\"\n }, mdx(\"tr\", {\n parentName: \"thead\"\n }, mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Level\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Likelihood\"), mdx(\"th\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Description\"))), 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 }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Little to no capability for adversary to exploit\")), 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 }, \"Low\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"High cost for adversary to exploit\")), 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 }, \"Medium\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Medium cost for adversary to exploit\")), 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 }, \"High\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Low cost for adversary to exploit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"5\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Near Certain\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Little to no cost for adversary to exploit\")), mdx(\"tr\", {\n parentName: \"tbody\"\n }, mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Level\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Impact\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Description\")), 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 }, \"Negligible\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Little to no mission degradation\")), 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 }, \"Moderate\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Partial mission degradation\")), 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 }, \"Major\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Critical mission degradation\")), 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 }, \"Catastrophic\"), mdx(\"td\", {\n parentName: \"tr\",\n \"align\": null\n }, \"Complete mission failure\")))), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Test Design\"), \": Uses overarching \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" test design.\"), mdx(\"p\", null, mdx(\"strong\", {\n parentName: \"p\"\n }, \"Data and Analysis\"), \": Data will consist of results from the Mission\\nRisk Assessment Process for Cyber (MRAP-C), the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Cooperative Vulnerability and Penetration Assessment\"\n }, \"CVPA\"), \", and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \". During\\ntest execution, the test team will also collect performance data for all\\nmeasures within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \".\"), mdx(\"p\", null, \"The test team will record all data on test team logs and will store all\\nresults in the appropriately classified test team \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E database. Where\\nunable to collect quantitative data, the test team will collect end user\\nand \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" qualitative data. The test team will collect data according to\\neach measure within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1. The test team will note periods of time when\\ncyber-effects were generated by the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \" team. After test execution, the\\ntest team will evaluate the impacts of disruptive and non-disruptive\\ncyber-effects to each measure within \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Critical Operational Issue\"\n }, \"COI\"), \" 1. The test team will consult\\nwith \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2 to determine the likelihood of the demonstrated and\\nspeculated cyber-effects from the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adversarial Assessment\"\n }, \"AA\"), \". The test team will then provide a\\nrisk rating of each effect. Using each risk rating as input, the test\\nteam will then provide the overall risk rating to this measure.\"), mdx(\"p\", null, \"[1]\", \" Cyber test and evaluation is a rapidly evolving concept. Be sure to\\nreference the most current guidance as it may change more frequently\\nthan this \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Measures Guide.\"), mdx(\"p\", null, \"[2]\", \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Department of Defense\"\n }, \"DoD\"), \" Cybersecurity Test and Evaluation Guidebook, Version 2.0, Change\\n1, 10 Feb 20\"), mdx(\"p\", null, \"[3]\", \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"National Institute of Standards and Technology\"\n }, \"NIST\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Security Plan OR Special Publication\"\n }, \"SP\"), \" 800-12, \\u201CAn Introduction to Information Security,\\u201D Rev. 1,\\nJun 17\"), mdx(\"p\", null, \"[4]\", \" System Survivability Key Performance Parameter (SS \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Key Performance Parameter\"\n }, \"KPP\"), \") Pillars are\\ndefined in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Chiefs of Staff\"\n }, \"JCS\"), \" Cyber Survivability Endorsement Implementation Guide,\\nVersion 1.01\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#measures-overview","title":"Measures Overview"},{"url":"#composite-measures","title":"Composite Measures"}]},"parent":{"__typename":"File","relativePath":"measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES.md"},"frontmatter":{"metaTitle":"APPENDIX C CYBER-RELATED MEASURES ","metaDescription":"APPENDIX C CYBER-RELATED MEASURES "}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"a7a397bc-d207-56b9-819e-804a37a205d4"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/measures_guide/page-data.json b/sites/oteguide/page-data/measures_guide/page-data.json new file mode 100644 index 00000000..95b4612e --- /dev/null +++ b/sites/oteguide/page-data/measures_guide/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/measures_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"ed07c865-1b51-5fec-92f3-4bddd036c10a","title":"Measures Guide","slug":"/measures_guide"},"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\": \"Measures Guide\",\n \"metaTitle\": \"Measures Guide\",\n \"metaDescription\": \"Measures Guide\"\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, \"March 2021\"), mdx(\"p\", null, \"Last Updated/Reviewed: 25 March 2021\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-2/9\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{},"parent":{"__typename":"File","relativePath":"measures_guide.md"},"frontmatter":{"metaTitle":"Measures Guide","metaDescription":"Measures Guide"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"ed07c865-1b51-5fec-92f3-4bddd036c10a"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/safety_risk_mgmt_guide/page-data.json b/sites/oteguide/page-data/safety_risk_mgmt_guide/page-data.json new file mode 100644 index 00000000..15065434 --- /dev/null +++ b/sites/oteguide/page-data/safety_risk_mgmt_guide/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/safety_risk_mgmt_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"0ef4bab1-3850-5e1e-8575-81d23556f4f8","title":"Safety Risk Management Guide","slug":"/safety_risk_mgmt_guide"},"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\": \"Safety Risk Management Guide\",\n \"metaTitle\": \"Safety Risk Management Guide\",\n \"metaDescription\": \"Safety Risk Management Guide\"\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, \"Last Updated/Reviewed: 08 December 2020\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \"\"), mdx(\"h1\", null, \"ENVIRONMENT, SAFETY AND OCCUPATIONAL HEALTH\"), mdx(\"p\", null, \"The three basic principles of environment, safety, and occupational\\nhealth (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \") are to sustain readiness, leverage resources, and be a\\ngood neighbor. The test director (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \") is responsible for providing a\\nsafe and healthy workplace during test execution, enhancing mission\\naccomplishment, preserving resources and minimizing risks--on and off\\nthe installation or public lands. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Safety (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \") supports these\\nresponsibilities with subject matter experts (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \") assigned to the\\ncore/test teams. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" will assist the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and the team in\\nnavigating \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" statutory compliance, the database/tools, planning\\nprocess, health and safety plan development, Integrated Safety Review\\nBoards (ISRB), and ultimately the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" Certification Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \") (if\\nrequired) for each test activity.\"), mdx(\"h1\", null, \"Safety Database and Tools\"), mdx(\"p\", null, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" uses a safety database as the starting point for every \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\nactivity and the ticket to a safe, compliant activity. It is comprised\\nof a collection of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" tools that includes standard work templates,\\nsystems safety analysis databases, \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"test team exposure identification\\ntools\"), \" , Integrated Safety Reviews, and the formal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" certification\\nprocess, which ultimately results in an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" certification for dedicated\\noperational test. The system aggregates data through the life of a\\nprogram, maintains individual records of each test activity, certifies\\nsafety and environmental planning, and supports the \\\"Readiness for\\nDedicated Operational Test\\\" decision. Upon receipt of an \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Tasking\\nOrder or notification of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" experiment participation, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" will initiate a new database entry for the core (or experimentation)\\nteam to capture known technology and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" factors and develop an initial\\ntechnology risk assessment. Then, as the test team develops each\\noperational test concept, \", mdx(\"strong\", {\n parentName: \"p\"\n }, \"the safety office \", mdx(\"abbr\", {\n parentName: \"strong\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" will initiate an\\nactivity-specific integrated safety review for each test activity\"), \" .\\nThe process will be available to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" and has the capability to branch\\nout to safety SMEs and other test experts as required to accomplish a\\nthorough analysis and develop the identified hazard list with\\nmitigations. Early initiation of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" database is critical to allow\\nadequate time to request environmental analysis and scope test risks.\\nSince complex environmental analyses can take years to complete, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"\\nshould consult with the safety office \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" early in to determine whether\\na \\\"long pole\\\" may exist. The system connects the team and \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" SMEs to\\ndevelop risk factors, assess installation environmental documentation,\\nand determine the test activity risk level. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" database facilitates all\\nof these phases and builds the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \".\"), mdx(\"h1\", null, \"Planning and Review Process\"), 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\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" assigns safety SMEs to advise and consult on \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \"-related\\nmatters with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", Detachment (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"), and Experimentation Office (EX)\\ntest team's designated safety point-of-contact (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \"), and attends\\nprogram/experiment \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" meetings. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" leads the initial\\ntechnological safety review in pre-planning phases and guides the test\\nteams during site safety and environmental compliance planning for test\\nexecution. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" review composition is tailorable. Consider including\\nthe program office, sponsor, \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test team safety \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \",\\nand others as needed. Safety-related concerns are normally identified\\nduring \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" planning, combined \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Developmental Test\"\n }, \"DT\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \" events, experimentation activities,\\nand at system safety working group meetings or system safety design\\nreview meetings. Identified hazards must be controlled or mitigated to\\nacceptable levels before start of test, which is the purpose of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \"\\ndatabase.\"), mdx(\"h1\", null, \"Health and Safety Plan\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" uses the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" database to build the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" interactively with the\\ntest team. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" covers environmental and occupational health and\\nsafety issues while documenting compliance with laws and regulations. It\\nis the key document evaluated by the ISRB, or \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" for Dedicated\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"'s (or onsite responsible person's) daily\\npretest/deployment briefing guide. When used, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" assures statutory\\ncompliance and produces a solid foundation for test site risk management\\nconsiderations.\"), mdx(\"p\", null, \"Hazards are identified in the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \", each with an initial risk level (low,\\nmedium, high, and extremely high) that is controlled or mitigated, as\\nwell as feasible to reduce the risk. Table 1 is an aid tailored from\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Pamphlet\"\n }, \"AFPAM\"), \" 90-803, \", 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,\"), \" used to\\nassess \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" risk levels for each type of hazard.\"), mdx(\"p\", null, \"Table 1. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" Mission Impact Matrix\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"th\", null, \"Mishap Risk Index\"), mdx(\"th\", null, \"AFOTEC Mission Impact\"), mdx(\"th\", null), mdx(\"th\", null), mdx(\"th\", null))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Severity Probability\"), mdx(\"td\", null, \"I-Catastrophic\"), mdx(\"td\", null, \"II-Critical\"), mdx(\"td\", null, \"III-Moderate\"), mdx(\"td\", null, \"IV-Negligible\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"A \\u2013 Frequent\"), mdx(\"td\", null, \"Severe\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"B \\u2013 Likely\"), mdx(\"td\", null), mdx(\"td\", null, \"Substantial\"), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"C \\u2013 Occasional\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"Minimal\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"D \\u2013 Seldom\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null, \"No impact\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"E \\u2013 Unlikely\"), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Risk Assessment Value (AFPAM90-803)\")), mdx(\"td\", null, mdx(\"strong\", null, \"Technology (Mil Std 882E)\")), mdx(\"td\", null, mdx(\"strong\", null, \"Impact to Test Activities\")), mdx(\"td\", null, mdx(\"strong\", null, \"ESOH Impact Acceptance Level\")), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Extremely High\"), mdx(\"td\", null, \"High\"), mdx(\"td\", null, \"Severe\"), mdx(\"td\", null, \"AFOTEC/CC\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"High\"), mdx(\"td\", null, \"Serious\"), mdx(\"td\", null, \"Substantial\"), mdx(\"td\", null, \"Det/EX/CC\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, \"Medium\"), mdx(\"td\", null, \"Medium\"), mdx(\"td\", null, \"Minimal\"), mdx(\"td\", null, \"Det/EX/DO\"), mdx(\"td\", null)), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, \"Low\"), mdx(\"td\", null, \"Low\"), mdx(\"td\", null, \"No\"), mdx(\"td\", null, \"Det/EX/TD\"), mdx(\"td\", null)))), mdx(\"p\", null, \"This is a subjective process and should not be confused with the\\ndeficiency report (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Deficiency Report\"\n }, \"DR\"), \") or system safety processes. Residual risk is the\\nremaining mishap risk that exists after control measures are in place.\\nThe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" finally considers all residual risks to assess an overall risk\\nlevel for \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" mission impact to test activities, which in turn\\ndetermines the risk acceptance authority. The appropriate \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" mission\\nimpact risk acceptance decision authority for low risk---no \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" impact\\nto test activities is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/EX \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"; for medium risk---minimal \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \"\\nimpact to test activities is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/EX DO; and for high\\nrisk---substantial \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" impact to test activities is the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" or EX\\nDirector. 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\"), \" is the risk acceptance authority for extremely\\nhigh risk---severe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" impact to test activities. The decision\\nauthority can accept the risk and proceed, or elevate (or consult other\\ngeneral officers prior to making a risk decision in the case of 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\"), \") the decision to the next higher authority. When an identified\\nhazard's control measures cannot be implemented, the risk level reverts\\nback to the initial (higher) risk, which in turn may require elevating\\nthe risk decision authority level before proceeding with the activity.\"), mdx(\"h1\", null, \"Integrated Safety Review Board\"), mdx(\"p\", null, \"The Integrated Safety Review Board (ISRB) assembles to consider all\\nknown \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" risk factors prior to all operational test activities with\\nthe exception of formal Dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E. The ISRB reviews all \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" data\\nand analysis known at the time. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" works with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" and\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/EX test team's safety \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" to prepare and coordinate the ISRB,\\nwhich the safety office chairs. The ISRB may be conducted in person, or\\nvia teleconference or video teleconference. The board structure is\\ntailorable to the programmatic or experiment situation. The ISRB focuses\\ntest team personnel exposure, and the early (preliminary) safety hazards\\nof the operational test activity. The board uses an Independent Safety\\nReview Exposure Identification Tool (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Early Influence Team\"\n }, \"EIT\"), \") to determine operational test\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" hazards likely to be present during those activities. Examples of\\nthese activities are: Contractor or Development Test Observations,\\nOperational Assessments (outside the purview of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63-119),\\nDemonstrations, Experiments or any other similar test activities.\"), mdx(\"h1\", null, \"Environment, Safety and Occupational Health Certification Board\"), mdx(\"p\", null, \"The Environment, Safety and Occupational Health Certification Board\\n(\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \") assembles to consider all outstanding \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" risk factors, to\\nformalize the risk acceptance decision authority, and to certify the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" analyses in a certification memorandum for Dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" follows direction outlined in \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63-119, \", mdx(\"em\", {\n parentName: \"p\"\n }, \"Certification of\\nSystem Readiness for Dedicated Operational Testing\"), \" , Atch 23,\\n\\\"Integrated Technical, Health, and Safety Reviews.\\\" The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" is\\naccomplished prior to dedicated \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Initial Operational Test\"\n }, \"IOT\"), \"&E. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \" works with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \"\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \" and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \" test team's safety \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" to prepare and coordinate the\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \", which the safety office chairs. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" may be conducted in\\nperson, or via teleconference or video teleconference. The board\\nstructure is tailorable to the programmatic situation. For example, for\\nan \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \"-controversial program, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" could demand a formal meeting\\nwith multiple attendees; whereas, for a well-structured and\\nwell-documented program with significant but acknowledged risks, a\\nteleconference between the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \", test team safety \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \", \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Safety OR Support Equipment OR Systems Engineering\"\n }, \"SE\"), \" \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Subject Matter Expert\"\n }, \"SME\"), \",\\nDirector of Safety, and the risk acceptance authority could suffice. The\\n\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" focuses on the safety of test, technology, and environment as\\nthey pertain to the scope of the test activities. The Board pays\\nparticular attention to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Health and Safety Plan\"\n }, \"HSP\"), \" as the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Director OR Technical Director OR Technology Development OR Technology Director\"\n }, \"TD\"), \"'s primary \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" field source\\nfor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" hazards and mitigations, and emergency and mishap\\nnotifications. Additional sources include: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Manual\"\n }, \"AFMAN\"), \" 63-119, ITHSR,\\nAttachment 23, criteria; safety DRs; environmental considerations;\\ndeployment issues; system safety deficiencies related to the system\\nunder test; occupational health; infrastructure support requirements;\\nand others.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" gives the test activity an overall risk assessment based on\\nidentified hazards and mitigations applied. Then, the Board considers\\nthe potential impact of those risks on test activities. Table 2 outlines\\nthe different levels of \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \"-related hazard risks and their impact to\\ntest activities, and establishes the appropriate risk decision\\nauthority.\"), mdx(\"p\", null, \"Table 2. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health\"\n }, \"ESOH\"), \" Mission Impact Risk Levels and Acceptance\"), mdx(\"table\", null, mdx(\"thead\", null, mdx(\"tr\", {\n className: \"header\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"No Mission Impact:\"), mdx(\"br\", null), \"No ESOH hazards have been identified that impact test activities. Known hazards identified have been adequately controlled (mitigated) to acceptable levels. The potential ESOH-related capability impacts are negligible. The Test Director or higher is the risk decision authority to accept the hazard controls.\"))), mdx(\"tbody\", null, mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Minimal Mission Impact:\"), mdx(\"br\", null), \"Some ESOH hazards have been identified with minimal impact on test activities. Known hazards have been adequately identified and controlled (mitigated) to an acceptable level. Some conditions will not be resolved prior to the test but sufficient mitigation measures are in place to reduce the operational objective limitations. The Detachment Director of Operations or higher is the appropriate level to accept the limitations.\")), mdx(\"tr\", {\n className: \"even\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Substantial Mission Impact:\"), mdx(\"br\", null), \"Some ESOH hazards have been identified with substantial impact on test activities. Known hazards have been adequately identified and the majority were resolved or mitigated. ESOH-related operational objective impacts were mitigated to acceptable levels. Some will not be resolved by test completion that may limit mission capability and may potentially influence affected test results. The Detachment Commander or higher is the appropriate level to accept and manage the limitations.\")), mdx(\"tr\", {\n className: \"odd\"\n }, mdx(\"td\", null, mdx(\"strong\", null, \"Severe Mission Impact:\"), mdx(\"br\", null), \"There are ESOH shortfalls identified with severe impact on test activities. The majority of known hazards have been identified and controlled (mitigated) to an acceptable level. However, some ESOH-related operational objectives have the potential to limit test capabilities and will not be resolved in time. If it is deemed necessary to proceed with the test considering these significant limitations, it may be appropriate that Senior (General Officer) level external involvement occur along with the AFOTEC Commander accepting responsibility to proceed with test execution.\")))), mdx(\"p\", null, \"The Director of Safety assigns the final risk in the form of a\\ncertification memorandum (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" Memo) and signs the memo. The\\nappropriate risk decision authority for the test activity will accept\\nthe risk and endorse the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" Memo. After risk acceptance, a copy of\\nthe \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" Memo will be forwarded as \\\"info\\\" to the next higher decision\\nauthority as level of risk dictates (i.e., \", 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\"), \" to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/DO to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Detachment\"\n }, \"Det\"), \"/\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Commander OR Critical Component\"\n }, \"CC\"), \" to\\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\"), \"). Coordination and approval of the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Environment, Safety, and Occupational Health Certification Board\"\n }, \"ESOHCB\"), \" Memo will be\\naccomplished prior to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \"&E activities.\"));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#environment-safety-and-occupational-health","title":"ENVIRONMENT, SAFETY AND OCCUPATIONAL HEALTH"},{"url":"#safety-database-and-tools","title":"Safety Database and Tools"},{"url":"#planning-and-review-process","title":"Planning and Review Process"},{"url":"#health-and-safety-plan","title":"Health and Safety Plan"},{"url":"#integrated-safety-review-board","title":"Integrated Safety Review Board"},{"url":"#environment-safety-and-occupational-health-certification-board","title":"Environment, Safety and Occupational Health Certification Board"}]},"parent":{"__typename":"File","relativePath":"safety_risk_mgmt_guide.md"},"frontmatter":{"metaTitle":"Safety Risk Management Guide","metaDescription":"Safety Risk Management Guide"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"0ef4bab1-3850-5e1e-8575-81d23556f4f8"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/sq/d/1685914912.json b/sites/oteguide/page-data/sq/d/1685914912.json index 74768e8e..a4cf2853 100644 --- a/sites/oteguide/page-data/sq/d/1685914912.json +++ b/sites/oteguide/page-data/sq/d/1685914912.json @@ -1 +1 @@ -{"data":{"site":{"siteMetadata":{"headerTitle":"AFOTEC OT&E Guide","helpUrl":"","tweetText":"","logo":{"link":"https://oteguide.il2.dsop.io/","image":""},"headerLinks":[{"link":"","text":""}]}}}} \ No newline at end of file +{"data":{"site":{"siteMetadata":{"headerTitle":"AFOTEC OT&E Guide","helpUrl":"","tweetText":"","logo":{"link":"https://oteguide.il2.dso.mil/","image":""},"headerLinks":[{"link":"","text":""}]}}}} \ No newline at end of file diff --git a/sites/oteguide/page-data/sq/d/1928916242.json b/sites/oteguide/page-data/sq/d/1928916242.json index 4bd8bee2..bd111238 100644 --- a/sites/oteguide/page-data/sq/d/1928916242.json +++ b/sites/oteguide/page-data/sq/d/1928916242.json @@ -1 +1 @@ -{"data":{"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/fn_guides"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/glossary"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/"},"tableOfContents":{"items":[{"url":"#about","title":"About"},{"url":"#app-notes","title":"App Notes"},{"url":"#credits","title":"Credits","items":[{"url":"#the-ote-guide-team-is","title":"The OT&E Guide Team is:"},{"url":"#the-app-team-is","title":"The App Team is:"}]}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes"},"tableOfContents":{"items":[{"url":"#afotecs-role-in-fielding-combat-capability","title":"AFOTECs Role in Fielding Combat Capability"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision"},"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"}]}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities"},"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"}]}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit"},"tableOfContents":{"items":[{"url":"#exit-criteria","title":"Exit Criteria"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking"},"tableOfContents":{"items":[{"url":"#initial-tasking-order","title":"Initial Tasking Order"},{"url":"#tasking-order-update","title":"Tasking Order Update"},{"url":"#program-transfer","title":"Program Transfer"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct"},"tableOfContents":{"items":[{"url":"#define-the-what","title":"Define the \"What\"","items":[{"url":"#system-under-test","title":"System Under Test"},{"url":"#measures","title":"Measures"},{"url":"#criteria-and-thresholds","title":"Criteria and Thresholds"},{"url":"#data-and-data-elements","title":"Data and Data Elements"},{"url":"#effectiveness-and-suitability","title":"Effectiveness and Suitability"},{"url":"#coi-operations-measures-data-hierarchy","title":"COI-Operations-Measures-Data Hierarchy"},{"url":"#conditions","title":"Conditions"},{"url":"#operational-capabilities","title":"Operational Capabilities"}]},{"url":"#test-design","title":"Test Design","items":[{"url":"#test-design-goal","title":"Test Design Goal"},{"url":"#test-designs","title":"Test Designs"}]},{"url":"#test-execution","title":"Test Execution","items":[{"url":"#test-capabilities","title":"Test Capabilities"},{"url":"#verification-validation-and-accreditation","title":"Verification, Validation, and Accreditation"},{"url":"#data-management","title":"Data Management"},{"url":"#detailed-test-procedures","title":"Detailed Test Procedures"},{"url":"#limitations","title":"Limitations"},{"url":"#resourcing-test-events","title":"Resourcing Test Events"},{"url":"#technical-reviews","title":"Technical Reviews"},{"url":"#test-plans","title":"Test Plans"},{"url":"#administrative-considerations","title":"Administrative Considerations"},{"url":"#executing-the-test","title":"Executing the Test"}]},{"url":"#analysis-and-evaluation","title":"Analysis and Evaluation","items":[{"url":"#inspection","title":"Inspection"},{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#effectiveness-and-suitability-1","title":"Effectiveness and Suitability"},{"url":"#reporting-ratings","title":"Reporting Ratings"},{"url":"#deficiency-reporting","title":"Deficiency Reporting"},{"url":"#exit-criteria-assessment","title":"Exit Criteria Assessment"}]},{"url":"#conclusions-and-documenting","title":"Conclusions and Documenting"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec"},"tableOfContents":{"items":[{"url":"#directorate-roles-and-responsibilities","title":"Directorate Roles and Responsibilities"},{"url":"#signature-and-approval","title":"Signature and Approval"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback"},"tableOfContents":{"items":[{"url":"#handling-information-requests","title":"Handling Information Requests"},{"url":"#marking-and-protecting-data","title":"Marking and Protecting Data"},{"url":"#distribution-statements","title":"Distribution Statements"},{"url":"#test-program-case-file","title":"Test Program Case File"},{"url":"#impact-of-system-modifications","title":"Impact of System Modifications"},{"url":"#visual-information-documentation","title":"Visual Information Documentation"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap"},"tableOfContents":{"items":[{"url":"#2-letter-coord-of-air-force-operation-test-and-evaluation-center-produced-documentsbriefings-8-work-days","title":"2 Letter Coord of Air Force Operation Test and Evaluation Center-Produced Documents/Briefings (8 Work Days)"},{"url":"#commanderexecutive-director-briefing-request","title":"Commander/Executive Director Briefing Request"},{"url":"#command-section-coord-process-maximum-of-7-work-days","title":"Command Section Coord Process (Maximum of 7 Work Days)"},{"url":"#other-product-review-processes","title":"Other Product Review Processes"},{"url":"#things-to-consider-when-producing-documents-for-coordinationreview","title":"Things to Consider when Producing Documents for Coordination/Review","items":[{"url":"#drafting-plansreports-and-briefings","title":"Drafting Plans/Reports and Briefings:"},{"url":"#actionable-comments","title":"Actionable Comments"},{"url":"#meeting-external-suspenses","title":"Meeting External Suspenses"}]},{"url":"#accreditation-plansreports","title":"Accreditation Plans/Reports"},{"url":"#joint-reliability-maintainability-evaluation-team-charters","title":"Joint Reliability, Maintainability Evaluation Team Charters"}]}}},{"node":{"fields":{"slug":"/fn_guides/accreditation_guide"},"tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#test-capability-accreditation","title":"Test Capability Accreditation"},{"url":"#the-use-of-modeling-and-simulation","title":"The Use of Modeling and Simulation"},{"url":"#verification-validation-and-accreditation-definitions","title":"Verification, Validation and Accreditation Definitions"},{"url":"#acquisition-implications-of-verification-validation-and-accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"},{"url":"#accreditation-concepts","title":"Accreditation Concepts"},{"url":"#risk-matrix-example","title":"Risk Matrix: Example"},{"url":"#previous-accreditation","title":"Previous Accreditation"},{"url":"#accreditation-process","title":"Accreditation Process"},{"url":"#test-capability-accreditation-concept","title":"Test Capability Accreditation Concept"},{"url":"#accreditation-plan-and-report-format","title":"Accreditation Plan and Report Format"},{"url":"#accreditation-references-and-resources","title":"Accreditation References and Resources"},{"url":"#air-force-agency-for-modeling-and-simulation","title":"Air Force Agency for Modeling and Simulation"},{"url":"#modeling-and-simulation-coordination-office","title":"Modeling and Simulation Coordination Office"},{"url":"#best-practices","title":"Best Practices"},{"url":"#summary","title":"Summary"},{"url":"#references-and-resources","title":"References and Resources"},{"url":"#governance","title":"Governance"},{"url":"#points-of-contact","title":"Points of Contact"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources"},"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"}]}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide"},"tableOfContents":{"items":[{"url":"#introduction-and-intent","title":"INTRODUCTION AND INTENT"},{"url":"#vocabulary-of-lessons-learned","title":"Vocabulary of Lessons Learned"},{"url":"#policy-guidance","title":"Policy Guidance"},{"url":"#process","title":"PROCESS"},{"url":"#milestoneevent-triggers","title":"Milestone/Event Triggers"},{"url":"#observations-review","title":"Observations Review"},{"url":"#dissemination","title":"Dissemination"},{"url":"#lessons-learned-resolution","title":"Lessons Learned (Resolution)"},{"url":"#conclusion","title":"CONCLUSION"},{"url":"#observation-sheet","title":"OBSERVATION SHEET"},{"url":"#interview-sheet","title":"INTERVIEW SHEET"}]}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide"},"tableOfContents":{"items":[{"url":"#purpose","title":"PURPOSE"},{"url":"#executive-summary-body-and-appendices","title":"Executive Summary, Body, and Appendices"},{"url":"#consistency-is-key","title":"Consistency is Key"},{"url":"#one-voice","title":"One Voice"},{"url":"#templates","title":"Templates"},{"url":"#microsoft-word-options","title":"Microsoft Word Options","items":[{"url":"#display","title":"Display:"},{"url":"#proofing","title":"Proofing:"},{"url":"#advanced","title":"Advanced:"}]},{"url":"#focus-areas","title":"Focus Areas"},{"url":"#styles","title":"Styles"},{"url":"#acronyms","title":"Acronyms"},{"url":"#commas","title":"Commas"},{"url":"#next-page-and-page-breaks","title":"\"Next Page\" and \"Page\" Breaks"},{"url":"#headers-and-footers","title":"Headers and Footers"},{"url":"#page-numbering","title":"Page Numbering"},{"url":"#blank-pages","title":"Blank Pages"},{"url":"#capitalization","title":"Capitalization"},{"url":"#citing-air-force-or-other-military-bases","title":"Citing Air Force (or Other Military) Bases"},{"url":"#vertical-lists","title":"Vertical Lists"},{"url":"#numbering-tables-and-figures","title":"Numbering Tables and Figures"},{"url":"#tables","title":"Tables"},{"url":"#figures","title":"Figures"},{"url":"#passive-voice","title":"Passive Voice"},{"url":"#copyrightstrademarks","title":"Copyrights/Trademarks"},{"url":"#wordiness","title":"Wordiness"},{"url":"#hyphens-en-dashes-and-em-dashes","title":"Hyphens, En Dashes, and Em Dashes"},{"url":"#apostrophes","title":"Apostrophes"},{"url":"#choppy-sentences","title":"Choppy Sentences"},{"url":"#numbers","title":"Numbers"},{"url":"#dates","title":"Dates"},{"url":"#abbreviations","title":"Abbreviations"},{"url":"#terms","title":"Terms"},{"url":"#symbols-and-units-of-measure","title":"Symbols and Units of Measure"},{"url":"#verb-tenses","title":"Verb Tenses"},{"url":"#embedded-files","title":"Embedded Files"},{"url":"#converting-pictures","title":"Converting Pictures"},{"url":"#referencesdocumentation","title":"References/Documentation"},{"url":"#patches","title":"Patches"},{"url":"#classification-markings","title":"Classification Markings"},{"url":"#distribution-list","title":"Distribution List"},{"url":"#sf298-report-documentation-page","title":"SF298 Report Documentation Page"},{"url":"#spell-check","title":"Spell Check"},{"url":"#configuration-control","title":"Configuration Control"},{"url":"#table-of-contents","title":"Table of Contents"},{"url":"#standardization-checklist","title":"Standardization Checklist"}]}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide"},"tableOfContents":{"items":[{"url":"#strategy-planning-and-programming-process","title":"STRATEGY, PLANNING, AND PROGRAMMING PROCESS"}]}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide"},"tableOfContents":{"items":[{"url":"#environment-safety-and-occupational-health","title":"ENVIRONMENT, SAFETY AND OCCUPATIONAL HEALTH"},{"url":"#safety-database-and-tools","title":"Safety Database and Tools"},{"url":"#planning-and-review-process","title":"Planning and Review Process"},{"url":"#health-and-safety-plan","title":"Health and Safety Plan"},{"url":"#integrated-safety-review-board","title":"Integrated Safety Review Board"},{"url":"#environment-safety-and-occupational-health-certification-board","title":"Environment, Safety and Occupational Health Certification Board"}]}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide"},"tableOfContents":{"items":[{"url":"#purpose","title":"PURPOSE","items":[{"url":"#definition","title":"Definition"},{"url":"#support-goals","title":"Support Goals"}]},{"url":"#test-range-and-facility-capabilities","title":"TEST RANGE AND FACILITY CAPABILITIES"},{"url":"#existing-test-capability-identification","title":"EXISTING TEST CAPABILITY IDENTIFICATION"},{"url":"#test-capability-gap-identification","title":"TEST CAPABILITY GAP IDENTIFICATION"},{"url":"#test-capability-gap-support-and-reporting","title":"TEST CAPABILITY GAP SUPPORT AND REPORTING"},{"url":"#munitions-management","title":"MUNITIONS MANAGEMENT"},{"url":"#test-resource-plan-requirements-verification-and-feedback","title":"TEST RESOURCE PLAN REQUIREMENTS VERIFICATION AND FEEDBACK"}]}}},{"node":{"fields":{"slug":"/acronyms"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide"},"tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#the-operational-test-and-evaluation-construct","title":"The Operational Test and Evaluation Construct"},{"url":"#operational-sufficiency-and-technical-adequacy","title":"Operational Sufficiency and Technical Adequacy"},{"url":"#operational-test-and-evaluation-test-activity-cycles","title":"Operational Test and Evaluation Test Activity Cycles"},{"url":"#using-a-core-team-approach","title":"Using a Core Team Approach."},{"url":"#construct-development-meetings","title":"Construct Development Meetings"},{"url":"#battlespace-development","title":"Battlespace Development","items":[{"url":"#researching-the-capability-or-system-being-acquired","title":"Researching the Capability or System Being Acquired"},{"url":"#battlespace-depiction","title":"Battlespace Depiction","items":[{"url":"#the-evaluation-view","title":"The Evaluation View"},{"url":"#the-evaluation-view-1","title":"The Evaluation View 1"},{"url":"#the-evaluation-view-2","title":"The Evaluation View 2"},{"url":"#capability-requirements-mapping","title":"Capability Requirements Mapping"},{"url":"#mission-statement","title":"Mission Statement"},{"url":"#critical-operational-issues","title":"Critical Operational Issues"},{"url":"#operations","title":"Operations"}]},{"url":"#operational-employment-and-support-conditions","title":"Operational Employment and Support Conditions","items":[{"url":"#measures-of-effectiveness","title":"Measures of Effectiveness"},{"url":"#operational-conditions-factors-and-levels","title":"Operational Conditions (Factors and Levels)"},{"url":"#identify-factors-and-levels","title":"Identify Factors and Levels."},{"url":"#prioritizing-factors","title":"Prioritizing Factors"}]},{"url":"#operational-capabilities-oc","title":"Operational Capabilities (OC)"}]},{"url":"#evaluation-summary-chart","title":"Evaluation Summary Chart","items":[{"url":"#mission-statement-in-an-evaluation-summary-chart","title":"Mission Statement in an Evaluation Summary Chart"},{"url":"#critical-operational-issues-in-an-evaluation-summary-chart","title":"Critical Operational Issues in an Evaluation Summary Chart"},{"url":"#mission-effects-in-an-evaluation-summary-chart","title":"Mission Effects in an Evaluation Summary Chart"},{"url":"#operational-capability-requirements-in-an-evaluation-summary-chart","title":"Operational Capability Requirements in an Evaluation Summary Chart"}]},{"url":"#test-design","title":"Test Design","items":[{"url":"#test-design-goals","title":"Test Design Goals"},{"url":"#types-of-test-design","title":"Types of Test Design"},{"url":"#factor-management","title":"Factor Management."},{"url":"#unconstrained-and-constrained-events","title":"Unconstrained and Constrained events"},{"url":"#statistical-measures-of-merit","title":"Statistical Measures of Merit"},{"url":"#test-events","title":"Test Events"},{"url":"#test-design-validations","title":"Test Design Validations"}]},{"url":"#measures-development","title":"Measures Development"},{"url":"#test-execution-planning","title":"Test Execution Planning","items":[{"url":"#test-methodology","title":"Test Methodology"},{"url":"#test-scenarios","title":"Test Scenarios"},{"url":"#test-capability-needs-and-shortfalls","title":"Test Capability Needs and Shortfalls","items":[{"url":"#time-phased-investment-document","title":"Time-Phased Investment Document"},{"url":"#determining-range-requirements","title":"Determining Range Requirements"},{"url":"#range-requirement-identification","title":"Range Requirement Identification"},{"url":"#range-selection-considerations","title":"Range Selection Considerations"},{"url":"#national-cyber-range-considerations","title":"National Cyber Range Considerations"},{"url":"#test-targets","title":"Test Targets"},{"url":"#range-safety-considerations","title":"Range Safety Considerations"},{"url":"#range-instrumentation-considerations","title":"Range Instrumentation Considerations"},{"url":"#range-data-processing-considerations","title":"Range Data Processing Considerations"},{"url":"#test-article-instrumentation","title":"Test Article Instrumentation"},{"url":"#program-introduction-document-release-authority","title":"Program Introduction Document Release Authority"}]},{"url":"#the-use-of-modeling-and-simulation","title":"The Use of Modeling and Simulation"},{"url":"#test-capability-accreditation","title":"Test Capability Accreditation"},{"url":"#test-constraints-and-limitations","title":"Test Constraints and Limitations"},{"url":"#basis-of-estimate-for-test-resources","title":"Basis of Estimate for Test Resources"},{"url":"#initial-resource-estimates","title":"Initial Resource Estimates"}]},{"url":"#documenting-the-operational-test-and-evaluation-construct","title":"Documenting the Operational Test and Evaluation Construct"}]}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide"},"tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#test-activity-sequence","title":"TEST ACTIVITY SEQUENCE"},{"url":"#analysis-evaluation-and-reporting","title":"ANALYSIS, EVALUATION, AND REPORTING","items":[{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#reporting","title":"Reporting"}]},{"url":"#structure-of-an-evaluation","title":"STRUCTURE OF AN EVALUATION","items":[{"url":"#ote-evaluation-structure","title":"OT&E Evaluation Structure"}]},{"url":"#rating-tenetsprinciples","title":"RATING TENETS/PRINCIPLES","items":[{"url":"#rating","title":"Rating","items":[{"url":"#terminology","title":"Terminology"},{"url":"#report","title":"Report"}]},{"url":"#ratings-and-visual-indicators","title":"Ratings and Visual Indicators"},{"url":"#rating-taxonomy","title":"Rating Taxonomy","items":[{"url":"#ote-and-oue-rating-taxonomy","title":"OT&E and OUE Rating Taxonomy"},{"url":"#eoa-and-oa-rating-taxonomy","title":"EOA and OA Rating Taxonomy"},{"url":"#operational-utility-assessment-oua-rating-taxonomy","title":"Operational Utility Assessment (OUA) Rating Taxonomy"}]}]},{"url":"#ratings-for-continuous-and-cumulative-feedback","title":"Ratings for Continuous and Cumulative Feedback"},{"url":"#rating-measures","title":"RATING MEASURES","items":[{"url":"#general-methods-for-rating-measures","title":"General Methods for Rating Measures","items":[{"url":"#direct-measurement","title":"Direct Measurement"},{"url":"#reasonable-inference","title":"Reasonable Inference"}]},{"url":"#types-of-measures","title":"Types of Measures"},{"url":"#measures-worksheet","title":"Measures Worksheet"},{"url":"#rating-measures-of-effectiveness","title":"Rating Measures of Effectiveness","items":[{"url":"#basis-for-moe-evaluation","title":"Basis for MOE Evaluation","items":[{"url":"#effect-criteria-or-identified-standard","title":"Effect Criteria or Identified Standard"},{"url":"#feedback-from-test-participants","title":"Feedback from Test Participants"},{"url":"#problemsdeficiencies","title":"Problems/Deficiencies"},{"url":"#required-workarounds","title":"Required Workarounds"},{"url":"#statistical-confidence","title":"Statistical Confidence"},{"url":"#reasonable-inference-of-mop-and-mos-impacts","title":"Reasonable Inference of MOP and MOS Impacts"},{"url":"#key-performance-parameters","title":"Key Performance Parameters"},{"url":"#moe-notable-findings","title":"MOE Notable Findings"}]}]},{"url":"#rating-mops-and-moss","title":"Rating MOPs and MOSs","items":[{"url":"#test-conditions","title":"Test Conditions"},{"url":"#deficiency-reports","title":"Deficiency Reports"},{"url":"#beyond-the-point-estimate","title":"Beyond the Point Estimate"},{"url":"#operational-experiencejudgement","title":"Operational Experience/Judgement"},{"url":"#key-performance-parameters-1","title":"Key Performance Parameters"},{"url":"#additional-observations","title":"Additional Observations"}]}]},{"url":"#rating-critical-operational-issues","title":"RATING CRITICAL OPERATIONAL ISSUES","items":[{"url":"#basis-for-coi-evaluations","title":"Basis for COI Evaluations","items":[{"url":"#preponderance-of-measures-meeting-criteria","title":"Preponderance of Measures Meeting Criteria"},{"url":"#prominent-measures","title":"Prominent Measures"},{"url":"#operational-conditions","title":"Operational Conditions","items":[{"url":"#cyber-effects","title":"Cyber Effects"}]},{"url":"#interaction-of-results","title":"Interaction of Results"},{"url":"#holistic-considerations","title":"Holistic Considerations"},{"url":"#coi-notable-findings","title":"COI Notable Findings"}]}]},{"url":"#rating-operational-effectiveness-and-suitability","title":"RATING OPERATIONAL EFFECTIVENESS AND SUITABILITY","items":[{"url":"#rating-effectiveness-and-suitability","title":"Rating Effectiveness and Suitability"}]},{"url":"#mission-capability-determination-optional","title":"Mission Capability Determination (Optional)"},{"url":"#test-reporting","title":"TEST REPORTING","items":[{"url":"#continuous-reporting","title":"Continuous Reporting","items":[{"url":"#operational-assessment-reports","title":"Operational Assessment Reports"},{"url":"#status-reports","title":"Status Reports"},{"url":"#periodic-reporting","title":"Periodic Reporting"},{"url":"#observation-reports","title":"Observation Reports"},{"url":"#significant-event-reports","title":"Significant Event Reports"},{"url":"#operational-test-situation-reports","title":"Operational Test Situation Reports"}]},{"url":"#final-reporting","title":"Final Reporting","items":[{"url":"#effectiveness-and-suitability-final-reporting","title":"Effectiveness and Suitability Final Reporting","items":[{"url":"#oue-final-reporting","title":"OUE Final Reporting"},{"url":"#iote-final-reporting","title":"IOT&E Final Reporting"},{"url":"#qote-final-reporting","title":"QOT&E Final Reporting"},{"url":"#fote-final-reporting","title":"FOT&E Final Reporting"},{"url":"#mote-final-reporting","title":"MOT&E Final Reporting"}]},{"url":"#interim-summary-report","title":"Interim Summary Report"},{"url":"#operational-utility-assessment-final-reporting","title":"Operational Utility Assessment Final Reporting"}]}]},{"url":"#coordination-and-publishing","title":"COORDINATION AND PUBLISHING","items":[{"url":"#controversial-information","title":"Controversial Information"},{"url":"#signatureapproval-levels","title":"Signature/Approval Levels"},{"url":"#coordination-method","title":"Coordination Method"},{"url":"#history-office","title":"History Office"},{"url":"#technical-editor-role","title":"Technical Editor Role"},{"url":"#report-medium","title":"Report Medium"},{"url":"#report-timeline-exceptions","title":"Report Timeline Exceptions"},{"url":"#final-report-publishing","title":"Final Report Publishing"},{"url":"#report-briefings","title":"Report Briefings"}]}]}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide"},"tableOfContents":{"items":[{"url":"#overview","title":"OVERVIEW"},{"url":"#elements-of-the-test-planning-process","title":"ELEMENTS OF THE TEST PLANNING PROCESS","items":[{"url":"#critical-operational-issues-and-operations","title":"Critical Operational Issues and Operations"},{"url":"#response-variables","title":"Response Variables"}]},{"url":"#factors-levels-and-prioritization","title":"Factors, Levels, and Prioritization"},{"url":"#goals-and-types-of-test","title":"GOALS AND TYPES OF TEST"},{"url":"#characterize","title":"Characterize"},{"url":"#compare","title":"Compare"},{"url":"#problem-identification","title":"Problem Identification"},{"url":"#types-of-test-designs","title":"TYPES OF TEST DESIGNS"},{"url":"#factorials","title":"Factorials","items":[{"url":"#fractional-factorial","title":"Fractional Factorial"},{"url":"#creating-fractional-factorial-designs-in-jmp-13","title":"Creating Fractional Factorial Designs in JMP 13:"}]},{"url":"#optimal-designs-computer-generated-designs","title":"Optimal Designs (Computer Generated Designs)","items":[{"url":"#creating-a-d-optimal-design-in-jmp-13","title":"Creating a D-Optimal design in JMP 13:"}]},{"url":"#augmented-designs","title":"Augmented Designs"},{"url":"#designs-for-computer-experiments","title":"Designs for Computer Experiments","items":[{"url":"#space-filling-designs","title":"Space-Filling Designs"}]},{"url":"#test-designs-for-comparing-systems","title":"Test Designs for Comparing Systems"},{"url":"#test-designs-for-problem-identification","title":"Test Designs for Problem Identification"},{"url":"#combinatorial-designs-covering-arrays","title":"Combinatorial Designs (Covering Arrays)","items":[{"url":"#creating-a-combinatorial-design-in-acts","title":"Creating a Combinatorial Design in ACTS:"},{"url":"#example-of-a-combinatorial-design","title":"Example of a Combinatorial Design"}]},{"url":"#demonstrations","title":"Demonstrations"},{"url":"#cases","title":"Cases"},{"url":"#observational-studies","title":"Observational Studies"},{"url":"#test-design-measures-of-merit","title":"TEST DESIGN MEASURES OF MERIT"},{"url":"#power","title":"Power"},{"url":"#optimality-efficiency","title":"Optimality (Efficiency)"},{"url":"#correlation-multicollinearity","title":"Correlation (Multicollinearity)"},{"url":"#prediction-variance","title":"Prediction Variance"},{"url":"#comparing-measures-of-merit","title":"Comparing Measures of Merit"},{"url":"#the-three-principles-of-design-of-experiments","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"},{"url":"#randomization","title":"Randomization"},{"url":"#replication","title":"Replication"},{"url":"#blocking","title":"Blocking"},{"url":"#typical-situations","title":"TYPICAL SITUATIONS","items":[{"url":"#how-do-i-select-a-design","title":"How do I Select a Design?"},{"url":"#i-have-factors-that-are-hard-to-change","title":"I Have Factors that Are Hard to Change"},{"url":"#can-i-combine-developmental-test-and-operational-test-data","title":"Can I Combine Developmental Test and Operational Test Data?"},{"url":"#i-have-disallowed-combinations","title":"I Have Disallowed Combinations"},{"url":"#my-power-is-too-low","title":"My Power Is Too Low"},{"url":"#i-have-factor-levels-that-depend-on-other-factor-levels","title":"I Have Factor Levels that Depend on Other Factor Levels"}]},{"url":"#best-practicespitfalls-in-test-design","title":"Best Practices/Pitfalls in Test Design"},{"url":"#pitfalls","title":"Pitfalls:"},{"url":"#appendices","title":"Appendices"},{"url":"#test-design-guidance","title":"Test Design Guidance"},{"url":"#technical-references-and-citations","title":"Technical References and Citations"},{"url":"#footnotes","title":"Footnotes"},{"url":"#fn1","title":"fn1"},{"url":"#fn2","title":"fn2"},{"url":"#fn3","title":"fn3"},{"url":"#fn4","title":"fn4"},{"url":"#fn5","title":"fn5"},{"url":"#fn6","title":"fn6"},{"url":"#fn7","title":"fn7"},{"url":"#fn8","title":"fn8"},{"url":"#fn9","title":"fn9"},{"url":"#fn10","title":"fn10"},{"url":"#fn11","title":"fn11"},{"url":"#fn12","title":"fn12"},{"url":"#fn13","title":"fn13"},{"url":"#fn14","title":"fn14"},{"url":"#fn15","title":"fn15"},{"url":"#fn16","title":"fn16"},{"url":"#fn17","title":"fn17"},{"url":"#fn18","title":"fn18"},{"url":"#fn19","title":"fn19"},{"url":"#fn20","title":"fn20"},{"url":"#fn21","title":"fn21"},{"url":"#fn22","title":"fn22"},{"url":"#fn23","title":"fn23"},{"url":"#fn24","title":"fn24"},{"url":"#fn25","title":"fn25"},{"url":"#fn26","title":"fn26"},{"url":"#fn27","title":"fn27"},{"url":"#fn28","title":"fn28"},{"url":"#fn29","title":"fn29"},{"url":"#fn30","title":"fn30"},{"url":"#fn31","title":"fn31"},{"url":"#fn32","title":"fn32"},{"url":"#fn33","title":"fn33"},{"url":"#fn34","title":"fn34"},{"url":"#fn35","title":"fn35"},{"url":"#fn36","title":"fn36"},{"url":"#fn37","title":"fn37"},{"url":"#fn38","title":"fn38"},{"url":"#fn39","title":"fn39"},{"url":"#fn40","title":"fn40"},{"url":"#fn41","title":"fn41"}]}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide"},"tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#section-1-fundamentals-of-measurement","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT","items":[{"url":"#measures-overview","title":"Measures Overview"},{"url":"#qualities-of-a-good-measure-set","title":"Qualities of a Good Measure Set"}]},{"url":"#section-2-measures-development","title":"SECTION 2 MEASURES DEVELOPMENT","items":[{"url":"#developing-moes","title":"Developing MOEs"},{"url":"#developing-mops-and-moss","title":"Developing MOPs and MOSs"}]},{"url":"#section-3-measure-documentation","title":"SECTION 3 MEASURE DOCUMENTATION","items":[{"url":"#measures-worksheet-overview","title":"Measures Worksheet Overview"},{"url":"#measures-worksheet-header","title":"Measures Worksheet Header"},{"url":"#body-of-the-measures-worksheet","title":"Body of the Measures Worksheet"},{"url":"#formatting-measures","title":"Formatting Measures"}]},{"url":"#appendix-a-categories-of-measures","title":"APPENDIX A CATEGORIES OF MEASURES","items":[{"url":"#continuous-measures","title":"Continuous Measures"},{"url":"#discrete-measures","title":"Discrete Measures"},{"url":"#composite-measures","title":"Composite Measures"}]},{"url":"#appendix-b-measure-review-quick-reference","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"},{"url":"#appendix-c-cyber-related-measures","title":"APPENDIX C CYBER-RELATED MEASURES","items":[{"url":"#measures-overview-1","title":"Measures Overview"},{"url":"#composite-measures-1","title":"Composite Measures"}]}]}}}],"group":[{"nodes":[{"tableOfContents":{"items":[{"url":"#2-letter-coord-of-air-force-operation-test-and-evaluation-center-produced-documentsbriefings-8-work-days","title":"2 Letter Coord of Air Force Operation Test and Evaluation Center-Produced Documents/Briefings (8 Work Days)"},{"url":"#commanderexecutive-director-briefing-request","title":"Commander/Executive Director Briefing Request"},{"url":"#command-section-coord-process-maximum-of-7-work-days","title":"Command Section Coord Process (Maximum of 7 Work Days)"},{"url":"#other-product-review-processes","title":"Other Product Review Processes"},{"url":"#things-to-consider-when-producing-documents-for-coordinationreview","title":"Things to Consider when Producing Documents for Coordination/Review","items":[{"url":"#drafting-plansreports-and-briefings","title":"Drafting Plans/Reports and Briefings:"},{"url":"#actionable-comments","title":"Actionable Comments"},{"url":"#meeting-external-suspenses","title":"Meeting External Suspenses"}]},{"url":"#accreditation-plansreports","title":"Accreditation Plans/Reports"},{"url":"#joint-reliability-maintainability-evaluation-team-charters","title":"Joint Reliability, Maintainability Evaluation Team Charters"}]},"fields":{"slug":"/OT&E_Guide/6-6-acap"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#test-capability-accreditation","title":"Test Capability Accreditation"},{"url":"#the-use-of-modeling-and-simulation","title":"The Use of Modeling and Simulation"},{"url":"#verification-validation-and-accreditation-definitions","title":"Verification, Validation and Accreditation Definitions"},{"url":"#acquisition-implications-of-verification-validation-and-accreditation","title":"Acquisition Implications of Verification, Validation and Accreditation"},{"url":"#accreditation-concepts","title":"Accreditation Concepts"},{"url":"#risk-matrix-example","title":"Risk Matrix: Example"},{"url":"#previous-accreditation","title":"Previous Accreditation"},{"url":"#accreditation-process","title":"Accreditation Process"},{"url":"#test-capability-accreditation-concept","title":"Test Capability Accreditation Concept"},{"url":"#accreditation-plan-and-report-format","title":"Accreditation Plan and Report Format"},{"url":"#accreditation-references-and-resources","title":"Accreditation References and Resources"},{"url":"#air-force-agency-for-modeling-and-simulation","title":"Air Force Agency for Modeling and Simulation"},{"url":"#modeling-and-simulation-coordination-office","title":"Modeling and Simulation Coordination Office"},{"url":"#best-practices","title":"Best Practices"},{"url":"#summary","title":"Summary"},{"url":"#references-and-resources","title":"References and Resources"},{"url":"#governance","title":"Governance"},{"url":"#points-of-contact","title":"Points of Contact"}]},"fields":{"slug":"/fn_guides/accreditation_guide"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/acronyms"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/1-6-art-principles"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#overview","title":"OVERVIEW"},{"url":"#elements-of-the-test-planning-process","title":"ELEMENTS OF THE TEST PLANNING PROCESS","items":[{"url":"#critical-operational-issues-and-operations","title":"Critical Operational Issues and Operations"},{"url":"#response-variables","title":"Response Variables"}]},{"url":"#factors-levels-and-prioritization","title":"Factors, Levels, and Prioritization"},{"url":"#goals-and-types-of-test","title":"GOALS AND TYPES OF TEST"},{"url":"#characterize","title":"Characterize"},{"url":"#compare","title":"Compare"},{"url":"#problem-identification","title":"Problem Identification"},{"url":"#types-of-test-designs","title":"TYPES OF TEST DESIGNS"},{"url":"#factorials","title":"Factorials","items":[{"url":"#fractional-factorial","title":"Fractional Factorial"},{"url":"#creating-fractional-factorial-designs-in-jmp-13","title":"Creating Fractional Factorial Designs in JMP 13:"}]},{"url":"#optimal-designs-computer-generated-designs","title":"Optimal Designs (Computer Generated Designs)","items":[{"url":"#creating-a-d-optimal-design-in-jmp-13","title":"Creating a D-Optimal design in JMP 13:"}]},{"url":"#augmented-designs","title":"Augmented Designs"},{"url":"#designs-for-computer-experiments","title":"Designs for Computer Experiments","items":[{"url":"#space-filling-designs","title":"Space-Filling Designs"}]},{"url":"#test-designs-for-comparing-systems","title":"Test Designs for Comparing Systems"},{"url":"#test-designs-for-problem-identification","title":"Test Designs for Problem Identification"},{"url":"#combinatorial-designs-covering-arrays","title":"Combinatorial Designs (Covering Arrays)","items":[{"url":"#creating-a-combinatorial-design-in-acts","title":"Creating a Combinatorial Design in ACTS:"},{"url":"#example-of-a-combinatorial-design","title":"Example of a Combinatorial Design"}]},{"url":"#demonstrations","title":"Demonstrations"},{"url":"#cases","title":"Cases"},{"url":"#observational-studies","title":"Observational Studies"},{"url":"#test-design-measures-of-merit","title":"TEST DESIGN MEASURES OF MERIT"},{"url":"#power","title":"Power"},{"url":"#optimality-efficiency","title":"Optimality (Efficiency)"},{"url":"#correlation-multicollinearity","title":"Correlation (Multicollinearity)"},{"url":"#prediction-variance","title":"Prediction Variance"},{"url":"#comparing-measures-of-merit","title":"Comparing Measures of Merit"},{"url":"#the-three-principles-of-design-of-experiments","title":"THE THREE PRINCIPLES OF DESIGN OF EXPERIMENTS"},{"url":"#randomization","title":"Randomization"},{"url":"#replication","title":"Replication"},{"url":"#blocking","title":"Blocking"},{"url":"#typical-situations","title":"TYPICAL SITUATIONS","items":[{"url":"#how-do-i-select-a-design","title":"How do I Select a Design?"},{"url":"#i-have-factors-that-are-hard-to-change","title":"I Have Factors that Are Hard to Change"},{"url":"#can-i-combine-developmental-test-and-operational-test-data","title":"Can I Combine Developmental Test and Operational Test Data?"},{"url":"#i-have-disallowed-combinations","title":"I Have Disallowed Combinations"},{"url":"#my-power-is-too-low","title":"My Power Is Too Low"},{"url":"#i-have-factor-levels-that-depend-on-other-factor-levels","title":"I Have Factor Levels that Depend on Other Factor Levels"}]},{"url":"#best-practicespitfalls-in-test-design","title":"Best Practices/Pitfalls in Test Design"},{"url":"#pitfalls","title":"Pitfalls:"},{"url":"#appendices","title":"Appendices"},{"url":"#test-design-guidance","title":"Test Design Guidance"},{"url":"#technical-references-and-citations","title":"Technical References and Citations"},{"url":"#footnotes","title":"Footnotes"},{"url":"#fn1","title":"fn1"},{"url":"#fn2","title":"fn2"},{"url":"#fn3","title":"fn3"},{"url":"#fn4","title":"fn4"},{"url":"#fn5","title":"fn5"},{"url":"#fn6","title":"fn6"},{"url":"#fn7","title":"fn7"},{"url":"#fn8","title":"fn8"},{"url":"#fn9","title":"fn9"},{"url":"#fn10","title":"fn10"},{"url":"#fn11","title":"fn11"},{"url":"#fn12","title":"fn12"},{"url":"#fn13","title":"fn13"},{"url":"#fn14","title":"fn14"},{"url":"#fn15","title":"fn15"},{"url":"#fn16","title":"fn16"},{"url":"#fn17","title":"fn17"},{"url":"#fn18","title":"fn18"},{"url":"#fn19","title":"fn19"},{"url":"#fn20","title":"fn20"},{"url":"#fn21","title":"fn21"},{"url":"#fn22","title":"fn22"},{"url":"#fn23","title":"fn23"},{"url":"#fn24","title":"fn24"},{"url":"#fn25","title":"fn25"},{"url":"#fn26","title":"fn26"},{"url":"#fn27","title":"fn27"},{"url":"#fn28","title":"fn28"},{"url":"#fn29","title":"fn29"},{"url":"#fn30","title":"fn30"},{"url":"#fn31","title":"fn31"},{"url":"#fn32","title":"fn32"},{"url":"#fn33","title":"fn33"},{"url":"#fn34","title":"fn34"},{"url":"#fn35","title":"fn35"},{"url":"#fn36","title":"fn36"},{"url":"#fn37","title":"fn37"},{"url":"#fn38","title":"fn38"},{"url":"#fn39","title":"fn39"},{"url":"#fn40","title":"fn40"},{"url":"#fn41","title":"fn41"}]},"fields":{"slug":"/fn_guides/analyst_test_design_guide"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#define-the-what","title":"Define the \"What\"","items":[{"url":"#system-under-test","title":"System Under Test"},{"url":"#measures","title":"Measures"},{"url":"#criteria-and-thresholds","title":"Criteria and Thresholds"},{"url":"#data-and-data-elements","title":"Data and Data Elements"},{"url":"#effectiveness-and-suitability","title":"Effectiveness and Suitability"},{"url":"#coi-operations-measures-data-hierarchy","title":"COI-Operations-Measures-Data Hierarchy"},{"url":"#conditions","title":"Conditions"},{"url":"#operational-capabilities","title":"Operational Capabilities"}]},{"url":"#test-design","title":"Test Design","items":[{"url":"#test-design-goal","title":"Test Design Goal"},{"url":"#test-designs","title":"Test Designs"}]},{"url":"#test-execution","title":"Test Execution","items":[{"url":"#test-capabilities","title":"Test Capabilities"},{"url":"#verification-validation-and-accreditation","title":"Verification, Validation, and Accreditation"},{"url":"#data-management","title":"Data Management"},{"url":"#detailed-test-procedures","title":"Detailed Test Procedures"},{"url":"#limitations","title":"Limitations"},{"url":"#resourcing-test-events","title":"Resourcing Test Events"},{"url":"#technical-reviews","title":"Technical Reviews"},{"url":"#test-plans","title":"Test Plans"},{"url":"#administrative-considerations","title":"Administrative Considerations"},{"url":"#executing-the-test","title":"Executing the Test"}]},{"url":"#analysis-and-evaluation","title":"Analysis and Evaluation","items":[{"url":"#inspection","title":"Inspection"},{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#effectiveness-and-suitability-1","title":"Effectiveness and Suitability"},{"url":"#reporting-ratings","title":"Reporting Ratings"},{"url":"#deficiency-reporting","title":"Deficiency Reporting"},{"url":"#exit-criteria-assessment","title":"Exit Criteria Assessment"}]},{"url":"#conclusions-and-documenting","title":"Conclusions and Documenting"}]},"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide/6-7-case-study"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#handling-information-requests","title":"Handling Information Requests"},{"url":"#marking-and-protecting-data","title":"Marking and Protecting Data"},{"url":"#distribution-statements","title":"Distribution Statements"},{"url":"#test-program-case-file","title":"Test Program Case File"},{"url":"#impact-of-system-modifications","title":"Impact of System Modifications"},{"url":"#visual-information-documentation","title":"Visual Information Documentation"}]},"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#directorate-roles-and-responsibilities","title":"Directorate Roles and Responsibilities"},{"url":"#signature-and-approval","title":"Signature and Approval"}]},"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#purpose","title":"PURPOSE"},{"url":"#executive-summary-body-and-appendices","title":"Executive Summary, Body, and Appendices"},{"url":"#consistency-is-key","title":"Consistency is Key"},{"url":"#one-voice","title":"One Voice"},{"url":"#templates","title":"Templates"},{"url":"#microsoft-word-options","title":"Microsoft Word Options","items":[{"url":"#display","title":"Display:"},{"url":"#proofing","title":"Proofing:"},{"url":"#advanced","title":"Advanced:"}]},{"url":"#focus-areas","title":"Focus Areas"},{"url":"#styles","title":"Styles"},{"url":"#acronyms","title":"Acronyms"},{"url":"#commas","title":"Commas"},{"url":"#next-page-and-page-breaks","title":"\"Next Page\" and \"Page\" Breaks"},{"url":"#headers-and-footers","title":"Headers and Footers"},{"url":"#page-numbering","title":"Page Numbering"},{"url":"#blank-pages","title":"Blank Pages"},{"url":"#capitalization","title":"Capitalization"},{"url":"#citing-air-force-or-other-military-bases","title":"Citing Air Force (or Other Military) Bases"},{"url":"#vertical-lists","title":"Vertical Lists"},{"url":"#numbering-tables-and-figures","title":"Numbering Tables and Figures"},{"url":"#tables","title":"Tables"},{"url":"#figures","title":"Figures"},{"url":"#passive-voice","title":"Passive Voice"},{"url":"#copyrightstrademarks","title":"Copyrights/Trademarks"},{"url":"#wordiness","title":"Wordiness"},{"url":"#hyphens-en-dashes-and-em-dashes","title":"Hyphens, En Dashes, and Em Dashes"},{"url":"#apostrophes","title":"Apostrophes"},{"url":"#choppy-sentences","title":"Choppy Sentences"},{"url":"#numbers","title":"Numbers"},{"url":"#dates","title":"Dates"},{"url":"#abbreviations","title":"Abbreviations"},{"url":"#terms","title":"Terms"},{"url":"#symbols-and-units-of-measure","title":"Symbols and Units of Measure"},{"url":"#verb-tenses","title":"Verb Tenses"},{"url":"#embedded-files","title":"Embedded Files"},{"url":"#converting-pictures","title":"Converting Pictures"},{"url":"#referencesdocumentation","title":"References/Documentation"},{"url":"#patches","title":"Patches"},{"url":"#classification-markings","title":"Classification Markings"},{"url":"#distribution-list","title":"Distribution List"},{"url":"#sf298-report-documentation-page","title":"SF298 Report Documentation Page"},{"url":"#spell-check","title":"Spell Check"},{"url":"#configuration-control","title":"Configuration Control"},{"url":"#table-of-contents","title":"Table of Contents"},{"url":"#standardization-checklist","title":"Standardization Checklist"}]},"fields":{"slug":"/fn_guides/editing_reports_guide"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#test-activity-sequence","title":"TEST ACTIVITY SEQUENCE"},{"url":"#analysis-evaluation-and-reporting","title":"ANALYSIS, EVALUATION, AND REPORTING","items":[{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#reporting","title":"Reporting"}]},{"url":"#structure-of-an-evaluation","title":"STRUCTURE OF AN EVALUATION","items":[{"url":"#ote-evaluation-structure","title":"OT&E Evaluation Structure"}]},{"url":"#rating-tenetsprinciples","title":"RATING TENETS/PRINCIPLES","items":[{"url":"#rating","title":"Rating","items":[{"url":"#terminology","title":"Terminology"},{"url":"#report","title":"Report"}]},{"url":"#ratings-and-visual-indicators","title":"Ratings and Visual Indicators"},{"url":"#rating-taxonomy","title":"Rating Taxonomy","items":[{"url":"#ote-and-oue-rating-taxonomy","title":"OT&E and OUE Rating Taxonomy"},{"url":"#eoa-and-oa-rating-taxonomy","title":"EOA and OA Rating Taxonomy"},{"url":"#operational-utility-assessment-oua-rating-taxonomy","title":"Operational Utility Assessment (OUA) Rating Taxonomy"}]}]},{"url":"#ratings-for-continuous-and-cumulative-feedback","title":"Ratings for Continuous and Cumulative Feedback"},{"url":"#rating-measures","title":"RATING MEASURES","items":[{"url":"#general-methods-for-rating-measures","title":"General Methods for Rating Measures","items":[{"url":"#direct-measurement","title":"Direct Measurement"},{"url":"#reasonable-inference","title":"Reasonable Inference"}]},{"url":"#types-of-measures","title":"Types of Measures"},{"url":"#measures-worksheet","title":"Measures Worksheet"},{"url":"#rating-measures-of-effectiveness","title":"Rating Measures of Effectiveness","items":[{"url":"#basis-for-moe-evaluation","title":"Basis for MOE Evaluation","items":[{"url":"#effect-criteria-or-identified-standard","title":"Effect Criteria or Identified Standard"},{"url":"#feedback-from-test-participants","title":"Feedback from Test Participants"},{"url":"#problemsdeficiencies","title":"Problems/Deficiencies"},{"url":"#required-workarounds","title":"Required Workarounds"},{"url":"#statistical-confidence","title":"Statistical Confidence"},{"url":"#reasonable-inference-of-mop-and-mos-impacts","title":"Reasonable Inference of MOP and MOS Impacts"},{"url":"#key-performance-parameters","title":"Key Performance Parameters"},{"url":"#moe-notable-findings","title":"MOE Notable Findings"}]}]},{"url":"#rating-mops-and-moss","title":"Rating MOPs and MOSs","items":[{"url":"#test-conditions","title":"Test Conditions"},{"url":"#deficiency-reports","title":"Deficiency Reports"},{"url":"#beyond-the-point-estimate","title":"Beyond the Point Estimate"},{"url":"#operational-experiencejudgement","title":"Operational Experience/Judgement"},{"url":"#key-performance-parameters-1","title":"Key Performance Parameters"},{"url":"#additional-observations","title":"Additional Observations"}]}]},{"url":"#rating-critical-operational-issues","title":"RATING CRITICAL OPERATIONAL ISSUES","items":[{"url":"#basis-for-coi-evaluations","title":"Basis for COI Evaluations","items":[{"url":"#preponderance-of-measures-meeting-criteria","title":"Preponderance of Measures Meeting Criteria"},{"url":"#prominent-measures","title":"Prominent Measures"},{"url":"#operational-conditions","title":"Operational Conditions","items":[{"url":"#cyber-effects","title":"Cyber Effects"}]},{"url":"#interaction-of-results","title":"Interaction of Results"},{"url":"#holistic-considerations","title":"Holistic Considerations"},{"url":"#coi-notable-findings","title":"COI Notable Findings"}]}]},{"url":"#rating-operational-effectiveness-and-suitability","title":"RATING OPERATIONAL EFFECTIVENESS AND SUITABILITY","items":[{"url":"#rating-effectiveness-and-suitability","title":"Rating Effectiveness and Suitability"}]},{"url":"#mission-capability-determination-optional","title":"Mission Capability Determination (Optional)"},{"url":"#test-reporting","title":"TEST REPORTING","items":[{"url":"#continuous-reporting","title":"Continuous Reporting","items":[{"url":"#operational-assessment-reports","title":"Operational Assessment Reports"},{"url":"#status-reports","title":"Status Reports"},{"url":"#periodic-reporting","title":"Periodic Reporting"},{"url":"#observation-reports","title":"Observation Reports"},{"url":"#significant-event-reports","title":"Significant Event Reports"},{"url":"#operational-test-situation-reports","title":"Operational Test Situation Reports"}]},{"url":"#final-reporting","title":"Final Reporting","items":[{"url":"#effectiveness-and-suitability-final-reporting","title":"Effectiveness and Suitability Final Reporting","items":[{"url":"#oue-final-reporting","title":"OUE Final Reporting"},{"url":"#iote-final-reporting","title":"IOT&E Final Reporting"},{"url":"#qote-final-reporting","title":"QOT&E Final Reporting"},{"url":"#fote-final-reporting","title":"FOT&E Final Reporting"},{"url":"#mote-final-reporting","title":"MOT&E Final Reporting"}]},{"url":"#interim-summary-report","title":"Interim Summary Report"},{"url":"#operational-utility-assessment-final-reporting","title":"Operational Utility Assessment Final Reporting"}]}]},{"url":"#coordination-and-publishing","title":"COORDINATION AND PUBLISHING","items":[{"url":"#controversial-information","title":"Controversial Information"},{"url":"#signatureapproval-levels","title":"Signature/Approval Levels"},{"url":"#coordination-method","title":"Coordination Method"},{"url":"#history-office","title":"History Office"},{"url":"#technical-editor-role","title":"Technical Editor Role"},{"url":"#report-medium","title":"Report Medium"},{"url":"#report-timeline-exceptions","title":"Report Timeline Exceptions"},{"url":"#final-report-publishing","title":"Final Report Publishing"},{"url":"#report-briefings","title":"Report Briefings"}]}]},"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#afotecs-role-in-fielding-combat-capability","title":"AFOTECs Role in Fielding Combat Capability"}]},"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/fn_guides"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/glossary"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/1-1-introduction"}}]},{"nodes":[{"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"}]}]},"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#introduction-and-intent","title":"INTRODUCTION AND INTENT"},{"url":"#vocabulary-of-lessons-learned","title":"Vocabulary of Lessons Learned"},{"url":"#policy-guidance","title":"Policy Guidance"},{"url":"#process","title":"PROCESS"},{"url":"#milestoneevent-triggers","title":"Milestone/Event Triggers"},{"url":"#observations-review","title":"Observations Review"},{"url":"#dissemination","title":"Dissemination"},{"url":"#lessons-learned-resolution","title":"Lessons Learned (Resolution)"},{"url":"#conclusion","title":"CONCLUSION"},{"url":"#observation-sheet","title":"OBSERVATION SHEET"},{"url":"#interview-sheet","title":"INTERVIEW SHEET"}]},"fields":{"slug":"/fn_guides/lessons_learned_guide"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#section-1-fundamentals-of-measurement","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT","items":[{"url":"#measures-overview","title":"Measures Overview"},{"url":"#qualities-of-a-good-measure-set","title":"Qualities of a Good Measure Set"}]},{"url":"#section-2-measures-development","title":"SECTION 2 MEASURES DEVELOPMENT","items":[{"url":"#developing-moes","title":"Developing MOEs"},{"url":"#developing-mops-and-moss","title":"Developing MOPs and MOSs"}]},{"url":"#section-3-measure-documentation","title":"SECTION 3 MEASURE DOCUMENTATION","items":[{"url":"#measures-worksheet-overview","title":"Measures Worksheet Overview"},{"url":"#measures-worksheet-header","title":"Measures Worksheet Header"},{"url":"#body-of-the-measures-worksheet","title":"Body of the Measures Worksheet"},{"url":"#formatting-measures","title":"Formatting Measures"}]},{"url":"#appendix-a-categories-of-measures","title":"APPENDIX A CATEGORIES OF MEASURES","items":[{"url":"#continuous-measures","title":"Continuous Measures"},{"url":"#discrete-measures","title":"Discrete Measures"},{"url":"#composite-measures","title":"Composite Measures"}]},{"url":"#appendix-b-measure-review-quick-reference","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"},{"url":"#appendix-c-cyber-related-measures","title":"APPENDIX C CYBER-RELATED MEASURES","items":[{"url":"#measures-overview-1","title":"Measures Overview"},{"url":"#composite-measures-1","title":"Composite Measures"}]}]},"fields":{"slug":"/fn_guides/measures_guide"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide/4-3-OT-construct"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#introduction","title":"INTRODUCTION"},{"url":"#the-operational-test-and-evaluation-construct","title":"The Operational Test and Evaluation Construct"},{"url":"#operational-sufficiency-and-technical-adequacy","title":"Operational Sufficiency and Technical Adequacy"},{"url":"#operational-test-and-evaluation-test-activity-cycles","title":"Operational Test and Evaluation Test Activity Cycles"},{"url":"#using-a-core-team-approach","title":"Using a Core Team Approach."},{"url":"#construct-development-meetings","title":"Construct Development Meetings"},{"url":"#battlespace-development","title":"Battlespace Development","items":[{"url":"#researching-the-capability-or-system-being-acquired","title":"Researching the Capability or System Being Acquired"},{"url":"#battlespace-depiction","title":"Battlespace Depiction","items":[{"url":"#the-evaluation-view","title":"The Evaluation View"},{"url":"#the-evaluation-view-1","title":"The Evaluation View 1"},{"url":"#the-evaluation-view-2","title":"The Evaluation View 2"},{"url":"#capability-requirements-mapping","title":"Capability Requirements Mapping"},{"url":"#mission-statement","title":"Mission Statement"},{"url":"#critical-operational-issues","title":"Critical Operational Issues"},{"url":"#operations","title":"Operations"}]},{"url":"#operational-employment-and-support-conditions","title":"Operational Employment and Support Conditions","items":[{"url":"#measures-of-effectiveness","title":"Measures of Effectiveness"},{"url":"#operational-conditions-factors-and-levels","title":"Operational Conditions (Factors and Levels)"},{"url":"#identify-factors-and-levels","title":"Identify Factors and Levels."},{"url":"#prioritizing-factors","title":"Prioritizing Factors"}]},{"url":"#operational-capabilities-oc","title":"Operational Capabilities (OC)"}]},{"url":"#evaluation-summary-chart","title":"Evaluation Summary Chart","items":[{"url":"#mission-statement-in-an-evaluation-summary-chart","title":"Mission Statement in an Evaluation Summary Chart"},{"url":"#critical-operational-issues-in-an-evaluation-summary-chart","title":"Critical Operational Issues in an Evaluation Summary Chart"},{"url":"#mission-effects-in-an-evaluation-summary-chart","title":"Mission Effects in an Evaluation Summary Chart"},{"url":"#operational-capability-requirements-in-an-evaluation-summary-chart","title":"Operational Capability Requirements in an Evaluation Summary Chart"}]},{"url":"#test-design","title":"Test Design","items":[{"url":"#test-design-goals","title":"Test Design Goals"},{"url":"#types-of-test-design","title":"Types of Test Design"},{"url":"#factor-management","title":"Factor Management."},{"url":"#unconstrained-and-constrained-events","title":"Unconstrained and Constrained events"},{"url":"#statistical-measures-of-merit","title":"Statistical Measures of Merit"},{"url":"#test-events","title":"Test Events"},{"url":"#test-design-validations","title":"Test Design Validations"}]},{"url":"#measures-development","title":"Measures Development"},{"url":"#test-execution-planning","title":"Test Execution Planning","items":[{"url":"#test-methodology","title":"Test Methodology"},{"url":"#test-scenarios","title":"Test Scenarios"},{"url":"#test-capability-needs-and-shortfalls","title":"Test Capability Needs and Shortfalls","items":[{"url":"#time-phased-investment-document","title":"Time-Phased Investment Document"},{"url":"#determining-range-requirements","title":"Determining Range Requirements"},{"url":"#range-requirement-identification","title":"Range Requirement Identification"},{"url":"#range-selection-considerations","title":"Range Selection Considerations"},{"url":"#national-cyber-range-considerations","title":"National Cyber Range Considerations"},{"url":"#test-targets","title":"Test Targets"},{"url":"#range-safety-considerations","title":"Range Safety Considerations"},{"url":"#range-instrumentation-considerations","title":"Range Instrumentation Considerations"},{"url":"#range-data-processing-considerations","title":"Range Data Processing Considerations"},{"url":"#test-article-instrumentation","title":"Test Article Instrumentation"},{"url":"#program-introduction-document-release-authority","title":"Program Introduction Document Release Authority"}]},{"url":"#the-use-of-modeling-and-simulation","title":"The Use of Modeling and Simulation"},{"url":"#test-capability-accreditation","title":"Test Capability Accreditation"},{"url":"#test-constraints-and-limitations","title":"Test Constraints and Limitations"},{"url":"#basis-of-estimate-for-test-resources","title":"Basis of Estimate for Test Resources"},{"url":"#initial-resource-estimates","title":"Initial Resource Estimates"}]},{"url":"#documenting-the-operational-test-and-evaluation-construct","title":"Documenting the Operational Test and Evaluation Construct"}]},"fields":{"slug":"/fn_guides/OTE_construct_development_guide"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#about","title":"About"},{"url":"#app-notes","title":"App Notes"},{"url":"#credits","title":"Credits","items":[{"url":"#the-ote-guide-team-is","title":"The OT&E Guide Team is:"},{"url":"#the-app-team-is","title":"The App Team is:"}]}]},"fields":{"slug":"/"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/6-3-resources"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide/6-2-risk-management"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#environment-safety-and-occupational-health","title":"ENVIRONMENT, SAFETY AND OCCUPATIONAL HEALTH"},{"url":"#safety-database-and-tools","title":"Safety Database and Tools"},{"url":"#planning-and-review-process","title":"Planning and Review Process"},{"url":"#health-and-safety-plan","title":"Health and Safety Plan"},{"url":"#integrated-safety-review-board","title":"Integrated Safety Review Board"},{"url":"#environment-safety-and-occupational-health-certification-board","title":"Environment, Safety and Occupational Health Certification Board"}]},"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide"}}]},{"nodes":[{"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"}]}]},"fields":{"slug":"/OT&E_Guide/3-2-standing-activities"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#strategy-planning-and-programming-process","title":"STRATEGY, PLANNING, AND PROGRAMMING PROCESS"}]},"fields":{"slug":"/fn_guides/strat_planning_programming_guide"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#initial-tasking-order","title":"Initial Tasking Order"},{"url":"#tasking-order-update","title":"Tasking Order Update"},{"url":"#program-transfer","title":"Program Transfer"}]},"fields":{"slug":"/OT&E_Guide/6-1-1-tasking"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/6-1-3-team-training"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#purpose","title":"PURPOSE","items":[{"url":"#definition","title":"Definition"},{"url":"#support-goals","title":"Support Goals"}]},{"url":"#test-range-and-facility-capabilities","title":"TEST RANGE AND FACILITY CAPABILITIES"},{"url":"#existing-test-capability-identification","title":"EXISTING TEST CAPABILITY IDENTIFICATION"},{"url":"#test-capability-gap-identification","title":"TEST CAPABILITY GAP IDENTIFICATION"},{"url":"#test-capability-gap-support-and-reporting","title":"TEST CAPABILITY GAP SUPPORT AND REPORTING"},{"url":"#munitions-management","title":"MUNITIONS MANAGEMENT"},{"url":"#test-resource-plan-requirements-verification-and-feedback","title":"TEST RESOURCE PLAN REQUIREMENTS VERIFICATION AND FEEDBACK"}]},"fields":{"slug":"/fn_guides/test_capability_guide"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#exit-criteria","title":"Exit Criteria"}]},"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/3-3-test-strategy"}}]}]}}} \ No newline at end of file +{"data":{"allMdx":{"edges":[{"node":{"fields":{"slug":"/OTE_construct_development_guide"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/fn_guides"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/"},"tableOfContents":{"items":[{"url":"#about","title":"About"},{"url":"#app-notes","title":"App Notes"},{"url":"#credits","title":"Credits","items":[{"url":"#the-ote-guide-team-is","title":"The OT&E Guide Team is:"},{"url":"#the-app-team-is","title":"The App Team is:"}]}]}}},{"node":{"fields":{"slug":"/glossary"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/lessons_learned_guide"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/measures_guide"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide"},"tableOfContents":{"items":[{"url":"#strategy-planning-and-programming-process","title":"STRATEGY, PLANNING, AND PROGRAMMING PROCESS"}]}}},{"node":{"fields":{"slug":"/safety_risk_mgmt_guide"},"tableOfContents":{"items":[{"url":"#environment-safety-and-occupational-health","title":"ENVIRONMENT, SAFETY AND OCCUPATIONAL HEALTH"},{"url":"#safety-database-and-tools","title":"Safety Database and Tools"},{"url":"#planning-and-review-process","title":"Planning and Review Process"},{"url":"#health-and-safety-plan","title":"Health and Safety Plan"},{"url":"#integrated-safety-review-board","title":"Integrated Safety Review Board"},{"url":"#environment-safety-and-occupational-health-certification-board","title":"Environment, Safety and Occupational Health Certification Board"}]}}},{"node":{"fields":{"slug":"/test_capability_guide"},"tableOfContents":{"items":[{"url":"#purpose","title":"PURPOSE","items":[{"url":"#definition","title":"Definition"},{"url":"#support-goals","title":"Support Goals"}]},{"url":"#test-range-and-facility-capabilities","title":"TEST RANGE AND FACILITY CAPABILITIES"},{"url":"#existing-test-capability-identification","title":"EXISTING TEST CAPABILITY IDENTIFICATION"},{"url":"#test-capability-gap-identification","title":"TEST CAPABILITY GAP IDENTIFICATION"},{"url":"#test-capability-gap-support-and-reporting","title":"TEST CAPABILITY GAP SUPPORT AND REPORTING"},{"url":"#munitions-management","title":"MUNITIONS MANAGEMENT"},{"url":"#test-resource-plan-requirements-verification-and-feedback","title":"TEST RESOURCE PLAN REQUIREMENTS VERIFICATION AND FEEDBACK"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes"},"tableOfContents":{"items":[{"url":"#afotecs-role-in-fielding-combat-capability","title":"AFOTECs Role in Fielding Combat Capability"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-1-introduction"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/1-6-art-principles"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision"},"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"}]}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities"},"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"}]}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit"},"tableOfContents":{"items":[{"url":"#exit-criteria","title":"Exit Criteria"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-1-tasking"},"tableOfContents":{"items":[{"url":"#initial-tasking-order","title":"Initial Tasking Order"},{"url":"#tasking-order-update","title":"Tasking Order Update"},{"url":"#program-transfer","title":"Program Transfer"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-3-team-training"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec"},"tableOfContents":{"items":[{"url":"#directorate-roles-and-responsibilities","title":"Directorate Roles and Responsibilities"},{"url":"#signature-and-approval","title":"Signature and Approval"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup"},"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"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources"},"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"}]}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap"},"tableOfContents":{"items":[{"url":"#2-letter-coord-of-air-force-operation-test-and-evaluation-center-produced-documentsbriefings-8-work-days","title":"2 Letter Coord of Air Force Operation Test and Evaluation Center-Produced Documents/Briefings (8 Work Days)"},{"url":"#commanderexecutive-director-briefing-request","title":"Commander/Executive Director Briefing Request"},{"url":"#command-section-coord-process-maximum-of-7-work-days","title":"Command Section Coord Process (Maximum of 7 Work Days)"},{"url":"#other-product-review-processes","title":"Other Product Review Processes"},{"url":"#things-to-consider-when-producing-documents-for-coordinationreview","title":"Things to Consider when Producing Documents for Coordination/Review","items":[{"url":"#drafting-plansreports-and-briefings","title":"Drafting Plans/Reports and Briefings:"},{"url":"#actionable-comments","title":"Actionable Comments"},{"url":"#meeting-external-suspenses","title":"Meeting External Suspenses"}]},{"url":"#accreditation-plansreports","title":"Accreditation Plans/Reports"},{"url":"#joint-reliability-maintainability-evaluation-team-charters","title":"Joint Reliability, Maintainability Evaluation Team Charters"}]}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct"},"tableOfContents":{"items":[{"url":"#define-the-what","title":"Define the \"What\"","items":[{"url":"#system-under-test","title":"System Under Test"},{"url":"#measures","title":"Measures"},{"url":"#criteria-and-thresholds","title":"Criteria and Thresholds"},{"url":"#data-and-data-elements","title":"Data and Data Elements"},{"url":"#effectiveness-and-suitability","title":"Effectiveness and Suitability"},{"url":"#coi-operations-measures-data-hierarchy","title":"COI-Operations-Measures-Data Hierarchy"},{"url":"#conditions","title":"Conditions"},{"url":"#operational-capabilities","title":"Operational Capabilities"}]},{"url":"#test-design","title":"Test Design","items":[{"url":"#test-design-goal","title":"Test Design Goal"},{"url":"#test-designs","title":"Test Designs"}]},{"url":"#test-execution","title":"Test Execution","items":[{"url":"#test-capabilities","title":"Test Capabilities"},{"url":"#verification-validation-and-accreditation","title":"Verification, Validation, and Accreditation"},{"url":"#data-management","title":"Data Management"},{"url":"#detailed-test-procedures","title":"Detailed Test Procedures"},{"url":"#limitations","title":"Limitations"},{"url":"#resourcing-test-events","title":"Resourcing Test Events"},{"url":"#technical-reviews","title":"Technical Reviews"},{"url":"#test-plans","title":"Test Plans"},{"url":"#administrative-considerations","title":"Administrative Considerations"},{"url":"#executing-the-test","title":"Executing the Test"}]},{"url":"#analysis-and-evaluation","title":"Analysis and Evaluation","items":[{"url":"#inspection","title":"Inspection"},{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#effectiveness-and-suitability-1","title":"Effectiveness and Suitability"},{"url":"#reporting-ratings","title":"Reporting Ratings"},{"url":"#deficiency-reporting","title":"Deficiency Reporting"},{"url":"#exit-criteria-assessment","title":"Exit Criteria Assessment"}]},{"url":"#conclusions-and-documenting","title":"Conclusions and Documenting"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback"},"tableOfContents":{"items":[{"url":"#handling-information-requests","title":"Handling Information Requests"},{"url":"#marking-and-protecting-data","title":"Marking and Protecting Data"},{"url":"#distribution-statements","title":"Distribution Statements"},{"url":"#test-program-case-file","title":"Test Program Case File"},{"url":"#impact-of-system-modifications","title":"Impact of System Modifications"},{"url":"#visual-information-documentation","title":"Visual Information Documentation"}]}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach."},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart"},"tableOfContents":{"items":[{"url":"#mission-statement-in-an-evaluation-summary-chart","title":"Mission Statement in an Evaluation Summary Chart"},{"url":"#critical-operational-issues-in-an-evaluation-summary-chart","title":"Critical Operational Issues in an Evaluation Summary Chart"},{"url":"#mission-effects-in-an-evaluation-summary-chart","title":"Mission Effects in an Evaluation Summary Chart"},{"url":"#operational-capability-requirements-in-an-evaluation-summary-chart","title":"Operational Capability Requirements in an Evaluation Summary Chart"}]}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design"},"tableOfContents":{"items":[{"url":"#test-design-goals","title":"Test Design Goals"},{"url":"#types-of-test-design","title":"Types of Test Design"},{"url":"#factor-management","title":"Factor Management"},{"url":"#unconstrained-and-constrained-events","title":"Unconstrained and Constrained events"},{"url":"#statistical-measures-of-merit","title":"Statistical Measures of Merit"},{"url":"#test-events","title":"Test Events"},{"url":"#test-design-validations","title":"Test Design Validations"}]}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development"},"tableOfContents":{"items":[{"url":"#researching-the-capability-or-system-being-acquired","title":"Researching the Capability or System Being Acquired"},{"url":"#battlespace-depiction","title":"Battlespace Depiction","items":[{"url":"#the-evaluation-view","title":"The Evaluation View"},{"url":"#the-evaluation-view-1","title":"The Evaluation View 1"},{"url":"#the-evaluation-view-2","title":"The Evaluation View 2"},{"url":"#capability-requirements-mapping","title":"Capability Requirements Mapping"},{"url":"#mission-statement","title":"Mission Statement"},{"url":"#critical-operational-issues","title":"Critical Operational Issues"},{"url":"#operations","title":"Operations"}]},{"url":"#operational-employment-and-support-conditions","title":"Operational Employment and Support Conditions","items":[{"url":"#measures-of-effectiveness","title":"Measures of Effectiveness"},{"url":"#operational-conditions-factors-and-levels","title":"Operational Conditions (Factors and Levels)"},{"url":"#identify-factors-and-levels","title":"Identify Factors and Levels."},{"url":"#prioritizing-factors","title":"Prioritizing Factors"}]},{"url":"#operational-capabilities","title":"Operational Capabilities"}]}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning"},"tableOfContents":{"items":[{"url":"#test-methodology","title":"Test Methodology"},{"url":"#test-scenarios","title":"Test Scenarios"},{"url":"#test-capability-needs-and-shortfalls","title":"Test Capability Needs and Shortfalls","items":[{"url":"#time-phased-investment-document","title":"Time-Phased Investment Document"},{"url":"#determining-range-requirements","title":"Determining Range Requirements"},{"url":"#range-requirement-identification","title":"Range Requirement Identification"},{"url":"#range-selection-considerations","title":"Range Selection Considerations"},{"url":"#national-cyber-range-considerations","title":"National Cyber Range Considerations"},{"url":"#test-targets","title":"Test Targets"},{"url":"#range-safety-considerations","title":"Range Safety Considerations"},{"url":"#range-instrumentation-considerations","title":"Range Instrumentation Considerations"},{"url":"#range-data-processing-considerations","title":"Range Data Processing Considerations"},{"url":"#test-article-instrumentation","title":"Test Article Instrumentation"},{"url":"#program-introduction-document-release-authority","title":"Program Introduction Document Release Authority"}]},{"url":"#the-use-of-modeling-and-simulation","title":"The Use of Modeling and Simulation"},{"url":"#test-capability-accreditation","title":"Test Capability Accreditation"},{"url":"#test-constraints-and-limitations","title":"Test Constraints and Limitations"},{"url":"#basis-of-estimate-for-test-resources","title":"Basis of Estimate for Test Resources"},{"url":"#initial-resource-estimates","title":"Initial Resource Estimates"}]}}},{"node":{"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/2-7-Best-Practices"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/2-8-Summary"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/3-1-Governance"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS"},"tableOfContents":{"items":[{"url":"#critical-operational-issues-and-operations","title":"Critical Operational Issues and Operations"},{"url":"#response-variables","title":"Response Variables"}]}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments"},"tableOfContents":{"items":[{"url":"#space-filling-designs","title":"Space-Filling Designs"}]}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)"},"tableOfContents":{"items":[{"url":"#creating-a-d-optimal-design-in-jmp-13","title":"Creating a D-Optimal design in JMP 13:"}]}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials"},"tableOfContents":{"items":[{"url":"#fractional-factorial","title":"Fractional Factorial"},{"url":"#creating-fractional-factorial-designs-in-jmp-13","title":"Creating Fractional Factorial Designs in JMP 13:"}]}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-9-Cases"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays"},"tableOfContents":{"items":[{"url":"#creating-a-combinatorial-design-in-acts","title":"Creating a Combinatorial Design in ACTS:"},{"url":"#example-of-a-combinatorial-design","title":"Example of a Combinatorial Design"}]}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-3-Power"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-1-Replication"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design"},"tableOfContents":{"items":[{"url":"#best-practices","title":"Best Practices"},{"url":"#pitfalls","title":"Pitfalls:"}]}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-5-One-Voice"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-6-Templates"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS"},"tableOfContents":{"items":[{"url":"#how-do-i-select-a-design","title":"How do I Select a Design?"},{"url":"#i-have-factors-that-are-hard-to-change","title":"I Have Factors that Are Hard to Change"},{"url":"#can-i-combine-developmental-test-and-operational-test-data","title":"Can I Combine Developmental Test and Operational Test Data?"},{"url":"#i-have-disallowed-combinations","title":"I Have Disallowed Combinations"},{"url":"#my-power-is-too-low","title":"My Power Is Too Low"},{"url":"#i-have-factor-levels-that-depend-on-other-factor-levels","title":"I Have Factor Levels that Depend on Other Factor Levels"}]}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes"},"tableOfContents":{"items":[{"url":"#fn1","title":"fn1"},{"url":"#fn2","title":"fn2"},{"url":"#fn3","title":"fn3"},{"url":"#fn4","title":"fn4"},{"url":"#fn5","title":"fn5"},{"url":"#fn6","title":"fn6"},{"url":"#fn7","title":"fn7"},{"url":"#fn8","title":"fn8"},{"url":"#fn9","title":"fn9"},{"url":"#fn10","title":"fn10"},{"url":"#fn11","title":"fn11"},{"url":"#fn12","title":"fn12"},{"url":"#fn13","title":"fn13"},{"url":"#fn14","title":"fn14"},{"url":"#fn15","title":"fn15"},{"url":"#fn16","title":"fn16"},{"url":"#fn17","title":"fn17"},{"url":"#fn18","title":"fn18"},{"url":"#fn19","title":"fn19"},{"url":"#fn20","title":"fn20"},{"url":"#fn21","title":"fn21"},{"url":"#fn22","title":"fn22"},{"url":"#fn23","title":"fn23"},{"url":"#fn24","title":"fn24"},{"url":"#fn25","title":"fn25"},{"url":"#fn26","title":"fn26"},{"url":"#fn27","title":"fn27"},{"url":"#fn28","title":"fn28"},{"url":"#fn29","title":"fn29"},{"url":"#fn30","title":"fn30"},{"url":"#fn31","title":"fn31"},{"url":"#fn32","title":"fn32"},{"url":"#fn33","title":"fn33"},{"url":"#fn34","title":"fn34"},{"url":"#fn35","title":"fn35"},{"url":"#fn36","title":"fn36"},{"url":"#fn37","title":"fn37"},{"url":"#fn38","title":"fn38"},{"url":"#fn39","title":"fn39"},{"url":"#fn40","title":"fn40"},{"url":"#fn41","title":"fn41"}]}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options"},"tableOfContents":{"items":[{"url":"#display","title":"Display:"},{"url":"#proofing","title":"Proofing:"},{"url":"#advanced","title":"Advanced:"}]}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-9-Styles"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-1-Acronyms"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-7-Capitalization"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-2-Tables"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-3-Figures"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING"},"tableOfContents":{"items":[{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#reporting","title":"Reporting"}]}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION"},"tableOfContents":{"items":[{"url":"#evaluation-structure","title":"Evaluation Structure"}]}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT"},"tableOfContents":{"items":[{"url":"#measures-overview","title":"Measures Overview"},{"url":"#qualities-of-a-good-measure-set","title":"Qualities of a Good Measure Set"}]}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT"},"tableOfContents":{"items":[{"url":"#developing-measures-of-effectiveness","title":"Developing Measures of Effectiveness"},{"url":"#developing-measures-of-performance-and-measures-of-suitability","title":"Developing Measures of Performance and Measures of Suitability"}]}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION"},"tableOfContents":{"items":[{"url":"#measures-worksheet-overview","title":"Measures Worksheet Overview"},{"url":"#measures-worksheet-header","title":"Measures Worksheet Header"},{"url":"#body-of-the-measures-worksheet","title":"Body of the Measures Worksheet"},{"url":"#formatting-measures","title":"Formatting Measures"}]}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES"},"tableOfContents":{"items":[{"url":"#measures-overview","title":"Measures Overview"},{"url":"#composite-measures","title":"Composite Measures"}]}}},{"node":{"fields":{"slug":"/acronyms"},"tableOfContents":{}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES"},"tableOfContents":{"items":[{"url":"#continuous-measures","title":"Continuous Measures"},{"url":"#discrete-measures","title":"Discrete Measures"},{"url":"#composite-measures","title":"Composite Measures"}]}}}],"group":[{"nodes":[{"tableOfContents":{"items":[{"url":"#2-letter-coord-of-air-force-operation-test-and-evaluation-center-produced-documentsbriefings-8-work-days","title":"2 Letter Coord of Air Force Operation Test and Evaluation Center-Produced Documents/Briefings (8 Work Days)"},{"url":"#commanderexecutive-director-briefing-request","title":"Commander/Executive Director Briefing Request"},{"url":"#command-section-coord-process-maximum-of-7-work-days","title":"Command Section Coord Process (Maximum of 7 Work Days)"},{"url":"#other-product-review-processes","title":"Other Product Review Processes"},{"url":"#things-to-consider-when-producing-documents-for-coordinationreview","title":"Things to Consider when Producing Documents for Coordination/Review","items":[{"url":"#drafting-plansreports-and-briefings","title":"Drafting Plans/Reports and Briefings:"},{"url":"#actionable-comments","title":"Actionable Comments"},{"url":"#meeting-external-suspenses","title":"Meeting External Suspenses"}]},{"url":"#accreditation-plansreports","title":"Accreditation Plans/Reports"},{"url":"#joint-reliability-maintainability-evaluation-team-charters","title":"Joint Reliability, Maintainability Evaluation Team Charters"}]},"fields":{"slug":"/OT&E_Guide/6-6-acap"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#reporting","title":"Reporting"}]},"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#continuous-measures","title":"Continuous Measures"},{"url":"#discrete-measures","title":"Discrete Measures"},{"url":"#composite-measures","title":"Composite Measures"}]},"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#measures-overview","title":"Measures Overview"},{"url":"#composite-measures","title":"Composite Measures"}]},"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/1-6-Acquisition-Implications-of-Verification,-Validation-and-Accreditation"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/1-5-acquisition-pathways"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/2-1-Acronyms"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/acronyms"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/1-6-art-principles"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/2-5-Air-Force-Agency-for-Modeling-and-Simulation"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/3-8-Apostrophes"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/2-3-Augmented-Designs"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#researching-the-capability-or-system-being-acquired","title":"Researching the Capability or System Being Acquired"},{"url":"#battlespace-depiction","title":"Battlespace Depiction","items":[{"url":"#the-evaluation-view","title":"The Evaluation View"},{"url":"#the-evaluation-view-1","title":"The Evaluation View 1"},{"url":"#the-evaluation-view-2","title":"The Evaluation View 2"},{"url":"#capability-requirements-mapping","title":"Capability Requirements Mapping"},{"url":"#mission-statement","title":"Mission Statement"},{"url":"#critical-operational-issues","title":"Critical Operational Issues"},{"url":"#operations","title":"Operations"}]},{"url":"#operational-employment-and-support-conditions","title":"Operational Employment and Support Conditions","items":[{"url":"#measures-of-effectiveness","title":"Measures of Effectiveness"},{"url":"#operational-conditions-factors-and-levels","title":"Operational Conditions (Factors and Levels)"},{"url":"#identify-factors-and-levels","title":"Identify Factors and Levels."},{"url":"#prioritizing-factors","title":"Prioritizing Factors"}]},{"url":"#operational-capabilities","title":"Operational Capabilities"}]},"fields":{"slug":"/OTE_construct_development_guide/1-8-Battlespace-Development"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#best-practices","title":"Best Practices"},{"url":"#pitfalls","title":"Pitfalls:"}]},"fields":{"slug":"/analyst_test_design_guide/4-4-Best-Practices-and-Pitfalls-in-Test-Design"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/2-7-Best-Practices"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/2-6-Blank-Pages"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/4-2-Blocking"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#define-the-what","title":"Define the \"What\"","items":[{"url":"#system-under-test","title":"System Under Test"},{"url":"#measures","title":"Measures"},{"url":"#criteria-and-thresholds","title":"Criteria and Thresholds"},{"url":"#data-and-data-elements","title":"Data and Data Elements"},{"url":"#effectiveness-and-suitability","title":"Effectiveness and Suitability"},{"url":"#coi-operations-measures-data-hierarchy","title":"COI-Operations-Measures-Data Hierarchy"},{"url":"#conditions","title":"Conditions"},{"url":"#operational-capabilities","title":"Operational Capabilities"}]},{"url":"#test-design","title":"Test Design","items":[{"url":"#test-design-goal","title":"Test Design Goal"},{"url":"#test-designs","title":"Test Designs"}]},{"url":"#test-execution","title":"Test Execution","items":[{"url":"#test-capabilities","title":"Test Capabilities"},{"url":"#verification-validation-and-accreditation","title":"Verification, Validation, and Accreditation"},{"url":"#data-management","title":"Data Management"},{"url":"#detailed-test-procedures","title":"Detailed Test Procedures"},{"url":"#limitations","title":"Limitations"},{"url":"#resourcing-test-events","title":"Resourcing Test Events"},{"url":"#technical-reviews","title":"Technical Reviews"},{"url":"#test-plans","title":"Test Plans"},{"url":"#administrative-considerations","title":"Administrative Considerations"},{"url":"#executing-the-test","title":"Executing the Test"}]},{"url":"#analysis-and-evaluation","title":"Analysis and Evaluation","items":[{"url":"#inspection","title":"Inspection"},{"url":"#analysis","title":"Analysis"},{"url":"#evaluation","title":"Evaluation"},{"url":"#effectiveness-and-suitability-1","title":"Effectiveness and Suitability"},{"url":"#reporting-ratings","title":"Reporting Ratings"},{"url":"#deficiency-reporting","title":"Deficiency Reporting"},{"url":"#exit-criteria-assessment","title":"Exit Criteria Assessment"}]},{"url":"#conclusions-and-documenting","title":"Conclusions and Documenting"}]},"fields":{"slug":"/OT&E_Guide/4-4-building-the-ot-construct"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/2-7-Capitalization"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide/6-7-case-study"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/2-9-Cases"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/1-6-Characterize"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/3-9-Choppy-Sentences"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/2-8-Citing-Air-Force-(or-Other-Military)-Bases"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/5-2-Classification-Markings"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#creating-a-combinatorial-design-in-acts","title":"Creating a Combinatorial Design in ACTS:"},{"url":"#example-of-a-combinatorial-design","title":"Example of a Combinatorial Design"}]},"fields":{"slug":"/analyst_test_design_guide/2-7-Combinatorial-Designs-Covering-Arrays"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/2-2-Commas"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/1-7-Compare"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/3-7-Comparing-Measures-of-Merit"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/5-6-Configuration-Control"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/1-4-Consistency-is-Key"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OTE_construct_development_guide/1-7-Construct-Development-Meetings"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#handling-information-requests","title":"Handling Information Requests"},{"url":"#marking-and-protecting-data","title":"Marking and Protecting Data"},{"url":"#distribution-statements","title":"Distribution Statements"},{"url":"#test-program-case-file","title":"Test Program Case File"},{"url":"#impact-of-system-modifications","title":"Impact of System Modifications"},{"url":"#visual-information-documentation","title":"Visual Information Documentation"}]},"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#directorate-roles-and-responsibilities","title":"Directorate Roles and Responsibilities"},{"url":"#signature-and-approval","title":"Signature and Approval"}]},"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/3-5-Correlation-Multicollinearity"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/4-2-Dates"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/2-8-Demonstrations"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#space-filling-designs","title":"Space-Filling Designs"}]},"fields":{"slug":"/analyst_test_design_guide/2-4-Designs-for-Computer-Experiments"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/5-3-Distribution-List"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OTE_construct_development_guide/2-4-Documenting-the-Operational-Test-and-Evaluation-Construct"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#critical-operational-issues-and-operations","title":"Critical Operational Issues and Operations"},{"url":"#response-variables","title":"Response Variables"}]},"fields":{"slug":"/analyst_test_design_guide/1-3-ELEMENTS-OF-THE-TEST-PLANNING-PROCESS"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/4-7-Embedded-Files"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#mission-statement-in-an-evaluation-summary-chart","title":"Mission Statement in an Evaluation Summary Chart"},{"url":"#critical-operational-issues-in-an-evaluation-summary-chart","title":"Critical Operational Issues in an Evaluation Summary Chart"},{"url":"#mission-effects-in-an-evaluation-summary-chart","title":"Mission Effects in an Evaluation Summary Chart"},{"url":"#operational-capability-requirements-in-an-evaluation-summary-chart","title":"Operational Capability Requirements in an Evaluation Summary Chart"}]},"fields":{"slug":"/OTE_construct_development_guide/1-9-Evaluation-Summary-Chart"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/evaluation_and_reporting_guide"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/1-3-Executive-Summary,-Body,-and-Appendices"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#fractional-factorial","title":"Fractional Factorial"},{"url":"#creating-fractional-factorial-designs-in-jmp-13","title":"Creating Fractional Factorial Designs in JMP 13:"}]},"fields":{"slug":"/analyst_test_design_guide/2-1-Factorials"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/1-4-Factors,-Levels,-and-Prioritization"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#afotecs-role-in-fielding-combat-capability","title":"AFOTECs Role in Fielding Combat Capability"}]},"fields":{"slug":"/OT&E_Guide/1-3-fielding-combat-capes"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/3-3-Figures"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/1-8-Focus-Areas"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#fn1","title":"fn1"},{"url":"#fn2","title":"fn2"},{"url":"#fn3","title":"fn3"},{"url":"#fn4","title":"fn4"},{"url":"#fn5","title":"fn5"},{"url":"#fn6","title":"fn6"},{"url":"#fn7","title":"fn7"},{"url":"#fn8","title":"fn8"},{"url":"#fn9","title":"fn9"},{"url":"#fn10","title":"fn10"},{"url":"#fn11","title":"fn11"},{"url":"#fn12","title":"fn12"},{"url":"#fn13","title":"fn13"},{"url":"#fn14","title":"fn14"},{"url":"#fn15","title":"fn15"},{"url":"#fn16","title":"fn16"},{"url":"#fn17","title":"fn17"},{"url":"#fn18","title":"fn18"},{"url":"#fn19","title":"fn19"},{"url":"#fn20","title":"fn20"},{"url":"#fn21","title":"fn21"},{"url":"#fn22","title":"fn22"},{"url":"#fn23","title":"fn23"},{"url":"#fn24","title":"fn24"},{"url":"#fn25","title":"fn25"},{"url":"#fn26","title":"fn26"},{"url":"#fn27","title":"fn27"},{"url":"#fn28","title":"fn28"},{"url":"#fn29","title":"fn29"},{"url":"#fn30","title":"fn30"},{"url":"#fn31","title":"fn31"},{"url":"#fn32","title":"fn32"},{"url":"#fn33","title":"fn33"},{"url":"#fn34","title":"fn34"},{"url":"#fn35","title":"fn35"},{"url":"#fn36","title":"fn36"},{"url":"#fn37","title":"fn37"},{"url":"#fn38","title":"fn38"},{"url":"#fn39","title":"fn39"},{"url":"#fn40","title":"fn40"},{"url":"#fn41","title":"fn41"}]},"fields":{"slug":"/analyst_test_design_guide/4-8-Footnotes"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/fn_guides"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/1-5-GOALS-AND-TYPES-OF-TEST"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/glossary"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/3-1-Governance"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/2-4-Headers-and-Footers"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/3-7-Hyphens,-En-Dashes,-and-Em-Dashes"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/lessons_learned_guide/1-2-INTRODUCTION-AND-INTENT"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/evaluation_and_reporting_guide/2-INTRODUCTION"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/measures_guide/2-INTRODUCTION"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/1-1-introduction"}}]},{"nodes":[{"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"}]}]},"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/lessons_learned_guide"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/measures_guide"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#display","title":"Display:"},{"url":"#proofing","title":"Proofing:"},{"url":"#advanced","title":"Advanced:"}]},"fields":{"slug":"/editing_reports_guide/1-7-Microsoft-Word-Options"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/2-6-Modeling-and-Simulation-Coordination-Office"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/2-3-Next-Page-and-Page-Breaks"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/3-1-Numbering-Tables-and-Figures"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/4-1-Numbers"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide/4-3-OT-construct"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/4-2-OT-test-activity-cycles"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OTE_construct_development_guide"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/1-2-OVERVIEW"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/1-5-One-Voice"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#about","title":"About"},{"url":"#app-notes","title":"App Notes"},{"url":"#credits","title":"Credits","items":[{"url":"#the-ote-guide-team-is","title":"The OT&E Guide Team is:"},{"url":"#the-app-team-is","title":"The App Team is:"}]}]},"fields":{"slug":"/"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OTE_construct_development_guide/1-5-Operational-Test-and-Evaluation-Test-Activity-Cycles"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#creating-a-d-optimal-design-in-jmp-13","title":"Creating a D-Optimal design in JMP 13:"}]},"fields":{"slug":"/analyst_test_design_guide/2-2-Optimal-Designs-(Computer-Generated-Designs)"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/2-5-Page-Numbering"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/5-1-Patches"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/3-2-Points-of-Contact"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/lessons_learned_guide/1-4-Policy-Guidance"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/3-3-Power"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/1-8-Problem-Identification"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/3-9-Randomization"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/2-9-References-and-Resources"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/4-1-Replication"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/6-3-resources"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide/6-2-risk-management"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#measures-overview","title":"Measures Overview"},{"url":"#qualities-of-a-good-measure-set","title":"Qualities of a Good Measure Set"}]},"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#developing-measures-of-effectiveness","title":"Developing Measures of Effectiveness"},{"url":"#developing-measures-of-performance-and-measures-of-suitability","title":"Developing Measures of Performance and Measures of Suitability"}]},"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#measures-worksheet-overview","title":"Measures Worksheet Overview"},{"url":"#measures-worksheet-header","title":"Measures Worksheet Header"},{"url":"#body-of-the-measures-worksheet","title":"Body of the Measures Worksheet"},{"url":"#formatting-measures","title":"Formatting Measures"}]},"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#evaluation-structure","title":"Evaluation Structure"}]},"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#environment-safety-and-occupational-health","title":"ENVIRONMENT, SAFETY AND OCCUPATIONAL HEALTH"},{"url":"#safety-database-and-tools","title":"Safety Database and Tools"},{"url":"#planning-and-review-process","title":"Planning and Review Process"},{"url":"#health-and-safety-plan","title":"Health and Safety Plan"},{"url":"#integrated-safety-review-board","title":"Integrated Safety Review Board"},{"url":"#environment-safety-and-occupational-health-certification-board","title":"Environment, Safety and Occupational Health Certification Board"}]},"fields":{"slug":"/safety_risk_mgmt_guide"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist"}}]},{"nodes":[{"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"}]}]},"fields":{"slug":"/OT&E_Guide/3-2-standing-activities"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#strategy-planning-and-programming-process","title":"STRATEGY, PLANNING, AND PROGRAMMING PROCESS"}]},"fields":{"slug":"/strat_planning_programming_guide"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/1-9-Styles"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/2-8-Summary"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/4-5-Symbols-and-Units-of-Measure"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/evaluation_and_reporting_guide/3-TEST-ACTIVITY-SEQUENCE"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/3-2-TEST-DESIGN-MEASURES-OF-MERIT"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/3-8-THE-THREE-PRINCIPLES-OF-DESIGN-OF-EXPERIMENTS"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/1-9-TYPES-OF-TEST-DESIGNS"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#how-do-i-select-a-design","title":"How do I Select a Design?"},{"url":"#i-have-factors-that-are-hard-to-change","title":"I Have Factors that Are Hard to Change"},{"url":"#can-i-combine-developmental-test-and-operational-test-data","title":"Can I Combine Developmental Test and Operational Test Data?"},{"url":"#i-have-disallowed-combinations","title":"I Have Disallowed Combinations"},{"url":"#my-power-is-too-low","title":"My Power Is Too Low"},{"url":"#i-have-factor-levels-that-depend-on-other-factor-levels","title":"I Have Factor Levels that Depend on Other Factor Levels"}]},"fields":{"slug":"/analyst_test_design_guide/4-3-TYPICAL-SITUATIONS"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/5-7-Table-of-Contents"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/3-2-Tables"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#initial-tasking-order","title":"Initial Tasking Order"},{"url":"#tasking-order-update","title":"Tasking Order Update"},{"url":"#program-transfer","title":"Program Transfer"}]},"fields":{"slug":"/OT&E_Guide/6-1-1-tasking"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/6-1-3-team-training"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/4-7-Technical-References-and-Citations"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/1-6-Templates"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/4-4-Terms"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#purpose","title":"PURPOSE","items":[{"url":"#definition","title":"Definition"},{"url":"#support-goals","title":"Support Goals"}]},{"url":"#test-range-and-facility-capabilities","title":"TEST RANGE AND FACILITY CAPABILITIES"},{"url":"#existing-test-capability-identification","title":"EXISTING TEST CAPABILITY IDENTIFICATION"},{"url":"#test-capability-gap-identification","title":"TEST CAPABILITY GAP IDENTIFICATION"},{"url":"#test-capability-gap-support-and-reporting","title":"TEST CAPABILITY GAP SUPPORT AND REPORTING"},{"url":"#munitions-management","title":"MUNITIONS MANAGEMENT"},{"url":"#test-resource-plan-requirements-verification-and-feedback","title":"TEST RESOURCE PLAN REQUIREMENTS VERIFICATION AND FEEDBACK"}]},"fields":{"slug":"/test_capability_guide"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/4-6-Test-Design-Guidance"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#test-design-goals","title":"Test Design Goals"},{"url":"#types-of-test-design","title":"Types of Test Design"},{"url":"#factor-management","title":"Factor Management"},{"url":"#unconstrained-and-constrained-events","title":"Unconstrained and Constrained events"},{"url":"#statistical-measures-of-merit","title":"Statistical Measures of Merit"},{"url":"#test-events","title":"Test Events"},{"url":"#test-design-validations","title":"Test Design Validations"}]},"fields":{"slug":"/OTE_construct_development_guide/2-1-Test-Design"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/2-5-Test-Designs-for-Comparing-Systems"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/analyst_test_design_guide/2-6-Test-Designs-for-Problem-Identification"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#test-methodology","title":"Test Methodology"},{"url":"#test-scenarios","title":"Test Scenarios"},{"url":"#test-capability-needs-and-shortfalls","title":"Test Capability Needs and Shortfalls","items":[{"url":"#time-phased-investment-document","title":"Time-Phased Investment Document"},{"url":"#determining-range-requirements","title":"Determining Range Requirements"},{"url":"#range-requirement-identification","title":"Range Requirement Identification"},{"url":"#range-selection-considerations","title":"Range Selection Considerations"},{"url":"#national-cyber-range-considerations","title":"National Cyber Range Considerations"},{"url":"#test-targets","title":"Test Targets"},{"url":"#range-safety-considerations","title":"Range Safety Considerations"},{"url":"#range-instrumentation-considerations","title":"Range Instrumentation Considerations"},{"url":"#range-data-processing-considerations","title":"Range Data Processing Considerations"},{"url":"#test-article-instrumentation","title":"Test Article Instrumentation"},{"url":"#program-introduction-document-release-authority","title":"Program Introduction Document Release Authority"}]},{"url":"#the-use-of-modeling-and-simulation","title":"The Use of Modeling and Simulation"},{"url":"#test-capability-accreditation","title":"Test Capability Accreditation"},{"url":"#test-constraints-and-limitations","title":"Test Constraints and Limitations"},{"url":"#basis-of-estimate-for-test-resources","title":"Basis of Estimate for Test Resources"},{"url":"#initial-resource-estimates","title":"Initial Resource Estimates"}]},"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview"}}]},{"nodes":[{"tableOfContents":{"items":[{"url":"#exit-criteria","title":"Exit Criteria"}]},"fields":{"slug":"/OT&E_Guide/5-test-lifecycle-exit"}}]},{"nodes":[{"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"}]},"fields":{"slug":"/OT&E_Guide/3-3-test-strategy"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OTE_construct_development_guide/1-3-The-Operational-Test-and-Evaluation-Construct"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/OTE_construct_development_guide/1-6-Using-a-Core-Team-Approach."}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/2-9-Vertical-Lists"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/lessons_learned_guide/1-3-Vocabulary-of-Lessons-Learned"}}]},{"nodes":[{"tableOfContents":{},"fields":{"slug":"/editing_reports_guide/3-6-Wordiness"}}]}]}}} \ No newline at end of file diff --git a/sites/oteguide/page-data/sq/d/2619113677.json b/sites/oteguide/page-data/sq/d/2619113677.json index 0c53d03b..a23bff5a 100644 --- a/sites/oteguide/page-data/sq/d/2619113677.json +++ b/sites/oteguide/page-data/sq/d/2619113677.json @@ -1 +1 @@ -{"data":{"allMdx":{"edges":[{"node":{"fields":{"slug":"/OT&E_Guide","title":"OT&E Guide"}}},{"node":{"fields":{"slug":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation 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/3-1-involvement-decision","title":"Involvement Decision"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-2-standing-activities","title":"Standing Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-3-test-strategy","title":"Test Strategy"}}},{"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/4-3-OT-construct","title":"OT&E Construct"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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":"/fn_guides/accreditation_guide","title":"Accreditation Guide"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/fn_guides/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/fn_guides/editing_reports_guide","title":"Editing Guide"}}},{"node":{"fields":{"slug":"/fn_guides/strat_planning_programming_guide","title":"Strategy, Planning, and Programming Guide"}}},{"node":{"fields":{"slug":"/fn_guides/safety_risk_mgmt_guide","title":"Safety Risk Management Guide"}}},{"node":{"fields":{"slug":"/fn_guides/test_capability_guide","title":"Test Capability Guide"}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/fn_guides/OTE_construct_development_guide","title":"OT&E Test Construct Development Guide"}}},{"node":{"fields":{"slug":"/fn_guides/evaluation_and_reporting_guide","title":"Evaluation and Reporting Guide"}}},{"node":{"fields":{"slug":"/fn_guides/analyst_test_design_guide","title":"Analyst Test Design Guide"}}},{"node":{"fields":{"slug":"/fn_guides/measures_guide","title":"Measures Guide"}}}]}}} \ No newline at end of file +{"data":{"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}}} \ No newline at end of file diff --git a/sites/oteguide/page-data/strat_planning_programming_guide/page-data.json b/sites/oteguide/page-data/strat_planning_programming_guide/page-data.json new file mode 100644 index 00000000..3267d3ca --- /dev/null +++ b/sites/oteguide/page-data/strat_planning_programming_guide/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/strat_planning_programming_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"8d8a2a54-3669-59d5-b415-28a0567cb65c","title":"Strategy, Planning, and Programming Guide","slug":"/strat_planning_programming_guide"},"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\": \"Strategy, Planning, and Programming Guide\",\n \"metaTitle\": \"Strategy, Planning, and Programming Guide\",\n \"metaDescription\": \"Strategy, Planning, and Programming Guide\"\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, \"Last Updated/Reviewed: 28 October 2020\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-5/8\"), mdx(\"h1\", null, \"STRATEGY, PLANNING, AND PROGRAMMING PROCESS\"), mdx(\"p\", null, \"The Strategy, Planning, and Programming Process (SP3) is located on the\\nA-5/8 shared drive. References include a Guide and a Process Chart that\\nA-5/8 periodically updates.\"), mdx(\"p\", null, \"SP3 is the means by which \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" generates its short and long term\\nplans, assesses the risks to those plans, and identifies the actions\\nneeded to reduce risk and achieve the plans. The process is repeatable,\\ndefined, defendable and transparent, and provides timely \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nCommander engagement. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"/A5/8 is the responsible SP3 \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\norganization. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" SP3 incorporates \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" guidance and the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nCommander's guidance to produce three basic products: the annual Program\\nObjective Memorandum (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \") submission to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters Air Force\"\n }, \"HAF\"), \"; the annual Planning\\nChoices submission to \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Headquarters Air Force\"\n }, \"HAF\"), \"; and a prioritized Time-Phased Investment\\nDocument (T\\u2011PhID) document for submission to the various \", 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\\nInfrastructure resource organizations.\"), mdx(\"p\", null, \"The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \" provides resource allocation decisions in response to strategic\\nplanning and programming guidance. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \" is a major document in the\\nPlanning, Programming, Budgeting, and Execution (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Planning, Programming, Budgeting, and Execution\"\n }, \"PPBE\"), \") process, and is\\nthe basis for budget estimates. The \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \" is the principal programming\\ndocument that proposes how a Component will respond to the Defense\\nPlanning Guidance (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Defense Planning Guidance\"\n }, \"DPG\"), \") and satisfy assigned functions over the Future\\nYears Defense Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Future Years Defense Program\"\n }, \"FYDP\"), \"). \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A5/8 submits the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \"\\nCommander-approved \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \" summarizing required manpower, resources, and\\nequipment associated with the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" operational test (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Operational Test\"\n }, \"OT\"), \") mission.\\n\", mdx(\"em\", {\n parentName: \"p\"\n }, \"(\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" A-8P)\")), mdx(\"p\", null, \"The Planning Choices submission is similar to the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \", and provides\\nfuture resource allocation decisions in response to strategic planning\\nand programming guidance for the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Future Years Defense Program\"\n }, \"FYDP\"), \" beyond the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \". In general, the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"\\nCorporate process uses Planning Choice decisions to inform \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \"\\nsubmissions. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \" submissions must support future \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \" force structure and\\nposture designs. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A5/8 submits the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander-approved\\nPlanning Choices summarizing manpower, resources, and equipment\\nassociated with the \", 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\"), \" mission. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"(\", mdx(\"abbr\", {\n parentName: \"em\",\n \"title\": \"Point of Contact\"\n }, \"POC\"), \" A-8P)\")), mdx(\"p\", null, \"The prioritized Time-Phased Investment Document (T-PhID) document is\\nprovided to various \", 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\\norganizations. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" owns almost no test assets, and must rely on other\\n\", 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 assist in developing, managing, and\\nsustaining solutions. \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A5/8 submits the \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Commander-approved,\\nprioritized T-PhID requirements document to appropriate resource\\norganizations. \", mdx(\"em\", {\n parentName: \"p\"\n }, \"(POCs: A-5R and A-8Z)\")));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#strategy-planning-and-programming-process","title":"STRATEGY, PLANNING, AND PROGRAMMING PROCESS"}]},"parent":{"__typename":"File","relativePath":"strat_planning_programming_guide.md"},"frontmatter":{"metaTitle":"Strategy, Planning, and Programming Guide","metaDescription":"Strategy, Planning, and Programming Guide"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"8d8a2a54-3669-59d5-b415-28a0567cb65c"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/page-data/test_capability_guide/page-data.json b/sites/oteguide/page-data/test_capability_guide/page-data.json new file mode 100644 index 00000000..2704d072 --- /dev/null +++ b/sites/oteguide/page-data/test_capability_guide/page-data.json @@ -0,0 +1 @@ +{"componentChunkName":"component---src-templates-docs-js","path":"/test_capability_guide","result":{"data":{"site":{"siteMetadata":{"title":"AFOTEC OT&E Guide","docsLocation":""}},"mdx":{"fields":{"id":"25e79469-49b4-5029-be56-5fe334347bab","title":"Test Capability Guide","slug":"/test_capability_guide"},"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 Capability Guide\",\n \"metaTitle\": \"Test Capability Guide\",\n \"metaDescription\": \"Test Capability Guide\"\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, \"31 July 2020\"), mdx(\"p\", null, \"Last Updated/Reviewed: 26 February 2021\"), mdx(\"p\", null, \"Originating Office: \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" A-5/8\"), mdx(\"h1\", null, \"PURPOSE\"), mdx(\"p\", null, \"Enable \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Adaptive-Relevant Test\"\n }, \"ART\"), \" and reduce risk by identifying, supporting, and advocating\\nfor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test capability requirements.\"), mdx(\"h2\", null, \"Definition\"), mdx(\"p\", null, \"The infrastructure or support system necessary to enable an operator to\\nexercise a system in a combat realistic environment to include threats\\nand targets for the purpose of conducting an operational test or\\nassessment and/or an integrated developmental/operational test.\"), mdx(\"h2\", null, \"Support Goals\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provide accurate reference data on test range and facilities\\ncapabilities.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provide research and analysis on existing test capabilities to\\nsupport operational test planning needs.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Identify gaps in test capability that need to be filled to support\\nfuture operational test needs.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Prioritize, advocate, track, and report on solutions to test\\ncapability gaps.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provide feedback and support on weapons, munitions, and targets\\nplanning and allocation programming.\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Provide feedback on test resource plan (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Plan\"\n }, \"TRP\"), \") requirements to ensure\\naccurate support levels are being planned for and reported.\"))), mdx(\"h1\", null, \"TEST RANGE AND FACILITY CAPABILITIES\"), mdx(\"p\", null, \"Provide reference information on the capabilities of test ranges and\\nfacilities to enable the planning and execution of operational tests and\\nassessments in combat realistic environments to include threats and\\ntargets.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Range and Facilities Database (Capabilities, POCs, etc)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Resource Management Center\"\n }, \"TRMC\"), \" Database\"), mdx(\"ul\", {\n parentName: \"li\"\n }, mdx(\"li\", {\n parentName: \"ul\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"(US) Air Force\"\n }, \"AF\"), \"/\", mdx(\"abbr\", {\n parentName: \"li\",\n \"title\": \"Technical Editor OR Test Evaluation\"\n }, \"TE\"), \" List\"))), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Range and Facilities Briefs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Range Commanders Council (RCC) Briefs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Program Introduction Documents (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Introduction Document\"\n }, \"PID\"), \")/Statement of Capability (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Statement of Capabilities\"\n }, \"SOC\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"List of Training / Joint Exercises\"))), mdx(\"h1\", null, \"EXISTING TEST CAPABILITY IDENTIFICATION\"), mdx(\"p\", null, \"Provide support to test directors and the test team\\u2019s requests for test\\ncapability research and analysis, identifying existing test capabilities\\nto enable operational test planning and execution.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Capability Readiness Assessment\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Request a new \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessment\"\n }, \"TCRA\"), \" for your Test Program\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessment\"\n }, \"TCRA\"), \" Status Dashboard\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Completed \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"test capability readiness assessment\"\n }, \"TCRA\"), \" Archive\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Nevada Test and Training Range Test Capabilities\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Contact A-8Z\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Capabilities Slide\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Briefing Template (Contact A-3)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Resource Plan support\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Mission Applications Suite\"\n }, \"AMAS\"), \" (SharePoint Link)\"))), mdx(\"h1\", null, \"TEST CAPABILITY GAP IDENTIFICATION\"), mdx(\"p\", null, \"Provide support to identify test capability gaps to support multiple\\noperational test programs. Leveraging Intelligence data, emerging\\ntechnologies research, and operator experience to document \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\ncapability current and future needs.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Threat Intelligence Research\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Validated Online Lifecycle Threat\"\n }, \"VOLT\"), \" & TTL (Contact A-2N)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Capability Gap Research\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Gap Database\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" Test Team Input\"))), mdx(\"h1\", null, \"TEST CAPABILITY GAP SUPPORT AND REPORTING\"), mdx(\"p\", null, \"Provide support and advocate for projects which address \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Air Force Operational Test and Evaluation Center\"\n }, \"AFOTEC\"), \" test\\ncapability gaps. Supporting and tracking all applicable test capability\\ninvestment programs and the foreign material acquisition process.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Time-Phased Investment Document (T-PhID)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Monthly Report\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Capabilities Investment Programs\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Central Test & Evaluation Investment Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Central Test & Evaluation Investment Program\"\n }, \"CTEIP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Joint Aircraft Survivability Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Joint Aircraft Survivability Program\"\n }, \"JASP\"), \"\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Resource Enhancement Program (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Resource Enhancement Program\"\n }, \"REP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Threat Systems Working Group (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Threat Systems Working Group\"\n }, \"TSWG\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Investment Planning and Programming (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Test Investment Planning and Programming\"\n }, \"TIPP\"), \")\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Foreign Material Acquisition (FMA)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Call / Submission\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Submission\"))), mdx(\"h1\", null, \"MUNITIONS MANAGEMENT\"), mdx(\"p\", null, \"Provide support to test directors and the test teams to properly\\nforecast ammunitions, munitions, and aerial targets necessary to plan\\nand execute operational tests and assessments.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions, Missiles, and Target\"\n }, \"MMT\"), \" Allocation Requests\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Munitions, Missiles, and Target\"\n }, \"MMT\"), \" Support and Feedback on Test Resource Plans\"))), mdx(\"h1\", null, \"TEST RESOURCE PLAN REQUIREMENTS VERIFICATION AND FEEDBACK\"), mdx(\"p\", null, \"Provide support to test teams by soliciting, tracking, and reporting\\ntest resource needs and enabling program objective memorandum (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Objective Memorandum\"\n }, \"POM\"), \")\\ninputs, the Resource Requirements Board (\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Requirements Review Board\"\n }, \"RRB\"), \"), and data justification\\nfor \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \" funding letters.\"), mdx(\"ul\", null, mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Test Resource Plan Support\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"AFOTEC Mission Applications Suite\"\n }, \"AMAS\"), \" (Contact \", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Technology Reference Model OR Test Resource Manager\"\n }, \"TRM\"), \" and/or A-8P)\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Requirements Review Board\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"\", mdx(\"abbr\", {\n parentName: \"p\",\n \"title\": \"Program Executive Office / Officer\"\n }, \"PEO\"), \" Funding Letters\")), mdx(\"li\", {\n parentName: \"ul\"\n }, mdx(\"p\", {\n parentName: \"li\"\n }, \"Contractor Request Review Panel\"))));\n}\n;\nMDXContent.isMDXComponent = true;","tableOfContents":{"items":[{"url":"#purpose","title":"PURPOSE","items":[{"url":"#definition","title":"Definition"},{"url":"#support-goals","title":"Support Goals"}]},{"url":"#test-range-and-facility-capabilities","title":"TEST RANGE AND FACILITY CAPABILITIES"},{"url":"#existing-test-capability-identification","title":"EXISTING TEST CAPABILITY IDENTIFICATION"},{"url":"#test-capability-gap-identification","title":"TEST CAPABILITY GAP IDENTIFICATION"},{"url":"#test-capability-gap-support-and-reporting","title":"TEST CAPABILITY GAP SUPPORT AND REPORTING"},{"url":"#munitions-management","title":"MUNITIONS MANAGEMENT"},{"url":"#test-resource-plan-requirements-verification-and-feedback","title":"TEST RESOURCE PLAN REQUIREMENTS VERIFICATION AND FEEDBACK"}]},"parent":{"__typename":"File","relativePath":"test_capability_guide.md"},"frontmatter":{"metaTitle":"Test Capability Guide","metaDescription":"Test Capability Guide"}},"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":"/accreditation_guide","title":"Accreditation 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":"/fn_guides","title":"Functional Guides"}}},{"node":{"fields":{"slug":"/","title":"Operational Test & Evaluation Guide"}}},{"node":{"fields":{"slug":"/glossary","title":"Glossary"}}},{"node":{"fields":{"slug":"/lessons_learned_guide","title":"Lessons Learned Guide"}}},{"node":{"fields":{"slug":"/measures_guide","title":"Measures Guide"}}},{"node":{"fields":{"slug":"/strat_planning_programming_guide","title":"Strategy, Planning, and Programming 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":"/OT&E_Guide/1-1-introduction","title":"Introduction"}}},{"node":{"fields":{"slug":"/OT&E_Guide/2-test-lifecycle-overview","title":"Test Lifecycle Overview"}}},{"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/4-1-levels-of-test","title":"Levels of Test"}}},{"node":{"fields":{"slug":"/OT&E_Guide/3-1-involvement-decision","title":"Involvement Decision"}}},{"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-2-OT-test-activity-cycles","title":"OT&E Test Activity Cycles"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-0-ot-business-practices","title":"OT Business Practices"}}},{"node":{"fields":{"slug":"/OT&E_Guide/4-3-OT-construct","title":"OT&E Construct"}}},{"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-4-coordination-across-afotec","title":"Coordination Across AFOTEC"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-2-risk-management","title":"Risk Management"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-1-2-team-standup","title":"Team Stand-up"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-3-resources","title":"Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-4-Operational-Sufficiency-and-Technical-Adequacy","title":"Operational Sufficiency and Technical Adequacy"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-6-acap","title":"AFOTEC Collaborative Action Platform (ACAP)"}}},{"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/4-4-building-the-ot-construct","title":"Building the OT&E Construct and Test Activities"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-5-continuous-and-cumulative-feedback","title":"Continuous and Cumulative Feedback"}}},{"node":{"fields":{"slug":"/OT&E_Guide/6-7-case-study","title":"Case Study Review"}}},{"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-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-9-Evaluation-Summary-Chart","title":"Evaluation Summary Chart"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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/2-1-Test-Design","title":"Test Design"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-2-Measures-Development","title":"Measures Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-3-Test-Capability-Accreditation","title":"Test Capability Accreditation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-2-INTRODUCTION","title":"INTRODUCTION"}}},{"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":"/OTE_construct_development_guide/1-8-Battlespace-Development","title":"Battlespace Development"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-4-The-Use-of-Modeling-and-Simulation","title":"The Use of Modeling and Simulation"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-5-Verification,-Validation-and-Accreditation-Definitions","title":"Verification, Validation and Accreditation Definitions"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-7-Accreditation-Concepts","title":"Accreditation Concepts"}}},{"node":{"fields":{"slug":"/accreditation_guide/1-8-Risk-Matrix:-Example","title":"Risk Matrix: Example"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-2-Test-Capability-Accreditation-Concept","title":"Test Capability Accreditation Concept"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-1-Accreditation-Process","title":"Accreditation Process"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-3-Accreditation-Plan-and-Report-Format","title":"Accreditation Plan and Report Format"}}},{"node":{"fields":{"slug":"/accreditation_guide/2-4-Accreditation-References-and-Resources","title":"Accreditation References and Resources"}}},{"node":{"fields":{"slug":"/OTE_construct_development_guide/2-3-Test-Execution-Planning","title":"Test Execution Planning"}}},{"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-7-Best-Practices","title":"Best Practices"}}},{"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-2-Points-of-Contact","title":"Points of Contact "}}},{"node":{"fields":{"slug":"/accreditation_guide/1-9-Previous-Accreditation","title":"Previous Accreditation"}}},{"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-4-Factors,-Levels,-and-Prioritization","title":"Factors, Levels, and Prioritization"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/1-7-Compare","title":"Compare"}}},{"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-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-8-Demonstrations","title":"Demonstrations"}}},{"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-9-Cases","title":"Cases"}}},{"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/3-3-Power","title":"Power"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-1-Observational-Studies","title":"Observational Studies"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-4-Optimality-Efficiency","title":"Optimality (Efficiency)"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/3-6-Prediction-Variance","title":"Prediction Variance"}}},{"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-5-Correlation-Multicollinearity","title":"Correlation (Multicollinearity)"}}},{"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-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":"/analyst_test_design_guide/4-2-Blocking","title":"Blocking"}}},{"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":"/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-8-Focus-Areas","title":"Focus Areas"}}},{"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-9-Styles","title":"Styles"}}},{"node":{"fields":{"slug":"/analyst_test_design_guide/4-5-Appendices","title":"Appendices"}}},{"node":{"fields":{"slug":"/editing_reports_guide/2-2-Commas","title":"Commas"}}},{"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-1-Acronyms","title":"Acronyms"}}},{"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-5-Page-Numbering","title":"Page Numbering"}}},{"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":"/analyst_test_design_guide/4-7-Technical-References-and-Citations","title":"Technical References and Citations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/1-2-PURPOSE","title":"PURPOSE"}}},{"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-3-Figures","title":"Figures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-5-Copyrights-and-Trademarks","title":"Copyrights and Trademarks"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-6-Wordiness","title":"Wordiness"}}},{"node":{"fields":{"slug":"/editing_reports_guide/3-4-Passive-Voice","title":"Passive Voice"}}},{"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/3-8-Apostrophes","title":"Apostrophes"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-1-Numbers","title":"Numbers"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-2-Dates","title":"Dates"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-3-Abbreviations","title":"Abbreviations"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-4-Terms","title":"Terms"}}},{"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-7-Embedded-Files","title":"Embedded Files"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-6-Verb-Tenses","title":"Verb Tenses"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-8-Converting-Pictures","title":"Converting Pictures"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-1-Patches","title":"Patches"}}},{"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/5-6-Configuration-Control","title":"Configuration Control"}}},{"node":{"fields":{"slug":"/editing_reports_guide/4-9-References-and-Documentation","title":"References and Documentation"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-5-Spell-Check","title":"Spell Check"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-4-SF298-Report-Documentation-Page","title":"SF298 Report Documentation Page"}}},{"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":"/evaluation_and_reporting_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/editing_reports_guide/5-8-Standardization-Checklist","title":"Standardization Checklist "}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/4-ANALYSIS,-EVALUATION,-AND-REPORTING","title":"ANALYSIS, EVALUATION, AND REPORTING"}}},{"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-2-INTRODUCTION-AND-INTENT","title":"INTRODUCTION AND INTENT"}}},{"node":{"fields":{"slug":"/evaluation_and_reporting_guide/5-STRUCTURE-OF-AN-EVALUATION","title":"STRUCTURE OF AN EVALUATION"}}},{"node":{"fields":{"slug":"/lessons_learned_guide/1-5-PROCESS","title":"PROCESS"}}},{"node":{"fields":{"slug":"/measures_guide/2-INTRODUCTION","title":"INTRODUCTION"}}},{"node":{"fields":{"slug":"/measures_guide/3-SECTION-1-FUNDAMENTALS-OF-MEASUREMENT","title":"SECTION 1 FUNDAMENTALS OF MEASUREMENT"}}},{"node":{"fields":{"slug":"/measures_guide/4-SECTION-2-MEASURES-DEVELOPMENT","title":"SECTION 2 MEASURES DEVELOPMENT"}}},{"node":{"fields":{"slug":"/measures_guide/7-APPENDIX-B-MEASURE-REVIEW-QUICK-REFERENCE","title":"APPENDIX B MEASURE REVIEW QUICK REFERENCE"}}},{"node":{"fields":{"slug":"/measures_guide/5-SECTION-3-MEASURE-DOCUMENTATION","title":"SECTION 3 MEASURE DOCUMENTATION"}}},{"node":{"fields":{"slug":"/measures_guide/8-APPENDIX-C-CYBER-RELATED-MEASURES","title":"APPENDIX C CYBER-RELATED MEASURES "}}},{"node":{"fields":{"slug":"/acronyms","title":"Acronyms"}}},{"node":{"fields":{"slug":"/measures_guide/6-APPENDIX-A-CATEGORIES-OF-MEASURES","title":"APPENDIX A CATEGORIES OF MEASURES"}}}]}},"pageContext":{"id":"25e79469-49b4-5029-be56-5fe334347bab"}},"staticQueryHashes":["1685914912","1685914912","1928916242","1928916242","2619113677","2619113677"]} \ No newline at end of file diff --git a/sites/oteguide/fn_guides/safety_risk_mgmt_guide/index.html b/sites/oteguide/safety_risk_mgmt_guide/index.html similarity index 84% rename from sites/oteguide/fn_guides/safety_risk_mgmt_guide/index.html rename to sites/oteguide/safety_risk_mgmt_guide/index.html index 797f99fc..6a4bb217 100644 --- a/sites/oteguide/fn_guides/safety_risk_mgmt_guide/index.html +++ b/sites/oteguide/safety_risk_mgmt_guide/index.html @@ -1,4 +1,4 @@ -Safety Risk Management Guide

      Safety Risk Management Guide

      Last Updated/Reviewed: 08 December 2020

      Originating Office: AFOTEC SE

      ENVIRONMENT, SAFETY AND OCCUPATIONAL HEALTH

      The three basic principles of environment, safety, and occupational +Safety Risk Management Guide

      Safety Risk Management Guide

      Last Updated/Reviewed: 08 December 2020

      Originating Office: AFOTEC SE

      ENVIRONMENT, SAFETY AND OCCUPATIONAL HEALTH

      The three basic principles of environment, safety, and occupational health (ESOH) are to sustain readiness, leverage resources, and be a good neighbor. The test director (TD) is responsible for providing a safe and healthy workplace during test execution, enhancing mission @@ -127,7 +127,7 @@ the risk and endorse the ESOHCB Memo will be forwarded as "info" to the next higher decision authority as level of risk dictates (i.e., Det/TD to Det/DO to Det/CC to AFOTEC/CC). Coordination and approval of the ESOHCB Memo will be -accomplished prior to OT&E activities.

      \ No newline at end of file diff --git a/sites/oteguide/webpack.stats.json b/sites/oteguide/webpack.stats.json index 91089893..2e3d3a6c 100644 --- a/sites/oteguide/webpack.stats.json +++ b/sites/oteguide/webpack.stats.json @@ -1 +1 @@ -{"errors":[],"warnings":[],"namedChunkGroups":{"polyfill":{"chunks":[1,0,6],"assets":["webpack-runtime-989ddf52d489f6f735fc.js","webpack-runtime-989ddf52d489f6f735fc.js.map","commons-58ffe4445524790e8a26.js","commons-58ffe4445524790e8a26.js.map","polyfill-eb0d07966faded618939.js","polyfill-eb0d07966faded618939.js.map"],"children":{},"childAssets":{}},"app":{"chunks":[1,5,7,0,3],"assets":["webpack-runtime-989ddf52d489f6f735fc.js","webpack-runtime-989ddf52d489f6f735fc.js.map","framework-3e6dec6139dadaa7d0c7.js","framework-3e6dec6139dadaa7d0c7.js.map","styles.edc5de1cdab62f848f13.css","styles-9411612e31e4f14527d1.js","styles-9411612e31e4f14527d1.js.map","commons-58ffe4445524790e8a26.js","commons-58ffe4445524790e8a26.js.map","app-eec04d2f552ddc7b4bf2.js","app-eec04d2f552ddc7b4bf2.js.map"],"children":{},"childAssets":{}},"component---src-pages-404-js":{"chunks":[4],"assets":["component---src-pages-404-js-555291e02c08bfd2409a.js","component---src-pages-404-js-555291e02c08bfd2409a.js.map"],"children":{},"childAssets":{}},"component---src-templates-docs-js":{"chunks":[],"assets":[],"children":{},"childAssets":{}}},"assetsByChunkName":{"polyfill":["webpack-runtime-989ddf52d489f6f735fc.js","commons-58ffe4445524790e8a26.js","polyfill-eb0d07966faded618939.js"],"app":["webpack-runtime-989ddf52d489f6f735fc.js","framework-3e6dec6139dadaa7d0c7.js","styles.edc5de1cdab62f848f13.css","styles-9411612e31e4f14527d1.js","commons-58ffe4445524790e8a26.js","app-eec04d2f552ddc7b4bf2.js"],"component---src-pages-404-js":["component---src-pages-404-js-555291e02c08bfd2409a.js"],"component---src-templates-docs-js":[]}} \ No newline at end of file +{"errors":[],"warnings":[],"namedChunkGroups":{"polyfill":{"chunks":[1,0,6],"assets":["webpack-runtime-989ddf52d489f6f735fc.js","webpack-runtime-989ddf52d489f6f735fc.js.map","commons-58ffe4445524790e8a26.js","commons-58ffe4445524790e8a26.js.map","polyfill-eb0d07966faded618939.js","polyfill-eb0d07966faded618939.js.map"],"children":{},"childAssets":{}},"app":{"chunks":[1,5,7,0,3],"assets":["webpack-runtime-989ddf52d489f6f735fc.js","webpack-runtime-989ddf52d489f6f735fc.js.map","framework-3e6dec6139dadaa7d0c7.js","framework-3e6dec6139dadaa7d0c7.js.map","styles.edc5de1cdab62f848f13.css","styles-9411612e31e4f14527d1.js","styles-9411612e31e4f14527d1.js.map","commons-58ffe4445524790e8a26.js","commons-58ffe4445524790e8a26.js.map","app-03e333c274b6bc210459.js","app-03e333c274b6bc210459.js.map"],"children":{},"childAssets":{}},"component---src-pages-404-js":{"chunks":[4],"assets":["component---src-pages-404-js-555291e02c08bfd2409a.js","component---src-pages-404-js-555291e02c08bfd2409a.js.map"],"children":{},"childAssets":{}},"component---src-templates-docs-js":{"chunks":[],"assets":[],"children":{},"childAssets":{}}},"assetsByChunkName":{"polyfill":["webpack-runtime-989ddf52d489f6f735fc.js","commons-58ffe4445524790e8a26.js","polyfill-eb0d07966faded618939.js"],"app":["webpack-runtime-989ddf52d489f6f735fc.js","framework-3e6dec6139dadaa7d0c7.js","styles.edc5de1cdab62f848f13.css","styles-9411612e31e4f14527d1.js","commons-58ffe4445524790e8a26.js","app-03e333c274b6bc210459.js"],"component---src-pages-404-js":["component---src-pages-404-js-555291e02c08bfd2409a.js"],"component---src-templates-docs-js":[]}} \ No newline at end of file -- GitLab