GEARSS_Comments_Matrix_(CRM).xlsx

XLSX spreadsheet 51 KB Posted

Attached to
GEARSS GPS Engineering, Analysis and Remote Site Sustainment Federal contract opportunity
Solicitation number
FA882315r0001
Issued by
Department of the Air Force Space Command Space and Missile Systems Center

About this file

Format to submit comments to Draft RFP

View the file

Other files for this federal contract opportunity

Other files attached to GEARSS GPS Engineering, Analysis and Remote Site Sustainment, newest first.
File Type Posted
Pricing_Volume_Contract_Schedule_Table_V2.xlsx XLSX spreadsheet
Amendment_0002.pdf PDF
Atch_9_-_M-III_BASIS_OF_AWARD_AND_EVALUATION_CRITERIA.pdf PDF
GEARSS_RFP_Amendment_1_Summary_of_Changes.pdf PDF
GEARSS_RFP_-_Industry_Questions_-_Government_Response.pdf PDF
FA882315R0001_0001.pdf PDF
Atch_1_-_GEARSS_PWS.pdf PDF
Atch_8_-_L-III__INFORMATION_TO_OFFERORS.pdf PDF
FA8823-15-R-0001_GEARSS_Model_Contract.pdf PDF
Atch_3_-_Data_Rights.pdf PDF
Atch_7_-_STD_SCA_WD_2079_GEARSS.pdf PDF
Atch_4_-_GEARSS_GFP_List.pdf PDF
Atch_2_-GEARSS_DD254.pdf PDF
Atch_9_-_M-III_BASIS_OF_AWARD_AND_EVALUATION_CRITERIA.pdf PDF
Atch_8_-_L-III__INFORMATION_TO_OFFERORS.pdf PDF
Pricing_Volume_Contract_Schedule_Table.xlsx XLSX spreadsheet
Exhibit_A_-GEARSS_CDRLs.pdf PDF
Atch_10_-_SMC_OCI_Checklist.docx DOCX document
Atch_1_-_GEARSS_PWS.pdf PDF
Atch_6_-_Offerors_Phase_In_Plan_at_Award_if_applicable.docx DOCX document
Atch_5_-_Letter_of_Identification_(LOI).docx DOCX document
GEARSS_Pre_Solicitation_Draft_RFP_Industry_Comment_Resolution_(Final)_-_20150708.pdf PDF
Atch_2_-_DD254_Draft.pdf PDF
Atch_10_-_Addendum_to_Section_M.docx DOCX document
Atch_8_-_Letter_of_Identification_(LOI)__-_Official_Travel_of_Government_Contractors.docx DOCX document
Atch_7_-_ASCN_GFP_Attachment.pdf PDF
Atch_6_-_CAPE_GFP_Attachment.pdf PDF
GEARSS_Draft_RFP_Model.pdf PDF
Atch_3_-_Data_Rights_in_GEARSS.pdf PDF
Atch_9_-_Addendum_to_Section_L.docx DOCX document
Atch_4_-_DGX_GFP_Attachment.pdf PDF
Atch_1_-_Performance_Workstatment_(PWS).pdf PDF
Atch_5_-_KWAJ_GFP_Attachment.pdf PDF
Exhibit_A_-_CDRLs.pdf PDF
Show all 34

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

EN

Comment Resolution Matrix
Document: GEARSS _______________________________
#POC/ Org/ PhonePage #, Section #, Paragraph #Critical, Substantive, AdminWas (Original Language)ACTION (Suggested Change)RationaleA = PO Accepts

R = PO Rejects M = PO accepts with Modification PO Response

FM

Comment Resolution Matrix
Document: GEARSS ______________________________
#POC/ Org/ PhonePage #, Section #, Paragraph #Critical, Substantive, AdminWas (Original Language)ACTION (Suggested Change)RationaleA = PO Accepts

M = PO accepts with Modification PO Response

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
Critical0
Substantive0
Administrative0

JA

Comment Resolution Matrix
Document: GEARSS ________________________________
#POC/ Org/ PhonePage #, Section #, Paragraph #Critical, Substantive, AdminWas (Original Language)ACTION (Suggested Change)RationaleA = PO Accepts

M = PO accepts with Modification PO Response

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
Critical0
Substantive0
Administrative0

PI

Comment Resolution Matrix
Document: GEARSS __________________________________
#POC/ Org/ PhonePage #, Section #, Paragraph #Critical, Substantive, AdminWas (Original Language)ACTION (Suggested Change)RationaleA = PO Accepts

M = PO accepts with Modification PO Response

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
Critical0
Substantive0
Administrative0

PKC

Comment Resolution Matrix
Document: GEARSS __________________________________
#POC/ Org/ PhonePage #, Section #, Paragraph #Critical, Substantive, AdminWas (Original Language)ACTION (Suggested Change)RationaleA = PO Accepts

M = PO accepts with Modification PO Response

19
20
21
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
Critical0
Substantive0
Administrative0

SB

Comment Resolution Matrix
Document: GEARSS _______________________________
#POC/ Org/ PhonePage #, Section #, Paragraph #Critical, Substantive, AdminWas (Original Language)ACTION (Suggested Change)RationaleA = PO Accepts

M = PO accepts with Modification PO Response

SE

Comment Resolution Matrix
Document: GEARSS _______________________________
#POC/ Org/ PhonePage #, Section #, Paragraph #Critical, Substantive, AdminWas (Original Language)ACTION (Suggested Change)RationaleA = PO Accepts

M = PO accepts with Modification PO Response

SLA

Comment Resolution Matrix
Document: GEARSS _______________________________
#POC/ Org/ PhonePage #, Section #, Paragraph #Critical, Substantive, AdminWas (Original Language)ACTION (Suggested Change)RationaleA = PO Accepts

M = PO accepts with Modification PO Response

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:
1Comment NumberNumber sequentially. This will be used to identify specific comments.
2Reviewer NameEnter your name, Rank (as required) First, Middle Initial, Last
3OrganizationEnter the organization you represent, i.e., Gov, Aero, SE&I, etc.
4Office SymbolEnter the office symbol you are assigned to, i.e., ENR, GPC, etc.
5Phone NumberEnter the phone number where you may be reached.
6e-mailEnter the e-mail where you may be reached.
7Document Line #Enter the line # if the document is prepared with the line #.
8PageEnter the page number your comment relates to.
9ParagraphEnter the paragraph number your comment relates to. i.e., 3., 3.0, 3.1.1, 3.1.1.1, etc.
10Comment Against (Baseline/ PIRN/IRNEnter the document you review / comment against
11Original Reviewed (WAS)Enter the original text from the document reviewed
12Suggested Change -
New Text (IS)Enter the change that you, as a reviewer, recommends.
13Rationale for ChangeEnter your rationale for change comments.
14Date of the new textEnter the date for the new text suggested
15TYPE 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)
16Disposition -

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.
17Disposition RationalEnter the rational for the disposition status
18Final Changed TextEnter the final text agreed, if there is a re-evaluation. If no-revaluation, ICC enters the text suggested, becomes the final
19Reviewer Concurrence
(Concur or Non Concur)Reviewer approves the final text
20Concurrence Method (email, phone, mtg)Enter method Concurrence received
21Date Concurrence ReceivedEnter the date Concurrence received
22Non Concurrence RationalEnter the Rational if reviewer does not agree with the disposition
23Final Comment StatusEnter the Final Comment Status (Open/Closed)
24DOOR ID (if applicable)Enter the ID from the DOORS Data Base
25NotesNotes
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
CODEIMPORTANCEDEFINITION
CCriticalComments 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.
SSubstantiveComments 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.
AAdministrativeComments 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
CODERECOMMENDATIONDEFINITION
AAcceptAccept comment as written. No change.
A/CAccept with CommentAccept comment with changes, providing detailed explanation. The individual making the comment and the Project Officer will reconcile the comment.
DDeferredComments are administrative and will be included in the next change, or the comments are not within the scope of the proposed request for disposition.
RRejectRationale 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 .