Welcome to A PRESENT Program

                   

A BRANCH Coordinated Service (ABCS) Vision Discovery Project (VDP)


Introductions

A PRESENT for YHWH!

What is A PRESENT?

  1. A PRESENT is developed and built by all people on planet earth for our Heavenly Father YHWH and his Anointed (Messiah, Christ) Son, Yahoshua (JESUS) and his servants.
  2. A PRESENT is A District set aside as a PLACE for YHWH’s HABITAT and for leadership of the Kingdom YHWH set up. We named this Development Site A Kingdom District (AKD).
  3. A PRESENT is the land development site, the Land Of Israel Subarea (LOIS) for AKD; which has been pre-selected by our creator client YHWH; and that is an area nearly ten miles square around Jerusalem, Israel.
  4. A PRESENT is the 10-Dimention PROGRAM; spatial 3-D plan, database and applications, geographic information, projects’ portfolios and notebooks, resource management, plan and actual improvements,  for A Kingdom District (AKD) Land Design Development and other related PROJECTS within the boundaries of AKD.  Various particulars of these PROJECTS are ordered and outlined in the Holy Bible, especially within the writings of the Prophet Ezekiel, Chapters 1 & 40-48.

YHWH is AKD’S Designer and builder CLIENT AND SPONSOR. The word of YHWH (The Holy Bible) is the Design Team’s Introduction, Instruction, CODE, Specifications, Authority and Authorization to proceed with AKD. Completing this Program for AKD will provide and present, A WONDERFUL PRESENT TO YHWH.

A Kingdom District (AKD)

AKD is a product of heaven produced on earth. We pray and cast our vote of allegiance to OUR FATHER IN HEAVEN (YHWH) when we pray: “Thy Kingdom come thy will be done on earth. . .” Prayer is not enough. We need follow through. We need people and governments doing the will of YHWH here on planet earth. Once people on earth are willing to do what YHWH wills our prayer begins to be answered; and YHWH becomes our CLIENT KING. One of the definitions of a CLIENT is: person or organization to whom goods or services are provided. When we do the will of YHWH, we do and provide the things YHWH wants, the services YHWH desires and deserves.

AKD is a place YHWH wills to be on earth. It is a place built by loving people in the pattern given them by their CLIENT YHWH.

In heaven, YHWH has a throne (kesa = cover). That Throne covers a special place, called the Habitat or House of YHWH.  Ezekiel was given a vision of this KESA AND HABITAT as it is to be developed (descends) on earth.  The Land Design Development District (L3D) surrounding and supporting the HABITAT OF YHWH we named A Kingdom District (AKD).

Ezekiel describes this district and is given specific architectural instructions about its development. Then he says;

Eze 43:4-7  . . . the glory (KABODE) of the LORD YHWH filled the house (HABITAT). And I heard him speaking to me out of the house (HABITAT); and the man stood by me. And he said unto me, Son of man, the place (HOME) of my throne (COVER), and the place (HOME) of the soles of my feet (CARPET REGAL), where I will dwell in the midst of the children of Israel for ever . . .

 

The Prophet Ezekiel envisioned YHWH’S AKD approximately 2,500 years ago, and recorded for us our CLIENT’S VISION for AKD. The process of developing and overseeing all the various design aspects and projects of AKD we call Program Development.

The PROGRAM is intended to complete a set of projects related to a common goal executed over an extended period of time.

Therefore, in the following outline we develop a Work Breakdown Structure (WBS) for the set of projects controlling the Program DESIGN Development of various AKD PROJECTS.

AKD is an assembly of projects. We have named a northern project of AKD: ZADOK with A Very High Mountain (AVHM), which includes on its top, Ezekiel’s Temple Complex (ETC), and the COVERED HABITAT a.k.a. the Throne House; under AVHM are the OLD CITY OF JERUSALEM and the new 144,000 room King David’s Hotel II (KDH2). The southern part of AKD contains See-YAH or SMMH a new city with its adjacent CARL, which means FARM, or a fenced area for growing crops and providing protection for live stock. AKD is further divided into 100 SECTIONS. Each SECTION is 2,500 cubits square which is about a square mile. The Northern Forty SECTIONS are named ZADOK. The Central Forty SECTIONS are named LEVI. The Southern Twenty SECTIONS are for the CITY, See-YAH and the adjacent CARLS.

Eze 48:20  All the oblation (A PRESENT, A District) shall be five and twenty thousand (25,000) by five and twenty thousand (25,000): ye shall offer the holy oblation (A TERRITORIAL GIFT, A PRESENT), (A DISTRICT) foursquare, with the possession (which includes the property) of the city.

 

So, how do we get started on the development of AKD?

Getting AKD started.

Initiation Phase

The Initiation Phase is the first phase in a project's lifecycle with a focus on project definition and project feasibility. Accordingly, the Program divides tools for this phase into two subsections: creation of a Charter, and the events and tasks that precede the Charter.

Pre Charter
The pre charter tasks are steps an agency takes, either on a formal or an informal basis, to decide whether to launch a project, and what form that project should take. It begins with identifying and analyzing a business need or problem, considering the various alternatives for addressing that need (including doing nothing), analyzing the feasibility and impacts of implementing the chosen alternative, procuring funding, and evaluating the risks.

Best practices for these processes have already been described in the @ccesswashington core systems framework. To maintain consistent practices across the program and avoid duplication of program development efforts, this project management program includes these pre-charter best practices via links to the public sector core systems program, and incorporates applicable practices and tools to a newly surfacing “enterprise” opportunity.

The Charter
Once the decision has been made to proceed with the project, best practices dictate that a project charter should be created. The charter is a formal document that defines and describes the program at a high level. It covers governance, scope, approach, roles and responsibilities, as well as the goals, objectives, and deliverables of the program, among other things. The document functions as the formal agreement for the project and is signed by the appropriate parties as such. Signature of the charter document marks the end of the initiation phase, and the document is the tangible deliverable resulting from the efforts exerted up to this point. Changes to the charter after signoff will require invocation of the change management process. This process is described in more detail in Phase II - Planning .

The charter for the Washington State Master Licensing Service (MLS) project is included in the program as an example of a complete charter. The components in the MLS correspond to each of the sections described in the charter and are linked accordingly. In addition to the MLS, there are additional examples for each of the individual charter components.

Planning Phase

The next two phases in a project's lifecycle, planning and execution, are the most critical to project success, and are closely intertwined as well. The planning phase is when the detailed aspects of the project are determined, coordinated, and documented. The execution phase is when these plans are carried out. The temptation is to abbreviate or skip the planning phase altogether to get the project underway quickly. This approach, however, inevitably leads to inefficiencies in the execution phase, which prolong the overall process if not doom it completely. The quality and quantity of work completed during the planning phase is critical to the project's success, and will avoid the "Ready, Fire, Aim" syndrome common to many project failures.

Best practices for the planning phase include the creation of plans for managing all major aspects of the project, including communications, risk, resource acquisition, training and implementation, among others. People often confuse the work of the planning phase with the creation of a Work Breakdown Structure (WBS), leading to the neglect of the rest of the best practice plans. The planning phase sets expectations for staff and stakeholders, and must include their buy off. The plans facilitate as well as document these agreements.

While some projects combine plans for all aspects of project execution in a single Project Plan, the Program recommends the preparation of individual plans for each aspect. For all but the smaller projects, Project Plans have a tendency to become very large, making them daunting to compile in the planning phase and cumbersome to use during the execution phase. The Program has organized the planning phase best practices in a suggested order of their preparation, based upon the timing of the need for them in the execution phase. In reality, however, some or all of these plans are frequently developed concurrently. The only one that must be done ahead of all the others is the Change Management Plan.

Other than setting aside enough time and resources to plan properly, one further tip for project success is to pay attention to the interdependencies of the various plans, making sure that when a change is made to one plan, the impacts are carried through to the other plans as needed.

 

With this said, we at See-MaKe xmj BRANCH officially decided to proceed by faith with the Initiation Phase, believing that as planned A PRESENT will be delivered to YHWH.

 

Sincerely,

David Carl Lewis,

Overseer:

Google search
WWW DavidsBRANCH.com

  NEXT PAGE