CPS-ミッション立案スクール

Jan.09, 2016

システムズエンジニアリング 



Munetaka UENO
ueno@cps-jp.org

Center for Planetary Science (CPS)
Kobe University

CPS-ミッション立案スクール

Jan.09, 2016

Systems Engineering“The objective of systems engineering is to see to it that the system
is designed, built, and operated so that it accomplishes its purposein the most cost-effective way possible, considering
performance, cost, schedule and risk.”

NASA Systems Engineering Handbook SP6105

CPS-ミッション立案スクール

Jan.09, 2016

Systems Engineering
Systems engineering is a methodical, disciplined approach for the design, realization,technical management, operations, and retirement of a system.
A “system” is a collection of different elements that together produce results not
obtainable by the elements alone.
Elements can include people, hardware, software, facilities, policies anddocuments.
All things required to produce system level results.
Systems engineering is the art and science of developing an operable systemcapable of meeting requirements within imposed constraints.
Not dominated by the perspective of a single discipline.
The responsibility of engineers, scientists, and managers working together䎃䎃 䎃 䎃 䎃 䎃 䎃 ಽഀ䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 䎃 ⛔ว䎃CPS-ミッション立案スクール

システム開発のVチャート䎃䎃㘈ቴ䈱ᦼᓙ䊶䍤䍎䍛䍼㩷䉰䊷䊎䉴䇮ㆇ↪ႎ๔ᦠ㩷ᅷᒰᕈ⏕⹺㩷䊚䉾䉲䊢䊮ⷐ᳞ቯ⟵㩷ㆇ↪㩷ㆇ↪䉮䊮䉶䊒䊃㩷 㩷 ᅷᒰᕈ⏕⹺⸘↹ቯ⟵䈘䉏䈢䊚䉾䉲䊢䊮ⷐ᳞㩷ㆇ↪ᢥᦠ㩷ⷐ᳞ಽᨆᅷᒰᕈ⏕⹺ᅷᒰᕈ⏕⹺㩷ⷐ᳞⠪䈮䉋䉎㩷ᅷᒰᕈ⏕⹺⸘↹㩷䍚䍛䍡䍯ⷐ᳞ᦠ㩷ⷐ 㩷᳞ಽᨆ䍏䍎䍕䍡䍖䍟䍊⸳䍚䍛䍡䍯䇮⹜㛎ႎ๔ᦠ㩷㩷䍚䍛䍡䍯㩷⸳⸘䈱ᅷᒰᕈ⏕⹺䍚䍛䍡䍯⹜㛎㩷 㩷ᬌ⸽㩷䍚䍛䍡䍯઀᭽ᦠ㩿⸳⸘⚿ᨐ㪀㩷⸳⸘⠪䈮䉋䉎ᬌ⸽⸘↹㩷䍚䍛䍡䍯⹜㛎ታᣉ⸘↹ᦠ䇮ᚻ㗅䍐䍻䍡䍖䍼䍸䍎䍚䍌䍻ᅷᒰᕈ⏕⹺㩷䍙䍪䍼䍚䍛䍡䍯䇮⹜㛎ႎ๔ᦠ㩷䍙䍪䍼䍚䍛䍡䍯઀᭽ᦠ䋨ⷐ᳞✬䋩㩷ⷐ 㩷᳞ಽᨆ䍏䍎䍕䍡䍖䍟䍊⸳㩷䍙䍪䍼㩷 ⸳⸘䈱ᅷᒰᕈ䍚䍛䍡䍯㩷 ⏕⹺䍙䍪䍼䍚䍛䍡䍯⹜㛎㩷 㩷ᬌ⸽㩷⸳⸘⠪䈮䉋䉎ᬌ⸽⸘↹㩷䍙䍪䍼䍚䍛䍡䍯઀᭽ᦠ㩿⸳⸘⚿ᨐ✬㪀㩷䍙䍪䍼䍚䍛䍡䍯⹜㛎ታᣉ⸘↹ᦠ䇮㩷ᚻ㗅ᦠ㩷䍐䍻䍡䍖䍼䍸䍎䍚䍌䍻ᅷᒰᕈ⏕⹺㩷䍘䍻䍬䍽䍎䍦䍻䍢઀᭽ᦠ䋨ⷐ᳞✬䋩㩷ⷐ㩷 ᳞ಽᨆ䍏䍎䍕䍡䍖䍟䍊⸳䍘䍻䍬䍽䍎䍦䍻䍢㩷⵾ㅧ࿑㕙㩷䍘䍻䍬䍽䍎䍦䍻䍢䍂⹜㛎ႎ๔ᦠ㩷㩷⸳⸘䈱ᅷᒰᕈ⏕⹺ᬌ⸽㩷⸳⸘⠪䈮䉋䉎ᬌ⸽⸘↹㩷䍘䍻䍬䍽䍎䍦䍻䍢⹜㛎㩷 㩷䍘䍻䍬䍽䍎䍦䍻䍢⹜㛎ታᣉ⸘↹ᦠ㩷ᚻ㗅ᦠ㩷䍐䍻䍡䍖䍼䍸䍎䍚䍌䍻⵾ㅧ࿑㕙㩷䉮䊮䊘䊷䊈䊮䊃䉇䉰䊑䉲䉴䊁䊛䈱䉂䈮䈫䉌䉒䉏䈝䇮਄૏䈱䉲䉴䊁䊛䈎䉌৻⽾䈚䈢ⷞὐ䈪‛੐䉕⠨䈋䉎੐䈏ᔅⷐ䇯౏Ꮕ䊶䉝䊤䉟䊜䊮䊃䊶ା㗬ᐲ䊶㊀㊂䈱㈩ಽ╬䈮․䈮䈅䈩䈲䉁䉎䇯䉲䉴䊁䊛䊶䉰䊑䉲䉴䊁䊛䈭䈬䈱ฦ㓏ጀ䈮䈍䈇䈩ห᭽䈭䊒䊨䉶䉴䈏➅䉍㄰䈚ታᣉ䈘䉏䉎䈏䇮ᔅⷐ䈮ᔕ䈛䈩਄૏䈱㓏ጀ䈮䉅┙䈤ᚯ䉎䇯⵾૞㩷⵾ຠ㩷࿑ 䎕䎐䎔䎃 䭾䮀䮍䮧㐿⊒䬽䰢䮈䮪䯃䮏䎃

5

Jan.09, 2016䬺⵾૞䯂⺞㆐䬽▤ℂ䬷䭫䮺䮍䭷䮳䯃䭾䮮䮺䯂⹜㛎䭡䬦䬵䬓䬠䬿䬓䬓䬷䬓䬕䬢䬷䬺䬹䭚䫻䬨䬹䭞䬰䫺࿑ 䎕䎐䎕 䬺␜䬨䭗䬕䬺䫺䎶䎨 ᵴേ䬽㊀ⷐᕈ䬾ᣧᦼᲑ㓏䬺䬙䬠䭚䭾䮀䮍䮧⸳⸘䬺䬑䭚䫻䎃䎃CPS-ミッション立案スクール
Jan.09, 2016䬦䬚䬦䬹䬛䭘䫺⃻ታ䬺䬾㐿⊒䬽ਛ⋚એ㒠䬺䬙䬓䬵䭑ᄢዊ䬤䭍䬥䭍䬹ਇౕว䬛⊒↢䬨䭚䬢䬷䬾ㆱ䬠䭘䭛䬹䬓䫻䬬䬽㓙䬺䬾䫺ⷐ᳞䬽䮏䮳䯃䭼䮚䮱䮍䭪䭡⏕଻䬨䭚╬䬽 䎶䎨 䬽⠨䬗䬺ೣ䬲䬮ኻಣ䬛䮦䮊䭾䮮䮺䭼䭶䮂䮀䬺䬷
プロジェクトにおけるライフサイクル・作業量䬲䬵㊀ⷐ䬶䬑䭚䫻䎃䎃䎃ೋᦼᲑ㓏䈎䉌䭩䭭䮏䮞䮊䮏䭡ᗧ⼂䬦䬮䬄䭾䮀䮍䮧ᕁ⠨䬅䬷䬄䮱䮀䭶䬽⼂೎䬅䭡ታ〣䎃䭾䮀䮍䮧䮁䎃䭯䮺䭿䮒䭩䮱䮺䭷䊔䊷䉴䊤䉟䊮䈱⛮⛯ᕈ䉕଻䈧䈖䈫䈏㊀ⷐ
䎃 Systems
䎃 EngineeringProject䎃Management䎃䮞䮴䭿䭮䭶䮏䎃䮥䮔䭿䮨䮺䮏䎃䎃䎃䎃 SE䮞䮴䮂䮀䬺䬙䬠䭚䮞䮴䭿䭮䭶䮏䮥䮔䭿䮨䮺䮏䎃Project䎕䎑䎖 䎶䎨 䬷㑐ㅪಽ㊁䬷䬽㑐ଥ䎃
Management of the Systems Engineering Process䎃䎃Time䎃࿑ 䎕䎐䎗 䬺䮞䮴䭷䮰䮧䯂䮞䮴䭿䭮䭶䮏䭡ᡰ䬗䭚䰀ᯏ⢻䬽㑐ଥ䭡␜䬨䫻䮞䮴䭿䭮䭶䮏ో૕䬽ᵴേ䭡⛔₸䯂▤ℂ᭎ᔨᬌ⸛㧛᭎ᔨ⸳⸘㨨⸘↹᳿ቯ㨨ၮᧄ⸳⸘㨨⹦⚦⸳⸘㨨⵾૞࡮⹜㛎㨨ᛂ਄ߍ࡮ㆇ↪㨨ᑄ᫈| A䎃 䬨䭚䮞䮴䭿䭮䭶䮏䮥䮔䭿䮨䮺䮏䭡ᡰ䬗䭚 䎖 ᯏ⢻䬽䬕䬰䫺ᛛⴚ⊛䬹㕙䬶䭼䮤䯃䮏䬨䭚䬽䬛୘䫽䬽ኾ㐷ᛛⴚ䊒䊥䊐䉢䊷䉵A䋯䊒䊥䊐䉢䊷䉵A䋯 䎨䏑䏊䏌䏑䏈䏈䏕䏌䏑䏊䯵䬷䊐䉢䊷䉵A 䎶䎨 䌼䊐䉢䊷䉵B䌼䊐䉢䊷䉵C䌼䊐䉢䊷䉵D 䌼 䊐䉢䊷䉵 E| 䊐䉢䊷䉵F䯴䎧䎨䰆䎃 䎧䏌䏖䏆䏌䏓䏏䏌䏑䏈䎃䬶䬑䭙䫺቟ో䯂ା㗬ᕈ⏕଻䬽㕙䬶䭼䮤䯃䮏䬨䭚䬽䬛቟ోା㗬ᕈ଻䎃 ⸽䯴䎶䎉䎰䎤䯵䬶䬑䭚䫻䎃䎃಴ౖ䋺Advisory Commission
for Mission Success, November 10, 2004䎃䭼䮝䭾䮀䮍䮧䯂䭺䮺䮤䯃䮔䮺䮏䬽ౕ૕⊛䬹⸳⸘䯂㐿⊒䬾䬬䭛䬭䭛䬽ኾ㐷ಽ㊁䬽䭯䮺䭿䮒䭩䬺ᆔ䬼䭚䬢䬷䬺࿑ 䎕䎐䎕䎃 䮞䮴䭿䭮䭶䮏䬺䬙䬠䭚䮰䭫䮜䭼䭫䭶䮲䬷૞ᬺ㊂䬽㑐ଥ䎃䬹䭚䬽䬶䫺䎶䎨 䬽ᓎഀ䬾਄૏䭾䮀䮍䮧䬚䭘䬽ⷐ᳞ಽᨆ䫺䬬䬽⚿ᨐ䬷䬦䬵䬽⸳⸘઀᭽䬷ⷐ᳞䬽䮏䮳䯃䭼䮚䮱䮍䭪䬽⏕⹺䫺䭶䮱䮍䭪䭲䮲䬹ⷐ⚛䬽㐿⊒⸘↹䬽┙᩺䫺䭫䮺䮆䮜䭮䯃䮀⺞ᢛ䫺⒳䫽䬽䮏䮳䯃䮐䭱䮜⚿ᨐ䬽್ᢿ䫺⵾૞䯂䭫䮺䮍䭷䮳䯃䭾䮮䮺䯂⹜㛎⸘↹䬽▤ℂ䬹䬸䫺䬓䭞䬿䫺䬄὾䬜㠽䬽ਠ䬅䬽䭗䬕䬹䭑䬽䬶䬑䭚䫻䎃
CPS-ミッション立案スクール
6
Jan.09, 2016
䎃JAXAのプログラム/プロジェクトマネジメント
䉲䉴䊁䊛䉵䉣䊮䉳䊆䉝䊥䊮䉫䊒䊨䉫䊤䊛䊙䊈䉳䊜䊮䊃䉼䉢䉾䉪䋧䊋䊤䊮䉴䊚䉾䉲䊢䊮䊨䊷䊄䊙䉾䊒• SE䊒䊨䉶䉴䈱໪⫥䈫ᶐㅘⷐ᳞ಽᨆ/ᯏ⢻ಽᨆ• 䊚䉾䉲䊢䊮ᬌ⸛䊚䉾䉲䊢䊮⸳⸘⚿ᨐ• 䊒䊨䉳䉢䉪䊃ᵴേ䈱⹏ଔ• 䉲䉴䊁䊛ᛛⴚ/ᖱႎ䈱⫾Ⓧ/ᵴ↪
• ᛛⴚ䊨䊷䊄䊙䉾䊒䈱䈫䉍䉁䈫䉄• ᛛⴚၮḰ䈱૕♽ൻ• ᛛⴚ⠪⢒ᚑ䊒䊨䉫䊤䊛䈱┙᩺䊶䊒䊨䉫䊤䊛⸘↹╷ቯ/▤ℂ䊶䊚䉾䉲䊢䊮ⷐ᳞╷ቯ/▤ℂ䉼䉢䉾䉪䋧䊋䊤䊮䉴቟ోା㗬ᕈ଻⸽䋨S&MA䋩• ቟ోା㗬ᕈၮḰ䈱ᢛ஻• ቟ోା㗬ᕈክᩏ䊚䉾䉲䊢䊮ᬌ⸛䊒䊨䉳䉢䉪䊃䊙䊈䉳䊜䊮䊃• ㆡಾ䈭⸘↹䈱⸳ቯ• ⸘↹䈱⏕ታ䈭ㆀⴕ䋨 WBS䇮䉴䉬䉳䊠䊷䊦▤ℂ䇮䉮䉴䊃▤ℂ䇮䊥䉴䉪▤ℂ ╬䋩ታᣉ⁁ᴫႎ๔䉝䊄䊋䉟䉴䉲䉴䊁䊛ᛛⴚ䊨䊷䊄䊙䉾䊒૞ᬺ⚿ᨐ䋨䉲䉴䊁䊛઀᭽䊶ᬌ⸽⸘↹/⚿ᨐ╬䋩• 䉲䉴䊁䊛⸳⸘• ታⵝ䊶䉟䊮䊁䉫䊧䊷䉲䊢䊮• ⹏ଔ䊶⸃ᨆ• SE䊙䊈䉳䊜䊮䊃ᛛⴚၮḰ䈮ၮ䈨䈒ታᣉ⁁ᴫႎ๔䉝䊄䊋䉟䉴ታᣉ⁁ᴫႎ๔䉝䊄䊋䉟䉴

S&MA⁁ᴫႎ๔䉲䉴䊁䊛䉵䉣䊮䉳䊆䉝䊥䊮䉫䊒䊨䉶䉴䈮ၮ䈨䈒⚵❱ㅪ៤ੱ᧚੤ᵹኾ㐷ᛛⴚ䊨䊷䊄䊙䉾䊒

WBS䈮ၮ䈨䈒
૞ᬺᜰ␜

S&MAᣇ㊎䈮ၮ䈨䈒• ቟ో㐿⊒଻⸽૞ᬺ⁁ᴫ䊝䊆䉺• ⷐ⚛ᛛⴚ㐿⊒ᛛⴚᬌ⸛᧦ઙ
• 䉰䊑䉲䉴䊁䊛ᛛⴚ㐿⊒ឭ␜䉲䉴䊁䊛઀᭽ឭ␜ኾ㐷ᛛⴚ• ᛛⴚၮḰ䈱૞ᚑ• ኾ㐷ᛛⴚ⎇ⓥ- వ┵⎇ⓥ- ታ↪ൻ⎇ⓥ• 䊒䊨䉳䉢䉪䊃䈱⺖㗴⸃᳿• 䊒䊨䉳䉢䉪䊃䈱ኾ㐷ክᩏ䇼ಠ଀䇽䋺⁛┙⹏ଔ/ክᩏ䋺䉟䊮䊒䉾䊃䋺䉝䉡䊃䊒䉾䊃䋺䊒䊨䉳䉢䉪䊃ౝᵴേ䋺ฦㇱ㐷䈱ᵴേ࿑ 䎕䎐䎗䎃 䮞䮴䭷䮰䮧䯂䮞䮴䭿䭮䭶䮏䭡ᡰ䬗䭚䰀ᯏ⢻䬽㑐ଥ䎃ታ㓙䬽㐿⊒䬶䬾೨ㅀ䬽 䎳䎳䎳䯴╙ 䎕 ┨䫺䎕䎑䎕 ෳᾖ䯵䭡ታᣉ䬦䬵䬓䭚䬛䫺䭊䬷䭢䬸䬽 䎶䎨 䮞䮴䮂䮀䬾䬨䭈䬵䬽䮜䭮䯃䮁䬶ㆡಾ䬺ታᣉ䬤䭛䭚ᔅⷐ䬛䬑䭚䫻䬢䬽䬮䭐䫺᭎ᔨ⸳⸘䬽䭩䭭䮏䮞䮊䮏䬷䬦䬵䫺䬢䭛䭘 䎶䎨 䮞䮴䮂䮀䬽䮰䭫䮜䭼䭫䭶䮲䬺䭞䬮䭚⸘↹䭡૞䭚䬢䬷䬛ᄢಾ䬶䬑䭚䯴䬬䬽䬮䭐䬺䬾䫺ᬌ⸛䬛ᔅⷐ䯵䫻䬬䬽ᓟ䭑䫺䎶䎨 䬽
CPS-ミッション立案スクール
Jan.09, 2016ฦ䮞䮴䮂䮀䬾หᤨਗⴕ⊛䬺ㅴ᝞䬦䬵䬙䭙䫺⋧੕䬺㑐ㅪ䬦䬑䬲䬵䬓䭚䫻䮞䮴䭿䭮䭶䮏䬽䮰䭫䮜䭼䭫䭶䮲䬷ฦ䎶䎨 䮞䮴䮂䮀䬽㑐䭞䭙䬺䬳䬓䬵䬾SEプロセス 䎖䎑䎘 㗄䭡ෳᾖ䬽䬢䬷䫻䎃䎃䎃䭾䮀䮍䮧⸳⸘䯴ಽഀ䯵⵾૞䯂䭫䮺䮍䭷䮳䯃䭾䮮䮺䎃䮞䮴䮂䮀⟲䯴⛔ว䯵䮞䮴䮂䮀⟲䯂 䎃⹏ଔ䮞䮴䮂䮀⟲䎃䎧䎔䎃䎃䱺䱙䱦䱘䲇ⷐ᳞ቯ⟵䎃䎬䎖 ㆇ↪䯂଻቞䯂䎨䎔䎃䎃䎃䮏䮳䯃䮐䭱䮜䎃ᑄ᫈䎧䎕䎃䎃䍚䍛䍡䍯ⷐ᳞ಽᨆ䎃䎨䎕䎃䎃䎃䎃ᬌ⸽䯂ᅷᒰᕈ䎃⏕⹺䎬䎕 䱜䲇䱭䱢䲈䲄䱚䱦䱘䲇䎃䎧䎖䎃䎃䎃䎃䎃ᯏ⢻⸳⸘䎃䎬䎔䎃䎃䎃䎃䎃䎃⵾૞䎃䎧䎗䎃䎃䎃䎃䎃‛ℂ⸳⸘䎃䎃䎃SE䮥䮔䭿䮨䮺䮏⟲䎃䎰䎘䎃䎃䎃䭺䮺䮜䭪䭵䮬䮳䯃䎃䎰䎔䎃䎃䎃䎶䎨⸘↹▤ℂ䎰䎖䎃䮱䮀䭶䮥䮔䭿䮨䮺䮏䭾䮮䮺▤ℂ䎃䎰䎕䎃䎃䎃䎃ᛛⴚክᩏ䎃䎃䎰䎗䎃䭫䮺䮆䮜䭮䯃䮀▤ℂ䎃䎃䎃䎰䎙䎃ᛛⴚ䮎䯃䮆▤ℂ࿑ 䎖䎐䎔䎃 䎶䎨 䮞䮴䮂䮀ో૕௝䎃CPS-ミッション立案スクール

11Jan.09, 2016

Deﬁnition(ミッション定義)
1.“The art and science of developing an operable system capable of meeting mission
requirements within imposed constraints including mass, cost and schedule.”
2. Satisfy in a (near-)optimal manner all the requirements
3. Requires trade-offs involving diverse systems and disciplines
a. Propulsion, power, communications, orbital dynamics, thermal, structure,mechanisms, navigation, control, soil mechanics, aerothermodynamics,…
4. You need to identify what the important parameters are and how they are related!
5. Define and compare a small number of different possible scenarios
6. Choose most promising option and perform more detailed design, including space& ground segments, operations, cost and risk

CPS-ミッション立案スクール

Jan.09, 2016

Thoughts on the explorer to the moon
1. Achievement of science objectives generally involves coupling one or moresensing elements to physical parameters of the environment, and measuring theeffect.

a. Might be a quasi-continuous time series of one or more parameters, perhaps
down-sampled or compressed, either at one location or along the path of thevehicleb. Might be a field (gravity, magnetic) that varies in time as well as space.
c. Might be a remote measurement or in situ.
d. Might be a passive measurement (seismic monitoring) or an active one (activeseismic sounding, Ground-Penetrating Radar)e. Measurement performance may depend strongly on configuration, deployment
and minimization of unwanted effects.

CPS-ミッション立案スクール

Jan.09, 2016

Some techniques with heritage
1. Radio science, in various forms ­ Doppler tracking, VLBI, signal strength vs. time/location.
2. Laser ranging of passing reflectors on the surface, or the surface itself
3. Gravimetry, gradiometry, seismology
4. Space physicsʼ experiments ­ magnetic field, electric field, EM waves, particles,radiation.
5. Atmospheric physical properties & profiles (measured during descent, remotelyfrom the surface, from an aerial platform,…)

6. Radar sounding (from orbit, of the surface and/or sub-surface, or GPR at thesurface, or upward-looking of the ionosphere,…)7. Heat flow

CPS-ミッション立案スクール

Jan.09, 2016

Project Planning
1. Purpose and objectives of the projecta. Key questions to be answeredb. Key technical performance parametersc. Technical and programmatic constraints
2. Technology availability and development needs
a. Potential cost and schedule drivers
3. Potential cost class (~200M$, ~350M$, ~500M$, ~1B$)
4. Ability and need to re-use existing equipment/products
5. Availability and need for human resources, skills, technical facilities
6. Risk assessmenta. Risk management and mitigation actions
Development approach:a. Result from above considerations

CPS-ミッション立案スクール

Jan.09, 2016

Objectives ­ Requirements - Solutions
Objective is the high level motivation
Which scientific question/application purpose shall the project address and whatanswer is sought

Requirement is the translation of this objective into verifiable statements of what isneeded to achieve the objective
have several levels of detailare traceable, all the way back to the top level
Include quantities
Solution is the response to the all requirements
There can be several solutions meeting requirements
Non-compliance needs to be negotiatedCPS-ミッション立案スクール

Jan.09, 2016

Mission Objectives
Science objectives: Objectives should ­a. respond to important scientific questions
b. state why a space mission is neededc. be appealing
to General public
to Science communityApplication objective: Objectives should ­a. serve an important need of the general public ­ benefits!
b. state the unique contribution from space

CPS-ミッション立案スクール

Why do we need requirements?
1. To provide motivation and focus to the projecta. Communicating to others what shall be achieved
2. Requirements shallanswer the WHY?
by specifying the WHAT?
and not addressing the How?
3. To identify the trade-off for the best solution
4. Place priority on possible solutions/options
5. Priority helps resolving ­a. Conflicting requirements
b. De-scope paths
6. Provide specifications to engineering and lower level subsystems

Jan.09, 2016

CPS-ミッション立案スクール

Jan.09, 2016

Properties of Requirements
1. Mission statement: captures the objectives and measurements required in a single
sentence
2. Requirements are formal statements expressing what is needed to fulfill themission objectives
3. Requirements shall be product related, not process related
4. Clear requirements are key to good design
5. Requirements are hierarchical: lower level system requirements shall come fromhigher level mission requirements

CPS-ミッション立案スクール

Jan.09, 2016

Requirements ­ Examples
1. Good Examples:a. The mission shall provide a measurement of the x constant with an accuracy
better than 10­13

b. The mission shall allow scanning of the sky with an angular rate of 60 arcsec/saround an axis of rotation which is 50 0.1 away from the Sun direction
c. The mission shall have a nominal in-orbit duration of 4 years

2. Bad Examples:a. The system design shall maximize the spectral resolution
b. The mass shall be below 1000 kg

CPS-ミッション立案スクール

Jan.09, 2016

Trade-oﬀ
1. Trade-off allows exploring alternative solutions to a baseline

2. The parameter space needs to be prepared, and an evaluation criterion shall beestablished using requirements

3. Most common criteria: mass, cost; several system properties can be translated
into them ­a. Power consumption ? generation of more power ? solar array size ? massb. Higher telemetry volume ? larger HGA, more power for TM&C ? massc. High performance ? complex solutions ? more effort for verification ? longer
integration time ? cost

CPS-ミッション立案スクール

Jan.09, 2016

Requirements & Design Drivers
1. Identification of design drivers is result of requirement analysis
a. First iteration during definition of mission concept2. Design drivers constrain flexibility of system design ? there should be as few aspossible!
3. Classification of requirements: unavoidable ­ negotiable
4. Typical (expected) unavoidable design drivers:a. Mission profileb. Communications
c. Power generation
5. Negotiable (examples):a. Planning of telemetry downlink
b. Operations constraints

CPS-ミッション立案スクール

Jan.09, 2016

参考2䣌䣃䣚䣃儻兑儜儋儓儬兂儱儜充兗儬儻兑償儝 (ver. 1.5)Ỵᐃ⥲ྜ஦ᴗィ⏬
‽ഛ儥兠兄㛗‽ഛ儥兠兄凚兓兠儑兗儔儔兏兠儻➼僸ྵ僦凛

Approvalᐃ⩏⤊஢⥲ྜ஦ᴗィ⏬
儻兑儜儋儓儬兂儱兠儜兇儻兑儜儋儓儬儥兠兄Completion‽ഛ

Definition

ImplementationពᛮỴᐃ凚⌮஦㛗凛元儧儛克兗僔ᐃ⩏ィ⏬Ỵᐃ儹儋兠儞⤊஢僤働僔άືୖグ僑ᚲせ僐యไཬ僙㈨㔠
儻兑儜儋儓儬⥲⤒㈝僔ୖ㝈್儻兑儜儋儓儬⛣⾜ᑂᰝ儻兑儜儋儓儬‽ഛᑂᰝ 元儧儛克兗ᐃ⩏僔ጇᙜᛶ• ୰ᮇィ⏬➼僎僔ᩚྜᛶ• 元儧儛克兗僔౯್• ᶵᵓ僔㛗ᮇⓗィ⏬僔ᡂ❧ᛶ凚஦ᴗ兟ேဨ兟㈨㔠僸ྵ僦凛ึᮇせồ᮲௳僎兎儝儓➼僔ㄆ㆑僸ඹ᭷儻兑儜儋儓儬兂儱兠儜兇僔㈐௵僎ᶒ㝈僸㉸傮僱兎儝儓僑僕傎⌮஦㛗傎ᮏ㒊➼僔㛗僸ྵ僦ୖ఩僔⫋ไ僑储僱⪅傲傎僃僔㈐௵僎ᶒ㝈僑傰傪僌ᑐᛂ儻兑儜儋儓儬⛣⾜儻兑儜儋儓儬⤊஢僤働僔άືୖグ僑ᚲせ僐యไཬ僙㈨㔠

儻兑儜儋儓儬┠ᶆ僔ぢ┤傽㈨※僔㏣ຍᢞධ
儻兑儜儋儓儬僔୰Ṇ儻兑儜儋儓儬兟ḟ儹儋兠儞⛣⾜僔ጇᙜᛶ• ୰ᮇィ⏬➼僎僔ᩚྜᛶ• 元儧儛克兗僔౯್• ᶵᵓ僔㛗ᮇⓗィ⏬僔ᡂ❧ᛶ凚஦ᴗ兟ேဨ兟㈨㔠僸ྵ僦凛䝥䝻䝆䜵䜽䝖䛾ᨭ᥼ᥦ᱌䞉元儧儛克兗㐩ᡂ僑㛵僵僱㔜せ僐ၥ㢟傲Ⓨ⏕傽僅ሙྜ䝥䝻䝆䜵䜽䝖䛻ᑐ䛩䜛 ホ౯䛸䛭䛾ᑐᛂᑂᰝ➨୕⪅ホ౯儻兑儜儋儓儬㐍ᤖሗ࿌఍᪥ᖖⓗ僐ሗ࿌僑僮僱☜ㄆ凚ᢸᙜᮏ㒊㛗傎䣕䢨䣏䣃傎䣅䣇儎儹儇儝凛ᥦ᱌

MDRSRR元儧儛克兗ᐃ⩏ᑂᰝ儛儝優兄せồᑂᰝ儻兑儜儋儓儬儥兠兄僔ゎᩓᐇ⾜Preparationึᮇせồ᮲௳僎兎儝儓➼僔ㄆ㆑僸ඹ᭷ពᛮỴᐃ凚⌮஦㛗凛⥲ᣓ僎ᘬ⥅傴⤒㦂兟▱㆑僔᭷ᙧ໬䣕䣃䣅஦๓ホ౯➼䣕䣃䣅஦๓ホ౯➼元儧儛克兗僸ᥦ᱌傿僱⪅(SACは宇宙政策委員会に読み替え)

z元儧儛克兗僸㐩ᡂ傿僱ᡭẁ僎傽僌タᐃz≉ᐃ僔㈨※僎᫬㛫僔僨僎᫬㝈ⓗ⤌⧊僑僮僰ᐇ᪋儻兑儜儋儓儬儥兠兄僸ྵ僧僅ᶵᵓ元儧儛克兗僑㛵僵僱傿僟僌僔⤌⧊ཬ僙ᙺ⫋ဨ僕傎ᙜヱ元儧儛克兗僔㐩ᡂ僑ྥ傷ດຊ傽僐傷僲僖僐僯僐傪傏

BDB-07005 NC

SDR䣒䣆䣔

儛儝優兄ᐃ⩏ᑂᰝ

予備設計

䣅䣆䣔

㛤Ⓨ᏶஢ᑂᰝ 兟兟兟兟兟兟 兟兟兟ᴫᛕ᳨ウᴫᛕタィィ⏬Ỵᐃ

ᇶᮏタィヲ⣽タィ〇స兟ヨ㦂㐠⏝Concept Studies

Concept Development

Project Formulation

Preliminary Design

Final Design

Production & Testing

Operations僃僔௚僔せồ兟ไ⣙儙儓償儝儓免儈優兎儆元儧儛克兗せồ᭩凚᱌凛ᴫᛕ᳨ウ儛儝優兄僔ᐇ⌧ྍ⬟ᛶ⥲⤒㈝እ㒊ᶵ㛵僎僔ᙺ๭ศᢸୖ఩僔⫋ไ僑储僱⪅⤌⧊ཬ僙ィ⏬傱僯僔せồ兎儝儓㆑ู僎ᑐᛂ㈨㔠兟⤌⧊儝儗兠儻ෆ儝儗兠儻እ㛤Ⓨ兟〇㐀௻ᴗ僔㑅ᐃᡭ⥆傳

儛儝優兄僔ศᯒ兟ᐃ⩏
儛儝優兄せồ᭩凚᱌凛儻兑儜儋儓儬兂儱兠儜兇z 儥兠兄僔ᴗົ僸⤫ᣓ傿僱㈐௵僎ᶒ㝈z 兎儝儓僔పῶ僑ດ僧僊僊傎᭱㐺僎⪃傮僱ᡭἲ僎▱㆑僸僨僉僌儻兑儜儋儓儬僸㐙⾜

儛儝優兄௙ᵝ᭩凚᱌凛儝儗兠儻ᴫᛕタィ儛儝優兄僔ᐇ⌧ྍ⬟ᛶ儻兑儜儋儓儬㛵ಀ⪅僎僔ㄪᩚ儻兑儜儋儓儬඲య僔兂儱儜充兗儬凚兎儝儓僞僔ᑐᛂ傎儥兠兄僔㐙⾜⬟ຊྥୖ➼凛㛤Ⓨ兟㐠⏝僔ᐇ᪋せồ஦㡯僑㛵傿僱兂儱儜充兗儬凚せồ傱僯僔୍㈏ᛶ兟㐺ྜᛶ僔☜ㄆ 䲑 ゎỴ⟇刍儽兠儝免儈兗僔ぢ┤傽僸ྵ僦刏凛儻兑儜儋儓儬ィ⏬僔❧᱌ᢏ⾡兂儱儜充兗儬ィ⏬

儻兑儜儋儓儬ィ⏬᭩凚᱌凛凚ᑂᰝィ⏬僸ྵ僦凛• 儻兑儜儋儓儬僔㐩ᡂ┠ᶆ• 儝儗兠儻ᐃ⩏• 元儧儛克兗儙儓償儝儓免儈優兎儆• 㛤Ⓨ᪉㔪• యไ⾲䢪᱌䢫• WBS䜢ྵ䜐άືෆᐜ• 免儈儹儙儈儓兏儗儝儬ぢ✚僨僰• 兎儝儓僔ศᯒ兟ᑐᛂ⟇• ๓ᥦ᮲௳兟ไ⣙᮲௳• 㛵㐃ィ⏬
➼儝儕儜光兠兏㈨※傜ὀグ傝凬儽兠儝免儈兗໬** MASA.Okada **11CPS-ミッション立案スクール

Jan.09, 2016

Mission Phases ­ Phases 0 & A
1. Phase 0 ­ Analysis/needs identification
a. Understanding of functional and technical requirements (correct requirements
formulation and priorities), mission statementb. Preliminary technical requirement specifications
c. Conduct trade-off studies to select preferred system conceptd. Definition of mission concept (design, profile, configuration)e. Preliminary assessment of programmatic aspects
f. Preliminary risk assessment
2. Phase A ­ Feasibility
a. Elaborate possible system and operations concepts and propose technical solutions
b. Initiate pre-development of critical technologies
c. Conduct trade-off studies to select preferred system concept
d. Assess the technical and programmatic feasibility of the possible concepts byidentifying constraints relating to implementation, costs, schedules, organization,operations, maintenance, production and disposale. Determine uncertainty levels update risk assessment

CPS-ミッション立案スクール

Jan.09, 2016

Mission Phases ­ Phase B
1. Phase B ­ Preliminary Definitiona. Confirm technical solution for the system and operations concept and establish
preliminary design

b. Preliminary organizational breakdown structure
c. Establish baseline master schedule and costd. Identify and define external interfacese. Finalize product tree and establish subsystem requirements and preliminary
subsystem design

f. Initiate long lead item procurement
g. Update risk assessment

CPS-ミッション立案スクール

Jan.09, 2016

Mission Phases ­ Phase C
1. Phase C ­ Detailed Definition
a. Detailed system and subsystem design
b. Performance simulations
c. Mathematical models (thermal, power, structural; observation, comm., etc)
d. Initiate production and qualification of engineering and qualification models
e. Detailed definition of internal and external interfaces
f. Update of risk assessment

CPS-ミッション立案スクール

Jan.09, 2016

Mission Phases ­ Phase D
1. Phase D ­ Production & Qualificationa. Completion of qualification testing & verifications (thermal-vac, vibration, EMC,etc)

b. Manufacturing, integration and test of flight hardwarec. Verification of operations with ground segment
2. Phase E ­ Utilizationa. Launch preparations and launchb. in-flight verification (commissioning)c. Mission operations planningd. Science operations planninge. Data analysis/exploitation
3. Phase F ­ Disposala. Mission disposal (space debris mitigation)b. Data archiving and final documentation

CPS-ミッション立案スクール

Jan.09, 2016Margins ­ Contingencies
1. Equipment level margins according to maturity
a. 5% for off-the-shelf items (no changes)
b. 10% for off-the-shelf items with minor modifications
c. 20% for new designs, new developments, major modifications
2. System margin (at least 20%)a. On top of and in addition to equipment margins; applied after summing best
estimates + marginb. Two options for the propellant calculation +10% margin + 2% residuals­ Margin on total dry mass and margin on launcher: typically used during early
study phases +10% margin­ Margin on maximum separated mass: typically used later, when mission analysis
and launcher analysis become available
3. Always keep lots of margins
4.“Margin philosophy for Science Assessment Studies” (See appendix)