CPG Most asked questions

 

As a potential industry partner, what considerations should be applied when routing submissions to CPG or CSC?

CPG will identify and assess each submission and align the submission with the corresponding organization.

 

What type of attachments are accepted?

.PDF, .xls, .doc, .zip

Media and larger files will be coordinated with FRONT DOOR and the interested party.

 

How long does a submission take for review and response?

Based on current volume and complexity, submissions may take an average of 72 hours.

 

Why was my submission rejected?

-      Does not meet the current needs, or

-      Not enough information, or

-      Technology is over cost

 

How long will my submission be retained in CPG system?

Submissions will be stored until notified or requested for deletion.

 

What are the CPG White Paper requirements?

Problem Statement 

 “What is the system-level problem to be solved and why is it important?” It need only be a paragraph stating the problem and the possible military benefit (new or improved capability) if a solution is found. Half a page should be sufficient.  

Technical Background 

This section provides the broader context in which the white paper is being submitted, providing an elaboration of the problem statement and military benefits stated in the previous section (Problem Statement). It may include a historical overview of the problem with respect to a current system capability performance shortfall, previous approaches to solving the problem that either provided the current capability or failed to provide a needed capability, and a brief explanation of any current line of research that promises a solution. This section may require more than one page.  

References should be cited if they can provide additional background. Of particular value are reports describing test and evaluation (T&E) trials of developing or in-fleet systems that document a specific system performance shortfall, or a concept-of-operations study that quantifies the gain from a hypothesized new system or an improved capability in an existing system.  

Technical Objectives 

 “What is the nature of the solution to be provided?” or “What specific technologies are needed?” It lists general technical objectives that collectively will provide a solution to the system-level problem stated above (Problem Statement) and describes how they will provide either a new or improved military capability (new system or an improved current system). It is helpful to include the basic hypotheses and assumptions that underpin each objective. This section should require one page at most.  

Technical Challenges 

 “What are the specific technologies to be developed?” or “What are the specific difficulties to be encountered?” It lists the technical hurdles that must be overcome to meet the technical objectives, identifying the ones that are the most important or the most difficult. This section should require one page at most.  

Technical Approach 

 “What is the plan of work?” It contains an outline of a general schedule of work broken down into logical units that will resolve the technical challenges and meet the technical objectives. This section should require no more than one page.  

The work should be organized into several tasks, each related to a specific objective or set of objectives, each lasting for a specified length of time. Tasks can be performed sequentially or simultaneously. Significant events (e.g., a field test, the construction of piece of equipment) and milestones (e.g., the delivery of software, the completion of a task, submission of a report) should be identified for each task. Each task should be described by a separate paragraph with its events and milestones listed as bullets.