Explain how the acquisition of those rights is consistent with 10 USC 2320, DFARS 227.71/227.72, and the life-cycle needs of the program. Identify the DFARS clauses that will be included into the resulting contracts Identify the estimated cost of the IP rights to CDRLs. Describe the process the program will follow to question or challenge contactor assertions or markings. Describe the approach for maintaining the software and its related documentation once software maintenance is transferred from the OEM Describe the use of withholding or incentives specific to performance in the area of data management Describe to what extent an Integrated Data Environment (IDE) will be used during contract performance, including any required interfaces to government data systems/repositories, how those requirements will be satisfied, the digital format standards to be used, and why the team selected those standards. Describe what evaluation criteria will be used to evaluate IP rights proposed by offerors during source selection The business case analysis calculation, conducted in concert with the engineering tradeoff analysis, that outlines the approach for using open systems architectures and acquiring technical data rights. Analyze the contractor's economic interest in such IP that potential offerors developed exclusively at private expense by performing market research. Analyze the Government's costs to acquire, maintain, store, retrieve and protect the data, repair/maintenance/overhaul philosophies, spare/repair parts considerations, and whether procurement of the items, components or processes can be accomplished on a form, fit or function basis
Specify the impact of this acquisition approach on the national technology or industrial base and the analysis used to make this determination. If is an impact, summarize the industrial base constraints, how they will be managed, and the plan for future assessment, including frequency. Industrial and Manufacturing Readiness (not applicable to software-intensive programs without production components). Estimate the risk of industry being unable to provide program design or manufacturing capabilities at planned cost and schedule. Identify the Manufacturing and Quality Management systems and summarize how they will contribute to minimizing cost, schedule, and performance risks throughout the product life cycle. Sustaining Industrial Capabilities. Summarize the make-or-buy approach to establish and maintain access to competitive suppliers for critical areas at system, subsystem, and component level (e.g., requiring an open-systems-architecture or a make-or-buy plan). List critical items and their sources. When the analysis indicates that the needed industrial capabilities are in danger of being lost, the strategy should indicate whether government action is required to preserve the industrial capability. The strategy should also address product technology obsolescence, replacement of limited-life items, regeneration options for unique manufacturing processes, and conversion to performance specifications at the subsystems, component, and spares levels. Identify any planned or completed MOAs. Life-Cycle Signature Support If a Technology Development Strategy, provide a table (see example Table 6) that indicates the program life-cycle signature support requirements. Identify the mission data type (signatures, electronic warfare integrated reprogramming, order of battle, geospatial intelligence, and system characteristics and performance data sets); specific subcategories, if known (Radar, Thermal, Acoustic, etc.); the domain (Space, Air, Land, Naval, Missile Defense, etc.); subcategories within the domain (e.g., for Air domain: ‘Fighter Aircraft’); and data fidelity required, if known (e.g., dB, °C, resolution, Hz, etc.). If additional or more-specific requirements have been identified, they should be included. Life-Cycle Signature Support Requirements