DFAS CORPORATE WAREHOUSE (DCW) by jay16344

VIEWS: 80 PAGES: 11

									Transportation Global Edit Table–Redesign
(TGET-R)




Functional Requirements Document (FRD)
Phase II Release




March 13, 2007


Prepared for: TGET FUNCTIONAL REQUIREMENTS BOARD



                       i
Change Control:

 Date             Author              Version   Change Reference




Document Review Trail:

Name                       Position                     Date Reviewed




Disposition:

Name                       Media                      Location


Distribution:

Name                       Title                      Date




                                      i
                                                               Table of Contents

1     INTRODUCTION...................................................................................................... 3

1.1      Purpose ...........................................................................................................................................................3

1.2      Background ....................................................................................................................................................3

1.3      Project Overview ...........................................................................................................................................3


2     JUSTIFICATION FOR AND NATURE OF CHANGES ............................................ 4

2.1      Justification for Change ................................................................................................................................4

2.2      Description of Changes .................................................................................................................................4

2.3      Assumptions ...................................................................................................................................................5


3     REQUIREMENTS .................................................................................................... 5

3.1      Master TAC (DAASC) Replacement ...........................................................................................................5

3.2      Marine Corps Interface ................................................................................................................................5

3.3      Air Force Interface ........................................................................................................................................6

3.4      PowerTrack Interface ...................................................................................................................................6


4     SUMMARY OF IMPACTS ........................................................................................ 6

4.1      Operational Impacts ......................................................................................................................................6


5     PROJECT RISKS .................................................................................................... 6

6     RESPONSIBILITIES ................................................................................................ 7

6.1      DCD Program Management Office Responsibilities ..................................................................................7

6.2      DTIM Program Management Office Responsibilities ................................................................................8

6.3      SABRS Program Management Office Responsibilities ..............................................................................8


7     SECURITY ............................................................................................................... 8

8     TESTING ................................................................................................................. 8

9     TRAINING ................................................................................................................ 9

10       SUMMARY ........................................................................................................... 9

11       APRROVALS ..................................................................................................... 10


                                                                            ii
1   INTRODUCTION

1.1 Purpose

The purpose of this document is to describe the functional requirements associated with Phase II
of the Transportation Global Edit Table-Redesign (TGET-R) Initiative.

This document describes known requirements in sufficient detail to gain management approval,
establish the scope of this initiative, identify initial project timelines, and ensure management
expectations are clearly defined for this initiative. The intended audience for this document is
personnel involved in requirement definition, design, development, testing, and implementation
of Phase II of TGET-R to include integration with designated legacy applications.

This document also establishes a basis for responsibility between the TGET-R Program
Management Office (PMO), and Third Party Payment System (TPPS) Oversight Council by
providing an inventory of functional requirements agreed upon for Phase II of the TGET-R
Initiative. The FRD includes a description of the requirements, a summary of impacts, and an
end-to-end analysis of the proposed initiative.

This FRD will serve as one of the references for functional requirements. Detailed interface
requirements will be captured in other documents designed to supplement this FRD.

1.2 Background

By majority vote on July 19, 2001, the Transportation Global Edit Table (TGET) was selected as
the single source for accounting and transportation account code data for the Department of
Defense. Subsequently, on August 30, 2001, the Assistant Deputy Under Secretary of Defense-
Transportation Policy (ADUSD/TP) and Office of the Undersecretary of Defense (Comptroller)
signed a memorandum directing the implementation of the Automated Commercial Payment and
Accounting Process which included the establishment of TGET.

Therefore, the primary function of the TGET-R Initiative is to provide a centralized and secure
repository for accounting and transportation data accessible to transportation users worldwide.
TGET-R will provide dynamic validation, editing, data sharing and distribution of the line of
accounting (LOA) and transportation account code (TAC) data.

1.3 Project Overview

In Phase II of the TGET-R Initiative, development efforts will focus on replacing the DAASC
“Master TAC Table” application, enhancing the Air Force and Marine Corps TAC/LOA
interfaces, and creating a new interface with US Bank’s PowerTrack billing system.

Phase II of the TGET-R Initiative proposes to incorporate functionality currently resident in the
DAASC Master TAC table. TGET-R enhanced functionality will essentially reduce from three to
two (TGET/FACTS) the number systems TAC Administrators use to populate line of accounting
and associated transportation account code data. Development of Master TAC functionality
                                             3
within TGET-R would allow external users to view and download line of accounting and
transportation account code data via a set of web-based screens. Additionally, TGET-R would
provide external users with TAC related contact information including the names, telephone
numbers and email addresses of each service’s TAC Administrator.

Phase II of the TGET-R Initiative would also include the development of two in-bound interfaces
from the Standard Accounting, Budget and Reporting System (SABRS), a Marine Corps
accounting system, and Defense Transaction Interface Module (DTIM), a DFAS system. The
two interfaces will provide the Air Force and Marine Corps another means to insert and update
its line of accounting and transportation account code data within TGET-R.

Phase II of TGET-R Initiative will also include a new interface with the Global Exchange System
(GEX) similar to data sent to shipper systems today. This data will then be converted by GEX
and sent to Powertrack to create the chart of accounts.

2   JUSTIFICATION FOR AND NATURE OF CHANGES

2.1 Justification for Change

The Third Party Payment System Oversight Council with the endorsement of the US
Transportation Command has directed the TGET-R PMO to incorporate functionality similar to
that found in the Master TAC table capability currently maintained by DAASC, thereby
eliminating the need for this capability.

2.2 Description of Changes

To fully meet the goals and objectives established for Phase II of the Transportation Global Edit
Table Redesign Initiative, the TGET PMO must

    1. Create individual TAC tables for each component to enforce service unique attributes and
       business rules.
    2. Modify the existing TGET maintenance screens and population processes to
       accommodate the new TAC attributes.
    3. Create a set of web-based screens to enable authorized users the to query and view line of
       accounting and associated TAC data
    4. Create a set of web-based screens to enable authorized users to download line of
       accounting and associated TAC data
    5. Create a Master TAC Archive table to store existing TAC data migrated to BEIS from the
       Master TAC table maintained within DAASC
    6. Create a set of web-based screens to enable authorized users to view the Master TAC
       Archive table
    7. Create new user roles and separate menu items associated with this expanded
       functionality
    8. Create a process to allow potential users to request access to TAC data.
    9. Create in bound interface processes to populate, update, and delete Marine Corps and Air
       Force line of accounting and associated transportation account code data.
                                            4
    10. Create a new interface with US Bank’s PowerTrack billing system through GEX. Data
        will mirror the information sent to the shipper systems.


2.3 Assumptions

The TGET PMO makes the following assumptions:

    1. Active senior level involvement from TPPS Oversight Council, OADUSD(TP), DFAS,
       and Business Transformation Agency (BTA) will occur to ensure cooperation by all
       system participants in this initiative.
    2. Subject Matter Experts and other knowledgeable points of contact (POCs) for the current
       systems will be identified and available to work with the TGET Program Management
       Office (PMO) to clarify requirements.
    3. Designated applicable systems personnel will be available to participate in testing, when
       required.
    4. BEIS will leverage existing interface capabilities where possible.
    5. The Insert and Update TAC functionality in the Master TAC table will be disabled after
       TGET-R is implemented.


3   REQUIREMENTS

3.1 Master TAC Table (DAASC) Replacement

Provide query access to records currently available in the Master TAC table.
    There will be an established (TBD) cut-off period when the Master TAC records will be
       migrated into an archive area of BEIS. These records will be accessed separately from
       TGET-R Active TAC records.

Provide functionality currently available in the Master TAC.
    Provide input and query access to TAC attributes formerly contained in the Master TAC
           o DODAAC (Department of Defense Activity Address Code)
           o AUTHD PURP (Authorized purpose, describes the intended use of the TAC)
    Provide download capability of TAC data
    Provide POC information for TAC Coordinators
    Provide capability to view TAC record structure
    Provide access to TGET access-request forms

3.2 Marine Corps Interface

The SABRS interface allows the Marine Corps to insert, update, and delete LOA and TAC data
into TGET-R. After processing each Marine Corps file, TGET-R will generate and return to
SABRS an email notification listing all inserted or rejected records as well as records identified
as duplicates. The email notification will include the record identification number of each
inserted record as well as an error message for each record rejected. Marine Corps personnel will
                                              5
use existing capabilities within the maintenance screens to delete as well as query LOA and TAC
data.

3.3 Air Force Interface

The DTIM interface allows the Air Force to insert, update, and delete LOA and TAC data into
TGET-R. After processing each Air Force file, TGET-R will generate and return to DTIM an
email notification listing all inserted and rejected records as well as records identified as
duplicates. The email notification will include the record identification number of each inserted
record as well as an error message for each record rejected. Air Force personnel will use the
existing capabilities within the maintenance screens delete as well as query LOA and TAC data.

3.4 PowerTrack Interface

TGET-R will produce a baseline download file to initially populate the PowerTrack Chart of
Accounts (CoA). Subsequently, TGET will produce weekly incremental download files for all
changes made in TGET-R since the last download, to append the CoAs.

The PowerTrack Chart of Accounts (COA) stores line of accounting and TAC information for
use in TAC conversions, carrier invoicing, e-bills, and LOA corrections. To ensure that it
contains valid segmented LOAs, the Chart of Accounts needs to be populated with LOAs and
TACs from the TGET to take full advantage of the automated process.

The Services have a vested interest in the TGET 814 Interface to ensure that valid TACs and
LOAs are available for use in PowerTrack. By minimizing errors and rework required at DFAS
due to invalid accounting data, PowerTrack invoices may be processed faster and reduced
interest charges to the Services and Agencies.

From time to time, one of the Services may need to create a new CoA. To accommodate this
requirement, every fourth week, immediately after generating the incremental file, TGET-R will
create a new baseline file. Incremental files will always be based off the most current baseline
file.

4   SUMMARY OF IMPACTS

4.1 Operational Impacts

The operational impacts of this initiative are primarily targeted to the workload reduction for
each TAC Coordinators relative to populating LOA and TAC data in multiple systems.
Additionally, current DAASC Master TAC Table users will be required to submit new requests
for access to TGET-R.

5   PROJECT RISKS

The key success factor for the TGET-R Phase II Initiative is the development of Master TAC
Table functionality within TGET-R. Personnel who are intimately familiar with both the
                                            6
operation of the Master TAC, its source of data and business rules must be available to assist in
accomplishing this task.

The risk in this area is that personnel from DAASC, Powertrack PMO, SABRS PMO, DTIM
PMO and TAC Administrators will be unable or otherwise uncommitted to fully participate in
this project. The need to leverage on-board expertise within this functional area is critical.

Project Risks:

       Lack of system documentation on the Master TAC Table.
       Resource availability may impact schedule and implementation timelines.
       Overly ambitious scheduling of new development due to existing project timelines.
       Cross project milestone coordination among personnel from the three interfacing systems
        may prove problematic.
       Lack of a clearly defined acceptance criteria which may slow enterprise level acceptance
        testing.

6   RESPONSIBILITIES


6.1 BEIS Program Management Office Responsibilities

       The BEIS Program Manager will appoint a dedicated Project Officer (PO) who will be
        responsible for accomplishing the requirements as stated in the FRD.
       BEIS Program Manager will insure that the TGET Project Officer has sufficient
        resources, including team members and operating funds to fulfill the requirements of the
        FRD.
       The BEIS Program Manager will assign this initiative to a Business Enterprise
        Information Services (BEIS) Release and will further assign a BEIS Test Coordinator
        responsible for organizing the associated Functional Validation, System Integration, and
        User Acceptance testing activities.
       The TGET Project Officer will ensure the BEIS Project Plan is updated to reflect key
        milestones associated with this initiative.
       The TGET Project Officer will ensure all scheduled Requirements Review and Analysis
        (RRA) sessions associated with this initiative are conducted in accordance with the BEIS
        Project Plan. These sessions must be well documented, with meeting minutes
        disseminated to all parties involved.
       The TGET Project Officer will ensure the required BEIS Functional Requirements
        Review (FRR) and Critical Design Review (CDR) tasks are incorporated into the BEIS
        Project Plan for the Release. The TGET Project Officer is also responsible for ensuring
        these reviews are conducted in accordance with established BEIS standards.
       The TGET Project Officer will ensure project risks are properly documented and that an
        effective risk mitigation strategy is adopted to minimize the impacts of these risks.




                                             7
6.2 DTIM Program Management Office Responsibilities

       The DTIM Program Management Office will appoint dedicated personnel who will be
        responsible for working with the TGET Project Officer in defining requirements, defining
        acceptance criteria and developing a test plan.

       The DTIM Program Management Office will ensure staff members are represented during
        the RRA requirements gathering sessions associated with this initiative.


6.3 SABRS Program Management Office Responsibilities

       The SABRS Program Management Office will appoint dedicated personnel who will be
        responsible for working with the TGET Project Officer in defining requirements, defining
        acceptance criteria and developing a test plan.
       The SABRS Program Management Office will ensure staff members are represented
        during the RRA requirements gathering sessions associated with this initiative.


6.4 DAASC/GEX and the DoD PowerTrack PMO Responsibilities
       The Chief of DAASC/GEX and DoD PowerTrack PMO must assign and identify
        technical and functional points of contact for this interface. The Chief of DAASC/GEX
        and DoD PowerTrack PMO must notify the BEIS PM of changes in personnel identified
        as points of contact in this document. Notify the BEIS PM of any changes to the interface
        requirements. Draft and coordinate an interface-testing schedule with the TGET Project
        Officer to validate the TGET data to be transmitted to DAASC/GEX. Provide TGET
        technical staff with data, communications, and security requirement information, i.e. IP
        Address and system accesses protocol.


7   SECURITY

System security requirements will be developed in accordance with the provisions of Office of
Management and Budget Circular A-130, Management of Federal Information Resources, and
DoD Directive 5200.28, Security Requirements for Automated Information Systems. System
security risks will be assessed and managed in accordance with DoD Instruction 5200.40, DoD
Information Technology Security Certification and Accreditation Process (DITSCAP). DFAS
Policy contained in DFAS Information Management Regulation 8000.1-R, Part E, Information
System Security Policy, will be used to implement the federal and DoD requirements contained
in the above referenced Circular, Directive, and Instruction.

8   TESTING

The TGET Project Officer along with representative from the US Bank, DTIM PMO and SABRS
PMO will assist the BEIS Test Director in the developing acceptance criteria and test scripts to

                                            8
ensure the functional requirements are fully satisfied. Each PMO will be responsible for the
preparation of test scripts and performing the necessary functional validation testing and
acceptance testing associated with their own systems development efforts in support of this
initiative.

9   TRAINING

The BEIS PMO is responsible for training BEIS Production Support staff on all facets of this
new initiative.

Likewise, the DTIM and SABRS PMOs are responsible for ensuring all affected personnel are
aware of this initiative and receive training on applicable facets of this new initiative

10 SUMMARY

In summary, the proposed Transportation Global Edit Table Redesign Initiative will incorporate
Master TAC functionality into TGET-R as well as develop two automated interfaces to capture
accounting and transportation account code data for the Air Force and the Marine Corps and
produce a baseline download file to initially populate the PowerTrack Chart of Accounts.




                                            9
11 APRROVALS



             Signature                      Date



Co-Chair TPPS Council Representative



Co-Chair TPPS Council Representative



TGET Project Manager




                                       10

								
To top