US Space Command

BY ORDER OF THE USCINCSPACE UI33-2
UNITED STATES SPACE COMMAND 15 May 1996

Communications

USCINCSPACE COMMAND AND CONTROL INITIATIVES PROGRAM

This instruction establishes the policy and procedures for the Commander in Chief, United States Space Command (USCINCSPACE), Command and Control (C2) Initiatives Program. It applies to HQ United States Space Command (USSPACECOM) and its components, Air Force Space Command (AFSPC), Naval Space Command (NAVSPACECOM), and United States Army Space Command (USARSPACE). HQ North American Aerospace Defense Command (NORAD) and Cheyenne Mountain Operations Center (CMOC) are invited to participate in this program. The reporting requirement in this directive is exempt from licensing in accordance with paragraph 2.11.10. of AFI37-124, the Information Collections and Report Management Program; Controlling Internal, Public and Interagency Air Force Information Collections. This instruction does not apply to the Air Force Reserve nor Air National Guard units.

SUMMARY OF REVISIONS
This instruction clarifies the project submission process and amplifies the need for obligation of funds within 30 days.

1. Reference:

1.1. Chairman, Joint Chiefs of Staff Instruction 7401.02, CINC Command and Control Initiatives Program.

2. Terms. See Attachment 1.

3. General. The Joint Staff budgets funds annually to provide the Unified Commanders in Chief (CINC) discretionary funds for timely, low-cost, near-term improvements to their C2 systems to meet unforeseen requirements. These funds may include procurement funds and/or Operations and Maintenance (O&M) funds. Joint Staff/J6 makes these funds available to the Unified CINCs through the C2 Initiatives Program (C2IP). The funds must be used in the fiscal year in which they are issued, and all funded projects must be operational within one year of funds receipt. Because of close Congressional scrutiny of C2IP, early obligation (within 30 days of funds receipt) is crucial; funds not obligated within 30 days of funds receipt jeopardize the allocation of C2IP funds to USCINCSPACE in succeeding fiscal years as well as continued Congressional funding of the Joint Staff program.

3.1. The key events of each C2IP cycle, which lasts approximately 18 months, are:

3.1.1. Joint Staff issues call for proposals (approximately March).

3.1.2. USCINCSPACE C2IP Manager issues call for proposals (no later than the third week of March).

_______________
Supersedes: UR102-1, 28 Jan 91
No. of Printed Pages: 11
OPR: SPJ6N (Major Richard M. McBreen)
Approved by: Colonel Rodney S. Lusey
Distribution: FX (Joint Staff/J6U, Washington DC 20318-6000...............................................................1)
3.1.3 HQ USSPACECOM and HQ NORAD directors, Commander CMOC, and component commander representatives get initial Deputy USCINCSPACE approval of and/or further guidance on draft proposals during a joint NORAD/USSPACECOM Directors' meeting (no later than second week of April).

3.1.4. USSPACECOM, NORAD, components, and CMOC submit proposals to C2IP Manager under director (USSPACECOM and NORAD) or command (CMOC and components) signature (no later than fourth week of April).

3.1.5. C2IP Prioritization Board reviews proposals and prioritizes them (no later than third week of May).

3.1.6. Mission Systems Integration Board (or one of its panels) reviews the proposals for integration into and interoperability with the CINC's C2 systems.

3.1.7 C2IP Manager submits list to Deputy USCINCSPACE (no later than 30 June).

3.1.8. Deputy USCINCSPACE approves C2IP Prioritization Board's list (no later than third week of July).

3.1.9. C2IP Manager sends package to the Joint Staff (no later than 1 August).

3.1.10. Joint Staff reviews all CINC packages for validation and funding approval (August and September).

3.1.11. Joint Staff releases project validation and approval message and requests funding (1 October).

3.1.12. Joint Staff forwards funds to CINCs (15 November, contingent on signing of authorization and appropriation bills).

3.1.13. C2IP Manager distributes funds (on receipt of Joint Staff funds).

3.1.14. Project managers obligate funds (within 30 days).

3.1.15. Projects completed and operational (within 1 year of receipt of funds).

3.1.16. Project managers submit project completion reports (within 30 days of project completion but no later than 15 December).

3.1.17. C2IP Manager submits completion reports to Joint Staff (within 30 days of project completion) and consolidated completion report (31 December).

3.2. Out-of-cycle proposals can be submitted to the C2IP Manager any time during the fiscal year. The C2IP Prioritization Board will review out-of-cycle proposals and assign priority numbers relative to the proposals already submitted to the Joint Staff for that fiscal year. The Deputy USCINCSPACE has approval authority on all out-of-cycle submissions. The Joint Staff will notify the C2IP Manager of an out-of-cycle proposal's disposition (not validated/validated/validated and funded) within 14 days of receiving the proposal and will forward funds within 30 days.

4. C2IP Project Criteria:

4.1. A C2IP proposal must meet the following criteria to be validated and approved for funding:

4.1.1. Utility. C2IP projects are intended to give the CINCs a capability to implement timely, low-cost, near-term improvements to their C2 systems to meet unforeseen requirements. Improvements should discernibly increase the readiness and combat capability of the command by enhancing the CINC's ability to command and control forces.

4.1.2. Project Size. Total funds provided by C2IP for a project (all appropriations) may not exceed $300,000.

4.1.3. Project Duration. C2IP projects must be completed and operational within one year after receipt of funding. Although procurement funds are multi-year funds, they, as well as the O&M funds distributed under this program, must be used in the fiscal year in which they are allocated. To that end, project managers must obligate their funds within 30 days of receipt. If they fail to do so, the C2IP Manager will withdraw the funds and reallocate them to the next unfunded project on the list of Joint Staff-validated projects. Available standard contract vehicles should be used when feasible to reduce time to obligate.

4.1.4. Logistics Supportability. C2IP projects (equipment, modifications, software, etc.) shall be logistically supported through standard DoD logistics channels or have provision for follow-on contractor support included in the normal O&M budget.

4.1.5. Human Resources. Human resource requirements generated from C2IP projects shall be fulfilled using standard manpower and personnel procedures for Joint activities.

4.1.6. Conformity and Interoperability:

4.1.6.1. C2IP projects must be consistent with the CINC's C4 Systems Master Plans, Chairman, Joint Chiefs of Staff Instruction 6212.01A, and approved technical architectures.

4.1.6.2. C2IP projects essentially support joint operations. Therefore, C2IP projects must be interoperable between Service C2 systems.

4.2. Valid Nonmateriel C2IP Projects. C2IP funds can also be applied toward the following nonmateriel types of projects:

4.2.1. Studies. C2IP funds can be used to fund engineering solutions to specific problems and to document the implementation of these solutions in C4 Systems Master Plans.

4.2.2. Travel. C2IP funds can be used for TDY to bring unique expertise to work on a specific C2 project or problem.

4.2.3. Test and Evaluation. C2IP funds can be used to test and evaluate systems, equipment, or procedures that may provide enhanced C2 capabilities.

4.2.4. Software. C2IP funds can be used to upgrade software for existing C2 systems or C2 models.

4.3. Invalid C2IP Projects. C2IP funds cannot be applied toward the following types of projects:

4.3.1. Continuing Funds. C2IP funds cannot be used to support C2 projects begun under this program (such as annual maintenance contracts or long-term leases). Equipment or software purchased under
this program should be supported through standard DoD logistics channels or have provisions for follow-on contractor support included in the agency's normal O&M budget.

4.3.2. Human Resource Augmentation. C2IP funds cannot be used to fund additional human resource requirements.

4.3.3. Incremental Funding. C2IP funds cannot be used to fund purchases of equipment or services for a specific project year after year. The funds are for near-term fixes. Any continuing need for funds to support C2 projects begun under this program must be picked up under normal funding lines.

4.3.4. Circumvention of Normal Approval Process. C2IP funds cannot be used to expand the scope of separately approved and funded projects or programs. In addition, C2IP funds cannot be used for projects that have been specifically denied or deleted in the PPBS process at the Service Headquarters, OSD, OMB, or Congressional level, unless approved by the Director, Joint Staff/J6.

5. Responsibilities:

5.1. Deputy USCINCSPACE has approval authority for all C2IP submissions to the Joint Staff.

5.2. HQ USSPACECOM Director of Command Control Systems (SPJ6) oversees the administration of the USCINCSPACE program. SPJ6V is the Chairperson of the C2IP Prioritization Board and appoints the C2IP Manager from within the Directorate.

5.3. HQ USSPACECOM Director of Operations (SPJ3) and Director of Plans (SPJ5); Commander, CMOC; AFSPC/CC; COMNAVSPACECOM; COMARSPACE; HQ NORAD Director of Operations (NJ3) and Director of Plans (NJ5); and HQ NORAD/USSPACECOM Director of Intelligence (N-SPJ2) and Director of Logistics (N-SPJ4), if submitting C2IP projects for consideration, will:

5.3.1 Designate an O-6 voting member to serve on the C2IP Prioritization Board and advise SPJ6, in writing, of the name, grade, office symbol, telephone number, and security clearance of the designee immediately upon appointment.

5.3.2. Ensure that their directorate or command sponsored projects meet the criteria listed in paragraph 4.

5.3.3. Under their signatures, submit their projects to J6 (in priority order if submitting more than one project).

5.4. C2IP Prioritization Board:

5.4.1. Is comprised of individuals designated in paragraph 5.1 and 5.2 for voting membership. The chairperson may invite other individuals to attend (e.g., contracting and comptroller personnel).

5.4.2. Holds meetings at the discretion of the chairperson, but at least once a year, to review new proposals and develop a recommended prioritized list for Deputy USCINCSPACE approval.

5.5. The HQ USSPACECOM comptroller office will designate an advisor to the C2IP Manager.

5.6. C2IP Manager:

5.6.1 Acts as the command focal point for all coordinated actions with the Joint Staff C2IP Manager and the project managers.

5.6.2. Issues the annual call for project proposals.

5.6.3. Acts as the C2IP Prioritization Board Secretary. As such:

5.6.3.1. Sets up board meetings.

5.6.3.2. Prepares the staff summary sheet forwarding the recommended priority list to Deputy USCINCSPACE.

5.6.3.3. Distributes copies of the Deputy USCINCSPACE-approved priority list to the board membership for further dissemination within their respective organizations.

5.6.3.4. Assembles the formal proposal package for final Joint Staff/J6 approval according to Chairman, Joint Chiefs of Staff Instruction 7401.02.

5.6.4. Maintains obligation status, by project, of all funds allocated and reports status to the Joint Staff/J6 as prescribed in reference 1.1., with courtesy copies to the project managers. Also sends courtesy copies of quarterly status reports to Directors (USSPACECOM and NORAD) and commanders (CMOC and components) who have active C2IP projects.

5.6.5. In the event project managers do not obligate their funds in 30 days, grants approval of extension requests or forwards recommendation for disapproval to HQ USSPACECOM J6 for final determination.

5.6.6. Reallocates excess funds according to the approved priority list after receiving Joint Staff/J6 approval.

5.6.7. Submits project completion reports to the Joint Staff within 30 days of project completion and a consolidated completion report by 31 December.

5.7. Project Managers:

5.7.1. Prepare requirements documents and begin validation process as soon as the C2 deficiency is identified, preferably before submitting as a C2IP proposal.

5.7.2. Prepare project submission package as delineated in Attachment 2 and obtain command (for components and CMOC) or director-level (for USSPACECOM and NORAD) signature.

5.7.3. Brief proposal to C2IP Prioritization Board at the time and place designated by the C2IP Manager and in the format specified in Attachment 3.

5.7.4. Ensure funds are obligated within 30 days of receipt according to the procedures in paragraph 6. If delay is unavoidable, submit a request for an extension to the C2IP Manager detailing the cause for the delay and a plan of action and milestones for resolving it.

5.7.5. Immediately advise the C2IP Manager of any changes in the scope or funding requirements of their projects or status of their funds.

5.7.6. Ensure the C2IP Manager receives copies of all documents that commit or obligate their funds immediately upon execution.

5.7.7. Provide the C2IP Manager with completion reports within 30 days of project completion in the format described in Attachment 4.

6. Commitment and Obligation Procedures:

6.1. Funds are considered committed when 21st Comptroller Squadron (21CPTS) finance personnel have signed and recorded a reference number on a Military Interdepartmental Purchase Request (MIPR, DD Form 448), Fund Cite Authorization (FCA, AF Form 616), or (AF Form 9). Funds are not obligated until a MIPR is accepted reimbursable (Category I) or an actual delivery order has been placed with a vendor by 21CONS contracting personnel or by contracting personnel of the accepting activity. Whether the funds are to be obligated locally or by another agency, it is incumbent upon the project manager to ensure they are obligated within 30 days.

6.2. If the funds are obligated by other than 21CONS-supported activities:

6.2.1. The project manager provides the C2IP Manager with the name, mailing address, telephone number, and fax number of the activity that has agreed to purchase the equipment or services.
6.2.2. The C2IP Manager prepares the MIPR or FCA, as appropriate, and submits to 21CPTS after coordination with the HQ USSPACECOM comptroller advisor designated in paragraph 5.4. for signature. Project managers can expedite the process by hand-carrying a self-prepared document through the C2IP Manager and HQ USSPACECOM comptroller advisor and delivering it to 21CPTS for funds verification and assignment of reference numbers. The project manager must provide a copy of the completed document to the C2IP Manager as soon as feasible. The C2IP Manager then forwards the original funding document to the addressed agency as soon as possible since the agency cannot obligate funds until it receives the original funding document.

6.3. Otherwise, the project manager prepares the required documents (e.g., AF Form 9) and submits to the C2IP Manager for coordination and forwarding to 21CPTS finance and contracting personnel through the HQ USSPACECOM comptroller advisor. The project manager has the same "walk-through" option described above.

RODNEY S. LUSEY, Colonel, USA
Joint Secretary

Attachments:
1. Terms
2. Format for Submission of C2IP Proposals
3. Briefing Proposals to the C2IP Prioritization Board
4. Project Completion Report Format

TERMS

1. C2IP Proposal. A request for C2IP funding submitted by USCINCSPACE in accordance with reference 1.1.

2. C2IP Project. A C2IP proposal that has been validated by the Joint Staff C2IP Review Board.

3. Command and Control System. The facilities, equipment, communications, computers, procedures, and personnel essential to a commander for planning, directing, and controlling operations of assigned forces pursuant to the mission assigned. (Joint Pub 1-02, The DoD Dictionary of Military and Associated Terms, 1 December 1989).

4. Funding Approval. Determination by Joint Staff/J6 that a C2IP project can be funded. Only validated C2IP projects can be approved for funding. Funds may be allocated only to approved C2IP projects.

5. Out-of-Cycle Request. An out-of-cycle request is a project request that emerges throughout the year which was not submitted in the original yearly call.

6. Validated. Certification by the Joint Staff C2IP Review Board that a C2IP proposal meets all of the criteria set forth in this instruction.

FORMAT FOR SUBMISSION OF C2IP PROPOSALS

1. Purpose. Each C2IP proposal must "stand alone" and contain elements of information needed to ensure that the proposal will conform with program established guidelines. The proposal should be complete and detailed enough to enable the Joint Staff Review Board to understand the merits of your case based on this document alone.

2. Format. Use the following format for all annual and out-of-cycle proposal submissions. Provide all information (or indicate not applicable). Unclassified proposals are preferred. Otherwise, classify each paragraph. Be concise, limiting length to 1-1/2 typed pages (single spaced), excluding the required interoperability information.

PRIORITY NO. The highest directorate (for USSPACECOM and NORAD) or command (for component and CMOC) proposal should be numbered as one.

TITLE: Short title of proposal.

PREVIOUS HISTORY: Explain all previous or current attempts to obtain funding for the project. Indicate if this proposal is a C2IP resubmission. Identify original submission, indicate whether Joint Staff validated the original submission, and state why you are resubmitting it. You should not submit proposals for more than one funding source.

COST: Estimate of nonrecurring cost for acquisition should be as accurate as possible, in terms of types of funds available for the C2IP cycle (Procurement and/or O&M funds). As appropriate, itemize equipment, quantity, and unit cost. Provide a breakout and the total cost of COMSEC resources, if needed. If provided by Service COMSEC account(s), identify those accounts by command and COMSEC account number. Also include cost of leased communications (if any) and source of funding. Seek assistance from servicing comptroller for correct appropriation type.

DESCRIPTION: Describe equipment, software, or services to be acquired. Explain what it is or does. Identify equipment by nomenclature.

JUSTIFICATION: Explain how the proposal will improve the CINC's C2 capability. Be brief and clearly relate the proposal to the provisions of this instruction, especially unforeseen circumstances and immediate need. State why existing systems cannot satisfy this requirement. Indicate objectives, missions, or functions that will be adversely impacted by failure to acquire funding approval. Describe how the project will fit into the CINC's long-range objectives as defined in the C4 Systems Master Plan. Describe how the proposal will fit into the C4I for the Warrior concept.

INTEROPERABILITY:

a. Describe how this proposal will interoperate with existing equipment and how you will achieve compliance with standards. Specifically address the proposal's joint interfaces and system security.

b. C2IP projects which might connect to Global Command and Control System or the Global Combat Support System should comply with the Defense Information Infrastructure Common Operating Environment. This document is available at DISA D6 at (703) 735-8768 or DSN 653-8768.

c. The proponent must review the information technology standards for implementation in the respective system/project. The applicable standards are contained in the Technical Architecture Framework for Information Management (TAFIM), Volume 7, Adopted Information Technology Standards. Include a statement that the system is TAFIM-compliant where applicable.
INTEGRATED COMMUNICATIONS DATA BASE (ICDB) NUMBER: Include all communications requirements.

TRAINING: Describe additional training required for the proposal and explain how training will be funded and who will conduct it.

ADDITIONAL HUMAN RESOURCES: Indicate whether additional human resources are required as a result of the proposal.

LOGISTICS SUPPORT: Indicate the amount, type, and provider.

OUTYEAR SUPPORT COST: Describe other costs required by, or as a result of, the project, such as recurring maintenance. Follow-on O&M costs are not fundable through the C2IP. Explain how outyear costs will be funded.

WAIVERS: Describe waivers requested, if any. Waivers from C2IP guidelines, existing standards, and other guidance must be addressed.

PROCUREMENT PLAN: Describe acquisition strategy and how funds will be obligated within 30 days.

SEND FUNDS TO: Organization or office accepting the MIPR or FCA. The address must be the accepting activity's responsible accounting and finance office or the project management point of contact. Include the full mailing address, point of contact, E-Mail and DSN and/or commercial phone and fax numbers.

PROJECT MANAGEMENT POC: Individual, rank, office, mailing address, E-Mail, and DSN and/or commercial phone and fax numbers of POC and alternate (if applicable) for the project.
BRIEFING PROPOSALS TO THE C2IP PRIORITIZATION BOARD

1. The C2IP Manager will announce how much time each briefer will have to brief his proposal and answer questions from C2IP Prioritization Board members, and he will strictly control adherence to the limits he sets.

2. Slides. As a minimum, each briefing must address the following elements.

2.1. Requirement. State the C2 deficiency you expect to correct.

2.2. Approach. Describe your technical solution.

2.3. Business Plan Elements.

2.3.1. Concept of Operations. Briefly explain how the staff and/or operators will use the acquired capability. Include the specific support the finished product will provide to CINCNORAD, USCINCSPACE, or the command and the specific CINC mission(s) that it will support.

2.3.2. Return on Investment. On this slide, make two columns labeled "Returns" and "Expected Values."

2.3.2.1. Under "Returns," list returns appropriate to your project. Examples include man-hour and cost savings greater than the cost of the project, anticipated savings over a number of years, and measurable increases in efficiency or operational improvements.

2.3.2.2. Under "Expected Values," list the values of the returns you expect to see when your project is fully implemented.

2.3.3. Required Funding Profile, Obligation Plan, and Sustainment Plan.

2.3.3.1. List the amount of funds you are requesting by type of appropriation (Procurement and/or O&M) available for the C2IP cycle. The accuracy of these figures is critical to the entire program since Joint Staff/J6 apportions each category of funds separately.

2.3.3.2. Funds POC. List the person and office to whom the C2IP Manager is to send your funds.

2.3.3.3. Funding Document Desired. List what kind of funding document the C2IP Manager should send to your funds POC (e.g., MIPR or FCA).

2.3.3.4. Funds Obligation. List the contract number(s), the government contract manager(s), and the date the funds will be on contract. If you will not be using contracts, specify the steps you will take to obligate your funds in 30 days (Purchase Requests, IMPCard purchases).

2.3.3.5. Sustainment Plan. Identify sustainment costs and funding source.

2.3.4. Timeline. Base your timeline on the day you receive your funds (label this day "Funds Received"). Build the rest of the timeline in terms of number of days before and after "Funds Received." Show the major steps, including funds obligation and purchases, it will take to acquire the new capability and finish the project.

3. Bring 10 hard copies of your briefing to give to the Prioritization Board members at the beginning of your brief.

PROJECT COMPLETION REPORT FORMAT

1. Project Managers are responsible for sending project completion reports to the C2IP Manager within 30 days after project completion. The report is a single-page, typed memorandum with enclosures.

2. Format.

2.1. Project title.

2.2. Total cost and appropriation(s).

2.3. Start date and completion date.

2.4. Contractors.

2.5. Benefit to the Warfighter.

2.6. Lessons learned.

2.7. Description. Short descriptive paragraph, to include how the project increases the Warfighter capability.

3. Enclosure. Unclassified photograph of the completed project (optional). The photograph is not required; however, it is helpful to the Joint Staff when they demonstrate C2IP benefits to DoD senior officials.