extracted from a history database of transactions processed by Defense Automatic Addressing System (DAAS).
published on a monthly, quarterly, semiannual
or required basis.
Special Reports related to transactions processed by DAAS are available upon
official request. These reports will be published on an on-time or temporary basis.
Continuing reports require approval and the assignment on a Reports Control Symbol
(RCS).
Changes or additions to standard reports described below, require prior approval of the
Assistant Secretary of Defense (Comptroller).
The following reports are standard reports and are available through the
Logistics Reports application, Total
Report Management Solution (TRMS), and depending on size, on magnetic tape cartridge or
floppy disks.
Section 1. Transaction Volumes by Document Identifier Codes,
transactions rejected, passed, and various other, such as rejected for invalid DoDAAC, RI
to etc.
Section 2. Transactions volumes by origins. This section
reflects the transaction transmitted to DAAS. It is prepared by Service/Agency. A special
Section is also prepared for Naval Ships by associated activities.
Section 3. This section is divided into two subsections, basic and
supplementals
Section 3, Supp 1. Basic involves monthly volumes by
Service/Agency routing indicator codes. This includes counts of requisitions, passing
orders, referral orders, issue transactions, total demands, cancellations, AFT follow-ups,
AT_, and Materiel Release Orders (A5_) by priorities, and customer excess report
transactions to/from Military Routing Identifier (MILRI) Codes.
Section 3, Supp 2. involves Inventory Control Point Excess
Report Transaction Volumes. This report is prepared monthly with 12 months accumulation.
Section 4. Item Action Frequency. This section reflects the
frequency of requisitions on NIINS. It is prepared separately for each Service/Agency.
a. Section 4, Part 2
Section 5. High Action Items. This section pertains to items in
Section 4 which were requisitioned more than 100 times in one month. It is prepared
monthly for each Service/Agency, NSN, Quantity requisitioned by ServiceAgency, and SOS.
Section 6. Reserved for future Use.
Section 7. Communications Pipeline (Transaction Date versus
Message Header Date). This report is prepared for Service/Agency to show number of
requisitions by different time lapse frequency. The report is prepared by comparing
transactions date by message date.
Section 8. Communications Pipeline (Transactions Date versus Date
received by DAAS). The report is prepared by comparing the date in the requisition with
date received by DAAS.
Section 9. Communications Pipeline. (Message Date/Time versus
Date/Time received by DAAS. This report is prepared to show number of transactions in
different time lapses(0-1, 1-4 hours etc.)
Section 10. Communications Pipeline Extract. This is similar to
Section 7-8-9, except it is tailored to specific days, activities, communications routing
indicator etc. Prepared upon special request only.
Section 11. DAAS FMS Notice of Availability (NOA) Transactions (AD_).
a. Part 2. FMS Notice of Availibility Rejects
See DAAS Manual DoD 4000.25-10-M.
Section 12. DAAS Source Of Supply (SOS) Records. This report is
divided into two parts.
a. Part I. DAAS SOS File Summary. This part of Section 12
contains statistical data pertaining to the DAAS SOS records. This report is prepared for
each Service/Agency and the report will be distributed to the DAAS Focal Points as
requested.
b. Pary II. DAAS Interim SOS file. This part of Section 12 contains a
complete list of DAAS Interim SOS records. Distributed upon request.
Section 13. Reserved for future use.
Section 14. Reserved for future use.
Section 15. Country Code/Contractor Up/Down Traffic Report. This
section reflects the monthly volumes received and transmitted by the FMS/MAP Grant Air
Countries and DoD and Defense Logistics Agency Contractors.
Section 16. This report is prepared for the U.S. Air Force. Specific
logistics data is extracted for analysis of base performance standards. This section is
prepared monthly. It contains statistical data indicating performance factors for supply
points with selected Air Force major commands, and selected USAF Bases .
a. Supp. 1 - Air Force Command Rejects
b. Supp 2 - Air Force Pipeline Reports
Section 17. Reserved
Section 18.
Report of Logistics Information for Marine Corps Only. Selected Unit Transactions
Statistics.This report contains the requisition and supply status transaction volume by
Marine Corps Activity.
a. Part 2 - Requisition Action to Supply Sources. This report lists
the number of transactions passed or routed to supply sources by DAAS for each Marine
Corps Activity.
a. This section reflects delinquent MRADS for which 90 calendar days
have passed since the date shipped as reflected in the shipment status with exclusions as
cited in DoD 4140.22-M, MILSTRAP. This section is prepared quarterly by requisitioning
Service/Agency and is divided into two subsections and a recapitulation of grand totals.
(1) Subsection 1 contains the total number of Document Identifier (DI)
codes AS_/AU_ for each applicable activity for which no MRAD (D6S) has been received and
the 90-180 calendar days have passed since the ship date reflected in the shipment status.
The sequence is by requisitioning activity within service/agency; by priority group I
(1-3), II (4-8), iii (9-15); total of all priority groups; with a grand total for each
priority group.
(2) Subsection 2 contains the total number of DI Codes AS_/AU_ for
each applicable activity for which no MRAD has been received and over 180 calendar days
have elapsed since the ship date reflected in the shipment status.
(3) The recapitulation of grand totals contains a recap of open
lines as contained in subsections 1 and 2; responses received that matched or did not
match to the shipment status in the Shipment Status Correlation File (SSCF); and the
percentages of the matched, unmatched, and delinquent MRADS.
* "Open Lines" contains the grand total by Service/Agency of all AS_/AU_
transactions in SSCF for which no MRAD has been received which have aged 1-89 calendar
days, 90-180 calendar days, and over 180 calendar days.
* "Responses" contain two categories and a total which reflect MRADS received
that were matched or unmatched to the SSCF.
* "Percentages" contain three categories that reflect the percentages of
MRADS that matched the SSCF and MRADS that did matched the SSCF based on total response
received. The percentages of delinquent MRADs (cumulative figure of open line 90 calendar
days and over) is determined from the SSCF based on the ship date reflected in the
shipment status transactions.
Section 22
. FAA Activity Report: This report is broken out by the following
categories:
a By Issue priority groups:, IPG I (1-3), IPG II (4-8) and IPG III
(9-15).
b From Source of Supply (SOS): Military Routing Identifier Code
(MILRIC)
c Supply Status Codes
d Individual Totals, for each DI Code, within priority, for each SoS,
and grand totals.
Section 23
. FAA BB, BC Quarterly Report: A summary, by NSN line item, showing the
number of open backorders, by SOS and the grand total of FAA Backorders held by each SOS.
Section 24
. Department of Agriculture, this report is deleted
Section 25
. DAAS furnishes the U. S. Department of State copies of selected
transactions in which the requisitions activity address begins with "19". DAAS
list selected status transactions, based on status codes specified by the Department of
State, and furnishes this report to the Department of State.
You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.
By using this IS (which includes any device attached to this IS), you consent to the following conditions:
The USG routinely intercepts and monitors communications on this IS for purposes
including, but not limited to, penetration testing, COMSEC monitoring, network
operations and defense, personnel misconduct (PM), law enforcement (LE), and
counterintelligence (CI) investigations.
At any time, the USG may inspect and seize data stored on this IS.
Communications using, or data stored on, this IS are not private, are subject to routine
monitoring, interception, and search, and may be disclosed or used for any USG-authorized
purpose.
This IS includes security measures (e.g., authentication and access controls) to protect
USG interests--not for your personal benefit or privacy.
Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI
investigative searching or monitoring of the content of privileged communications, or
work product, related to personal representation or services by attorneys,
psychotherapists, or clergy, and their assistants. Such communications and work product
are private and confidential. See User Agreement for details.
CUI
Rules of Behavior Acknowledgement
The following DLA General Rules of Behavior delineate the responsibilities of, and expectations for, all individuals with access to DLA systems, networks, and internal web sites.
What is the purpose of the Rules of Behavior?
The DLA Rules of Behavior summarize laws and guidelines from various DLA and Department of Defense (DOD) documents.
What are Rules of Behavior?
Rules of Behavior support accomplishing a Defense-in-Depth strategy of Information Assurance (IA) initiatives. These guidelines were established to hold users accountable for their actions and responsible for information security. Rules of Behavior establish standards of actions in recognition of the fact that knowledgeable users are the foundation of a successful security program. The Rules of Behavior highlight the need for users to understand that taking personal responsibility for the security of a computer and the data it contains is an essential part of their job.
Who is covered by these rules?
These rules are to be followed by the entire DLA workforce (civilian, military, and contractor) with access to DLA systems, networks, and internal web sites. This DLA workforce should be fully aware of, and abide by, DLA security policies as well as related DOD policies.
What are the penalties for Noncompliance?
Noncompliance to these rules will be enforced through sanctions commensurate with the level of infraction. Actions may result in removal of system access.
Misuse of Privacy Act data may result in civil and criminal charges and fines.
USER RESPONSIBILITIES
USERS WILL:
Safeguard the information contained in DLA systems from unauthorized or inadvertent modification, disclosure, destruction, denial of service, and use. DLA systems, networks, and internal web sites are for official use and authorized purposes in accordance with DOD 5500.7-R, Joint Ethics Regulation
http://www.defenselink.mil/dodgc/defense_ethics/ethics_regulation/index.html.
Information is subject to monitoring and security testing.
Screen-lock the computer or log off when leaving the work area.
Report known or suspected incidents immediately.
Use DLA computers only for lawful and authorized purposes.
Comply with safeguards, policies, and procedures to prevent unauthorized access to DLA computer systems.
Comply with terms of software licenses and only use licensed and authorized software. Do not install single-license software on shared hard drives or servers.
Choose strong Passwords that are at least eight characters in length that include at least one capital letter, one lower case letter, one special character, and one number. Change the Password at least every 90 days.
Not share Login IDs or account Passwords with anyone.
Recognize the accountability assigned to a Login ID and Password. Each user must have a unique ID to access DLA systems. Recognize that Login IDs identify an individual's actions on DLA systems and the Internet. Individual user activity is recorded, including sites and files accessed on the Internet.
Use authorized virus scanning software on the workstation or PC and the home computer. Know the source before using diskettes or downloading files. Scan files for viruses before opening them.
Know your data and properly classify and protect all data inputs and outputs according to their sensitivity and value. Label sensitive media and ensure that sensitive information is removed from hard disks that are sent out for maintenance. Classified data shall be processed on classified systems only.
Use the email system for official Government business, ensuring email messages are professional and accurately states DLA and DOD policies and positions.
Not send sensitive information over the Internet unless it has been encrypted.
Not generate or send offensive or inappropriate email messages, images, or sound files. Limit distribution of email to only those who need to receive it.
NOTE: The user is identified as a user of DLA's computer systems when logged onto the Internet.
Learn about information security to help the Information Assurance Officer (IAO) and Terminal Area Security Officer (TASO). Numbers alone make users the most important security asset. Compared to one IAO or TASO per DLA application or system, users offer many eyes and ears to detect threats to DLA information systems.
By clicking 'Accept', you agree to comply with the DLA Rules of Behavior.
