FEATURED

NASA Center of Excellence for Collaborative Innovation @TopCoder

TopCoder is honored to be a participating vendor of the NASA CoECI!  The CoECI was launched to enable acceleration of US Government implementation of new models of problem solving using collaborative innovation methodologies, such as crowd sourcing and open innovation, to meet agency requirements.  Led by NASA, the CoECI serves as a convening body which harnesses and redistributes the collective experience of all participating federal agencies regarding best practices in collaborative and distributed innovation.

 

Through the CoECI, we hope to bring exciting new challenges and projects in science, healthcare, technology, education and government service to our Community. We will announce new projects here our CoECI TopCoder Network page, so stay tuned!

 

For more information about the CoECI, visit http://www.nasa.gov/offices/COECI/index.html

 

 

LATEST NEWS

May
02

Two New CMS Contest Opportunities!

posted by on May 02, 2013 at 3:42 pm

The Centers for Medicare & Medicaid Services (CMS) have kicked-off two new projects! There will be two conceptualization contest opportunities launching between 5/2 and 5/5. Visit the links below to register for each contest:

Apr
15

CMS2 Project – Conceptualization Contest!

posted by on April 15, 2013 at 9:57 am

The Centers for Medicare & Medicaid Services (CMS) have kicked-off a new project to prevent healthcare fraud and the first contest is now live!  The goal of this project is help design a peer-to-peer data exchange network to support studies that seek to identify fraudulent claims. Visit here for more details about the project and to register for the Conceptualization contest.

 

Apr
01

$10,000 Robonaut Challenge!

posted by on April 01, 2013 at 2:26 pm

Attention all robotics and computer vision enthusiasts! Want a chance to work on the robot on the International Space Station? The $10,000 NASA Robonaut Challenge is your ticket!

Robonaut 2 is the first humanoid robot in space and was sent to the International Space Station (ISS) with the intention of taking over tasks too dangerous or too mundane for astronauts. There’s only one problem: Robonaut 2 needs to learn how to interact with the types of input devices the astronauts use on the ISS.

How do we fix that? To start, NASA has built several taskboards for Robonaut to play with.

The taskboards have a number of LEDs that turn on when the power switch is flipped or the buttons are pushed. See a video of R2 interacting with the taskboard.

In these challenges, competitors will write algorithms to control Robonaut and teach him how to interact with the taskboard.

Learn more here about the competition here and compete here.

Mar
06

The Tech Challenge for Atrocity Prevention is Underway!!

posted by on March 06, 2013 at 4:44 pm

Calling all TopCoder algorithmists and developers! We have an important challenge for you-join USAID and Humanity United and get involved in the Tech Challenge for Atrocity Prevention.

Learn more and register here.

Feb
10

Introducing the launch of the NASA ISS FIT (Food Intake Tracker) iPad App Challenge!

posted by on February 10, 2013 at 6:43 pm

Introducing the launch of the NASA ISS FIT (Food Intake Tracker) iPad App Challenge!

As part of this challenge, participants are tasked with formulating a leading edge solution to an intractable, age old problem: How can I keep track of what I’m eating? We all know that there are a dozen, if not hundreds of solutions out there that can help. But imagine you live on a 925,000 lb floating space platform that is orbiting the Earth at a height of 230 miles at a speed of nearly 17,500 MPH. And you’re busy. Very busy.

Astronauts, Cosmonauts, and Space Cadets (okay, we made the last one up), all face huge technical challenges, are performing scientific experiments on a daily basis, and are working hard to stay fit. One of the key aspects of this is working to understand how microgravity affects their bodies, and how to best keep them healthy. And as part of both space medicine and science, we need to understand what they’ve eaten, and how much they’ve eaten.

Sounds simple, right? Not really.

So here’s the challenge: we need to design, develop and produce an iPad application that will allow ISS crewmembers to easily track foods. The iPad application should seamlessly identify the user, track all dietary intake (food and beverages), and provide a timestamp of when the food was consumed.

To find out more about the challenge, click here, or, click the following links to sign up for our two first contests which launch on Sunday (02/10/13)

Feb
08

Announcing the winners of the ISS Longeron Challenge!

posted by on February 08, 2013 at 3:35 pm

We are excited to congratulate the following members who placed in the top 10:

1st place:  carlop – $10,000
2nd place:  zlfengyi1 - $5,000
3rd place:  nhzp339  - $3,000
4th place:  Psyho - $1,750
5th place:  zaq1xsw2tktk - $1,500
6th place:  chianti - $1,250
7th place:  chyx111 - $1,000
8th place:  ejdeon  - $750
9th place:  b285714  - $500
10th place:  Karalabe - $250

To check out the full results, visit here.

Also, please visit http://www.topcoder.com/iss/ to learn more about the next Marathon Match Challenge: ISS-FIT (Food Intake Tracker) that will be launching Sunday, February 10, 2013.

Thank you to all who participated. We had a great turnout and look forward to seeing you all compete in the next Marathon Match!

Congratulations again!

Nov
27

CMS Status Report for week ending Nov 23, 2012

posted by on November 27, 2012 at 11:46 pm
Hi All: Highlights from this week include the urgent items:
  • UI Prototype review
  • Review Organizational Provider Screening External Datasources (Architecture)
  • Review Provider Enrollment Drools: Front-End Evaluation (3,4 & %) (Architecture)
  • Review System Admin Controllers (Assembly)
  • Define and refine mainframe connectivity integration requirements (ERD and functionality list to be provided by Topcoder), including a list of ENROLEE maintenance tasks
  • Define and refine MNITS requirements (including filenet details)
  • Monitor forums and continue discussion on open issues
Full report details can be found below:

                                                     Project Status Report

Project Name: Prepared by: Period Ending:
Medicaid Provider Screening Portal Sarah Ramkissoon/Andy LaMora 23-Nov-12

Executive Summary

Item Comments
Overall
  • Projecting a Q4 Implementation though there are significant risks
Scope/Quality
  • On track
Schedule
  • Risk due to closeness of year-end and the number of contests still in progress
Budget/Resources
  • Project budget to be watched closely
Contest Management
  • On track – approximately  contests remaining in Oct – Dec

upcoming Milestones/Deliverables Summary

Project Milestones/Deliverables

Estimated End

Revised  End

Status

Reference
Complete Architecture

December

Risk

 
Complete All workflows

December

Risk
Prototype

November

Stable


pcoming Activities

Work Required  - Sponsor (Nov 24- Dec 6)
URGENT:

  • UI Prototype review
  • Review Organizational Provider Screening External Datasources (Architecture)
  • Review Provider Enrollment Drools: Front-End Evaluation (3,4 & %) (Architecture)
  • Review System Admin Controllers (Assembly)
  • Define and refine mainframe connectivity integration requirements (ERD and functionality list to be provided by Topcoder), including a list of ENROLEE maintenance tasks
  • Define and refine MNITS requirements (including filenet details)
  • Monitor forums and continue discussion on open issues
Work Required – Topcoder(Nov 24- Dec 6)
URGENT:

  • Launch  and monitor contests in progress

Other/Upcoming:

  • Create overall site design summary walk-through
  • Contest to verify charter against specification document to ensure no missed requirements
  • Work with client to resolve outstanding questions and issues.

 ISSUES and RISKs Summary


Ref #

 Description

Reported Date

Action By Date

Status

r7

 Risk: Requirements on key areas still outstanding: Mainframe connectivity requirements and MNITS.  Confirmation on Netstudy, DMF and PECOS files are also outstanding and may impact the project scope and schedule

11-01-12

11-15-12

Open

r6

 Risk: To satisfy PT33-NPI requirements there will likely be need to integrate with legacy systems/processes as well as perform manual processes outside of the system (e.g. sending letter cancellation requests, consolidation request fulfillment, etc)Action:  Topcoder to review and ensure nuances and requirements integrated – risk to the timeline due to complexity

10-25-12

11-15-12

Open

r5

 Risk:IBM License test requires time to conduct test and review results. If the results are not as expected, a new/alternate strategy/discussions may be requiredAction: Expedite testing by using an IBM copilot to set up smart clouds, enabling POC testing on the IBM stack.

Update: Issue is still unresolved – alternate strategies will be explored in addition to pursuing smart cloud set-up

09-20-12

10-21-12

Open

r1

 Risk: A significant number of new provider organizations have been provided by client in mid-late September timeframe.  As a result the time to complete the UI wireframes that included these new organizational types has increased.Action:  Run required organizational wireframes contests aggressively, including in parallel where possible, or with very short periods between contests where parallel is not possible.

09-20-12

10-21-12

Open

i7

 Issue:    Budget is projected to go over 500K due to the necessity of having more assembly contests than was originally projected, as requirements complexity increased recently (e.g. PT33-NPI requirements, dis-enrollment, etc) and known functionality (e.g. Mainframe connectivity requirement, IBM Stack port, etc) has proven to be more complex, and more expensive to build and test.Update: Budget reviewed and will be in-line with expectations

 

i6

 Risk: Missed or new requirement to ensure dis-enrollment functionality is present will impact administrative workflow timelines.Action:  Topcoder will expedite inclusion of the missed functionality as best possible (consider use of bug race or other methodology to expedite inclusion)

10-25-12

11-15-12

Closed

i5

 Issue: Client is experiencing difficulty downloading UI submissions, in particular wireframes due to their size.Action:  Topcoder will propose a new methodology to facilitate wireframe viewing

10-18-12

10-18-12

Closed

i3

 Issue: Client is concerned that feedback to UI wireframes are not being reflected and client is having trouble tracking which wireframes reflect feedback given by Angie.Action:  Topcoder is running short bug races to make wireframe changes and Dan shown how to follow bug races in Cockpit.  Topcoder’s James will update the demo box twice weekly with wireframe updates (on a scheduled basis where possible)

09-26-12

10-21-12

Closed

i4

 Issue: Death master file access: will not be available. For development purposes, it will be assumed that a file will be uploaded weekly or monthly and a webservice utilized to process the file.  A simple screen interface will be created to facilitate the upload.

10-11-12

10-15-12

CLosed

r3

 Risk: Topcoder is currently experiencing technical difficulties with the software that allows for downloading of judging bundle packages. Action:Topcoder staff are working on getting the issue resovled with highest priority.Update: Judging bundles are now available for download

09-20-12

10-03-12

Closed

i2

 Issue:  Strategy to address licensing for IBM assets requiredAction:  Feedback on the elements to port provided by client.  Creation on contest to port elements to IBM stack in progress 07-26-12

08-31-12

Closed

r2

 Issue:  Developers require API access to 3rdsites to check for licensing and other authorization information Update (Aug 16, 2012):  MN DHS and CMS (state and federal health agencies respectively) are looking into getting API access.

Alternate:  Create  well-formatted private web pages that allows for screen-scraping, and query with querystring tokens, post, etc

  

 

 

07-26-12

08-23-12

Closed

i1

 Issue:  Strategy required on IBM stack vs. generic stackResolution: Build two POCs ( “hello world” applications) and implement open source stack version.  Client will then prioritize elements to port to the IBM stack

07-12-12

07-31-12

  Closed

Project budget update  

Ref #

 Description

Comments

1

 Approximate contest cost to date: $550,000

Tracking Budget status closely to ensure in-line with expectations

 

Nov
27

CMS Status Report for week ending Nov 16, 2012

posted by on November 27, 2012 at 11:43 pm
Hi All: Highlights from this week include the urgent items:
  • UI Prototype review
  • Review Organizational Provider Screening External Datasources (Architecture)
  • Review Provider Enrollment Drools: Front-End Evaluation (3,4 & %) (Architecture)
  • Review System Admin Controllers (Assembly)
  • Define and refine mainframe connectivity integration requirements (ERD and functionality list to be provided by Topcoder), including a list of ENROLEE maintenance tasks
  • Define and refine MNITS requirements (including filenet details)
  • Monitor forums and continue discussion on open issues
Full report details can be found below:

                                                     Project Status Report

Project Name: Prepared by: Period Ending:
Medicaid Provider Screening Portal Sarah Ramkissoon/Andy LaMora 16-Nov-12

Executive Summary

Item Comments
Overall
  • Projecting a Q4 Implementation though there are significant risks
Scope/Quality
  • Missed scope (smaller items) adding pressure to timeline. On track  otherwise (r7)
Schedule
  • Risks emerging – see details in Risks and Issues section (r7)
Budget/Resources
  • Project budget to be watched closely (i7)
Contest Management
  • On track – approximately  contests remaining in Oct – Dec

upcoming Milestones/Deliverables Summary

Project Milestones/Deliverables

Estimated End

Revised  End

Status

Reference
Complete Workflow for All Providers

November

Risk

r1, i2,r6,i6, r7
Administrative Workflow

Early November

Risk

r1,i2,r6,i6
UI wireframes (all)

Early November

Risk

r1
Prototype

November

Stable

r1


pcoming Activities

Work Required  - Sponsor (Nov 17-30)
URGENT:

  • UI Prototype review
  • Review Organizational Provider Screening External Datasources (Architecture)
  • Review Provider Enrollment Drools: Front-End Evaluation (3,4 & %) (Architecture)
  • Review System Admin Controllers (Assembly)
  • Define and refine mainframe connectivity integration requirements (ERD and functionality list to be provided by Topcoder), including a list of ENROLEE maintenance tasks
  • Define and refine MNITS requirements (including filenet details)
  • Monitor forums and continue discussion on open issues
Work Required – Topcoder (Nov 17-30)
URGENT:

  • Launch  and monitor contests in progress

Other/Upcoming:

  • Create overall site design summary walk-through
  • Contest to verify charter against specification document to ensure no missed requirements
  • Work with client to resolve outstanding questions and issues.

 ISSUES and RISKs Summary


Ref #

 Description

Reported Date

Action By Date

Status

i7

 Issue:    Budget is projected to go over 500K due to the necessity of having more assembly contests than was originally projected, as requirements complexity increased recently (e.g. PT33-NPI requirements, dis-enrollment, etc) and known functionality (e.g. Mainframe connectivity requirement, IBM Stack port, etc) has proven to be more complex, and more expensive to build and test.Update:Contingency budget amount will be used.  Will continue to monitor budget closely to be in-line with expectations 

10-25-12

11-15-12

Open

r7

 Risk: Requirements on key areas still outstanding: Mainframe connectivity requirements and MNITS.  Confirmation on Netstudy, DMF and PECOS files are also outstanding and may impact the project scope and schedule

11-01-12

11-15-12

Open

r6

 Risk: To satisfy PT33-NPI requirements there will likely be need to integrate with legacy systems/processes as well as perform manual processes outside of the system (e.g. sending letter cancellation requests, consolidation request fulfillment, etc)Action:  Topcoder to review and ensure nuances and requirements integrated – risk to the timeline due to complexity

10-25-12

11-15-12

Open

r5

 Risk:IBM License test requires time to conduct test and review results. If the results are not as expected, a new/alternate strategy/discussions may be requiredAction:Expedite testing by using an IBM copilot to set up smart clouds, enabling POC testing on the IBM stack.Update: Issue is still unresolved – alternate strategies will be explored in addition to pursuing smart cloud set-up

09-20-12

10-21-12

Open

r1

 Risk: A significant number of new provider organizations have been provided by client in mid-late September timeframe.  As a result the time to complete the UI wireframes that included these new organizational types has increased.Action:  Run required organizational wireframes contests aggressively, including in parallel where possible, or with very short periods between contests where parallel is not possible.

09-20-12

10-21-12

Open

i6

 Risk: Missed or new requirement to ensure dis-enrollment functionality is present will impact administrative workflow timelines.Action:  Topcoder will expedite inclusion of the missed functionality as best possible (consider use of bug race or other methodology to expedite inclusion)

10-25-12

11-15-12

Closed

i5

 Issue: Client is experiencing difficulty downloading UI submissions, in particular wireframes due to their size.Action:  Topcoder will propose a new methodology to facilitate wireframe viewing

10-18-12

10-18-12

Closed

i3

 Issue: Client is concerned that feedback to UI wireframes are not being reflected and client is having trouble tracking which wireframes reflect feedback given by Angie.Action:  Topcoder is running short bug races to make wireframe changes and Dan shown how to follow bug races in Cockpit.  Topcoder’s James will update the demo box twice weekly with wireframe updates (on a scheduled basis where possible)

09-26-12

10-21-12

Closed

i4

 Issue: Death master file access: will not be available. For development purposes, it will be assumed that a file will be uploaded weekly or monthly and a webservice utilized to process the file.  A simple screen interface will be created to facilitate the upload.

10-11-12

10-15-12

CLosed

r3

 Risk: Topcoder is currently experiencing technical difficulties with the software that allows for downloading of judging bundle packages. Action:Topcoder staff are working on getting the issue resovled with highest priority.Update: Judging bundles are now available for download

09-20-12

10-03-12

Closed

i2

 Issue:  Strategy to address licensing for IBM assets requiredAction:  Feedback on the elements to port provided by client.  Creation on contest to port elements to IBM stack in progress 07-26-12

08-31-12

Closed

r2

 Issue:  Developers require API access to 3rdsites to check for licensing and other authorization information Update (Aug 16, 2012):  MN DHS and CMS (state and federal health agencies respectively) are looking into getting API access.Alternate:  Create  well-formatted private web pages that allows for screen-scraping, and query with querystring tokens, post, etc  

 

07-26-12

08-23-12

Closed

i1

 Issue:  Strategy required on IBM stack vs. generic stackResolution: Build two POCs ( “hello world” applications) and implement open source stack version.  Client will then prioritize elements to port to the IBM stack

07-12-12

07-31-12

  Closed

Project budget update  

Ref #

 Description

Comments

1

 Projected outstanding contests cost: $90,000

n/a

2

 Approximate contest cost to date: $490,000

Tracking Budget status closely to ensure in-line with expectations

 

Nov
27

CMS Status Report for week ending Nov 9, 2012

posted by on November 27, 2012 at 11:38 pm
Hi All: Highlights from this week include the urgent items:
  • Define and refine mainframe connectivity integration requirements (ERD and functionality list to be provided by Topcoder), including a list of ENROLEE maintenance tasks
  • Define and refine MNITS requirements (including filenet details)

Full report details can be found below:

Project Status Report

Project Name: Prepared by: Period Ending:
Medicaid Provider Screening Portal Sarah Ramkissoon/Andy LaMora 09-Nov-12

Executive Summary

Item Comments
Overall
  • Projecting a Q4 Implementation though there are significant risks
Scope/Quality
  • Missed scope (smaller items) adding pressure to timeline. On track  otherwise (r7)
Schedule
  • Risks emerging – see details in Risks and Issues section (r7)
Budget/Resources
  • Project budget to be watched closely (i7)
Contest Management
  • On track – approximately  contests remaining in Oct – Dec

upcoming Milestones/Deliverables Summary

Project Milestones/Deliverables

Estimated End

Revised  End

Status

Reference
Complete Workflow for All Providers

November

Risk

r1, i2,r6,i6, r7
Administrative Workflow

Early November

Risk

r1,i2,r6,i6
UI wireframes (all)

Early November

Risk

r1
Prototype

November

Stable

r1


pcoming Activities

Work Required  - Sponsor (Nov 10-17)
URGENT:

  • Define and refine mainframe connectivity integration requirements (ERD and functionality list to be provided by Topcoder), including a list of ENROLEE maintenance tasks
  • Define and refine MNITS requirements (including filenet details)
  • Confirm the provider will know the LISStudyID (WDSL requirement) as per Netstudy requirements
  • Clarify DMF and PECOS files requirements (confirmation of whether UI required)

Other/Upcoming:

  • Requires client time, input and assistance to:
    • Screening rules and front-end validation (drools contests) for individual providers
    • External sources assemblies for organizational providers
    • UI prototype and wireframes
  • Monitor forums and continue discussion on open issues
Work Required – Topcoder (Nov 10-17)
URGENT:

  • Update ERD and functionality list for organizational type
  • Update miscellaneous PEPS requirements in original concepts documentation
  • Launch Miscellaneous services and Provider enrollment contests
  • Review Netstudy requirements and get confirmation whether UI required for DMF and PECOS

Other/Upcoming:

  • Create overall site design summary walk-through
  • Contest to verify charter against specification document to ensure no missed requirements
  • Work with client to resolve outstanding questions and issues.

 ISSUES and RISKs Summary


Ref #

 Description

Reported Date

Action By Date

Status

i7

 Issue:    Budget is projected to go over 500K due to the necessity of having more assembly contests than was originally projected, as requirements complexity increased recently (e.g. PT33-NPI requirements, dis-enrollment, etc) and known functionality (e.g. Mainframe connectivity requirement, IBM Stack port, etc) has proven to be more complex, and more expensive to build and test. 

10-25-12

11-15-12

Open

r7

 Risk: Requirements on key areas still outstanding: Mainframe connectivity requirements and MNITS.  Confirmation on Netstudy, DMF and PECOS files are also outstanding and may impact the project scope and schedule

11-01-12

11-15-12

Open

r6

 Risk: To satisfy PT33-NPI requirements there will likely be need to integrate with legacy systems/processes as well as perform manual processes outside of the system (e.g. sending letter cancellation requests, consolidation request fulfillment, etc)Action:  Topcoder to review and ensure nuances and requirements integrated – risk to the timeline due to complexity

10-25-12

11-15-12

Open

r5

 Risk:IBM License test requires time to conduct test and review results. If the results are not as expected, a new/alternate strategy/discussions may be requiredAction:Expedite testing by using an IBM copilot to set up smart clouds, enabling POC testing on the IBM stack.Update: Issue is still unresolved – alternate strategies will be explored in addition to pursuing smart cloud set-up

09-20-12

10-21-12

Open

r1

 Risk: A significant number of new provider organizations have been provided by client in mid-late September timeframe.  As a result the time to complete the UI wireframes that included these new organizational types has increased.Action:  Run required organizational wireframes contests aggressively, including in parallel where possible, or with very short periods between contests where parallel is not possible.

09-20-12

10-21-12

Open

i6

 Risk: Missed or new requirement to ensure dis-enrollment functionality is present will impact administrative workflow timelines.Action:  Topcoder will expedite inclusion of the missed functionality as best possible (consider use of bug race or other methodology to expedite inclusion)

10-25-12

11-15-12

Closed

i5

 Issue: Client is experiencing difficulty downloading UI submissions, in particular wireframes due to their size.Action:  Topcoder will propose a new methodology to facilitate wireframe viewing

10-18-12

10-18-12

Closed

i3

 Issue: Client is concerned that feedback to UI wireframes are not being reflected and client is having trouble tracking which wireframes reflect feedback given by Angie.Action:  Topcoder is running short bug races to make wireframe changes and Dan shown how to follow bug races in Cockpit.  Topcoder’s James will update the demo box twice weekly with wireframe updates (on a scheduled basis where possible)

09-26-12

10-21-12

Closed

i4

 Issue: Death master file access: will not be available. For development purposes, it will be assumed that a file will be uploaded weekly or monthly and a webservice utilized to process the file.  A simple screen interface will be created to facilitate the upload.

10-11-12

10-15-12

CLosed

r3

 Risk: Topcoder is currently experiencing technical difficulties with the software that allows for downloading of judging bundle packages. Action:Topcoder staff are working on getting the issue resovled with highest priority.Update: Judging bundles are now available for download

09-20-12

10-03-12

Closed

i2

 Issue:  Strategy to address licensing for IBM assets requiredAction:  Feedback on the elements to port provided by client.  Creation on contest to port elements to IBM stack in progress 07-26-12

08-31-12

Closed

r2

 Issue:  Developers require API access to 3rdsites to check for licensing and other authorization information Update (Aug 16, 2012):  MN DHS and CMS (state and federal health agencies respectively) are looking into getting API access.Alternate:  Create  well-formatted private web pages that allows for screen-scraping, and query with querystring tokens, post, etc  

 

07-26-12

08-23-12

Closed

i1

 Issue:  Strategy required on IBM stack vs. generic stackResolution: Build two POCs ( “hello world” applications) and implement open source stack version.  Client will then prioritize elements to port to the IBM stack

07-12-12

07-31-12

  Closed

Project budget update  

Ref #

 Description

Comments

1

 Projected outstanding contests cost: $90,000

n/a

2

 Approximate contest cost to date: $490,000

Tracking Budget status closely to ensure in-line with expectations

 

Nov
27

CMS Status Report for week ending Nov 2, 2012

posted by on November 27, 2012 at 11:34 pm

Hi All: Highlights from this week include the urgent items:

  • Define and refine mainframe connectivity integration requirements (ERD and functionality list to be provided by Topcoder), including a list of ENROLEE maintenance tasks
  • Define and refine MNITS requirements (including filenet details)
  • Confirm the provider will know the LISStudyID (WDSL requirement) as per Netstudy requirements
  • Clarify DMF and PECOS files requirements (confirmation of whether UI required)

Full reports details can be found below:

Project Status Report

Project Name: Prepared by: Period Ending:
Medicaid Provider Screening Portal Sarah Ramkissoon/Andy LaMora 02-Nov-12

Executive Summary

Item Comments
Overall
  • Projecting a Q4 Implementation though there are significant risks
Scope/Quality
  • Missed scope (smaller items) adding pressure to timeline. On track  otherwise (r7)
Schedule
  • Risks emerging – see details in Risks and Issues section (r7)
Budget/Resources
  • On track – see details in budget section
Contest Management
  • On track – approximately  contests remaining in Oct – Dec

upcoming Milestones/Deliverables Summary

Project Milestones/Deliverables

Estimated End

Revised  End

Status

Reference
Complete Workflow for All Providers

Late-Oct

November

Risk

r1, i2,r6,i6, r7
Administrative Workflow

Late-Oct

Early November

Risk

r1,i2,r6,i6
UI wireframes (all)

Late-Oct

Early November

Risk

r1
Prototype

November

Stable

r1


pcoming Activities

Work Required  - Sponsor (Nov 3-10)
URGENT:

  • Define and refine mainframe connectivity integration requirements (ERD and functionality list to be provided by Topcoder), including a list of ENROLEE maintenance tasks
  • Define and refine MNITS requirements (including filenet details)
  • Confirm the provider will know the LISStudyID (WDSL requirement) as per Netstudy requirements
  • Clarify DMF and PECOS files requirements (confirmation of whether UI required)

Other/Upcoming:

  • Requires client time, input and assistance to:
    • Screening rules and front-end validation (drools contests) for individual providers
    • External sources assemblies for organizational providers
    • UI prototype and wireframes
  • Monitor forums and continue discussion on open issues
Work Required – Topcoder (Nov 1 – 10)
URGENT:

  • Update ERD and functionality list for organizational type
  • Update miscellaneous PEPS requirements in original concepts documentation
  • Launch Miscellaneous services and Provider enrollment contests
  • Review Netstudy requirements and get confirmation whether UI required for DMF and PECOS

Other/Upcoming:

  • Create overall site design summary walk-through
  • Contest to verify charter against specification document to ensure no missed requirements
  • Work with client to resolve outstanding questions and issues.

 ISSUES and RISKs Summary


Ref #

 Description

Reported Date

Action By Date

Status

r7

 Risk: Requirements on key areas still outstanding: Mainframe connectivity requirements and MNITS.  Confirmation on Netstudy, DMF and PECOS files are also outstanding and may impact the project scope and schedule

11-01-12

11-15-12

Open

i6

 Risk: Missed or new requirement to ensure dis-enrollment functionality is present will impact administrative workflow timelines.Action:  Topcoder will expedite inclusion of the missed functionality as best possible (consider use of bug race or other methodology to expedite inclusion)

10-25-12

11-15-12

Open

r6

 Risk: To satisfy PT33-NPI requirements there will likely be need to integrate with legacy systems/processes as well as perform manual processes outside of the system (e.g. sending letter cancellation requests, consolidation request fulfillment, etc)Action:  Topcoder to review and ensure nuances and requirements integrated – risk to the timeline due to complexity

10-25-12

11-15-12

Open

r5

 Risk:IBM License test requires time to conduct test and review results. If the results are not as expected, a new/alternate strategy/discussions may be requiredAction:Expedite testing by using an IBM copilot to set up smart clouds, enabling POC testing on the IBM stack.Update: Issue is still unresolved – alternate strategies will be explored in addition to pursuing smart cloud set-up

09-20-12

10-21-12

Open

r1

 Risk: A significant number of new provider organizations have been provided by client in mid-late September timeframe.  As a result the time to complete the UI wireframes that included these new organizational types has increased.Action:  Run required organizational wireframes contests aggressively, including in parallel where possible, or with very short periods between contests where parallel is not possible.

09-20-12

10-21-12

Open

i5

 Issue: Client is experiencing difficulty downloading UI submissions, in particular wireframes due to their size.Action:  Topcoder will propose a new methodology to facilitate wireframe viewing

10-18-12

10-18-12

Open

i3

 Issue: Client is concerned that feedback to UI wireframes are not being reflected and client is having trouble tracking which wireframes reflect feedback given by Angie.Action:  Topcoder is running short bug races to make wireframe changes and Dan shown how to follow bug races in Cockpit.  Topcoder’s James will update the demo box twice weekly with wireframe updates (on a scheduled basis where possible)

09-26-12

10-21-12

Open

i4

 Issue: Death master file access: will not be available. For development purposes, it will be assumed that a file will be uploaded weekly or monthly and a webservice utilized to process the file.  A simple screen interface will be created to facilitate the upload.

10-11-12

10-15-12

CLosed

r3

 Risk: Topcoder is currently experiencing technical difficulties with the software that allows for downloading of judging bundle packages. Action:Topcoder staff are working on getting the issue resovled with highest priority.Update: Judging bundles are now available for download

09-20-12

10-03-12

Closed

i2

 Issue:  Strategy to address licensing for IBM assets requiredAction:  Feedback on the elements to port provided by client.  Creation on contest to port elements to IBM stack in progress 07-26-12

08-31-12

Closed

r2

 Issue:  Developers require API access to 3rdsites to check for licensing and other authorization information Update (Aug 16, 2012):  MN DHS and CMS (state and federal health agencies respectively) are looking into getting API access.Alternate:  Create  well-formatted private web pages that allows for screen-scraping, and query with querystring tokens, post, etc  

 

07-26-12

08-23-12

Closed

i1

 Issue:  Strategy required on IBM stack vs. generic stackResolution: Build two POCs ( “hello world” applications) and implement open source stack version.  Client will then prioritize elements to port to the IBM stack

07-12-12

07-31-12

  Closed

Project budget update  

Ref #

 Description

Comments

1

 Projected outstanding contests cost: $90,000

n/a

2

 Approximate contest cost to date: $387,000

Budget on Track as Expected

 

Older Entries