___SE&I-2_DRAFT_RFP_CRM.xlsx
XLSX spreadsheet 19 KB Posted
- Attached to
- Systems Engineering & Integration-2 (SE&I-2) FINAL Request for Proposal (RFP) Federal contract opportunity
- Solicitation number
- FA8811-20-R-0003
About this file
This document contains a draft request for proposal (RFP) for continued Systems Engineering & Integration (SE&I-2) services as well as background information on the related federal contract opportunity. The Space and Missile Systems Center/Launch Enterprise (SMC/ECL) at Los Angeles Air Force Base, CA is seeking industry feedback on the dRFP through 8 November 2019 using the provided comment resolution matrix (CRM). An Industry Day with one-on-one meetings will be held from 23-25 October 2019 for interested parties who submit requests by 18 October 2019. Though not a small business set-aside, responses from small and small disadvantaged businesses are encouraged. The North American Industry Classification System code is 541715 with a small business size standard of 1250 employees. Questions should be submitted to the primary and secondary Points of Contact provided via email. Tecolote Research, Inc. will provide non-Government administrative support under appropriate non-disclosure agreements.
___SE&I-2_DRAFT_RFP_CRM
View the file
Other files for this federal contract opportunity
Show all 50
Systems Engineering & Integration-2 (SE&I-2) FINAL Request for Proposal (RFP) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CRM
Comment Resolution Matrix
Comment# POC/ Org/ Phone Document Name, Page #, and Paragraph # Critical, Substantive, Admin Comment Rationale A = Accepts R = Rejects M = Modification PO Response
| Critical | 0 |
| Substantive | 0 |
| Administrative | 0 |
Instructions
| GENERAL: | |||
| Following are the instructions for Comments Resolution Matrix (CRM) | |||
| INSTRUCTION: | |||
| During the review process, comments, questions, concerns regarding the document under review is to be documented and communicated using the CRM. The CRM, sheet 1 of this workbook, is initiated by the Reviewer and provided to the Project Officer as directed in the timeline associated with the assigned task. Following are instructions for completing the CRM form: | |||
| Project Officer & Reviewer completes: | |||
| 1 | Comment Number | Number sequentially. This will be used to identify specific comments. | |
| 2 | Reviewer Name | Enter your name, First, Middle Initial, Last | |
| 3 | Organization | Enter the organization you represent, i.e., Gov, Aero, SE&I, etc. | |
| 4 | Office Symbol | Enter the office symbol you are assigned to, i.e., ENR, GPC, etc. | |
| 5 | Phone Number | Enter the phone number where you may be reached. | |
| 6 | Enter the e-mail where you may be reached. | ||
| 7 | Document Line # | Enter the line # if the document is prepared with the line #. | |
| 8 | Page | Enter the page number your comment relates to. | |
| 9 | Paragraph | Enter the paragraph number your comment relates to. i.e., 3., 3.0, 3.1.1, 3.1.1.1, etc. | |
| 10 | Comment Against (Baseline) | Enter the document you review / comment against | |
| 11 | Original Reviewed (WAS) | Enter the original text from the document reviewed | |
| 12 | Suggested Change - | ||
| New Text (IS) | Enter the change that you, as a reviewer, recommends. | ||
| 13 | Rationale for Change | Enter your rationale for change comments. | |
| 14 | Date of the new text | Enter the date for the new text suggested | |
| 15 | TYPE Critical/Substantive/Admin (C/S/A) | Enter the "Type" code that best fits the proposed change. Use the Comment Type Code Table below. (Critical/Substantive/Admin) |
| The reviewer assigns an importance code to each comment provided on the CRM. Below is the table to be used in determining comment importance. | ||
| COMMENT TYPE CODE TABLE | ||
| CODE | IMPORTANCE | DEFINITION |
| C | Critical | Comments of a very serious nature that will preclude final approval and publication of the document. You are willing to elevate the comment or issue to senior organizational leadership (e.g., general officer) and recommend they non-concur. These are the “show-stoppers.” Convincing rationale for critical comments must be provided. The individual making the comment and the document writer will reconcile the comment. |
| S | Substantive | Comments of a less serious nature that have noticeable impact on the document’s quality or content. The document appears to be incorrect, misleading, confusing, or inconsistent with other sections. |
| A | Administrative | Comments that address minor items such as typographical, format, and/or grammatical errors. |
| CRM Adjudication: | ||
| Upon review of each comment, the Project Officer assigns a recommendation code. As necessary, the reasoning regarding the assigned disposition will be provided. Below is the table to be used in determining comment resolution. | ||
| COMMENT RESOLUTION CODE TABLE | ||
| CODE | RECOMMENDATION | DEFINITION |
| A | Accept | Accept comment as written. No change. |
| R | Reject | Rationale for rejection. For example, rationale will include “comment not technically sound, not cost effective, or cosmetic in nature”. |
| M | Modification | Accept comment with changes, providing detailed explanation. |
File details come from the government source that posted it. Updated .