Blank CRM DSS 12 Dec 2023.xlsx
XLSX spreadsheet 49 KB Posted
- Attached to
- Draft Solicitation - Data Software Services
- Solicitation number
- 23-01
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CRM
Document Title and Rev: Draft Data Software Services RFP (FA8806-23-R-0001) Document Date: 12 December 2022 Types of Comments:
A - Administrative: addresses what appears to be typographical, format, grammar, punctuation, and style errors S - Substantive: addresses factually incorrect material M - Major: addresses incorrect material that may cause non-concurrence with the publication C - Critical: addresses contentious issue that will cause non-concurrence with the publication Gov't Decisions A - Accept (Agree with comment) R - Reject (Disagree with comment; rationale required for rejection) M - Accept with modification (Partially agree with comment; rationale required for modification)
Item # Author: Numeric order of comments. Accomplish when all comments from all sources are entered and sorted. To number the matrix rows, highlight this column only and then select the numbering ICON on the formatting tool bar.
Used to track comments by source. Manually enter numbers from the first comment to the last comment. These numbers will stay with the comment and will not change when consolidated with other comments.
| NOTE: For column 2 do not use the auto numbering feature or these numbers will change when matrices are merged. | Source |
| Author: Insert office symbol. | Type |
| A/S/M/C | Page |
Author: Page numbers expressed in decimal form using the following convention:
(Page I-2 = 1.02, Page IV-56 = 4.56, etc.) This format enables proper sorting of consolidated comments.
0 – General Comments 0.xx - Preface, TOC, Executive Summary (Page i = 0.01, Page xi = 0.11) 1.xx – Chapter I 2.xx – Chapter II 3.xx – Chapter III x.xx – Chapter x, etc.
51.xx – Appendix A 52.xx – Appendix B 52.01.xx - Annex A to Appendix B 53.xx – Appendix C, etc.
99.xx – Glossary
NOTE: For Program Directives enter the page number as a whole number, (1, 2, 3, etc.) PDs are normally sorted by paragraph and line number and the page number helps to find the paragraph.
NOTE: Since joint publications (JPs) do not contain an appendix I, the number 59.00 will be skipped. Para / Section # Author: Paragraph number that pertains to the comment expressed. (i.e. 4a, 6g, etc.)
NOTE: An entry in this column should be used when commenting on draft program directives. An entry is optional for comments on draft joint publications. Line Author: Line number on the designated page that pertains to the comment, expressed in decimal form (i.e., line 1=1, lines 4-5 = 4.5, lines 45-67 = 45.67, etc.) For figures where there is no line number, use "F" with the figure number expressed in decimal form (i.e. figure II-2 as line number F2.02). For appendices, use the "F" and the appendix letter with the figure number (i.e. appendix D, figure 13 as line number FD.13; appendix C, annex A, figure 7 as line number FCA.07) Comment For any proposed changes include WAS/IS text.
If you need clarification or have a question, please contact the document author; do not pose questions as comments.
| Author: Provide comments using line-in-line-out format according to JSM 5711.01A, Joint Staff Correspondence Preparation (Examples are provided in CJCSI 5120.02, Joint Doctrine Development System. To facilitate adjudication of comments, copy and insert complete sentences into the matrix. This makes it unnecessary to refer back to the publication to understand the rationale for the change. Do not use Tools, Track Changes mode to edit the comments in the matrix. Include deleted material in the comment in the strike through mode. Add material in the comment with underlining. Do not combine separate comments into one long comment in the matrix, (i.e. 5 comments rolled up into one). | Rationale |
| Provide concise, objective explanation of the rationale for the comment. | Decision |
A/R/M Author: This column is for OPR use only. No rationale required for accepted items. Rationale for rejection is placed in the rationale comment box and highlighted for clarity. For modifications, the complete modified language will be placed (and annotated) as the bottom entry for that item in the “Comments” column and the rationale for the modification placed in the rationale comment box and highlighted for clarity. Notes Verified (Y/N) Author: Verification from Source for closure of comment
&"Arial,Bold"&12Comment Resolution Matrix (CRM)
&"Arial,Regular"&10As of &D &T &"Arial,Regular"&10UNCLASSIFIED &"Arial,Regular"&10&P of &N image1.png
File details come from the government source that posted it. Updated .