Glossary Terms:

A

• Actions/Action page - Often when you are on the web you have a form and it always submits its data to an action page, where it performs an action. 
• Accounts Payable - All bills, invoices, PO's and reimbursements that are due to be paid. Money that is owed to others from your company. 
• Accounts Receivable - All invoices that are not paid. Money that is owed to your company. 
• Active - Status that designates data as being in use. This status relates to customers, vendors, and items. When active, data will show up in search and list by default.
• Add - This is a general term which usually means create, multiply, or add on to. Common things could be add a customer, add an invoice - basically this means create a new one or apply an additional one. 
• Add to Queue - Link that assigns current customer to a list or "queue" which is a step before the shopping cart.
• Admin Time Clock - Allows user to see all active time cards/hours based on requested parameters. Also gives ability to edit the time cards. 
• Adobe/PDF - See PDF. This is a product made by Adobe which requires a reader. PDF stands for Portable Document Format which  is a format that can be read across browsers. 
• Advanced Add to Cart - Make changes to the item already added to the cart- price, cost, quantity, and tax category. Add discounts. *Special feature: put in unknown quantity, but known price to have the system determine how much you can sell based on dollars a customer has to spend.
• Advanced Searches - Access data based on specific parameters in all areas of database: customer, vendor, parts, elements of time, invoices, expense receipts, po's,
• API - application programming interface- a set of functions and procedures allowing the creation of applications that access the features or data of an operating system, application, or other service. Allows our software to connect to other software through a "door" that we can elect to open or keep closed.
• A/P's - See Accounts Payable. A/P's is an acronym for Accounts Payable which is an accounting term for who do I owe. 
• A/R's - See Accounts Receivable. A/R's is an acronym for Accounts Receivable which is an accounting term for who owes me money and how can I collect it.
• Assets - Any resources owned by the business. Tracked on the balance sheet through user-maintained balance sheet items (not automated by system).
• Assign to Cart - Action taken to add a customer to a shopping cart. Link is seen to the right of the customer information from the customer homepage.
• Ctrl A - This is a keyboard shortcut on windows for selecting all the content in a certain area.

B

• Balance Sheet Item - A user-maintained account that stores data on the balance sheet. 
• Bank Reconciliation - Matching deposits and expenses in database to monthly bank statement. Must verify all transactions by date for these transactions to appear on the reconciliation page. 
• Banks - Virtual representations of banks or credit cards. May also be used to represent a location for tracking cash sales.
• Barcode - Made up of 15 spaces that may contain letters, numbers or symbols. Used to track inventory and speed up the sales process.
• Basic Live PO - Used to create inventory or inventory items in database. Name is dynamic and may be changed in the corp-wide settings (see section C).
• Bit Map Image - This is similar to a JPEG or a GIF image. Technically a bitmap means little tiny blocks of color that are organized in an image format to show a picture of some kind. The other kind of image is what is called a vector which has smooth mathematical lines that creates its visual appearance. 
• Black Box - Custom coded takeover of a page in the database. Gives customer specific functionality requested. Also makes page static to other system-wide updates so can create limitations in the long run.
• Browser - This is the tool for viewing web based content. There are multiple different browsers and some of them are based on your operating system or preference. Browsers are how all things are shown over the web. 
• BSI - Acronym short for Balance Sheet Items it may also be shown as B.S.I. These balance sheet items are what are called user-maintained items and is a miniature account for various things. Some of these things could be where you account for things such as loans, individual or company investments, large assets like buildings, vehicles, or machinery. 
• Build & Sell - This is a term used with a function called Recipe/Build. The build and sell is a quick, just in time, preformatted group or kit. So if there are multiple things that are sold together you can create this kit or grouping that you can use just in time on an invoice when you are selling these items.  
• Build & Hold - This term is used with Recipe/Builds as well but this term is used on the raw goods side. So a build and hold uses raw goods, meaning taking them from inventory, called ingredients. And produces outcomes or other products to be used farther down the manufacturing line or to be sold independently. 
• Bulk (in general - edit, verify, etc.) - The word bulk means more than one. In the system it is often used such as bulk edit meaning I am going to edit multiple lines at one. Or bulk verify meaning I am going to verify multiple things at one time. There is also bulk labels, bulk printing, etc. We are dealing with multiples of things. 
• Bulk Verify - Used to verify multiple deposits or expense receipts at one time. 
• Bump Value Up - The term bump just means move in a direction. Some systems would say debit or credit. We just say bump meaning which direction of flow is it going. Bump up means you are somehow increasing a value or total.  
• Bump Value Down - The term bump just means move in a direction. Some systems would say debit or credit. We just say bump meaning which direction of flow is it going. Bump down means you are decreasing a value or total. 

C

• Cart - Where items are placed in order to make a purchase (see also Shopping Cart).
• Check - One of many methods of payment, usually flowing out of a bank.
• Check Requests - A check request is a form of an expense receipt which is almost a question. Can I spend this money? It is similar to how a quote and an invoice are related, a quote is a potential precursor to an invoice. This is the same for check requests and expenses. A check request is a potential precursor to an expense. It does not count toward financials at this point. It requires an approval and once it is approved then it can become an actual expense and be booked on the financials. 
• Child - Refers to items in the database that can be sold. Connected to a parent item (parent inventory) which carries the name and some information. The child item is unique and can carry much more unique information (see also Sub Inventory).
• Chooser - Home page interfaces. 40+ choices plus custom options available. Called chooser because the user "chooses" which one is most suitable to their needs.
• Classic - Interface that shows all potential functions in the system. Not geared toward any particular tasks or industry.
• Clear Cart - Wipes out all actions related to the active shopping cart. Must perform this action in order to log out of the system, or to start a new cart.
• Clock in/out - Tracks users hourly work. Requires user to be assigned to a department.
• Closed - Potential status of a sub or child item. Once a sub/child item is at quantity 0, it can be closed. 
• Corp ID - Identifying number associated with every corp. Assigned upon activation.
• Corp Key or Alias - A corp key is a combination of three letters of the corporation name, a dash, and then a numeric corp id number. For example pla-0053. Pretend that this company's name was Playground and the Corp Id was 53, this could be it's corp key. The alias is like a username for the corp instead of the technical three digit plus numeric. An example for this one could be something like testing or playground. 
• Corp-wide Settings - Admin level settings that affect the database on a corp wide level. Options for setting system wide naming conventions, tax settings, discounts, etc.
• Corporation - This is a virtual world inside of a system. Corporation is also synonymous with entity, business, company, etc. Usually a corporation can have locations and different things within it but it is usually a tax entity. Often in the system you will see us use the word corp as a shortened form of corporation or business entity. 
• Counter Sale - Shopping cart that is not assigned to a customer. Used in sales situations where the customer is unknown and does not need to be.
• Create - This is another word for adding or making something new. For example create a new my cart favorite button or create new invoice link. 
• Cross Corp Invoice to PO - Special function that must be added by a system administrator (fees associated with this function) that allows one corp on the same server as another corp, to send inventory via an invoice. Both corps must agree to connect, then one makes an invoice, and the other turns that invoice automatically into a PO.
• CSS - This is an acronym for a web look and feel tool called a Cascading Style Sheet. The css of a site dictates colors, roll overs, margins, spacing, font, and other look and feel pieces. Inside of the system/platform we allow you to change a lot of these.  
• CSV - Comma Separated Values is a simple file format used to store tabular data, such as a spreadsheet or database. Files in the csv format can be imported to and exported from programs that store data in tables.
• Ctrl A - This is a keyboard shortcut on windows for selecting all the content in a certain area.
• Ctrl C - This is a keyboard shortcut on windows for copying a certain selection and putting it on the clipboard for future use. Ctrl V is used to paste.
• Ctrl N - This is a keyboard shortcut on windows for creating a new tab in your browser window. Often you can do the same thing by right clicking a tab and clicking new or duplicate, etc. 
• Ctrl P - This is a keyboard shortcut on windows for printing a certain page.
• Ctrl V - This is a keyboard shortcut on windows for pasting a certain selection held in memory. Either Ctrl C or Ctrl X are the ways of copying something to memory. 
• Ctrl X - This is a keyboard shortcut on windows for cutting a certain selection and putting it on the clipboard for future use. Ctrl V is used to paste.
• Ctrl Y - This is a keyboard shortcut on windows for redoing something that has been undone. It's brother command is Ctrl Z or undo.
• Ctrl Z - This is a keyboard shortcut on windows for undoing a previous action. It's brother command is Ctrl Y or redo.  
• Ctrl + - This is a keyboard shortcut on windows for zooming in on the webpage or browser. This is control plus sign (+). 
• Ctrl - - This is a keyboard shortcut on windows for zooming out on a webpage or browser. This is control minus sign (-).
• Custom - This is a broad term and can be used in many different ways. Often we use custom to refer to custom code, custom look and feel, custom flow, or custom processes. Also we use it generally to say we could add that in but it would be custom, meaning it would be specific to your needs and wants and go through a process of design and development to meet your needs. 
• Custom Logic - This is part of custom code but the term custom logic usually resides more toward the top of the page. It is like the brain for the page. This is how we control what is happening or could happen on a single page. You may often hear us say, "We could black box that." Meaning we could add code and logic at an insertion point to make the page perform custom actions, logic, flow, or other code related options. 
• Customer Queue - Customers waiting to make purchases can be placed in line or a queue so that they are seen in a first come first served order. Multiple queues can be used to designate customers as VIP, Pickup, etc.
• Customers - The people or companies you sell items or services to.

D

• Database - This is a background storage engine that holds all of the data tables, rows, and columns. The database engine that we use is called a MySQL server. This database server is very robust and can handle millions and millions of records, queries, and actions at a single time. Technically the database is that storage engine but sometimes we generally refer to it when discussing data or the storage area. For example, when a cart is fully submitted it transfers from session memory into the database.
• Default Homepages - Every user gets to set their default homepage. This is where you land, or are taken to, when you click your logo or home link. Think of this as your virtual starting spot or home base. The reason it says homepages is there are hundreds of choices that you could set as your default. As a side note you can also switch at any point to facilitate the task at hand. The original goal of this was like a person with a shed in their back yard. If they are paining they want painting stuff from the shed, if they are doing yard work you want yard work from the shed. Depending on the task at hand you may want easier access to options and/or tools. If you want you can even have a custom dashboard or default homepage made. 
• Default Settings - The system has a base of permissions and settings. This is how things interact and are used. A default setting means where it was set originally without any interaction or where that setting has currently been set to. Often these default setting will be changed based on needs, wants, or dictations from administration or higher authority. Settings come on a corporation level, a player group level, a page level, and even on a user level. 
• Delayed Inventory Counter - Used to count parent inventory by scanning barcode and entering quantity.
• Departments - Used to organize employees. Allows employees to utilize the clock in/out function (see above).
• Deposits - A total amount of money that flows into a bank.
• Deposit Types - Chart of accounts for deposits. System comes with several options and the user creates the rest.
• Dewy Decimal System - This was a funny name used as a code name/alias for a project to take functionality from 2 decimal points to 5 decimal points. Sorry librarians, no pun intended. ;) This was just taking numeric quantities, costs, and prices to multiple decimals of accuracy. 
• Disabled - One of the three statuses that refers to items and their ability to be sold or not sold. In this case, when an item is disabled, it is part of inventory but is unable to be sold (on lock down until enabled).
• Discount Calculator - Feature in the shopping cart that allows salesperson to discount items by dollar amount or percentage. Discounts can be by line item or added to the shopping cart as a whole.
• Discount Engine - Used to create reoccurring discounts. Settings determine if discounts are by category or item, and if by day, date, or time.
• DPI (Dots Per Inch) - This deals with image resolution both on screen and for printing. If you are printing something you want your DPI higher. If you are just viewing it on screen usually 72 DPI is enough for your eye to catch on the screen versus images for print are usually printed at at least 300-600 DPI. 
• Drill-Downs - This is a term for navigating through layers. An example might be you doing a customer search and it returned a number of customers. Then you would drill-down on the associated link to see their details, or drill-down to see their history, or drill-down to see other information, etc. 
• Duplicate Invoice to New Cart - Allows user to take an existing invoice and create a new shopping cart that is exactly the same as the original. Great for repeat sales in certain industries.

E

• E-Commerce - This is any sort of online web presence where you sell your goods and services over the internet. The software has both free and paid versions of ECommerce that are fully integrated and built in for our clients. Some of the cool features that you can harness are mobile ready, bill pay - where customers can come in and pay some of their bills, photo gallery, expanded descriptions, technical specs, automated emailing, and tons of custom display options.
• Edit - Function associated with all aspects of database- customers, vendors, items, banks, e/rs, deposits, invoices, etc. 
• Edit Line Items - Makes changes to the line items (second section) that have been added to a PO, deposit, invoice or E/R. 
• Edit Main - Makes changes to the main section (first section) of a PO, deposit, invoice, or E/R.
• Edit Payments - Makes changes to the payment section (third section) of an E/R or invoice.
• Elements of Time - May be defined by your business. Giant toolset that can be customized to meet your needs. Customer time clock, an appointment book, a scheduler of sorts, a dispatching solution, a payroll timesheet for employees, a mini blog, a general reminder system, etc. You name it, you set it up, and then you get to use it over and over again. You can search it, display it, add to it, create new templates, invoice time, quote time, and generally work with almost anything that has a time element associated with it.
• Employees - An employee is technically someone who works for a company. Inside of the system employee is a term that is used for persons who use the system and have permissions inside the system. Employees may have time cards, payroll, permissions, settings; they can also be used on expense/receipts and PO's and in these instances can be used virtually like a vendor. They also populate the salesperson list. 
• Equity - Equity is a section on the balance sheet which means some sort of long-term value. You can have different things like owner equity, paid in equity, investments, worth and distribution of wealth.
• EOT's - See Elements of Time. EOT is an acronym for Elements of Time. Another term is Time. When you search for time you are searching for an Element of Time. Technically you can have unlimited number of templates which are like cookie cutters. And then you can make an unlimited amount of cookies from those cookie cutters. It can go very deep.  
• ER's - Expense Receipt- these words used together mean any total amount of money that flows out of a bank.
• Expense Types - Chart of accounts for expenses. System comes with several options and the user creates the rest.

F

• Favorites - There are two primary ways that we use the word favorites in the system. One is a list of saved reports called your favorites. Another one is actually where favorites is a shortened term for My Favorite Buttons which are graphical point of sale buttons. 
• Flash - Flash is a shortened term for an Adobe Flash player. Flash has been used on the internet since early times. It could as simple as animations, special buttons, rich interfaces, etc. The software application uses Flash for navigation screens, check writing, barcode generating, and my cart favorite buttons (customer point of sale buttons). 
• Flash Bubble Interfaces -  There are three Flash interfaces that were designed my Russell Moore that may be used as default navigation homepages. They have special features such as rollovers, sliding menus, and drop downs. 
• Flash Buttons - Once again these are a shortened term for the my cart favorite buttons. Custom point of sale buttons setup by companies. These can be named, organized, colored, nest them, group them, preset settings, setup special pricing parameters, etc. These are often used as a standalone sale buttons or in the split cart view. Split cart has one screen of buttons and the other screen shows the cart so that you can see what has been added to the cart. 
• Flex Grid - Allows a user to custom code up to 30 fields per each main section. In short, flex grid allows the user to add additional tie ins, database fields and notes.
• Footers - A footer is anything that happens on the bottom of the page that is consistently there. Usually such things as navigation, branding, logos, copyrights, or other consistent notifications. 
• Form/Submit Form -  Anytime that a user can interact with a website is usually in a form. The software application has tons of web forms. Without getting super detailed you can have text fields, number fields, drop downs, text areas, radial groups, list boxes, check boxes, toggle switches, buttons, and other form features. The submit part of a form is when it actually gets sent back to the server and some sort of action takes place such as a search, an add, an update, a commit, a continue, etc. 
• Functions - This is a general term that could be used for what is your business function meaning process or flow. It could mean a logic decision behind the scenes - pass this variable to the function and you will get this result. It could also just generally mean how do things function meaning how do things work, how does it interact. Another term that we use sometimes is if you are dealing with API sockets (Application Programming Interface), we will often talk about the socket as if you are calling a certain function. 

G

• Gallery - A gallery is usually a collection of things most often photos, media/content, files, some sort of digital content. All of the 12 main players have their own galleries. Most galleries are tied to individual items within the groups. 
• General Tie-in - This could be one of two things. It could be talking about a thing called a flex grid tie-in which would be additional data related to the main item. Another reason we use general tie-in is if we don't know where the connection is going to go it can be tied to all sorts of things. Basically the tie-in means a relationship and general means you will need to categorize it.  
• GIF Image - A GIF image is a graphic and is considered to be in the Bitmap family. They have somewhat of a limitation on colors but they can still go up into the hundreds (like 256 colors). Some other really good benefits is they can have a transparent background and they can contain small animations.
• Global - This is a general term. We use it in a couple different ways. One would be a global variable meaning it is available for all. We have global settings which are generic across the whole system or a starting point. Then dealing with a world-building concept - global means within a world what is the style, attributes, presets, etc. for that world. All of these uses indicate broader or more general terms. 
• GPS - Global Positioning System. Basically inside of the software application, GPS can mean a physical location like an actual GPS or sometimes it is used as a term for a virtual locator of where I am in this world or in the system. Indicating a location, such as I am in invoices or deposits, etc. A cousin to GPS is something called an RFID tag. Both of them use some sort of X, Y, and Z coordinates but the main difference is that GPS is over a broader spectrum and RFID is in the confines of some smaller geo-fence but you can still tell where things are moving and can track things in spatial ways. 
• Gram Counter - Control added to the shopping cart for the cannabis industry that helps salesperson stay compliant in how much cannabis they sell to a customer. Multiple varieties exist based on requirements of the state of operation.

H

• Hardware - Technically this is computer peripheral type term. It usually means something that physically exists or something you physically connect to a computer. There is a physical aspect to it. You can see it, touch it, connect to it, it can contain it's own programs and software, etc. Some common pieces are laptops, desktops, monitor, disc drive, scanners, printers, and so on. Almost anything that has a physical component and an electronic piece that can be associated with a computer is called hardware.  
• Hash - The word hash has a number of different meanings. Usually inside of a computer system a hash means a small encrypted value that may be de-crypted or decoded by the computer. A way to make something non-human readable but still decipherable to a computer with the correct codes to unwind it. A general term for hash is a mix of things that gives you a new item or output at the end. 
• Headers - These are usually at the top of the page and have a reoccurring look, feel, theme, navigation, search options, menus, etc. It is basically a way of standardizing multiple pages to look similar - you can use or create a header. 
• History - History inside of the software application takes on numerous different flavors. History could be just what happens over time. It could also be user interactions, cause and effect cycles, check points, etc. The history is also a shortened word for the audit trail, the log files, and the decision trees within the system. Most histories inside of the system are unalterable - they are caught and monitored behind the scenes as actions take place. History inside of the software application can take on a couple different forms - effectual, historical, financial. These are all aspects of history but they all have a little bit of their own flavor. 
• Homepages - This is a web term for a starting spot or a spot that has like pieces. What we do is allow everyone to start with their own homepage or starting area. This allows them to navigate the system or have quicker access for the features they use. The other use of the term homepage in the system is for each of the 12 main players. All of these 12 main players have their own homepage or main hub for the features associated with that player. Such as invoice homepage, PO homepage, expense/receipt homepage, etc. Sometimes these are called sub homepages. 
• Hover - Action used to view links in the database. At the top of every page user can 'hover' over the main links to access myriad other pages in the database.
• HTML Buttons - There are two different terms for HTML buttons. Any form inside of the system technically has an HTML button to help it submit or do any other process. The other use of the term HTML buttons deals with my cart favorites and this is a comparison between Flash buttons or HTML buttons - meaning how the buttons are generated. 

I

• Ice Down - This is a term for basically permission based locking. This goes back to an analogy we use with liquid water turning more solidly into ice. As data in the system becomes more firm or set it virtually gets iced down. 
• Inactive - Status that designates data as being out of use. This status relates to customers, vendors, and items. When inactive, data will not show up in search and list by default. User must specifically request to view inactive data.
• Interactive Map - This is a graphic that shows a lot of the key elements inside of the system. A number of different departments, homepages, areas that have their own tools, etc. It is one of the standard navigation homepages. It is also used often for training when we are trying to show flow between the different areas or departments. The help file for that page goes into major details as to why things are organized on the map the way they are. 
• Internal Build PO - This type of PO is used internally to take raw goods and combine them to create something new (kitting, packages, groups, mini manufacturing, etc.). For example, say you wanted to make a cake, the raw goods might be flour, sugar, eggs, butter, etc. The internal build PO would subtract the raw goods from inventory (negative quantities) and create a new product called cake or cookies (positive quantities). This PO type has it's own permission and is very powerful.This same PO type is used by the system when using the internal recipe/build process. The recipes are basically a pre-set group of ingredients, parts, items, and/or outputs. These recipes are called "build and hold" recipes. The internal build PO may also be used when taking a certain part, painting it, heating it, cutting it, chopping it, combining it, or somehow changing it into some other part (any type of mini manufacturing). This PO type, internal build, is how you physically control your inventory counts. Similar to the update PO, this PO is not vendor specific and does require a special permission to use this PO type.
• Internal Repair - This deals with a stock/unit. Basically it makes an internal serialized item become a customer and you can use anything from your shop or store and attribute it or apply it to that specific stock/unit. 
• Invoice - Use to record a sale of any item or service to a customer.

J

• JPEG Image - A format for compressing image files. Every form in the database has a storage space for jpegs that can be accessed from the photo/scan button.
• Jump - This could be a couple different things. Often we will use the word jump to indicate some sort of motion or movement. This could be let's jump into this or jump to this place on the page or somewhere else in the application. Sometimes we use the same phrase when we talk about using the quick search inside of the system to navigate somewhere. So while this is an action term indicating movement and navigation it can also refer to times when you skip multiple steps by clicking or jumping somewhere. 
• Junk - This could refer to email, junk email. It could also refer to doing something which you are going to get rid of. Or it could be if you are putting garbage into the system, you are going to get garbage back out. This refers to putting bad data in the system - junk, garbage. 
• Just in Time - An acronym for this is JIT. This was originally developed in manufacturing and operational warehouses. Now it has been modified and is used in all kinds of things such as just in time inventory management, just in time bill pay, just in time project management, just in time communications, and so on. Instead of planning and preparing everything out to the nines sometimes you can do it just in time which saves both time and money and is an efficiency factor.  

K

• Keep - This is usually some sort of an action where you are maintaining or keeping something for later use. It could also involve something that you do continuously - for instance keep clicking on this, keep drilling down, keep refreshing, keep checking back, etc. Saying either save that or continue on that path. 
• Kill - This is a general term usually meaning to delete, destroy, make inactive, hide, etc. It is a general term that means to get rid of something. Other times you might talk about if it is going to kill the system meaning too heavy of a load, too intense, too many sub details, etc. 
• Knock knock - Who's there? It could be a joke but actually we use it in computer speaking when we are trying to gain access to API sockets. You play knock knock with the server. The server responds who are you? What do you want? Then you have to respond that those questions/requests. It is kind of a back and forth protocol. 

L

• Labels - Can be printed via browser settings from multiple locations in the database. Item labels can be used to add items to the shopping cart, item labels can be printed from within the shopping cart for certain industries, labels can be printed for plants from the cultivation homepage.
• Liabilities - Financial obligations of a company. Tracked on the balance sheet.
• Line Items - "Meat and potatoes of a form." Can be inventory items on a PO, expenses on an expense receipt, and invoice sales on a deposit.
• Link - A link could be an actual web link where you go from page to page. These are often used in navigation or drill-downs. A link could also be things that get connected or tied in. Such as an invoice might be linked with a customer or an item is linked with a PO. Another definition for link is an item within a chain of a process. What are the links that it needs to go through?
• Locations - Way to sort inventory, allocate sales tax rates, organize operations in the database. Completely dynamic.
• Lock - A lock usually means that something becomes more secure. It could be locking people out, locking things down, it could be advancing something so that people with lower permissions cannot access or see it. Another example could be a system being put or going on lock down - like the system or a database table. A lock is used to inhibit access. 
• Logout - Function that allows a user to leave the database. Once logged out, another user can log in from that computer. Note.. logging out does not clock out the user.
• Logs - Associated with customers/clients. Area where notes may be kept for historical reference.
• Look and Feel - Basically this deals with what you see. Your interface colors, your color choices, your navigation buttons, your interface layout design, your defaults, your style, etc. The software system allows for all kinds of dynamic colors, fonts, watermarks, graphics, logos, and styling to help with your look and feel. 
• Look Back Date - Usually this means that we are going back in time to look at data or content. Very common for inventory levels, sales, and balance sheet items.
• LPI (Lines Per Inch) - This is a printing term that deals with resolution. Another common one for this is DPI which is dots per inch. Often computer screens and printers deal with DPI where LPI is for professional print shops. 

M

• Main - The software application uses the term main in multiple different ways. It could be main homepage, main navigation, main or core logic. The word main might also refer to sub homepages such as main customer homepage, main invoice homepage, main deposit homepage. Going deeper the word main could also mean the starting of the object. Anything that can hold subs is a main. For instance the main invoice details or main element of time. We end up adding sub details, such as line items and payments, to a main bucket, item, or container. It is very common within the application to see the words edit main. This deals with going directly to edit the details required to start or initiate a new object within the system. 
• Make/Model - This is tied to serialized or stock/unit inventory. The make is usually similar to a brand name. Then the model is usually some sort of a sub division within that, that has some known attributes or pieces. In the system we allow you to define the makes/models and the underlying presets that go along with those. These are set up into one to many relationships where one make can have an unlimited number of models.  
• Manager's Time Clock - This is a permission/section that allows a user to oversee time clock records for departments that have been assigned to that manager. Time clocks have three different levels. You have the user level which is easy to add but you cannot edit anything. Then manager's time clock which allows you to add and edit but only at a certain level. Then admin time clock that allows for corporation wide adds, edits, and reports. 
• Mark-up - This usually deals with a pricing model where you take a value and you multiple it by a cost to arrive at a new price. Depending on if you are doing widget (small, bulk) type inventory or serialized (stock/unit) inventory there may be multiple levels of mark-up. Another way that mark-up is used is sometimes on coding language. A mark-up language is where certain things have tags, attributes, and parameters. 
• Media Content - Technically media/content is any kind of file, which could be spreadsheets, text documents, PDFs, graphics, photos, scans, audio files, video files, etc. that may be added to the system. Inside of the application we allow media/content to be added to any of the 12 main items, any of the 12 main player groups, or just generically to the system as a whole. Basically this is your paperless office function. 
• Merchant Processing - This is a general term used to talk about credit card transactions, authorizations, and processing. The system acts as the client side or software piece. It sends transactions over to a gateway which authorizes, confirms, and holds secure data. The merchant part of it deals with converting that data into real monies that will get pushed into the company's bank account.
• Mini Conversions - A conversion is where something gets converted into something else. Usually it deals with units of measure. For example gallons of water, liters of water, cups of water, drops of water, etc. The reason we use the word mini conversions is that we are trying to track a semblance of what is happening instead of a full conversion that might be unalterable. These mini conversions are simulating the breakdown or conversion into smaller or bigger groupings. 
• Mobile - This could mean mobile as in on a mobile device where the sizing or layout changes based on screen size. It could also mean the ability to carry, transport, or move around. It may also mean the ability to transfer pieces between things - the data can become mobile. The ability of the data to transfer between places such as to different corps, other software, different places in the application, etc. Often you might here the words mobile app or mobile ready - that usually means a software system that runs natively on android or iOS devices. 
• Money Types - Options for making and receiving payments.
• Money Type Settings - List that shows all existing options for making and receiving payments. Boxes may be selected or deselected to customize payment options based on form (Invoice, Shopping Cart, Deposit, Expense)
• More Options - Button provides access to links that are associated with the page in use. At the top of most pages.
• My Cart Favorites - Custom preset buttons that determine how items assigned to those buttons are sold.
• My Settings - This deals with access to user level settings within the software application. This could be anything from password and profile information to default cart types, expense types, Flash buttons, etc.

N

• Ctrl N - This is a keyboard shortcut on windows for creating a new tab in your browser window. Often you can do the same thing by right clicking a tab and clicking new or duplicate, etc. 
• News & Updates - Updates and how to's are posted here to alert users of new functionality within the system.
• Normal Parts/Items - The word "parts" is used to mean any item that is tracked as a group (including labor and services). It is also important to note that the words "parts" and "part number" are editable on a per corporation basis from the corp-wide settings. Specific items are called units or stock numbers (serialized units) and are handled through a different section (usually bigger ticket items). Sometimes the word normal parts applies itself to how things are tracked meaning tracking things in and out. 

O

• One to Many - This is a database concept and usually deals with some main element that may have subs, children, add-ons, additions, or some unlimited number of connections. Some examples could be one customer has multiple invoices or each invoice has multiple line items. We use the concept of one to many to talk way beyond just database things but that is where it came from. 
• One to One - This is also a database concept and usually what it means is a direct relationship. It's the opposite of a one to many. Often a one to one indicates a switch, a toggle, an additional value that may be conditional, an option of being turned on or invoked. 
• Online Bill Pay - This is where a customer would actually get a button, a link, or an email where they could go pay for a statement online using a credit card. 
• Open/Opened - This is a common term that we use to talk about being engaged, active, selected, etc. An example might be open this package, meaning make it active or current. Or open the invoice homepage, meaning go to that page and open it. Or you may hear someone say tell me what tabs you have opened, meaning what do you have showing. 

P

• Ctrl P - This is a keyboard shortcut on windows for printing a certain page.
• Packages - This is used in a number of different ways. Often it deals with batches for sub inventory. Sometimes they are called packages or child packages where you get into parent or child relationship. Packages could get into shipping. Packages could also be used for a certain set of features. For example if you were in a certain industry and wanted to buy the extended package that would be a set of extended features. Sometimes it is also used in the recipe/build area if you are creating certain recipes to create a package, or a kit, or some sort of group. 
• Page Settings - These deal with what happens on a single page. As a note there are corporation or world-level settings. There are group level settings such as invoices or PO settings. There are individual settings, there are also these page settings which deal with just how certain pages act, interact, show/hide, react, etc. 
• Parent - This usually refers to inventory and kind of a parent-child relationship. The parent is usually the main element or place holder. We then refer to the parent as the main item and the subsequent children are those related to that parent.  
• Parent Attributes - These are optional but these are classifications and categories that can be associated with different inventory items. These are ways to group and flag your inventories. This can help with sales and filtering of items/products. These are unlimited and often help in categorizing or searching or sub-filtering pieces together. As an example, say you bought outdoor equipment from a wholesaler but you really wanted to make sure that things were known for their brand. Not necessarily the vendor you purchased them from but the brand. This could be one example of a parent attribute but there are unlimited possibilities. 
• Parent Inventory - Inventory items. May be sold as is (status active) or may be set up not to be sold (allow subs only) but to act as name holders for sub inventory (see sub inventory). May also be set to inactive if no longer needed for sales.
• Parts - Items or services that are sold. The name 'part' can be changed to reflect the 'widget' inventory and or services. 
• Part Category/Categories - Organizes items into a subset. Technically a part category helps in searches, in your reports, and on your financials. It also helps if you are going to be setting up any sub inventory attributes. Most of your sales reports are done by category at the top level and then by item. 
• Parts Homepage - Main inventory homepage. May search for inventory by vendor, category, or item. Printable views also accessed from this homepage, as well as a multitude of advanced searches.
• Patient - System default is customer- patient is an example of a choice for renaming 
• Payee - Refers to individual or business being paid, either vendor or employee.
• Payments Not Yet Deposited - As invoices are created, payments are applied. This verbiage stands for the state of these payments. They are 'waiting' to be included on a deposit.
• PDF-Portable Document Format - a file format that is used to share data. Many pages in the system may be exported to PDF through the click of a button.
• Permissions - Over 100 rules that allow or block access to functions within the database. 
• PNG Image - Portable Network Graphic- type of image file that is accepted for upload under the Media/Content link located on most forms in the database.
• PO's - This abbreviation stands for both Purchase Order, used to receive inventory and Production Order, used to record and track light manufactured items.
• Post - A post has a couple different things that it could be. One, any time a form is submitted it is called a post in technical terms. A post in accounting usually means let's lock it down and make it tight, also meaning lock it down from lower permission users. A post could also mean when you take smaller details and combine them into a summed entry, this entry can also be called a post. If you are talking about fences, it's the big tall thing. :)
• Printable - View of data that is condensed in order to print more succinctly. Editing is unavailable in the printable view.

Q

• Quick Search - This function appears on each page and allows one to quickly search for any element.
• Quote - The step prior to creating an invoice. Can be skipped if desired or created and turned into an invoice.
• QR Code - A two dimensional barcode that holds more data than a one dimensional barcode. 
  
  

R

• Raster Image - This is also sometimes called a bitmap image. Usually what this means is that there are little blocks of color to make the image. If it is blown up to big it can become pixelated. For example, people who work in PhotoShop deal with raster images all the time. The opposite of a raster image is what is called a vector image, which deals with smooth mathematical lines, arcs, and curves. Vector images scale very well because they are mathematically based. 
• Recipe/Builds - Method of selling items grouped together into a 'kit' or 'recipe'. Pulls inventory onto the invoice in set quantities.
• Refresh Queue - A queue is basically a digital line. This could be used for projects, people waiting, people who need to be served, etc. Refreshing the queue typically just means what is the current status or order of these people or things waiting. Some of the pages actually have settings so that the queue will refresh itself at an interval the company has selected. 
• REI's - This is short for a reimbursement. A reimbursement is money that was paid out of a person's pocket that needs to be paid back directly to that person. These are very common in the expense/receipt side of the application. Fro example, say I was out and bought a new broom and wanted to have the company reimburse me for buying the broom. On a technical side reimbursements in the system must be paid back in full. There is something called a split in the system that you can chip away at an expense and make payments to it but a reimbursement must be paid in full. There are tools in the systems to combine or pay reimbursements in bulk. 
• Reoccurring Elements of Time - Often you will have things that you want to reoccur over and over again such as company meetings, a set/reoccurring due date, even a person's schedule - things that happen over and over again. Inside the system you have to create one primary element of time that exists by itself, then you can tell it to reoccur or choose how to reoccurs. The master needs to be created first and then you can duplicate that master to create the further elements for reoccurring. 
• Reoccurring Expense Receipts - This is some sort of a bill or expense that happens over and over again. This is very common for rent, insurance, draws, auto-transfers from banks, etc. You set up the master and then you can tell it when to duplicate itself and advance it's dates for creating the additional expense/receipts. 
• Reoccurring Invoices - This is charging a customer over and over again in some kind of a reoccurring subscription, or repetitive purchases, etc. Once a single invoice is setup it could be set to reoccurring if there is some sort of constant, regular billing. If the invoice amount changes you may not want to go this route. This is best used for the same items/services and amount reoccurring on a regular interval. Once again you have to have a master invoice and then it knows what to copy. This section inside of the system can do it both automatically and as a manual reminder in case things need to change. 
• Request PO - This PO type is used for ordering, requesting, or getting quotes from vendors. This PO type records all of the main PO info without taking it to the next step (receiving). The PO request may easily be turned into a "Basic Live" PO by switching the PO type. When this happens, the request will hold all of it's original info and becomes received (actual or live). At this point, it will function just as a basic live PO would (inventory counts and payables). This PO type is vendor specific. See corp-wide settings for custom naming.
• Responsive - This has a couple of general meanings. One of the most modern ones is called a responsive webpage, meaning it sizes well for different devices. The layout will change depending on the size of the screen, that is called responsive. Another use of the word responsive is talking about clients getting back with you, vendors, or even the server - such as the server is not responsive meaning that it is not responding to requests presently which could mean it may be asleep or dead for a bit.
• Restore to Cart - This means you are taking something, usually a quote, and putting it back into the flexible shopping cart mode where you can add, edit, change, and use the bulk tools in the shopping cart. As a note, restore to cart is from quotes but there is also an option to duplicate to cart which is taking a completed invoice and restoring it to the cart. 
• Results - This is also a general term. It could mean a goal - what are you desired results. It could mean results of a query - what came back from a search. It could also deal with testing results for something such as new code. Results are also trying to find what you are looking for. What do you get out of this thing that you are looking for. 
• RFID - Radio frequency i.d.- Used in the cannabis industry to track all inventory and plants. Unique number associated with inventory items.
• Rounding - Rounding deals with the level of accuracy, usually with number. This could be decimals to decimals or decimals to integers. It is also important to know that the deeper you split something apart there might be virtual saw dust or shavings which is referred to as rounding error - trying to get it split apart or broken down as close as you can. Rounding is often used in taxes, discounts, and eventually needs to be equated into money if you are dealing with dollars and cents. Sometimes inside of the system we allow things to be flexible up to 5 decimal points - the term we use for this in the application is the dewy decimal system - this is not related to libraries.   

S

• Sales Tax Settings - All settings are dynamic and can be entered on the location homepage. 
• Server (what server are you on?) - All corps are assigned a server that houses all their data. Server number is visible in URL ie. https://data4.adilas.biz
• Settings - Settings are usually some sort of user preferences or default values to help a page or a function configure itself. Inside of the system there are four main types of settings. We have corporation or world level settings. We have group or system player settings - for example invoices, parts, customers, etc. We also have what are called page settings which deal with a specific page function, flow, or process. The lastly we also have a thing called individual or user settings - this is where an individual or user gets to set some preferences such as default types, navigation, other presets and defaults. 
• Shopping Cart - Where sales happen in the database (see also Cart).  The shopping cart is how you sell your stuff. It is the interface between your customers and the entire rest of the system. The shopping cart eventually helps you to create your invoices and quotes. It is literally tied to almost everything in the system. If you took out this piece of the puzzle, not much would be happening. This is the "interface" piece.
• Show/Hide Search Criteria - This is usually a button or a link that helps you collapse or expand search forms. Often pages or reports needs user inputs or filters but showing that right off the bat takes up valuable real estate on the page. So the show/hide search criteria allows you to expand or collapse that when you need to interact with the input, filter, and searching section.  
• Smart Group - Basically, a smart group button is a my cart favorite button that contains all of the functionality of the normal cart favorite buttons plus it allows for pre-set pricing structures (quantities, weights, and prices) to be assigned or connected to one or more inventory items. Smart group buttons allow for both assignments (who gets to play) and rules (how things interact or play) to be set up.
• Snow Owl - This is a look and feel theme or motif. Snow Owl is a series of header, footers, options, settings, and styling for the pages. Originally developed by Russell Moore in 2017. Additional changes have been made. This theme currently has the most modern features, access to tools, functions, settings, and more. Sometimes we talk about Snow Owl in a general sense but this encompasses hundreds of settings, features, and options that are part of running Snow Owl. 
• Software - This is a term meaning any kind of code or program that is installed on a machine. Often software deals with licenses, updates, versioning, etc. Some of it's family members are hardware, firmware, freeware, shareware, and even sometimes vaporware. Even though the system is a web application it is sometimes generically called software. 
• Special Line Items - These deal with the hardcoded part numbers or "special line items" that are used within the application. Many of them have special uses and special code that is built in to the main application. These are things such as labor, fee, discount, verbage, other, shipping, trade-ins, and more. Basically these are special parts or items that can be attached to an invoice or PO and some of them even have special treatment on how they are tracked financially on the P&L and Balance Sheet.  
• Special Live PO - PO used to bring in inventory from multiple vendors. This PO type allows the main vendor to be set as the payable (who will get paid), and the line items may contain bulk, generic, or non-vendor specific items. These PO types are used by companies that buy the same item from multiple vendors and don't want certain items to be tracked on a per vendor basis. The items become a bulk or general usage item and are usually maintained under a special internal vendor. 
• Special Parts - This can be two different things, it can refer to unlimited items that don't track quantity such as labor or services, or it can refer to the special built-in application items.
• Special Request - This is the request side of the special live PO's. Very similar to a basic request except it allows multi and mixed vendors. See description of special live PO's above for more info. Once received, all special request PO's will need to be flipped over to the special live PO status in order to show up and become real or live. 
• Specific - Specific basically limits the scope. We use it as a general term and it could mean specific in reference to talking about a specific item or a specific relationship. We also use it when referring to things like corp specific, vendor specific, location specific, user specific etc. Once again it takes that general topic and narrows it down to that scope. 
• Split Cart - Feature that allows user to view shopping cart and my cart favorite buttons on the same screen simultaneously (see M for My cart favorite).
• Split/Splits - This has a number of different features associated with the word splits. This could be split payments - which is typically dealing with multiple locations where you may have to split or divide payments. A general term called splits in the system is a term used for payments that are on account. This is used when you need to pay a vendor and you may owe a larger sum than you can pay right then. You can attribute whatever monies you would like to that vendor's account and it will pay off or satisfy those expenses. Sometimes split can refer to split screen functionality that diverges or splits. If you are dividing revenue sharing you might create some sort of a split. 
• Start New Cart - Function that allows user to begin a sale.
• Statements - a time stamped report or "snapshot" of who owes you what.
• Stock/Unit Cust - A restricted view of serialized inventory. The view is 'customer' friendly, hence the name 'Cust.'
• Stock/Unit Full - A full view of serialized inventory. Includes cost and other info that should be hidden from customers.
• Students - Technically a student is a person who learns. There is a corp wide setting that you can use for your customers and if you happen to be engaged with people who are called students you may change your customer name to student. This can also deal with people who are learning from your media files or procedures. 
• Sub Attributes - Unique information associated with a sub inventory item. This information is driven by sub inventory templates that are created based on the tracking needs of the business (see sub attribute templates).
• Sub Attribute Templates - Templates that carry the unique data assigned to sub inventory items. These are assigned by the business based on tracking needs.
• Sub Inventory - Items in the database that can be sold. Connected to a parent item (parent inventory) which carries the name and some information. Sub inventory is unique and can carry much more unique information (see also Child).
• Switch Corp - If a business has more than one corp they can switch between them without logging out.
• System Assets - Contains all company assets. Deposits, Accounts Receivable, Invoices etc.
• System Basics - Basic permissions and links to preform calculations.
• System Liabilities - Contains all company liabilities. In general all payables that your company owes.
• System-Maintained BSI - Item on the balance sheet that are automatically generated and updated by the database.
• System Maintenance - Section that contains homepages that allow the user to maintain different functions.
• System Management - High security level that allows the user to maintain corpwide settings and user permissions.
• System Reports - General reports to help you know and understand the company finances, inventory levels and historical data.
• System Time & Requests - Inter company calendar. Used to schedule any 'element of time.'

T

• T terms connected in the sub notes below - click to view whole document

U

• U terms connected in the sub notes below - click to view whole document

V

• V terms connected in the sub notes below - click to view whole document

W

• W terms connected in the sub notes below - click to view whole document

X

• X terms connected in the sub notes below - click to view whole document

Y

• Y terms connected in the sub notes below - click to view whole document

Z

• Z terms connected in the sub notes below - click to view whole document

Steve and Sean were talking about ecommerce and what is needed to keep systems going. Lots of moving pieces. After that, it switched over to a sales meeting. Steve was asking questions about some dealerships and recent contacts that Sean and Marisa were making. We talked about how much custom code is needed per client or per industry vertical.

We got into a conversation about the client facing scheduler and how cool it will be, but also how much code it will take to make it fully functional. The subject then flipped over to automation, wizards, settings, training, and education needs. As things get more complex, there needs to be ways of letting people know what is needed and what needs to be done. If the education is not there, it actually makes it even harder to figure it out. We talked more about ways of helping to speed up the training and onboarding processes. We need a way for our client to figure things out and/or be educated on what is possible and what is needed. Steve was mentioning that we need a balance between sales and new development.

As a side note, in some of our design prototypes for the fracture project, we were working on a better UI/UX as well as a thing called education mode (toggle on/off for extra help and information). The goal was to make it available but hidden. If it was needed, it was there. If it wasn't needed, it was hidden but still avaiable. Also, a good UI/UX will help eliminate some of the education stuff (not all of it).

The final topic of the morning meeting was dealing with advertising and pushing that forward. We also talked about having the best team we have ever had. Good stuff!

Looking into needs and wants for the date/time pickers. Created a small to do list. We then jumped into unique event settings. We talked about new possible time settings (see element of time # 8004). We got pretty deep going over potential and where we want things to go. The goal is to make and create an "Any Scheduler" or an "Any" Scheduler. We also went over some look and feel stuff and where we are headed there. I showed Bryan some recent news and updates and how we are planning a full facelift for the time or elements of time section. Just for fun. Here are some our notes that we were passing between the chat session over GoToMeeting.

Meeting with Bryan on time templates and sub templates for availability

- Define what we want...

- How are we going to tie things in?

- What will it look like?

- How will they control it?

- Permissions?

- Settings?

- Availability?

- Just time slots that are open (appointments, hair salons, PT-physical therapy, etc.)

- Book a range (campgrounds, cabins, rooms, etc.)

- Internal - able to do this right now... - it would be cool to speed it up

- External - only able to do reoccurring one-to-many and unique events - we need the 1-1 (one-to-one) or one party to a certain event or place or timeslot.

- "Any Scheduler" or "Any" Scheduler >> and go online with it - what are the rules to make it easy for a user but flexible and powerful (backend)

Meeting with Bryan and going over the "any scheduler". He was showing me an older campground reservation system that Will and Steve did inside of adilas back in 2018. It has been pretty buried and not used that much. Bryan was looking around at other different scheduling options such as Airbnb, hair salons, etc. Looking at how we do it internally (selling and booking time).

We started talking about availability templates. Basically, timeslot placeholders. Lay it out and then use it if needed. We did some brainstorming and after we stopped, I was thinking that we also need payee id (user stuff) and store id (location information). Making progress.

Work session with Bryan going over projects. We talked about date-picker stuff and then moved onto scheduling. I was pitching a small proposal to add in a temp roster for the horizontal time view. This would be a JSON formatted setting that would allow you to pre-load in certain people to your horizontal time view. It's not real availability, but it was a step in the right direction. I did a bunch of drawing and brainstorming with Byran. Most of it was on the fly. He recorded a few notes.

We then switched and got into deeper availability and the layered calendar options that we are planning on building. This flow would allow us to prep or overlay a schedule or virtual availability schedule over the main calendar (elements of time). We went over ideas for flow, logic, and what it might look like. We determined that there were 3 main steps. For a single assignment, we would need who it was that was being assigned? The who could also be the what. For example: are we setting the availability for a person, place, or thing? That's step one. Step two would deal with a date or a date/time range. These first two steps would always be required. The third step would ask if we need to reoccur or duplicate those new availability settings. We would need to select that option, only if needed. If used, we would copy or duplicate the existing settings in bulk.

We got into tons of details and ideas. Lots of drawing and brainstorming. Bryan and I were even playing in Microsoft Excel and doing some fake table layout and data input stuff for the new layer tables. We would like to think of the new overlay functionality for the calendar as layers or availability layers. This will end up being part of our "any" scheduler. Behind the scenes, we will have the real elements of time (that already exists). The front or overlay layers will be for things like employee scheduling, non availability, holidays, web availability (options for online booking), etc. Fun stuff.

Planning with Bryan. The topic of the day was brainstorming on the "any" scheduler or any scheduling stuff. We talked about a number of different steps and what we could save and where.

1. We will use JSON page level settings for simple and advanced (shifts) rostering. Thinking about a number of different tabs going across the page for the new settings. Tab 1 would be simple full day rostering, tab 2 would be advanced shift level rostering, tab 3 would be shift settings, and tab 4 would be the web availability stuff listed below (in number 2).
2. The more advanced stuff will be saved in the layers or availability layers. We have already come up with 3 sub steps of that process. Click here for more info about the web availability layers. As a note, the web availability layers would be saved in a database as individual records vs JSON object storage. It will help us look things up and map usage/availability levels better.
3. We will offer a number of different, user defined, saved favorites. These are custom reports with saved search criteria. Some of these may be calendar views, horizontal time views, vertical time views, and other custom reports. Here are a few links with some ideas. See element of time #'s 8004 and 6967 in the shop.

Good brainstorming session and going over ideas. We got pretty technical and did a lot of drawings. It's fun to see how things progress and the progression of things.

Bryan and I looking at the advanced rostering and scheduling options and settings. We are getting into things like days, swing, and graveyard shifts. More work and planning on the "any" scheduler. Talking about next steps and going over plans. Bryan is doing great and we are adding in more settings to help things be data driven vs just code driven. That allows us to cater to more people and clients without super detailed custom code. If we base things off of the settings, it becomes data driven and even if it does something special, it is based off a setting, so other can use or do the same thing. Good stuff!

Notes and thoughts about an MVP (minimal viable product or minimal viable plan) for Fracture - future project for adilas:

- Dynamic yet standard CSS - allow for others to change their dynamic CSS (look and feel) - maybe hold some of this in settings and in the database somehow. That way, they could always change it and we could dynamically pull it in on the fly.

- Full API socket access with good documentation. Every feature, every function, super small getters and setters for each section.

- Funding options - real money, time, products, investments, selling percentages or shares, etc. Be open to lots of options. Multi million dollar stone soup type analogy.

- Along with funding the options, I would like to make a page that shows the time value of money based on total gross sales by Adilas, LLC. For example: If someone wanted to buy a percentage or share, they could see the total gross revenue (year over year sales totals) and then see what that value is multiplied by a factor, say 3. The standard is between 1-10 times of the total gross revenue as a general ballpark number. We could show them a price and then let them purchase that percentage or share (somehow contact us). Each day that the page is up, the price would go up daily, based on the total gross revenue. Just for fun, they could roll it backwards (view only), if they wanted to look at things based on past dates. Just playing with numbers. We may have to figure out some other things, just an idea.

- If we did seek some outside funding, we could put up 20-30% of adilas (shares or percentage for co-ownership). We could also open up options for funding as a loan or to lend or loan Adilas, LLC monies. That money could be put on the balance sheet with promissory notes plus interest.

- Just as a rough number, shooting for $10 million in funding for projects and future development. It very well could go beyond that. We could start on projects once we get a portion of that (seed monies). Technically, we could start with anything. Shooting for a smaller $2 million for a seed money level start. If further budgets were needed, they could contain things like marketing, sales material, training, education, documentation, look and feel, interface changes (UI/UX and GUI updates), new features, bulk tools, upgrades, maintenance, servers, team members, admin/management, developers, support staff, internal training, different roles and responsibilities, hourly wages/compensation, salaries, perks, plans, project management, R&D, AI (artificial intelligence), "Any" scheduler, design work, API sockets, consulting, white labeling, settings, permissions, templates, marketing, advertising, promotions, sales, certifications, merchant processing, external marketplace stuff, 3rd party solutions, and other areas. Just putting a number out there for a general goal.

- Another thing that we want to keep doing is creating content - written, verbal, visual, video, etc. Good, clean, data, and content.

- Make an MVP plan for where we are going - we already have lots of research and planning for fracture and other projects - just need to pull it all together. Pitch the pitch and review other notes. See the developer's notebook for other topics as needed. Most of the notes are stored there or are referenced there. Great resource.

Meeting with Bryan on some of his new settings for the "Any" scheduler. We got super deep into the logic on the horizontal time view page. He is currently working on rostering for different shifts.

Met back up with Bryan for a planning meeting. Going over horizontal time views (see EOT # 8004 and # 6967 for more info). Coming up with ideas for the any scheduler. Looking at ways to reuse concepts, functionality, and code from existing pages. Especially the horizontal time view page and the calendar view pages.