1 / 53

A U.S. Perspective: CALS to c-Commerce In The 21 st Century

CALS/EC Seminar. A U.S. Perspective: CALS to c-Commerce In The 21 st Century. Sunshine City Prince Hotel Tokyo, Japan. Friday, January 24, 2003. Robert S. Kidwell Vice President / Sr. Technical Director ManTech International Corporation. Basic Foundation.

dreama
Download Presentation

A U.S. Perspective: CALS to c-Commerce In The 21 st Century

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CALS/EC Seminar A U.S. Perspective: CALS to c-Commerce In The 21st Century Sunshine City Prince Hotel Tokyo, Japan Friday, January 24, 2003 Robert S. Kidwell Vice President / Sr. Technical Director ManTech International Corporation

  2. Basic Foundation • Since the events of “911” (September 11, 2001) Homeland Security & Homeland Defense have become our highest priority. • InformationTechnology has increased in importance in our society. • For example, in the Public Sector there are many new initiatives that can only be achieved by “Information Superiority” enabled by Interoperability.

  3. Information Superiority “The ability to collect, process and distribute an uninterrupted flow of information, while exploiting and/or denying an adversary’s ability to do the same.” “Getting the right information to the right people at the right time in the right form.” U.S. DoD 5000.2 April 2002 Commercial = Competitive Advantage and Network Centric Information DoD/Military = Force or Survival Advantage and Network Centric Warfare (NCW) is transforming the U.S. DoD into the Information Age Basic Foundation

  4. National Information Assets Must be superior to those who would challenge us. We must possess information systems in both business and operational areas that provide a dominant knowledge position” Promote improvement in DoD Policies Make better use of secure, accurate, and timelydata Integration & Interoperability Ensure current DoD transformation initiatives aimed at improving programs and business practices resulting in more effective and efficient collaboration Increase the use of industrial base capabilities Information Superiority

  5. Medical E-CAT Supplier EMALL Increased Visibility Increased Sales Streamline Order Process Collect Payment Faster shopdod.mil [ Future ] US Defense Information Needs Profile • “To me, our DoD has the most varied and insatiable (appetite) need for accurate, timely, and secureinformation than any organization on the planet. In time of future conflicts information will become the predominant factor. 1M Items Customer • Reduced Procurement • Cost • Reduced Pricing • Reduced Administrative • Lead Time • Improved Efficiency • Extended Life Cycle • 3500 + Technical Manuals • turned into IETM(s) • Web Centric/The JIA • Life cycle Maintenance • Vendor Inventory • Lab equip • Dental • Optical • Medical equip • $8M/Monthly • Sales • DoD is moving from e-Commerce to c-Commerce Security * Security * Security

  6. “The ability of systems, units, or forces to provide data, information, material, and services to, and accept the same from other systems, units, or forces.” [ U.S. DoD 500.2 April 2002 ] Computer-Based Systems View “Interoperability is the ability of dissimilar systems to be linked together and operate as a single entity Multiple levels and degrees of interoperability Technical considerations Business case model cost considerations [ U.S. DoD C4ISR Highlights Five Levels of Interoperability ] Interoperability

  7. Featuring Examples • Where relevant, I will highlight the specific work examples of our own information technology projects for which we are currently doing on a National and International Level for the U.S. Department of Defense (DoD) www.dcnicn.com/calsec03/

  8. Hot Topics • Information Technology Theme • Collaboration or c-Commerce • Information Interoperability • Homeland Security • e-GOV • e-Procurement • Our Briefing Summary Points

  9. Affiliations CALS Industry Steering Group Board of Directors Chair, Information Technology CALS Expo, EC Expo International CALS Congress Vice Chair of the Americas Association for Enterprise Integration (AFEI) 1998 – 2002 Government Electronic Information Technology Board of Directors CALS Create Data once, use many times Suite of Standards Based on International Standards as a “Neutral Format Profile” Creation of the Contractor Integrated Technical Information Service or CITIS Fore runner of Internet Based Information Sharing, Serving, as a Collaborative Domain Integrated Data Environment (IDE) To me, CALS became a global wake-up call that electronic digital information sharing is the way of our future.

  10. 1. Collaboration or c-Commerce

  11. U.S. Government Public Sector “The only Concept we can Count On Today is Change Itself” Driving Change Today • National Security, Terrorism, and Global Security • American Economy and Global Economy • Aging Work Force • Unprecedented Coordination between our Federal, State, and Local Governments • Every Company Doing Business with the Government has created a Homeland Security Division/Unit[ ManTech National Security Solution Group ] “Agility: The Ability to Respond to Unexpected Change”

  12. Collaboration or c-Commerce “The Emerging e-Business Model” “ Collaborative Decision Process: Uniting People In Collaborative Business Process” “When Wal-Mart sells a Light Bulb on the Point of Sale Terminal IT goes to My factory instantly I (General Electric) MAKE A Light Bulb for the one just Sold. The Enterprise is Now totally complete with Information” Jack Welch Former CEO/General Electric • Virtual Organization • Virtual Integration • Virtual Collaboration “A set of Electronic Enabled Collaborative Interactions Between an Enterprise, It’s Customers, BusinessPartners, Suppliers and Employees” Gartner Group

  13. Collaboration or c-Commerce We at ManTech’s e-IC are involved in Defining “The Future Logistics Enterprise” (FLE) for the U.S. Department of Defense (DoD) with Special Consideration on Integrating The Supply Chain Based on the Principles of c-Commerce and Interoperability with the Goal of Achieving Information Superiority

  14. Joint Vision 20/20 Doctrine Condition Based Maintenance + “Prognostics” Total Lifecycle System Management Executive Agent Depot Maintenance Department with Industry End-To-End Distribution The Future Logistics Enterprise (FLE) “Interoperability is the Foundation of Effective Joint Multinational and Interagency Operations. Interoperability is a Mandate for the Joint Force 20/20 Especially in terms of Communications and InformationSharing The Future Logistics Enterprise is DoD’s near Term Blueprint to Improve Military Effectiveness And Logistics Support through End-To-End CustomerServiceandEnterpriseIntegration Based on: Enabled By Enterprise Integration

  15. Make Plan Source Deliver Return Maintain “The Supply Chain is the Collection of People, Organizations and Resources that provide the Materials and Services Necessary to Supply Product to the Customer” Supply Chain Council The “SCOR” Model All Across the Department of Defense (DoD) Logistics Transformation is Underway

  16. 2020 Goals, Objectives & Vision SCOR Concepts, Roles & Constructs FLE Functional/Business Processes, Performance, Business Practices & Metrics Concept Validation & Requirements Definition “AS IS”* (Processes, Systems & Applications) Implementation Strategy & Direction Gap and Overlap Assessment Implementation (Processes, Systems & Applications) Static & Dynamic Models Our Approach: Top Down“Warfighter to Source” Plan Source Make Deliver Return Maintain • * Includes approved changes & • On-going initiatives

  17. Collaborative Supply Chain Test Environment Virtual Enterprise Business Processes e-Business Drivers • • • ManTech e-IC • Defense Logistics Agency Shared Data Environment Sub-contractor Extended Enterprise • • Military • • SupplierExtended Enterprise e-Marketplaces Virtual Enterprise • • • Enabling Technology Not Just Speed, but Speed with a Destination Organization & Culture

  18. WWW.DCNICN.COM * The Defense Collaboration Network/International Collaboration Network

  19. What is the DCNICN? DCN-ICN is a set of secure Web services that facilitate and ease collaboration and information sharing between working groups, regardless of location • Service Oriented Approach providing Web-centric • Application (Collaboration and Information) Services • to: • Virtual Organizations • Project Teams • Integrated Product Teams • Integrated Process Teams

  20. Information Services • Core Information Services • Related Interest Organizations • CALS/EC/STEP Initiatives and Implementations • CALS/EC/STEP Publications and Repositories • Electronic Publishing • CorePlus Information Services • Document Management System • Digital Technical Information Technologies • CALS/EC/STEP Events • CALS/EC/STEP Specialists and Partnerships • CALS/EC /STEP Test and Certification Resources • Information Subscription/Notification Dissemination Information services are browser accessible (IE 5.x+, NN 4.7+)

  21. ManTech’s Role in support of TC184/SC4 • Design/ develop/ implement/ sustain of Collaboration/ Information sharing Website, SC4ONLINE (www.tc184-sc4.org) • Secretariat Support of SC operations including balloting, publication, coordination with ISO, Convenors, Technical experts

  22. 2. Information Interoperability

  23. Information Interoperability • “Information interoperability” begins by considering human-to-human, human-to-machine, and machine-to-machine interactions. • Only when shared information is interpretedcorrectly is there successful communication with corresponding desired outcomes. • Only when information is engineered for perfect interpretation can there be perfect communications that is timely, accurate, and complete in it’s understanding.

  24. In order to have “understanding” users of information must address information in context with regard for viewpoints and different language and symbol constructs. Today we hear the terms “semantic Web,” “semantic mediation,” and “semantic information interoperability.” These are the newest of ideas in the global business lexicon. Meaning and resulting effect concentrates on achieving accurate understanding and accurate exchange of information. That is consistent with what are ever-present goals. Internet and Web-based Environment Advanced Ideas from Data Warehousing and Data Mining to Knowledge Management

  25. Traditional EAI is Point to Point Hard-coded Mappings “Brittle, tightly-coupled EAI/B2Bi interfaces”

  26. EII Utilizes an Intermediate Abstract Conceptual Model New / Legacy Source Applications New / Legacy Target Applications The Integration Schema also known as Abstract Conceptual Model (ACM) is based on ISO 10303 (STEP) information model and provides an ontology to capture both the semantics and context of data.

  27. OPNAV 4790 Processes ECPs, Logistics, Maintenance, etc. <!-- =========================================== --> <!ELEMENT identifier(#PCDATA)> <!ATTLIST identifier datatype CDATA #FIXED "STRING"> <!-- =========================================== --> <!ELEMENT part_relationship (part_relationship.other_relating_product_identifier, part_relationship.other_relating_.other_product_relationship_name, part_relationship.other_product_relationship_description, part_relationship.related_product)> <!ATTLIST part_relationship id ID #IMPLIED> <!ELEMENT part_relationship.other_relating_product_identifier (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_identifier datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship.other_relating_product_design_version (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_design_version datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship_ref EMPTY> <!ATTLIST part_relationship_ref refid IDREF #REQUIRED> <!-- =========================================== --> <!ELEMENT identifier(#PCDATA)> <!ATTLIST identifier datatype CDATA #FIXED "STRING"> <!-- =========================================== --> <!ELEMENT part_relationship (part_relationship.other_relating_product_identifier, part_relationship.other_relating_.other_product_relationship_name, part_relationship.other_product_relationship_description, part_relationship.related_product)> <!ATTLIST part_relationship id ID #IMPLIED> <!ELEMENT part_relationship.other_relating_product_identifier (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_identifier datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship.other_relating_product_design_version (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_design_version datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship_ref EMPTY> <!ATTLIST part_relationship_ref refid IDREF #REQUIRED> <!-- =========================================== --> <!ELEMENT identifier(#PCDATA)> <!ATTLIST identifier datatype CDATA #FIXED "STRING"> <!-- =========================================== --> <!ELEMENT part_relationship (part_relationship.other_relating_product_identifier, part_relationship.other_relating_.other_product_relationship_name, part_relationship.other_product_relationship_description, part_relationship.related_product)> <!ATTLIST part_relationship id ID #IMPLIED> <!ELEMENT part_relationship.other_relating_product_identifier (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_identifier datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship.other_relating_product_design_version (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_design_version datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship_ref EMPTY> <!ATTLIST part_relationship_ref refid IDREF #REQUIRED> <!-- =========================================== --> <!ELEMENT identifier(#PCDATA)> <!ATTLIST identifier datatype CDATA #FIXED "STRING"> <!-- =========================================== --> <!ELEMENT part_relationship (part_relationship.other_relating_product_identifier, part_relationship.other_relating_.other_product_relationship_name, part_relationship.other_product_relationship_description, part_relationship.related_product)> <!ATTLIST part_relationship id ID #IMPLIED> <!ELEMENT part_relationship.other_relating_product_identifier (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_identifier datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship.other_relating_product_design_version (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_design_version datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship_ref EMPTY> <!ATTLIST part_relationship_ref refid IDREF #REQUIRED> <!-- =========================================== --> <!ELEMENT identifier(#PCDATA)> <!ATTLIST identifier datatype CDATA #FIXED "STRING"> <!-- =========================================== --> <!ELEMENT part_relationship (part_relationship.other_relating_product_identifier, part_relationship.other_relating_.other_product_relationship_name, part_relationship.other_product_relationship_description, part_relationship.related_product)> <!ATTLIST part_relationship id ID #IMPLIED> <!ELEMENT part_relationship.other_relating_product_identifier (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_identifier datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship.other_relating_product_design_version (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_design_version datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship_ref EMPTY> <!ATTLIST part_relationship_ref refid IDREF #REQUIRED> <!-- =========================================== --> <!ELEMENT identifier(#PCDATA)> <!ATTLIST identifier datatype CDATA #FIXED "STRING"> <!-- =========================================== --> <!ELEMENT part_relationship (part_relationship.other_relating_product_identifier, part_relationship.other_relating_.other_product_relationship_name, part_relationship.other_product_relationship_description, part_relationship.related_product)> <!ATTLIST part_relationship id ID #IMPLIED> <!ELEMENT part_relationship.other_relating_product_identifier (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_identifier datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship.other_relating_product_design_version (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_design_version datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship_ref EMPTY> <!ATTLIST part_relationship_ref refid IDREF #REQUIRED> <!-- =========================================== --> <!ELEMENT identifier(#PCDATA)> <!ATTLIST identifier datatype CDATA #FIXED "STRING"> <!-- =========================================== --> <!ELEMENT part_relationship (part_relationship.other_relating_product_identifier, part_relationship.other_relating_.other_product_relationship_name, part_relationship.other_product_relationship_description, part_relationship.related_product)> <!ATTLIST part_relationship id ID #IMPLIED> <!ELEMENT part_relationship.other_relating_product_identifier (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_identifier datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship.other_relating_product_design_version (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_design_version datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship_ref EMPTY> <!ATTLIST part_relationship_ref refid IDREF #REQUIRED> <!-- =========================================== --> <!ELEMENT identifier(#PCDATA)> <!ATTLIST identifier datatype CDATA #FIXED "STRING"> <!-- =========================================== --> <!ELEMENT part_relationship (part_relationship.other_relating_product_identifier, part_relationship.other_relating_.other_product_relationship_name, part_relationship.other_product_relationship_description, part_relationship.related_product)> <!ATTLIST part_relationship id ID #IMPLIED> <!ELEMENT part_relationship.other_relating_product_identifier (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_identifier datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship.other_relating_product_design_version (#PCDATA)> <!ATTLIST part_relationship.other_relating_product_design_version datatype CDATA #FIXED "STRING"> <!ELEMENT part_relationship_ref EMPTY> <!ATTLIST part_relationship_ref refid IDREF #REQUIRED> Navy SH-60 EXS Sikorsky ECS Legacy App’s Enterprise Integration Center (e-IC) Navy SH-60 (Seahawk Helicopter)Interoperability High Level Architecture This component will be developed by ManTech e-IC Existing System at Sikorsky (built for Army) Sikorsky Life Cycle Support Applications Modulant Interoperability Server Interoperability Server • EXS = Enterprise eXchange Server

  28. 3. Homeland Security and e-GOV

  29. Ministry of Land, Infrastructure, and Transportation Utilize and conserve land in Japan in an integrated and systematic way. Develop essential infrastructure. Implement transportation policies. Promote progress on meteorological tasks. Maintain marine safety and security. Accomplish this by removing bureaucracy and employing integration strategy. You are “slimming” organizations and achieving improvements in administrative “quickness.” So are we… Department of Homeland Security Encompasses those activities that are focused on combating terrorism and occur within the United States and its territories. Detect Deter Protect against Respond to terrorist attacks Creating New Organizations

  30. Vice President President Major Cabinet Departments and Agencies Involved in Homeland Security OVP NSC OHS DPC NEC OMB ONDCP PCIPB WH Counsel Borders Emergency Response CIP WMD Special Protection NSTAC Agriculture Commerce HHS FEMA Transportation Treasury Justice State Defense NIH National Enforcement 94 U.S. Attorneys Coast Guard JCS Food Safety Industry & Political Affairs Security Security NIAID Western Hemisphere APHIS Secret Service Customs Criminal Division NORTHCOM TSA Planning & CIAO CDC Mexico Desk Assistance ARS FLETC NORAD TVCS FAA NIST Canada Desk National Forest Service NCID OFAC JTF - CS Policy Justice Programs Preparedness FHA Counterterrorism FDA USPHS NIOSH FinCEN SOLIC & Homeland ODP Regional Management OEP Offices ATF Personnel OIPR Consular NDMS Reserve Affairs FBI Visa Office NGB IC CT Division Energy Interior EPA GSA VA CSTs Health Affairs OSWER NDPO National DIA NPS Police Technology Service Hospitals CIA Labs CEPPO AT&L U.S. Army USMC NIPC NRO BIA Police FCIRC CTC Labor OERR NNSA DOMS CBIRF DDR&E INS NSA Buildings Service BLM Police NPC OAR Medical Command NBC Defense BW R&D OSHA Border Patrol Protective Service FWS Police Army Intelligence NIMA ORIA USUHS DTRA MRMC DEA Incident Disaster Services Navy Intelligence OECA INR Response C3I USAMRIID AFRRI Teams Marshals Service NEIC USAF Intelligence DOE Intel DISA Material Command NRC FCC USPS Marine Intelligence DOT Intel OPPTS ORD OW SBCCOM NCS Transformation For Starters!!!

  31. Border Security Preparedness Transportation Security Mitigation Coast Guard Response Immigration Services Recovery Department of Homeland Security Secretary Deputy Secretary State, Local, and Private Sector Coordination Secret Service Emergency Preparedness and Response Chemical, Biological, Radiological, and Nuclear Countermeasures Information Analysis and Infrastructure Protection Border and Transportation Security Infrastructure Protection Science & Technology Development Physical Assets Chemical Telecommunications & Cybersecurity Biological/Agricultural Radiological/Nuclear • Federal Emergency Management Agency • Chemical, Biological, Radiological and Nuclear Response Assets • Domestic Emergency Support • Nuclear Incident Response • Office of Domestic Preparedness • National Domestic Preparedness Office Threat Analysis Visa Processing • Civilian Biodefense Research Programs • Lawrence Livermore National Laboratory • National BW Defense Analysis Center • Plum Island Animal Disease Center • Critical Infrastructure Assurance Office • Federal Computer Incident Response Center • National Communications System • National Infrastructure Protection Center • National Infrastructure Simulation and Analysis Center • Immigration & Naturalization Service • Customs Service • Animal & Plant Health Inspection Service • Coast Guard • Federal Protective Service • Transportation Security Administration

  32. e-Government“Citizen Centric” • Web-Enabling Government — transforming traditional government operations to integrated, Internet-based environments for improved public sector accessibility, efficiency, and customer service — has become a primary objective for organizations across all levels of government. • Emerging and established programs underway across government organizations that serve to integrate the essential components of successful KM initiatives, include: • e-Learning • Citizen Relationship Management • Information Technology implementation • Data warehousing and other related disciplines • Internet/Web Links to State/Local Governments

  33. Also, a planned Solution Architects Working Group website SAWG.gov The Federal Enterprise Architecture (FLE) “A Foundation for Government Wide Improvement” The Federal Enterprise Architecture is being Constructed through a series of “Reference Models” designed to Facilitate Cross-Agency Analysis and Improvement. The Business Reference Model Serves as the Foundation for the Other Reference www.fea.pmo.gov

  34. 4. e-Procurement Paperless Contracting Environment * e-Bidding

  35. Wide Area Workflow Paperless Contracting Environment APPLICATIONS SHARED PROCESS DEBX Closeout DD 1594 Wide Area Workflow SHARED DATA Vendor Data Contract Data Financial Data Log/Receipt Data SPS/Legacy Systems DPPS/Legacy Systems DPPS Legacy Systems E-CAT Medical Suppliers Post Award Contract Pay Contract Closeout Solicitation Requirements Evaluation/Award Contracting Continuum

  36. CCR Process & Metrics Data Output Vendor Data Input On-line DUNS Validation Public Web Search Daily Extracts 3rd Party Data Validation 838 EDI CCR Tools CD-ROM US Postal Service CAGE Federal Reserve Bank SBA Planned TIN Planned • Database Metrics (As of Dec 2002) • - Approximately 211,000 active vendors • Averaging <12 hours processing time • (Requirement is <48 hours per DFARS)

  37. 5. Our Briefing Summary Points

  38. Technology vs. Standards ebXML STEP XML EDI Summary • Internet Technologies will Continue it’s Explosive Growth • Application service suites, Web Services • Software As A Service (SAAS) Subscription vs. License • Information Assurance • Search Engines: Subscription/Notification Profile (PUSH) • Wireless Communications • c-Commerce will continue to evolve over the next 5-7 years. I • believe it will Achieve Information Superiority and Interoperability • Standards will play a very important role: The Question is how • do we Achieve Global International Standards? • Information Exchange Standards will make the largest • impact • OASIS e-GOV XML Committee • Formed December 2002 • e-GOV framework Exchange between interested countries

  39. Summary Information Interoperability Information Superiority c-Commerce EC B2C B2B CALS Thank You CALS/EC • CALS/EC Promotion Toward Realization of e=Japan • CALS to c-Commerce in the 21st Century

  40. Backup - Slides

  41. CALS Technical Information • Engineering Drawings • Inventory/Logistics • Technical Publications and • Manuals EC/EDI Business Transactions Exchange STEP/PDES Standard • Product Description • International Movement • To: • Completely and Accurately • Describe a Product • Component or Assembly • of Parts Data • Purchase Order • Advanced Shipping Notice • RFQ • Proposal Process Improvement Based On ANSI X12 / CEFACT ISO 1030 Principals of Concurrent Engineering and “IPPT” CIRCA 1991 - - - In The Early Years Exchange of Information in Standard Electronic Digital Format • Move From Paper To Electronic Storage and Exchange

  42. CIRCA 1994/1996 - - - In The Mid Years e _ _ _ _ _ _ e-Everything ELECTRONIC BUSINESS “Simply a way of doing business electronically”? e-Commerce: • Concept that embraces a growing range of enabling • technologies for supporting The Timely Exchange of • Business Information Transaction(s) • Electronic Data Interchange (EDI) • Automatic Identification Technology • Bar Coding • E-Mail • Fax • Electronic Catalogs • Internet Technologies • These are what we conduct over the growing range • of enabling technologies Or _ _ B2C Or _ _ B2B e-Business: Delivery of: Information, Products/Services, Payments VIA Computer Networks

  43. CIRCA 1996/Today - - - - - Internet Technologies Virtual Enterprises CALS / Electronic Commerce Continuum Process Model Outsourcing Over NII/GII Distributed Collaborative Engineering Product/Process Data Driven Manufacturing Initial Complementary Intersection of CALS and EC / EDI Technical Data Interchange Network Enabled Business Practices Integration EDI and Internal Applications Electronic Data Interchange

  44. Sample Capabilities Area • E-Mail • EDI (basic capability, non-integrated) • Network-based Bulletin Board Electronic Data Interchange • EDI integrated with Manufacturing Resource • Planning (MRP) and CAD/CAM systems • EDI integrated with financial systems Integration of EDI and Internal Systems • Data interchange among heterogeneous systems, • such as STEP (in CAD to CAD exchange), IGES, • SGML, SQL, EDI Trans. 841 • Enterprise-wide technical data repository Technical Data Interchange • Numerical Control Systems • Manufacturing Executive Systems (MES) • STEP in manufacturing process • MRP/Product Data Management (PDM)/Enterprise • Resource Planning (ERP) Data Driven Process Manufacturing Product/ CIRCA 1996/Today – Internet Technologies R. S. Kidwell / ManTech

  45. CIRCA 1996/Today - - - Use Of XML NOTE: • Over the past year alone the market for XML • servers has delivered an incredible performance • Between 2001 and 2002 XML servers have grown • by 168% which, IDC firmly believes, will in turn create • a market worth some $3.5 billion by 2006 • Reference: IDC, Monday, September 16, 2002 • http://www.it-analysis.com • By 2003, the Gartner Group predicts that 80% of Web-based • B2B traffic will be passed as XML documents Virtual Enterprises c-Commerce Product Development/ Distribution Outsourcing Via e-Markets Collaborative Business Practice Initial Complementary Intersection of CALS and EC / EDI Product/ Technical Data Interchange XML Internet Enabled Business Practices Integration ERP/EDI and Internal Applications XML Electronic Data Interchange XML

  46. Word Example New-Economy Definition New-New-Economy Definition Filed (verb) Round (noun) Positioning (noun) Returns (noun, plural) Red (noun, slang) Networking (noun) “Etoys filed today.” “AllAdvantage.com just finished Its second round.” “Schwab is meeting with the Street to clarify its positioning “Amazon.com saw record returns Last quarter.” “Have you seen NetZero’s red?” “Alice is totally focused on Networking these days.” To file paperwork for an IPO. A round of venture capital Investment A non-Internet company’s attempt to Characterize itself an an Internet Company. Increased value of an investment or Stock price. Short for “red herring” – an IPO Prospectus. Frantic building of a telecom Infrastructure in a rapidly growing company To file paperwork for bankruptcy. A round of layoffs. An Internet company’s attempt to charac- terize itself as a non-Internet company. Defective or late-arriving merchandise Sent back to the retailer. Short for “red ink” – operating losses. Frantic building of a contact infrastructure To find a job, any job, in a rapidly Shrinking economy. Summary View: Does The c’ in c’Commerce Really Mean Collaboration? “We live in a Fast Fast Paced Business, Economic, and Technology Environment Where “Change” is the only thing we can Count On.” Source: Industry Standard

  47. End User Communities Vendor Communities Application Services Summary View: Does The c’ in c-Commerce Really Mean Collaboration? • Promises of c-Commerce are the Next • Big Step in our Progression • Integrated/Dynamic Supply Chain Management • New Product Collaborative Engineering/Life Cycle • Product Data Sharing • Interoperability Among Different Applications • CostEffective Data Exchange Solutions • Open/Upward Compatibility of Computer/Network etc. _ _ _ Thank You

  48. Market Overview: EDI Software and Services • EDI transactions (whether clear text or encapsulated • in XML) will continue to account for the majority of all • computerized Business-To-Business (B2B) transactions • for the next several years, and EDI revenues for software • and services will grow from $1.8 billion in 2001 to $2.1 • billion by 2006. * • [*] Market Overview: EDI Software and Services, Ken Vollmer, • March 2002

  49. IT Trends 2003 • Electronic Data Interchange (EDI) • Trends for EDI in 2003 include continued • growth in EDI usage, a return of stability to the • value-added network market, more common • usage of hybrid EDI systems and a growth in • the use of universal translators. * • [*] Giga Information Group, Ken Vollmer 2002

  50. EDI Messages used for Gov’t and DoD Acquisition (ASC X12) • 810 Invoice • 820 Payment Order/Remittance Advice • 824 Application Advice (to accept or reject translated data) • 836 Award Notice • 838 Trading Partner Profile • 840 Request For Quotation (RFQ) • 843 Response To Request For Quotation • 850 Purchase Order Or Delivery Order • 855 Purchase Order Acknowledgment • 864 Text Message • 997 Functional Acknowledgment

More Related