Center for Army Lessons Learned: Collection Priorities
Center for Army Lessons Learned (CALL) collects, analyzes, disseminates, integrates, and archives Army and joint, interagency, intergovernmental, and multinational (JIIM) observations, insights, lessons (OIL) and tactics, techniques, and procedures (TTP) to support full-spectrum military operations. One of the most important operative tasks in CALL's mission statement is collection. Collection of the latest OIL and TTP and their subsequent integration into the operational and institutional Army helps units and Soldiers meet the serious challenges posed by today's operating environment. CALL collects OIL, TTP, and operational products and records from the field primarily through five methods:
Observations, Insights, and Lessons
Commanders and staffs at all echelons have a responsibility to send relevant collected OIL and other documentary materials to CALL to capture lessons learned products for dissemination to the Army.
Observations, insights, and lessons are information from any source that explains the conditions experienced by military forces during war or training, the issues that arose during those operations or exercises, and the potential solutions to the problems military forces experienced. Examples of OIL include AARs, unit TTP, interviews with Soldiers, incident reports, and most CALL-distributed products.
Observations describe the conditions experienced by military forces during war or training. Example: "The daily average temperature in Iraq country was 110 degrees, and it had a negative effect on troops and equipment."
Insights describe the issues that arose while conducting military operations or training. Example: "Due to the extreme heat experienced in Iraq, the (insert piece of equipment) failed to operate properly."
Lessons provide potential solutions to the problems experienced under set military conditions (for example, extreme heat). Example: "By doing ... X, ... our equipment continued to work despite the extreme heat."
Observations, insights, and lessons are not lessons learned because they have not been validated by the Army's assigned proponents, and there is no assurance an actual change in behavior will occur.
Lessons learned definition
CALL defines lessons learned as "validated knowledge and experience derived from observations and the historical study of military training, exercises, and combat operations that lead to a change in behavior at either the tactical (standing operating procedures [SOP]), TTP, etc.), operational, or strategic level or in one or more of the Army's DOTMLPF (doctrine, organization, training, materiel, leadership and education, personnel, and facilities) domains."
The lessons learned process (LLP) is a deliberate and systematic process for collecting and analyzing field data and disseminating, integrating, and archiving OIL collected from Army operations and training events. OIL do not constitute lessons learned without changing individual, unit, or Army behavior.
Lessons learned collection process
Units should collect OIL, tactics, TTP, AARs, and other operational and training documentation from relevant sources and forward them to CALL. The sources include but are not limited to the following:
Through both formal and informal means, units conduct collection activities, assessments, and AARs as a basis for forwarding relevant OIL to CALL for subsequent dissemination throughout the Army. At a minimum, observers should identify the task, describe the event, and highlight facts and data to corroborate the OIL. There are two methods of collection:
Sending OIL to CALL
Commanders and staffs at all echelons have a responsibility to submit their collected OIL to CALL. CALL is responsible for disseminating this information to the Army through its Website and products. Units and organizations are encouraged to follow the submission guidelines posted on the CALL Non-Secure Internet Protocol Router Network (NIPRNET) and Secret Internet Protocol Router Network (SIPRNET) Websites (See Figure 4-1) to submit OIL, either electronically or in hard copy digital format (that is, electronically stored/burned onto a compact discread only memory [CDROM]).
CALL desires the following minimum information requirements for observations:
The After-Action Review
Army Regulation 11-33, (Army Lessons Learned Program) directs assigned units, brigade-size or larger to submit unit-level AARs and other lessons learned material to CALL for review, analysis, dissemination, and archiving in accordance with the following general guidelines:
Writing the After-Action Review
CALL developed an AAR Report Template (See Appendix B) for units to use to prepare final, comprehensive reports documenting recent operations. Its design is based on extensive institutional experience of what makes an outstanding AAR. Commanders are encouraged to include the following key information in their AARs.
Theater Observation Detachment (TOD)
CALL maintains embedded collectors, normally majors or lieutenant colonels called TODs, in designated operational units. CALL uses both internal personnel and external volunteers to fill embed positions. Embedded volunteers include officers from both the active and reserve components to include the Army Reserve and National Guard, CTCs, branch proponents, and training support divisions. External commands support the embed program to improve predeployment training, validate the implementation of the operating environment into training and mission rehearsal exercises, and validate post-mobilization training. TODs integrate themselves into a unit's operations and simultaneously serve as an advocate for CALL. Figure 4-2 depicts the TOD's role as a liaison between the field units and CALL. Other key tasks the TOD performs are:
TOD and the commander
Upon the TOD's arrival in theater, he conducts an in-brief with the supported unit commander or chief of staff. At a minimum, the commander or chief of staff can expect to hear the TOD's role and his proposed collection plan. CALL highly welcomes the commander's input to the collection plan and will adjust it accordingly. Periodically, the TOD updates the commander regarding the collection plan's status.
Collection and Analysis Team
CALL has an on order mission to deploy worldwide to collect lessons and TTP from both contingency operations and training exercises. Since September 11, 2001, CALL has sent out 50 CAATs, mostly related to operations in Operation Iraqi Freedom (OIF) and Operation Enduring Freedom (OEF). Subject matter experts from around the Army comprise a CAAT, which develops issues for collection approved by the Combined Arms Center (CAC) commander (See Figure 4-3). CAATs follow a very disciplined and developed collection process and subsequently debrief the CAC commander regarding their findings.
CAAT Collection Process
CAATs execute collection in four distinct phases (See Figure 4-4):
Commander's responsibility to a visiting CAAT
CAATs normally require the following minimal support from the visited command:
Operational Records and Products from the Operational Army
CALL highly encourages units to send copies of its key operational records and documents generated from operational deployments. CALL proactively collects copies of many key operational documents from units; however, it is only able to collect a fraction of what is available. Documents collected are permanently placed in the CALL archives, which makes them available for future use to the field and institutional Army. Experience has shown operational products and records are invaluable tools in helping units prepare for an operational deployment to OIF or OEF. Operations orders (OPORDs) and associated fragmentary orders (FRAGOs) alone provide a wealth of operational and intelligence information for a unit preparing for a similar mission. CALL receives hundreds of requests a year from Soldiers, Department of Defense (DOD) civilians, and DOD contractors asking exactly for this type of information. Units are strongly encouraged to send digital copies of the following operational documents and records to CALL for archiving:
Send the above documents to CALL using the same method described above to send an AAR.
Last Reviewed: May 18, 2012