| Task | Description |
| 017 | Common API: non-normative API extensions |
| 047 | Trouble Ticket API: non-normative API extensions |
| 050 | Billing Mediation API: Specifications and Project Management |
| 051 | Billing Mediation API: Java Profile: Reference Implementation coding |
| 052 | Billing Mediation API: Java Profile: TCK coding |
| 053 | Billing Mediation API: XML Profile: Reference Implementation coding |
| 054 | Billing Mediation API: XML Profile: TCK coding |
| 055 | Billing Mediation API: Web Services Profile: Reference Implementation coding |
| 056 | Billing Mediation API: Web Services Profile: TCK coding |
| 057 | Billing Mediation API: non-normative API extensions |
| 063 | Inventory API: XML Profile: Reference Implementation coding |
| 064 | Inventory API: XML Profile: TCK coding |
| 065 | Inventory API: Web Services Profile: Reference Implementation coding |
| 066 | Inventory API: Web Services Profile: TCK coding |
| 067 | Inventory API: non-normative API extensions |
| 077 | Service Quality Management API: non-normative API extensions |
| 087 | Pricing API: non-normative API extensions |
| 097 | Discovery API: non-normative API extensions |
| 107 | Fault Management API: non-normative API extensions |
| 117 | Order Management API: non-normative API extensions |
| 120 | Performance Management API: Specifications and Project Management |
| 121 | Performance Management API: Java Profile: Reference Implementation coding |
| 122 | Performance Management API: Java Profile: TCK coding |
| 123 | Performance Management API: XML Profile: Reference Implementation coding |
| 124 | Performance Management API: XML Profile: TCK coding |
| 125 | Performance Management API: Web Services Profile: Reference Implementation coding |
| 126 | Performance Management API: Web Services Profile: TCK coding |
| 127 | Performance Management API: non-normative API extensions |
| 131 | Tigerstripe: plugins for RI and TCK stubs generation |
| Task | Description |
| 200 | Deployment of an OSS/J API and public disclosure (Prosspero candidate) |
| 201 | Internal adoption project (a pilot project) for an OSS/J API and results published |
| 202 | Lab facilities for business demonstrator (not as part of a pilot project) |
| 203 | Public case study about actual implementation of an OSS/J API |
| 204 | Publication of actual financial data and ROI findings for any of the OSS/J adoption project options listed above |
| 205 | Public OSS/J presentation at a major conference |
| 206 | Active representation to standard bodies to increase OSS/J API adoption. This must be carried out demonstrably |
| 207 | Permanent technical support to OSS/J handling queries regarding the Service Provider own environment |
| 208 | Permanent business support to OSS/J handling queries regarding the OSS/J strategy and priorities |
| 209 | Extensions of an OSS/J API to cover specific SP environment needs |
| 210 | Contribution ot the implementation of an API |
| 211 | Technical documentation or presentation on alignment of SP Environment data model with OSS/J Data Model |
| 212 | Technical documentation or presentation on alignment of SP architecture with OSS/J APIs Architecture |
| 213 | Use of company offices for holding OSS/J conferences, seminars, etc. |
| 214 | Private OSS/J presentation at customer premises with support other OSS/J other members |