OST-R | ITS JPO Home | Research | Research Archive

Research Archive

Description of Lines 139 to 162

Tasks 139 to 162 of the 2003 to 2007 Work Plan of the Electronic Freight Manifest

The graphic represents tasks on lines 139 to 162 of the FY 2003 to FY 2007 Work Plan of the Electronic Freight Management.

Many tasks in the graphic are subtasks of other tasks. The tasks are listed in bullets below, in proper hierarchical order and with the associated costs, where included, and the time span for each task.

EFM Foundation Elements (continued)

  • EFM Information Highway (continued)
    • Develop Operational Plan and Tools (continued)
      • Award Contract – Mitretek, Q3 of FY 2004
      • Milestones (Web Services) – Q3 of FY 2004 to Q2 of FY 2005
        • Ongoing Technical Support for Web Services approach in FIH Conceptual Operations Plan – Mitretek, Q3 of FY 2004 to Q2 of FY 2005
  • EFM Business Case – $300K Cost in FY 2004, Q1 of FY 2004 through Q1 of FY 2006
    • Develop Deployment Test Plan – Q1 of FY 2004 through Q1 of FY 2006
      • Prepare SOW (Battelle) – Onder Group, Q1 to Q2 of FY 2004
      • Award Contract – Onder Group, Q2 of FY 2004
      • Milestones – Q2 of FY 2004 through Q1 of FY 2006
        • Develop EFM Program Plan – Q2 of FY 2004 through Q1 of FY 2005
          • Map business processes of supply chain – Battelle Group, Q2 to Q3 of FY 2004
          • Define legacy technology systems – Battelle Group, Q3 of FY 2004
          • Map data to FIH and standard – Battelle Group, Q4 of FY 2004
          • Prepare EFM Program plan – Battelle Group, Q4 of FY 2004 through Q1 of FY 2005
        • Recruitment and Outreach – Q2 of FY 2004 to Q1 of FY 2005
          • Stakeholder (public and private) recruitment – Battelle Group, Q2 of FY 2004 to Q1 of FY 2005
          • Industry and Government Outreach – Battelle Group, Q2 of FY 2004 to Q1 of FY 2005
        • Prepare a system-level design document for EFM – Q3 of FY 2004 through Q1 of FY 2005
          • Define Data Needs – Battelle Group, Q4 of FY 2004
          • Develop EFM Architecture – Battelle Group, Q2 of FY 2004
          • Data Integrity and QA Plan – Battelle Group, Q1 of FY 2005
          • Develop System-Level Design Document – Battelle Group, Q1 of FY 2005
        • Conduct EFM proof of concept with "The Limited" and their Supply Chain partners – Q2 of FY 2005 through Q1 of FY 2006
          • Prototype Development – Battelle Group, Q2 of FY 2005
          • Deployment and Training – Battelle Group, Q2 of FY 2005