Although outdated in some respects, the SERD process is spelled-out in MIL-HDBK-2097A, 27 July 1997, Acquisition of Support Equipment and Associated Logistics Support. This handbook was revalidated on 10 September 2014 for use in acquisitions, with this disclaimer on the cover page:  “If cited as a requirement, contractors may disregard the requirements of this document and interpret its contents only as guidance.” (The out-of-date portions of the handbook include references to other publications and some dated terminology such as the term “Logistics Support Analysis,” now referred to as either “supportability analysis” or “PSA.”) The recent revalidation of the handbook, however, indicates that its basic concepts remain sound. It lays-out the SERD process including steps to be taken to develop requirements, to prioritize SE selection criteria (starting with common SE being most preferable, and newly-developed items being least preferable), as well as specific design considerations for peculiar SE.

As described by SAE-TA-STD-0017, SERDs are recorded in several parts. These parts provide key narrative and quantitative data used to propose and validate SE needs. The narrative approach is used with engineering data that supports the developer's description of a needed support function along with a recommended means of satisfying this need. Quantitative methods are used to provide availability, logistics support, and acquisition-type data regarding the item of SE being recommended. The standard also clarifies that the SERD is intended to support overall systems management of SE development, acquisition and optimum standardization within and among systems. SERD submissions and subsequent revisions (configuration changes, allowance adjustments, etc.) are a continuing requirement throughout the life cycle of the end article.

While all the Services use the SERD process, the Air Force and Navy have some resource information that is readily available and useful to all Logistics practitioners. Here are a sampling of helpful resources:

• Air Force Product Support Tool Kit (PSTK) describes the SERD process from the Air Force perspective, including inclusion of the Contracts Data Requirement List (CDRL) for the SERD in the contract Request for Proposal (RFP), as well as a description of stakeholder reviews of SERDs submitted by the contractor.
• Air Force Handbook 23-123, Volume 3, Air Force Equipment Management, provides information on management of SERDs within the Air Force Equipment Management System. Specific references include para 1.4.2.8, para 2.2.3.1, para 2.2.4.1, and para 2.2.5.3, and para 3.5.2.4.
• NAVAIR Instruction 13600.1A, 24 June, 2014, Acquisition of Support Equipment Utilizing the Support Equipment Recommendation Data Process, contains a SERD acquisition process which is abbreviated and shown below as an example.

In addition, Data Item Description (DID)-ILSS-80118C SE Recommendation, identifies a report made up of six sections of SE/SE-relevant information to be used for SE acquisition, logistics support, and life-cycle management purposes.