1 / 31

Using the Performance Specification Process In Hazard Elimination and Control

Using the Performance Specification Process In Hazard Elimination and Control. Pamela Wilkinson, MS Technical Director, System Safety ESOH. Agenda. Background Requirements Analysis Performance Specification Conclusion Questions. Background. Prior to 1994: Detail Specifications

marinel
Download Presentation

Using the Performance Specification Process In Hazard Elimination and Control

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. Using the Performance Specification Process In Hazard Elimination and Control Pamela Wilkinson, MS Technical Director, System Safety ESOH

  2. Agenda • Background • Requirements Analysis • Performance Specification • Conclusion • Questions

  3. Background • Prior to 1994: • Detail Specifications • Detailed the method for how something was built. • Proscriptive • 1994 – Present: • Performance Specifications • Defines the functional requirements for the product, the environment in which it must operate, and interface characteristics.  • States requirements in terms of the required results.  • Does not state the methods for achieving the required results.

  4. Performance Specification Defines the expected result Ship

  5. Hazard Mitigation • So how does this relate to mitigating hazards? • If the contractor is required to meet specified safety performance requirements, they will more carefully select equipment in the design phase that will do so.

  6. Requirements Analysis JCIDS Documents • System Safety related requirements often • vague or missing. • Requirements are rarely defined explicitly. • MIL-STD-882 is an mandatory Requirement per DODI 5000.02.

  7. Requirements Analysis Determine what existing requirements apply • JCIDS Documents • KPPs • Federal Laws (EPA) • Military Standards (MIL-STD-1472G) • Industry Standards (IEEE) • User needs/Operational Requirements

  8. Requirements Analysis • Must be done in conjunction with other discipline’s Requirements Traceability Analyses • Expect there to be Trade-offs to eliminate conflicts. • Likely will need to adjust some requirements to meet Cost, Schedule & Performance Considerations

  9. Requirements Analysis Basic Questions to Consider • Where will the system be used? • How will the system accomplish its mission objective? • What are the critical system parameters to accomplish the mission? • How are the various system components to be used? • How effective or efficient must the system be in performing its mission? • How long will the system be in use by the user? • What environments will the system be expected to operate in an effective manner?

  10. Requirements/P-Specs Requirements must be Verifiable • Allows the contractor to know what the government meant by the requirement. • Allows the government to know the contractor has achieved user requirements.

  11. Requirements/P-Specs • Requirements must then be written into Performance Specifications (P-Specs) • Remain traceable: • Design • Manufacturing • Operations

  12. Performance Specification A well written P-Spec: • Articulates user needs in terms that are: • Output oriented • Operational • Functional • Performance based • Measurable

  13. Performance Specification

  14. Performance Specification The document included requirements such as: • “be easily taken apart for transport in Army wagons and • be capable of being reassembled for operation in an hour, • carry 350 pounds for 125 miles, and • maintain 40 miles per hour in still air.”

  15. Performance Specification

  16. Performance Specification Quantitative (not Qualitative) The mandrel shall have a hardness of not less than 60 and not more than 65 on the Rockwell “C” scale. The mandrel shall be rugged. (Subjective) (Measurable)

  17. P-Spec Examples Human Systems Integration The system shall be deployable by a two-man crew. No special tools or heavy lift devices shall be required. • Temperature • The system shall operate normally in temperatures from 0 to 40 degrees C (+32 to +104 degrees F). The system shall withstand storage and transportation in temperature extremes from –30 to +50 degrees C (-22 to 122 degrees F). Exposed Edges The equipment design shall have all exposed edges and corners rounded to prevent cuts or punctures.

  18. P-Spec Examples ENVIRONMENTAL EXAMPLE: Lithium batteries in the system must be UL certified and be able to pass NOSSA requirements for shipment via Navy Vessel with no additional testing.

  19. Verification/Validation • Analysis • Demonstration • Examination • Test

  20. Verification/ Validation Verification • Ensures the system was built according to specification requirements

  21. Verification/ Validation Validation • Ensures the system operates according to those specification requirements

  22. Verification/Validation Analysis • Technical models • Charts • Circuit diagrams • Documentation

  23. Verification/Validation Demonstration • Actual Operation of the Product

  24. Verification/Validation Examination • Simple physical manipulation • Sight • Touch • Smell • Hear • Counting

  25. Verification/Validation Test Actual testing of the system or product Verified via the test report

  26. Verification P-Spec. #1 P-Spec. #2 P-Spec. #3 Verification #1 Verification #2 Verification #3

  27. Verification/Validation Events • First Article Test (FAT) • System Integration Test (SIT) • Performance Article Test (PAT) • Joint Interoperability Test (JIT) • Operational Testing (OT) • Operational Environment Event (OEE)

  28. P-Spec Examples Human Systems Integration The system shall be deployable by a two-man crew. No special tools or heavy lift devices shall be required. • Temperature • The system shall operate normally in temperatures from 0 to 40 degrees C (+32 to +104 degrees F). The system shall withstand storage and transportation in temperature extremes from –30 to +50 degrees C (-22 to 122 degrees F). • Temperature • The system shall operate normally in temperatures from 0 to 40 degrees C (+32 to +104 degrees F). The system shall withstand storage and transportation in temperature extremes from –30 to +50 degrees C (-22 to 122 degrees F). • Temperature • The system shall operate normally in temperatures from 0 to 40 degrees C (+32 to +104 degrees F). The system shall withstand storage and transportation in temperature extremes from –30 to +50 degrees C (-22 to 122 degrees F). • Temperature • The system shall operate normally in temperatures from 0 to 40 degrees C (+32 to +104 degrees F). The system shall withstand storage and transportation in temperature extremes from –30 to +50 degrees C (-22 to 122 degrees F). Exposed Edges The equipment design shall have all exposed edges and corners rounded to prevent cuts or punctures.

  29. Verification Matrix

  30. Conclusion

  31. Questions

More Related