Jamie Frankel’s Work SummaryBall Aersopace Engineering Aide I Jamie Frankel SME: Natalie Gustafson Engineer II
Agenda Smaller Projects: 1) Historical MA Info Capture2) MMOD Tool3) Conference Tracking4) Project5) AREL Project6) Ground Command and Control7) Compliance Tracking Larger Projects: • BCP Tool • DOORS MA Standards Library • Natalie Gustafson
Historical MA Info Capture (Finished 12/10/18) • Collected and converged historical MA information from many of the MAMs to support Joseph Hangge’s historical costing project. Figure 1: Example portion of Historical MA Information spreadsheet. Ball Aerospace Proprietary Information
MMOD Tool (Finished Dec 2018) Figure 2: CAD model defining coordinate system and rendering defining velocity vector. • Worked with Michelle Voelker to determine risk assessment of different sized meteoroids striking different components on Weather satellite • Consulted on her MATLAB Code. • Validation by JPL and NASA-Goddard. • Performed computations and analysis to determine normal vector components for each exposed hardware component. • Dependent on geometry of component and orientation on WSF-M.
MMOD Tool Continued Figure 3: Spreadsheet capturing calculations. Figure 4: Documentation used to define and determine normal vectors for each face.
Conference Tracking Project (Finished 1/28/2019) • Updated the 2019 MA and Security calendar spreadsheet to reflect the conferences that personnel planned to attend in the future. • Single reference source for relevant industry events. • Supports strategic scheduling of conferences and travel for SMA. • Implemented “data friendly” practices by adding continuity in data entry methods. • Conference spreadsheet now owned by Barbara.
Example: Portion of Spreadsheet Ball Aerospace Proprietary Information
AREL Project (Finished 1/24/2019) • Cross-referenced the 2544839 PMP document against the requirements listed in AREL for BATC STD 23 and TOR-2006(8583)-5236. • Captured missing requirements in both the spreadsheet and Word document. • The agile PMP document’s requirements most closely resembled the TOR and was dissimilar in almost all cases from the STD 23 requirements. • Project was handed over to SME Jeff Blanchard.
AREL Project Continued • Green -Correct (standards matched exactly) • Yellow - Standard existed but were/was different • Red - Standard did not exist Figure 5: Section of AREL spreadsheet showing differences between documents.
Ground Command and Control (Finished 3/5/2019) Figure 6: Title page of resultant document. Reviewed previous work done for Ground C2. Amalgamated Dave’s Kepler Mission Operations Assurance document and Aerospace Corp.’s Mission Assurance Practices for Satellite Operations document. Dave and Brian later created Mission Assurance Role in Mission Operations document.
Compliance Tracking Document (Finished 4/15/2019) Cross-referenced every requirement flowed down from Prime Contractor with the PMP document and with the respective MAPon Ball startup program Captured all missing and reworded requirements in both the spreadsheet and PMP document.
Compliance Tracking Continued Figure 7: Annotated PMP document. Figure 8: Spreadsheet detailing the location of each requirement and its status.
BCP Tool Intro to On Orbit Reliability Tool Outputs Command Window Figure 2 Figure 1 More Modularity Results Comparison DOORS MA Standards Library Overview Import Procedure DOORS Basics Tables and Pictures Training In depth Agenda
Intro to On Orbit Reliability Tool (MATLAB) • User runs script and choses date to run. • For following slides 4/19/2019 was chosen. • User decides what data to filter. Figure 9: Pop-up menu for date. Figure 10: Pop-up menu for data sorting.
Intro to OOR Tool Continued Figure 11: Prompts in command window. Ball Aerospce Proprietary Information • User types the probability (as a decimal) and the year they are interested in viewing into the command window. • For Mean Time to Failure the user should enter “.5” and “20” years (as shown) as this will have the program look at when (within the entire timespan) the groups are predicted to have 50% chance of survival
Outputs Part 1/3: Command Window • The command window will output the specifics of each group (as chosen by the user via the spreadsheet). • Inputs are .5 and 20 for this output. • The programs in each group are displayed as well as how many items are in each group. • If desired, the values for and and the respective confidence levels of each group can also be output.
Outputs Part 2/3: Figure 2 • The user will see Figure 2 which includes 4 subplots: • Weibull Probability Plot • PDF • ECDF (w/ & w/o censoring) • Weibull Plot (w/ & w/o censoring) Note: if Figure 2 does not appear, drag Figure 1 to the side
Outputs Part 3/3: Figure 1 • Figure 1 shows the Weibull Plot without any censoring. • Shows a reference line at the probability of interest. • Shows a reference line at the time of interest. • Outputs the probability at desired time of each group in the read out.
Example of Figure 1 Time of interest reference line (in this case 20 years). Probability of interest reference line.
Figure 1: More Modularity • Once the script has been run, the user has the option to click the space bar (while in Figure 1) which creates a movable cursor. • Once the cursor has been placed: • The title updates to the location selected. • The read-out in the figure updates. • The command window outputs all of the new desired data.
Example of Resetting Cursor Movable cursor to select new probability and time of interest. Old crosshairs. Figure 13: Example screen after space bar clicked, before cursor has been placed. Figure 14: Example screen after cursor has been placed. Notice updated title and read-out. Figure 15: Example command window after cursor has been placed.
Comparison • With this particular grouping of data we can see that the Mean Time to Failure has changed. • Due to certain busses becoming decommissionedafter the original run date. • Note: Mean Time to Failure has actually increased! Figure 17: Specific data used for comparison. Figure 16: Comparison of Mean Time to Failure
Results of On Orbit Reliability Tool • Can now analyze data with more flexibility (therefore more accuracy) in terms of: • Grouping • Date • Type • Probability of interest • Date of interest
DOORS MA Standards Library • Goal: avoid redundancy and wasted time/effort/money in project proposals … • Create a place where all of the requirements Ball typically adheres to are easily accessible to teams and programs. • Have context of entire document. • Create easy method to strip documents down to shall statements. • Have documents easily highlight requirements that significantly drive cost and schedule and why. • Highlight what methods (SOW, WI, CDRL…etc.) Ball uses to show compliance with each requirement. • Track changes (tailoring) between programs and program types. • Show requirement allocation.
Import Procedure Import information found on Alphabetical Major Links: DOORS • Locate PDF file and open using Microsoft word. • Save the file as a .doc (Word 97-2003 Document). • Deleted the first few sections (table of contents, list of tables, and cover page). • Search for continued tables and merge them to have table in its entirety. • Under Developer/Visual Basic run the following macros: • RemoveHeadAndFoot.vba (will remove the headers and footers) • Can do this without the macro (see document left). • Pic_To_OLEFig.vba (converts pictures to OLE if possible) • Alerts on errors and possible problem figures. • Reports counts of figures before and after. • Tables_To_OLE.vba (converts tables to OLE) • Alerts on tables longer than one page. • Reports on counts of figures and tables before and after. • Add all of the necessary headings and subheadings (opening docs in Word instead of converting them should automatically catch most headings and subheadings). • Remove all of the section breaks, column breaks, manual line breaks, and extra paragraph spacing. • Ensure everything is either body text or headings 1-9. • Ensure each heading has no space before or after it. • Remove all space between table captions and table and remove all space between figure captions and figure (so it will import to DOORS as one attribute). • Insert bullet points in the necessary places to match the original doc. • Save as .RTF and import in DOORS • Ensure that everything came through correctly. • Fix any imperfections. Figure 18: Where to find document on DOORS SharePoint. *With the macros1, this process is much more efficient than it used to be; that being said it is still time consuming to have to repeat this process for each document. 1) Macros developed by Colin Stewart
DOORS Basics 1/3 Figure 19: Location of MA STD Library and my work. • The DOORS Library with the work I have created can be found under “MA STD Library” • “Jamie Frankel 11/2018-5/2019” • “TRAINING CLICK HERE”
DOORS Basics 2/3 Figure 20: Example of expandable sidebar navigation. • Importing and using DOORS allows for easy navigation of large documents with expandable sidebar navigation.
DOORS Basics 3/3 Figure 21: Cover page of template document. • The template headings are pictured above. • Details can be found in “MAM DOORS Template Defined” owned by Ball.
Tables and Pictures • Tables and pictures are visible in both DOORS Web Access (DWA) and the DOORS Client. • In the client, one can double click on a figure or table and it will be automatically opened in MS Word (as long as it was uploaded as an OLE Object).
Training • Natalie Gustafson offers monthly Introduction to DOORS training (accessible on Training Enrollment Dashboard). • Will teach extra sessions specifically to teams/projects if requested. • Can teach for this endeavor specifically as well. • I created two specific training modules for the MA effort (DWA and Client) which take users through all of the actions they would need to use the modules. • They can use these as reference at any time in case they don’t know/remember how to use the module.