Farm Produce Business:
Corporate Data Flow Diagram Design
A particular task of the Business Development Planning of the Venture Sartup Starting Phase is the developing of an integrated Business Processes of the etire company of the growth Vision of f the aggregator or founder entrepreneur, reflecting further expansion of the Farm-Produce Business into a formal corporation that invariably thrusts the business into the Venture Startup Stage and more specifically into the Starting Phase of that stage.
As observed already, the Starting Phase prepares, through the Business Development Department/Group, the venture for the implementation of the Founding Vision through the expansion of staff, and development into the Execution Phase. So the business entity now enters the Starting Phase and more structured operations is demanded for a growth vision. The expanded Business process development occurs guided by the Organizational Chart which captures the Founding Vision through the departmental units, the intra-department projected activities, and the staffs count of each department, and as a result a consistent set of business activities is defined and crafted for each department and for every staff of each department on which the job descriptions are ultimately documented.
Using these business activities, the integrated operations of each department is developed from implementing operating Business Process system for the routinization of said department, requires a well designed data network trunk by which the operations staffs share data. Yet, the specifics of accomplishing this integration of the departmental activities into Business Processes and then the integration of the business processes to integrate the entire company and then such as setting the operations as to allow the mere plug in of staffs as hired, entails a combining of the revamped enterprise design by the Organization Chart and the expanded Business processes can obtain with the use of Data Flow Diagrams. The resulting vision-descriptive Data Flow Diagram is then utilized to plan out the IT network data communication trunk in detailed capture of and manifesting of the Founding Vision.
Yet, while it seems rationale to develop the data flow diagrams at the department level and then integrate, that approach of developing corresponding vision-specific Data Flow Diagrams is actually more difficult to do than the approach that follows the reverse of working in reverse by starting from a corporate integrated data trunk and then implementing the drill-down details at section levels. However, because the actual flow path of the data is just as important, the design of the enabling IT Network as such is required to provide consistent support of the operations. So the design of the diagram also has to have in forethought the implementation with a network, and with the interconnecting cables as the data flow paths. Moreover, the business activities and the attendant data flow diagram must be employed in the development of the software specifications. The implementation of these features of the enabling IT network suggests necessity of indicating time-delays on the various nodes of the data points as such should help in the assessment of data storage and the type of storage as well as the type of data recovery from each of the storage node.
So generally, the data trunk is represented as the first step or the Global Diagram in the Data Flow Diagram which shows the flow of data between the departments that shows the integration of the company as a whole. The Global Data Flow Diagram must show not only the data flow within the company but also the interaction with the external of the company both in reflection of the extended enterprise, suppliers and customers
Following the development of the Global Data Flow Diagram, then the tasks of the drill-down layers of the of first the Processes and the activities each of the department being expanded out into yet smaller data flow diagrams are performed. Specifically, the groups within each of the department are integrated with a data flow diagram. At this level the data flow diagrams are actually developed with the business processes. Then, of course, the business processes fundamentally groups business activities into units this point of the development of the Data Flow Diagrams is the best basis to consider the data storage systems matters considered. The data storage forms the basis of the time delays hence the issues of time-delays are undertaken because the needs are more clearly defined at the business process than at the business activities level. Yet because data storage systems are usually not distributed through the venture but rather centralized even if with replications, required that the time-delays should be able to inform on the need or lack thereof of an abstraction of such time-delays into vertical nodes that would define data flow lines from the points of time-delays into the central data points or Data Centers.
The next level of the drill-down process in developing the Data Flow Diagram focuses on the Business Activities of each departmental group. This stage of the development is usually the easiest having been already developed prior as business activities. The development of the Business Activities, however, had been based on the contents of the job tasks of staffs, and a such the activities data flow mapping must consider yet again the activity-nodes with time-delays, assessed in terms of the Performance Times for the activities as due to be undertaken by the staffs. Yet because most staff activities are performed with software, mostly the software architectures on which performance times are estimated form the basis of quantifying the time-delays. The nodes of the time-delays however are also uniquely different in the sense that the data output may be more or less than the data input, depending on the format adopted for the input and output data in the representation of the role of the software deployed for the use of the staff.
The full integration of the venture demands that once completed the next management level is incorporated into the data flow diagram, so the flow of data from group operations to the manager and return are diagrammed. The inclusion of the Management Layers is critical in order to introduce the concept of signals and triggers as will become evident presently. Indeed the entire business operates with signals and triggers that amend and adjust the processes and activities. Next, the business activities which are usually developed for the group operations are then finally represented in data flow diagram. Because the Management Layers are hierarchical, the manner of implementation of diagram is of some consideration.
The representation however could be of one of two layouts. One layout format is hierarchical with the primary data flow diagram integrating the departments representing the highest mount with the rest of the development being depicted below the preceding data flow diagram. The other layout is simply flat, a pure 2D layout. In this case the data flow diagram of each subsequent design is literally fanned out with the primary data flow diagram being in the middle as the rest of them sort of mushrooms outwards around the primary diagram.
There is no preference for the layout, and the choice is idiosyncratic. Both layouts gives a hierarchical overall structure of the management level data flow diagrams. While the flat layout diagrams show the management on fanned base and as such much closer to the traditional military hierarchical reporting formalism, the hierarchical data flow diagram provides a structure of minarets around each level of data flow diagram.
The time-delays as reckoned for the management layers, however, must reflect the management mindset of approach of the venture as perceived in the vision. For realistic assessment of the time delays, it may even be helpful to actually represent the managing activities of each Manager taken into consideration the possibility of the adoption of more advanced software technologies tools for performing some of the tasks. The use of such software as based on management layer-specific algorithm is actually is within the realm of consideration with a map of the error and measurements data derivative of the data feed from the business processes level of data flow diagramming. The resulting contrasts of data are employed yet into generating reports data that flow into the next upper level of the management layer.
The use of corresponding the Data flow diagram to capture the data matters of the Farm Produce Business includes the time-delays as reflected by the role of the Green Subsistence Farming, and as such requires in-depth appreciation of the underlying supply chain characteristics of the Green Subsistence Farming the produce supply of and from which the applicable time-delay must be assessed. Therefore, keeping apprised on the presentation on Green Subsistence Farming as published on this same platform as this article would be quite instructive.