e.g. view how many users a Participant Regulator or a Reporting Entity have set up in order to cap them off System if a defined limit is reached. 1.2.7 Provide Internal Users with the ability to Manage their security credentials. e.g. change password. 2 1.3 Manage participant regulators users 1.3.1 Provide NSSMC, as the hub operator, with the ability to create and manage user accounts with roles, permissions and access rights for designated users at the Participant Regulators. Note: NSSMC is Participant Regulator as well. For NSSMC users, the FRS is the backbone of its internal systems. For other Participant Regulators users, the FRS is only its “single window collection application”. Yes 3 1.3.2 Provide NSSMC with the ability to re-assign Participant Regulators user roles, subject to business rules. 2 1.3.3 The System will manage user authentication based on secure Identity Access Management procedures adopted by the NSSMC (based on digital certificates, to be defined based on nationally adopted standards). Yes 3 1.3.4 Provide Participant Regulators Users with the ability to Manage their security credentials. e.g. change password. 2 1.4 Manage reporting entities users 1.4.1 Provide the NSSMC with the ability to create and manage external user accounts for designated users at the reporting entities with roles, permissions and access rights. Provide Internal Users with the ability to Maintain a Reporting Entity’s key main contact details Provide Reporting Entities Users with the ability to Maintain the rest of their contact details Yes 3 1.4.2 Provide the NSSMC with the ability to re-assign external user roles, subject to business rules. 2
or checks which have sector/peer group specific variables 2.4.4 Provide the NSSMC with the ability to individually switch on and off plausibility rules., for all or specific Reporting Entities, or all rules for all or specific Reporting Entities 2 2.4.5 Provide the with the ability to define which plausibility rules should be triggered automatically and which manually. 2 2.4.6 Provide the NSSMC with the ability to manually or automatically run plausibility checks against submitted data. 2 2.4.7 Provide Internal Users and relevant Participant Regulators with the ability to view the Plausibility Outcome e.g. red, green outcome 2 2.4.8 Provide the NSSMC with the ability to define and configure alerts and notifications based on the result of applying the plausibility rules. 1 2.5 Validation of instance documents 2.5.1 Provide the NSSMC with the ability to define and configure different standardized procedures for validating instance documents, based on the profile of the reporting entity and the type of reporting requirement. Yes 3 2.5.2 The NSSMC will be able to configure internally defined validation rules. 2 2.5.3 In addition, the NSSMC will be able to version control all validation rules, with the ability to select which rules to apply. e.g. to switch individual validation rules on and off at a rule level, on a per Reporting Entity basis. i.e. specific rules, for specific Reporting Entities 2 2.5.4 The NSSMC will be able to test changes to validation prior to applying them in live. 1 2.5.5 The System shall automatically be able to determine which Validation Rules should apply to a Resubmission of data. 2
8.8 Website resolution 8.8.1 The web user interfaces must support a minimum resolution of 1024 x 768 2 8.8.2 Other screen resolutions supported 2 8.9 Web standards 8.9.1 The System must use XHTML 1.1 or HTML 5. The System must use CSS2.1 or CSS3. 2 8.9.2 The System must pass W3C and CSS validation checks. 2 8.10 Mobile device compatibility The external and internal facing systems should support mobile devices such as tablets. 2 9. Usage 9.1 Reporting Entities Population The System must be able to support a population of up to 30,000 Reporting Entities. 2 9.2 Monitoring The System must provide management information on system statistics, usage trends and data peaks 2 9.3 User Population – External The System must support a user population of at 50,000 users from Reporting Entities The System must support a user population of at least 500 users from Participant Regulators 2 9.4 User Population Growth – External The System must support increasing numbers of external users as other Reporting Entities and users are added over time. 2 9.5 User Population Peak Usage – External The System must maintain good performance, reliability and resilience at points of peak usage, coinciding with the deadlines to submit various returns. 2 9.6 User Population – Internal The System must support a user population of approximately 50 internal 2 9.7 User Population – Peak Usage Internal 2