FIMS Flashcards
2.1.1 What is one of the mandatory success factors in selecting and implementing an FIMS? (p.13)
Know your Business requrements
- Up to you FM to identify all key areas & Guide Vendor
- Vendor cannot be expecteded to know your specific fleet functions.
2.1.2 What should you do once you know of the gaps between best in class data and your own? (p.15)
FMO ( Future Mode of Operation)
- You now have the info needed to design FMO
- Business processes become evident
- Team identifies work needed
- Proccesses & Sub Processes created
- Data repositories identified
2.2 FIMS categories or Tier 1 Enterprise Management Systems
Function : Other functions ( AP, Vendor Man., Finance)
IT : Server / Intranet
Workflow Automation : Not Vehicle Specific / Automation requires specifics addons
Cost : Software costs high / Fleet Services Drive costs higher
Implementation Time : Longer to add Fleet Terms / No time needed for Interface
2.2 FIMS categories or Tier 2 Enterprise Asset Management Systems
Function : Generic Asset Management
IT : Server / Intranet / Internet Option
Workflow Automation : Not Vehicle Specific / Automation requires specifics addons
Cost : Software costs high / Fleet Services Drive costs higher
Implementation Time : Longer to add Fleet Terms / Longer times for Interface
2.2 FIMS categories or Tier 3 Comprehensive Vehicle Fleet Management Systems
Function : Specializes in Vehicles / Equipment / Life Cycle Management
IT : Server / Intranet / Cloud
Workflow Automation : Vehicle Specific / Automation requires some configuration
Cost : Software costs reasonable / Pro Fleet Services for projects but at lower cost
Implementation Time : Some time to configure / Longer times for Interface
2.2 FIMS categories or Tier 4 Specific Fleet Function Management Systems
Function : Not Comprehensive ( Specific to 1 function )
IT : Server / Database / Networking / Run on PC
Workflow Automation : Specific for Fleet function / Automation requires some configuration
Cost : Software license or subscription fee / Low cost / One-Time purchase for PC
Implementation Time : Short / Longer times for Interface / Could be manual for PC
2.3 Information applications or software.
Fleet organization must know and document the business requirements and use cases.
2.3.1 What are use cases? (p.17)
Use Cases simply outline the process, workflow or function for which the software will be used and the method of use.
- The fleet acquisition stakeholders consist of:
* The software users (e.g. operations and administrative staff)
* The support roles (e.g. procurement)
* The relevant managers and leaders
* Finance and budget personnel
* IT resources, etc.
- They must all be engaged in the process in order to achieve a successful outcome and to reduce re-work
2.3.2 What can add complexity, cost and time to the process of migrating to a new software? (p.18)
- Cooperation from the Existing Supplier - Not happy - Send them a Template to obtain needed info. - Add these details in the contract upfront to prevent issues on the backend. ( Data belongs to cust. )
- Migration of Data from Existing to New - Data cleanup from years most times
- Data sanitation and Format Discrpancancies - “garbage in garbage out” - common mistake in data migration is to underestimate the time required to ensure proper database table structure
- Cutover Details - “hot cutover” technique must be used - existing and new software work in parallel and the existing software is decommissioned when there are no users active on the system (i.e. late at night)
- Process Changes - Opportunity to improve the organization’s effectiveness and efficiency with new FMO - New process needs to be simple / ^ efficient to get the buy-in of the process actors. - Insructions for the new process need to be clear, concise and well-tested prior to launch
- Change Managemenet Communicatins and Training - Regular communications from the leaders and project management team about the benefits of the new software and the progress status would assist to reduce the resistance to change - comprehensive training
2.3.3 What is meant by the phrase “garbage in garbage out”? (p.19)
If a mistake was made while entering the data, the database will contain this mistake
2.3.4 What is the “hot cutover” technique? (p.19)
Existing and new software work in parallel and the existing software is decommissioned when there are no users active on the system (i.e. late at night)
2.3.5 List some communications and training that are important during software transition. (p.19)
- Regular communications from the leaders and project management team about the benefits of the new software and the progress status
- Comprehensive training for all software users at launch time and some refresher Post launch.
2.3.6 What are the functions of an Enterprise system? (p. 20)
Other functions ( AP, Vendor Man., Finance) - These systems are used for supporting all the functions of an enterprise as a whole
2.3.7 What are the advantages and disadvantages of an Enterprise system? (p.21)
Advantages: May already have a system / No Interface time / IT Infrastructure already exists / Software upgrades at same time
Disadvantages: Functions like ( Finance,AP, HR,) take priority over Fleet Man. / Terminoligy shortage / Rigidly guarded / Time and cost high / Not specialists
2.3.8 What are the functions of an Enterprise Asset Management System? (p.22)
- Used to manage fleet and other assets such as servers, printers, communication network components, building heating and cooling system components, etc.
- Provides for asset records including location, move/modify/delete functions, preventive maintenance forecast, repair records
- Compartmentalized by asset type and requires configuration and terminology customization for the fleet functions
- Workflow automation requirements
2.3.9 What are the advantages and disadvantages of an Enterprise Asset Management System? (p.22-23)
Advantages:
Multi-purpose software to manage all enterprise assets reduces the need for disparate solutions for managing different assets
* ( same system may be used to manage vehicles, IT servers, PCs, printers, etc. in an organization)
As with the Enterprise solution, IT infrastructure and resources can be shared for multiple uses.
Legal contracts may be already in place for other asset management
Disadvantages: Still need for Interface development / Need customization for Fleet / You can get a better deal with specific systems Not Specialists
2.3.10 What are the functions on a Commercial Off the Shelf (COTS) fleet management system? (p.23)
This software is dedicated and specialized for fleet management function
- The higher echelon solutions are very comprehensive and consist of all the software modules to support the end-to-end lifecycle management of the vehicle asset, including the required work flows, data repositories, document management and so on, which we will discuss at length in a subsequent section.
The lower and middle echelon software must be scrutinized and understood clearly to ensure that your requirements are being met and that there are firm plans in place to meet any gap
2.3.11 What are the advantages and disadvantages of a COTS Commercial off the Shelf (COTS) Fleet Management fleet management system? (p.23-24)
Advantages: Easy to configure and implement because it’s specific to Fleet Managmenet / Fleet expertise / Flexible Infrastructure / Less customer reliant
Disadvantages: Basic package may be more than you need // Cost has Floor / Still requires custom configuration
2.4 Fleet function-specific management software.
The function specific software allows for a low cost of entry and it is useful for companies who only provide one specific fleet service
2.4.1 What are some of the uses of fleet function specific software? (p.24)
Management of the shop or garage, parts inventory, work order, purchase order, timesheet, and so on.
2.4.2 Why is it important to understand a company’s future evolution strategy? (p.25)
Needs to be understood in the terms of impact on current / short term buying decisions
- Do you plan to offer other services in the future?
2.4.3 What is an integration consideration that may not allow two software’s to communicate? (p. 25)
- There are subtle issues in terms of when the system actually sends the data and whether this meets the user requirement.
- Several function specific systems are of an older vintage and may not necessarily have up-to-date interfacing capabilities
2.4.4 Why is it important to consider 2-3 vendors with strong financials and a solid track record? ( p.26)
- Before making a purchasing decision, it is important to ensure that the supplier space is competitive
- If you cannot find at least 2 or 3 quality vendors, this is a strong indication that the longevity of the supplier and the software is in doubt
2.5 Elements of a Fleet Information Management System (FIMS).
- The functionality offered by a FIMS in the marketplace is enormous in its scope and there are some generic FIMS attributes to consider.
- Suppliers offer several options in the system architecture offerings for delivery of the solution.
2.5.1 What are two things to consider when choosing an FIMS? (p.36)
- FM needs to consider the commercial or business model which makes the most sense for your organization
- The budget
2.5.2 Why are PC based fleet management applications seldom used in the industry today? (p.37)
- Fleet management application which runs on a stand-alone PC and does not require any connectivity to other computers, servers, etc
2.5.3 What does the term ‘client server’ refer to? (p.37)
- Network architecture in which each computer or process on network is either a client or Server. * Driver portal
2.5.4 What does the term ‘thin client’ refer to in client-server applications? (p.37)
- Usually refers to software, but, it is increasingly used for computers, such as network computers and Net PCs that are designed to serve as the clients for client/server architectures
2.5.5 What is the purpose of a thin client in client-server application? (p.37)
- A Thin Client in client-server applications is a client designed to be especially small so that the bulk of the data processing occurs on the server
- A thin client is a network computer without a hard disk drive
2.5.6 What does the term thick client refer to? (p.37)
- Usually refers to software, it can also apply to a network computer that has relatively strong processing abilities
2.5.7 What is the purpose of a thick client? (p.37)
- Thick Client is one that performs the bulk of the data processing operations
- A thick client is a network computer with a hard disk drive
- The data itself is stored on the server
2.5.8 What is a web application? (p.38)
- Any application which runs on the internet and can be accessed from a PC using a web browser and typing in the web site address (also known as Uniform Resource Locator or URL) could be called a web application
2.5.9 Define the term ASP (p.38)
- A web application provider that has its own data center may also be called an Application Service Provider (ASP)
2.5.10 What are the benefits of ASPs for companies? (p.38)
- ASPs are a way for companies (suppliers and customers alike) to outsource some or almost all aspects of their information technology needs
2.5.11 What is cloud computing? (p38)
- A type of computing that relies on sharing computing resources rather than having local servers or personal devices to handle applications