<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>OSD - SE - ODASD(SE)</title>
<link>https://yse.yabesh.ir/std/handle/yse/27</link>
<description/>
<pubDate>Fri, 03 Apr 2026 19:48:51 GMT</pubDate>
<dc:date>2026-04-03T19:48:51Z</dc:date>
<item>
<title>MIL-HDBK-61A</title>
<link>https://yse.yabesh.ir/std/handle/yse/228492</link>
<description>MIL-HDBK-61A; CONFIGURATION MANAGEMENT GUIDANCE
OSD - SE - ODASD(SE)
This military handbook provides guidance and information to DoD acquisition managers, logistics managers, and other individuals assigned responsibility for Configuration Management. Its purpose is to assist them in planning for and implementing effective DoD configuration management activities and practices during all life cycle phases of defense systems and configuration items. It supports acquisition based on performance specifications, and the use of industry standards and methods to the greatest practicable extent.  &lt;br&gt;This handbook is closely related to the following &lt;b&gt;Electronic Industries Alliance (EIA) Standards:&lt;/b&gt;  &lt;/span&gt;&lt;pre&gt;&amp;#8226;  &lt;b&gt;ANSI/EIA-649-1998&lt;/b&gt;, "National Consensus Standard for Configuration Management," &amp;#8226;  &lt;b&gt;EIA-836&lt;/b&gt;, "Consensus Standard for Configuration Management Data Exchange and Interoperability," and &amp;#8226;  &lt;b&gt;ANSI/EIA-632-1998&lt;/b&gt;, "Processes for Engineering a System."&lt;/pre&gt; &lt;br&gt;  &lt;br&gt;&lt;b&gt;ANSI/EIA Standard 649&lt;/b&gt; provides the basic configuration management principles and the best practices employed by industry to identify product configuration and effect orderly management of product change.  &lt;br&gt;&lt;b&gt;EIA-836&lt;/b&gt; (scheduled for initial draft publication in January 2001) EIA-836 facilitates the interoperability and exchange of configuration management data. The level of interoperability between dissimilar systems is determined by trading partner agreement. The extensible markup language (XML) facilitates data sharing and exchange among different systems. EIA-836 provides a set of standard definitions and business objects that can be used by XML frameworks in interfacing the content elements among one or more systems or databases. To be most effective, the capabilities of the process, tools or systems, should embody the CM principles in ANSI/EIA-649 in conjunction with the business objects and data element definitions in EIA-836.  &lt;br&gt;&lt;b&gt;ANSI/EIA-632&lt;/b&gt; describes the Systems Engineering process of which CM is an integral part. &lt;b&gt;[See 4.2.2]&lt;/b&gt;  &lt;br&gt;The acquisition reform environment is significantly different from one in which the Government imposed its own management requirements on contractors by military standards. Configuration management activity must be applied to items at a level that is consistent with acquisition strategy, protects the interests of the government, and flexibly accommodates contractor standard methodology. With a major share of configuration control authority shifted to contractors, the DoD configuration management activity must still continue to provide assurance of supportability and interoperability of military equipment and software. This responsibility requires careful planning and implementation of a DoD configuration management strategy that is in concert with the acquisition, logistic support, and maintenance philosophy of each given material item.  &lt;br&gt;As the DoD transitions to performance based acquisition and the use of digital CM information interfaces, this handbook provides the insight necessary to:  &lt;pre&gt;  &amp;#8226;  Understand the application of the basic principles of CM articulated in ANSI/EIA-649 to the DoD      acquisition and operational environment   &amp;#8226;  Plan for and make prudent and cost effective choices in effecting DoD configuration management activities      throughout the life cycle of a material item   &amp;#8226;  Provide the necessary basis for CM in RFPs and Contracts   &amp;#8226;  Evaluate contractor proposals and CM processes   &amp;#8226;  Acquire and process necessary CM information   &amp;#8226;  Use data models (schema), data dictionaries, and CM data object templates as a framework for translating      and communicating configuration information among diverse, distributed, data bases in an integrated data      environment   &amp;#8226;  Measure CM performance effectiveness of both Government activities and contractors&lt;/pre&gt; &lt;br&gt;  &lt;br&gt;&lt;b&gt;&lt;u&gt;Intended Use:&lt;/u&gt;&lt;/b&gt; This military handbook provides guidance and information to DoD acquisition managers, logistics managers, and other individuals, who are assigned responsibility for Configuration Management. Its purpose is to assist them in planning for and implementing effective DoD configuration management activities and practices during all life cycle phases of defense systems and configuration items. It supports acquisition based on performance specifications, and the use of industry standards and methods to the greatest practicable extent.  &lt;br&gt;
</description>
<pubDate>Mon, 01 Jan 2001 00:00:00 GMT</pubDate>
<guid isPermaLink="false">https://yse.yabesh.ir/std/handle/yse/228492</guid>
<dc:date>2001-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>DI-SESS-81785</title>
<link>https://yse.yabesh.ir/std/handle/yse/111457</link>
<description>DI-SESS-81785; Systems Engineering Management Plan (SEMP)
OSD - SE - ODASD(SE)
&lt;strong&gt;Use/relationship:&lt;/strong&gt; &lt;br&gt;The SEMP describes the contractor's technical approach and proposed plan for the conduct, management, and control of the integrated systems engineering effort. It shall be consistent with the government Systems Engineering Plan (SEP), if available. &lt;br&gt;The SEMP content may be tailored depending on the scope, purpose, and the acquisition phase of the program. The contractor's SEMP shall contain the annotated mapping between contractor and government SE processes. The government SE processes may be noted in the SEP. The SEMP shall also show alignment of contractor and subcontractor SE processes. &lt;br&gt;This Data Item Description (DID) contains content preparation instructions for the data product generated by the specific and discrete task requirements as delineated in the contract. &lt;br&gt;This DID supersedes DI-MGMT-81024.
</description>
<pubDate>Thu, 01 Jan 2009 00:00:00 GMT</pubDate>
<guid isPermaLink="false">https://yse.yabesh.ir/std/handle/yse/111457</guid>
<dc:date>2009-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>UDI-V-23990D</title>
<link>https://yse.yabesh.ir/std/handle/yse/6794</link>
<description>UDI-V-23990D; ELECTRIC ACCOUNTING MACHINE CARDS/LISTING, OUTFITTING MATERIAL
OSD - SE - ODASD(SE)
</description>
<pubDate>Thu, 01 Jan 1976 00:00:00 GMT</pubDate>
<guid isPermaLink="false">https://yse.yabesh.ir/std/handle/yse/6794</guid>
<dc:date>1976-01-01T00:00:00Z</dc:date>
</item>
</channel>
</rss>
