{"id":616,"date":"2023-01-18T20:13:08","date_gmt":"2023-01-18T20:13:08","guid":{"rendered":"https:\/\/guide.dafdto.com\/?p=616"},"modified":"2023-04-11T12:15:28","modified_gmt":"2023-04-11T12:15:28","slug":"digital-considerations-for-acquisition-documents","status":"publish","type":"post","link":"https:\/\/guide.dafdto.com\/2023\/01\/18\/digital-considerations-for-acquisition-documents\/","title":{"rendered":"Digital Considerations for Acquisition Documents"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"616\" class=\"elementor elementor-616\" data-elementor-post-type=\"post\">\n\t\t\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-b15e3a5 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"b15e3a5\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-66 elementor-top-column elementor-element elementor-element-09d764a\" data-id=\"09d764a\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-8c066f3 elementor-widget elementor-widget-text-editor\" data-id=\"8c066f3\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<style>\/*! elementor - v3.20.0 - 13-03-2024 *\/\n.elementor-widget-text-editor.elementor-drop-cap-view-stacked .elementor-drop-cap{background-color:#69727d;color:#fff}.elementor-widget-text-editor.elementor-drop-cap-view-framed .elementor-drop-cap{color:#69727d;border:3px solid;background-color:transparent}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap{margin-top:8px}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap-letter{width:1em;height:1em}.elementor-widget-text-editor .elementor-drop-cap{float:left;text-align:center;line-height:1;font-size:50px}.elementor-widget-text-editor .elementor-drop-cap-letter{display:inline-block}<\/style>\t\t\t\t<div class=\"a_c_50a7110f a_c_50a7110f root-75 CanvasZone row CanvasZone--alignment CanvasZone--noMargin CanvasZone--read\" data-automation-id=\"CanvasZone\"><div class=\"k_c_50a7110f\"><div class=\"a_e_50a7110f q_e_50a7110f CanvasSection CanvasSection-col CanvasSection-sm12 CanvasSection--read CanvasSection-xl12\" data-automation-id=\"CanvasSection\"><div id=\"1212fc8d-dd6b-408a-8d5d-9f1cc787efbb\" class=\"ControlZone ControlZone--clean a_a_50a7110f\" data-automation-id=\"CanvasControl\"><div class=\"ControlZone--control\"><div class=\"rte-webpart\" data-sp-feature-tag=\"Rich Text Editor\" data-sp-feature-instance-id=\"1212fc8d-dd6b-408a-8d5d-9f1cc787efbb\"><div class=\"cke_editable rte--read rte--inline ckeditable_removeMargin highlightFocusFix blockQuoteFont orderedListStyling uniformSpacingForElements cke_editable rteEmphasis root-76\" data-automation-id=\"textBox\"><p>The DAF Digital Transformation Office (DTO) knows that as programs transform to incorporate digital acquisition, these core documents may still be required (i.e. will not be represented as source of truth within a model; or will be source of truth in a model yet still needed by Senior Acquisition Leaders in a document form) and will need to include digital acquisition planning information. \u00a0<\/p><\/div><\/div><\/div><\/div><\/div><\/div><\/div><div class=\"a_c_50a7110f a_c_50a7110f root-75 CanvasZone row CanvasZone--alignment CanvasZone--noMargin CanvasZone--read\" data-automation-id=\"CanvasZone\"><div class=\"k_c_50a7110f\"><div class=\"a_e_50a7110f n_e_50a7110f CanvasSection CanvasSection-col CanvasSection-sm12 CanvasSection--read CanvasSection-xl6\" data-automation-id=\"CanvasSection\"><div id=\"5e4c8539-a532-4694-a71a-c8bd479c9c22\" class=\"ControlZone ControlZone--clean a_a_50a7110f\" data-automation-id=\"CanvasControl\"><div class=\"ControlZone--control\"><div class=\"rte-webpart\" data-sp-feature-tag=\"Rich Text Editor\" data-sp-feature-instance-id=\"5e4c8539-a532-4694-a71a-c8bd479c9c22\"><div class=\"cke_editable rte--read rte--inline ckeditable_removeMargin highlightFocusFix blockQuoteFont orderedListStyling uniformSpacingForElements cke_editable rteEmphasis root-76\" data-automation-id=\"textBox\"><p>The DTO has looked at the core acquisition documents:\u00a0Acquisition Strategy Plan (ASP),\u00a0Systems Engineering Plan (SEP),\u00a0Test and Evaluation Master Plan (TEMP), and\u00a0Life Cycle Sustainment Plan (LCSP)\u00a0and provide the information below to help.\u00a0 The ASP template is located as a PowerPoint file available for download from the directory to the right.\u00a0 Also available for download are the word documents of the information that is located below for the SEP, TEMP and LCSP.\u00a0 As the DTO progresses these data products are expected to be updated, and we are open to comments from programs that will make these better products for the overall acquisition community.<\/p><\/div><\/div><\/div><\/div><\/div><\/div><\/div>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<div class=\"elementor-column elementor-col-33 elementor-top-column elementor-element elementor-element-26a9ec8\" data-id=\"26a9ec8\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-c1c15f4 elementor-widget elementor-widget-text-editor\" data-id=\"c1c15f4\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<ul><li><a href=\"https:\/\/guide.dafdto.com\/wp-content\/uploads\/2023\/01\/Acquisition-Strategy-Panel-ASP_Template_23FEB2021.pptx\">Click here to access the Acquisition Strategy Panel (ASP) Template<\/a><\/li><li><a href=\"https:\/\/guide.dafdto.com\/wp-content\/uploads\/2023\/01\/DOD-SEP-Outline-Version-4-September-2021.docx\">Click here to access the latest DoD SEP Outline<\/a><\/li><li><a href=\"https:\/\/guide.dafdto.com\/wp-content\/uploads\/2023\/01\/LCSP-Digital-Considerations-091020.docx\">Click here to access the LCSP Digital Considerations<\/a><\/li><li><a href=\"https:\/\/guide.dafdto.com\/wp-content\/uploads\/2023\/01\/TEMP-sections-to-address-DE-2020-1202-MLK.docx\">Click here to access the instructions for adding DE instructions into a TEMP<\/a><\/li><\/ul>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-2a2ff37 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"2a2ff37\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-b1af5c9\" data-id=\"b1af5c9\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-c6174a6 elementor-widget elementor-widget-text-editor\" data-id=\"c6174a6\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div><h2 id=\"acquisition-strategy-plan-(asp)\">Acquisition Strategy Plan (ASP):<\/h2><\/div><p><strong>Task 1:\u00a0 Identify areas within ASP template that need to address the DTO Objectives.<\/strong><\/p><ul><li>SAF\/AQX maintains the Acquisition Strategy briefing template for programs where the Service Acquisition Executive (SAE) is the Decision Authority (e.g. large MDAP ACAT I size programs).<\/li><li>Each Program Executive Officer directorate or program may tailor their ASP Templates as required.<\/li><li>DTO recommended updates were officially implemented as of Feb 2021.\u00a0 Changes were primarily implemented in the notes pages to support communication of Digital acquisition strategies and impacts. Programs should verify directorate\/division ASP template configuration with their Program Execution Group<\/li><li><p>Particular slides with significant content change includes:<\/p><ul><li><p>Business<\/p><ul><li>Slide 17 \u201cBusiness Strategy\u201d<\/li><li>Slide 19 \u201cCompetition Strategy\u201d<\/li><li>Slide 21 \u201cContract Incentives\u201d<\/li><li>Slide 22 \u201cIntellectual Property (IP) Strategy\u201d<\/li><li>Slide 35 \u201cProgram Office\u201d<\/li><\/ul><\/li><li>Technical<ul><li>Slide 24-25 \u201cSystems Engineering (SE)\u201d<\/li><li>Slide 26 \u201cDigital Engineering\/MBSE Strategy\u201d<\/li><li>Slide 29 \u201cProduct Support Strategy\/Digital Engineering\u201d<\/li><li>Slide 30 \u201cTest and Evaluation (T&amp;E)\u201d<\/li><li>Slide 38 &#8220;Agile Software Development&#8221;<\/li><\/ul><\/li><\/ul><\/li><li>These changes align with the\u00a0<a title=\"https:\/\/usaf.dps.mil\/:b:\/t\/afmcde\/EeVn0zRCp35EojClf_4_0OUBguy6xxryx6owrrNNe7v-wA?e=5XLJp0\" href=\"https:\/\/guide.dafdto.com\/wp-content\/uploads\/2023\/01\/Digitial-Building-Code-2022-Memo-Signature-Final.pdf\" data-cke-saved-href=\"https:\/\/usaf.dps.mil\/:b:\/t\/afmcde\/EeVn0zRCp35EojClf_4_0OUBguy6xxryx6owrrNNe7v-wA?e=5XLJp0\" data-interception=\"on\">SAF\/AQ Digital Building Code memo dated 2022<\/a>.\u00a0<\/li><\/ul>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-3e00e07 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"3e00e07\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-f1c84ee\" data-id=\"f1c84ee\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-fcd316e elementor-widget elementor-widget-text-editor\" data-id=\"fcd316e\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div><h2 id=\"systems-engineering-plan-(sep)\">Systems Engineering Plan (SEP):<\/h2><i class=\"f_b_1310c973 g_b_1310c973 css-92\" aria-hidden=\"true\"><\/i><\/div><p>This section of the page was updated on October 25, 2021.\u00a0 Previously this section listed several additions to the OSD SEP Outline version 3.0.\u00a0 Many of those additions were incorporated into version 4.0 of the OSD SEP Outline which can be found by clicking\u00a0<a href=\"https:\/\/guide.dafdto.com\/wp-content\/uploads\/2023\/01\/DOD-SEP-Outline-Version-4-September-2021.docx\">here<\/a>.\u00a0 The OSD Guidance, to include the SEP Outline, can be found on the\u00a0<a title=\"https:\/\/ac.cto.mil\/erpo\/\" href=\"https:\/\/ac.cto.mil\/erpo\/\" target=\"_blank\" rel=\"noopener\" data-cke-saved-href=\"https:\/\/ac.cto.mil\/erpo\/\" data-interception=\"off\">Engineering Reference for Program Offices<\/a>.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-6c877ac elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"6c877ac\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-f883c5e\" data-id=\"f883c5e\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-1ba8459 elementor-widget elementor-widget-text-editor\" data-id=\"1ba8459\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div><h2 id=\"test-and-evaluation-master-plan-(temp)\">Test and Evaluation Master Plan (TEMP)<\/h2><p>\u00a0<\/p><\/div><p><strong>Task 1: Identify areas within TEMP template that need to address transformation objectives.<\/strong><\/p><ul><li>Content is more important than format.\u00a0 Do not repeat content in the various sections, and consolidate as practicable.\u00a0 DOT&amp;E TEMP Guidebook 3.1, dated 19 Jan 2017, was used as the reference.\u00a0 The TEMP should be specific to the program and tailored to meet program needs.<\/li><li>Note: DOT&amp;E pilot program format (see 8 Apr 2019 memo) has a reduced number of sections (3).\u00a0 Therefore content may need to go in another section, or be incorporated via reference, for TEMPs using the abbreviated format.<\/li><\/ul><p>In the order appearing in the template:<\/p><ul><li>1.3.1 Program Background<ul><li>Include reference to Acquisition Strategy sections that address Digital Acquisition \/ Digital Engineering Objectives.\u00a0 The TEMP\u00a0<u>supports<\/u>\u00a0the Acquisition Strategy with a Test &amp; Evaluation Strategy.<\/li><li>Describe whether the program has chosen a\u00a0<i>model-supported, model integrated, or model-centric strategy<\/i>.\u00a0 A program\u2019s test strategy needs to reflect the acquisition strategy digital objectives and how they will be utilized\/supported.<ul><li>Is a Government Reference Model (GRM) and\/or Acquisition Reference Model (ARM) being used on the program?\u00a0 If so, testers need to understand the former, and help build the latter.<\/li><\/ul><\/li><\/ul><\/li><\/ul><ul><li>1.3.5 System Engineering Requirements<ul><li>Include reference to Systems Engineering Plan (SEP) sections addressing Digital Engineering Objectives.\u00a0 Expected new sections include:<ul><li>Modeling strategy<\/li><li>Key modeling activities<\/li><li>Technical reviews &#8211; how models used for continuous\/dynamic review vs. static data (i.e. PowerPoint charts)<\/li><\/ul><\/li><li>TEMP supports the SEP with a strategy to meet applicable systems engineering needs along and across the \u201cV\u201d \u2013 particularly system level verification.<\/li><li>Reference AF Digital Guide \u201cKey Digital Engineering Features\u201d product(s), and other applicable briefings.\u00a0 Explain how T&amp;E objectives are leveraging (or driving) key digital features chosen for the program.\u00a0<\/li><li>Examples:<ul><li>Will Technical Performance Measures (TPMs) status be available to all stakeholders via dynamic digital environment vs. monthly contractual updates via email to one particular group in the program office? \u00a0Describe here (or other section where program\u2019s Integrated Digital Environment (IDE) is explained) how this will be implemented to include Integrated Test Team (ITT) access.<\/li><li>If program is model-centric, describe early tester participation in building model frameworks\/views (e.g., the ARM) and populating with T&amp;E content.\u00a0 This will be necessary whenever models will be used to \u201coutput\u201d system level test plans, especially with resource-loaded content and schedule linkages.\u00a0<\/li><li>If program is model-supported or model-collaborative, then testers still need to collaborate with the prime contractor and program office via some defined level of access to models in order to begin detailed test planning.\u00a0 Examples include aircraft envelope expansion predictions and test point matrices.<\/li><\/ul><\/li><\/ul><\/li><\/ul><ul><li>2.2 Common T&amp;E Database Requirements<ul><li>This is required by AFI99-103, Para 5.18.\u00a0 Implementation is left to the program.<\/li><li>The requirement for a description of provisions\/methods for \u201c\u2026accessing, collecting, validating, and sharing data as it becomes available from contractor testing, Government DT, OT\u2026\u201d is already in the template.\u00a0 However, more detail specific to implementation of the intended digital environment is needed.\u00a0 The typical description seen in most TEMPs is very generic and needs more critical thought.\u00a0<\/li><li><i>Goal is an \u201c<\/i><i>Integrated Digital Environment<\/i><i>\u201d<\/i>\u00a0(link to illustration of one possible implementation only) that includes testers (DT &amp; OT), contractor, program office engineering, other functional specialties, independent certification authorities, and others designated as needing access by the ITT.<ul><li>The \u201cCommon T&amp;E Database\u201d could certainly be a subset of the program\u2019s IDE.<\/li><li>Describe \u201chow\u201d test data will be shared.\u00a0 Use references to other program documents when pertinent. \u00a0The contract needs to have more details than the TEMP as the TEMP is not a contractual document.<\/li><li>Is the \u201cCommon T&amp;E Database\u201d cloud-based? If not who is hosting and controls access?\u00a0 Is there one data repository, or several (may be driven by security levels)?\u00a0 Procedures &amp; applications to be used?\u00a0 Is the \u201cdata dictionary\u201d specified as a contract deliverable?\u00a0 Is raw or reduced data needed, and\/or products such as quick-look reports?<ul><li>\u201cRaw Data\u201d will be very large quantities, need to account for this in planning the infrastructure and transfer methods<\/li><\/ul><\/li><li>Does the test community have access to requirements database? (E.g., DOORS)<\/li><li>Does the test community have access to contractor problem report database?<\/li><li>Can the above information needs be satisfied by one overarching IDE?\u00a0 Or are other, more stove-piped implementations necessary?\u00a0 Short of access, static \u201csnap shots\u201d of database content would have to be used.<\/li><li>There are limitations when interfacing with Government networks, e.g. large amounts (100s of GB to TB) of data transfer via standard AFNET does not work very well.<ul><li>Example: Transfer of sled test video from contractor network via logging into server from AFNET did not work at all when attempted by one recent program.\u00a0 The local base network \u201cchoked\u201d on very large data files and timed out.<\/li><li>In the 21<sup>st<\/sup>\u00a0century we should not be hand carrying hard drives of data between test &amp; data analysis locations on a regular basis.\u00a0 Typically contractors do not allow Government hard drives to be connected to their networks, and the test team will have to get special permission to connect contractor-owned drives to a Government network.<\/li><li>Consider dedicated point-to-point AFNET lines.\u00a0 412 Test Wing has implemented this before successfully between Edwards AFB and contractor facilities.\u00a0 The cost is low and benefit high to a program.<\/li><\/ul><\/li><li>Classified vs. unclassified.\u00a0 Is a new DREN terminal or Taclane needed?\u00a0 Does contract DD254 have the right boxes checked? (E.g., does the contractor need a COMSEC account to store keys for encryption devices \u2013 although many devices can now be keyed remotely)<\/li><li>Consider a \u201csandbox\u201d approach to implement an IDE.\u00a0 Pilot tools deployed on Cloud-1 would likely be program-funded.\u00a0 Check if a PEO-funded \u201cIntegrated Digital Sandbox\u201d has been deployed &amp; is available to the program.\u00a0 GBSD &amp; ABMS used this approach.<\/li><li>A minimal IDE would be used for exchanging documents\/artifacts (e.g., SharePoint).\u00a0 While useful, this is not realizing the full potential of \u201cgoing digital.\u201d\u00a0 Documents are static artifacts unless stakeholders have the ability to asynchronously collaborate on maturing them.<\/li><li>What user functions &amp; features do testers need?\u00a0 Is user access from primary work PC needed?\u00a0 Does access location matter (i.e. classified vs. unclassified facility, unique PC configuration)?<\/li><li>What level of collaboration with the contractor is planned for test planning &amp; execution?\u00a0 \u201cInsight\u201d vs. \u201cOversight\u201d for contractor DT&amp;E?<\/li><li>Will cybersecurity and airworthiness processes demand large amounts of data to be reviewed by the Government, and how will the ITT facilitate this flow of data? (ITT has a vested interest but may not be the primary player in facilitating flow of data \u2013 depends on the scope of the test program in supporting certifications.)<\/li><li>Will CDRL deliverables (e.g., test plans) be digitally available for dynamic and collaborative review prior to formal delivery? [As opposed to the way it is generally done today \u2013 informal draft document via email, if at all, and formal delivery with contractual overhead activity and deadlines.]<\/li><li>Are the program requirements for an IDE described in the contract?\u00a0 Briefly describe these in TEMP, or provide direct references to statement of work etc.<\/li><\/ul><\/li><\/ul><\/li><\/ul><ul><li>3.1 T&amp;E Strategy<ul><li>Concise summary description of how test program is implementing or leveraging Digital Engineering \u2013 should reference applicable sections of supported program documents<ul><li>Digital Engineering (DE) Implementation \u2013 is there a separate plan? Or, summarized in the acquisition strategy and SEP?<\/li><li>How much collaboration with the prime contractor is planned?\u00a0<\/li><li>Use of Model-Based Engineering \/ Model-Based Systems Engineering (MBE\/MBSE) for test planning, test readiness reviews, &amp; test execution<\/li><li>Examples: Analysis via models to build a test matrix in a detailed test plan.\u00a0 Model views utilized for test readiness reviews.\u00a0 Comparing predictions from models to actual test results, and the process by which models are updated\/improved during development of the system.<\/li><li>Use of Integrated Digital Environment (IDE)<ul><li>How is data (of all forms needed for test planning and independently evaluating test results) efficiently accessed by stakeholders.\u00a0 This will likely include model data in some form.<\/li><\/ul><\/li><\/ul><\/li><li>How does the test strategy support acquisition strategy and system engineering needs (including verification at the various levels \u2013 system of systems, system, subsystem, etc.)?<ul><li>Tools: Verification Cross Reference Matrix (VCRM) and Integrated Test Event Matrix (ITEM) \u2013 former is part of the system specification, latter is derived from former.\u00a0 These should be digitally available to ITT via an IDE.<\/li><\/ul><\/li><li>Test strategy must be synchronized with contract language \u2013 confirm here<ul><li>What does the Government test team need from the contractor in terms of digital access and\/or delivery?<ul><li>Access to dynamic vs. static warehoused data<\/li><li>Access to models \u2013 views, ability to provide input and observe output, etc.\u00a0 Which models does the ITT really need?<\/li><li>Access to simulations, or ability to run independently<\/li><li>Technical Data Packages (e.g., modifications to test aircraft)<\/li><li>Cybersecurity testing \u2013 facilities, test items, other support<\/li><li>Laboratory testing<\/li><\/ul><\/li><\/ul><\/li><li>Digital (IT) infrastructure \u2013 services &amp; transport<ul><li>What type of connectivity is needed between contractor, program office, and test organizations?\u00a0 Cloud-based?\u00a0 Direct?\u00a0 Indirect (through intermediary)?<\/li><li>DREN? AFNET? Contractor-managed network?<\/li><li>Capacity needed? (Consider file sizes; documents vs. flight test raw data)<\/li><\/ul><\/li><li>Software tools (Identify any that require approval to be utilized on Gov\u2019t networks? Long lead times are typical, need to be addressed early.)<ul><li>E.g. CAD tools, Cameo, PLM TeamCenter or Windchill, AFSIM<\/li><\/ul><\/li><\/ul><\/li><\/ul><ul><li>3.2.3 Modeling &amp; Simulation (DT&amp;E utilization) \u2013 see existing language in template already \u2013 includes:<ul><li>\u201cDescribe the key models and simulations and their intended use. Include the developmental test objectives to be addressed using M&amp;S to include any approved operational test objectives.\u201d<\/li><li>\u201cIdentify who will perform M&amp;S verification, validation, and accreditation.\u201d<\/li><li>\u201cIdentify data needed and the planned accreditation effort.\u201d<\/li><li>\u201cIdentify how the developmental test scenarios will be supplemented with M&amp;S, including how M&amp;S will be used to predict the Sustainment KPP and other sustainment considerations.\u201d<\/li><li>\u201cIdentify developmental M&amp;S resource requirements in Part IV.\u201d<\/li><\/ul><\/li><\/ul><p>Augmenting questions for critical thought:<\/p><ul><li style=\"list-style-type: none;\"><ul><li>What are the modeling objectives for program\u2019s effort?\u00a0 In other words, what does the Gov\u2019t need to able to do with the model(s)?<ul><li>These are NOT modeling requirements<\/li><\/ul><\/li><li>What are the modeling capabilities needed for DT&amp;E, and when?<ul><li>Predict, Test, Validate &#8211; how will models be used, and for what ends?<\/li><li>Descriptive models vs. Analytical models, and integrating analytical with descriptive<\/li><li>Expect model(s) to evolve if system\/product is in development<\/li><li>Examples: Analytical models to define performance characteristics, e.g. Flight sciences: Aerodynamic, propulsion, flying qualities.\u00a0 Airframe structures (loads, flutter).\u00a0 Mission systems: Electronic Warfare, Radar, weapons usage.<\/li><li>Examples: descriptive models of a test plan review process, or stakeholder relationships within a program including all test organizations and certifying authorities.<\/li><li>Training for testers on use of models? \u00a0Formal vs. informal?<\/li><\/ul><\/li><li>What is needed from specific models for independent evaluation?\u00a0 (Definition of modeling elements and data, if not addressed in another plan like the SEP.\u00a0 If not in the TEMP, needs to be documented by ITT such that PMO can implement in a contract.)<ul><li>Output of models alone (artifact)?<\/li><li>Electronic access to contractor models with ability to input parameters and observe\/collect output?\u00a0 Is ability to access &amp; utilize model views needed?<\/li><li>Delivery of models to Government (including test community)?\u00a0 Format &#8211; Is source code needed, just executable code, and\/or summary design information (e.g. control law block diagrams)?\u00a0 One delivery vs. multiple?\u00a0 Timing?<\/li><li>Delivery of drawings for special instrumentation \u201ctemporary\u201d modifications.\u00a0 What\/How\/When \u2013 2D vs. 3D.\u00a0 What tools needed to view\/modify.\u00a0 See latest standards for sustainment TDPs \u2013 should be same format (e.g. MIL-STD 31000B).\u00a0<\/li><\/ul><\/li><li>Who is responsible for managing models?\u00a0 [There will be overlap with PMO engineering requirements here, which should be documented in the acquisition strategy and SEP.\u00a0 Focus on access to and usage of models for system level verification that the independent testers need to write reports, as agreed to with the PMO.\u00a0 Whether the Government or Contractor actually manages the models may not be critical to testers, as long as AFTC has access.]<\/li><\/ul><\/li><\/ul><ul><li>3.3 Developmental Test Approach<ul><li>3.3.1 Mission oriented approach.\u00a0 This section describes how to test the system in a mission context.\u00a0 Will any previously addressed models, simulations, and\/or analysis be used?\u00a0 Likely necessary for non-testable scenarios, including those too expensive or resource intensive to execute in practice.<\/li><li>3.3.2 Developmental Test Events (Description, Scope, and Scenario) and Objectives [Is anything needed in this section that has not already been addressed above?]<\/li><\/ul><\/li><li>3.5.3 Modeling &amp; Simulation (OT&amp;E utilization)<ul><li>This is OTA content (AFOTEC or MAJCOM test organization).\u00a0 If OTA needs access to contractor-produced &amp; maintained models, this generally needs to be written into the contract.<\/li><\/ul><\/li><li>4.2 Test Resource Summary \u2013 10 subsections including:<ul><li>4.2.3 Test Instrumentation<ul><li>If the contractor is performing instrumentation design, will the Government be able to review the design digitally?\u00a0 How?<\/li><li>How will final design \/ drawings be delivered?\u00a0 3D models, or 2D representation of 3D data?\u00a0 (Latter case is less desired \u2013 old way of doing things &#8211; Government should be using 3D tools rather than paying contractor to reduce 3D models to 2D artifacts.)<ul><li>Does AFTC require new software tools to utilize 3D data?<\/li><\/ul><\/li><li>Is a Technical Data Package (TDP) required?\u00a0 Generally yes, if a Government-owned test asset is being permanently modified and will be managed\/sustained by the Government in the long term.<ul><li>Review T-2 modification documentation &amp; requirements<\/li><li>Review TDP requirements &amp; what is really needed [need a good link to references]<\/li><\/ul><\/li><\/ul><\/li><li>4.2.8 Models, Simulations, and Test Beds<ul><li>See existing language in the DOT&amp;E Guide &#8211; what needs to be augmented as a result of program\u2019s chosen digital acquisition strategy?<\/li><li>Are there any resource needs specific to Government use of planned models, simulations, and Test-Beds to execute current test program, possibly including provisioning for future capability updates?<\/li><li>Which digital and\/or modeling capabilities &amp; training does the Government need to have in place before award?\u00a0 Must be ready for execution so the Government isn\u2019t behind on day one!<\/li><\/ul><\/li><li>4.2.10 Special Requirements<ul><li>Anything that doesn\u2019t quite fit above or not previously included.\u00a0 Such as:<\/li><li>Licensing and\/or AF approval for data processing tools\/means\/methods, use of unique Government or contractor databases, or IT infrastructure unique to the program or enterprise<\/li><li>Examples: Use of Distributed Test Operations, AFNET data \u201cpipe\u201d installation at contractor facilities, remote access to contractor models \/ databases \/ data storage, new or modified DREN point of service.<\/li><li>Unique contractual arrangements such as \u201cDesign Agent\u201d construct.<\/li><li>Reference to a DE\/MBE\/MBSE Implementation Plan the program has produced, and what ITT stakeholders need to support it.\u00a0<\/li><li>Specialized DE\/MBSE Training for DT&amp;E personnel.<\/li><\/ul><\/li><\/ul><\/li><\/ul>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-f6b14ee elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"f6b14ee\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-1169deb\" data-id=\"1169deb\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-8d0fe67 elementor-widget elementor-widget-text-editor\" data-id=\"8d0fe67\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div><h2 id=\"lifecycle-sustainment-plan-(lcsp)\">Lifecycle Sustainment Plan (LCSP)<\/h2><p>\u00a0<\/p><\/div><p><strong>Task 1: Identify areas within LCSP template that need to address transformation objectives.<\/strong><\/p><p><b>Digital Considerations within the Lifecycle Sustainment Plan (LCSP)<\/b><\/p><p><b>Introduction<\/b><\/p><p><i>The product support strategy should align with the model-based acquisition strategy \u2013 as defined below:<\/i><\/p><ul><li>Modeling objectives are used to select one of the model-based acquisition types:<ul><li><b>Model-supported acquisition<\/b>: models are used to support various engineering activities, including the production of key documents for contractual purposes<\/li><li><b>Model-collaborative acquisition:\u00a0\u00a0<\/b>Models form part of the contractual artifacts but as secondary or complementary artifacts<\/li><li><b>Model-centric acquisition:\u00a0\u00a0<\/b>Models are primary artifacts (with the capability to generate required documentation)<\/li><\/ul><\/li><\/ul><p><b>__________________________________________________________________________<\/b><\/p><p><b>1. Product Support Strategy (Section 3)<\/b><\/p><ul><li>This section directly relates to the Acquisition Strategy Sections 5.5 and 6.2, and therefore should address the model-based acquisition strategy (e.g., model-supported, model-integrated, model-centric)<\/li><li>Summarize the product support strategy for meeting sustainment requirements necessary to satisfy the model-based acquisition strategy requirements (Technical Data Strategy\/Intellectual Property Strategy)<\/li><li>Use of digital twin for product support decisions<\/li><\/ul><p><b>2. Cybersecurity (Section 3.1.4) Address considerations for cybersecurity within the program protection plan (PPP) that is of course an annex to the LCSP.<\/b><\/p><ul><li>Address supportability and\/or sustainment efforts support compliance with the Program Protection Planning (PPP) and the AFLCMC System Security Engineering Standard Processes within the model-based environment<\/li><\/ul><p><b>3. Influencing Design and Sustainment (Section 5)<\/b><\/p><ul><li>Identify model-based requirements that affect system\u2019s design and performance<\/li><li>Identify impacts of the model-based requirements to a system\u2019s product support strategy, planning, and implementation<\/li><\/ul><p><span class=\"fontColorRed\"><i>Beyond this section, the LCSP addresses each of the 12 product support elements<\/i><\/span><\/p><p><b>4. Design Interface (Section 9.1)<\/b><\/p><ul><li>Should articulate model-based requirements as a design-consideration \u2013 as outlined in the SEP (systems engineering plan)<\/li><\/ul><p><b>5. Sustaining Engineering (Section 9.3)<\/b><\/p><ul><li>Document the Failure Reporting, Analysis, and Corrective Action System (FRACAS) to include how the FRACAS data will be used from initial modeling and analysis through the fielding of the system.<\/li><\/ul><p><b>6. Maintenance Planning and Management (Section 9.4.3)<\/b><\/p><ul><li>Outline the maintenance concepts for hardware and software, to include considerations for maintenance (depot activation requirements) in a model-based environment<\/li><li>Considerations include manpower skills, support equipment needs, how the program will determine repair time, testability requirements, etc. within a model-based environment<\/li><li>Identify use of preventative maintenance strategies that rely on model-based environment like CBM+<\/li><li>Identify how the program will acquire and manage necessary data to populate the supply and maintenance systems that support maintenance concepts in a model-based environment (CBM+?)<\/li><\/ul><p><b>7. Supply Support (9.4.4)<\/b><\/p><ul><li>Should include considerations for provisioning and cataloguing processes (provisioning technical documentation delivery\/storage) in a model-based environment<\/li><\/ul><p><b>8. Packaging, Handling, Storage, and Transportation (PHS&amp;T) (9.4.5)<\/b><\/p><ul><li>Identify the program strategy for safely packaging, handling, storing, and transporting the system as well as any special requirements and interfaces with agencies or DoD components responsible for transporting the system within the model-based environment.\u00a0 Product support requirements for tracking shipped components.<\/li><\/ul><p><b>9. Technical Data (9.4.6)<\/b><\/p><ul><li>Define the technical data strategy for support of a model-based environment<\/li><li>Define the program&#8217;s approach to managing the data during acquisition and sustainment (e.g., access, method of delivery, format, and storage) within a model-based environment<\/li><li>Technical data rights strategy in support of the model-based requirements<\/li><li>If operating in an integrated data environment, consideration for network compatibility issues and mitigation steps for operating in the model-based environment<\/li><li>Document logistics data enterprise architecture generated which identifies electronic data repositories, information exchange requirements, and\/or usage<\/li><li>Identification of preliminary engineering\/products support data needed<\/li><li>Process by which the TOs will transfer from Acquisition to Sustainment<\/li><\/ul><p><strong>10.\u00a0<\/strong><b>Support Equipment (9.4.7)<\/b><\/p><ul><li>Requirements for overall support strategy for SE to include identification of the following:\u00a0 support equipment documents, supply support, interim spares, manpower, training, technical data, maintenance level and maintenance task requirements, computer resource support, calibration, facility requirements, support equipment for SE, hand tools and depot level support equipment\u00a0<\/li><li>Identify the support equipment strategy aligned with the model-based requirements (maintenance concept, acquisition strategy) (e.g., Support equipment drawing delivery in 3D?) \u00a0Would we require delivery of the support equipment drawing in a PDF? Or 3D model?<\/li><li>Considerations for newly designed support equipment technical data that can be used in a model-based environment<\/li><li>Delivery of support equipment technical packages in model based environment<\/li><li>Considerations for development versus non-development<\/li><\/ul><p><b>11. Training and Training Support (9.4.8)<\/b><\/p><ul><li>Address potential security issues for working in an integrated environment (e.g., integration of training systems with vendors)<\/li><li>Trainers and simulators \u2013 digital twin technology<\/li><\/ul><p><b>12. Manpower (9.4.9)<\/b><\/p><ul><li>Manpower requirements aligned with the maintenance and support equipment strategy<\/li><li>Considerations for manpower requirements for operating in a model-based environment<\/li><\/ul><p><b>13. Facilitates and Infrastructure (9.4.10)\u00a0<\/b><\/p><ul><li>Address use of digital facilities drawings<\/li><li>Civil engineering considerations<\/li><\/ul><p><b>14. Computer Resources (9.4.11)<\/b><\/p><ul><li>Identify, plan, resource, and acquire facilities, hardware, software, documentation, manpower and personnel necessary for planning and management of mission critical computer hardware and software systems.\u00a0 Programs should coordinate and implement agreements necessary to manage technical interfaces, manage work performed by maintenance activities, and establish\/update plans for periodic test and certification activities required throughout the life-cycle.<\/li><li>Program\u2019s support plan for software\/system in an integrated data environment<\/li><li>Identification of all systems\/software used for operating in the model-based environment<\/li><li>Licensing agreements for operating within the model-based tools<\/li><li>Configuration management approach to include obsolescence, deficiency, modification, hardware\/software baseline, and requirements management within model-based environment<\/li><li>Software baseline delivery methods Owning and managing the technical baseline<\/li><li>Strategy for managing the technical baseline into sustainment (e.g., access to data)<\/li><li>Considerations for open system architecture (document the OSA strategy)<\/li><li>Hosting and infrastructure strategy<\/li><li>Cybersecurity compliance<\/li><\/ul>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>The DAF Digital Transformation Office (DTO) knows that as programs transform to incorporate digital acquisition, these core documents may still be required (i.e. will not be represented as source of truth within a model; or will be source of truth in a model yet still needed by Senior Acquisition Leaders in a document form) and [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/guide.dafdto.com\/wp-json\/wp\/v2\/posts\/616"}],"collection":[{"href":"https:\/\/guide.dafdto.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/guide.dafdto.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/guide.dafdto.com\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/guide.dafdto.com\/wp-json\/wp\/v2\/comments?post=616"}],"version-history":[{"count":19,"href":"https:\/\/guide.dafdto.com\/wp-json\/wp\/v2\/posts\/616\/revisions"}],"predecessor-version":[{"id":734,"href":"https:\/\/guide.dafdto.com\/wp-json\/wp\/v2\/posts\/616\/revisions\/734"}],"wp:attachment":[{"href":"https:\/\/guide.dafdto.com\/wp-json\/wp\/v2\/media?parent=616"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/guide.dafdto.com\/wp-json\/wp\/v2\/categories?post=616"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/guide.dafdto.com\/wp-json\/wp\/v2\/tags?post=616"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}