ATAC_Business_Rules_v1_2_(Update_June_17)_(2).pdf

ADVANCED TRACEABILITY AND CONTROL

(ATAC)

Business Rules

Rev 1.2: 01 OCT 2012

ADVANCED TRACEABILITY AND CONTROL (ATAC)

BUSINESS RULES

TABLE OF CONTENTS

SECTION TITLE PAGE

1 Background 3 2 Scope of Work 4 3 Services to be Performed 6 4 Service Locations 16 5 Reporting Requirements 18 6 Quality Control 19 7 Acronyms 20

SECTION 1: BACKGROUND

1.1. Advanced Traceability and Control (ATAC) is a U.S. Navy program managed by the NAVSUP Weapon Systems Support (WSS) that combines supply, transportation, and financial logistics of repairable items into an integrated supply chain distribution system. These items are either Class IX spare parts (primarily repairables) or Class VII (primarily whole engines), at the request of the commodity manager. These items are more economical to repair than to replace when they become unserviceable and are critical contributors to warfighter readiness.

1.2. The Electronic Retrograde Management System (eRMS) is a web-based system that is utilized both afloat and ashore; in-port, in-garrison, and in-theater; for both serviceable and unserviceable parts. The capabilities provided by its different modules are selectively combined to meet the needs of specific customers. eRMS is the IT solution which enables the ATAC process.

1.3. ATAC operates a global network of nodes and hubs which provide IT processing, packaging, and ATAC approved transportation providers. In addition, the ATAC hub in San Diego provides oversight of a centralized transportation management and support to allow capable customer sites utilizing eRMS to ship material directly to the appropriate destination in a timely and cost-effective fashion while providing asset visibility.

1.4. ATAC provides services to a broad range of global customers aligned to US Fleet Forces Command (USFFC) , the Navy Systems Commands (SYSCOMs), the US Marine Corps (USMC), the US Coast Guard (USCG), the Defense Logistics Agency (DLA), the Department of Homeland Security (DHS), and other Components/Services. This specifically includes:

1.4.1. eRMS Afloat Customers: Carriers (CVN), Amphibious Platforms (LHA, LHD, LPD, LSD), Cruisers (CG), Destroyers (DDG), Combat Logistics Force (CLF) ships, USCG Cutters (WHEC, WMEC)

1.4.2. eRMS Ashore Customers: Naval Air Stations (NAS/NAF), Marine Aviation Logistics Squadrons (MALS), USMC Repairable Issue Points (RIP), Fleet Readiness Centers (FRC), Navy Shipyards (NSY), Regional Maintenance Centers (RMC), Submarine Bases (SUBASE), SPAWAR System Centers (SSC), Naval Surface/Undersea Warfare Centers (NSWC, NUWC)

1.4.3. eRMS Expeditionary Customers: Marine Expeditionary Units (MEU), Naval Construction Battalions (Seabees), Explosive Ordnance Disposal (EOD) units, and other Navy Expeditionary Combat Command (NECC) subordinate activities

1.4.4. Commercial repair vendors, using either WebCAV or eRMS DISPATCH software

1.4.5. DLA Distribution Centers using Distribution Standard System (DSS)

1.4.6. Non-WSS supply chain customers (Ground Marines, Army, Air Force, etc), at their request and expense

1.4.7. The table below shows ATAC volumes for FY11 (excluding Army & Air Force pilots):

Retrograde Engines Ground Marines

Repair & Return RDO RFI Total

372,299 6,775 53,136 21,262 80,562 198,628 732,662

SECTION 2: SCOPE OF WORK

2.1. Authority. NAVSUP Global Logistics Support (GLS) is authorized by NAVSUP Weapon Systems Support (WSS) 034 as the Service Provider to execute the ATAC. FLCs San Diego (Western CONUS through Mid-Pac), Norfolk (Eastern CONUS through CENTCOM), and Yokosuka (WestPac through South Asia) shall be authorized to implement policy and guidance in their AORs IAW NAVSUP WSS Program Manager direction (see section 4.1 for specific AOR definitions). The ATAC Program shall be considered a distinct Business Unit within the NAVSUP GLS enterprise and under each FLC.

2.2 Funding

Each FLC will develop annual and emergent budget requirements in coordination with the PM and their individual business office. The aggregated business requirements will be reviewed by GLS and the PM prior to submission. The GLS enterprise is responsible for requesting and obtaining the resources necessary to execute the ATAC mission, although the PM will advocate where possible.

2.3. Employees

2.3.1. The FLCs shall provide all personnel and supervision required for the performance of the ATAC services specified below, including during periods of surge volume. These FTE may partially or wholly consist of contractors or Foreign Nationals.

2.3.2. The FLCs shall comply fully with Federal and DOD regulations regarding occupational safety and health.

2.3.3. Personnel operating motor vehicles must possess a valid state drivers license and comply with base vehicle operation requirements.

2.3.4. Personnel must be available to work intermittently on nights and weekends, in place of daytime work hours, to accommodate pickup of ships’ materiel offloads when necessary.

2.3.5. The FLCs shall ensure each employee obtains from local government facility security offices any necessary passes and identification badges required for access to the facility, including DOD Common Access Cards (CAC).

2.3.6. Individual FLCs will perform human resource functions for ATAC personnel within their Area of Responsibility (AOR), including: execution of staffing and funding, hiring, travel, pay and compensation.

2.4. Facility and Materials

2.4.1. The FLCs shall comply fully with Federal regulations, all applicable federal, state, and local laws and permits, and DOD directives regarding environmental matters, fire safety, workplace safety, and hazardous material handling/transportation.

2.4.2. The FLCs shall ensure classified material is immediately turned over to the appropriate personnel at the co-locator once identified as such. When classified material is shipped, PRE- REPSHIP and REPSHIP messages will be generated according to proper procedures.

2.4.3. The FLCs shall safeguard all government property provided for its use. At the close of each work period, vehicles, facilities, support equipment and materials shall be secured.

2.4.4. The FLCs shall perform the services required under this agreement during a normal work week comprising eight continuous hours per day, beginning no earlier than 6:00 AM local time and covering core business hours (0900-1500), five days per week, except for federal holidays/administrative days . On an exception basis, the FLC’s facility shall be available on work nights and weekends, in lieu of daytime hours, to accommodate ship offload schedules. Locations providing regular support to customers in another time zone (e.g., San Diego support to the east coast) shall make appropriate arrangements to ensure reasonable coverage is available during the supported customer’s business hours. The specific hours and days of the week for each specific work site will be established by agreement with the Program Manager.

2.4.5. The working areas shall be of sufficient size and quality to allow the unhampered performance of the services specified below. At a minimum, this requires that there be space for receiving and segregation of material by type, plus staging areas for screening, packaging, and shipping. Additionally, a climate-controlled office space shall be provided of sufficient size to allow both employees and Technical Assistance for Repairables Processing (TARP) representatives to perform required work on computers, print documents, and manage paperwork. The workspace shall be physically distinct and separately securable from any co-located activities.

2.4.6. The FLCs shall provide all equipment, tools, materials, vehicles, utilities, and other items or services required for the performance of the services specified below, to include packaging, crating, and specialized packaging equipment (e.g., ESD station, heat sealer, etc) and forklifts.

2.5. Information Technology

2.5.1. Personnel shall have a DOD Common Access Card (CAC), access to the Navy-Marine Corps Intranet (NMCI) or equivalent networks, and an account in the Navy ERP system, as needed. The FLC is responsible for ensuring that any System Access and Authorization Requests (SAAR) are signed by an accountable security manager. The FLC must provide any hardware, software, or IT services needed to maintain connectivity and is responsible for resolving problems local to the FLC’s location/IT.

2.5.2. Personnel shall be knowledgeable on the use of the Electronic Retrograde Management System (eRMS). The Program Manager will provide initial training to personnel and additional training as needed or per the request of the FLC. The FLCs are responsible for 100% data accuracy and timeliness of information entered into eRMS. eRMS is a NAVSUP WSS program.

2.6. Co-locator

Items ineligible for the ATAC program, per 4.2.1 below, will be turned over to an accountable activity for proper handling. The FLCs shall designate a co-locator at each ATAC operating location.

SECTION 3: SERVICES TO BE PERFORMED

3.1. Overview. ATAC service requires handling several different categories of material in various segments of the repair cycle. Four primary categories of service are required, depending upon the nature of the material and its point in the repair cycle. The chart below summarizes the four categories of service and the work to be performed for each category. This work requires data entry into eRMS. The sections following the chart describe in further detail the specific categories of service and the work processes to be performed for each.

Categories of Service

Functions to be Performed

NRFI

(Retrograde, EI, QDR)

Engines, R&R (Repair & Return) RFI Offloads/MTIS RDO/RFI, Ground Marines (GM)

Receiving X X X X

Screening X X

Packaging X X X

Shipping X X X X

Customer/Quality Service

X X X X

3.1.1. NRFI (Retrograde)

The largest segment of the ATAC system involves processing and controlling repairable components which have become unserviceable and which are being returned from the end user or an intermediate maintenance activity to enter the depot level repair cycle. This category applies only to the NRFI components which are Beyond the Capability of Maintenance (BCM) of retail customers;

NRFI material is also moved under the Engines and R&R scenarios, in which case different business rules are applied. This category also applies to Engineering Investigations (EI) and Quality Deficiency Report (QDR) exhibits, to which eRMS applies special business rules.

3.1.2. Repair & Return (R&R)

R&R items are NRFI and RFI components which are not yet BCM at the retail level, but which cannot be locally repaired by the owning customer. Material is laterally redistributed to another activity with maintenance capability, who will either repair and return the broken unit or issue one off their shelf in exchange for the broken item. However, none of these events occur in the wholesale system and no MILSTRIP/MILSTRAP Transaction Item Reports (TIRs) are generated.

3.1.3. Engines

ATAC moves NRFI and RFI whole engines IAW individual disposition messages from the Type Commander (TYCOM) class desks. Whole engines are not stock numbered and their movements are not reported to the wholesale system. Engines have very lean inventories and are extremely high value items.

3.1.4. RFI Offloads / Material Turned Into Stores (MTIS)

Retail customers return excess RFI items to the wholesale system either because they are a Navy Working Capital Fund (NWCF) activity not authorized to hold material excess to their allowance beyond a certain level or because they are end-use activities seeking MTIS credit under the Material Returns Program (MRP). While the business rules associated with the two scenarios are necessarily different, the ATAC process is the same for both.

3.1.5. Ground Marine (GM) items

Under OPNAV/CMC Navy-Marine Corps Logistics Integration (NLI), ATAC moves Ground Marine secondary repairable (SECREP) items. Identification, disposition, and packaging are the responsibility of the GMs, while ATAC provides transshipment and traceability services. ATAC supports both Combat Logistics Battalions (CLB) deployed as part of Marine Expeditionary Units (MEU), whether embarked afloat or deployed ashore, and in-garrison Repairable Issue Points (RIP).

The MEUs are supported using essentially the engine process above, while the RIPs are supported using the RDO/RFI process below.

3.1.6. RDO/RFI

Redistribution orders (RDO) are issued by NAVSUP WSS to direct wholesale stock from a stock point (DD) to another stock point or (more typically) a commercial repair vendor. Project code ZI7 (alphabetic Z, alphabetic I, numeric 7) is used to tell the stock point not to ship these items themselves, but instead to make them available for ATAC pickup in order to provide traceability and achieve cost savings. ATAC receives consolidated copies of the RDOs in the form of daily Pickup Directives (PUD), specifying the origin, destination, document numbers, and quantities of material to be moved. After the commercial vendor repairs the items, another PUD is automatically generated for ATAC to move the Ready For Issue (RFI) item back to a stock point or directly to a Fleet unit (if a reconsignment). While the previous scenarios share many common eRMS modules and processes, the RDO/RFI system is distinct. NOTE: Not all stock points and repair vendors have been implemented on the ZI7 program.

3.1.7. DISPATCH

Commercial repair vendors participating in the RDO/RFI ZI7 program which do not use Web Commercial Asset Visibility (WebCAV) reporting software can utilize an additional eRMS module called DISPATCH. Under this program, inventory receipt, NRFI induction, RFI completion, and inventory issue TIRs are generated by eRMS to provide repair visibility to the supply system. At the end of the repair process, the vendor calls an ATAC dispatcher who inputs the relevant data in eRMS, before continuing on to the RFI stage of the RDO/RFI program.

3.1.8. Centralized Transportation Management

ATAC San Diego’s traffic management specialists shall be considered the ATAC Transportation Office for all shipments coordinated or executed by the ATACs or eRMS customer sites (including those operated by FLCs). To the extent permitted by readiness requirements, the Program Manager has directed the ATAC Program to reduce transportation costs, for instance by using the ATAC Tailored Transportation Contract (TTC) CONUS, Worldwide Express (WWX) OCONUS, and spot quotes as needed. It is the responsibility of the Transportation Office to determine the best value method of transportation for a given channel based on the origin, destination, weight, and priority of individual and aggregate shipments. Major changes in transportation methods or philosophy must be approved by the Program Manager. Shipping activities will ship only IAW Transportation Office procedures, including the periodic best-value grid provided to OCONUS shippers. The Transportation Office is also responsible for ensuring on-time pickups (where applicable), resolving customs delays, ensuring Pre-REPSHIP and REPSHIP requirements are met (and refusing to process such shipments otherwise), researching frustrated shipments, posting Proofs of Shipment (POS) & Proofs of Delivery (POD) on 100% of shipments, and validating transportation charges in a timely manner.

3.1.9. Changes to Business Rules

The Program Manager may in the future add or remove functions to the ATAC program. It is expected that the FLCs display flexibility in accommodating changes so long as those changes can be accomplished with existing resources. Substantial new requirements will receive commensurate increases in resources, per negotiation between the FLCs, the Program Manager, and NAVSUP HQ.

The FLCs shall notify the Program Manager of any significant procedural changes to the business rules described in this document. Mutual agreement between the FLCs and Program Manager shall serve as sufficient authority to make major changes to policy or procedures, but minor ATAC/eRMS procedural changes are made at the discretion of the Program Manager; agreed changes shall be documented herein.

3.2. Receiving (excluding RDO/RFI).

3.2.1. Eligible Materials: ATAC will accept custody of Depot Level Repairables (DLRs)/Secondary Repairables (SECREPs), excepting those exclusions listed below. In addition, ATAC will accept non-BER (Beyond Economical Repair) Field Level Repairables (FLRs) under the R&R, EI, PQDR, and RFI Offload scenarios. Items which can clearly be identified as exclusions will be immediately rejected to the customer if they are present. Items identified as exclusions only after material has been received or when material return to the customer is not feasible will be turned over to the co-locator using the appropriate eRMS function. eRMS will automatically identify exclusion items.

ATAC Exclusions

a. Consumable items (MCC other than D, E, G, H, Q, X), except for special projects

b. Top Secret, Classified Controlled Cryptological Items (CCI)/COMSEC, and all Arms, Ammunition, and Explosives (AA&E) items (CIIC D, E, F, K, L, N, P, Q, R, T, 1-6, 8)

c. Radioactive material (SMCC R, X; SMIC RS, RE)

d. Strategic Weapons Systems (SWS) items (COG 2P, 2X, 4P, 4X, 6A, 6H, 6P, 6X, 8P, 8X)

e. Items pre-determined for delivery to DRMO for disposal

f. Lateral distributions not processed in eRMS (e.g., BMD, A2, or A5 docids not generated by eRMS)

g. Items lacking a DD1348-1A, HAZMAT certification, or other required documentation, as appropriate

3.2.2. Material Delivered by Customers: The FLC will be responsible for the loading/unloading of all eligible DLRs brought or shipped to the ATAC. Receiving hours shall be the hours of operation as defined above. Uncertified HAZMAT should be refused or immediately excepted to the colocator.

3.2.3. Material Picked up from Customers: The FLC shall be responsible for picking up eligible DLRs from local end customers, unless other arrangements are agreed upon by the FLC and customer. For those locations requiring “on call” pickup service, material pickup will be the next working day. ATAC will pickup all eligible material available when performing regularly scheduled pickups. Local customers are generally considered to be those on-base or within a 50 mile radius, unless otherwise noted. Uncertified HAZMAT shall not be accepted.

3.2.4. Custody Transfer (Paperwork): ATAC will accept custody by signing individual DD 1348-1A IRRDs. In cases where multiple 1348s are shipped on a manifest, ATAC may sign that manifest instead, but only after verifying receipt quantity at a minimum (and individual document numbers if time/space permit) - pen and ink changes by the customer are not permitted. ATAC will furnish copies of signed documents to customers upon request only – primary proof of custody transfer is the receipt date in eRMS. These rules are applicable to both material delivered to the ATAC and material picked up from a customer. The acceptable document identifiers (subject to future change) for DD 1348-1As are:

DD1348-1A produced by any IT system

a. A5_ (Engines or Ground Marine items only)

b. BC1 (unscreened retrograde)

c. BEI (Engineering Investigation [EI] exhibit)

d. BQD (Product Quality Deficiency Report [PQDR] exhibit)

e. D6_ (RFI Offloads)

DD1348-1A produced by eRMS only

a. BC2 (screened retrograde)

b. BMD (R&R or Packup Kit [PUK] component movement)

3.2.5. Custody Transfer (eRMS): Every item entering ATAC custody shall have Proof of Custody Transfer recorded in eRMS using the Receiving function. Receiving personnel shall use the provided barcode scanners to perform data entry. All efforts will be made to receive items in eRMS as they arrive, even if that delays processing and shipment of outbound material. eRMS provides the option of printing out a hardcopy POCT receipt for those customers who wish one. eRMS will identify ATAC exclusions automatically for rejection to the colocator at the time of receipt. eRMS will also identify Carcass Express items at the time of receipt, to allow for expedited processing and shipment. Note that there are separate Receiving options in eRMS for RFI items and Engines; in addition, engine movements may be coordinated remotely, rather than staging engines at the ATAC.

3.2.6. Intercept Requests and Customer Returns: Customers may request that ATAC intercept inbound items shipped erroneously for return to the customer. ATAC will load the document numbers of intercept requests in eRMS. At the time of receipt, eRMS will flag intercept items and generate a customer return. ATAC can additionally generate a Customer Return on an item which has been received and not yet shipped. ATAC will return/ship the item back to the customer using standard shipping procedures (see 3.5).

3.2.7. Contractor Returns: Contractor returns will be processed using the appropriate eRMS receiving function. Receipt should be made using the original NIIN, to permit reidentification to the corrected NIIN during the screening process. This may require research assistance from NAVSUP

WSS.

3.2.8. Supply Discrepancies: ATAC will not be required to submit manually-generated SDRs for every discrepancy discovered at receiving. They will work with Technical Assistance for Repairables Processing (TARP) representative to do inbound sampling and identify customers requiring re-training. In the future, eRMS may automatically generate SDRs.

3.2.9. AIT Receiving: At the request of the FLC, handheld devices will be made available for performing the receiving function. The handhelds do not currently have wireless connectivity and require docking and synching with a desktop, but may be wireless in the future.

3.2.10. Passive Radio Frequency Identification (pRFID): The Program Manager reserves the right to implement additional/alternative receiving procedures using pRFID in the future. If such procedures impact workload requirements, the Program Manager will negotiate appropriate changes to staffing levels with the FLC.

3.3. Screening (excluding RDO/RFI)

3.3.1. Items Requiring Screening: eRMS will automatically determine which items require technical screening in the program based on previous entry by customers into the system and additional program logic. When reviewing items which have been received in eRMS, those not requiring screening will proceed directly to packaging. Typically, only unscreened retrograde (BC1), RFI offloads (D6_), and contractor returns require screening. In all cases, eRMS will automatically produce any required Transaction Item Reports (TIRs) as needed.

3.3.2. Items Requiring Manual Disposition Input: In most cases, disposition is already known or eRMS will automatically determine disposition. However, in a small number of cases where items were not previously entered into eRMS by the customer, the system will ask the user to enter the DODAAC of the destination. If this information is not present on the turn-in paperwork, it is necessary to contact the customer. Any problems occurring in this process should be addressed to the Program Office. The items requiring manual input of disposition when initial eRMS data entry occurs at the ATAC are:

a. Ground Marine and other Service items

b. Engines

c. EIs / PQDRs

3.3.3. NRFI Screening: When screening BC1s, ATAC personnel will compare the CAGE and Part Number listings on the eRMS screen to those physically marked on the component. ATAC will not use the CAGE/PN provided on customer DD 1348-1As. eRMS will display all CAGEs and PNs which apply to the entered NIIN. If none of the CAGE/PN markings on the component match those in eRMS, then ATAC will input the CAGE/PN from the component into eRMS and select a matching NIIN in order to perform a reidentification of the component. If CAGE/PN markings are missing, multiple/ambiguous markings are present, or ATAC cannot positively identify the component within four working days, it will be forwarded to the applicable ATAC hub using the Deep Screen feature. ATAC may also return the item to the customer, if available and upon request.

The serial number will be entered when available.

3.3.4. NRFI Deep Screening: Deep screening is performed at the two hubs, by equipment specialists in Norfolk and remotely at San Diego. The deep screeners shall use supply technical files (e.g., NAVSUP WSS Asset Visibility and FLIS), technical/maintenance documentation and drawings, and/or contact the Item Manager and/or Original Equipment Manufacturer (OEM) in order to positively identify items. Use of digital photographs may be necessary. Attempts shall be made for a minimum of 30 days, after which ATAC is authorized to force items to DRMO for disposal. If the deep screener has difficulty obtaining a response, they shall contact the Program Office for assistance.

3.3.5. NRFI Directed to DRMO: If reidentification from a BC1 results in eRMS directing the component to DRMO, ATAC personnel should turn over to the ATAC Hub Deep Screen Equipment Specialist. They in turn may contact either the Program Office or the NAVSUP WSS Item Manager for confirmation. If the component is not reidentified and is directed to DRMO, ATAC personnel may optionally confirm the disposition. Items already in ATAC custody which are then directed to DRMO are not considered an ATAC exclusion.

3.3.6. RFI Screening: RFI screening focuses on packaging discrepancies and the potential absence of an RFI tag, as opposed to the identification screening of NRFI items. However, ATAC is still responsible for attempting to verify the identity of the component so long as they do not compromise the OEM packaging or RFI tag. Correctible packaging deficiencies should be noted in eRMS and remediated. Large offloads will be transshipped to the ATAC hub for screening. Items marked with TARP tape are presumed to have already been screened as long as the tape has not been compromised.

3.3.7. RFI Rejects: Items whose RFI status cannot be confirmed shall be rejected back to the customer, if feasible; eRMS will produce an A6E DIC DD 1348-1A. Where not feasible, ATAC is authorized to downgrade the item to F condition using the eRMS function.

3.3.8. Paperwork: eRMS will produce multiple copies of the required DD 1348-1As. In addition, ATAC will use the Item Label option to produce a MIL-STD 129P tag when items are going to the local DD. If the 1348 states that additional paperwork (such as a logbook or Scheduled Removal of Component [SRC] card) is required, ATAC will ensure Logbooks, MAFs, and SRCs will physically be retained with the material, if provided.

3.4. Packaging (excluding RDO/RFI)

3.4.1. Packaging Requirements: ATAC shall package IAW the NAVSUP P700 / CNP-700 https://tarp.navsisa.navy.mil/p700 for all items passing through ATAC custody.

Container requirements and some special handling information is printed on the DD 1348-1A by eRMS. Full packaging instructions are in the CNP-700 website, accessible through eRMS or directly. Level 2 (fully capable) packaging is required for all NRFI items and Level 3 for all RFI items unless an exception has been authorized by the Program Office to transship an excess backlog to the nearest ATAC hub. In addition, items going to the local DD require a MIL-STD 129P label, which may be printed in eRMS, if not already present. Items marked as TARP Certified do not require additional packaging, unless apparent damage has occurred. ATAC is required to obliterate any obsolete markings on the outer container/pack and remove obsolete DD 1348-1As (e.g., BC1s).

3.4.2. Containers: Reusable containers shall be ordered periodically to ensure an adequate supply of the most commonly used containers is available when needed. In addition, when a CRRC is not locally assigned, ATAC will attempt to furnish containers from their inventory to local/transient customers upon request. Containers are available from the Container Reuse and Refurbishment Centers (CRRC) https://tarp.navsisa.navy.mil/crrc and from the supply system as 6K COG free issue items.

3.4.3. Heavy Packaging/Crating: ATAC will use the eRMS “Send to Packaging” feature to indicate items likely to experience a processing delay due to packaging requirements, including crating.

Items requiring crating will be turned over to the local DD (except where the ATAC has a local woodworking capability) using an exception manifest and received back from the DD for ATAC https://tarp.navsisa.navy.mil/p700 https://tarp.navsisa.navy.mil/crrc shipment. Crating will be performed in compliance with Wood Packaging Material (WPM) regulations.

3.4.4. Items Going to DRMO: Items being directed to DRMO do not require additional packaging and should be removed from any reusable containers prior to turnover.

3.4.5. pRFID: The Program Manager reserves the right to implement additional/alternative packaging procedures using pRFID in the future. If such procedures impact workload requirements, the Program Manager will negotiate appropriate changes to staffing levels with the FLC.

3.5. Shipping (excluding RDO/RFI)

3.5.1. eRMS Manifesting: eRMS automatically sorts items ready for shipping into manifest lists based on priority and destination. ATAC personnel will create manifests consolidating items going to the same destination on the same manifest. eRMS automatically assigns a Transportation Control Number (TCN) which serves as the manifest number, using the format [ATAC site DODAAC] + [Julian Date] + [sequence number] + [RXX]. The various lists available for manifesting are shown below:

a. Local Stow: All items directed to the nearest local stow point (DD) are listed here (both NRFI and RFI). All items must have a MIL-STD 129P item label.

b. Local RFI Stow: This list displays only the RFI items from the Local Stow option, if those must be manifested separately due to different delivery procedures. All items must have a MIL-STD 129P item label.

c. Local DRMO: Items directed to disposal. Arrangements must be made with the local DRMO for pickup/delivery. Do not send any reusable containers or MUCs. Note that some items require DEMIL prior to shipment to DRMO, which may in turn require the item be returned to the original customer.

d. Local Delivery: Destinations within a local service area may be designated to appear here to facilitate local deliveries. Contact ATAC San Diego to add or remove destination DODAACs from this category.

e. Carcass Express: High priority (Movement Priority Designator [MPD] 03 and higher) items appear here. These items must be manifested and shipped directly to the final destination, which also means they must be fully packaged. They are generally the highest priority to ship (along with engines). May be consolidated with routine shipments provided it meets the required carcass express delivery time.

f. Co-Locator: Items going to the co-locator (as an ATAC exclusion or for packaging) appear here.

g. OCONUS Node to CONUS: Routine priority items not falling in a local category appear here. Personnel must indicate in eRMS whether shipment is being made by Air Mobility Command (AMC) or commercial carrier, and whether items are going to the hub for transshipment or direct to final destination. Items being shipped direct must be fully packaged. Items with an OCONUS destination should be shipped directly using this option, not via transshipment at the CONUS hub. All shipment decisions must be IAW ATAC San Diego direction.

h. Customer Return: Successful intercepts or other customer returns appear here.

i. Engine: Engines must be manifested individually and do not use the standard eRMS manifest number convention, instead using document number + XXX. These are special interest items.

3.5.2. Means of Shipment: The ATAC Transportation Office at ATAC San Diego will provide periodic direction on which transportation carriers to use from which location at which priorities and weight classes. In addition, they will specify the commercial account numbers to be used. The FLC and eRMS sites shall only ship IAW these instructions. In general, AMC is not used due to lack of time definite delivery, non-traceability, and expense. The FLC is responsible for preparing documentation (including customs), arranging and executing transportation IAW these instructions, and contacting ATAC San Diego for direction on exception shipments. ATAC San Diego / the Program Office will provide a listing of required Transportation Account Codes (TACs).

3.5.3: Proof of Shipment (POS) and Proof of Delivery (POD): The FLC shall load POS in eRMS within 24 hours of shipment. Commercial shipments made IAW ATAC San Diego instructions will have POD automatically loaded by the commercial carriers the evening of the delivery. Local deliveries must be manually loaded into eRMS by the FLC. 100% of shipments must have POD loaded; the Program Office will attempt to resolve missing PODs first, but will contact the ATAC as necessary.

3.5.4. pRFID: The Program Manager reserves the right to implement additional/alternative shipping procedures using pRFID in the future. If such procedures impact workload requirements, the Program Manager will negotiate appropriate changes to staffing levels with the FLC.

3.6. RDO/RFI & DISPATCH Processes

3.6.1. Pickup Directives (PUDs): PUDs are generated automatically by the supply system or manually by eRMS users. Each one carries a Routine or Expedited priority indicator. All RDO/RFI items are considered to be at least Carcass Express priority (if Routine) or higher (if Expedited).

The major types of PUDs are:

1. Redistributions of NWCF stock carrying Project Code ZI7 (alphabetic Z, alphabetic I, numeric 7), primarily from DDs and less commonly from retail sites (NAS, MALS, etc)

2. Deliveries of A-condition items from commercial vendors using the WebCAV or DISPATCH software, primarily to DDs and less commonly to retail sites

3. Redistributions of USMC SECREPs

4. Deliveries of repaired R&R items from one retail site to another

3.6.2. Scheduling: Every PUD must be scheduled with a transportation carrier and pickup date.

Pickup sites may be designated as auto-scheduled or manually scheduled. Automatically scheduled pickups have the ATAC TTC carrier assigned by default and are typically daily pickups. All other PUDs should be scheduled within 1 working day. Scheduling is a function that is centrally performed by the ATAC Transportation Office. The assigned carrier can be changed when posting shipment data (see below). In the case of Urgent (immediate shipment needed) requirements, the ATAC Transportation Office shall authorize sites to self-ship and provide the data to ATAC for entry in eRMS. Items transported via the RDO/RFI process have high visibility and the Scheduling screens in eRMS should be checked throughout the day for unscheduled PUDs.

3.6.3. Pickups: ATAC is responsible for picking up all freight made available by the DD under the ZI7 program. ATAC will enter any discrepancies into eRMS upon receipt of the material using the appropriate codes: NQ (insufficient quantity), NX (excess quantity), or NR (no quantity of expected RDO received). Entry of NR/NQ remarks may be suspended by the FLC for up to 48 hours, to allow for the late arrival of the discrepant quantity. Verification of quantities is only required to the level of packaging documentation – i.e., packages are not to be opened to verify the internal counts in the case of multipacks. Discrepancies should be immediately reported to the issuing DD. eRMS will automatically create additional PUDs for the missing quantity on an NQ; after 2 weeks, eRMS will automatically convert the non-received PUD into an NR. If RDO Screening is being performed for the pickup site, it should be completed prior to recording the pickup in eRMS. Items transported via the RDO/RFI process have high visibility and the Post Pickup screens in eRMS should be frequently reviewed for delinquent pickups/deliveries.

3.6.4. Transportation: RDO/RFI transportation is centrally managed by the ATAC Transportation Office (per para 3.1.8). There is one entry in eRMS made for both the POR (POCT) and POS data.

When there is a delay in shipment, the POR data should be loaded immediately, and then updated to add the shipment data. This includes pickup attempts that resulted in an NR. The means of shipment chosen should reflect the priority of the item; delivery cycle times are found at the end of this document. Items transported via the RDO/RFI process have high visibility and PODs which do not automatically load shall be quickly researched and input using the eRMS RDO/RFI Open POD report. Items being shipped from CONUS to OCONUS require entry into the US Customs & Border Patrol Automated Export System (AES).

3.6.5. DISPATCH: The DISPATCH process allows ATAC to provide in-repair visibility at commercial vendors who do not use WebCAV. The process begins upon delivery of an RDO carcass from a DD. Upon repair, the vendor will call the ATAC Transportation Office. At that time, the Dispatcher shall correct the induction date (if necessary), input the repair date, generate a DD1348-1A, schedule a pickup, and provide any needed documentation via email, fax, or web to the vendor. DISPATCH requests may also be faxed. It may be necessary to work with NAVSUP WSS 01 POCs at Mechanicsburg and Philadelphia to resolve contract data issues. If the vendor indicates the wrong item was received (misidentification), process the carcass to the correct MRIL location if the correct NIIN is known or to the nearest ATAC hub for screening if not. If the vendor indicates an item is BER, use the appropriate option in eRMS to process the change to H condition and process the shipment to DRMO (or decrement the site inventory if vendor is scrapping).

3.7. Customer/Quality Service

3.7.1. Care of Material in Custody: ATAC necessarily acts as a temporary material collection point, due to the nature of material pickups, customer deliveries, fluctuating operational tempos, the priority placed on receiving material as it arrives, and processing & packaging time requirements.

The FLC is responsible for the care of material while it is in ATAC custody. The FLC shall handle all items with care and take precautions to ensure that material handled is not lost, damaged, misused, subjected to deterioration by elements of the weather, or otherwise neglected while in the FLC’s custody.

3.7.2. Traceability and Control: eRMS is the system of record for all ATAC services. The FLC is responsible for quickly, accurately, and completely entering requisite data in the system. All material handled by ATAC is subject to signature control and custody turnover requires that signature be legible (or electronic) and accompanied by a date.

3.7.3. Customer Inquiry Response: The FLC shall respond to inquiries from customers or system users concerning the status, disposition, and POD of material handled. This response will include any necessary research and communication and copies of documentation necessary to respond to Transportation Discrepancy Reports (TDRs), Supply Discrepancy Reports (SDRs), system loss reports, or other inquiries concerning the status or disposition of material handled by the FLC.

3.7.4. Customer Service: ATAC shall maintain customer service toll-free phone lines, including one for general inquiries (currently 877-846-8728) and one for performance of the DISPATCH function (currently 866-215-3084). In addition, ATAC shall monitor a customer service email address (currently ATACCustomerService@navy.mil).

mailto:ATACCustomerService@navy.mil

SECTION 4: SERVICE LOCATIONS

4.1. Regions

4.1.1. The ATAC Program shall organize operating locations into East, West, and Pacific regions.

4.1.2. East Region: The East region will be managed at ATAC Norfolk and encompass the service areas of FLCs Norfolk, Jacksonville, and Sigonella: areas east of the Mississippi in CONUS, the Caribbean, the Atlantic coasts of Central and South Americas, Europe, the Mediterranean, Africa, and Southwest Asia (SWA).

4.1.3. West Region: The West region will be managed at ATAC San Diego and encompass the service areas of FLCs San Diego, Puget Sound, and Pearl Harbor: areas west of the Mississippi in CONUS, Alaska, Hawaii (Mid-Pac), and the Pacific coasts of Central and South Americas. In addition, ATAC San Diego remains the lead ATAC and has overall responsibility for the performance of the ATAC Program across all regions, specifically for transportation management.

4.1.4. Pacific Region: The Pacific region will be managed at ATAC Yokosuka and encompass the service area of FLC Yokosuka: Asia (less SWA) and the Western Pacific (WestPac), including Korea, Japan, Diego Garcia, Australia, Thailand, the Philippines, and Guam.

4.2. Types of Locations

4.2.1. Hubs: The ATAC service locations at San Diego and Norfolk shall be designated as hubs and will have sufficient physical space and human resources to support large volumes of regular business, overflow from other operating locations, and administrative functions, as determined by the Program Manager with FLC input.

4.2.2. Nodes: Other ATAC locations shall be minimally staffed and resourced to support processing, packaging, and transshipping typical volumes of material, as determined by the Program Manager with FLC input.

4.2.3. Mobile Nodes: Temporary nodes shall be established upon Fleet request and Program Manager approval to support expeditionary and contingency operations. These mobile nodes may or may not be staffed by FLC personnel, but will be supported by the appropriate FLC region. The FLC will budget additional resources as needed.

4.2.4. Customer Sites: Customers using eRMS are not listed here. However, ATAC is responsible to support them per Program Manager direction and existing agreements. Examples of customers are Naval Air Stations (NAS), Marine Aviation Logistics Squadrons (MALS), Shipyards & Regional Maintenance Centers (RMC), Fleet Readiness Centers (FRC), and ships of all sizes.

4.3. Current Nodes/Hubs

Region Type Location DODAAC RIC East Hub Norfolk, VA N68620 PDH East Node Bahrain N3310A PDY East Node Jacksonville, FL N3307A PDU East Node Mayport, FL (Jacksonville Det) N4639A PMP East Node Rota, ES N59000 PG9

East Node Sigonella, IT N3309A PDW East Node Souda Bay, GR N59005 NSZ East Node Panama, PA N59004 N6A East Node Guantanamo Bay, CU N55892 NQ2 East Node Djibouti, DJ N55899 NQ5

Pacific Node Chin Hae, ROK N32778 PEF Pacific Node Guam N4572A PGM Pacific Node Iwakuni, JP N4181A PUK Pacific Node Okinawa, JP N4182A PUJ Pacific Node Singapore N4535A NAN Pacific Node Yokosuka, JP N4179A PUP Pacific Node Yokota, JP N3054B PEU Pacific Node Atsugi, JP (FRIA only) N4180A PUN

West Hub San Diego, CA N46433 PDJ West Node Everett, WA (Puget Sound Det) N48439 NTR West Node Pearl Harbor, HI N3116B PFJ West Node Puget Sound (Bremerton), WA N3118B PFN

4.4. Current/Past Mobile Nodes

Region Location DODAAC RIC East Al Asad, IQ N40024 NCZ East Al Jaber, KW N4534A NAL East Al Taqaddum, IQ N4569A NFN East Alexandria, EG N3524B PEG East Aqaba, JO N55897 PKJ East Bagram, AF N4570A NDF East Bastion, AF N55898 PD8 East Camp Buehring, KW N55896 PHK East Dwyer, AF N59006 P4R East Fujairah, UAE N4533A NAM East Jebel Ali, UAE N55591 PC3 East Kandahar, AF N4568A NEU Esat Leatherneck, AF N59002 P2G Pacific Clark AB, PH N4641A PPH Pacific Korat, TH N4605A PFL Pacific Pohang, ROK R49005 PK6 Pacific Rockhampton, AU N55894 P49 Pacific Townsville, AU N55893 P53 Pacific Utapao, TH N50081 PHQ Pacific Yechon, ROK N58796 PGE

SECTION 5: REPORTING REQUIREMENTS

5.1. GENERAL

In the performance of ATAC services, the FLCs shall monitor, compile and maintain pertinent information regarding the performance of the system.

5.2. RECORDING INFORMATION

eRMS. The FLC shall record material identification and processing information in eRMS for all material handled in the performance of ATAC services.

5.3. REPORTING TRANSPORTATION DATA

Throughput volume and cycle time will be measured automatically in eRMS. In addition, the ATAC Program shall collect a weekly Work-in-Process (WIP) report. Transportation costs and avoidances shall be reported quarterly.

5.4. REPORTING BUDGET EXECUTION

Budget execution by site will be reported monthly to the Program Manager, within 2 weeks after the end of the month.

5.5. ATAC MANAGEMENT REPORT

The FLCs shall be prepared to provide the Program Manager status reports as needed.

5.6. REPORTING METRICS TO HIGHER ECHELON COMMANDS

All metrics being provided to other commands (e.g., NAVSUP, USFFC, CNAF, CNSF, CSF, NECC, MSC, NAVAIR, NAVSEA, SPAWAR, NAVFAC, OPNAV, LOGCOM, HQMC, USTRANSCOM) shall be provided by the Program Manager directly or only with specific Program Manager approval.

SECTION 6: QUALITY CONTROL

6.1. MONITORING ATAC SYSTEM EFFECTIVENESS

The FLCs are responsible for monitoring ATAC system effectiveness, quality, and timeliness. The FLCs shall investigate problems as they occur, not only to fix the problems, but also to determine the root causes for the purpose of business process improvement, and to prevent any such problems from recurring. The FLCs shall take necessary action to resolve inefficiencies within its own operations, and shall make recommendations to the Program Manager to correct inefficiencies in ATAC processes or other processes outside the control of the FLCs.

6.2. FACILITY ACCESS

The Program Manager, ATAC Director, and TARP representatives shall have unrestricted access to service locations. The Program Manager’s designated agents are authorized to conduct quality sampling without prior notification. The FLCs shall provide access to visitors upon request.

6.3. SCHEDULING AND PICKUP METRICS

All attempts shall be made to schedule and execute pickup requests within 1 working day. ATAC may make local arrangements with sites to pickup routine retrograde on a less frequent periodic basis, such as once or twice a week, by mutual consent.

6.4. DELIVERY CYCLE TIMES

The FLCs will provide monthly delivery cycle time metrics, which may also be obtained in eRMS.

Metrics are measured in calendar days. End-to-end delivery cycle times (including during periods of surge volume) are listed in the chart below. Cycle time begins when ATAC or an assigned carrier first accept custody of an item and terminate upon the date of signed delivery at the final destination, less the pickup day (e.g., an item picked up on Monday and delivered on Wednesday has a cycle time of 2 days;

same day deliveries have a cycle time of 0 days). Note the chart below includes cycle times at the nodes and hubs, not just transit time. It may be revised by the PM outside of these business rules as required.

Cycle Time Standards (calendar days, POR to final POD)

Category Express/Expedited Routine

NRFI 8 14

R&R, GMs, EI, PQDR 4 6

RDO/RFI 6 8

Engines 6 14

RFI Offloads/MTIS N/A 20

6.5. REPORTS

The Program Manager will provide periodic reports which the FLCs shall work in a timely fashion.

These reports, their contents, and their periodicity are subject to change. Current reports are:

a. Due In From CLF Report (Weekly)

b. Overdue WIP Report (Weekly)

c. Open POD Report (Weekly)

d. CT/SIT Report (Monthly)

6.6. MATERIAL LOSSES

Material determined to be lost while in ATAC inventory (meaning there is Proof of Custody Transfer to ATAC and no Proof of Shipment) shall be written off using the eRMS Inventory Loss function. Items lost during shipment (meaning there is Proof of Turnover/Shipment but no Proof of Delivery or Receipt) shall be written off using the eRMS Shipper’s Loss function. The FLCs shall perform causative research and ATAC San Diego will centrally process losses for all sites/shipments after final review. The primary list of items to research shall be the monthly CT/SIT report and ATAC shall process the appropriate loss for items that cannot be located within 45 days of receipt of the listing.

SECTION 7. ACRONYMS

AES Automated Export System AIT Automatic Identification Technology AMC Air Mobility Command AOR Area of Responsibility ATAC Advanced Traceability and Control BCM Beyond Capability of Maintenance BER Beyond Economical Repair BOS Base Operating Support CAC Common Access Card CAGE Commercial And Government Entity CAV Commercial Asset Visibility CIIC Controlled Item Identification Code CLB Combat Logistics Battalion CLF Combat Logistics Force CMC Commandant of the Marine Corps CNAF Commander, Naval Air Forces CNSF Commander, Naval Surface Forces COG Cognizance Code CONUS Continental United States CRRC Container Reutilization and Refurbishment Center CSF Commander, Naval Submarine Forces CT Carcass Tracking DD Distribution Depot DLA Defense Logistics Agency DLR Depot Level Repairable DOD Department of Defense DODAAC DOD Activity Address Code DRMO Defense Reutilization Marketing Office EI Engineering Investigation eRMS Electronic Retrograde Management System ERP Enterprise Resource Planning FLC NAVSUP Fleet Logistics Center FLIS Federal Logistics Information System FLR Field Level Repairable FTE Full-Time Equivalent GLS NAVSUP Global Logistics Support GM Ground Marines HAZMAT Hazardous Material HQMC Headquarters, Marine Corps IAW In Accordance With IT Information Technology LOGCOM Marine Corps Logistics Command MCC Material Control Code MEU Marine Expeditionary Unit MILSTRAP Military Standard Transaction Reporting and Accounting Procedures MILSTRIP Military Standard Requisitioning and Issue Procedures MPD Movement Priority Designator

MRP Material Returns Program MSC Military Sealift Command MTIS Material Turned Into Stores MUC Multiuse Container NAVAIR Naval Air Systems Command NAVFAC Naval Facilities Engineering Command NAVSEA Naval Sea Systems Command NAVSUP Naval Supply Systems Command NECC Navy Expeditionary Combat Command NLI Naval (or Navy-Marine Corps) Logistics Integration NMCI Navy-Marine Corps Intranet NRFI Not Ready-For-Issue NSDRS Navy Supply Discrepancy Reporting System NWA Network Activity NWCF Navy Working Capital Fund OCONUS Outside continental United States OEM Original Equipment Manufacturer OPNAV Office of the Chief of Naval Operations POCT Proof of Custody Transfer POD Proof of Delivery POR Proof of Receipt POS Proof of Shipment POT Proof of Turnover PQDR Product Quality Deficiency Report pRFID Passive Radio Frequency…