2022_003_001_883842.pdf (718.48 kB)
Download file

Guidance for Tailoring DoD Request for Proposals (RFPs) to Include Modeling

Download (718.48 kB)

With the advent of digital engineering and the Department of Defense (DoD) Digital Engineering strategy, programs are attempting to include digital engineering as part of their acquisition strategy. Realizing the desired benefits of digital engineering requires program offices to consider how to best acquire the models and artifacts necessary to gain the advantages of a robust digital engineering program. This report provides guidance for government program offices that are including digital engineering/modeling requirements into a request for proposal (RFP). Since RFPs can be released at many different program phases and because every program is different, the information in this report is meant to stimulate thought on the part of the program office into different areas to consider. The report provides overall guidance and more specific guidance regarding statements of work, deliverables, and Sections L and M of a request for proposal. Sample language included in this report is provided as exemplars and is not intended to be copied verbatim. We encourage program managers to use this report as a resource when partnering with contracting officers. 




Publisher Statement

This material is based upon work funded and supported by the Department of Defense and the US Army Development Command Aviation and Missile Center (DEVCOM AvMC) under Contract No. FA8702-15-D-0002 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The view, opinions, and/or findings contained in this material are those of the author(s)and should not be construed as an official Government position, policy, or decision, unless designated by other documentation. References herein to any specific commercial product, process, or service by trade name, trade mark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by Carnegie Mellon University or its Software Engineering Institute. NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT

Copyright Statement

©2022 Carnegie Mellon University This material has been approved for public release and unlimited distribution. Please see Copyright notice for non-US Government use and distribution. Internal use:* Permission to reproduce this material and to prepare derivative works from this material for internal use is granted, provided the copyright and “No Warranty” statements are included with all reproductions and derivative works. External use:* This material may be reproduced in its entirety, without modification, and freely distributed in written or electronic form without requesting formal permission. Permission is required for any other external and/or commercial use. Requests for permission should be directed to the Software Engineering Institute at permission@sei.cmu.edu. * These restrictions do not apply to U.S. government entities.

Usage metrics