Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Using a Crosswalk File to Manage Givers and Receivers

9 views

Published on

A presentation to the Joint Space Cost Council at Ball Aerospace and Technologies Corporation, Boulder, Colorado, 21 September 2017.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Using a Crosswalk File to Manage Givers and Receivers

  1. 1. Programmatic Architecture and the Cross Walk File 1 Using a Cross Walk File to Manage Givers and Receivers Ron Powell Glen Alleman Rick Price Joint Space Cost Council Ball Aerospace and Technologies Corporation Boulder, Colorado, 21 September 2017
  2. 2. Programmatic Architecture and the Cross Walk File ❻ Steps to Building the Credible IMS 2 WBS Risk Register Master Plan Deliverable Need Dates Master Schedule(s) Master Schedule(s) Master Schedule(s) Master Schedule(s) Cross Walk File Connects Dependencies Between Master Schedule ❻ ❺ ❹❸ ❶ ❷ AleatoryEpistemic
  3. 3. Programmatic Architecture and the Cross Walk File Our Plan Has To Contain  Who is going to do the work?  What are the outcomes from this work?  When does the work need to get performed?  Where is the work being performed?  Why are we doing all this?  How is the work going to actually be performed?
  4. 4. Our Plan Has To State Outcomes  Who ‒ Staffing Plan  What ‒ SOW/SOO/CDRL/WBS  When ‒ Contract Delivery Dates  Where ‒ Facilities and Services  Why ‒ Contract / ConOps  How ‒ Technical Deliverable Strategy Six Honest Serving Men, from The Elephant’s
  5. 5. Programmatic Architecture and the Cross Walk File ❹ ‒ How Do We Establish “Need Dates” Discussion Topics  What does the Contract say – How do we know this date is credible? – How do we establish schedule margin for the date to protect the contract date?  At IBR how do you – Show credibility for all the work, including subcontractor – Using the SRA to establish margin – Show how cost is adequate to meet requirements – Understand the risks and their mitigations 5
  6. 6. Programmatic Architecture and the Cross Walk File ❺ ‒ The Integrated Master Schedule(s) … 6  Show what Done looks like.  Show the work needed to get to Done.  Defines the needed resources to reach Done  Identifies risks to Done and their handling.  Measures physical progress toward Done in units meaningful to the decision makers.
  7. 7. Programmatic Architecture and the Cross Walk File ❻ ‒ Making Interdependencies Visible 7 Simple Representation of an IMS consisting of 4 project files linked serially. CROSS WALK FILESEIT Project Plan Payload Project Plan Ground Project Plan Launch Project Plan Output TO Payload FROM SEIT Input from SEIT FOR Payload Output TO Ground FROM Payload Input from Payload FOR Ground Input from Ground FOR Launch Output TO Launch FROM Ground Integrated Master Schedule Each line represents an external link between project files
  8. 8. Programmatic Architecture and the Cross Walk File ❻ ‒ Cross Walk Path  Connections between Microsoft Project files are isolated through the Cross Walk file to prevent accidental loops from being introduced while the horizontal connections are developed. – The inter-event margin between these program event files can be placed in the cross walk file for easy management and visibility. 8 CROSSWALK EVENT A Shared Connection Schedule Margin Receiving Milestone Send Milestone AC SA AC AC AC Inbound Outbound EVENT W – The entire critical path for the program—through all individual program event files—can be seen in the cross walk file. – Work on each program event file can take place in parallel for maximum efficiency of the planning staff.
  9. 9. Programmatic Architecture and the Cross Walk File The Problem with Distributed Planning and Controls  Individual .MPP files built by planner need to be integrated into a submittal for the IMS section of the PMB  Building the IMS is an iterative and incremental process – Gather the data one step at a time  Divide the program into segments, for example – CDR and Before – Post-CDR: Fabrication and Test – Assembly, Integration Test and Operations  Always keep the Events “in the box” at the end of every day  Keep all work to the left of the Event with a Deadline 9
  10. 10. Programmatic Architecture and the Cross Walk File Linking Program Events Vertically Across Individual IMP Files 10
  11. 11. Programmatic Architecture and the Cross Walk File Why A Crosswalk File?  By using a crosswalk file between these links, we are able to: – Stop unnecessary schedule turmoil before it propagates through entire network, » No one schedule can impact the other schedules without permission / knowledge of crosswalk file owner » No changes in one file will impact the work in other files until the Cross Walk file is updated and republished – Better management of the the triggers that keep the files in sync with each other, – Create a mechanism to manage the time (aka slack) between promised delivery dates and actual need by dates of deliverables, – Creates a mechanism for explicit margin to be added and managed between project plans 11
  12. 12. Programmatic Architecture and the Cross Walk File Discussion Topics  How are multiple IMS’s being handled today? – IPTs – Subcontractors  How is multiple change control processes being handled today?  How is the critical path managed across and between IPTs today?  How can a Cross Walk paradigm improve – Visibility to interdependencies – Manage schedule margin – Show end-to-end Critical Path – Provide visibility to Alternative Points of Incorporation 12

×