FY2010/2011 President�s Budget P- and R-Forms Data Call

Document Sample
FY2010/2011 President�s Budget P- and R-Forms Data Call Powered By Docstoc
					27 FY 2013 Budget Estimate Submission (BES)
       P-Forms and R-Forms Data Call (C16)

27.1 SUSPENSE 1: 17 AUGUST 2011 (P-FORMS)
All P-Forms are due to HQDA no later than17 August 2011.

27.2 SUSPENSE 2: 15 AUGUST 2011 (R-FORMS)
All R-Forms are due to HQDA no later than15 August 2011.

a. DoD 7000.14R, Department of Defense, Financial Management Regulation (FMR), Volume
2A and 2B, Budget Formulation and Presentation, (http://www.dtic.mil/comptroller/fmr), dated,
January 2011 and February 2011.

b. OMB Circular A-11, Preparation, Submission and Execution of the Budget, most recently
updated July 2010.

Army Budget Office (ABO), Director of Investment Note:

      As the Army’s Director of Investment, I applaud all members of the Army
      program, budget, and acquisition communities for your continued exemplary
      contributions to our Soldiers. Your performance meeting increased reporting
      requirements under a condensed timeline was especially noteworthy and
      appreciated. It was through your expertise, adaptation, and resilience our Army
      was resourced commensurate to its wartime mission.

Resource Formulation Guide                  27-1                                   Volume 3
      Looking forward, FY13 begins a period of increased fiscal scrutiny and reduced
      funding by our elected and appointed officials as they grapple with deficit
      reduction measures and rebalancing discretionary spending. It will require each of
      us to seek efficiencies within our span of control and judiciously allocate
      resources supporting strategic Army efforts. The FY13 budget increases
      transparency to Army stakeholders – both in terms of the Overseas Contingency
      Operations (OCO) funding as well as identifying component-level funding in the
      base budget. Ensuring an accurate depiction of investment requirements across all
      components not only meets Congressional reporting requirements but strengthens
      process ownership for all Army stakeholders. And, in doing so, helps to ensure
      Army-wide priorities are appropriately resourced. I challenge you to your best
      efforts. Rest assured that the Army Budget Investment team is always available to
      assist with this mission. We are one Army team dedicated to resourcing the
      greatest fighting force ever assembled.

                                  Table 27-1. Schedule of Events
                                    EVENT                                  DATE
       1. ABO makes draft Annexes available to the field                 21 Jun 11
       2. ABO makes draft COMPO Split available to the field             22 Jun 11
       3. P&R Forms available in system                                  22 Jun 11
       4. Draft Annex and COMPO Split due to ABO (FIRM)                  27 Jun 11
       5. RFS Lock for P&R Forms (Dollars/QTY and COMPO)                  5 Jul 11
       6. ABO makes final Annexes available to the field                  8 Jul 11
       7. ABO makes final COMPO Split available to the field              8 Jul 11
       8. RFS Quantities Lock (AMMO ONLY)                                 15 Jul 11
       9. ABO makes final Annex available to field (AMMO ONLY)            18 Jul 11
       10.R-Forms due to ABO (FIRM)                                      15 Aug 11
       11.P-Forms due to ABO (FIRM)                                      17 Aug 11
       12.DASC/SSO comments on P&R forms due to ABO                      24 Aug 11
       13.GO/SES Review                                                  26 Aug 11
       14.Printer                                                        31 Aug 11
       15.Final to OSD/OMB                                                6 Sep 11

a. This chapter provides updated guidance and submission requirements for preparing Army
Procurement Backup Books (P-Forms) and Research, Development, Test, and Evaluation
(RDTE) Descriptive Summaries (R-Forms) in support of the FY13 Budget Estimate Submission

Resource Formulation Guide                       27-2                                 Volume 3
                          FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

b. Request addressees prepare P-Form and R-Form exhibits and supplementary schedules with
dollars and quantities, as appropriate, to reflect the budget database lock. See Table 27-1 for
database lock schedule.

c. Table 27-1 provides the timeline to prepare budget justification materials. Section 27.11
provides HQDA Staff functional area POCs. Section 27.11 provides general preparation
guidance for P-Forms. Section 27.16 provides general R-Form preparation guidance.

d. Program dollar amounts and quantities will include both base and OCO numbers. These
dollars will now be broken out into separate columns on both the P-40 and P-5 for procurement.
Refer to Section 27.16.1 for further RDT&E OCO guidance.

e. FY11 and FY12 columns for funding will be locked, but must be consistent with the
FY12 President’s Budget program amounts. The only changes to these two years will be to
ensure the program passes validation. All top line numbers MUST NOT be changed.

f. All P-Forms and R-Forms will be dated “September 2011.”

g. The Chemical Demilitarization appropriation will not use the P&R Forms software
application to prepare justification materials.

a. System Administrators now have the ability to suppress FY’s in individual sections of the

b. R2 will automatically sum when Project dollars are changed, when you hit import funds or
when you turn on/off projects within a PE.

c. Base and OCO requests will now be split into separate columns on the P-40 and P-5.

d. Budget data will be transferred from locked Resource Formulation System (RFS) positions to
the Web Army RDA Budget Update Computer System (WARBUCS) and P/R System. It is vital
that you check P-Form and R-Form data with the official data in RFS to ensure accuracy. All
files will be located in the download section of the system for easy access

e. Columns will be locked with no means for data entry for any FY that should not change. The
column header will display a padlock to let the user know the field is locked.

f. Import Funds will now provide a message stating funds will import to the parent and all
associated projects. You will be given the opportunity to either cancel the import or continue.

g. Starting with FY13 BES, there is a requirement for all appropriations to submit their budget
in the new XML format. Prior to FY13 only RDTE documents were in this format. This process
is done through a web service operated by the Defense Technical Information Center (DTIC).

h. To ensure all forms meet this new requirement it will be necessary to validate the data entered
before programs are submitted to HQDA. The validation process will begin when the user tries

Resource Formulation Guide                     27-3                                     Volume 3
to move items from field ready to HQDA open, see Section 27.17 for examples of the process
and errors/warning that could prevent the forms from being submitted.

a. Go to the following URL in Internet Explorer: https://pandr.altess.army.mil

b. Log in using CAC

c. If you don't have P&R Forms account, you will be taken to the New User Registration Page

d. Complete the New User Registration Form and then click submit

e. Your sponsor will receive an e-mail with your request for access

f. You will receive an e-mail when the sponsor approves your request

g. Once you receive the e-mail, go to the URL listed above

h. Log in using CAC

i. You will be redirected to the P&R Forms Homepage

j. Once access to the P&R Forms system has been approved, each user can request permissions
for specific items from the Appropriation Sponsor (as listed in Section 27.10).

Resource Formulation Guide                   27-4                                  Volume 3
                       FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

APPROPRIATION                 ASA(FM&C)                       ARMY STAFF
                                    NAME                             NAME
                                      DSN                              DSN
                             COMMERCIAL                       COMMERCIAL
                           OFFICE SYMBOL                    OFFICE SYMBOL
                           E-MAIL ADDRESS                   E-MAIL ADDRESS

AIRCRAFT                         Bill Schultz                  Brian Craddock
AND RELATED                   DSN 224-9108                     DSN 664-7019
RDT&E                          703-614-9108                     703-604-7019
                              SAFM-BUI-M                            SAAL-SA
              william.h.schultz@us.army.mil       brian.craddock@us.army.mil

MISSILES                   Beverly Turner                         Stan Darbo
(Tactical)                 DSN 224-7589                        DSN 664-7208
(Air Msl Def)               703-614-7589                        703-604-7208
AND RELATED                SAFM-BUI-M                              SAAL-SM
RDT&E         beverly.turner@us.army.mil              stan.darbo@us.army.mil

WTCV AND                       Mun Baker                        David Nelson
RELATED                     DSN 224-7992                       DSN 865-1610
RDT&E                        703-614-7992                       703-545-1610
                             SAFM-BUI-G                          SAAL-SMS
                    mun.baker@us.army.mil         david.l.nelson@us.army.mil

AMMUNITION                    Kathy Boivin                        Jeff Brooks
AND RELATED                 DSN 224-8874                       DSN 664-7212
RDT&E                        703-614-8874                       703-604-7212
                            SAFM-BUI-M                             SAAL-SM
                  mary.boivin@us.army.mil            jeff.brooks@us.army.mil

Resource Formulation Guide                 27-5                                   Volume 3
APPROPRIATION                  ASA(FM&C)                       ARMY STAFF
                                    NAME                              NAME
                                      DSN                               DSN
                             COMMERCIAL                        COMMERCIAL
                           OFFICE SYMBOL                     OFFICE SYMBOL
                           E-MAIL ADDRESS                    E-MAIL ADDRESS

OPA 1/3                           Pam Roe                          Steve Rann
AND RELATED                  DSN 224-8157                       DSN 664-7231
RDT&E                         703-614-8157                       703-604-7231
                              SAFM-BUI-C                           SAAL-ZCS
                    pamela.roe@us.army.mil                   ranns@us.army.mil

OPA 2 / 4 - ASA(RDA)         Charity Kapolka                        Mike Payne
AND RELATED                    DSN 222-8295                      DSN 664-7160
RDT&E                           703-614-8295                      703-604-7160
                               SAFM-BUI-C                            SAAL-SA
                 charity.kapolka@us.army.mil       michael.t.payne@us.army.mil

OPA 2 - ODISC4             Charity Kapolka                       Mike Ramsey
AND RELATED                 DSN 222-8295                        DSN 227-0534
RDT&E                        703-614-8295                        703-697-0534
                             SAFM-BUI-C                               CIO/G-6
              charity.kapolka@us.army.mil          michael.ramsey@us.army.mil

RDTE Admin               Tracy Washington
                            DSN 222-4943

RDTE S&T (BA 1, 2, 3)             Julie Fenton                     Lora Latham
                               DSN 224-8294                      DSN 329-2233
                                703-614-8294                      703-601-2233
                                SAFM-BUI-G                           SAAL-TS
                    julie.fenton@us.army.mil           lora.lathan@us.army.mil

RDTE Non-Acquisition     Charito Homoroc
Programs                   DSN 224-6212

Resource Formulation Guide                  27-6                                 Volume 3
                     FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

APPROPRIATION                ASA(FM&C)                      ARMY STAFF
                                 NAME                              NAME
                                   DSN                               DSN
                          COMMERCIAL                        COMMERCIAL
                        OFFICE SYMBOL                     OFFICE SYMBOL
                        E-MAIL ADDRESS                    E-MAIL ADDRESS

CHEM DEMIL                   Gary Golden                     Stephen Fahy
                           DSN 224-9268                     DSN 664-2311
                            703-614-9268                     703-604-2311
                           SAFM-BUI-M                            SAIE-CD
                 gary.golden@us.army.mil         stephen.fahy@us.army.mil

Resource Formulation Guide              27-7                                    Volume 3
a. The DoD FMR provides specific guidance for preparing each P-Form exhibit. This section
provides additional guidance for preparing these exhibits.

b. Prepare and submit P-Forms using the P&R Forms software application to ensure the forms
arrive at HQDA no later than 17 August 2011. For Standard Study Numbers (SSNs) which
belong to more than one command, the command with the largest funding amount against that
SSN is responsible for preparing the entire P-Form, with input from the other commands who
share the program, with the new XML format in place the command with the largest funding
amount will also be responsible to make sure the program is validated correctly, refer back to
paragraph 27.8 h.

c. For the P-Form Narrative Sections:

  (1) The ultimate P&R Form users are Congressional committee staffers. Funding is less likely
to be provided if the Congressional staffers cannot understand what your program provides in
support of the Army and/or Joint Force. Tailor the narrative to that audience. Keep the narratives
clear and concise, and make sure the narratives address the budget years’ activities being
justified. Make sure you say what the program is buying and why! Remember mysteries
don’t get funded and, if they do, they could become billpayers.

  (2) Use the spell check function in P&R Form on all narrative sections of all P-Forms.

  (3) P-Forms must not contain comments or footnotes related to reprogramming, withholds,
paybacks, unfunded personnel, unfinanced requirements, revised quantities, internal Army or
DoD documents such as Resource Management Decisions (RMDs).

  (4) Minimize the use of acronyms and abbreviations in the justification material. When
acronyms or abbreviations are used for the first time on a particular P-Form, they are to be
spelled out in their entirety.

  (5) Within narrative justifications, do not use "M" to denote millions. Use “million” with three
decimal places. For example, “$6K” should be “$.006 million” and “$5M” should be “$5.000

d. Pricing Procedures: Pricing procedures will be fully consistent with guidance in OMB
Circular A-11 and the OSD FY13-17 Integrated Program and Budget Guidance dated . Inflation
and spend out rates for use in developing the FY13 Budget Estimate Submission (BES) will be
the indices published in the FY12 President’s Budget, which can be found on the OSD
Comptroller website at https://guidanceweb.ousdc.osd.mil

e. Year Designations and Fiscal Years Reported:

   (1) Past Year (PY) is FY11.

   (2) Current Year (CY) is FY12.

Resource Formulation Guide                     27-8                                     Volume 3
                            FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

   (3) Budget Year (BY) is FY13.

   (4) Future Years (FYDP) is FY14-17

   (5) A complete set of budget exhibits is required for all procurement line items which reflect
   a budget request of $5M or greater in any of the three active years - Past Year (FY11),
   Current Year (FY12) or Budget Year (FY13). For programs with a funding value of less than
   $5M, only a P-40 is required.

   (6) Fiscal Year Reported: The following information details specific fiscal year requirements
   for each exhibit: Date on P-Forms: Will be automatically populated by the P&R Forms
   software and will display "September 2011" for the FY13 Budget Estimate Submission.

f. Item Nomenclature, SSN, and Budget Line Item Number (BLIN) will be automatically
populated by the P&R Forms software and will match the P-1.

g. Required P-Forms: The following are the P-Forms to be submitted for each procurement
appropriation, as applicable. Refer to Chapter 4, FMR, Volume 2A, for required exhibits and
their proper sequencing, as the P-Form requirements and their sequencing vary, depending on

              Prepared by the field proponents              Prepared by HQDA
              P-3a              P-21                 P-1/R-1   SAFM-BUI-C/G/M
              P-5               P-25                 P-1R      G8 (with SAALT
              P-5a              P-26                           assist)

              P-5e              P-40
              P-10 Series       P-40M
              P-17              MYP Exhibits

   (1) P-3a exhibits will show the financial plan for FY11-17. The P-3a Installation Schedule
   will show uninstalled equipment for Prior Years, as well as Planned Installations for
   FY11-17. Installation costs must be reflected in the fiscal year the installation of mod kits
   actually occurs. The FMR now requires a P-3a be submitted for any modification new
   start with first year costs over $2 million or more than $10 million within three years.

   (2) P3a will now show contract dates for prior years as well as the current budget year.

   (3) P5 – when showing your OCO request on the P5 make sure you meet one of OSD/OMB
   criteria for your request. They are listed in Section 27.14.

   (4) The P5 is now the only form that Unit Cost and Quantity can be selected. The selected
   unit cost and quantity will automatically populate the P5a and P21.

   (5) COMPO Split is not to be used as a Cost Element.

Resource Formulation Guide                       27-9                                   Volume 3
   (6) P5a exhibits will address FY11-13; a P-5a is required for all OPA programs that fall
   under the “Items Less Than $5 million” line.

      P5a will now display MDAP codes for ACAT programs.

      “Procurement History and Planning:” show actual data for the last contract award made
       in the Past Year or most recent unexpired program year in which the item was procured.

      For contractor data, include plant location (city and state). When filling in the contractor
       data, whether you use Contractor Method and Type or Funding Vehicle, you must use
       only what is in the drop down list. For the Current Year and Budget Year, insert the
       contractor name/location if the item is to be procured sole source; otherwise insert
       "TBS/TBD." You must use either TBS or TBD consistently through the document.

      The unit cost reflected in the P-5a is the hardware unit cost, which must track to the P-5
       hardware costs. P-5e exhibits are required for ACAT I and II systems. (Sections 23.11
       and 23.12)

   (7) Exhibit P-20 will be prepared for ACAT I/II systems, which have been identified in
   Sections 23.11 and 23.12. Procurement of Ammunition, Army appropriation will prepare the
   Exhibit P-20 for all budget line items. NOTE: For the Procurement of Ammunition, Army
   appropriation, the Exhibit P-20 is prepared in the Ammo system and not the P&R Forms

   (8) P-21 exhibits will display the delivery schedules for FY11–FY13 program quantities.
   Show actual quantities accepted in FY11 (prior to 01 October 2011). Monthly production
   schedules will begin with FY11 and continue for as many fiscal years as are necessary to
   display monthly deliveries of all program quantities. You must also show deliveries for all
   quantities procured for other services to include FMS.

      COMPO Splits will no longer be shown on the P-21.

      P-21 is not necessary if item being procured is either a COTS or GOTS. Annotate this on
       your P5a.

   (9) P-40 exhibits will reflect FY11-17. Appropriation sponsors will provide Base and OCO
   funding detail to their respective business managers. Business managers will spread these
   numbers across all appropriate SSNs within the BLIN using budget numbers provided in
   ANNEXES. Numbers should not be changed. For the Other Procurement, Army (OPA)
   appropriation, indicate the Approved Acquisition Objective (AAO) on all P-40s.

        Please remember to identify all related RDTE Program Elements (PEs).

        If funding for a program continues past FY17, you must put “Continuing” in both the
          To Complete and the Total Program Columns.

        Please be sure to include the Cost to Complete (TC) funding amounts for all ACAT

Resource Formulation Guide                    27-10                                      Volume 3
                          FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

      The below change pertains only to how the forms will be printed in XML. They will still
       be created the same way in ALTESS.

        Baby P-40s will no longer be printed. For programs that have funding greater than
           $5M, the funding will print on a new P5 and programs that have funding less than
           $5M funding will print on a new P40a.

h. Item Description, Justification, and Compo Split. In most cases, the narrative on the P-40
should not exceed one page and will be divided into two separate paragraphs labeled
"DESCRIPTION" and "JUSTIFICATION.” These narratives should be in layman terms with all
acronyms spelled out on each page the first time they appear. Abbreviations should be kept to a
minimum, but when used they should be obvious to those without detailed technical knowledge
of the item.

   (1) DESCRIPTION: Describe the function and capabilities of each item being procured. The
   narrative should also provide a clear, concise statement relating planned procurement to the
   total objective for the line item. The P-40 should stand alone in justifying new programs. The
   Description should ONLY say what the program is and not why the program needs money.

   (2) JUSTIFICATION: This section will include separate paragraphs for BASE and OCO
   requirements. Each paragraph will briefly explain why the item is needed, and why it must be
   procured in FY13. If applicable, operationalize the procurement requested (e.g., procures
   enough YYY for one IBCT). For all procurement appropriations with the exception of
   Procurement of Ammunition, insert the sentences “FY13 Base procurement dollars in the
   amount of $XX.XXX million supports…” and “FY13 OCO procurement dollars in the
   amount of $XX.XXX million supports…”. Procurement of Ammunition, Army (PAA)
   appropriation (see paragraph 3 below for PAA).

   (3) JUSTIFICATION for PAA: The first sentence of the Justification for Procurement of
   Ammunition, Army appropriation will start with the following: “This is a training standard
   (or training unique or war reserve) item”. The second sentence must be “The FY13 supports
   annual training and builds a war reserve inventory in accordance with the Army procurement
   goals”. The next sentence begins “FY13 Base procurement dollars in the amount of
   $XX.XXX million supports…”. The next paragraph begins with “FY13 OCO procurement
   dollars in the amount of $XX.XXX million supports…”

   (4) COMPO SPLIT: This section will include a breakout of quantities and amounts at the
   resourced SSN level (baby SSNs) and will be rolled to the parent P40. COMPO Splits passed
   from RFS to P-40s MUST NOT BE CHANGED. COMPO Split will now be included on
   P5 because of new XML format.

i. Multiyear Procurement Contracts: For Multiyear (MY) procurements proposed for FY13, use
the P-5a exhibit to provide the estimates for those programs. A complete set of exhibits
contained in the DoD FMR will be prepared for each MYP. This includes any program requiring
FY13 advance procurement funding to support later multiyear contracts. Submission will be
made for all new or revised multiyear candidates even if they do not exceed the thresholds
outlined in the FMR.

Resource Formulation Guide                   27-11                                    Volume 3
j. Until the RFS database can be updated to show the OCO amounts in the ANNEX, the only
place they will be annotated will be the P1. A copy of this document will be included in the
download section of P/R System.

k. Low Rate Initial Production (LRIP): The FMR requires LRIP be procured with procurement
dollars if the asset originally procured for testing will subsequently be fielded (previously you
could use either RDT&E or Procurement).

l. Armament Retooling and Manufacturing Support (ARMS) Program: Use of PAA for the
ARMS program requires submission of exhibits listed below per OMB Circular A-11. Section
185 of that Circular provides detailed instructions to complete these exhibits. For completion of
OMB submission requirements, as well as gaining OUSD approval for the ARMS Guaranteed
Loan Program, each individual loan must be supported by the following exhibits:

   (1) Schedule P: Program and Financing Schedule for the ARMS Initiative Guaranteed Loan
   Financing Account (one for each guarantee).

   (2) Schedule H: Status of Guaranteed Loans (one for each guarantee).

   (3) Schedule F: Balance Sheet (one for each guarantee).

   (4) Schedule U: Summary of Loan Levels and Subsidy Data (one for each guarantee and one
   which consolidates multiple guarantees from the same point of origin). This exhibit will also
   include a narrative statement describing the location, name of business, kind of business,
   name of lender, and guaranteed loan terms, the government’s subsidy cost and rate; and the
   Army point of contact at PEO Ammunition.

m. The Exhibit 300 Reports (Capital Planning and Business Case Reports), while not a part of
the P- or R- Forms justification books, are a budget justification and reporting requirement for
major Information Technology (IT) investments. Section 300 of OMB Circular A-11 outlines the
guidelines for the Exhibit 300 reports. Exhibit 300 reports are submitted to the Office of
Management and Budget (OMB) as part of the BES. OMB evaluates the Exhibit 300 Reports as
part of the Budget Pass Back in the Nov/Dec timeframe. The reports are then updated as part of
the President’s Budget submission. The CIO/G6, in coordination with the Army Budget Office,
works with the program managers and manages the submission of the Exhibit 300 reports.
Coordination among preparing officials is critical to ensure consistent justification on the
submissions. Inconsistencies in information reported in the P- and R- Form justification and the
Exhibit 300 reports have resulted in budget reductions in the past. Program managers, PEOs, and
Department of the Army System Coordinators (DASCs) should review both documents to ensure
the justification is consistent. As with most budget displays this year, Exhibit 300 Reports will
include FY11-FY17

Resource Formulation Guide                    27-12                                     Volume 3
                          FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

         Maneuver Control System (Army Tactical Command and Control System)
         Stock Control System (SCS)
         Integrated Maintenance Data System (IMDS)
         Global Command and Control System - Army (GCCS-A)
         Mounted Battle Command on the Move
         Joint Ammunition Management Standard System (JAMSS)
         Global Transportation Network (GTN)
         General Fund Enterprise Business Systems
         Laser Hellfire
         Patriot Advanced Capability-Third Edition (PAC-3)
         Light Utility Helicopter
         Guided Multiple Launch Rocket System DPICM/Unitary (Tactical Rockets)
         Cargo Helicopter (CH-47F) CH-47D Upgrade
         Javelin (Advanced Anti-Tank Weapon System--Medium)
         Force XXI Battle Command Brigade and Below (FBCB2)
         Excalibur - Projectile, 155mm Extended Range (XM982)
         High Mobility Artillery Rocket System (HIMARS)
         Longbow Hellfire- Hellfire Missile System
         Abrams Tank Upgrade (M1A2)
         Bradley Fighting Vehicle Systems Upgrade
         Family of Medium Tactical Vehicles (FMTV)
         Longbow Apache (AH-64D) (LBA)
         High Mobility Multi-Purpose Wheeled Vehicle (HMMWV) Family of Vehicles
         Guided MLRS DPICM/AW
         Black Hawk Upgrade - Utility Helicopter Upgrade
         Armed Reconnaissance Helicopter

Resource Formulation Guide                   27-13                                   Volume 3
         Joint Cargo Aircraft
         Longbow Apache Block III
         Chemical Demilitarization-Assembled Chemical Weapons Alternatives
         Joint Tactical Radio System Network Enterprise Domain
         Chem Demil-Chemical Materials Agency
         Stryker-Armored Vehicle
         Brigade Combat Team (BCT) Modernization
         Modernized UH-60 Black Hawk
         Warfighter Information Network Tactical Increment 1
         Warfighter Information Network Tactical Increment 2
         Warfighter Information Network Tactical Increment 3
         DoD High Performance Computing Modernization Program
         Joint Tactical Radio System Ground Mobile Radio
         Joint Land Attack Cruise Missile Defense Elevated Netted Sensor System
         Ground Soldier Ensemble (GSE)
         Joint Tactical Radio System Handheld, Manpack, Small Form Factor
         Global Combat Support System-Army (GCSS-Army)
         Gray Eagle TUAV Extended Range/Multiple Purpose
         Joint Tactical Radio System Airborne and Maritime/Fixed Station
         PATRIOT/MEADS Combined Aggregate Program
         Theater High Altitude Area Defense (THAAD)
         Mine Resistant Ambush Protected
         Multifunctional Information Distribution (MIDS)
         Spin-Out Early Infantry Brigade Combat Team

Resource Formulation Guide               27-14                                    Volume 3
                        FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

   Army Data Distribution System (Data Radio)
   Advanced Field Artillery Tactical Data System (AFATDS)
   Battle Command Sustainment Support System (BCS3)
   Secure Mobile Anti-Jam Reliable Tactical Terminal (SMART-T)
   Forward Area Air Defense Command and Control (FAAD C2)
   Common Hardware Systems (CHS)
   Lightweight 155mm Howitzer System (LW-155)
   PALADIN/Field Artillery Ammunition Support Vehicle
   Standard Integrated Command Post System
   Joint Land Component Constructive Training Capability
   Joint Biological Point Detection System (JBPDS)
   2.75 Inch Rocket Systems
   Tactical Unmanned Aerial Vehicle
   Monocular Night Vision Devices (MNVD) AN/PVS-14
   Night Vision Thermal Systems - Thermal Weapon Sight (TWS)
   Intelligent Munition System
   Precision Guided Mortar Munition (PGMM)
   Common Remotely Operated Weapon System (CROWS)
   Close Combat Tactical Trainer (CCTT)
   Multiple Integrated Laser Engagement System
   Cartridge, 120mm, APFSDS-T, M829A3
   Surface Launched Advanced Medium Range Air-To-Air Missile
   Mid Range Munition
   Mounted Soldier System
   ZZ - AcqBiz Testing-Training program in production
   Region Joint Battle Command-Platform

Resource Formulation Guide                 27-15                                   Volume 3

27.14.1 Major Equipment
a.     Replacement of losses that have occurred only for items not already programmed for
replacement in the Future Years Defense Plan (FYDP) – no accelerations. Accelerations must
be in the base budget.

b.     Replacement or repair to original capability (to upgraded capability if that is currently
available) of equipment returning from theater. The replacement may be a similar end item if
the original item is no longer in production. Incremental cost of non-war related upgrades, if
made, should be included in the base.

c.     Purchase of specialized, theater-specific equipment.

d.     Funds must be obligated within 12 months.

27.14.2 Ground Equipment Replacement
Combat losses and washouts (returning equipment that is not economical to repair); replacement
of equipment given to coalition partners, if consistent with approved policy; in-theater stocks
above customary equipping levels on a case-by-case basis.

27.14.3 Equipment modification (enhancements)
Operationally-required modifications to equipment used in theater or in direct support of combat
operations, for which funding can be obligated in 12 months, and that is not already in the

27.14.4 Munitions
Replenishment of munitions expended in combat operations in theater. Training ammunition for
theater-unique training events is allowed. Forecasted expenditures are not allowed. Case by
case assessment for munitions where existing stocks are insufficient to sustain theater combat

27.14.5 Aircraft Replacement
Combat losses, defines as losses by accident or by enemy action that occurs in the theater of

27.14.6 Research and Development
Projects required for combat operations in specific theaters that can be delivered in 12 months.

Resource Formulation Guide                    27-16                                     Volume 3
                          FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

27.14.7 Exclusion from War/Overseas Contingency Funding
The items listed below are more appropriately funded in the base budget. TRAINING EQUIPMENT
Training vehicles, aircraft, ammunition, and simulators. Exception: training base stocks of
specialized, theater-specific equipment that is required to support combat operations in the
theater of operations, and support to deployment-specific training described above. EQUIPMENT SERVICE LIFE
Acceleration of SLEPs already in the FYDP. INDUSTRIAL BASE CAPACITY
Programs to maintain industrial base capacity (e.g., “war-stoppers”)

Items proposed for increases in reprogrammings or as payback for prior reprogrammings must
meet the criteria above.

          Contract Methods/Types
SS/FP     Sole Source/Fixed Price
C/FP      Competitive/Fixed Price
SS/FFP    Sole Source/Firm Fixed Price
C/FFP     Competitive/Firm Fixed Price
SS/FPEPA  Sole Source/Fixed-Price Economic Price Adjustment
C/FPEPA   Competitive/Fixed-Price Economic Price Adjustment
SS/FPIF   Sole Source/Fixed-Price Incentive Firm
C/FPIF    Competitive/Fixed-Price Incentive Firm
SS/FPIS   Sole Source/Fixed-Price Incentive Successive Targets
C/FPIS    Competitive/Fixed-Price Incentive Successive Targets
SS/FPAF   Sole Source/Fixed-Price Award-Fee
C/FPAF    Competitive/Fixed-Price Award-Fee
SS/FPRP   Sole Source/Fixed-Price with Prospective Price Redetermination
C/FPRP    Competitive/Fixed-Price with Prospective Price Redetermination
          Sole Source/Fixed Ceiling Price with Retroactive Price
SS/FPRR   Redetermination
          Competitive/Fixed Ceiling Price with Retroactive Price
C/FPRR    Redetermination
SS/FFPLOE Sole Source/Firm Fixed Price, Level of Effort

Resource Formulation Guide                    27-17                                     Volume 3
C/FFPLOE     Competitive/Firm Fixed Price, Level of Effort
SS/CR        Sole Source/Cost
C/CR         Competitive/Cost
SS/CS        Sole Source/Cost Sharing
C/CS         Competitive/Cost Sharing
SS/CPIF      Sole Source/Cost-Plus Incentive-Fee
C/CPIF       Competitive/Cost-Plus Incentive-Fee
SS/CPAF      Sole Source/Cost-Plus Award-Fee
C/CPAF       Competitive/Cost-Plus Award-Fee
SS/CPFF      Sole Source/Cost-Plus Fixed-Fee
C/CPFF       Competitive/Cost-Plus Fixed-Fee
SS/IDDQ      Sole Source/Indefinite Delivery, Definite Quantity
C/IDDQ       Competitive/Indefinite Delivery, Definite Quantity
SS/IDRT      Sole Source/Indefinite Delivery, Requirements
C/IDRT       Competitive/Indefinite Delivery, Requirements
SS/IDIQ      Sole Source/Indefinite Delivery, Indefinite Quantity
C/IDIQ       Competitive/Indefinite Delivery, Indefinite Quantity
SS/T&M       Sole Source/Time and Materials
C/T&M        Competitive/Time and Materials
SS/LH        Sole Source/Labor-hour
C/LH         Competitive/Labor-hour
SS/Letter    Sole Source/Letter
C/Letter     Competitive/Letter
SS/BA        Sole Source/Basic Agreement
C/BA         Competitive/Basic Agreement
SS/BOA       Sole Source/Basic Ordering Agreement
C/BOA        Competitive/Basic Ordering Agreement
SS/BPA       Sole Source/Blanket Purchasing Agreement
C/BPA        Competitive/Blanket Purchasing Agreement
SS/UCA       Sole Source/Undefinitized Contract Action
C/UCA        Competitive/Undefinitized Contract Action
SS/TBD       Sole Source/To Be Determined
C/TBD        Competitive/To Be Determined
SS/Various   Sole Source/Various
C/Various    Competitive/Various

             Funding Vehicles/Other
Allot        Allotment
Sub Allot    Sub Allotment
IA           Interagency Agreement
MIPR         Military Interdepartmental Purchase Request
FFRDC        Federally Funded Research & Development Center
RO           Reimbursable Order

Resource Formulation Guide                27-18                     Volume 3
                     FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

Reqn        Requisition
PO          Purchase Order
WR          Work Request
Grant       Grant
TBD         To Be Determined
Various     Various

Resource Formulation Guide              27-19                                   Volume 3
        SUBMISSION (R-2/R-2A/R-3/R-4/R-4A/R-5
27.16.1 General
a. It is imperative that each R-Form briefly and accurately describe and display the Army’s
programs and clearly report senior Army leadership decisions. When submitted to Congress, the
R-Form presents the DoD position; as such, it will not contain language criticizing or
questioning DoD or HQDA decisions. Any reference to internal Army or DoD planning

b. You are reminded to ensure:

      All data field entries, including those that are automatically populated, are verified for

      All acronyms and abbreviations are spelled out when they are first used in each R-Form

      All narrative language is written in layman terms to the greatest extent possible; technical
       language must be kept to a bare minimum and mathematical or scientific notations will
       not be included.

      That the terms “K” to denote thousands and “M” to denote millions are not to be used in
       narrative justification; these terms must be spelled out.

      R-Forms must conform to instructions provided in the DoD FMR. The updated FMR is
       available at: http://www.dtic.mil/comptroller/fmr/

        Scroll down the page until the FMR chapters are visible

        Select Volume 2A, Chapter 1 for general guidance

        Select Volume 2B, Chapter 5 for specific RDTE guidance, including detailed R-Form

c. R-Forms will be completed using the P&R Forms application so the forms arrive at
HQDA no later than 15 August 2011. Refer to Section 27.9 of this chapter (above) for
registration guidance.

d. Final FY12 President’s Budget (PB) R-Forms (dated February 2011) will be used as the start
point for this submission. Previous R-Forms submissions are archived at the P&R Forms home
page and may be accessed for review.

e. Fiscal Year’s 2011-2017 will be displayed in the R-forms.

Resource Formulation Guide                     27-20                                      Volume 3
                          FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

f. NOTE: FY 2012 will not be updated at this time.

g. The following excerpt from the OSD FY2013-FY2017 Integrated Program/Budget
Submission is provided, detailing the specific construct of the R-Form Exhibits.

       If an RDT&E Program Element received or is expected to receive funding from
       supplemental appropriations or Overseas Contingency Operations (OCO), these amounts
       shall be included in the totals in all exhibits and broken out in footnotes on the R-2
       exhibit for current budget year.

      All data, to include the Exhibit R-4 and R-4a should reflect development from FY2011-
       FY2013. The R-1 exhibit will display line item funding detail for FY2011, FY2012, and
       FY2013. The FY2012 request will be displayed as the sum of the annual base funding
       and the OCO funding. The FY2013 request will be displayed in three (3) columns each:
       (1) the annual base funding; (2) the OCO funding; (3) Total Request.

      The R-2 and the R-2a funding table should display the combined costs of both the annual
       base request and the Overseas Contingency Operations (OCO) request. This would track
       to the funding displayed in the revised construct for FY2011, FY2012, and FY2013.
       Components would use the Description section of the R-2 and the R-2a to separately
       describe the effort being funded with the base and with the OCO requests. It is assumed
       that the R-3, R-4 would for the most part be identical.

h. Requirements for submission of R-Form Descriptive Summaries are as follows:

      No R-Forms are required if the program element (i.e., all projects in the PE) has no
       funding in FY11 through FY13.

      Exhibit R-2 is required for every PE if one or more projects are funded in any year
       between 2011 through 2013 regardless of the amount.

      Exhibit R-2a shall be prepared for each project with funding in any year from FY11
       through FY13 regardless of the amount to include those projects containing only
       Congressional adds.

      Exhibit R-3 shall be prepared for each project with funding FY13 in Budget Activities
       (BAs) 4, 5 and 7.

      Exhibits R-4 and R-4a shall be prepared for each project with funding in FY13 in BAs 4,
       5, and 7.

      In those cases where a PE or project is shared by more than one organization, each
       organization will be granted field view and edit permissions to prepare its portion of the
       R-Form. The organization with the greater distribution of dollars overall in the PE will
       prepare the PE level (summary) R-2 Forms and coordinate the consolidated package with
       HQDA Staff POCs for R-Form submission.

Resource Formulation Guide                   27-21                                     Volume 3
27.16.2 R-Form Update Requirements
a. Resource Summary (Exhibit R-2 & R-2A): The database will include base and OCO for
FY11-FY12 and base for FY14 – FY17. The FY13 base and FY13 OCO, and FY13 total will be
displayed separately in the table.

b. Mission Description and Budget Item Justification (Exhibits R-2 and R-2a): This Section
will contain the information from the FY12 President’s Budget (PB). The R-2 shall include a
description and justification of the efforts included in the Program Element (PE). The R-2A
shall include a description and justification of the efforts included in the specific project.

c. This budget submission is for FY13 and will require narrative bullets in the
“Accomplishments/ Planned Program” section for fiscal years 2011 through 2013. Efforts for
each fiscal year will be placed in a separate row even if the effort continues across the fiscal
years. It is important to note that no two efforts should have same descriptive title. This will
cause errors in form validation.

NOTE: The totals for the “Accomplishments/Planned Program Table” (R-2A) and the R-3 must
balance to the final database lock.

      Accomplishments: An accomplishment is an effort which was completed using FY10

      Planned Program: If an effort continues past FY11, or does not begin until FY12 and
       beyond, it is considered a “planned program.” Existing bullets should be modified as
       necessary to reflect all changes since the FY12 Budget Estimate Submission.

d. Small Business Innovative Research/Small Business Technology Transfer Program
(SBIR/STTR) Adjustments: The FY11 database will be adjusted prior to the 30 June 2011
database lock and therefore should NOT be reflected here. FY2011 SBIR/STTR reductions will
be reflected under the Program Change Summary (FY2011 column). Program Change Summary
(Exhibit R-2): This table shows five columns, one each for FY11, FY12, FY13 Base, FY13 OCO
and FY13 Total.

      Previous President’s Budget: This row will be populated with the official FY12
       President’s Budget database position.

      Current Budget Submit (FY13 BES): This row will be populated with the current
       database lock to include the data entered manually.

      Total Adjustments: This row will automatically calculate the delta between the “Previous
       President’s Budget” and the “Current Budget.” A breakout of the “Total Adjustments”
       delta should be provided using the appropriate rows below the “Total Adjustments” line.

      “Congressional General Reductions” (FY 2011 column only) include undistributed
       reductions as shown on the FY11 RAP that do not identify a specified line (e.g., FFRDC
       and Economic Assumptions).

Resource Formulation Guide                    27-22                                     Volume 3
                          FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

      “Congressional Directed Reductions” (FY 2011 column only) include specified
       reductions directed to specific PE/projects.

      “Congressional Rescissions” (FY 2011 column only) include both specified and
       unspecified rescissions.

      “Congressional Adds” FY 2011 displays increases to specified program elements/projects
       to include additions to the FY11 base and OCO Supplemental accounts.

      Congressional Directed Transfers (FY 2011 column only) include any Congressional
       directed transfers from other appropriations.

      SBIR/STTR Transfer – (FY 2011 column only) FY11 SBIR/STTR reductions will be
       reflected here Adjustments to Budget Years: Entries in the FY2013 column should be
       limited only to the “Adjustments to Budget Year” row, except for FY13 OCO requests
       which should be entered in the Congressional Adds row.

      In the Program Change Summary edit screen of the P&R Form application, there is an
       additional line at the bottom of the table, which will display a delta between the total of
       the entries you have made and the “Total Adjustments” line. If the figures in this row are
       red in any of the columns, you are out of balance with the “Total Adjustments” line and
       you will need to make a change to your entries to bring the total in line with the “Total
       Adjustments” delta. Not doing so will result in a validation warning that will need to be
       corrected before for can be submitted to HQ.

      Change Summary Explanation: This section is applicable to all years, including FY11.
       Explain any significant changes (+/- 10%) since the FY11 President’s Budget
       submission, including the amount of change (+/-), by year. Significant changes include
       +/- 10% funding, schedule or technical changes. Also include FY11, FY12 and FY13
       OCO requests. The FY13 OCO request entries should read as: “Anticipated FY __
       Overseas Contingency Operations Supplemental request increase.”

e. Other Program Funding Summary (Exhibit R-2A for Projects in BAs 4, 5, and 7 only): Refer
to DoD FMR, Chapter 5, page 5-15, for specific requirements to complete this table. The table
will reflect all years from FY11 through FY17.

f. Acquisition Strategy (Exhibit R-2A for Projects in BAs 4, 5 and 7 only): Provide an
explanation of acquisition, management and contracting strategies for each project.

g. Army RDT&E Cost Analysis (Exhibit R-3): This form is required for all projects in BAs 4, 5
and 7, which have funding greater than $1 million in FY13. The FMR contains directions in
Volume 2B, Chapter 5, pages 5-18/5-19, should you require instructions before entering data.
Data should be accurate as of the final database lock. Be sure to separate the FY13 Base and
FY13 OCO efforts in separate rows and columns.

h. Schedule Profile (Exhibit R-4): This exhibit is required for all projects in BAs 4, 5, and 7,
which have funding in FY12. The R-4 provides a schematic display of major program milestones
such as engineering milestones, acquisition approvals, test and evaluation events, and other key

Resource Formulation Guide                    27-23                                      Volume 3
milestones for the program. It covers both the budget years and program years (FY11 through
FY17). Be sure to include FY12 OCO effort schedules.

i. OSD (DOT&E) has been particularly critical of variances and inconsistencies between test
data submitted on the T&E 1 exhibits and the test data reflected in the R-3 Exhibits of the
Army’s R-Form submission. Please note that R-3 test information should correlate to the T&E 1
Exhibit information, which is submitted separately.

j. Schedule Profile Detail (Exhibit R-4a): This exhibit is required for all projects in BAs 4, 5 and
7 which have funding in FY13. This chart provides a tabular display of the major program
milestones identified on the R-4, as well as any additional program events contributing to and
supporting the schedule profile identified on the R-4. Such events may include LRIP approval,
Milestone B or C, IOC, Developmental Test and Evaluation, and Operational Test and
Evaluation for the total program. The table must be filled in, as appropriate, for FY11 through
FY17. Adjust all years, as necessary, to reflect schedule changes, which have occurred since the
FY13 Budget Estimate Submission. Be sure to include FY13 OCO impacts to the schedules.

k. Termination Liability Funding for Major Defense Acquisition Programs (Exhibit R-5): This
exhibit is required for all ACAT I RDTE programs. This exhibit should include funds budgeted
for termination liability within ACAT I RDTE programs. As applicable, identify the funded
levels specified in the contract by year.

27.16.3 Classification
This submission of RDTE R-Forms will be unclassified. R-Forms for classified programs or
Special Access Programs (SAP) will be provided through separate channels. Any non-SAP
classified R-Forms should be coordinated, approved, and cleared through the HQDA Deputy
Chief of Staff for Intelligence, DCS, G-2.

Resource Formulation Guide                     27-24                                     Volume 3
                         FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

When you hit the submit button you will see a message that states “Running validation ….” (see
Figure 27-1).

                                         Figure 27-1

Please be patient as this may take several minutes. Once the validation is complete the system
will display a “Validation Results” window where you will see a line for each Program Element
(PE) that you submitted.

As you can see in Figure 27-2, RDT&E PEs: 0102419A, 0203752A, and 0203744A were

                                         Figure 27-2

For each PE submitted, you will see a line with “Errors”, “Warnings”, or “Passed” in bold text.
For submitted PEs with “Errors”, you can view the errors or the XML, and you can also
download the XML by clicking on the link that for the action you want to perform. For submitted
PEs with “Warnings”, you can view the warnings or the XML, or download the PDF of XML by
clicking on the link for the action you want to perform. For submitted PEs that “Passed”
validation, you can view the XML, or download the PDF or XML by clicking on the action that
you wish to perform.

Resource Formulation Guide                  27-25                                    Volume 3
When you click the “Ok” button, all PEs that “Passed” validation will automatically move to
HQ, while any PEs containing “Errors” or “Warnings” will remain in Field Ready until the
issues causing the “Errors” or “Warnings” have been fixed.

      The errors are structure in nature, meaning there is information missing from the forms.

      The warnings are a result of the math being incorrect.

NOTE: Once you fix all “Errors” you may still have “Warnings” the next time you try to

In Figure 27-2 above, PE 0102419A has errors annotated by the word “Errors” in bold,
underlined text. This is a hyperlink, so to see the errors for this PE you must click on the
“Errors” link. The output will change to display the two structure errors as seen in Figure 27-3

                                           Figure 27-3

Each “Structure Error” will be preceded by “Go to Line”, which is a hyperlink to the incorrect
line in the XML file. When this link is clicked, a new window will open displaying the XML file
showing a highlighted line where the incorrect data is according to the DTIC standard.

Resource Formulation Guide                    27-26                                     Volume 3
                          FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

                                           Figure 27-4

The above Structure error shown in Figure 27-4 was caused because the titles are not unique.

To correct this error simply change one of the titles (i.e., remove the acronym from the second

In Figure 27-3 above, PE 0203752A has warnings annotated by the word “Warnings” in bold,
underlined text. This is a hyperlink, so to see the warnings for this PE you must click on the
“Warnings” link. The output will change to display the two warnings as seen in Figure 27-5

Resource Formulation Guide                    27-27                                    Volume 3
                                         Figure 27-5

Each warning message will contain the PE, Project Number, and Project in square brackets “[]”
and a message describing the DTIC rule that was broken.

                                         Figure 27-6

The warning shown in Figure 27-6 can be fixed simply by putting the amount of budget
adjustments in either row 12, 13, or 14.

Resource Formulation Guide                  27-28                                   Volume 3
                           FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

Starting with Figure 27-7, you will see examples of a few Procurement Errors/Warnings and how
to fix them.

                                           Figure 27-7

There are three different errors with this SSN. 1. 2 & 3.

Resource Formulation Guide                     27-29                                  Volume 3
To fix these errors to pass validation you will need to do the following:

                                           Figure 27-8

1. When you have more than one other related program element, you need to use a comma, not a

                                           Figure 27-9

2. There are duplicate names in “cost elements” on the P5. You must not have duplicate entries.
If you have more than one cost element titled “Fielding” you will need to make a distinction
between them (such as A. Fielding – B. Fielding ). You can use whatever you prefer as long as it
makes them different.

Resource Formulation Guide                     27-30                                  Volume 3
                           FY 2012Budget Estimate Submission (BES) P- and R-Forms Data Call (C16)

                                           Figure 27-10

3. The reason this is showing an error for Project Number (reference to a baby SSN) is because
there are also duplicate cost elements on the baby SSNs even though they are turned off. Any
program that is included in the submission, even if it is turned off, must pass the validation rules.

Resource Formulation Guide                     27-31                                      Volume 3

Shared By: