|
02157
|
Physical Inventory at the Enterprise Level
|
Warehouse |
NECC |
New |
Change Request: Process Improvement
Description:
We are requesting the addition of functionality within the Inventory process to enable users to conduct inventories by Reportable Commodities at the Enterprise level. This enhancement would allow users to schedule inventories for an entire commodity type across a specified Region or Site, thereby improving inventory management efficiency and ensuring timely accountability for assets across broader organizational scopes.
Recommended:
During the Inventory process, users with the appropriate Region/Site access should be able to select an optional Region/Site on the same interface where they can choose specific Reportable Commodities for inventory. Additionally, an Enterprise Rollup selection feature could be included, enabling users to select an entire Region/Site for inventory at once, streamlining the process and enhancing inventory management capabilities.
Mission Critical:
NECCINST 5200.45
Benefits:
The addition of this capability would empower users to conduct inventories across multiple warehouses or an entire Region/Site simultaneously, significantly enhancing the efficiency and speed of the inventory process.
Frequency: Daily
Users:
All users who utilize multiple warehouses and the Physical Inventory function. |
|
02156
|
Adding Attachments to Multiple Records
|
Warehouse |
NECC |
New |
Change Request: Process Improvement
Description:
We are requesting the implementation of functionality within DPAS Warehouse that allows users to add a single attachment to multiple records simultaneously. Currently, attachments must be added individually to each record, which is highly time-consuming—particularly in scenarios such as uploading identical birth documents to a large number of serialized assets. Enabling batch attachment functionality would greatly enhance efficiency and reduce administrative workload.
Recommended:
Requesting an enhancement to the current functionality that would allow users to apply the same attachment to multiple records within the Selected Inventory tab under the Inventory Update Manager/User function. This improvement would streamline the process of associating common documentation—such as birth documents—with multiple inventory records, thereby increasing efficiency and reducing administrative burden within asset management workflows.
Mission Critical:
In accordance with NECC instruction 5200.45, all supporting documentation must be retained in a centralized repository (DPAS).
Benefits:
Having this capability will reduce the man hours associated with adding Key Support Documentation to all assets within the NECC Logistics Program, streamline the process and enhance efficiency when managing multiple records that require the same documentation.
Frequency: Daily
Users:
This functionality would be utilized by the majority of NECC DPAS users who perform receiving, transfer, and issuance operations for all assets required to be recorded in DPAS. |
|
02155
|
Adding Manage SKO to Inventory Update Manager
|
Warehouse |
NECC |
New |
Change Request: Process Improvement
Description:
We are requesting enhanced functionality within DPAS to allow for the replacement of SKO components or the modification of their condition codes in a more timely and efficient manner. At present, users are limited to two options: either route the SKO through the QA/QC process or fully disassemble the SKO, update condition codes or replace components, and then reassemble it. This process is time-consuming and introduces unnecessary operational delays.
Recommended:
Integrating the existing Manage SKO functionality, currently utilized within the QA/QC process, into the Inventory Update Manager would streamline workflows and reduce processing time for users when performing component swaps or updating condition codes.
Mission Critical:
In accordance with NECC instruction 5200.45, all SKO assemblies need to be updated regularly to maintain inventory accuracy and material readiness status
Benefits:
Implementing this capability will significantly reduce the man-hours required to replace SKO components or update their condition codes, thereby increasing overall efficiency and minimizing resource expenditure.
Frequency: Daily
Users:
This functionality would be utilized by the majority of NECC DPAS users who perform receiving, transfer, and issuance operations for all assets required to be recorded in DPAS. |
|
02154
|
Allocation Mgmt - Add Location field
|
|
NECC |
New |
Change Request: Process Improvement
Description:
At present, the Allocation Management Search Criteria functionality allows users to search for various types of allocations associated with specific assets. However, users have expressed the need for enhanced search capabilities, specifically the inclusion of a Location field. This addition would enable users to filter and identify items that are allocated within a designated location, thereby improving the efficiency and accuracy of allocation searches.
Recommended:
Add a Location field to the Search Criteria within the Allocation Management functionality to allow users to filter results based on specific allocation locations.
Mission Critical:
NECCINST 5200.45
Benefits:
Adding this search field will help in searching for allocations within a specific location.
Frequency: Daily
Users:
This functionality would be utilized by the majority of NECC DPAS users who perform receiving, transfer, and issuance operations for all assets required to be recorded in DPAS. |
|
02153
|
Commodity Type Field Add in SKO Catalog
|
Warehouse |
NECC |
New |
Change Request: Process Improvement
Description:
When accessing assets within the SKO Catalog, users are currently unable to directly verify the appropriate reportable commodity associated with each item. As a result, users must first navigate to Catalog Management > Stock Number to obtain the necessary commodity information. Once the appropriate commodity has been identified, users must then return to the SKO Catalog to update the assembly accordingly—completing this process on a line-item-by-line-item basis. This additional step ensures that all entries are accurately aligned with their respective commodity classifications.
Recommended:
Implement the addition of the appropriate reportable commodity type for each component within the SKO. This information can be integrated either as an additional column in the existing layout or as an optional field within the grid options.
Mission Critical:
COMNECC/COMNECCPACINST 5200.45.
Benefits:
Incorporating this enhancement will streamline the process of verifying and updating assemblies, reducing the need for cross-referencing within the WH module.
Frequency: Daily
Users:
All users required to verify the components of the SKOs within their respective inventories to ensure accuracy and compliance. |
|
02152
|
Refactor ICP Report Requirement
|
Materiel Management |
USMC |
New |
Change Request: Process Improvement
Description:
LIN/TAMCN, Stock Number, and ICN Reports are not available within the Material Management Module. Duplicate and modify the ICN enterprise view, currently in the Warehouse Module, into the Material Management (ICP) module. Material Managers need the ability to select an NSN and or serial number. The return results should display a complete enterprise view of all specified required information. Returned selection should have at a minimum, the following key elements. (TAMCN, NSN, Warehouse DoDAAC, Condition Code, Purpose Code, Available to Issue, allocated (by Type Allocated), In Maintenance quantity, Intransit quantity, quantity in an exception status), due in quantity.
Recommended:
1.0. ELMS, from within Material Management (ICP) module, using the MM Inventory inquiry process, shall provide an Inventory Manager (IM) the ability to search by the addition data elements of LIN/TAMCN and Serial Number.
1.1. ELMS, from within Material Management (ICP) module, using the MM Inventory inquiry process, shall provide an Inventory Manager (IM) with the ability to select from the options grid the following elements to be displayed at a minimum:
a. LIN\TAMCN (currently present) i. Inventory Total Qty (currently present)
b. NSN (currently present) j. Inventory Available Qty (currently present)
c. RSA DoDAAC (currently present) k. Allocated to MRO Qty (new required element)
d. RSA RIC (currently present) l. Intransit Due-In qty (new required element)
d. Condition Code (currently present) m. Serial Number (new required element)
e. Purpose Code (currently present)
f. Project Code(currently present)
g. Stocking UI Price (currently present)
h. Extended Price (currently not calculating)
Mission Critical:
Benefits:
Meets MARCORLOGCOM's business model
Assists in 100% Accountability of assets
Complies with current audit controls
Frequency: Daily
Users: |
|
02151
|
Material Redistribution (MM) Process Corrections
|
Materiel Management |
USMC |
New |
Change Request: Process Improvement
Description:
During MARCORLOGCOM’s review of current ELMS processes within the Material Management (ICP) module, it was discovered that system is incorrect selecting and displaying inventory records not within the scope of the redistribution request. This process of incorrect selecting and displaying data lends itself to the Inventory Manager selecting invalid data resulting in inventory mismatches and transactional denials. This also created unnecessary denials leading to inventory requests.
Recommended:
1.0 In the Material Management (ICP) module, when an Inventory Manager is creating a new “Redistribution Order”, ELMS shall not automatically create the 527D/DW_ transactions until after the Inventory Manager completes the MRO 940R/A5_ request. (see attached document)
1.2 Currently, during the creation of the “Redistribution Order” the system returns the user first to the main results gridline. This forces the Inventory Manager to locate and select the document being worked prior to completing the 940R/A5_ process. Much like the “Customer Requestion” process in ELMS, the system shall proceed directly to the 940R/A5_ entry screen without returning first to the main results gridline. (see attached document, image 1.1 and 1.2)
1.3. When initiating a “New Redistribution Order” in the Material Management (ICP) module, if a Condition Code is selected and there is no on hand available assets to issue anywhere in the associated ICP, the system shall provide a popup alert to the Inventory Manager stopping the process and allowing the Inventory Manager to select a Condition Code that is appropriate to support the redistribution. (see attached document, image 1.0)
2.0 Currently, when creating the Material Redistribution order 940R/A5_, all Condition Codes and Purpose Codes are populated and displayed in the selection grid. When creating a 940R/A5_ Material Redistribution release order, in the Material Management (ICP) module, the system shall only display the Condition Code, associated Purpose Codes, and inventory with on hand available quantities matching the original Condition Code and Purpose Code selected. (see attached document, image 1.5)
Mission Critical:
Benefits:
Meets MARCORLOGCOM's business model
Assists in 100% Accountability of assets
Complies with current audit controls
Frequency: Daily
Users: Materiel Managers and ICP users affected |
|
02150
|
Include PSD Id in TPF Transactions
|
PA,Materiel Management |
ASA-ALT |
New |
Change Request: Process Improvement
Description:
The Army's Decision Support Tool (DST) is the system that tracks new equipment fielding and when they are to occur. Each fielding is assigned a PSD Id to each each equipment fielding. Currently the PSD Id is not included in the DLMS transaction to denote why the equipment is being sent to a Unit. The proposed improvement is to have ELMS provide for the input of the PSD Id into the PA Disposition Transfer Out and into the MM Customer Requisition processes enabling the value to be included in the DLMS transactions. See also ELMS SCR 01938
Recommended:
1. Modify MM Customer Requisition to provide for input of the PSD Id.
2. Modify PA Disposition to provide for the input of the PSD Id.
3. Include the PSD Id in the DLMS 527D (PMR) and DLMS 856S (Shipment Status) transactions sets within the Reference Identification loop using the PWC qualifier.
Mission Critical:
Provides 100% confirmation to DST that the fielding has occurred.
Benefits:
Provides visibility that a fielding is being planned via the 527D.
Provides 100% validation that the planned fielding occurred enabling DST to be able to close the fielding systematically.
Frequency: Daily
Users: All users that issue/transfer materiel to users of GCSS-Army.
|
|
02149
|
Option to print DD 1348 before disposal is approved
|
Warehouse |
ASA-ALT |
New |
Change Request: Process Improvement
Description:
When creating a disposal action within the DPAS WM module a DD 1348 can't be printed until the disposal is approved by the "Warehouse Manager and the "COR". For the COR to approve a disposal action they should verify that all signed documentation is uploaded in DPAS before approving the action. Since the DD 1348 can't be printed until after the COR approves the disposal the users are having to create the DD 1348's outside of DPAS. This can cause issues with data accurate since the users can't allow the system to generate the information. This also increases the time it takes to complete the transaction.
Recommended:
Allow the DD 1348 to be printed before the COR has to approve the transaction but after the "warehouse manager" has given the first approval.
Mission Critical:
The process must be flexible to support the business. This change will enable greater flexibility.
Benefits:
The DD 1348 will no longer have to be created outside of DPAS therefore the time to complete the action will decrease and the data on the DD 1348 will be in sync with the information that has been stored in the DPAS WM module.
Frequency: Daily
Users: All
|
|
02148
|
DCAPES interface for FSM
|
FSM |
DAF |
New |
Change Request: Process Improvement
Description:
Currently Authorization managers must input readiness code 'A' authorizations into FSM either via Mass update or manual input. In some cases the Unit Type Code (UTC)s and Auth details in FSM do not match the UTCs in the authoritative system which causes mismatches between the systems and requires manual intervention.
Recommended:
Establish an interface to the authoritative system Deliberate and Crisis Action Planning and Execution System (DCAPES) to limit or eliminate manual intervention. The DCAPES PMO also has a requirement for their system to accommodate this requirement
Mission Critical:
Removes the manual process of establishing readiness code 'A' requirements. Additionally this will resolve a recent AFAA audit finding, that identified mismatches in FSM from the authoritative database with regard to UTC requirements
Benefits:
By leveraging the direct interface we remove the manual process and remove the requirement to reconcile the data from both systems.
Frequency: Daily
Users: Existing UTCs are validated biennially, currently there are over 160K UTC tasked authorizations
|
|
02147
|
NSN COG Information
|
Warehouse |
Navy |
New |
Change Request: Process Improvement
Description:
Currently the COG information does not import from FLIS nor is there a field for the COG.
Recommended:
Allow the COG to import from FLIS and add that field to DPAS records.
Mission Critical:
Benefits:
We track the COG for our equipment for reporting purposes. It will allow us to continue that process.
Frequency: Daily
Users: 100+ Users
|
|
02146
|
Inventory Status
|
Warehouse |
Navy |
New |
Change Request: Process Improvement
Description:
There is not a way to track status of an inventory.
Recommended:
Create an Inventory Status report that shows locations that have been inventoried and those that have not been inventoried for a user selected date range.
Mission Critical:
Benefits:
Allows for a way to track inventoried and to be inventoried locations for a selected date range.
Frequency: Daily
Users: 100+ Users
|
|
02145
|
PROJECT POC
|
Warehouse |
Navy |
New |
Change Request: Process Improvement
Description:
Unable to determine the project POC from the Project table. You can only view it by editing the project code.
Recommended:
Add the project POC information to the grid options of the project table.
Mission Critical:
Benefits:
Allows the user to view the project POC.
Frequency: Daily
Users: 100+ Users
|
|
02144
|
Project Field Character Increase
|
Warehouse |
Navy |
New |
Change Request: Process Improvement
Description:
Current field is only three characters. With the size of our structure we need to increase the number of characters from three to ten.
Recommended:
Increase the number of characters from three to ten.
Mission Critical:
Increasing the Project Code will prevent the duplications of project numbers.
Benefits:
Increasing the Project Code will prevent the duplications of project numbers.
Frequency: Daily
Users: 100+ Users
Removed 04/29/2025 - per email from Justin Smeltzer - Project Code is a DoD Standard Element |
|
02143
|
Maint Mgmt Assignment by Custodian Nbr
|
PA,Materiel Management |
USAF |
New |
Change Request: Process Improvement
Description:
Current DPAS configuration limits the ability to assign assets to M&U at the UIC level. Aviation maintenance units within FH-AFHAF have custodian accounts that are not required to use M&U but assigned assets are loaded against a Maint Group ID (MGID). This results in asset records being bridged over to M&U but are not actively managed.
Recommended:
Provide capability to bridge/ unbridge by Custodian Number's. Adding MGID characteristic to Custodian Number's.
Mission Critical:
PAD 22-02 signed by the Chief of Staff of the Air Force (CSAF) directs the centralized management of CAvSE at the enterprise level, residing within the 440 SCOS Aviation Support Equipment Management Flight. This change will allow for future data mining actions, ensuring equipment accuracy.
Benefits:
This will enable the Air Force to achieve the desired effects in improving overall readiness and war-fighter support.
Frequency: Hourly
Users: This change will be applicable to 15,000+ users assigned to Site FH-AFHAF, as well as other agencies or departments that conduct maintenance on their support equipment.
|
|
02142
|
Inclusion of TFSMS Attribute Data in the Enterprise Catalog
|
PA,MU,Warehouse,Materiel Management |
USMC |
New |
Change Request: New System Process
Description:
The interface being constructed between TFSMS and ELMS was lacking key attributes that are essential in identifying and defining the LIN/TAMCN used by the Marine Corps. Inventory Managers and Equipment Specialists throughout the Marine Corps rely on the additional data being requested to assist in their day to day management of Class VII inventory. The data being asked for should be added to the Enterprise catalog.
Recommended:
1.0 The ELMS system shall include in it interface with the Marine Corps TFSMS system the following key attributes used to minimally assist in identification and defining controlled Class VII inventory:
TAMCN
NATIONAL_STOCK_NUMBER
STANDARDIZATION_CATEGORY_CODE
TAM_STATUS
TAM_STATUS_DATE
ITEM_EXIT_DATE
COLLOQUIAL_NAME
MODEL_NUMBER
DIMENSION_HEIGHT_IN_FEET
DIMENSION_WIDTH_IN_INCHES
DIMENSION_WIDTH_IN_FEET
DIMENSION_LENGTH_IN_FEET DIMENSION_LENGTH_IN_INCHES
DIMENSION_HEIGHT_IN_IN
STAND_PKG_CUBECHES
STD_PKG_LB_WT
1.1 Once the interface is established, the ELMS system shall include all identified attributes in the Enterprise level catalog for the Marine Corps. the primary key to link the information to the catalog is [National_Stock_Number].
1.2 Once the information is included in the Enterprise level catalog, ELMS will make that information available to sub-catalogs (ie, SKO, Stock Item, M&U, Material Management, PA)
1.3 The frequency of the update shall be dependent on the interface agree established between Marine Corps TFSMS system and ELMS.
2.0 NSN SUBSTITUTION: The ELMS system shall provide the inventory Manager, operating in the Material Management module, with the capability to substitute an NSN within a TAMCN group, taking into consideration STANDARDIZATION_CATEGORY_CODE from the TFSMS attributes, which will be added to the Enterprises Catalog.
2.1 In the case where a denial is received at the Material Management module and the document is placed back into a backorder status. ELMS shall provide the Inventory Manager with a capability to substitute and NSN only when the replacement NSN is with the like LIN\TAMCN group. The criteria for the replacement will be strictly controlled by NSNs that have "In Service" (IS), "Plan Allowance" (PL), Disposal Plan (DP) assets available based on the [TAM_STATUS] attribute in the catalog.
2.1.1 At no time shall the system provide the Inventory Manager with the ability to select and alternate asset that is in Achieve (AR) status.
2.2 At the time of substitution, the Inventory Manager shall be provided with the capability to chose a replacement NSN with a different Condition Code and Purpose Code availability.
2.3 ELMS shall be programed to conduct a virtual verification of the selection being made by the Inventory Manager ensuring the warehouse selected, the NSN, quantity, Condition Code and the Purpose Code and support the requested MRO. If the asset is not available matching the specifications identified for the substitution, ELMS will provide the Inventory Manager with an alert and the process will be halted until the error is corrected.
Mission Critical:
Benefits:
- Meets MARCORLOGCOM's business model
- Assists in 100% accountability of assets
- Complies with current audit controls
Frequency: Daily
Users: Affects all USMC users
|
|
02141
|
Inbound Serial Number Enforcement for EDI
|
Materiel Management |
USMC |
New |
Change Request: New System Process
Description:
ELMS must enforce Serialized Item Management (SIM) for designated National Item Identification Numbers (NIINs) across various Enterprise Logistics Management System (ELMS) modules. Data exchanges with external trading partner systems via DLMS EDI/X12 transactions sometimes fail to include required serial numbers for serialized assets. This occurs primarily in, but not limited to:
• 856S (Shipment Notices – Due-In Transactions)
• 945A (Materiel Release – Advice Transactions)
• 947I (Inventory Adjustment Transactions)
The absence of serial numbers in these transactions compromises data integrity and prevents compliance with DoD serialized property management regulations outlined in:
• DoDM 4140.01 (DoD Supply Chain Materiel Management Procedures)
• DLMSO Manuals (DLMS Volume 2, Supply)
• MILSTRAP/DLMS Mapping for EDI transactions
This System Change Request (SCR) proposes a standardized method to detect, report, manage, and resolve these data quality format issues within ELMS. These changes are required to enforce compliance with SIM policies within DPAS modules and ensure accurate logistics accountability and audit readiness.
Recommended:
Implement an automated edit-check mechanism within ELMS to identify inbound DLMS EDI transactions missing required serial numbers, route them to an error handling interface for user remediation, and support transaction reprocessing once corrected. This ensures serialized assets are tracked consistently across the enterprise.
Scope: This change applies to all ELMS modules ingesting DLMS EDI/X12 transactions involving serialized asset movement, including but not limited to:
• Receipt and Due-In processing
• Inventory management and adjustments
• Inbound shipment confirmations
• Materiel Release Orders
Requirements:
1.1. Edit Checks for Serialized Transactions. ELMS shall implement automated validation logic for inbound EDI 856S, 945A, and 947I transactions to detect when a transaction line item is for a NIIN that is marked as serialized but lacks an associated serial number(s).
1.1.2 Enforcement Against Serialized NIIN Catalog. The system shall reference the ELMS NIIN Catalog or Master Item File to determine if an item requires serialized tracking before enforcing serial number validation.
1.1.3. Transaction Error Flagging. Transactions missing required serial numbers shall not be ingested into ELMS records but instead flagged as “Unprocessed” and queued for user intervention in the Interface Queue Manager.
1.1.4. Error Queue Management Dashboard. ELMS shall provide an enhanced dashboard view in the Interface Queue Manager that displays:
• Transaction type (i.e., 856S, 945A, 947I, etc.)
• Originating trading partner
• NIIN and quantity
• Serial number missing status
• Error message: “Serialized NIIN reported without corresponding serial numbers”
1.1.5. Manual Update Interface. The dashboard shall support manual entry of missing serial numbers by the ELMS User after collection from the originating trading partner system.
1.1.6 Audit Trail Capture. The system shall capture all entries made manually to enhance the inbound EDI transactions:
• User ID
• Date/time stamp
• Action performed
• Original vs. updated values
1.1.7 Reprocessing Capability. Once updated with the required serial numbers, the transaction shall be made available for resubmission ingestion using standard processing logic. Successful ingestion will update the transaction status to “Processed” and remove it from the error queue.
1.1.8 System Alerts. ELMS shall provide automated notifications (email or in-system alert) to designated user roles when transactions are flagged as unprocessed due to missing serial numbers.
1.1.9 Metrics and Reporting. The system shall generate periodic reports that include:
• Number of transactions flagged for missing serials
• Time to resolution
• Frequency by trading partner
• NIINs most affected
1.1.10. Configuration Flexibility. Administrators shall be able to update the list of NIINs subject to Serialized Item Management without requiring code changes, using an ELMS catalog or configuration table.
Mission Critical:
Benefits:
- Meets MARCORLOGCOM's business model
- Assists in 100% accountability of assets
- Complies with current audit controls
Frequency: Daily
Users:
|
|
02140
|
Upload of Supporting Documentation to Documents that are Closed
|
PA,Warehouse,Materiel Management |
USMC |
New |
Change Request: New System Process
Description:
ELMS currently does not possess the ability to attach Key Supporting Documents (KSA) (ie. LTI's, signed 1348s, 1149) to a document that is in a closed status. This was discussed during the on site visit to the ELMS LEIDO's facility in early March 2025. This will impact MARCORLOGCOM's ability to answer audit related inquires if not resolved.
Recommended:
1.0 Inventory Managers, using the Material Management (MM) module, shall be provided with the capability to upload an attached Key Supporting Documentation (KSDs) to documents considered closed in ELMS. This is to facility the requirement to extract supporting documentation during an audit evaluation.
1.1 ELMS shall provide the Inventory Manager, the Material Management (MM) module with a capability retrieve attachments from any document recorded in the system.
2.0 Warehouse personnel, using the Warehouse Module (WM) module, shall be provided with the capability to upload an attached Key Supporting Documentation (KSDs) to documents considered closed in ELMS. This is to facility the requirement to extract supporting documentation during an audit evaluation.
2.1 ELMS shall provide warehouse personnel, in the Warehouse Module (WM) module with a capability retrieve attachments associated to the warehouse they are assigned to.
3.0 Personnel using the Property Accountability (PA) module, shall be provided with the capability to upload an attached Key Supporting Documentation (KSDs) to documents considered closed in ELMS. This is to facility the requirement to extract supporting documentation during an audit evaluation.
3.1 ELMS shall provide personnel using the Property Accountability (PA) module with a capability retrieve attachments associated to the account which they are assigned to.
Mission Critical:
Benefits:
- Meets MARCORLOGCOM's business model
- Assists in 100% accountability of assets
- Complies with current audit controls
Frequency: Daily
Users: This change impacts all USMC users
|
|
02139
|
Warehouse Financial Accounting
|
Warehouse,Materiel Management |
MDA |
New |
Change Request: Process Improvement
Description:
MDA has a requirement to manage operating materiel and supplies "OM&S" that are currently being managed using MS Excel spreadsheets. In addition, MDA is requesting DPAS system enhancements to support “actual cost” accounting for OM&S within the warehouse module. On occasion, MDA may have assets (non-capital and capital) that are awaiting transfer / disposition that it would like to have stored in a warehouse. DPAS does not currently support fixed asset accounting or OM&S accounting by actual cost for items that are accounted for in the warehouse. The proposed solution is for DPAS to configure to manage fixed assets within the warehouse module or through integration with a fixed asset module and to be able to electronically report those items to the MDA financial statements supported by Defense Agencies Initiative (DAI).
Recommended:
• By Stock Nbr, permit the user to determine how they want to financially account for the $ value of OM&S (MAC, LAC, ACT). Note: MAC = Moving Average Cost, LAC = Latest Acquisition Cost and ACT = Actual Cost. Actual cost would be limited to serialized OM&S.
• Develop a DAI accounting interface reporting capability to report capital assets and OM&S managed within the warehouse similar to how property accountability performs the financial reporting.
• Enable fixed assets and OM&S to transfer between DPAS modules along with their cost and depreciation. Items transferred between organizations with different catalogs will need to have the valuation set based upon the receiving entity's catalog.
Mission Critical:
The implementation of this SCR is in support of customers of the Warehouse / Materiel Mgmt. modules in support of financial accounting of fixed capital assets and OM&S. Methodologies must be DoD 7000.14R / FASAB / US. Treasury USSGL compliant to support an agency's Financial Improvement Audit Readiness "FIAR".
Benefits:
Supports financial compliance for all assets / supplies accounted for using DPAS regardless of module.
Frequency: Daily
Users: This change impacts all users of the Warehouse module.
|
|
02138
|
Update DRRS reporting for DAF Site-ids
|
PA,MU,Warehouse,FSM |
HQ AF/A4LR |
New |
Change Request: Policy/Regulatory
Description:
With the implementation of SCR 1935, we now require an updated Defense Readiness Reporting System (DRRS) report that will include the Authorization identification code on the property record. Additionally now the the Aviation Support (AvSE) community has completed the implementation of the M&U module we will also need to include the status of the assets that have been profiled in M&U.
Recommended:
Recommend updating the current DRRS report to include all DAF assets and add in the new data elements that are required for reporting
Mission Critical: IAW CJCSI 3401.02B Services are mandated to report DRRS readiness capabilities
Benefits: DAF will be in compliance with CJCSI 3401.02B
Frequency: Weekly
Users: |
|
|
Disclaimer | Accessibility
