Draft RFP CRM PTS-G.xlsx

XLSX spreadsheet 70 KB Posted Aug 6, 2024

Attached to: Protected Tactical SATCOM - Global (PTS-G) Draft RFP
Solicitation number: FA880725X000XPTSG-dRFP
Issued by: Department of the Air Force

About this file

Written by GovTribe AI · Aug 6, 2024

This document is a draft Request for Proposal (dRFP) for the Protected Tactical SATCOM - Global (PTS-G) Space Production Vehicles, which includes Operations and Maintenance. The purpose of the dRFP is to solicit feedback from industry regarding the contents of the document, including the Statement of Work, Contract Data Requirements List, data rights, compliance and reference documents, Sections L and M, cybersecurity requirements, government cyber testing, Security Classification Guide, system integration and test plan, payload resource configuration, and technical requirements. Interested offerors are invited to submit comments via a Comment Resolution Matrix by September 6, 2024. The government will review the feedback and may schedule clarification sessions with industry. This dRFP is for information, planning, and market research purposes only and does not constitute a formal solicitation or a promise to issue a solicitation in the future. Vendors interested in competing for this effort must register for access to the Bidder's Library and provide facility clearance information to receive classified requirements.

View the file

Other files

File	Type	Posted
1_FormDD2875.pdf	PDF	Aug 6, 2024
Bidders Library Livelink Instructions.docx	DOCX document	Aug 6, 2024
3_Livelink_User_Agreement.pdf	PDF	Aug 6, 2024
2_AF Form 4394.pdf	PDF	Aug 6, 2024

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

CRM

	For instructions see the "INSTRUCTIONS" TAB below
	Commenter Identification Fields		Comment Description Fields
	(1)
COMMENT NO.	(2)
ENTITY	(3)
Proprietary Comment	(4)
COMMENTER NAME	(5)
PHONE #	(6)
EMAIL	Document	(7)

DOC LINE#

(if applicable)	(8)
PARA #	(9)

COMMENT TYPE

(C/S/A)	(10)
COMMENT	(11)

ORIGINAL TEXT

( FROM ) (12)

SUGGESTED CHANGE

( TO ) (13)

RATIONALE FOR CHANGE

&8&T &"Arial Rounded MT Bold,Bold"&14CRM STANDARD TEMPLATE &8&D

&8&Z&F &8&P

&8GPS CDM 072308-03 JUN 10_ CRM_Template &8&P of &N

INSTRUCTIONS

GENERAL:

Following are the instructions for form GPS CDM 072308-03 JUN 10_ CRM_Template

INSTRUCTIONS:

During the review process, comments, questions, concerns regarding the document under review is to be documented and communicated using the CRM. The Tech Lead or ICC will copy the CRM Template file to the CCPD Smartbook and fill out the CRM header information. The CRM, sheet 1 of this workbook, is initiated by the Commenter and provided to the Project Officer as directed in the timeline associated with the assigned task.

Following are instructions for completing the CRM form:

Insert rows in the "White" section only of the CRM sheet for additional needed comments, this preserves printing and metrics.

Insert a row by positioning the cursor on row below where you want a new row to be entered above it, then click Home>Insert>Insert Sheet Row.

Begin new paragraph by clicking Alt-Enter at the point that you want a new paragraph started in the text.

	Technical Leads and ICC (Interface Control Contractor) completes the HEADER INFORMATION at top of form:
		ICC:	Replace text with the ICC (Interface Control Contractor) name and phone number.
	Baslined Document (CCB Version):		Replace text with the Baselined Document number
		Proposed Change:	Replace text with the Proposed Change being reviewed
		Title:	Replace text with the Title of the Proposed Change Document
		Date:	Replace text with the Date the Document as last approved
		Tech Lead Name:	Replace text with the Technical Lead name and phone number.
	Commenter completes:
	1	Comment No.	Number sequentially. This will be used to identify specific comments.
	2	Entity	Pick the Entity you represent, i.e., Gov, Aero, SE&I, etc.
	3	Office Symbol	Pick the office symbol you are assigned to, i.e., ENR, GPC, etc.
	4	Comment Originator Name	Enter your name, Rank (as required) First, Middle Initial, Last Name
	5	Phone #	Enter the phone number where you may be reached.
	6	Email	Enter the e-mail where you may be reached.
	7	Document Line #	Enter the document line number if paragraph number in not applicable.
	8	Paragraph #	Enter the paragraph number your comment relates to. i.e., 3., 3.0, 3.1.1, 3.1.1.1, etc.
	9	Comment Type
(C/S/A)	Pick the "Type" code that best fits the importance of the proposed change.

Use the Comment Type Code Table below. (Critical/Substantive/Administrative)

10	Comment	Enter comment or question about text.
11	Original Text (FROM)	Enter the original text from the document being reviewed (Baseline Doc, PIRN, or IRN)
12	Suggested Change (TO)	Enter the change that you, as a commenter, recommend.
13	Rationale for Change	Enter your rationale for the change.
Technical Leads and ICC completes:
14	Doc Phase	Pick the phase in which the comment is made. (PRE-WG, WG, WTR, POST-WTR)

PRE-WG = Deferred comments from a previous change iteration WG = Comments as a result of any Working Group WTR = Comments as a result of the Wing Technical Review POST-WTR = Comments made after the ERB or CCB

	15	Date of Comment	Enter the date (mm/dd/yy) the comment is made or new text suggested.
	16	Comment Against
(Baseline/ Proposed Change)	Choose whether you are commenting against the Baseline Document or Proposing a Change.
	17	DOORS ID (if applicable)	Enter the DOORS Id from the DOORS Data Base.
	18	Requirement?	Pick whether the DOORS Id is a Contract Requirement. Y = Yes or N = No.
	19	Requirement Change Type	Pick the type of change to the requirement: Addition, Change, Clarification, or Deletion.
	20	Disposition	Pick your disposition of each comment provided by the Commenter. Use the Comment Resolution Code Table below to choose whether you Accept, Accept with Comment, Reject, or Deferred the comment.
	21	Disposition Rational	Enter the rational for the disposition status
	22	Final Changed Text	Enter the final text agreed to if there is a re-evaluation. If no re-evaluation, the text suggested in column 16 will be final.
	Commenter completes:
	23	Commenter Concurrence
(Concur or Non Concur)	Pick the concurrence of the final text and/or disposition.
	24	Non Concurrence Rationale	Enter the Rationale, if Commenter does not agree with the ICC's disposition
	Technical Leads and ICC completes:
	25	Concurrence Method (email, phone, mtg)	Pick the method Concurrence received
	26	Date Concurrence Received	Enter the date Concurrence received
	27	Final Comment Status	Enter the Final Comment Status (Open/Closed)
	28	Notes	Notes

COMMENTER:
The commenter 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.

Gautam Nagaraj	6176203707	gnagaraj@draper.com
Ric Dargusch	6172581846	rdargusch@draper.com
Robert King	6172583342	rking@draper.com