1 / 13

HFS 500 8 Nov 2012

HFS 500 8 Nov 2012. The Plan. 3:45 ~ 4:45 Discuss: HTCO, HSI Teams: ID 2 HSI requirements & 2 human costs of ownership Break 5:00 ~5:40 Concept of Operations for Project FAA Safety Risk Management Time permitting: Vicente & Rasmussen’s EID Break

marek
Download Presentation

HFS 500 8 Nov 2012

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. HFS 5008 Nov 2012

  2. The Plan 3:45 ~ 4:45 Discuss: HTCO, HSI Teams: ID 2 HSI requirements & 2 human costs of ownership Break 5:00 ~5:40 Concept of Operations for Project FAA Safety Risk Management Time permitting: Vicente & Rasmussen’s EID Break 5:45-6:45 Competition Project Team Meetings

  3. Discussion: HTCO, HSI Do these concepts… • Support the goal of ‘systems thinking’? • Handle complexity? • Handle change? • Enable the development of systems that are useful, usable, and understandable? • Support proactivity? the early detection and avoidance of negative trends? • Have other benefits?

  4. http://www.hfetag.com/subtags/briefs/docs-64/HFEHSI_Shattuck_64.pdfhttp://www.hfetag.com/subtags/briefs/docs-64/HFEHSI_Shattuck_64.pdf

  5. Discussion: HTCO, HSI Do these concepts… • Support the goal of ‘systems thinking’? • Handle complexity? • Handle change? • Enable the development of systems that are useful, usable, and understandable? • Support proactivity? the early detection and avoidance of negative trends? • Have other benefits?

  6. Concept of Operations An example of an OV-1, a DoDAF view that compliments the concept of operations. publib.boulder.ibm.com/infocenter/rsysarch/v11/index.jsp?topic=/com.ibm.sa.abm.doc/topics/c_OV1_High_Level_Over_ABM.html

  7. Concept of Operations (ConOps) • Written for the customer and users • Can help team gain common ground • High level description • Describes use of and interaction with the system • Justifies the system concept; explains the benefits • Scenario(s) describing the system’s use • For competition project, scenarios are broken out from ConOps

  8. ConOps The Formal View The Informal View Written to give the customer an overview of the system concept Includes justification re. user benefits and user experience • AKA the “Operational Concept Document” • Based on inputs from wide range of stakeholders • Defines & explains critical top-level objectives/user needs (quant’ly or qual’ly) • Includes a block diagram of the top-level functions • Identifies user roles, responsibilities, & skills • See INCOSE SE Handbook

  9. FAA’s SMS & SRM Safety Management System (SMS): • Safety Policy • Safety Promotion • Safety and Risk Management (SRM) • Safety Assurance Organizational Safety Culture Be sure to use the documents identified in the competition guide for your team’s SRM!

  10. FAA’s SRM Develop an Error-Tolerant System: • Multiple defenses • Mechanisms for: • detecting a developing problem • recognizing problems • accessing & controlling resources to resolve problem • system recovery; ensure a recovery path

  11. FAA’s SRM • What matters most is that the risks get identified • Not whether or not they get quantified

More Related