• Predictive Analytics for Improved Cost Management  



Blog



It is not evident how WBS 10.0 which is not just integration of all systems together but also the integration with launch vehicle as well as other related launch operations is calculated without knowing the complexities of the mission.  Also, environmental I&T associated with observatory integration is in WBS 10.0. WBS 10 covers all S/C and System-level I&T that is not specific to an individual instrument or S/C subsystem. It includes Assembly & Integration, System Test, and Ground Support Equipment. Costs for the prototype/EM hardware used in flight system testbeds are covered within each applicable component estimate (represented by the ...
Why is there no assembly level object at the s/c top level.  All the subsystems within the s/c bus need to be assembled because all the s/c bus subsystems are very much intertwined together. So there has to be an assembly object at the top of the bus? Assembly I&T is performed by the Space Subsystem object.  Adding an additional Assembly object at the top of multiple subsystem-assembly pairings produces very high redundant costs.  However, the estimator can certainly perform organizational calibration and use worksheet set multipliers to adjust outputs at this top level if an overall assembly is added. ...
What about software? I never heard it mentioned. How does the space catalog address software? Actually, we did discuss software briefly.  Since flight software is included with each electronic item, some portion of an independently estimated software cost should be removed from the result.  The separate TruePlanning for Software catalog can be used to estimate development and COTS new/modified/reused/deleted code, sized via multiple approaches:  SLOC, function point, use cases as well as via a Functional Sizing calculator. To watch the "Best Practices using the TruePlanning Space Missions" Webinar, click here.
What kinds of software costs would you say are not included in the calibrated cost to the particular space component? Flight software costs are included with each electronic component.  Ground software costs are included with MOS.  Ground data handling costs beyond the typical level used by most robotic space missions may not be adequately covered with the MOS factors. To watch the "Best Practices using the TruePlanning Space Missions" Webinar, click here.
Some space components had an asterisk (modeled outside of PRICE TruePlanning)?  What does that mean? There are some components that are not found on the Component Type drop down but rather are modeled with CERs outside of True H (Space Parachute for example).  These CERs are available via custom cost objects, per below, rather than the Space Component cost object. To watch the "Best Practices using the TruePlanning Space Missions" Webinar, click here.
Is there an EM and prototype calculator, or do you treat every type or prototoype (breadboard, brassboard, mass model, etc) as a full prototype? Fractional prototype quantities are acceptable.  Regarding a calculator-- good idea.  We will investigate feasibility. To watch the "Best Practices using the TruePlanning Space Missions" Webinar, click here.
Can you mix catalog objects from different catalogs into the same assembly? (ex. a microcircuit with a space component) The Space Catalog was designed to use only the components in that Catalog and some activities are different to other Catalogs.  When using a Space System cost object, a Space Sub-assembly and a Space Assembly, do not mix regular System, Assembly and Hardware Cost Objects in the same Space System.  If Regular System, Assembly and Hardware items are included as component of a Space System, the results will be different to using only Space Catalog components.  A Project may contain separate Space ...
On one of your slides you mention using Assembly at the subsystem level for HW to HW integration (I can see this for Payloads as those are usually stand alone),  however, for spacecrafts a lot of subsystems aren't integrated as a stand alone, are you overstating possible costs by doing at each subsystem vs. a spacecraft level assembly which would encompass the integration of all the subsystems at the spacecraft level? A bus (or payload) can have just one subsystem-assembly pairing, with all components listed below, rather than multiple subsystems (or instruments) each with multiple separate pairings.  In general, note that the ...
You mentioned using production qty vs. prototype, even with the Space Mission Objects, however typically Spacecrafts are very low qty and my experience from heavy PRICE H use is that the production qty uses a much steeper slope. Is it now more realistic with the industry data in the space objects that production qty is good to use now? Yes, that is our recommendation.  We have seen production first units higher in cost than prototypes.  We recommend using the latter for engineering models and test units. To watch the "Best Practices using the TruePlanning Space Missions" Webinar, click here.
Do you have capability to do CONOPS which drive the design? Good idea!  As demonstrated, we allow the user to model complexity (or any other input) as a function of requirements, specifications, etc which could include a CONOPS value as well.  Also, another companion application is our linkage to the design-trade tools ModelCenter and i-Sight. To watch the "Best Practices using the TruePlanning Space Missions" Webinar, click here.