Abstract: A data storage method and system. The method includes defining, by a computing system, a meta-object, a schema based structured definition for the meta-object, and a taxonomy with configuration data. The computing system creates content associated with the taxonomy and associates topics of the content with a logical storage room representations. Reference coordinates associated with the logical storage room representations are associated with the taxonomy. The computing system generates updated configuration data that includes the reference coordinates and a uniform resource identifier associated with the content is generated. The computing system generates an account associated with the meta-object for a user. Metering charges for usage of the account and a report associated with the account and usage are generated.

Abstract: Methods, systems, and products are provided for workflow decision management. Embodiments include maintaining a device state history; identifying a plurality of device usage patterns in dependence upon the device state history; identifying a plurality of workflow scenarios in dependence upon the device usage patterns; determining a workflow administration capacity in dependence upon the plurality of workflow scenarios; identifying a plurality of workflows in dependence upon the workflow scenario; executing the plurality of workflows in dependence upon the workflow administration capacity.

Abstract: A method, system, and computer-readable medium for predicatively selecting which work packets will be needed by a software factory to create a deliverable custom software are presented. In a preferred embodiment, the computer-implemented method includes: presenting an initial checklist that consists of a series of question groups; receiving answers to the initial checklist; in response to determining that received answers to the initial checklist indicate that a new series of questions is required to predict which work packets will be needed to create the deliverable custom software, dynamically generating a new checklist; evaluating leading indicators for the received answers; based on relevancy of answers and the leading indicators, eliminating irrelevant questions from the new checklist; and based on answers to remaining relevant questions, determining if a particular work packet will be needed to create the deliverable custom software in the software factory.

Abstract: Enterprise Intelligence (‘EI’) reporting in an EI framework, including: identifying, by an EI report generator, EI report criteria for inclusion in an EI report; extracting, by an EI report generator, EI report information that meets the EI report criteria from an EI data repository; assembling, by an EI report generator, the EI report information into an EI report; and presenting the EI report to an EI administrator.

Abstract: Security for a software factory is provided by detecting a request by a user to utilize the software factory. Upon being authenticated, the user is granted permission to access specific areas of the software factory. A log is created of locations in software factory that have been accessed by the user. This log is then utilized in an audit that describes how effective the software factory is in creating deliverable software.

Abstract: A method, system, and computer-readable medium for managing a work packet's life cycle, wherein the work packet is assembled in a software factory that creates custom software in a standardized manner, are presented. In a preferred embodiment, the computer-implemented method comprises the steps of: defining a work packet to perform a sub-function of a custom software, wherein the work packet is a pre-stored, reusable, self-contained, discrete unit of software code; assembling the work packet; archiving the work packet in an asset repository; retrieving the work packet from the asset repository; and sending the work packet to an assembly line for consolidation with other work packets to create a custom software.

Abstract: A method, system and computer-readable medium for creating software in a standardized manner are presented. The method includes the steps of: receiving, at a software factory, a description of software needs from a customer; creating, in the software factory, a project proposal that meets performance criteria found in the description of software needs; inducting the project proposal into the software factory, where inducting the project proposal initially evaluates the project proposal's compatibility with a capacity of the software factory; parsing the project proposal into major functional areas; retrieving work packets that are appropriate for the project proposal, where the work packets are pre-stored, reusable, self-contained, discrete units of software code; assembling the work packets into a deliverable software; testing the deliverable software; and delivering the deliverable software to the customer.

Abstract: Enterprise Intelligence (‘EI’) reporting in an EI framework, including: identifying, by an EI report generator, EI report criteria for inclusion in an EI report; extracting, by an EI report generator, EI report information that meets the EI report criteria from an EI data repository; assembling, by an EI report generator, the EI report information into an EI report; and presenting the EI report to an EI administrator.

Abstract: Managing processes in an Enterprise Intelligence (‘EI’) assembly of an EI framework, including: for each executing EI assembly in the EI framework, in real time: tracking, by the process state transition manager, the present state of processes of each executing EI assembly; analyzing, by the process state transition manager, the present state; and storing, by the process state transition manager, results of the state analysis.

Abstract: Enterprise Intelligence (‘EI’) management in an EI framework including: analyzing, by an assembly analysis engine, a plurality of EI assemblies, each EI assembly configured to carry out a business capability upon execution; choreographing, by an assembly engine, execution of one or more of the EI assemblies; and reporting, by the assembly engine to an EI administrator, information related to execution of the one or more of the EI assemblies.

Abstract: Decomposing a process model in an Enterprise Intelligence (‘EI’) framework, including: receiving, by a process model decomposer, a process model for an EI assembly; identifying, by the process model decomposer in dependence upon an EI framework metamodel, component parts of the process model; and generating, in dependence upon the identified component parts, a taxonomy breakdown comprising a definition of a process classification.

Abstract: Managing a collection of assemblies in an Enterprise Intelligence (‘EI’) framework, including: identifying, by an assembly collection tool, one or more processes for inclusion in a specification of an assembly, the assembly configured to carry out a business capability upon execution in the EI framework; identifying for each process, by the assembly collection tool, one or more tasks that comprise the process; identifying for each task, by the assembly collection tool, one or more steps that comprise the task; identifying, by the assembly collection tool, a sequence for executing the steps, tasks, and processes in the assembly; generating, in dependence upon the identified processes, tasks, steps, and sequence, the specification of the assembly; and storing the specification in a EI assembly repository.

Abstract: Enterprise Intelligence (‘EI’) assembly analysis in an EI framework, including: determining, by an EI assembly analysis engine, the present execution state of one or more EI assemblies; determining, by the EI assembly analysis engine, the ideal execution state for the one or more EI assemblies; and identifying, by the EI assembly analysis engine, differences between the present execution state of the one or more EI assemblies and the ideal execution state for the one or more EI assemblies.

Abstract: A computer-implemented method, system, and computer-readable medium for determining if a software factory is ready to take on a software project is presented. In a preferred embodiment, the computer-implemented method includes the steps of: determining if an infrastructure for a software factory has been procured; determining if operational software needed to assemble work packets in an assembly line in the software factory has been installed; determining if a workflow event model for an assembly line in the software factory has been configured; determining if workload in the assembly line has been balanced; determining if communication channels between the software factory and a customer's computer system have been defined and cleared for data transmission; and in response to determining that any element described above has been determined not to have occurred, prohibiting an induction of a software project into the software factory.

Abstract: Within the context of a software factory, process sensors detect time consuming activities that extend beyond an estimated predetermined completion timeline for a project. These process sensors also detect wait states that are caused by processes and activities of tasks that are not critical to completing the project. A process analysis is used to determine if defined added value processes and activities identified in a value stream analysis are interdependent to a critical path for executing the project. If the defined added value processes and activities identified in the value stream analysis are determined to not be interdependent to the critical path for executing the project, then a determination is made that performance of the defined added value processes and activities identified in the value stream analysis is wasteful and such processes and activities are eliminated from the process.

Abstract: A method, system, and computer-readable medium for maintaining a health of a software factory that creates custom software in a standardized manner is presented. In a preferred embodiment, the method includes the steps of: defining work packets to perform sub-functions of a custom software; tracking a transmission of the work packets to an assembly line in a software factory; monitoring any retrieval of software artifacts that are used to create the work packets; monitoring any on-going changes of work activities that are contained in the work packets; determining if execution of the work packets conforms to governance guidelines for the software factory; monitoring the software factory to ensure that the work packets comply with an architecture of the software factory; tracking quality metrics for an execution of the work packets in an assembly line in the software factory; and transmitting all tracked and monitored information described above to a dashboard.

Abstract: A computer-implemented method, system, and computer-readable medium for determining if a software factory is ready to take on a software project is presented. In a preferred embodiment, the computer-implemented method includes the steps of: receiving a software project proposal including a custom software description describing a specific project type of the software project; determining, by a computer processor, that the software project proposal is qualified for acceptance by a software factory, utilizing a scorecard for the specific project type, wherein the scorecard provides a maturity assessment of resources required and identifies any potential choke-points for the specific project type; and in response to a determination that the software project proposal is qualified for acceptance by the software factory, the software factory undertaking the software project proposal.

Abstract: Methods, systems, and products are provided for intermediate message invalidation that include receiving, to an intermediate message validation service, a message to be forwarded to a device to administer at least one value of an attribute of the device; determining, by the intermediate message validation service, that the message is invalid; and terminating, by the intermediate message validation service, the invalid message. Embodiments may also include notifying a system administrator that the message is invalid.

Abstract: A method, system, and computer-readable medium for assembling work packets within a software factory are presented. In a preferred embodiment, the computer-implemented method comprises the steps of: collecting a plurality of software artifacts that have been archived during an assembly of previous work packets; collecting a plurality of metrics that have been utilized during the assembly of previous work packets; defining a template for a new work packet, wherein the template for the new work packet is created by a packet definition process that defines attributes that are needed in the new work packet; selecting requisite software artifacts from the plurality of software artifacts; selecting requisite metrics from the plurality of metrics; and sending the template, requisite software artifacts and requisite metrics to a packet assembly process, wherein the packet assembly process assembles the requisite software artifacts to create the new work packet.

Abstract: A system decision engine enables a software factory to effectively handle intelligent load balancing and distribution to workers on a software assembly line through the use of pre-configured rules. The pre-configured rules are based on a projected availability of workers based on past traffic analysis of work packets being sent to particular workers on the software assembly line.