Attch 13 - CRM template - Used for dRFP (questions-comments).xlsx
XLSX spreadsheet 29 KB Posted
- Attached to
- Launch Operations Support Contract (LOSC) Request for Proposal (RFP) – DRAFT Federal contract opportunity
- Solicitation number
- FA4610-21-R-0003
About this file
This document provides information regarding the Launch Operations Support Contract (LOSC) Request for Proposal (RFP) for Vandenberg Space Force Base. The LOSC is a non-personal services contract to provide maintenance, modification, and modernization for aging facilities, property, and Western Range support equipment to ensure successful performance during tests, operations, and launch. Services include ensuring real property installed equipment and facilities are maintained and operationally ready for ballistic missile, space, guided weapon, and aircraft test and evaluation missions in support of multiple government agencies.
The current LOSC contract awarded to Call Henry, Inc. is set to expire in June 2022. The follow-on contract will be 100% small business set aside under NAICS code 561210 with a size standard of $41.5M. The draft RFP will be released on June 15th with an industry day occurring from July 16-19th. Comments on the draft RFP are due by July 19th. The final RFP is scheduled for release on October 5th with proposals due November 19th and anticipated award in August 2022. Performance would begin October 1st, 2022. The contract will utilize a hybrid FPIF contract type.
View the file
Other files for this federal contract opportunity
Show all 50
Launch Operations Support Contract (LOSC) Request for Proposal (RFP) – DRAFT 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
RFP
| Comment Resolution Matrix | |||||||
| Document: | |||||||
| # | POC/ Org/ Phone | Page #, Section #, Paragraph # | Critical, Substantive, Admin | Was (Original Language) | ACTION (Suggested Change) | Rationale | A = PO Accepts |
R = PO Rejects
| M = PO accepts with Modification | PO Response |
| 1 | |
| 2 | |
| 3 | |
| 4 | |
| 5 | |
| 6 | |
| 7 | |
| 8 | |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
| 15 | |
| 16 | |
| 17 | |
| 18 | |
| 19 | |
| 20 | |
| 21 | |
| 22 | |
| 23 | |
| 24 | |
| 25 | |
| 26 | |
| 27 | |
| 28 | |
| 29 | |
| 30 | |
| 31 | |
| 32 | |
| 33 | |
| 34 | |
| 35 | |
| 36 | |
| 37 | |
| 38 | |
| 39 | |
| 40 | |
| 41 | |
| 42 | |
| 43 | |
| 44 | |
| 45 | |
| 46 | |
| 47 | |
| 48 | |
| 49 | |
| 50 | |
| 51 | |
| 52 | |
| 53 | |
| 54 | |
| 55 | |
| 56 | |
| 57 | |
| 58 | |
| 59 | |
| 60 | |
| 61 | |
| 62 | |
| 63 | |
| 64 | |
| 65 | |
| 66 | |
| 67 | |
| 68 | |
| 69 | |
| 70 | |
| 71 | |
| 72 | |
| 73 | |
| 74 | |
| 75 | |
| 76 | |
| 77 | |
| 78 | |
| 79 | |
| 80 | |
| 81 | |
| 82 | |
| 83 | |
| 84 | |
| 85 | |
| 86 | |
| 87 | |
| 88 | |
| 89 | |
| 90 | |
| 91 | |
| 92 |
| 0 | |
| Critical | 0 |
| Substantive | 0 |
| Administrative |
Instructions
| GENERAL: | |||
| Following are the instructions for MGUE TDS version 7, 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, Rank (as required) 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/ PIRN/IRN | 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) | |
| 16 | Disposition - |
Accept, Accept with Comment Reject, or Deferred Comment
| (A/ A/C /R/D) | Enter your disposition of each comment provided by the reviewer using the Comment Resolution Code Table below. | ||
| 17 | Disposition Rational | Enter the rational for the disposition status | |
| 18 | Final Changed Text | Enter the final text agreed, if there is a re-evaluation. If no-revaluation, ICC enters the text suggested, becomes the final | |
| 19 | Reviewer Concurrence | ||
| (Concur or Non Concur) | Reviewer approves the final text | ||
| 20 | Concurrence Method (email, phone, mtg) | Enter method Concurrence received | |
| 21 | Date Concurrence Received | Enter the date Concurrence received | |
| 22 | Non Concurrence Rational | Enter the Rational if reviewer does not agree with the disposition | |
| 23 | Final Comment Status | Enter the Final Comment Status (Open/Closed) | |
| 24 | DOOR ID (if applicable) | Enter the ID from the DOORS Data Base | |
| 25 | Notes | Notes | |
| Disposition: | |||
| 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. |
| A/C | Accept with Comment | Accept comment with changes, providing detailed explanation. The individual making the comment and the Project Officer will reconcile the comment. |
| D | Deferred | Comments are administrative and will be included in the next change, or the comments are not within the scope of the proposed request for disposition. |
| R | Reject | Rationale for rejection. For example, rationale will include “comment not technically sound, not cost effective, or cosmetic in nature”. |
File details come from the government source that posted it. Updated .