10.07.2015 Views

MAP-01-011 HFI Technical Guide - Human Factors Integration ...

MAP-01-011 HFI Technical Guide - Human Factors Integration ...

MAP-01-011 HFI Technical Guide - Human Factors Integration ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>MAP</strong>-<strong>01</strong>-<strong>01</strong>1 – <strong>HFI</strong> <strong>Technical</strong> <strong>Guide</strong> (STGP 11)15.1.2 Stakeholders<strong>HFI</strong> <strong>Technical</strong> IssuesA list of potential stakeholders for this area is given below. This list is notexhaustive and should be seen to be a guide only. <strong>HFI</strong> Foci should refine this listbased upon the structure of their project, the attendees at the relevant HFSG orHFWG and in light of guidance and requests from industry, DEC and Customer 2representatives.• DEC• IPT <strong>HFI</strong> Foci• IPT RequirementManager (RqM)• MLS CG• TES-SSG-CSHF• TES-SSG-CSNav• TES-SSG-ShipDes15.1.3 Operability of Combat SystemsIn order to develop a highly operable Combat System user-equipment interface itis necessary to base the design on the needs of users when performing missioncritical tasks. To achieve this the following information must be derived:• Identify each member of the Combat Team and define his station (whichmay change from watch to watch e.g. Officer of the Watch), his post withinthe complement (e.g. Navigating Officer), his rank or rate and the specificrole held in mission scenarios (e.g. Weapons Director).• Define the operational scenarios that will most stretch the capability of manand machine.• Determine the way in which someone performing a specific role can bestperform his tasks whilst making use of the user-equipment interface.The following design issues apply to the development of the user-equipmentinterface:• Users should be presented with a common working environment defined ina <strong>Human</strong> <strong>Factors</strong> Style <strong>Guide</strong> (see Annex 3). For a Combat System thiswill require the use of consistent display features and symbology andstandard control devices and actions. This will help to ensure a highdegree of interoperability across the Combat System.• An alarms and warnings policy must be defined within the context of thewhole vessel (Chap 17).• Operation of systems must be resistant to malevolent operation. This isparticularly true of Combat Systems because of the sensitivity ofinformation and the restrictions necessarily placed on access to weaponfiringor emission controls.• Modern sensors are increasing the flow of contact information into theCombat System. In order to cope with this increase the Combat Systemmust take over a significant part of the user’s workload through the use ofautomated detection and tracking of contacts.Nov 2006 Page 15-4 Issue 4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!