This thread is for discussions of Schedule Extreme Pro.

The SRS is the CRM to the SXP.

I've just finished the first phase of the SRS.   Using SRS, I can create an instanteous workflow environment for any virtual community.   Contact me for details or demo code. (davepamn@relia.net)

Within days, SRS could become your websites virtual community allowing a community to start forming around your technology and ideas.  SRS is self managed by the community.  SRS can receive inputs feedback from a variety of resource types.  Dynamic Form create allow specific information to be requested during user postings of data.  

The code is pure ASP, so you drop it on a NT server and your ready to go.

The SRS product is the replacement to conventional email collaboration.  SRS can do everything email can and more.   SRS broadcast messages to anyone in the world using email, but only allows response to come back through the SRS. SRS is stops the SPAM from slowing down work.  SRS organizes your collaboration efforts.

SRS is scalelable, so it can distributed out of the box to thousands of companies.  Within minutes they can get their whole corporation using the product.  Hundreds of people can login and use the product.

Beta Site click here

The "Survival Recovery System" will revolutionize email communication and slow down spam and virus vulnerability.  SRS will provide a centralized communication collaboration system where all corporate workflow can be done.

People join the SRS and are allowed to post messages to channels.  The SRS operates on the assumption that the “people have the answers”.  Center leader are promoted from the community and control the “workflow” of the message.  Center leaders are trusted community members and are expected to have integrity and promote the general welfare of the community.

As the message advances through time: all the work decision history is stored, auxilliary attachments are connected to the message, drill down into feedback between channel groups is possible, and all channel group comments are embedded in the message.

Keith Ogden is quoted to say, "we must be able to measure time performance" between channel groups.   The message structure can be analyzed to extract time and quality metrics.   Keith believes the SRS will become a CMM business intelligence tool.   Its possible to built ghant charts for the time lines stored in the message.  

Think about the message as a piece of work on an assembly line.  At any point, a controller, in the SRS can see the progress of the work message.   Because the message is associated with a priority status it will be possible to see which agencies are being over run with critical messages.

The most powerful feature of the tool will be the capability to correspond back and forth from the SRS to anyone in the world and requesting a response, while maintaining all information historical information within the confines of the SRS.   No information is lost in a correspondence of emails.

As companies start to rely more and more on information, a centralized approach to information management only makes sense.

click here

Dynamic Form

This is the setup form for the dynamic form.  

The user will be able to add or remove an unlimited number of fields on the data form.  

Step 1:  The user creates a form and associates the it with a channel classification

Step 2:  The user enters in field information, such as, sort position, field type, field name, field length, and field description.   If the field type is a list box, the user will be able to enter in list box items.

Step 3:  The dynamic form will then generate the input html form to be stored in the database and an output xsl to transform the inputted xml structure into output readable html.

The form transform component will take the definition and build an html form to be stored in the database.  The html form will receive input from the form and transform it into a message xml structure stored in the central database.  

click here

Features of a Channel

Each Channel can have one or more channels, for which, the controller group can promote too.
Only the controlling group can promote a message to another channel
Cross talk and message status notification can be disseminated to other channel groups

For example, if a message involved accounting, the message may be need to route to in a formal promotion route or deviate to other groups.  A search capability will allow searching and reporting for a specific message.  

There are three roles a user can play: basic user, center leader, or administrator.  Only the center leader can promote the message to another channel.  The Center leader can decide the different routes the message needs to take.  Center leader may want to monitor the message status being worked by other center leaders and coordinate handoff.

In many cases, having a centralized point for the mixture of messages makes sense.  So the different groups talk about one topic and work through the issues together.  We anticipate the groups will generate a lot of cross talk and the cross talk will always map back to the originating message.  The cross talk remains as support communication.  Cross talk may include two types of communication coordination: general discussions and more department-specific communications.  The user can segment the type of cross talk communication by adding a user define feedback topic to post feedback too.  Perhaps a gag topic will be created to talk trivia and post personalized social information not relevant to a work topic.

The work message will receive the following

Unique Id
Priority number
Attachment
Decisions (Rules that follow a logic tree)
Feedback messages
Routing instructions

click here

Center leaders have the privilege to promote a message to another channel.  This is done from the message page by selected the target channel and pressing the promote button.  A history note is append to the message with the following information:

From channel
To channel
Date Promotion Occurred.

So as, the message gets promoted through the pipeline, messages with higher priorities get the highest visibility.  Also, the user can filter messages according to a specific message priority.  At a glance, you should be able to tell how someone is doing, like on a scale of 1-5, if they're up and running or just barely communicating.  

Follow-up will be critical.  People can select how much message traffic they want to see based on the priority system.  They can ask for all traffic, only priority 1s, etc.  If a hospital is burning down, you don't want it to get lost in a thousand incoming messages.  Filtering and deciphering information quickly will be important.  If their state is '0', we know they're not okay.  Once the workload starts, keeping track of the progress becomes critical.  Estimates to completion should be available to show progress.  The survival center might have a person delegated to review only (priority 1) traffic.  Another would only get priority 2 traffic.  Lower priority messages can be moved to a low priority queue and worked when convenient.  The idea of segmentation and integration is definitely required.  

click here

Sometimes the center leader will become overwhelmed.  Other times they will need to get more information.  The cross talk forum allows them to talk directly with relevant resources to get more detail.  A system of color codes will help them understand their message status.

Each community will have a different emergency plan.  It is important to careful review the emergency plan and make sure that a continuity folder is created to document a series of checklist items to follow.  

So the checklists represent the sequential steps in the emergency plan.   Center leaders will be able to set up an checklist template and once the template has been defined with questions it can be used to store the center leaders responses.  The structure of the checklist is a set of questions with checkboxes for leader to click.  The information is stored in the database.

Some indicators would tell progress, others would tell workload, etc.  Each community would have its own workflow plan.  Other indicator lights would designate specific needs.  The workflow plan would need to be pre-set-up.  Messages that don't fit the pre-design workflow could go into an overflow area where a specialist could decide where to route it.  I think if the message goes to the community and it does not fit a classification then they have a miscellaneous channel, and then they research where to put it.  

Overview:  A resource will be able to create a schedule pattern.   Schedule patterns represent one or more days between Monday and Sunday for which work can be applied.  A single day can have one or more shift segments.   A shift segment describes the start time, time interval, labor account, and location information.   Once a shift segment is assigned to a day, resources assignments can be applied to the shift.  Only individuals in the schedule group can be assigned to a shift.  One the assignment is complete the resource is notified by email of the shift assignment. Resources can request specific shift assignments or request time off from the supervisor.  The supervisor can “Accept” or “Decline” the requests.  

If the schedule pattern is made public, resources can schedule appoints with resources working the shift.  If the schedule pattern is private only resources in the schedule group can view the schedule.