1 / 27

Virtual Space Logistics Readiness Center (VSLRC)

Virtual Space Logistics Readiness Center (VSLRC). Kickoff Meeting 8 October 2002. Introduction of Team. Northrop Grumman Defense Enterprise Solutions Lonna Dumouchel: Program Manager Laura Kistler: Functional Lead Greg Golden: Technical Lead Dymond Associates Inc.: Consultant.

rudolf
Download Presentation

Virtual Space Logistics Readiness Center (VSLRC)

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. Virtual Space Logistics Readiness Center (VSLRC) Kickoff Meeting 8 October 2002

  2. Introduction of Team • Northrop Grumman Defense Enterprise Solutions • Lonna Dumouchel: Program Manager • Laura Kistler: Functional Lead • Greg Golden: Technical Lead • Dymond Associates Inc.: Consultant

  3. Company Overview • THIS SLIDE AND THE NEXT SHOULD PRESENT RATHER GENERAL, HIGH LEVEL INFORMATION • IT SHOULD NOT BE PERCEIVED AS AMARKETING PITCH • THIS IS A BIG “HOT BUTTON” FOR THE LAB

  4. Company Overview (Cont’d) • Quantitative and Strategic Analysis • Operations Research • Statistical Analysis • Business Process Reengineering • Cost/Benefit Analysis • Functional Economic Analysis • Information Technology • Systems Analysis and Design • Software Development • Database Management Modeling and Simulation • Process Modeling • Analytical & Decision • Support Tools • Logistics Simulations

  5. Technical Approach Problem Identification • No near real time, secure, web-enabled means for data exchange and display • Need to obtain visibility of status of space system assets for accurate decision making and reporting • Need to capture logistics and operations processes, policies, and systems as they evolve • Need an architectural solution to support EAF, cross-functional C2 objectives • Scaleable • Interoperable

  6. Technical ApproachUsers/Customers • HQ AFSPC/LGZ/LGX/LGM/LGS/SC • 14 AF/LG • Det 11SSMs • SMC/AX • OO-ALC/LH • HQ AFMC/DR

  7. Technical ApproachGoals/Objectives • Improved visibility of operational and logistical status through advanced information composition • Architecture to support near and long-term solutions • Legacy and evolving systems • AF Logistics/C2 requirements (current and future)

  8. Technical ApproachTechnical Challenges • Access to data systems, interfaces and databases • Access to key system users (experts)

  9. Technical Approach to Solution • Iterative, spiral development techniques used • Develop CONOPS (high level) • Depict VSLRC functional, system and reporting requirements • Data system and process analysis • Questionnaires used for in-depth focus • Interviews with SMEs • Det 11 interviews • Identify “holes/buckets” • Will work with UDRI on recommendations • Technological infrastructure overview • Size,scale and scope of operations

  10. Technical Approach to Solution (Cont’d) • Develop CONOPS (Cont’d) • ROI Analysis • Jointly define metrics and cost elements • Describe non-tangible benefits of VSLRC • Identify strengths, weaknesses, risks • Validate with AFSPC • Balanced Scorecard Approach (BCA) • Identify applicability to requirements • Identify performance measurements/mgmt objectives • Recommendations for incorporation into VSLRC

  11. Technical Approach to Solution (Cont’d) • Functional requirements managed with Rational Requisite Pro • Requirements Traceability Matrix (RTM) • Use Cases • Map within documentation requirements

  12. Technical Approach to Solution (Cont’d) • Requirements Traceability Matrix

  13. Technical Approach to Solution (Cont’d) Requirements View

  14. Technical Approach to Solution (Cont’d) Documented Requirements and Mapping

  15. Technical Approach to Solution (Cont’d) • Conceptual Demonstration • Slide presentation (only) to avoid resource drain • Data representation • Functional requirements representation • Maximize efficiencies • Cross functional • IT architecture/recommendation • Consistent and interoperable w/AF and DOD standards

  16. Technical Approach Major Milestones • Functional Requirements Identification • Technological Alternatives • Return on Investment (ROI) • Final Program Review • Conceptual Demonstration • Final Technical Report

  17. Technical ApproachProgress Measurement • MS Project detailed baseline schedule • Program Reviews • Monthly Status Reports (MSRs) • Funds and Man-Hour Expenditure Report • Internal contract progress/status reviews by Corporate Leads

  18. Technical Approach Exit Criteria • Requirements Traceability Matrix (RTM) • Baseline Cost of Work Performed (BCWP) • Conceptual Demonstration

  19. Planned Travel • DC to Dayton – KickOff Mtng • DC to LA – Data Collection • Dayton to LA – Data Collection • DC to OO-ALC – Site Survey • Dayton to CO – Data Collection and Progress Review • DC to CO (2 trips) – Data Collection and Progress Review Further travel requirements will be performed within contract cost/funding provided

  20. Risks • Management • Cost • Schedule • Technical • Data Access Requirements • Access to personnel (SMEs) for interviews • Risk Abatement Strategy • Leverage off of already existing studies/reports • Use management tools to monitor progress • Report any shortfalls in receiving access to data required to AFRL/HESS and associated impact to effort

  21. Major Unresolved Issues None

  22. Potential Benefits/Payoffs • First iteration in depicting VSLRC rqmnts (CONOPs) • Data system reduction • Advanced technological infrastructure • Improve Supply Chain Management (SCM) and LRC objectives • Performance Management/ Measurement goals identified and implemented • Conceptual demonstration of possibilities • Return On Investment (ROI) • Sound business case for “marketing” of VSLRC concept to senior leadership

  23. Programmatics Schedule

  24. ProgrammaticsMan-Hours and Types TypeHours Project Mgr 19 Sr. Analyst Manager I 879 Sr. Analyst Manager II 304 1,202

  25. ProgrammaticsDeliverables TypeDue Date Monthly Status Report 15th day of each month Funds and Man-Hour Rpt 15th day of each month Presentation Material As Required Technical Report (Draft) 7.5 MAC (~Apr 03) Technical Report (Final) 9.5 MAC (~Jun 03) All deliverables will be presented in contractor format

  26. ProgrammaticsContractor billing schedule/strategy • Invoiced monthly based on expenses incurred

  27. QUESTIONS?

More Related