• DocumentCode
    2722511
  • Title

    Operational requirements for security measures

  • Author

    Spaight, W.H.T.

  • Author_Institution
    London, UK
  • fYear
    2000
  • fDate
    2000
  • Firstpage
    64
  • Lastpage
    70
  • Abstract
    Many physical and procedural security measures have not met users´ needs because the implications of what is required have not been fully thought through. An operational requirement is a statement of needs based upon a thorough and systematic assessment of the problems to be solved and the hoped for outcomes. It should provide the link between a high level need and the system procurement process. It is easy to consider in principle but hard to develop in practice. The paper explains the development of an operational requirement and gives examples of where it has and has not been used. Examples include the procurement of equipment and the procedures and numbers needed for a guarding regime
  • Keywords
    access control; management; security; equipment procurement; guarding regime; high level need; needs statement; operational requirements; security measures; system procurement process; systematic assessment; user needs; Force measurement; Government; Guidelines; Hardware; Process design; Procurement; Research and development; Research and development management; Security; Testing;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Security Technology, 2000. Proceedings. IEEE 34th Annual 2000 International Carnahan Conference on
  • Conference_Location
    Ottawa, Ont.
  • Print_ISBN
    0-7803-5965-8
  • Type

    conf

  • DOI
    10.1109/CCST.2000.891169
  • Filename
    891169