all data is live and searchable
[reset this page] .
[historical web outline - entries by month] .
[adilas community funded projects] .
[contact adilas.biz support - email form] .
[help]
|
Adilas.biz Developer's Notebook Report - 12/1/2013 to 12/31/2013 - (52)
|
||||||
|
Photos
|
Time Id | Color | Title/Caption | Start Date | Notes | |
|
AU 1888 |
|
Daily Tasks | 12/2/2013 |
• Working on a custom patient upload for a client. List of 3,000 persons; some already in the system and some that were not yet added. Migrated the records and invoiced the client. • An intern came over and we worked on his credit card validation functions. He is also working on the credit card gateways and turning their code into functions as well. Good stuff. • New logo for a client. • Email and tech support. • Started working on the view history section of eCommerce. This deals with showing account activity for customer and clients. • Working on showing invoice histories for back-end eCommerce pages. • Helping an intern with media/content application. • Working on showing quotes for backend eCommerce pages. |
|
|
AU 1889 |
|
Daily Tasks | 12/3/2013 |
• Prep work on the adilas platform concepts and theory. Found a couple good entries in the adilas university site for the developer’s notebook. They were 4/12/12 and 9/28/13. Good stuff. • Making some phone calls on SSL’s and how best to set up server structures. • Went in to Bridgerland to work with the interns. My sister and two interns were there. We started out with my sister doing some training on PO’s, inventory, and parts. We played in a play site and added tons of candy bars and different items. We flipped PO vendors and even did a global find and replace on a duplicate items. After the training we briefly talked about how quick things transfer directly to eCommerce. • We then did a two hour brainstorming session on the current adilas server and database structure. We talked current state and tons about future plans. Lots of talk about platform and making adilas into a full on business platform. Steve joined our GoToMeeting session and really helped out a ton. Of the 2 hour session, Steve talked for about 45 minutes on different subjects. Great session. We recorded the whole session through GoToMeeting. I spent quite a bit of time drawing out small models and diagrams in a graphics program. It worked out pretty slick and helped to illustrate the points that were being made. Awesome session! 30 miles. • My sister and I sat down and went over 10-15 categories in the adilas user guide. She took notes and I talked and showed concepts using some of the training graphics. Fun mix of history, concepts, and basics. -On payroll taxes, we have had the request to check into tax settings for persons who work in multiple departments. Currently, the system treats each employee and each department separately. Some of the employers would like it to track independently, like we do in the back end, and then bring it together in the front end as a group. That way they make sure that the employee is getting enough taxes withheld. |
|
|
AU 1891 |
|
Daily Ideas | 12/3/2013 | -On payroll taxes, we have had the request to check into tax settings for persons who work in multiple departments. Currently, the system treats each employee and each department separately. Some of the employers would like it to track independently, like we do in the back end, and then bring it together in the front end as a group. That way they make sure that the employee is getting enough taxes withheld. | |
|
AU 3650 |
|
Tech - Current adilas.biz Model as of 2013 & Proposed 2014 Model | 12/3/2013 |
Current Model for adilas.biz as of 2013: (Please see sketches in photo gallery) - Adilaswebservices.biz – web presence parts & stock/unit inventories - Adilas university – small shell with email functionality - Main adilas.biz server – dedicated box, SSL, database, photos, main application box Proposed Model for adilas.biz for 2014: (See sketch on scan in photo gallery) |
|
|
AU 1890 |
|
Daily Tasks | 12/4/2013 |
• On the phone with Steve. Talking about server clusters and expansion options. We talked about label needs and fixing a special label for invoice line items. Lots of talk about reps, training and upcoming needs. • Checking out some new label requirements for Colorado MMJ groups. Added the new requirements and did some testing. • Called and talked with Steve. • As a note two interns were over here today working on projects. • Emails, tech support, and getting gateway files and documentation for an intern as he is working on credit card gateways and such. • Working with an intern on the media/content project. We added some java script to help validate against forbidden file extensions. • New logo for a client. • Helping intern with the media/content project. • Also looking at some software commercials for ideas. • Working on a logo for a play site for a guy who is in North Dakota. • Also worked on a new logo for a client. |
|
|
AU 1892 |
|
Daily Ideas | 12/5/2013 |
-When going to the platform level… Make sure and keep users greater than corporations or worlds. This may require a master user list on the admin adilas world. Each user needs to be tied to a home planet or world. -It might be funny to treat users as if they were space or cloud travelers. They need a home base or home planet. They could also gain virtual passports or visas to go and visit or work on other worlds. Once again, keep and/or make users be bigger than corporations or worlds. -I am thinking for this first round of splitting up the adilas system, that we need to move off all traffic from the main adilas.biz server. My initial cluster will be the main adilas.biz server, D1 (data one), D2 (data two) and MC1 (media/content one). -So in other words… Cluster 1 (cluster one) will have three (or more) data servers and one content server. It will look like this: (see sketch in photo gallery) o CL1 = Cluster one o MC1 = Media/content one o D1 = Data one o D2 = Data two o D3 = Data three o Main adilas = special mother ship data server -As an additional note… The different pieces could also have an alias or nickname. We could use either the cryptic names or the alias names. Treat it like a neighborhood or town. Cryptic might be “1200 North 200 East”, the alias may be “Hill Haven” or “Ranch of the Rockies” or something like that. Think physical address or general subdivision (area). -If we allow world traveling… do we want to monitor who goes where? Is this shown, searchable, or hidden? -Plan that many businesses may end up being interconnected and/or related in one way or another. Set it up so that the different worlds can view who has access to what and what has been done. Take adilas out of the picture… Let world “A: do business with world “T” without having to ask the adilas world if that is okay. Think of easy interchange options like Legos or different building blocks. If you make some standard connections, virtually anything could be bolted on, snapped on, or used as an add-on piece. -Small note about platform and space… We draw clusters as if they live right next to each other. In real life, we could use virtually any configuration. Think in all different directions (space). As I think about this… the only real cluster is actually the data boxes or data servers. Those are a single physical box or computer server. The thing that make a “cluster” is which data servers are tied to which media/content servers. So maybe, we need to say “data clusters” and “media/content clusters”. Anyway, just trying to figure out some naming conventions. -Trying to figure out the general structure and what to call things…. Internet – Web or Cloud Level Adilas – Universe Level Media/Content Server Clusters Data Server Clusters Database(s) Level (at least one is required) Corporation(s) Level – world level Location(s) Level – geographic areas or virtual areas Sub Classifications – optional Departments – optional -Working on the structure of how to organize the adilas worlds. This is a semi expanded list. This could be expanded to super techy levels. (See sketch in photo gallery) 1. Internet – Web – Cloud – Beyond??? 2. Adilas Admin Level – Universe Level 3. Media/Content Server Cluster – optional and light relationship 4. Domain – Data Server Cluster – Independent piece – Requires an SSL, domain name, a box or a server. This is the start of the data server cluster or DSL. App server. 5. Databases – At least one but possible to have many on the same data or app server. 6. Corporations – World Level – At least two per database. One as a dummy and one as real value. There may also be a controller corporation per database (depending). 7. Locations – Areas – way of divvying up a corporation. At least one location per corporation is required. 8. Sub Locations – Optional sub category of the locations. This piece is not yet done. 9. System Player Groups – 12 main groups. Most of these may be tied to allocation. Some exist outside of the location scope but still under the corp or corporation scope. 10. Departments – optional sub under users. |
|
|
AU 1893 |
|
Daily Tasks | 12/5/2013 |
• Brainstorming on server structures and world building concepts. See other notes a couple pages back. • Went in to BATC. The interns and my sister were there. We used the big white board to draw and sketch out ideas and naming conventions. We also found that the content servers may be a looser tie or relationship than originally thought. We took some pictures of the brainstorming session on the whiteboard. We watched a fun video about the data center of Facebook. That was pretty cool and made our project look much smaller. My sister did some training on recipe/builds and we had some fun playing around in those sections. • Light code work on the media/content project. 30 miles. • Brainstorming and sketching more ideas about world building levels and data structure pieces. • Went out to my brother’s house to get some more video clips. He had 20 new clips for me. 20 miles. • Emails. |
|
|
AU 1914 |
|
Daily Ideas | 12/5/2013 |
-On sub locations and sub classifications (previously known as invoice classifications)… These classifications may need a tie to an actual location even if it is “all” or one (unassigned). Basically, I’m thinking about combining the two sections. A sub location could be a sub classification tied to a main location. Currently this section doesn’t exist. Anyway, maybe think about combining sub locations and sub classifications vs. an invoice classification deals with opening it up more to be able to play with any of the main system player groups. Such as expense/receipts, deposits, stock/units, PO’s, etc. -Check the multiplier on the build and hold recipes. There may be a multiplier problem. Maybe rework and check math. -On the server and data structure model. It could also be expanded to include: Groups, individuals, data, and time. Without indenting it might look like this: 1. Internet 2. Adilas Admin – Universe Level 3. Media/Content Server – optional 4. Domain or App Server – Data Server 5. Database – Cluster Level ---- Note: as of 12/13/13 The Cluster Level will be on the database level. It started on the media/content level, then the server level, and now the database level. ---- On 12/20/13 it changed again – Universe, Galaxies, Clusters, Solar systems. 6. Corporations – World Level 7. Locations – (prior page numbering) 8. Sub Locations – optional – (prior page numbering) 9. System Player Groups – (prior page numbering) 10. Departments – optional sub of users – (prior page numbering) **New numbering – Basically, below the world level, things really blow up and get into the details, relationships, etc. 6. Corporations – World Level 7. Locations a. Sub Locations – optional 8. System Player Groups a. 12 Main Player Groups i. Customers 1. Customer Types – user defined – dynamic list ii. Invoices 1. Invoice Types iii. Quotes – (Etc., etc., etc. – it just keeps going and going – deeper and deeper) – as another note… this is where sub classifications would come in to play, possibly for each main player group. iv. Parts – General Inventory Items v. Stock/Units – Serialized Inventory vi. Elements of Time – Calendaring & Scheduling vii. Employee/Users viii. Vendors ix. PO’s or Purchase Orders x. Expense/Receipts xi. Deposits xii. Balance Sheet Items – As a note, each one of these 12 main player groups could have tons of subs, types, and special functions ---- this gets pretty deep! 9. Individuals – Unlimited number with a huge variety. These are objects and are tied to the 12 main groups. 10. Data Level – these relate back to tables in the database or what bucket to store the date in. a. Main b. Line Items c. Payments d. System History e. Flex Grid Tie-Ins f. Special Subs & Relationships g. Photos & Scans h. Custom Documents i. Other Content 11. Dates & Time – Run all levels over “Time” a. Years b. Months c. Weeks d. Days e. Hours f. Minutes g. Seconds -We watched an awesome video on Facebook and how they track and store huge amounts of data. Very inspiring. Their goal is to be big and huge. They have huge data centers with tons of servers. Our goal is to be super small and nimble vs. huge and at a single giant datacenter. I want to be in datacenters all over the world. We could take up a small corner or a couple of bays on a server rack and be totally happy. Zero overhead. Spread out. Be all about tools, service, and customization options. We could potentially live anywhere - US, foreign, web, cloud, Intranets – behind company firewalls, and even on personal computers and devices. |
|
|
AU 1894 |
|
Daily Tasks | 12/6/2013 |
• Small tweaks on the ACH stuff for Shari. Looking into a web service problem between the main adilas.biz server and the adilas university server. • Emails and tech support. • Recording notes in notebook. Helping an intern with the media/content project. |
|
|
AU 1895 |
|
Daily Tasks | 12/9/2013 |
• Emails. • Tech support, phone calls, working with an intern on API settings. Paying bills and recording expenses. • On the phone with a client dealing with storage units and reoccurring invoices. • Recording notes. • Meeting with some contacts about a security bidding and tracking system. We talked a lot of options and ideas. Good meeting. • Special update for a client on their customer types. Missed a small piece on the last digital upload. No charge. |
|
|
AU 1915 |
|
Daily Ideas | 12/9/2013 | -Request for more options to show when viewing an invoice line item report. Three new requested fields are: the part weight value, the part reference number, and the part RFID field. These fields are tied to part numbers but they are wanted on the invoice line item search results. Virtual pass through values. | |
|
AU 1896 |
|
Daily Tasks | 12/10/2013 |
• Recording notes in my notebook. • Working with an intern on where we are going. We both went to Smithfield to get him some GoToMeeting footage from our adilas design meeting back on 12/3/13. 20 miles. • Went in to Bridgerland. I had to wear the neck brace. My neck has been hurting. I worked with the interns on their projects. We did a group lesson on adding pagination to reports. An intern worked more on the media/content project. 30 miles. • Email and bank stuff. |
|
|
AU 1897 |
|
Daily Tasks | 12/11/2013 |
• Emails and tech support. Getting some training DVD’s ready for a rep in California. • Recording notes from loose pages into my notebook. • Working with an intern on his credit card validation and formatting functions. Good stuff. This is his first live project and it looks very good. I was very impressed. • On the phone with Steve. Going over funding and upcoming projects. Exciting times. • Ordering two new servers. Reviewing old quotes and looking at new prices and features online. Called and left a message for Newtek. • More signing off on an intern’s first live project. • Another intern came over and we had a design meeting for the growth of adilas and where we are headed. We spent most of the evening at the table drawing and hashing out ideas and who will need to do what. Great meeting and lots of good ideas. A couple of notes of importance are: single sign on – this is a single login that allows a user to sign in once and then move around at will. We already do this; we just didn’t know what it was called. The other key word is “fractal”. This is a series of patterns that repeat over and over to form a whole or certain shape. This intern used this word to describe what we were doing. Basically, a server and database structure that repeats itself and makes other shapes by doing the same thing over and over. A fractal. |
|
|
AU 3651 |
|
Brainstorming: Server Structure & Migration | 12/11/2013 |
Brainstorming server migration with an intern: 1. Get new server, get new domains & SSL’s 2. Duplicate over to new server 3. Figure out who is moving 4. Inform who is moving 5. Create redirection 6. Maintenance – shut down corps on the opposite server 7. Work on getting extra data out Developer: 8. Create blend database – figure out pre-populated table 9. Plan Mother ship Postponed 10. Start work on mother ship 11. Get MS server 12. Transfer info to MS 13. Work multiple DBs on same server Brainstorming with an intern – going over server structure: (See sketches & relationships on scan in photo gallery) 1. Script to create a new instance of the db… defaults, code, prep for the new corp a. Table structure (keys, indexes, etc.) b. Default values and code tables (dummy) - Application - Session - FORM - URL - Variable - Argument Corp id needs to be the master Brainstorming with an intern: Server Structures (Please see sketches and layout on scans in photo gallery) Cluster Loose Cluster Domain Level Brainstorming with an intern: Server Structures (Please see sketches/scans in photo gallery) Brainstorming with an intern: Client Application Structure (Please see sketches/scans in photo gallery) |
|
|
AU 1898 |
|
Daily Tasks | 12/12/2013 |
• Checking out new servers. Ordered three new servers. Talked with the sales rep, reviewed quotes, and went ahead with it. Exciting! One new media/content server and two new data servers. Also ordered 5 new domain names for future data servers. Emails and tech support. • Went in to Bridgerland to work with the interns. Brainstorming with interns on server layout stuff. Lots of drawings on the whiteboard. We talked lots of concepts. Talked about objects and data over time and how to speed up processes. We talked about splitting databases, indexing numeric dates and times, and cloud structures and virtual load balancing. We need to plan for media/content servers, data servers, databases (clusters), and then corporations with in the databases. Light research and talk about existing cloud structures and how they handle similar pieces. Still leaning towards our own manual load balancing and cluster models. 30 miles. • My sister came to Bridgerland and taught us a great class on concepts of mixing and blending and making objects. We started out talking about PO’s (purchase orders) and what they need to take or allow. No specific order, just brainstorming and listing pieces. We then talked about chocolate chip cookies and what it takes to make those. We talked about timing, processes, and even checkpoints. We then talked options and how adilas allows for mixing and blending and tons of options. Great comparison between the two things. We then took it a little farther and started talking about options, choices, and flow for invoices and shopping carts. Tons of cool cross over ideas. The whole session or class was a whiteboard discussion of sorts. Good stuff. At the end we talked about allowing users and companies the option of organizing processes and space to be more efficient. This could be more in-line custom code, new settings, sub classifications, or custom processes and /or virtual checkpoints. We talked business mapping and using an application flex grid. Great session and good participation. • Recording notes on what happened today. Exciting stuff! • Emails. |
|
|
AU 1916 |
|
Daily Ideas | 12/12/2013 | -Super cool scripture this morning in the Old Testament. Ezra 10:4 – This is only part of the verse but it says, “We also will be with thee: be of good courage, and do it.” Very positive and great support, just what I needed. | |
|
AU 1899 |
|
Daily Tasks | 12/13/2013 |
• New logo for a company and emails. • Took a credit card payment over the phone for a client. Reset their login info and stuff. • Emails, phone calls, and tech support. • On the phone with Newtek checking on new servers. Trying to get organized and do some planning. As a note we will be changing some of the structure as follows: o Universe – Adilas Admin – (See 12/20/13 for new name changes) o Servers – Data or App servers o Worlds – Corporations with in a cluster or database • Light research on updates for ColdFusion. Checking out versions online. • Checking in on new servers and poking around a bit. They are brand new and totally blank servers. • Writing a special email with instructions for getting the new servers online and up and running. • An intern came over and we worked on more brainstorming on the new server clusters. We called Newtek and asked them about options for load balancing. There are some good options but I keep coming back to smaller independent models. It means more work but I can see some great advantages in going in that direction. We also talked about using cloud options but we decided to side table that for now. • Went out to my brother’s house to get some new video files. He has been working really hard and gave me tons of new files. I got 38 new video clips from June and July of 2013. I also got 4 new clips from an interview at Bridgerland. Good stuff. 30 miles. |
|
|
AU 1900 |
|
Daily Tasks | 12/14/2013 |
• Reviewing a video interview that my brother put together form the adilas interview back on 9/11/13. It was 4 different videos. Good stuff. I’d like to burn some copies and give it to people at Bridgerland. It promotes both BATC and adilas. That’s exciting! My brother did a great job! • Working on duplicating the adilas database. Lots of SQL. • Working on duplicating the adilas database. Going through each table and deleting as needed records from a copy of the database. Lots of detail work. • Added a note to the news and updates page that we have some new servers coming on board very soon. Small graphic of a couple rearranging some furniture. |
|
|
AU 3652 |
|
Tech - Database Tables & Special Needs | 12/14/2013 |
Database Tables That Have Special Needs: - Banks: o 1 = Dummy o 7 = No Bank Assigned o 50 = Void - Cart Favorite Categories: o 1 = General Category - Chart of Accounts: o 649 = Void o 834 = Not Assigned - Corporations: o 1 = Dummy - Financial Group Subs: o 35 = n/a (tied to the void chart of account) - Part Categories: o 2 = Internal Use - Payee: o 1821 = N/A System o 2036 = Stock Unit - Store Location: o 22 = Void - Units of Measurement: o 1 = each Messed Up Tables: - Makes - Models - Model to common features - Model to usage classes - Common features - Usage classes - Sub inventory types Questions on Tables: - App status history - Cluster app types - Custom docs to corps - Custom documents - Cluster corporations (or something like that) - Fed state allowances - Federal tax tables - General table - Help files - Cluster history flags - Master corporation list - Master stock list Cluster Specific Tables: - Photo upload history - Cluster payee - State tax tables - Testing - Web page - Zip codes What about id #’s … hard coded or soft and dynamic? It depends… |
|
|
Adi 829 |
|
Custom Code | 12/15/2013 | ||
|
AU 1901 |
|
Daily Tasks | 12/16/2013 |
• Emails and tech support. • Working on a smaller version of the adilas database. This will be given to the adilas interns and hopefully will also be a starting point for splitting and duplication of database clusters. Looking for special database values that are used as hard coded pieces such as void banks, void locations, system vendors, and other hardcoded sections. • Working with an intern on doing calculations for state tax withholdings. He is trying to wrap his head around where things come from and where they go. • New logo for a company. Go the graphic from my brother. • Helping an intern with state tax calculations. Light training on flow and database logic. • Small change to the code to calculate Arkansas state tax withholdings. Posted files online. • Working on code for the adilas database stuff. Created a full mini version of current code, a mini database, and all supporting files. Total file size is about 60 MB. |
|
|
AU 1902 |
|
Daily Tasks | 12/17/2013 |
• New logo for a company. • Added a new quantity label link from the shopping cart line items to the label generator. Posted files online. • Went in to Bridgerland to work with the interns. One intern and I worked on the adilas mini project and getting the mini database and files to run. Good stuff. I ended up getting pulled out of class to talk to some perspective clients who sell trucks and stock/units. 30 miles. • Went to my brother’s house to give him some videos that my other brother had made. We talked briefly about graphics and upcoming commercials. Good meeting. • Went to my other brother’s house to drop off the adilas jump drive so that he could put more videos on it. Talked briefly about hours and work. • On the phone with a contact doing a demo on using adilas and on using adilas and how we deal with stock/units. This contact and his brother were the guys I met at Bridgerland earlier today. They wanted to see some of what we do. Good demo and he will check with his brother and get back with me. |
|
|
AU 1917 |
|
Daily Ideas | 12/17/2013 |
-Make a check list for setting up a new server and/or database. That is okay to write things down. That way we don’t have to remember every little tweak. -I would really like to make some flow charts for pages, functions, and flow for the different pieces. I did this with an intern to talk about flow inside the payroll section. It was fun and helped him get his head around it much quicker. At some future point, it may be fun to animate flow or ever allow some user defined flow with the pieces. -On the server and database names…. Maybe just group everything together and call it “clusters”. Instead of saying domain, data servers, and databases… maybe just say clusters and then use the cluster name to talk about the sub pieces. Kind of general alias vs. super techy stuff. A possible naming convention might be dd-3-7 where dd = domain & database. 3 = the server # and 7 = the database number. Anyway, just an idea. (See 12/20/13 for new names.) -Use the data 1 server for existing clients that are good and solid. -Use the data 2 server for all new clients. -All of the “junk” or existing files and data will stay on the original server. Only good data and files will be moved to new servers. This doesn’t have to happen all at once. Move things as they become ready. -Setup small databases on the adilas server. Migrate that data as a group when ready. This is on a per corporation basis. Basically, we want to keep the new servers as clean as possible. -On making and naming data sources… We may use a general data source that deals on the admin level. We could use that to look-up the more corp or cluster specific databases or data sources. -On images… It may be nice to bury things a level deeper than just the corporation id number. An example might be: images/dd-3-7/corp 5 where the domain or data server are part of the naming convention. -On images… It may be good to stick the company logo inside the corporation image folder in the new structure. If we had to move anything it would all be together. -On the new code, remove all web service calls. Make the new servers even tighter and more dynamic. Basically, we’ll button up some things on the old system and then focus on the new system and new code to head where we want to go. -We may end up doing a sample API using JSON objects to help with emailing the invoices and quotes. In a nut shell, we are going to be headed more and more toward exchanging code and objects using webservices. -As a reminder… “Easy on the how, not so easy on the what.” Quote from a lady in the Box Elder School District. |
|
|
AU 1903 |
|
Daily Tasks | 12/18/2013 |
• Recording notes form loose papers. On the phone doing some tech support stuff. • Sending an email request to help get the new servers setup with domain names, SSL certificates, and MySQL database installed. • On the phone with Steve. We talked about the new servers and how we are planning to serve things during the migration process. We talked quite a bit about vision and how to keep things going and flowering. We talked about API and webservice options. We also talked about load balancing and individual adilas worlds for each client. Great conversations. • Working with an intern to get him new files and a local instance of adilas working on his computer. Good stuff. • Working with an intern on duplication of databases. We looked over some code files, talked about goals, and create a plan for what we want. Good progress. There are still some variables that are not completely ironed out. That is on the plan for tomorrow. • Working on the eCommerce section for showing quotes and orders for a single customer. This is the view history section for the quotes in the eCommerce section. • Writing an email about custom settings for a user and her wanting to hide/show certain links and values inside of adilas. We keep getting more and more requests like that. Interesting. • On the phone with Steve going over new and upcoming pieces and potential. Lots of future potential in the coming months. Very exciting stuff. • Working on a verbage change for PO’s. Changed the external invoice number field to an external reference field. This little change ended up hitting 20 different pages for PO’s. It is crazy how many pages are needed to get the job done. Posted tons of new pages online. New web and eCommerce settings for wholesale pricing, default customer type, skip shipping, email invoice settings, etc. Light testing. |
|
|
AU 1918 |
|
Daily Ideas | 12/18/2013 | -Quote from Steve – “Inspect what you expect.” | |
|
AU 1904 |
|
Daily Tasks | 12/19/2013 |
• On a conference call with some folks from Texas. They had some questions about bank balances, balance sheets, etc. Small training session on those pieces. We also changed some colors and showed them some new tools. Good session. • An intern came over and we had a planning and brainstorming session on how we are going to setup adilas and all of the server and cluster structures. Lots of drawing and sketching of ideas. We also started listing out goals, needs, and known issues. We decided that we would use corp key id’s, allow unique aliases if needed, and make the corporation id’s all come from the master control center. We also determined that users would be help in a master list as well. We would have records on the admin master level, the cluster level, and the world level. Users may also have a local or inter world id and an id that is global or outer world id. Each world will mostly use the inter world id numbers. The more global or outer world id number will only be used to determine cross world or cross cluster relationships. Also, I gave the intern a copy of some of the adilas code for his home machine. I think that will help him get his head around things better for future projects. Safety and security through sharing. • Went in to Bridgerland for the last class session of the year. We had 3 interns there and my sister. My sister taught us for an hour on expense/receipts and how seeing the bigger picture helps us understand the system thinking. As you get the bigger picture, you start looking at cause and effect relationships. As you start seeing cause and effect relationships, you start formulating goals and desired outcomes. Once you have a goal or have an anticipation of what an action does, you have more focus and are able to get to the task at hand. In a way having the goal and knowing how to get the outcome helps you move around the system better. Another interesting concept was dealing with a super flexible interface and then slowly becoming more rigid or linear. Think of driving to school... You could come from any direction until you get to the school. Once you get there, you most likely have to use an existing door to get in. Then once inside, you may have more halls, corners, levels, etc. Once you get to the classroom, you may be limited to one or two doors to actually enter the room. Interesting analogy. This relates to tons of things in life. My sister also used the white board and adilas map as visuals to help with her lesson. Good stuff. We then went into the system and played around with specific goals and cause and effects in mind. After that, all of us boys did a session in ColdFusion on the photo gallery for elements of time. This project is ¾ of the way done but has been sitting on the sidelines since 10/10/13. At the end of class we had each person come up to the whiteboard and map out the flow and pages for elements of time. I would say a page and how it was connected and the guys would draw the pages and flow on the board. I thought it was really fun and good way to visually figure out what was there or part of the tool set. 30 miles. • Emails, giving my dad some files and recording notes in my notebook. It’s been a good day. |
|
|
AU 1905 |
|
Daily Tasks | 12/20/2013 |
• Adding new output options to the advanced invoice line items report. These are values that are stored on the parts table but may be needed as pass through values. Part reference number, part weight, barcode number, and the RFID tag number. Posted files online and sent a couple emails out. Also did some research on graphical user interfaces. See notes on next page (below). • An intern came over and we had a fully day of brainstorming on the master controller application for the adilas universe level. We hashed out database tables on paper. Talked about flow, structure, and organization. Great session. WE came up with world terms for all the of the adilas structures. They are: 1. Universe 2. Galaxies – one or more domains connected to a content server 3. Clusters – domains or data servers 4. Solar systems – databases 5. Worlds – corporations (most people will only be dealing with worlds and corporations) • Helping another intern migrate the media/content project from scratch pages to real adilas files. More work with the other inter on planning and brainstorming. We also talked quite a bit about source control and putting adilas files out on a code source control server. We also talked a lot about using web services to push things back and forth. • Emails and light tech support. • Recording notes from today’s sessions. |
|
|
AU 1919 |
|
Daily Ideas | 12/20/2013 |
-When creating diagrams and flow… Maybe list the pages and organize them but don’t put any flow lines unless there is a built-in or automatic flow. This will allow us to do scenarios vs. a more rigid or mandatory process. Use actual mini page graphics. -Processes may start out pretty flexible but then may become more specific as things progress. See the driving to school analogy in the notes on 12/19/13. Idea came from my sister. -Graphical Interface Ideas…. (See scan in photo gallery) o Sub Homepage: map layout, sub homepage, world building concepts – group – use GPS and map layout graphics to help show world building concepts o Reports and options – search reports and special options o Individual Data Level – Individuals, Data, Run all levels over time – (use page icons to help with graphics and icons and buttons) |
|
|
AU 3653 |
|
Brainstorming: New Server Structure | 12/20/2013 |
Brainstorming with an intern on new server structures: - New databases get corp id – they don’t generate them they get assigned - Master controller – Mother ship o Cluster Controller – Master Corp id’s • World Controller – Master User id’s - Corp key id – set a default to 3 alpha-numeric. But let them change it. Alias must be unique - On vendors & payees – we need to allow vendors & payees at will. However the payee id. - Inter world id #s & outer world id #s – just for users Master Controller – Universe Level Master Corporations: - Corp id - Corp name - Corp key id - Corp key id alias - Cluster id - Corp status - Corp admin - Corp address 1, 2 - City - State - Zip - Phone - Web address - Corp email Master corporation history: - Corp history id - Corp history date - Corp history change Cluster Controller: Domain on server level - Cluster corporation - Same as master table - Minus to increments on corp id - Minus cluster id - Plus data source id Master User: - User id - User first name - User last name - Corp id - Status Master User Corp: - Id - Corp id - User id - Status User request: - User id - Corp key id - Status Cluster datasource: - Id - Datasource name - Notes - Start date - End date - Status Cluster user: - Same as master user - User login id Master Clusters: - Cluster id - Cluster name - Cluster alias - Domain - Cluster notes - Cluster start date - End data - Status - Cluster version User History: Master User Corp History: Cluster User Corp: Table to hold login records. World Controller – database level – if more than one world per database it becomes a virtual solar system. Corporation: - Corp key id - New column - Alias disable auto increment on corp id Payee: - User id World Controller Continued… - Where can people switch worlds (modify) (as well as login page) - Change datasource id - Change payee id - Record who accesses which corps - Super user login o Web services o User info o Reporting service Master Controller: (cont) Webservices: - New corp - Update corp - New user - Update user - Password change - Request access to world - Accept/deny request - User request applications - Help file access - Retrieve update - Record update Application: - Modify structure – see records - Run reports Clusters Controller: (cont) - Reporting web services System to move or extract someone to a new location Brandon & intern – Brainstorming on table design for universe and cluster level tables and database stuff. (See scans in photo gallery) |
|
|
AU 1906 |
|
Daily Tasks | 12/21/2013 |
• Playing with some ideas for a graphical layout. The idea involves page icons, names, and world building concepts. Also did some research on the structure of the universe and how clusters play in to that model. • Working with an intern on migrating code on the media/content project. We are taking his old files and bringing them into adilas as live files. Also working with another intern on new database tables, layout structure, and use cases. Good stuff. He made a small Microsoft Excel file with all of the new table names. • Tech support and emails. Sent an update email to a client about changes to new servers. Added a Christmas card to the news and updates page on adilas. It was a picture of Mary, Joseph, and baby Jesus. I also put up a general update about new changes and moving to a cluster based server model. |
|
|
AU 1920 |
|
Daily Ideas | 12/21/2013 |
-Count your blessing and you will be surprised what the Lord has done. This is a great little line from a song. -Add a next and previous link to PO’s, invoices, deposits, expense/receipts, elements of time, recipes, and balance sheet items. We also need next and previous links for stock/units and quotes. |
|
|
AU 1907 |
|
Daily Tasks | 12/23/2013 |
• Recording house, emails, phone calls, and organizing my workspace. • Helping an intern with some migration questions. Emails and light brainstorming on the application level flex grid. This will end up tying business to business and world to world. It will be the big brother to the current system players flex grid section. Good stuff. • Ordering SSL’s (secure socket layers) for new adilas domains and servers. • Working on help files for the new stock number corp-wide settings. Helping an intern on his project and light tech support. • On the phone with Steve going over things. He had some code and css questions. CSS = cascading style sheets. • Build a small css drop-down menu template for Steve. |
|
|
AU 1921 |
|
Daily Ideas | 12/23/2013 |
-Sometimes the imperfections actually allow for the game to be played. For example: the game of football. The perfect play on offense would result in a touchdown on every play or every drive. A perfect play defensively is zero yardage or a loss of yardage. In order to play the game, you actually need the imperfections on one side or the other. Kind of interesting. Another example is rock climbing. You have to have the imperfections, otherwise you wouldn’t have any holds. The same is true in life. If you don’t have any imperfections, how will you play the game of life? They play a vital role and are somewhat required. Game on! -We’ve had a request to make the stock/unit “VIN or serial number” be dynamic. This will end up being a new corp-wide setting. -We got some more requests for customer loyalty cards, gift cards, and rewards cards. Future development project. |
|
|
AU 1908 |
|
Daily Tasks | 12/24/2013 |
• Recording some notes about choice and accountability. See the notes on the previous page (below). • Prep for a customer upload. Reviewing files and making some notes. • Working on a blank landing page for new adilas domain names. • On the phone with an adilas consultant going over options for customer uploads. We also talked about packaging and how that would work. Packaging, meaning taking new product and putting it together in packages. • Sent an email to Steve and the consultant about doing packaging inside of adilas. I sent them a scan of this notebook from 6/7/13 with some recorded ideas on making packages. Kind of fun to use the notebooks. • New logo for Steve and a company that we need to submit data to. • Working on help files for corp-wide settings and admin corp-wide settings. |
|
|
AU 1922 |
|
Daily Ideas | 12/24/2013 |
-I’m thinking that seeking protection through sharing is very important. This includes sharing the power and control of the application. If something is shared, it becomes less of a controlling piece. -Along with sharing… I’m thinking that the new universe level controls are very important. I’m also thinking that they need to be part of the main application to keep the package complete. We could always permission those pieces and hid them, but if they are built in to the application we could potentially have more options if we have to change the configuration in any way. Think permissions and settings vs. separate systems. Maybe include the code and pieces in the main application and just keep them hidden or inactive unless needed. -As a side note, I wonder if God does the same thing with us… He builds in all the pieces and then only activates them as needed. Just a side thought. -The more we can go permissions and settings, they better. It makes things more reusable and versatile. -What if we used the database more to hold settings and page flow. Instead of hard coding everything (names, links, flow, validation), what if we actively used the database more to control all of the different pieces. Be open and allow for custom settings. Encourage individual adaptation and then follow up with cause and effect relationships. Help people choose their consequences by making correct choices. -This might get tricky, but I’d love to mix freedom, agency, and choices to … be easy on the “how” and be not so easy on the “what”. Basically, allow for diversity and embrace it, but still help people get their job done. |
|
|
AU 1909 |
|
Daily Tasks | 12/26/2013 |
• Reviewing notes, backing up files, and reviewing progress on some of the projects. • Setting up FTP settings on remote servers. • Called Newtek about FTP options on servers. Needed some work done on the server firewalls. • On the phone with Steve going over new and upcoming projects. We talked a lot about packages, batches, and tracking things full circle. We ended up with a mix of ideas that deal with elements of time, parts, PO’s, invoices, customer, and flex grid tie-ins. We will be working on a solution that will put both flex grid and element of time working together in tandem. That will be cool! We also talked about barcodes and RFID tags being part of the batch and virtual tracking process. • Showing an intern a rough walk through on migrating customers from spreadsheets to the adilas databases. Gave him some sample data with some instructions. Prepped some other files from the intern. |
|
|
AU 1923 |
|
Daily Ideas | 12/26/2013 |
-On file folders for corporations… I need to include a hash of some sort of the documents, media, content, photos, and files. It would also be very nice to move certain pieces to storage areas outside of the web or domain root area. Make the system look-up small pieces of the puzzle instead of putting everything in a front facing page. -For media and content files… maybe think of a double hash with a check back to the calling site to verify the user. The double hash might be part user id and part corporation id. That would definitely increase the security. -Idea from Steve… We may need two more fields per invoice and PO line items. They are: RFID tag and barcode number. This may help us track batches, lots, and packages. We may be able to combine these fields if needed. Then again, we may want both of these values to help with reverse type look-ups. -If we can mix and blend to help people do batches, packaging, and maybe even RFID tagging, we could really sell those tools over and over again. This could even help with mini or light manufacturing processes. |
|
|
AU 1910 |
|
Daily Tasks | 12/27/2013 |
• Emails. Setup FTP options for new servers. Also pointed domain names to new servers. • Recording notes in notebooks. • Recording expense/receipts for new servers, SSL’s, domain names and web hosting fees. |
|
|
AU 1911 |
|
Daily Tasks | 12/28/2013 |
• Checking out new domain names and prepping for SSL certificates. Recording bills and expenses. Lots of expenses and tying to balance sheet items. • Prepping customer upload files for an intern. Made a new spreadsheet to help with flow, mapping, and customer types. Sent 5 new upload files off to the intern. • Working on the elements of time photo gallery. Going over pages and checking off code. |
|
|
AU 1924 |
|
Daily Ideas | 12/28/2013 |
-As we map out the system… just show the pieces in general – don’t be too specific. Think just in time connections and draw or make relationships as needed. (See scan in photo gallery) Basic graphics, functions, and pages. Connect lives as needed to show flow or processes. -Change the verbage on expense/receipts to show an external reference number instead of an external invoice number. |
|
|
AU 1912 |
|
Daily Tasks | 12/30/2013 |
• On the phone with Steve going over creating packages and batches. We went rounds and rounds and got some good ideas. Our temporary ideas deal with recording batch numbers on the PO’s in the external reference number field. We could also store that same number on the RFID tag field for the parts or items. The last piece of the puzzle deals with putting the correct RFID tag number on each invoice line item as it goes out through the shopping cart. We also talked about ways to help the people cascade and/or update other pieces in the system. • Working with my brother on some ideas for an adilas commercial and overview tour of the system. Showed him some of the new graphics. • On the phone with a client. We were going over balance sheet items and how book the different pieces. We did some loans, some payments on account, and paying for PO’s. Good training session. • I had the interns and my brother come over to my house. I was helping all three with different projects. One intern was working on data imports for customers and vendors. The other intern was working on the media/content files and pages. My brother and I were laying down scratch tracks (recording audio) for adilas commercials and overview tutorials and training material. It was kind of fun bouncing between all of the different pieces and projects. Crazy times. • Phone calls and tech support. • Helping an intern with paths to view and upload files using the media/content application. • Recording notes in my notebook. • Calling and sorting out issues with SSL certificates for new data servers. • Working on custom data Imports for multiple different customers and corporations. • Migrating vendors and customer for 10 different corporations. Sent an update email to a consultant in CO. |
|
|
AU 3654 |
|
Brainstorming - Packaging | 12/30/2013 |
New packages & batches – “run & roll” … “light tracking” Tag 12 from - 5 of A - 7 of B - 12 of C PO main external ref # Part main – RFID tag # Invoice – many – pull from RFID # if possible Package Homepage: - On PO’s, if neg pull RFID - 3 left – how does - 10 new Line Items: - Add RFID field per line item Incoming Items with special #’s: - Bring it in Selling it out: - Cascade and/or update items? - On batches… help them re-batch and update the actual parts Side Notes: - Bulk problems - Individual problems - Mixed problems - Go to the part – change it - Need to cascade on PO’s as well |
|
|
AU 1913 |
|
Daily Tasks | 12/31/2013 |
• I had a couple really long tech support calls for a client and dealing with balance sheet questions. Basically, a conference call with upper management and going over things step by step. Lots of back and forth conversations. Also, two interns were over here at my house. We got one intern hooked up with some live code on his machine. He is starting to work on payroll stuff. Another intern is working on a page to help do look-ups for developers. These are things like customer types, part categories, and vendors per corporation. • Working on the elements of time photo gallery. • On the phone with Steve talking about projects and funding. We also lightly talked about tweaks to the balance sheet and graphical user interfaces (GUI’s). There should be some good stuff coming this next year. • Finished up the code to help with photo gallery for elements of time. |
|
|
AU 1925 |
|
Daily Ideas | 12/31/2013 | -2013 was a great year! I am very blessed! Thank you Lord! Let’s do it again! | |
|
AU 3634 |
|
Brainstorming: On the Adilas Team & Adilas Application | 12/31/2013 |
Scan: Notes from a meeting – Thoughts on an adilas team - Don’t lose the entrepreneurial spirit. That’s a gem! Dream it up and go get it! - Sometimes we may be missing a huge key piece of the puzzle. o Maybe a huge piece we are missing is the custom code work and consulting sections. We are allowing tons of outside reps & consultants make tons of money on our product. We may need our own little team that could capitalize on those pieces. o What are our inputs & outputs? o Where are our needs? o How can we solve those needs? o We need to help pick up what people want. - Keep building toward the dream. Spend time on where it needs to go. - Keep doing good and keep serving. Sometimes service pays more than hard money. Story about a guy buying a pack of cigarettes from a lady who was trying to quit. That little act of service was still in force 40+ years later. Great story. - Going back to the pieces we are missing. There are tons of jobs and projects. Let’s internalize them and allow other people’s money to help fund those projects. Why couldn’t adilas have a team that does sales, consulting, and custom implementation. That may be the next phase of growth. - On a different note, we really need to help map out the system. A virtual adilas “you are here” or a flow chart of what goes on. An adilas GPS system or sorts. Scan: Edits & Notes to the Results = Mix(Functions, Players, Concepts) Flyer (Please see scan in photo gallery) Get results by applying business functions, application players, and core concepts. Here is a quick look at what we bring to the table to help you run your business. Results = Mix(Functions, Players, Concepts) It would be so cool to make a flyer for each one of these things. Not just a flyer per section but a flyer per line 1-12 on all 4 sections. Results: (Turn this into questions & statements. Who, what, when, how, where, why?) What are you looking for? What is the goal or outcome? 1. Get Something for Your Pain 2. Make More Money 3. Custom Interface & Graphical Look/Feel 4. Flow & Processes (Logical, Smooth) 5. Tracking Numbers & Data Values 6. Tie-in Paperwork & Documentation 7. Archive & Storage of data 8. Search-ability – All Data Is Live And Searchable 9. Ease of Use 10. Custom Business Solutions 11. Other Goals & Output 12. You Name It… Dream it up, we’ll wire it up! Dynamic & Adaptable – Your e-Business buffet! Application Players: What tools are you going to use? 1. Customers 2. Invoices 3. Quotes 4. Vendors 5. PO’s (Purchase Orders) 6. Parts (General Inventory Items) 7. Stock/Units (Serialized Inventory) 8. Deposits 9. Expense/Receipts 10. Employee/Users 11. User-Maintained Balance Sheet Items 12. Elements of Time (Calendar & Scheduling) Business Functions: What do you want? How will you reach your goals? 1. Sales, Inventory Tracking, & POS (Point of Sale) 2. CRM (Customer Relationship Management) 3. CMS (Content Management System) 4. Online Expense Tracking 5. Payroll & Timecards 6. Calendar & Scheduling 7. Create Data Relationships Between System Players 8. Backend Office & Accounting Functions 9. Histories & Reports 10. BI (Business Intelligence) 11. Web Presence & eCommerce 12. Virtual Data Portal (Big Data) Core Concepts: Why & how does it work? Virtual world building… 1. Capture & Record the Story 2. Groups, Characters, Players, & Individuals 3. Relationships 4. Trouble, Problems, Needs, & Goals 5. Decisions & Choices 6. Consequences (Cause & Effects) 7. Accountability 8. Permissions & Settings 9. Systems Thinking 10. Vision & Future Developments 11. Tech, Tools, & Maintenance 12. Objects & Data Over Time Each corporation inside of adilas is its own little fenced in area or world… where only assigned users for that corporation may play and/or participate. Corp-wide settings allow for variations and custom usage of the adilas platform. Scan: Adilas Results Flyer Updated Adilas Results Flyer (Please see scan in photo gallery) Free Weekly Demos Scan: Sketch – One to Many Relationships, Mixing & Blending Sketch – One to Many Relationships, Mixing & Blending (Please see scan in photo gallery) Scan: Adilas.biz eBusiness Seminar Brainstorming Adilas.biz eBusiness Seminar Brainstorming Adilas.biz eBusiness Seminar flyer: - Business functions - More white space - Less wordy - More marketing • Sales, Inventory Tracking, & Point of Sale • CRM (Customer Relationship Management) • Payroll, Timecards, & Online Expense Tracking • Calendar & Scheduling • Backend Office & Accounting Functions |
|
|
AU 3635 |
|
Brainstorming: Content Server Structure & Planning | 12/31/2013 |
Scan: Adilas Content Server Planning Adilas Content Server Planning Adilas – Content Server (Pig Server) 3 hr front end – planning & flow & research: Behind the Scenes: - Connect invoice to membership dates - Elements of time to a front facing calendar - Media to elements of time User payment invoice – user accessing content at appropriate time – file time – mold List: - Default corp type - Adjusted date time - App type id - Cat 1 - Cat 2 - Cat 3 - Admin flag - Date - Desc - Duration - File size - File type - Name - Path - Rating level - Reference - Sort - Corp-id - Main id - Payee id Scan: Adilas Content Server Planning Adilas – Pig (content server) (Please see sketches on scan in photo gallery) - CMS media id - MCS media status - Corp folder with hash - Final name Scan: Adilas Content Server Planning (Please see sketches in photo gallery) Reference: - 2 = local - 3 = remote - 4 = physical – reg - 5 = physical – ultra - 4,5 = all physical Tick list: https: on remote - Temp - Thumb - Small - Large Web Facing File Structure: - Client file = what they named it - File size - What the server names it making it unique |
|
|
AU 3636 |
|
Tech & Teaching: Payroll Relationships & Flow | 12/31/2013 |
Scan: Notes – To-Do - Hard code state initials into Fed State Allowance table - Changed allowed amount in Fed State Allowances – CO 2013, 2014 - When done – we need to get the developer’s fed state allowances & his state tax tables Scan: Payroll Sketch of flow & relationships: Payroll (Please see sketches & flow on scan in photo gallery) Users – department – connects (many) – action Payroll – calculate (giant add form) – action (hits the db) – view or edit – action (hits the db) Has not hit but needed State supplied: Your wage limit is ____, your % is ____ State: employee txs/employer cont Scan: Payroll Working with a developer on payroll & how things work Payroll home (start) – check joiner table & calc – record personal payroll - Department home - Add/edit payee to department - Payroll home - Calculate payroll - Record personal payroll Sketches, examples, & flow – please see scan in photo gallery Scan: Payroll Research Payroll Research: Formula for Computing Tax to be Withheld: LEGEND: - G = Gross pay for pay period - P = Number of pay periods per year - A = Annualized gross pay (G x P) - E1 = Personal and Dependent Exemptions - E2 = Age 65 and Over & Blind Exemptions - T = Annualized taxable income - W = Annualized tax to be withheld - W/H = Tax to be withheld for pay period Formula (Effective January 1, 2008) 1. (G)P – [$3,000 + (E1 x $930) + (E2 x 8000] = T 2. If: a. T is: Not over $3,000 b. W is: 2 % of T c. T is: Over $3,000 But not Over $5,000 d. Then: $60 + (3% of excess over $3,000) e. T is: Over $5,000 But not Over $17,000 f. Then: $120 + (5% of excess over $5,000) g. If Over $17,000 h. Then: $720 + (5.75% of excess over $17,000 3. W + P = W/H Example: John claims exemptions for himself, his wife, and their three children for withholding tax purposes. He is paid on a semimonthly basis, and his gross wages for this pay period were $725. 1. T = (G)P – [3,000 + (930)E1] So T = (725)24 – [3,000 + (930)5] 17,400 – 7.650 = 9,750(T) 2. T is over $5,000, but not over $17,000 So W = $120 + 5% of $4,750 $120 + $237.50 = $357.50 3. W/H = W / P So $357.50 / 24 = $14.90 The tax to be withheld for the current period is $14.90 Pay Period Conversion Table (P) - Annual = 1 - Semiannual = 2 - Quarterly = 4 - Monthly = 12 - Semimonthly = 24 - Bi weekly = 26 - Weekly = 52 - Daily = 300 |
|
|
AU 3637 |
|
Notes: Packaging | 12/31/2013 |
Scan: Known Issues With Packaging Known Issues With Packaging 1. Bulk vs. Individual 2. When do things switch? a. Mixing of pieces – new vs. old – how can you tell 3. Start the beginning – where does it go? What happens as it changes. 4. Coming in, going out 5. Mixing & re-batching & re-packaging Control – number Lots, packages, groups, batches, orders, RFID tags, liters, control # Settings: 1. Do you need the extra tracking? Yes/no – what to call it? |
|
|
AU 3638 |
|
Note: Adilas API Layout & Flow | 12/31/2013 |
Scan: Adilas API Adilas API (application programming interface) (Please see sketches on scans in photo gallery) Web server – HTML – CF – API – CFC – DB Classic adilas – web – CF – CFC – API – JSON – DB |
|
|
AU 3639 |
|
Tech - Database Tables | 12/31/2013 |
Scan: Database Tables Database Tables (One to Many Relationships – Please see sketch in photo gallery) - Vendors/Payees - Purchase Orders (main) - Po Invoice Line Items (many) - Parts or Items (many) - Invoices (main) - Customer - Flex Grid Main: - PO #5 – PO Main - Vend #10 – PO main tied to vendors Lines: - Part 20 – Vend 10 – 5 – $1 - Part 21 – Vend 10 – 5 – $2.50 - Part 22 – Vend 10 – 4 – $5 - Part 23 – Vend 10 – 7 – $10 - Part – Vend – Qty – Cost Scan: Corporations Table Corporations Table: - Use RFID tag numbers – tinyint(1) 0 - RFID tag number name – varchar (50) Null RFID tag “Control Number” - Corp vin name – varchar(50) Null “Serial Number” - PO/Invoice line items (loop over each corp) - RFID tag number – varchar(50) Null Methods – - Add Invoice Line Item - Add PO Line Item - Check parts - Update PO Line Item - Update Invoice Line Item |
|
|
AU 3640 |
|
Tech - Shopper Planning Layout | 12/31/2013 |
Scan: Shopper Planning & Layout: Cork key Id: Shopper Image Path: Company Name: Save Settings [button] - Shopper corp key id - Shopper image path - Shopper company name - Corp-id (real) - Web page setting id (1 or real) – DB |
|
|
AU 3641 |
|
Research: 3D Manufacturing & Robotics, SEO, Etc. | 12/31/2013 |
Scans: Robotics, 3D Manufacturing Research Robotics, 3D Manufacturing Research Robotics Manufacturing Training, Research, & Industrial Applications Information Package (Please see scan in photo gallery) Scan: Research: The Periodic Table of SEO Success Factors (Search Engine Optimization) The Periodic Table of SEO Success Factors (Search Engine Optimization) (Please see scan in photo gallery) Scan: Research: PICK Chart – (Possible, Implement, Challenge, Kill) Chart PICK Chart – (Possible, Implement, Challenge, Kill) Chart (Please see scan in photo gallery) |
|