Business Process Reengineering (BPR) and Standard Line of Accounting (SLOA) Template Instructions

Aug 31, 2026

Upload by Rhys

Instructions guide completion of a Business Process Reengineering (BPR) and Standard Line of Accounting (SLOA) template aligned to DoDAAF SV-6. The guidance explains when an existing SV-6 can be reused and how to append BPR and SLOA sections (Columns AK through AS) with requested exchange data. It highlights that blue cells with yellow text are critical per data exchange, while non-feasible cases must be documented in Column AR with a rationale in Column AS, including projected subsumption dates (MM/YY).

LanguageEnglish

CategoryPresentations

FormatDOCX

Pages10

Reading Time4 min

AccessFree to download

Template Instructions

SV-6 Reuse and Append Requirements

Critical Fields for Each Data Exchange

Handling Non-Feasible Business Process Changes

Initial SLOA Implementation Plan Requirements

Business Process Reengineering (BPR) and Standard Line of Accounting (SLOA) Template Instructions The template is based on the DoDAAF SV-6 (C1 from the Initial SLOA Implementation Plan Template, see below) and best of breed implementation. The definitions for each column are listed in the next section. If the system’s program management office already has an up-to-date SV-6, then this template does not need to be used. The Component will only need to append the current SV-6 with Business Process Reengineering (BPR) and Standard Line of Accounting (SLOA) section (Columns AK through AS) and supply the requested information. If it is not available, not all information needs to be filled out. However, the columns in blue with yellow text must be filled out for each data exchange. They are considered critical to this effort. There may be certain cases where the implementation of this requirement is not feasible without a business process change. This should be identified in Column AR with an explanation provided in column AS. SV-6 System Data Exchanges Column Descriptions Initial SLOA Implementation Plan Template SLOA Memo Excerpt: Initial SLOA Implementation Plan Template (an Excel template will also be provided on http://dcmo.defense.gov/products-and-services/standard-financial-information-structure/): The Plan should address unreconciled differences caused by interoperability with trading partners’ or customers’ systems by: Analyzing existing functionality and cost-efficiency within a mixed Legacy and Target and/or Enterprise Resource Planning (ERP) systems environment. Determining the best way forward to resolve inherent data exchange problems. Consolidating functionality by reducing the overall number of systems and thereby interfaces, which pass transactional data. This should be based on a DoDAF SV-6 structure outlining each of the system’s interfaces. (2) Each interface is required to be labeled as Target or Legacy. (D) Evaluating if those systems/interfaces can be subsumed by the Target and/or ERP systems. (1) Each interface is required to be labeled as Subsumed or Maintained. (2) Each interface is required to be labeled as SLOA Applicable or Not Applicable. (3) Rule of thumb: Those that are Target (C)(2), which will be Maintained (D)(1), lead to postings between commitments and disbursements; and Those that are Legacy (C)(2), which will be Maintained (D)(1), should be noted with a comment specifying why these Legacy interfaces are critical/applicable. (E) Implementing the SLOA for the remaining interfaces. Projected dates (MM/YY) are required for subsumption or SLOA implementation. System owners and Service Providers must also ensure that their systems are interoperable with their trading partners’ or customers’ systems with respect to this requirement. Certain cases may require a business process reengineering effort to effectively execute this requirement. Components should identify this in their SLOA implementation plans. Participating in SLOA coordination discussions with the Office of the Under Secretary of Defense (Comptroller)/Deputy Chief Financial Officer and the Office of the Deputy Chief Management Officer after their receipt of the Component-level plans to form an Enterprise SLOA Transition Plan with targeted completion dates. Note: Items (C)(1) through (D)(1) should already exist, given that for (C)(1) and (C)(2) Target systems should have an SV-6 and given that (D)(1) was a requirement associated to FY2010 National Defense Authorization Act (NDAA) IRB certification. If items (C)(1) through (D)(1) have been done properly, then items (D)(2) & (E)(1) should be an intelligible task.

FAQs

When does the template need to be used versus when an existing SV-6 is sufficient?

If the program management office already has an up-to-date SV-6, the template does not need to be used. The component then appends the current SV-6 with the BPR and SLOA section (Columns AK through AS).

Which fields are mandatory for each data exchange?

Columns in blue with yellow text must be filled out for each data exchange, as they are considered critical to the effort.

What should be done if implementing the requirement requires a business process change?

Identify the case in Column AR and provide an explanation in Column AS, noting why the requirement is not feasible without a process change.

Aug 31, 2026

Upload by Rhys