Schedule Syndication

OD/Kerry M. SoileauApril 28, 2009

Suborganizations

Big org

Suborg 1

Suborg 2 Suborg 3

Suborg31

Suborg32

Suborg 4

Organizations are usually made up of smaller suborganizationsAlthough they are separate entities, their work is usually interdependent on the activities of other suborganizationsThis means that it is necessary to monitor the completed work and future plans of other suborganizations

Overview ScheduleTypically the way this is done is, at various times an OVERVIEW SCHEDULE is publishedThis document collects top-level schedule dates from each of the suborganizations and combines them together on a single scheduleEach of the suborganizations gets a copy of this schedule and uses it to do its own internal planning and scheduling

Problems

While useful, this approach has several weaknesses:1. Interested parties cannot

control the freshness of the data; they are stuck with whatever was current the last time the overview was published

2. Interested parties cannot control the content of the schedule. They are stuck with whatever was considered “top level” by the schedule’s creator.

This overview schedule has much more

information than I need

AND it hasn’t been updated in more than a month…

On-Demand Overview ScheduleWe propose to enable any user to generate a customized overview schedule on demand.This document collects top-level schedule dates from each of the suborganizations to which that user is subscribed (i.e., is interested in) and combines them together on a single schedule. This produces a schedule which contains only information of interest, and is as up-to-date as feasible.

On-demand overview schedule

Prototype Screenshot

HTML Screenshot

Sample Initial Selection of Source Schedules

SCSRP (Software Change and Schedule Release Panel)

• Display Delivery Schedule

IDDT

• ISS Flight/Transition Schedule 1 -pager

ISS Systems Integration

• ECW File Schedule

Software Product Delivery Team Working Group

• Standard Weekly Calendar

Caution and Warning System Integration Team

• HRCS Ground Segment Integrated Schedule

International Partners Integration

• Schedule

• Schedule

Test Activity Schedule

• Development Schedule

Data Integration Team (DIT)

PPL WG

GN&C PPL

STS Launch Schedule

ISS Crew Rotation Schedule\

et cetera

Key for Schedule Source Datatitle• The identifier for the source schedule

description• More details about the source schedule

event• An individual event of interest

subject• An identifier for the event

startdate• The calendar date on which the event is scheduled to occur

enddate• The calendar date on which the event is scheduled to occur

starttime• The time of day on which the event is scheduled to occur

endtime• The time of day on which the event is scheduled to occur

location• The locale for the event

url• An optional URL for additional information about the event

source• The identifier for the source schedule from which the event data was obtained

Proposed Source Calendar Data Format

<ses version="1.0"> <channel> <title>ASCB</title> <description></description> <event> <subject>IMMT (ISS Mission Management

Team)</subject> <startdate>4/13/2009</startdate> <enddate></enddate> <starttime>8:00:00 AM</starttime> <endtime></endtime> <location>30M/118,119</location> <url>http://kerrysoileau.com/feeds/ASCB.xml</url> <source>ASCB</source> </event> <event> <subject>CRCP (Computer Resources Control

Panel)</subject> <startdate>4/13/2009</startdate> <enddate></enddate> <starttime>9:30:00 AM</starttime> <endtime></endtime> <location>SCTF/2043</location> <url>http://kerrysoileau.com/feeds/DIT.xml</url> <source></source> </event> </channel></ses>

XML format is recommended for several reasons:XML is naturally machine-readable and many parsers are available.XML creation and editing is made easy by a number of available applications, including the free XML Notepad. Direct text editing is also an option.Once created, the source calendar data can easily drive the creation of web pages for the source organization, so this would no longer have to be done manually.

Proposed Subscription File Format

<feeds><url>file:///D:/Feeds/SPN.xml</url><url>file:///D:/Feeds/ASCB.xml</url><url>file:///D:/Feeds/DIT.xml</url><url>file:///D:/Feeds/PICB.xml</url><url>file:///D:/Feeds/MIP.xml</url><url>file:///D:/Feeds/ISSStandardOuts.xml</url><url>file:///D:/Feeds//ISSCCSR9.xml</url>

</feeds>

This is the file by which each user indicates the source schedules of interest.It contains the URL locations of the data for each source schedule of interest. It can be easily modified either manually or through the overview schedule application.

To Do Determine host server for software Develop software Develop documentation for

Users Source Schedule Maintainers

Upload software to server Determine host location for

Menu of available source schedules Help website Source schedule data template

Determine identity of voice help Determine default set of source schedules Determine initial selection of source schedules Determine participating organizations For each org, determine POC responsible for that org’s source schedules Develop template for source schedule data Determine deadline for deployment of source schedules Determine release date for system

Announcement Letters

Letter to Users• April 14, 2009• Dear User:• A new way of producing overview schedules is now being introduced. You have been

identified as a prospective user of this feature.• To access the system, you must do a few one-time-only setup tasks.• SETUP PROCEDURE• To use the system, you must install the overview generation software on your

workstation, taking care that the provided file named subscriptions.xml is in the same folder. The software activates like any other Windows executable.

• USE• Once you are set up, you may generate an overview schedule at any time by running

the overview generation software named _______ available at _________ for download. You will be able to print the generated schedule using the software.

• The overview schedule will initially include a default set of source schedules from which the overview schedule will be assembled. If at any time you wish to change the set of source schedules, you may do so using a feature of the overview generation software. The default set default set of source schedules is given in the following table:

• • • • • • • A listing of available schedules from which to assemble a custom set of source

schedules may be found at http://__________________.• If any questions refer to the help website or contact _____________ at (___)___-____.• Sincerely,

Letter to Source Schedule Maintainers• April 14, 2009• Dear Source Schedule Maintainer:• A new way of producing overview schedules is now being introduced. You

have been identified as the responsible person in your organization for source schedule maintenance. This means you will be in charge of keeping the source schedule for you organization as complete and accurate as feasible.

• A template from which to build an initial source schedule may be found at http://__________________.

• Please have your source schedules in place by __/__/__.• If any questions refer to the help website or contact _____________ at

(___)___-____.• Sincerely,•

DTD Specification for Source Calendar Data

<!ATTLIST ses version NMTOKEN #REQUIRED ><!ELEMENT channel ( event+ ) ><!ELEMENT enddate ( #PCDATA ) ><!ELEMENT endtime ( #PCDATA ) ><!ELEMENT event ( subject, startdate, enddate, starttime, endtime, location, url, source ) ><!ELEMENT location ( #PCDATA ) ><!ELEMENT ses ( channel ) ><!ELEMENT source ( #PCDATA ) ><!ELEMENT startdate ( #PCDATA ) ><!ELEMENT starttime ( #PCDATA ) ><!ELEMENT subject ( #PCDATA ) ><!ELEMENT url ( #PCDATA ) >