Embed Size (px)
Citation preview
www.Broadband Infraco.co.za
Registration Number: 1989/001763/07
Woodmead Country Club Estate, Building No.9, No.1 Woodlands Drive, Woodmead Extension 34, South Africa
Postnet Suite 321, Private Bag X26, Sunninghill, 2157
BROADBAND INFRACO (SOC) LTD Date : 28 March 2018
Enquiries: Lwandle Mgidlana Tel : 011 235-1851
E-Mail : [email protected]
Dear Sir/Madam, REQUEST FOR PROPOSALS: INF/TEN/0222 CLOSING DATE: 03 MAY 2018 AT 12h00 PM (SOUTH AFRICAN TIME). INVITATION TO SUBMIT PROPOSAL: APPOINTMENT OF A SERVICE PROVIDER WHO WILL SUPPLY, INSTALL, TEST, CONFIGURE, AND INTERGRATE THE OPERATIONAL SUPPORT SYSTEM (OSS) & BUSINESS SUPPORT SYSTEMS (BSS) NETWORK ELEMENT/SYSTEM AT BROADBAND INFRACO.
Please take note that this is a confidential request and you are requested to treat all information, including this Request for Proposals as confidential and you must not discuss or divulge this information to any 3rd party without our written permission.
1. BACKGROUND ON BROADBAND INFRACO
Broadband Infraco legislative mandate is set out in the Broadband Infraco Act No. 33 of 2007 (the “Act”). The main objectives as set out in the Act are to expand the availability and affordability of access to electronic communications, including but not limited to underdeveloped and under serviced areas, in accordance with the Electronic Communications Act and commensurate with international best practice and pricing, through the provision of electronic communications network services and electronic communications services.
In addition, Broadband Infraco must comply with the Public Finance Management Act of 1999 as amended (the “PFMA”), National Treasury Regulations issued in terms of the Public Finance Management Act, and the Companies Act No. 71 of 2008 and other laws that govern the financial affairs, the stability and soundness of the financial system and manage the budget preparation process; and enforce transparency and effective management in respect of revenue and expenditure, assets and liabilities, of the Company.
2. OBJECTIVE
The objective of this Request for Proposal (RFP) is to appointment of a service provider who will supply, install, test, configure and integrate the Operational Support System (OSS) & Business Support Systems (BSS) network element/system at Broadband Infraco. Once Broadband Infraco has received and evaluated the responses, an award is expected to be made to one service provider. This process is dependent on the decisions made by the company’s adjudicating committee.
2
3. LODGING OF TENDER AND CLOSING DATE
Your response in a sealed cover and endorsed;
CONFIDENTIAL INVITATION TO SUBMIT A PROPOSAL: APPOINTMENT OF A SERVICE PROVIDER WHO WILL SUPPLY, INSTALL, TEST, CONFIGURE AND INTERGRATE THE OPERATIONAL SUPPORT SYSTEM (OSS) & BUSINESS SUPPORT SYSTEMS (BSS) NETWORK ELEMENT/SYSTEM AT BROADBAND INFRACO. NAME OF BIDDER ON THE COVER. REQUEST FOR PROPOSALS: INF/TEN/0222 ATTENTION: Lwandle Mgidlana
must be delivered to Broadband Infraco at Country Club Estate, Building 9, 21 Woodlands Drive, Woodmead, Sandton before 12h00 PM (RSA Time) on 03 May 2018.
One (1) original AND a copy of the original on a CD or USB. NB* All information in the hard copy proposal must be saved in the CD and USB.
Incomplete information will be rejected and Broadband Infraco will NOT accept late
responses.
3.1 Broadband Infraco’s Representative’s details for this RFP is:
Name : Lwandle Mgidlana Address : Woodmead Country Club Estate, Building 9,
21 Woodlands Drive, Woodmead, Sandton Tel No. : + 27 11 235 1851 Fax No. : 0867435344 E-Mail : [email protected]
3.2 Please take note that all questions or queries on this RFP must be communicated in
writing to Infraco’s Representative at the above-stated electronic mail address.
In terms of Broadband Infraco’s Corporate Policy, all questions and queries received will be answered in writing. In the interests of fairness, the question together with Broadband Infraco’s clarification and/or response thereto will only be made available to those bidders who have submitted a Receipt of Invitation Form indicating an intention to tender. The name of the bidder who requested clarification and/or posed a question will not be reflected in the clarification and/or response.
3.3 The tender documents are:
3.3.1 This RFP and the documents attached to this RFP as set out in the Document List and, 3.3.2 Such addenda, responses to bidders’ queries and clarifications as may be issued by Broadband
Infraco from time to time. 3.4 The provisions of this RFP and Infraco's Standard Conditions of Tender (Annexure B) are
taken to be mutually explanatory of one another but in the event of ambiguity, discrepancy, divergence, inconsistency or omission from or in or between this RFP and Broadband Infraco's Standard Conditions of Tender, the provisions of this RFP shall take precedence over the provisions of Broadband Infraco's Standard Conditions of Tender.
3.5 A bidder is a Person, Original, Partnership, Agent, Joint Venture, Firm or Company eligible to submit a tender in response to this RFP.
3
3.6 Broadband Infraco deems that a submission of a proposal by a bidder in response to this RFP constitutes the bidders acceptance of the Standard Conditions of Tender and the additional terms contained in this RFP.
3.7 Broadband Infraco’s reservations of rights in respect of the tender 3.7.1 Bidders’ attention is specifically drawn to the fact that a contract in respect of the Employer’s
Requirements will not necessarily result from the tender responses Broadband Infraco receives in response to this RFP. Broadband Infraco reserves the right to conduct a further procurement process with or without a request for tender or to enter into negotiations with any one or more of the bidders, should it decide to proceed with contract award.
3.7.2 Broadband Infraco reserves the right to subject bidders and their facilities to assessment as
part of the evaluation process or as a condition of the contract award. 3.7.3 Broadband Infraco reserves the right not to evaluate and/or consider any proposal by a bidder
that do not comply strictly with the requirements as set out in this RFP and/or who do not meet one or more of the prerequisite tender requirements set out in the Technical Specification (Annexure F).
3.7.4 Broadband Infraco reserves the right to make a decision on the contract award based solely on
the information received in the responses to this RFP. Broadband Infraco also reserves the right to use relevant information not contained in any tender but which is within the knowledge of any employee or Board member of Broadband Infraco or its advisors, agents or representatives for the purposes of making its decision.
3.8 Disclaimer of liability for representations, warranties or statements
Broadband Infraco believes all information contained in this RFP (and all its schedules and annexes) and all guidelines or in any other written material furnished or information orally transmitted to a potential bidder (including, but not limited to any opinion, information or advice that may be provided to a potential bidder by or on behalf of Broadband Infraco) to be correct but Broadband Infraco does not (save to the extent otherwise expressly provided for in a future written agreement with a successful bidder) make any representations or warranties, express or implied as to the accuracy or completeness of such information and expressly disclaims any and all liability for such representations, warranties or statements.
3.9 Black Economic Empowerment
Broadband Infraco requires all interested parties to provide their valid Broad Based Black Economic Empowerment status from a verified agencies, sworn affidavits from QSEs and EMEs to be eligible to claim BBBEE points.
The Employer is committed to Broad Based Black Economic Empowerment principles and as such complies to the BEE Codes of Good Practice published by the Department of Trade Industry (DTI). The bidder is expected to be evaluated on these principles and must present a valid BBBEE status certificate and BBBEE Scorecard based on the DTI Interpretative Guide to the Codes of Good Practice (http://www.thedti.gov.za/bee/InterpretiveGuide28june07doc.pdf)
4. KEY TENDER DATES
The following key tender dates are applicable to this tender:
Activity Key Tender Dates
RFP Advert Date 28 March 2018
Compulsory briefing session 10 April 2018 AT 12 PM
Briefing session details Woodmead Country Club Estate, Building 9, Woodlands Drive, Woodmead, Sandton
Closing Date for queries pertaining to this RFP
21 April 2018 @ 15h00
RFP closing date 03 May 2018 @ 12h00 Noon
4
Any questions which may arise with regard to the interpretation of the RFP, or additional information required to clarify the RFP are to be submitted to: Att : Lwandle Mgidlana Broadband Infraco (SOC) Ltd Telephone no. : +27 11 235 1851 Facsimile no. : 0867435344 Email: : [email protected]
The bidder is requested to refer to the clause and sub-clause number(s) to which its questions relate.
4.1 The validity period of the tender is one hundred and twenty (120) days from the tender closing date with the possibility of extension should it be necessary to allow the evaluation process.
5. BIDDERS OBLIGATIONS
5.1 Number of copies required.
A hard copy of each tender must be submitted as an original along with one electronic copy of the complete tender on CD or USB all in PDF format.
5.2 Required information for evaluation.
Make available all information in the response indicating compliance and/or non-compliance of each item required by the bid.
Acknowledging that non-submission of information required to evaluate of administrative and functionality will disqualify or prejudice the bidder in claiming and getting points where points are allocated.
5.3 Compliance and deviations
Indicate clearly which item of the bid is not quoted for or any deviations to the scope and specification of this bid.
6. CONDITIONS OF CONTRACT
Broadband Infraco will only accept proposals from interested parties that are prepared to accept and comply with the contract conditions as per the New Engineering Contracts (NEC) – NEC3 Professional Service Contract – PSC3), as published by Thomas Telford Publishing on behalf of the Institution of Civil Engineers, United Kingdom. Copies available from Thomas Telford Ltd, 1 Heron Quay, London. (ISBN 0 7277 2634 X).
In South Africa, the published NEC can be purchased from Thomas Telford Publications, telephone number (011) 803 3008, and fax number (011) 803 3009. The General Services Contract will be accompanied by the Service Level Agreement provided and signed for by both parties.
7. SPECIFICATION See attached Annexure F
5
8. EVALUATION CRITERIA
The tender will be evaluated by taking into account information requested in this RFP. Please refer to Annexure F for specifications and the evaluation criteria.
8.1 Mandatory administrative and technical requirements
Mandatory administrative and technical requirements (gatekeepers) of the bid (see Annexure C, D and F for detailed mandatory administrative and technical requirements of this bid).
8.2 Black Economic Empowerment
BBBEE is a deliberate socio-economic process or intervention strategy designed to redress the imbalances of the past and to facilitate the participation of Black people in the economy. Broadband Infraco shall apply the provisions of the Broad Based Black Economic Empowerment Act and its codes of good practice as verification of the bidders’ BEE status.
8.3 Insurance
Provide details of local as well as international professional indemnity insurance (if applicable).
8.4 Joint Ventures/Distributors/Agents
Stipulate if applicable and ensure that all companies submit their required documentation including a valid consolidated B-BBEE certificate.
9. COMPANY INFORMATION REQUIRED
9.1 General Data
Registered Company Name
Postal Address
Contact Person
Position in the Company
Telephone number
E-Mail address
9.2 SARS Certificate (for South African registered companies only)
Bidder is required to submit copy of Tax Clearance Certificate and verification PIN (Third party authorization) to be used by Broadband Infraco to validate the copy on the SARS website. Failure to submit the copy of valid Tax Clearance Certificate and verification information will result in the invalidation and disqualification of your bid response.
9.3 Shareholding and Directors
The firm must indicate the nature of the shareholding of the firm and provide the names of directors of the firm. Indicate percentage owned by Black Women, Black youth and by disabled.
9.4 National Treasury List of Restricted Service Providers No bid will be awarded to a person or company who has been listed in the National treasury lists of restricted service provider/suppliers as updated by National treasury.
6
9.5 National Treasury’s Central Supplier Database (NT - CSD) With effect from 1 April 2016, accounting officers and accounting authorities may not award any bid to a supplier/service provider not registered as a prospective supplier on the National Treasury’s Central Supplier Database. Please attach the first page of the Central Supplier Database (CSD) from National Treasury to the bid response.
9.6 Other mandatory administrative and technical requirements. Other mandatory administrative and technical requirements are stipulated under item 15 of the bid (See from page 17).
10. DISCUSSIONS Broadband Infraco reserves the right to call upon any bidder to discuss or present its proposals as and when deemed necessary at the bidder’s cost. Under no circumstances will a presentation by or negotiation with any bidder constitute an award or promise / undertaking to award the contract.
11. SPECIAL CONDITIONS OF THIS BID
These special conditions must be read in conjunction with the general conditions and NEC3 Professional Services Contract (PSC3) that are applicable to this bid:
a. To award this tender to a bidder that did not score the highest total number of points, only in accordance with section 2(1)(f) of the PPPFA (Act 5 of 2000), as amended.
b. To negotiate with one or more preferred bidder(s) identified in the evaluation process, regarding any terms and conditions, including price without offering the same opportunity to any other bidder(s) who has not been awarded the status of the preferred bidder(s).
c. To accept part of a tender rather than the whole tender.
d. To carry out site inspections, product evaluations or explanatory meetings in order to verify the nature and quality of the services offered by the bidder(s), whether before or after adjudication of the Bid.
e. To correct any mistakes at any stage of the tender that may have been in the Bid documents or occurred at any stage of the tender process.
f. To cancel and/or terminate the tender process at any stage, including after the Closing Date and/or after presentations have been made, and/or after tenders have been evaluated and/or after the preferred bidder(s) have been notified of their status as such.
g. Award to multiple bidders based either on size or geographic considerations (where applicable).
12. SIGNED CONFIDENTIALITY AGREEMENT
The attached confidentiality agreement included in Annexure F must be signed by the person who is authorised to sign on behalf of the firm and returned with the response to this RFP.
7
13. BID APPROVAL Bid document for the appointment of a service provider who will supply, install, test, configure and integrate the Operational Support System (OSS) & Business Support Systems (BSS) network element/system at Broadband Infraco (INF/TEN/ 0222).
.................................. Ms Deliwe Rampa General Manager – Supply Chain Management Date:
8
RECEIPT OF INVITATION FORM TO: Broadband Infraco (SOC) Ltd FROM
Country Club Estate, Building 9
Name of firm
Attention
21 Woodlands Drive, Woodmead, Sandton Lwandle Mgidlana
Sender Email
______________________________
Tel No. 011 235-1851 Fax No.
REQUEST FOR PROPOSALS: INF/TEN/ 0222 CLOSING DATE: 03 MAY 2018 @ 12h00 PM
INVITATION TO SUBMIT A PROPOSAL: APPOINTMENT OF A SERVICE PROVIDER WHO WILL SUPPLY, INSTALL, TEST, CONFIGURE AND INTERGRATE THE OPERATIONAL SUPPORT SYSTEM (OSS) & BUSINESS SUPPORT SYSTEMS (BSS) NETWORK ELEMENT/SYSTEM AT BROADBAND INFRACO. 1 We have noted the deadline for the RFP submission and will be submitting our quotation before
then and as instructed. We propose to submit a quotation in the name of the firm stated above.
2 We do not intend to submit a response for this service, and return all of the attached
documentation herewith. Our reason for not wishing to submit a quotation is as follows:
(NB)*
This form must be send back to Broadband Infraco’s contact on the deadline of question responses – 21 April 2018 at 15H00 to allow Broadband to send responses and for individual bidders to prepare the responses so as the closing date cannot be affected by late questions and responses.
Submission of this form will help Broadband Infraco compile a list of interested bidders who will be directly contactable when there are scope changes, addendums and/or for any formal communication for tender INF/TEN/ 0222.
Yours faithfully for the bidder
9
Document List
1. RFP Document
2. Annexure A - Document list.
3. Annexure B - Broadband Infraco Standard Conditions of Tender.
4. Annexure C – Mandatory Administrative and Technical requirements of Tender.
5. Annexure D - Tender Returnable.
6. Annexure E - Confidentiality Agreement.
7. Annexure F – A1: Technical Specification.
8. Standard Bidding Document 1: Invitation to Bid
9. Annexure G – SBD 4: Declaration of interest.
10. Annexure J – SBD 6.1: Preferential Points claim in terms of the Preferential Procurement
Regulations, 2017.
11. Annexure H – SBD 8: Declaration of bidder’s past Supply Chain Management Practices.
12. Annexure I - Independent bid determination.
13. Annexure K – A3: Pricing Schedule.
10
ANNEXURE B
BROADBAND INFRACO (SOC) LTD
STANDARD CONDITIONS OF TENDER
January 2008
11
1 GENERAL Actions 1 Broadband Infraco (SOC) Ltd (Infraco), Infraco's Representative and each
bidder submitting a tender shall act timeously as stated in these Conditions of Tender and in a manner which is fair, equitable, transparent, competitive and cost-effective.
Interpretation 2 Terms shown in italics vary for each tender. The details of each term for this
tender are identified in the Tender Data. Terms shown in capital initials are defined terms in the appropriate conditions of contract.
3 Any additional or amended requirements in the Tender Data and additional
requirements given in the Schedules in the tender returnables are deemed to be part of these Conditions of Tender.
4 The Conditions of Tender and the Tender Data shall not form part of any
contract arising from this invitation to tender. Communication 5 Each communication between Broadband Infraco and a bidder shall be to or
from Infraco's Representative only, and in a form that can be read, copied and recorded. Communication shall be in the English language. Infraco takes no responsibility for non-receipt of communications from or by a bidder.
Infraco's rights to accept or reject any tender
6 Infraco may accept or reject any variation, deviation, tender, or alternative tender, and may cancel the tender process and reject all tenders at any time prior to the formation of a contract. Broadband Infraco or Broadband Infraco's Representative will not accept or incur any liability to a bidder for such cancellation and rejection, but will give written reasons for the action upon written request to do so. Broadband Infraco reserves the right to accept the whole of any part of any tender.
After the cancellation of the tender process or the rejection of all tenders
Broadband Infraco may abandon the proposed work and services, have it performed in any other manner, or re-issue a similar invitation to tender at any time.
2 BIDDERS OBLIGATIONS The bidder shall comply with the following obligations when submitting a
tender and shall: Eligibility 1 Submit a tender only if the bidder complies with the criteria stated in the Tender
Data and the bidder, or any of his principals, is not under any restriction to do business with Infraco.
Cost of tendering
2 Accept that Infraco will not compensate the bidder for any costs incurred in the preparation and submission of a tender, including the costs of any testing necessary to demonstrate that aspects of the tender satisfy the evaluation criteria.
Check documents
3 Check the tender documents on receipt, including pages within them, and notify Infraco's Representative of any discrepancy or omissions using the enclosed fax-back form.
Confidentiality and copyright of documents
4 Treat as confidential all matters arising in connection with the tender. Use and copy the documents provided by Infraco only for the purpose of preparing and submitting a tender in response to this invitation.
12
Standardised specifications and other publications
5 Obtain, as necessary for submitting a tender, copies of the latest revision of standardised specifications and other publications, which are not attached but which are incorporated into the tender documents by reference.
Acknowledge receipt
6 Complete the Receipt of invitation and submit the tender fax-back form, which is attached to the Letter of Invitation, and return it within five days of receipt of the invitation.
7 Acknowledge receipt of Addenda to the tender documents, which Infraco's
Representative may issue, and if necessary apply for an extension to the deadline for tender submission, in order to take the Addenda into account.
Site visit and / or clarification meeting
8 Attend a site visit and/or clarification meeting at which bidders may familiarise themselves with the proposed work, services or supply, location, etc. and raise questions. Details of the meeting(s) are stated in the Tender Data.
Seek clarification
9 Request clarification of the tender documents, if necessary, by notifying Infraco's Representative earlier than the closing time for clarification of queries.
Insurance 10 Be informed that the extent (if any) of insurance provided by Infraco may not
be for the full cover required in terms of the relevant category listed in Section 8 of the conditions of contract, the bidder is advised to seek qualified advice regarding insurance.
Pricing the tender
11 Include in the rates, prices, and the tendered total of the prices (if any) all duties, taxes (except VAT), and other levies payable by the successful bidder. Such duties, taxes and levies are those applicable 14 days prior to the deadline for tender submission.
12 Show Value Added Tax (VAT) payable by Infraco separately as an addition to
the tendered total of the prices. 13 Provide rates and prices that are fixed for the duration of the contract and not
subject to adjustment except as provided for in the conditions of contract. 14 State the rates and Prices in South African Rand unless instructed otherwise
as an additional condition in the Tender Data. The selected conditions of contract may provide for part payment in other currencies.
Alterations to documents
15 Not make any alterations or additions to the tender documents, except to comply with instructions issued by Infraco's Representative or if necessary to correct errors made by the bidder. All such alterations shall be initialled by all signatories to the tender. Corrections may not be made using correction fluid, correction tape or the like.
Alternative tenders
16 Submit alternative tenders only if a main tender, strictly in accordance with all the requirements of the tender documents is also submitted. The alternative tender is submitted with the main tender together with a schedule that compares the requirements of the tender documents with the alternative requirements the bidder proposes.
17 Accept that an alternative tender may be based only on the criteria stated in
the Tender Data and as acceptable to Broadband Infraco. Submitting a tender
18 Submit a tender for providing the whole of the works, services or supply identified in the Contract Data unless stated otherwise as an additional condition in the Tender Data.
13
19 Return the tender returnables to Infraco, completing without exception all the forms, data and schedules included therein.
20 Submit the tender as an original plus the number of copies stated in the Tender
Data and provide an English translation for documentation submitted in a language other than English. Tenders may not be written in pencil but must be completed in ink.
21 Sign the original and all copies of the tender where indicated. Infraco will hold
the signatory duly authorised and liable on behalf of the bidder. 22 Seal the original and each copy of the tender as separate packages marking
the packages as "ORIGINAL" and "COPY". Each package shall state on the outside Infraco's address and invitation to tender number stated in the Tender Data, as well as the bidders name and contact address.
23 Seal original and copies together in an outer package that states on the
outside only Infraco's address and invitation to tender number as stated in the Tender Data. The outer package must be marked “CONFIDENTIAL”
24 Accept that Infraco will not assume any responsibility for the misplacement or
premature opening of the tender if the outer package is not sealed and marked as stated
Note:
Infraco prefers not to receive tenders by post, and takes no responsibility for delays in the postal system or in transit within or between Infraco offices.
Where tenders are sent per fax, Infraco takes no responsibility for difficulties in transmission caused by line or equipment faults.
Where tenders are sent via courier, Infraco takes no responsibility for tenders delivered to any other site than the tender office.
Infraco employees are not permitted to deposit a tender into the Infraco tender box on behalf of a bidder, except those lodged by post or courier.
Closing time 26 Ensure that Infraco has received the tender at the address and in the tender
box or fax specified in the Tender Data no later than the deadline for tender submission. Proof of posting will not be taken by Infraco as proof of delivery. Infraco will not accept a tender submitted telephonically, e-mail or by telegraph unless stated otherwise in the Tender Data.
27 Accept that, if Infraco extends the deadline for tender submission for any
reason, the requirements of these Conditions of Tender apply equally to the extended deadline.
Tender validity 28 Hold the tender(s) valid for acceptance by Infraco at any time within the validity
period after the deadline for tender submission. 29 Extend the validity period for a specified additional period if Infraco requests
the bidder to extend it. A bidder agreeing to the request will not be required or permitted to modify a tender, except to the extent Infraco may allow for the effects of inflation over the additional period.
Clarification of tender after submission
30 Provide, on request from Infraco's Representative during the evaluation of tenders, any other material that has a bearing on the tender, the bidders commercial position (including notarised joint venture agreements), preferencing arrangements or samples of materials, considered necessary by Infraco for the purpose of a full and fair risk assessment. This may include providing a breakdown of rates or Prices. No change in the total of the Prices or substance of the tender is sought, offered, or permitted except as required
14
by Infraco's Representative to confirm the correction of arithmetical errors discovered in the evaluation of tenders. The total of the Prices stated by the bidder as corrected by Infraco's Representative with the concurrence of the bidder, shall be binding upon the bidder
Submit bonds, policies etc.
31 If instructed by Infraco's Representative (before the formation of a contract), submit for Infraco's acceptance, the bonds, guarantees, policies and certificates of insurance required to be provided by the successful bidder in terms of the conditions of contract.
32 Undertake to check the final draft of the contract provided by Infraco's
Representative, and sign the Form of Agreement all within the time required by these Conditions of Tender.
33 Where an agent on behalf of a principal submits a tender, an authenticated
copy of the authority to act as an agent must be submitted with the tender. Fulfil BEE requirements
34 Comply with Broadband Infraco’s requirements regarding BEE and Black Women-owned Suppliers.
3 BROADBAND INFRACO'S UNDERTAKINGS Broadband Infraco, and Broadband Infraco's Representative, shall: Respond to clarification
1 Respond to a request for clarification received earlier than the closing time for clarification of queries. The response is notified to all bidders.
Issue Addenda 2 If necessary, issue Addenda that may amend, amplify, or add to the
tender documents, to each bidder. If a bidder applies for an extension to the deadline for tender submission, in order to take Addenda into account in preparing a tender, Infraco may grant such an extension and Infraco's Representative shall notify the extension to all bidders.
Return late tenders 3 Return tenders received after the deadline for tender submission
unopened to the bidder submitting a late tender. Tenders will be deemed late if they are not on the designated fax or in the designated tender box at the date and time stipulated as the deadline for tender submission.
Non-disclosure 4 Not disclose to bidders, or to any other person not officially concerned with such processes, information relating to the evaluation and comparison of tenders and recommendations for the award of a contract, until after the award of the contract to the successful bidder.
Grounds for rejection 5 Consider rejecting a tender if there is any effort by a bidder to influence
the processing of tenders or contract award. Disqualification 6 Instantly disqualify a bidder (and his tender) if it is established that the
bidder offered an inducement to any person with a view to influencing the placing of a contract arising from this invitation to tender.
Test for responsiveness
7 Determine before detailed evaluation, whether each tender properly received
meets the requirements of these Conditions of Tender,
has been properly signed, and
is responsive to the requirements of the tender documents. 8 Judge a responsive tender as one which conforms to all the terms,
conditions, and specifications of the tender documents without
15
material deviation or qualification. A material deviation or qualification is one which, in Broadband Infraco's opinion would
detrimentally affect the scope, quality, or performance of the works, services or supply identified in the Contract Data,
change Broadband Infraco's or the bidders risks and responsibilities under the contract, or
affect the competitive position of other bidders presenting responsive tenders, if it were to be rectified.
Non-responsive tenders
9 Reject a non-responsive tender, and not allow it to be subsequently made responsive by correction or withdrawal of the non-conforming deviation or reservation.
Arithmetical errors 10 Check responsive tenders for arithmetical errors, correcting them as
follows:
Where there is a discrepancy between the amounts in figures and in words, the amount in words shall govern.
If a bill of quantities applies and there is a discrepancy between the rate and the line item total, resulting from multiplying the rate by the quantity, the rate as quoted shall govern. Where there is an obviously gross misplacement of the decimal point in the rate, the line item total as quoted shall govern, and the rate will be corrected.
Where there is an error in the total of the Prices, either as a result of other corrections required by this checking process or in the bidders addition of prices, the total of the Prices, if any, will be corrected.
The corrected price will be communicated to the bidder. The bidder may withdraw the tender, but may not change the tendered price.
11 Reject a tender if the bidder does not accept the corrected total of the
Prices (if any). Evaluating the tender 12 Evaluate responsive tenders in accordance with the procedure and
criteria stated in the Tender Data. The evaluated tender price will be disclosed only to the relevant Infraco tender committee and will not be disclosed to bidders or any other person.
Clarification of a tender
13 Obtain from a bidder clarification of any matter in the tender which may not be clear or could give rise to ambiguity in a contract arising from this tender if the matter were not to be clarified.
Acceptance of tender 14 Notify Infraco's acceptance to the successful bidder before the expiry
of the validity period, or agreed additional period. Providing the notice of acceptance does not contain any qualifying statements, it will constitute the formation of a contract between Broadband Infraco and the successful bidder.
Notice to unsuccessful bidders
15 After the successful bidder has acknowledged Infraco’s notice of acceptance, notify other bidders that their tenders have not been accepted, following Infraco’s current procedures.
Prepare contract documents
16 Revise the contract documents issued by Broadband Infraco as part of the tender documents to take account of
Addenda issued during the tender period,
inclusion of some of the tender returnables, and
16
other revisions agreed between Infraco and the successful bidder, before the issue of Infraco's notice of acceptance (of the tender).
The schedule of deviations attached to the form of offer and acceptance, if any.
Issue final contract 17 Issue the final contract documents to the successful bidder for
acceptance within one week of the date of Infraco's notice of acceptance.
Sign Form of Agreement
18 Arrange for authorised signatories of both parties to complete and sign the original and one copy of the Form of Agreement within two weeks of the date of Infraco's notice of acceptance of the tender. If either party requires the signatories to initial every page of the contract documents, the signatories for the other party comply with the request.
Complete Adjudicator's Contract
19 Unless alternative arrangements have been agreed, arrange for both parties to complete and sign the Form of Agreement and Contract Data for the NEC Adjudicator's Contract with the selected adjudicator.
Provide copies of the contracts
20 Provide to the successful bidder the number of copies stated in the Tender Data of the signed copy of the contracts within three weeks of the date of Broadband Infraco's acceptance of the tender.
17
BID EVALUATION METHODOLOGY
Broadband Infraco has set minimum standards that a bidder needs to meet in order to be evaluated and
selected as a successful bidder. The minimum standards consist of the following:
Mandatory documents to be
submitted with the bid
Technical Evaluation
Criteria
(Stage 1)
Proof of Concept
Criteria
(Stage 2)
Price and B-BBEE
Criteria
(Stage 3)
1. Bidders must submit
all documents as
outlined in Table 1
below.
2. Bidders will only
pass this gate if they
have attended the
briefing and signed
the attendance
register.
Only bidders that comply
with ALL these criteria will
proceed to Stage 1.
Bidder(s) are required to
achieve a minimum of 65
points out of 80 points to
proceed to Stage 2 (Proof
of Concept Evaluation).
Bidder(s) are required to
achieve a minimum of
15 points out of 20 to
proceed to Stage 3
(Price & B-BBEE
Evaluation).
Price and B-BBEE
Evaluation on the
80/20 preferential
point system
Mandatory documents that must be submitted with the bid
Without limiting the generality of Broadband Infraco’s other critical requirements for this Bid, bidder(s)
must submit the documents listed in Table 1 below. All documents must be completed and signed by
the duly authorised representative of the prospective bidder(s). During this phase Bidders’ responses
will be evaluated based on compliance with the listed administration and mandatory bid requirements.
The bidder(s) proposal may be disqualified for non-submission of any of the documents.
18
Table 1: Documents that must be submitted for Pre-qualification
Document that must be submitted Non-submission may result in disqualification?
Invitation to Bid – SBD 1 YES Complete and sign the supplied pro forma document
Tax Status
Tax Clearance Certificate –
SBD 2
YES i. Written confirmation that SARS may on an
ongoing basis during the tenure of the contract
disclose the bidder’s tax compliance status.
(Refer Section 4.1.4)
ii. Proof of Registration on the Central Supplier
Database (Refer Section 4.1.5)
iii. Vendor number
iv. In the event where the Bidder submits a hard
copy of the Tax Clearance Certificate, the CSD
verification outcome will take precedence.
Declaration of Interest – SBD 4 YES Complete and sign the supplied pro forma document
Preference Point Claim Form –
SBD 6.1
YES Non-submission will lead to a zero (0) score on
BBBEE
Declaration of Bidder’s Past
Supply Chain Management
Practices – SBD 8
YES Complete and sign the supplied pro forma document
Certificate of Independent Bid
Determination – SBD 9
YES Complete and sign the supplied pro forma document
Bidder Compliance form for
Functional Evaluation
YES Complete and sign
Registration on Central Supplier
Database (CSD
YES Bidders must be registered as a service
provider on the Central Supplier Database
(CSD). If you are not registered proceed to
complete the registration of your company
prior to submitting your proposal. Visit
https://secure.csd.gov.za/ to obtain your vendor
number.
Submit proof of registration.
Pricing Schedule YES Submit full details of the pricing proposal as per
in a separate envelope
19
1.1. State 1: Technical Evaluation Criteria = 80 points
All bidders are required to respond to the technical evaluation criteria.
Only Bidders that have met the Pre-Qualification Criteria in will be evaluated in Stage 1for
functionality.
Functionality will be evaluated as follows:
i. Technical Evaluation – Bidders will be evaluated out of 80 points and are required to
achieve minimum threshold of 65 points of 80 points for Stage 1 in order to proceed to
Stage 2 (Proof of Concept Evaluation).
ii. Proof of Concept Evaluation - Bidder(s) are required to achieve a minimum of 15 points
out of 20 to proceed to Stage 3 (Price & B-BBEE Evaluation).
As part of due diligence, Broadband Infraco may conduct a site visit at a client of the Bidder (reference)
for validation of the services rendered. The choice of site will be at Broadband Infraco’ sole discretion.
The Bidder’s information will be scored according to the following points system:
Functionality Maximum Points
Achievable
Minimum Threshold
Technical Evaluation
80 65
Proof of Concept Evaluation 20 15
Phase 2: Price and BBBEE Evaluation (80+20) = 100 points
Only Bidders that have met the 80 point threshold in Phase 1 will be evaluated in Phase 2 for price and
BBBEE. Price and BBBEE will be evaluated as follows:
In terms of regulation 6 of the Preferential Procurement Regulations pertaining to the Preferential
Procurement Policy Framework Act, 2000 (Act 5 of 2000), responsive bids will be adjudicated on the
80/20-preference point system in terms of which points are awarded to bidders on the basis of:
- The bid price (maximum 80 points)
- B-BBEE status level of contributor (maximum 20 points)
20
i. Phase 1 – Price Evaluation (0 Points)
The following formula will be used to calculate the points for price:
Where
Ps = Points scored for comparative price of bid under consideration
Pt = Comparative price of bid under consideration
Pmin = Comparative price of lowest acceptable bid
ii. Stage 2 – BBBEE Evaluation (20 Points)
a. BBBEE Points allocation
A maximum of 20 points may be allocated to a bidder for attaining their B-BBEE status level of
contributor in accordance with the table below:
B-BBEE Status Level of Contributor Number of Points
1 20
2 18
3 14
4 12
5 6
6 4
7 2
8 2
Non-compliant contributor 0
B-BBEE points may be allocated to bidders on submission of the following documentation or evidence:
- A duly completed Preference Point Claim Form: Standard Bidding Document (SBD 6.1); and
- B-BBEE Certificate
Criteria Points
Price Evaluation
Ps =80
min
min1
P
PPt
80
www.infraco.co.za
Registration Number: 1989/001763/30
Woodmead Country Club Estate, Building No.9, No.1 Woodlands Drive, Woodmead Extension 34, South Africa
Postnet Suite 321, Private Bag X26, Sunninghill, 2157
Annexure D (TENDER RETURNABLES CHECKLIST) Supplier: ………………………………….. Bid Number…..…………
Item Number
Description YES NO
Administrative requirements
1. Full copy of submission on CD / USB
2. 1 tender hard copy, (1 original)
3 Sections
3. General Commercial (including costs offer for the month, year and for two years)
4. Technical response indicating compliance to the requirements of the bid
5. Financial statements
Company information
6. General data
7. Company profile covering all the administrative, technical and functionality requirements of the bid
8. Completion and submission of SBD 4 “Declaration of Interest”
9. Completion and submission of SBD 8 “Bidder’s past SCM experience”
10. Completion and submission SBD 9 “ Independent Bid determination”
11. Valid SARS Tax clearance certificate accompanied by a third party authorisation PIN as provided by the tax authority to each bidder.
12. Shareholding and Directors percentage ownership
13. Cover letter indicating acceptance of NEC’s Professional Contract and negotiation of an acceptable SLA or Finance contract.
14. Signed confidentiality agreement
15. Acceptance of validity of tender – 120 days from closing of bid
16. No bid will be awarded to a person or company who has been listed in the National treasury lists of restricted service provider/suppliers as updated by National treasury.
17. With effect from 1 April 2016, accounting officers and accounting authorities may not award any bid to a supplier/service provider not registered as a prospective supplier in the National Treasury’s Central Supplier Database. Please attach the first page of the Central Supplier Database (CSD) from National Treasury to the bid response.
B-BBEE
18. Valid B-BBEE status certificate from accredited verification agencies, Accounting officers or accredited auditors, Sworn affidavits for QSEs and EMEs. BBBEE points will be awarded as per the Act and PPR 2017.
Technical requirements
19. - Refer to Scope / Specification and terms of supply (Annexure F)
23. - Compliance to other requirements of the bid.
22
Annexure E
CONFIDENTIALITY AND NON-DISCLOSURE AGREEMENT
CONFIDENTIALITY AND NON-DISCLOSURE AGREEMENT
“Agreement”
Between
BROADBAND INFRACO SOC LIMITED
And
________________________________________________________________________________
[NAME OF OTHER PARTY]
23
THE PARTIES TO THIS AGREEMENT ARE:-
I. BROADBAND INFRACO (SOC) LIMITED a company incorporated under the laws of the
Republic of South Africa, having its registered office at Country Club Estate, Building 9, 21
Woodlands Drive, Woodmead, Sandton, Republic of South Africa, with registration number
1989/001763/07 [hereinafter referred to as the “Disclosing Party”).
II. NAME OF OTHER PARTY a company incorporated under the laws of [insert name of country],
having its registered office at [registered address], Republic of South Africa, with registration
number [insert registration number] [hereinafter referred to as the “Receiving Party”).
Hereinafter individually referred to as a “Party” and jointly as the “Parties”.
NOW THEREFORE, IT IS HEREBY AGREED AS FOLLOWS:
The Disclosing Party intends providing the Receiving Party with certain information relating to the Disclosing Party for the purpose of tendering for – appointment of a service provider who will supply, install, test, configure and integrate the Operational Support System (OSS) & Business Support Systems (BSS) network element/system at Broadband Infraco. 1.1 1.2 The parties wish to record the terms and conditions upon which the Disclosing Party shall
disclose Confidential Information to the Receiving Party, which terms and conditions shall
constitute a binding and enforceable Agreement between the parties and their agents.
1.3 Notwithstanding the date of signature hereof, this agreement shall be binding upon the parties
with effect from the date upon which the Disclosing Party shall have disclosed any Confidential
Information to the Receiving Party, whichever date is the earliest.
1.4 Neither this Agreement nor the exchange of information contemplated hereby shall commit
either party to continue discussions or to negotiate, or to be legally bound to any potential
business relationship. The parties shall only be bound to a business relationship by way of a
further definitive written Agreement signed by the Parties.
1.5 The party disclosing the Confidential Information shall be known as the “Disclosing Party” and
the party receiving Confidential Information shall be known as the “Receiving Party”.
2. THE CONFIDENTIAL INFORMATION
“Confidential Information” shall for the purpose of this Agreement include, without limitation,
any technical, commercial or financial information, know-how, trade secrets, processes,
machinery, designs, drawings, technical specifications and data relating to the Project
24
(including, but not limited to, the information set out in 1.1 above) in whatever form, relating to
the disclosing Party's business practices or the promotion of the disclosing Party's business
plans, policies or practices, which information is communicated to the receiving Party, or
otherwise acquired by the Receiving Party from the Disclosing Party, during the course of the
Parties' commercial interactions, discussions and negotiations with one another, whether such
information is formally designated as confidential or not.
3. DISCLOSURE OF CONFIDENTIAL INFORMATION
3.1 The Disclosing Party shall only disclose the Confidential Information to the Receiving Party to
the extent deemed necessary or desirable by the Disclosing Party in its discretion.
3.2 The Parties acknowledge that the Confidential Information is a valuable, special and unique
asset proprietary to the Disclosing Party.
3.3 The Receiving Party agrees that it will not, during or after the course of its relationship with the
disclosing party under this agreement and/or the term of this Agreement, disclose the
Confidential Information to any third party for any reason or purpose whatsoever without the
prior written consent of the Disclosing Party and to the extent of such authorisation, save in
accordance with the provisions of this Agreement. In this Agreement “third party” means any
party other than the Receiving and Disclosing Parties or their Representatives.
3.4 Notwithstanding anything to the contrary contained in this Agreement the Parties agree that
the Confidential Information may be disclosed by the Receiving Party to its respective
employees, agents, officers, directors, subsidiaries, associated companies, shareholders and
advisers (including but not limited to professional financial advisers, legal advisers and
auditors) ("Representatives") on a need-to-know basis and for the purposes of the Project;
provided that the Receiving Party takes whatever steps are necessary to procure that such
Representatives agree to abide by the terms of this Agreement to prevent the unauthorised
disclosure of the Confidential Information to third parties. For purposes of this clause, the
Receiving Party’s Representatives shall be deemed to be acting, in the event of a breach, as
the Receiving Party’s duly authorised agents.
3.5 Except as otherwise contemplated in this Agreement, the Parties agree in favour of one
another not to utilise, exploit or in any other manner whatsoever use the Confidential
Information disclosed pursuant to the provisions of this Agreement for any purpose
whatsoever other than the Project without the prior written consent of the Disclosing Party.
3.6 Accordingly, the Receiving Party agrees to indemnify, defend and hold the Disclosing Party
harmless from and against any and all suits, liabilities, causes of action, claims, losses,
damages, costs (including, but not limited to, cost of cover, reasonable attorneys' fees and
25
expenses), or expenses of any kind (collectively, "Losses") incurred or suffered by the
Disclosing Party and/or its Representatives arising from or in connection with the Receiving
Party's unauthorized use or disclosure of the Disclosing Party's Confidential Information in
violation of the Agreement.
4. TITLE
All Confidential Information disclosed by the Disclosing Party to the Receiving Party is
acknowledged by the Receiving Party to be proprietary and the exclusive property of the
Disclosing Party. This Agreement shall not confer any rights of ownership or license on the
Receiving Party of whatever nature in the Confidential Information.
5. RESTRICTING ON DISCLOSURE AND USE OF THE CONFIDENTIAL INFORMATION
5.1 The Receiving Party undertakes not to use the Confidential Information for any purpose other
than:
5.1.1 the Project; and
5.1.2 in accordance with the provisions of this Agreement.
6. STANDARD OF CARE
The Receiving Party agrees that it shall protect the Confidential Information disclosed pursuant
to the provisions of this Agreement using the same standard of care that it applies to safeguard
its own proprietary, secret or Confidential Information but no less than a reasonable standard
of care, and that the Confidential Information shall be stored and handled in such a way as to
prevent any unauthorised disclosure thereof.
7. RETURN OF MATERIAL CONTAINING OR PERTAINING TO THE CONFIDENTIAL
INFORMATION
7.1 The Disclosing Party may, at any time, and in its sole discretion request the Receiving Party to
return any material and/or data in whatever form containing, pertaining to or relating to
Confidential Information disclosed pursuant to the terms of this Agreement and may, in addition
request the Receiving Party to furnish a written statement to the effect that, upon such return,
the Receiving Party has not retained in its possession, or under its control, either directly or
indirectly, any such material and/or data.
7.2 If it is not practically able to do so, the Receiving Party shall destroy or ensure the destruction
of all material and/or data in whatever form relating to the Confidential Information disclosed
26
pursuant to the terms of this Agreement and delete, remove or erase or use best efforts to
ensure the deletion, erasure or removal from any computer or database or document retrieval
system under its or the Representatives' possession or control, all Confidential Information and
all documents or files containing or reflecting any Confidential Information, in a manner that
makes the deleted, removed or erased data permanently irrecoverable. The Receiving Party
shall furnish the Disclosing Party with a written statement signed by one of its directors or duly
authorized senior officers to the effect that all such material has been destroyed.
7.3 The Receiving Party shall comply with any request by the Disclosing Party in terms of this
clause, within 7 (seven) business days of receipt of any such request.
8. EXCLUDED CONFIDENTIAL INFORMATION
The obligations of the Receiving Party pursuant to the provisions of this Agreement shall not
apply to any Confidential Information that:
8.1 is known to, or in the possession of the Receiving Party prior to disclosure thereof by the
Disclosing Party;
8.2 is or becomes publicly known, otherwise than as a result of a breach of this Agreement by the
Receiving Party;
8.3 is developed independently of the Disclosing Party by the Receiving Party in circumstances
that do not amount to a breach of the provisions of this Agreement;
8.4 is disclosed by the Receiving Party to satisfy an order of a court of competent jurisdiction or to
comply with the provisions of any law or regulation in force from time to time; provided that in
these circumstances, the Receiving Party shall advise the Disclosing Party to take whatever
steps it deems necessary to protect its interests in this regard and provided further that the
Receiving Party will disclose only that portion of the Confidential Information which it is legally
required to disclose and the Receiving Party will use its reasonable endeavours to protect the
confidentiality of such Confidential Information to the greatest extent possible in the
circumstances;
8.5 is disclosed to a third party pursuant to the prior written authorisation and limited to the extent
of such approval of the Disclosing Party;
8.6 is received from a third party in circumstances that do not result in a breach of the provisions
of this Agreement.
27
9. TERM
This Agreement shall commence upon the date referred to in paragraph 1.3 and shall endure
for a period of 2 (two) years after the date of termination of the relationship between the parties
referred to herein.
10. ADDITIONAL ACTION
10.1 Each Party to this Agreement shall execute and deliver such other documents and do such
other acts and things as may be reasonably necessary or desirable to give effect to the
provisions of this Agreement.
10.2 Nothing contained in the Agreement shall be construed as creating an obligation on the part of
either Party to refrain from entering into a business relationship with any third party. Nothing
contained in the Agreement shall be construed as creating a joint venture, partnership or
employment relationship between the Parties. Except as specified herein, neither Party shall
have the right, power or implied authority to create any obligation or duty (express, implied or
otherwise) on behalf of the other Party. For the avoidance of doubt, nothing in this Agreement
shall oblige either of the Parties to enter into any agreements or transactions whatsoever.
11. BREACH
In the event that the Receiving Party should breach any of the provisions of this Agreement and
fail to remedy such breach within seven (7) business days from date of a written notice to do
so, then the Disclosing Party shall be entitled to invoke all remedies available to it in law
including, but not limited to, the institution of urgent proceedings as well as any other way of
relief appropriate under the circumstances, in any court of competent jurisdiction, in the event
of breach or threatened breach of the Agreement and/or an action for damages.
12. AMENDMENTS
No amendment, interpretation or waiver of any of the provisions of this Agreement shall be
effective unless reduced in writing and signed by the duly authorised representatives of both
Parties.
13. ENFORCEMENT
The failure or delay by the Disclosing Party to enforce or to require the performance at any time
of any of the provisions of this Agreement shall not be construed to be a waiver of such
28
provision, and shall not affect either the validity of this Agreement or any part hereof or the right
of the Disclosing Party to enforce the provisions of this Agreement.
14. HEADINGS
The headings of the clauses of this Agreement are used for convenience only and shall not
affect the meaning or construction of the contents of this Agreement.
15. REPRESENTATIONS & WARRANTIES
15.1 Each Party represents that it has authority to enter into this Agreement and to do all things
necessary to procure the fulfilment of its obligations in terms of this Agreement.
15.2 The Disclosing Party warrants that disclosure of the Confidential Information to the Receiving
Party:
15.2.1 will not result in a breach of any other Agreement to which it is a party; and
15.2.2 will not, to the best of its knowledge and belief, infringe the rights of any third party; and the
Disclosing Party hereby indemnifies and holds the Receiving Party harmless against any
liability for third party claims on such a basis.
16. ENTIRE AGREEMENT
This Agreement contains the entire agreement of the Parties with respect to the subject matter
of this Agreement and supersedes all prior agreements between the Parties, whether written
or oral, with respect to the subject matter of this Agreement.
17. GOVERNING LAW
This Agreement and the relationship of the Parties in connection with the subject matter of this
Agreement and each other shall be governed and determined in accordance with the laws of
the Republic of South Africa.
18. DOMICILIA AND NOTICES
18.1 The Parties hereby choose domicilium citandi et executandi (“domicilium”) for all purposes
under the Agreement the addresses set out below:
29
18.2 Any notice given by one party to the other is deemed to have been received by the addressee:
(Insert particulars of bidder above)
18.2.1 on the date on which the same was delivered to the addressee's address if delivered by hand;
or
18.2.2 on the seventh calendar day after the date of posting if sent by pre-paid registered post to the
addressee's address; or
18.2.3 on despatch, if sent to the addressee's then telefax number.
18.3 A party may change that party's address for this purpose, by notice in writing to the other party,
such a change of address being effective seven days after the deemed receipt by the
addressee of such written notice, provided that the changed address must be a physical
address. A notice will also be necessary in respect of new or changed telefax number.
19. SEVERABILITY
In the event of any one or more of the provisions of this Agreement being held for any reason
to be invalid, illegal or unenforceable in any respect, such invalidity, illegality or unenforceability
shall not affect any other provision of this Agreement, and this Agreement shall be construed
as if such invalid, illegal or unenforceable provisions was not a part of this Agreement, and this
Agreement shall be carried out as nearly as possible in accordance with its original terms and
intent.
20. ASSIGNMENT
20.1 Neither Party may assign or otherwise transfer any of its rights or obligations under this
Agreement to any third party without the prior written consent of the other Party.
PARTY PHYSICAL ADDRESS POSTAL ADDRESS TELEPHONE NO. CONTACT
PERSON
BROADBAND
INFRACO STAT
OWNED
COMPANY
LIMITED
COUNTRY CLUB ESTATE,
BUILDING 9, 21
WOODLANDS DRIVE,
WOODMEAD,
SANDTON
Postnet Suite
321, Private Bag
X26, Sunninghill,
2157
011 235-1848 POLELO MADUWA
30
20.2 This Agreement shall be binding on and shall inure for the benefit of the successors and
permitted assigns and personal representatives (as the case may be of the parties).
21. PUBLICITY
Neither party will make or issue any formal or informal announcement or statement to the press
or any third party in connection with this Agreement without the prior written consent of the other
Party.
SIGNED by the Parties and witnessed on the following dates and at the following places respectively:
SIGNED at on
AS WITNESS:
For: BROADBAND INFRACO (SOC) LIMITED
DULY AUTHORISED
(NAME OF WITNESS IN PRINT) [SPECIFY FULL NAME OF SIGNATORY]
SIGNED at on
AS WITNESS:
For: [NAME OF OTHER PARTY]
DULY AUTHORISED
(NAME OF WITNESS IN PRINT) [SPECIFY FULL NAME OF SIGNATORY]
31
Annexure F: SPECIFICATION
32
Table of Contents
EXECUTIVE SUMMARY ............................................................................................................................... 35
1 INTRODUCTION TO THE BROADBAND INFRACO TRANSFORMATION PROGRAM ........ 35
1.1 Broadband Infraco Company Overview............................................................................ 35
1.2 Broadband Infraco business goals and priorities .............................................................. 36
1.3 RFP Scope ....................................................................................................................... 39
1.4 High level requirements .................................................................................................. 42
1.5 Overall Broadband Infraco transformation scope as use cases .......................................... 43
1.6 Use case Descriptions ...................................................................................................... 43
1.7 Use case interrelations .................................................................................................... 43
1.8 Overall Functional requirement platforms architecture .................................................... 44
1.9 The project Phase scoping along Use Case prioritization ................................................... 44
2. BROADBAND INFRACO OPERATING MODEL IT COMPONENT ARCHITECTURE
REQUIREMENT ............................................................................................................................................... 45
2.1 Overall Functional IT Architecture ................................................................................... 45
2.1.1 Customer Management Platform: ................................................................................ 46
2.1.2 Service Delivery Platform: ............................................................................................. 47
2.1.3 Network Management Platform: .................................................................................. 48
2.1.4 Billing Platform: ............................................................................................................... 49
2.1.5 Integration Infrastructure ............................................................................................... 50
2.1.6 Existing Broadband Infraco infrastructure .................................................................. 52
2.2 Statement of Compliance ................................................................................................ 53
3. SOLUTION DELIVERY METHODOLOGY ........................................................................................... 53
4. EXPECTED RESPONSE STRUCTURE ................................................................................................... 57
4.1 Section: High level solution architecture .......................................................................... 57
4.1.1 Sub-section: High level solution description............................................................... 57
4.1.2 Sub-section: Functional requirements......................................................................... 57
4.2 Section: Use Case scenarios ............................................................................................. 58
33
4.3 Section: Integration Architecture ..................................................................................... 58
4.3.1 Sub-section: Integration architecture .......................................................................... 58
4.3.2 Sub-section: Interface Overview .................................................................................. 59
4.3.3 Sub-section: Non-functional requirements ................................................................. 60
4.3.4 Sub-section: Integration of existing Broadband Infraco applications ..................... 60
4.4 Section: Methodology, Skills & Experiences ..................................................................... 60
4.4.1 Solution Delivery Methodology ..................................................................................... 60
4.4.2 Skills & Experiences ...................................................................................................... 61
4.5 Section: Pricing & Timeline .............................................................................................. 61
4.6 Broadband Infraco service oriented business requirement engineering methodology ....... 62
34
ABBREVIATIONS
Abbreviations Description
BSS Business Support system
CDM
Common Data Model
COBIT
Control Objectives for Information and related Technology
CORBA
Common Object Request Broker Architecture
eTOM Enhanced Telecomm Operations Model
ERP
Enterprise Resource Planning
Multi Technology Operation System Interface
GB921E
TM-Forum Business process Frameworks
IF Integration Framework
ITIL Information Technology Infrastructure Library
OSS
Operations Support System
OSS/J
Operational Support System/Java
RFI
Request for Information
RFP
Request for Proposal
SID Shared Information and Data Model
SNMP Simple Network Management Protocol
SOA Service Oriented Architecture
TAM Telecommunication Application Map
TMForum Telecommunication Management Forum
UML Unified Modelling Language
35
EXECUTIVE SUMMARY
This document expresses the solution requirements for Broadband Infraco’s Operational
Support Systems (OSS) and Business Support System (BSS). The requirements are based
on the TM-Forum’s Frameworx: Business Process Framework (eTOM), Information
Framework (SID), Application Framework (TAM), and Integration Framework (IF). The
Integration Framework specifically contains standard interfaces, such as MTOSI and OSS/J.
The documents attached as Appendices must be used to indicate compliance with each
requirement. The additional information provided with a response and/or solution must show
how the requirement is satisfied.
The following table provides an overview of appendixes to the current RFP:
Appendix Description
A_Input_Functional Requirements List of functional requirements and their mapping to eTOM level 2
B_Input_UseCases List of identified use cases with priorities and their dependencies, their mapping to the functional requirements, to eTOM level 2, to SID level 1
C_Input_UC descriptions High level use case descriptions over all phases
D_Input_Functional Architecture Use case mapping to TAM level 1, platform definition, phase model
E_Consolidated Response Template
Excel template to be used by the respondent addressing: - applications involved in use cases - coverage of use cases and functional requirements - eTOM conformance per application - SID conformance per application - TAM coverage per application - API compliance
F_Non-Funtional Requirements v1.0
List of Non-Functional Requirements
Table 1: List of Appendixes
1 INTRODUCTION TO THE BROADBAND INFRACO TRANSFORMATION PROGRAM
1.1 Broadband Infraco Company Overview
Broadband Infraco legislative mandate is set out in the Broadband Infraco Act No. 33 of 2007
(the “Act”). The main objectives as set out in the Act are to expand the availability and
affordability of access to electronic communications, including but not limited to
underdeveloped and under serviced areas, in accordance with the Electronic Communications
Act and commensurate with international best practice and pricing, through the provision of
electronic communications network services and electronic communications services.
In addition, Broadband Infraco must comply with the Public Finance Management Act of 1999
as amended (the “PFMA”), National Treasury Regulations issued in terms of the Public
Finance Management Act, and the Companies Act No. 71 of 2008 and other laws that govern
the financial affairs, the stability and soundness of the financial system and manage the budget
XML Extensible Markup Language
36
preparation process; and enforce transparency and effective management in respect of
revenue and expenditure, assets and liabilities, of the Company.
Broadband Infraco vision is to be the wholesale provider of choice for Backhaul connectivity.
Our portfolio of wholesale products and services are based on the provision of high capacity
managed bandwidth from Point of Presence (POP) to POP delivered on our resilient National
Long Distance network. Our network covers all nine provinces, major cities and towns of South
Africa and also extends to the borders of our neighbouring countries of Botswana, Lesotho,
Mozambique, Namibia, Swaziland and Zimbabwe to provide required interconnectivity.
Broadband Infraco is a Tier 1 Investor in the 5.1 Tbits/s West Africa Cable System (WACS),
which connects South Africa to the United Kingdom, with landing stations in Portugal and
along the West Coast of Africa.
Our products and services are based on variety of technology portfolio, including Synchronous
Digital Hierarchy (SDH), Dense Wavelength Division Multiplexing (DWDM) or Optical
Transport Network (OTN), IP/MPLS and Carrier Ethernet.
1.2 Broadband Infraco business goals and priorities
Along its business and system transformation program Broadband Infraco is considered as a
system organized around the various holistic enterprises architectural layers as illustrated
here below and with the Enterprise operating model
Figure 1: Holistic Enterprise Architecture Layers
Integration
Information
Business
Organization
Technology
-
ApplicationTime to Value
37
The primary focus of Broadband Infraco organization is to bring business value at its
perimeter. This business value is aiming to maximize the achievement of core transformation
objectives on the long run such as:
Maximize Operational Efficiency (cost/ time /quality/ effectiveness)
Ensure strategic & operational efficiency by reducing the process cost, reducing
the time to execute, minimize rework while increasing effectiveness and
efficiency
Maximize Revenue and Margin (revenue/ profitability / cost/ churn)
Increase revenue and margin by a sustained customer acquisition, reduced churn
and profitable product and production portfolio handling
Maximize Customer Experience (access / time and quality)
Mandatory enhancement of the Broadband Infraco customer experience with the
introduction of new Broadband Infraco touch points reduction of request handling
time and increase of quality.
As reflected along these business goals, the scope of the Broadband Infraco business and
systems transformation is wide. It encompasses a large number of business domains and
application areas in the OSS/BSS/ERP landscape. In this context, Broadband Infraco has set
up a transformation program structured in 3 phases steered by a service oriented business
requirement engineering approach supporting an overarching architectural governance model
and business driven design authority.
Business Goals
Phase /
Architectural
Partition Priority
Generate additional revenue on Broadband Infraco managed
services (Assurance processes) for our customers and other
service providers.
1 Priority 1
Reinforce operational robustness to handle existing and
potential large customer’s requirements. Broadband Infraco is
in the process of acquisitioning a large institutional customer
with a large number of sites (SA Connect project).
Maximize resources efficiency and skills usage across the
Broadband Infraco operating model (Assurance, Billing &
revenue Management, Fullfillment)
Increase the level of process automation across the Broadband
Infraco business & systems operating model (OSS/BSS/ERP):
Assurance Processes, Fulfilment, Billing (usage based) and
Revenue Management / Enterprise Management (Finance
Management).
38
Maximize customer experience with the introduction of a Self-
care portal
Increase regulatory /legal corporate compliance (Fulfillment)
Fasten introduction of new product offering and technology
(e.g. Carrier Ethernet (Eline, ELAN, Etree), IP (Transit, VPN),
Central Services (Housing, Hosting)
2
Priority 2 Maximize resources efficiency and skills usage across the
Broadband Infraco operating model Billing (usage based) and
Revenue Management/ Enterprise Management (Finance
Management)
Increase regulatory /legal corporate compliance ( Finance
Management)
Table 2: Broadband Infraco Business Goals and Priorities
Taken all together these phases aim to the development/optimization and governance of
Broadband Infraco’s operating model.
The approach considers each phase of Broadband Infraco business transformation program
as a partition of Broadband Infraco’s overall Enterprise Architecture. It enables the deployment
of a consistent and business value driven architecture along the holistic layers of Enterprise
Architecture:
Organization & business layer
Information and data layer
Integration layer
Technology and tools layer
39
Figure 2: Business Value Driven Enterprise Architecture Deployment
Deploying a phased approach along the Broadband Infraco’s business transformation phases
will minimize the risk of integration complexities. In addition the OSS/BSS will be based on the
following well established TM-forum frameworks:
eTOM: The business framework gives the abstract description of business operations
and other activities, the purpose of which is to establish the information system to
support business and other activities.
SID: The information framework has functions of describing the activities of enterprises
with a unified information model and acting as a method of describing the enterprise
information infrastructure.
TAM: The framework of the application is the abstract description of business support
functions.
1.3 RFP Scope
This RFP is aiming to:
Acquire the services of a service provider to source, implement and integrate an
OSS/BSS solution along each phase of the Broadband Infraco’s transformation
program.
Integration
Information
Business
Organization
Technology
-
Application
Phase 1
Phase 2
Phase 3
…..
Phase n
40
Identify service providers to provide and design the OSS/BSS solution providing
the best value for money and the best fit with the core transformation objectives
and business goals.
Select the Services Providers with OSS/BSS solution that conform and comply with
the Frameworx as well as their ability to master the TM Forum Frameworx usage
along their proposed design and implementation.
Short list the most appropriate respondent in the perspective of this Request for
Proposal associated to each phase of the Broadband Infraco’s transformation.
Identify and select an appropriate solution to communicate with the legacy systems and
applications.
Evaluate the capability of the responder’s methodology in terms of low level design,
implementation and deployment to accompany Broadband Infraco’s architectural
governance of the solution and Broadband Infraco’s business and system
operating along the 4 architectural layers:
Business and organization layer
Information and data layer
Integration layer
Technology and Application layer
It is expected that a respondent employs a well-defined Solution Delivery Methodology providing also the necessary input such as Frameworx Mapping of low level solution design to enable the bottom–up consolidation in the Business Analysis and Architectural Governance Model.
Respondent to provide detailed deployment plan of the following application and solution
required.
Phase 1: Services assurance (Fault management, Trouble shooting,
Performance, quality and services management)
Services Fulfilment and Customer billing (Order management, Services and resources management, Services activation and Billing)
Phase 2: Customer care (customer management and contact center
application) Broadband Infraco operating model functional requirements.
Key business stakeholders, influencing factors and fact
On each Phase, do each modules for the Assurance first before moving to the
Fulfillment and Billing modules.
Start with Phase 1 then move to Phase 2 and on each Phases, complete each module
before moving to the next module.
The identification of the various Broadband Infraco key business stakeholders, key business
influencing factors and facts along the 3 dimensions of the Broadband Infraco business
operating model:
The internal dimension
The external dimension
41
Portfolio dimension
Figure 3: 3 Dimensions to Capture Key Business Stakeholders, Key Business
Influencing Factors and Facts
A responding solution provider will demonstrate how the proposed solution satisfies the
requirements for all portfolio types as well as provide some reference implementations.
The RFP requirements is driven by the need for maximizing operational efficiency, revenue
and margin as well as customer experience.
The required solution should integrate operational automation and improve network operation
efficiency and effectiveness across service fulfilment, assurance and billing. These business
capabilities can be mixed and matched to support the optimization of the current business and
systems operating model but also accompany the evolution of Broadband Infraco capabilities
within an ever changing business environment.
This approach will focus along each phase and step on the deployment and governance of
“just enough architecture” (Gartner) to govern the quick delivery of business value through the
speed and ease of adding new, and extending old, business capabilities on a standardized
service oriented architecture.
To ensure the openness of this platform to the vast array of Information Communication and
Entertainment (ICE) industry players, rapid computed solution development and decreased
integration tax, this approach adopts the principle of TMForum Frameworx compliance along
the multiple architectural layers:
Business layer compliance to TMForum Business Process Framework ( eTOM)
Information & data layer compliance to TMForum Information Framework ( SID)
Application Layer compliance to TMForum Application Framework ( TAM)
1
2
3
Supplier
PartnerCompetitors
Employee
Shareholders
Other stakeholders (e.g. Legal Authority Labor Authority)
Product
Service
Resource
Supplier / Partner
Enterprise
Market / Sales
Customer
customer
Portfolio dimension
Internal
dimension
External dimension
42
Integration layer compliance to TMForum Integration Framework ( TNA)
The aim of this approach is to tackle the very operational business goal that Broadband
Infraco currently faces while introducing the concept of Enterprise Architecture deployment
and governance.
1.4 High level requirements
The high level requirements have been captured and classified along the following set of
TMForum customer centric and network business streams processes.
Customer centric:
1. Request-to-answer: This process is comprised of activities relevant to managing
customer requests across all communication channels (customer interfaces).
2. Order-to-payment: This process deals with all activities which convert the
customer request or an accepted offer into a ‘Ready for use’ product.
3. Usage-to-payment: This process deals with all activities related to the handling
of the product/service usage.
4. Request-to-change: This process deals with all activities which convert the
customer‘s change request into a ‘Ready for use’ product.
5. Termination-to-confirmation: This process deals with all activities related to the
execution of customer‘s termination request.
6. Problem-to-solution: This process deals with a technical complaint (problem as
unplanned interruption to a product service or reduction in its quality) initiated by
the customer, analyzes it to identify the source of the issue, initiates resolution,
monitors progress and closes the trouble ticket.
7. Complaint-to-solution: This process deals with a complaint (a customer inquiry
in which the customer is not pleased with a product or the handling speed of an
inquiry problem) initiated by the customer, analyzes it to identify the source of the
issue, initiates resolution, monitors progress and closes the trouble ticket.
Network Centric
1. Production Order-to-acceptance: This process manages the provisioning and
termination process, starting from the feasibility check and ending with the
activation of services and resources.
2. Trouble Ticket-to-solution: This process is either triggered internally through a
service or resource alarm, or externally, through a trouble ticket generated based
on a complaint of a customer.
3. Activation-to-Usage Data: This process focuses on the enabling of usage, the
collection of usage records and the monitoring of performance criteria.
43
4. Capacity Management: This process aims to ensure the timely and cost-efficient
provisioning of the accurate capacity of services and components.
5. Service Lifecycle Management: This process defines, plans, designs and
implements all services in order to support the introduction, operations and
retirement of market products.
6. Resource Lifecycle Management: This process defines, plans, designs and
implements all resources in order to support the introduction, operations and
retirement of market products.
The TM Forum Frameworx will form the basis of the solution requirements. The content of
this RFP focuses on requirements that are specific to Broadband Infraco’s operating model
as listed in the Appendix A_Input_Functional Requirements v1.0.xlsx
1.5 Overall Broadband Infraco transformation scope as use cases
Use case identification forms the basis of high level Broadband Infraco solution requirements
scoping. The identified use cases together with their correlation to high level Broadband
Infraco solution requirements and scoping in terms of Frameworx components is
documented in Appendix B_Input_UseCases v1.0.xlsx .
1.6 Use case Descriptions
The use case descriptions illustrate the scope of each identified use case. The use case
description encompasses the business goals and the involved processes, information and
logical applications. It is formalized with a literal description combined with a high level
footprint of business activities and information manipulated within respectively the Business
Process Framework, Information Framework and Application Framework. The full
description for each use case is provided in Appendix C_Input_UC descriptions v1.0.docx
1.7 Use case interrelations
An outlook of use case interrelations is illustrated in the figure below.
Figure 4: Use Case Interrelations Example
uc UC Dependencies B_01_Inv oice Customer
«fxUseCase»
B_01_Inv oice
Customer
(from B_03_Collect
Customer Payments)
«fxUseCase»
B_03_Collect
Customer Payments
(from B_02_Determine
Price Charges)
«fxUseCase»
B_02_Determine
Price Charges
(from B_06_Manage
Compensation)
«fxUseCase»
B_06_Manage
Compensation
«extend»
«extend»
«extend»
44
The full interrelations between use case is provided as a table in Appendix
B_Input_UseCases v1.0.xlsx
1.8 Overall Functional requirement platforms architecture
Taken all together the UC Families form the Broadband Infraco functional requirement
platform.
Figure 5: Functional Requirement Platform
1.9 The project Phase scoping along Use Case prioritization
UC Family Use Case Name Use Case
Priority
Assurance
A_01_Manage Customer Problem
1
A_02_Manage Service Trouble 1
A_03_Manage Resource Trouble 1
A_04_Manage S/P Trouble 1
A_05_Manage Customer SLA 1
A_06_Manage ServIce Quality 1
A_07_Manage Resource
Performance 1
Customer Relationship
CR_01_Manage Customer Interaction
CR_02_Manage Customer Self-Service
CR_03_Manage Customer Data
Fulfillment
F_01_Establish Customer Offer
F_02_Check Feasibility
F_03_Design Customer Solution
F_04_Deliver Customer Order
F_05_Deliver Service Order
F_06_Deliver Resource Order
Billing
B_01_Invoice Customer
B_03_Collect Customer Payments
B_04_Manage Customer Debt
B_05_Manage Bill Inquiry
B_06_Manage Compensation
Assurance
A_01_Manage Customer Problem
A_02_Manage ServIce Trouble
A_03_Manage Resource Trouble
A_04_Manage S/P Trouble
A_05_Manage Customer SLA
A_06_Manage ServIce Quality
A_07_Manage Resource Performance
A_08_Manage S/P Performance
A_09_Collect & Distribute Performance & Usage Data
Enterprise Management
EM_01_Manage Field Forces
EM_02_Manage Logistics
EM_03_Manage Finances
EM_04_Manage Asset
EM_05_Manage Procurement
EM_06_Manage Human Resources
Supply Chain Management
SC_01_Manage S/P Engagement
SC_02_Manage S/P Contract
SC_03_Deliver S/P Requisition Order
Portfolio Lifecycle Management
PLM_01_Innovate & Retire Product Offering
PLM_02_Innovate & Retire Product Technology
PLM_03_Manage Offering Portfolio
PLM_04_Manage Technical Portfolio
PLM_05_Manage Portfolio Lifecycle
PLM_06_Manage Offering Capabilities
PLM_07_Manage Infrastructure Capabilities
PLM_08_Plan Marketing Communication & Promotions
PLM_09_Fulfill Marketing Communications & Promotions
SC_04_Manage Supplier Payments
B_02_Determine Price Charges
45
A_08_Manage S/P Performance 1
A_09_Collect & Distribute
Performance & Usage Data 1
Billing B_01_Invoice Customer 1
B_06_Manage Compensation 1
Customer
Relationship CR_03_Manage Customer Data 1
Enterprise
Management EM_01_Manage Field Forces 1
Customer
Relationship
CR_01_Manage Customer
Interaction 2
Fulfillment
F_01_Establish Customer Offer 1
F_02_Check Feasibility 1
F_03_Design Customer Solution 1
F_04_Deliver Customer Order 1
F_05_Deliver Service Order 1
F_06_Deliver Resource Order 1
Billing
B_02_Determine Price Charges 1
B_03_Collect Customer Payments 1
B_04_Manage Customer Debt 1
B_05_Manage Bill Inquiry 1
Customer
Relationship
CR_02_Manage Customer Self-
Service 3
Table 3: Use Cases Priorities
The use case priorities are provided as a table in Appendix B_Input_UseCases v1.0.xlsx
2 BROADBAND INFRACO OPERATING MODEL IT COMPONENT ARCHITECTURE
REQUIREMENT
2.1 Overall Functional IT Architecture
The following section provides a functional architecture from systems perspective and
identifies in terms of functional building blocks, of TAM applications framework and the
functional scope of the targeted information architecture SID.
The relevant TAM applications framework have been identified based on the functional scope
of the identified use cases. This scoping allows ensuring completeness insofar as the
46
functionalities required covering the functional scope of the identified use cases will be
covered by one of the identified TAM applications framework. But in the other direction, this
functional information architecture SID defined as TAM applications framework does not imply
that every single sub-application and functionality defined within a TAM application framework
is required to fulfil the identified use cases.
The respondent shall use the scoped TAM application to scope and reference the
functionalities of the applications of the offered solution.
The figure below provides an overview of the functional information architecture SID:
Figure 6: Functional information architecture (SID)
The scoping of TAM level 1 applications per use case and the grouping in platforms and
phases is provided in Appendix D_Input_Functional Architecture v1.0.xlsx
The next section is introducing, defining the platforms (architectural building blocks) and will
position more specifically in terms of comments the scoped level-1 TAM applications within
those platforms.
2.1.1 Customer Management Platform:
2.1.1.1 Overall Description
Core business platform for the customer-facing Broadband Infraco’s operations. Covers
CRM and Order Management across all interaction channels.
Network Management Platform Billing Platform
Enterprise Management Platform
Integration Infrastructure
Customer Management Platform
4.2 Product Catalog Management
3.5 Corporate Sales Management
5.1 Customer Information Management
5.2 Transactional Document Production
5.3 Customer Order Management
5.6 Customer Service Representative Toolbox
5.8 Customer Problem Management
5.5 Customer Contact Management, Retention & Loyalty
5.4 Customer Self Management
5.18 Customer SLA Management
5.17 Case Management
5.9 Receivables Management
5.10 Billing Inquiry, Dispute & Adjustment Management
5.11 Bill Format / Render
5.13 Billing Account Management
5.14 Collection Management
5.15 Bill Calculation
5.19 Charge Calculation and Balance Management
Service Delivery Platform
6.1 Service Catalog Management
6.3 Service Order Management
7.1 Resource Lifecycle Management(7.1.7 Resource Catalog Management)
7.3 Resource Order Management
6.2 Service Inventory Management
6.5 Service Problem Management
6.9 Service Quality Management
7.2 Resource Inventory Management
7.4 Resource Domain Management
6.8 Service Test Management
6.7 Service Performance Management
7.9 Resource Performance Management
7.1 Resource Lifecycle Management(without 7.1.7)
7.11 Resource Test Management
7.10 Fault Management
7.7 Billing Data Mediation
8.3 Wholesale / Interconnect Billing
Portfolio Lifecycle Management Platform
4.3 Product Lifecycle Management
4.4 Product Performance Management
11.1 Catalog Management
7.12 Workforce Management
8.1 Supply Chain Management
9.2 HR Management
9.3 Financial Management
9.4 Asset Management
Enterprise Service Bus Business Process Management
Data Mapping & Transformation Service Repository
47
2.1.1.2 Comments on identified TAM L1 applications
The requirements of Application framework (TAM) should support the following functional requirements in line with telecommunication framework. The functional requirements are included in Appendix D.
4.2 Product Catalog Management: this TAM application focuses on the portion of the
overall portfolio relevant to the Customer Management Platform: the product definition
and the relationship to its underlying components. It can be seen as a functional subset
of the overall 11.1 Catalog Management TAM applications. In any case, the Product
Catalog requires functional integration with the TAM applications Service Catalog &
Resource Catalog in order to provide an end-to-end consistent and correlated portfolio
catalog.
5.2 Transactional Document Production: although its main application area will be
for billing (as such it could be allocated to the Billing Platform), the usage of this TAM
application in other cases such as offer management for instance should be
investigated.
5.6 Customer Service Representative Toolbox: unlike in the consumer business
where CSRs might manage a customer over its entire lifecycle, Broadband Infraco’s
wholesale business model puts the emphasis on key account management.
Nevertheless, the identification of the CSR toolbox application set highlights the
importance of a common and shared platform to manage the ongoing and the history
of the different types of customer interactions.
5.8 Customer Problem Management / 5.17 Case Management: both TAM
applications relate back to a similar set of functionalities, with Case Management being
more generic and covering all types of inquiries and Customer Problem Management
being more focused on the “Incident Management” use case. In the overall solution,
these applications will require interfacing/integration with Billing Inquiry Handling /
Service Problem / Fault Management
2.1.2 Service Delivery Platform:
2.1.2.1 Overall Description
Platform to manage the provisioning and delivery of the communications and network
services offered by Broadband Infraco on a wholesale basis. Interacts with the network
infrastructure platforms to configure and activate network-based services
2.1.2.2 Comments on identified TAM L1 applications
The requirements of Application framework (TAM) should support the following functional requirements in line with telecommunication framework. The functional requirements are included in Appendix D.
6.1 Service Catalogue Management / 7.1.7 Resource Catalogue Management: see
PLMP / 11.1 Catalogue Management.
48
6.3 Service Order Management / 7.3 Resource Order Management: seen together
cover the scope of technical order management.
2.1.3 Network Management Platform:
2.1.3.1 Overall Description
Platform for network operations management of the Broadband Infraco network infrastructure
assuring service availability and performance across all technologies. Manages the physical
aspects of the Broadband Infraco’s networks and provides a consolidated view on the different
technology layers, equipment’s and transmission links of the Broadband Infraco’s networks.
2.1.3.2 Comments on identified TAM applications
The requirements of Application framework (TAM) should support the following functional requirements in line with telecommunication framework and they are in Appendix D:
6.2 Service Inventory Management / 7.2 Resource Inventory Management: both
TAM applications relate back to a similar set of functionalities and considered together,
they provide an end-to-end consistent and correlated view on the technical inventory
of Broadband Infraco supporting top-down and bottom-up correlation. In the overall
solution, these TAM applications might be implemented as an integrated application
or a set of discrete applications.
6.7 Service Performance Management / 6.9 Service Quality Management / 7.9
Resource Performance Management: those TAM applications cover a similar set of
functionalities over the Service & Resource layers. In the overall solution, these TAM
applications might be implemented as an integrated application or a set of discrete
applications.
6.5 Service Problem Management / 7.10 Fault Management: those TAM
applications cover a similar set of functionalities over the Service & Resource layers.
In the overall solution, these TAM applications might be implemented as an integrated
application or a set of discrete applications.
6.8 Service Test Management / 7.2 Resource Test Management: those TAM
applications cover a similar set of functionalities over the Service & Resource layers.
In the overall solution, these TAM applications might be implemented as an integrated
application or a set of discrete applications.
7.1 Resource Lifecycle Management: given its focus on managing network and IT
capacity, this TAM application is primarily allocated to the Network Management
Platform. But it also includes 7.1.7 Resource Catalog Management, which has been
allocated together with 6.1 Service Catalog Management to the Service Delivery
platform. Together they can be seen as a functional subset of the overall 11.1 Catalog
Management TAM application providing a catalog definition over the Service &
Resource layers, integrated with 4.2 Product Catalog for an end-to-end Portfolio
Catalog definition.
49
7.4 Domain Management: this TAM application identifies a set of functionalities which
are already covered by some other “discrete” TAM application (e.g. 7.4.1 Resource
Discovery vs. 7.2 Resource Inventory). The focus of 7.4 Domain Management is not
to duplicate any of those functionalities but to ensure consistency and agnosticism of
these functionalities across the various technical infrastructures.
2.1.4 Billing Platform:
2.1.4.1 Overall Description
Platform for the collection of appropriate usage records, production of customer bills, for
providing pre-bill use information and billing to customers, for processing their payments, and
performing payment collections. In addition, it handles customer inquiries about bills and
supports the resolution of billing problems.
Platform for the collection of appropriate multiple customer billing records, production of
customer bills, for providing pre-bill use information and billing to customers, for processing
their payments, and performing payment collections. The solution should be able to generate
customer invoices in different customer location such as regional, provincial and district area,
this include type of customer categories, e.g. education centers, police stations, etc. In
addition, it handles customer inquiries about bills and supports the resolution of billing
problems.
2.1.4.2 Comments on identified TAM L1 applications
The requirements of Application framework (TAM) should support the following functional requirements in line with telecommunication framework as outlined in Appendix D:
5.9 Receivables Management / 5.14 Collection Management: These L1 TAM
applications present a set of functionalities linked with the financial management of
accounts receivables. As such they might, in the overall solution, be implemented in
combination with other financial functionalities (see 9.3 Financial Management) in an
integrated financial application (ERP application suite).
5.19 Charge Calculation and Balance Management: this L1 TAM application has
two sub-applications: 5.19.1 Charge Calculation & 5.19.2 Balance Management.
Charge Calculation may be as simple as direct application of a price to an event (flat
fee) or may be more complex, involving a combination of price and other factors
(usage). For the current Broadband Infraco portfolio, flat fee charging capabilities are
sufficient, but for future portfolio extensions, usage based charging is an expected
capability. As far as Balance management is concerned, this group of functionalities
typically refers to the balance management for pre-paid services or spending / usage
limits on post-paid customer and are as such, not required for the Broadband Infraco
wholesales portfolio.
7.7 Billing Data Mediation: the current Broadband Infraco wholesale portfolio does
not require usage based billing, but the application architecture must support the
introduction of this capability to accommodate future portfolio extensions.
50
8.3 Wholesale / Interconnect Billing: the introduction of this capability is finally
planned yet, but should be covered at least as an option in the solution design.
2.1.5 Integration Infrastructure
2.1.5.1 Key architectural principles
Loose coupling: introduce agility by decoupling the business-driven process layer
from the technology-driven application layer. This is achieved by introducing
services/interfaces between the process and application layers that are loosely
coupled to both and separate business process control of the critical business logic
from the individual applications.
Contract Interfaces: applications to present open contract interfaces that allow for
business process control. Contracts express the purpose and the capabilities of the
service/interface as well as the rules governing the usage of the service/interface, the
specific conditions necessary to invoke the service, and the terms of information
exchange with the service.
Common Communication Vehicle: a common platform for inter-application
communication accommodating the various application interfaces enabling loose
coupling to applications. Loose coupling is further enforced by the use of a common
data model for inter-application information exchange.
Use of Standards: standards are to be used at every level of the integration
infrastructure: standard process framework (e.g. eTOM) for process definition,
standard information framework (e.g. SID) for common data model, standardized
interfaces (e.g. OSS/J, MTOSI, ), standard technologies/protocols (SOAP, WSDL,
JAVA, BPEL, …)
51
2.1.5.2 Functional Overview
The proposed solution should adopt a systems approach which is the same or similar to the
one depicted in the figure below.
Figure 7 : Integration Infrastructure Functional Overview
2.1.5.3 Building blocks definitions
Business Process Management: following capabilities are typically expected from a
BPM infrastructure:
Process Designer – used to design and validate process definitions (process
flows & business rules) that may be composed of both manual activities and
automated activities. Automated activities orchestrate the defined services /
interfaces
Process & Rules Engine – run-time environment instantiating process flows &
business rules
Activity Monitor – provides access to status and performance metrics on the
execution of processes
Data Mapping & Transformation: a Common Data Model (CDM) spans over all
enterprise applications and data sources integrated in the application platform. Data
Mapping & Transformation manages all mapping & transformation (static and/or rule
based) between interfaces over the enterprise-+wide information exchange model
(CDM). Implementing a specific and functionally isolated data transformation layer is
not mandatory from day one, but it is definitely critical for allowing the architecture to
scale.
Enterprise Service Bus: following capabilities are typically expected from an ESB
infrastructure:
52
Invocation – the ability to call services / interfaces.
Routing – distribute messages according to rules
Mediation – reconcile incompatible protocols and interaction patterns of
disparate connected applications and systems
Messaging – provide an infrastructure to ensure that messages are passed and
exchanged between applications and systems
Quality of Service – security, reliability or transaction handling.
Management – monitoring, administration, audit and logging.
Service Repository: in a SOA implementation, the Service Repository is a key
component supporting service discoverability and reusability. It is a directory that
contains information about the available services. It is the functional component used
to discover and locate existing services. It is also a key enabler for SOA governance
and service lifecycle management since one of the prerequisites for a service to be
extended is that it can be discovered and identified as a candidate for extension.
2.1.6 Existing Broadband Infraco infrastructure
2.1.6.1.1 CRM
# APPLICATION Scope
1 VTiger CRM (only Trouble Ticketing currently used for internal purpose)
Table 4: Existing Infrastructure CRM
2.1.6.2 Network Operation Centre Systems
# APPLICATION Scope
2
Coriant
Telecommunication
Network
Management
System
Configuration and fault management of Coriant network elements
3 ZTE Netnumen Configuration and fault management of ZTE network elements
4 Timepictra –
Symmetricom Configuration and fault management of synchronisation elements
5 Open NMS Fault and performance monitoring (open source)
6
Environmental
Alarm System –
ECS (INALA)
Configuration and fault management of the environmental alarm
units
53
7
JDSU ONMS
(Remote Fiber
Testing System)
Configuration and fault management of the JDSU OTDR elements
8 Cacti Network management of the Cisco routers
9 Rancid Configuration management (open source)
10 TACACS + Access control (open source)
Table 5: Existing Infrastructure Network Operation Center Systems
2.1.6.3 Corporate IT Systems
# APPLICATION Scope
11 MS Active
Directory Directory services
12 MS Exchange Messaging
13 Pure Message Content filtering
14 Pastel Evolution Procure to pay
15 Remedy Asset management
16 Mapinfo Drawings
17 Sophos Antivirus
18 Sharepoint Internet and document management
19 VIP People HR Payroll
20 ISA/ OWA Email firewall
21 WSUS Windows updates
Table 6: Existing Infrastructure Corporate IT Systems
2.2 Statement of Compliance
The documents attached as Appendices must be used to indicate compliance with each
requirement. The additional information provided with a response and/or solution must
show how the requirement is satisfied. The list of Appendices is indicated in Table 1.
3 SOLUTION DELIVERY METHODOLOGY
The respondent’s solution delivery methodology is an important component of the Broadband Infraco transformation program and a key evaluation criterion for both the present RFP and the upcoming RFPs.
54
The respondent’s solution delivery methodology will be initiated by a handover of specifications elaborated on the base of Broadband Infraco’s business requirement engineering methodology as described previously. The business analysis and architectural governance model (UC model, Business Activity Model, Business Entity Model, Platform Independent Model) form the base of these specifications along the various Broadband Infraco architectural layers
Business & organization Layer
Information Layer
Integration Layer
Technology and Application
Beyond providing specifications for the solution to be delivered, the Business Analysis and Governance Model support the Broadband Infraco architectural guidance and governance principle accompanying the solution delivery methodology steps along each of the architectural layer mentioned above.
Figure 8: Broadband Infraco Architectural Governance and Solution Delivery
Methodology
In this context, it is expected that the respondent employs not only a well-defined solution delivery methodology similar to the one illustrated in the figure below but also that the respondent solution delivery methodology enables and eases Broadband Infraco architectural guidance and governance in order to enable the top-down and bottom-up consolidation in the Business Analysis and Architectural Governance Model.
customercustomercustomercustomer customer
Use case
Model
Business
Streams
Req.Req.Req.Requirements.Req.Requirements.Req.eq.Req.Requirements.
Driver
Enabler
Business
Activity
Business
Role
Business
Entity
Business
Service
Interface
Application
So
lutio
n D
eliv
ery
Me
tho
do
log
y
BB
I Arc
hite
ctu
ral G
uid
an
ce &
Go
ve
rna
nc
e
Integration
Information
Business
Organization
Technology
-
Application
Phase 1
Phase 2
Phase 3
Phase n
55
BROADBAND INFRACO Architectural Guidance and
Governance
Handover consolidated requirements to selected vendors
o Technical requirements
o Functional requirements
o Integration requirements
o Information exchange data model
Define implementation guidelines
Organizational alignment recommendations
↓ ↓ ↓ ↓ ↓
BROADBAND INFRACO Solution
Implementation and Deployment ↓ ↓ ↓ ↓ ↓ ↓
Org
an
iza
tio
n L
ay
er
Bu
sin
es
s L
ay
er
Info
rma
tio
n L
ay
er
Inte
gra
tio
n L
ay
er
Tec
hn
olo
gy
& A
pp
lic
ati
on
Lay
er
Vendor Solution Design step
Tec
hn
olo
gy
ma
nag
em
en
t
Qu
ality
ma
nag
em
en
t
Tra
inin
g &
Kn
ow
led
ge m
an
ag
em
en
t
Pro
gra
m/ p
roje
ct M
an
ag
em
en
t
Ac
co
un
t / En
ga
ge
me
nt M
an
ag
em
en
t
Allia
nc
e / v
en
do
r Ma
nag
em
en
t
Platform dependent Solution Architecture
design
Technical Architecture design
Interface specification design including
service contract
High level design including process design
as orchestration of services / interfaces and
supporting components
Test case based on use cases
Migration mapping & modelling
Migration script design
Solution development
Vendor Solution Development step
Low level design
Customization and configuration
Integration with internal /external systems
Business Activity Model
(BAM):
Business Entity Model
(BEM):
Business Role Model
(BRM):
Business Analysis and
Governance Model
Use Case Model
56
Figure 9: Solution Delivery Methodology Outlook
Unit test
Migration script built
Vendor Solution Test step
System integration testing
Performance Testing
User Acceptance Test
Package and release
Iterative testing
Dry Run
Solution sign-off
Vendor Solution deployment step
Pre- release preparation notes
Cut-over & go live
Post production and parallel run
Warranty
Cut-over set up & pre-migration preparation
Migration execution
BROADBAND INFRACO Organizational
alignment
Deploy organizational alignment
Document end to end processes including
manual activities
Redefine tasks and responsibilities (job
descriptions)
Training
Acceptance
Business ActivityModel (BAM):
Business EntityModel (BEM):
Business RoleModel (BRM):
Business Analysis and Governance Model
Business
ServiceApplication
Use Case Model
57
4 EXPECTED RESPONSE STRUCTURE
In addition to generic response requirements defined in the commercial section of this RFP
(e.g. company profile, NDA, BBBEE …), this section describes the specific response
requirements and structure to the present RFP. All listed sections are compulsory. The
respondent might, if deemed necessary, extend the structure with additional sections, but will
not allocate required responses / information to sections different than those specified.
4.1 Section: High level solution architecture
4.1.1 Sub-section: High level solution description
The respondent shall present the offered solution, providing at least:
High level solution description
Description of involved applications
Mapping to defined platforms (a deviation to the defined platform structure is
acceptable if motivated properly)
Break-down to phases clearly defining which applications / application modules are
part of which phase
Description of how the proposed solution / solution alternatives address the core
transformation objectives & business goals
Note that respondents are welcome to provide various solution options in different
combination of best of breed versus integrated solutions versus open source.
4.1.2 Sub-section: Functional requirements
Using the provided template (Appendix E Consolidated Response Template), the
respondent shall present the conformance to the functional requirements, addressing:
applications involved in use cases
coverage of use cases and functional requirements
eTOM conformance per application
API compliance
The response template is a key element to the RFP response and every worksheet is
compulsory. The respondent might, if necessary, complement the template with additional
information addressing the functional requirements in this sub-section.
Concerning the Frameworx conformance/compliance statements (eTOM, SID, Interfaces),
officially TMforum certified applications (PC – Product Certified) are preferred (in which case
the official certification statements have to be provided). Should the involved applications not
be officially certified, the respondent will self-assess (SA – Self Assessment) the application
58
conformance/compliance level. Furthermore, the respondent will indicate in which timeframe
he plans official TMForum product certification.
4.2 Section: Use Case scenarios
For each use case and over the phases, the respondent shall provide an overview how the
offered solution will address the use case requirements and the related functional
requirements. This section comes in addition to the use case coverage with the response
template and shall at least:
Define how the applications involved in the use case address the requirements
Provide a good understanding of the level of automation (manual, semi-automated,
automated) for the relevant activity groups
Explain the potential intermediate solutions due to a phased introduction of required
applications
The attention of the respondent is drawn to the fact that not every use case requirement or
related functional requirement has to be entirely automated. Manual or semi-automated
activities are acceptable insofar as the overall solution ensures qualitative and economical
operations.
4.3 Section: Integration Architecture
4.3.1 Sub-section: Integration architecture
The respondent shall demonstrate how the proposed solution and integration approach
provisions for scalability (dimensioning, geographical distribution …), modularity (standalone,
replaceable components …) flexibility (new or changed applications, technologies, and
requirements) and agility (ability to rapidly adapt to a changing environment).
In this section, the respondent will specifically address the principles to be covered by the
integration infrastructure:
Loose coupling: introduce agility by decoupling the business-driven process layer
from the technology-driven application layer. This is achieved by introducing
services/interfaces between the process and application layers that are loosely
coupled to both and separate business process control of the critical business logic
from the individual applications.
Contract Interfaces: applications to present open contract interfaces that allow for
business process control. Contracts express the purpose and the capabilities of the
service/interface as well as the rules governing the usage of the service/interface, the
specific conditions necessary to invoke the service, and the terms of information
exchange with the service.
Common Communication Vehicle: a common platform for inter-application
communication accommodating the various application interfaces enabling loose
59
coupling to applications. Loose coupling is further enforced by the use of a common
data model for inter-application information exchange.
Use of Standards: standards are to be used at every level of the integration
infrastructure: standard process framework (e.g. eTOM) for process definition,
standard information framework (e.g. SID) for common data model, standardized
interfaces (e.g. OSS/J, MTOSI,), standard technologies/protocols (SOAP, WSDL,
JAVA, .NET. BPEL, …)
4.3.2 Sub-section: Interface Overview
For the applications involved in the offered solution, the respondent shall list the available
pre-existing interfaces/services, describing:
Providing application
Functional description
Technical information (protocol, …)
Context (typical consumer application, …)
Furthermore, for each of the applications involved, the respondent shall qualify the approach
and reached degree of coupling (coupling is the degree of interaction among interfaces /
services or business process logic invoking the interfaces / services) and cohesion (cohesion
is the degree of interaction among the parts that make up an interface/service) for the pre-
existing interfaces / services.
According to TMForum GB942U, the types of cohesion from highest (best) degree to the
lowest (worst) degree are:
Functional Cohesion – a Business Services performs exactly one action or achieves a
single goal
Informational Cohesion – a Business Service performs a number of actions, each action
with its own entry point, each action independent from the others, all performed on the
same data structure
Communicational Cohesion – a Business Service performs a series of actions related by
the sequence of steps to be followed, and also all actions are performed on the same data
Procedural Cohesion – a Business Service performs a series of actions related by the
sequence of the steps to be followed by the Business Services
Temporal Cohesion – a Business Service performs a series of actions related by time
Logical Cohesion – a Business Service performs a series of related actions, one of which
is selected by the calling Business Services or business process
Coincidental Cohesion – a Business Service performs multiple unrelated actions, or
actions cannot be defined
The types of coupling from lowest (best) degree to the highest (worst) degree are
Data Coupling – all inputs/outputs are homogenous data types
60
Stamp Coupling – inputs/outputs include complex data structures, but
a Business Service operates only on some of the pieces during one
execution of the Business Services
Control Coupling – a control element is passed to a Business Service,
that is, one Business Service or business process explicitly controls the
logic of another
Common Coupling – multiple Business Services have access to the
same global data
Content Coupling – one Business Service directly references the
contents of another
4.3.3 Sub-section: Non-functional requirements
The respondent shall demonstrate how the solution addresses the non-functional
requirements
4.3.4 Sub-section: Integration of existing Broadband Infraco applications
The respondent shall describe which and how existing Broadband Infraco systems are
planned to be integrated in the offered solution.
Note that it is not required for every existing Broadband Infraco application to be integrated
into the final solution design. The respondent will motivate the reasons for integrating /
replacing existing Broadband Infraco applications and provision for the integration cost in the
solution pricing.
4.4 Section: Methodology, Skills & Experiences
The purpose of this section is to allow the respondent to demonstrate the efficiency and
effectiveness of its solution delivery methodology as well as its capability to enable and ease
Broadband Infraco’s architectural guidance and governance. This aspect is of particular
importance to enable the top-down and bottom-up consolidation of the solution in the Business
Analysis and Architectural Governance Model.
4.4.1 Solution Delivery Methodology
In this section, the respondent shall describe its solution delivery methodology covering the
various steps identified in the section 3 Solution Delivery Methodology.
Along this description the respondent should particularly describe its approach regarding the
handling of Broadband Infraco’s consolidated requirement handover. Respondent should also
state its capability to provide along the deployment of its methodology the necessary
Frameworx based documentation along the 4 architectural layers of its solution
Business layer
Information and Data Layer
Integration Layer
Technology& application Layer
61
The respondent can accompany such statement by providing examples illustrating one or more of the following items:
Respondent proprietary use cases: flow description on the base of with mapping of
business activities to lowest existing business process framework process element
l1/l2/l3/l4, identification of business entities manipulated by each business activities
along the information framework)
Proprietary data mapping to Information Framework business entities , identification
of new business entities if any
Platform dependent solution architecture design / technical architecture design
(mapping to the application framework logical area l1/l2 /l3 and functionalities)
Service and interface specification design including service contract (mapping to
each framework: business process, information and application framework)
4.4.2 Skills & Experiences
In this section, the respondent shall demonstrate based on reference projects that he brings
sufficient skills and experience (potentially together with his partners) in order to manage
successfully such a business and systems transformation program.
In terms of TMForum expertise, the respondent should also:
state membership of their company and partner companies
state the number and list of TMForum certified personnel available in its
organization.
For global organizations, it is mandatory to indicate if the entire skill set required to conduct
this transformation program, and specifically the integration activities, is available locally. If
not, it has to be clearly defined how resources and expertise of other regions/partners will be
included in the transformation program.
Global organizations shall also specify the level of involvement of the local organization in
the reference projects and their relevance in terms of expertise for the present
transformation program.
4.5 Section: Pricing & Timeline
For each phase, the respondent shall provide detailed pricing information and estimated
timelines.
The price should be at least broken down and detailed into following components:
Hardware (covering the different operating environments)
Software / licenses
Note: a detailed license plan covering one time / recurring prices as well as the
62
licensing structure (per user, element, node …) is required. The software /
licenses shall cover the different operating environments.
Training
Maintenance (the underlying maintenance and support contract shall be provided)
Integration
Beyond the scope of delivery of the current RFP, the respondent shall define the pricing for
onsite and remote professional services.
The respondent is furthermore expected to provide for each phase an estimated timeline
with a draft project plan indicating clearly key milestones.
4.6 Broadband Infraco service oriented business requirement engineering
methodology
Steering of “loose coupling” and “cohesion” over the Broadband Infraco’s transformation
program, where each phase of the program delivers tangible business value and builds on
each other, is key to establish the Broadband Infraco’s operating model as a stable and flexible
execution platform. In order to achieve this, each phase consists in an architectural partition
and is tackled in an iteration built upon the 4 architectural views of the TMForum Frameworx
solution development lifecycle:
Business view aiming to capture the Broadband Infraco business stakeholders
business requirements
System view aiming to provide clear specification for the solution to implement and
deploy
Implementation view aiming to build the solution
Deployment view to deploy the solution
63
Figure 10: The 4 views of TMForum Frameworx Lifecycle
These 4 architectural views represent the underlying modeling approach of business
capabilities along the following project steps:
Business requirement scoping
Business requirement analysis
Vendor evaluation and selection
Solution implementation and deployment.
Each of these projects steps relates to the 4 views to ensure the development and
implementation of Broadband Infraco’s business and systems solutions. These business
and systems solutions can be a manual, semi-automated or fully automated orchestration
of these business capabilities.
Figure 11: Mapping to Broadband Infraco Project Steps
The implementation is illustrated here below along the Broadband Infraco transformation
program.
Business
View
Systems
View
Deployment
View
Implementation
View
Logical layer
Physical layer
Stakeholders:
business teams, business analyst
Stakeholders:
users,operations
Stakeholders:
development, implementation
Stakeholders:
IT architects,modeler
Business
Req.
Scoping
Vendor Evaluation
and Selection
Business Requirement Analysis
Solution implementation and deployment
64
Figure 12: RFI & RFPs Approach
Along the Broadband Infraco transformation program, use cases are used to qualify, describe and specify Broadband Infraco’s business operations associated to each Broadband Infraco architectural partition/phase.
The use case is an artifact used to specify the expected behavior of a system. Considering Broadband Infraco in one of its transformation phases as a system, the use case allows capturing the Broadband Infraco’s (non) functional requirements and describes what the system does in terms of actions (business activities referenced to the Business Process Framework) manipulating information (Business Entities referenced to the Information Framework) performed by a given system that produces results of interest for a given actor (business role referenced to the Business Process Framework). As such, each use case aims to specify one or more business capabilities of the analyzed system (transformation phase). Use cases act as functional specifications for the target application (referenced to the Application Framework) supporting the system behavior.
In the Broadband Infraco business and systems transformation, the architectural partition/phase is considered as a system of interest for a given phase. Therefore, a set of use cases is required to cover the entire scope of business requirements associated to each phase. This set of use cases referred to as Broadband Infraco use case model ensures the traceability of business requirements from their capture in the business requirement scoping step up to their morphing, phase after phase, into clear specification for service oriented business capabilities to design, implement and deploy across the manual and computed Broadband Infraco’s environment.
The Business Requirement Scoping aims to identifying the entire set of use cases to be tackled within the Broadband Infraco’s transformation program. The core deliverables of this step are:
the capture of the Broadband Infraco high level requirements classified along high
level business context (TMForum business stream GB921E) and Business Process
Framework L2 core processes as well as the identification of key (internal & external)
stakeholders
the listing of use cases to be addressed in the scope of the Broadband Infraco’s
transformation program. In order to avoid duplicated work in the specification exercise
over the transformation program and more importantly to instill re-usability and
High level requirements & Use case identification
UC
design
Phase 1 Phase 2 Phase 3
RFP
Imple-
menta-tion
RFI
(OSS/BSS/ERP)UC
design
RFP
Imple-
menta-tion
UC
design
RFP
Imple-
menta-tion
1
3 4.1 4.2 4.3
Busi ness View Syst ems Vi ew
Depl oyment View I mpl ementat ion View
Logical layer
Physical layer
St akeholder s: business t eams, business analyst
St akeholder s:
user s,oper at ions
St akeholder s:
development ,
implement at ion
St akeholder s: I T ar chit ects,
m odeler
Business
Req. Scoping
Vendor Evaluation
and Selection
Business Requirement Analysis
Solution implementation and
deployment
Busi ness View Syst ems Vi ew
Depl oyment View I mpl ementat ion View
Logical layer
Physical layer
St akeholder s: business t eams, business analyst
St akeholder s:
user s,oper at ions
St akeholder s:
development ,
implement at ion
St akeholder s: I T ar chit ects,
m odeler
Business
Req. Scoping
Vendor Evaluation
and Selection
Business Requirement Analysis
Solution implementation and
deployment
Busi ness View Syst ems Vi ew
Depl oyment View I mpl ementat ion View
Logical layer
Physical layer
St akeholder s: business t eams, business analyst
St akeholder s:
user s,oper at ions
St akeholder s:
development ,
implement at ion
St akeholder s: I T ar chit ects,
m odeler
Business
Req. Scoping
Vendor Evaluation
and Selection
Business Requirement Analysis
Solution implementation and
deployment
Busi ness View Syst ems Vi ew
Depl oyment View I mpl ementat ion View
Logical layer
Physical layer
St akeholder s: business t eams, business analyst
St akeholder s:
user s,oper at ions
St akeholder s:
development ,
implement at ion
St akeholder s: I T ar chit ects,
m odeler
Business
Req. Scoping
Vendor Evaluation
and Selection
Business Requirement Analysis
Solution implementation and
deployment
Business
requirement scoping
Business
requirement analysis
Vendor
evaluation & selection
Solution
implementation & deployment
Use case definition + Prioritization
2
65
modularity of the business capabilities to develop, each use case identifies a
meaningful, autonomous, re-usable and compassable function supporting one and
more business streams.
Business Requirement Analysis documents use cases (in the use case model) as flows of Broadband Infraco business activities involving Broadband Infraco business roles, manipulating Broadband Infraco business entities, and mapped to logical application areas. These application areas scope the physical applications to be integrated in the distributed computing environment. This set of logical application is referred to as functional IT architecture.
On the base of the identified use case the business analysis step is twofold. It encompasses:
1. An overall high level analysis and phase definition aiming to the following
deliverables :
Use Case Description : describing each use case (high level description) as
well as their TMForum Frameworx footprint
Use Case Interrelations : organizing and structuring the use case model
along their interrelation
Phase qualification: qualifying the Broadband Infraco transformation phase
along consistent use cases grouping forming the architectural partition of
interest.
Phase periodization: priories the various phases
Functional requirement platform: organizing the use case in functional
platforms (referenced to the business process framework) to be addressed
along each phases
Functional IT architecture: organizing the logical application area of interest
in application platforms to be addressed along each phases.
These deliverables form the base for the present Request for Information (RFP)
covering the entire Broadband Infraco transformation program
2. For each phase, a detailed use cases design builds a consistent Business
Analysis Model that will be used to ensure the architectural governance of each
transformation phase. As such the business analysis model forms the base for:
clear specification for the solution to be implemented and deployed,
central architectural governance tool along each holistic Broadband Infraco
architectural layer:
Business and organization
Information & data
66
Integration
Technology and tools.
The business analysis and governance model is the core deliverable of the business analysis
phase and is materialized in a UML (Unified Modelling Language) Model (eg. Enterprise
Architect). It will act as fundamental deliverable for the upcoming Request for Proposals
supporting the final vendor evaluation and selection for each phase. It is organized in different
sections, structuring the functional analysis components into enterprise-wide and reusable
libraries:
Use Case Model: all the Broadband Infraco Use cases documenting (description
/ flow) its business operation
Business Activity Model: the Broadband Infraco library of business activities that
will be orchestrated in the use cases and realized by the application capabilities
Business Entity Model: the Broadband Infraco library of information object and
data manipulated by the Broadband Infraco activities. It is also the semantic and
logical data model that will specify the necessary data transformation/mediation
and messages between applications
Business Role Model: the Broadband Infraco library of roles involved in the
business operations
Platform Independent Model: logical applications defining the functional scope of
each application to be implemented as a set of reusable business capabilities.
During the vendor evaluation and selection the Business Analysis Model will be used as a
business governance tool steering the deployment of the OSS/BSS/ vendor evaluation
strategy, defining the Platform Dependent Model (PDM) and assist the final vendors in their
design.
Along the Implementation and deployment, the Business Analysis Model will further be aligned to the low level design of the selected vendor solution and extended with the following libraries
Platform Dependent Model : physical vendor specific application including an
interface library
Business Capability Library: Business Service Candidates / Interfaces
67
Figure 13: Broadband Infraco Service Oriented Business Requirement Engineering
Methodology
Phase after phase, the Business Analysis is incrementally becoming a business and systems operating governance model documenting the Broadband Infraco’s Enterprise Architecture. Such model referred to as Business Analysis and Architectural Governance Model will be the
Frameworx
Business Requirement Analysis :
Use case description ( literal description / BPF L2 , IF L1 ABE, AFL1 Area, Actors )
Use case interaction + Use case grouping and family
Functional requirement platform
Functional IT architecture
Architectural Partition scoping and phase priorities on the base of BBI Business Goal priorities
UC design
Phase 1 Phase 2 Phase 3
…
RFP
Implementation
RFI UC design
RFP
Implementation
UC design
RFP
Implementation
2
3
4.1 4.2 4.3
BBI Requirements
Req.
Req.
Req.
Req.
Req.
Req.
Req.
Req.
Req.
Requirements.
Requirements.
Requirements.
ProcurementIT Management External Relations
Corporate Mgmt & Business Excellence
Human Resources Management
Finance & Risk Management
Customer
Network
Product
customer customer
Sales & Distribution
Customer Relationship Mgmt
ProductionOrder-to-Acceptance _(PA)
TroubleTicket-to-Solution _(TS)
Usage-to-UsageData _(UU)
Capacity Management _(CAM)
Service LifecycleManagement _(SLM)
Resource LifecycleManagement _(RLM)
ContinuityManagement _(COM)
Decision-to-Relaunch _(DR)
Decision-to-Elimination _(DE)
Marketing
Idea-to-BusinessOpportunity _(IBO)
BusinessOpportunity-to-Launch _(BOL)
Usage-to-Payment _(UP)
Request-to-Change _(RC)
Order-to-Payment _(OP)
Request-to-Answer _(RA)
Termination-to-Confirmation _(TC)
Problem-to-Solution _(PS)
Complaint-to-Solution _(CS)
OperationsStrategy, Infrastructure & product
Enterprise Management
S trateg y&
Co mmi t
In frastru ctu re Lifecycle Man ag emen t
Pro d u ct Li fecycle Man ag emen t
Op eratio n Su ppo rt&
Read in ess
F u l fi l lment Assu ran ce Bi l l in g
S trateg ic & En terp rise P lan ning
F in an cial Asset Man agemen t
E n terp rise Risk Man agemen t
S takeh o ld er & E xtern al Relation s Man agemen t
E n terp rise E ffectiveness Man agemen t
Hu man Reso urces Man agemen t
Kn o wled ge & Research Man agemen t
Marketin g & Offer Man agemen t
Service Develo p men t & Man agemen t
Reso u rce Develo p ment & Man agemen t
S u p p ly Ch ain Develo pment and Man agemen t
Cu sto mer Relatio nsh ip Man agemen t
Service Man ag emen t & Operations
Reso u rce Man ag emen t & Operations
S u p p l ier / Partner Relationsh ip Man agemen t
Customer
Source: TMF
Business Process
Framework L2 core processes
Business Streams
BBI Business Goals
BBI Business Goals
BBI Business Goals
BBI Business Goals
Business Requirement Scoping: Capture & Classify High level requirements BBI along high level business context and L2 core processes
Use case identification
Network Management Platform Billing Platform
Enterprise Management Platform
Integration Infrastructure
Customer Management Platform
4.2 Product Catalog Management
3.5 M/S Corporate Sales Management
5.1 Customer Information Management
5.2 Transactional Document Production
5.3 Customer Order Management
5.6 Customer Service Representative Toolbox
5.8 Customer Problem Management
5.5 Customer Contact Management, Retention & Loyalty
5.4 Customer Self Management
5.18 Customer SLA Management
5.17 Case Management
5.9 Receivables Management
5.10 Billing Inquiry, Dispute & Adjustment Management
5.11 Bill Format / Render
5.13 Billing Account Management
5.14 Collection Management
5.15 Bill Calculation
5.19 Charge Calculation and Balance Management
Service Delivery Platform
6.1 Service Catalog Management
6.3 Service Order Management
7.1 Resource Lifecycle Management(7.1.7 Resource Catalog Management)
7.3 Resource Order Management
6.2 Service Inventory Management
6.5 Service Problem Management
6.9 Service Quality Management
7.2 Resource Inventory Management
7.4 Resource Domain Management
6.8 Service Test Management
6.7 Service Performance Management
7.9 Resource Performance Management
7.1 Resource Lifecycle Management(without 7.1.7)
7.11 Resource Test Management
7.10 Fault Management
7.7 Billing Data Mediation
7.8 Real-time Billing Mediation
8.3 Wholesale / Interconnect Billing
Portfolio Lifecycle Management Platform
4.3 Product Lifecycle Management
4.4 Product Performance Management
11.1 Catalog Management
7.12 Workforce Management
8.1 Supply Chain Management
9.2 HR Management
9.3 Financial Management
9.4 Asset Management
Enterprise Service Bus Business Process Management
Data Mapping & Transformation
In functional scope of Phase 1
In functional scope, but application introduced in later Phase
Out of functional scope of Phase 1
Service Repository
Network Management Platform Billing Platform
Enterprise Management Platform
Integration Infrastructure
Customer Management Platform
4.2 Product Catalog Management
3.5 M/S Corporate Sales Management
5.1 Customer Information Management
5.2 Transactional Document Production
5.3 Customer Order Management
5.6 Customer Service Representative Toolbox
5.8 Customer Problem Management
5.5 Customer Contact Management, Retention & Loyalty
5.4 Customer Self Management
5.18 Customer SLA Management
5.17 Case Management
5.9 Receivables Management
5.10 Billing Inquiry, Dispute & Adjustment Management
5.11 Bill Format / Render
5.13 Billing Account Management
5.14 Collection Management
5.15 Bill Calculation
5.19 Charge Calculation and Balance Management
Service Delivery Platform
6.1 Service Catalog Management
6.3 Service Order Management
7.1 Resource Lifecycle Management(7.1.7 Resource Catalog Management)
7.3 Resource Order Management
6.2 Service Inventory Management
6.5 Service Problem Management
6.9 Service Quality Management
7.2 Resource Inventory Management
7.4 Resource Domain Management
6.8 Service Test Management
6.7 Service Performance Management
7.9 Resource Performance Management
7.1 Resource Lifecycle Management(without 7.1.7)
7.11 Resource Test Management
7.10 Fault Management
7.7 Billing Data Mediation
7.8 Real-time Billing Mediation
8.3 Wholesale / Interconnect Billing
Portfolio Lifecycle Management Platform
4.3 Product Lifecycle Management
4.4 Product Performance Management
11.1 Catalog Management
7.12 Workforce Management
8.1 Supply Chain Management
9.2 HR Management
9.3 Financial Management
9.4 Asset Management
Enterprise Service Bus Business Process Management
Data Mapping & Transformation
In functional scope of Phase 2
In functional scope, but application introduced in later Phase
Out of functional scope of Phase 2
Service Repository
Network Management Platform Billing Platform
Enterprise Management Platform
Integration Infrastructure
Customer Management Platform
4.2 Product Catalog Management
3.5 M/S Corporate Sales Management
5.1 Customer Information Management
5.2 Transactional Document Production
5.3 Customer Order Management
5.6 Customer Service Representative Toolbox
5.8 Customer Problem Management
5.5 Customer Contact Management, Retention & Loyalty
5.4 Customer Self Management
5.18 Customer SLA Management
5.17 Case Management
5.9 Receivables Management
5.10 Billing Inquiry, Dispute & Adjustment Management
5.11 Bill Format / Render
5.13 Billing Account Management
5.14 Collection Management
5.15 Bill Calculation
5.19 Charge Calculation and Balance Management
Service Delivery Platform
6.1 Service Catalog Management
6.3 Service Order Management
7.1 Resource Lifecycle Management(7.1.7 Resource Catalog Management)
7.3 Resource Order Management
6.2 Service Inventory Management
6.5 Service Problem Management
6.9 Service Quality Management
7.2 Resource Inventory Management
7.4 Resource Domain Management
6.8 Service Test Management
6.7 Service Performance Management
7.9 Resource Performance Management
7.1 Resource Lifecycle Management(without 7.1.7)
7.11 Resource Test Management
7.10 Fault Management
7.7 Billing Data Mediation
7.8 Real-time Billing Mediation
8.3 Wholesale / Interconnect Billing
Portfolio Lifecycle Management Platform
4.3 Product Lifecycle Management
4.4 Product Performance Management
11.1 Catalog Management
7.12 Workforce Management
8.1 Supply Chain Management
9.2 HR Management
9.3 Financial Management
9.4 Asset Management
Enterprise Service Bus Business Process Management
Data Mapping & Transformation
In functional scope of Phase 3
In functional scope, but application introduced in later Phase
Out of functional scope of Phase 3
Service Repository
Assurance
A_01_Manage Customer Problem
A_02_Manage ServIce Trouble
A_03_Manage Resource Trouble
A_04_Manage S/P Trouble
A_05_Manage Customer SLA
A_06_Manage ServIce Quality
A_07_Manage Resource Performance
A_08_Manage S/P Performance
A_09_Collect & Distribute Performance & Usage Data
Enterprise Management
EM_01_Manage Field Forces
EM_02_Manage Logistics
EM_03_Manage Finances
EM_04_Manage Asset
EM_05_Manage Procurement
EM_06_Manage Human Resources
Supply Chain Management
SC_01_Manage S/P Engagement
SC_02_Manage S/P Contract
SC_03_Deliver S/P Requisition Order
Portfolio Lifecycle Management
PLM_01_Innovate & Retire Product Offering
PLM_02_Innovate & Retire Product Technology
PLM_03_Manage Offering Portfolio
PLM_04_Manage Technical Portfolio
PLM_05_Manage Portfolio Lifecycle
PLM_06_Manage Offering Capabilities
PLM_07_Manage Infrastructure Capabilities
PLM_08_Plan Marketing Communication & Promotions
PLM_09_Fulfill Marketing Communications & Promotions
SC_04_Manage Supplier Payments
Prio 1
Prio 2Out of scope
Prio 3
Customer Relationship
CR_01_Manage Customer Interaction
CR_02_Manage Customer Self-Service
CR_03_Manage Customer Data
Fulfillment
F_01_Establish Customer Offer
F_02_Check Feasibility
F_03_Design Customer Solution
F_04_Deliver Customer Order
F_05_Deliver Service Order
F_06_Deliver Resource Order
Billing
B_01_Invoice Customer
B_03_Collect Customer Payments
B_04_Manage Customer Debt
B_05_Manage Bill Inquiry
B_06_Manage Compensation
B_02_Determine Price Charges
Network Management Platform Billing Platform
Enterprise Management Platform
Integration Infrastructure
Customer Management Platform
4.2 Product Catalog Management
3.5 M/S Corporate Sales Management
5.1 Customer Information Management
5.2 Transactional Document Production
5.3 Customer Order Management
5.6 Customer Service Representative Toolbox
5.8 Customer Problem Management
5.5 Customer Contact Management, Retention & Loyalty
5.4 Customer Self Management
5.18 Customer SLA Management
5.17 Case Management
5.9 Receivables Management
5.10 Billing Inquiry, Dispute & Adjustment Management
5.11 Bill Format / Render
5.13 Billing Account Management
5.14 Collection Management
5.15 Bill Calculation
5.19 Charge Calculation and Balance Management
Service Delivery Platform
6.1 Service Catalog Management
6.3 Service Order Management
7.1 Resource Lifecycle Management(7.1.7 Resource Catalog Management)
7.3 Resource Order Management
6.2 Service Inventory Management
6.5 Service Problem Management
6.9 Service Quality Management
7.2 Resource Inventory Management
7.4 Resource Domain Management
6.8 Service Test Management
6.7 Service Performance Management
7.9 Resource Performance Management
7.1 Resource Lifecycle Management(without 7.1.7)
7.11 Resource Test Management
7.10 Fault Management
7.7 Billing Data Mediation
7.8 Real-time Billing Mediation
8.3 Wholesale / Interconnect Billing
Portfolio Lifecycle Management Platform
4.3 Product Lifecycle Management
4.4 Product Performance Management
11.1 Catalog Management
7.12 Workforce Management
8.1 Supply Chain Management
9.2 HR Management
9.3 Financial Management
9.4 Asset Management
Enterprise Service Bus Business Process Management
Data Mapping & Transformation
In functional scope of Phase 1
In functional scope, but application introduced in later Phase
Out of functional scope of Phase 1
Service Repository
Network Management Platform Billing Platform
Enterprise Management Platform
Integration Infrastructure
Customer Management Platform
4.2 Product Catalog Management
3.5 M/S Corporate Sales Management
5.1 Customer Information Management
5.2 Transactional Document Production
5.3 Customer Order Management
5.6 Customer Service Representative Toolbox
5.8 Customer Problem Management
5.5 Customer Contact Management, Retention & Loyalty
5.4 Customer Self Management
5.18 Customer SLA Management
5.17 Case Management
5.9 Receivables Management
5.10 Billing Inquiry, Dispute & Adjustment Management
5.11 Bill Format / Render
5.13 Billing Account Management
5.14 Collection Management
5.15 Bill Calculation
5.19 Charge Calculation and Balance Management
Service Delivery Platform
6.1 Service Catalog Management
6.3 Service Order Management
7.1 Resource Lifecycle Management(7.1.7 Resource Catalog Management)
7.3 Resource Order Management
6.2 Service Inventory Management
6.5 Service Problem Management
6.9 Service Quality Management
7.2 Resource Inventory Management
7.4 Resource Domain Management
6.8 Service Test Management
6.7 Service Performance Management
7.9 Resource Performance Management
7.1 Resource Lifecycle Management(without 7.1.7)
7.11 Resource Test Management
7.10 Fault Management
7.7 Billing Data Mediation
7.8 Real-time Billing Mediation
8.3 Wholesale / Interconnect Billing
Portfolio Lifecycle Management Platform
4.3 Product Lifecycle Management
4.4 Product Performance Management
11.1 Catalog Management
7.12 Workforce Management
8.1 Supply Chain Management
9.2 HR Management
9.3 Financial Management
9.4 Asset Management
Enterprise Service Bus Business Process Management
Data Mapping & Transformation
In functional scope of Phase 2
In functional scope, but application introduced in later Phase
Out of functional scope of Phase 2
Service Repository
Network Management Platform Billing Platform
Enterprise Management Platform
Integration Infrastructure
Customer Management Platform
4.2 Product Catalog Management
3.5 M/S Corporate Sales Management
5.1 Customer Information Management
5.2 Transactional Document Production
5.3 Customer Order Management
5.6 Customer Service Representative Toolbox
5.8 Customer Problem Management
5.5 Customer Contact Management, Retention & Loyalty
5.4 Customer Self Management
5.18 Customer SLA Management
5.17 Case Management
5.9 Receivables Management
5.10 Billing Inquiry, Dispute & Adjustment Management
5.11 Bill Format / Render
5.13 Billing Account Management
5.14 Collection Management
5.15 Bill Calculation
5.19 Charge Calculation and Balance Management
Service Delivery Platform
6.1 Service Catalog Management
6.3 Service Order Management
7.1 Resource Lifecycle Management(7.1.7 Resource Catalog Management)
7.3 Resource Order Management
6.2 Service Inventory Management
6.5 Service Problem Management
6.9 Service Quality Management
7.2 Resource Inventory Management
7.4 Resource Domain Management
6.8 Service Test Management
6.7 Service Performance Management
7.9 Resource Performance Management
7.1 Resource Lifecycle Management(without 7.1.7)
7.11 Resource Test Management
7.10 Fault Management
7.7 Billing Data Mediation
7.8 Real-time Billing Mediation
8.3 Wholesale / Interconnect Billing
Portfolio Lifecycle Management Platform
4.3 Product Lifecycle Management
4.4 Product Performance Management
11.1 Catalog Management
7.12 Workforce Management
8.1 Supply Chain Management
9.2 HR Management
9.3 Financial Management
9.4 Asset Management
Enterprise Service Bus Business Process Management
Data Mapping & Transformation
In functional scope of Phase 3
In functional scope, but application introduced in later Phase
Out of functional scope of Phase 3
Service Repository
Phase 1
Phase 2
Phase 3
Functional IT architecture
Functional requirement
platform
Assurance
A_01_Manage Customer Problem
A_02_Manage ServIce Trouble
A_03_Manage Resource Trouble
A_04_Manage S/P Trouble
A_05_Manage Customer SLA
A_06_Manage ServIce Quality
A_07_Manage Resource Performance
A_08_Manage S/P Performance
A_09_Collect & Distribute Performance & Usage Data
Enterprise Management
EM_01_Manage Field Forces
EM_02_Manage Logistics
EM_03_Manage Finances
EM_04_Manage Asset
EM_05_Manage Procurement
EM_06_Manage Human Resources
Supply Chain Management
SC_01_Manage S/P Engagement
SC_02_Manage S/P Contract
SC_03_Deliver S/P Requisition Order
Portfolio Lifecycle Management
PLM_01_Innovate & Retire Product Offering
PLM_02_Innovate & Retire Product Technology
PLM_03_Manage Offering Portfolio
PLM_04_Manage Technical Portfolio
PLM_05_Manage Portfolio Lifecycle
PLM_06_Manage Offering Capabilities
PLM_07_Manage Infrastructure Capabilities
PLM_08_Plan Marketing Communication & Promotions
PLM_09_Fulfill Marketing Communications & Promotions
SC_04_Manage Supplier Payments
Prio 1
Prio 2Out of scope
Prio 3
Customer Relationship
CR_01_Manage Customer Interaction
CR_02_Manage Customer Self-Service
CR_03_Manage Customer Data
Fulfillment
F_01_Establish Customer Offer
F_02_Check Feasibility
F_03_Design Customer Solution
F_04_Deliver Customer Order
F_05_Deliver Service Order
F_06_Deliver Resource Order
Billing
B_01_Invoice Customer
B_03_Collect Customer Payments
B_04_Manage Customer Debt
B_05_Manage Bill Inquiry
B_06_Manage Compensation
B_02_Determine Price Charges
Network Management Platform Billing Platform
Enterprise Management Platform
Integration Infrastructure
Customer Management Platform
4.2 Product Catalog Management
3.5 M/S Corporate Sales Management
5.1 Customer Information Management
5.2 Transactional Document Production
5.3 Customer Order Management
5.6 Customer Service Representative Toolbox
5.8 Customer Problem Management
5.5 Customer Contact Management, Retention & Loyalty
5.4 Customer Self Management
5.18 Customer SLA Management
5.17 Case Management
5.9 Receivables Management
5.10 Billing Inquiry, Dispute & Adjustment Management
5.11 Bill Format / Render
5.13 Billing Account Management
5.14 Collection Management
5.15 Bill Calculation
5.19 Charge Calculation and Balance Management
Service Delivery Platform
6.1 Service Catalog Management
6.3 Service Order Management
7.1 Resource Lifecycle Management(7.1.7 Resource Catalog Management)
7.3 Resource Order Management
6.2 Service Inventory Management
6.5 Service Problem Management
6.9 Service Quality Management
7.2 Resource Inventory Management
7.4 Resource Domain Management
6.8 Service Test Management
6.7 Service Performance Management
7.9 Resource Performance Management
7.1 Resource Lifecycle Management(without 7.1.7)
7.11 Resource Test Management
7.10 Fault Management
7.7 Billing Data Mediation
7.8 Real-time Billing Mediation
8.3 Wholesale / Interconnect Billing
Portfolio Lifecycle Management Platform
4.3 Product Lifecycle Management
4.4 Product Performance Management
11.1 Catalog Management
7.12 Workforce Management
8.1 Supply Chain Management
9.2 HR Management
9.3 Financial Management
9.4 Asset Management
Enterprise Service Bus Business Process Management
Data Mapping & Transformation
In functional scope of Phase 1
In functional scope, but application introduced in later Phase
Out of functional scope of Phase 1
Service Repository
Network Management Platform Billing Platform
Enterprise Management Platform
Integration Infrastructure
Customer Management Platform
4.2 Product Catalog Management
3.5 M/S Corporate Sales Management
5.1 Customer Information Management
5.2 Transactional Document Production
5.3 Customer Order Management
5.6 Customer Service Representative Toolbox
5.8 Customer Problem Management
5.5 Customer Contact Management, Retention & Loyalty
5.4 Customer Self Management
5.18 Customer SLA Management
5.17 Case Management
5.9 Receivables Management
5.10 Billing Inquiry, Dispute & Adjustment Management
5.11 Bill Format / Render
5.13 Billing Account Management
5.14 Collection Management
5.15 Bill Calculation
5.19 Charge Calculation and Balance Management
Service Delivery Platform
6.1 Service Catalog Management
6.3 Service Order Management
7.1 Resource Lifecycle Management(7.1.7 Resource Catalog Management)
7.3 Resource Order Management
6.2 Service Inventory Management
6.5 Service Problem Management
6.9 Service Quality Management
7.2 Resource Inventory Management
7.4 Resource Domain Management
6.8 Service Test Management
6.7 Service Performance Management
7.9 Resource Performance Management
7.1 Resource Lifecycle Management(without 7.1.7)
7.11 Resource Test Management
7.10 Fault Management
7.7 Billing Data Mediation
7.8 Real-time Billing Mediation
8.3 Wholesale / Interconnect Billing
Portfolio Lifecycle Management Platform
4.3 Product Lifecycle Management
4.4 Product Performance Management
11.1 Catalog Management
7.12 Workforce Management
8.1 Supply Chain Management
9.2 HR Management
9.3 Financial Management
9.4 Asset Management
Enterprise Service Bus Business Process Management
Data Mapping & Transformation
In functional scope of Phase 2
In functional scope, but application introduced in later Phase
Out of functional scope of Phase 2
Service Repository
Network Management Platform Billing Platform
Enterprise Management Platform
Integration Infrastructure
Customer Management Platform
4.2 Product Catalog Management
3.5 M/S Corporate Sales Management
5.1 Customer Information Management
5.2 Transactional Document Production
5.3 Customer Order Management
5.6 Customer Service Representative Toolbox
5.8 Customer Problem Management
5.5 Customer Contact Management, Retention & Loyalty
5.4 Customer Self Management
5.18 Customer SLA Management
5.17 Case Management
5.9 Receivables Management
5.10 Billing Inquiry, Dispute & Adjustment Management
5.11 Bill Format / Render
5.13 Billing Account Management
5.14 Collection Management
5.15 Bill Calculation
5.19 Charge Calculation and Balance Management
Service Delivery Platform
6.1 Service Catalog Management
6.3 Service Order Management
7.1 Resource Lifecycle Management(7.1.7 Resource Catalog Management)
7.3 Resource Order Management
6.2 Service Inventory Management
6.5 Service Problem Management
6.9 Service Quality Management
7.2 Resource Inventory Management
7.4 Resource Domain Management
6.8 Service Test Management
6.7 Service Performance Management
7.9 Resource Performance Management
7.1 Resource Lifecycle Management(without 7.1.7)
7.11 Resource Test Management
7.10 Fault Management
7.7 Billing Data Mediation
7.8 Real-time Billing Mediation
8.3 Wholesale / Interconnect Billing
Portfolio Lifecycle Management Platform
4.3 Product Lifecycle Management
4.4 Product Performance Management
11.1 Catalog Management
7.12 Workforce Management
8.1 Supply Chain Management
9.2 HR Management
9.3 Financial Management
9.4 Asset Management
Enterprise Service Bus Business Process Management
Data Mapping & Transformation
In functional scope of Phase 3
In functional scope, but application introduced in later Phase
Out of functional scope of Phase 3
Service RepositoryBBI Business Goals 3
BBI Business Goals 2
BBI Business Goals 1
Customer Relationship
CR_01_Manage Customer Interaction
CR_02_Manage Customer Self-Service
CR_03_Manage Customer Data
Fulfillment
F_01_Establish Customer Offer
F_02_Check Feasibility
F_03_Design Customer Solution
F_04_Deliver Customer Order
F_05_Deliver Service Order
F_06_Deliver Resource Order
Billing
B_01_Invoice Customer
B_03_Collect Customer Payments
B_04_Manage Customer Debt
B_05_Manage Bill Inquiry
B_06_Manage Compensation
Assurance
A_01_Manage Customer Problem
A_02_Manage ServIce Trouble
A_03_Manage Resource Trouble
A_04_Manage S/P Trouble
A_05_Manage Customer SLA
A_06_Manage ServIce Quality
A_07_Manage Resource Performance
A_08_Manage S/P Performance
A_09_Collect & Distribute Performance & Usage Data
Enterprise Management
EM_01_Manage Field Forces
EM_02_Manage Logistics
EM_03_Manage Finances
EM_04_Manage Asset
EM_05_Manage Procurement
EM_06_Manage Human Resources
Supply Chain Management
SC_01_Manage S/P Engagement
SC_02_Manage S/P Contract
SC_03_Deliver S/P Requisition Order
Portfolio Lifecycle Management
PLM_01_Innovate & Retire Product Offering
PLM_02_Innovate & Retire Product Technology
PLM_03_Manage Offering Portfolio
PLM_04_Manage Technical Portfolio
PLM_05_Manage Portfolio Lifecycle
PLM_06_Manage Offering Capabilities
PLM_07_Manage Infrastructure Capabilities
PLM_08_Plan Marketing Communication & Promotions
PLM_09_Fulfill Marketing Communications & Promotions
SC_04_Manage Supplier Payments
B_02_Determine Price Charges
Network Management Platform Billing Platform
Enterprise Management Platform
Integration Infrastructure
Customer Management Platform
4.2 Product Catalog Management
3.5 Corporate Sales Management
5.1 Customer Information Management
5.2 Transactional Document Production
5.3 Customer Order Management
5.6 Customer Service Representative Toolbox
5.8 Customer Problem Management
5.5 Customer Contact Management, Retention & Loyalty
5.4 Customer Self Management
5.18 Customer SLA Management
5.17 Case Management
5.9 Receivables Management
5.10 Billing Inquiry, Dispute & Adjustment Management
5.11 Bill Format / Render
5.13 Billing Account Management
5.14 Collection Management
5.15 Bill Calculation
5.19 Charge Calculation and Balance Management
Service Delivery Platform
6.1 Service Catalog Management
6.3 Service Order Management
7.1 Resource Lifecycle Management(7.1.7 Resource Catalog Management)
7.3 Resource Order Management
6.2 Service Inventory Management
6.5 Service Problem Management
6.9 Service Quality Management
7.2 Resource Inventory Management
7.4 Resource Domain Management
6.8 Service Test Management
6.7 Service Performance Management
7.9 Resource Performance Management
7.1 Resource Lifecycle Management(without 7.1.7)
7.11 Resource Test Management
7.10 Fault Management
7.7 Billing Data Mediation
7.8 Real-time Billing Mediation
8.3 Wholesale / Interconnect Billing
Portfolio Lifecycle Management Platform
4.3 Product Lifecycle Management
4.4 Product Performance Management
11.1 Catalog Management
7.12 Workforce Management
8.1 Supply Chain Management
9.2 HR Management
9.3 Financial Management
9.4 Asset Management
Enterprise Service Bus Business Process Management Data Mapping & Transformation Service Repository
Business Process
Framework (eTOM)
For The Information and
Communications Services
Industry
Addendum E:End-to-End Business Flows
Release 9.0
GB921 Addendum E
Version 9.1
Phase 1 Phase 2 Phase 3
Phase 1
Phase 2
Phase 3
Use Case Name Manage Customer Interaction
Use Case Description
Manage Customer Interaction (UC) is responsible for a consistent and accurate handling of all interactions between BBI and potential and existing customers across
all interfaces available (customer contact center, KAM, face to face). It deals with
contact management, understanding the reason for contact, directing customer
contacts to the appropriate process, contact closure, exception management, contact results analysis and reporting. The customer contact history and reports are
made accessible to all actors involved in customer interactions.
Furthermore, Manage Customer Interaction (UC) is responsible to validate
customer satisfaction after a customer interaction and to initiate relevant actions
ensuring customer satisfaction.
Contacts may be customer initiated or provider initiated and be rela ted to one or
several of Service Fulfillment, Service Assurance (service quality management and
trouble or problem management) and Billing related customer enquiries or
contacts.
Remark: Manage Customer Interaction (UC) focuses on personal customer
interactions (KAM, CC, …). Customer Self-Service over a customer portal is covered
in a separate UC Manage Customer Self-Service (UC)
Business Process
Framework
level 2
1.1.1.1 CRM - Support & Readiness
1.1.1.2 Customer Interface Management 1.1.1.9 Retention & Loyalty
Information Framework domain / level 1 ABEs
Common / PartyRole, Business Interaction Customer / Customer
TAM domain / level 1
app
5.1 Customer Information Management
5.17 Case Management 5.5 Customer Contact Management, Retention & Loyalty
Actors
Primary : Customer
Secondary :
[TSP-EXP]_CRMSelling (e.g. BBI KAM) ,
[TSP-EXP]_CRMRepresentative (e.g BBI CCC,)
Use Case Name Manage Customer Interaction
Use Case Description
Manage Customer Interaction (UC) is responsible for a consistent and accurate handling of all interactions between BBI and potential and existing customers across
all interfaces available (customer contact center, KAM, face to face). It deals with
contact management, understanding the reason for contact, directing customer
contacts to the appropriate process, contact closure, exception management, contact results analysis and reporting. The customer contact history and reports are
made accessible to all actors involved in customer interactions.
Furthermore, Manage Customer Interaction (UC) is responsible to validate
customer satisfaction after a customer interaction and to initiate relevant actions
ensuring customer satisfaction.
Contacts may be customer initiated or provider initiated and be rela ted to one or
several of Service Fulfillment, Service Assurance (service quality management and
trouble or problem management) and Billing related customer enquiries or
contacts.
Remark: Manage Customer Interaction (UC) focuses on personal customer
interactions (KAM, CC, …). Customer Self-Service over a customer portal is covered
in a separate UC Manage Customer Self-Service (UC)
Business Process
Framework
level 2
1.1.1.1 CRM - Support & Readiness
1.1.1.2 Customer Interface Management 1.1.1.9 Retention & Loyalty
Information Framework domain / level 1 ABEs
Common / PartyRole, Business Interaction Customer / Customer
TAM domain / level 1
app
5.1 Customer Information Management
5.17 Case Management 5.5 Customer Contact Management, Retention & Loyalty
Actors
Primary : Customer
Secondary :
[TSP-EXP]_CRMSelling (e.g. BBI KAM) ,
[TSP-EXP]_CRMRepresentative (e.g BBI CCC,)
Use Case Name Manage Customer Interaction
Use Case Description
Manage Customer Interaction (UC) is responsible for a consistent and accurate handling of all interactions between BBI and potential and existing customers across
all interfaces available (customer contact center, KAM, face to face). It deals with
contact management, understanding the reason for contact, directing customer
contacts to the appropriate process, contact closure, exception management, contact results analysis and reporting. The customer contact history and reports are
made accessible to all actors involved in customer interactions.
Furthermore, Manage Customer Interaction (UC) is responsible to validate
customer satisfaction after a customer interaction and to initiate relevant actions
ensuring customer satisfaction.
Contacts may be customer initiated or provider initiated and be rela ted to one or
several of Service Fulfillment, Service Assurance (service quality management and
trouble or problem management) and Billing related customer enquiries or
contacts.
Remark: Manage Customer Interaction (UC) focuses on personal customer
interactions (KAM, CC, …). Customer Self-Service over a customer portal is covered
in a separate UC Manage Customer Self-Service (UC)
Business Process
Framework
level 2
1.1.1.1 CRM - Support & Readiness
1.1.1.2 Customer Interface Management 1.1.1.9 Retention & Loyalty
Information Framework domain / level 1 ABEs
Common / PartyRole, Business Interaction Customer / Customer
TAM domain / level 1
app
5.1 Customer Information Management
5.17 Case Management 5.5 Customer Contact Management, Retention & Loyalty
Actors
Primary : Customer
Secondary :
[TSP-EXP]_CRMSelling (e.g. BBI KAM) ,
[TSP-EXP]_CRMRepresentative (e.g BBI CCC,)
1
Integration
Information
Business
Organization
Technology
-
Application
Phase 1
Phase 2
Phase 3
…..
Phase n
analysis Process model
Process1 Process2 Process3
analysis Process model
Process1 Process2 Process3
analysis Process model
Process1 Process2 Process3
BBI Processes
BBI High Level Business Context
Integration
Information
Business
Organization
Technology
-
Application
Phase 1
Phase 2
Phase 3
Integration
Information
Business
Organization
Technology
-
Application
Phase 1
Integration
Information
Business
Organization
Technology
-
Application
Phase 1
Phase 2
Business Analysis and Governance Model
Business ActivityModel (BAM):
Business EntityModel (BEM):
Business RoleModel (BRM):
Business
ServiceApplication
Use Case Model Edelweiss Service Consulting Sarl ©
Serge Garcia & Iwan Gramatikoff
68
pivotal tool acting as common source of truth in Broadband Infraco’s business transformation program for:
Broadband Infraco business process model: that will be consistently extended
along the phases of the transformation program
Broadband Infraco Information Model: semantic logical data model that will be
consistently extended along the phases of the transformation program
Broadband Infraco SOA design: as the functional requirement platform for SOA
service identification and design building on reusable business analysis components
Broadband Infraco organization alignment along the phases of the transformation
program
Figure 14: Broadband Infraco Business Analysis and Governance Model
As depicted in the figure above, the Business Analysis Model plays a pivotal role. It acts as a
common reference for a consistent implementation and deployment along the different areas
of redesign as well as a consolidated documentation of Broadband Infraco’s organization,
processes and components requiring information models.
Furthermore, for the processes, and process automation, the Business Analysis Model
provides the functional requirements for IT design and implementation but also the base for
business and system operating model governance along the 4 architectural layers:
Business and organization layer
Information and data layer
Integration layer
Technology and application layer
The Business Analysis Model and Architectural Governance Model extensively use the
TMForum Frameworx.
customer
customer
E2E Process Model
customer
Organization
5
Leverage and enriched the
Business Analysis Model for
future partition (e.g Phase 2 &3)
Leverage the Business
Analysis Model to def ine
and document E2E
process model
Information Model
4 Leverage the Business Analysis Model to
def ine and document the P&T information
model
3
Business Activity Model
(BAM):
Business Entity Model
(BEM):
Business Role Model
(BRM):
Business Analysis and
Governance Model
Use Case Model
SRBPE
ESB
CDM
SRBPE
ESB
CDM Service Oriented IT Architecture
Leverage the Business
Analysis Model to def ine
clear specif ication for
SOA Architecture
Leverage the Business
Analysis Model to support
organization alignmentIntegration
Information
Business
Organization
Technology
-
Application
Phase 1
Phase 2
Phase 3
…..
Phase n
1
2
69
Business Process Framework
Information Framework
Integration Layer
Application Layer
Therefore, the conformance/compliance requirement of the responder to each of the
frameworks is elementary in evaluating the respondent’s ability to master the TMForum
Frameworx usage together with their proposed solution and will thus be a key factor in the
vendor evaluation and selection.
EVALUATION CRITERIA
Technical Evaluation – Bidders will be evaluated out of 80 points and are required to achieve
minimum threshold of 65 points of 80 points for Stage 1 in order to proceed to Stage 2 (Proof
of Concept Evaluation).
Proof of Concept Evaluation - Bidder(s) are required to achieve a minimum of 15 points out
of 20 to proceed to Stage 3 (Price & B-BBEE Evaluation).
Item Functionality Evaluation Allocation
STAGE 1 (A)
1. OSS/J
15
- Management (SQM) 1
- Trouble Ticket 3
- Inventory 1
- Service Activation 1
- Billing Mediation 2
- Quality of Service (QoS) 1
- Fault Management 3
- Order Management 1
- Discovery 1
- Service Quality 1
2.
MTOSI/MTNM
15
- Service Activation 1
- Manage Service Inventory
2
- Manage Resource Inventory
2
- Resource Provisioning 2
- Resource Trouble Management 4
- Resource Performance Management
4
70
3. IPDR
4. - Supplier/Partner Settlements
2
5 - Network Data Management – Usage
3
5. Identity Management
- Identity Management
5
6. TIP
- Product Catalog 1
- Test Lifecycle Management 1
- Service Problem Management 1
- Performance Management
1
- Resource Alarm Management 1
7. Proposal Methodology (and Approach) including capability to render the required service
- Methodology and Approach - Maintenance, support, advisory and value-added services - Systems integration and architecture overview - Skills Transfer to Broadband Infraco employees
Bidders should provide a detailed proposal on how the projected will be implemented, the proposal must include time lines.
15
8. Vendor must have successfully performed at least one similar
implementation
a. No successful implementation – 0 points
b. One (1) or more successful Implementation – 10 points
The service provider must provide reference letters which
include the name of each client, client contact person,
telephone number, email and when system was implemented.
10
9. Proposed Project Manager must have managed the implementation of at least two (2) similar projects involving the proposed software within the last five years. A detailed CV(s) for Project Manager(s) must be provided.
5
10. Company must have been in business for longer than 2 years
a. <2 years = 0 points
10
71
b. ≥2 years and above years’ in business = 5 points
80 POINTS
TO QUALIFY FOR EVALUATION IN STAGE 2 (PROOF OF CONCEPT) BIDDERS NEED TO
SCORE 65 POINTS OR MORE OUT OF 80 POINTS IN STAGE 1
STAGE 2 (B)
1. Proof of Concept (POC)
- Demonstration of the proposed solution - Testing of similar systems implemented at 2 or more clients - Demonstration of the programming component - Conduct tests to show/prove compatibility with BBI’s
network equipment
20
TOTAL A + B = 100
TO QUALIFY FOR PRICE & B-BBEE EVALUATION BIDDERS NEED TO SCORE 15 POINTS
OR MORE OUT OF 20 POINTS IN STAGE 2 EVALUATION (PROOF OF CONCEPT)
72
Annexure G
PRICING
73
For each phase, the respondent shall provide detailed pricing information and estimated timelines.
The price should be at least broken down and detailed into following components:
Hardware (covering the different operating environments) Software / licenses
Note: a detailed license plan covering one time / recurring prices as well as the licensing structure (per user, element, node …) is required. The software / licenses shall cover the different operating environments.
Training Maintenance (the underlying maintenance and support contract shall be
provided) Integration
Beyond the scope of delivery of the current RFP, the respondent shall define the pricing for onsite and remote professional services.
The respondent is furthermore expected to provide for each phase an estimated timeline with a draft project plan indicating clearly key milestones.
74
STANDARD BIDDING DOCUMENT 1 - PART A: INVITATION TO BID
YOU ARE HEREBY INVITED TO BID FOR REQUIREMENTS OF BROADBAND INFRACO (SOC) LTD
BID NUMBER: INF/TEN/0222 CLOSING DATE: 02 May 2018 CLOSING TIME: 12H00 PM
DESCRIPTION
APPOINTMENT OF A SERVICE PROVIDER WHO WILL SUPPLY, INSTALL, TEST, CONFIGURE, AND INTERGRATE THE OPERATIONAL SUPPORT SYSTEM (OSS) & BUSINESS SUPPORT SYSTEMS (BSS) NETWORK ELEMENT/SYSTEM AT BROADBAND INFRACO.
BID RESPONSE DOCUMENTS MUST BE SUBMITTED THROUGH EMAIL.
SUPPLIER INFORMATION
NAME OF BIDDER
POSTAL ADDRESS
STREET ADDRESS
TELEPHONE NUMBER CODE NUMBER
CELLPHONE NUMBER
FACSIMILE NUMBER CODE NUMBER
E-MAIL ADDRESS
VAT REGISTRATION NUMBER
TAX CLEARANCE NUMBER
TCS PIN: OR CSD No:
B-BBEE STATUS LEVEL VERIFICATION CERTIFICATE [TICK APPLICABLE BOX]
Yes
No
B-BBEE STATUS LEVEL SWORN AFFIDAVIT
Yes
No
IF YES, WHO WAS THE CERTIFICATE ISSUED BY?
AN ACCOUNTING OFFICER AS CONTEMPLATED IN THE CLOSE CORPORATION ACT (CCA) AND NAME THE APPLICABLE IN THE TICK BOX
AN ACCOUNTING OFFICER AS CONTEMPLATED IN THE CLOSE CORPORATION ACT (CCA)
A VERIFICATION AGENCY ACCREDITED BY THE SOUTH AFRICAN ACCREDITATION SYSTEM (SANAS)
A REGISTERED AUDITOR
NAME: [A B-BBEE STATUS LEVEL VERIFICATION CERTIFICATE/SWORN AFFIDAVIT(FOR EMEs& QSEs) MUST BE SUBMITTED IN ORDER TO QUALIFY FOR PREFERENCE POINTS FOR B-BBEE]
ARE YOU THE ACCREDITED REPRESENTATIVE IN SOUTH AFRICA FOR THE GOODS /SERVICES /WORKS OFFERED?
Yes No [IF YES ENCLOSE PROOF]
ARE YOU A FOREIGN BASED SUPPLIER FOR THE GOODS /SERVICES /WORKS OFFERED?
Yes No [IF YES ANSWER PART B:3 BELOW ]
SIGNATURE OF BIDDER ……………………………… DATE
CAPACITY UNDER WHICH THIS BID IS SIGNED (Attach proof of authority to sign this bid; e.g. resolution of directors, etc.)
75
PART B: TERMS AND CONDITIONS FOR BIDDING
1. BID SUBMISSION:
1.1. BIDS MUST BE DELIVERED BY THE STIPULATED TIME TO THE CORRECT ADDRESS. LATE BIDS WILL NOT BE ACCEPTED FOR CONSIDERATION.
1.2. ALL BIDS MUST BE SUBMITTED ON THE OFFICIAL FORMS PROVIDED–(NOT TO BE RE-TYPED) OR ONLINE
1.3. BIDDERS MUST REGISTER ON THE CENTRAL SUPPLIER DATABASE (CSD) TO UPLOAD MANDATORY INFORMATION NAMELY:
(BUSINESS REGISTRATION/ DIRECTORSHIP/ MEMBERSHIP/IDENTITY NUMBERS; TAX COMPLIANCE STATUS; AND BANKING INFORMATION FOR VERIFICATION PURPOSES). B-BBEE CERTIFICATE OR SWORN AFFIDAVIT FOR B-BBEE MUST BE SUBMITTED TO BIDDING INSTITUTION.
1.4. WHERE A BIDDER IS NOT REGISTERED ON THE CSD, MANDATORY INFORMATION NAMELY: (BUSINESS REGISTRATION/ DIRECTORSHIP/ MEMBERSHIP/IDENTITY NUMBERS; TAX COMPLIANCE STATUS MAY NOT BE SUBMITTED WITH THE BID DOCUMENTATION. B-BBEE CERTIFICATE OR SWORN AFFIDAVIT FOR B-BBEE MUST BE SUBMITTED TO BIDDING INSTITUTION.
1.5. THIS BID IS SUBJECT TO THE PREFERENTIAL PROCUREMENT POLICY FRAMEWORK ACT 2000 AND THE PREFERENTIAL
PROCUREMENT REGULATIONS, 2017, THE GENERAL CONDITIONS OF CONTRACT (GCC) AND, IF APPLICABLE, ANY OTHER LEGISLATION OR SPECIAL CONDITIONS OF CONTRACT.
2. TAX COMPLIANCE REQUIREMENTS 2.1 BIDDERS MUST ENSURE COMPLIANCE WITH THEIR TAX OBLIGATIONS.
2.2 BIDDERS ARE REQUIRED TO SUBMIT THEIR UNIQUE PERSONAL IDENTIFICATION NUMBER (PIN) ISSUED BY SARS TO ENABLE THE ORGAN OF STATE TO VIEW THE TAXPAYER’S PROFILE AND TAX STATUS.
2.3 APPLICATION FOR TAX COMPLIANCE STATUS (TCS) OR PIN MAY ALSO BE MADE VIA E-FILING. IN ORDER TO USE THIS PROVISION, TAXPAYERS WILL NEED TO REGISTER WITH SARS AS E-FILERS THROUGH THE WEBSITE WWW.SARS.GOV.ZA.
2.4 BIDDERS MAY ALSO SUBMIT A PRINTED TCS TOGETHER WITH THE BID.
2.5 IN BIDS WHERE CONSORTIA / JOINT VENTURES / SUB-CONTRACTORS ARE INVOLVED, EACH PARTY MUST SUBMIT A SEPARATE PROOF OF TCS / PIN / CSD NUMBER.
2.6 WHERE NO TCS IS AVAILABLE BUT THE BIDDER IS REGISTERED ON THE CENTRAL SUPPLIER DATABASE (CSD), A CSD NUMBER AND PROOF MUST BE PROVIDED.
3. QUESTIONNAIRE TO BIDDING FOREIGN SUPPLIERS
3.1. IS THE BIDDER A RESIDENT OF THE REPUBLIC OF SOUTH AFRICA (RSA)? YES NO
3.2. DOES THE BIDDER HAVE A BRANCH IN THE RSA? YES NO
3.3. DOES THE BIDDER HAVE A PERMANENT ESTABLISHMENT IN THE RSA? YES NO
3.4. DOES THE BIDDER HAVE ANY SOURCE OF INCOME IN THE RSA? YES NO
IF THE ANSWER IS “NO” TO ALL OF THE ABOVE, THEN, IT IS NOT A REQUIREMENT TO OBTAIN A TAX COMPLIANCE STATUS / TAX COMPLIANCE SYSTEM PIN CODE FROM THE SOUTH AFRICAN REVENUE SERVICE (SARS) AND IF NOT REGISTER AS PER 2.3 ABOVE.
NB: FAILURE TO PROVIDE ANY OF THE ABOVE PARTICULARS MAY RENDER THE BID INVALID.
76
Annexure H: Standard Bidding Document 4
DECLARATION OF INTEREST 1. Any legal person, including persons employed by the state¹, or persons having a kinship with
persons employed by the state, including a blood relationship, may make an offer or offers in terms of this invitation to bid (includes an advertised competitive bid, a limited bid, a proposal or written price quotation). In view of possible allegations of favouritism, should the resulting bid, or part thereof, be awarded to persons employed by the state, or to persons connected with or related to them, it is required that the bidder or his/her authorised representative declare his/her position in relation to the evaluating/adjudicating authority where-
- the bidder is employed by the state; and/or - the legal person on whose behalf the bidding document is signed, has a relationship
with persons/a person who are/is involved in the evaluation and or adjudication of the bid(s), or where it is known that such a relationship exists between the person or persons for or on whose behalf the declarant acts and persons who are involved with the evaluation and or adjudication of the bid.
2. In order to give effect to the above, the following questionnaire must be completed and
submitted with the bid. 2.1 Full Name of bidder or his or her representative:
…………………………………………………………. 2.2 Identity Number:……………………………………………………………………………………… 2.3 Position occupied in the Company (director, trustee, shareholder², member):
………………………………………………………………………………………………………… 2.4 Registration number of company, enterprise, close corporation, partnership agreement or
trust: ………………………………………………………………………..………….……………… 2.5 Tax Reference Number: …………………………………………………………………………… 2.6 VAT Registration Number: …………………………………………………………………………
2.6.1 The names of all directors / trustees / shareholders / members, their individual identity
numbers, tax reference numbers and, if applicable, employee / PERSAL numbers must be indicated in paragraph 3 below.
¹“State” means – (a) any national or provincial department, national or provincial public entity or constitutional
institution within the meaning of the Public Finance Management Act, 1999 (Act No. 1 of 1999);
(b) any municipality or municipal entity; (c) provincial legislature; (d) national Assembly or the national Council of provinces; or (e) Parliament. ²”Shareholder” means a person who owns shares in the company and is actively involved in the
management of the enterprise or business and exercises control over the enterprise. 2.7 Are you or any person connected with the bidder YES / NO presently employed by the state? 2.7.1 If so, furnish the following particulars:
Name of person / director / trustee / shareholder/ member: ……....…………………………
77
Name of state institution at which you or the person connected to the bidder is employed : ………………………………………………………….. Position occupied in the state institution: ………………………………… Any other particulars: ……………………………………………………………… ……………………………………………………………… ………………………………………………………………
2.7.2 If you are presently employed by the state, did you obtain YES / NO
the appropriate authority to undertake remunerative work outside employment in the public sector?
2.7.2.1 If yes, did you attach proof of such authority to the bid YES / NO
document? (Note: Failure to submit proof of such authority, where applicable, may result in the disqualification of the bid.
2.7.2.2 If no, furnish reasons for non-submission of such proof:
……………………………………………………………………. ……………………………………………………………………. …………………………………………………………………….
2.8 Did you or your spouse, or any of the company’s directors / YES / NO trustees / shareholders / members or their spouses conduct business with the state in the previous twelve months?
2.8.1 If so, furnish particulars:
………………………………………………………………….. ………………………………………………………………….. …………………………………………………………………...
2.9 Do you, or any person connected with the bidder, have YES / NO any relationship (family, friend, other) with a person employed by the state and who may be involved with the evaluation and or adjudication of this bid?
2.9.1 If so, furnish particulars. ……………………………………………………………... …………………………………………………………..….
………………………………………………………………
2.10 Are you, or any person connected with the bidder, YES/NO aware of any relationship (family, friend, other) between
any other bidder and any person employed by the state who may be involved with the evaluation and or adjudication of this bid?
2.10.1 If so, furnish particulars.
……………………………………………………………… ……………………………………………………………… ………………………………………………………………
2.11 Do you or any of the directors / trustees / shareholders / members YES/NO
of the company have any interest in any other related companies whether or not they are bidding for this contract?
78
2.11.1 If so, furnish particulars: ……………………………………………………………………………. ……………………………………………………………………………. …………………………………………………………………………….
3 Full details of directors / trustees / members / shareholders.
Full Name Identity Number Personal Income Tax Reference Number
State Employee Number / Persal Number
4 DECLARATION
I, THE UNDERSIGNED (NAME)………………………………………………………………………
CERTIFY THAT THE INFORMATION FURNISHED IN PARAGRAPHS 2 and 3 ABOVE IS CORRECT. I ACCEPT THAT THE STATE MAY REJECT THE BID OR ACT AGAINST ME SHOULD THIS DECLARATION PROVE TO BE FALSE. ………………………………….. ..…………………………………………… Signature Date …………………………………. ……………………………………………… Position Name of bidder
November 2011
79
Annexure I: Standard Bidding Document 8
DECLARATION OF BIDDER’S PAST SUPPLY CHAIN MANAGEMENT PRACTICES
1 This Standard Bidding Document must form part of all proposals invited. 2 It serves as a declaration to be used by institutions in ensuring that when goods and
services are being procured, all reasonable steps are taken to combat the abuse of the supply chain management system.
3 The bid of any bidder may be disregarded if that bidder, or any of its directors have-
a. abused the institution’s supply chain management system; b. committed fraud or any other improper conduct in relation to such system; or c. failed to perform on any previous contract.
4 In order to give effect to the above, the following questionnaire must be completed and submitted with the bid.
Item Question Yes No
4.1 Is the bidder or any of its directors listed on the National Treasury’s Database of Restricted Suppliers as companies or persons prohibited from doing business with the public sector? (Companies or persons who are listed on this Database were informed in writing of this restriction by the Accounting Officer/Authority of the institution that imposed the restriction after the audi alteram partem rule was applied). The Database of Restricted Suppliers now resides on the National Treasury’s website(www.treasury.gov.za) and can be accessed by clicking on its link at the bottom of the home page.
Yes
No
4.1.1 If so, furnish particulars:
4.2 Is the bidder or any of its directors listed on the Register for Tender Defaulters in terms of section 29 of the Prevention and Combating of Corrupt Activities Act (No 12 of 2004)? The Register for Tender Defaulters can be accessed on the National Treasury’s website (www.treasury.gov.za) by clicking on its link at the bottom of the home page.
Yes
No
4.2.1 If so, furnish particulars:
4.3 Was the bidder or any of its directors convicted by a court of law (including a court outside of the Republic of South Africa) for fraud or corruption during the past five years?
Yes
No
4.3.1 If so, furnish particulars:
4.4 Was any contract between the bidder and any organ of state terminated during the past five years on account of failure to perform on or comply with the contract?
Yes
No
4.4.1 If so, furnish particulars:
80
Annexure H – Standard Bidding Document 8 continue
CERTIFICATION
I, THE UNDERSIGNED (FULL NAME)………………………………………………… CERTIFY THAT THE INFORMATION FURNISHED ON THIS DECLARATION FORM IS TRUE AND
CORRECT. I ACCEPT THAT, IN ADDITION TO CANCELLATION OF A CONTRACT, ACTION MAY BE TAKEN
AGAINST ME SHOULD THIS DECLARATION PROVE TO BE FALSE. ………………………………………... ………………………….. Signature Date
………………………………………. ………………………….. Position Name of Bidder
Js365bW
81
Annexure J – Standard Bidding Document 9
CERTIFICATE OF INDEPENDENT BID DETERMINATION
1 This Standard Bidding Document (SBD) must form part of all proposals¹ invited.
2 Section 4 (1) (b) (iii) of the Competition Act No. 89 of 1998, as amended, prohibits an
agreement between, or concerted practice by, firms, or a decision by an association of firms,
if it is between parties in a horizontal relationship and if it involves collusive bidding (or bid
rigging).² Collusive bidding is a pe se prohibition meaning that it cannot be justified under any
grounds.
3 Treasury Regulation 16A9 prescribes that accounting officers and accounting authorities must take all reasonable steps to prevent abuse of the supply chain management system and authorizes accounting officers and accounting authorities to:
a. disregard the bid of any bidder if that bidder, or any of its directors have abused the
institution’s supply chain management system and or committed fraud or any other improper conduct in relation to such system.
b. cancel a contract awarded to a supplier of goods and services if the supplier committed
any corrupt or fraudulent act during the bidding process or the execution of that contract.
4 This SBD serves as a certificate of declaration that would be used by institutions to ensure that,
when proposals are considered, reasonable steps are taken to prevent any form of bid-rigging.
5 In order to give effect to the above, the attached Certificate of Bid Determination (SBD 9) must
be completed and submitted with the bid:
¹ Includes price quotations, advertised competitive proposals, limited proposals and proposals.
² Bid rigging (or collusive bidding) occurs when businesses, that would otherwise be expected
to compete, secretly conspire to raise prices or lower the quality of goods and / or services for
purchasers who wish to acquire goods and / or services through a bidding process. Bid rigging
is, therefore, an agreement between competitors not to compete.
82
Annexure J – Standard Bidding Document 9 continue
CERTIFICATE OF INDEPENDENT BID DETERMINATION
I, the undersigned, in submitting the accompanying bid:
________________________________________________________________________
(Bid Number and Description)
in response to the invitation for the bid made by:
______________________________________________________________________________
(Name of Institution)
do hereby make the following statements that I certify to be true and complete in every respect:
I certify, on behalf of:_______________________________________________________that:
(Name of Bidder)
1. I have read and I understand the contents of this Certificate;
2. I understand that the accompanying bid will be disqualified if this Certificate is found not to be
true and complete in every respect;
3. I am authorized by the bidder to sign this Certificate, and to submit the accompanying bid, on
behalf of the bidder;
4. Each person whose signature appears on the accompanying bid has been authorized by the
bidder to determine the terms of, and to sign the bid, on behalf of the bidder;
5. For the purposes of this Certificate and the accompanying bid, I understand that the word
“competitor” shall include any individual or organization, other than the bidder, whether or not
affiliated with the bidder, who:
(a) has been requested to submit a bid in response to this bid invitation;
(b) could potentially submit a bid in response to this bid invitation, based on their
qualifications, abilities or experience; and
(c) provides the same goods and services as the bidder and/or is in the same line
of business as the bidder
6. The bidder has arrived at the accompanying bid independently from, and without consultation,
communication, agreement or arrangement with any competitor. However communication
between partners in a joint venture or consortium³ will not be construed as collusive bidding.
7. In particular, without limiting the generality of paragraphs 6 above, there has been no
consultation, communication, agreement or arrangement with any competitor regarding:
(a) prices;
(b) geographical area where product or service will be rendered (market
allocation)
83
(c) methods, factors or formulas used to calculate prices;
(d) the intention or decision to submit or not to submit, a bid;
(e) the submission of a bid which does not meet the specifications and conditions
of the bid; or
(f) bidding with the intention not to win the bid.
8. In addition, there have been no consultations, communications, agreements or arrangements
with any competitor regarding the quality, quantity, specifications and conditions or delivery
particulars of the products or services to which this bid invitation relates.
9. The terms of the accompanying bid have not been, and will not be, disclosed by the bidder,
directly or indirectly, to any competitor, prior to the date and time of the official bid opening or
of the awarding of the contract.
³ Joint venture or Consortium means an association of persons for the purpose of combining their expertise, property, capital, efforts, skill and knowledge in an activity for the execution of a contract.
10. I am aware that, in addition and without prejudice to any other remedy provided to combat
any restrictive practices related to proposals and contracts, proposals that are suspicious will
be reported to the Competition Commission for investigation and possible imposition of
administrative penalties in terms of section 59 of the Competition Act No 89 of 1998 and or
may be reported to the National Prosecuting Authority (NPA) for criminal investigation and or
may be restricted from conducting business with the public sector for a period not exceeding
ten (10) years in terms of the Prevention and Combating of Corrupt Activities Act No 12 of 2004
or any other applicable legislation.
………………………………………………… …………………………………
Signature Date
…………………………………………………. …………………………………
Position Name of Bidder
Js91
84
Annexure K - Standard Biding Document 6.1
PREFERENCE POINTS CLAIM FORM IN TERMS OF THE PREFERENTIAL PROCUREMENT REGULATIONS 2017
This preference form must form part of all bids invited. It contains general information and serves as a claim form for preference points for Broad-Based Black Economic Empowerment (B-BBEE) Status Level of Contribution NB: BEFORE COMPLETING THIS FORM, BIDDERS MUST STUDY THE GENERAL
CONDITIONS, DEFINITIONS AND DIRECTIVES APPLICABLE IN RESPECT OF B-BBEE, AS PRESCRIBED IN THE PREFERENTIAL PROCUREMENT REGULATIONS, 2017.
1. GENERAL CONDITIONS
1.1 The following preference point systems are applicable to all bids:
- the 80/20 system for requirements with a Rand value of up to R50 000 000 (all applicable taxes included); and
- the 90/10 system for requirements with a Rand value above R50 000 000 (all applicable taxes included).
1.2
a) The value of this bid is estimated to not exceed R50 000 000 (all applicable taxes included) and therefore the 80/20 preference point system shall be applicable; or
1.3 Points for this bid shall be awarded for:
(a) Price; and
(b) B-BBEE Status Level of Contributor.
1.4 The maximum points for this bid are allocated as follows:
POINTS
PRICE 80
B-BBEE STATUS LEVEL OF CONTRIBUTOR 20
Total points for Price and B-BBEE must not exceed
100
1.5 Failure on the part of a bidder to submit proof of B-BBEE Status level of contributor together with the bid, will be interpreted to mean that preference points for B-BBEE status level of contribution are not claimed.
1.6 The purchaser reserves the right to require of a bidder, either before a bid is adjudicated or at any time subsequently, to substantiate any claim in regard to preferences, in any manner required by the purchaser.
85
2. DEFINITIONS
(a) “B-BBEE” means broad-based black economic empowerment as defined in section 1 of the Broad-Based Black Economic Empowerment Act;
(b) “B-BBEE status level of contributor” means the B-BBEE status of an entity in terms of a code of good practice on black economic empowerment, issued in terms of section 9(1) of the Broad-Based Black Economic Empowerment Act;
(c) “bid” means a written offer in a prescribed or stipulated form in response to an invitation by an organ of state for the provision of goods or services, through price quotations, advertised competitive bidding processes or proposals;
(d) “Broad-Based Black Economic Empowerment Act” means the Broad-Based Black Economic Empowerment Act, 2003 (Act No. 53 of 2003);
(e) “EME” means an Exempted Micro Enterprise in terms of a code of good practice on black economic empowerment issued in terms of section 9 (1) of the Broad-Based Black Economic Empowerment Act;
(f) “functionality” means the ability of a tenderer to provide goods or services in accordance with specifications as set out in the tender documents.
(g) “prices” includes all applicable taxes less all unconditional discounts;
(h) “proof of B-BBEE status level of contributor” means:
1) B-BBEE Status level certificate issued by an authorized body or person;
2) A sworn affidavit as prescribed by the B-BBEE Codes of Good Practice;
3) Any other requirement prescribed in terms of the B-BBEE Act;
(i) “QSE” means a qualifying small business enterprise in terms of a code of good practice on black economic empowerment issued in terms of section 9 (1) of the Broad-Based Black Economic Empowerment Act;
(j) “rand value” means the total estimated value of a contract in Rand, calculated at the time of bid invitation, and includes all applicable taxes;
3. POINTS AWARDED FOR PRICE
3.1 THE 80/20 OR 90/10 PREFERENCE POINT SYSTEMS
A maximum of 80 or 90 points is allocated for price on the following basis: 80/20 or 90/10
min
min180
P
PPtPs or
min
min190
P
PPtPs
Where
Ps = Points scored for price of bid under consideration
Pt = Price of bid under consideration
Pmin = Price of lowest acceptable bid
86
4. POINTS AWARDED FOR B-BBEE STATUS LEVEL OF CONTRIBUTOR
4.1 In terms of Regulation 6 (2) and 7 (2) of the Preferential Procurement Regulations, preference points must be awarded to a bidder for attaining the B-BBEE status level of contribution in accordance with the table below:
B-BBEE Status Level of
Contributor
Number of points
(90/10 system)
Number of points
(80/20 system)
1 10 20
2 9 18
3 6 14
4 5 12
5 4 8
6 3 6
7 2 4
8 1 2
Non-compliant
contributor
0 0
5. BID DECLARATION
5.1 Bidders who claim points in respect of B-BBEE Status Level of Contribution must complete the following:
6. B-BBEE STATUS LEVEL OF CONTRIBUTOR CLAIMED IN TERMS OF PARAGRAPHS 1.4 AND 4.1
6.1 B-BBEE Status Level of Contributor: . = ………(maximum of 10 or 20 points)
(Points claimed in respect of paragraph 7.1 must be in accordance with the table reflected in paragraph 4.1 and must be substantiated by relevant proof of B-BBEE status level of contributor.
7. SUB-CONTRACTING
7.1 Will any portion of the contract be sub-contracted?
(Tick applicable box)
YES NO
7.1.1 If yes, indicate:
i) What percentage of the contract will be subcontracted............…………….…………%
ii) The name of the sub-
87
contractor………………………………………………………….. iii) The B-BBEE status level of the sub-
contractor......................................…………….. iv) Whether the sub-contractor is an EME or QSE
(Tick applicable box)
YES NO
v) Specify, by ticking the appropriate box, if subcontracting with an enterprise in terms of
Preferential Procurement Regulations,2017:
Designated Group: An EME or QSE which is at last 51% owned by: EME
√
QSE
√
Black people
Black people who are youth
Black people who are women
Black people with disabilities
Black people living in rural or underdeveloped areas or townships
Cooperative owned by black people
Black people who are military veterans
OR
Any EME
Any QSE
8. DECLARATION WITH REGARD TO COMPANY/FIRM
8.1 Name of
company/firm:…………………………………………………………………………….
8.2 VAT registration
number:……………………………………….…………………………………
8.3 Company registration
number:…………….……………………….…………………………….
8.4 TYPE OF COMPANY/ FIRM
Partnership/Joint Venture / Consortium
One person business/sole propriety
Close corporation
Company
(Pty) Limited [TICK APPLICABLE BOX]
8.5 DESCRIBE PRINCIPAL BUSINESS ACTIVITIES
………………………………………………………………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
…………………………..
8.6 COMPANY CLASSIFICATION
Manufacturer
88
Supplier
Professional service provider
Other service providers, e.g. transporter, etc. [TICK APPLICABLE BOX]
8.7 Total number of years the company/firm has been in
business:……………………………
8.8 I/we, the undersigned, who is / are duly authorised to do so on behalf of the
company/firm, certify that the points claimed, based on the B-BBE status level of
contributor indicated in paragraphs 1.4 and 6.1 of the foregoing certificate, qualifies
the company/ firm for the preference(s) shown and I / we acknowledge that:
i) The information furnished is true and correct;
ii) The preference points claimed are in accordance with the General Conditions as indicated in paragraph 1 of this form;
iii) In the event of a contract being awarded as a result of points claimed as shown in paragraphs 1.4 and 6.1, the contractor may be required to furnish documentary proof to the satisfaction of the purchaser that the claims are correct;
iv) If the B-BBEE status level of contributor has been claimed or obtained on a fraudulent basis or any of the conditions of contract have not been fulfilled, the purchaser may, in addition to any other remedy it may have –
(a) disqualify the person from the bidding process;
(b) recover costs, losses or damages it has incurred or suffered as a result of that person’s conduct;
(c) cancel the contract and claim any damages which it has suffered as a result of having to make less favourable arrangements due to such cancellation;
(d) recommend that the bidder or contractor, its shareholders and directors, or only the shareholders and directors who acted on a fraudulent basis, be restricted by the National Treasury from obtaining business from any organ of state for a period not exceeding 10 years, after the audi alteram partem (hear the other side) rule has been applied; and
(e) forward the matter for criminal prosecution.
………………………………………. SIGNATURE(S) OF BIDDERS(S)
DATE: …………………………………..
ADDRESS …………………………………..
…………………………………..
…………………………………..
WITNESSES 1. ……………………………………..
2. …………………………………….
www.infraco.co.za
Registration Number: 1989/001763/30
Woodmead Country Club Estate, Building No.9, No.1 Woodlands Drive, Woodmead Extension 34, South Africa
Postnet Suite 321, Private Bag X26, Sunninghill, 2157
