Swinford, Leicestershire, LE17 6AZ, UK | +44 1788 869 126 | firstname.lastname@example.org
Formed in January 2001 Transform Technology (Trantech) provides consulting & coaching on the deployment of business, technical, technological and project management activities for Transport & Renewables business sectors.
Whether you want Coaching or Consulting, we will work with you to thoroughly understand your business challenge and advise, suggest, or take charge of implementing a solution, in line with your preference.
We aim to implement common sense solutions for your business challenges. Simplest is best.
We have collectively over 70 years experience, working for a wide range of companies from Start Ups, through SME’s, to Multi National businesses across a wide range of market sectors, both in the UK and internationally.
We work with a network of like minded associates so even if we don't have what you need, we know someone who does!
2018 was the year Electric Vehicles really 'stood up to be noticed.'
They are the future — whether you think that is reasonable or not, the Internal Combustion Engine (ICE) development (particularly Diesel,) has largely stopped. That means that emissions reduction programmes are not being pursued. — So if you buy an ICE car this year, it will likely be no 'cleaner' than one you could have bought 1 or 2 years ago!
We are seeing one of the 'Major Technological Discontinuities' in life. Future Mobility is going to be different!
Trantech has many skills in the domain of Electric Vehicles including Battery Technology, Traction Electronics, Body Electronics and SMART Grid charging solutions.
How will the autonomous vehicle cope with normal roads?
It is likely that the first autonomous vehicles will need to be segregated from 'normal' drivers. Why? Because normal drivers are not sufficiently predictable. They can cause their vehicle to impact the autonomous vehicle's 'space' before it has time to react. This amounts to unacceptable risk.
Trantech has been working with Warwick University to refine requirements for the West Midlands CAV Testbed using 83km of roads around the West Midlands, Coventry, Solihull and Birmingham.
It is likely that the first truly autonomous vehicle on our roads will be the Low Speed Autonomous Transport (LSAT) units.
These have a maximum speed of 25km per hour and will be used mainly for 'last mile' transportation.
Smart Grid technology is an increasing necessity in tomorrow’s world.
Existing power distribution networks will be unable to cope as the demand for local charging of Electric personal, public service and commercial vehicles increases.
Buses pose a unique challenge in that they generally run 24/7 (albeit in different quantities) so there is not a natural ‘down time’ for battery charging. The challenge therefore is to manage the charging requirements through detail monitoring of battery state of charge (SoX) and other vehicle parameters and marry this to charge point geography and availability.
There is no point in another bus turning up to a charging point if a first bus is already connected.
Buses generally demand greater power than Cars, so recharge times are longer and the rate of charge is slower than for smaller batteries. Battery heat management may also be a concern.
Having good quality data is the key to managing charging demand. Knowing what the battery State of Charge (SoX) is precisely, and continuously mapping this to Bus route and distance travelled together with available Smart Grid charging points will determine whether the Bus can meet its schedule or not.
Smart Grids are not just about managing the various supply inputs (Wind power, Hydro Power, Solar Power, Nuclear Power, Fossil Fuel power etc.) it’s also about knowing and managing the outputs – the demand.
Rail Reliability Engineering is a service Trantech provided for more than 15 years.
and Electromechanical investigations with 8D root cause analysis.
Everything from 25Kv connector systems to SIL level software audits.
Trantech works with a network of Associate companies to deliver customer solutions in rail be they small and simple or large and complex.
Metro trains are a little different from their mainline cousins.
Metros are 'all electric' usually powered from a 'third rail' which can supply Direct Current (DC) or Alternating current (AC) at between 500v and 800v depending on the metro line in question.
Passenger information and on/off train communications rely on a number of different technologies. 'Leaky Feeder' antennas are just one of these.
Trantech has worked closely with London Underground to improve the reliability of Traction systems, Data Transmissions systems, Passenger Information Systems and Train Communication systems.
Trantech has led consortia developing Diagnostics and Prognostic systems for Metro trains.
With 35 years experience, Industrial Automation is a core business offering.
Trantech can help you investigate and specify your requirements and can assist you to both source and install the automation solution that supports your business in the way you want.
With a network of Systems Integrators, Trantech can tackle most of your challenges from data management to process control and visualisation
DESIGN / DEVELOPMENT / TEST
Good Electromagnetic Engineering is the basis for proven good design practices for signal integrity, power integrity, and the control of EMI emissions and immunity (EMC).
Our aim is to help people learn how to effectively design and manufacture electronic equipment (products, systems, installations, etc.) to meet functional specifications and conform to EMC standards, directives and other requirements.
In the Model Based Design (MBD) process, all of the development activities are coupled to an executable model that represents the software requirements. The executable model enables the demonstration and validation of the requirements prior to software code generation. After the requirements have been validated, the software code is generated directly from the executable model using automated tools. The benefits of the MBD process include:
Functional safety has become a critically important issue across all areas of industry. With the expanding digitalisation and automation of life and industry also new challenges and requirements for functional safety technology arise. As a result, manufacturers and operators place top priority on the quality and safety of products and plants in order to protect people, property and the environment against technology-related risk.
Functional safety is achieved when every specified safety function is carried out and the level of performance required of each safety function is met. This is normally achieved by a process that includes the following steps as a minimum:
DESIGN / DEVELOPMENT
Cool Electronics are happy electronics!
keeping your critical silicon devices cool is an increasingly challenging activity with todays technology be it a smartphone or an EV battery pack
Passive or active, conventional or solid state, Trantech has the experience you seek to advise on your cooling pack solution.
During the initiating process, you will refine the project goals, review the expectations of all stakeholders, and determine assumptions and risks in the project. You will also start project team selection At the end of this phase you will produce a Statement of Work, which is a document that provides a description of the services or products that need to be produced by the project.
During the planning process, you will detail the project in terms of its outcome, team members’ roles and responsibilities, schedules, resources, scope and costs. At the end of this phase, you will produce a project management plan, which is a document that details how your project will be executed, monitored and controlled, and closed. Such a document also contains a refined project scope, and is used as the project baseline.
During the executing process, you apply your project management plan. In other words you direct your team so that it performs the work to produce the deliverables as detailed in the plan. The executing process also involves implementing approved changes and corrective actions.
Controlling and monitoring
During the controlling and monitoring process, you supervise project activities to ensure that they do not deviate from the initial plan and scope. When this happens, you will use a change control procedure to approve and reject change requests, and update the project plan/scope accordingly. The controlling and monitoring phase also involves getting approval and sign-off for project deliverables.
During the closing process, you formally accept the deliverables and shut down the project or its phases. You will also review the project and its results with your team and other stakeholders of the project. At the end of the project you will produce a formal project closure document, and a project evaluation report.
Identifying risks can be not only a positive experience but also an experience that your whole team can take part in and learn from.
Leverage the collective knowledge and experience of your entire team. Ask everyone to identify risks they've either experienced before or may have additional insight about.
A project risk log, also referred to as a project risk register, is an integral part of any effective risk management process. As an ongoing database of each project’s potential risks, it not only helps you manage current risks but serves as a reference point on past projects as well. By outlining your risk register with the proper data points, you and your team can quickly and correctly identify and assess possible threats to any project.
APQP is a structured process that includes critical tasks from concept approval through production.
The aim is to create a product quality plan for developing and manufacturing products that meet customer requirements.
This planning uses a five-phase process:
The process to follow when capturing and documenting the customers' needs for a system product or service, ensuring that any useful information that is obtained is kept and that any questions and answers are documented in a controlled and retrievable way.
The requirements capture phase should ensure that the users’ needs are understood before designing and implementing a system to meet them. It also provides part of the basis for system and acceptance testing.
SET UP REQUIREMENTS CAPTURE
Understand requirements and scope - identify which project they are to do with, or whether it is a new project. Obtain some means of splitting the requirement capture task between a team if needed e.g. initial grouping.
GATHER FULL REQUIREMENTS
Record all requirements and annotate each one. Store all questions and answer interchanges used while expanding on requirements.
Identify requirement groups, document them and review.
PRODUCE REQUIREMENTS DOCUMENTS
For each group, compile its requirements into a reviewable form.
REVIEW REQUIREMENTS DOCUMENTS WITH CUSTOMERS
• Review requirements documents and their grouping with customers and knowledge holders
• Record review
• Record grouping document
• Record final requirements document
The requirements may not be completely known at the start of a project so they may have to be evolved during part of the project's lifecycle.
DOCUMENTATION AND CONTROL
Appendix E details the items that need to be documented to control the activities taking place during the requirement capture process.
– FMEA is a Qualitative and systematic tool
– FMEA helps to find the possible causes of failure and the likelihood of failures being detected before occurrence
–You need both a knowledgeable individual and a team of the right people to undertake a good FMEA
FMEA uses three criteria to assess a problem, ranked between 1 and 10
Severity • What is the impact of a failure? (High number = high impact)
Occurrence • How likely is it that item will fail? (High number = high likelihood of failure)
Detection • How likely is it that the potential failure can be detected before it occurs? (High number = LOW possibility of detection)
Once ranked, the ‘Risk Priority Number’ (RPN) can be calculated:
RPN= severity x occurrence x detection
– Any single number in any category >8 needs investigation and mitigation
– Any RPN >80 needs investigation and mitigation
8D stands for 'The 8 disciplines or the 8 critical steps for solving problems.'
It is a highly disciplined and effective scientific approach for resolving chronic and recurring problems.
This approach uses team synergy and provides excellent guidelines to identify the root cause of the problem, implement containment actions, develop and then implement corrective actions and preventive actions that make the problem go away permanently.
Isolates and contains the most basic causes of any undesirable condition.
Identifies the factors that contribute to the problem.
Eliminates systemic factors that cause the condition
Keeps teams from jumping to conclusions too early.
Prevents problem recurrence.
Our CEO is a Registered EU Business Coach for the Horizon 2020 R&D Programme.
We offer all forms of Business coaching including Strategy, Communications, Marketing. Finance, Engineering, Manufacturing, Purchasing and Supplier Development.
A project is a unique, transient endeavour, undertaken to achieve planned objectives, defined in terms of outputs, outcomes or benefits.
A project is usually deemed to be a success if it achieves the objectives according to their acceptance criteria, within an agreed timescale and budget.
A key factor that distinguishes project management from just 'management' is that it has this final deliverable and a finite timespan, unlike management which is an ongoing process. Because of this a project professional needs a wide range of skills; often technical skills, and certainly people management skills and good business awareness.
Systems engineering is focused on the system as a whole; it emphasises its total operation.
It looks at the system from the outside, that is, at its interactions with other systems and the environment, as well as from the inside. It is concerned not only with the engineering design of the system but also with external factors, which can significantly constrain the design. These include the identiﬁcation of customer needs, the system operational environment, interfacing systems, logistics support requirements, the capabilities of operating personnel, and such other factors as must be correctly reﬂected in system requirements documents and accommodated in the system design.
Requirements Capture is the most important activity a Project Manager has to undertake.
Without clear Requirements that are understood and agreed by both parties, the Project will be at risk
Gathering Requirements is not complicated but its not considered 'interesting' by most engineers or managers and therefore is likely to be — at best, incomplete and at worst, 'assumed.'
Never assume anything when it comes to capturing and agreeing Requirements.
A simple check list will help get you started. Consider the Requirements document to contain:
The design of the physical architecture of the electrical system has a big impact on a product's cost and weight. But, for many companies, the tools used in the architectural design stage provide only limited information and are unable to identify the cost impact of small but important changes to either physical layout or electrical design configurations.
The massive complexity inherent in autonomous vehicle design will push the tools and methodologies used by automotive engineers to their limits. This is especially true in the electrical and electronic systems domains as they come to dominate the operation of a vehicle’s safety-critical systems and amenities.
To compete, autonomous car manufacturers will need a new design methodology that enables young engineers to design accurate and optimised systems, which can only be done by capturing the experience and knowledge of time-served engineers. They will need 'Generative' design.
System-level technical requirements are a critical precursor to and foundation of system design and development. A top-level system design is generally under the stewardship of the project team and represents the team's independent projection of the way a system could be implemented to meet requirements with acceptable risk.
The primary reason for developing a top-level system design is to provide a technical foundation for planning the program. It is the de facto technical approach to meeting the customer's needs. A top-level system design developed early in an acquisition program can be used to assess system feasibility and provide some assurance that the implemented design will satisfy system requirements. Done early in a program, design effort can be a powerful basis for developing fact-based projections of cost, schedule, performance, and risk, and provide the foundation for subsequent design efforts.
The goal of reliability engineering is to evaluate the inherent reliability of a product or process and pinpoint potential areas for reliability improvement. Realistically, all failures cannot be eliminated from a design, so another goal of reliability engineering is to identify the most likely failures and then identify appropriate actions to mitigate the effects of those failures.
The reliability evaluation of a product or process can include a number of different reliability analyses. Depending on the phase of the product lifecycle, certain types of analysis are appropriate. As the reliability analysis are being performed, it is possible to anticipate the reliability effects of design changes and corrections. The different reliability analyses are all related, and examine the reliability of the product or system from different perspectives, in order to determine possible problems and assist in analysing corrections and improvements.
The reliability engineering activity should be an ongoing process starting at the concept phase of a product design and continuing throughout all phases of a product lifecycle. The goal always needs to be to identify potential reliability problems as early as possible in the product lifecycle. While it may never be too late to improve the reliability of a product, changes to a design are orders of magnitude less expensive in the early part of a design phase rather than once the product is manufactured and in service.
18 years of customer satisfaction and supportive partnerships
UK +44 (0) 1788 869 126
Mobile +44 (0) 7815 151018
Saint Leonard de Noblat
France +33 (0) 5 55 57 15 24
Mobile +44 (0) 7815 151018