Abstract:
A Phasetime Method and Automated System for tracking Element Efforts that result in end products, at least including products of art, industry, and nature, and reporting Development Event Efforts by their virtual Points in Phasetime within designated Past, Present, and Future Project Development Phases. Dynamically generated Phasetime Reports display Element Project Efforts within a live Phasetime Matrix in relation to their Phase of Development and Points in Phasetime. Development Events occur within Project Development Phases, which Phases may vary in number and kind depending on the end product. Development Events include Project Production Elements, Element Efforts, the duration of said Efforts, and Efforts&#39; Points in Phasetime. Element Efforts, tracked by Phasetime Project Development Event Instances, are reported in edited Storyboard Beats in Phasetime Macro, Micro, and Nano Views depicting the Efforts&#39; effect on the end Product&#39;s Storyline. Effortology keys allow browsers to alter the Storyboard Storyline Report.

Description:
CROSS REFERENCE OF RELATED APPLICATION 
       [0001]    This Non-Provisional application claims the benefit of priority under 35 U.S.C. sctn. 119 to a Provisional Application No. 61/403,121 filed Sep. 11, 2010, the contents of which are incorporated herein in their entirety. 
     
    
     BACKGROUND OF THE PRESENT INVENTION 
       [0002]    1. Field of Invention 
         [0003]    The present invention is directed to a dynamic method for the collecting, tracking, storing, and reporting of Development Event Efforts as to their Points in Phasetime within a Phase of Development of a Product, regardless if those Efforts are energies expended by Elements comprising any one or more animal, vegetable or mineral substance or matter, and regardless of the nature of the Product. 
         [0004]    2. Description of Related Arts 
         [0000]    U.S. Pat. No. 7,034,78 Irmer; Frank, Archibald; Nicholas Ian 
         [0005]    The above referenced Patent which includes a reference to phasetime is in an unrelated field and whose method has no relevance to the method of the present invention. 
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT 
       [0006]    Referring to the drawings of the invention, a Point in Phasetime System and Method Thereof are illustrated. It is understood that the components could be designed, arranged and developed in a myriad of configurations not displayed. It is also understood that the following detailed description of the present invention as referenced in the drawings are not intended to limit the scope of the present invention as claimed, but is only for illustration of the preferred embodiment of the present invention. 
         [0007]    The present preferred embodiment of the invention will best be understood by reference to the drawings, wherein like parts are designated by like numerals throughout. 
       LIST OF REFERENCE NUMERALS 
       [0000]    
       
           100 . Elements 
           102 . People (PP) 
           104 . Places (PL) 
           106 . Projects (PR) 
           108 . Objects (OB) 
           110 . Projects  2  (PR 2 ) 
           112 . Point In Phasetime (PiPT) 
           114 . Effort 
           116 . Effort Instances 
           118 . Role 
           120 . Services 
           122 . Contribution 
           124 . Utilization 
           126 . Effort Instance and Phasetime Data Virtual Matrix 
           128 . Associative Value 
           130 . People to Places Association 
           132 . People to Objects Association 
           134 . Places to Objects Association 
           136 . Data Collection 
           138 . Data Reporting 
           140 . Effort Instance and Phasetime Data Collection Interfaces 
           142 . Data Collection Forms 
           144 . Data Validation and Verification Interfaces and Processes 
           146 . Data Reporting Interfaces and Processes 
           148 . Showlinks Core Database 
           150 . Showlinks Data Repository Database 
           152 . Past Project Efforts 
           154 . Present Project Efforts 
           156 . Future Project Efforts 
           158 . Data Search Queries 
           160 . Data Search Query Interface 
           162 . People Effort Instance Report 
           164 . Places Effort Instance Report 
           166 . Projects Effort Instance Report 
           168 . Objects Effort Instance Report 
           170 . CICPE Display 
           172 . Phasetime Matrix Report 
           174 . Section  1 : Header 
           176 . Section  2 : Phasetime Matrix 
           178 . Arrow of Phasetime X Axis 
           179 . Section  3 : Effort Instance PiPT Window 
           180 . Phasetime Report Modules 
           182 . Phasetime Report Header Module 
           184 . Phasetime Matrix Generator Modules 
           186 . Phasetime X Axis Generator Module 
           188 . Phasetime Effort Instance Modules 
           192 . Past/Present/Future Indicator 
           194 . Effort Instance Owner 
           196 . Storyboard Beats In Phasetime 
           200 . Efforts In Phasetime 
           202 . Macro Phasetime 
           204 . Micro Phasetime 
           206 . Nano Phasetime 
           208 . Phases of Development 
           210 . Concept Development [BLUEPRINT] 
           212 . Pre-Production 
           214 . Production 
           216 . Post-Production 
           218 . Manufacturing, Distribution, and Promotion 
           220 . Post Manufacturing, Distribution, and Promotion 
           222 . Phase Boxes 
           224 . Effort Phase Box 
           226 . Phasetime Clockworks 
           228 . Phasetime Clockwork  1   
           230 . Phasetime Clockwork  2   
           232 . Phasetime Clockwork  3   
           234 . Phasetime Clockwork  4   
           236 . Phasetime Clockwork  5   
           238 . Phasetime Clockwork  6   
           240 . Storyboard Header Section 
           242 . Storyboard Body Section 
           244 . Storyboard Footer Section 
           246 . Macro, Micro, Nano Multimedia Content 
           248 . Search Links 
           250 . Effortology Key 
           252 . Macro, Micro, Nano Storyboard Modules 
           254 . Storyboard Header Section Generator Module 
           256 . Storyboard Multimedia Body Generator Module 
           258 . Storyboard Footer Section Generator Module 
           260 . Showlinks Macro, Micro, Nano Multimedia Database 
           262 . Multimedia Exhibits 
           268 . Editing and Formatting Processes 
           270 . Phasetime Matrix Report Generating Module 
           272 . PiPT Effort Instance Indicator 
           274 . Arrow of Phasetime Clockwork Icons 
           300 . Project Phasetime 
           301 . Product Runtime 
           302 . Publication Date 
           303 . Phasetime Parturient Event 
           304 . Published Product 
           306 . Products Storyline Data 
           307 . Storyline Architect 
           308 . Macro, Micro, Nano Editing Process 
           309 . Effortologist 
           310 . Phasetime Macro Storyline View Generating Modules 
           312 . Phasetime Macro Storyline View 
           314 . Phasetime Micro Storyline View Generating Modules 
           316 . Phasetime Micro Storyline View 
           318 . Phasetime Nano Storyline View Generating Modules 
           320 . Phasetime Nano Storyline View 
           322 . Developmental Cycle 
           324 . Phasetime Macro 
           326 . Phasetime Micro 
           328 . Phasetime Nano 
           330 . Storyline View 
           332 . Beat in Phasetime 
           334 . Phasetime Development Event Instance 
           336 . Storyline 
           338 . Storylinevent Published Data 
           340 . Storylinefforts Published Data 
           342 . Storylinefx Published Data 
           344 . Element&#39;s Effort Instance 
       
     
       SUMMARY OF THE PRESENT INVENTION 
       [0120]    This invention relates to Phasetime tracking and reporting processes and systems. More specifically, it relates to scientifically gathering, storing and reporting of Element Effort Phasetime Data in a Product&#39;s Development as a Project flows through its development Phases of Production, which data is then dynamically reported by the system according to the system&#39;s Points in Phasetime process. 
       DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT 
       [0121]      FIG. 1  illustrates the association capabilities of Elements ( 100 ) and Effort Instances ( 116 ) as they relate to the “Point in Phasetime Method and System Thereof.” 
         [0122]    According to  FIG. 1 , the “Point In Phasetime Method and System Thereof” is comprised of Effort Instances  116  which are constructed of Elements  100  that are associated to one another via their Effort  114  on a Project (PR)  106  within a Point In Phasetime (PiPT)  112 . 
         [0000]    Said Elements  100  can include, but are not limited to, the following:
       Project (PR)  106 —a required Element  100  in which all other Elements  100  have Efforts  114 .   People (PP)  102 —an Element  100  who has an Effort  114  (referred to as a Role  118 ) on the Project (PR)  106 .   Place (PL)  104 —an Element  100  which has an Effort  114  (referred to as a Services  120 ) on the Project (PR)  106 .   Object (OB)  108 —an Element  100  which has an Effort  114  (referred to as a Utilization  124 ) on the Project (PR)  106 .   Project  2  (PR 2 )  110 —another Project Element  100  which has an Effort  114  (referred to as a Contribution  122 ) on the Project (PR)  106 .   Point in Phasetime  112 —a virtual Element  100  which defines the point in time in which an Element&#39;s  100  Effort  114  has occurred on the Project (PR)  106 .       
 
         [0129]    Accordingly,  FIG. 1  details that an Effort  114  value details an exertion (or use of energy) expended on a Project (PR)  106  in the development of an end product. Additionally, said Effort  114  values tie an Element  100  to a Project  106  based on the particular perspective of the Element  100  according to the below:
       People (PP)  102  Effort  114  on Project (PR)  106 =Role  118  Value   Places (PL)  104  Effort  114  on Project (PR)  106 =Services  120  Value   Project  2  (PR 2 )  110  Effort  114  on Project (PR)  106 =Contribution  122  Value   Object (OB)  110  Effort  114  on Project (PR)  106 =Utilization  124  Value       
 
         [0134]      FIG. 2  reaffirms the significance of the Effort  114  values in the association of Elements  100  according to the “Point in Phasetime Method and System Thereof” and establishes the core building blocks of an Effort Instance and Phasetime Data Virtual Matrix  126 . 
         [0135]    Accordingly, both  FIG. 1  and  FIG. 2  acknowledge that the “Point in Phasetime Method and System Thereof” is comprised of Effort Instances  116 , wherein said Effort Instances  116  are constructed of Elements  100  associated to one another via their Effort  114  on a Project (PR)  106  within a Point In Phasetime (PiPT)  112 . 
         [0136]      FIG. 2  builds on this principle by defining that Points of Phasetime  112  indicate “when” all of the Elements  100  have exerted their Efforts  114  on the Project (PR)  106 , wherein each of the Elements  100  are similarly related to one another through their association to a Project (PR)  106  during a shared Point in Phasetime  112 . The shared commonality of the Point in Phasetime  112  with the Elements  100  in their association to a Project (PR)  106  is the binding principle that allows for an Effort Instance and Phasetime Data Virtual Matrix  126 . 
         [0137]      FIG. 3  defines the associative characteristics of the “Point in Phasetime Method and System Thereof” as it relates to an Effort Instance  116  and Phasetime Data Virtual Matrix  126 . 
         [0138]    Accordingly,  FIG. 2  acknowledges that the “Point in Phasetime Method and System Thereof” is comprised of Effort Instances  116  which are constructed of Elements  100  that are associated to one another via their Efforts  114  on a Project (PR)  106  within a Point in Phasetime  112 .  FIG. 3  further establishes the relevancy of the Point in Phasetime  112 , as a virtual 5 th  Element  100 , being a necessary component in the association of all Elements  100  to one another. 
         [0139]    Specifically, the Effort Instance and Phasetime Data Virtual Matrix  126  dictates that the following associations can be made between Elements within the “Point in Phasetime Method and System Thereof,” wherein a Point In Phasetime  112  value represents the point in a Phase of Development  208  at which the association occurs:
       [1]—People to Project Association  118 =Associative Value  128  (Role  118 ) that defines “what People (PP)  102  did on a Project (PR)  106 ” at a given Point In Phasetime (PiPT)  112 .   [2]—Places to Project Association  120 =Associative Value  128  (Services  120 ) that defines “what Places (PL)  104  did on a Project (PR)  106 ” at a given Point in Phasetime (PiPT)  112 .   [3]—Object to Project Association  124 =Associative Value  128  (Utilization  124 ) that defines “what Object (OB)  108  did on a Project (PR)  106 ” at a given Point In Phasetime (PiPT)  112 .   [4]—People to Places Association  130 =Associative Value  128  that ties a People (PP)  102  to a Places (PL)  104  at a given Point In Phasetime (PiPT)  112 .   [5]—People to Objects Association  132 =Associative Value  128  that ties a People (PP)  102  to an Objects (OB)  108  at a given Point In Phasetime (PiPT)  112 .   [6]—Places to Objects Association  134 =Associative Value  128  that ties a Places (PL)  104  to an Objects (OB)  108  at a given Point In Phasetime (PiPT)  112 .   [7]—Projects to Project  2  Association=Associative Value  128  (Contribution  122 ) that defines “what Project 2  (PR 2 )  110  did on a Project (PR)  106 ” at a given Point in Phasetime (PiPT)  112 .       
 
         [0147]      FIG. 4  defines both the Data Collection  136  and Data Reporting  138  capabilities of the “Point in Phasetime Method and System Thereof”. 
         [0148]    According to  FIG. 4 , Element  100  data, Effort Instance  116  data, and Point in Phasetime  112  data are collected from the following Effort Instance and Phasetime Data Collection Interfaces  140 :
       Data Collection Forms  142     Data Validation and Verification Interfaces and Processes  144     Data Reporting Interfaces and Process  146  (migration of data from a Repository to a Core Database  148 ).       
 
         [0152]    As defined by  FIGS. 1-3 , the “Point in Phasetime Method and System Thereof” is comprised of Effort Instances  116  which are constructed of Elements  100  that are associated to one another via their Efforts  114  on a Project (PR)  106  within a Point In Phasetime (PiPT)  112 . According to  FIG. 4 , said Effort Instances  116  are stored in the Core Database (DB)  148  as part of the Effort Instance &amp; Phasetime Data Virtual Matrix  126 . 
         [0153]    The Point in Phasetime  112  values are particularly important in the “Point in Phasetime Method and System Thereof” as they define when events, associations, etc. occur. In addition they have the [virtual] ability to define:
       Past Project Efforts  152 —Those Effort Instances  116  that define associations to, and Efforts  114  on a Project (PR)  106  that has been released as a product.   Present Project Efforts  154 —Those Effort Instances  116  that define associations to, and Efforts  114  on a Project (PR)  106  that is currently in production and has a contracted release date.   Future Project Efforts  156 —Those Effort Instances  116  that define associations to, and Efforts  114  on a Project (PR)  106  that has a contracted release date but is not yet in production.       
 
         [0157]    According to  FIG. 4 , Effort Instance  116  and Point in Phasetime  112  data is extracted from the Effort Instance &amp; Phasetime Data Virtual Matrix  126  in response to Data Search Queries  158  executed from Data Search Query Interfaces  160 , wherein the following dynamic Effort Instance  116  reports are the result of said Data Search Queries  158 :
       People Effort Instance Report  162 —A report from a People (PP)  102  perspective that details the Effort Instance  116  data (Elements  100 , Associations  130   132   134 , Efforts  114 , and Point in Phasetime  112 ) in a CICPE Display  170 .   Places Effort Instance Report  164 —A report from a Places (PL)  104  perspective that details the Effort Instance  116  data (Elements  100 , Associations  130   132   134 , Efforts  114 , and Point in Phasetime  112 ) in a CICPE Display  170 .   Projects Effort Instance Report  166 —A report from a Projects (PR)  106  perspective that details the Effort Instance  116  data (Elements  100 , Associations  130   132   134 , Efforts  114 , and Point in Phasetime  112 ) in a CICPE Display  170 .   Objects Effort Instance Report  168 —A report from an Objects (OB)  108  perspective that details the Effort Instance  116  data (Elements  100 , Associations  130   132   134 , Efforts  114 , and Point in Phasetime  112 ) in a CICPE Display  170 .       
 
         [0162]    Additionally,  FIG. 4  details that Phasetime Matrix Reports  172  can be accessed from the queried Effort Instance Reports  162   164   166   168 . Said Phasetime Matrix Reports  172  can display (but are not limited to) the following:
       Section  1 : Header  174     Section  2 : Phasetime Matrix  176     Arrow of Phasetime X Axis  178     Section  3 : Effort Instance PiPT Window  179         
 
         [0167]      FIG. 5  defines the System (Database) parameters used in “Point in Phasetime Method and System Thereof” as they relate to the structure and data found within the Phasetime Matrix Report  172 . 
         [0168]    According to  FIG. 4 , the Core Database (DB)  148  stores Past, Present, and Future Project Efforts  152   154   156  within the Effort Instance and Phasetime Data Virtual Matrix  126 .  FIG. 5  builds on the principle by defining those Phasetime Report Modules  180  used to store Point in Phasetime  112  data, wherein said modules are used to output Point in Phasetime  112  data within a Phasetime Matrix Report  172 . 
         [0169]    Said Phasetime Report Modules  180  can include, but are not limited to, the following:
       Phasetime Report Header Module  182     Phasetime Matrix Generator Module  184     Phasetime X Axis Generator Module  186     Phasetime Effort Instance Modules  188         
 
         [0174]    Accordingly, each of the above Phasetime Report Modules  180  are used to generate specific attributes within Phasetime Matrix Reports  172 :
       The Phasetime Header Module  182 —generates a Section  1 : Header  174  within the Phasetime Matrix Report  172  that includes the Project&#39;s  106  name, Past/Present/Future Indicator  192 , and an Effort Instance  116  PiPT Effort Instance indicator  272 .   The Phasetime Matrix Generator Module  186 —generates a Section  2 : Phasetime Matrix  176  within the Phasetime Matrix Report  172  in the form of a two-dimensional graphical display with three-dimensional attributes time line which also displays the Effort Instance Owner&#39;s  194  general information and Effort  114  on the Project (PR)  106 .   The Phasetime X Axis Generator Module  186 —generates an Arrow of Phasetime X Axis  178  within the Phasetime Matrix Report  172 ; wherein said Arrow if Phasetime X Axis  178  is a linear [Phasetime] indicator that details the scope (from start date to end date) of a Project (PR)  106  in which Effort Instances  116  exist.   Phasetime Effort Instance Modules  188 —generates a Section  3 : Effort Instance PiPT Window  179  within the Phasetime Matrix Report  172 , wherein said Section  3 : Effort Instance PiPT Window  179  displays Effort Instance Reports  162   164   166   168  and links indicating which Elements&#39;  100  have Efforts  114  on the Project (PR)  106  within the Phasetime Matrix Wireframe  176 .       
 
         [0179]      FIG. 5  also details that the Phasetime Matrix Report  172  will display a link to a Storyboard Beats in Phasetime  196  which are detailed in consecutive Diagrams. 
         [0180]      FIG. 6  illustrates the reporting capabilities of the “Point in Phasetime Method and System Thereof” as related to the display of an Effort Instance Owner&#39;s  194  Effort Instance Report  162   164   166   168 ; as well as those Effort Instance Reports  162   164   166   168  of Elements  100  associated to the Effort Instance Owner  194  through their Effort Instance  166 , all of which is reported within a Phasetime Matrix Report  172 . 
         [0181]    The Phasetime Matrix Report  172  is composed of the following sections: 
         [0182]    1. Section  1 : Header  174   
         [0183]    2. Section  2 : Phasetime Matrix  176   
         [0184]    3. Arrow of Phasetime X Axis  178   
         [0185]    4. Section  3 : Effort Instance PiPT Window  179   
         [0186]    According to  FIG. 6 , the Section  1 : Header  174  displays:
       The name of a Project (PR)  106  (on which the Effort Instance Owner  194  has an Effort  114 )   Project Phasetime Indicator  192 —denotes if the Project  106  was released in the Past  152 , or is a Present  154  release, or is a Future  156  release).   PiPT Effort Instance Indicator  272 —denotes a Macro  202 , Micro  204 , or Nano  206  view of the Effort Instance Owner&#39;s  194  Effort Instance  116 .       
 
         [0190]    According to  FIG. 6 , the Phasetime Matrix Wireframe  176  is used to display:
       The Effort Instance Owner&#39;s  194  name   The Effort  114  of the Effort Instance Owner  194  on the Project (PR)  106     The Effort Instance Owner&#39;s  194  contact information   A list of all of the Projects (PR)  106  Phases of Development  208  according to a linear timeline. Said Phases of Development  208  include:
           Concept Development  210     Pre-Production  212     Production  214     Post-Production  216     Manufacturing, Distribution, and Promotion  218     Post Manufacturing, Distribution, and Promotion  220     
           Phase Boxes  222  which indicate the start date and end date of a Phase of Production  208  along a linear timeline   The Effort Phase Box  224  which indicates the start and end date in which the Effort Instance Owner&#39;s  194  Effort  114  occurred along a linear timeline.   The highlighted section of a Project&#39;s  206  Phase of Production  208  are more or less proportional representations of the Effort Instance Owner&#39;s  194  Effort&#39;s  114  start and end dates, whose proportions are more or less in relation to the duration of the appropriate Phasetime and its context to the earliest start date of Phasetime Clockworks I  228  and its latest end date in Phasetime Clockworks V  235 , or if republished, in Phasetime Clockworks VI  236 .   The Phase Boxes  222 , Effort Phase Boxes  224 , and Arrow of Phasetime X Axis  176  are interactive. Clicking or putting a mouse over the Phase Boxes  222  or Effort Boxes  224  controls the content in the Section  3 : Effort Instance PiPT Window  179 .       
 
         [0205]    According to  FIG. 6 , the Arrow of Phasetime X Axis  176  is used to display:
       The Phase Boxes  222  and Effort Phase Boxes  224  in relationship to a corresponding a Phase of Production  208  and a Phasetime Clockworks  226  which indicates Project Phasetime  300  and Product Runtime  301 :
           Phasetime Clockworks I  228 —Concept Development   Phasetime Clockworks II  230 —Pre-Production   Phasetime Clockworks III  232 —Production   Phasetime Clockworks IV  234 —Post Production   Phasetime Clockworks V  235 —Mfg./Dist./Promotion   Phasetime Clockworks VI  236 —Post Mfg./Dist/Promotion   
               
 
         [0213]    According to  FIG. 6 , the Section  3 : Effort Instance PiPT Window  179  is used to display:
       All Element&#39;s  100  who have Effort Instance Reports  162   164   166   168  as they relate to a specific Phase of Production  208 .
           Said list of Elements  100  are displayed within the Section  3 : Effort Instance PiPT Window  179  when a user clicks on a Phase Box  222  or Effort Box  224  within the Phasetime Matrix Wireframe  176 , or by mousing over a Phasetime Clockworks  226   230   232   234   235   236  within the Arrow of Phasetime X Axis  176 .   
           The Effort  114  values related to those Elements  100  who have Effort Instances  116     The start and end dates in which those displayed Effort Instances  116  occurred.   Past, Present and Future Effort Instance Reports  162   164   166   168  indicted in Section  1 : Header, and referenced in the Arrow of Phasetime X Axis  176     Macro, Micro, and Nano Effort Instance Reports  162   164   166   168  indicated in the Section  1 : Header  174 , referenced in the Arrow of Phasetime X Axis  176 , and selected from Section  2  Arrow of Phasetime Clockwork Icons  274 .   Past Project Effort  152  data which is selected by clicking or putting a mouse over the Arrow of Phasetime X Axis  176  arrow pointing to the screen&#39;s left.   Future Project Effort  156  data which is selected by clicking or putting a mouse over the Arrow of Phasetime X Axis  274  arrow pointing to the screens right, all of which may link to the Storyboard Beats In Phasetime  196 .       
 
         [0222]      FIG. 7  illustrates the reporting capabilities of the “Point in Phasetime Method and System Thereof” as related to the display of the Storyboard Beats in Phasetime  196 . 
         [0223]    The Storyboard Beats in Phasetime  196  is a report accessed from the Phasetime Matrix Report  172 . It contains the following design components and corresponding attributes:
       Storyboard Header Section  240 —Displays Project (PR)  106  info, the Effort Instance Owner&#39;s  194  Effort  114  and info, and Macro  202 , Micro  204  or Nano  206  details.   Storyboard Body Section  242 —Displays “Macro, Micro, Nano Multimedia Content”  246  which can include, but is not limited to, music, video, picture, motion graphics, etc.   Storyboard Footer Section  244 —Displays additional Storyboard Beats in Phasetime  196  information or links which can include, but are not limited to, Search Links  248  and Effortology Key  250  links.       
 
         [0227]      FIG. 8  defines the System (Database  148 ) parameters used by the “Point in Phasetime Method and System Thereof” to generate a Storyboard Beats in Phasetime  196 . 
         [0228]    According to  FIG. 4 , the Core Database (DB)  148  stores Past, Present, and Future Effort  152   154   156  data within the Effort Instance and Phasetime Data Virtual Matrix  126 .  FIG. 8  builds on said principle by defining those Macro, Micro, Nano Phasetime Modules used to generate content within the Storyboard Beats In Phasetime  196 . 
         [0229]    Accordingly, the Core Database (DB)  148  includes at least Macro, Micro, and Nano Storyboard Modules  252  which include, but are not limited to the following:
       Storyboard Header Section Generator Module  254     Storyboard Multimedia Body Generator Module  256     Storyboard Footer Section Generator Module  258         
 
         [0233]    Additionally,  FIG. 7  indicates that a Showlinks Micro, Macro, and Nano Multimedia Database  260  exists within the “Point In Phasetime Method and System Thereof,” wherein said “Multimedia Database”  260  outputs Macro, Micro, Nano Multimedia Content  246  into the Storyboard Beats In Phasetime  196  via the Storyboard Multimedia Body Generator Module  256 . Said Macro, Micro, Nano Multimedia Content  246  can include, but is not limited to, the following:
       Video   Music   Motion graphic   Images   Etc.       
 
         [0239]    As defined above, the Macro, Micro, and Nano Storyboard Modules  252  are used to populate the data that appears within the Storyboard Beats in Phasetime  196 . The following describes each module and the corresponding Storyboard data it reports:
       Storyboard Header Section Generator Module  254 —Reports Project (PR)  106  info and the Effort Instance Owner&#39;s  194  Effort  114  and Info within the Storyboard Header Section  240  of the Storyboard Beats in Phasetime  196 .   Storyboard Multimedia Body Generator Module  256 —Reports Macro, Micro, and Nano Multimedia Content  246  within the Storyboard Body Section  242  of the Storyboard Beats In Phasetime  196 .   Footer Section Generator Module  258 —Reports additional Storyboard Beats in Phasetime  196  information or links that can include, but are not limited to, Search Links  248  and Effortology Key  250  links.       
 
         [0243]      FIG. 9  is a very high line diagram that details all of the System database parameters and reporting modules used by the “Point in Phasetime Method and System Thereof” in the generation of the Phasetime Matrix Report  172  and the Storyboard Beats in Phasetime  196 . 
         [0244]    According to  FIG. 9 , the “Point in Phasetime Method and System Thereof” is comprised of, but not limited to, the following databases:
       Showlinks Data Repository Database  150     Showlinks Core Database  148     Showlinks Macro, Micro, Nano Multimedia Database  260         
 
         [0248]    Accordingly, Multimedia Exhibits  262  are transferred from the Showlinks Data Repository Database  150  to the Macro, Micro, Nano Multimedia Database  260  via an Editing &amp; Formatting Process  268 , wherein said Editing and Formatting Processes  268  will create formatted and organized Macro, Micro, Nano Multimedia Content  246  used in the Storyboard Beats In Phasetime  196 . 
         [0249]    Additionally, Effort Instance  116  and Point In Phasetime  112  data are output from the Showlinks Core Database  148  by a Phasetime Matrix Report Generating Module  270  and displayed within Phasetime Matrix Reports  172  and Effort Instance Reports (CICPE)  162   164   166   168 . 
         [0250]    Finally, the diagram details that a Storyboard Beats In Phasetime  196  is accessed from Phasetime Matrix Reports  172  and Effort Instance Reports  162   164   166   168 , wherein the Micro, Macro, and Nano Phasetime  202   204   206  data used in the Storyboard Beats In Phasetime  196  is dynamically extracted from both the Showlinks Core Database  148  and the Showlinks Macro, Micro, Nano Multimedia Database  260  by Micro, Macro, and Nano Storyboard Modules  252 . 
         [0251]      FIG. 10  details how Phasetime Macro  324 , Phasetime Micro  326 , and Phasetime Nano  328  Storyline Views  330  are generated from Published Products  204 . 
         [0252]    According to  FIGS. 1-4  a Project (PR)  106  exists in which all Elements  102   104   108   110  exert their Efforts  114  in an Effort Instance  116 . This concept is expanded in  FIG. 10  by detailing those additional Project (PR)  106  attributes used in Effort Instances  116  as related to Points in Phasetime  112  and the generation of Project Phasetime  300  data and reports. 
         [0253]    Accordingly, Projects (PR)  106  have corresponding Project Phasetimes  300  which can be broken down into six Phases of Development  208 , wherein said Phases of Development  208  detail the Project&#39;s (PR)  106  Development Cycle  302 . Specifically, Phases of Development are designated segments of a Project&#39;s (PR)  106  Development Cycle  322  according to its Product type: 
         [0254]    1) Concept Development Blueprint  210   
         [0255]    2) Pre-Production  212   
         [0256]    3) Production  214   
         [0257]    4) Post Production  216   
         [0258]    5) Manufacturing/Distribution /Promotion  218   
         [0259]    6) Post Manufacturing/Distribution/Promotion  220   
         [0260]    According to  FIG. 10 , Effort Instances  116  are related to Project Phasetimes  302  by Point in Phasetime  112  values which detail “when” an Element  100  exerted their Effort  114  on the Project (PR)  106 . In addition Projects (PR)  106  will become Published Products  304  after they have officially been published or released to the public. Specifically, this occurs when the Project (PR) is issued a Publication Date  302  (a date on which the Project  106  is published and becomes a Published Product  304 , a Phasetime Parturient Event  303 . 
         [0261]      FIG. 10  also details that a Product&#39;s Storyline Data  306  is converted into Phasetime Macro  324 , Phasetime Micro  326 , and Phasetime Nano  328  data jointly by a Storyline Architect  307  and an Effortologist  309  during the Macro, Micro, and Nano Editing Process  308  derived from Project Phasetimes  300 , wherein said Project Phasetimes  300  are furnished by the Project&#39;s (PR)  106  Effort Instance  116  and corresponding Points In Phasetime  112 . 
         [0262]    Said Macro, Micro, and Nano Editing Processes  308  are used to produce Macro  202 , Micro  204 , and Nano  206  Phasetime data for their Storyline View  330  which can include, but are not limited to, the following: 
         [0263]    1. Phasetime Macro  324 —A landscape view of an Effort Instance Owner&#39;s  194  Effort  114  on a Project (PR)  106  at a Point in Phasetime  112 . 
         [0264]    2. Phasetime Micro  326 —A portrait view of an Effort Instance Owner&#39;s  194  Efforts  114  on a Project (PR)  106  at a Point in Phasetime  112 . 
         [0265]    3. Phasetime Nano  328 —A close-up view of an Effort Instance Owner&#39;s  194  Effort  114  on a Project (PR)  106  at a Point in Phasetime  112 . 
         [0266]      FIG. 11  details how Phasetime Macro  324  Storyline Views  330  are generated from Published Products  204 . 
         [0267]    According to  FIGS. 10 and 11 , a Project (PR)  106  exists in which all Elements  102   104   108   110  exert their Efforts  114  in an Effort Instance  116 , whereby additional Project (PR) attributes used in Effort Instances  116  are related to Points in Phasetime  112  and the generation of Project Phasetime  300  data and reports. Accordingly, Projects (PR)  106  have corresponding Project Phasetimes  300  which can be broken down into six Phases of Production  208 , wherein said Phases of Development  208  detail the Project&#39;s (PR)  106  Development Cycle  302 . 
         [0268]      FIGS. 10 and 11  further define that Effort Instances  116  are related to Project Phasetimes  302  by Point in Phasetime  112  values which detail “when” an Element  100  exerted their Effort  114  on the Project (PR)  106 . In addition said Projects (PR)  106  will become Published Products  304  after they have officially been published or released to the public. Specifically, this occurs when the Project (PR) is issued a Publication Date  302  (a date on which the Project  106  is published and becomes a Published Product  304 ). 
         [0269]      FIG. 11  expands on this concept by detailing that a Product&#39;s Storyline Data  306  is converted into Phasetime Macro  324  data jointly by a Storyline Architect  307  and an Effortologist  309  during the Macro, Micro, and Nano Editing Process  308  derived from Project Phasetimes  300 . Specifically, said Macro, Micro, and Nano Editing Process  308  is used to produce Phasetime Macro  324  data which is displayed within a Phasetime Macro Storyline View  310  report, wherein a Phasetime Macro Storyline Generating Module  310  is used to create said Phasetime Macro Storyline View  310  report. 
         [0270]    The Phasetime Macro Storyline View  310  is a landscape view of a Published Product  304 , wherein the objective of said landscape view is to provide a Storyline Product overview, whose Beat in Phasetimes  332  associates an Effort Instance Owner&#39;s  194  Effort  114  to appropriate Phasetime Macro  324  landscape view attributes, which are comprised of hi-line Phasetime Micro  326  view data of the Effort Instance Owner&#39;s  194  Development Event Instance  334 . 
         [0271]    Accordingly, said Development Event Instances  334  occur when an Effort Instance Owner  194  (a People  102 , a Places  104 , a Project  106 , or an Object  108 ) perform conjoined Efforts  114  on a Project (PR)  106  in relation to a Point in Phasetime  112  within a Phase of Development  208  of a Published Product  304 . 
         [0272]      FIG. 12  details how Phasetime Micro  326  Storyline Views  330  are generated from Published Products  204 . 
         [0273]    According to  FIGS. 10 ,  11 , and  12  a Project (PR)  106  exists in which all Elements  102   104   108   110  exert their Efforts  114  in an Effort Instance  116 , whereby additional Project (PR) attributes used in Effort Instances  116  are related to Points in Phasetime  112  and the generation of Project Phasetime  300  data and reports. Accordingly, Projects (PR)  106  have corresponding Project Phasetimes  300  which can be broken down into six Phases of Production  208 , wherein said Phases of Development  208  detail the Project&#39;s (PR)  106  Development Cycle  302 . 
         [0274]      FIGS. 10 ,  11 , and  12  further define that Effort Instances  116  are related to Project Phasetimes  302  by Point in Phasetime  112  values which detail “when” an Element  100  exerted their Effort  114  on the Project (PR)  106 . In addition, said Projects (PR)  106  will become Published Products  304  after they have officially been published or released to the public. Specifically, this occurs when the Project (PR) is issued a Publication Date  302  (a date on which the Project  106  is published and becomes a Published Product  304 ). 
         [0275]      FIG. 12  expands on this concept by detailing that a Product&#39;s Storyline Data  306  is converted into Phasetime Micro  326  data jointly by a Storyline Architect  307  and an Effortologist  309  during the Macro, Micro, and Nano Editing Process  308  derived from Project Phasetimes  300 . Specifically, said Macro, Micro, and Nano Editing Process  308  is used to produce Phasetime Micro  326  data which is displayed within a Phasetime Micro Storyline View  316  report; wherein a Phasetime Micro Storyline Generating Module  314  is used to create said Phasetime Micro Storyline View  316  report. 
         [0276]    The Phasetime Micro Storyline View  316  is a portrait view of a Published Product  304 , wherein the objective of said portrait view is to provide a Storyline Product scene-sequence view, whose Beat in Phasetimes  332  associates an Effort Instance Owner&#39;s  194  Effort  114  to appropriate Phasetime Micro  326  portrait view attributes, which are comprised of hi-line Phasetime Nano  328  view data of the Effort Instance Owner&#39;s  194  Development Event Instance  334 . 
         [0277]    Accordingly, said Development Event Instances  334  occur when an Effort Instance Owner  194  (a People  102 , a Places  104 , a Project  106 , or an Object  108 ) perform conjoined Efforts  114  on a Project (PR)  106  in relation to a Point in Phasetime  112  within a Phase of Development  208  of a Published Product  304 . 
         [0278]    FIG.  13 —The “Detailed Phasetime Project/Published Product Micro Storyline Diagram # 1 C” details how Phasetime Micro  326  Storyline Views  330  are generated from Published Products  204 . 
         [0279]    According to  FIGS. 10-13  a Project (PR)  106  exists in which all Elements  102   104   108   110  exert their Efforts  114  in a Effort Instance  116 , whereby additional Project (PR) attributes used in Effort Instances  116  are related to Points in Phasetime  112  and the generation of Project Phasetime  300  data and reports. Accordingly, Projects (PR)  106  have corresponding Project Phasetimes  300  which can be broken down into six Phases of Production  208 , wherein said Phases of Development  208  detail the Project&#39;s (PR)  106  Development Cycle  302 . 
         [0280]      FIGS. 10-13  further define that Effort Instances  116  are related to Project Phasetimes  302  by Point in Phasetime  112  values which detail “when” an Element  100  exerted their Effort  114  on the Project (PR)  106 . In addition said Projects (PR)  106  will become Published Products  304  after they have officially been published or released to the public. Specifically, this occurs when the Project (PR) is issued a Publication Date  302  (a date on which the Project  106  is published and becomes a Published Product  304 ). 
         [0281]      FIG. 13  expands on this concept by detailing that a Product&#39;s Storyline Data  306  is converted into Phasetime Nano  328  data jointly by a Storyline Architect  307  and an Effortologist  309  during the Macro, Micro, and Nano Editing Process  308  derived from Project Phasetimes  300 . Specifically, said Macro, Micro, and Nano Editing Process  308  is used to produce Phasetime Nano  328  data which is displayed within a Phasetime Nano Storyline View  320  report, wherein a Phasetime Nano Storyline Generating Module  318  is used to create said Phasetime Nano Storyline View  320  report. 
         [0282]    The Phasetime Nano Storyline View  316  is a close-up view of a Published Product  304 , wherein the objective of said close-up view is to provide a Storyline Product scene blueprint view, whose Beat in Phasetimes  332  associates an Effort Instance Owner&#39;s  194  Effort  114  to appropriate Phasetime Micro  326  portrait view attributes, which are comprised of hi-line Phasetime Nano  328  view data of the Effort Instance Owner&#39;s  194  Development Event Instance  334 . 
         [0283]    Accordingly, said Development Event Instances  334  occur when an Effort Instance Owner  194  (a People  102 , a Places  104 , a Project  106 , or an Object  108 ) perform conjoined Efforts  114  on a Project (PR)  106  in relation to a Point in Phasetime  112  within a Phase of Development  208  of a Published Product  304 . 
         [0284]    FIG.  14 —According to  FIGS. 1 ,  2 ,  3 ,  4 ,  10 ,  11 ,  12 , and  13 , the “Point in Phasetime Method and System Thereof” is comprised of Effort Instances  116  which are constructed of Elements  100  (People  102 , Places  104 , Projects  106 , and Objects  108 ) that are associated to one another via their Efforts  114  on a Project (PR)  106  within a Point In Phasetime (PiPT)  112 .  FIG. 14  expands on this concept by detailing how Effort Instances interact and affect a Point In Phasetime&#39;s  112  Storyline  336  as displayed within Phasetime Macro  324 , Phasetime Micro  326 , and Phasetime Nano  328  Storyline Views  330 . 
         [0285]    According to  FIG. 14 , a Storyline  332  is an attribute of an Effort  114  by any Element  102   104   106   108  that details the creative decisions involved in the production of the Project (PR)  106  as defined by a Phasetime Development Event [Instance]  334 . Said Phasetime Development Event [Instance] is defined as a development event that occurs when the Elements  100 , a People (PP)  102 , a Places (PL)  104 , a Project (PR)  106 , and an Object (OB)  108 , perform conjoined Efforts  114  on a Project (PR)  106  in relation to a Point in Phasetime  112  within a Phase of Development  208  of an industry product. 
         [0286]    Accordingly, Projects (PR)  106  will become Published Products  304  after they have officially been published or released to the public. Specifically, this occurs when the Project (PR) is issued a Publication Date  302  (a date on which the Project  106  is published and becomes a Published Product  304 ). 
         [0287]    In addition, Storylinevent Published Data  338  is converted from the Point In Phasetime  112  of the Phasetime Development Event [Instance]  334  into Phasetime Macro  324 , Phasetime Micro  326 , and Phasetime Nano  328  data jointly by a Storyline Architect  307  and an Effortologist  309  during the Macro, Micro, and Nano Editing Process  308  derived from Project Phasetimes  300 , wherein said Project Phasetimes  300  are furnished by the Project&#39;s (PR)  106  Effort Instance  116  and corresponding Points In Phasetime  112 . 
         [0288]    Diagram  14  details dotted lines which tie Phasetime Macro  324 , Phasetime Micro  326 , and Phasetime Nano  328  Storyline Views  330  to the Product Storyline  336  within the Phasetime Development Event [Instance]  334 . Said dotted lines are used to indicate: 
         [0289]    1) How the Storyline  336  affects Elements  100  and production; 
         [0290]    2) How Element  100  Efforts  114  may reverse that process and affect the Storyline  336  through Storylinefforts  340  and Storylinefx  342 . 
         [0291]    Accordingly, the ability for the Phasetime Development Event [Instance]  334  to affect the Storyline  336  is an attribute of an Effort  114  by an Element  100  which goes to the heart of the Published Product&#39;s  304  story, whether the Element  100  is in front of or behind the camera, microphone, etc.