fang- Formerly a news group

== Formerly a newsgroup-- An internal job tracking program ==
(Feb 2001 - Dec 2003) Status: Complete

When I first joined Arafura Connect back in 01/12/2000, jobs were raised, assigned and tracked using a handful of private news groups on an internal (Micro$oft developed) NNTP server. After working at Arafura Connect for three months, I became so frustrated with the current system, I wrote one in C. The name FANG (Formerly A NewsGroup), was named after the fact that our system used to be run on a set of news groups. Below are some screenshots of this program:

This is the technician's main intray. This screen views jobs that have been raised. The different coloured lines indicate status of the job-- new job, updated job, waiting (for parts/quote), sundry job, perpetual job, closed job. Status's are used as semaphores by techs and the coordinator. For example, when a part becomes available for a job, the coordinator will change the status of a job from 'waiting on parts' to 'updated'. The tech will then see that it's a job they can work on. Perpetual jobs are periodic jobs that are self generated by fang.

Here you can filter what jobs you want to view in the intray. Most users only want to view their new, waiting, and updated jobs.

This screen views parts on back order against jobs. This screen is used not only to see what parts are waiting, but also to cross check fang job numbers with any supplier references (Nb/ a similar facility exists for string searches on parts).

These screens are an actual job. The first one is the job header.

The next one is a list of work performed... which gives times and descriptions of what a tech did on a job.

This is editing a work performed entry.

Here is a list of 'parts used' for the job.

Here is editing one such part entry.

This is the archive selection screen. Archiving allows you to manage multiple job groups, or simply organise jobs into different ages, job lots, etc.

This is a FangCust facility. fang queries a FangCust service (FangCust has been developed by Peter Green, which provides customer details and phone numbers. This is used to search for a customer, and then insert their details into a newly created job (which fang automatically does).

Back

	This is the technician's main intray. This screen views jobs that have been raised. The different coloured lines indicate status of the job-- new job, updated job, waiting (for parts/quote), sundry job, perpetual job, closed job. Status's are used as semaphores by techs and the coordinator. For example, when a part becomes available for a job, the coordinator will change the status of a job from 'waiting on parts' to 'updated'. The tech will then see that it's a job they can work on. Perpetual jobs are periodic jobs that are self generated by fang.
	Here you can filter what jobs you want to view in the intray. Most users only want to view their new, waiting, and updated jobs.
	This screen views parts on back order against jobs. This screen is used not only to see what parts are waiting, but also to cross check fang job numbers with any supplier references (Nb/ a similar facility exists for string searches on parts).
	These screens are an actual job. The first one is the job header.
	The next one is a list of work performed... which gives times and descriptions of what a tech did on a job.
	This is editing a work performed entry.
	Here is a list of 'parts used' for the job.
	Here is editing one such part entry.
	This is the archive selection screen. Archiving allows you to manage multiple job groups, or simply organise jobs into different ages, job lots, etc.
	This is a FangCust facility. fang queries a FangCust service (FangCust has been developed by Peter Green, which provides customer details and phone numbers. This is used to search for a customer, and then insert their details into a newly created job (which fang automatically does).