Defense Parts Management Portal Scope Stand alone functionality on Team now Objective: Find ATP stock, or, Find a qualified Mfg. source Stand alone development on Team now Metrics Reporting Tool MRT Shared Data Warehouse SDW Service Schools like AFIT Stand alone functionality to be linked Defense Acquisition University GIDEP DPMP DKSP Parts Management: Parts Selection Parts Standardization Obsolescence Obsolescence Data Repository ODR Whatever is useful ModePro Skipping the fluff slides to get to meat. Not regurgitating the background material we are all familiar with. Trying to put a fence around our project so we can begin to think about how to make all of this work together. That is what DSPO does---”making systems work together” I am not much of a chartist but, what I am trying to show here are the big things inside the fence, which is in scope. GREEN are functional stand alone things on our Team now. A good bit of that is directly controlled by DSPO. YELLOW are stand alone things soon to be functional with some additional work ongoing now at GIDEP. Solid arrows show solid links today; dotted arrows depict efforts underway to develop links. DPMP overlaps with GIDEP but is also separate from what GIDEP does today. I think this model will evolve over time as we start to deliver capability and as users provide feedback. This portal will find an appropriate item in ATO inventory, or, failing there, find a suitable stable of capable companies who can make us one---all of us--faster, better, cheaper. Central Contractor Registry CCR DSPO Tools ASSIST, WSIT Pinnacle E-Mall Global Item Registry ExecSearch Industry Sources Tools & Data Defense Supply Centers DSCC, DSCR, DSCP Defense Qualified Mfgrs. & Parts Lists Defense Maintenance Depots

Spirals #1 & #2 Essential Process-initial focus is Parts Selection Basic Presence GIDEP Leads Spiral #2 Query TBD The basic portal presence and our vision for the future was briefed at the Industry Day session this past May. The Home Page is being developed by GIDEP and Tom Myers will provide an update of progress since that early showing. Brian Mansir has been conducting interviews over the past few months of people who do Parts Selection. He will share with us what we learned and how that affects our vision and our requirements. As I have been pursuing this project, Brian Mansir is the architect and Tom Myers is the host. By architect I mean the person who designs the basic structure and functionality in a seamless integration of capabilities. He also defines our requirements so we can communicate amongst ourselves and to interested industry participants. In the role of host, GIDEP is the technical face to the customer. There will always be need for human to human interface to bring about some connectivity, resolve issues, invite participation, determine priorities for development. That remains the case whether or not the servers end up on some farm managed by DLA. I see GIDEP, in close association with DLIS, as being integral to this role. We are sneaking up on spiral #2 where we face a critical decision. By policy, we will accommodate all comers. We can do it “direct” or via a third party “integrator”. However we decide, we have several choices for the underlying technology that generates those queries. We are working now to put a name to that “TBD”. Spiral #2 is the key spiral because everything we do depends on generating a query that is based on product parameters of interest.

Way Ahead Defense Parts Management Portal: Develop a consensus regarding business model-is it to be a government project presumably meaning a DSPO effort, or, is it to be a consortium? Reach consensus on our requirements so the white paper can be published and continually updated. Once that is decided, beyond the spiral view, we need a development roadmap which shows bite-sized (more easily fundable) projects in logical sequence with a reasonable estimate of cost and schedule. Absent this roadmap, we have no compelling case to ask for money-from government or from a consortium. There needs to be at least a basic idea for the business benefits to justify investment. Beyond that, there needs to be a sales/marketing campaign to attract support and guide development and accumulate information that becomes the BCA. I believe there are several years of effort to overcome inertia and establish sustainable forward momentum, starting with a budget that matches our ambitions. Merge that Data Sharing Project with AIA into the Portal Implementation Team. Develop Data Exchange Standards Engage Business Transformation Agency (BTA). We will need blessings of Investment Review Board (IRB). Here is what I see as the road ahead for the portal. Keep in mind, the portal is only the infrastructure that makes sharing possible. We need data sharing to make that infrastructure bear fruit and validate the wisdom of investing in it. Ergo, that second to the last point about integrating the AIA-OSD Tiger Team into this effort. We are talking about sharing that goes beyond getting Lockheed to share within Lockheed. If we do this right and get proper industry participation, we are talking about being, by far, the most efficient and effective tool for all matters related to Parts Management writ large. Companies can do things to share within their own boundaries. But, by participating in this portal, they get 1000X the benefit for a small fraction of the development and ongoing maintenance cost.

Way Ahead PSMC and DMSMS WG: Merge Training, Work Shop, Tools Committees. Add Joint Contracts Clause Committee. Develop a comprehensive conference strategy. Expand Portal Implementation Team to include services; rationalize industry participation. Exploit sunset clause for DMSMS WG to upgrade staff and to elevate to charter by USD/ATL. PMSG for overall governance? Continually update the group on what we have learned from the interviews and how that affects our vision, the spirals, the development roadmap and the funding level required to achieve desired schedule for progress. Here are some ideas I have regarding some possible ways to bring the PSMC Community and the DMSMS Community closer together. I am not talking about submerging or subsuming anything or anybody. I am talking about getting willing people to work together in the larger context while mindful of the unique challenges in Parts Selection---whether it is early in the life of a product when we call it Design Engineering or late in the life of a product when we call it DMSMS. My main goal for this meeting is to reach consensus on our requirements so our white paper can be updated. And, to hear about progress since the last meeting.