An indispensable tool for resource management in Afghanistan: the requirements and Resourcing Documents (RRD) database.

Author:Peters, Sabine
 
FREE EXCERPT

There are three words that sum up coalition efforts pertinent to the on-going train, advise, and assist (TAA) mission in Afghanistan: "effective, sustainable, and affordable" Afghan National Defense and Security Forces (ANDSF). One might argue that effective, affordable, and sustainable Afghan forces are mutually exclusive endeavors given the duration of the conflict, and the billions of dollars in US and other coalition contributions this operation has already swallowed.

However, rest assured that systems and processes are nonetheless in place to help balance available resources with mission essential capabilities In theater.

One indispensable tool for submitting, tracking, consolidating, justifying, and prioritizing mission requirements, as well as the subsequent request for funding, is the Requirements and Resourcing Documents (RRD) database. The keeper of this Access database is the Program and Analysis (PandA) division within the Combined Security Transition Command--Afghanistan (CSTC-A) CJ-8, Resource Management Directorate. In It, requirement submissions for funding consideration in the program objective memorandum (POM) are assigned sequential tracking numbers for internal use. It Is unclear who created the initial framework of this database, but with each deployment rotation, designated analysts In PandA have been steadily improving its functionality. POM submissions, regardless of funding source (US, coalition, or the Government of the Islamic Republic of Afghanistan (GIRoA)), are consolidated from a variety of mission elements across the Resolute Support area of operations. The PandA team is then tasked with recommending a validated POM submission by Afghan ministry (Ministry of Defense (MoD), and Ministry of Interior (Mol)) to the CSTC-A leadership for approval.

The seemingly daunting task of capturing and tracking hundreds of requirement submissions in the RRD database is made easier, or more manageable, by requiring a number of key data fields to be populated: the requirement owner; budget activity group (BAG); sub-activity group (SAG); RRD number; requirement title; the comprehensive cost and requirements system (CCARS) number for existing, recurring requirements; descriptions; justifications; requested dollar amounts; and fiscal year. Along with the funding request for a given requirement, the database holds supporting documentation; such as, item specifications, existing related contracts, cost estimates, and memoranda of...

To continue reading

FREE SIGN UP