We use cookies to provide social media features and to analyse our traffic. See more about our use of cookies.

Institute for Apprenticeships and Technical Education logo

Digital and technology solutions professional

This is not the latest approved version of this apprenticeship. View the latest version

This apprenticeship is in revision

Key information

  1. Status: In development
  2. Ticked Proposal approved
    Ticked Occupational standard approved
    Ticked End-point assessment plan approved
  3. Reference: ST0119
  4. Level: 6
  5. Degree: integrated degree
  6. Typical duration to gateway: 48 months
  7. Typical EPA period: 3 months
  8. Route: Digital
  9. Date updated: 23/01/2023
  10. Lars code: 25
  11. EQA provider: Office for Students
  12. Review:

    This apprenticeship standard will be reviewed after three years

This apprenticeship has options. This document is currently showing the following option:

Hide contents

Contents

Print occupational standard

Details of the occupational standard

Occupation summary

This occupation is found in organisations where digital technologies can be used to solve problems that exist across a range of functions. Whether looking for ways to reduce waste, increase productivity, ensure resilient and responsive customer service, or create a secure transactional environment, organisations turn to digital and technological solutions to achieve these aims. Wherever these activities take place Digital and Technology Solutions Professionals (DTSPs) are influencing outcomes and making things happen.

DTSPs are found in small, medium and large organisations across all industries such as banking and finance, digital and technology, communications, construction, education, utilities, engineering, law, manufacturing, health, government and public services pharmaceutical, retail and transport.

The broad purpose of the occupation is to evaluate, initiate, create and support business solutions using digital technology. DTSPs use data to evaluate the commercial and security risks and benefits of potential digital and technology solutions before making recommendations for strategies that may have far reaching consequences.

DTSPs are influencers in their organisations with a clear focus on delivering business improvements through digital and technological solutions. They have a passion for digital technology; keeping in touch with emerging trends and developments .

DTSPs have a broad set of skills and knowledge across the main areas of the digital and technology landscape. This enables them to understand the complexity of information systems, systems development, data, cyber security, business organisation, IT project management and computer and network infrastructures . They view all of this with a rigorous approach to commerciality and budget to deliver quality solutions.

In addition to this broad set of skills and knowledge they specialise in one of the following areas:

  • Option 1: Software engineer
  • Option 2: IT consultant
  • Option 3: Business analyst
  • Option 4: Cyber security analyst
  • Option 5: Data analyst
  • Option 6: Network engineer

For example:

  •  In a manufacturing company DTSP Software Engineers could be developing solutions to support the construction of physical products.
  • In a utility company DTSP IT Consultants could be on a remote site to implement a solution for improving energy usage or reducing outages through the application of new technologies.
  • In an engineering company DTSP Business Analysts could be reviewing a change to an engineering process to determine the impact on other processes within the organisation.
  • in a technology company DTSP Cyber Security Analysts could be working with clients to address security management issues in the clients’ processes.
  • In a pharmaceutical company DTSP Data Analysts could be working with large amounts of information to interpret the results of a field trial of a new medicine.

In a communications company DTSP Network Engineers could be involved in developing additions to an existing national network.

In their daily work DTSPs are excellent communicators and may interact with internal and external customers, team members and senior leaders. They can work independently and within multi-disciplinary teams . They may interact with decision-makers, strategists, and policymakers, often in senior roles in private or public sector organisations as well as with individuals and groups (internal and external) with a stake in the defined system, currently or in the future.

An employee in this occupation is likely to have some responsibility for budgets and/or resources, teams, and projects. In some organisations they may hold leadership positions. Work may typically be conducted in a desk-based environment, but that desk may be in an office or on a site depending on the solution being worked upon.

For example. a DTSP Software Engineer could be working on a client’s site during the development and implementation of a new client system.

An employee in this occupation will be responsible for working with little or no supervision and may be accountable for the supervision of others if the position requires it.

DTSPs are at the heart of problem solving, bringing an innovative, multi-disciplined approach to bear where there are unpredictable and variable influencing factors. They may have a remit to commission work from others and hold them accountable for outputs of a technical nature. Their professional position within a business means they fulfil a leadership role within their technical specialism demonstrating a strong ethical awareness of technological trends.

A description of each specialism follows:

Option 1) Software engineer
The primary role of the Software Engineer is to undertake all requirements during the solution development life-cycle from gathering requirements to analysis, design, code, build, test, implementation and support. They may also be required to supervise the work of junior software developers and others who may be working on elements of the solution and work with product managers and UX designers in implementing solutions. They will apply software engineering principles to all stages of the solution life-cycle, from gathering requirements, undertaking analysis and design, development of code and data requirements whilst also ensuring security feature are addressed. As well as creating new code, they can support existing code by troubleshooting, reverse engineering and conducting root cause analysis. They typically work as part of a large collaborative team and will have responsibility for significant elements of software solutions.

Option 2) IT consultant
An IT consultant bridges the gap between users and technology: they reinvent the digital world of the future. They require a broad set of skills in business analysis , solutions development, network infrastructure, data, cyber security etc. They use their consulting skills to get to the root of a problem and advise clients, both externally and internally, on how to best utilise technology to meet their business objectives, overcome problems and increase productivity. They provide strategic guidance and training to clients, both externally and internally, about digital and technology solutions. They facilitate changing business processes, improved structure, and efficiency through enhancements to digital and technology solutions . They design, build and install innovative customer experiences using the latest technologies to win business for their organisation.


Option 3) Business analyst
A business analyst is an interpreter between two worlds: business and IT, bridging the gap of understanding between business and technology teams. They analyse and understand business needs and define and manage business requirements . They oversee design and delivery of tested system solutions throughout a project life-cycle to ensure these meet business requirements . They are key communicators and drivers of collaboration throughout the development life cycle. They are focused on the customer and work closely with the IT delivery team. They are essential in the development of successful digital and technology solutions through their rigorous analysis of business requirements to inform their recommendations and insight.

Option 4) Cyber security analyst
A Cyber Security Analyst leads in the work to define, implement and maintain security products and systems within an organisation’s policies and service level agreements . They will need to analyse and understand the points of vulnerability within IT systems and a proactive and agile approach to maintain high levels of systems and organisational security. They will monitor security performance using tools, statistical reporting and analysis, using the output of monitoring to problem solve, propose improvements and implement changes to meet service level requirements. A Cyber Security Analyst leads technical implementation of security infrastructures and technical designs, including producing cost and timescale estimates and identifying risks. After implementation they take ownership for obtaining the information required to diagnose and resolve more complex problems and escalations such as security incidents and business recovery. They engage with third parties to jointly resolve in-depth product issues where necessary and completing cyber risk assessments .

Option 5) Data analyst
The primary role of a data analyst is to collect, organise and study data to provide new business insight to a range of stakeholders . They are responsible for leading the provision of up-to-date, accurate and relevant data analysis for the organisation. They are typically involved with managing, cleansing, abstracting and aggregating data across the network infrastructure. They look for opportunities to build data driven insights into decision makin g. They have a current understanding of data structures, software development procedures and the range of analytical tools used to undertake a wide range of standard and custom analytical studies , providing data solutions to a range of business issues. They are comfortable supporting teams and colleagues with analytics and report the results of data analysis activities making recommendations to improve business performance .

Option 6) Network engineer
The primary role of a network engineer is to lead in the planning, design , installation, maintenance and support of communication networks within an organisation or between organisations. They take a proactive and agile approach to maintain high levels of network performance and availability for their users, such as staff, clients, customers and suppliers. They understand network configuration, cloud, network administration and monitoring tools , and give technical advice and guidance to their users . As part of their role they analyse system requirements to ensure the network and its services operate to desired levels with security at the heart of everything they do . They understand data traffic and transmission across the network and have a major role to play in ensuring network security and resilience . They are the key problem solver when networks fail and respond with resilience under pressure.

Typical job titles include:

Business analyst Computing data analyst Cyber security professional It consultant Network engineer Software engineer

Core occupation duties

Duty KSBs

Duty 1 Critically analyse a business domain to identify opportunities for improvement

K1 K2 K3 K5 K7 K8 K10 K11 K12 K13 K14 K15 K16 K19 K20

S1 S2 S5 S9 S11 S12 S13 S14 S15

B1 B2 B3 B4 B6

Duty 2 Analyse business and technical requirements to select and specify appropriate technology solutions.

K1 K2 K3 K5 K10 K11 K12 K14 K16 K17 K20

S1 S2 S3 S7 S9 S10 S13 S15

B1 B2 B3 B4 B6 B8

Duty 3 Identify organisational information requirements and model data solutions using conceptual data modelling techniques

K1 K2 K3 K4 K5 K7 K8 K9 K11 K12 K13 K14 K15 K16 K19 K20

S1 S2 S5 S8 S9 S11 S13 S14 S15

B1 B2 B3 B6 B7 B8

Duty 4 undertake a security risk assessment for a simple IT system to identify, analyse and evaluate security threats and hazards to planned and installed information systems or services (e.g. Cloud services) and provide recommendations.

K1 K2 K3 K4 K6 K9 K11 K12 K13 K14 K15 K16 K17 K19 K20

S1 S2 S3 S5 S6 S9 S12 S13 S15

B1 B2 B3 B5 B6 B8

Duty 5 apply organisational theory, change management, marketing, strategic practice, human resource management and IT service management to technology solutions development.

K4 K7 K8 K12 K14 K15

S2 S9 S10

B1 B2 B3 B5 B6 B7 B8

Duty 6 follow a systematic methodology for initiating, planning, executing, controlling, and closing technology solutions projects using industry standard processes, methods, techniques and tools to execute and manage projects.

K1 K2 K3 K4 K8 K9 K10 K14 K15 K16 K19 K20

S1 S2 S3

B1 B2 B3 B4 B8

Duty 7 plan, design and manage computer networks with an overall focus on the services and capabilities that network infrastructure solutions enable in an organisational context. Identifies network security risks and their resolution.

K1 K2 K3 K4 K5 K7 K8 K10 K11 K12 K13 K14 K15 K16 K19 K20

S12 S13 S14 S15

B1 B2 B3 B4 B6 B7 B8

Duty 8 communicate effectively with a range of stakeholders both technical and non-technical at all levels of influence and responsibility.

K1 K3 K5 K11 K12 K14 K15 K16 K19 K20

S1 S2

B1 B2 B3 B4 B5 B6 B7 B8

Duty 9 devise and engage in continuous professional development

K2 K3 K5 K8 K9 K10 K12 K14 K15 K16 K17

S1 S2 S12

B1 B2 B3 B5 B6 B7 B8

Duty 10 conduct and present effective research using engaging, well-structured approaches

K6 K17 K18

S7 S10

B1 B2 B3 B6

Duty 11 design, build and test high-quality software solutions.

K3 K4 K6 K7 K10 K12

S2 S4 S5 S9

B1 B2 B3 B4 B6

Duty 12 apply engineering principles to all stages of the software development process, from requirements, analysis and design, development and data requirements

K4 K8 K14 K15 K16 K19 K20

B5 B7 B8

Duty 13 Apply skills and knowledge of systems development, cyber security, data, AI and infrastructure in the creation of digital solutions.

K1 K4 K5 K6 K7 K12 K14 K15 K16 K17 K18 K19 K20

S1 S2 S5 S9 S11 S14

B1 B2 B3 B4 B6 B7 B8

Duty 14 Analyse ethical and legal implications of digital and technology solutions and make recommendations as a result of this analysis. For example, with regard to artificial intelligence or the use of personal data.

K1 K6 K14 K15 K16 K17 K18 K20

S1 S2 S5 S10 S11 S15

B1 B2 B3 B6

Duty 15 Mentor others in the development and implementation of digital and technical solutions.

K2 K3 K4 K5 K10 K11 K12

B4 B5 B6 B7 B8

Option duties

Software engineering professional duties

Duty KSBs

Duty 16 Accountable for the undertaking and completion of the analysis of software engineering business issues for either the entire requirement or subset thereof dependent on complexity and/or scope size.

K21 K22 K23 K28

S16 S23

Duty 17 Implement the software solution, or part thereof, dependent on complexity, scope size and technology (including bespoke code, implementation of COTS package, or tailoring of package, or combinations of these) into the environment required (including systems test, user test environment, or live environment as appropriate).

K21 K22 K23 K24 K28

S19 S20

Duty 18 Creation of an over-arching software solution design suitable to resolving the business issues for either the entire requirement or subset thereof dependent on complexity and/or scope size.

K24 K26 K27 K28

S17 S18 S19

Duty 19 Build the software solution, or part thereof, dependent on complexity, scope size, and technology (including bespoke code, implementation of COTS (Commercial-off-the-shelf) package, or tailoring of package, or combinations of these).

K21 K22 K23 K24 K25 K26 K27 K28

S18 S19 S20 S21

Duty 20 Supervise the work of more junior team members undertaking work in the software solution life-cycle

K21 K28

S16 S17 S22

Duty 21 Test that the software solution, or part thereof, dependent on complexity, scope size and technology (including bespoke code, implementation of COTS package, or tailoring of package, or combinations of these) meets the business needs identifying any remedial actions required

K25 K26 K28

S16 S18 S21 S22 S23

Duty 22 Work closely with all key stakeholders to ensure the software solution or part thereof, dependent on complexity and scope size, is understood and correctly used.

K21 K28

S17 S22

Duty 23 Ongoing support of the software solution or part thereof, dependent on complexity and technology (including bespoke code, implementation of COTS package, or tailoring of package or combinations of these).

K21 K28

S22 S23

IT consultant professional duties

Duty KSBs

Duty 24 Perform internal and external client interviews to identify short and long term digital and technology business goals.

K29 K30 K35 K36

S28 S29

Duty 25 Perform gap analysis against current industry best practices.

K30 K34

S24 S26

Duty 26 Distinguish, analyse and document digital and technology requirements and manage those requirements through a project life cycle.

K30 K31 K34

S24 S26 S28 S29 S30

Duty 27 Use a range of methodologies, techniques and work products to produce digital and technology solutions for internal and external clients.

K30 K34 K35

S24 S26

Duty 28 Generate, develop and win new digital and technology business.

K33 K36

S24 S25 S26

Duty 29 Create and use intellectual capital to solve diverse technology and digital business issues in innovative ways.

K32 K33 K34

S28 S29 S30 S31

Duty 30 Design, test, install and monitor new systems and processes.

K33 K34 K35 K36

S24 S25 S26 S27 S28 S29 S30 S31

Duty 31 Devise and deliver training for users and other consultants.

K31 K32 K33

S25 S27

Duty 32 Manage walk-throughs to identify, document and manage key technical risks within an internal or external client’s organisation.

K31 K32

S27

Duty 33 Analyse an internal/external client’s IT environment to determine requirements and recommend technology and digital solutions to address their business problems and needs.

K32 K33 K34 K35 K36 K44

S24 S25 S26

Business analyst professional duties

Duty KSBs

Duty 34 Analyse an internal or external client’s business processes and recommend digital or process solutions to address their business problems and needs.

K37 K38 K39 K40 K43

S32 S33

Duty 35 Distinguish, analyse and document business requirements and manage those requirements through a project life cycle.

K38 K39

S32 S36

Duty 36 Analyse data and be responsible for logical data models to create suggestions for strategic and operational improvements and changes.

K39 K40 K43

S33 S35 S36

Duty 37 Design the user interface and propose and produce prototypes, including the look and feel of the graphical design and navigational elements.

K40 K41 K44

S33 S36 S37 S38 S39

Duty 38 Formulate and interpret business requirements into System Functional requirements, developing proposed solution designs including architecture.

K38 K43 K44

S32 S35 S38

Duty 39 Develop business test scenarios and test cases for verifying that the "right system is built", to meet the organisation’s requirements.

K38 K41 K42 K43

S34 S36 S37 S38

Duty 40 Produce written documentation to support work, report findings and present to stakeholders.

K38 K41 K44

S32 S35 S38 S39

Cyber security professional duties

Duty KSBs

Duty 41 Analyse and evaluate security threats to technology solutions and implement technical and process solutions to mitigate these threats.

K45 K46 K47 K49 K51

S40 S41 S43 S46

Duty 42 Perform security risk assessments within wider IT development teams, ensuring cyber security is embedded within the deliverables of the team.

K46 K47

S41

Duty 43 Lead a range of cyber security audit activities to demonstrate security control effectiveness.

K47 K48 K50

S42 S46

Duty 44 Apply advanced problem solving techniques to address cyber security issues.

K45 K48 K49 K50 K52

S40 S44 S46 S47

Duty 45 Plan and perform a business impact analysis in response to a security incident and implement a recovery plan.

K49 K51 K52

S40 S43 S44

Duty 46 Demonstrate effective management of cyber security processes and systems within the defined Service Level Agreements (SLAs).

K46 K48 K49 K50 K51 K52

S43 S45 S46 S47

Computing data analyst professional duties

Duty KSBs

Duty 47 Analytic support for colleagues

K53 K55 K58 K59

S49 S50 S51

Duty 48 Support the analytics strategy and measurement for specific teams across the business

K53 K54 K55 K57 K58 K59

S48 S49 S50 S51

Duty 49 Deliver insights, analysis, data and measurement that help the business achieve its objectives

K54 K55 K56 K57 K58 K59 K60

S48 S50 S51 S52 S53 S54 S55

Duty 50 Work with other stakeholders in order to understand their requirements

K53 K55 K56 K57 K58 K59 K60

S49 S50 S51 S55

Duty 51 Keep up to date with the latest developments within the field of data analytics

K53 K55 K56 K58 K59 K60

S48 S49 S51 S52 S54

Network engineering professional duties

Duty KSBs

Duty 52 Analyse a network system and make recommendations to optimise performance and efficiencies of network systems.

K62 K64 K66

S56 S59 S60

Duty 53 Design operational networks and apply appropriate security products and processes in line with organisational requirements.

K61 K63 K64 K66 K67

S56 S62

Duty 54 Plan system upgrades to a network or hardware or software or operating systems.

K61 K63 K64 K65 K66 K67 K68

S57 S58 S59 S60 S61 S62 S63

Duty 55 Produce relevant network information or documentation to meet user needs.

K64 K66

S57 S58 S61 S62 S63

Duty 56 Maintain accurate logical records in line with organisational policy and when carrying out network tasks and identify when network updates are required.

S56 S57 S58 S59 S61 S63

Duty 57 Interpret requirements and technical specifications in relation to network systems.

K61 K63 K64 K66 K67 K68

S57 S60 S61 S62

Duty 58 Escalate network security or resilience risk as appropriate, providing solution/s to identified risk area.

K61 K64 K65 K66

S58 S59 S60 S61 S63

Duty 59 Problem solve to address technical performance issues in network systems.

K61 K64 K65 K66

S59 S60 S61 S62 S63


KSBs

Knowledge

K1: How organisations adapt and exploit digital technology solutions to gain a competitive advantage. Back to Duty

K2: The principles of strategic decision making concerning the acquisition or development of digital and technology solutions. For example business architecture approaches such as capability models and target operating models. Back to Duty

K3: Principles of estimating the risks and opportunities of digital and technology solutions. Back to Duty

K4: Techniques and approaches involved in creating a business case for new digital and technology solutions. For example journey, product and capability mapping and value chains. Back to Duty

K5: A range of digital technology solution development techniques and tools. Back to Duty

K6: The approaches and techniques used throughout the digital and technology solution lifecycle and their applicability to an organisation’s standards and pre-existing tools. Back to Duty

K7: The roles, functions and activities within digital technology solutions within an organisation. Back to Duty

K8: How teams work effectively to produce digital and technology solutions. Back to Duty

K9: The concepts and principles of leadership. Back to Duty

K10: Management techniques and theories. For example, effective decision making, delegation and planning methods, time management and change management. Back to Duty

K11: The nature and scope of common vulnerabilities in digital and technology solutions. For example, the risks of unsecure coding and unprotected networks. Back to Duty

K12: The role of data management systems within Digital and Technology Solutions. Back to Duty

K13: Principles of data analysis for digital and technology solutions. Back to Duty

K14: A range of quantitative and qualitative data gathering methods and how to appraise and select the appropriate method. Back to Duty

K15: Principles of estimating cost, and time resource constraints within digital and technology solutions activities. Back to Duty

K16: Fundamental computer networking concepts in relation to digital and technology solutions. For example, structure, cloud architecture, components, quality of service. Back to Duty

K17: Reporting techniques, including how to synthesise information and present concisely, as appropriate to the target audience. Back to Duty

K18: Techniques of robust research and evaluation for the justification of digital and technology solutions. Back to Duty

K19: Relevant legal, ethical, social and professional standards to a digital and technology solution. For example, Diversity, Accessibility, Intellectual Property, Data Protection Acts, Codes of Practice, Regulatory and Compliance frameworks. Back to Duty

K20: Sustainable development approaches as applied to digital and technology solutions such as green computing. Back to Duty

K21: How to operate at all stages of the software development life cycle and how each stage is applied in a range of contexts. For example, requirements analysis, design, development, testing, implementation. Back to Duty

K22: Principles of a range of development techniques, for each stage of the software development cycle that produce artefacts and the contexts in which they can be applied. For example UML, unit testing, programming, debugging, frameworks, architectures. Back to Duty

K23: Principles of a range of development methods and approaches and the contexts in which they can be applied. For example Scrum, Extreme Programming, Waterfall, Prince2, TDD. Back to Duty

K24: How to interpret and implement a design, compliant with functional, non-functional and security requirements including principles and approaches to addressing legacy software development issues from a technical and socio-technical perspective. For example architectures, languages, operating systems, hardware, business change. Back to Duty

K25: The factors affecting product quality and approaches for how to control them throughout the development process. For example security, code quality, coding standards. Back to Duty

K26: How to select and apply a range of software tools used in Software Engineering. Back to Duty

K27: Approaches to the interpretation and use of artefacts. For example UML, unit tests, architecture. Back to Duty

K28: Approaches to effective team work and the range of software development tools supporting effective teamwork. For example, configuration management, version control and release management. Back to Duty

K29: Principles of different consulting methodologies. For example issue-based, and hypothesis based. Back to Duty

K30: How consulting interfaces with project management, business analysis and business management. Back to Duty

K31: Principles of change management within organisations. Back to Duty

K32: The barriers to solving digital and technology problems or maximising opportunities. Back to Duty

K33: Approaches to presenting recommendations to stakeholders and influencing action. Back to Duty

K34: Approaches to analytical and critical thinking to define business problems objectively and create value for the client. Back to Duty

K35: Questioning strategies and active listening to ensure all requirements are gathered. Back to Duty

K36: The ethical and legal requirements in client and provider relationships. Back to Duty

K37: Elicitation and Collaboration approaches, including how to prepare for and conduct elicitation activities and confirm the results. Back to Duty

K38: Approaches to Requirements Life Cycle Management including how to manage and maintain requirements and design information from inception to retirement of a product. Back to Duty

K39: Principles of Strategy Analysis, including how to identify the business need, address that need, and align the change strategy within the organisation. Back to Duty

K40: Solution Evaluation, including how to assess the performance of and value delivered by a solution and to recommend improvements on increasing values. Back to Duty

K41: Legislation and industry standards relevant to Business Analysis in the organisation and sector. Back to Duty

K42: The purpose and value of quality assurance techniques. Back to Duty

K43: A range of Business Analysis investigative techniques. Back to Duty

K44: Approaches to change control and requirements management. Back to Duty

K45: Principles of cyber security tools and techniques. Back to Duty

K46: Principles of quantitative and qualitative risk management theory including the role of risk stakeholders. Back to Duty

K47: Concepts and approaches to cyber security assurance. Back to Duty

K48: Key legislative frameworks and the regulatory landscape for cyber security including Data Protection Act 2018 , Network Information System Directive 2018, Regulation of Investigatory Powers Act 2000, ISO 27001. Back to Duty

K49: Approaches to incident response and management including escalation and investigation of cyber security breaches and their root cause. Back to Duty

K50: Ethical principles and codes of good practice of at least one significant cyber security professional body and the ethical responsibilities of a cyber security professional. Back to Duty

K51: Principles of common security architectures and methodologies. Back to Duty

K52: Approaches to deployment of cyber security technology components in digital systems to provide security functionality. For example hardware and software to implement security controls. Back to Duty

K53: The barriers that exist to effective data analysis between analysts and their stakeholders and how to avoid or resolve these. Back to Duty

K54: How to critically analyse, interpret and evaluate complex information from diverse datasets. Back to Duty

K55: Data formats, structures, architectures and data delivery methods including “unstructured” data. Back to Duty

K56: Sources of data such as files, operational systems, databases, web services, open data, government data, news and social media. Back to Duty

K57: Approaches to data processing and storage, database systems, data warehousing and online analytical processing, data-driven decision making and the good use of evidence and analytics in making choices and decisions. Back to Duty

K58: How Data Analytics operates within the context of data governance, data security, and communications. Back to Duty

K59: How Data Analytics can be applied to improve an organisation’s processes, operations and outputs. Back to Duty

K60: How data and analysis may exhibit biases and prejudice. How ethics and compliance affect Data Analytics work, and the impact of international regulations. For example, General Data Protection Regulation, Data Protection Act 2018. Back to Duty

K61: The role and function of virtual or physical network components and functions and typical topologies and service architectures. Back to Duty

K62: The main network protocols in use, their purpose, features and relationship to each other. For example, Ethernet, IP (Internet Protocol), TCP (Transmission Control Protocol), OSPF (Open Shortest Path First). Back to Duty

K63: The benefits and risks of cloud computing and the common integration deployments (private, public, hybrid). Including the benefits and risks of virtualisation as a concept; key features of virtualisation and current cloud platforms available. Back to Duty

K64: The main factors that affect network performance, and how to mitigate these on network performance by implementing changes to QoS. For example, Traffic Shaping, Policing, Queuing, Topology (physical and logical), and Network Policy (Traffic Analysis, DPI (Deep Packet Inspection). Back to Duty

K65: Principles of failure modes in protocols. For example, why a protocol may ‘hang’ and the effect of data communication errors and approaches to addressing failures to optimise network performance. Back to Duty

K66: Key security concepts. For example threats, vulnerabilities, exploits, detection and mitigation techniques, and security program elements such as user awareness, physical access control, multi-layer defence models. Back to Duty

K67: SDN (Software Defined Networking) and Network Function Virtualisation Core Principles. For example, Control Plane Separation, flexibility, overlay networks, disassociation of software and hardware layers. Back to Duty

K68: Key elements of mobile networks. For example RAN (Radio Access Network), EPC (Evolved Packet Core), IMS (IP Multimedia Subsystem) including some specific key functions such as S/P/U-Gateways and the concepts in communicating over free-space media such as interference, ground bounce, encryption and in mobile endpoint platforms such as tracking user location and roaming. Back to Duty

Skills

S1: Analyse a business problem to identify the role of digital and technology solutions. Back to Duty

S2: Identify risks, determine mitigation strategies and opportunities for improvement in a digital and technology solutions project. Back to Duty

S3: Analyse a business problem in order to specify an appropriate digital and technology solution. Back to Duty

S4: Initiate, design, code, test and debug a software component for a digital and technology solution. Back to Duty

S5: Apply relevant standard processes, methods, techniques and tools. For example, ISO Standards, Waterfall, Agile in a digital and technology solution project. Back to Duty

S6: Manage digital and technology solutions projects. For example, identifying and resolving deviations from specification, applying appropriate Project Management methodologies. Back to Duty

S7: Work effectively within teams, leading on appropriate digital technology solution activities. Back to Duty

S8: Apply relevant organisational theories. For example, change management principles, marketing approaches, strategic practice, and IT service management to a digital and technology solutions project. Back to Duty

S9: Apply relevant security and resilience techniques to a digital and technology solution. For example, risk assessments, mitigation strategies. Back to Duty

S10: Initiate, design, implement and debug a data product for a digital and technology solution. Back to Duty

S11: Determine and use appropriate data analysis techniques. For example, Text, Statistical, Diagnostic or Predictive Analysis to assess a digital and technology solutions. Back to Duty

S12: Plan, design and manage simple computer networks with an overall focus on the services and capabilities that network infrastructure solutions enable in an organisational context. Back to Duty

S13: Report effectively to colleagues and stakeholders using the appropriate language and style, to meet the needs of the audience concerned. Back to Duty

S14: Research, investigate, and evaluate innovative technologies or approaches in the development of a digital and technology solution. Back to Duty

S15: Apply relevant legal, ethical, social and professional standards to a digital and technology solution. Back to Duty

S16: Identify and define software engineering problems that are non-routine and incompletely specified. Back to Duty

S17: Provide recommendations as to the most appropriate software engineering solution. Back to Duty

S18: Use appropriate analysis methods, approaches and techniques in software engineering projects to deliver an outcome that meets requirements. Back to Duty

S19: Implement software engineering projects using appropriate software engineering methods, approaches and techniques. Back to Duty

S20: Respond to changing priorities and problems arising within software engineering projects by making revised recommendations, and adapting plans as necessary, to fit the scenario being investigated. Back to Duty

S21: Determine, refine, adapt and use appropriate software engineering methods, approaches and techniques to evaluate software engineering project outcomes. Back to Duty

S22: Evaluate learning points arising from software engineering work undertaken on a project including use of methods, analysis undertaken, selection of approach and the outcome achieved, in order to identify both lessons learnt and recommendations for improvements to future projects. Back to Duty

S23: Extend and update software development knowledge with evidence from professional and academic sources by undertaking appropriate research to inform best practice and lead improvements in the organisation. Back to Duty

S24: Analyse client needs and determine how to advise them strategically through improved business processes, new ideas, or technology solutions. Back to Duty

S25: Effectively communicate value add to the client through a variety of media. For example, presentations, written reports, Storytelling in a professional setting through performing socio-technical process improvements in a range of environments. Back to Duty

S26: Make evidence based recommendations taking into account risks, costs, and benefits. Back to Duty

S27: Participate in walk-throughs for Information Technologies, to identify, document and evaluate key risks within a client’s organisation. Back to Duty

S28: Perform stakeholder analysis to identify, determine and deepen understanding of system requirements and develop client relationships. Back to Duty

S29: Effect change within an organisation through evaluation of a new system, process or initiative. Back to Duty

S30: Ensure legal and ethical requirements are accommodated in the development of digital and technology solutions. Back to Duty

S31: Evaluate the  success of new systems, processes, or initiatives. Back to Duty

S32: Use requirements elicitation, analysis and documentation to produce an acceptable solution for business problems or further opportunities. Back to Duty

S33: Conduct Process Analysis, Definition, Mapping and Modelling within a business situation without supervision. Back to Duty

S34: Produce Use Cases which are of value to all stakeholders of a system. Back to Duty

S35: Use tools and benchmarking to support modelling and requirements gathering and recommend approaches to team members as required. Back to Duty

S36: Produce a business case to scope a proposed project including business benefits and recommendations. Back to Duty

S37: Use products of analysis in the design and development of a system. Back to Duty

S38: Evaluate the impacts of model selection and how they inter-relate with each other when generating business analytics. Back to Duty

S39: Recommend and use appropriate software tools to implement Business Analysis tasks and outcomes. Back to Duty

S40: Discover, identify and analyse security threats, attack techniques and vulnerabilities and recommend mitigation and security controls. Back to Duty

S41: Undertake security risk assessments for complex systems without direct supervision and propose a remediation strategy relevant to the context of the organisation. Back to Duty

S42: Recommend improvements to the cyber security approaches of an organisation based on research into future potential cyber threats and considering threat trends. Back to Duty

S43: Manage cyber security risk. Back to Duty

S44: Use appropriate cyber security technology, tools and techniques in relation to the risks identified. Back to Duty

S45: Lead cyber security awareness campaigns and evaluate their effectiveness. Back to Duty

S46: Analyse cyber security requirements against other design requirements for systems or products, identify conflicting requirements and recommend appropriate solutions with clear explanation of costs and benefits. Back to Duty

S47: Lead the design and build of systems in accordance with a security case to address organisational challenges. Back to Duty

S48: Define Data Requirements and perform Data Collection, Data Processing and Data Cleansing. Back to Duty

S49: Apply different types of Data Analysis, as appropriate, to drive improvements for specific business problems. Back to Duty

S50: Find, present, communicate and disseminate data analysis outputs effectively and with high impact through creative storytelling, tailoring the message for the audience. Visualise data to tell compelling and actionable narratives by using the best medium for each audience, such as charts, graphs and dashboards. Back to Duty

S51: Identify barriers to effective analysis encountered both by analysts and their stakeholders within data analysis projects. Back to Duty

S52: Apply a range of techniques for analysing quantitative data such as data mining, time series forecasting, algorithms, statistics and modelling techniques to identify and predict trends and patterns in data. Back to Duty

S53: Apply exploratory or confirmatory approaches to analysing data. Validate and and test stability of the results. Back to Duty

S54: Extract data from a range of sources. For example, databases, web services, open data. Back to Duty

S55: Analyse in detail large data sets, using a range of industry standard tools and data analysis methods. Back to Duty

S56: Identify and collate stakeholder needs in relation to computer network requirements, plans and designs. Back to Duty

S57: Plan, design, document, and develop the relevant elements of a computer network within an organisation or between organisations, taking into account customer requirements (performance, scale), constraints (budget, equipment availability), and define policies for their use. Back to Duty

S58: Monitor performance and ensure networks are configured correctly and perform as expected by designers or architects. Undertake capacity management and audit of IP addressing and hosted devices. Back to Duty

S59: Investigate, troubleshoot and resolve data network faults in local and wide area environments, using information from multiple sources, Physically or Remotely by console connection. Recommend and implement short term fixes to restore service and, or, quality of experience and recommend longer term changes to prevent recurrence or reduce impact of future occurrences. Back to Duty

S60: Implement computer networks from a design including testing and validation. This includes populating variables in configurations, for example, IP addresses and subsequent application of configuration to equipment such as routers, switches, firewalls. Back to Duty

S61: Secure network systems by establishing and enforcing policies, and defining and monitoring access. Support and administer firewall environments in line with IT security policy. Back to Duty

S62: Research and evaluate emerging network technologies and assess relevance to current network requirements. Provide an objective opinion on how new features and technologies may be incorporated as required by the organisation. Back to Duty

S63: Investigate security concerns or attacks. For example, Distributed Denial of Service (DDOS), port scanning, assessing key metrics and indicators, evidencing the chosen steps to mitigate. Back to Duty

Behaviours

B1: Has a strong work ethic and commitment in order to meet the standards required. Back to Duty

B2: Reliable, objective and capable of both independent and team working. Back to Duty

B3: Acts with integrity with respect to ethical, legal and regulatory requirements ensuring the protection of personal data, safety and security. Back to Duty

B4: Commits to continuous professional development; maintaining their knowledge and skills in relation to developments in digital and technology solutions that influence their work. Back to Duty

B5: Interacts professionally with people from technical and non-technical backgrounds. Presents data and conclusions in an evidently truthful, concise and appropriate manner. Back to Duty

B6: Participates in and shares best practice in their organisation, and the wider community for aspects relevant to digital and technology solutions. Back to Duty

B7: Maintains awareness of trends and innovations in the subject area, utilising a range of academic literature, online sources, community interaction, conference attendance and other methods which can deliver business value. Back to Duty

B8: Champions diversity and inclusion in their work ensuring that digital technology solutions are accessible. Back to Duty


Qualifications

English and Maths

Apprentices without level 2 English and maths will need to achieve this level prior to taking the End-Point Assessment. For those with an education, health and care plan or a legacy statement, the apprenticeship’s English and maths minimum requirement is Entry Level 3. A British Sign Language (BSL) qualification is an alternative to the English qualification for those whose primary language is BSL.

Other mandatory qualifications

Digital and Technology Solutions Professional Integrated degree

Level: 6 (integrated degree)

Professional recognition

This standard aligns with the following professional recognition:

  • British Computer Society for Registered IT Technician (RITTech)
Print EPA plan

End-point assessment plan

Introduction and overview

This document explains the requirements for end-point assessment (EPA) for the digital and technology solutions professional apprenticeship. End-point assessment organisations (EPAOs) must follow this when designing and delivering the EPA.

Digital and technology solutions professional apprentices, their employers and training providers should read this document.

An approved EPAO must conduct the EPA for this apprenticeship. Employers must select an approved EPAO from the Education and Skills Funding Agency’s Register of end-point assessment organisations (RoEPAO).

A full-time apprentice typically spends 48 months on-programme (this means in training before the gateway) working towards competence as a digital and technology solutions professional. All apprentices must spend at least 12 months on-programme. All apprentices must complete the required amount of off-the-job training specified by the apprenticeship funding rules.

This EPA has 2 assessment methods.

The grades available for each assessment method are:

Assessment method 1 - project report with presentation, questions and answers:

  • fail
  • pass
  • distinction

Assessment method 2 - professional discussion underpinned by a portfolio:

  • fail
  • pass
  • distinction

The result from each assessment method is combined to decide the overall apprenticeship grade. The following grades are available for the apprenticeship:

  • fail
  • pass
  • merit
  • distinction

EPA summary table

On-programme (typically 48 months)
The apprentice must complete training to develop the knowledge, skills and behaviours (KSBs) of the occupational standard.

The apprentice must complete training towards English and maths qualifications in line with the apprenticeship funding rules. This includes those with an education, health and care plan or a legacy statement. British sign language (BSL) qualifications are an alternative to English qualifications for those who have BSL as their primary language.

The apprentice must complete training towards any other qualifications listed in the occupational standard.

The qualification(s) required are:

Digital and Technology Solutions Professional Integrated degree

The apprentice must compile a portfolio of evidence.

End-point assessment gateway
The employer must be content that the apprentice is working at or above the occupational standard.

The apprentice’s employer must confirm that they think the apprentice:

  • is working at or above the occupational standard as a digital and technology solutions professional
  • has the evidence required to pass the gateway and is ready to take the EPA
  • has achieved 330 credits of the BSc Digital and Technology Solutions Professional degree apprenticeship (subject to university board approval). The final 30 credits of the BSc Digital and Technology Solutions Professional degree will be attributed to the end-point assessment

The apprentice must have passed any other qualifications listed in the digital and technology solutions professional occupational standard ST0119.

The qualification(s) required are:

Digital and Technology Solutions Professional Integrated degree

The apprentice must achieve all of the qualifications listed in the Digital and technology solutions professional occupational standard ST0119 relevant to their chosen option.

The apprentice must have achieved English and mathematics qualifications (including those with an education, health and care plan or a legacy statement) as specified by the apprenticeship funding rules. British Sign Language (BSL) qualifications are an alternative to English qualifications for those who have BSL as their primary language.

For the project report with presentation, questions and answers, the apprentice must submit the following supporting material: project title and summary requirements. To ensure the project allows the apprentice to meet the KSBs mapped to this assessment method to the highest available grade, the EPAO should sign-off the project’s title and scope at the gateway to confirm it is suitable.

For the professional discussion underpinned by a portfolio the apprentice must submit a portfolio of evidence.

The apprentice must submit any policies and procedures as requested by the EPAO.

End-point assessment (typically 3 months)
Grades available for each assessment method:

Project report with presentation, questions and answers

  • fail
  • pass
  • distinction

Professional discussion underpinned by a portfolio

  • fail
  • pass
  • distinction

Overall EPA and apprenticeship can be graded:

    • fail
    • pass
    • merit
    • distinction
Professional recognition
This apprenticeship aligns with British Computer Society for Registered IT Technician (RITTech) .

The apprenticeship will either wholly or partially satisfy the requirements for registration at this level.





Re-sits and re-takes



  • Re-take and re-sit grade cap: merit
  • Re-sit timeframe: typically 3 months
  • Re-take timeframe: typically 6 months

Duration of end-point assessment period

The EPA is taken in the EPA period. The EPA period starts when the EPAO confirms the gateway requirements have been met and is typically 3 months.

The EPAO should confirm the gateway requirements have been met and the EPA should start as quickly as possible.

EPA gateway

The apprentice’s employer must be content that the apprentice has attained sufficient KSBs to complete the apprenticeship. The employer may take advice from the apprentice's training provider, but the employer must make the decision. The apprentice will then enter the gateway.

The apprentice must meet the gateway requirements before starting their EPA.

They must:

  • confirm they are ready to take the EPA
  • have achieved English and maths qualifications in line with the apprenticeship funding rules
  • have passed Digital and Technology Solutions Professional Integrated degree
  • submit a Project title and summary for the project report with presentation, questions and answers

The apprentice will scope out and provide a summary of what the project will cover and will submit this to the EPAO at the gateway. This should demonstrate that the work-based project report will provide sufficient opportunity for the apprentice to meet the KSBs mapped to this method. The summary is not formally assessed and will typically be no longer than 500 words.

The project proposal needs to include a summary of the project plan, research requirements, an overview of how the project will be planned to include timeframes and the date the work-based project report must be submitted to the independent assessor taking into account the deadlines stipulated within this end-point assessment plan. The EPAO will sign off the project summary within 2 weeks of the Gateway to ensure sufficient scope to meet the KSBs mapped to this assessment method.

  • submit a Portfolio of evidence for the professional discussion underpinned by a portfolio

• apprentices must compile a portfolio of evidence during the on-programme period of the apprenticeship

• it must contain evidence related to the KSBs that will be assessed by the professional discussion

• the portfolio of evidence will typically contain 6 discrete pieces of evidence

• evidence must be mapped against the KSBs

• evidence may be used to demonstrate more than one KSB; a qualitative as opposed to quantitative approach is suggested

• evidence sources may include:

o workplace documentation/records, for example workplace policies/procedures, records

o witness statements

o annotated photographs

o video clips (maximum total duration 10 minutes); the apprentice must be in view and identifiable

This is not a definitive list; other evidence sources are possible.

• Although it is expected that apprentices at degree level will be reflective in their practice, it should be noted that the EPA assesses individuals on evidence of output against the KSBs, not reflective accounts or any methods of self-assessment.

• any employer contributions should focus on direct observation of performance (for example witness statements) rather than opinions

• the evidence provided must be valid and attributable to the apprentice; the portfolio of evidence must contain a statement from the employer and apprentice confirming this

• the portfolio of evidence must be submitted to the EPAO at the gateway

The portfolio of evidence is not directly assessed. It underpins the professional discussion and therefore should not be marked by the EPAO. EPAOs should review the portfolio of evidence in preparation for the professional discussion but are not required to provide feedback after this review of the portfolio.

The apprentice must submit the gateway evidence to their EPAO, including any organisation specific policies and procedures requested by the EPAO.

Order of assessment methods

The assessment methods can be delivered in any order.

The result of one assessment method does not need to be known before starting the next.

Project report with presentation, questions and answers

Overview

A project involves the apprentice completing a significant and defined piece of work that has a real business application and benefit.

NB - The project may be undertaken pre-gateway, however, the Project Report must be completed after the apprentice has gone through the gateway.

A Digital and Technology Solutions Project may take years and not all projects experience a full life cycle, sometimes being abandoned for cost reasons or change of business strategy. A Digital Technology Solutions Professional may be one of a multidisciplined team and therefore may not control the timescale of the project. Therefore a project (or part project) cannot be designed or delayed to fit into the EPA timescale nor the specification of the EPAO as results can range from successful new recommendations on process, product or decommission. This cannot be predicted.

The project must give the apprentice the opportunity to demonstrate the KSBs mapped to this assessment method.

The project must meet the needs of the employer’s business and be relevant to the apprentice’s occupation and apprenticeship. The EPAO must confirm that it provides the apprentice with the opportunity to demonstrate the KSBs mapped to this assessment method to the highest available grade. The EPAO must refer to the grading descriptors to ensure that projects are pitched appropriately.

This assessment method has 2 components:

  • project with a project output
  • presentation with questions and answers

Rationale

This assessment method is being used because a project is a fundamental activity within the sectors in which a DTSP works. Every specialism within the DTSP apprenticeship works within a project-based approach and so this is a valid way of measuring competence.

The project may be undertaken pre-gateway, however, the Project Report must be completed after the apprentice has gone through the gateway.

A Digital and Technology Solutions Project may take years and not all projects experience a full life cycle, sometimes being abandoned for cost reasons or change of business strategy. A Digital Technology Solutions Professional may be one of a multidisciplined team and therefore may not control the timescale of the project. Therefore a project (or part project) cannot be designed or delayed to fit into the EPA timescale nor the specification of the EPAO as results can range from successful new recommendations on process, product or decommission. This cannot be predicted.

Component 1: Project with a project output

Delivery

The project report with presentation, questions and answers must be structured to give the apprentice the opportunity to demonstrate the KSBs mapped to this assessment method to the highest available grade.

The apprentice’s project can be based on any of the following:

  • a specific problem
  • a recurring issue
  • an idea or opportunity

To ensure the project allows the apprentice to meet the KSBs mapped to this assessment method to the highest available grade, the EPAO should sign-off the project’s title and scope at the gateway to confirm it is suitable.

The project output must be in the form of a report.

The apprentice must start the project after the gateway. They must complete and submit the to the EPAO by the end of weekreport 12 of the EPA period. The employer should ensure the apprentice has the time and resources, within this period, to plan and complete their project. The apprentice must complete their project and the production of its components unaided.

The apprentice may work as part of a team to complete the project which could include technical internal or external support. However, the project output must be the apprentice’s own work and reflective of their own role and contribution. The apprentice and their employer must confirm that the project output(s) is the apprentice’s own work when it is submitted.

The report must include at least:

  • an introduction
  • the scope of the project (including key performance indicators and stakeholder engagement)
  • how the outcomes would be achieved
  • a project plan
  • research and findings
  • project outcomes
  • recommendations and conclusions.

The project report has a word count of 9000 words. A tolerance of 10% above or below the word count is allowed at the apprentice’s discretion. Appendices, references and diagrams are not included in this total. The project report must map, in an appendix, how it evidences the KSBs mapped to this assessment method.

Component 2: Presentation with questions

Delivery

In the presentation with questions the apprentice delivers a presentation to an independent assessor on a set subject. The independent assessor must ask questions following the presentation. This gives the apprentice the opportunity to demonstrate the KSBs mapped to this assessment method.

The apprentice must prepare and submit their presentation speaker notes and supporting materials presentation with questions and answers. The independent assessor must ask questions after the presentation. The presentations must include:

  • an overview of the project
  • the project scope (including key performance indicators)
  • summary of actions undertaken by the apprentice
  • project outcomes and how these were achieved

The apprentice must prepare and submit their presentation speaker notes and supporting materials to the EPAO at the same time as the report by the end of week 12 of the EPA period.

The apprentice must notify the EPAO, at that point, of any technical requirements for the presentation. During the presentation, the apprentice must have access to:

  • presentation software
  • a copy of the project report and presentation
  • notes
  • computer

The independent assessor must have at least 2 weeks to review the project output(s) and presentation speaker notes and supporting materials, to allow them to prepare questions. 

The EPAO must give the apprentices at least 14 days notice of the presentation with questions.

The apprentice must deliver their presentation to the independent assessor on a one-to-one basis.

The independent assessor must ask questions after the presentation.

The purpose of the questions is to explore and verify the apprentice’s understanding of their project area in relation to the apprenticeship standard.

The presentation and questions must last 60 minutes. This will typically include a presentation of 30 minutes and questioning lasting 30 minutes. The independent assessor can increase the total time of the presentation and questioning by up to 10%. This time is to allow the apprentice to complete their last point or respond to a question if necessary.

The independent assessor must ask at least 4 questions. They must use the questions from the EPAO’s question bank or create their own questions in-line with the EPAO’s training. Follow up questions are allowed where clarification is required.

The independent assessor must use the full time available for questioning. The independent assessor must make the grading decision. The project components must be assessed holistically by the independent assessor when they are deciding the grade.

The independent assessor must make the grading decision. The project components must be assessed holistically by the independent assessor when they are deciding the grade.

The independent assessor must keep accurate records of the assessment. They must record:

  • the KSBs demonstrated in the report and presentation
  • the apprentice’s answers to questions
  • the KSBs demonstrated in answers to questions
  • the grade achieved 

Assessment location

The presentation with questions must take place in a suitable venue selected by the EPAO (for example the EPAO’s or employer’s premises).

The presentation with questions should take place in a quiet room, free from distractions and influence.

The presentation with questioning can be conducted by video conferencing. The EPAO must have processes in place to verify the identity of the apprentice and ensure the apprentice is not being aided.

Question and resource development

The EPAO must develop a purpose-built assessment specification and question bank. It is recommended this is done in consultation with employers of this occupation. The EPAO should maintain the security and confidentiality of EPA materials when consulting employers. The assessment specification and question bank must be reviewed at least once a year to ensure they remain fit-for-purpose.  

The assessment specification must be relevant to the occupation and demonstrate how to assess the KSBs mapped to this assessment method. The EPAO must ensure that questions are refined and developed to a high standard. The questions must be unpredictable. A question bank of sufficient size will support this.

The EPAO must ensure that the apprentice has a different set of questions in the case of re-sits or re-takes.

EPAO must produce the following materials to support the project report with presentation, questions and answers:

  • independent assessor EPA materials which include:
    • training materials
    • administration materials
    • moderation and standardisation materials
    • guidance materials
    • grading guidance
    • question bank
  • EPA guidance for the apprentice and the employer

The EPAO must ensure that the EPA materials are subject to quality assurance procedures including standardisation, training, and moderation.

Professional discussion underpinned by a portfolio

Overview

In the discussion, an independent assessor and apprentice have a formal two-way conversation.

The apprentice can refer to and illustrate their answers with evidence from their portfolio of evidence. It gives the apprentice the opportunity to demonstrate their competency across the KSBs mapped to this EPA method.

Rationale

This assessment method is being used because:

  • breadth of the core of the standard and opportunities to evidence across this throughout the duration of the programme
  • allows the opportunity to explore depth of understanding surrounding the relevant specialist KSBs

·.

Delivery

The professional discussion must be structured to give the apprentice the opportunity to demonstrate the KSBs mapped to this assessment method to the highest available grade.

An independent assessor must conduct and assess the professional discussion.

The purpose of the independent assessor's questions will be to explore the following topics and themes:

Theme A: Underlying Principles

Theme B: Technical Solutions

Theme C: Innovation and Response

Theme D: Legal, Ethics and Landscape

The EPAO must give an apprentice 14 days notice of the professional discussion.

The independent assessor must have at least 2 week(s) to review the supporting documentation.

The apprentice must have access to their during the professional discussion.

The apprentice can refer to and illustrate their answers with evidence from their , however the is not directly assessed.

The professional discussion must last for 60 minutes. The independent assessor can increase the time of the professional discussion by up to 10%. This time is to allow the apprentice to respond to a question if necessary.

The independent assessor must ask at least 4 questions. Follow-up questions are allowed where clarification is required. The independent assessor must use the questions from their EPAO’s question bank or create their own questions in-line with the EPAO’s training.

The independent assessor must make the grading decision. The independent assessor must keep accurate records of the assessment. They must record:

  • the apprentice’s answers to questions
  • the KSBs demonstrated in answers to questions
  • the grade achieved 

Assessment location

The professional discussion must take place in a suitable venue selected by the EPAO (for example the EPAO’s or employer’s premises).

The professional discussion can be conducted by video conferencing. The EPAO must have processes in place to verify the identity of the apprentice and ensure the apprentice is not being aided.

The professional discussion should take place in a quiet room, free from distractions and influence.

Question and resource development

The EPAO must develop a purpose-built assessment specification and question bank. It is recommended this is done in consultation with employers of this occupation. The EPAO should maintain the security and confidentiality of EPA materials when consulting employers. The assessment specification and question bank must be reviewed at least once a year to ensure they remain fit-for-purpose.  

The assessment specification must be relevant to the occupation and demonstrate how to assess the KSBs mapped to this assessment method. The EPAO must ensure that questions are refined and developed to a high standard. The questions must be unpredictable. A question bank of sufficient size will support this.

The EPAO must ensure that apprentice has a different set of questions in the case of re-sits or re-takes.

The EPAO must produce the following materials to support the professional discussion underpinned by a portfolio:

  • independent assessor assessment materials which include:
  • training materials
  • administration materials
  • moderation and standardisation materials
  • guidance materials
  • grading guidance
  • question bank
  • EPA guidance for the apprentice and the employer

The EPAO must ensure that the EPA materials are subject to quality assurance procedures including standardisation, training, and moderation.

Grading

Project report with presentation, questions and answers

Fail - does not meet pass criteria

Theme
KSBs
Pass
Apprentices must demonstrate all of the pass descriptors
Distinction
Apprentices must demonstrate all of the pass descriptors and all of the distinction descriptors
(Core) The Organisational Context
K1 K2

Identifies the role digital technology solutions play in gaining a competitive advantage by adapting and exploiting them (K1)

Explains the principles of strategic decision making concerning the acquisition or development of digital and technology solutions. (K2)

 

N/A

(Core) Project Requirements
S3 B3

Analyses relevant evidence to produce a proposal for a digital and technology based project in line with legal, ethical and regulatory requirements whilst ensuring the protection of personal data, safety and security (S3,B3)

N/A

(Core) Project Planning and Resources
K3 K4 K15 S2 S14

Produces a project plan which estimates risks and opportunities  and determines mitigation strategies.' (K3, S2)

Evaluates appropriate techniques and approaches that are used in creating a business case (K4)

The project applies techniques to estimate cost and time resource constraints.' (K15)

Researches information on innovative technologies/approaches and investigates and evaluates them in the development of a digital and technology solution. (S14)

 

N/A

(Core) Solution Proposal
S1

Analyses the business problem behind the project proposal to identify the role of digital and technology solutions. (S1)

Justifies their choice of digital and technology solutions for specific roles in the project proposal. (S1)

(Core) Project Delivery
K5 S5 S6

Carries out the identified solution proposal utilising a range of digital tools and standard approaches. (K5, S5)   

Manages the project delivery to achieve digital and technology solutions. (S6)

Justifies the selection and use of standard processes and methods. (K5, S5)

(Core) Project Evaluation
K17 K18 S13 B5

Justifies their methods of research and evaluation which determined the selection of digital and technology solutions identified for the project. (K18)

Presents an overview of the project to appropriate stakeholders using appropriate language and style. (K17, S13, B5)    

 

Compares and contrasts their chosen digital technology solution to alternative approaches within their research outcomes. (K18,S13)

 

 

 

(Software Engineer) Technical Solutions
K25 K26 K27

Analyses the factors affecting product quality and the approaches controlling them throughout the project development process. (K25/SEK5).

Selects and applies software tools appropriate to the Software Engineering project solution. (K26/SEK6)

Outlines approaches to the interpretation and use of artefacts. (K27/SEK7)

Evaluates the impact of approaches used to control product quality throughout the project development process. (K25/SEK5)

(Software Engineer) Innovation and Response
S16 S17 S18 S19 S22

Identifies and defines a non-routine, unspecified software engineering problem. (S16/SES1)  

Recommends a software engineering solution that is appropriate for the project brief. (S17/SES2)

Selects and applies analysis methods, approaches and techniques in software engineering projects to deliver an outcome that meets requirements. (S18/SES3) 

Demonstrates how they implement software engineering projects using appropriate software engineering methods, approaches and techniques. (S19/SES4)

Evaluates their selection of approach, methodology, analysis and outcomes to identify both lessons learned and recommendations for improvements to future projects software engineering projects. (S22/SES7)

 

Evaluates their choice of software engineering solution for the project brief. (S17/SES2) 

Justifies their choice of analysis methods approaches and techniques. (S18/SE3)

Compares and contrasts the implementation of their software engineering solution with alternative approaches. (S22/SES7)   

 

(IT Consultant) Underlying Principles
K29 K32

Evaluates the principles of different consulting methodologies. (K29/ITK1)

Summarises the barriers to solving problems or maximizing opportunities. (K32/ITK4)

 

N/A

(IT Consultant) Innovation and Response
K33 S24 S26 S28

Analyses client needs to advise a strategic approach to improve business processes, provide new ideas and/or technology solutions. (S24/ITS1)

Demonstrates presenting recommendations to stakeholders and influencing action, considering risks, costs and benefits. (K33/ITK5, S26/ITS3)

Demonstrates how they perform stakeholder analysis to identify, determine and deepen understanding of system requirements and develop client relationships. (S28, ITS5)

 

Critically evaluates the impact of methods used to present recommendations to stakeholders. (K33/ITK5, S26/ITS3)

(IT Consultant) Ethics and Landscape
S30

Evaluates how they ensure legal and ethical requirements are accommodated in the development of digital and technology solutions. (S30/ITS7)

N/A

(IT Consultant) Technical Solutions
S31

Demonstrates how they evaluate the success of a new system, process, or initiative. (S31, ITS8)

N/A

(Business Analyst) Technical Solutions
S32 S34

Compare and contrast how they use requirements elicitation, analysis and documentation to produce an acceptable solution for business problems or further opportunities. (K37/BAK1,S32/BAS1)     

Evaluate the impact of Use Cases on all stakeholders of a system. (S33/BAS3)

N/A

(Business Analyst) Legal, Ethics and Landscape
K44 S36 S38

Demonstrate how they produce a business case to scope a proposed project including business benefits and recommendations. (S36/BAS5)

Evaluates the impact of model selection and how they inter-relate with each other when generating business analytics in line with the project brief. (S38/BAS7)

Describes Solution Evaluation, including how to assess the performance of and value delivered by a solution and to recommend improvements on increasing value. (K40/BAK4)

Outlines the approaches used for change control and requirements management within the project. (K44/BAK8)

 

N/A

(Business Analyst) Innovation and Response
K40 S39

Applies the principles of Solution Evaluation to assess performance of and value delivered in the project and outlines recommendations on how to increase value in the future. (K40/BAK4)

Demonstrates how they recommend and apply software tools to implement Business Analysis tasks and outcomes in the project brief. (S39/BAS8)

 

Critically analyses their approach to Solution Evaluation has had on project outcomes. (K40/BAK4)

Critically evaluates the use of appropriate software tools to implement Business Analysis tasks and outcomes. (S39/BAS8)      

 

(Cyber Security Analyst) Underlying Principles
K45 K51

Explains the principles of cyber security tools and techniques as related to the project. (K45/CSK1)      

Relates the principles of security architectures and methodologies to the project. (K51/CSK7)  

 

N/A

(Cyber Security Analyst) Innovation and Response
K52 S42 S46 S47

Describes approaches to deployment of cyber security technology components in digital systems to provide security functionality. (K52/CSK8)

Demonstrate how they recommend improvements to the cyber security approaches of an organisation based on research into future potential cyber threats and considering threat trends in the project. (S42/CSS3)

Demonstrate how they analyse cyber security requirements in the project against other design requirements for systems or products and identify conflicting requirements and recommend appropriate solutions with clear explanation of costs/benefits. (S46/CSS7)

Demonstrate how they lead the design and build of systems in accordance with a security case to address organisational challenges in the project. (S47/CSS8)

 

Justifies their choice of approach to deployment of cyber security technology components in digital systems to provide security functionality within the project. (K52/CSK8)

(Cyber Security Analyst) Technical Solutions
S40 S44

Demonstrate how they discover, identify and analyse security threats, attack techniques and vulnerabilities using cyber security architectures, methodologies, tools and techniques to recommend mitigation and security controls in the project. (S40/CSS1)   

Selects and applies cyber security tools and techniques in relation to the risks identified in the context of the project. (K41/CSK1, S44/CSS5)

Critically evaluates how they discover, identify and analyse security threats, attack techniques and vulnerabilities and recommend mitigation and security controls in the project (S40/CSS1)

(Data Analyst) Underlying Principles
K54 K56 K58

Critically analyses data sets, using a range of industry standard tools and data analysis methods. (K54/DAK2)

Outlines sources of data used for the project. (K56/DAK4)

Describes how Data Analytics operates within the context of data governance, data security, and communications in respect of the project. (K58/DAK6)

 

Summarises the outcomes of analysing, interpreting and evaluating complex information from diverse datasets. (K54/DAK2)

Critically evaluates  sources of data for the project. (K56/DAK4)

(Data Analyst) Innovation and Response
S50 S52 S53 S54 S55

Visualises data to tell compelling and actionable narratives by using the best medium for each audience. (S50/DAS3)   

Demonstrates how they have applied a range of techniques for analysing quantitative data such as data mining, time series forecasting, algorithms, statistics and modelling techniques to identify and predict trends and patterns in data. (S52/DAS5)

Demonstrates how they have applied exploratory or confirmatory approaches to analysing data. and how they have validated and tested stability of the results. (S53/DAS6)

Demonstrates how they extract data from a range of sources. (S54/DAS7)

Demonstrates how they analyse, in detail large data sets, using appropriate industry standard tools and data analysis methods. (S55/DAS8)   

 

 

Evaluates their approach to finding, presenting, communicating and disseminating data analysis outputs effectively and with high impact through creative storytelling, tailoring the message for the audience.  Compares and contrasts alternative approaches to visualise data to tell compelling and actionable narratives by using the best medium for each audience. (S50/DAS3)

Evaluates how they apply a wide range of techniques for analysing quantitative data such as data mining, time series forecasting, algorithms, statistics and modelling techniques to identify and predict trends and patterns in data. (S52/DAS5)

Evaluates how they apply exploratory or confirmatory approaches to analysing data and evaluates their approach to in depth validation and testing stability of the results. (S53/DAS6)

Evaluates their approach to in depth extraction of data from a range of sources leading making conclusions from the data for decision-making purposes for an internal or external stakeholder.(S54/DAS7)

Evaluates their approach to analysing in detail large data sets, using a range of industry standard tools and data analysis methods and suggests how this allows internal or external stakeholders to draw conclusions from the data for decision-making purposes. (S55/DAS8)

 

 

(Network Engineer) Underlying Principles
K61 K62 K66

Explain the role of physical and/or virtual network component and their impact within a project. (K61/NEK1)

Explain network fundamentals concepts (protocols, features etc.) and the relationships between them that are relevant to a specific project undertaken. (K62/NEK2)

Describe key security concepts and security programme elements. (K66/NEK6)

 

N/A

(Network Engineer) Innovation and Response
S56 S57 S60 S62

Demonstrate how they identify and collate stakeholder network needs. (S56/NES1)

Demonstrate how they plan, design, document and develop network solutions taking into consideration stakeholder requirements and define appropriate operational policies. (S57/NES2)

Demonstrate how they implement, test and validate networks from a design, explaining the chosen design and implementation. (S60/NES5)

Demonstrate how they research and evaluate emerging network technologies, utilising appropriate sources of evidence, to support an objective recommendation. (S62/NES7)

 

Critically evaluate how they plan, design, document and develop network solutions taking into consideration stakeholder requirements and define appropriate operational policies. (S57/NES2)

Critically evaluate how they research and evaluate emerging network technologies, utilising appropriate sources of evidence, to support an objective recommendation. (S62/NES7)

 

(Network Engineer) Technical Solutions
S63

Demonstrate how security concerns or attacks are investigated and mitigated. (S63/NES8)

N/A

Professional discussion underpinned by a portfolio

Fail - does not meet pass criteria

Theme
KSBs
Pass
Apprentices must demonstrate all of the pass descriptors
Distinction
Apprentices must demonstrate all of the pass descriptors and all of the distinction descriptors
(Core) The Organisational Context
K7

Reviews the roles, functions and activities relevant to technology solutions within an organisation. (K7)

N/A

(Core) Core Technical Concepts
K6 K11 K12 K14 K16

Critically evaluates the nature and scope of common vulnerabilities in digital and technology solutions (K11)

Explains core technical concepts for digital and technology solutions, including:

- The approaches and techniques used throughout the digital and technology solution lifecycle and their applicability to an organisation’s standards and pre-existing tools.(K6)

- Data gathering, data management, and data analysis.(K12, K14)

- Computer networking concepts.(K16)    

 

N/A

(Core) Applied Technical Solutions
K13 S4 S9 S10 S11 S12

Demonstrates the use of core technical concepts for digital and technology solutions, including:

- Initiate, design, code, test and debug a software component for a digital and technology solution. (S4)

- Security and resilience techniques. (S9)

- Initiates, designs, implements and debugs a data product for a digital and technology solution. (S10)

- Plans, designs and manages simple computer networks. (S12)

- Applies the principles of data analysis for digital and technology solutions. (K13, S11)

 

N/A

 

(Core) Leading and Working Together
K8 K9 K10 S7 S8 B4 B6 B7

Explains how teams work effectively to produce a digital and technology solution applying relevant organisational theories using up to date awareness of trends and innovations. (K8, S7, B4,B6,B7)    

Describes the concepts and principles of leadership and management as they relate to their roleand how they apply them. (K9, K10,S8)    

 

N/A

 

(Core) Social Infrastructure - Legal, Ethical and Sustainability
K19 K20 S15 B1 B2 B8

Applies relevant legal, ethical, social and professional standards to digital and technology solutions considering both technical and non-technical audiences and in line with organisational guidelines. (K19, S15, B1, B2, B5)

Explains sustainable development approaches within digital technologies as they relate to their role including diversity and inclusion. (K20, B8)

 

Justifies the application of relevant legal, ethical, social and professional standards to digital and technology solutions. (K19, S15)

Evaluates the impact of sustainable digital technology practices of their organisation. (K20)   

 

(Software Engineer) Underlying Principles
K21 K22 K23

Describes scenarios covering all stages of a development lifecycle, identifying techniques and methods are applied in each case. (K21/SEK1)

Explains the principles of a range of development techniques, for each stage of the software development cycle that produce artefacts and the contexts in which they can be applied. (K22/SEK2)

Explains the principles of a range of development methods and approaches and the contexts in which they can be applied. (K23/ SEK3)

 

N/A

(Software Engineer) Technical Solutions
K24 K28

Describes. how to interpret and implement a design, compliant with functional, non-functional and security requirements. K24/SEK4

Describes how tools that support teamwork can be used effectively. K28/SEK8

 

N/A

 

(Software Engineer) Innovation and Response
S20 S21

Describes how they respond to changing priorities and problems arising within software engineering projects by making revised recommendations, and adapting plans as necessary, to fit the scenario being investigated. (S20/SES5)

Explains how they determine, refine, adapt and use appropriate software engineering methods, approaches and techniques to evaluate software engineering project outcomes. (S21/SES6)

 

Demonstrates how their actions have influenced the creation of appropriate plans within teams and contributed to project outcomes. (S20/SES5)

 

Compares and contrasts how they respond to changing priorities and problems arising within software engineering projects by making revised recommendations, and adapting plans as necessary, to fit the scenario being investigated. (S20/SES5)

 

(Software Engineer) Legal, Ethics and Landscape
S23

Describes how they extend and update software development knowledge with evidence from professional and academic sources by undertaking appropriate research to inform best practice and lead improvements in the organisation. (S23/SES8)

 

N/A

 

(IT Consultant) Underlying Principles
K30 K31 K34 K35 K36

Explains how consulting interfaces with project management, business analysis and business management. (K30/ITK2)

Explains the principles of change management within organisations. (K31/ITK3)

Compares and contrasts approaches to analytical and critical thinking to define business problems objectively and create value for the client. (K32/ITK6)

Describes questioning strategies and active listening to ensure all requirements are gathered. (K35/ITK7)

Explains the ethical and legal requirements in client/provider relationships. (K36/ITK8)

 

N/A

(IT Consultant) Innovation and Response
S25 S27

Evaluates how they effectively communicate value add to the client through a variety of media in a professional setting through performing socio-technical process improvements in a range of environments. (S25/ITS2)

Explain how they participate in walk-throughs for IT, to identify, document and evaluate key risks within a client’s organisation. (S27/ITS4)

 

Compares and contrasts how they effectively communicate value add to the client through a variety of media in a professional setting through performing socio-technical process improvements in a range of environments. (S25/ITS2)

Critically evaluates how they participate in walk-throughs for IT, to identify, document and evaluate key risks within a client’s organisation. (S27/ITS4)

 

(IT Consultant) Technical Solutions
S29

Evaluates how they effect change within an organisation through evaluation of a new system, process or initiative. (S29/ITS6)

N/A

(Business Analyst) Legal, Ethics and Landscape
K41 K42 S33

Explains legislation and industry standards relevant to the organisation and sector. (K41/BAK5)

Describes the purpose and value of quality assurance techniques. (K42/BAK6)

Explains how they conduct Process Analysis, Definition, Mapping and Modelling within a business situation without supervision. (S33/BAS2)

 

N/A

(Business Analyst) Technical Solutions
K38 K43 S37

Evaluate approaches to Requirements Life Cycle Management including how to manage and maintain requirements and design information from inception to retirement of a product. (K38/BAK2)

Evaluate a range of Business Analysis investigative techniques. (K43/BAK7)

Explains how they use products of analysis in the design and development of a system. (S37/BAS6)

 

N/A

(Business Analyst) Innovation and Response
K39 S35

Explains how they use tools and benchmarking to support modelling and requirements gathering and recommend approaches to team members as required. (S35/BAS4)

Explains the principles of Strategy Analysis, including how to identify the business need, address that need, and align the change strategy within the organisation. (K39/BAK3)

 

Critically evaluates how they use tools and benchmarking to support modelling and requirements gathering and recommend approaches to team members as required. (S35/BAS4)

(Cyber Security Analyst) Legal, Ethics and Landscape
K46 K48 K50 S45

Explains the principles of quantitative and qualitative risk management theory including the role of risk stakeholders. (K46/CSK2)

Describes the key legislative frameworks and the regulatory landscape for cyber security. (K48/CSK4)

Explains the ethical principles and codes of good practice of at least one significant cyber security professional body and the ethical responsibilities of a cyber security professional. (K50/CSK6)

Describes how they lead cyber security awareness campaigns and evaluate their effectiveness.(S45/CSS6)

 

N/A

(Cyber Security Analyst) Technical Solutions
K47 K49 S41 S43

Evaluates concepts and approaches to cyber security assurance. (K47/CSK3)

Evaluates approaches to incident response and management including escalation and investigation of cyber security breaches and their root cause. (K49/CSK5)

Explains how they undertake security risk assessments for complex systems without direct supervision and propose a remediation strategy relevant to the context of the organisation. (S41/CSS2)

Explains how they manage cyber security risk. (S43/CSS4)

 

Critically evaluates how they undertake security risk assessments for complex systems without direct supervision and propose a remediation strategy relevant to the context of the organisation. (S41/CSS2)

Critically evaluates how they manage cyber security risk. (S43/CSS4)

 

(Data Analyst) Underlying Principles
K53 K55 K57

Describes the barriers that exist to effective data analysis between analysts and their stakeholders and how to avoid or resolve these. (K53/DAK1)

Explains data formats, structures, architectures and data delivery methods including “unstructured” data. (K55/DAK3) 

Explains approaches to data processing and storage, database systems, data warehousing and online analytical processing, data-driven decision making and the good use of evidence and analytics in making choices and decisions. (K57/DAK5)

 

 

N/A

(Data Analyst) Technical Solutions
K59

Describes how Data Analytics can be applied to improve an organisation’s processes, operations and outputs. (K59/DAK7)

Evaluates how data analytics can be applied to improve an organisation’s processes, operations and outputs. (K59/DAK7)

(Data Analyst) Legal, Ethics and Landscape
K60

Describes how data and analysis may exhibit biases and prejudice.  Describes how ethics and compliance affect Data Analytics work, and the impact of international regulations. (K60/DAK8) 

N/A

(Data Analyst) Innovation and Response
S48 S49 S51

Describes how they define Data Requirements and perform Data Collection, Data Processing and Data Cleansing. (S48/DAS1)

Describes how they apply different types of Data Analysis, as appropriate, to drive improvements for specific business problems. (S49/DAS2)

Describes how they have encountered barriers to effective analysis both by analysts and their stakeholders within data analysis projects. (S51/DAS4)

 

Evaluates how they define Data Requirements and perform Data Collection, Data Processing and Data Cleansing. (S48/DAS1)

Evaluates how they apply different types of Data Analysis, as appropriate, to drive improvements for specific business problems. (S49/DAS2)

Evaluates how they identify barriers to effective analysis encountered both by analysts and their stakeholders within data analysis projects. (S51/DAS4)

 

(Network Engineer) Technical Solutions
K63 K67 K68 S58 S61

Explains the benefits and risks of cloud computing and the common integration deployments (private, public, hybrid) including the benefits and risks of virtualisation as a concept; key features of virtualisation and current cloud platforms available. (K63/NEK3)

Explains Software Defined Networking and Network Function Virtualisation Core Principles. (K67/NEK7)

Describe the key elements of mobile networks including some specific key functions and communication concepts. (K68/NEK8)

Explains how they undertake network performance monitoring, including capacity management and auditing of IP addressing. (S58/NES3)

Explains how they secure network systems, apply security policies, access and firewalls. (S61/NES6)

 

Critically provide a comparative analysis between different cloud models stating their risks, strengths and weaknesses, considering their organisational needs. (K63/NEK3)

Critically evaluates how they undertake network performance monitoring, including capacity management and auditing of IP addressing. (S58/NES3)

(Network Engineer) Underlying Principles
K64 K65

Describe key factors that affect network performance and provide some mitigation strategies to increase quality of service. (K64/NEK4)

Explains the principles of failure modes in protocols and how they could be addressed. (K65/NEK5)

 

N/A

(Network Engineer) Innovation and Response
S59

Explain approaches for investigating, troubleshooting and resolving network faults. (S59/NES4)

Compare and contrast approaches for investigating, troubleshooting and resolving network faults. (S59/NES4)

Overall EPA grading

Performance in the EPA determines the apprenticeship grade of:

    • fail
    • pass
    • merit
    • distinction

An independent assessor must individually grade the: project report with presentation, questions and answers and professional discussion underpinned by a portfolio in line with this EPA plan.

The EPAO must combine the individual assessment method grades to determine the overall EPA grade.

If the apprentice fails one or more assessment methods, they will be awarded an overall fail. 

To achieve an overall pass, the apprentice must achieve at least a pass in all the assessment methods. To achieve an overall EPA merit, the apprentice must achieve a pass in either assessment method and a distinction in the remaining method. To achieve an overall EPA distinction, the apprentice must achieve a distinction in both assessment methods.

Grades from individual assessment methods must be combined in the following way to determine the grade of the EPA overall.

Project report with presentation, questions and answers Professional discussion underpinned by a portfolio Overall Grading
Fail Any grade Fail
Any grade Fail Fail
Pass Pass Pass
Pass Distinction Merit
Distinction Pass Merit
Distinction Distinction Distinction

Re-sits and re-takes

If the apprentice fails one or more assessment methods they can take a re-sit or a re-take at their employer’s discretion. The apprentice’s employer needs to agree that a re-sit or re-take is appropriate. A re-sit does not need further learning, whereas a re-take does.

The apprentice should have a supportive action plan to prepare for a re-sit or a re-take.

The employer and EPAO agree the timescale for a re-sit or re-take. A re-sit is typically taken within 3 months of the EPA outcome notification. The timescale for a re-take is dependent on how much re-training is required and is typically taken within 6 months of the EPA outcome notification.

If the apprentice fails the project assessment method, they must to amend the project output in line with the independent assessor’s feedback. The apprentice will be given 4 weeks to rework and submit the amended report.

Failed assessment methods must be re-sat or re-taken within a 6-month period from the EPA outcome notification, otherwise the entire EPA will need to be re-sat or re-taken in full.

Re-sits and re-takes are not offered to an apprentice wishing to move from pass to a higher grade.

The apprentice will get a maximum EPA grade of merit for a re-sit or re-take, unless the EPAO determines there are exceptional circumstances.

Roles and responsibilities

Roles Responsibilities

Apprentice

As a minimum, the apprentice should:

  • participate in and complete on-programme training to meet the KSBs as outlined in the occupational standard for a minimum of 12 months
  • complete the required amount of off-the-job training specified by the apprenticeship funding rules and as arranged by the employer and training provider
  • understand the purpose and importance of EPA
  • meet the gateway requirements 
  • undertake the EPA  

 

Employer

As a minimum, the apprentice's employer must:

  • select the EPAO and training provider 
  • work with the training provider (where applicable) to support the apprentice in the workplace and to provide the opportunities for the apprentice to develop the KSBs
  • arrange and support off-the-job training to be undertaken by the apprentice 
  • decide when the apprentice is working at or above the occupational standard and is ready for EPA 
  • ensure that supporting evidence required at the gateway is submitted in line with this EPA plan 
  • liaise with the training provider and EPAO to ensure the EPA is booked in a timely manner

Post-gateway, the employer must: 

  • confirm arrangements with the EPAO for the EPA (who, when, where) in a timely manner (including providing access to any employer-specific documentation as required, for example company policies)
  • ensure that the EPA is scheduled with the EPAO for a date and time which allows the opportunity for the apprentice to be assessed against the KSBs 
  • remain independent from the delivery of the EPA
  • ensure the apprentice is given sufficient time away from regular duties to prepare for, and complete all post-gateway elements of the EPA, and that any required supervision during this time (as stated within this EPA plan) is in place
  • where the apprentice is assessed in the workplace, ensure that the apprentice has access to the resources used on a regular basis 
  • pass the certificate to the apprentice upon receipt from the EPAO

EPAO

As a minimum, the EPAO must:  

  • conform to the requirements of this EPA plan and deliver its requirements in a timely manner 
  • conform to the requirements of the register of end-point assessment organisations (RoEPAO) 
  • conform to the requirements of the external quality assurance provider (EQAP) for this apprenticeship 
  • understand the occupational standard 
  • make the EPA contractual arrangements, including agreeing the price of the EPA 
  • develop and produce assessment materials as detailed for each assessment method in this EPA plan 
  • appoint qualified and competent independent assessors in line with the requirements of this EPA plan to conduct assessments and oversee their working 
  • appoint administrators (and invigilators where required) to administer the EPA  
  • provide training for independent assessors in terms of good assessment practice, operating the assessment tools and grading 
  • provide information, advice, guidance and documentation to enable apprentices, employers and training providers to prepare for the EPA 
  • confirm all gateway requirements have been met as quickly as possible 
  • arrange for the EPA to take place, in consultation with the employer 
  • ensure that the apprentice has access to the required resources and liaise with the employer to agree this if necessary, where the apprentice is not assessed in the workplace 
  • develop and provide assessment recording documentation to ensure a clear and auditable process is in place for providing assessment decisions and feedback to stakeholders 
  • have no direct connection with the apprentice, their employer or training provider in all instances; there must be no conflict of interest 
  • have policies and procedures for internal quality assurance (IQA), and maintain records of IQA activity and moderation for external quality assurance (EQA) purposes 
  • deliver induction training for independent assessors, and for invigilators and markers (where used) 
  • undertake standardisation activity on this apprenticeship for an independent assessor before they conduct an EPA for the first time, if the EPA is updated and periodically (a minimum of annually) 
  • manage invigilation of the apprentice to maintain security of the assessment in line with the EPAO’s malpractice policy 
  • verify the identity of the apprentice  
  • use language in the development and delivery of the EPA that is appropriate to the level of the occupational standard 

Independent assessor

As a minimum, an independent assessor must: 

  • have the competence to assess the apprentice at the level of this apprenticeship and hold any required qualifications and experience in line with the requirements of the independent assessor as detailed in the IQA section of this EPA plan 
  • understand the occupational standard and the requirements of this EPA 
  • have, maintain and be able to evidence, up-to-date knowledge and expertise of the occupation 
  • deliver the end-point assessment in-line with this EPA plan 
  • comply with the IQA requirements of the EPAO 
  • have no direct connection or conflict of interest with the apprentice, their employer or training provider; in all instances; there must be no conflict of interest 
  • attend induction training 
  • attend standardisation events when they start working for the EPAO, before they conduct an EPA for the first time and a minimum of annually for this apprenticeship  
  • assess each assessment method, as determined by the EPA plan  
  • assess the KSBs assigned to each assessment method, as shown in the mapping of KSBs to assessment methods in this EPA plan  
  • make the grading decisions 
  • record and report assessment outcome decisions, for each apprentice, following instructions and using assessment recording documentation provided by the EPAO, in a timely manner 
  • use language in the development and delivery of the EPA that is appropriate to the level of the occupational standard 
  • mark open (constructed) test answers accurately according to the EPAO’s mark scheme and procedures 

Training provider

As a minimum, the training provider must: 

  • work with the employer and support the apprentice during the off-the-job training to provide the opportunities to develop the KSBs as listed in the occupational standard 
  • conduct training covering the KSBs agreed as part of the Commitment Statement or the Individual Learning Plan 
  • monitor the apprentice’s progress during any training provider led on-programme learning 
  • advise the employer, upon request, on the apprentice’s readiness for EPA 
  • remain independent from the delivery of the EPA 

Reasonable adjustments

The EPAO must have reasonable adjustments arrangements for the EPA.

This should include:

  • how an apprentice qualifies for reasonable adjustment
  • what reasonable adjustments may be made

Adjustments must maintain the validity, reliability and integrity of the EPA as outlined in this EPA plan.

Internal quality assurance

Internal quality assurance refers to how the EPAO ensures valid, consistent and reliable EPA decisions. The EPAO must adhere to the requirements within the roles and responsibilities section:

The EPAO must also:

  • have quality assurance systems and procedures that ensure fair, reliable and consistent EPA regardless of employer, place, time or independent assessor
  • appoint independent assessors who are competent to deliver the EPA and who:
    • have recent relevant experience of the occupation or sector to at least occupational level 6 gained in the last 3 years or significant experience of the occupation or sector
  • operate induction training for anyone involved in the delivery or assessment of the EPA
  • provide training for independent assessors in good assessment practice, operating the assessment tools and making grading decisions
  • provide ongoing training for markers and invigilators
  • provide standardisation activity for this apprenticeship standard for all independent assessors:
    • before they conduct an EPA for the first time
    • if the EPA is updated
    • periodically as appropriate (a minimum of annually)
  • conduct effective moderation of EPA decisions and grades
  • conduct appeals where required, according to the EPAO’s appeals procedure, reviewing and making final decisions on EPA decisions and grades
  • have no direct connection with the apprentice, their employer or training provider.

Value for money

Affordability of the EPA will be aided by using at least some of the following:

  • utilising digital remote platforms to conduct applicable assessment methods
  • using the employer’s premises
  • conducting assessment methods on the same day

Professional recognition

This apprenticeship aligns with:

British Computer Society for Registered IT Technician (RITTech)

Mapping of KSBs to assessment methods

Knowledge Assessment methods
K1: Core.

How organisations adapt and exploit digital technology solutions to gain a competitive advantage.

Back to Grading
Project report with presentation, questions and answers
K2: Core.

The principles of strategic decision making concerning the acquisition or development of digital and technology solutions. For example business architecture approaches such as capability models and target operating models.

Back to Grading
Project report with presentation, questions and answers
K3: Core.

Principles of estimating the risks and opportunities of digital and technology solutions.

Back to Grading
Project report with presentation, questions and answers
K4: Core.

Techniques and approaches involved in creating a business case for new digital and technology solutions. For example journey, product and capability mapping and value chains.

Back to Grading
Project report with presentation, questions and answers
K5: Core.

A range of digital technology solution development techniques and tools.

Back to Grading
Project report with presentation, questions and answers
K6: Core.

The approaches and techniques used throughout the digital and technology solution lifecycle and their applicability to an organisation’s standards and pre-existing tools.

Back to Grading
Professional discussion underpinned by a portfolio
K7: Core.

The roles, functions and activities within digital technology solutions within an organisation.

Back to Grading
Professional discussion underpinned by a portfolio
K8: Core.

How teams work effectively to produce digital and technology solutions.

Back to Grading
Professional discussion underpinned by a portfolio
K9: Core.

The concepts and principles of leadership.

Back to Grading
Professional discussion underpinned by a portfolio
K10: Core.

Management techniques and theories. For example, effective decision making, delegation and planning methods, time management and change management.

Back to Grading
Professional discussion underpinned by a portfolio
K11: Core.

The nature and scope of common vulnerabilities in digital and technology solutions. For example, the risks of unsecure coding and unprotected networks.

Back to Grading
Professional discussion underpinned by a portfolio
K12: Core.

The role of data management systems within Digital and Technology Solutions.

Back to Grading
Professional discussion underpinned by a portfolio
K13: Core.

Principles of data analysis for digital and technology solutions.

Back to Grading
Professional discussion underpinned by a portfolio
K14: Core.

A range of quantitative and qualitative data gathering methods and how to appraise and select the appropriate method.

Back to Grading
Professional discussion underpinned by a portfolio
K15: Core.

Principles of estimating cost, and time resource constraints within digital and technology solutions activities.

Back to Grading
Project report with presentation, questions and answers
K16: Core.

Fundamental computer networking concepts in relation to digital and technology solutions. For example, structure, cloud architecture, components, quality of service.

Back to Grading
Professional discussion underpinned by a portfolio
K17: Core.

Reporting techniques, including how to synthesise information and present concisely, as appropriate to the target audience.

Back to Grading
Project report with presentation, questions and answers
K18: Core.

Techniques of robust research and evaluation for the justification of digital and technology solutions.

Back to Grading
Project report with presentation, questions and answers
K19: Core.

Relevant legal, ethical, social and professional standards to a digital and technology solution. For example, Diversity, Accessibility, Intellectual Property, Data Protection Acts, Codes of Practice, Regulatory and Compliance frameworks.

Back to Grading
Professional discussion underpinned by a portfolio
K20: Core.

Sustainable development approaches as applied to digital and technology solutions such as green computing.

Back to Grading
Professional discussion underpinned by a portfolio
K21: Software engineering professional.

How to operate at all stages of the software development life cycle and how each stage is applied in a range of contexts. For example, requirements analysis, design, development, testing, implementation.

Back to Grading
Professional discussion underpinned by a portfolio
K22: Software engineering professional.

Principles of a range of development techniques, for each stage of the software development cycle that produce artefacts and the contexts in which they can be applied. For example UML, unit testing, programming, debugging, frameworks, architectures.

Back to Grading
Professional discussion underpinned by a portfolio
K23: Software engineering professional.

Principles of a range of development methods and approaches and the contexts in which they can be applied. For example Scrum, Extreme Programming, Waterfall, Prince2, TDD.

Back to Grading
Professional discussion underpinned by a portfolio
K24: Software engineering professional.

How to interpret and implement a design, compliant with functional, non-functional and security requirements including principles and approaches to addressing legacy software development issues from a technical and socio-technical perspective. For example architectures, languages, operating systems, hardware, business change.

Back to Grading
Professional discussion underpinned by a portfolio
K25: Software engineering professional.

The factors affecting product quality and approaches for how to control them throughout the development process. For example security, code quality, coding standards.

Back to Grading
Project report with presentation, questions and answers
K26: Software engineering professional.

How to select and apply a range of software tools used in Software Engineering.

Back to Grading
Project report with presentation, questions and answers
K27: Software engineering professional.

Approaches to the interpretation and use of artefacts. For example UML, unit tests, architecture.

Back to Grading
Project report with presentation, questions and answers
K28: Software engineering professional.

Approaches to effective team work and the range of software development tools supporting effective teamwork. For example, configuration management, version control and release management.

Back to Grading
Professional discussion underpinned by a portfolio
K29: IT consultant professional.

Principles of different consulting methodologies. For example issue-based, and hypothesis based.

Back to Grading
Project report with presentation, questions and answers
K30: IT consultant professional.

How consulting interfaces with project management, business analysis and business management.

Back to Grading
Professional discussion underpinned by a portfolio
K31: IT consultant professional.

Principles of change management within organisations.

Back to Grading
Professional discussion underpinned by a portfolio
K32: IT consultant professional.

The barriers to solving digital and technology problems or maximising opportunities.

Back to Grading
Project report with presentation, questions and answers
K33: IT consultant professional.

Approaches to presenting recommendations to stakeholders and influencing action.

Back to Grading
Project report with presentation, questions and answers
K34: IT consultant professional.

Approaches to analytical and critical thinking to define business problems objectively and create value for the client.

Back to Grading
Professional discussion underpinned by a portfolio
K35: IT consultant professional.

Questioning strategies and active listening to ensure all requirements are gathered.

Back to Grading
Professional discussion underpinned by a portfolio
K36: IT consultant professional.

The ethical and legal requirements in client and provider relationships.

Back to Grading
Professional discussion underpinned by a portfolio
K37: Business analyst professional.

Elicitation and Collaboration approaches, including how to prepare for and conduct elicitation activities and confirm the results.

Back to Grading
Project report with presentation, questions and answers
K38: Business analyst professional.

Approaches to Requirements Life Cycle Management including how to manage and maintain requirements and design information from inception to retirement of a product.

Back to Grading
Professional discussion underpinned by a portfolio
K39: Business analyst professional.

Principles of Strategy Analysis, including how to identify the business need, address that need, and align the change strategy within the organisation.

Back to Grading
Professional discussion underpinned by a portfolio
K40: Business analyst professional.

Solution Evaluation, including how to assess the performance of and value delivered by a solution and to recommend improvements on increasing values.

Back to Grading
Project report with presentation, questions and answers
K41: Business analyst professional.

Legislation and industry standards relevant to Business Analysis in the organisation and sector.

Back to Grading
Professional discussion underpinned by a portfolio
K42: Business analyst professional.

The purpose and value of quality assurance techniques.

Back to Grading
Professional discussion underpinned by a portfolio
K43: Business analyst professional.

A range of Business Analysis investigative techniques.

Back to Grading
Professional discussion underpinned by a portfolio
K44: IT consultant professional,Business analyst professional.

Approaches to change control and requirements management.

Back to Grading
Project report with presentation, questions and answers
K45: Cyber security professional .

Principles of cyber security tools and techniques.

Back to Grading
Project report with presentation, questions and answers
K46: Cyber security professional .

Principles of quantitative and qualitative risk management theory including the role of risk stakeholders.

Back to Grading
Professional discussion underpinned by a portfolio
K47: Cyber security professional .

Concepts and approaches to cyber security assurance.

Back to Grading
Professional discussion underpinned by a portfolio
K48: Cyber security professional .

Key legislative frameworks and the regulatory landscape for cyber security including Data Protection Act 2018 , Network Information System Directive 2018, Regulation of Investigatory Powers Act 2000, ISO 27001.

Back to Grading
Professional discussion underpinned by a portfolio
K49: Cyber security professional .

Approaches to incident response and management including escalation and investigation of cyber security breaches and their root cause.

Back to Grading
Professional discussion underpinned by a portfolio
K50: Cyber security professional .

Ethical principles and codes of good practice of at least one significant cyber security professional body and the ethical responsibilities of a cyber security professional.

Back to Grading
Professional discussion underpinned by a portfolio
K51: Cyber security professional .

Principles of common security architectures and methodologies.

Back to Grading
Project report with presentation, questions and answers
K52: Cyber security professional .

Approaches to deployment of cyber security technology components in digital systems to provide security functionality. For example hardware and software to implement security controls.

Back to Grading
Project report with presentation, questions and answers
K53: Computing data analyst professional.

The barriers that exist to effective data analysis between analysts and their stakeholders and how to avoid or resolve these.

Back to Grading
Professional discussion underpinned by a portfolio
K54: Computing data analyst professional.

How to critically analyse, interpret and evaluate complex information from diverse datasets.

Back to Grading
Project report with presentation, questions and answers
K55: Computing data analyst professional.

Data formats, structures, architectures and data delivery methods including “unstructured” data.

Back to Grading
Professional discussion underpinned by a portfolio
K56: Computing data analyst professional.

Sources of data such as files, operational systems, databases, web services, open data, government data, news and social media.

Back to Grading
Project report with presentation, questions and answers
K57: Computing data analyst professional.

Approaches to data processing and storage, database systems, data warehousing and online analytical processing, data-driven decision making and the good use of evidence and analytics in making choices and decisions.

Back to Grading
Professional discussion underpinned by a portfolio
K58: Computing data analyst professional.

How Data Analytics operates within the context of data governance, data security, and communications.

Back to Grading
Project report with presentation, questions and answers
K59: Computing data analyst professional.

How Data Analytics can be applied to improve an organisation’s processes, operations and outputs.

Back to Grading
Professional discussion underpinned by a portfolio
K60: Computing data analyst professional.

How data and analysis may exhibit biases and prejudice. How ethics and compliance affect Data Analytics work, and the impact of international regulations. For example, General Data Protection Regulation, Data Protection Act 2018.

Back to Grading
Professional discussion underpinned by a portfolio
K61: Network engineering professional.

The role and function of virtual or physical network components and functions and typical topologies and service architectures.

Back to Grading
Project report with presentation, questions and answers
K62: Network engineering professional.

The main network protocols in use, their purpose, features and relationship to each other. For example, Ethernet, IP (Internet Protocol), TCP (Transmission Control Protocol), OSPF (Open Shortest Path First).

Back to Grading
Project report with presentation, questions and answers
K63: Network engineering professional.

The benefits and risks of cloud computing and the common integration deployments (private, public, hybrid). Including the benefits and risks of virtualisation as a concept; key features of virtualisation and current cloud platforms available.

Back to Grading
Professional discussion underpinned by a portfolio
K64: Network engineering professional.

The main factors that affect network performance, and how to mitigate these on network performance by implementing changes to QoS. For example, Traffic Shaping, Policing, Queuing, Topology (physical and logical), and Network Policy (Traffic Analysis, DPI (Deep Packet Inspection).

Back to Grading
Professional discussion underpinned by a portfolio
K65: Network engineering professional.

Principles of failure modes in protocols. For example, why a protocol may ‘hang’ and the effect of data communication errors and approaches to addressing failures to optimise network performance.

Back to Grading
Professional discussion underpinned by a portfolio
K66: Network engineering professional.

Key security concepts. For example threats, vulnerabilities, exploits, detection and mitigation techniques, and security program elements such as user awareness, physical access control, multi-layer defence models.

Back to Grading
Project report with presentation, questions and answers
K67: Network engineering professional.

SDN (Software Defined Networking) and Network Function Virtualisation Core Principles. For example, Control Plane Separation, flexibility, overlay networks, disassociation of software and hardware layers.

Back to Grading
Professional discussion underpinned by a portfolio
K68: Network engineering professional.

Key elements of mobile networks. For example RAN (Radio Access Network), EPC (Evolved Packet Core), IMS (IP Multimedia Subsystem) including some specific key functions such as S/P/U-Gateways and the concepts in communicating over free-space media such as interference, ground bounce, encryption and in mobile endpoint platforms such as tracking user location and roaming.

Back to Grading
Professional discussion underpinned by a portfolio
Skill Assessment methods
S1: Core.

Analyse a business problem to identify the role of digital and technology solutions.

Back to Grading
Project report with presentation, questions and answers
S2: Core.

Identify risks, determine mitigation strategies and opportunities for improvement in a digital and technology solutions project.

Back to Grading
Project report with presentation, questions and answers
S3: Core.

Analyse a business problem in order to specify an appropriate digital and technology solution.

Back to Grading
Project report with presentation, questions and answers
S4: Core.

Initiate, design, code, test and debug a software component for a digital and technology solution.

Back to Grading
Professional discussion underpinned by a portfolio
S5: Core.

Apply relevant standard processes, methods, techniques and tools. For example, ISO Standards, Waterfall, Agile in a digital and technology solution project.

Back to Grading
Project report with presentation, questions and answers
S6: Core.

Manage digital and technology solutions projects. For example, identifying and resolving deviations from specification, applying appropriate Project Management methodologies.

Back to Grading
Project report with presentation, questions and answers
S7: Core.

Work effectively within teams, leading on appropriate digital technology solution activities.

Back to Grading
Professional discussion underpinned by a portfolio
S8: Core.

Apply relevant organisational theories. For example, change management principles, marketing approaches, strategic practice, and IT service management to a digital and technology solutions project.

Back to Grading
Professional discussion underpinned by a portfolio
S9: Core.

Apply relevant security and resilience techniques to a digital and technology solution. For example, risk assessments, mitigation strategies.

Back to Grading
Professional discussion underpinned by a portfolio
S10: Core.

Initiate, design, implement and debug a data product for a digital and technology solution.

Back to Grading
Professional discussion underpinned by a portfolio
S11: Core.

Determine and use appropriate data analysis techniques. For example, Text, Statistical, Diagnostic or Predictive Analysis to assess a digital and technology solutions.

Back to Grading
Professional discussion underpinned by a portfolio
S12: Core.

Plan, design and manage simple computer networks with an overall focus on the services and capabilities that network infrastructure solutions enable in an organisational context.

Back to Grading
Professional discussion underpinned by a portfolio
S13: Core.

Report effectively to colleagues and stakeholders using the appropriate language and style, to meet the needs of the audience concerned.

Back to Grading
Project report with presentation, questions and answers
S14: Core.

Research, investigate, and evaluate innovative technologies or approaches in the development of a digital and technology solution.

Back to Grading
Project report with presentation, questions and answers
S15: Core.

Apply relevant legal, ethical, social and professional standards to a digital and technology solution.

Back to Grading
Professional discussion underpinned by a portfolio
S16: Software engineering professional.

Identify and define software engineering problems that are non-routine and incompletely specified.

Back to Grading
Project report with presentation, questions and answers
S17: Software engineering professional.

Provide recommendations as to the most appropriate software engineering solution.

Back to Grading
Project report with presentation, questions and answers
S18: Software engineering professional.

Use appropriate analysis methods, approaches and techniques in software engineering projects to deliver an outcome that meets requirements.

Back to Grading
Project report with presentation, questions and answers
S19: Software engineering professional.

Implement software engineering projects using appropriate software engineering methods, approaches and techniques.

Back to Grading
Project report with presentation, questions and answers
S20: Software engineering professional.

Respond to changing priorities and problems arising within software engineering projects by making revised recommendations, and adapting plans as necessary, to fit the scenario being investigated.

Back to Grading
Professional discussion underpinned by a portfolio
S21: Software engineering professional.

Determine, refine, adapt and use appropriate software engineering methods, approaches and techniques to evaluate software engineering project outcomes.

Back to Grading
Professional discussion underpinned by a portfolio
S22: Software engineering professional.

Evaluate learning points arising from software engineering work undertaken on a project including use of methods, analysis undertaken, selection of approach and the outcome achieved, in order to identify both lessons learnt and recommendations for improvements to future projects.

Back to Grading
Project report with presentation, questions and answers
S23: Software engineering professional.

Extend and update software development knowledge with evidence from professional and academic sources by undertaking appropriate research to inform best practice and lead improvements in the organisation.

Back to Grading
Professional discussion underpinned by a portfolio
S24: IT consultant professional.

Analyse client needs and determine how to advise them strategically through improved business processes, new ideas, or technology solutions.

Back to Grading
Project report with presentation, questions and answers
S25: IT consultant professional.

Effectively communicate value add to the client through a variety of media. For example, presentations, written reports, Storytelling in a professional setting through performing socio-technical process improvements in a range of environments.

Back to Grading
Professional discussion underpinned by a portfolio
S26: IT consultant professional.

Make evidence based recommendations taking into account risks, costs, and benefits.

Back to Grading
Project report with presentation, questions and answers
S27: IT consultant professional.

Participate in walk-throughs for Information Technologies, to identify, document and evaluate key risks within a client’s organisation.

Back to Grading
Professional discussion underpinned by a portfolio
S28: IT consultant professional.

Perform stakeholder analysis to identify, determine and deepen understanding of system requirements and develop client relationships.

Back to Grading
Project report with presentation, questions and answers
S29: IT consultant professional.

Effect change within an organisation through evaluation of a new system, process or initiative.

Back to Grading
Professional discussion underpinned by a portfolio
S30: IT consultant professional.

Ensure legal and ethical requirements are accommodated in the development of digital and technology solutions.

Back to Grading
Project report with presentation, questions and answers
S31: IT consultant professional.

Evaluate the  success of new systems, processes, or initiatives.

Back to Grading
Project report with presentation, questions and answers
S32: Business analyst professional.

Use requirements elicitation, analysis and documentation to produce an acceptable solution for business problems or further opportunities.

Back to Grading
Project report with presentation, questions and answers
S33: Business analyst professional.

Conduct Process Analysis, Definition, Mapping and Modelling within a business situation without supervision.

Back to Grading
Professional discussion underpinned by a portfolio
S34: Business analyst professional.

Produce Use Cases which are of value to all stakeholders of a system.

Back to Grading
Project report with presentation, questions and answers
S35: Business analyst professional.

Use tools and benchmarking to support modelling and requirements gathering and recommend approaches to team members as required.

Back to Grading
Professional discussion underpinned by a portfolio
S36: Business analyst professional.

Produce a business case to scope a proposed project including business benefits and recommendations.

Back to Grading
Project report with presentation, questions and answers
S37: Business analyst professional.

Use products of analysis in the design and development of a system.

Back to Grading
Professional discussion underpinned by a portfolio
S38: Business analyst professional.

Evaluate the impacts of model selection and how they inter-relate with each other when generating business analytics.

Back to Grading
Project report with presentation, questions and answers
S39: Business analyst professional.

Recommend and use appropriate software tools to implement Business Analysis tasks and outcomes.

Back to Grading
Project report with presentation, questions and answers
S40: Cyber security professional .

Discover, identify and analyse security threats, attack techniques and vulnerabilities and recommend mitigation and security controls.

Back to Grading
Project report with presentation, questions and answers
S41: Cyber security professional .

Undertake security risk assessments for complex systems without direct supervision and propose a remediation strategy relevant to the context of the organisation.

Back to Grading
Professional discussion underpinned by a portfolio
S42: Cyber security professional .

Recommend improvements to the cyber security approaches of an organisation based on research into future potential cyber threats and considering threat trends.

Back to Grading
Project report with presentation, questions and answers
S43: Cyber security professional .

Manage cyber security risk.

Back to Grading
Professional discussion underpinned by a portfolio
S44: Cyber security professional .

Use appropriate cyber security technology, tools and techniques in relation to the risks identified.

Back to Grading
Project report with presentation, questions and answers
S45: Cyber security professional .

Lead cyber security awareness campaigns and evaluate their effectiveness.

Back to Grading
Professional discussion underpinned by a portfolio
S46: Cyber security professional .

Analyse cyber security requirements against other design requirements for systems or products, identify conflicting requirements and recommend appropriate solutions with clear explanation of costs and benefits.

Back to Grading
Project report with presentation, questions and answers
S47: Cyber security professional .

Lead the design and build of systems in accordance with a security case to address organisational challenges.

Back to Grading
Project report with presentation, questions and answers
S48: Computing data analyst professional.

Define Data Requirements and perform Data Collection, Data Processing and Data Cleansing.

Back to Grading
Professional discussion underpinned by a portfolio
S49: Computing data analyst professional.

Apply different types of Data Analysis, as appropriate, to drive improvements for specific business problems.

Back to Grading
Professional discussion underpinned by a portfolio
S50: Computing data analyst professional.

Find, present, communicate and disseminate data analysis outputs effectively and with high impact through creative storytelling, tailoring the message for the audience. Visualise data to tell compelling and actionable narratives by using the best medium for each audience, such as charts, graphs and dashboards.

Back to Grading
Project report with presentation, questions and answers
S51: Computing data analyst professional.

Identify barriers to effective analysis encountered both by analysts and their stakeholders within data analysis projects.

Back to Grading
Professional discussion underpinned by a portfolio
S52: Computing data analyst professional.

Apply a range of techniques for analysing quantitative data such as data mining, time series forecasting, algorithms, statistics and modelling techniques to identify and predict trends and patterns in data.

Back to Grading
Project report with presentation, questions and answers
S53: Computing data analyst professional.

Apply exploratory or confirmatory approaches to analysing data. Validate and and test stability of the results.

Back to Grading
Project report with presentation, questions and answers
S54: Computing data analyst professional.

Extract data from a range of sources. For example, databases, web services, open data.

Back to Grading
Project report with presentation, questions and answers
S55: Computing data analyst professional.

Analyse in detail large data sets, using a range of industry standard tools and data analysis methods.

Back to Grading
Project report with presentation, questions and answers
S56: Network engineering professional.

Identify and collate stakeholder needs in relation to computer network requirements, plans and designs.

Back to Grading
Project report with presentation, questions and answers
S57: Network engineering professional.

Plan, design, document, and develop the relevant elements of a computer network within an organisation or between organisations, taking into account customer requirements (performance, scale), constraints (budget, equipment availability), and define policies for their use.

Back to Grading
Project report with presentation, questions and answers
S58: Network engineering professional.

Monitor performance and ensure networks are configured correctly and perform as expected by designers or architects. Undertake capacity management and audit of IP addressing and hosted devices.

Back to Grading
Professional discussion underpinned by a portfolio
S59: Network engineering professional.

Investigate, troubleshoot and resolve data network faults in local and wide area environments, using information from multiple sources, Physically or Remotely by console connection. Recommend and implement short term fixes to restore service and, or, quality of experience and recommend longer term changes to prevent recurrence or reduce impact of future occurrences.

Back to Grading
Professional discussion underpinned by a portfolio
S60: Network engineering professional.

Implement computer networks from a design including testing and validation. This includes populating variables in configurations, for example, IP addresses and subsequent application of configuration to equipment such as routers, switches, firewalls.

Back to Grading
Project report with presentation, questions and answers
S61: Network engineering professional.

Secure network systems by establishing and enforcing policies, and defining and monitoring access. Support and administer firewall environments in line with IT security policy.

Back to Grading
Professional discussion underpinned by a portfolio
S62: Network engineering professional.

Research and evaluate emerging network technologies and assess relevance to current network requirements. Provide an objective opinion on how new features and technologies may be incorporated as required by the organisation.

Back to Grading
Project report with presentation, questions and answers
S63: Network engineering professional.

Investigate security concerns or attacks. For example, Distributed Denial of Service (DDOS), port scanning, assessing key metrics and indicators, evidencing the chosen steps to mitigate.

Back to Grading
Project report with presentation, questions and answers
Behaviour Assessment methods
B1: Core.

Has a strong work ethic and commitment in order to meet the standards required.

Back to Grading
Professional discussion underpinned by a portfolio
B2: Core.

Reliable, objective and capable of both independent and team working.

Back to Grading
Professional discussion underpinned by a portfolio
B3: Core.

Acts with integrity with respect to ethical, legal and regulatory requirements ensuring the protection of personal data, safety and security.

Back to Grading
Project report with presentation, questions and answers
B4: Core.

Commits to continuous professional development; maintaining their knowledge and skills in relation to developments in digital and technology solutions that influence their work.

Back to Grading
Professional discussion underpinned by a portfolio
B5: Core.

Interacts professionally with people from technical and non-technical backgrounds. Presents data and conclusions in an evidently truthful, concise and appropriate manner.

Back to Grading
Project report with presentation, questions and answers
B6: Core.

Participates in and shares best practice in their organisation, and the wider community for aspects relevant to digital and technology solutions.

Back to Grading
Professional discussion underpinned by a portfolio
B7: Core.

Maintains awareness of trends and innovations in the subject area, utilising a range of academic literature, online sources, community interaction, conference attendance and other methods which can deliver business value.

Back to Grading
Professional discussion underpinned by a portfolio
B8: Core.

Champions diversity and inclusion in their work ensuring that digital technology solutions are accessible.

Back to Grading
Professional discussion underpinned by a portfolio

Mapping of KSBs to grade themes

Project report with presentation, questions and answers - Project

KSBS GROUPED BY THEME Knowledge Skills Behaviour
(Core) The Organisational Context
K1 K2

How organisations adapt and exploit digital technology solutions to gain a competitive advantage. (K1)

The principles of strategic decision making concerning the acquisition or development of digital and technology solutions. For example business architecture approaches such as capability models and target operating models. (K2)

N/A

N/A

(Core) Project Requirements

S3
B3

N/A

Analyse a business problem in order to specify an appropriate digital and technology solution. (S3)

Acts with integrity with respect to ethical, legal and regulatory requirements ensuring the protection of personal data, safety and security. (B3)

(Core) Project Planning and Resources
K3 K4 K15
S2 S14

Principles of estimating the risks and opportunities of digital and technology solutions. (K3)

Techniques and approaches involved in creating a business case for new digital and technology solutions. For example journey, product and capability mapping and value chains. (K4)

Principles of estimating cost, and time resource constraints within digital and technology solutions activities. (K15)

Identify risks, determine mitigation strategies and opportunities for improvement in a digital and technology solutions project. (S2)

Research, investigate, and evaluate innovative technologies or approaches in the development of a digital and technology solution. (S14)

N/A

(Core) Solution Proposal

S1

N/A

Analyse a business problem to identify the role of digital and technology solutions. (S1)

N/A

(Core) Project Delivery
K5
S5 S6

A range of digital technology solution development techniques and tools. (K5)

Apply relevant standard processes, methods, techniques and tools. For example, ISO Standards, Waterfall, Agile in a digital and technology solution project. (S5)

Manage digital and technology solutions projects. For example, identifying and resolving deviations from specification, applying appropriate Project Management methodologies. (S6)

N/A

(Core) Project Evaluation
K17 K18
S13
B5

Reporting techniques, including how to synthesise information and present concisely, as appropriate to the target audience. (K17)

Techniques of robust research and evaluation for the justification of digital and technology solutions. (K18)

Report effectively to colleagues and stakeholders using the appropriate language and style, to meet the needs of the audience concerned. (S13)

Interacts professionally with people from technical and non-technical backgrounds. Presents data and conclusions in an evidently truthful, concise and appropriate manner. (B5)

(Software Engineer) Technical Solutions
K25 K26 K27

The factors affecting product quality and approaches for how to control them throughout the development process. For example security, code quality, coding standards. (K25)

How to select and apply a range of software tools used in Software Engineering. (K26)

Approaches to the interpretation and use of artefacts. For example UML, unit tests, architecture. (K27)

N/A

N/A

(Software Engineer) Innovation and Response

S16 S17 S18 S19 S22

N/A

Identify and define software engineering problems that are non-routine and incompletely specified. (S16)

Provide recommendations as to the most appropriate software engineering solution. (S17)

Use appropriate analysis methods, approaches and techniques in software engineering projects to deliver an outcome that meets requirements. (S18)

Implement software engineering projects using appropriate software engineering methods, approaches and techniques. (S19)

Evaluate learning points arising from software engineering work undertaken on a project including use of methods, analysis undertaken, selection of approach and the outcome achieved, in order to identify both lessons learnt and recommendations for improvements to future projects. (S22)

N/A

(IT Consultant) Underlying Principles
K29 K32

Principles of different consulting methodologies. For example issue-based, and hypothesis based. (K29)

The barriers to solving digital and technology problems or maximising opportunities. (K32)

N/A

N/A

(IT Consultant) Innovation and Response
K33
S24 S26 S28

Approaches to presenting recommendations to stakeholders and influencing action. (K33)

Analyse client needs and determine how to advise them strategically through improved business processes, new ideas, or technology solutions. (S24)

Make evidence based recommendations taking into account risks, costs, and benefits. (S26)

Perform stakeholder analysis to identify, determine and deepen understanding of system requirements and develop client relationships. (S28)

N/A

(IT Consultant) Ethics and Landscape

S30

N/A

Ensure legal and ethical requirements are accommodated in the development of digital and technology solutions. (S30)

N/A

(IT Consultant) Technical Solutions

S31

N/A

Evaluate the  success of new systems, processes, or initiatives. (S31)

N/A

(Business Analyst) Technical Solutions

S32 S34

N/A

Use requirements elicitation, analysis and documentation to produce an acceptable solution for business problems or further opportunities. (S32)

Produce Use Cases which are of value to all stakeholders of a system. (S34)

N/A

(Business Analyst) Legal, Ethics and Landscape
K44
S36 S38

Approaches to change control and requirements management. (K44)

Produce a business case to scope a proposed project including business benefits and recommendations. (S36)

Evaluate the impacts of model selection and how they inter-relate with each other when generating business analytics. (S38)

N/A

(Business Analyst) Innovation and Response
K40
S39

Solution Evaluation, including how to assess the performance of and value delivered by a solution and to recommend improvements on increasing values. (K40)

Recommend and use appropriate software tools to implement Business Analysis tasks and outcomes. (S39)

N/A

(Cyber Security Analyst) Underlying Principles
K45 K51

Principles of cyber security tools and techniques. (K45)

Principles of common security architectures and methodologies. (K51)

N/A

N/A

(Cyber Security Analyst) Innovation and Response
K52
S42 S46 S47

Approaches to deployment of cyber security technology components in digital systems to provide security functionality. For example hardware and software to implement security controls. (K52)

Recommend improvements to the cyber security approaches of an organisation based on research into future potential cyber threats and considering threat trends. (S42)

Analyse cyber security requirements against other design requirements for systems or products, identify conflicting requirements and recommend appropriate solutions with clear explanation of costs and benefits. (S46)

Lead the design and build of systems in accordance with a security case to address organisational challenges. (S47)

N/A

(Cyber Security Analyst) Technical Solutions

S40 S44

N/A

Discover, identify and analyse security threats, attack techniques and vulnerabilities and recommend mitigation and security controls. (S40)

Use appropriate cyber security technology, tools and techniques in relation to the risks identified. (S44)

N/A

(Data Analyst) Underlying Principles
K54 K56 K58

How to critically analyse, interpret and evaluate complex information from diverse datasets. (K54)

Sources of data such as files, operational systems, databases, web services, open data, government data, news and social media. (K56)

How Data Analytics operates within the context of data governance, data security, and communications. (K58)

N/A

N/A

(Data Analyst) Innovation and Response

S50 S52 S53 S54 S55

N/A

Find, present, communicate and disseminate data analysis outputs effectively and with high impact through creative storytelling, tailoring the message for the audience. Visualise data to tell compelling and actionable narratives by using the best medium for each audience, such as charts, graphs and dashboards. (S50)

Apply a range of techniques for analysing quantitative data such as data mining, time series forecasting, algorithms, statistics and modelling techniques to identify and predict trends and patterns in data. (S52)

Apply exploratory or confirmatory approaches to analysing data. Validate and and test stability of the results. (S53)

Extract data from a range of sources. For example, databases, web services, open data. (S54)

Analyse in detail large data sets, using a range of industry standard tools and data analysis methods. (S55)

N/A

(Network Engineer) Underlying Principles
K61 K62 K66

The role and function of virtual or physical network components and functions and typical topologies and service architectures. (K61)

The main network protocols in use, their purpose, features and relationship to each other. For example, Ethernet, IP (Internet Protocol), TCP (Transmission Control Protocol), OSPF (Open Shortest Path First). (K62)

Key security concepts. For example threats, vulnerabilities, exploits, detection and mitigation techniques, and security program elements such as user awareness, physical access control, multi-layer defence models. (K66)

N/A

N/A

(Network Engineer) Innovation and Response

S56 S57 S60 S62

N/A

Identify and collate stakeholder needs in relation to computer network requirements, plans and designs. (S56)

Plan, design, document, and develop the relevant elements of a computer network within an organisation or between organisations, taking into account customer requirements (performance, scale), constraints (budget, equipment availability), and define policies for their use. (S57)

Implement computer networks from a design including testing and validation. This includes populating variables in configurations, for example, IP addresses and subsequent application of configuration to equipment such as routers, switches, firewalls. (S60)

Research and evaluate emerging network technologies and assess relevance to current network requirements. Provide an objective opinion on how new features and technologies may be incorporated as required by the organisation. (S62)

N/A

(Network Engineer) Technical Solutions

S63

N/A

Investigate security concerns or attacks. For example, Distributed Denial of Service (DDOS), port scanning, assessing key metrics and indicators, evidencing the chosen steps to mitigate. (S63)

N/A

Professional discussion underpinned by a portfolio - Discussion

KSBS GROUPED BY THEME Knowledge Skills Behaviour
(Core) The Organisational Context
K7

The roles, functions and activities within digital technology solutions within an organisation. (K7)

N/A

N/A

(Core) Core Technical Concepts
K6 K11 K12 K14 K16

The approaches and techniques used throughout the digital and technology solution lifecycle and their applicability to an organisation’s standards and pre-existing tools. (K6)

The nature and scope of common vulnerabilities in digital and technology solutions. For example, the risks of unsecure coding and unprotected networks. (K11)

The role of data management systems within Digital and Technology Solutions. (K12)

A range of quantitative and qualitative data gathering methods and how to appraise and select the appropriate method. (K14)

Fundamental computer networking concepts in relation to digital and technology solutions. For example, structure, cloud architecture, components, quality of service. (K16)

N/A

N/A

(Core) Applied Technical Solutions
K13
S4 S9 S10 S11 S12

Principles of data analysis for digital and technology solutions. (K13)

Initiate, design, code, test and debug a software component for a digital and technology solution. (S4)

Apply relevant security and resilience techniques to a digital and technology solution. For example, risk assessments, mitigation strategies. (S9)

Initiate, design, implement and debug a data product for a digital and technology solution. (S10)

Determine and use appropriate data analysis techniques. For example, Text, Statistical, Diagnostic or Predictive Analysis to assess a digital and technology solutions. (S11)

Plan, design and manage simple computer networks with an overall focus on the services and capabilities that network infrastructure solutions enable in an organisational context. (S12)

N/A

(Core) Leading and Working Together
K8 K9 K10
S7 S8
B4 B6 B7

How teams work effectively to produce digital and technology solutions. (K8)

The concepts and principles of leadership. (K9)

Management techniques and theories. For example, effective decision making, delegation and planning methods, time management and change management. (K10)

Work effectively within teams, leading on appropriate digital technology solution activities. (S7)

Apply relevant organisational theories. For example, change management principles, marketing approaches, strategic practice, and IT service management to a digital and technology solutions project. (S8)

Commits to continuous professional development; maintaining their knowledge and skills in relation to developments in digital and technology solutions that influence their work. (B4)

Participates in and shares best practice in their organisation, and the wider community for aspects relevant to digital and technology solutions. (B6)

Maintains awareness of trends and innovations in the subject area, utilising a range of academic literature, online sources, community interaction, conference attendance and other methods which can deliver business value. (B7)

(Core) Social Infrastructure - Legal, Ethical and Sustainability
K19 K20
S15
B1 B2 B8

Relevant legal, ethical, social and professional standards to a digital and technology solution. For example, Diversity, Accessibility, Intellectual Property, Data Protection Acts, Codes of Practice, Regulatory and Compliance frameworks. (K19)

Sustainable development approaches as applied to digital and technology solutions such as green computing. (K20)

Apply relevant legal, ethical, social and professional standards to a digital and technology solution. (S15)

Has a strong work ethic and commitment in order to meet the standards required. (B1)

Reliable, objective and capable of both independent and team working. (B2)

Champions diversity and inclusion in their work ensuring that digital technology solutions are accessible. (B8)

(Software Engineer) Underlying Principles
K21 K22 K23

How to operate at all stages of the software development life cycle and how each stage is applied in a range of contexts. For example, requirements analysis, design, development, testing, implementation. (K21)

Principles of a range of development techniques, for each stage of the software development cycle that produce artefacts and the contexts in which they can be applied. For example UML, unit testing, programming, debugging, frameworks, architectures. (K22)

Principles of a range of development methods and approaches and the contexts in which they can be applied. For example Scrum, Extreme Programming, Waterfall, Prince2, TDD. (K23)

N/A

N/A

(Software Engineer) Technical Solutions
K24 K28

How to interpret and implement a design, compliant with functional, non-functional and security requirements including principles and approaches to addressing legacy software development issues from a technical and socio-technical perspective. For example architectures, languages, operating systems, hardware, business change. (K24)

Approaches to effective team work and the range of software development tools supporting effective teamwork. For example, configuration management, version control and release management. (K28)

N/A

N/A

(Software Engineer) Innovation and Response

S20 S21

N/A

Respond to changing priorities and problems arising within software engineering projects by making revised recommendations, and adapting plans as necessary, to fit the scenario being investigated. (S20)

Determine, refine, adapt and use appropriate software engineering methods, approaches and techniques to evaluate software engineering project outcomes. (S21)

N/A

(Software Engineer) Legal, Ethics and Landscape

S23

N/A

Extend and update software development knowledge with evidence from professional and academic sources by undertaking appropriate research to inform best practice and lead improvements in the organisation. (S23)

N/A

(IT Consultant) Underlying Principles
K30 K31 K34 K35 K36

How consulting interfaces with project management, business analysis and business management. (K30)

Principles of change management within organisations. (K31)

Approaches to analytical and critical thinking to define business problems objectively and create value for the client. (K34)

Questioning strategies and active listening to ensure all requirements are gathered. (K35)

The ethical and legal requirements in client and provider relationships. (K36)

N/A

N/A

(IT Consultant) Innovation and Response

S25 S27

N/A

Effectively communicate value add to the client through a variety of media. For example, presentations, written reports, Storytelling in a professional setting through performing socio-technical process improvements in a range of environments. (S25)

Participate in walk-throughs for Information Technologies, to identify, document and evaluate key risks within a client’s organisation. (S27)

N/A

(IT Consultant) Technical Solutions

S29

N/A

Effect change within an organisation through evaluation of a new system, process or initiative. (S29)

N/A

(Business Analyst) Legal, Ethics and Landscape
K41 K42
S33

Legislation and industry standards relevant to Business Analysis in the organisation and sector. (K41)

The purpose and value of quality assurance techniques. (K42)

Conduct Process Analysis, Definition, Mapping and Modelling within a business situation without supervision. (S33)

N/A

(Business Analyst) Technical Solutions
K38 K43
S37

Approaches to Requirements Life Cycle Management including how to manage and maintain requirements and design information from inception to retirement of a product. (K38)

A range of Business Analysis investigative techniques. (K43)

Use products of analysis in the design and development of a system. (S37)

N/A

(Business Analyst) Innovation and Response
K39
S35

Principles of Strategy Analysis, including how to identify the business need, address that need, and align the change strategy within the organisation. (K39)

Use tools and benchmarking to support modelling and requirements gathering and recommend approaches to team members as required. (S35)

N/A

(Cyber Security Analyst) Legal, Ethics and Landscape
K46 K48 K50
S45

Principles of quantitative and qualitative risk management theory including the role of risk stakeholders. (K46)

Key legislative frameworks and the regulatory landscape for cyber security including Data Protection Act 2018 , Network Information System Directive 2018, Regulation of Investigatory Powers Act 2000, ISO 27001. (K48)

Ethical principles and codes of good practice of at least one significant cyber security professional body and the ethical responsibilities of a cyber security professional. (K50)

Lead cyber security awareness campaigns and evaluate their effectiveness. (S45)

N/A

(Cyber Security Analyst) Technical Solutions
K47 K49
S41 S43

Concepts and approaches to cyber security assurance. (K47)

Approaches to incident response and management including escalation and investigation of cyber security breaches and their root cause. (K49)

Undertake security risk assessments for complex systems without direct supervision and propose a remediation strategy relevant to the context of the organisation. (S41)

Manage cyber security risk. (S43)

N/A

(Data Analyst) Underlying Principles
K53 K55 K57

The barriers that exist to effective data analysis between analysts and their stakeholders and how to avoid or resolve these. (K53)

Data formats, structures, architectures and data delivery methods including “unstructured” data. (K55)

Approaches to data processing and storage, database systems, data warehousing and online analytical processing, data-driven decision making and the good use of evidence and analytics in making choices and decisions. (K57)

N/A

N/A

(Data Analyst) Technical Solutions
K59

How Data Analytics can be applied to improve an organisation’s processes, operations and outputs. (K59)

N/A

N/A

(Data Analyst) Legal, Ethics and Landscape
K60

How data and analysis may exhibit biases and prejudice. How ethics and compliance affect Data Analytics work, and the impact of international regulations. For example, General Data Protection Regulation, Data Protection Act 2018. (K60)

N/A

N/A

(Data Analyst) Innovation and Response

S48 S49 S51

N/A

Define Data Requirements and perform Data Collection, Data Processing and Data Cleansing. (S48)

Apply different types of Data Analysis, as appropriate, to drive improvements for specific business problems. (S49)

Identify barriers to effective analysis encountered both by analysts and their stakeholders within data analysis projects. (S51)

N/A

(Network Engineer) Technical Solutions
K63 K67 K68
S58 S61

The benefits and risks of cloud computing and the common integration deployments (private, public, hybrid). Including the benefits and risks of virtualisation as a concept; key features of virtualisation and current cloud platforms available. (K63)

SDN (Software Defined Networking) and Network Function Virtualisation Core Principles. For example, Control Plane Separation, flexibility, overlay networks, disassociation of software and hardware layers. (K67)

Key elements of mobile networks. For example RAN (Radio Access Network), EPC (Evolved Packet Core), IMS (IP Multimedia Subsystem) including some specific key functions such as S/P/U-Gateways and the concepts in communicating over free-space media such as interference, ground bounce, encryption and in mobile endpoint platforms such as tracking user location and roaming. (K68)

Monitor performance and ensure networks are configured correctly and perform as expected by designers or architects. Undertake capacity management and audit of IP addressing and hosted devices. (S58)

Secure network systems by establishing and enforcing policies, and defining and monitoring access. Support and administer firewall environments in line with IT security policy. (S61)

N/A

(Network Engineer) Underlying Principles
K64 K65

The main factors that affect network performance, and how to mitigate these on network performance by implementing changes to QoS. For example, Traffic Shaping, Policing, Queuing, Topology (physical and logical), and Network Policy (Traffic Analysis, DPI (Deep Packet Inspection). (K64)

Principles of failure modes in protocols. For example, why a protocol may ‘hang’ and the effect of data communication errors and approaches to addressing failures to optimise network performance. (K65)

N/A

N/A

(Network Engineer) Innovation and Response

S59

N/A

Investigate, troubleshoot and resolve data network faults in local and wide area environments, using information from multiple sources, Physically or Remotely by console connection. Recommend and implement short term fixes to restore service and, or, quality of experience and recommend longer term changes to prevent recurrence or reduce impact of future occurrences. (S59)

N/A

Contact us about this apprenticeship

Employers involved in creating the standard: Accenture, BT, Capgemini, CGI, Ford, Fujitsu, GSK, HMRC, HP, IBM, John Lewis, Lloyds Banking Group, Network Rail, Tata Consulting Services AstraZeneca, Barclays, Bentley, Thales, MC2.

Version log

Version Change detail Earliest start date Latest start date Latest end date
Revised version awaiting implementation In revision Not set Not set Not set
1.1 The funding band for this standard has been reviewed as part of the apprenticeship funding band review. The new funding band is £25000 13/05/2019 Not set Not set
1.0 Approved for delivery 26/03/2015 12/05/2019 Not set

Is this page useful?

Tell us about your visit

Help us improve our website