modification delivery order mdo version 1 0 1
Download
Skip this Video
Download Presentation
Modification/Delivery Order (MDO) Version 1.0.1

Loading in 2 Seconds...

play fullscreen
1 / 120

Modification/Delivery Order (MDO) Version 1.0.1 - PowerPoint PPT Presentation


  • 117 Views
  • Uploaded on

Modification/Delivery Order (MDO) Version 1.0.1. October 2006. MDO Overview. Introduction to MDO Benefits of MDO Status of MDO Deployment Expectations for Lead Users Available MDO Training Material MDO - Web-Based Application Demonstration MDO Workload Management

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Modification/Delivery Order (MDO) Version 1.0.1' - derry


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
mdo overview
MDO Overview
  • Introduction to MDO
  • Benefits of MDO
  • Status of MDO Deployment
  • Expectations for Lead Users
  • Available MDO Training Material
  • MDO - Web-Based Application Demonstration
    • MDO Workload Management
    • Generate Modifications and Delivery Orders through MDO
      • Issue a Delivery Order
      • Issue a Definitization Modification
      • Issue a Modification Changing Delivery Schedule
    • Review/Signature/Release Process
    • Working with Reports
      • MOCAS Reports
      • MDO Reports
  • User Issues
  • MDO Version Changes/Updates
  • Questions
introduction to mdo
Introduction to MDO
  • MDO will replace ACO Mod Module.
  • MDO is designed to provide DCMA Administrative Contracting Officers (ACOs) and Contract Administrators (CAs), with an updated automated tool to support the contract modification and delivery order writing process.
  • MDO takes the Agency another step closer to application accessibility via the web in lieu of reliance upon applications dependent upon client-server accessibility.
benefits of mdo
Benefits of MDO

Why is DCMA moving from ACO Mod Module to MDO?

MDO is -

  • Accessible via the web.
  • Able to interface with our Customers’ and Vendors’ systems.
    • The same electronic transaction (EDI format) that updates MOCAS can be routed to Customers and Vendors as a standard electronic transaction to that their systems can be automatically updated to reflect ACO-issued modifications and delivery orders.
    • Eliminates manual updates, which are considered to be time-consuming and prone to generate a number of errors.
    • Current EDI Testing:
      • Customers’ Systems - Ongoing test with ITIMP (NAVICP) and PADS (Army). Testing scheduled for BSM in Feb 07.
      • Vendors’ Systems – Ongoing test with Boeing.

$2.4M Savings!

10-to-1 payback in three years

benefits of mdo1
Benefits of MDO

MDO –

  • Creates electronic delivery orders that automatically post to EDA, eliminating the current manual posting process. Next version of MDO will post delivery orders to EDI.
  • Allows users from one CMO to issue MDO documents against another CMO’s workload (different DoDAACs).

MDO Delivery Order

EDA

status of mdo deployment
Status of MDO Deployment
  • Jun 06 – Beta test successfully completed at DCMA Hartford, DCMA AIMO Kelly and DCMA AIMO Greenville.
  • Jun 06 – MDO Lead-Users received hands-on training at four different locations across the Agency.
  • Jun 06 – Tasking Memo 06-206 issued to DCMAN requiring Navy completion of MDO Self-Guided General User Training.
  • Oct 06 – Tasking Memo – Requires Lead User Training and Deployment Across Agency (including tertiary offices). Suspense – October 13, 2006
mdo exceptions
MDO Exceptions

Documents that cannot be processed in MDO -

  • Modifications and Delivery Orders against contracts that are not currently in MOCAS.
  • Modifications against support contracts.
  • Global Modifications, including Name Changes, Novations, Admin Office and Pay Office Changes.
  • Modifications against Non-DoD Contracts
  • Modifications against BOAs, BPAs, or IDC basic instruments.

Note: MDO Version 1.5 is expected to permit these types of mods.

expectations for lead users
Expectations for Lead Users
  • Serve as the MDO expert advisor and first-line of assistance for users.
  • As the MDO expert advisor, arrange and present an overview of MDO to users. (recommended training material is available at http://home.dcma.mil/CBT/MDO/resources.htm).
  • Verify appropriate user roles (example: only warranted contracting officers may sign/release MDO documents)
  • Verify that all users have access to EDA and Reveal reports.
  • Ensure allContracting Officers, CAs, and 1106’s responsible for issuing modifications and delivery orders complete user training.
  • Require users to complete MDO Training Survey upon completion of training.
  • Require users to issue modifications and delivery orders via MDO immediately following completion of MDO user training.
available mdo training material
Available MDO Training Material
  • Power-Point Presentation
  • User Manual
  • Training Issues Document
  • Videos
  • Training Objectives Checklist
  • Training Survey

All MDO Training Material Posted at - http://home.dcma.mil/CBT/MDO/resources.htm

mdo workflow

EDA

EDA

MOCAS

MOCAS

MOCAS

MOCAS

MOCAS

MOCAS

FTP

FTP

ANSI X.12

ANSI X.12

FTP

SDW

SDW

850s & 860s

850s & 860s

FTP

ANSI X.12

SDW

850s & 860s

SQL,

SQL,

RPC

RPC

GEX

SQL,

ANSI X.12

ANSI X.12

XML

XML

RPC

eTools

eTools

850s & 860s

850s & 860s

ANSI X.12

XML

850s & 860s

www

www

IDB

IDB

www

Industry

Industry

IDB

Customer

EDA

Industry

DCMA User

DCMA User

MDO Workflow

FTP

GEX

GEX

slide12

Log Into eTools

Click eTOOLS Icon

slide13

Enter Username and Password

MDO is an e-tool application which requires a DCMA network log-in and password. No further sign-in is required.

slide14

Select MDO eTool

Click on MDO eTOOLS Icon

slide16

MDO Screen Layout Consists of a Header, Content Area, and Footer

The Header Consists of the Title Bar and Menu Bar

The Content Area Contains the Title of the Current Page and a Data Description Table

Click on a Search for Contracts Live-Link to Generate Mod or Generate Delivery Order

The Footer Provides Links to Standard DCMA Web Sites

slide17

Click on Query

Retrieving Data for Generating MDO Documents

Contract Search Criteria

Note: Contract Number Includes SPIIN When Searching for a Delivery Order

Enter the Basic Instrument Number with or without dashes or spaces.

slide18

Click on the “Create” Live-Link to Navigate to the Generate Mod or Generate Delivery Order screen

A list of contracts is returned based on query results.

slide19

Click on “My Work”

Live-Link

Modifications and Delivery Orders are Generated from this Screen

Depending on whether you are generating a Modification or a Delivery Order, you will navigate to the “Create Mod Page” or to the “Create Delivery Order Page.” Both pages auto-populate based on the Basic Contract or Basic Instrument. We will discuss this screen in detail later in the training module.

slide20

After Modifications and Delivery Orders Have Been Generated, the User will Be Able to View the Actions at the View My Work Page

Click on “Transfer My Work” to Transfer Actions to Another User

Generated Modifications will Appear Under the Contract Modifications Tab

“Assigned To” Column Shows to Whom the Action is Currently Assigned

  • Contracts will be assigned a status category:
  • Work in process
  • Rejected
  • Waiting for ACO Approval

Generated Delivery Orders will Appear Under the Contract Modifications Tab

slide21

Users May Transfer All Work or Individual Contractual Actions to Another User.

Click on Transfer Work Button to Complete the Transfer.

The New User will Now Be Able to View the Actions in Their “My Work Page.”

slide22

Kind of Mod, Type of Mod, and Kind of Contract are Selected.

These fields are not editable in later screens (user must cancel and generate a new modification).

Preparing a Modification Using MDO

This is the Obligation Amount as Currently Shown in MOCAS. Changes to the Obligation amount will not update until your modification has processed in MOCAS.

Click “Generate” and Then Go To My Work

Mod Number: User May Overwrite

NOTE: If user overwrites, alpha characters must be in Upper Case (CAPs). After generating, the number is no longer editable (user must cancel and generate a new modification).

slide24

Search for Contract Being Modified;

Click Query

Click “Create” Live-Link to

Pre-Generate a Modification

slide25

Verify/Change Mod Number;

  • Select Kind of Mod, Type of Mod and Kind of Contract;
  • Click “Generate”

CAUTION!

This is the only place that you can change the Kind of Mod,

Type of Mod, and Kind of Contract! If you make a

mistake, you must cancel the action and start over!

Receive Confirmation of Modification Creation; Click “Go to My Work”

slide27

All Delivery Schedules are Associated with a Line Item. User Must Click “Browse Line Items” to Access Associated Schedules.

slide30

Click “edit” Icon to Modify Schedule

Do not modify a CLIN that has fully shipped (shipped complete).

Partially shipped CLIN/schedule quantities may be modified (quantities reduced) as long as the items have not shipped. Since SDW data is generally 24 hours behind MOCAS updates, it is recommended that users verify Quantity Shipped on-line in MOCAS before issuing a modification changing schedules and CLINs.

slide32

New Date Appears at View Schedule Page; Click OK

Select the New Date from the Pop-Up Calendar

Click “Save Changes”

slide33

Click “Contract Number”

Review/Verify Delivery Date Change

slide35

Use the Opening Remarks Area to Identify the Authority for Issuing the Modification.

Click “Save Changes”

slide39

Review/Update Mod Number

  • Select Kind of Mod, Type of Mod, and Kind of Contract
  • Click “Generate”

Users Must Remember to Change Kind of Contract from “9 Unpriced Order Against BOA (BPA/IDT)” to the Appropriate Kind of Contract.

slide42

This Definitization Modification Calls for a Decrease in Estimated and Obligated Amounts.

Click on Appropriate ACRN

slide43

Click on Decrease Obligation Live-Link

  • 1. Users may deobligate funds using two different methods (only use one method):
  • Enter the new obligated amount in the Obligation Amount Field, or
  • Click on the Decrease Obligation Live-Link
  • 2. Users shall not:
  • Decrease an ACRN Obligated Amount which will result in a negative unliquidated obligation (ULO) amount.
  • Deobligate funds that have already cancelled. Canceling funds status should be reviewed in MOCAS prior to deobligation.
slide46

Review/Verify Obligated Amount. Note: ULO Amount will not update until Modification has Processed in MOCAS

Click on CLIN

slide48

Click “Save Changes”

User should make any necessary changes. In this instance, the user changed the Unit Price and Price Indicator. The Total Line Item Amount automatically updated when the user input the new Unit Price.

slide51

To Update the Delivery Date and Change the Estimated Indicator to Actual, Click on “edit” Icon

slide52

Change the Delivery Date Indicator by Selecting “Actual”; Change the Delivery Date by Using the Pop-Up Calendar

Click “Save Changes”

slide54

Review/Verify Schedule

(Total Quantity Scheduled Equals CLIN Order Quantity)

Click “Contract Number”

slide56

Update the Total Contract Amount and Change Definitization Status to “D Definitized”

New Field Added for ODO Payment Office. When modifying ODO contracts, users must select the appropriate ODO payment office DoDAAC from the drop-down menu

Click “Save Changes”

slide58

All Changes are Listed on this Screen. The Changes will also Appear on the PDF, under the Summary of Changes.

  • The User has the Option of “Undo” which will remove the change and reset the contract to the original state.
  • Click on “Contract Number”
slide60

Enter Authority for Issuing Delivery Order in “Opening Remarks”

  • Enter any closing remarks
  • Click “Save Changes”
slide64

Send to ACO/Review/Release Modification

  • ACO Approval Authority is Linked to the CAFU eTool.
  • Click on “Submit to ACO for approval” Live-Link
slide65

Enter ACO’s email address;

Click “Send to ACO”

slide66

User May Recall the Modification.

  • Status Changes to “Waiting for ACO approval”;
  • Note: After the ACO Releases the Modification, the Action will Disappear from the User’s Screen
slide72

ACO Receives a Confirmation of Release Action. Click “Release Mod”

ACO Receives Confirmation of Release. Click “Go to My Work”

slide75

Verify/Change Order Number (use all CAPS);

  • Click “Generate”;
  • Note: All Other Fields are Auto-populated Based on the Basic Instrument.

User Receives Confirmation;

Click “Go to My Work”

Click on “View”

slide77

Click “add” Icon

The ACRN is Automatically Populated, Starting with AA. Users May Change the ACRN Accordingly.

slide78

After Verifying/Changing ACRN, Adding Obligated Amount, and Long Line of Accounting;

Click “Add”

Verify ACRN and Obligated Amount;

Click “Contract Number”

slide81

Users may edit the CLIN. This field accepts ELIN and SLIN numbers. NOTE: Users MUST follow DFARS Part 204 Line Item Number formatting requirements.

Assign ACRN to CLIN, unless Not Separately Priced or No Cost Line Item Type is selected.

Select Line item type.

Users should select Product (Supply) Line Item type for tangible items that have a unit price, unit of measure, and quantity. This includes all items for repair.

Click “Add”

  • User should note that CLIN, Order Quantity, Unit Price, Purchase Unit, Noun, PQA Site, and Acceptance Site are mandatory fields.
  • Users should select a Service Completion Date for Service Line Items Only.
slide82

Verify Line Item Information;

Click “add” Icon to Add a Schedule for this CLIN.

slide83

Ship To, Delivery Date, and Quantity Scheduled are Mandatory Fields.

Click “Add”

Review/Verify Schedule Information;

Click “OK”

slide84

Click “OK”

Review/Verify Schedule. Note: Total Quantity Scheduled Must Equal CLIN Order Quantity.

slide85

Click “Back to Browse Line Items”

Users May Add Additional Line Items.

Click “add” Icon

slide87

Verify Line Item Information;

Click “add” Icon to Add Schedule

slide91

Review/Verify CLINs;

Click “Contract Number”

slide93

Enter Authority for Issuing Delivery Order on the First Line of the Opening Remarks.

Click “Save Changes”

slide97

Do Not Change Administered By Field

Effective date of the Delivery Order. Note: Defaulted to date Delivery Order created. To ensure correct formatting, users should populate the date using the pop-up calendar.

User must input Total Contract Amount. Note:The amount must equal or be greater than the sum of all CLIN amounts, depending on the type of contract (incrementally funded contracts).

SCD associated with Basic Instrument. Editable with drop down list. NOTE: User selection shall be limited to valid codes (None, A, or B). Do not use “C.”

Click “Save Changes”

slide99

CA May View PDF; Only ACO Should Print Hard Copy with Signature Block.

Follow Previous Review/Release Procedures

review signature release process
Review/Signature/Release Process
  • CAFU eTool Links to MDO ACO Authority
  • Only Warranted Contracting Officers Shall Sign/Release MDO Documents
  • Do Not Share User ID Codes and Passwords
  • Recommend ACO’s verify, at a minimum, –
    • Modification Number
    • Effective Date
  • Summary of Changes
    • Type of Contract
    • Kind of Modification
    • Type of Modification
    • 1st Line Cites Authority for Modification
    • Summary of Changes
  • Contract Administration Data
  • Signature Block
slide103

eTOOL REPORTS

MDO has One Detailed Report and One Cube. For Detailed Report, Click View Icon

slide107

Reveal Reports

  • Access the Reveal Reports Website at:
  • District East - http://reveal-e.dcmde.dcma.mil/
  • District West - http://reveal-w.dcmdw.dcma.mil/
slide108

Accepted ACO Modifications: Report number UNMA030G is divided into two sections.

The first section provides a list of all accepted transactions. This means that the header information (Inventory level data) accepted into MOCAS. However, it does not indicate that the full transaction was successfully received into MOCAS.

Users must verify that their transaction is listed in the second half of the Accepted Transaction Report. The second half of the report provides detailed acceptance information. A fully accepted ACO Modification transaction should appear in both sections of the reports.

slide109

Rejected ACO Modifications: Rejected ACO Modifications Report number UNMA010G provides a list of all rejected transactions. Errors are listed in the right-hand column of the report. Users must review the error and match the three-digit error code to the Error Messages and Corrective Action table found in Appendix B of this users manual. The table will identify a corrective action.

slide110

Accepted ACO Delivery Orders: Report number UNMA030A is divided into two sections.

The first section provides a list of all accepted transactions. This means that the header information (Inventory level data) accepted into MOCAS. However, it does not indicate that the full transaction was successfully received into MOCAS.

Users must verify that their transaction is listed in the second half of the Accepted Transaction Report. The second half of the report provides detailed acceptance information. An fully Accepted Delivery Order transaction should appear in both sections of the reports.

slide111

Rejected Delivery Order Report: Rejected Abstract Report Transactions Report number UNMA010A provides a list of all rejected transactions. Errors are listed in the right-hand column of the report. Users must review the error and match the three-digit error code to the Error Messages and Corrective Action table found in Appendix B of this users manual. The table will identify a corrective action.

slide113

User Issues(Refer to Training Issues Document for Details)

  • Erroneous or Missing Data: When data is erroneous in MOCAS or missing from SDW, users should make corrections in MOCAS before issuing documents in MDO.
    • Example: Unit of measure; order quantity, ship-to DoDAAC missing from MOCAS or SDW but is present on the contract in EDA or EDW.
  • Modification Duplication: To prevent duplicate creation of modifications or duplicate changes and ultimate rejection of documents, users should coordinate with other users (CAs, Mod Input Clerks, etc.) before issuing documents in MDO, ACO Mod Module, or via Free Form.
  • Numbering of Modifications: Modifications against contracts require a 6 digit modification number. Modifications against orders require a 2 digit modification number. MDO concatenates the delivery order and modification number “behind the scene” to ensure proper transmittal to MOCAS (EDI).
user issues con t
User Issues (con’t)
  • Remit To: MDO usually displays the remit-to CAGE code as null. Users should not change the CAGE or the address in MDO. Remit-to addresses are used by the payment office when issuing paper checks. Electronic payments are made using the CCR information.
  • Changes/Deletion of CLIN and Schedule Quantities:
    • Users should always delete CLINs instead of reducing quantities to zero.
    • Users do not need to delete schedules prior to deleting the CLIN. Deleting the CLIN also deletes all associated schedules.
    • Users should always delete schedules instead of reducing quantities to zero.
    • The sum of all schedule quantities must equal the total quantity on order for the associated CLIN.
    • Do not reduce CLIN/schedule quantities that have already fully shipped.
    • Partially shipped CLIN/schedule quantities may be modified (quantities reduced) as long as the items have not shipped.
  • MDO is a Live Database:
    • Users must cancel all “practice” modifications and delivery orders.
    • Signed/Released MDO documents will post to EDI (MOCAS) and EDA.
user issues con t1
User Issues (con’t)
  • Product CLINs Total Amount: The total amount must equal the quantity multiplied by the unit price.
  • PDF Format:
    • Compliant with FAR 53.105
    • Compliant with DCMA Forms Management Control
    • Legal sufficiency is related to the content of the MDO documents – not the format of the PDF.
  • Deployment: Upon completion of MDO training by Lead Users, start using MDO to issue modifications and delivery orders.
  • User Roles:
    • CAFU eTool Governs Authorization for Release/Signature of MDO Documents
    • ACO is Authorized Individual to Release/Sign MDO Documents
    • CAs/PTs are not Authorized to Release/Sign MDO Documents
  • Follow-Up Actions: Rejections, Successful Posting to EDA and EDW, Reviewing Reveal Reports.
  • Process for Reporting User Issues:
    • Lead User
    • DCMA Helpdesk
    • DCMA HQ Process Advocates
mdo version 1 0 1 changes
MDO Version 1.0.1 Changes
  • ODO Payment Office: Added a drop-down box to the Edit Contract Page for users to select the ODO Payment office code. Users should not change the Payment Office code “9” which is an indicator that the contract is an ODO. Users must select the appropriate ODO payment office code from the ODO Payment Office drop-down box. ODO payment office code can be found on the basic contract.
  • Issued By DoDAAC: Corrected MDO EDI transmission to MOCAS to reflect the appropriate Issue By office DoDAAC.
mdo version 1 0 2 changes
MDO Version 1.0.2 Changes
  • Modification Effective Date: Added a field to the Edit Contract Page to allow users to establish a modification effective date. This date will display as the modification effective date field on the modification PDF document. The signature date on the PDF document will be the date the ACO releases the document.
  • Line of Accounting: When a user changes (edit or delete) the LOA, the PDF will show the ACRN only, without the entire LOA. However, when the user adds a new LOA, both the ACRN and LOA will display on the PDF.
mdo version 1 5 changes
MDO Version 1.5 Changes
  • Line of Accounting Template
  • New Fields – Estimated Cost, Fixed Fee, Canceling Funds Indicator, Line Item Description, Days for Acceptance, Definitization Status for Delivery Orders, Requisition Number for Delivery Orders
  • Free Text Changes
  • Changes to NSN Field and Opening Text
  • Attachments
  • PDF Changes
  • MDO Numbering Validations

(Deployment Date Estimated–March 2007)

ad