CAGE Extensions

<< Click to Display Table of Contents >>

Navigation:  Definitions and Concepts >

CAGE Extensions

For most contractors shipments are made from the same entity to which contracts are awarded. In other words, the address CAGE code for both the Prime and Ship-From blocks on their Wide-Area Workflow (WAWF) Receiving Reports (etc.) will be the same CAGE code. In this case, CAGE Extensions do not apply.

Many contractors make use of mil-spec packaging houses or third-party logistics (3PL) providers. Others may use subcontracting companies to perform some contracts or portions of them. Still others may be subdivisions of a corporate entity that was awarded the contract (aka Prime Contractor).

WAWF will not allow entities other than the Prime Contractor to submit transactions such as Receiving Reports on their behalf, unless permission is granted to do so. One way is for the Prime to to give the Shipper a WAWF login under their account. While this may be okay for corporate entities, but it gives the shipper more access than is necessary, or probably, desirable for simply submitting transactions. Another way is for the Prime to submit the transaction themselves.

The solution is use of a CAGE Extension. This is done by the Prime, granting limited access to the shipping entity’s CAGE code to submit transactions on behalf of the Prime. The shipper’s validated users can then create Receiving Reports on the WAWF web site using their own credentials. Shippers submitting Receiving Reports (aka DD250s) via Electronic Data Interchange (EDI) must simply remember to attach their CAGE code to the Prime’s CAGE. Software systems like MIL-Comply will that automatically when appropriate

hmtoggle_arrow1 How to Create a CAGE Extension